Re: Possible XSV bug - failure to report namespace errors with import

<snip/>

As in other cases already discussed, XSV does not issue any undefined
(type/element/group) errors wrt a set of schema documents until they
are used to validate an instance.  A switch to force premature closure
and warn of outstanding undefined components is on my 'todo' list.  In
the interim, validating a schema document with XSV does exactly what
that means: confirms or denies that the it is valid per the schema for
schemas, which does _not_ itself express/require/enforce referential
coherence.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/

Received on Friday, 5 January 2001 12:21:06 UTC