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

Re: 2.6.1.1, error code not defined

From: Dave Pawson <dave.pawson@gmail.com>
Date: Mon, 15 Dec 2008 11:09:09 +0000
Message-ID: <711a73df0812150309t1d541ee5md4023dfb836b32d3@mail.gmail.com>
To: public-xml-processing-model-comments@w3.org

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.

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
Received on Monday, 15 December 2008 11:09:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 15 December 2008 11:09:44 GMT