<?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: Resource, Resource! Wherefore art thou Resource?</title>
	<atom:link href="http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource/feed" rel="self" type="application/rss+xml" />
	<link>http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource</link>
	<description>musings of Roy T. Fielding</description>
	<lastBuildDate>Thu, 21 May 2009 18:54:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert Cerny</title>
		<link>http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-20</link>
		<dc:creator>Robert Cerny</dc:creator>
		<pubDate>Wed, 27 Feb 2008 19:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-20</guid>
		<description>I think that the requirement is unnecessarily strong. Unambiguous identification is very difficult, impossible in some cases. All those subjects could not be talked about with such a strong requirement in place. &lt;em&gt;In my opinion&lt;/em&gt; it would be sufficient to be able to state whether two resources identify the same subject. Such information could be provided by services. How the service learns whether two resources represent the same subject, is up to the service provider, but human control is unavoidable, although it might be supported by machines, e.g automatic reasoning for uncovering contradictions. Different service providers may provide different responses.</description>
		<content:encoded><![CDATA[<p>I think that the requirement is unnecessarily strong. Unambiguous identification is very difficult, impossible in some cases. All those subjects could not be talked about with such a strong requirement in place. <em>In my opinion</em> it would be sufficient to be able to state whether two resources identify the same subject. Such information could be provided by services. How the service learns whether two resources represent the same subject, is up to the service provider, but human control is unavoidable, although it might be supported by machines, e.g automatic reasoning for uncovering contradictions. Different service providers may provide different responses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy carroll</title>
		<link>http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-18</link>
		<dc:creator>jeremy carroll</dc:creator>
		<pubDate>Tue, 26 Feb 2008 11:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-18</guid>
		<description>I agree. Ambiguity occurs; design for it, not against it.</description>
		<content:encoded><![CDATA[<p>I agree. Ambiguity occurs; design for it, not against it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy T. Fielding</title>
		<link>http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-16</link>
		<dc:creator>Roy T. Fielding</dc:creator>
		<pubDate>Mon, 25 Feb 2008 03:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-16</guid>
		<description>I think a lot of people have an opinion on what the key requirements should be, but there doesn&#039;t seem to be much (if any) agreement, nor has there been adequate investigation of why these things should even be called &lt;em&gt;requirements&lt;/em&gt; when, for the most part, they are only wishful thinking at best.

If anything, the folks doing the most talking these days have talked themselves into the same corner where the AI systems failed -- the closed-world assumption.  These requirements are the antithesis of what Tim included in his &lt;a href=&quot;http://www.w3.org/DesignIssues/RDFnot.html&quot; rel=&quot;nofollow&quot;&gt;Design Notes&lt;/a&gt;:

&lt;blockquote cite=&quot;Tim Berners-Lee&quot;&gt;
The Semantic Web is what we will get if we perform the same globalization process to Knowledge Representation that the Web initially did to Hypertext. We remove the centralized concepts of absolute truth, total knowledge, and total provability, and see what we can do with limited knowledge.
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>I think a lot of people have an opinion on what the key requirements should be, but there doesn&#8217;t seem to be much (if any) agreement, nor has there been adequate investigation of why these things should even be called <em>requirements</em> when, for the most part, they are only wishful thinking at best.</p>
<p>If anything, the folks doing the most talking these days have talked themselves into the same corner where the AI systems failed &#8212; the closed-world assumption.  These requirements are the antithesis of what Tim included in his <a href="http://www.w3.org/DesignIssues/RDFnot.html" rel="nofollow">Design Notes</a>:</p>
<blockquote cite="Tim Berners-Lee"><p>
The Semantic Web is what we will get if we perform the same globalization process to Knowledge Representation that the Web initially did to Hypertext. We remove the centralized concepts of absolute truth, total knowledge, and total provability, and see what we can do with limited knowledge.
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Semergence &#187; Blog Archive &#187; This Post Is Ambiguous</title>
		<link>http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-15</link>
		<dc:creator>Semergence &#187; Blog Archive &#187; This Post Is Ambiguous</dc:creator>
		<pubDate>Mon, 25 Feb 2008 00:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-15</guid>
		<description>[...] When was the last time you had an unambiguous discussion? [...]</description>
		<content:encoded><![CDATA[<p>[...] When was the last time you had an unambiguous discussion? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Davis</title>
		<link>http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-14</link>
		<dc:creator>Ian Davis</dc:creator>
		<pubDate>Sun, 24 Feb 2008 23:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://roy.gbiv.com/untangled/2008/resource-resource-wherefore-art-thou-resource#comment-14</guid>
		<description>I think it&#039;s a key requirement that the owner of the URI has the means to state what it identifies unambiguously. 

However, that doesn&#039;t mean that other people can&#039;t say things that make it ambiguous. Like you imply, that&#039;s just life.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s a key requirement that the owner of the URI has the means to state what it identifies unambiguously. </p>
<p>However, that doesn&#8217;t mean that other people can&#8217;t say things that make it ambiguous. Like you imply, that&#8217;s just life.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.694 seconds -->
