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

RE: xml context for p:filter

From: <Toman_Vojtech@emc.com>
Date: Wed, 9 Jul 2008 07:50:18 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870BBADCA6@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-comments@w3.org>

 

> -----Original Message-----
> From: public-xml-processing-model-comments-request@w3.org 
> [mailto:public-xml-processing-model-comments-request@w3.org] 
> On Behalf Of James Fuller
> Sent: Wednesday, July 09, 2008 1:25 PM
> To: public-xml-processing-model-comments@w3.org
> Subject: xml context for p:filter
> 
> 
> to quote the p:filter definition in the latest editors draft
> 
> --------------------
> 
> The p:filter step selects portions of the source document based on a
> (possibly dynamically constructed) XPath select expression.
> 
> <p:declare-step type="p:filter">
>      <p:input port="source"/>
>      <p:output port="result" sequence="true"/>
>      <p:option name="select" required="true"/>
> <!-- XPathExpression -->
> </p:declare-step>
> 
> This step behaves just like an p:input with a select expression except
> that the select expression is computed dynamically.
> 
> --------------------
> 
> if the select expression is computed e.g.
> 
> <p:option name="select" 
> required="fn:concat(a/text(),b/text(),//c/text())"/>
> 

You can't use XPath expressions in the value of "required" in step
daclarations. The only possible values are true|false.
As for the context for computing the select expression, I think the same
rules as for other options apply (see spec, sections 5.7.2 and 5.7.2).

Regards,
Vojtech
Received on Wednesday, 9 July 2008 11:51:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 July 2008 11:51:08 GMT