Refresh the list of RFCs published under httpwg.org #766
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The list was no longer complete as the IETF HTTP WG published a few other RFCs. Also, the https://httpwg.org/specs page is not such a good source for the list because it fails to list a few specs, and also contains one RFC that is actually not published under https://httpwg.org/specs. The comment explains how to extract the list from the underlying GitHub repository instead. In terms of updates, this will swap the URL of a few additional RFC entries from `www.rfc-editor.org` to `httpwg.org/specs`, notably RFC9110, RFC9111, RFC9112 and RFC9113. That's intended, the `httpwg.org/specs` versions are more readable, as discussed in: w3c/browser-specs#933
tidoust
added a commit
to w3c/browser-specs
that referenced
this pull request
Nov 23, 2023
Take 3 :) PR #1135 actually had a couple of issues that made the code essentially useless because it only ran on a handful of IETF specs: - the code favored info from Specref over info from IETF - the code only really applied to drafts due to a buggy RegExp Fixing these problems yielded a new issue: the assumption that HTTP WG specs are always available under `httpwg.org` turns out to be wrong. Also, there are other specs that are not published by the HTTP WG but that still have an `httpwg.org` version. The code now looks at the actual list of specs in the underlying GitHub repository: https://github.com/httpwg/httpwg.github.io. As a result, the nightly URL of all IETF specs that have an `httpwg.org` version now targets that version, implementing the suggestion in #933 (see that issue for the list of affected specs). A companion PR was sent to Specref to implement a similar switch there: tobie/specref#766 The code also looks at the obsolescence data in datatracker and sets the `standing` and `obsoletedBy` properties accordingly. This fixes #327.
dontcallmedom
approved these changes
Nov 23, 2023
tidoust
added a commit
to w3c/browser-specs
that referenced
this pull request
Nov 23, 2023
Take 3 :) PR #1135 actually had a couple of issues that made the code essentially useless because it only ran on a handful of IETF specs: - the code favored info from Specref over info from IETF - the code only really applied to drafts due to a buggy RegExp Fixing these problems yielded a new issue: the assumption that HTTP WG specs are always available under `httpwg.org` turns out to be wrong. Also, there are other specs that are not published by the HTTP WG but that still have an `httpwg.org` version. The code now looks at the actual list of specs in the underlying GitHub repository: https://github.com/httpwg/httpwg.github.io. As a result, the nightly URL of all IETF specs that have an `httpwg.org` version now targets that version, implementing the suggestion in #937. A companion PR was sent to Specref to implement a similar switch there: tobie/specref#766 The code also looks at the obsolescence data in datatracker and sets the `standing` and `obsoletedBy` properties accordingly. This fixes #327.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The list was no longer complete as the IETF HTTP WG published a few other RFCs.
Also, the https://httpwg.org/specs page is not such a good source for the list because it fails to list a few specs, and also contains one RFC that is actually not published under https://httpwg.org/specs. The comment explains how to extract the list from the underlying GitHub repository instead.
In terms of updates, this will swap the URL of a few additional RFC entries from
www.rfc-editor.orgtohttpwg.org/specs, notably RFC9110, RFC9111, RFC9112 and RFC9113. That's intended, thehttpwg.org/specsversions are more readable, as discussed in: w3c/browser-specs#933(Side note that updates in browser-specs to align the URLs are upcoming)