This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This issue was originally reported by Xan Gregg. Give a complete and formal definition of schema composition, and use it for currently defined (e.g. include) and currently undefined (e.g. schema docs on command line) cases. See http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Jun/0058.html (http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Jun/0058.html). This item was classified as Req in the meeting of 2004-06-10 (http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Jun/0120.html). This topic has been discussed at some length and working papers have been prepared for the WG both by Noah Mendelsohn and by Michael Sperberg-McQueen. Following our discussion at the 2005 Technical Plenary, MSM was asked to prepare a new proposal. His plan is first to outline a notation for describing the XML mappings (following on from NM's proposal presented in January 2005). That notation should make it easier to have clearer discussions of identity conditions on components; once the identity conditions on components are clearer, the core of this requirement can be addressed more readily.
The working papers mentioned in the description are currently member-only (alas), but for those with member access the following URIs should be of interest: XML Schema Composition: An attempt to clearly set out our current design (Noah Mendelsohn, June 2004). http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Jul/att-0004/CompositionArchitecture.html Notes on RQ-151 (C. M. Sperberg-McQueen, July and November 2004): http://www.w3.org/2004/07/msm/rq-151.notes.html Branch draft of Structures (diffed) showing possible changes (Noah Mendelsohn, January 2005). http://www.w3.org/XML/Group/2004/06/xmlschema-1/structuresNoahCompositionDiffs.html (See also http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2005Jan/0001.html for pointers to other forms of the branch draft and auxiliary material.)
On its telcon today, the Working Group discussed this and other issues related to schema composition and concluded (not without some pangs of regret) that for scheduling reasons it is not feasible for us to resolve them before we go to Last Call. The WG continues to believe that this issue is important and should be resolved; our decision to close the issue for now reflects the fact that we have not been able to reach consensus on how to resolve the problems related to composition, coupled with the observation that for the most part, users are able to avoid the problems by avoiding problematic constructs in their schema documents. The cost of delaying XSDL 1.1 for these issues is thus high, while the practical benefit for users is not as high as it might be. The Working Group continues to hope that this issue can be resolved at some point in the future. Accordingly I am closing this issue with a disposition of LATER.
*** Bug 5374 has been marked as a duplicate of this bug. ***