search

opengeospatial / SELFIE

Second Environmental Linked Feature Interoperability Experiment
https://opengeospatial.github.io/ELFIE
14 stars 8 forks source link

Clarify selection of owl:sameAs over schema:sameAs #98

Closed dblodgett-usgs closed 4 years ago

dblodgett-usgs commented 4 years ago

Was this intentional? https://opengeospatial.github.io/ELFIE/json-ld/elf.jsonld switched to owl:sameAs https://opengeospatial.github.io/ELFIE/contexts/elfie-2/elf-index.jsonld

Concerns were raised on 2/25 call.

abhritchie commented 4 years ago

xxx:sameAs was introduced for the same-thing-in-multiple-repos use case. For example: data about the same Victorian borehole are held by both GSV and CERDI; here in NZ we have monitoring stations shared by regional authorities and utilities companies. sameAs was proposed because it means exactly that: these information resources are describing exactly the same thing. subjectOf is ambiguous. owl:sameAs is arguably appropriate valid in this use case - the graphs should be merged without concern - but the universally strong and emotional reaction to owl:sameAs shows schema:sameAs is safer ... and acceptable to this IE as logical consistency and inferencing are a secondary concern.

dblodgett-usgs commented 4 years ago

Should it be "same-thing-in-multiple-repos-with-different-non-information-identifiers" use case? schema:subjectOf takes care of the "same-thing-in-multiple-repos-using-shared-non-information-identifiers" right?

abhritchie commented 4 years ago

Not the way subjectOf is currently used.