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

Re: Where is my c:result?

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 19 Sep 2008 09:19:59 -0400
To: James Garriss <james@garriss.org>
Cc: "xproc-dev\@w3.org" <xproc-dev@w3.org>
Message-ID: <m21vzgs268.fsf@nwalsh.com>
James Garriss <james@garriss.org> writes:

> Excellent.  My mistake was assuming that p:compare had a primary output.
> What should have tipped me off as I read the spec?  Is it that primary
> equals false?  From the spec:

Yep, primary=false is the flag.

> <p:declare-step type="p:compare">
>      <p:input port="source" primary="true"/>
>      <p:input port="alternate"/>
>      <p:output port="result" primary="false"/>
>      <p:option name="fail-if-not-equal" select="'false'"/>         <!--
> boolean -->
> </p:declare-step>
>
> As to a working solution, you had the right idea, but as calabash informs
> us:  Attribute "step" not allowed on p:output.  Instead, we can put a result
> port in p:compare, like such:
>
>     <p:compare fail-if-not-equal="true" name="compareBookstores">
>         <p:input port="source">
>             <p:pipe step="main" port="source"/>
>         </p:input>
>         <p:input port="alternate">
>             <p:pipe step="main" port="alternate"/>
>         </p:input>
>         <p:output port="result"/>
>     </p:compare>

No, that's not right. You aren't allowed to put a p:output on an atomic
step. Does Calabash miss that too? Sigh. Another day, another bug :-)

The output port is part of the declaration of the p:compare step.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | A proof tells us where to concentrate
http://nwalsh.com/            | our doubts.-- Anonymous

Received on Friday, 19 September 2008 13:20:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 19 September 2008 13:20:41 GMT