ISO Releases OOXML FAQ
I Don't Believe in Imaginary Property writes "The ISO has put out a FAQ concerning OOXML, but it may raise more questions than it answers. For one, it promises to address problems if they arise in the future. PJ of Groklaw said that's akin to 'selling you a car with four different sizes of tires and assuring that that if you see it's a problem, you can always bring it in for maintenance.' It also handwaves the OSP discriminatory patent promise issues, when asked about contradictions states that some 'may still remain', and asserts that duplicate standards are 'something that need[s] to be decided by the market place.' Notably, the FAQ does not answer the question, 'what the hell were you thinking?'"
... for their NEW international standard, "how to act like a complete jackass when deciding to adopt an international standard."
Eviscerati.Org: All Hail the Eviscerati
A: Sorry, but we can't hear you over the sound of us thumbing through all these big stacks of cash.
The enemies of Democracy are
I cannot count the times people have asked me "What was the post-BRM voting on ISO/IEC 29500?"
Maybe they should rename themselves the "International Organization for Vague and Undefined Standardization, To Be Decided By The Market"
SJW: Someone who has run out of real oppression, and has to fake it.
So they're basically saying: "Since we've done a lot of successful standards before, there can't possibly be anything wrong with how this one was carried out."
My sci-fi novel, Ghost Thief, is now available from Amazon.com.
If the Imperial system consisted of definitions like "Measure this like King George III would have", I'm sure people would argue against that being a standard also.
My sci-fi novel, Ghost Thief, is now available from Amazon.com.
Living up to your name, I see.
Two absolutely key requirements for a standard are that it be well specified and possible to usefully implement. The OOXML processes wasn't even long enough for someone to *read* the standard, and all the criticisms that were submitted by standards bodies were ignored in bulk - hence there is *no way* that the ISO could have known that OOXML met those requirements.
-- The act of censorship is always worse than whatever is being censored. Always.
What people think of the 'standard' is totally relevant. Simply blindly accepting something as the golden rule is ignorant, and this will (probably) lower the esteem of this standards body for a very long time. That is damaging to the purpose of standards, and part of the reason that there are not 47 international standards bodies. Since OOXML is not the only specification out there, it behoves anyone with contrary feelings to promote their favorite standard rather than try to bring down OOXML. Okay, back to your logic problems. How do you promote your own favorite standard without verbally bashing this one that is trying to supplant the good value of your favorite standard?
Yes, I know that sounds like being negative, but you must remember that using OOXML as a design example of what standards SHOULD NOT BE is a valid method to promote the standard of your choice.
Support NYCountryLawyer RIAA vs People
We've seen blatant, ample evidence that this was a bought vote. We've seen MS bribe normally uninterested countries into voting their way. We've seen them manage to fast-track a standard when it is obviously due more scrutiny (if nothing else, due to its larger size compared to the earlier ODF standard). And we've seen *blatant* vote tampering with Norway, which voted yes despite a majority of its technical advisors voting no.
The ISO's complicity in all this cheating is plain and obvious to anyone who cares to look. Their attitude of blaming the observers is, frankly, insulting to the morals and intelligence of anyone who is speaking the truth.
Yes, this does bring suspicion on the validity of the other standards. However, the other standards do not have the blatant, obvious process tampering that this one did, nor (to my knowledge) the enormous, unscrupulous corporation with an interest in seeing the standard passed.
brennanw (5761)
One would think you'd be used to it by now.
We reviewed the process before it started, all the while during its course and afterwards as well. In other words:
"Our review process sucks so much that we can't even spot the most blatant and obvious abuse in our entire history right while it's going on under our noses."
Thanks, ISO. That removes my final doubts regarding your reliability and competence. Only leaves me to wonder how you're getting anything done right at all.
Assorted stuff I do sometimes: Lemuria.org
...if ISO was paid in euros or dollars. You'd probably want to fast-track to this degree if your bribe goes down in value the longer you take.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
I don't know much about the ISO process or about previous ISO standards, but it's entirely possible that this is the first time that an ISO standards process has been gamed so thoroughly.
There is evidence that multiple new countries signed up as ISO members *specifically* to vote in OOXML. If so, that's an extremely large scale procedural attack. If this is the first time that a procedural attack on that scale has been attempted, then the whole situation only implies that the ISO wasn't prepared to withstand an attack of that magnitude (and now are trying to cover their asses in response).
Now, if that is what occurred and the ISO goes on refusing to admit to the problem rather than trying to fix it then the ISO name will no longer be worth trusting - but the ISO still has a month or so to make a procedural catch on this issue, fix the problem, and save their reputation.
-- The act of censorship is always worse than whatever is being censored. Always.
Lots of standards have revisions. I presume that before we had 802.11 a/b/g/n we simply had 802.11.
Just hours ago I was reading the TWAIN 1.9a specification. 1.9a being a big tip-off that the spec has changed over time.
My TV and DVD player are connected with HDMI 1.3 compliant cables.
So yes, if there are problems with the standard they will change the standard. That is standard behavior if you will.
ODF: 5+ applications can write the format.
OOXML: Zero applications can write the format.
ODF Wins!
The FAQ is all about not fixing it. They're rationalizing about how they have great process and how they have to accept the result of that process. The fix is in.
And Microsoft? Now that they've built this grand machine for subverting ISO do you expect them to use it once and then throw it away? Not likely. Their duty to their shareholders and all that...
You can stick a fork in the ISO. They're done.
Help stamp out iliturcy.
IETF requires demonstrated interoperability using prototype reference implementations before they will adopt a standard.
ISO generally first adopts standards, then waits for people to prototype implementations and discover the bugs in the standard (unless someone walks in with existing technology and asks for it to be standardized). When people start reporting that aspects of the standard can't be implemented, ISO works on fixing it.
After ISO adopted the Open System Interconnection (OSI) standards, they had to set up "implementers' workshops" to figure out how to make their newly adopted standards workable. (The OSI standards are the 7-layer reference model and related protocol suite that were pushed aside by the Internet protocol suite, a.k.a TCP/IP. Many OSI protocols were never fully implemented or never made to work.)
The workshops met (one was sponsored by NIST) and produced a lot of documents on things that needed to be done to make OSI work. When the Clinton/Gore administration came into office, they killed US government support for the OSI protocols and told its agencies to use the Internet protocols.
A bunch of mindless jerks who will be the first up against the wall when the revolution comes