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

Re: 2.6.1.1, error code not defined

From: Dave Pawson <dave.pawson@gmail.com>
Date: Thu, 5 Feb 2009 13:07:53 +0000
Message-ID: <711a73df0902050507n35a0a0c8l7e325d986055fed2@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: public-xml-processing-model-comments@w3.org

2009/2/5 Norman Walsh <ndw@nwalsh.com>:
> "Dave Pawson" <dave.pawson@gmail.com> writes:
>
>> 2008/12/15  <Toman_Vojtech@emc.com>:
>>>
>>>> An option that has neither a specified value nor a default value will
>>>> not appear as an in-scope variable. Consequently, an attempt to refer
>>>> to that variable will raise an error.
>>>>
>>>> Mostly the CR defines the error code when first mentioned. Not done in
>>>> this case?
>>>> XS0010?
>>>> XS0018?
>>>> XS0031?
>>>>
>>>
>>> This one is covered by dynamic error err:XD0023:
>>
>> How about adding that to the text of the CR to make
>> it explicit which error should be reported, as has been done
>> elsewhere.
>
> It's in the last paragraph of the ancestor section. I'm not sure repeating
> it in a note is going to be the least confusing thing.

OK, consistent approach I guess was my request.
I'll leave it to you to decide.

regards




-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
Received on Thursday, 5 February 2009 13:08:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 February 2009 13:08:28 GMT