-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Spec URL Should be Normalized #3328
Comments
What spec URLs in BCD? The only URLs commonly used in BCD are the Assuming we really are talking about spec URLs though... This is an interesting idea. I take it the idea is basically to have a table of specifications, with each spec's entry including its base URL, so that links to stuff within that spec are then written relative to that base URL. So something like... SpecInfo.json
RTCPeerConnection.json
Something like that, anyway. I think I have missed the specific use case for this but the general idea is probably something like this for how it would be built, no? |
@a2sheppy the schema has At least right now, it only appears to be used in |
I believe we should move |
@chrisdavidmills I think moving spec data is a good idea, but until the license issue is resolved this will prevent me from contributing to it. |
@jpmedley this is an issue, certainly, which could perhaps be mitigated in a few ways (e.g. by getting W3C spec folks to add their own specs to our data), but really it would be so much better to sort out the license issue once and for all. I'll bring this up with our lawyer again and see if he managed tro make any headway with the discussion. |
https://github.com/tobie/specref is a source of truth you could use for this, but I think you'll find some of the URLs still need massaging and getting them updating in specref can be difficult because it sometimes requires updating a page under https://www.w3.org/TR/. I've dealt with this problem in https://foolip.github.io/day-to-day/ but not in a way that is maintenance-free. |
Closing this. We're not planning to do anything about this for now. Might come back in the future, when MDN is based on more structured data. |
The spec URLs in BCD should be normalized. In non-tech speech, this means deduplicate. This serves two purposes:
An automated consistency check within a file cannot solve this problem because many interfaces contain members that contributed by multiple specs.
The text was updated successfully, but these errors were encountered: