|
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
ProvONE extension to PROV for workflows(simplify to our needs), instead of AbstractActivity/AbstractEntity
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)
- Paolo Missier (ProvOne)
- ??? (UNICORE, UniProv)
- Alessandro Spinuso ( s-provenance)
- Andreas Schreiber (DLR, reproducible science with python)
- Ashish Gehani (incremental re-computation, accountability)
- Bertram Ludäscher
- James Cheney, Edinburgh
Papers |