W3C home > Mailing lists > Public > www-rdf-interest@w3.org > October 2003

AW: The "info" URI Scheme

From: Leo Sauermann <leo@gnowsis.com>
Date: Thu, 2 Oct 2003 19:13:32 +0200
To: "'Karl Dubost'" <karl@w3.org>, <www-rdf-interest@w3.org>
Message-ID: <000401c38908$81ee7d20$0b01a8c0@Bundeslade>

> > That's normal life on the SW. Agent's beware.
> utopia.


utopia ?


http://slashdot.org/slashdot.rdf
http://www.wired.com/news_drop/netcenter/netcenter.rdf
http://boingboing.net/rss.xml
http://www.digitalidworld.com/backend.php
....


the other 

---> 16273 <---- 

active RSS news feeds are here:

http://www.syndic8.com/

soon things like
http://boingboing.net/2003_10_01_archive.html#106502088793444933
could be uriqa or joseki enabled.

in fact the architecture would be fine if it was queryable.


An RDQL (http://www.hpl.hp.com/semweb/rdql.htm) example:
SELECT ?a WHERE
(<http://boingboing.net/2003_10_01_archive.html#106502088793444933>
rdf:type ?a)

-> first dereference boingboing.net and see if the server is enhanced
with RDF query (like uriqa)
-> then send the query to the rdf server at boingboing.net

this would enable us to have a distributed semantic web.

If the url was not dereferencable, I would have to query Google, which
has to buffer all data. another advantage is that the url is always
actualized.

greetings
Leo
Received on Thursday, 2 October 2003 13:14:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:02 GMT