Part of WP6
We will follow the W3C standard PROV-O. This was developed following these recommendations:
See https://www.w3.org/2005/Incubator/prov/wiki/images/0/02/Provenance-XG-Overview.pdf (updated 2010)
Broad Recommendations (I): Short Term (1-2 years)
- There should be a standard way to represent at a minimum three basic provenance entities:
- a handle (URI) to refer to an object (resource)
- a person/entity that the object is attributed to
- a processing step done by a person/entity to an object to create a new object
- A provenance framework should include a mechanism to access provenance-related information addressed by other standards, such as licensing information of the object, digital signature for the object, digital signature for provenance records
- A provenance framework should include a standard way for sites to make provenance information about their content available to other parties in a selective manner, and for others to access that provenance information
Broad Recommendations (II): Longer Term (3-5 years)
- A provenance framework should include a standard way to express the provenance of provenance assertions, as there can be several accounts of provenance and with different granularity and that may possibly conflict
- A provenance framework should include a representation of provenance that is detailed enough to enable reapplying the process and reproduce it
- A provenance framework should allow referring to versions of objects as they evolve over time, or to temporal information statements of when the object was created, modified, or accessed. In particular it should provide for a representation of how one version (or parts thereof) was derived from another version (or parts thereof).
- A provenance framework should include a standard way to represent a procedure which has been enacted
- A provenance framework should include a way to determine commonality of derivation in two resources"
Read PROV-O metadata
Given the URL of a research object, find PROV-O metadata for it as described in the PROV-AQ standard.
We will create a web widget which given a URL, performs a HEAD request to look for the standard HTTP header:
Link: <provenance-URI>; rel="http://www.w3.org/ns/prov#has_provenance"; anchor="target-URI"
If it is found, a button will be displayed to show a popup with provenance information. This will use provjs.
Save PROV-O metadata
For datasets in the West_Life Virtual Folder, we will store provenance information in the University of Southampton Provenance Store or ProvStore. We will provide the Link header whenever provenance metadata has been saved.
We will provide an API to save provenance information, based on provstore-api.
If possible, we will provide a header declaring a Provenance Query Service.
The Common European Research Information Format (CERIF) is a schema for use by "Current Research Information Systems" to exchange information about:
- Persons (researchers/authors)
- Organisational Units (institutions, institutes, etc...)
Where we have metadata for a dataset, we will offer it in CERIF format as described in OpenAire guidelines for use of CERIF.
Does ARIA have a mapping between their vocabulary and CERIF?
Domain Specific Metadata
Also see B2NOTE
Convert a specific provenance chain to a workflow.