NoOOXML

1. Because Technical Committee 182 was looking into DIS29500, not Technical Committee 171

TC 171 - Technical Committee for Computer Software and Networks
TC 182 - Technical Committee for Information Privacy (protection?) in Computer Systems (sic!)

Hey, next time let's start new committees, "Technical Committee for Numerical Accuracy in Computer Systems" and declare that only our committee is the competent committee…

It would be useful to document who TC 182 really is, and how they became the authority on this issue when it's surely TC 171's job.

http://kt.pkn.pl/?pid=czkt&id=182

The reason of moving the issue from TC171 to TC182 is quite unclear. More on that matter - http://polishlinux.org/poland/poland-vote-for-microsoft-ooxml/

1. False: Technical Committee 171 studied DIS 29500 technically during months and decided to reject it based on technical flaws. Later magically appeared a new committee, with little relation with the matter (security), that was designated as the one in charge of to decide the vote. Curiously only Microsoft friends were allowed to be members of that committee and nobody that could risk a vote "approval without (!) comments" was allowed to get into.

2) also ditto.

3) Yes, totally balanced toward Microsoft particular interests.

Detailed information is provided by PolishLinux.

But basically, if you don't like what your technical committee concludes of its study… Change the committee!

More information about the arbitrary change of committee when the matter was already assigned and in study by one committee competent in the matter, to another committee with almost no relation with the matter (apart that almost all its members were Microsoft friends/partners).

Who knows the name of the corrupt?

Say here!

It is incredible that these things appear in a democratic country of the European Union.