Create SSSOM files for all mappings
self-assigning
We should have SSSOM files for all mappings This will make explicit the things that are currently secret knowledge or implicit. E.g.
- what abbrevs like FTT mean, and what URI they expand to
- when mappings were made, who made them, and what method they used
- whether the mappings are intended to be 1:1/exact, owl:Equivalent, or loose/close matches
In doing this we should review mappings such as those to FTT. Will make a new ticket
http://legacy.alexandria.ucsb.edu/gazetteer/FeatureTypes/ver100301/00000621.htm
Note: This strongly impacts the SWEET / ENVO mapping as part of the ESIP Semantic Harmonization Cluster activities. @rduerr @kaiiam
in case anyone is wondering, SSSOM is apparently A Simple Standard for Sharing Ontology Mappings (SSSOM)
Hmmm... thanks for the hint - quite useful. I think we will need to discuss at the next ESIP semantic harmonization call as well as for the SWEET work.
xref https://github.com/EnvironmentOntology/envo/issues/1160 and the older one https://github.com/EnvironmentOntology/envo/issues/1028
PR in the making in ODK to supporting sssom mappings directly: https://github.com/INCATools/ontology-development-kit/pull/649