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

Re: Detecting errors

From: Josh Matthews <joshmatthews@gmail.com>
Date: Thu, 9 Oct 2008 13:11:09 -0400
Message-ID: <ffee23380810091011i180c507alfc4bd690e47677f7@mail.gmail.com>
To: "Norman Walsh" <ndw@nwalsh.com>
Cc: public-xml-processing-model-comments@w3.org
On Thu, Oct 9, 2008 at 8:14 AM, Norman Walsh <ndw@nwalsh.com> wrote:

> Consider the following pipeline:
>
> <p:declare-step name="main" ...>
>  <p:input port="source"/>
>  <p:output port="source"/>
>
>  <p:declare-step type="px:unused">
>    <p:input port="source"/>
>    <p:output port="source"/>
>    <px:undeclared/>
>  </p:declarestep>
>
>  <p:identity/>
> </p:declare-step>
>
> (a) Does this pipeline contain an error?
> (b) Are implementations allowed to report it?
> (c) Are implementations required to report it?
>

I think the answer to both is no. There is no static error that can catch
this, and the only dynamic error that comes close is XD0017 ("It is a
dynamic error if the running pipeline attempts to invoke a step which the
processor does not know how to perform."). In this case, however, the
running pipeline does not attempt to invoke the declared step that contains
the undeclared step (I assume that is what you intended by naming the step
"px:unused") - so no error occurs.

There is no error to report, so it is not required nor allowed.

Cheers,
Josh Matthews
Received on Thursday, 9 October 2008 17:11:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:25 UTC