<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: New Paths in Standardization</title>
	<atom:link href="http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=new-paths-in-standardization</link>
	<description>Thinking the unthinkable, pondering the imponderable, effing the ineffable and scruting the inscrutable</description>
	<lastBuildDate>Tue, 07 Feb 2012 11:20:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: zbog</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1797</link>
		<dc:creator>zbog</dc:creator>
		<pubDate>Sun, 13 Apr 2008 10:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1797</guid>
		<description>Whoa, Rob, not so fast!&lt;br/&gt;Who said OOXML is a standard just yet?&lt;br/&gt;See Norway&#039;s protest:&lt;br/&gt;http://blogs.freecode.no/isene/2008/04/09/the-demonstration-speech/</description>
		<content:encoded><![CDATA[<p>Whoa, Rob, not so fast!<br />Who said OOXML is a standard just yet?<br />See Norway&#8217;s protest:<br /><a href="http://blogs.freecode.no/isene/2008/04/09/the-demonstration-speech/" rel="nofollow">http://blogs.freecode.no/isene/2008/04/09/the-demonstration-speech/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper Lund Stocholm</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1795</link>
		<dc:creator>Jesper Lund Stocholm</dc:creator>
		<pubDate>Wed, 09 Apr 2008 13:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1795</guid>
		<description>Anomyous,&lt;br/&gt;&lt;br/&gt;XPS is being dealt with by ECMA TC46 and a good guess will be that it will be submitted to SC34 in FT-mode.&lt;br/&gt;&lt;br/&gt;However -TC46 has established liaison-agreements with quite a large number of committees.&lt;br/&gt;&lt;br/&gt;From: http://www.ecma-international.org/memento/TC46-M.htm&lt;br/&gt;&lt;br/&gt;TC46 has formal liaisons with the following standards bodies:&lt;br/&gt;&lt;br/&gt;ISO/IEC JTC1/SC 28: Office equipment&lt;br/&gt;ISO/IEC JTC 1/SC 29: Coding of audio, picture, multimedia and hypermedia information&lt;br/&gt;ISO/IEC JTC 1/SC 34: Document Description and Processing Languages&lt;br/&gt;ISO TC 130 WG2: Graphic technology – Prepress data exchange&lt;br/&gt;ISO TC 171 : Document management applications&lt;br/&gt;Ecma TC45: Office Open XML Formats&lt;br/&gt;International Color Consortium&lt;br/&gt;&lt;br/&gt;It doesn&#039;t seem that they have actually produced anything yet - at least I cannot locate any available drafts of the future spec.</description>
		<content:encoded><![CDATA[<p>Anomyous,</p>
<p>XPS is being dealt with by ECMA TC46 and a good guess will be that it will be submitted to SC34 in FT-mode.</p>
<p>However -TC46 has established liaison-agreements with quite a large number of committees.</p>
<p>From: <a href="http://www.ecma-international.org/memento/TC46-M.htm" rel="nofollow">http://www.ecma-international.org/memento/TC46-M.htm</a></p>
<p>TC46 has formal liaisons with the following standards bodies:</p>
<p>ISO/IEC JTC1/SC 28: Office equipment<br />ISO/IEC JTC 1/SC 29: Coding of audio, picture, multimedia and hypermedia information<br />ISO/IEC JTC 1/SC 34: Document Description and Processing Languages<br />ISO TC 130 WG2: Graphic technology – Prepress data exchange<br />ISO TC 171 : Document management applications<br />Ecma TC45: Office Open XML Formats<br />International Color Consortium</p>
<p>It doesn&#8217;t seem that they have actually produced anything yet &#8211; at least I cannot locate any available drafts of the future spec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Holloway</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1793</link>
		<dc:creator>Matthew Holloway</dc:creator>
		<pubDate>Mon, 07 Apr 2008 11:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1793</guid>
		<description>@nate, here&#039;s a blog post I wrote about not having a final text for review...&lt;br/&gt;&lt;br/&gt;http://holloway.co.nz/blog/?p=12</description>
		<content:encoded><![CDATA[<p>@nate, here&#8217;s a blog post I wrote about not having a final text for review&#8230;</p>
<p><a href="http://holloway.co.nz/blog/?p=12" rel="nofollow">http://holloway.co.nz/blog/?p=12</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peets</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1791</link>
		<dc:creator>Peets</dc:creator>
		<pubDate>Mon, 07 Apr 2008 07:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1791</guid>
		<description>This clearly shows what happens when you let a fraudster into a deal that is more based on trust than well written contracts.  The ISO process was mainly technical, with rules aiming at standardising the process and guiding it rather than containing the sort of blatant abuse Microsoft has developed a well earned reputation for.&lt;br/&gt;&lt;br/&gt;The resulting damage is immense, but I for one expect this to have a rather strong tail end.  The EU monopoly commission has been suspiciously quiet which suggests they&#039;re busy.  If they convict a company for not disclosing interoperability standards, what will they make of a company destroying the standards process to gain full control?&lt;br/&gt;&lt;br/&gt;Worse for MS is that they already HAVE a conviction, and this event will suggest that a different approach is required to bring the company back to acceptable behaviour (IMHO impossible, a collaborative stance does not agree with Ballmers&#039; MO). This could get very, very ugly for Microsoft.&lt;br/&gt;&lt;br/&gt;And deservedly so.</description>
		<content:encoded><![CDATA[<p>This clearly shows what happens when you let a fraudster into a deal that is more based on trust than well written contracts.  The ISO process was mainly technical, with rules aiming at standardising the process and guiding it rather than containing the sort of blatant abuse Microsoft has developed a well earned reputation for.</p>
<p>The resulting damage is immense, but I for one expect this to have a rather strong tail end.  The EU monopoly commission has been suspiciously quiet which suggests they&#8217;re busy.  If they convict a company for not disclosing interoperability standards, what will they make of a company destroying the standards process to gain full control?</p>
<p>Worse for MS is that they already HAVE a conviction, and this event will suggest that a different approach is required to bring the company back to acceptable behaviour (IMHO impossible, a collaborative stance does not agree with Ballmers&#8217; MO). This could get very, very ugly for Microsoft.</p>
<p>And deservedly so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dark Phoenix (Nixa)</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1790</link>
		<dc:creator>Dark Phoenix (Nixa)</dc:creator>
		<pubDate>Mon, 07 Apr 2008 07:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1790</guid>
		<description>Well, Microsoft is already pushing Silverlight through Windows Update (using the same technique as with Internet Explorer and Windows Media Player), so it wouldn&#039;t surprise me.  But indeed, XPS is next in the queue.</description>
		<content:encoded><![CDATA[<p>Well, Microsoft is already pushing Silverlight through Windows Update (using the same technique as with Internet Explorer and Windows Media Player), so it wouldn&#8217;t surprise me.  But indeed, XPS is next in the queue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Farning</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1789</link>
		<dc:creator>David Farning</dc:creator>
		<pubDate>Sun, 06 Apr 2008 20:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1789</guid>
		<description>I think that it is fair to say that we will soon see silverlight being pushed through as open internet XML.</description>
		<content:encoded><![CDATA[<p>I think that it is fair to say that we will soon see silverlight being pushed through as open internet XML.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1784</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 04 Apr 2008 11:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1784</guid>
		<description>&gt;That 30 day period expired last Saturday,and we still have not seen the final text. I don&#039;t know if this is being held up because of the appeals being lodged, or what.&lt;br/&gt;&lt;br/&gt;Are there any support at all in directives or instructions of the organization handling the text for allowing the appeals to matter to the 30 day deadline?&lt;br/&gt;&lt;br/&gt;From my understanding the 30 day deadline is a hard limit counted from the BRM. All NBs with dignity should be sending appeals requiring that IS29500 must be withdrawn as standard since it has failed to be handled within the fast track. &lt;br/&gt;&lt;br/&gt;It seems to me like ISO forgot the situation that OOXML could be too  flawed so that the BRM instructions could not be applied within a month. &lt;br/&gt;&lt;br/&gt;What the secretary thinks about how useful it would be with OOXML as IS29500 does not matter. They might manipulate things by cherry picking options from the directives during the BRM vote, but there is no way they can do the same trick when 13.12 explictly demand the final text to be available within 30 days.</description>
		<content:encoded><![CDATA[<p>>That 30 day period expired last Saturday,and we still have not seen the final text. I don&#8217;t know if this is being held up because of the appeals being lodged, or what.</p>
<p>Are there any support at all in directives or instructions of the organization handling the text for allowing the appeals to matter to the 30 day deadline?</p>
<p>From my understanding the 30 day deadline is a hard limit counted from the BRM. All NBs with dignity should be sending appeals requiring that IS29500 must be withdrawn as standard since it has failed to be handled within the fast track. </p>
<p>It seems to me like ISO forgot the situation that OOXML could be too  flawed so that the BRM instructions could not be applied within a month. </p>
<p>What the secretary thinks about how useful it would be with OOXML as IS29500 does not matter. They might manipulate things by cherry picking options from the directives during the BRM vote, but there is no way they can do the same trick when 13.12 explictly demand the final text to be available within 30 days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1783</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 04 Apr 2008 06:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1783</guid>
		<description>Actually IE supports gestandaardiseerde versies van  HTML, ASCII, JPEG (ISO 15444), PNG, XML, TIFF, en nog een paar honderd RFC&#039;s.</description>
		<content:encoded><![CDATA[<p>Actually IE supports gestandaardiseerde versies van  HTML, ASCII, JPEG (ISO 15444), PNG, XML, TIFF, en nog een paar honderd RFC&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1782</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 03 Apr 2008 16:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1782</guid>
		<description>Rob, isn&#039;t the disregard for the post-BRM directive you mentioned a good reason for an appeal, since obviously the proper procedure hasn&#039;t been followed. Only have to find a NB that would appeal...</description>
		<content:encoded><![CDATA[<p>Rob, isn&#8217;t the disregard for the post-BRM directive you mentioned a good reason for an appeal, since obviously the proper procedure hasn&#8217;t been followed. Only have to find a NB that would appeal&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1781</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 03 Apr 2008 15:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1781</guid>
		<description>Rob, there is a typo in your comment. The JTC 1 directive on post BRM activities is 13.12, not 13.2.</description>
		<content:encoded><![CDATA[<p>Rob, there is a typo in your comment. The JTC 1 directive on post BRM activities is 13.12, not 13.2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zaine_ridling</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1780</link>
		<dc:creator>zaine_ridling</dc:creator>
		<pubDate>Thu, 03 Apr 2008 12:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1780</guid>
		<description>Mama told me there&#039;d be days like this. I&#039;m eager to see if anyone else will implement this wet string code in the market.&lt;br/&gt;&lt;br/&gt;In my little 46 years, I&#039;ve learned that you can trust nothing — especially institutions and governments, for they are so easily bought off.</description>
		<content:encoded><![CDATA[<p>Mama told me there&#8217;d be days like this. I&#8217;m eager to see if anyone else will implement this wet string code in the market.</p>
<p>In my little 46 years, I&#8217;ve learned that you can trust nothing — especially institutions and governments, for they are so easily bought off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1778</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 03 Apr 2008 00:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1778</guid>
		<description>Speaking of press releases, I have not seen one on the  IS32000 PDF standard despite it passing the ballot.</description>
		<content:encoded><![CDATA[<p>Speaking of press releases, I have not seen one on the  IS32000 PDF standard despite it passing the ballot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1777</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 02 Apr 2008 23:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1777</guid>
		<description>@Nate, the final text of OOXML has not yet been presented to NB&#039;s yet.  We had to vote on it based on a 6,045 page specification with over 1,000 change descriptions, many of which were contradictory.  &lt;br/&gt;&lt;br/&gt;JTC1 Directives, 13.2, which deals with post-BRM activities for Fast Track, states:  &quot;In not more than one month after the ballot resolution group meeting the SC Secretariat shall distribute the final report of the meeting and final DIS text in case of acceptance.&quot;&lt;br/&gt;&lt;br/&gt;That 30 day period expired last Saturday,and we still have not seen the final text.  I don&#039;t know if this is being held up because of the appeals being lodged, or what.</description>
		<content:encoded><![CDATA[<p>@Nate, the final text of OOXML has not yet been presented to NB&#8217;s yet.  We had to vote on it based on a 6,045 page specification with over 1,000 change descriptions, many of which were contradictory.  </p>
<p>JTC1 Directives, 13.2, which deals with post-BRM activities for Fast Track, states:  &#8220;In not more than one month after the ballot resolution group meeting the SC Secretariat shall distribute the final report of the meeting and final DIS text in case of acceptance.&#8221;</p>
<p>That 30 day period expired last Saturday,and we still have not seen the final text.  I don&#8217;t know if this is being held up because of the appeals being lodged, or what.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luc</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1776</link>
		<dc:creator>Luc</dc:creator>
		<pubDate>Wed, 02 Apr 2008 22:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1776</guid>
		<description>&quot;Yesterday 01-Apr-08, ISO announced that they accepted Betamax as a video tape archiving standard, in addition to the de-facto VHS tape standard.  So now, you have the choice to archive your DVDs on either ISO Betamax or VHS tape format.&quot;&lt;br/&gt;&lt;br/&gt;Does this sound stupid ?  Yes, it does.&lt;br/&gt;&lt;br/&gt;And what about this other news : &quot;Yesterday 01-Apr-08, ISO announced that they accepted OOXML as a file format archiving standard, in addition to the de-facto MS-binary standard.  So now, you have the choice to archive your ODF files on either ISO OOXML or MS-binary file format.&quot;&lt;br/&gt;&lt;br/&gt;Does this sound stupid also ?  Yes, it does.  Never mind...</description>
		<content:encoded><![CDATA[<p>&#8220;Yesterday 01-Apr-08, ISO announced that they accepted Betamax as a video tape archiving standard, in addition to the de-facto VHS tape standard.  So now, you have the choice to archive your DVDs on either ISO Betamax or VHS tape format.&#8221;</p>
<p>Does this sound stupid ?  Yes, it does.</p>
<p>And what about this other news : &#8220;Yesterday 01-Apr-08, ISO announced that they accepted OOXML as a file format archiving standard, in addition to the de-facto MS-binary standard.  So now, you have the choice to archive your ODF files on either ISO OOXML or MS-binary file format.&#8221;</p>
<p>Does this sound stupid also ?  Yes, it does.  Never mind&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Răzvan Sandu</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1775</link>
		<dc:creator>Răzvan Sandu</dc:creator>
		<pubDate>Wed, 02 Apr 2008 20:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1775</guid>
		<description>Oh, Rob, but OpenHTML *does* exist !&lt;br/&gt;&lt;br/&gt;Only it&#039;s called SilerLight:   :-(&lt;br/&gt;&lt;br/&gt;http://silverlight.net/&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;Răzvan</description>
		<content:encoded><![CDATA[<p>Oh, Rob, but OpenHTML *does* exist !</p>
<p>Only it&#8217;s called SilerLight:   :-(</p>
<p><a href="http://silverlight.net/" rel="nofollow">http://silverlight.net/</a></p>
<p>Răzvan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1774</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Wed, 02 Apr 2008 18:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1774</guid>
		<description>So Rob, how long was the completed text available to NBs between the BRM and the final tallying of votes?  Was there a complete version of DIS 29500 ever made available?  And is it available to the public yet?</description>
		<content:encoded><![CDATA[<p>So Rob, how long was the completed text available to NBs between the BRM and the final tallying of votes?  Was there a complete version of DIS 29500 ever made available?  And is it available to the public yet?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1773</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 02 Apr 2008 15:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1773</guid>
		<description>&quot;Thus VML becomes the first and only standard that Microsoft Internet Explorer fully supports.&quot;&lt;br/&gt;&lt;br/&gt;That&#039;s a bit harsh. I&#039;m pretty sure IE fully supports HTML 3.2[0]&lt;br/&gt;&lt;br/&gt;According to Wikipedia[1] the only HTML elements that IE still does not support correctly are &quot;q&quot; and &quot;object&quot;, which were not in a standard until HTML 4 was released in Dec 1997.[2]&lt;br/&gt;&lt;br/&gt;[0] http://www.w3.org/TR/REC-html32&lt;br/&gt;[1] http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(HTML)&lt;br/&gt;[2] http://www.w3.org/TR/REC-html40-971218/</description>
		<content:encoded><![CDATA[<p>&#8220;Thus VML becomes the first and only standard that Microsoft Internet Explorer fully supports.&#8221;</p>
<p>That&#8217;s a bit harsh. I&#8217;m pretty sure IE fully supports HTML 3.2[0]</p>
<p>According to Wikipedia[1] the only HTML elements that IE still does not support correctly are &#8220;q&#8221; and &#8220;object&#8221;, which were not in a standard until HTML 4 was released in Dec 1997.[2]</p>
<p>[0] <a href="http://www.w3.org/TR/REC-html32" rel="nofollow">http://www.w3.org/TR/REC-html32</a><br />[1] <a href="http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(HTML)" rel="nofollow">http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(HTML)</a><br />[2] <a href="http://www.w3.org/TR/REC-html40-971218/" rel="nofollow">http://www.w3.org/TR/REC-html40-971218/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1771</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 02 Apr 2008 13:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1771</guid>
		<description>The next in the queue is XPS.  Will this be handled by JTC1 or TC171 (which just cleared PDF standard).   TC171 currently has  15 P members and 22 O members.  We need to keep watch here.</description>
		<content:encoded><![CDATA[<p>The next in the queue is XPS.  Will this be handled by JTC1 or TC171 (which just cleared PDF standard).   TC171 currently has  15 P members and 22 O members.  We need to keep watch here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yoon Kit</title>
		<link>http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1770</link>
		<dc:creator>Yoon Kit</dc:creator>
		<pubDate>Wed, 02 Apr 2008 13:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/04/new-paths-in-standardization.html#comment-1770</guid>
		<description>Wasn&#039;t &quot;Microsoft Office OpenHTML&quot; released back in 2003?&lt;br/&gt;&lt;br/&gt;yk.</description>
		<content:encoded><![CDATA[<p>Wasn&#8217;t &#8220;Microsoft Office OpenHTML&#8221; released back in 2003?</p>
<p>yk.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.553 seconds -->

