Re: restricting anySimpleType in complexType definition

You and Mark have ended up at the same, correct, place.  The WG
decided not to provide shorthand for combinations of derivation steps
that could easily be done separately, so what you have is the best
you can get.  And I think it's perfectly OK as you have it, why fuss
over saving three or four lines?

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 Monday, 17 June 2002 17:44:46 UTC