Re: [Last-Call] [httpapi] Last Call: <draft-ietf-httpapi-rfc7807bis-04.txt> (Problem Details for HTTP APIs) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hello carsten.

On 2022-11-03 11:04, Carsten Bormann wrote:
What my comment was trying to say is that it is unlikely that IANA will convert any registered type URI
https://iana.org/assignments/http-problem-types#foo
into an ID on that HTML page. So the fragment identifier points into thin air.
Worse, there is no contract (specification/documentation) for the HTML format that IANA uses here, and they have been actively barring the RFC editor to put fragment identifiers into IANA references.
So they might go ahead and put an id=“foo” on a later registration that points to a document called foo, or uses a footnote called foo, …
E.g., on https://www.iana.org/assignments/cbor-tags
you find an id=“Kris_Zyp” and an id=“note1”.
I don’t think the registrant or the designated expert should be juggling fragment IDs in an attempt to avoid this kind of conflict.

all true, no doubt. i never understood why you wouldn't support fragment identifiers on those pages for the obvious usefulness this would provide, but that's a different discussion.

the question then is whether we want to include guidance that we know will not be properly supported at the fragment identifier level. we could say it's kind of ok because you will end up on the correct page and will probably figure it out, but that certainly isn't technically what should be happening.

either we remove the guidance, or we can add a note saying that for those URIs, fragment identification will not work. my preference is for the latter, because it would be useful to end up on the registry page.

thanks and cheers,

dret.

--
Erik Wilde | mailto:erik.wilde@xxxxxxxx    |
           | https://youtube.com/ErikWilde |

--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux