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

Alex Oliva, the Potential 'Successor' of RMS, Has a New Web Site
More freedom for Alex Oliva
Azure is Turning 17 This Year, Still Losing Money and Staff
Hallmark of pyramid schemes, deriving "value" out of things that do not really exist?
Richard Stallman on RISC-V and Free Hardware
Invidious is under attack by Google
IDG 'Reviews' of GNU/Linux Now Contain LLM Slop
It's typically ads or commercials... or sometimes spin disguised as news
In Gopher and Gemini Protocol People Abandon Services Based in the United States
There's no resistance whatsoever
Python and Microsoft: Pandas Should Have Known OpenDocument Format (ODF) and Microsoft Excel Are Different and Competing Things
now we're meant to think that in order to open ODF files we need some functions with "Excel" in their name
Not Only Windows, Surface, and "Hey Hi" PCs; Microsoft's Hardware Ventures Are a Dumpster Fire; HoloLens Mixed Reality Hardware Now Axed Altogether and Staff is Miserable
Microsoft is in a terrible state
Links 15/02/2025: University Price Hikes and Copyright Action Against Slop Companies
Links for the day
Slopwatch: All Those New 'Articles' Are Fake and Crafted by Chatbots (LLM Slop)
Google News is promoting these as "Linux" news; they're not even made by humans
 
Links 15/02/2025: Harms to Health, Public Domain, and More
Links for the day
Gemini Links 15/02/2025: On Autistic People, AuraGem Over HTTPS
Links for the day
The Cyber Show (C|S) Speaks of the "Rise of the Nerd Reich."
This 'Valentine Episode' is quite good
Strong Momentum for the Free Software Foundation (FSF) as Winter Approaches Its End in Boston or in the Northern Hemisphere
FSF's founder, Richard Stallman, gives another talk in Italy in 9 days from now
The 'Drunken Plagiarists' Are Harming Journalism About GNU/Linux
They lessen the incentive to do real journalism abut GNU/Linux
Female Nazis and racist Swiss women
Reprinted with permission from Daniel Pocock
Links 15/02/2025: Erasing of American Science and Tesla SLAPPing Critics
Links for the day
Gemini Links 15/02/2025: Spectacles and "Before Sunset", Moving Domains Out of the US
Links for the day
Microsoft Has Only $17,482 Million Left, "Cash on Hand" Sank 40 Billion Dollars in 2 Years
Microsoft runs low on money in the bank
YouTube Layoffs Mean That YouTube is Still Losing a Lot of Money (Net Income or Profit Almost Definitely Negative)
In more recent years Google defunded many vloggers
Certificate Authority (CA) Let's Encrypt Now Down to TEN (0.3% of the Whole) in Geminispace
The number of capsules that use Let's Encrypt is, according to Lupa, about to fall to single-digit figures
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, February 14, 2025
IRC logs for Friday, February 14, 2025
Gemini Links 14/02/2025: Mysterious Friend and "Eight by Eight"
Links for the day
They Will Never Leave Linus Torvalds Alone, Rust is Just Another Way to Cause Instability and Infighting in Linux
We already identified the Rust "community" as troublemakers more than 5 years ago and we wrote about the evidence
Apple: Social Justice or Social Nationalism?
Remember to buy Apple, folks
Links 14/02/2025: Mass Layoffs at Sophos, Chatbots Failing Very Badly, "DOGE as a National Cyberattack"
Links for the day
Moving Away From Certificate Authorities (CAs) Like Let's Encrypt Means Taking Away From the US Government the Power to 'Censor' Sites by Revoking Certificates
Gemini capsule is cheap to run and easy (easier than a Web site) to maintain. More people disillusioned and frustrated with social control media flock to it.
BetaNews' Managing Editor Wayne William Took Charge of GNU/Linux Articles and His Articles Are Real (He Actually Wrote Them)
We are frankly relieved to see that Wayne William recognised the problem and did something about it
Links 14/02/2025: Publicity Rights Violated (ByteDance), Bribes to Trump Passed via Social Control Media 'Settlements' Again
Links for the day
Gemini Links 14/02/2025: Constitution, Cosmic DE, and More
Links for the day
Slopwatch: Anti-Linux Articles Published by Bots, Dominating Google News
So a lot of the Web is Microsoft chatbot-generated anti-Linux FUD
Links 14/02/2025: Measles Outbreak in Texas, Zelensky Warns Russia Will Attack a NATO Country
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, February 13, 2025
IRC logs for Thursday, February 13, 2025
Gemini Links 13/02/2025: gwit and Restart
Links for the day
Links 13/02/2025: Algorithm Bots and 'Teleport' Breakthrough
Links for the day
EPO Staff Representatives Confront the President Who Says 'F--king' in Front of Female Workers Over Measurable Discrimination Against Female Colleagues
Central Staff Committee versus Lukashenko's sponsor
IBM Layoffs in 'RTO' Clothing Reported by Thomas Claburn
This "hey hi" (AI) nonsense is just a go-to excuse that IBM and GAFAM (and many others) use
Still Waiting for the EU to Abolish the Illegal and Unconstitutional Court Linked to EPO Corruption and Lobbyism by the Patent Litigation Industry
Sadly, all the blogs that used to talk about those issues have been infiltrated and then completely hijacked by the very perpetrators of the illegality
Social Engineering of the Free Software Movement is a Corporate Takeover With Code of Conduct (CoC) to Drive Out or Expel Dissent
Richard Stallman (RMS) covered "cancel culture"
Links 13/02/2025: Mass Layoffs at Google (Disguised as "Buyouts"), Telecoms Price Hikes as Collusion/Price-Fixing
Links for the day
[Video] Richard Stallman Questions and Answers Session in Google's YouTube or Invidious
From last night
Gemini Links 13/02/2025: Broken Watches and Naming Types
Links for the day
Corrupt Bill Gates Worming His Way Into Richard Stallman Videos in Google's YouTube
Reputation laundering riding other people's names?
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, February 12, 2025
IRC logs for Wednesday, February 12, 2025