<?xml version="1.0" encoding="UTF-8"?><item><title>iTunes and lax parsing</title><description>&lt;P&gt;It's &lt;A href="http://www.25hoursaday.com/weblog/"&gt;been&lt;/A&gt; &lt;A href="http://www.intertwingly.net/blog/2005/07/05/Insensitive-iTunes"&gt;reported&lt;/A&gt; that iTunes is lax in parsing the RSS extensions that they added to support iTunes.&lt;/P&gt;&#13;
&lt;P&gt;In a nutshell, the way iTunes finds the nodes it needs in an RSS document is apparently by scanning through the document doing a case-insensitive compare of the node name to the name it's looking for. &lt;/P&gt;&#13;
&lt;P&gt;XML is case-sensitive, so what most people do (an XPath query for /rss/channel for example) will not find nodes that the iTunes parser will find.&lt;/P&gt;&#13;
&lt;P&gt;The danger is that iTunes could become so popular that users will only test with it.&amp;nbsp; &lt;/P&gt;&#13;
&lt;P&gt;The precedent for this is Internet Explorer.&amp;nbsp; It accepts some pretty bizarre creations and tries its best to work with them.&amp;nbsp; Now that IE has been doing this for so long and so many sites depend on IE side-effects, that they've become the defacto standard, and folks like Mozilla have to work hard to emulate the bad parsing that IE does.&lt;/P&gt;&#13;
&lt;P&gt;Hopefully all the attention this is getting now will get Apple to make their parser more strict, although it will mean breaking things in the short term.&lt;/P&gt;&#13;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description><pubDate>Thu, 01 Sep 2005 19:17:09 GMT</pubDate></item>