The Final OOXML Update: Part III
Nov 03, 2009, 20:02 (0 Talkback[s])
(Other stories by Rob Weir)
Full Text Search: The Key to Better Natural Language Queries for NoSQL in Node.js
"In this Part I'll look at how Microsoft is using their
dominance in SC34 to push through hundreds of changes and additions
to OOXML, in a misuse of a procedure intended for correcting
drafting errors, to make OOXML "conform" to Microsoft's monopoly
"Let's start by taking a look at the OOXML defect log [PDF] that
SC34/WG4 uses to track their large list of errors and omissions
discovered in the published standard. This defect report currently
amounts to over 800 pages, longer than the entire ODF 1.0 standard.
But it is well worth downloading and browsing through.
"Some of these changes will be made in Technical Corrigenda
while others are proposed for Amendments. What is the difference?
SC34/WG4 itself made the distinction clear, in a presentation (N
1187 for those with access) it made to the SC34 Plenary in Prague,
where it outlined its practice for deciding which changes would be
made in corrigenda versus amendments:"