<?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: Namespacing &#038; Context - ramifications for the semantic web</title>
	<link>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/</link>
	<description>Mostly programming with a few bits of other stuff</description>
	<pubDate>Tue, 07 Oct 2008 08:25:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.1</generator>

	<item>
		<title>By: Manuel Simoni</title>
		<link>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-80823</link>
		<author>Manuel Simoni</author>
		<pubDate>Fri, 18 Apr 2008 14:36:38 +0000</pubDate>
		<guid>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-80823</guid>
					<description>My recent thinking re "semantic" data is that maybe a search engine is a better model for such systems than a triple store, which resonates with the points you are making.

A triple store requires very exact inputs to deliver any data at all.  In contrast, a search engine's motto is to "deliver results no matter what".

Basically, indexing and (page-)ranking all "title literals" (wikinames, blog titles, ...) should do the job, you probably wouldn't need a fulltext search engine.

And let's not forget the R in REST - a triple store has to return triples, whereas a search engine can return any representation, even a movie clip, which is a much better model for user facing systems.</description>
		<content:encoded><![CDATA[<p>My recent thinking re &#8220;semantic&#8221; data is that maybe a search engine is a better model for such systems than a triple store, which resonates with the points you are making.</p>
<p>A triple store requires very exact inputs to deliver any data at all.  In contrast, a search engine&#8217;s motto is to &#8220;deliver results no matter what&#8221;.</p>
<p>Basically, indexing and (page-)ranking all &#8220;title literals&#8221; (wikinames, blog titles, &#8230;) should do the job, you probably wouldn&#8217;t need a fulltext search engine.</p>
<p>And let&#8217;s not forget the R in REST - a triple store has to return triples, whereas a search engine can return any representation, even a movie clip, which is a much better model for user facing systems.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Danny</title>
		<link>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-80888</link>
		<author>Danny</author>
		<pubDate>Fri, 18 Apr 2008 18:17:41 +0000</pubDate>
		<guid>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-80888</guid>
					<description>Phil, should be an interesting experiment, looking forward to hearing how it goes (it sounds similar to the old Semantic Network stuff, which worked well for conceptual map kind of things, but not so good for practical data kind of applications). 

One question - a Semantic Web without URIs in the RDF, where's the Web bit? That an agent can follow it's nose (do a GET) to find more information is a feature, no?

Manuel, the triplestore/search engine is a bit apples/oranges - most search engines have some kind of database under the hood, the database itself will require fairly exact input.

Going the other way, a triplestore with SPARQL can make a very simple backend to a search engine, e.g. to find anything with the word "primer" in it:

SELECT DISTINCT ?o
WHERE {
?s ?p ?o .
FILTER regex( ?o, 'primer', 'i' ) 
}
LIMIT 10

try pasting it in here:
http://hyperdata.org/sparql/demo/sparql-editor.html</description>
		<content:encoded><![CDATA[<p>Phil, should be an interesting experiment, looking forward to hearing how it goes (it sounds similar to the old Semantic Network stuff, which worked well for conceptual map kind of things, but not so good for practical data kind of applications). </p>
<p>One question - a Semantic Web without URIs in the RDF, where&#8217;s the Web bit? That an agent can follow it&#8217;s nose (do a GET) to find more information is a feature, no?</p>
<p>Manuel, the triplestore/search engine is a bit apples/oranges - most search engines have some kind of database under the hood, the database itself will require fairly exact input.</p>
<p>Going the other way, a triplestore with SPARQL can make a very simple backend to a search engine, e.g. to find anything with the word &#8220;primer&#8221; in it:</p>
<p>SELECT DISTINCT ?o<br />
WHERE {<br />
?s ?p ?o .<br />
FILTER regex( ?o, &#8216;primer&#8217;, &#8216;i&#8217; )<br />
}<br />
LIMIT 10</p>
<p>try pasting it in here:<br />
<a href="http://hyperdata.org/sparql/demo/sparql-editor.html" rel="nofollow">http://hyperdata.org/sparql/demo/sparql-editor.html</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Eric Jain</title>
		<link>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-81113</link>
		<author>Eric Jain</author>
		<pubDate>Sat, 19 Apr 2008 07:26:05 +0000</pubDate>
		<guid>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-81113</guid>
					<description>Don't know about doing away with URIs... But some kind of context seems essential when looking at data from different sources. Two resources with different URIs may be the same thing, and two resources with the same URI may be different. Moreover, the meaning of "same" itself is context dependent!</description>
		<content:encoded><![CDATA[<p>Don&#8217;t know about doing away with URIs&#8230; But some kind of context seems essential when looking at data from different sources. Two resources with different URIs may be the same thing, and two resources with the same URI may be different. Moreover, the meaning of &#8220;same&#8221; itself is context dependent!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Richard Cyganiak</title>
		<link>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-82277</link>
		<author>Richard Cyganiak</author>
		<pubDate>Wed, 23 Apr 2008 11:24:28 +0000</pubDate>
		<guid>http://phildawes.net/blog/2008/04/18/namespacing-context-ramifications-for-the-semantic-web/#comment-82277</guid>
					<description>As I see it, URIs in RDF are 10% about disambiguating between terms, and 90% about allowing lookups of terms.

I suspect that by getting rid of the 10%, you also lose the 90%.</description>
		<content:encoded><![CDATA[<p>As I see it, URIs in RDF are 10% about disambiguating between terms, and 90% about allowing lookups of terms.</p>
<p>I suspect that by getting rid of the 10%, you also lose the 90%.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
