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

Re: Generating rdfs:seeAlso links for Tabulator with SPARQL CONSTRUCT

From: Dan Connolly <connolly@w3.org>
Date: Wed, 01 Nov 2006 08:33:18 -0600
To: Chris Bizer <chris@bizer.de>
Cc: Giovanni Tummarello <g.tummarello@gmail.com>, Chris Bizer <bizer@zedat.fu-berlin.de>, semantic-web@w3.org, bastian@quilitz.de, Tim Berners-Lee <timbl@w3.org>, Richard Cyganiak <richard@cyganiak.de>, "Seaborne, Andy" <andy.seaborne@hp.com>, Ivan Herman <ivan@w3.org>, Tobias Gauß <tobias.gauss@web.de>
Message-Id: <1162391598.8627.198.camel@dirk>

On Sat, 2006-10-28 at 18:33 +0200, Chris Bizer wrote:
> > The cool factor is probably in the URI rewriting.
> > But then again, maybe that is not a good idea? I wonder if  putting
> > instead in your foaf file a triple that says yourpage#cris sameAs
> > bigtimedb/id12345 would be more useful.. e.g.  if the tabulator found
> > other graphs where you are mentioned as the OTHER URI then such triple
> > would do the mapping , the query wouldn't.
> You are right, but this should be done in addition to setting the link not 
> as an alternative.
> If we want the Semantic Web to succeed, we need easily navigate-able links 
> NOW, instead of waiting for some hyper-intelligent discovery and mapping 
> algorithms that might be invented sometime in the future.

"hyper-intelligent"? handling owl:sameAs in this case is simpler
than SPARQL, no?

I think the tabulator already does it. I'm not sure.

In fact, the SPARQL queries are a sort of
substitution-of-equals-for-equals corrolary to the owl:sameAs

I suppose it's fine to play around with both alternatives for a while,
though the SPARQL CONSTRUCT approach feels like overkill, to me.

Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E
Received on Wednesday, 1 November 2006 14:33:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:41:54 UTC