- From: <bugzilla@farnsworth.w3.org>
- Date: Tue, 27 May 2008 03:50:49 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2067 cmsmcq@w3.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #4 from cmsmcq@w3.org 2008-05-27 03:50 ------- 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.
Received on Tuesday, 27 May 2008 03:51:28 UTC