<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2005/03/04/techplen</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/03/04/techplen"/><id>http://norman.walsh.name/2005/03/04/techplen/comments.atom</id><updated>2012-02-13T10:09:37.900192Z</updated><entry><title>Comment 1 on /2005/03/04/techplen</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/03/04/techplen#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2005-03-05T19:17:26Z</published><updated>2005-03-05T19:17:26Z</updated><author><name>Mike Champion</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>I feel complelled to note that when Liam Quinn polled the audience for anyone who was fluent in a language that XML 1.0 "excluded", there was nary a peep.  
</p>
    <p>
Those widespread cheers for XML 1.1 among W3C insiders have not echoed in the marketplace.  Microsoft has no religious objection to this, simply doesn't see enough collective benefit from XML 1.1 to outweigh the very real pain it inflicts on the XML industry.  Without truly widespread uptake, XML 1.1 simply adds one more variable to the already complex interoperability equation.  That's why Michael Rys (NOT "Microsoft", although that is a popular opinion here) suggested recinding it.  
</p>
    <p>
There are lots of good ideas in XML 1.1, especially the more sensible alignment with Unicode and removing the arbitrary restrictions on the characters that XML can represent (although the continued outlawing of 0x0 is mystifying). Furthermore, the failure to note NEL as a newline character in XML 1.0 is simply a bug that really must be fixed at some point. These changes simply didn't add up to enough reason to create a new version of XML, in the humble collective opinion of those of us at Microsoft who track the XML specs and advise management on the costs and benefits of implementing them. 
</p>
    <p>
I do agree with Michael Rys - W3C should recind it, and at some point in the future issue a new set of specs that offer its features in a coherent package that has enough other goodies in it to make it worth a wide audience implementing and converting to .  What W3C seens to be offering now is a death by a thousand cuts -- XML 1.1, Schema 1.1, future versions of the other specs that support XML 1.1, and so on.</p>
  </div></content></entry><entry><title>Comment 2 on /2005/03/04/techplen</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/03/04/techplen#comment0002"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0002</id><published>2005-03-05T20:58:29Z</published><updated>2005-03-05T20:58:29Z</updated><author><name>Mike Champion</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Sorry, Michael Rys says it was Jonathan Marsh who made the argument about recinding XML 1.1.</p>
  </div></content></entry><entry><title>Comment 3 on /2005/03/04/techplen</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/03/04/techplen#comment0003"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0003</id><published>2005-03-06T23:56:41Z</published><updated>2005-03-06T23:56:41Z</updated><author><name>Libby Miller</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>beautiful picture Norm :)</p>
  </div></content></entry><entry><title>Comment 4 on /2005/03/04/techplen</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/03/04/techplen#comment0004"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0004</id><published>2005-03-07T15:20:13Z</published><updated>2005-03-07T15:20:13Z</updated><author><name>Norman Walsh</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Thanks, Libby. Though I think Stuart
<a rel="nofollow" href="http://www.flickr.com/photos/skw/5906402/">beat</a> my efforts.
<a rel="nofollow" href="http://www.flickr.com/photos/skw/5906396/">Twice</a>. :-)</p>
  </div></content></entry><entry><title>Comment 5 on /2005/03/04/techplen</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/03/04/techplen#comment0005"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0005</id><published>2005-03-07T16:04:28Z</published><updated>2005-03-07T16:04:28Z</updated><author><name>Norman Walsh</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>In the original publication of this essay, I quoted Jonathan Marsh's opinion as if it was Microsoft's opinion. I had no business making that inference and I apologize for doing so. I have no idea what corporate position Microsoft might or might not hold with respect to rescinding XML 1.1.</p>
  </div></content></entry></feed>

