I would prefer to leave things as use and create owl:actuallySameAs and when this gets abused we can create owl:actuallySameAsReally
On Fri, Apr 1, 2016 at 4:32 PM, Henry Story <henry.st...@gmail.com> wrote: > > > On 1 Apr 2016, at 14:01, Sarven Capadisli <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 you need is mereologial logic so that you can start speaking of > things overlapping, being mostly the same, etc... > See Slide 26 of Jim Hendler's talk ( and the whole set of slides) > "On Beyond OWL: challenges for ontologies on the Web" > > > http://www.slideshare.net/jahendler/on-beyond-owl-challenges-for-ontologies-on-the-web > > > > > > > > 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 > > > > > -- Kontokostas Dimitris