-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import definitions from Reffy data #1761
Comments
@tabatkins is there anything @tidoust or I could do to help on this? |
dontcallmedom
added a commit
to w3c/mediacapture-transform
that referenced
this issue
Mar 8, 2021
Not available in bikeshed db yet - see also speced/bikeshed#1761
This was referenced Jan 5, 2023
Per https://lists.w3.org/Archives/Public/spec-prod/2023JanMar/0004.html, I think this is finished. 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
reffy supports extracting definitions from specs identified as browser specs and publishes its extracts as JSON data.
These definitions cover a broader set set of specifications and extract them daily from the latest editors draft (including for ReSpec documents), with around 20K more definitions identified in the process (see a more detailed comparison with Shepherd data.
If needed, the index of all specifications crawled for definitions is available in a JSON file, along with metadata about each specification. The list and metadata directly come from browser-specs.
(beyond my involvement in reffy, getting this done would also be very useful to me as a spec contributor since a number of WebRTC specs are stuck in terms of using auto-links due to outdated data in the Shepherd data)
/cc @tidoust
The text was updated successfully, but these errors were encountered: