Provenance Week 2018Participants from our group
| ||||||||
Changed: | ||||||||
< < | ProvONE extension to PROV for workflows | |||||||
> > | ProvONE extension to PROV for workflows(simplify to our needs), instead of AbstractActivity/AbstractEntity | |||||||
Changed: | ||||||||
< < | 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) | ||||||||
Added: | ||||||||
> > | 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) | ||||||||
Added: | ||||||||
> > | 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 | ||||||||
Added: | ||||||||
> > |
Provenance Week 2018Participants from our group
|