W3C home > Mailing lists > Public > semantic-web@w3.org > January 2006

Re: Showing the Semantic Web

From: Giovanni Tummarello <g.tummarello@gmail.com>
Date: Thu, 19 Jan 2006 00:14:44 +0100
Message-ID: <43CECBE4.3000705@gmail.com>
To: Stephen Rhoads <rhoadsnyc@mac.com>, semantic-web@w3.org

If its just nokia.com you want to hear about 
http://nokia.com/products/whatever# then why not using HTTP and MGET as 
in URIQA. or SparQL using named graph http://nokia.com/products.rdf  .
This however woudlnt at all display any "inverse" functionality  
(aggregation around concepts of anntations coming from diverse source, 
e.g the information that someone produces a non official, but yet 
compatible, datacable for http://nokia.com/products/whatever# ). Finding 
that cheap cable automagically (that is a triple about 
nokia.com/whatever that is not on their server) would be the wow element 
of the semantic web.
Else you reduce the semantic web beautiful idea to a series of "rss" 
feeds that you might use instead of browsing the HTML pages. Might be of 
some use, definitly nothing to wow about.


Stephen Rhoads wrote:

>Good point.
>I haven't been paying attention for a while, but have we yet solved the problem of how to query the Originator of a URI for an RDF description of that URI?
>>Http where do you exactly get the statements about 
>>http://example.com/philosophycal_concepts#freedom ? certainly nothing 
>>interesting lies on example.com, or nothing surprising anyway. Stuff 
>>that would make users go "wow" probably lies in DBs around. A "proper" 
>>"transport layer" would therefore somehow automatically (e.g. without 
>>explicitally namid the sources, else you're i nthe Sparql/named 
>>graph/well known db integration approach) connect those who ask about 
>>#freedom with those who write about it.
>>Like URIQA but automatically across the semantic web, something P2P a 
>>bit like RDFPeers (DHT storage of RDF graphs), but without the huge 
>>traffic generated at each query. RDFGrowth attemts to display such 
>>features, we'll see if it will be of any use once deployed publically.
Received on Wednesday, 18 January 2006 23:15:26 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:55 UTC