Semantic artefacts are living digital entities undergoing changes and revisions to cope with semantic drift and for improving/ extending the scope or granularity. Provenance information describing all these changes during the semantic artefact lifecycle should be provided to external users.
Provenance must be documented at an appropriate level of granularity to enable reuse of semantic artefacts and its components (class/ term/ concept and relation). This means that provenance is applicable both at the level of the semantic artefact as a container (where versioning may be the primary consideration) and components (where references to external artefacts are important in addition to versioning).
Provenance must be presented to the human user, but also should be expressed in a machine-readable way. All appropriate sources should be referred to (both source reference - semantic artefact, and creator reference) and the provenance should provide dates and lifecycle events.
Provenance information should be described using an appropriate standard model such as PROV. PROV-based machine readable description could be then used to provide means to automatically update any resource using the semantic artefact. The provenance information should contain all the necessary elements to build representations to the users such as changelogs and describe backward interoperability.
Semantic artefacts are living digital entities undergoing changes and revisions to cope with semantic drift and for improving/ extending the scope or granularity. Provenance information describing all these changes during the semantic artefact lifecycle should be provided to external users.
Provenance must be documented at an appropriate level of granularity to enable reuse of semantic artefacts and its components (class/ term/ concept and relation). This means that provenance is applicable both at the level of the semantic artefact as a container (where versioning may be the primary consideration) and components (where references to external artefacts are important in addition to versioning).
Provenance must be presented to the human user, but also should be expressed in a machine-readable way. All appropriate sources should be referred to (both source reference - semantic artefact, and creator reference) and the provenance should provide dates and lifecycle events.
Provenance information should be described using an appropriate standard model such as PROV. PROV-based machine readable description could be then used to provide means to automatically update any resource using the semantic artefact. The provenance information should contain all the necessary elements to build representations to the users such as changelogs and describe backward interoperability.