W3C home > Mailing lists > Public > public-lod@w3.org > July 2009

Re: owl:sameAs [recipe]

From: Hugh Glaser <hg@ecs.soton.ac.uk>
Date: Tue, 28 Jul 2009 21:07:53 +0100
To: "bill.roberts@planet.nl" <bill.roberts@planet.nl>, "public-lod@w3.org" <public-lod@w3.org>
Message-ID: <EMEW3|802a2602fac98a2840f0b3ed3dbc82efl6RL8402hg|ecs.soton.ac.uk|C83D%hg@ecs.soton.ac.uk>
On 28/07/2009 13:20, "bill.roberts@planet.nl" <bill.roberts@planet.nl>
wrote:

>  
> Hugh - I understand your point about different provenance and maintenance
> issues with linkage vs substantive knowledge, but if you dereference a URI,
> don't you want to also get the linkage information at that point?  Of course
You do usually at the moment, but I think you don't - you then want to make
a decision about what linkage to get, based on your knowledge of reliability
and utility of sources, probably combined with what the publisher
recommends.
So the RDF you get back from resolving one of our URIs such as
http://southampton.rkbexplorer.com/id/person-00021 gives recommended
coreference KBs by having things like:
<owl:Ontology rdf:about=""> ... <coref:coreferenceData
rdf:resource="http://southampton.rkbexplorer.com/crs/person-00021" />
> you could do that while still keeping the two knowledge bases separate, as
> long as your system for dereferencing can combine info from both KBs - perhaps
> that's what you mean?
So you can find the coreference data without leaving the Linked Data world
or hacking URIs. But you don't have to take it.
Best
Hugh

> you could do that while still keeping the two knowledge bases separate, as
> long as your system for dereferencing can combine info from both KBs - perhaps
> that's what you mean?
>  
> Cheers
>  
> Bill
> 
> 
> Van: public-lod-request@w3.org namens Hugh Glaser
> Verzonden: di 28-7-2009 12:01
> Aan: Eric Lease Morgan; public-lod@w3.org
> Onderwerp: Re: owl:sameAs [recipe]
> 
> For the record (  Alan!).
> I consider it bad practice to keep the knowledge about linking in the same KB
> as the substantive knowledge you are representing.
> You need two KBs: one for the knowledge you are publishing, and one for the
> linkage you are working on.
> These have very different provenance, maintenance patterns, etc..
> And you can include a link from URIs that you generate to the linkage KB.
> 
> In fact, this would then help Alan's problem about sameAs:- he could simply
> decide not to get your view of the linkage, whereas with sameAs in the
> resources he has no choice but to accept your view, and even your predicate
> when he resolves a URI or queries the SPARQL.
> 
> And I do agree with you about minting URIs to your local stuff, including
> authors; it is error-prone to try to re-use things like dbpedia for this, on
> any scale. And this is why you need to tackle the linkage problem as a
> separate engineering activity.
> 
> Best
> Hugh
> 
> (Of course I do have some software and architecture that supports separate
> linkage KBs (our CRS) so I would say this, but nevertheless I think it is the
> correct engineering approach, however it is done. Separation of Concerns.)
> 
> On 28/07/2009 02:23, "Eric Lease Morgan" <eric_morgan@infomotions.com> wrote:
> 
> 
> 
Received on Tuesday, 28 July 2009 20:08:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:20:51 UTC