[rfc-i] draft-iab-xml2rfc-03, "2.54 <table>"

paul.hoffman at vpnc.org (Paul Hoffman) Tue, 21 June 2016 23:42 UTC

From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Tue, 21 Jun 2016 16:42:52 -0700
Subject: [rfc-i] draft-iab-xml2rfc-03, "2.54 <table>"
In-Reply-To: <494ccbb1-8462-01f1-b9eb-2aa1bf82e6dc@gmx.de>
References: <494ccbb1-8462-01f1-b9eb-2aa1bf82e6dc@gmx.de>
Message-ID: <5E89F573-E5F1-41D5-9538-E30234494477@vpnc.org>

On 16 Jun 2016, at 1:22, Julian Reschke wrote:

> <https://greenbytes.de/tech/webdav/draft-iab-xml2rfc-03.html#rfc.section.2.54>:
>
>> 1. One optional <name> element (Section 2.32)
>> 2. Optional <iref> elements (Section 2.27)
>> 3. One optional <thead> element (Section 2.59)
>> 4. One or more <tbody> elements (Section 2.55)
>> 5. One optional <tfoot> element (Section 2.57)
>
> a) I'm not totally convinced anybody will use <tfoot>.

Neither am I, but some people seem to like to have bits of explanation 
in tables, and some like to put that after the table.

> b) When running conversion tests, I discovered test cases that verify 
> that texttables that only contain column titles work; converting them 
> to v3 format yields a <table> element with <thead> but no <tbody> 
> child element. This would be valid HTML5; why do we disallow it?

A table with no body seems semantically weird to me.

--Paul Hoffman