Open nicholascar opened 3 years ago
@nicholascar Can you give some examples of classes being constrained? Thanks.
Certainly: the Australian Government Ontology Profile (AGOP: https://linked.data.gov.au/def/agop) requires that ontologies published by the Australian Government Linked Data Working Group have certain metadata present. This is enforced by the specification resource within that profile (https://linked.data.gov.au/def/agop/spec) that mandates that instances of owl:Ontology
have skos:prefLabel
, dcterms:created
properties with certain values. The specification 's rules are testable against instance data (RDF files containing ontologies) by a validation resource written in SHACL.
So the constrained class here is owl:Ontology
: for an instance of such to be valid according to AGOP, it must have such and such properties. Following the logic in this issue's description, we might say:
<https://linked.data.gov.au/def/agop> constrains owl:Ontology
Similarly, the VocPub Profile constrains skos:ConceptScheme
but it also skos:Collection
and skos:Concept
...
Currently there is no way, in PROF, to say:
How do we say
<Profile_Y> constrains <Class_X>
?The motivation for this is that we want to be able to do a reveres look up to know what Profiles (Specifications) are relevant to what classes so that people can know, per class, what Profiles they should consider.
Suggested properties could be: