<?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: oai-ore and the shadow web</title>
	<atom:link href="http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/</link>
	<description>beep beep</description>
	<pubDate>Tue, 07 Oct 2008 04:55:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: delicious mark hubery</title>
		<link>http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-59664</link>
		<dc:creator>delicious mark hubery</dc:creator>
		<pubDate>Thu, 17 Apr 2008 20:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-59664</guid>
		<description>&lt;strong&gt;Blog Hopper...&lt;/strong&gt;

Hi There. I'm blog hopping....</description>
		<content:encoded><![CDATA[<p><strong>Blog Hopper&#8230;</strong></p>
<p>Hi There. I&#8217;m blog hopping&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nodalities &#187; Blog Archive &#187; This Week&#8217;s Semantic Web</title>
		<link>http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-59653</link>
		<dc:creator>Nodalities &#187; Blog Archive &#187; This Week&#8217;s Semantic Web</dc:creator>
		<pubDate>Thu, 17 Apr 2008 17:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-59653</guid>
		<description>[...] oai-ore and the shadow web [...]</description>
		<content:encoded><![CDATA[<p>[...] oai-ore and the shadow web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Diggory</title>
		<link>http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-55809</link>
		<dc:creator>Mark Diggory</dc:creator>
		<pubDate>Thu, 28 Feb 2008 19:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-55809</guid>
		<description>I would like to see this be the case, most of the new DSpace UI (Manakin specifically) technology will support including RDFa and microformats into the Item page generation and this would be an ideal use-case for it.

Cheers,
Mark Diggory
DSpace Systems Manager 
MIT Libraries</description>
		<content:encoded><![CDATA[<p>I would like to see this be the case, most of the new DSpace UI (Manakin specifically) technology will support including RDFa and microformats into the Item page generation and this would be an ideal use-case for it.</p>
<p>Cheers,<br />
Mark Diggory<br />
DSpace Systems Manager<br />
MIT Libraries</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Johnston</title>
		<link>http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-55456</link>
		<dc:creator>Pete Johnston</dc:creator>
		<pubDate>Mon, 25 Feb 2008 12:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-55456</guid>
		<description>Ed,

Good point.

Speaking only for myself here(!),  I completely agree that an XHTML/RDFa document would make a good representation of an ORE Resource Map; and that such a document could/would probably look very much like what we think of as a "splash page".

Of course if you want to talk about both 

(i) the Resource Map (with an XHTML/RDFa representation and possibly other representations via conneg) and 
(ii) a "splash page" 

as two distinct resources, which I guess we might want to do in some circumstances, then we need two distinct URIs for those two distinct resources.

But that's still perfectly do-able. One could probably even serve the _same_ XHTML/RDFa doc as a representation of _both_ of those _distinct_ resources (pace taking care with base URIs etc).</description>
		<content:encoded><![CDATA[<p>Ed,</p>
<p>Good point.</p>
<p>Speaking only for myself here(!),  I completely agree that an XHTML/RDFa document would make a good representation of an ORE Resource Map; and that such a document could/would probably look very much like what we think of as a &#8220;splash page&#8221;.</p>
<p>Of course if you want to talk about both </p>
<p>(i) the Resource Map (with an XHTML/RDFa representation and possibly other representations via conneg) and<br />
(ii) a &#8220;splash page&#8221; </p>
<p>as two distinct resources, which I guess we might want to do in some circumstances, then we need two distinct URIs for those two distinct resources.</p>
<p>But that&#8217;s still perfectly do-able. One could probably even serve the _same_ XHTML/RDFa doc as a representation of _both_ of those _distinct_ resources (pace taking care with base URIs etc).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Birbeck</title>
		<link>http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-55236</link>
		<dc:creator>Mark Birbeck</dc:creator>
		<pubDate>Fri, 22 Feb 2008 23:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/2008/02/22/oai-ore-and-the-shadow-web/#comment-55236</guid>
		<description>Hi,

I agree with you that things could be loosened. The Discovery document position tends to arise when it is assumed that it must be possible to tell the difference between a resource and an information resource, perhaps by performing an HTTP request. (This is something I know that Ian has argued in the past.)

In my view this is an over-literal reading of the situation, something various people have tried to tackle. My own comments are 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;. I also have an older post from a couple of years ago, which was originally intended to be a critical look at the whole discussion from the same standpoint as the Discovery document that you quote, but in the course of working it through I discovered that my own view was wrong. It may be of interest to others who are as confused as I was, and it's called &lt;a href="http://internet-apps.blogspot.com/2006/05/information-resource-debate-and-rdfa.html" rel="nofollow"&gt;The Information Resource Debate, and RDFa&lt;/a&gt;.

Interesting work, though. And a great use of RDFa.

All the best,

Mark Birbeck
http://webBackplane.com/mark-birbeck</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I agree with you that things could be loosened. The Discovery document position tends to arise when it is assumed that it must be possible to tell the difference between a resource and an information resource, perhaps by performing an HTTP request. (This is something I know that Ian has argued in the past.)</p>
<p>In my view this is an over-literal reading of the situation, something various people have tried to tackle. My own comments are 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>. I also have an older post from a couple of years ago, which was originally intended to be a critical look at the whole discussion from the same standpoint as the Discovery document that you quote, but in the course of working it through I discovered that my own view was wrong. It may be of interest to others who are as confused as I was, and it&#8217;s called <a href="http://internet-apps.blogspot.com/2006/05/information-resource-debate-and-rdfa.html" rel="nofollow">The Information Resource Debate, and RDFa</a>.</p>
<p>Interesting work, though. And a great use of RDFa.</p>
<p>All the best,</p>
<p>Mark Birbeck<br />
<a href="http://webBackplane.com/mark-birbeck" rel="nofollow">http://webBackplane.com/mark-birbeck</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
