Re: [Bug 9539] Assertion error reporting

Hi Pete,
    I rethought over the error message reporting for assertions. I
believe, the WG should not make this feature (i.e, providing a syntax,
for assertions error reporting) mandatory in the XSD 1.1 language.
This will make, assertions instruction consistent, with all other XSD
instructions (like, say simpleType/complexType/element & all others).

But the XSD 1.1 spec, could provide guidelines to implementors,
perhaps along following lines:
<details>
It is strongly encouraged, that implementers should provide a
mechanism to schema authors, a means to provide user-defined error
message, for assertions failure. If implementations, provide a means
to specify error message for assertions failure, then how
implementations accomplish this, is "implementation defined". The
possible suggested means to do this, are to specify, assertions error
message in the assertions 'annotation' or via a processor specific,
assertions attribute like, "message" (in a non-schema namespace).

A custom error message by schema authors, for assertions failure,
encourages less-verbose and domain specific error messages.

If implementations, do not provide a means to schema authors to
override, the processor specific error messages, then assertions error
reporting by implementations is, "implementation defined".
</details>

On Mon, Apr 26, 2010 at 3:38 PM, Pete Cordell <petexmldev@codalogic.com> wrote:
> Hi Mukul,
>
> As we are working on a new version I don't believe we have to be restricted
> by the constraints of the existing 1.0 syntax.  I'm sure I'll be put right
> if that's not the case!
>
> Regards,
>
> Pete Cordell
> Codalogic Ltd
> Interface XML to C++ the easy way using XML C++
> data binding to convert XSD schemas to C++ classes.
> Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
> for more info



-- 
Regards,
Mukul Gandhi

Received on Monday, 26 April 2010 11:56:44 UTC