W3C home > Mailing lists > Public > semantic-web@w3.org > April 2016

Re: Deprecating owl:sameAs

From: Herbert Van de Sompel <hvdsomp@gmail.com>
Date: Fri, 1 Apr 2016 08:56:57 -0600
Message-Id: <3A636BF4-963A-48AF-83C0-0F00E8548A79@gmail.com>
Cc: Sarven Capadisli <info@csarven.ca>, Linking Open Data <public-lod@w3.org>, SW-forum <semantic-web@w3.org>
To: Melvin Carvalho <melvincarvalho@gmail.com>
On Apr 1, 2016, at 07:28, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
>> On 1 April 2016 at 15:01, Sarven Capadisli <info@csarven.ca> wrote:
>> There is overwhelming research [1, 2, 3] and I think it is evident at this point that owl:sameAs is used inarticulately in the LOD cloud.
>> 
>> The research that I've done makes me conclude that we need to do a massive sweep of the LOD cloud and adopt owl:sameSameButDifferent.
>> 
>> I think the terminology is human-friendly enough that there will be minimal confusion down the line, but for the the pedants among us, we can define it along the lines of:
>> 
>> 
>> The built-in OWL property owl:sameSameButDifferent links things to things. Such an owl:sameSameButDifferent statement indicates that two URI references actually refer to the same thing but may be different under some circumstances.
> 
> What about
> 
> owl : sometimesSameAs
>  

Given my background in Memento "Time Travel for the Web", I am delighted that the temporal aspect is finally brought up. Sameness frequently depends on temporal context. Hence, I think sometimesSameAs would be very valuable. In other cases, things are just always the same irrespective of time. I would propose adding sameAsItEverWas to deal with such situations.

Herbert


>> 
>> 
>> Thoughts?
>> 
>> [1] https://www.w3.org/2009/12/rdf-ws/papers/ws21
>> [2] http://www.bbc.co.uk/ontologies/coreconcepts#terms_sameAs
>> [3] http://schema.org/sameAs
>> 
>> -Sarven
>> http://csarven.ca/#i
> 
Received on Friday, 1 April 2016 14:57:28 UTC

This archive was generated by hypermail 2.3.1 : Friday, 1 April 2016 14:57:32 UTC