<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.1.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The path from specificity to usefulness</title>
	<link>http://phildawes.net/blog/2007/01/08/the-path-from-specificity-to-usefulness/</link>
	<description>Mostly programming with a few bits of other stuff</description>
	<pubDate>Thu, 20 Nov 2008 23:34:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.1</generator>

	<item>
		<title>By: Dominic Sayers</title>
		<link>http://phildawes.net/blog/2007/01/08/the-path-from-specificity-to-usefulness/#comment-16139</link>
		<author>Dominic Sayers</author>
		<pubDate>Wed, 10 Jan 2007 12:27:57 +0000</pubDate>
		<guid>http://phildawes.net/blog/2007/01/08/the-path-from-specificity-to-usefulness/#comment-16139</guid>
					<description>Have you read Do Androids Dream of Electric Sheep?

Maybe you couldn't see the capcha by design...</description>
		<content:encoded><![CDATA[<p>Have you read Do Androids Dream of Electric Sheep?</p>
<p>Maybe you couldn&#8217;t see the capcha by design&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Seth Ladd</title>
		<link>http://phildawes.net/blog/2007/01/08/the-path-from-specificity-to-usefulness/#comment-16486</link>
		<author>Seth Ladd</author>
		<pubDate>Mon, 15 Jan 2007 18:37:44 +0000</pubDate>
		<guid>http://phildawes.net/blog/2007/01/08/the-path-from-specificity-to-usefulness/#comment-16486</guid>
					<description>The thing that is tricky about all of this, is that a URI sure enough identifies a singular resource.  However, that Resource can belong to an infinite amount of classes.  That is, the Resource can mean many different things to many different people.  This is both a strength and a weakness, and leads to much trickiness when implementing RDF.

The more vague a Resource is defined, the more useful it is, because people don't get caught up in over thinking, "Do I match the intended meanings?"

So, if RDF is to work, implementers have to allow for mechanisms to help humans deal with the many interpretations of the Resources those URIs identify.</description>
		<content:encoded><![CDATA[<p>The thing that is tricky about all of this, is that a URI sure enough identifies a singular resource.  However, that Resource can belong to an infinite amount of classes.  That is, the Resource can mean many different things to many different people.  This is both a strength and a weakness, and leads to much trickiness when implementing RDF.</p>
<p>The more vague a Resource is defined, the more useful it is, because people don&#8217;t get caught up in over thinking, &#8220;Do I match the intended meanings?&#8221;</p>
<p>So, if RDF is to work, implementers have to allow for mechanisms to help humans deal with the many interpretations of the Resources those URIs identify.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
