[Bug 30063] XSD treatment of Explicit Defaults

https://www.w3.org/Bugs/Public/show_bug.cgi?id=30063

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I'm not sure what point you are trying to make. There's obviously a design
choice between allowing a local element declaration to carry the attribute
value abstract="false", with no other value permitted, or not allowing the
attribute to appear at all. The specification clearly made the choice of not
allowing it to appear. If you're simply saying you would have chosen
differently, then that's nice to know, but it's not going to change anything at
this stage of the game.

I don't see the relevance of the rules in Element Locally Valid (Element),
which say D.{abstract} = false. The spec is talking here about properties of
components in the schema component model, which are only distantly related to
like-named attributes of elements in a schema document.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 15 February 2017 00:08:01 UTC