W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > July 2007

Re: XProc Editors Draft 2007-07-19: Appendix A.1 Comments

From: Innovimax SARL <innovimax@gmail.com>
Date: Tue, 24 Jul 2007 00:13:19 +0200
Message-ID: <546c6c1c0707231513wca78d82p7e31a60b7c1f50d2@mail.gmail.com>
To: "Jeni Tennison" <jeni@jenitennison.com>
Cc: public-xml-processing-model-wg@w3.org

Jeni

On 7/23/07, Jeni Tennison <jeni@jenitennison.com> wrote:
>
> A.1.3 Equal: The fail-if-not-equal option hasn't been described. Why
> return "1" or "0" rather than the more human-readable "true" or "false"?

I think it match directly boolean() of XPath, isn'it ?

> A.1.8 Insert: There's no need to specify an XPath context here, since
> this step has a match pattern, not a select expression.
>
> A.1.8 Insert: It would seem more useful to me to have insert add an
> element before or after the matched element itself. This would enable
> you to insert an element as the middle child, or in order (if the source
> was already sorted):
>
>    <p:insert>
>      <p:input port="insertion">
>        <p:inline><item n="3" /></p:inline>
>      </p:input>
>      <p:option name="match" value="/list/item[@n &lt; 3][last()]" />
>      <p:option name="before-or-after" value="before" />
>    </p:insert>

Well what do you do in case the match pattern doesn't match anything ?

Mohamed
-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Monday, 23 July 2007 22:13:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:53 GMT