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

[Bug 6166] Schema Component Model for Wildcards

From: <bugzilla@wiggum.w3.org>
Date: Fri, 17 Oct 2008 18:59:27 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1KquXn-0005Cb-4w@farnsworth.w3.org>


--- Comment #1 from Sandy Gao <sandygao@ca.ibm.com>  2008-10-17 18:59:26 ---
<xs:anyAttribute notNamespace=""/>

is currently not allowed, as it will not pass bullet 2 of " Wildcard
Properties Correct":

"2 If {variety} is not, {namespaces} has at least one member."

Agree that 2 variety values (or 2 properties) would work and certain things can
be simplified, but

- Mapping <xs:anyAttribute namespace="##all"/> to "not + {}" or
"disallowedNamespaces={}" could also be counter-intuitive to readers.
- API compatibility. Schema model APIs that support schema 1.0 probably already
defined a method like getVariety() on wildcards and people would expect ANY

The API concern is related to the implementation discussion in the bug report.
If the implementation doesn't intend to expose a schema model API, then it can
choose to have 2 variety values internally. If it does expose such an API, then
it probably already does so for schema 1.0 and would be concerned about

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 Friday, 17 October 2008 18:59:35 UTC

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