Re: Redefine and Import used together - is this valid?

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

Danny Vint writes:

> I have the following situation:
>
> 1) Base industry standard schema (ACORD)
> 2) A schema that imports the ACORD schema (to reuse data types and
> some elements) that defines my organizations new elements and
> aggregates (ACME)
> 3) A schema that redefines #1 ACORD to modify existing elements and
> aggregates to include my new ACME elements.
>
> I then have a docuemnt instance the references #3.
>
> Xerces and XSV say my document and schemas are valid.

XSV accepts your package because it never processes a namespaced
schema document more than once if it can avoid it, so the nested,
potentially problematic, import in (2), does not cause a problem
because the ACORD schema document has already been processed (during
the processing of (3), so the 'schemaLocation' of the import in (2) is
ignored).

This is conformant behaviour, because the REC says that
'schemaLocation' on <xs:import> is a hint, which need not be followed.

But it's not _required_ behaviour, for better or worse.

I'd like to see a way for users to mandate such behaviour. . .

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)

iD8DBQFFD9YxkjnJixAXWBoRAhs3AJ4u9n2bQD/1nkYbP4YcnZ2PE9IXxgCeO4CY
FiqsAOh2YY5s2Dfk/Y3uq1A=
=3fsp
-----END PGP SIGNATURE-----