Get "current" level from W3C API #176
Comments
tidoust
added a commit
to tidoust/browser-specs
that referenced
this issue
Nov 3, 2020
The current specification in a series of specifications was the last level that was not a delta spec, unless otherwise specified in specs.json. This update extends the definition as follows: for W3C specifications, the current specification becomes the one returned by the W3C API, unless otherwise specified in specs.json, and provided that the current specification returned by the W3C API is in the list. In turn, this allows us to drop the manual "current" entries in specs.json. They are no longer needed, the W3C API returns the right info for them. Fixes w3c#176.
tidoust
added a commit
that referenced
this issue
Nov 4, 2020
The current specification in a series of specifications was the last level that was not a delta spec, unless otherwise specified in specs.json. This update extends the definition as follows: for W3C specifications, the current specification becomes the one returned by the W3C API, unless otherwise specified in specs.json, and provided that the current specification returned by the W3C API is in the list. In turn, this allows us to drop the manual "current" entries in specs.json. They are no longer needed, the W3C API returns the right info for them. Fixes #176.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The code that determines the current specification in a series currently considers that the current level is the last level that is not a delta spec, unless otherwise specified in
specs.json:https://github.com/w3c/browser-specs/blob/master/src/compute-currentlevel.js#L11
For /TR/ specs, the "current" spec should be the level that gets returned when
/TR/[series shortname]is fetched. We can probably use that (or the info in Shepherd) as the source of truth. That would have the advantage of making it easier to follow transitions that are doomed to happen once in a while.See related discussion in w3c/reffy#417 (comment)
The text was updated successfully, but these errors were encountered: