-
Notifications
You must be signed in to change notification settings - Fork 45
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
Consolidate the JSON-LD format #406
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and agree we can include the RDF serialization JSON-LD as a starting example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, that is a good next step
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I won't go through all of the examples, but I would like to see enumerated values being correct.
Signed-off-by: Armin Tänzer <armin.taenzer@tngtech.com>
8a334fd
to
39360b2
Compare
FYI: I deleted the alias |
I think this is fine for merging, and we can iterate improving it afterwards. |
While there is still discussion surrounding the JSON serialization, this is an attempt to consolidate the JSON-LD format as a pure RDF format. This does not mean it can't be reused as a JSON serialization in the future, but please keep JSON discussions out of this PR for now.
This should bring us closer to a first functioning serialization that people can implement and try out.