Kasimier Buchcik <kbuchcik@4...> writes:

> One obvious example would be a scenario where an element "E"
> is validated against a lax wildcard; at this point no declaration for
> the element "E" exists, thus the element seems valid. A descendant
> element imports an additional schema via xsi. This schema contains an
> element declaration "DE" for "E", which -  if it would have been
> available - would have identified the element "E" as invalid. So this
> way the validation would differ from the schemata being computed all
> at validation begin.

This is actually an error [1]:

  4. xsi:schemaLocation and xsi:noNamespaceSchemaLocation [attributes]
     can occur on any element. However, it is an error if such an
     attribute occurs after the first appearance of an element or
     attribute information item within an element information item
     initially *validated* whose [namespace name] it addresses.

This error is intended to 'protect' streaming validators from giving
a different answer in this pathological case.

ht

[1] http://www.w3.org/TR/xmlschema-1/#schema-loc
-- 
 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@i...
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]

From ht@i... Mon Mar 14 08:42:11 2005
Received: from lisa.w3.o