[rfc-i] [IAB] draft-iab-xml2rfc-03, "B.2 Anchors and IDs"

paul.hoffman at vpnc.org (Paul Hoffman) Wed, 11 May 2016 14:15 UTC

From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Wed, 11 May 2016 07:15:56 -0700
Subject: [rfc-i] [IAB] draft-iab-xml2rfc-03, "B.2 Anchors and IDs"
In-Reply-To: <ba051d5b-6dad-4a88-b990-5836ac2a2ae2@gmx.de>
References: <60965ced-5f85-ab7a-f170-916fadfb9035@gmx.de> <C2E2DF4E-6097-4FB6-B85B-E0AA1DCE05A8@cisco.com> <72C81BDD-4BA4-4083-80F2-E89696A91F5F@vpnc.org> <ba051d5b-6dad-4a88-b990-5836ac2a2ae2@gmx.de>
Message-ID: <A4554862-C4BE-4711-9613-1072D67BFD83@vpnc.org>

On 10 May 2016, at 21:30, Julian Reschke wrote:

> On 2016-05-11 01:52, Paul Hoffman wrote:
>> ...
>> +1 to the request. I don't see a "need" to anchor in non-block text, nor
>> to obscure blocks.
>> ...
>
> I'm asking for consistency - why have @anchor in thead and tbody then?

Because they are block-y elements, yes?

--Paul Hoffman