[Volute] r3617 - trunk/projects/dm/provenance/description

Volute commit messages volutecommits at g-vo.org
Wed Oct 12 10:13:40 CEST 2016


Author: kriebe
Date: Wed Oct 12 10:13:39 2016
New Revision: 3617

Log:
Edits for provaccess

Modified:
   trunk/projects/dm/provenance/description/ProvDM.pdf
   trunk/projects/dm/provenance/description/provaccess.tex

Modified: trunk/projects/dm/provenance/description/ProvDM.pdf
==============================================================================
Binary file (source and/or target). No diff available.

Modified: trunk/projects/dm/provenance/description/provaccess.tex
==============================================================================
--- trunk/projects/dm/provenance/description/provaccess.tex	Tue Oct 11 23:02:09 2016	(r3616)
+++ trunk/projects/dm/provenance/description/provaccess.tex	Wed Oct 12 10:13:39 2016	(r3617)
@@ -1,38 +1,47 @@
-
-
-\subsection{provenance DataModel serialization}
-There are three possible families of ProvDM metadata serialization
+\subsection{Provenance Data Model serialization}
+There are three possible families of ProvDM metadata serializations.
 \begin{itemize}
- \item W3C serializations : Prov-N, PROV\-Json, PROV\-XML. These formats allow the possibility to add additional IVOA or ad hoc attributes to the basic ones in each class.
+ \item W3C serializations: Prov-N, PROV\-Json, PROV\-XML. These are serialization 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 Mapping of ProvDM classes onto tables with appropriate relationships. This can allow managment by a TAP service (the model mapping is then described with the TAP schema). The serialization will be a single table according to the query.
 
- \TODO{TAP SCHEMA of the ProvDM datamodel: Maybe Matthieu can provide us with a copy of the TAP schema he designed ?}
-  \item Direct VOTABLE mapping by using   some ad hoc mapping based on transcription of PROV-N format : this is called PROV-VOTABLE. Moreover in the future we could also define a VO-DML mapping (ref) version of the mapping.
-The following is an example of provenance metadata in this PROV-VOTABle format. Objects become Tables the class of which is rendred by a utype. Attributes and relationships become FIELDS or PARAMS. The model attribute names also become VOTABLE utypes.  
+ \TODO{TAP SCHEMA of the ProvDM datamodel: Maybe Mathieu can provide us with a copy of the TAP schema he designed ?}
+ \item Direct VOTABLE mapping by using some ad hoc mapping based on transcription of PROV-N format: this is called PROV-VOTABLE. Moreover in the future we could also define a VO-DML (\textbf{ref}) version of the mapping.
+The following is an example of provenance metadata in this PROV-VOTABLE format. Objects become tables, the class of which is rendered by a utype. Attributes and relationships become FIELDS or PARAMS. The model attribute names also become VOTABLE utypes.  
 \begin{verbatim}
-<TABLE name="cta:telescope_stage_520" utype="prov:activity" >
-     <PARAM name="start" utype="prov:startTime" datatype="char" arraysize="*" xtype="ISO8601" value="2015-07-30T09:45:00" >
-     <PARAM name ="stop" utype="prov:endTime"  datatype="char" arraysize="*" xtype="ISO8601" value = "2015-07-30T10:00:00" >
-     <PARAM name="methodname" utype="voprov:method_name" dataype="char" arraysize="*" value="Telescope_stage" >
-     <PARAM name="version" utype="voprov:method_version" datatype="char" arraysize="*" value="1.0" >    
-     <PARAM utype="voprov:used" datatype="char" arraysize="*" value="cta:run13000_EVT0" >
-     <PARAM utype="voprov:used" datatype="char" arraysize="*" value="cta:Stage1Config_5250" >    
+<TABLE name="cta:telescope_stage_520" utype="prov:activity">
+    <PARAM name="start" utype="prov:startTime" datatype="char" 
+           arraysize="*" xtype="ISO8601" value="2015-07-30T09:45:00">
+    <PARAM name ="stop" utype="prov:endTime"  datatype="char" 
+           arraysize="*" xtype="ISO8601" value = "2015-07-30T10:00:00">
+    <PARAM name="methodname" utype="voprov:method_name" dataype="char" 
+           arraysize="*" value="Telescope_stage">
+    <PARAM name="version" utype="voprov:method_version" datatype="char" 
+           arraysize="*" value="1.0">    
+    <PARAM utype="voprov:used" datatype="char" arraysize="*" 
+           value="cta:run13000_EVT0">
+    <PARAM utype="voprov:used" datatype="char" arraysize="*" 
+           value="cta:Stage1Config_5250">
 </TABLE>
-<TABLE name="cta:Stage1Config_5250", utype="prov:entity" >
-    <PARAM name="type" utype="prov:type" datatype="char" arraysize="*" value="file" >   
+<TABLE name="cta:Stage1Config_5250", utype="prov:entity">
+    <PARAM name="type" utype="prov:type" datatype="char" 
+           arraysize="*" value="file">   
 </TABLE>
-<TABLE name="cta:run1000_EVT1", utype="prov:entity" >
-      <PARAM name="label" utype="prov:label"datatype="char" arraysize="*" value="EVT1 file" >
-      <PARAM name="type" utype="prov:type" datatype="char" arraysize="*" value="file" >
-      <PARAM name="run" utype="cta:runNumber" datatype="int"  value="13000" >
-      <PARAM name="tel" utype="cta:telescope" datatype="char" arraysize="*" value="MST21" >
-      <PARAM utype="wasGeneratedBy"  datatype="char" arraysize="*" value="cta:Stage1Config_5250">
+<TABLE name="cta:run1000_EVT1", utype="prov:entity">
+    <PARAM name="label" utype="prov:label" datatype="char" arraysize="*" 
+           value="EVT1 file">
+    <PARAM name="type" utype="prov:type" datatype="char" arraysize="*" 
+           value="file">
+    <PARAM name="run" utype="cta:runNumber" datatype="int"  value="13000">
+    <PARAM name="tel" utype="cta:telescope" datatype="char" arraysize="*" 
+           value="MST21">
+    <PARAM utype="wasGeneratedBy" datatype="char" arraysize="*" 
+           value="cta:Stage1Config_5250">
 </TABLE>
 \end{verbatim}
   
   
 \end{itemize}
-\subsection{access protocols}
+\subsection{Access protocols}
 \begin{itemize}
 \item ProvDAL: retrieve provenance information based on given id of a dataEntity or activity
 
@@ -41,7 +50,7 @@
 \item ProvTAP: allows detailed queries for provenance information, discovery of datasets based on 
 e.g. code version.
 
-ProvTAP is a TAP service implementing the ProvDM datamodel. The PROVDM  mapping is included in the TAP schema (see above). The result of any query is a single table joigning information coming from one or several "provenace" tables available in the database. 
+ProvTAP is a TAP service implementing the ProvDM datamodel. The PROVDM  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. 
 
 A special case is considered where ProvDM and OBscore are both implemented in the same TAP service and queried together. The TAP response is then providing an Obscore Table with a ProvDM extension. We can imagine that in the future this could be hard-coded and registered as an ObsTAPRov service. 
 


More information about the Volutecommits mailing list