-
Notifications
You must be signed in to change notification settings - Fork 142
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
BCP 47 alias #688
Comments
Yeah true... this is an interesting case. I wonder if BCP47 should be treated as its own entry and point to https://www.rfc-editor.org/info/bcp47 ... I'm thinking that this is not an alias and maybe more things will become part of BCP47 over time. @mnot, would you know how "bcp" things work at the IETF? Could more RFCs be added over time? |
Yep, BCPs and STDs can refer to one or more RFCs, and they can change over time. |
ok, then yeah... BCP should point to https://www.rfc-editor.org/info/bcp47 ... @xfq, do you want to have a go at updating the entry? |
@tobie, alternatively, I wonder if the IETF bot script should be getting all the "BCP"s somehow? |
Yeah. I think that makes sense. Not sure where to get them from, though. |
In https://www.specref.org/?q=bcp47 I see:
But I think BCP 47 contains two RFCs, RFC 5646 and RFC 4647.
/cc @r12a
The text was updated successfully, but these errors were encountered: