Last modified by adavison on 2022/05/23 22:24
From version 10.3
edited by adavison
on 2020/08/05 11:46
Change comment: There is no comment for this version
To version 5.1
edited by adavison
on 2020/08/05 08:44
Change comment: Uploaded new attachment "starting-points.svg", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  == Introduction ==
2 2  
3 -Computational provenance is a record of all the steps in a computational scientific workflow, including the code that was run, input data, the computational environment (hardware, OS, compiler versions, library version...), the person who performed each step, and output data.
3 +Computational provenance is a record of all the steps in a computational scientific workflow, including the code that was run, input data, the computational environment (hardware, OS, compiler versions, library version...), and output data.
4 4  
5 5  Capturing computational provenance facilitates:
6 6  
... ... @@ -8,28 +8,16 @@
8 8  * management and tracking of workflows/projects by the scientists/engineers involved
9 9  * evaluation/review by other scientists and engineers
10 10  
11 +
11 11  
12 12  == Standards ==
13 13  
14 -The [[W3C PROV standard>>https://www.w3.org/TR/2013/NOTE-prov-overview-20130430/||rel="noopener noreferrer" target="_blank"]] provides a data model and related tools for provenance interchange on the web. The following diagram shows the three base classes of the PROV data model: Entity, Activity, and Agent. These three classes form the basis for the representation of provenance in the EBRAINS Knowledge Graph: every node in the KG has a type which is a subclass of one of these base classes.
15 +Information about the W3C PROV ontology and related tools
15 15  
16 -[[image:starting-points.svg||alt="The three Starting Point classes of the W3C PROV ontology and the properties that relate them."]]
17 17  
18 18  == Storage of provenance in the Knowledge Graph ==
19 19  
20 -We present here the current schemas for representing (a) data analysis and (b) simulations in the Knowledge Graph. These schemas will need to be extended to cover neurorobotics simulations, and probably a more explicit representation of pipelines/workflows (the chaining together of multiple analysis / simulation stages) will be needed.
21 21  
22 -[[image:Workflow provenance in the EBRAINS KG.svg||alt="KG schema for data analysis"]][[image:Workflow provenance in the EBRAINS KG-2.png||alt="KG schema for data analysis"]]
23 -
24 -[[image:Workflow provenance in the EBRAINS KG.png||alt="KG schema for simulation"]]
25 -
26 -(note that the diagrams do not show Agents; the person who launched each analysis/simulation activity is linked to the activity with a ##wasAssociatedWith## connection).
27 -
28 -(% class="box warningmessage" %)
29 -(((
30 -TODO: insert or link to the detailed schemas for each type
31 -)))
32 -
33 33  == Tools for automated capture of provenance ==
34 34  
35 35  * on different systems:
... ... @@ -44,6 +44,7 @@
44 44  
45 45  * local cache and synchronization?
46 46  
35 +
47 47  == User interfaces for browsing, visualizing, and searching provenance information ==
48 48  
49 49  
Workflow provenance in the EBRAINS KG-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.adavison
Size
... ... @@ -1,1 +1,0 @@
1 -58.6 KB
Content
Workflow provenance in the EBRAINS KG.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.adavison
Size
... ... @@ -1,1 +1,0 @@
1 -49.9 KB
Content
Workflow provenance in the EBRAINS KG.svg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.adavison
Size
... ... @@ -1,1 +1,0 @@
1 -159.5 KB
Content