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 15854 - Skip wildcards not valid in complex types with implicit complex content
Summary: Skip wildcards not valid in complex types with implicit complex content
Status: NEW
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: needsAgreement
Depends on:
Blocks:
 
Reported: 2012-02-02 11:37 UTC by Andreas Meissl
Modified: 2012-02-03 16:58 UTC (History)
1 user (show)

See Also:


Attachments

Description Andreas Meissl 2012-02-02 11:37:00 UTC
I'm not sure if I'm wright with my interpretation of clause 3 of derivation-ok-restriction. In special the following sentence:

"...and for every attribute information item A in E.[attributes], B's default binding for A subsumes that defined by T."

As I read it the following complex type is invalid:

<xs:complexType name="T">
   <xs:anyAttribute namespace="##any" processContents="skip"/>
</xs:complexType>

In this case the base type definition B would be xs:anyType and T would be the complex type T. The default binding for any potential attribute information item would be skip for T and lax for B (xs:anyType has a lax attribute wildcard). So B's default binding for A (lax) will not subsume T's default binding for A (skip).
Comment 1 David Ezell 2012-02-03 16:58:53 UTC
WG agrees that clause 4.3 of XML Schema 1.0 2e did handle this situation. We are researching the change history to find the motivation for the change.

See: RQ17a1, adopted 8 December 2006.