Clarify why processing @context is useful for JSON-based processors. #546
Conversation
msporny
requested review from
brentzundel,
David-Chadwick,
chaals,
ken-ebert and
burnburn
There was a problem hiding this comment.
This text does what is required and I would be happy for it to be merged.
I raised #548 as an alternative for the same thing because a line-by-line commentary turned out to be a difficult way to express what I thought might be improved. Feel free to merge either one and close the other.
index.html
Outdated
| <code>@context</code> mechanism. This is because the exact terms that a | ||
| producer and consumer of the data model described by this specification, | ||
| as well as any extensions used, are explicitly stated through the use and | ||
| processing of the <code>@context</code> property. In other words, the context |
There was a problem hiding this comment.
I had trouble parsing the sentence starting with This is because... ... I think a word was forgotten or something?
I like some of the language in your PR better than the language in this one. I'll try to merge PR #548 with this one where it makes sense to do so. |
There was a problem hiding this comment.
Once @dlongley's comments are addressed, I approve this PR.
msporny
force-pushed
the
msporny-issue-491
branch
from
be47a1f to
ad5c9bc
Compare
|
I have one question about this text which is, how does a JSON processor find the human readable document that is referred to? The text only says that the machine-readable description should exist at the URL in the @context. Wouldn't it be better to say that the human readable version should also be at the same URL, perhaps as comments in the JSON-LD. This is the text I am questioning: A human-readable document describing the expected order of values for the |
|
@David-Chadwick can you please open a new issue on the item you placed above. |
|
Done. You can close this PR now |
Related to issue #491.
Preview | Diff