<?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: Constraining RDF/XML</title>
	<atom:link href="http://blog.iandavis.com/2004/10/constraining-rdfxml/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.iandavis.com/2004/10/constraining-rdfxml</link>
	<description>blog.iandavis.com</description>
	<lastBuildDate>Tue, 23 Mar 2010 13:32:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Benjamin Nowack</title>
		<link>http://blog.iandavis.com/2004/10/constraining-rdfxml/comment-page-1#comment-97</link>
		<dc:creator>Benjamin Nowack</dc:creator>
		<pubDate>Mon, 18 Oct 2004 09:21:31 +0000</pubDate>
		<guid isPermaLink="false">http://iandavis.com/blog2/?p=825#comment-97</guid>
		<description>I agree with richard&#039;s comment re a default namespace. I&#039;m currently adding rdf export to my blog and tested the output with some rss readers . Some (many?) of them (e.g. opera&#039;s built-in) won&#039;t parse channel or item tags if they are prefixed with &quot;rss&quot;...</description>
		<content:encoded><![CDATA[<p>I agree with richard&#8217;s comment re a default namespace. I&#8217;m currently adding rdf export to my blog and tested the output with some rss readers . Some (many?) of them (e.g. opera&#8217;s built-in) won&#8217;t parse channel or item tags if they are prefixed with &#8220;rss&#8221;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Davis</title>
		<link>http://blog.iandavis.com/2004/10/constraining-rdfxml/comment-page-1#comment-96</link>
		<dc:creator>Ian Davis</dc:creator>
		<pubDate>Sat, 16 Oct 2004 23:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://iandavis.com/blog2/?p=825#comment-96</guid>
		<description>Thanks Richard. Those are helpful suggestions. I&#039;ve added them to the main posting.</description>
		<content:encoded><![CDATA[<p>Thanks Richard. Those are helpful suggestions. I&#8217;ve added them to the main posting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cyganiak</title>
		<link>http://blog.iandavis.com/2004/10/constraining-rdfxml/comment-page-1#comment-95</link>
		<dc:creator>Richard Cyganiak</dc:creator>
		<pubDate>Sat, 16 Oct 2004 23:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://iandavis.com/blog2/?p=825#comment-95</guid>
		<description>Sounds reasonable to me. An all-purpose writer would also have to deal with xml:lang. There&#039;s an unspecified edge case with circular statements about blank node, like in &quot;_:a :foo _:b. _:b :foo _:a.&quot;. I&#039;d also add:

Allow specification of a default namespace URI.

Order property elements within a node element using the algorithm described above.

Don&#039;t use rdf:parseType=&quot;resource&quot; or property attributes.</description>
		<content:encoded><![CDATA[<p>Sounds reasonable to me. An all-purpose writer would also have to deal with xml:lang. There&#8217;s an unspecified edge case with circular statements about blank node, like in &#8220;_:a :foo _:b. _:b :foo _:a.&#8221;. I&#8217;d also add:</p>
<p>Allow specification of a default namespace URI.</p>
<p>Order property elements within a node element using the algorithm described above.</p>
<p>Don&#8217;t use rdf:parseType=&#8221;resource&#8221; or property attributes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
