=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What you have is a classic case of a complex content model restricting
a starred wildcard, which is allowed, but only via a pretty obscure
route through the REC [1].  MS validators used to have a problem with
this but I think that got fixed some time back.  

What validator are you using?

ht

[1] http://lists.w3.org/Archives/Public/xmlschema-dev/2003Oct/0026
=2D -- 
 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 sp=
am]
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDEuYAkjnJixAXWBoRAtEIAKCEEdA/CylfYq18SuU8sDVh9YrMnACfS9Gx
pfF2tqq0+vMveG9LVjsJgBg=
=EYb9
=2D----END PGP SIGNATURE-----

From kevin.cobb@e... Tue Aug 30 02:30:39 2005
Received: from