/[volute]/trunk/projects/dm/provenance/description/provaccess.tex
ViewVC logotype

Diff of /trunk/projects/dm/provenance/description/provaccess.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 4011 by mnullmei, Wed May 3 14:36:32 2017 UTC revision 4012 by francois, Thu May 4 16:04:39 2017 UTC
# Line 1  Line 1 
1  \subsection{Provenance Data Model serialization}  \subsection{Provenance Data Model serialization}
2  There are three possible families of ProvenanceDM metadata serializations, examples for these can be found in the implementation section (\ref{sec:usecases-implementations}) and the links therein.  There are two possible families of ProvenanceDM metadata serializations, examples for these can be found in the implementation section (\ref{sec:usecases-implementations}) and the links therein.
3  \begin{itemize}  \begin{itemize}
4   \item W3C serializations: PROV\-N, PROV\-JSON, PROV\-XML. These are serializations of the W3C provenance data model. They allow the possibility to add additional IVOA or ad hoc attributes to the basic ones in each class. This way the IVOA models can produce W3C compliant serializations.   \item W3C serializations: PROV\-N, PROV\-JSON, PROV\-XML. These are serializations of the W3C provenance data model. They allow the possibility to add additional IVOA or ad hoc attributes to the basic ones in each class. This way the IVOA models can produce W3C compliant serializations.
5   \item Mapping of ProvenanceDM classes onto tables with appropriate relationships. This can allow management by a TAP service (the model mapping is then described with the TAP schema). The serialization will result in a single table according to the query.  % \item Mapping of ProvenanceDM classes onto tables with appropriate relationships. This can allow management by a TAP service (the model mapping is then described with the TAP schema). The serialization will result in a single table according to the query.
6    
7   %\TODO{TAP SCHEMA of the ProvenanceDM datamodel: Maybe Mathieu can provide us with a copy of the TAP schema he designed ?}   %\TODO{TAP SCHEMA of the ProvenanceDM datamodel: Maybe Mathieu can provide us with a copy of the TAP schema he designed ?}
8    
# Line 16  Line 16 
16    xsi:schemaLocation="http://www.ivoa.net/xml/VOTable/v1.2 http://www.ivoa.net/xml/VOTable/v1.2">    xsi:schemaLocation="http://www.ivoa.net/xml/VOTable/v1.2 http://www.ivoa.net/xml/VOTable/v1.2">
17    
18    
19  <RESOURCE name="HiPS">  <RESOURCE name="RGB">
20    
21  <TABLE name="activities" utype="prov:Activity" >  <TABLE name="activities" utype="prov:Activity" >
22    
# Line 76  Line 76 
76  </TABLE>  </TABLE>
77    
78  <TABLE name="usedRelationship" utype="voprov:Used" >  <TABLE name="usedRelationship" utype="voprov:Used" >
79        <FIELD name="head" datatype="char" arraysize="*" />        <FIELD name="activity" ucd="meta.id" utype="prov:Activity.id" datatype="char" arraysize="*" />
80        <FIELD name="tail" datatype="char" arraysize="*" />        <FIELD name="entity" ucd="meta.id" utype="prov:Entity.id" datatype="char" arraysize="*" />
81        <FIELD name="role" datatype="char" utype="Used.role" arraysize="*" />        <FIELD name="role" datatype="char" utype="voprov:Used.role" arraysize="*" />
82  <DATA>  <DATA>
83  <TABLEDATA>  <TABLEDATA>
84  <TR><TD>AlaRGB1</TD><TD>ivo://CDS/P/DSS2/POSSII#POSSII.J-DSS2.143</TD><TD>voprov:input</TD></TR>  <TR><TD>AlaRGB1</TD><TD>ivo://CDS/P/DSS2/POSSII#POSSII.J-DSS2.143</TD><TD>voprov:input</TD></TR>
# Line 89  Line 89 
89  </TABLE>  </TABLE>
90    
91  <TABLE name="WasGeneratedByRelationship" utype="voprov:WasGeneratedBy" >  <TABLE name="WasGeneratedByRelationship" utype="voprov:WasGeneratedBy" >
92        <FIELD name="head" datatype="char" arraysize="*" />        <FIELD name="entity" ucd="meta.id" utype="prov:Entity.id" datatype="char" arraysize="*" />
93        <FIELD name="tail" datatype="char" arraysize="*" />        <FIELD name="activity" ucd="meta.id" utype="prov:Activity.id"  datatype="char" arraysize="*" />
94        <FIELD name="role" datatype="char" utype="WasGeneratedBy.role" arraysize="*" />        <FIELD name="role" datatype="char" utype="voprov:WasGeneratedBy.role" arraysize="*" />
95  <DATA>  <DATA>
96  <TABLEDATA>  <TABLEDATA>
97  <TR><TD>ivo://CDS/P/DSS2color#RGB_NGC6946</TD><TD>AlaRGB1</TD><TD></TD></TR>  <TR><TD>ivo://CDS/P/DSS2color#RGB_NGC6946</TD><TD>AlaRGB1</TD><TD></TD></TR>
# Line 108  Line 108 
108        
109  \end{itemize}  \end{itemize}
110    
111    Such serializations can be retrieved through Access protocols (see \ref{AccessPro} ) or directly integrated in datasets headers or "associated metadata" in order to provide provenance metadata for these datasets.
112    
113    
114  \subsection{Access protocols}  \subsection{Access protocols}
115    \label{AccessPro}
116  We envision two possible access protocols:  We envision two possible access protocols:
117  \begin{itemize}  \begin{itemize}
118  \item ProvDAL: retrieve provenance information based on given id of a data entity or activity  \item ProvDAL: retrieve provenance information based on given id of a data entity or activity
119    
120  ProvDAL is a service whose interface is organized around one main PARAMETER, the ``ID'' of the entity (obs\_publisher\_did of an ObSDataSet for example). The response is given in one of the following formats: PROV-N, PROV-JSON, PROV-XML, PROV-VOTABLE. Additional parameters can complete ID to refine the query. FORMAT allows to choose the output format. STEP allows to discriminate between STEP=LAST, which gives the last step in the provenance chain, and STEP=ALL, which gives the whole chain.  ProvDAL is a service the interface of which is organized around one main PARAMETER, the ``ID'' of the entity (obs\_publisher\_did of an ObSDataSet for example). The response is given in one of the following formats: PROV-N, PROV-JSON, PROV-XML, PROV-VOTABLE. Additional parameters can complete ID to refine the query. FORMAT allows to choose the output format. STEP allows to discriminate between STEP=LAST which gives the last step in the provenance chain and STEP=ALL which gives the whole chain.
121  Multiple ID parameters are allowed in order to retrieve several data sets' provenance details at the same time.  Multiple ID PARAMETER is allowed in order to retrieve several data set provenance details at the same time.
122  \item ProvTAP: allows detailed queries for provenance information, discovery of datasets based on  \item ProvTAP: allows detailed queries for provenance information, discovery of datasets based on
123  e.g. code version.  e.g. code version.
124    
125  ProvTAP is a TAP service implementing the ProvenanceDM data model. The data model mapping is included in the TAP schema (see above). The result of any query is a single table joining information coming from one or several ``provenance'' tables available in the database.  ProvTAP is a TAP service implementing the ProvenanceDM data model. The data model mapping is included in the TAP schema. The mapping of ProvenanceDM classes and attributes onto tables and colomns of the schema with the appropriate relationships, datatypes, units, utypes and ucds is done similarly to the PROV-VOTABLE serialization. The query response will result in a single table according to the query.
126     This  single table is joining information coming from one or several ``provenance'' tables available in the database.
127    
128  A special case is considered where ProvenanceDM and ObsCore are both implemented in the same TAP service and queried together. The TAP response is then providing an Obscore table with a ProvenanceDM extension. We can imagine that in the future this could be hard-coded and registered as an ObsTapProv service.  A special case is considered where ProvenanceDM and ObsCore are both implemented in the same TAP service and queried together. The TAP response is then providing an Obscore table with a ProvenanceDM extension. We can imagine that in the future this could be hard-coded and registered as an ObsTapProv service.
129    

Legend:
Removed from v.4011  
changed lines
  Added in v.4012

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