OOXML Will Pass Amid Massive Irregularities
Tokimasa notes a CNet blog predicting that OOXML will make the cut. Updegrove agrees, as does the OpenMalasia blog. Reports of irregularities continue to surface, such as this one from Norway — "The meeting: 27 people in the room, 4 of which were administrative staff from Standard Norge. The outcome: Of the 24 members attending, 19 disapproved, 5 approved. The result: The administrative staff decided that Norway wants to approve OOXML as an ISO standard." Groklaw adds reportage of odd processes in Germany and Croatia.
Sounds like something a gastroentorologist would diagnose.
This is insane.
No day goes by without hearing from some croporate giant running roughshod over the laws, procedures or institutions of democratic countries.
The United States have let a handful of mega-croporations totally wreck it's economy with the blessing of the government that was elected while pulling the wool over the electorate's eyes.
It is time for the people to revolt, and put the croporations back to where they belong by firmly asserting the power of the government over croporations, if need by, by the croporate death penalty and the confiscation of the croporation's assets.
The government has thoroughly been subverted by croporate cronies; those should be charged with subversive sedition and thrown in jail and the key tossed in the Marianas trench.
I personally see the passive of OOXML as sign of a failure in the standards process. This thing in no way should pass, and there ought to be some sort of punishment for the attempts to subvert the integrity of the process by MS.
This kind of shocking. The ISO, an organization which has existed in high regard for sixty years, is done. They will no doubt continue as a holder of legacy certifications that will continue to matter for as long as they are not superseded, but as far as a respected body they are over. In a single act they have completely discredited their own approval process and by extension everything they approve.
No one looking to establish a new, credible, standard in an field relating to software or information exchange will ever use them as a prime standards body again. They are now a marketing term and not a professional resource.
http://www.noooxml.org/open:rejectooxmlnow/
^ Some reasons
I myself am no critical analyzer of standards, but the fact that the standard will still have a microsoft copyright on it is enough for me to say no. If, let's say, it was adobe instead of microsoft (and isn't pdf, for there are opensource implementations of pdf), I would still have the same viewpoint.
Standards shouldn't have disclosed code in, which is why I believe if something like a document format is standardized, the source code should be open to all.
If I am wrong about OOXML in that way, someone correct me.
20 good reasons to disapprove OOXML
... Microsoft therefore had to rush this standard through. Its a simple matter of commercial interests!" A disapproval would motivate the submitter to contribute to the existing ISO Office format, ODF (ISO 26300). We find historical precedence for a proposed Microsoft standard being disapproved in order to constructively motivate harmonization of standards: the Microsoft VML and W3C SVG standards. Microsoft's VML was rejected at the W3C in favour in Adobe's SVG. Microsoft's response was to join the W3C working group to improve SVG which later became a W3C standard. To the extent that SVG is incorporated into ISO/IEC:26300 SVG is an official ISO/IEC/ITTF international standard.
1. ISO's "Fast Track" process was abused for standard development 'on the fly'. In the past ECMA has "fast tracked" small (50-500 page), mature and industry accepted standards. OOXML is large (6000+ pages) and immature. An editorial of Redmond Developer News described: "By contrast [to ISO 26300], the Microsoft OOXML specification takes what might be called a kitchen sink approach." -- an ISO process is not thought to become a kitchen sink for half-baked ECMA standards. OOXML was only released in 2006 and is hardly accepted by the industry. The OOXML community around the format is a community of one. All third party supporters have contractual relations with the vendor. The limitations of the "Fast Track" process; fast evaluation time frames, extremely limited time to resolve all the concerns and little room for modification has demonstrated that the "Fast Track" process was unsuitable for OOXML. It gives us little surprise as the process was never intended for standard development.
2. OOXML is a proposed parallel standard without a justification. No empirical evidence was provided for the assertion that OOXML faithfully represents the corpus of existing documents of a specific vendor as opposed to the existing ISO standard or customized versions thereof. ECMA's branding of the format as a silver bullet for archiving cannot be tested by NBs. Additionally ECMA failed to provide a mapping between the legacy binary formats and OOXML. The binary legacy specifications was only made public in 2008. Multiple standards for the very same purpose with conversion issues undermine the respect for ISO standardization. You need a consistent justification to adopt another ISO standard for the same field which is not build upon an existing ISO standard - not to mention backwards compatibility to ISO 26300 architecture.
3. OOXML's ISO agenda is to undermine the adoption of the existing ISO Office standard. OOXML evangelist Mahugh explained: "When ODF was made an ISO standard, Microsoft had to react quickly as certain governments have procurement policies which prefer ISO standards.
4. OOXML is incompatible with ISO/IEC and WTO Technical Barrier to Trade (TBT) basic principles, which ISO/IEC are supposed to respect. The BRM added the notion of "Microsoft Office 97 to Microsoft Office 2008 inclusive" to which products' formats a 'faithful representation' is sought by the proposed ISO standard. International standards are not permitted to discriminate specific vendors positively, and thus all competitors negatively. The standard would become a technical market barrier, a tool of unfair competition. Formally a standard is supposed to avoid referencing products. Non-compliance with WTO requirements on technical barriers to trade due to formalities will be an obstacle for the adoption of OOXML in the public sector and undermine trust in the ISO label.
5. The BRM heavily amended those ECMA 'dispositions of comments' it had time to discuss. The BRM only discussed about 10% of the known technical issues. Of 54 non-editorial issues covered in detail, 48 were modified at the BRM. This left 850 issues without check-over, and pushed through by a bulk vote. These
Because, unlike most other other ISO standards for documents, like fax G3 and G4 compression, and ODF (Open Document Format) OOXML literally cannot be implemented by anyone other than Microsoft. This is not because the entire rest of the world contains no competent programmers, but because the standard simply does not have enough information to do so. Microsoft wrote the proposed standard with what amount to calls into their libraries of legacy Word code, the actions of which are NOT documented, rather than "tag X requires an indent level of 30000 millipels from the indent level of the enclosing block", or whatever.
... to prevent a resurrection of Microsoft.
The entire purpose of OOXML is to subvert the increasing call for public documents to be stored in a format that can A) be read without buying Word/Office/..., on the theory that documents created in a citizen's government should be available to those citizens without paying a corporate "tax", and B) that by documenting the format of the documents, readers/editors can be created, as needed, at a future time when the original creation tool may no longer exist or have a computer on which to run, unlike, say, Word documents, where support for older formats is simply dropped by Microsoft.
Microsoft is an ongoing criminal organization, and as such, should be seized under the RICO act, and its parts sold off or its source code simply published for those parts without buyers, and the buyers should be forever blocked from forming a cartel, single company, sharing directors,
http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf
OOXML:
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%20Part%201%20(PDF).zip
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%20Part%202%20(PDF).zip
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%20Part%203%20(PDF).zip
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%20Part%204%20(PDF).zip
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%20Part%205%20(PDF).zip
Cover up? Msft is not even shy about their brazen corruption anymore.
Yes, there was corruption. Tons of it. It has all been very well documented. Read groklaw.net or noooxml.org.
What does msft care is the slashdot/groklaw crowd doesn't like it?
http://www.groklaw.net/article.php?story=20080327170359776
"the president of the European Academy for Standardisation, Tineke Egyedi, is critical of OOXML being made a standard when ODF exists already, and she believes duplicative standards conflict with WTO rules"
Not that stuff like rules or laws ever stopped msft.