-
Notifications
You must be signed in to change notification settings - Fork 23
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
Labels
Comments
I think that ship has sailed. |
+1 to closing. At best it's a bikeshed issue, at worst it's an unnecessary incompatibility for systems that implement the draft spec. |
Closing, won't fix, but without prejudice if someone comes up with a significantly better name. WG Resolution: https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2018/2018-07-27-json-ld#section2-6 |
Closed
This was referenced Oct 27, 2018
This was referenced Jan 12, 2019
This was referenced Feb 9, 2019
This was referenced Mar 22, 2019
This was referenced Jun 7, 2019
Closed
This was referenced Oct 4, 2019
Merged
This was referenced Oct 18, 2019
Merged
This was referenced Feb 14, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: