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

Re:, error code not defined

From: Norman Walsh <ndw@nwalsh.com>
Date: Thu, 05 Feb 2009 07:39:19 -0500
To: public-xml-processing-model-comments@w3.org
Message-ID: <m2ocxhoy6g.fsf@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.

                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | A man is not necessarily intelligent
http://nwalsh.com/            | because he has plenty of ideas, any
                              | more than he is a good general because
                              | he has plenty of soldiers.-- Chamfort

Received on Thursday, 5 February 2009 12:40:13 UTC

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