<?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: Eve&#8217;n&#039;more</title>
	<atom:link href="http://danbri.org/words/2005/09/28/137/feed" rel="self" type="application/rss+xml" />
	<link>http://danbri.org/words/2005/09/28/137</link>
	<description>the web, the world, us, you and them</description>
	<lastBuildDate>Thu, 11 Mar 2010 21:48:30 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: darcusblog &#187; Blog Archive &#187; XML and RDF</title>
		<link>http://danbri.org/words/2005/09/28/137/comment-page-1#comment-1188</link>
		<dc:creator>darcusblog &#187; Blog Archive &#187; XML and RDF</dc:creator>
		<pubDate>Mon, 27 Mar 2006 11:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://danbri.org/words/2005/09/28/137#comment-1188</guid>
		<description>[...] Certainly the RDF world could look at simplifying the XML syntax, but I agree with Dan Brickley that an even more important goal is continuing the evolution of RDF tools. If hot application environments like Ruby Rails had RDF support that mirrored its current SQL-based ActiveRecord, then that will do more to encourage uptake of RDF than anything done with standards documents. [...]</description>
		<content:encoded><![CDATA[<p>[...] Certainly the RDF world could look at simplifying the XML syntax, but I agree with Dan Brickley that an even more important goal is continuing the evolution of RDF tools. If hot application environments like Ruby Rails had RDF support that mirrored its current SQL-based ActiveRecord, then that will do more to encourage uptake of RDF than anything done with standards documents. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Ayers, Raw Blog : &#187; Great Expectations</title>
		<link>http://danbri.org/words/2005/09/28/137/comment-page-1#comment-1175</link>
		<dc:creator>Danny Ayers, Raw Blog : &#187; Great Expectations</dc:creator>
		<pubDate>Wed, 28 Sep 2005 17:04:18 +0000</pubDate>
		<guid isPermaLink="false">http://danbri.org/words/2005/09/28/137#comment-1175</guid>
		<description>[...] Issues with RDF/XML have featured in discussion around the RDF watercooler this week, with iand offering 12 different versions of the same teensy bit of RDF, and danbri offering more. [...]</description>
		<content:encoded><![CDATA[<p>[...] Issues with RDF/XML have featured in discussion around the RDF watercooler this week, with iand offering 12 different versions of the same teensy bit of RDF, and danbri offering more. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shellac</title>
		<link>http://danbri.org/words/2005/09/28/137/comment-page-1#comment-1174</link>
		<dc:creator>shellac</dc:creator>
		<pubDate>Wed, 28 Sep 2005 09:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://danbri.org/words/2005/09/28/137#comment-1174</guid>
		<description>Swallow my example, will you?

&lt;dc:title ... &gt; -%gt;
&lt;rdf:predicate rdf:property=&quot;&dc;title&quot; ...&gt;</description>
		<content:encoded><![CDATA[<p>Swallow my example, will you?</p>
<p>&lt;dc:title &#8230; &gt; -%gt;<br />
&lt;rdf:predicate rdf:property=&#8221;&amp;dc;title&#8221; &#8230;&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shellac</title>
		<link>http://danbri.org/words/2005/09/28/137/comment-page-1#comment-1173</link>
		<dc:creator>shellac</dc:creator>
		<pubDate>Wed, 28 Sep 2005 09:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://danbri.org/words/2005/09/28/137#comment-1173</guid>
		<description>Some random comments:

The one issue I have with syntactic profiles is controlling the serialisation, which can be fiddly (otherwise it&#039;s a fine choice).

My suspicion is that when people are talking about issues with rdf/xml, they are specifically talking about xslt and rdf/xml. People like xslt (with good reason) and want to use it for everything. It&#039;s probably worth 
capturing some of the discussion about transforming rdf in the ESW wiki (http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0048.html ), which might help them out.

I could summarise that as: sparql will help a great deal.

One final random thought (and personal bugbear): if  rdf/xml had a way to write properties without qnames, eg:



Then you could have and rdf/xml normal form which:

1. Used only the rdf namespace.
2. Had a (useful) xml schema.
3. Only varied in order.

Much like trix et al. I don&#039;t want to write it, but if people want that kind of thing...</description>
		<content:encoded><![CDATA[<p>Some random comments:</p>
<p>The one issue I have with syntactic profiles is controlling the serialisation, which can be fiddly (otherwise it&#8217;s a fine choice).</p>
<p>My suspicion is that when people are talking about issues with rdf/xml, they are specifically talking about xslt and rdf/xml. People like xslt (with good reason) and want to use it for everything. It&#8217;s probably worth<br />
capturing some of the discussion about transforming rdf in the ESW wiki (<a href="http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0048.html" rel="nofollow">http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0048.html</a> ), which might help them out.</p>
<p>I could summarise that as: sparql will help a great deal.</p>
<p>One final random thought (and personal bugbear): if  rdf/xml had a way to write properties without qnames, eg:</p>
<p>Then you could have and rdf/xml normal form which:</p>
<p>1. Used only the rdf namespace.<br />
2. Had a (useful) xml schema.<br />
3. Only varied in order.</p>
<p>Much like trix et al. I don&#8217;t want to write it, but if people want that kind of thing&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
