5 ms·
Microsoft's OOXML is a joke, no matter who rubber-stamped it. It's effectively the binary Office formats expressed via XML. Any office suite adding support fo
by JoshTriplett 11y ago
Microsoft's OOXML is a joke, no matter who rubber-stamped it. It's effectively the binary Office formats expressed via XML. Any office suite adding support for it still has to include the myriad piles of compatibility hacks they did for binary Office documents. OOXML contains several "transitional purposes only" formats that were obsolete before they ever went through the joke of a "standardization process", rather than standardizing a single format; as a result, anything wanting to read real-world documents in the format has to handle all of those "transitional" formats. And OOXML contains elements like "lineWrapLikeWord6" and "useWord2002TableStyleRules".
OOXML was designed, effectively, to be the easiest possible transition from the binary Office formats rather than being the best possible document standard, or even a good document standard. Direct quote from the proponents of the standard: "OpenXML was designed from the start to be capable of faithfully representing the pre-existing corpus of word-processing documents, presentations, and spreadsheets that are encoded in binary formats defined by Microsoft Corporation."
That doesn't make it a bad representation format for a vendor's proprietary office suite, but it does make it a bad standard.
https://en.wikipedia.org/wiki/Standardization_of_Office_Open_XML https://en.wikipedia.org/wiki/Standardization_of_Office_Open... is worth reading; the "standardization" process itself was effectively politics, not technology.
By contrast, there are multiple independent implementations of ODF.
- dragonwriter 11y ago> the "standardization" process itself was effectively politics, not technology. All standardization processes are politics, pretty much by definition; defining a spec is technical, agreeing to a standard is political. Not to say that the standardization of OOXML wasn't a particularly bad outcome, but "bad" vs. "good" is a different distinction than "politics" vs. "technical". > By contrast, there are multiple independent implementations of ODF. IIRC, OOXML is implemented by OOo/LO and Google Docs as well as Microsoft Office, the former two are independent implementations from the latter, if not also from each other. (I'm not sure any of those implementations are bug-free as compared to anything that has been standardized, much less fully compatible with each other -- ISTR even the Microsoft one early on had significant reported divergences from the standard.)
- JoshTriplett 11y ago> All standardization processes are politics, pretty much by definition; defining a spec is technical, agreeing to a standard is political. Little to no "defining" went on in the OOXML process, hence my use of the phrase "rubber-stamped". What little did take place seems to have been limited to adding more documentation for dangling references to undocumented bits, such as some of the "compatibility" options. And no, there should be no "politics" in the agreement to a standard. The standard should be seeking the best solution to a problem, not the one best aligned with any particular party's best interests. No "I'll compromise on this if you compromise on that". And certainly no "let's make sure the people who would be inclined to say no don't get invited". OOXML wasn't just politics, it was dirty politics.
- dragonwriter 11y ago> Little to no "defining" went on in the OOXML process Yeah, defining a spec often happens outside of, and prior to standardization (refinement of the definition may or may not happen during a standardization process.) A standardization process with little defining can be bad or good, depending on why there is little defining. > And no, there should be no "politics" in the agreement to a standard. The standard should be seeking the best solution to a problem "Best" is subjective, and involves balancing concerns which different parties will weigh differently; producing a consensus on that is inherently a political process. > OOXML wasn't just politics, it was dirty politics. On this much, we agree.
- throwawaykf05 11y ago> The standard should be seeking the best solution to a problem, not the one best aligned with any particular party's best interests. 1. That is a rather idealistic view of the world. Standards are typically set by committees comprised of multiple parties, and all entities have an agenda. Sometimes its self-interest, sometimes it's just something like "all things being equal, we prefer doing things this way", but it undoubtedly influences the outcome. 2. Regarding OOXML, maybe the actual problem could be stated as, "the vast majority of the world's official documentation is in a proprietary format and we want to make it open in a way that doesn't inconvenience the millions of users of the existing files, because otherwise nobody would use the new format." Regardless of whether there were dirty politics, what would the best solution to that look like?