W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > April to June 2010

[Bug 9539] Assertion error reporting

From: <bugzilla@jessica.w3.org>
Date: Fri, 23 Apr 2010 16:18:41 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1O5LaT-0007Bt-PD@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9539





--- Comment #6 from Mukul Gandhi <gandhi.mukul@gmail.com>  2010-04-23 16:19:05 ---
(In reply to comment #4)
> I'm inclined to favour putting as an element inside xs:annotation, because (a)
> processors are already required to accept anything there, so it's a
> non-disruptive change; (b) the element can have an xml:lang attribute, (c) the
> message can contain arbitrary markup.

If we allow arbitrary markup for assertions messages, I think it's good, if we
have some guidelines (for example, the spec can say, "the string value of the
error message is, the concatenation of all text node descendants -- in document
order; of the error markup root node"), on how error messages should be
constructed for printing on consoles, or say storing them in string variables,
in programming languages, because that's the most common way, error messages
are utilized. Or perhaps, we can just say, that utilizing the error markup is,
implemented defined.

Regards,
Mukul

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 23 April 2010 16:19:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 April 2010 16:19:08 GMT