- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Wed, 13 Feb 2013 11:52:58 +0000
- To: George Cristian Bina <george@oxygenxml.com>
- Cc: xmlschema-dev@w3.org
George Cristian Bina writes:
> Regarding the lazy component construction my understanding of that was
> that during the schema creation when a module is read it may contain
> references that cannot be be resolved at that time but they should
> still be resolved when all the modules are read.
That's not the way I read it.
> This seems to be also what Saxon and Xerces do as they report an
> error on a schema like:
>
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
> <xs:element name="content">
> <xs:complexType>
> <xs:sequence minOccurs="0">
> <xs:element ref="a"/>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
>
> <xs:element name="test" type="xs:string"/>
> </xs:schema>
>
> even if I validate an instance document that refers only to the "test"
> element:
>
> <test xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:noNamespaceSchemaLocation="m.xsd">
> </test>
XSV is happy with that pair.
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, 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 from me _always_ has a .sig like this -- mail without it is forged spam]
Received on Wednesday, 13 February 2013 11:53:24 UTC