Relax provenance requirement to allow skos:inScheme

[rob-metalinkage]

If a scheme defines its provenance, then it should be adequate to use skos:inScheme to transitively inherit provenance requirements. Thinks like Vocprez could run a COALESCE over per-concept provenance and per scheme if they want to impose a requirment to display per Concept..

[nicholascar]

I think the idea that a Concept would inherit its provenance from its container - a ConceptScheme or other defining thing via rdfs:isDefinedBy - is already present.

You must assign at least one of prov:wasDerivedFrom, dcterms:source or dcterms:provenance to the CS and optionally may assign similar or other the any Concept. General container/member relations should lead one to assume a CS' provenance carries down to a Concept unless the Concept has individual other information.

I wouldn't want to build this all out, which is what I think you are saying with the COALESGE bit, as otherwise I might have to build out all container to member properties.

So, no action required in the profile?

You could on-display CS properties for the Concept in a query or template bit of the OGC VocPrez theme if you wish.

[rob-metalinkage]

No - I think it should be sufficient to assign provenance to the containing ConceptScheme is an inScheme is in place. The COALESCE would be the way a downstream client could handle it if it decided to always show the provenance