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

Establish versioned or living standard model for specs #8

Closed
csarven opened this issue Jul 7, 2019 · 8 comments
Closed

Establish versioned or living standard model for specs #8

csarven opened this issue Jul 7, 2019 · 8 comments

Comments

@csarven
Copy link
Member

csarven commented Jul 7, 2019

All specifications should be up front up about what to expect ie. are specs versioned or following a living standard model.

To avoid complications down the line and to learn from what's nearby, I'd like to point to https://www.w3.org/2019/04/WHATWG-W3C-MOU.html

Discuss.

@RubenVerborgh
Copy link
Contributor

RubenVerborgh commented Jul 7, 2019

My opinion:
Versioned. And we have different documents that can be in different versions.

@csarven
Copy link
Member Author

csarven commented Jul 7, 2019

Was that a unanimous/collective decision? Public discussion somewhere that I missed? Whatever is the decision, it has ramifications and I'd like make sure that's acknowledged and adhered down the line.

There are (dis)advantages to both.. versioned would entail that an implementation may conform to version X but not Y... so "interop" in context of versoin. Living Standard may entail or expected that implementations need to keep up with the spec and may not need to signal which features they support... or LS needs to be always backwards compatible or not.. There are finer details here that we should be careful about.

@RubenVerborgh

This comment has been minimized.

@justinwb
Copy link
Member

justinwb commented Jul 7, 2019

My opinion: it would be ideal to have version tracking, but also have an expectation that implementations keep up with the specification. Any change that impacts backwards compatibility after a specification reaches its first major version (1.0) should be taken extremely seriously and need to have an extremely strong case behind it.

@kjetilk
Copy link
Member

kjetilk commented Jul 8, 2019

Actually, I think that it would be reasonable to develop living standards as long as we (for some value of "we") are at the helm, but that we should have the ambition to graduate the development of the specifications into the W3C process with the formation of the WG, in which case it would stop being a living standard. We would probably still be deeply involved, but it would follow a different process, some of which might result in Recommendations, some may result in Notes. Exactly at what point a WG becomes appropriate, I'm not sure, but also not just up to us to decide, but I think we should have that in mind.

So, with some opinions stated, we should have a discussion :-)

@csarven
Copy link
Member Author

csarven commented Sep 12, 2019

https://www.w3.org/wiki/Evergreen_Standards has good documentation / considerations / expectations / practices.. on living standards.

@kjetilk
Copy link
Member

kjetilk commented Sep 16, 2019

https://www.w3.org/wiki/Evergreen_Standards has good documentation / considerations / expectations / practices.. on living standards.

Ah, I hadn't seen that. Thanks, @csarven ! @Mitzi-Laszlo , have you seen that? I think it is worth having a look at.

@kjetilk
Copy link
Member

kjetilk commented Jun 1, 2021

Consensus from Editor’s Meeting 2021-06-01 with @timbl @justinwb, @csarven and @kjetilk present:

The Editors prefer a versioned specification approach to allow implementers to code against a stable version.

@kjetilk kjetilk closed this as completed Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants