Bonum Certa Men Certa

The Deprecated “Smoking Screen” of OOXML Makes a Failure by Design

BSI British Standards says: “... a standard is an agreed, repeatable way of doing something. It is a published document that contains a technical specification or other precise criteria designed to be used consistently as a rule, guideline, or definition. Standards help to make life simpler and to increase the reliability and the effectiveness of many goods and services we use. They are intended to be aspirational - a summary of good and best practice rather than general practice. Standards are created by bringing together the experience and expertise of all interested parties such as the producers, sellers, buyers, users and regulators of a particular material, product, process or service.”



Whatever the OOXML file format will eventually look like if such ever appears, doesn't really make a difference for Microsoft. Office 2007 or the subsequent version of Microsoft Office will never produce a standard compliant format.

What is currently implemented in Office 2007 is NOT what is described in ECMA OOXML: ECMA OOXML is a format that Office 2007 can *read*, not the format that Office 2007 is *writing*, e.g. scripts, macros, passwords, Sharepoint tags, DRM and others. If you try encrypting a document in Office 2007, it is not longer even a zip file + XML at this point.

”It is not about what the global community needs but strictly the commercial interests of the omnipresent player.“It seems Microsoft will *NOT* change Office to become compliant with ECMA. Their marketing experts will simply advertise loud and clear that “OOXML is now an ISO standard”, and will blur the differences between MS OOXML, ECMA OOXML and ISO OOXML. This will do the trick for most people, who are not technical experts. But they will eventually get caught again in lies. It is not about what the global community needs but strictly the commercial interests of the omnipresent player.

The significant papyrus change in the format by deprecating some controversial issues in the format shows a significant failure of the format. Shuffling chapters around and putting some parts in the annex is not the answer. There are still major problems with the format as now proposed in its deprecated form, from cultural and linguistics adaptability problems, accessibility issues, to the reliance on Windows and the guidance to what is called the “DEVMODE” structure, increased patent problems, added harmonization and interoperability problems, third party implementation remains almost impossible and many others. And let us not forget the proposed format has never been implemented, tested and it not the consensus of the common.

The fact is that Office 2007 has not implemented the initially proposed ECMA format, so it is more than apparent that the new "smoke screen" proposals will never be implemented, even if they can be. It also dooms all the .docx files out there already. Is Microsoft ready for a recall or ready to develop another converter for this problem?

The TRUTH IS, every application will need to support the deprecated features in order to read files with the deprecated features, so moving stuff into deprecated status does not ease the burden of implementing DIS 29500.

If a file is one which was converted from the old format of Microsoft Office by DIS 29500 and allowed to wrap the old file in XML, it is kept unreadable for everyone else. The legacy binary formats remain closed. OOXML is still a closed format tied into to many proprietary formats.

OOXML on the trash canECMA 376 is a bomb-shaped standard. It redefines everything just to keep the legacy (and therefore a number of things that should be fixed by now, thanks to better engineering, and existing ISO standards) afloat. Why? There is a difference between preserving old files and preserving them with all internal bugs. In essence, Microsoft is shoving their own mistakes right down the throat of ECMA/ISO. Microsoft has the audacity to say the standard meets a different need, when all they mean is : we don't want to fix our bugs, because that would force us to use non-Microsoft standards, and that is unacceptable. Unfortunately, the new proposals do not change this fact.

The SpreadsheetML part of OOXML describes a “securityDescriptor” attribute, which according to the specification: “...defines user accounts who may edit this range without providing a password to access the range. Removing this attribute shall remove all permissions granted or denied to users for this range.” This is an important security-related feature that tells the application which users are allowed to edit arrange in a spreadsheet without a password. A would-be programmer implementing this feature would need to know how these user accounts are represented in the document. Are they comma-delimited? Semi-colon delimited? Space-delimited? You can't define a list without defining a list delimiter.

OOXML does not provide those details (although it does imply that more than one name is allowed). This function lacks sufficient definition to allow interoperability, which in the end is what repeatable, common use is all about. Finally, any vendor who wishes to have a competing spreadsheet product must be able to give the same results as Microsoft Excel. So a proposed ISO standard for Excel's file format must precisely specify the required calculation behavior, included precise definitions of spreadsheet functions, especially the crucial financial functions. However the specification given for spreadsheet functions in OOXML appears to be merely a dump of the end user documentation for Excel. The definitions are vague, with unstated assumptions, and in some cases clear errors in their definitions.

Furthermore, the proposed deprecated changes increase the already dramatic overlap with the established ISO standard for office documents. If creates new patent problems in such that now Microsoft reserves the right to sue you if you implement any of the deprecated stuff moved to the annex of the proposed standard.

It makes harmonization and interoperability worse than ever because without the code for interpreting the deprecated stuff, any file with deprecated data will be impossible to read properly.

Given the extent to which Office 2007 will have to be changed and the extensive coding work which would need to be done, don't you think that it is just wiser to reject OOXML as a ISO standard? It is not just one and for Microsoft to collaborate on the development of ODF and create one universal file format for everyone – the fundamental of standardization – OOXML need be rejected.

Aspirational, Consolidated are the Best Practices

An ISO Standard should not merely be the minutely detailed record of the operating characteristics of a single company's product, no matter how dominant that company is in its field. From the definitions provided by ISO and others, which were cited earlier, an International Standard should represent the “consolidated results of science, technology and industry.” A standard should be “aspirational.” In other words, it should not just show one vendor's way of accomplishing a task. It should attempt to provide “a summary of good and best practice” based on the consensus of expert opinion. It should teach the best practices for the repeatable, common practice of a given technology.

Industry records its best practices through standardization. The existing body of document and markup standards represents a compendium of reviewed, approved, and implemented best practices. The work of the World Wide Web Consortium (W3C) is especially relevant to XML document formats, since they maintain the core XML standard as well as related standards such as XHTML, CSS2, XSL, Xpath, XForms, SVG, MathML and SOAP, the standards that represent the very backbone of XML and XML-related technologies.

OOXML, however, incorporates very little of the consolidated best practices of the industry. Worse, would-be implementors of OOXML are asked to use Microsoft's proprietary, legacy formats, even when relevant and superior W3C standards are at hand. For example, Vector Markup Language (VML) was developed by Microsoft and proposed by it to the W3C, where it was evaluated by a technical committee and rejected back in 1998. The industry instead supported Scalable Vector Graphics (SVG), which was developed into a standard by the W3C and then widely adopted. The standard for XML vector graphics has been SVG for almost a decade. But OOXML uses the proprietary VML and Microsoft has only stated the intent to deprecate it.

The Culture of Self Interest is not Open



Let's be clear, an ISO standard should benefit everyone and should be developed by consensus and by open participation for all to embrace, enhance, and share. DIS 29500 as now proposed still only serves the commercial interest of one vendor and will always only serve the interest of one vendor Microsoft because that is the way it was designed.

Contributed by Russell Ossendryver / fanaticattack.com

Recent Techrights' Posts

Gemini Links 16/07/2025: Tmux and OCC25 Working TLS
Links for the day
Reboots Should Never be Necessary
"BUT WHAT ABOUT SECURITY!!"
There's Still Hope for the World Wide Web
Let's hope that the trajectory of the Web won't be leading us to over-reliance on Google, nor will it reward worthless slopfarms
Gemini Links 15/07/2025: Smolweb and Alhena 5.1.7
Links for the day
 
Links 16/07/2025: China’s Economy Grows Steadily, France Takes Action Regarding Harm to Children by GAFAM and Fentanylware (TikTok)
Links for the day
It is Not About Politics
Beware the people who try to make this about politics
Good Journalism Saves Lives
a shocking number of women die or get seriously hurt every day due to violence from a partner
Recognition of Women's Contributions to Free Software
Being passive is not an option when bad things are happening
Slopfarms Are Going to Perish Because Public Opinion is Changing
Many slopfarms will simply go offline
19 Years of Standing Up for Justice, Equality, and Truth
This week we shall take it up a notch
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, July 15, 2025
IRC logs for Tuesday, July 15, 2025
Links 15/07/2025: LLM Pollution and Pushback in Ukraine
Links for the day
Gemini Links 15/07/2025: xkcd, New Cert, and Alhena Gemlog
Links for the day
Links 15/07/2025: Press Freedom at Risk and New Facebook Blunders
Links for the day
The Danes Want GNU/Linux
David Heinemeier Hansson recently moved to GNU/Linux
Cory Doctorow Explains Why Software Freedom Matters, Whereas "Open Source" Misses the Point and Helps Monopolies
It's a very long article
BillPR (EpsteinGate-Bribed NPR) is Turning Into a Partial Slopfarm that Promotes Slop
"I went on a date with a chatbot!"
Two Weeks Passed Since Latest Large Wave of Microsoft Layoffs, More Expected Next Month
Blaming the debt on "AI" is just self-serving storytelling
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, July 14, 2025
IRC logs for Monday, July 14, 2025
Gemini Links 15/07/2025: Gemini "Style Sheets" and Switching From Microsoft GitHub to Codeberg
Links for the day
Coming Soon: Another OSI Scandal, This One Implicating Molly de Blanc
OSI has been fairly quiet lately
Outreachy & Debian pregnancy cluster, Meike Reichle evidence
Reprinted with permission from Daniel Pocock
Again, "Lunduke is Actually Sending His Audience to Attack People"
Microsoft Lunduke is not trying to "protect" Linux
XBox is Rapidly Turned Into a Slopfarm by Microsoft
Slop isn't about efficiency and saving money
One of the Most Hilarious Things About the Microsoft SLAPPs
It's so ridiculous
Financial Support for the Free Software Foundation or the GNU Project
The FSF has extended until Friday its fund-raising campaign
Illegally Hiding (or Demanding Secrecy Around) Illegal Requests or Attempts at Extortion
unlawful communications like threats
Microsoft's Halloween Documents and systemd, Wayland, Etc.
Maybe one day Wayland will be widespread. Or maybe not.
Gemini Links 14/07/2025: BOFH Archive, Updating Old Palm PDAS, and Nginx vs Slop Bots
Links for the day
Ubuntu is Becoming GAFAM-Like
What does that say about Canonical and Ubuntu?
Slopfarms Which Take Real Articles About GNU/Linux and Turn Them Into Copycats Which Are False
Even before the LLM hype those were quite common
The Firm That Picks on Techrights is Accustomed to Working With Criminals
Techrights never did anything illegal. So why is it being picked on by people who work with criminals?
Microsoft Said the Mass Layoffs Were for "Investment" in "AI", But It's Also Laying Off the "AI" and "Copilot" Staff
Months ago we showed many so-called "AI" people were getting the boot and this time it's the same
DryDeadFish is Dead, Long Live DryDeadFish
We kept checking, hoping it can recover from some temporary technical issue
For Quite Some Time Already Microsoft Attracts Crackpots, Scams, and More
Occasionally we talk about the situation at IBM as there are many parallels
Links 14/07/2025: Chatbots Broken Again, McHire LLM Shows Limits of the Hype
Links for the day
Changing One's Name Won't Change One's Past
People who have earned a bad reputation are not magically "entitled" to reset
People Who Assault Women Are Not Victims of "Distress"
It seems like an American tradition. In a country with almost 50 presidents, not even one was a female.
Slashdot Media Turned Linux Journal Into a Slopfarm and Now Slashdot Actively Promotes Anti-Linux Slopfarms
Yes, "no-nonsense" apparently means actual nonsense
Adoption of Gemini Protocol Still Growing
Gemini Protocol is being obscured by the media - it doesn't help that Google 'hijacked' the word "Gemini" - but people still manage to find out about it, download a client, and use it
Links 14/07/2025: Arresting Photographers, Threats to Revoke US Citizenship Over Criticism
Links for the day
More EPO Leaks on the Way
We hope that Mr. Rowan will actually try to refute what we say and show, not merely point the finger at the messengers
Decommodification is a Corporate Strategy Against Communities
systemd is led by Microsoft and hosted by Microsoft
copyleft.org 'Hijacked' by the People Who Attack the Person Who Created Copyleft
So far there's nothing "tasteless" in copyleft.org, but that can change at any time in the future
Asking People to Take Down Articles and Videos Only Makes These More Popular and "Viral"
If you do something bad, one of the worst things you can possibly do it try to silence those who speak about it
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, July 13, 2025
IRC logs for Sunday, July 13, 2025
Two-Thirds Towards FSF Goal, Richard Stallman to Give Talks in Europe
There are 67 left before reaching the target
Brett Wilson LLP "Takes it Personal" (Character Assassination, Not Professionalism). Everybody Can See That.
On behalf of violent men
Gemini Links 14/07/2025: Politicised Tech and "Leaving GitHub"
Links for the day