- From: <bugzilla@jessica.w3.org>
- Date: Wed, 25 May 2016 10:17:15 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29658 --- 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. [1] https://github.com/Microsoft/referencesource/blob/d925d870f3cb3f6acdb14e71522ece7054e2233b/System.Xml/System/Xml/Schema/SchemaSetCompiler.cs (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