<?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"
	>
<channel>
	<title>Comments on: RDFa and the Shadow Web</title>
	<atom:link href="http://rdfa.info/2007/11/22/rdfa-and-the-shadow-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://rdfa.info/2007/11/22/rdfa-and-the-shadow-web/</link>
	<description>Interoperable Web Metadata</description>
	<pubDate>Wed, 15 Oct 2008 01:54:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Mark Birbeck</title>
		<link>http://rdfa.info/2007/11/22/rdfa-and-the-shadow-web/#comment-9836</link>
		<dc:creator>Mark Birbeck</dc:creator>
		<pubDate>Fri, 23 Nov 2007 12:20:53 +0000</pubDate>
		<guid isPermaLink="false">http://rdfa.info/2007/11/22/rdfa-and-the-shadow-web/#comment-9836</guid>
		<description>Hi Ben,

The reason RDFa can solve this problem is because it has &lt;em&gt;both&lt;/em&gt; &lt;code&gt;@href&lt;/code&gt; and &lt;code&gt;@resource&lt;/code&gt;. This allows us to distinguish between relationships between documents (&lt;code&gt;@href&lt;/code&gt;) and relationships between other things (&lt;code&gt;@resource&lt;/code&gt;), or what is known in the trade as the distinction between information resources and other resources. (Whether there is a need for such a distinction is at the heart of Ian's comments on fragment identifiers.)

It's not something that will excite anyone not interested in RDF :) but for those who are, I've looked a little at how the fact that RDFa has two attributes helps to solve the problem. The discussion is in &lt;a href="http://internet-apps.blogspot.com/2007/11/once-more-on-information-resources-and.html" rel="nofollow"&gt;Once more on information resources and RDFa&lt;/a&gt;.

All the best,

Mark

-- 
  Mark Birbeck, formsPlayer

  mark.birbeck@formsPlayer.com &#124; +44 (0) 20 7689 9232
  http://www.formsPlayer.com &#124; http://internet-apps.blogspot.com

  standards. innovation.</description>
		<content:encoded><![CDATA[<p>Hi Ben,</p>
<p>The reason RDFa can solve this problem is because it has <em>both</em> <code>@href</code> and <code>@resource</code>. This allows us to distinguish between relationships between documents (<code>@href</code>) and relationships between other things (<code>@resource</code>), or what is known in the trade as the distinction between information resources and other resources. (Whether there is a need for such a distinction is at the heart of Ian&#8217;s comments on fragment identifiers.)</p>
<p>It&#8217;s not something that will excite anyone not interested in RDF <img src='http://rdfa.info/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> but for those who are, I&#8217;ve looked a little at how the fact that RDFa has two attributes helps to solve the problem. The discussion is in <a href="http://internet-apps.blogspot.com/2007/11/once-more-on-information-resources-and.html" rel="nofollow">Once more on information resources and RDFa</a>.</p>
<p>All the best,</p>
<p>Mark</p>
<p>&#8211;<br />
  Mark Birbeck, formsPlayer</p>
<p>  <a href="mailto:mark.birbeck@formsPlayer.com">mark.birbeck@formsPlayer.com</a> | +44 (0) 20 7689 9232<br />
  <a href="http://www.formsPlayer.com" rel="nofollow">http://www.formsPlayer.com</a> | <a href="http://internet-apps.blogspot.com" rel="nofollow">http://internet-apps.blogspot.com</a></p>
<p>  standards. innovation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
