/ Rui Lopes <rlopes@di.fc.ul.pt> was heard to say:
| Well, if we want consistency between steps and pipelines, I believe we should
| allow the definition of simple parameters (i.e. booleans, integers, etc.) in a
| pipeline, the same way it has been talked regarding steps parameters. Having
| this helps on defining a standardized sub-pipeline processing component.
I'm not sure about booleans and integers. I think I'd like to keep
types out of it and just let parameters all be strings.
I was thinking we could perhaps harmonize the two by saying that the
pipeline parameters become variable bindings in the static context for
XPath evaluation of p:if component expressions. Then we could say that
a p:if component without any test document evaluates its expression
against an empty document node.
<p:pipeline>
<p:parameter name="debug" select="1"/>
<p:input name="doc"/>
<p:input name="style"/>
<p:xslt>
<p:input name="stylesheet" label="style"/>
<p:input name="document" label="doc"/>
<p:output name="result"/>
</p:xslt>
<p:tee>
<p:input label="result"/>
<p:output name="styledresult"/>
<p:output name="testdoc"/>
</p:tee>
<p:if test-document="testdoc" xpath="/fo:root">
<p:input name="doc" label="styledesult"/>
<p:then>
<p:if xpath="$debug != 0">
<p:then>
<p:message>FO output</p:message>
</p:then>
</p:if>
<p:save href="someURI.fo">
<p:input name="document" label="doc"/>
</p:save>
</p:then>
<p:else>
<p:if xpath="$debug != 0">
<p:then>
<p:message>Non-FO output</p:message>
</p:then>
</p:if>
<p:save href="someURI.html">
<p:input name="document" label="doc"/>
</p:save>
</p:else>
</p:if>
</p:pipeline>
Be seeing you,
norm
--
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.