[tei-council] <content> vs <mixedContent>

[Lou Burnard]

On 06/10/14 12:05, Sebastian Rahtz wrote:

> Sort of. The user cannot change how <mixedContent> is implemented
> (its content model isn’t relevant here) but they can change their use of it
> i.e. by adding extra *Ref to the mix.

Yes; sorry; I meant of course by changing its <content>, not its content 
model.

>
>> Note also exactly the same uncertainties about what "text" means (for
>> example, are spaces normalised or not?) apply to the @allowText proposal.
> yes. very happy to see that go.
>
> I think you and I _do_ actually agree on where to go:
>
>   * no <textNode> (use macroRef key=“data.text”)
>   * define the “text node” in <mixedContent> to mean 'rng:data tyoe=“string”'

yes. Unless we mean 'rng:text' of course.


>
> I might wonder whether we need a new element to replace macroRef key=“data.*
> so that we can start to deprecate macros, but that’s another matter.

i like it already.