[Swift-commit] r2632 - provenancedb

[noreply at svn.ci.uchicago.edu]

Author: benc
Date: 2009-03-02 07:53:21 -0600 (Mon, 02 Mar 2009)
New Revision: 2632

Modified:
   provenancedb/provenance.xml
Log:
OPM export notes

Modified: provenancedb/provenance.xml
===================================================================
--- provenancedb/provenance.xml	2009-03-01 21:15:13 UTC (rev 2631)
+++ provenancedb/provenance.xml	2009-03-02 13:53:21 UTC (rev 2632)
@@ -1718,26 +1718,6 @@
 in this file)
 </para>
 </section>
-
-<section><title>Open provenance model (OPM)</title>
-<para>
-should provenance record track compound procedures? at present its
-heading in a direction where it only tracks app procedures, without
-regard for inputs and outputs of compound procedures.
-The turns datasets into having multiple producers - each level counts as
-having produced it. OPM model has some discussion of that as
-'alternate descriptions' in s3.
-</para>
-<para>
-relation to OPM Open Provenance Model
-<ulink url="http://twiki.ipaw.info/bin/view/Challenge/OPM"
->http://twiki.ipaw.info/bin/view/Challenge/OPM</ulink>
-<ulink url="http://eprints.ecs.soton.ac.uk/14979/1/opm.pdf"
->http://eprints.ecs.soton.ac.uk/14979/1/opm.pdf"</ulink>
-might be useful for the vocabulary at least
-</para>
-</section>
-
 <section><title>Input parameters</title>
 <para>
 Should also work on workflows which take an input parameter, so that we
@@ -1760,7 +1740,56 @@
 
 </section>
 
+<section id="opm"><title>Open Provenance Model (OPM)</title>
+<section><title>OPM-defined terms and their relation to Swift</title>
+<para>
+OPM defines a number of terms. This section describes how those terms
+relate to Swift.
+</para>
+<para>
+artifact: This OPM term maps well onto the internal Swift representation
+of <literal>DSHandle</literal>s. Each DSHandle in a Swift run is an
+OPM artifact, and each OPM artifact in a graph is a DSHandle.
+</para>
+<para>collection: OPM collections are a specific kind of artifact, containing
+other artifacts. This corresponds with DSHandles for composite data types
+(structs and arrays). OPM has collection accessors and collection
+constructors which correspond to the <literal>[]</literal> and
+<literal>.</literal> operators (for accessors) and various assignment
+forms for constructors.
+</para>
+<para>
+process: An OPM process corresponds to a number of Swift concepts (although
+they are slowly converging in Swift to a single concept). Those concepts
+are: procedure invocations, function calls, and operators.
+</para>
+<para>
+agent: There are several entities which can act as an agent. At the
+highest level where only Swift is involved, a run of the
+<literal>swift</literal> commandline client is an agent which drives
+everything. Some other components of Swift may be regarded as agents,
+such as the client side wrapper script. For present OPM work, the
+only agent will be the Swift command line client invocation.
+</para>
+<para>
+account: For present OPM work, there will be one account per workflow run.
+In future, different levels of granularity that could be expressed through
+different accounts might include representing compound procedure calls as
+processes vs representing atomic procedures calls explicitly.
+</para>
+<para>
+OPM graph: there are two kinds of OPM graph that appear interesting and
+straightforward to export: i) of entire provenance database (thus containing
+multiple workflow runs); ii) of a single run
+</para>
+</section>
+<section><title>OPM links</title>
+<para><ulink url="http://twiki.ipaw.info/bin/view/Challenge/OPM">Open Provenance Model at ipaw.info</ulink></para>
+</section>
+</section>
 
+
+
 <section><title>stuff</title>
 <para>
 TODO transcribe info from the pile of papers I wrote. esp query analysis