Re: import a schema that is not guaranteed to exist

Your best bet is to remove the schemaLocation from your import in
schema1 altogether.  That will make schema1 always valid as it stands.
Then use whatever environmental mechanism your validator provides to
supply schema2 or schema3, as appropriate.

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@cogsci.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]

Received on Friday, 28 February 2003 05:42:20 UTC