W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > July to September 2007

[Bug 4838] Chameleon <xs:include> behavior

From: <bugzilla@wiggum.w3.org>
Date: Fri, 06 Jul 2007 16:04:15 +0000
CC:
To: www-xml-schema-comments@w3.org
Message-Id: <E1I6qI3-0006Vb-BZ@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4838





------- Comment #2 from paul@sparrow-hawk.org  2007-07-06 16:04 -------
Here is a bug entry against one of my clients products that is related to this:

   If we have this case:

   A.xsd, targetNamespace="ns1"
     - includs B.xsd (a chameleon)
       - imports C.xsd, targetNamespace="ns2"
         - includes D.xsd (a chameleon)
           - contains global type "foo"

   And someting in A or B refers to foo, when we generate the schema,
   the result will put foo into ns1, not into ns2.

I'm pretty sure that this bug against my client's product is related to the
uncertainty that Sandy and Mike K. refer to about what the spec requires.
Received on Friday, 6 July 2007 16:04:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:06 UTC