[tei-council] <listRelation> floppiness

[Martin Holmes]

+1 for both actions. Let's avoid breaking backward compatibility just 
before a release, but I agree that <p> makes no sense there and we 
should deprecate it.

Cheers,
Martin

On 14-09-08 05:23 PM, Syd Bauman wrote:
> My fix for bug 658 failed to build because the new content model for
> <listRelation> does not allow <p>. Why on earth did it allow a <p>?
> Yes, I see the example, and I am unswayed. A <listRelation> should be
> (parallel to <listPerson> et alia) should be a list of <relation>s!
>
> I'm going to fix this by putting <p> back in, and suggest that we put
> on the docket for discussion deprecating and nuking listRelation/p.
>