-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://events.oasis-open.org/home/forum/2008

- From Groklaw:

,----[ Quote ]
| I gather OASIS has no sense of irony. It's a Security Challenges for the
| Information Society conference, September 30 through October 3 in New
| London: "The Forum will provide a unique opportunity for the security
| standards community (public sector, private sector and standards developing
| organizations) to come together to discuss current issues and challenges,
| strategic approaches, recent successes, and future outlooks." Microsoft is a
| Gold sponsor, and DTrace is Platinum, which is a higher category, but the
| OASIS newsletter titles the item, "Microsoft sponsors upcoming OASIS Security
| Forum near London". And so it begins, I fear.
`----


Related:

Ecma - a case study for vendor capture

,----[ Quote ]
| A small network of people of ECMA International dominated the whole ISO
| process around OOXML while technical experts of national ISO members were
| impeded by committee stuffing, rules bending and political intervention and
| the general restrictions of the revamped ISO/IEC fast-track process. Â*
|
| [...]
|
| On the right you find a picture of Jan van den Beld, back then general
| secretary of ECMA international who received the 2000 pages from Microsoft
| represented by its employee Jean Paoli (center). Jean Paoli is probably best
| known for taking the Microsoft credit for the standardization of XML. The
| other person with the beard is Adam Farquhar from the British Library, chair
| of ECMA TC 45. You also find the picture on the right in Adam Farquhar's May
| 07 presentation which advocates for OOXML. Â* Â* Â*
`----

http://www.noooxml.org/ecma-and-vendor-capture


Martin Bryan: we are getting “standardization by corporation”

,----[ Quote ]
| A November informative report of Martin Bryan, Convenor, ISO/IEC JTC1/SC34
| WG1 highlights the fallout of the ECMA-376 fast-track process for ISO. He
| says he is 'glad to be retiring before the situation becomes impossible' Â*
|
| [...]
|
| In what is an astonishingly outspoken report, Martin Bryan, Convenor, ISO/IEC
| JTC1/SC34 WG1 has given us insight into the total mess that Microsoft/ECMA
| have caused during their scandalous, underhand and unremitting attempts to
| get - what is a very poorly written specification {i.e. DIS 29500 aka OOXML,
| AR} - approved as an ISO standard. … Â* Â*
`----

http://www.noooxml.org/forum/t-30107...by-corporation


Dysfunctional ISO - Courtesy of Microsoft

http://opendotdotdot.blogspot.com/20...microsoft.html


Microsoft accused of stacking ISO committee

,----[ Quote
| In a memo sent following his last meeting as head of the working group on
| WG1, which is handling Microsoft’s application to make the Word format an ISO
| standard as ECMA 376, outgoing Governor Martin Bryan (above), an expert on
| SGML and XML, accused the company of stacking his group. Â*
`----

http://blogs.zdnet.com/open-source/?p=1777


Corrupt countries were more likely to support the OOXML document format

,----[ Quote ]
| Is this just a random coincidence? The median of the CPI index of the above
| mentioned 70 countries is 3.95. Of the most corrupted half (CPI index less
| than 3.95) 23 or 77% voted for approval (approval or approval with comments)
| and 7 or 23% for disapproval; 5 abstained. Of the least corrupted half (CPI
| index more than 3.95) 13 or 54% voted for approval and 11 or 46% voted for
| disapproval; 11 abstained - see the table below.
`----

http://www.effi.org/blog/kai-2007-09-05.en.html


Microsoft accused of more OOXML standards fiddling

,----[ Quote ]
| However the 11 new countries are refusing to say how they will vote. These
| include Cote d'Ivoire, Cyprus, Ecuador, Jamaica, Lebanon, Malta, Pakistan,
| Trinidad and Tobago, Turkey, Uruguay and Venezuela. Most people seem to think
| that these have been put there by Vole to make sure the standard gets pushed
| through.
`----

http://www.theinquirer.net/default.aspx?article=42106
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkizMpEACgkQU4xAY3RXLo49zgCeOgEVVkoZbW J1FqSBbZI3zFy5
8A4An0h0etQz4cl1W6J1Gc03xuqIMgz5
=iv1z
-----END PGP SIGNATURE-----