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 11218 - behavior of xsi:type underspecified in Element Locally Valid (Complex Type)
Summary: behavior of xsi:type underspecified in Element Locally Valid (Complex Type)
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2010-11-04 14:06 UTC by David Ezell
Modified: 2010-11-26 18:26 UTC (History)
1 user (show)

See Also:

Attachments

Description David Ezell 2010-11-04 14:06:03 UTC 
Validation Rule: Element Locally Valid (Complex Type)
The note after rule 3 is underspecified.  It needs wording to exclude xsi:type similar to wording in rule 2.
Comment 1 C. M. Sperberg-McQueen 2010-11-26 18:13:20 UTC 
In the member-accessible status-quo documents now being uploaded, the note in question now reads:

    Note: It is a consequence that ↑(with few exceptions)↑ each such U 
    will have the matching attribute information item ·attributed to· it 
    by clause 2.1 above. ↑The exceptions are uses of xsi:type and the 
    other attributes named in clause 2.1; no ·attribution· is performed 
    for them.↑

Accordingly, I'm marking this issue Resolved.  But comments and suggestions for improving the wording remain welcome.