W3C home > Mailing lists > Public > xproc-dev@w3.org > December 2008

binding primary output in a declare-step

From: James Sulak <jsulak@gmail.com>
Date: Sun, 7 Dec 2008 15:29:22 -0600
Message-ID: <7cb78b3b0812071329u2d1e4382x44b5a06feb54c508@mail.gmail.com>
To: xproc-dev <xproc-dev@w3.org>

Related to today's earlier discussion, is it a bug that I can't use
p:output to bind a primary port, or am I not understanding something?
For example, why does

<p:declare-step xmlns:p="http://www.w3.org/ns/xproc">
  <p:input port="source" primary='true'>
    <p:document href="test.xml"/>
  </p:input>
  <p:output port="res" sequence="true" >
    <p:pipe step="ident" port="result" />
  </p:output>
  <p:identity name="ident" />
</p:declare-step>

work, while

<p:declare-step xmlns:p="http://www.w3.org/ns/xproc">
  <p:input port="source" primary='true'>
    <p:document href="test.xml"/>
  </p:input>
  <p:output port="res" sequence="true" primary="true">
    <p:pipe step="ident" port="result" />
  </p:output>
  <p:identity name="ident" />
</p:declare-step>

does not?  I think the two pipelines should be equivalent, if I
understand things properly.

Thanks,

-James
Received on Sunday, 7 December 2008 21:29:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 7 December 2008 21:29:58 GMT