Skip to content

Use version 2.0 instead of 1.1 #548

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 Nov 16, 2017 · 1 comment
Closed

Use version 2.0 instead of 1.1 #548

gkellogg opened this issue Nov 16, 2017 · 1 comment
Labels
api defer Issue deferred to future Working Group spec-design syntax

Comments

@gkellogg
Copy link
Member

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.

This could impact a potential WG, which may want to make further changes, and then be in the place of using either 2.1 or 3.0, which is odd given that the previous recommendation is 1.0.
@gkellogg gkellogg added this to the JSON-LD 1.1 milestone Nov 16, 2017
This was referenced Jan 23, 2018
Closed
Merged
@gkellogg gkellogg removed this from the JSON-LD 1.1 milestone Jan 25, 2018
@gkellogg gkellogg added defer Issue deferred to future Working Group and removed on-hold labels Mar 12, 2018
@gkellogg gkellogg mentioned this issue Jun 30, 2018
Closed
@gkellogg
Copy link
Member Author

Closed in favor of w3c/json-ld-syntax#10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api defer Issue deferred to future Working Group spec-design syntax
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gkellogg