Re: Chameleon includes with no targetNamespace imports

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

1) I think it's a bug that XSV allows an import of the same (=none in
this case) namespace as that of the enclosing schema doc.

2) If it were an include (and it looks like XSV is treating it as
such) then yes, the results would be eligible for chameleon renaming.

3) If it were a legal import, e.g. of a non-null namespace, then the
results would, obviously, not be eligible.

4) The whole logic of import/(chameleon) include/redefine needs to be,
and will be, cleaned up in XML Schema 1.1.

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDHrNQkjnJixAXWBoRAlLgAJ4qb5djrebQxwIRgDNK/3fr8a8q6gCfayDn
5v1Q6NQ1dd6slutLMJl3vHY=
=KAZ4
-----END PGP SIGNATURE-----