Difference: ProvWeekJuly2018 (1 vs. 2)

  META TOPICPARENT 
  name="ObservationProvenanceDataModel"  

 Provenance Week 2018 



Participants from our group
 

 Anastasia Galkin (poster presentation here)
  Ole Streicher
  Michèle Sanguillon
  Mathieu Servillat
 
See the Webpage and Program of the meeting.

Topics discussed
- META TOPICPARENT
+  name="ObservationProvenanceDataModel"
-<
<
+ProvONE extension to PROV for workflows
->
>
+ProvONE extension to PROV for workflows(simplify to our needs), instead of AbstractActivity/AbstractEntity
-<
<
+prov:Plan for the EntityDescription
->
>
+prov:Plan for the ActivityDescription (instead of prov:Bundle)
 see Process/Program from ProvONE and UNICORE (poster for HPC workflows)
->
>
+Subclass Parameter from Entity (see UNICORE poster)
 Focus on Entities rather than on Activities (descriptions as a Plan, i.e. an Entity)

Triple Store, Neo4j...

SPADE: tool to capture provenance in an OS

Provenance Patterns (RDA)
->
>
+python-prov may handle extensions (like ProvOne), if done correctly; we may derive from it ( not cut&paste) to include our extensions (votable handling, ProvOne etc.)
 Contacts
->
>
+ Luc Moreau (critics on our Bundle approach, directing to ProvOne)
  Dong Huynh (python-prov package maintainer)
  ??? (ProvOne)
  ??? (UNICORE)

META TOPICPARENT	name="ObservationProvenanceDataModel"

Provenance Week 2018

Participants from our group

See the Webpage and Program of the meeting.

Topics discussed

ProvONE extension to PROV for workflows

prov:Plan for the EntityDescription

see Process/Program from ProvONE and UNICORE (poster for HPC workflows)

Focus on Entities rather than on Activities (descriptions as a Plan, i.e. an Entity)

Triple Store, Neo4j...

SPADE: tool to capture provenance in an OS

Provenance Patterns (RDA)

Contacts