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 4390 - What happens when attribute wildcard union is not expressible
Summary: What happens when attribute wildcard union is not expressible
Status: NEW
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0 only
Hardware: All Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-13 14:58 UTC by Sandy Gao
Modified: 2012-12-04 00:51 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2007-03-13 14:58:12 UTC
Section 3.4.2 talks about the need to union (and intersec) attribute wildcards in complex type extension; section 3.10.6 talks about how attribute wildcards are unioned (and intersected) and mentions the possibility for the result not to be expressible; section 3.4.3 indicates it's an error for the result of "intersection" not to be expressible.

But nowhere in the spec talks about what happens when the union is not expressible.

A clause 5 is probably in order for 3.4.3:

"5 If clause 3.2.2.1.2 in the correspondence specification above for {attribute wildcard} is satisfied, the intensional union must be expressible, as defined in Attribute Wildcard Union (ยง3.10.6)."