Nice thread We have proposed a justification framework for medical terminology mappings, see https://www.slideshare.net/kerfors/cim2014 <https://www.slideshare.net/mobile/kerfors/cim2014> http://www.macs.hw.ac.uk/~fm206/cim14/cim20140_submission_2.pdf On Friday, 1 April 2016, Barry Norton <barrynorton@gmail.com> wrote: > Or we could stop building naive applications that treat assertion as fact, > and instead only reason on statements we accept based on trust and > provenance. Wasn't that the plan? > > Regards, > > Barry > > On Fri, Apr 1, 2016 at 2:01 PM, Sarven Capadisli <info@csarven.ca > <javascript:_e(%7B%7D,'cvml','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. >> >> >> 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 15:03:21 UTC