dblodgett-usgs
commented
5 years ago This work was moved to ELFIE and SELFIE. See the ELFIE engineering report appendix here: https://docs.opengeospatial.org/per/18-097.html#ontology_from_uml
Ongoing SELFIE work is happening here. https://github.com/opengeospatial/SELFIE
The ISO19150 encoding generates three things with unique URIs related to CodeLists 1) an owl:Class representing the Code List 2) a skos:ConceptScheme for the members of the codelist 3) a skos:Collection with the values as members
hyf:HY_NameUsage a owl:Class ; rdfs:subClassOf skos:Concept .
hyfcode:HY_NameUsage a skos:ConceptScheme ; dct:isFormatOf hyf:HY_NameUsage .
hyfcode:HY_NameUsageCollection a skos:Collection ; skos:member https://www.opengis.net/def/hy_features/ontology/hyf/code/HY_NameUsage/vernacular .
These are not very linked together by default - this is very sad :-(
we have in OGC na a policy:equivalentCollection predicate:
so this makes sense: hyfcode:HY_NameUsage policy:equivalentCollection hyfcode:HY_NameUsageCollection .
but we also usually make the Collection the / hyfcode:HY_NameUsage policy:equivalentCollection hyfcode:HY_NameUsage/
So- what should we use to link the Class to the ConceptScheme (inverse of dct:isFormatOf)
dct:format seems just ugly and imprecise.
RDF -Datacube has a way to link elements to SKOS - but these are usually via the range of a predicated - not a statement about the class.
Any ideas?