Need to document W3C entries obsoleted by WHATWG specs #829
Comments
tidoust
added a commit
to tidoust/specref
that referenced
this issue
Oct 21, 2024
`access-control` was marked as an alias of `fetch`. That's not incorrect, but history-wise, `access-control` is more an alias of `cors`, which got superseded by `fetch`. That history wasn't properly recorded in the W3C database. It now is, so W3C update script is currently stuck because it wants to add an `access-control` entry that targets `cors`, duplicating the entry in `biblio.json`. This update drops the entry from `biblio.json`, so that updates may resume. (The superseding relationship between `cors` and `fetch` is not properly captured yet but that's orthogonal to the problem at hand, see tobie#829).
tidoust
added a commit
that referenced
this issue
Oct 21, 2024
* Drop `access-control` from biblio.json, now handled in w3c.json `access-control` was marked as an alias of `fetch`. That's not incorrect, but history-wise, `access-control` is more an alias of `cors`, which got superseded by `fetch`. That history wasn't properly recorded in the W3C database. It now is, so W3C update script is currently stuck because it wants to add an `access-control` entry that targets `cors`, duplicating the entry in `biblio.json`. This update drops the entry from `biblio.json`, so that updates may resume. (The superseding relationship between `cors` and `fetch` is not properly captured yet but that's orthogonal to the problem at hand, see #829).
dr-shorthair
pushed a commit
to dr-shorthair/specref
that referenced
this issue
Nov 29, 2024
…e#830) * Drop `access-control` from biblio.json, now handled in w3c.json `access-control` was marked as an alias of `fetch`. That's not incorrect, but history-wise, `access-control` is more an alias of `cors`, which got superseded by `fetch`. That history wasn't properly recorded in the W3C database. It now is, so W3C update script is currently stuck because it wants to add an `access-control` entry that targets `cors`, duplicating the entry in `biblio.json`. This update drops the entry from `biblio.json`, so that updates may resume. (The superseding relationship between `cors` and `fetch` is not properly captured yet but that's orthogonal to the problem at hand, see tobie#829).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
tr.rdffile (same for the W3C API) only knows about W3C specs. As such, it does not contain the information needed to fill theobsoletedByproperties of W3C specs that got superseded by WHATWG specs. When the shortname stayed the same, the data essentially moved towhatwg.json, which seems fine, but when the shortname changed in the process, the relationship gets lost in data. Main missing links:cors->fetchhtml5entries ->htmlxmlhttprequestentries ->xhrThe text was updated successfully, but these errors were encountered: