What part of "Executive Board"
makes you think they read 6,000 page XML specifications? <ge>
I think, in the best bureaucratic tradition,
they argued definitions until they convinced themselves that they didn't
need to do anything. They decided that one standard contradicts another
standard only if the proposed standard causes the existing standard not
to work. This is from analogy with the Chinese WAPI WiFi networking
standard last year that was defeated because the protocol caused radio
interference with existing 801.11 networks. So they said that OOXML
did not contradict ODF because both files could exist on the same disk
without interfering with each other. You will note that thiss argument
can be used for every XML format, every programming language, every operating
system, in fact every software standard, since software is ultimately data,
and data can be segregated on disks. So they essentially chose a
definition so narrow that it nullified the concept of "contradiction"
for most of what JTC1 has authority over.<!--
D(["mb","<div><br><span style\u003d\"color:rgb(0, 0, 153)\"><ge> Wait a second. You cannot have a OOXML document and a ODF document sitting on the same disk without having them interfer with each other. We just proved that with our tests of both ACME 374 and ODF Da Vinci plugin on the latest release of MSOffice Word 2007.\n</span><br style\u003d\"color:rgb(0, 0, 153)\"><br style\u003d\"color:rgb(0, 0, 153)\"><span style\u003d\"color:rgb(0, 0, 153)\">OOXML clearly does interfere with the loading of an ODF file into MSWord 2007. In prior versions of MSWord (98, 2000, XP, 2003
Group items tagged 
What part of "Executive Board" makes you think they read 6,000 page XML specifications? <ge>
I think, in the best bureaucratic tradition, they argued definitions until they convinced themselves that they didn't need to do anything. They decided that one standard contradicts another standard only if the proposed standard causes the existing standard not to work. This is from analogy with the Chinese WAPI WiFi networking standard last year that was defeated because the protocol caused radio interference with existing 801.11 networks. So they said that OOXML did not contradict ODF because both files could exist on the same disk without interfering with each other. You will note that thiss argument can be used for every XML format, every programming language, every operating system, in fact every software standard, since software is ultimately data, and data can be segregated on disks. So they essentially chose a definition so narrow that it nullified the concept of "contradiction" for most of what JTC1 has authority over.<!-- D(["mb","<div><br><span style\u003d\"color:rgb(0, 0, 153)\"><ge> Wait a second. You cannot have a OOXML document and a ODF document sitting on the same disk without having them interfer with each other. We just proved that with our tests of both ACME 374 and ODF Da Vinci plugin on the latest release of MSOffice Word 2007.\n</span><br style\u003d\"color:rgb(0, 0, 153)\"><br style\u003d\"color:rgb(0, 0, 153)\"><span style\u003d\"color:rgb(0, 0, 153)\">OOXML clearly does interfere with the loading of an ODF file into MSWord 2007. In prior versions of MSWord (98, 2000, XP, 2003