I take the point of view that Linked Data are claims, rather than facts.
Claims are made by different people/datasources, possibly conflicting, and
the consumer decides what/who to believe. I think that both dbpedia.org and
live.dbpedia.org should provide claims about the same URIs, without
requiring the sameAs indirection.
In this case, I would choose to see
http://live.dbpedia.org/resource/Slightly_Odway as a named graph that
contains assertions about http://dbpedia.org/resource/Slightly_Odway. Let's
abbreviate to live:Slightly_Odway and dbpedia:Slightly_Odway respectively.
An HTTP request to live:Slightly_Odway would return a description of a graph
named live:Slightly_Odway, which in turn has quadruples about
dbpedia:Slightly_Odway.
dbpedia:Slightly_Odway rdf:type ns7:DebutAlbums live:Slightly_Odway .
dbpedia:Slightly_Odway rdf:type ns7:JebediahAlbums live:Slightly_Odway .
...
The fact that it returns a description of itself complies with Linked Data
principles. The fact that these triples are talking about another URI may
look unconventional at first, but it's actually common in the wild. See [1]:
yago-res:Slightly_Odway owl:sameAs ns2:Slightly_Odway .
We might need to add some mechanism to convey in triples the same message of
the quadruples, or we may assume that if somebody asks for NT, they do not
care about the provenance, and just serve triples about
dbpedia:Slightly_Odway. If they ask for NQ, then we give them the
quadruples.
This solution would allow people to easily integrate data in a simple query,
retaining the ability of telling apart the sources, without requiring
inference.
SELECT *
WHERE {
GRAPH ?dbpedia {
dbpedia:Slightly_Odway ?p ?o .
}
GRAPH ?live {
dbpedia:Slightly_Odway ?p ?o .
}
--do interesting stuff here
}
What do y'all think?
Cheers,
Pablo
[1] http://dbpedia-live.openlinksw.com/page/Slightly_Odway
On Fri, Jun 24, 2011 at 9:52 PM, Kingsley Idehen <kide...@openlinksw.com>wrote:
> On 6/24/11 5:08 PM, Kingsley Idehen wrote:
> > Examples (note: owl:sameAs relations):
> >
> > 1.http://dbpedia-live.openlinksw.com/resource
> > 2.http://dbpedia-live.openlinksw.com/page/Slightly_Odway
> > 3.
> >
> http://dbpedia-live.openlinksw.com/describe/?url=http://dbpedia.org/resource/Slightly_Odway
>
> Should have been:
>
> 1.http://dbpedia-live.openlinksw.com/resource/Slightly_Odway
> 2.http://dbpedia-live.openlinksw.com/page/Slightly_Odway
> 3.
>
> http://dbpedia-live.openlinksw.com/describe/?url=http://dbpedia.org/resource/Slightly_Odway
>
>
>
> --
>
> Regards,
>
> Kingsley Idehen
> President& CEO
> OpenLink Software
> Web: http://www.openlinksw.com
> Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter/Identi.ca: kidehen
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense..
> http://p.sf.net/sfu/splunk-d2d-c1
> _______________________________________________
> Dbpedia-discussion mailing list
> Dbpedia-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
Dbpedia-discussion mailing list
Dbpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
