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

Annotation of /trunk/projects/dm/provenance/description/intro-requirements.tex

Parent Directory Parent Directory | Revision Log Revision Log


Revision 4377 - (hide annotations)
Thu Sep 21 10:48:15 2017 UTC (4 years ago) by mnullmei
File MIME type: application/x-tex
File size: 2812 byte(s)
remaining -- minimal -- grammar, style, and TeX fixes for Section 1
1 kriebe 3641 \subsection{Minimum requirements for provenance}\label{sec:requirements}
2 kriebe 3447
3 kriebe 3641 We derived from our goals and use cases the following minimum requirements for the Provenance Data Model:
4 kriebe 3447
5 kriebe 3641 \begin{itemize}
6 kriebe 3447
7 kriebe 3641 % == other models / serialisation
8 kriebe 3447
9 kriebe 3641 \item Provenance information must be stored in a standard model, with standard serialization formats.
10 kriebe 3447
11 kriebe 3641 \item Provenance information must be machine readable.
12 kriebe 3447
13 mnullmei 4377 \item Provenance data model classes and attributes should be linked to other IVOA concepts when relevant (DatasetDM, ObsCoreDM, SimDM, VOTable, UCDs, \ldots).
14 kriebe 3447
15 mathieu.servillat 3710 \item Provenance information should be serializable into the W3C provenance standard formats (PROV-N, PROV-XML, PROV-JSON) with minimum information loss.
16 kriebe 3447
17    
18 kriebe 3641 % == links between entity/activity
19 kriebe 3447
20 kriebe 3641 \item Provenance metadata must contain information to find immediate progenitor(s) (if existing) for a given entity, i.e. a dataset.
21     %All produced entities must contain information to find its immediate progenitor(s).
22 kriebe 3447
23    
24 kriebe 3641 \item An entity must point to the activity that generated it (if the activity is recorded).
25     %Provenance metadata must contain information to find the activity that generated a given entity.
26     %* All produced entities must contain information to find the activity that generated it
27    
28     \item Activities must point to input entities (if applicable).
29    
30 mathieu.servillat 3710 \item Activities may point to output entities.
31    
32 kriebe 3641 \item Provenance information should make it possible to derive the chronological sequence of activities.
33     %The order of the activities should be available.
34    
35     %\item Provenance information should contain the list of activities and progenitor entities.
36     % too vague .... must be an ordered list ... One step should also be allowed.
37     \end{itemize}
38    
39     % ==== Comment:
40     %These links can be used to trace back the sequence of processing steps (activities) and possibly the interim results.
41    
42    
43     % == additional information
44    
45     \begin{itemize}
46    
47     % Released entities must have a unique, persistent identifier (DOI, obs_publisher_did, ...), at least in their domain.
48     \item Provenance information can only be given for uniquely identifiable entities, at least inside their domain.
49     % comment: (DOI, obs_publisher_did, ...)
50     % Thus entities have to have a unique, persistent identifier.
51     % (to avoid ambiguities).
52    
53     \item Released entities should have a main contact.
54    
55     \item It is recommended that all activities and entities have contact information and contain a (short) description or link to a description.
56     % could also be the documentation.
57    
58     \end{itemize}
59    
60    
61     % Should this go into the requirements or the model?
62     %\item Activities should be defined by following keywords (attributes):
63     % \begin{itemize}
64     % \item unique ID
65     % \item status (COMPLETED/ERROR/...)
66     %
67     %... (see working draft and data model)
68     %* Entities should be defined by... (see working draft and data model)
69    

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