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

Re: p:filter select expression

From: Innovimax SARL <innovimax@gmail.com>
Date: Wed, 11 Jun 2008 10:01:06 +0200
Message-ID: <546c6c1c0806110101u1a6761c2od642df760e14640d@mail.gmail.com>
To: Toman_Vojtech@emc.com
Cc: public-xml-processing-model-wg@w3.org

On Wed, Jun 11, 2008 at 9:41 AM,  <Toman_Vojtech@emc.com> wrote:
>
>> -----Original Message-----
>> From: Innovimax SARL [mailto:innovimax@gmail.com]
>> Sent: Wednesday, June 11, 2008 9:32 AM
>> To: Toman, Vojtech
>> Cc: public-xml-processing-model-wg@w3.org
>> Subject: Re: p:filter select expression
>>
>> Well that's not that simple !
>> For example the @select attribut of p:option MUST select a XPathString
>>
>> That XPathString should be evaluated and MUST return a possibility
>> empty set of node
>
> I am sorry if that was not clear from my e-mail; that is exactly what I
> meant.

>
>>
>> Furthermore, I'm not in favor of reusing an error code XD... for the
>> component part
>
> I have no problem with introducing a new error code. But, especially
> because the spec says:
>
> "This step behaves just like an p:input with a select expression except
> that the select expression is computed dynamically."
>
> it sort of makes sense to me to reuse that same error code here
> (XD0016).

I don't think it was the case until now (take a loot at p:load)

Regards,

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 Wednesday, 11 June 2008 08:01:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 11 June 2008 08:01:43 GMT