Hi all, The HTML file (available from https://www.rfc-editor.org/rfc/rfc8176 <https://www.rfc-editor.org/rfc/rfc8176>) was generated using rfc2html (https://www.pypi.org/project/rfc2html <https://www.pypi.org/project/rfc2html>). Please feel free to direct questions to the maintainers listed on that page.
Thanks, RFC Editor/sg > On Oct 20, 2020, at 9:31 AM, Benjamin Kaduk <ka...@mit.edu> wrote: > > [adding back rfc-edi...@rfc-editor.org] > > Hi David, > > I am quite far removed from the actual operation of the script and the > rfc-editor.org website, so I don't know the answer to your question. That > said, my understanding is that it's set up with automation that assumes the > script is idempotent, and can regenerate various bits from scratch in > certain cases, so a manual edit might not be very reliable. > > -Ben > > On Tue, Oct 20, 2020 at 09:26:21AM -0700, David Brossard wrote: >> Thanks Ben (and apologies about the double submission). >> >> In this case, given the reference is not an RFC, that would explain why the >> script failed. Can we do a manual fix after the script has run to update >> the RFC? >> >> On Tue, Oct 20, 2020 at 9:24 AM Benjamin Kaduk <ka...@mit.edu> wrote: >> >>> On Tue, Oct 20, 2020 at 09:21:45AM -0700, RFC Errata System wrote: >>>> --VERIFIER NOTES-- >>>> Errata reports are for reporting issues with the authoritative RFC >>> version(s) as published by the RFC Editor. RFC 8176 predates the usage of >>> the "v3 XML" format, so the plain text version is the authoritative one, >>> and thus questions of HTML links are irrelevant for it. >>> >>> For what it's worth, this "bad HTML link" situation occurs with some >>> regularity -- the "html" versions of non-v3-XML RFCs are created by running >>> a script over the text version. The script uses heuristics to convert >>> certain types of text into links, and "Section <N>" gets expanded to this >>> document unless followed by "of RFC <Y>". I believe this script is >>> open-source and patches would be welcome, though I don't know the location >>> of the source-code repository in question off the top of my head. >>> >>> -Ben >>> >>> _______________________________________________ >>> OAuth mailing list >>> OAuth@ietf.org >>> https://www.ietf.org/mailman/listinfo/oauth >>> >> >> >> -- >> *David Brossard* >> Sr. Director of Product Management >> Identity, Authentication, Federation, and Single Sign-On | Salesforce >> c: +1 502-922-6538 (US) | +1 236-333-6379 (Canada) >> Learn more about identity here >> <https://trailhead.salesforce.com/content/learn/modules/identity_basics/identity_basics_product> >> | >> Identity for Developers >> <https://developer.salesforce.com/developer-centers/identity/> >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
