Re: Escalation mechanism for different interpretation of W3C XML-Schema specification ?

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

Michael Kay writes:

>> ...  I think this probably means that I would have to augment my 
>> list of schema document abstraction to actually make it a 
>> list of (schemadoc, targetNamespace) pairs, 
>
> That's precisely what I do in my implementation.

And what XSV does -- it is necessary to do this to ensure multiple
chameleon includes into different namespaces works properly.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, 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)

iD8DBQFK3DofkjnJixAXWBoRAmnlAJ9I6XnNvI5W6qSgTPvVOqzLg84aWgCfbYYy
lXbIHxYFMPnudei1X12a7IQ=
=F8lC
-----END PGP SIGNATURE-----