-
Notifications
You must be signed in to change notification settings - Fork 152
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
JSON-LD introduction via data model #155
Comments
I had a fairly lengthy discussion with @cygri on this and we came up with an idea of what could be done to resolve this issue. The notes below are very rough and are mainly meant as a reminder to me on how to re-organize the introduction to the JSON-LD spec. In general, the introduction should be re-written to do the following things, in this order:
This approach is geared toward people that know JSON and is meant to be a gentle migration into JSON-LD. Hopefully, this will make the introduction flow a bit more nicely. |
RESOLVED: Rewrite the introductory portions of the JSON-LD document to explain JSON-LD in JSON terms first, then describe the advantages of JSON-LD, then rework the Linked Data section as the JSON-LD data model section. |
|
+1 to the new Section 3.1; this address my comment. I'd say that the two six-item lists in 3.1 are quite redundant, and the second list is probably sufficient to get the point across. That's just an editorial comment. |
Thinking more about it, I believe that the section “3.1 Benefits of JSON-LD” should be moved to Section 2 and made non-normative. It provides rationale, and not basic concepts. |
I agree with Richard on this. The two (three) lists could should combined and probably the whole section should be moved into section 1 (I think that would work better than moving it to section 2). |
This issue was raised by @cygri as part of #47:
The text was updated successfully, but these errors were encountered: