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 5779 - QName resolution and xs:import
Summary: QName resolution and xs:import
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0/1.1 both
Hardware: PC Windows NT
: P2 normal
Target Milestone: CR
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2008-06-21 15:52 UTC by Michael Kay
Modified: 2009-04-20 22:20 UTC (History)
2 users (show)

See Also:


Attachments

Description Michael Kay 2008-06-21 15:52:10 UTC
This results from consideration of test suite bug #4057.

It is felt that the spec could be clearer in saying that when a QName in a schema document is intended to refer to a schema component in another namespace, then it's an error (violates a schema representation constraint) if there is no xs:import for that namespace, and this doesn't fall within the cases where unresolved QNames can be resolved later, or where schemas with unresolved QNames can be used provided the referenced component isn't needed.
Comment 1 C. M. Sperberg-McQueen 2008-07-18 16:31:05 UTC
Discussed at the 17 July 2008 telcon.  Yes, this should be 
clarified.
Comment 2 C. M. Sperberg-McQueen 2009-04-13 00:21:12 UTC
A wording proposal intended to resolve this issue is at 

  http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b5779.html
  (member-only link)

I'm marking the issue needs-review, accordingly.
Comment 3 David Ezell 2009-04-17 16:51:52 UTC
5779: QName resolution and xs:import
http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b5779.html


Summary: bug report requests clarification of rules regarding
schema documents which refer to other namespaces without
importing them.

MSM's recommendation: not complicated but should be reviewed
before adoption.

Comment 4 Sandy Gao 2009-04-20 21:29:21 UTC
During its 2009-04-17 telecon, the schema WG adopted the proposal in comment #2 to address this issue.

With this change, the WG believes that the issue raised in this bug report is addressed. I'm marking this RESOLVED accordingly.

Michael, if you would indicate your concurrence with or dissent from the WG's disposition of the comment by closing or reopening the issue, we'll be grateful. If we don't hear from you in the next two weeks, we'll assume that silence implies consent.