—————————–

• Markus D: how can we realize the simple thing : time series —> progenitor

need some description of an Activity : Extraction of a mag from an image etc .. follow the Prov relations : wasDerivedFrom or wasGeneratedby + Activity ID+ Used

• Carlos's use-case : Provenance from points in a SED or light curve

linking points in a data set to other dataproducts : extracted image, extracted spectrum, etc. Is it simple to solve? -without the prov DM: datalink + progenitor link if it exists datalink + preview if we want to illustrate only the point via an image -with provenance info : select the wasDerived relation in Prov : it will provide you with a progenitor if present.

• François : linking the prov info from Obscore : a prov column which contains a link to a Prov document in one PROV format (PROV-N, or PROV-JSON)

• IVOA PROV Data model design:

A suggestion to handle ActivityDescription by Ole

Example of Ole:

• Top graph: representation of an activity executed on real data
• Below graph : Define a template for a an ActivityDescription here “musesci_post” with known roles, with context dependent names, for instance here in the muse:namespace

a Bundle class (W3C compatible) for expressing ActivityDescription - solves the pb of roles A realisation of an Activity:

• uses the activity template
• uses entities with used roles and generated roles defined in the bundle for description

Musesci_post123 : Activity Instance has relation “Used” with role= “voprov:description” with instance Musesci_post:Bundle

All other used relation should instantiate a role defined in the related Bundle with domain specific namespace, here “muse:” Bundle is a W3C class derived from an Entity. This should be also possible in a VOTable serialisation

Discussion with Marco Molinaro about the potential use of the TAP-Autocomplete library at Trieste. Topics included a description of the available modes of usage, and what would be required at Trieste for potential installation and use of it. Carlos Rodrigo Blanco also expressed interest, and proposed the idea of having the library as a browser add on, which would work on any TAP GUI.

• Container technology (Docker etc) [BoF]
• Publishing tools and auth&aut [Marco]

• Informal discussion about DataLink requirements in TOPCAT
  • Mark T and Markus D, Mark T and Carlos - useful requirements input from data providers