Re: A complex type cannot be a restriction of a simpleType ??

"Arnaud Blandin" <blandin@intalio.com> writes:

> 
> I think I would drop you a note on the Castor behavior:
> 
> Castor is right (please tell me here if I am wrong) since the schema is
> missing an explicit targetNamespace so Castor assumes that the
> targetNamespace is going to be http://www.w3.org/2001/XMLSchema and thus
> when resolving 'ID', it will find {http://www.w3.org/2001/XMLSchema}ID
> which is a simpleType. Thus an exception is thrown.

Nope -- no targetNamespace means the definitions and declarations are
for names in no known namespace.  There's also no default namespace
declaration, so unprefixed references, such as base='ID' and
base='element', are also to names in no known namespace, so the ID
refered to is indeed the ID defined in the schema document Ted Toth
sent.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2002, 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/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

Received on Tuesday, 8 October 2002 04:10:34 UTC