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.
Via WICG/admin#190
The
biblio.json
file in WICG's admin repository has been maintained on and off in the past few years by random folks (including me). A few specs have now been retired or have moved somewhere else, and many active WICG specs do not appear in the list (for example, browser-specs contributes ~50 WICG specs to Specref that are not in WICG'sbiblio.json
file). All in all, the list in browser-specs is a better source for WICG specs.This update stops pulling updates from WICG's
biblio.json
files, making it possible to retire the file. New WICG specs will continue to be reported through the script that pulls data from browser-specs.This update also flags retired and obsoleted WICG specs in
refs/wicg.json
, see short analysis in:WICG/admin#190 (comment)
The script that looks at updates in browser-specs won't create entries that already exist in
refs/wicg.json
. One consequence is that possible updates to existing WICG specs listed in that file require manual intervention for the time being. It may make sense to delete most entries fromrefs/wicg.json
(leaving only retired specs that do not exist in browser-specs, and aliases that start withWICG-
), and to re-create them inrefs/browser-specs.json
by running the script that pulls info from browser-specs once WICG entries have been deleted. Not done here.