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

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

> This is actually a bit confusing, but I think I finally have my head around
> it (I certainly didn't two days ago).
> 
> If one looks at Section 4.3.3 of Part 1, the description of the {content
> type} deserialization rules discusses the EXPLICIT PARTICLE that is
> introduced as a parent of most complex type content models. To paraphrase,
> unless the complexType's content model is a lone all, group, sequence, or
> choice, the model is interpreted as if a compositor has been introduced. In
> the case of content='mixed', it is a choice compositor marked
> minOccurs='0'/maxOccurs='unbounded'.
> 
> That stated, I believe (but may be wrong) that the following:
> 
> <complexType name='bob' content='mixed' >
> 	<element name='a'/>
> 	<element name='b'/>
> 	<element name='c'/>
> </complexType>
> 
> is equivalent to:
> 
> <complexType name='bob' content='mixed' >
>  <choice minOccurs='0' maxOccurs='unbounded' >
> 	<element name='a'/>
> 	<element name='b'/>
> 	<element name='c'/>
>  </choice>
> </complexType>
> 
> This is pretty much the DTD story. If one really wants the "revolutionary
> structured mixed content model" that acts like elementOnly but allows
> non-whitespace character data, one would have needed to write this:
> 
> <complexType name='bob' content='mixed' >
>  <sequence minOccurs='m' maxOccurs='n' >
> 	<element name='a'/>
> 	<element name='b'/>
> 	<element name='c'/>
>  </sequence>
> </complexType>
> 
> where m and n are the values that match your expectations ;-)

The above analysis is entirely correct, as far as I can tell.

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:32:18 UTC