Thank you.  That confirms what I thought. Unfortunately, the element in
question is global, with no containing parent other than xs:schema, and
is defined by an anonymous complex type- not a design choice I would
have made had I designed the original schema.  Or at least not now that
I have first hand experience of its implications.

-----Original Message-----
From: Henry S. Thompson [mailto:ht@i...] 
Sent: Friday, October 07, 2005 2:34 AM
To: Grimaldi, Linda L.
Cc: xmlschema-dev@w...
Subject: Re: Advice, please: Restricting wild cards in anonymous types

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Grimaldi, Linda L. writes:

> I am working with a "standard" schema that allows <xs:any,
> namespace="##other" ... in its complex types.  The problem I am =
having
> is that, since the complex types are anonymous, I don't seem to be
able
> to restrict (or extend) them in the usual way.  Is there any way
around
> this issue, some other way to restrict the xs:any to a specific
element
> that is local to my own namespace?

Named or not, the only way to _change_ what the content model of the
containing element allows is by redefining a type -- in your case, the
first named type definition which itself contains the element
declaration with the anonymous type definition.

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@i...
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged
spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDRjLvkjnJixAXWBoRAtA3AJ9+nb7jVwYuVTVn1Oic+UcbdPedhACfegy/
IyN4eIc2ZSuxEgBkcNjI6nU=
=gUB3
-----END PGP SIGNATURE-----

From vincent@h... Fri Oct 07 14:10:06 2005
Received: from wiggum.w3.org