Provenance capture #17
Description
There are two places provenance will be required for a generalised solution:
- on changes to specific terms
- on publication of a vocabulary version
the first is less of an immediate issue if we use Git - as we can track changes provided this is done right.
the publication of a version of the vocabulary is more important however -this will need to tie into git automation procedures I guess.
Will create an new issue for that.
The main thing to watch out for is that any JSON expression is JSON-LD compliant. This can be done with "vanilla JSON-LD" PROV-O serialisation - which is not reusable as simple JSON, and no schema exists to validate it as its a graph serialisation - its only usable as a RDF serialisation. Or it can be done with an OGC API Records compatible JSON schema with a JSON-LD mapping to PROV-O - this OGC Building Blocks supports the full PROV model, including DAGs linked by object ids https://ogcincubator.github.io/bblock-prov-schema/bblock/ogc.ogc-utils.prov