Open
Description
Describe the issue
As pointed out by @royfielding in #1156 (comment):
It is not appropriate for the tools to override the anchor names chosen by the authors. We deliberately chose those names and expect them to appear in all section and ToC references. It is still a bug even if the old references work, since we do not want two or three alias names for every section ref. We only want the ones that are authored in the XML.
As an example, the Range Requests header in RFC 9110 points to the anchor #name-range-requests, while the appropriate anchor to point to would be #range.requests, as the presumably author-chosen identifier of the header's parent element:
<div id="range.requests">
<section id="section-14">
<h2 id="name-range-requests">
<a href="#section-14" class="section-number selfRef">14. </a>
<a href="#name-range-requests" class="section-name selfRef">Range Requests</a>
</h2>
<p id="section-14-1">…</p>
<p id="section-14-2">…</p>
<div id="range.units">…</div>
<div id="field.range">…</div>
<div id="field.accept-ranges">…</div>
<div id="field.content-range">…</div>
<div id="partial.PUT">…</div>
<div id="multipart.byteranges">…</div>
</section>
</div>Code of Conduct
- I agree to follow the IETF's Code of Conduct