<?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/"
		>
<channel>
	<title>Comments on: Unobtrusive Namespaces</title>
	<atom:link href="http://www.barefootliam.org/xml/20091111-unobtrusive-namespaces/feed" rel="self" type="application/rss+xml" />
	<link>http://www.barefootliam.org/xml/20091111-unobtrusive-namespaces</link>
	<description>Don't hurt your feet on the pointy brackets!</description>
	<lastBuildDate>Sat, 14 Nov 2009 01:08:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: barefootliam</title>
		<link>http://www.barefootliam.org/xml/20091111-unobtrusive-namespaces/comment-page-1#comment-29</link>
		<dc:creator>barefootliam</dc:creator>
		<pubDate>Sat, 14 Nov 2009 01:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.barefootliam.org/?p=31#comment-29</guid>
		<description>Actually I was harsher on DSRL in my post than I intended to be. The non-starter part is that I think it&#039;s important that the replacement for explicit namespace syntax for HTML 5 does not itself need an understanding of explicit namespace syntax to use it, so the file &quot;defining&quot; a namespace needs to be &quot;colon-free&quot; so to speak. But there&#039;s no reason, at least in principle, that DSRL couldn&#039;t be made colon-free in at least some usages. Last I saw, it was a draft. 

Obviously there would also need to be royalty-free patent commitments and also a zero-dollar version of the spec available under something like a W3C copyright.  But DSRL does have some features that would be useful, such as (obviously) the renaming.

Thanks for commenting!

[WORDPRESS HASHCASH] The poster sent us &#039;0 which is not a hashcash value.</description>
		<content:encoded><![CDATA[<p>Actually I was harsher on DSRL in my post than I intended to be. The non-starter part is that I think it&#8217;s important that the replacement for explicit namespace syntax for HTML 5 does not itself need an understanding of explicit namespace syntax to use it, so the file &#8220;defining&#8221; a namespace needs to be &#8220;colon-free&#8221; so to speak. But there&#8217;s no reason, at least in principle, that DSRL couldn&#8217;t be made colon-free in at least some usages. Last I saw, it was a draft. </p>
<p>Obviously there would also need to be royalty-free patent commitments and also a zero-dollar version of the spec available under something like a W3C copyright.  But DSRL does have some features that would be useful, such as (obviously) the renaming.</p>
<p>Thanks for commenting!</p>
<p>[WORDPRESS HASHCASH] The poster sent us &#8217;0 which is not a hashcash value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Jelliffe</title>
		<link>http://www.barefootliam.org/xml/20091111-unobtrusive-namespaces/comment-page-1#comment-28</link>
		<dc:creator>Rick Jelliffe</dc:creator>
		<pubDate>Fri, 13 Nov 2009 10:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.barefootliam.org/?p=31#comment-28</guid>
		<description>What was the reason for not allowing DSRL?

If they cannot understand namespaces enough to make a DSRL schema, why would they understand enough XML to put in your format?  

Wouldn&#039;t they be more likely just to not make any formal definition, but at most state a namespace in the text of a spec. In which case, making up a namespace declaration would be done by someone competent and interested in XML, who would understand namespaces. In which case DSRL would be OK.</description>
		<content:encoded><![CDATA[<p>What was the reason for not allowing DSRL?</p>
<p>If they cannot understand namespaces enough to make a DSRL schema, why would they understand enough XML to put in your format?  </p>
<p>Wouldn&#8217;t they be more likely just to not make any formal definition, but at most state a namespace in the text of a spec. In which case, making up a namespace declaration would be done by someone competent and interested in XML, who would understand namespaces. In which case DSRL would be OK.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
