W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2016

[Bug 29658] [SER31] Problem with schema

From: <bugzilla@jessica.w3.org>
Date: Wed, 25 May 2016 10:17:15 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29658-523-pSDUHFC9Ut@http.www.w3.org/Bugs/Public/>

--- Comment #6 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
(In reply to C. M. Sperberg-McQueen from comment #4)
> It looks as if the Microsoft validator is imposing a constraint not defined
> in XSD 1.0, and slightly different from the repair used in XSD 1.1.  If it
> is behaving consistently, it should raise the same error on
> json-node-output-method-type.
It appears to behave consistently, as far as I could see [1].

> The union type QName-or-EQName is not misnamed; the first member is QName;
> it appears as the value of the 'members' attribute, rather than as a child.
Yes, I missed that, thanks.

> IF the WGs decide to change the schema, I think a simple workaround would be
> to move the pattern facet from the member to the union, expanding it to
> handle the enumerated value of xs:token as well:
>    <!--* not tested *-->
>    <snip />
I can confirm that the proposed solution in comment 4 worked (but should be
applied to json-node-output-method-type as well.

> Alternatively, we could declare types
>   - Prefixed-Name (a QName with a colon)
>   - Qualified-EQName (an EQName with a non-empty namespace name)
This appears to work as well.

(line 612, Res.Sch_UnionFromUnion is the error raised).

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 25 May 2016 10:17:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 25 May 2016 10:17:18 UTC