[Swift-commit] r2859 - provenancedb

[noreply at svn.ci.uchicago.edu]

Author: benc
Date: 2009-04-15 04:55:28 -0500 (Wed, 15 Apr 2009)
New Revision: 2859

Modified:
   provenancedb/provenance.xml
Log:
ongoing provenance notes

Modified: provenancedb/provenance.xml
===================================================================
--- provenancedb/provenance.xml	2009-04-15 09:20:38 UTC (rev 2858)
+++ provenancedb/provenance.xml	2009-04-15 09:55:28 UTC (rev 2859)
@@ -1943,6 +1943,30 @@
 like a plain binary operator inside the Swift compiler and runtime)
 </para>
 
+<para>
+provenance of references vs provenance of the data in them: the array and
+structure access operators can be used to acquire <literal>DSHandle</literal>s
+which have no value yet, and which are then subsequently assigned. In this
+usage, the provenance of the containing structure should perhaps be that it
+is constructed from the assignments made to its members, rather than the
+other way round. There is some subtlety here that I have not fully figured
+out.
+</para>
+
+<para>
+Piecewise construction of collections: arrays and structs can be
+constructed piecewise using <literal>. =</literal> and <literal>[] =</literal>.
+how is this to be represented in OPM? perhaps the closing operation maps
+to the OPM process that creates the array, so that it ends up looking
+like an explicit array construction, happening at the time of the close?
+</para>
+
+<para>
+Provenance of mapper parameters: mapper parameters are artifacts. We can
+represent references to those in a Swift-specific part of an artifacts
+value, perhaps. Probably not something OPM-generalisable.
+</para>
+
 </section>
 
 </section>