Skip to content

Use version 2.0 instead of 1.1 #10

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.

Sign up for GitHub

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

Jump to bottom
Closed
gkellogg opened this issue Jun 30, 2018 · 3 comments
Closed

Use version 2.0 instead of 1.1 #10

gkellogg opened this issue Jun 30, 2018 · 3 comments
Labels
propose closing spec:wontfix

Comments

@gkellogg
Copy link
Member

gkellogg commented Jun 30, 2018 •
edited
Loading

Comments at TPAC suggested that as our work is a breaking change (causing 1.0 processors that are not 1.1 compatible to intentionally break when they see "@version": 1.1), semantic versioning would suggest that we use a major release number, rather than a minor number.

Original issue is Use version 2.0 instead of 1.1 #548
@gkellogg
Copy link
Member Author

I think this is a no-go zone

@gkellogg gkellogg mentioned this issue Jun 30, 2018
Closed
@azaroth42
Copy link
Contributor

Yup, agree with closing. Charter is pretty clear on backwards compatibility.

@azaroth42
Copy link
Contributor

Closing, won't fix. Rationale: We're not chartered to make breaking changes.

WG Resolution: https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2018/2018-07-27-json-ld#section2-3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
propose closing spec:wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gkellogg @azaroth42