Provenance day in Heidelberg, Germany, 2016 June 14th

hosted at ARI, prior to the data forum http://www.g-vo.org/edp-forum-2016

Follow-up meeting

Participants

insert your name here...

Venue

A room is reserved for us at Astronomisches Rechen-Institut (ARI), see http://www.g-vo.org/edp-forum-2016/venue.html for how to get there.

Topics discussed

See Minutes from Mathieu attached here and from Kristin attached here

Apologies for the draft nature of the minutes -- Mireille

* Data Model updates

* Structuring a database from the data model

* Storing/serializing the Activity/Entity Descriptions

- AI Mathieu: make a proposition for next meeting (vo-table params? or json? xml?)

* Access to the Provenance database

- prepare a first version without "Parameter"-class and a link to ObsCore /

- prototype a ProvTAP based on a dedicated TAP schema for Activity/Agent/Entity reusing ObsTAP for Entity? (not sure I got it right ...ML)

* Structure and content of the IVOA working draft

* Roadmap for Trieste (Interop in October) and beyond

* Contributions to ADASS Oct. 2016?

- AI: Kristin: Provenance Overview/Review --> oral proposal submitted

- AI: Mathieu: CTA + Provenance -->

* Next Provenance day meeting: arranged for July 20th

* News : the Provenance Week , washington DC in June / RDA interest group (little activity) / next RDA meeting in Denver , attached to CODATA conference

Goals as proposed for roadmap (Kristin)

• define minimum requirements for the data model
• finalize the data model (diagram)
  so that it works with only minor modifications for all our use cases
  including VODML-compliant representation (e.g. using Modelio, Magic Draw)
• have the draft out as official working draft possibly before Trieste
  • structure of the draft
  • rewrite a concise introduction : AI: Mathieu: goals , definition for the "provenance" term in our context, how it is inserted in astronomical context, what it is not (different from Workflow, for instance), previous efforts, insert architecture section
  • including minimum requirements
    • what is needed and reused from the W3C proposal: a kind of W3C Core
  • including a section on serialising the data model
  • including a section on accessing provenance data

• examples
  • get the progenitors for a specified dataset (entity)
  • give me the history, activities and progenitors for a particular entity
  • responsibility view for the agent : who was involved for this activity
  • for this entity get me the activities execution status and activity description

• is Activity description part of the model or part of the implementation
• should we plan diff levels of detail? e.g., details levels : basic, detailed, full??
  
• it is up to the applications and access services --> AI Mireille? all ?: iterate to reformulate more simply

• Assign sections to various writers and decide a deadline: end of July?
• Work out relations between SimDM and ProvDM
  • Have at least one use case worked out with both models