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

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

From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Mon, 06 Jun 2016 11:45:30 -0700
Subject: [rfc-i] [IAB] draft-iab-xml2rfc-03, "B.2 Anchors and IDs"
In-Reply-To: <62810739-6bd4-fb4e-dd2f-42afb6184b53@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> <A4554862-C4BE-4711-9613-1072D67BFD83@vpnc.org> <62810739-6bd4-fb4e-dd2f-42afb6184b53@gmx.de>
Message-ID: <6885012C-E4BB-4C7C-93AE-F5EF9348AA37@vpnc.org>

On 11 May 2016, at 8:13, Julian Reschke wrote:

> On 2016-05-11 16:15, Paul Hoffman wrote:
>> 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?
>
> But are they non-obscure?

Correct.

> What we have right now doesn't make a lot of sense to me. Why can I 
> link to <thead>, but not to a <note>?

Because to some of us a <note> is obscure. Could you send a specific 
list of changes you want, sometime soon? If not, we can certainly 
revisit this in a later version of the vocabulary.

--Paul Hoffman