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:35:29 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1O5Lqj-0007a9-5y@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9539





--- Comment #7 from Mukul Gandhi <gandhi.mukul@gmail.com>  2010-04-23 16:35:53 ---
(In reply to comment #5)
> I agree with Michael's Comment #4, but can we call it xs:errorMessage rather
> than just xs:message as I feel the former is less ambiguous.
> 
> (And I don't think we need xs:errorMessage to go inside xs:appinfo. i.e. we
> have:
>    <xs:annotation>
>         <xs:errorMessage>
>            error message ...
>         </xs:errorMessage>
>    </xs:annotation>
> )

I think, we would need to have an error message in either <appinfo> or the,
<documentation> tag of, <annotation>.

I think, the grammar of <annotation> could make this evident (as shown, below):

<annotation
  id = ID
  {any attributes with non-schema namespace . . .}>
  Content: (appinfo | documentation)*
</annotation>

The <appinfo> tag, looks a more appropriate place to me, to write the
assertions error message.

Regarding, <xs:errorMessage> I think the spec could say:
If implementing an error markup in, annotation of an assertion, there should be
only one <xs:errorMessage> element within, 'appinfo' tag of 'annotation'. Any
following siblings, of the first xs:errorMessage tag, should be discarded by
the XSD 1.1 processors, for the purpose of assertions error message,
construction.

These are some quick thoughts, from me. The exact wordings of this subject,
could be rephrased by the WG.     


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:35:54 GMT

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