W3C home > Mailing lists > Public > xmlschema-dev@w3.org > January 2006

RE: xs:choice and xs:sequence question

From: Stan Kitsis <skits@microsoft.com>
Date: Thu, 12 Jan 2006 14:02:31 -0800
Message-ID: <2967212019EB7B4D990E06E1AC2F2319060683EC@RED-MSG-60.redmond.corp.microsoft.com>
To: "George Cristian Bina" <george@oxygenxml.com>, "Michael Kay" <mike@saxonica.com>
Cc: <d_a_carver@yahoo.com>, <xmlschema-dev@w3.org>

I think that most users won't even bother looking at the spec.  However
for those who want to figure out what's going on (as in George's
example), a handy reference can save time.


Stan Kitsis, 
Webdata - XML
Microsoft Corporation

-----Original Message-----
From: xmlschema-dev-request@w3.org [mailto:xmlschema-dev-request@w3.org]
On Behalf Of George Cristian Bina
Sent: Thursday, January 12, 2006 10:51 AM
To: Michael Kay
Cc: d_a_carver@yahoo.com; xmlschema-dev@w3.org
Subject: Re: xs:choice and xs:sequence question

Hi Mike,

I do not see reportig the place of the error in the XML Schema spec and 
formulating a good error message as excluding each other. I agree that 
some parts of the specification are not easy to read, however this is 
not a subtitution of the error message, it is an enhancement to that.

I find this useful especially when people say: well that schema engine 
reports that my schema is valid while Xerces[1] or oXygen reports this 
error. Pointing to the schema specification saves a lot of time as you 
have immediatelly access to the place in the specification that is 
related with the error. If it is difficult to read that it is a lot more

difficult to take the whole schema specification and first look for the 
place related to the error and then read that.

[1] oXygen uses currently Xerces 2.7.1 for validating XML schema files. 
In the next release we added the possibility to use most of the XML 
Schema processors: Saxon SA, XSV, MSXML 4.0 and .NET, LIBXML, IBM SQC.

Best Regards,
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger

Michael Kay wrote:
>>oXygen reports the error with a link to the specification 
>>related with that:
> A tangential remark: I wonder how useful this is? I know Appendix C
> that validity errors "should" be reported citing the chapter and verse
> the spec, but is there really any serious prospect that the average
> author will get any value from this? Your link points to the sentence:
> "A content model must be formed such that during .validation. of an
> information item sequence, the particle component contained directly,
> indirectly or .implicitly. therein with which to attempt to .validate.
> item in the sequence in turn can be uniquely determined without
> the content or attributes of that item, and without any information
> the items in the remainder of the sequence."
> I suspect most users can't even parse the syntax of this sentence, let
> understand what it means.
> I decided in Saxon that there wasn't any point in referring people to
> spec, and instead try to explain what's wrong in my own words. In this
> you will get a message to the effect: "the content model is ambiguous,
> <elementname> appears in more than one place".
> Any views on this from users?
> Michael Kay
> http://www.saxonica.com/
Received on Thursday, 12 January 2006 22:03:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:15:32 UTC