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

Pick a better keyword for @nest #3

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

Pick a better keyword for @nest #3

gkellogg opened this issue Jun 30, 2018 · 3 comments
Labels
propose closing satisfied Requirement Satisfied

Comments

@gkellogg
Copy link
Member

gkellogg commented Jun 30, 2018

People haven’t been satisfied with the @nest term for describing nested properties, although nothing better has come along.

Original issue was Ignoring semantically meaningless nesting #246.

@gkellogg
Copy link
Member Author

I think that ship has sailed.

@azaroth42
Copy link
Contributor

+1 to closing. At best it's a bikeshed issue, at worst it's an unnecessary incompatibility for systems that implement the draft spec.

@azaroth42
Copy link
Contributor

Closing, won't fix, but without prejudice if someone comes up with a significantly better name.
Rationale: Unnecessary bikeshedding.

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

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

No branches or pull requests

2 participants