moved connection language to 2.4 and added initial env to 2.5

langspec/langspec.xml

@@ -435,10 +435,10 @@ free.</para>
          <para>Primary input and primary output ports may be implicitly connected if no explicit
             connection is given, see <xref linkend="primary-input-output"/>.</para>
          <para>Output ports on compound steps have a dual nature: from the perspective of the
-            compound step's siblings, its outputs are just ordinary outputs and can be connected as
-            described above. From the perspective of the subpipeline inside the compound step, they
-            are inputs into which something may be connected to produce the output of the compound
-            step.</para>
+            compound step's siblings, its outputs are just ordinary outputs and can be connected the
+            sames other <glossterm>declared outputs</glossterm>. From the perspective of the
+            subpipeline inside the compound step, they are inputs into which something may be
+            connected to produce the output of the compound step.</para>
          <para>Within a compound step, the <glossterm>declared outputs</glossterm> of the step can
             be connected to any of the various available outputs of <glossterm
                baseform="contained steps">contained steps</glossterm> in combination with other
@@ -624,9 +624,9 @@ free.</para>
          </itemizedlist>
          <para>When an input accepts a sequence of documents, the documents can come from any
             combination of these locations.</para>
-         <para>The output ports are connected by use when their are referenced by another input port
-            or expression.</para>
-         <para>An output may be connected to:</para>
+         <para>In contrast, output ports are connected when they are referenced by another input
+            port, <glossterm baseform="declared outputs">declared output</glossterm> or other
+            expression and may be connected to:</para>
          <itemizedlist>
             <listitem>
                <para>The input port of some other step (including <tag>p:iteration-source</tag> or
@@ -645,6 +645,9 @@ free.</para>
          </itemizedlist>
          <para>As with an input, the output can be a sequence of documents constructed from any
             combination of the above.</para>
+         <para>An output port may have multiple consumers and this results in multiple connections.
+            A subset of these connections are the input port connections for various sibling or
+            contained steps.</para>
          <para>Within the context of a <glossterm>compound step</glossterm>, the <glossterm>declared
                outputs</glossterm> of the compound step must describe their connections.  The set of
             possibilities for this connection is exactly the same set as for any other input port
@@ -799,7 +802,21 @@ free.</para>
       <para>A step with no parent inherits the <glossterm>empty environment</glossterm>. </para>
          <section>
             <title>Initial Environment</title>
-            <para>blah blah blah ...</para>
+            <para>When a pipeline is invoked by a processor, an initial environment is constructed.
+                  <termdef xml:id="dt-initial-environment">An <firstterm>initial
+                     environment</firstterm> is a <glossterm>connection</glossterm> for each of the
+                     <glossterm>readable ports</glossterm> and a set of option bindings used to
+                  construct the <glossterm>in-scope bindings</glossterm>.</termdef>  This
+               environment is used in place of the <glossterm>empty environment</glossterm> that
+               might have otherwise been provided.</para>
+            <para>An implementation is free to provide any set of mechanisms to construct
+               connections for the input ports of the invoked step.  These mechanisms are not
+               limited to the variety of mechnisms described within this specification.  Any
+               extensions are implementation defined.</para>
+            <para>The set of <glossterm>in-scope bindings</glossterm> are constructed from a set of
+               option name/value pairs.  Each option value can be a simple string value, a specific
+               data type instance (e.g. xs:dateTime), or a more complex value like a map item.  How
+               these values are specified is implementation defined.</para>
          </section>
     </section>
     <section xml:id="xpath-context">