W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2009

[Bug 8119] defaultAttributes and complexType extension/restriction don't play nice

From: <bugzilla@wiggum.w3.org>
Date: Sat, 31 Oct 2009 00:33:35 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1N41uR-0005EK-5l@wiggum.w3.org>

Michael Kay <mike@saxonica.com> changed:

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

--- Comment #2 from Michael Kay <mike@saxonica.com>  2009-10-31 00:33:34 ---
I'm inclined to agree. Compared with some of the usability problems in 1.0,
like attribute groups being combined by intersection rather than by union, and
content models in a restricted type having to be repeated on the derived type,
this is pretty minor; and it's not clear there's a simple change that would
make life better for everyone. defaultAttributes is a schema-document-wide
default, which makes sense if you want to use the same value on most
declarations in the schema document; if you don't want to use the same value on
most declarations, then you don't have to use it.

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 Saturday, 31 October 2009 00:33:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:10 UTC