OOXML Still Causing Problems
More than a month after Microsoft's failed attempt to rig the ISO's OOXML adoption ballot, the aftershocks are still being felt. This time, it's the fallout from all the last minute ballot stuffers.
In the days leading up to the OOXML ballot's closure, the ISO was flooded with new members, particularly on SC 34, the committee responsible for the vote. Now, with the vote over, the new entries who were so gung-ho to be apart of the international standards community are nowhere to be found.
The result? SC 34 can't get anything done, because the new arrivals upped the quorum count, and now they're not interested in playing ball.
Justin Ryan is a Contributing Editor for Linux Journal.
|Understanding OpenStack's Success||Feb 21, 2017|
|Natalie Rusk's Scratch Coding Cards (No Starch Press)||Feb 17, 2017|
|Own Your DNS Data||Feb 16, 2017|
|IGEL Universal Desktop Converter||Feb 15, 2017|
|Simple Server Hardening||Feb 14, 2017|
|Server Technology's HDOT Alt-Phase Switched POPS PDU||Feb 13, 2017|
- Understanding OpenStack's Success
- Own Your DNS Data
- Simple Server Hardening
- Understanding Firewalld in Multi-Zone Configurations
- Teradici's Cloud Access Platform: "Plug & Play" Cloud for the Enterprise
- Returning Values from Bash Functions
- From vs. to + for Microsoft and Linux
- Tech Tip: Really Simple HTTP Server with Python
- Natalie Rusk's Scratch Coding Cards (No Starch Press)
- Bash Shell Script: Building a Better March Madness Bracket