- From: Murray Maloney <murray@muzmo.com>
- Date: Thu, 07 Dec 2006 21:27:28 -0500
- To: XProc WG <public-xml-processing-model-wg@w3.org>
Here's a sub-proposal to rename and consolidate. The <p:pipe/> was offered
by Richard
as an alternative for <p:internal/>. I really like the name because it fits
into and supports
the pipeline metaphor so readily. I realized why I objected to
<p:document/> for <p:here/>
and I decided to consolidate <p:external/> with <p:here/> to garner a
simple <p:document/>
that encompasses both into a single element. The distinction that we are
left with is between
pipes and documents. No need to simplify any further.
Consider...
<p:input port="myInput" select="..." sequence="no">
<p:pipe step="step1" port="result" />
<p:document href="http://www.muzmo.com/.../document.xml"/>
<p:document><p>Document is right here.</p></p:document>
</p:input>
<p:output port="myOutput" select="..." >
<p:pipe step="step8" port="result" />
<p:document href="http://www.muzmo.com/.../document.xml"/>
<p:document><p>Document is right here.</p></p:document>
</p:output >
Default <p:pipe/> attribute values are step="previous" or step="next"
depending on
whether the active context is <input> or <output>. The default is always
port="result."
I have always appreciated the power inherent in co-constraints between content
and a privileged attribute, especially when one of them is (or implies) a link.
In the case that both href value and content are provided on <p:document>
the href value has precedence by default, but it is not an error to provide
both.
<p:input port="myInput" select="..." sequence="no">
<p:document href="http://www.muzmo.com/.../document.xml"> <!-- has
precedence -->
<p>Document is right here.</p> <!-- ignored -->
</p:document>
</p:input>
Received on Friday, 8 December 2006 02:28:00 UTC