2067 2005-09-09 02:58:02 +0000 Issue to do with identity constraints and chameleon include 2009-04-21 19:21:32 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only All All CLOSED FIXED medium, work, idc cluster resolved P3 normal --- 1 sandygao cmsmcq www-xml-schema-comments oldest_to_newest 5947 0 sandygao 2005-09-09 02:58:02 +0000 An XPath expression that selects elements or attributes in a particular namespace must use prefixes associated with that namespace. If you want to use identity constraints in a chameleon schema, then, the XPath expression must be modified to use prefixes which are associated with the target namespace of the including schema. See: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001OctDec/0047.html This is originally an issue against XML Schema 1.0. See bug 2066. 15325 1 ht 2007-06-08 13:56:40 +0000 The WG resolved to accept http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b2067.200701.htm as a resolution of this issue at its f2f in February of 2007 (http://www.w3.org/XML/Group/2007/01/xml-schema-ftf-minutes#friam.2067) 15644 2 David_E3 2007-06-27 12:50:21 +0000 At the June 2007 f2f: Based on the decisions in 4419, Sandy volunteered to prepare a wording proposal that brings 2067 resolutions into alignment with 4419. This follows a request (in March) from MSM to reopen the issue since actual consensus on this issue has been hard to prove until now. 15897 3 cmsmcq 2007-07-20 19:29:03 +0000 The proposal mentioned in comment #2 (http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b2067-2.200707.html) [member-only link] was discussed and approved at today's WG telcon. It resolves this issue, which I am marking accordingly. As quasi-originator of the bug report, Jeni Tennison should be notified and asked whether this resolves her issue; this has not yet been done. 20274 4 cmsmcq 2008-05-27 03:50:49 +0000 At http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008May/0033.html (member-only link), Sandy Gao points out a problem. We changed how chameleon include works as part of 2067, but there seems to be a problem: unqualified QName references are *not* updated to point to the renamed components so they will all become dangling. (The only exceptions are the XPaths, where we allow an xpathDefaultNamespace attribute with a ##targetNamespace value.) Michael Kay proposes a solution later in the same thread. I'm reopening this issue to ensure that this gets tracked. 20302 5 cmsmcq 2008-05-29 06:53:39 +0000 A wording proposal intended to resolve this issue is at http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b4767.html (member-only link). The 2067- and 4767-related parts are intertwined, but not hopelessly; if necessary the WG can take separate action on the two issues. 20408 6 cmsmcq 2008-06-07 01:29:27 +0000 The proposal mentioned in comment #5 was adopted by the WG at today's meeting. Sandy, as the originator (and re-opener) of the issue, please indicate by closing or reopening the issue whether you are satisfied with the resolution.