-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update JSON-LD to 1.1? #47
Comments
Here it is:
And an example in the json-ld playground |
Thanks a lot @azaroth42. We will follow your guidance when updating Appendix A as described in #45. And we'll add you to the Acknowledgments, of course! |
hvdsomp
added a commit
that referenced
this issue
Oct 5, 2021
Reworked Appendix A with a new example that does not leverage IANA-registered link relation types as per the discussion in #45. Also adding the JSON-LD 1.1 solution to the problem of not being able to use "linkset" links in link sets when mapping to JSON-LD as provided by @azaroth42 in #47. Unfortunately, as things stand with not being able to express IANA-registered link relation types as HTTP URIs (see also #45) it will not be possible to use "linkset" links (or any other IANA-registered link types) in link sets that need to be mapped to JSON-LD until a solution is found with that regard.
Addressed in 0838136 |
Propose this issue be closed as it's been dealt with |
Closing. Addressed in https://www.ietf.org/archive/id/draft-ietf-httpapi-linkset-04.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
W3C.REC-json-ld-20140116
-->W3C.REC-json-ld11-20200716
If you then use the scoped context feature from 1.1, it would be possible (I believe without having actually done the definition) to avoid the confusion for
linkset
used in different parts of the document structure. Happy to help with the context definition if that would be useful.The text was updated successfully, but these errors were encountered: