/[volute]/trunk/projects/dm/provenance/description/intro-previousefforts.tex
ViewVC logotype

Contents of /trunk/projects/dm/provenance/description/intro-previousefforts.tex

Parent Directory Parent Directory | Revision Log Revision Log


Revision 4377 - (show annotations)
Thu Sep 21 10:48:15 2017 UTC (3 years, 10 months ago) by mnullmei
File MIME type: application/x-tex
File size: 3284 byte(s)
remaining -- minimal -- grammar, style, and TeX fixes for Section 1
1 \subsection{Previous efforts}
2 The provenance concept was early introduced by the IVOA within the scope of the
3 Observation Data Model \citep[see IVOA note by ][]{note:observationdm}, as a
4 class describing where the data is coming from. A full observation data model
5 specifically dedicated to spectral data was then designed \citep[Spectral Data
6 Model,][]{std:SpectralDM}, as well as a fully generic characterisation
7 data model of the measurement axes of data \citep[Characterisation Data
8 Model,][]{std:CharacterisationDM}, while the progress on the provenance data
9 model was slowing down.
10
11 The IVOA Data Model Working Group first gathered various use cases coming from
12 different communities of observational astronomy (optical, radio, X-ray,
13 interferometry). Common motivations for a provenance tracing of their history
14 included: quality assessment, discovery of dataset progenitors, and access to
15 metadata necessary for reprocessing. The provenance data model was then designed
16 as the combination of \emph{Data processing}, \emph{Observing configuration},
17 and \emph{Observation ambient conditions} data model classes.
18 The \emph{Processing class} was embedding a sequence of processing stages which
19 were hooking specific ad hoc details and links to input and output datasets,
20 as well as processing step descriptions. Despite the attempts at
21 an UML description of the model and writing XML serialization examples, the IVOA
22 efforts failed to provide a workable solution: the scope was probably too
23 ambitious and the technical background too unstable. A compilation of these
24 early developments can be found on the IVOA site \citep{std:previousefforts}.
25 From 2013 onwards, the IVOA concentrated on use cases related to processing
26 description and decided to design the model by extending the basic W3C
27 provenance structure, as described in the current specification.
28
29 Outside of the astronomical community, the Provenance Challenge series (2006 --
30 2010), a community effort to achieve inter-operability between different
31 representations of provenance in scientific workflows, resulted in the Open
32 Provenance Model (OPM) \citep{moreau2010}. Later, the W3C Provenance Working
33 Group was founded and released the W3C Provenance Data Model as Recommendation
34 in 2013 \citep{std:W3CProvDM}. OPM was designed to be applicable to anything,
35 scientific data as well as cars or immaterial things like decisions. With the
36 W3C model, this becomes more focused on the web. Nevertheless, the core concepts
37 are still in principle the same in both models and are very general, so they
38 can be applied to astronomical datasets and workflows as well. The W3C model was
39 taken up by a larger number of applications and tools than OPM, we are therefore
40 basing our modeling efforts on the W3C Provenance Data Model, making it less
41 abstract and more specific, or extending it where necessary.
42
43
44 The W3C model even already specifies PROV-DM Extensibility Points (section 6 in
45 \citealt{std:W3CProvDM}) for extending the core model. This allows one to
46 specify additional roles and types for each entity, agent or relation using the
47 attributes \texttt{prov:type} and \texttt{prov:role}. By specifying well-defined
48 values for the IVOA model, we can adjust the model to our needs while still
49 being compliant with W3C.
50

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26