- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 16 Oct 2008 10:09:58 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6166 Summary: Schema Component Model for Wildcards Product: XML Schema Version: 1.1 only Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: Structures: XSD Part 1 AssignedTo: cmsmcq@w3.org ReportedBy: mike@saxonica.com QAContact: www-xml-schema-comments@w3.org The declarations <xs:anyAttribute/> and <xs:anyAttribute notNamespace=""/> are to all intents and purposes equivalent; both allow any attribute in any namespace. Yet the schema component model maintains a distinction between them. It provides three {variety}s of Namespace Constraint where two would be sufficient; it is not necessary to provide the option {variety}="any" because it is equivalent to {variety}="not" with {namespaces} equal to the empty set. Having three varieties where two would do unnecessarily complicates the rules for wildcard validation, subsets, union, and intersection. It also unnecessarily complicates an implementation, because an implementation that exposes the schema component model is required to maintain this meaningless distinction. Note: I think it would also ease the exposition of these algorithms if the Namespace Constraint had two properties, {allowedNamespaces} and {disallowedNamespaces}, with a rule that one of them must be empty; one could then dispense with {variety}. -- 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 Thursday, 16 October 2008 10:10:15 UTC