Difference: ProvWeekJuly2018 (1 vs. 5)

Revision 52018-08-22 - MireilleLouys

 
META TOPICPARENT name="ObservationProvenanceDataModel"
Changed:
<
<

Provenance Week 2018

>
>

Provenance Week 2018/ Conference in London

 

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

A survey in provenance by Melanie Herschel et. al. 2017

Declarative Datalog Debugging for Mere Mortals by Köhler et. al. 2012 (?)

Yin & Yang: Demonstrating Complementary Provenance from noWorkflow & YesWorkflow by Pimental 2016

A Survey of Data Provenance in e-Science by Simmhan 2005

Provenance in Databases - Why, How and Where by J. Cheney

Links

https://openprovenance.org/

Revision 42018-08-16 - AnastasiaGalkin

 
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

Changed:
<
<		A survey in provenance by Melanie Herschel et. al. 2017
>
>		A survey in provenance by Melanie Herschel et. al. 2017
  Declarative Datalog Debugging for Mere Mortals by Köhler et. al. 2012 (?)

Yin & Yang: Demonstrating Complementary Provenance from noWorkflow & YesWorkflow by Pimental 2016

A Survey of Data Provenance in e-Science by Simmhan 2005

Provenance in Databases - Why, How and Where by J. Cheney

Links

https://openprovenance.org/

Revision 32018-07-13 - AnastasiaGalkin

 
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)
Changed:
<
<
>
>
Added:
>
>
  • Alessandro Spinuso ( s-provenance)
  • Andreas Schreiber (DLR, reproducible science with python)
  • Ashish Gehani (incremental re-computation, accountability)
  • Bertram Ludäscher
  • James Cheney, Edinburgh

Papers

A survey in provenance by Melanie Herschel et. al. 2017

Declarative Datalog Debugging for Mere Mortals by Köhler et. al. 2012 (?)

Yin & Yang: Demonstrating Complementary Provenance from noWorkflow & YesWorkflow by Pimental 2016

A Survey of Data Provenance in e-Science by Simmhan 2005

Provenance in Databases - Why, How and Where by J. Cheney

Links

https://openprovenance.org/

Revision 22018-07-13 - OleStreicher

 
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

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:
>
>
  • Luc Moreau (critics on our Bundle approach, directing to ProvOne)
  • Dong Huynh (python-prov package maintainer)
  • ??? (ProvOne)
  • ??? (UNICORE)

Revision 12018-07-12 - MathieuServillat

 
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

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

View topic | History: r5 < r4 < r3 < r2 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback