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

Martin Holmes mholmes at uvic.ca
Fri Oct 3 15:48:53 EDT 2014


On 14-10-03 12:25 PM, Sebastian Rahtz wrote:
>
> On 3 Oct 2014, at 20:15, Lou Burnard <lou.burnard at retired.ox.ac.uk> wrote:
>> The point I was trying to make is that assming <bar> has a content model
>> like
>> <sequence><textNode/><elementRef key="foo"/></sequence>
>>
>> it can be satisfied by either of the following
>> <bar> stuff <foo/></bar>
>> or
>> <bar><foo/></bar>
>>
>>   because a <textNode> can always match nothing.
>
> hmm.  we can do enforce non-empty text nodes in the implementation, with (e.g.)
>
>    <data type="string">
> 	<param name="pattern">.+</param>
>    </data>

Dot doesn't typically match linebreaks, but it does match other spaces, 
so pretty-printing artifacts would satisfy this.

> I am now wondering whether our <textNode/> is actually needed.
> Why are we not doing <macroRef key=“data.text”/> in these
> circumstances? or was I asleep when we discussed that in the
> summer?

What's the practical difference between <rng:text> and <macroRef 
key=“data.text”/>?

Cheers,
Martin

> --
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> Não sou nada.
> Nunca serei nada.
> Não posso querer ser nada.
> À parte isso, tenho em mim todos os sonhos do mundo.
>


More information about the tei-council mailing list