search

hiscom / hispid

HISPID Terms
6 stars 1 forks source link

Use skos:exactMatch instead of owl:sameAs #37

Closed ben3000 closed 8 years ago

ben3000 commented 9 years ago

The owl:sameAs property is far more strict than skos:exactMatch, and thus may be too strict for the needs of our term definitions.

ben3000 commented 9 years ago

Aaron, I assigned you because you were going to discuss this with your guy a bit more before.

ben3000 commented 9 years ago

Should basisOfRecord be a sameAs/exactMatch of http://wiki.tdwg.org/twiki/bin/view/ABCD/AbcdConcept0400 for ABCD? Is this what you meant, Niels, when you said (in email): "ABCD has proper URIs for all elements and attributes in ABCD 2.06a, which we should probably use instead of the XPATHs."?

nielsklazenga commented 9 years ago

Yes, that is what I meant, but it was just a suggestion. If we want to run the documentation off the terms.rdf file, we still need to get the XPATH in somehow.

ben3000 commented 9 years ago

Ah, that is what http://rs.tdwg.org/dwc/terms/attributes/abcdEquivalence is for.

nielsklazenga commented 9 years ago

Yes. Is there an RDF with the Darwin Core terms as well? It would be nice to see how this is used.

ben3000 commented 9 years ago

Yes, see https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf. I'm using this as a template for our terms.rdf, although they don't use skos or owl as much as I think we should.

AaronWilton commented 9 years ago

i agree, we should try and use skos/owl as much as we can.

Within the mapping relationships of skos we have: broadMatch, narrowMatch, relatedMatch, closeMatch, exactMatch, relatedMatch.

Note - We need to ensure we use these correctly i think, as they may have implications for inferencing down the track - e.g., exactMatch is they only one that is transitive. Will follow this up...

"SKOS mapping properties are intended to express matching (exact or fuzzy) of concepts from one concept scheme to another, and by convention are used only to connect concepts from different schemes"

cf with skos relationships which are for relationships within a concept scheme

AaronWilton commented 9 years ago

from the Skos Primer - http://www.w3.org/TR/skos-primer/

Note on skos:exactMatch vs. owl:sameAs: SKOS provides skos:exactMatch to map concepts with equivalent meaning, and intentionally does not use owl:sameAs from the OWL ontology language [OWL]. When two resources are linked with owl:sameAs they are considered to be the same resource, and triples involving these resources are merged.

we should definitely use the skos definition rather than the OWL one.

ben3000 commented 9 years ago

Perhaps we should use owl:sameAs when this is the case? For example, when we're doing a direct semantic copy of an element from Dublin Core or Darwin Core.

AaronWilton commented 9 years ago

I think we should stick with skos mapping relationships

Sent from my Windows Phone

From: Ben Richardson Sent: 20/03/2015 7:58 p.m. To: hiscom/hispid Cc: Aaron Wilton Subject: Re: [hispid] Use skos:exactMatch instead of owl:sameAs (#37)

Perhaps we should use owl:sameAs when this is the case? For example, when we're doing a direct semantic copy of an element from Dublin Core or Darwin Core.

— Reply to this email directly or view it on GitHubhttps://github.com/hiscom/hispid/issues/37#issuecomment-83940567.

Please consider the environment before printing this email Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails. The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz

nielsklazenga commented 8 years ago

We are not using either, but use dcterms:replaces, dcterms:isReplacedBy and dwcattr:abcdEquivalence.