Hi Sarven,
I love the idea and I'm a big fan of your work filling my inbox with
public-lod mails!
Yet I believe this discussion is becoming too ad-hoc. In order to get a
bit of a structure into this, feel free to fork my samesamebutdifferent
ontology and pull request your suggestions:
https://github.com/pietercolpaert/samesamebutdifferent/blob/master/vocabulary.ttl
I already added the things we have come up with in turtle. As we are not
responsible for OWL, I suggest creating a new ontology on a new namespace.
Kind regards,
Pieter
P.S. Also feel free to donate a proper domain name for this
On 01-04-16 15:28, Melvin Carvalho wrote:
On 1 April 2016 at 15:01, Sarven Capadisli <i...@csarven.ca
<mailto:i...@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
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
--
+32486747122
Linked Open Transport Data researcher
Ghent University - Data Science Lab - iMinds
Board of Directors Open Knowledge Belgium
http://openknowledge.be
Open Transport working group coordinator at Open Knowledge International
http://transport.okfn.org
