Stefan Majewski wrote:
> Lou Burnard wrote:
>> The idea was to make all listXXX elements have similar content
>> models, but listPerson seems to have been left out. The standard
>> model would give listPerson a model like this:
>> headlike*, (personLike|listPerson)*, relation*
> that looks very good to me, much better than stuffing the relations
> into a wrapper element. Is this change likely to go into P5 1.0?
If I live...
>> i.e. you would nest one listPerson inside another rather than
>> arbitrarily call the outermost one a particDesc.
> The one advantage of <particDesc> appears to be that it may contain
> 'model.pLike'. We don't use this, but others might find it useful.
Exactly, yes. That's probably why I paused for thought when making the
> Therefore, the model would probably be something like (model.pLike+ |
> (headlike*, (personLike|listPerson)*, relation*)). If the
> content-model of <particDesc> will be equal to the model of
> <listPerson>, then one could probably drop <particDesc>.
I am thinking more of dropping particLinks, and making the model
(model.pLike+ | model.listPerson+)
but ((model.pLike+, particLinks?) | listPerson+) is also plausible.