- From: James Fuller <james.fuller.2007@gmail.com>
- Date: Wed, 9 Jul 2008 13:53:30 +0200
- To: Toman_Vojtech@emc.com
- Cc: public-xml-processing-model-comments@w3.org
On Wed, Jul 9, 2008 at 1:50 PM, <Toman_Vojtech@emc.com> wrote: > > > >> -----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 yes, sorry that was a typo > 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). should be something like <p:with-option name="select" select="fn:concat(a/text(),b/text(),//c/text())"/> and yes I agree that options handling applies J
Received on Wednesday, 9 July 2008 11:54:06 UTC