<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://purl.org/rss/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

  <channel rdf:about="http://lwn.net/headlines/276114/">
    <title>LWN: Comments on "OOXML approved as an ISO standard"</title>
    <link>http://lwn.net/Articles/276114/</link>
    <description>
This is a special feed containing comments posted
to the individual LWN article titled &quot;OOXML approved as an ISO standard&quot;.

    </description>

    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>2</syn:updateFrequency>
    <items>
      <rdf:Seq>
	<rdf:li resource="http://lwn.net/Articles/276977/rss" />
	<rdf:li resource="http://lwn.net/Articles/276474/rss" />
	<rdf:li resource="http://lwn.net/Articles/276298/rss" />
	<rdf:li resource="http://lwn.net/Articles/276258/rss" />
	<rdf:li resource="http://lwn.net/Articles/276253/rss" />
	<rdf:li resource="http://lwn.net/Articles/276252/rss" />
	<rdf:li resource="http://lwn.net/Articles/276221/rss" />
	<rdf:li resource="http://lwn.net/Articles/276222/rss" />
	<rdf:li resource="http://lwn.net/Articles/276214/rss" />
	<rdf:li resource="http://lwn.net/Articles/276210/rss" />
	<rdf:li resource="http://lwn.net/Articles/276202/rss" />
	<rdf:li resource="http://lwn.net/Articles/276160/rss" />
	<rdf:li resource="http://lwn.net/Articles/276155/rss" />
	<rdf:li resource="http://lwn.net/Articles/276142/rss" />
	<rdf:li resource="http://lwn.net/Articles/276131/rss" />
	<rdf:li resource="http://lwn.net/Articles/276126/rss" />
	<rdf:li resource="http://lwn.net/Articles/276124/rss" />
	<rdf:li resource="http://lwn.net/Articles/276121/rss" />
	<rdf:li resource="http://lwn.net/Articles/276120/rss" />
	<rdf:li resource="http://lwn.net/Articles/276119/rss" />
	<rdf:li resource="http://lwn.net/Articles/276118/rss" />
	<rdf:li resource="http://lwn.net/Articles/276117/rss" />
      
      </rdf:Seq>
    </items>

  </channel>
    <item rdf:about="http://lwn.net/Articles/276977/rss">
      <title>No it isn't</title>
      <link>http://lwn.net/Articles/276977/rss</link>
      <dc:date>2008-04-08T05:27:48+00:00</dc:date>
      <dc:creator>foo-bar</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
I didn't say it's immune to bribery. However IMHO the bribery must be on a different scale to
be efficient :-)

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276474/rss">
      <title>No it isn't</title>
      <link>http://lwn.net/Articles/276474/rss</link>
      <dc:date>2008-04-03T22:38:14+00:00</dc:date>
      <dc:creator>man_ls</dc:creator>
      <description>
      Apparently not that immune to bribery:
&lt;blockquote&gt;
There was a massive protest when Standard Norge decided that Norway will say yes to OOXML, despite the fact that most of the comitee-representatives were against.
&lt;/blockquote&gt;
&lt;a href=&quot;http://blog.abrenna.com/formal-protest-against-norways-yes-to-ooxml/&quot;&gt;
Link&lt;/a&gt; found on &lt;a href=&quot;http://lwn.net/Articles/276059/&quot;&gt;LWN cover story&lt;/a&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276298/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276298/rss</link>
      <dc:date>2008-04-03T04:17:28+00:00</dc:date>
      <dc:creator>foo-bar</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
To my understanding it won't work this way in Norway. This country is too rich and too
independent to be bribed in that trivial way. (I'm not an Norwegian BTW).
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276258/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276258/rss</link>
      <dc:date>2008-04-02T21:56:32+00:00</dc:date>
      <dc:creator>man_ls</dc:creator>
      <description>
      Oh well. Maybe a few Norwegian ministries will get a substantial discount on the next Office license, and maybe they will forget about it. It wouldn't even be illegal, probably.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276253/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276253/rss</link>
      <dc:date>2008-04-02T21:17:41+00:00</dc:date>
      <dc:creator>mszeliga</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
According to ISO rules there are now two months until the approved standard becomes a
standard, due this period any P-member may protest against the standard (and we already know
that Norway have stated that they will protest).
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276252/rss">
      <title>You think THIS is weird?</title>
      <link>http://lwn.net/Articles/276252/rss</link>
      <dc:date>2008-04-02T21:04:14+00:00</dc:date>
      <dc:creator>khim</dc:creator>
      <description>
      &lt;p&gt;Apparently Russia is using &quot;silent vote&quot;: if technical specialists say nothing (for example because they had no time or were unable to reach consensus or even if they ignored issue completely) clerks &lt;a href=&quot;http://www.info-foss.ru/news/2007/10/11/1&quot;&gt;automatically send &quot;YES&quot; vote to ISO&lt;/a&gt;. This is what happened with OOXML, but apparently this is NOT new procedure invented for OOXML. With rules like this it's a wonder that ISO creates usable specifications from time to time...&lt;/p&gt;

&lt;p&gt;OOXML cast a light on ISO's work - and it's NOT pretty. Lot's of rules, but no real substance. Even before Microsoft's manipulations. Why do we trust this organization at all?&lt;/p&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276221/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276221/rss</link>
      <dc:date>2008-04-02T19:48:56+00:00</dc:date>
      <dc:creator>ernest</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
People don't care. Beside, most people will never even hear about the real story.

Question: How many people here ever heard about how ISO made a new standard before OOXML was
proposed ? 

Did anybody here care before OOXML came along ? I didn't.

That is the current situation for 99.9% of the world.

The only reputation ISO needs is in the name.

Ernest.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276222/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276222/rss</link>
      <dc:date>2008-04-02T19:22:33+00:00</dc:date>
      <dc:creator>nix</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
In the computing field, sure. But except for a few language specs ISO has 
never really been especially important there, has it? The field prefers 
other methods (such as de facto standards, from icky Office up to, say, 
major scripting languages, many of which have only one implementation but 
are widely used nonetheless).
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276214/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276214/rss</link>
      <dc:date>2008-04-02T19:16:59+00:00</dc:date>
      <dc:creator>alecs1</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
If anyone is interested, I have a link on how voting took place in Romania:
&lt;a rel=&quot;nofollow&quot; href=&quot;http://aranea.zuavra.net/index.php/97/&quot;&gt;http://aranea.zuavra.net/index.php/97/&lt;/a&gt;
This guy details the voting process. In short, half the 27 members of the comitee joined ASRO
(The Romanian Standardization Association) in the last minute, and 10 of them voted yes. Most
of these late guys are very small companies with products based entirely on Microsoft
technologies. 
From the 15, 6 members were only made public in the day of the vote. 
The results were: 15 pro, 6 against, 5 abstained.

With the previous ocasion, *after* voting the comitee took a few minutes to actually discuss
what they voted, one of the pro voters said: &quot;hey, this standard has references to things that
are not standard, we standardise, but no really&quot;;.

I don't know about other countries, but I wouldn't expect any vertebral column from a comitee
based in Romania of these times.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276210/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276210/rss</link>
      <dc:date>2008-04-02T18:29:08+00:00</dc:date>
      <dc:creator>dark</dc:creator>
      <description>
      &lt;p&gt;Indeed. So much for ISO. ISO has approved a standard that &lt;i&gt;it hasn't 
even read&lt;/i&gt;. The text of the revised draft (which, among many other 
changes, has been split into eight parts and has 1500 new pages) was not 
available at the time of voting. I don't see how a standard organization's 
credibility can ever recover from that.
&lt;p&gt;It's not all bad. We'll just have to go back to arguing for standards 
on their merits, instead of their stamps of approval :)

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276202/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276202/rss</link>
      <dc:date>2008-04-02T17:55:38+00:00</dc:date>
      <dc:creator>dskoll</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Mmmm... point taken.

Microsoft is probably under a bit more scrutiny nowadays.  But still, ISO's credibility is
completely shot now.

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276160/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276160/rss</link>
      <dc:date>2008-04-02T16:41:00+00:00</dc:date>
      <dc:creator>nix</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Yeah, the way it was punished when Windows NT failed to actually conform to the POSIX
standard.

(Er, wait...)
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276155/rss">
      <title>Is this a joke?</title>
      <link>http://lwn.net/Articles/276155/rss</link>
      <dc:date>2008-04-02T16:19:16+00:00</dc:date>
      <dc:creator>khim</dc:creator>
      <description>
      &lt;p&gt;&lt;i&gt;Microsoft -- out of desperation -- jumped into the unknown world
of international standards, tried to manipulate it with some success
&amp;amp; finally ended up entangled forever in the big global community
where friendly US courts &amp;amp; legislators have no power
&amp;amp; the USA itself has less &amp;amp; less influence.&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;Microsoft knows &lt;b&gt;exactly&lt;/b&gt; what it does. And it's not new to &quot;the unknown world of international standards&quot;. Take a look on &lt;a href=&quot;http://www.ecma-international.org/publications/standards/Ecma-234.htm&quot;&gt;this&lt;/a&gt; international standard. Note date. Rivals had proprietary API, Microsoft had an &quot;open&quot; API. Then later when the treat passed Microsoft happily abandoned all pretence. This time stakes were higher since ODF got ISO approval but the idea is the same: make your offer &quot;standard&quot; then quickly make it irrelevant (beta of MS Office 14 is almost ready).&lt;/p&gt;

&lt;p&gt;Sorry, but this is not the first time Microsoft perverted and abused standards process. Not even close. That's just first time Microsoft perverted and abused ISO.&lt;/p&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276142/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276142/rss</link>
      <dc:date>2008-04-02T15:51:21+00:00</dc:date>
      <dc:creator>dskoll</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
If Microsoft wins a contract because it claims compliance with the OOXML ISO standard, then it
can be punished if it fails to comply with the standard.

So the ISO blessing is a double-edged sword for MSFT.

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276131/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276131/rss</link>
      <dc:date>2008-04-02T15:39:09+00:00</dc:date>
      <dc:creator>bronson</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Well, so much for the ISO!  I hope someone writes a book on how Microsoft subverted the ISO's
standards process.  I think it would be fascinating.  Clearly MS learned from their initial
gaffes and are now quite adept at it.

Oh well!  This doesn't really affect my life.  I don't think I've used a word processor since
2003.  :)
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276126/rss">
      <title>reality check</title>
      <link>http://lwn.net/Articles/276126/rss</link>
      <dc:date>2008-04-02T14:56:40+00:00</dc:date>
      <dc:creator>jabby</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
I find this view to be rather naive.

Microsoft has no problem navigating the world of international standards and patents.  It has
an army of lawyers and it knows exactly what it's doing.

Moreover, contrary to your worldview, the U.S. routinely ignores WTO rulings and strong-arms
international bodies (like the U.N.) and the trend for this behavior is on the *increase*.

Microsoft only gains credibility and wider adoption by having OOXML as an ISO standard.  It
sacrifices very little (some bureaucratic effort and the publication of some portion of its
file formats) and retains all of its other powers and benefits as an international corporate
behemoth (patents, copyrights, trademarks, trade secrets, proprietary binary blobs, DRM,
etc.).  

I'm afraid we see the situation quite differently.

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276124/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276124/rss</link>
      <dc:date>2008-04-02T14:42:40+00:00</dc:date>
      <dc:creator>jamesh</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
It isn't actually illegal not to follow an ISO standard.  If it was, then Microsoft would have
had to implement ODF :)
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276121/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276121/rss</link>
      <dc:date>2008-04-02T14:32:23+00:00</dc:date>
      <dc:creator>kh</dc:creator>
      <description>
      &lt;p&gt;&lt;a href=&quot;http://www.robweir.com/blog/2008/03/ooxmls-out-of-control-characters.html&quot;&gt;Here is one example&lt;/a&gt;, or maybe you thinking more along the lines of Kerberos?&lt;/p&gt;&lt;p&gt;And that does not even get into patent issues.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.usdoj.gov/atr/cases/ms_tuncom/major/mtc-00029523.htm&quot;&gt;Quoting&lt;/a&gt;:
&quot;17. Not content with Microsoft's corruption of the Kerberos standard, Microsoft has filed for a patent on its proprietary version. Consequently, not only will Microsoft products fail to interoperate with non-Microsoft products (because of the modification), but Microsoft will not allow anyone else to use its version unless they purchase a license from Microsoft.&quot;&lt;/p&gt;
&lt;p&gt;I think you can &lt;a href=&quot;http://msdn2.microsoft.com/en-us/library/cc206927.aspx&quot;&gt;try to license Microsoft's Kerberos patents from this page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I don't think there is any silver lining in this cloud.&lt;/p&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276120/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276120/rss</link>
      <dc:date>2008-04-02T14:17:41+00:00</dc:date>
      <dc:creator>purslow</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Exactly !  Microsoft can now be required under international law
to comply with the ISO standard &amp;amp; to publish all the material needed
to allow others to comply with it.  The company can no longer hide
behind the self-serving US legal system &amp;amp; a compliant US Congress.
Free-software developers &amp;amp; users everywhere -- incl in the USA --
can use the new international standard to force Microsoft into line.

Perhaps this is difficult for those who live in the USA to understand,
but those of us who don't should have no problem seizing the opportunity.

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276119/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276119/rss</link>
      <dc:date>2008-04-02T14:04:48+00:00</dc:date>
      <dc:creator>rfunk</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
The latest version of MS Office doesn't even comply with this standard.

Others can't comply because it references unpublished material.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276118/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276118/rss</link>
      <dc:date>2008-04-02T14:00:48+00:00</dc:date>
      <dc:creator>jnsc</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
You are one day late for an april fool's day joke.

:-(
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/276117/rss">
      <title>OOXML approved as an ISO standard</title>
      <link>http://lwn.net/Articles/276117/rss</link>
      <dc:date>2008-04-02T14:00:16+00:00</dc:date>
      <dc:creator>purslow</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
I don't like Microsoft's misbehaviours any more than the rest,
but isn't this really a big step forwards for free software ?

Apart from making a mockery of the ISO fast-track process 
&amp;amp; leaving themselves open to all kinds of appeals,
Microsoft has now tied itself down to an international standard.
Of course, it's badly flawed &amp;amp; based on their own software internals,
but they can now be required by everyone, incl free-software users,
to adhere to the ISO standard &amp;amp; to make sure their own products,
not least Microsoft Office, fully comply with it.
They can also be required to clarify any obscurities
&amp;amp; to ensure that it is actually useable by the rest of us.
Users of free office software will be able to interface
with Microsoft Office without any serious difficulties
or Microsoft will find itself facing action before the WTO &amp;amp; the courts.

Microsoft -- out of desperation -- jumped into the unknown world
of international standards, tried to manipulate it with some success
&amp;amp; finally ended up entangled forever in the big global community
where friendly US courts &amp;amp; legislators have no power
&amp;amp; the USA itself has less &amp;amp; less influence.

Let's hope the developers of Open Office, Koffice &amp;amp; the rest
are fully upto the opportunities which have opened up before them !

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
</rdf:RDF>

