Skip to content
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

Open
xfq opened this issue Nov 18, 2021 · 5 comments
Open

BCP 47 alias #688

xfq opened this issue Nov 18, 2021 · 5 comments

Comments

@xfq
Copy link
Collaborator

xfq commented Nov 18, 2021

In https://www.specref.org/?q=bcp47 I see:

[BCP47]
Alias of [rfc5646].

But I think BCP 47 contains two RFCs, RFC 5646 and RFC 4647.

/cc @r12a

@marcoscaceres
Copy link
Collaborator

marcoscaceres commented Nov 26, 2021

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?

@mnot
Copy link

mnot commented Nov 26, 2021

Yep, BCPs and STDs can refer to one or more RFCs, and they can change over time.

@marcoscaceres
Copy link
Collaborator

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?

@marcoscaceres
Copy link
Collaborator

@tobie, alternatively, I wonder if the IETF bot script should be getting all the "BCP"s somehow?

@tobie
Copy link
Owner

tobie commented Dec 8, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants