[rfc-i] draft-iab-xml2rfc-03, "2.56 <td>"

paul.hoffman at vpnc.org (Paul Hoffman) Mon, 06 June 2016 19:00 UTC

From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Mon, 06 Jun 2016 12:00:14 -0700
Subject: [rfc-i] draft-iab-xml2rfc-03, "2.56 <td>"
In-Reply-To: <bae14e5e-cf47-0a64-bdc8-ebe07fb2ff1c@gmx.de>
References: <bae14e5e-cf47-0a64-bdc8-ebe07fb2ff1c@gmx.de>
Message-ID: <75EDCDA7-D042-4652-BE6A-E8A0835E058B@vpnc.org>

On 14 May 2016, at 3:30, Julian Reschke wrote:

> <https://greenbytes.de/tech/webdav/draft-iab-xml2rfc-03.html#rfc.section.2.56>
>
> It seems to me that the content model for <td> and <th> is flawed; it 
> allows to mix block content with phrasing content.
>
> The grammar currently says:
>
>>     (t+
>>      | (text
>>         | artwork
>>         | bcp14
>>         | br
>>         | cref
>>         | dl
>>         | em
>>         | eref
>>         | figure
>>         | iref
>>         | ol
>>         | relref
>>         | sourcecode
>>         | strong
>>         | sub
>>         | sup
>>         | tt
>>         | ul
>>         | xref)+)
>
> ...so it special cases <t>, which is good. However, it allows mixing 
> text content with non-<t> block level elements, such as lists.
>
> We probably need something like:
>
>     ( (t
>         | artwork
>         | dl
>         | figure
>         | ol
>         | sourcecode
>         | ul
>       )+
>      | (text
>         | bcp14
>         | br
>         | cref
>         | em
>         | eref
>         | iref
>         | relref
>         | strong
>         | sub
>         | sup
>         | tt
>         | xref)*)
>
> instead.

Seems good. Done.

--Paul Hoffman