The purpose of this page is to analyze how the current RO model can be converted to other standards /vocabularies, or how other standards such as the W3C PROV-O can be converted to the RO model.
There is a related page ??Mapping RO Provenance to W3C PROV-O created for D4.2 M20. At the moment, we are aligning these two pages and people are advised not to use either of the page until this alignment is completed.
The rationale behind this decission is that Taverna is exporting provenance according to prov-o, and we want to have an equivalence between both vocabularies, in order to be able to incorpore them to our Research Objects
| PROV-O Term
|| RO term
|prov:Bundle||N/A||no direct mapping|
||owl:sameAs (should hopefully point to RO resource)|
The patterns below are extracted from the N3 rules of https://github.com/wf4ever/ro/tree/master/mapping/prov-o/
but can easily be rewritten to SPARQL CONSTRUCT ... WHERE ... queries.
|The above only works if PROV-O export from Taverna has saved the output to ?alias - for example:
The PROV-O export does not currently expose intermediate values, hence those would also be lacking ?alias, and those are not included in the wfprov mapping.
|As in the previous note for Usage, this only works if PROV-O export has saved the output to ?alias.|
quite taverna-prov specific which assumes that the engine must also have created the provenance container based on the workflow run