<?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: Amusing but Confusing</title>
	<atom:link href="http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html</link>
	<description>Thinking the unthinkable, pondering the imponderable, effing the ineffable and scruting the inscrutable</description>
	<lastBuildDate>Mon, 15 Mar 2010 13:38:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-362</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 25 Jan 2007 03:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-362</guid>
		<description>As you say, people don&#039;t confuse WordPro or WordPerfect with Word.  But they do confuse Office Open with Open Office as I demonstrated with numerous examples. &lt;br /&gt;&lt;br /&gt;Is this just a minor matter?  I guess it depends on who you are.  If I were the owner of the Open Office trademark I would not think it minor.</description>
		<content:encoded><![CDATA[<p>As you say, people don&#8217;t confuse WordPro or WordPerfect with Word.  But they do confuse Office Open with Open Office as I demonstrated with numerous examples. </p>
<p>Is this just a minor matter?  I guess it depends on who you are.  If I were the owner of the Open Office trademark I would not think it minor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-360</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 24 Jan 2007 23:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-360</guid>
		<description>I&#039;m afraid you&#039;re blowing the name problem out of proportion. Consider this: WordStar, WordPerfect, KWord, Word, Word Pro are all word processers, yet nobody confuses them. Nobody confuses Word Pro with Word, even though Word comes in a Professional edition!</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid you&#8217;re blowing the name problem out of proportion. Consider this: WordStar, WordPerfect, KWord, Word, Word Pro are all word processers, yet nobody confuses them. Nobody confuses Word Pro with Word, even though Word comes in a Professional edition!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-340</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Mon, 22 Jan 2007 16:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-340</guid>
		<description>Doug, I don&#039;t see how the &quot;Ecma&quot; versus &quot;Microsoft&quot; prefix would cause people to mistate &quot;Open Office XML&quot; for &quot;Office Open XML&quot;.  These seem to be independent errors.  &lt;br /&gt;&lt;br /&gt;In any case you may want to update the Wikipedia page for &lt;a href=&quot;http://en.wikipedia.org/wiki/Microsoft_Office_Open_XML&quot; rel=&quot;nofollow&quot;&gt;OOXML&lt;/a&gt; for that.  It currently calls it &quot;Microsoft Office Open XML&quot;.</description>
		<content:encoded><![CDATA[<p>Doug, I don&#8217;t see how the &#8220;Ecma&#8221; versus &#8220;Microsoft&#8221; prefix would cause people to mistate &#8220;Open Office XML&#8221; for &#8220;Office Open XML&#8221;.  These seem to be independent errors.  </p>
<p>In any case you may want to update the Wikipedia page for <a href="http://en.wikipedia.org/wiki/Microsoft_Office_Open_XML" rel="nofollow">OOXML</a> for that.  It currently calls it &#8220;Microsoft Office Open XML&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-339</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 22 Jan 2007 16:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-339</guid>
		<description>I would suggest using ODF and OOXML as both &lt;br /&gt;Open Document &lt;br /&gt;and&lt;br /&gt;Office Open XML seem confusing</description>
		<content:encoded><![CDATA[<p>I would suggest using ODF and OOXML as both <br />Open Document <br />and<br />Office Open XML seem confusing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Mahugh</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-338</link>
		<dc:creator>Doug Mahugh</dc:creator>
		<pubDate>Mon, 22 Jan 2007 16:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-338</guid>
		<description>Hi Rob,&lt;br /&gt;&lt;br /&gt;My point was that Bob consistently puts &quot;Microsoft&quot; in front of the name.  The standard is named &quot;Ecma Office Open XML&quot; and not &quot;Microsoft Office Open XML.&quot;  It&#039;s sort of like if somebody at MS were to consistently refer to &quot;IBM ODF&quot; as the name of the ODF standard.&lt;br /&gt;&lt;br /&gt;Bob usually puts &quot;Microsoft Office Open XML&quot; in the subject, which seems likely to contribute to confusion about the actual name.  (For example, that&#039;s the case in 6 of the 7 examples I gave, and the other one has &quot;MS Office Open XML&quot; in a sub-head.)  I understand Bob&#039;s point, that in his opinion Ecma Office Open XML is strongly associated with Microsoft, but I think it would cause less confusion if he made that point explicitly rather than renaming the standard.&lt;br /&gt;&lt;br /&gt;-  Doug</description>
		<content:encoded><![CDATA[<p>Hi Rob,</p>
<p>My point was that Bob consistently puts &#8220;Microsoft&#8221; in front of the name.  The standard is named &#8220;Ecma Office Open XML&#8221; and not &#8220;Microsoft Office Open XML.&#8221;  It&#8217;s sort of like if somebody at MS were to consistently refer to &#8220;IBM ODF&#8221; as the name of the ODF standard.</p>
<p>Bob usually puts &#8220;Microsoft Office Open XML&#8221; in the subject, which seems likely to contribute to confusion about the actual name.  (For example, that&#8217;s the case in 6 of the 7 examples I gave, and the other one has &#8220;MS Office Open XML&#8221; in a sub-head.)  I understand Bob&#8217;s point, that in his opinion Ecma Office Open XML is strongly associated with Microsoft, but I think it would cause less confusion if he made that point explicitly rather than renaming the standard.</p>
<p>-  Doug</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yoon Kit</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-336</link>
		<dc:creator>Yoon Kit</dc:creator>
		<pubDate>Mon, 22 Jan 2007 01:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-336</guid>
		<description>Im puzzled why Microsoft were not consistent with their naming conventions. After all, it was WordprocessingML, SpreadsheetML, PresentationML... &lt;br /&gt;&lt;br /&gt;... so shouldnt it be MicrosoftOfficeML? (MSOML)?&lt;br /&gt;Google doesnt bring up anything substantial for us to be confused with.&lt;br /&gt;&lt;br /&gt;yk.</description>
		<content:encoded><![CDATA[<p>Im puzzled why Microsoft were not consistent with their naming conventions. After all, it was WordprocessingML, SpreadsheetML, PresentationML&#8230; </p>
<p>&#8230; so shouldnt it be MicrosoftOfficeML? (MSOML)?<br />Google doesnt bring up anything substantial for us to be confused with.</p>
<p>yk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Storry</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-335</link>
		<dc:creator>Philip Storry</dc:creator>
		<pubDate>Sun, 21 Jan 2007 23:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-335</guid>
		<description>Luc,&lt;br /&gt;&lt;br /&gt;&quot;MSXML&quot; would cause confusion. A quick search with Google shows that many developers use that name as the core libraries that Microsoft provide for manipulating and traversing XML streams. In fact, the &quot;MSXML&quot; returns a healthy 1,999,000 hits, suggesting it&#039;s widely used by the technical community.&lt;br /&gt;&lt;br /&gt;However, MSOXML returns just 88 hits, most of which seem to be people using it as a name for Microsoft Office XML anyway.&lt;br /&gt;&lt;br /&gt;(A couple of the hits seem to be reproductions of code that I think Microsoft has put into web pages for round-trip editing of published HTML files from Office, but since it&#039;s just 88 hits and not a declared public standard, I&#039;d be willing to say this isn&#039;t relevant.)&lt;br /&gt;&lt;br /&gt;Therefore, MSOXML would be my first suggestion. One extra character makes all the difference... It stands, of course, for Microsoft Office XML. Why complicate things?&lt;br /&gt;&lt;br /&gt;Indeed, as a bonus, it&#039;s got a succinctness that eluded the specification itself... *grins*&lt;br /&gt;&lt;br /&gt;(My second is TRIX-MS - it stands for &quot;Tardy, Rushed, Incomplete XML Marketing Standard&quot;. But I suspect that this will not be approved by the vendor who owns - sorry, donated - the standard.)</description>
		<content:encoded><![CDATA[<p>Luc,</p>
<p>&#8220;MSXML&#8221; would cause confusion. A quick search with Google shows that many developers use that name as the core libraries that Microsoft provide for manipulating and traversing XML streams. In fact, the &#8220;MSXML&#8221; returns a healthy 1,999,000 hits, suggesting it&#8217;s widely used by the technical community.</p>
<p>However, MSOXML returns just 88 hits, most of which seem to be people using it as a name for Microsoft Office XML anyway.</p>
<p>(A couple of the hits seem to be reproductions of code that I think Microsoft has put into web pages for round-trip editing of published HTML files from Office, but since it&#8217;s just 88 hits and not a declared public standard, I&#8217;d be willing to say this isn&#8217;t relevant.)</p>
<p>Therefore, MSOXML would be my first suggestion. One extra character makes all the difference&#8230; It stands, of course, for Microsoft Office XML. Why complicate things?</p>
<p>Indeed, as a bonus, it&#8217;s got a succinctness that eluded the specification itself&#8230; *grins*</p>
<p>(My second is TRIX-MS &#8211; it stands for &#8220;Tardy, Rushed, Incomplete XML Marketing Standard&#8221;. But I suspect that this will not be approved by the vendor who owns &#8211; sorry, donated &#8211; the standard.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luc</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-333</link>
		<dc:creator>Luc</dc:creator>
		<pubDate>Sun, 21 Jan 2007 22:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-333</guid>
		<description>Rob,&lt;br /&gt;&lt;br /&gt;I think that there is an obvious name to be used : Microsoft XML, or MSXML in short.&lt;br /&gt;&lt;br /&gt;This name avoid any confusion, and clearly depicts the true content of the standard.&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Luc Bollen</description>
		<content:encoded><![CDATA[<p>Rob,</p>
<p>I think that there is an obvious name to be used : Microsoft XML, or MSXML in short.</p>
<p>This name avoid any confusion, and clearly depicts the true content of the standard.</p>
<p>Kind regards,<br />Luc Bollen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yoon Kit</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-330</link>
		<dc:creator>Yoon Kit</dc:creator>
		<pubDate>Sun, 21 Jan 2007 16:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-330</guid>
		<description>Rob,&lt;br /&gt;&lt;br /&gt;You wouldnt believe it, but Bill Gates also has this problem! &lt;br /&gt;&lt;br /&gt;Please read this entry from molly.com:&lt;br /&gt;&lt;br /&gt;http://www.molly.com/2006/12/14/who-questions-bill-gates-commitment-to-web-standards&lt;br /&gt;&lt;br /&gt;Bill Gates said:&lt;br /&gt;&quot;We have our smartest people who go and work on that stuff . . . we just did the OpenOffice . . . our office XML formats we contributed to them . . . we’ve got XML at the core of all our products.&quot;&lt;br /&gt;&lt;br /&gt;Is it a bad name, or is it really really clever?&lt;br /&gt;&lt;br /&gt;yk.</description>
		<content:encoded><![CDATA[<p>Rob,</p>
<p>You wouldnt believe it, but Bill Gates also has this problem! </p>
<p>Please read this entry from molly.com:</p>
<p><a href="http://www.molly.com/2006/12/14/who-questions-bill-gates-commitment-to-web-standards" rel="nofollow">http://www.molly.com/2006/12/14/who-questions-bill-gates-commitment-to-web-standards</a></p>
<p>Bill Gates said:<br />&#8220;We have our smartest people who go and work on that stuff . . . we just did the OpenOffice . . . our office XML formats we contributed to them . . . we’ve got XML at the core of all our products.&#8221;</p>
<p>Is it a bad name, or is it really really clever?</p>
<p>yk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephen o'grady</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-328</link>
		<dc:creator>stephen o'grady</dc:creator>
		<pubDate>Sun, 21 Jan 2007 00:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-328</guid>
		<description>ugh - stupid mistake on my part. thanks for the catch, Rob. i try to be careful, but suppose i just missed that one.</description>
		<content:encoded><![CDATA[<p>ugh &#8211; stupid mistake on my part. thanks for the catch, Rob. i try to be careful, but suppose i just missed that one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-327</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sat, 20 Jan 2007 21:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-327</guid>
		<description>Doug, Now you&#039;ve got me totally confused.  Help me out here.  Bob&#039;s blog entries all use the term &quot;Office Open XML&quot;.  That is what the standard is called, right?&lt;br /&gt;&lt;br /&gt;My point was how often it is misstated as &quot;Open Office XML&quot;, by users, by the press and by even Microsoft.  I wouldn&#039;t be surprised if Bob or I got it wrong once in a while.  My argument is that this is a confusing name.  But the examples you give seem to get the correct word ordering.  &lt;br /&gt;&lt;br /&gt;What am I missing here?</description>
		<content:encoded><![CDATA[<p>Doug, Now you&#8217;ve got me totally confused.  Help me out here.  Bob&#8217;s blog entries all use the term &#8220;Office Open XML&#8221;.  That is what the standard is called, right?</p>
<p>My point was how often it is misstated as &#8220;Open Office XML&#8221;, by users, by the press and by even Microsoft.  I wouldn&#8217;t be surprised if Bob or I got it wrong once in a while.  My argument is that this is a confusing name.  But the examples you give seem to get the correct word ordering.  </p>
<p>What am I missing here?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Mahugh</title>
		<link>http://www.robweir.com/blog/2007/01/amusing-but-still-confusing.html#comment-326</link>
		<dc:creator>Doug Mahugh</dc:creator>
		<pubDate>Sat, 20 Jan 2007 21:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/amusing-but-confusing.html#comment-326</guid>
		<description>FYI, you missed a site that I believe has used the term &quot;Microsoft Office Open XML&quot; more than any other in the last two weeks since the ISO contradiction period began: Bob Sutor&#039;s blog.&lt;br /&gt;&lt;br /&gt;Here are some typical examples, most of which use that misleading phrase in the headline itself:&lt;br /&gt;&lt;br /&gt;http://www.sutor.com/newsite/blog-open/?p=1342&lt;br /&gt;&lt;br /&gt;http://www.sutor.com/newsite/blog-open/?p=1343&lt;br /&gt;&lt;br /&gt;http://www.sutor.com/newsite/blog-open/?p=1345&lt;br /&gt;&lt;br /&gt;http://www.sutor.com/newsite/blog-open/?p=1346&lt;br /&gt;&lt;br /&gt;http://www.sutor.com/newsite/blog-open/?p=1355&lt;br /&gt;&lt;br /&gt;http://www.sutor.com/newsite/blog-open/?p=1356&lt;br /&gt;&lt;br /&gt;http://www.sutor.com/newsite/blog-open/?p=1359&lt;br /&gt;&lt;br /&gt;This makes it sort of hard to identify meaningful trends in the data you&#039;re presenting.  How many people have read the blog of IBM&#039;s VP of Open Source and Standards during that time, believing they were reading the truth, and then unknowingly repeated the misnomer he has been feeding them?</description>
		<content:encoded><![CDATA[<p>FYI, you missed a site that I believe has used the term &#8220;Microsoft Office Open XML&#8221; more than any other in the last two weeks since the ISO contradiction period began: Bob Sutor&#8217;s blog.</p>
<p>Here are some typical examples, most of which use that misleading phrase in the headline itself:</p>
<p><a href="http://www.sutor.com/newsite/blog-open/?p=1342" rel="nofollow">http://www.sutor.com/newsite/blog-open/?p=1342</a></p>
<p><a href="http://www.sutor.com/newsite/blog-open/?p=1343" rel="nofollow">http://www.sutor.com/newsite/blog-open/?p=1343</a></p>
<p><a href="http://www.sutor.com/newsite/blog-open/?p=1345" rel="nofollow">http://www.sutor.com/newsite/blog-open/?p=1345</a></p>
<p><a href="http://www.sutor.com/newsite/blog-open/?p=1346" rel="nofollow">http://www.sutor.com/newsite/blog-open/?p=1346</a></p>
<p><a href="http://www.sutor.com/newsite/blog-open/?p=1355" rel="nofollow">http://www.sutor.com/newsite/blog-open/?p=1355</a></p>
<p><a href="http://www.sutor.com/newsite/blog-open/?p=1356" rel="nofollow">http://www.sutor.com/newsite/blog-open/?p=1356</a></p>
<p><a href="http://www.sutor.com/newsite/blog-open/?p=1359" rel="nofollow">http://www.sutor.com/newsite/blog-open/?p=1359</a></p>
<p>This makes it sort of hard to identify meaningful trends in the data you&#8217;re presenting.  How many people have read the blog of IBM&#8217;s VP of Open Source and Standards during that time, believing they were reading the truth, and then unknowingly repeated the misnomer he has been feeding them?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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