-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
What does it take to get the JSON-Schema specification adopted by an IETF working group? #27
Comments
I'm pretty sure there are IETF documents (BCPs/Best Common Practices) and the like outlining this. I do not think we need an issue here to track it, unless you had something specific in mind @Relequestual? If we want to track getting things ready for working group submission, that seems like something we could use GitHub's "Projects" feature for (or a tag if that is too restrictive) |
Agreed. I had a look at the BCP and working group documents and couldn't find any inforamtion on how one goes from individual submission to working group rfc. (I'm assuming that's our aim here anyway) |
Yeah, there is documentation for that somewhere, can't remember offhand but I have seen some guidance and I'm sure I can find it again when we need it. |
If anyone happens to pass by here and does know where such a guide is located, please provide a link. thanks. |
It's RFC 7221, particularly https://tools.ietf.org/html/rfc7221#section-2 |
This is more a question that needs answering as opposed to an issue. If anyone can shed some light on this, please do comment.
The text was updated successfully, but these errors were encountered: