This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4066 - wildZ010 - no permitted namespaces
Summary: wildZ010 - no permitted namespaces
Status: RESOLVED FIXED
Alias: None
Product: XML Schema Test Suite
Classification: Unclassified
Component: Microsoft tests (show other bugs)
Version: 2006-11-06
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Henry S. Thompson
QA Contact: XML Schema Test Suite mailing list
URL:
Whiteboard: metadata updated 2009-01-15
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-10 23:45 UTC by Michael Kay
Modified: 2009-01-15 14:39 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2006-12-10 23:45:42 UTC
In the Microsoft Wildcard test set, test group wildZ010 uses a schema containing

<xsd:any namespace="" processContents="strict"/>

My reading of the specification is that this represents a wildcard whose {namespace constraint} is an empty set of namespaces, and which therefore cannot be matched by any element.

It follows that the instance document wildZ010.xml is invalid, yet the test metadata describes it as valid.
Comment 1 Zafar Abbas 2007-01-22 22:15:21 UTC
A namespace attribute on a wildcard without a value is not of much use, the Microsoft test interprets it the same as as not having the namespace attribute at all and default it to ##any.
Comment 2 Michael Kay 2008-06-22 15:10:03 UTC
Agreed that the spec is clear that this wildcard matches nothing, and the instance is therefore invalid. The test will be changed accordingly.