[tei-council] <mixedContent> content (was "Re: <content> vs <mixedContent>")

[Syd Bauman]

I just actually looked at the mixedContent elementSpec, and found the
following content model:

  <content>
    <rng:oneOrMore>
      <rng:choice>
      <rng:ref name="elementRef"/>
      <rng:ref name="classRef"/>
      </rng:choice>
    </rng:oneOrMore>
  </content> 

I wonder if we don't mean

    <content>
      <rng:zeroOrMore>
        <rng:choice>
          <rng:element name="text">
            <rng:empty/>
          </rng:element>
          <rng:ref name="elementRef"/>
          <rng:ref name="classRef"/>
        </rng:choice>
      </rng:zeroOrMore>
    </content>

Otherwise the ODD processor is going to have to do "magic" akin to
what we used to do with att.global in order to insert the reference to
the PCDATA. (Also, this makes it very clear to an ODD-writer who uses
mixed content that text nodes will be validated by matching against
the RELAX NG <text/> pattern, not the RELAX NG "string" datatype, nor
the RELAX NG "token" datatype, nor the W3C Schema "string" datatype,
nor the W3C Schema "token" datatype.)