[rfc-i] draft-iab-html-rfc-02: references

[julian.reschke at gmx.de (Julian Reschke)]

On 2016-02-27 17:27, Paul Hoffman wrote:
> On 27 Feb 2016, at 1:03, Julian Reschke wrote:
>
>> <http://greenbytes.de/tech/webdav/draft-iab-html-rfc-02.html#element.references>:
>>
>>
>>> If there is at least one <references> element, a "References" section
>>> is added to the document, continuing with the next major section
>>> number after the last <section>.
>>>
>>> Each references element will be added to that "References" section as
>>> if it were a section itself.
>>
>> That doesn't work. For a document that has only one <references>
>> element (for instance, just normative references), it will lead to
>> unnecessary (and uncommon) nesting.
>
> Why does "unnecessary (and uncommon) nesting" equate to "doesn't work"?
> Is that just a value judgement, or is there something technically wrong
> with that kind of nesting?

It's not wrong, but it's also not what the tools generate today, and 
most likely not what the RFC production center wants.

>>> <section id="n-references">
>>> <h2 id="s-3">
>>> <a href="#s-3" class="selfRef">3.</a>
>>> <a href="#n-references" class="selfRef">References</a>
>>> </h2>
>>> <section id="n-informative-references">
>>> <h3 id="s-3.1">
>>>   <a href="#s-3.1" class="selfRef">3.1.</a>
>>>   <a href="#n-informative-references" class="selfRef">
>>>     Informative References</a></h3>
>>> <dl class="reference">...
>>> </dl>
>>> </section>
>>> </section>
>>
>> This doesn't explain where the ID for the enclosing section comes from.
>
> Which ID are you referring to? Both of those look pretty clear to me,
> but maybe I'm missing something.

It's not clear where they come from; from the source document? Are they 
automatically inserted?

Best regards, Julian