- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Thu, 10 Mar 2011 21:44:17 +0000
- To: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>
- Cc: www-xml-schema-comments@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
C. M. Sperberg-McQueen writes:
> But perhaps I was conflating the description of include with
> that of import: the spec is clear that the schemaLocation
> of an xsd:include must point to an xsd:schema element in
> an infoset and not to some other representation of a
> schema. (If I understand correctly, it is not required that
> schemaLocation point to an XML document; it is allowed
> instead to point to some vendor-specific representation of
> an infoset -- JSON, perhaps, or EXI, or a proprietary binary
> dump format. That may have led me to overlook the fact
> that the target of schemaLocation must be a schema
> document, not a schema, as those terms are defined
> by the XSD spec.)
I think that's all correct -- and rolling import in with include in my
document was probably a mistake.
ht
- --
Henry S. Thompson, School of Informatics, University of Edinburgh
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 from me _always_ has a .sig like this -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFNeUYxkjnJixAXWBoRApMPAJ4iiaStMk60NNdMTp+rgpvnOsnDaACePA8v
cc5kJqx5X8g9HaUpc2EyYKs=
=WEUn
-----END PGP SIGNATURE-----
Received on Thursday, 10 March 2011 21:45:06 UTC