[Swift-commit] r3272 - text/swift_pc3_fgcs

[noreply at svn.ci.uchicago.edu]

Author: lgadelha
Date: 2010-04-05 14:18:25 -0500 (Mon, 05 Apr 2010)
New Revision: 3272

Modified:
   text/swift_pc3_fgcs/swift_pc3_fgcs.tex
Log:


Modified: text/swift_pc3_fgcs/swift_pc3_fgcs.tex
===================================================================
--- text/swift_pc3_fgcs/swift_pc3_fgcs.tex	2010-04-05 18:52:06 UTC (rev 3271)
+++ text/swift_pc3_fgcs/swift_pc3_fgcs.tex	2010-04-05 19:18:25 UTC (rev 3272)
@@ -226,7 +226,7 @@
 
 %\begin{verbatim}
 \lstset{basicstyle=\tt \footnotesize}
-\begin{lstlisting}[float,caption=sortProg Swift program.,frame=lines,label=sortprog]
+\begin{lstlisting}[float,caption={\tt sortProg} Swift program.,frame=lines,label=sortprog]
 app (file o) sortProg(file i) {
   sort stdin=@i stdout=@o;
 }
@@ -237,9 +237,9 @@
 %\end{verbatim}
 %\normalsize
 
-The Swift provenance model is close to OPM, but there are some differences. Dataset handles correspond closely with OPM artifacts as immutable representations of data. However they do not correspond exactly. An OPM artifact has unique provenance. However, a dataset handle can have multiple provenance descriptions. For example, in this SwiftScript program:
+The Swift provenance model is close to OPM, but there are some differences. Dataset handles correspond closely with OPM artifacts as immutable representations of data. However they do not correspond exactly. An OPM artifact has unique provenance. However, a dataset handle can have multiple provenance descriptions. For example, in the SwiftScript program displayed in listing \ref{multi}, the expression {\tt c[0]} evaluates to the dataset handle corresponding to the variable {\tt a}. That dataset handle has a provenance trace indicating it was assigned from the constant value {\tt 7}. However, that dataset handle now has additional provenance indicating that it was output by applying the array access operator {\tt []} to the array {\tt c} and the numerical value {\tt 0}.
 
-\begin{lstlisting}[float,caption=Example generating ,frame=lines]
+\begin{lstlisting}[float,caption=Multiple provenance descriptions for a dataset.,frame=lines, label=multi]
 int a = 7;
 int b = 10;
 int c[] = [a, b];
@@ -247,8 +247,8 @@
 \normalsize
 
 
-the expression {\tt c[0]} evaluates to the dataset handle corresponding to the variable {\tt a}. That dataset handle has a provenance trace indicating it was assigned from the constant value {\tt 7}. However, that dataset handle now has additional provenance indicating that it was output by applying the array access operator {\tt []} to the array {\tt c} and the numerical value {\tt 0}.
 
+
 In OPM, the artifact resulting from evaluating {\tt c[0]} is distinct from the artifact resulting from evaluating {\tt a}, although they may be annotated with an isIdenticalTo arc \cite{OPMcollections}.
 
 Except for {\em wasControlledBy}, the dependency relationships defined in OPM can be derived from the {\tt dataset\_usage} database relation. {\em used} and {\em wasGeneratedBy} are explicitly stored in the relation. For instance, if the tuple $\langle P_{id}, D_{id}, {\text I}, R \rangle$ is in the {\tt dataset\_usage} relation then it is equivalent to say $D_{id} \xleftarrow{\text{used(R)}} P_{id}$ in OPM. If we had 'O' instead of 'I' as the value for attribute {\tt direction} it would be equivalent to