RE: [xdi] reactions on paper "When owl:sameAs isn?t the Same..."

["Barnhill, William [USA]" <barnhill_william@bah.com>]

I was thinking more about this and think we may need a new $ word.

 

The use case is this:

Say we have =Alice whose doctor is @bobmed+doctor=Bob. Let's also say there is a global community of patients at @patient and Alice's identity as a patient is @patient!45. Alice as a patient {@patient!45} and Alice as an individual {=Alice} map to the same entity {her i-number} but they aren't synonyms because there are clear contexts where Alice's patient identity is not interchangeable with Alice's identity as an individual or as an entity, and vice versa, due to privacy, compliance, or other reasons. That means we cannot use $is. Given the semantics of $has and is I don't believe this maps to $is$has as that means =Alice has a member of her set that is @patient!45, whereas $partOf would mean that the set of members of @patient!45 are a subset of the members of =Alice, in the same way that the one identity is a subset of the other, but I'm interested in what others on the TC think on that.

 

What do people think of adopting $partOf for situations like this, i.e. @patient!45/$partOf/=Alice ?  This would map to/from h:partOf and skos:partOf.

 

Bill

---

From: Barnhill, William [USA] [mailto:barnhill_william@bah.com]
Sent: Thursday, June 24, 2010 3:22 PM
To: Paul Trevithick; Giovanni Bartolomeo
Cc: OASIS - XDI TC
Subject: RE: [xdi] reactions on paper "When owl:sameAs isn?t the Same..."

From my standpoint I've always thought of the XDI synonym dollar word, which is now $is, as mapping to owl:sameAs. I briefly thought it might be better to map to something a little weaker, skos:closeMatch, but came back around to believing it should map to owl:sameAs. Another reason I think h:correlation couldn't map to $is is that h:correlation is specifically not a transitive property according to the Higgins XDI Harmonization wiki, whereas $is must be.

 

Bill

---

From: Paul Trevithick [mailto:ptrevithick@gmail.com]
Sent: Thursday, June 24, 2010 2:15 PM
To: Giovanni Bartolomeo
Cc: OASIS - XDI TC
Subject: Re: [xdi] reactions on paper "When owl:sameAs isn?t the Same..."

Giovanni,

Last week it was proposed that h:correlation is the same as $is, but on further reflection I don't think that's right. I think $is is equivalent in semantics to owl:sameAs. Joseph and I discussed this a bit today on the XDI harmonization portion of the weekly Higgins call. In Higgins h:correlation means: representing the same thing in different contexts. The following para is copied from [1] (BTW, we use the term entity instead of resource):

h:correlation is subtly different from owl:sameAs. It is statement made by a human observer that the source and target of this link are believed to be alternative representations of the same real world person or object. A single, natural person would thus be represented by different entities in different contexts. This linkage does not presume that the entire set of attributes across these entities, if they were brought together and combined, is necessarily logically consistent. The ontologies in the two contexts may be such that each of the two representations cannot be merged and remain logically consistent. For this reason Higgins does not use owl:sameAs which does imply this ability to directly merge representations. h:correlation is stronger than rdfs:seeAlso but weaker than owl:sameAs. 

[1] http://wiki.eclipse.org/Higgins_Data_Model_2.0

On Jun 24, 2010, at 1:40 PM, Giovanni Bartolomeo wrote:

Hello,

having had time this week to look at these Drummond suggested readings:

?When owl:sameAs isn?t the Same: An Analysis of Identity Links on the  
Semantic Web?, by Harry Halpin, Ivan Herman, and Patrick J. Hayes

?RDF and XML: Towards a Unified Query Layer?, by Nuno Lopes, Stefan  
Bischof, Orri Erling, Axel Polleres, Alexandre Passant, Diego  
Berrueta, Antonio Campos, Jé?rôme Euzenat, Kingsley Idehen, Stefan  
Decker, Sté?phane Corlosquet, Jacek Kopecky ?, Janne Saarela, Thomas  
Krennwallner, Davide Palmisano, and Michal Zaremba

(both will be presented at nextcoming W3C RDF workshop,  
http://www.w3.org/2009/12/rdf-ws/) I would like to share with you some  
thoughts on how I believe XDI and XRI non-opaque identifiers could  
nicely address some issues presented there - especially in the first  
article.

Could you insert this topic into today's or next week's phc agenda?

Thank you very much,
Giovanni