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

Re: determining an xproc extension attributes

From: mozer <xmlizer@gmail.com>
Date: Mon, 1 Sep 2008 18:08:35 +0200
Message-ID: <21d9ade60809010908s74c32d86s7e0c2a8bb41cfd9e@mail.gmail.com>
To: "James Fuller" <james.fuller.2007@gmail.com>
Cc: public-xml-processing-model-comments@w3.org

James,

3.9 says

If you have an <p:option foo="donut"/>, then it's an XS0008 because
foo is not a valid attribute of p:option
but 3.9 do also say that <p:option my:foo="ombra"
xmlns:my="http://foo"/> is not an XS0008 error

and 3.8 says for the same example that you should consider the previous as
<p:option /> (that is by ignoring the attribute in a foreign namespace)


On Mon, Sep 1, 2008 at 4:41 PM, James Fuller
<james.fuller.2007@gmail.com> wrote:
>
> in section 3.9 Syntax Summaries it states;
>
> 'It is a static error (err:XS0008) if any element in the XProc
> namespace has attributes not defined by this specification unless they
> are extension attributes.
> '
> then in section 3.8 Extension attributes it says;
>
> 'A processor which encounters an extension attribute that it does not
> recognize must behave as if the attribute was not present.'
>
> Both of these statements seem to create a contradiction.
>
> How can a processor 'know' it is not recognizing an unknown extension
> attribute ?
>
> J
>
>
Received on Monday, 1 September 2008 16:09:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:41:08 UTC