Re: Schema for XSLT (concerns mixed content, content attribute)

"Box, Don" <dbox@develop.com> writes:

> Yeah, I thought about alternative ways to model that. One way would have
> been to use a named model group (that was my first pass btw). The problem is
> that for mixed content, you can't use sequence constraints. This is a
> problem with older technologies as well.

Yes you can -- the whole point of making 'mixed' orthogonal to the
content model is that e.g.

  <xs:complexType name='haystack' content='mixed'>
   <xs:sequence>
     <xs:element name='thread'/>
     <xs:element name='needle'/>
   </xs:sequence>
  </xs:complexType>

schema-validates _only_ <haystack> elements with exactly one <thread>
and one <needle> daughters, _in that order_.

Yet another reason to think again about the default <choice> wrapper
when you simply say

  <xs:complexType content='mixed'>
   <xs:element .../>
   . . .
  </xs:complexType>

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, 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/

Received on Thursday, 20 April 2000 12:25:25 UTC