- From: <Toman_Vojtech@emc.com>
- Date: Thu, 13 Nov 2008 12:09:56 -0500
- To: <public-xml-processing-model-comments@w3.org>
Hi Norm, It seems like you have missed my last comment on this topic, so I am resending it just to make sure the problem is fixed in the CR draft. Regards, Vojtech > -----Original Message----- > From: public-xml-processing-model-comments-request@w3.org > [mailto:public-xml-processing-model-comments-request@w3.org] > On Behalf Of Toman_Vojtech@emc.com > Sent: Monday, November 10, 2008 4:17 PM > To: public-xml-processing-model-comments@w3.org > Subject: RE: [closed] Re: Dynamic error for reporting XPath errors > > > > > I may just be blind, but we don't seem to have an error code for > > > reporting problems when an XPath expression fails to > > evaluate (invalid > > > expression, unbound variable, etc.). Or do we have one? > > > > No, I think you're right. I added this paragraph immediately before > > Section 2.6.1: > > > > <para>Irrespective of which version of XPath is used, all > expressions > > evaluated by XProc or passed to steps for evaluation must be > > valid XPath > > expressions. <error code="D0003">It is a > > <glossterm>dynamic error</glossterm> if an XPath expression > > is encountered > > which cannot be evaluated (because it is syntactically > > incorrect, contains > > references to unbound variables or unknown functions, or for > > any other reason). > > </error></para> > > > > Wait, err:XD0003 is already taken by p:viewport ("It is a > dynamic error > if the viewport source does not provide exactly one > document.")! Now the > same error code is used for two different things. > > Vojtech > > >
Received on Thursday, 13 November 2008 17:11:03 UTC