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

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

Michael Kay writes:

> I suspect, but without testing(!) that the strategy can be extended to
> xs:redefine as follows:
>
> (a) if redefinition for a namespace is required, create a new schema
> document with that targetNamespace that invokes the (previous) primary
> schema document for that namespace using xs:redefine, and contains all the
> redefinitions needed.
>
> (b) change the driver document to refer to the redefinition documents
> introduced in step (1) in place of the (previous) primary shcema documents.

Yes, that sounds right.

> A similar approach might also work reliably for "chameleon include".

Includes in general are less problematic, as there is no option for
processors -- they _must_ process the nominated schema document.

> But better advice is not to use redefine or chameleon include.

Hmmm -- let's leave redefine aside, as we've agreed to differ on that
before, but I'm surprised you recommend against chameleon include.  I
find it hugely useful (for those little bits that you use all the time
but aren't worth putting in a namespace) and am not aware of any
interop problems with it. . .

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)

iD8DBQFK04WokjnJixAXWBoRAsvbAJ9nerp4yckxN4iPts1pBBDyZvyalgCaAzfm
mGqLLD1JN8IMkIsAynGy96k=
=Ot+l
-----END PGP SIGNATURE-----

Received on Monday, 12 October 2009 19:38:48 UTC