Azaroth suggestions

[gkellogg]

• "This specification defines JSON-LD" => "This specification defines JSON-LD 1.1". Fixes Should abstract refer to 1.1 version? #217.
• Remove "if desired" Fixes Remove somewhat passive-aggressive "if desired" from Introduction #218.
• Improve default language definition. Fixes default language is described rather than defined in 1.4 #219.
• it's => its fixes. Fixes Typo: it's --> its in id map definition #221, fixes Typo: it's --> its in type map definition #223, and fixes Typo: it's --> its in 4.1.4 #239.
• ore => or. Fixes Typo: ore --> or in included block definition #222.
• Simplify simplicity. Fixes Simplicity design goal can be even simpler! #224.
• Improve data model overview. For Data Model Overview is misleading? #225.
• Clarify that literals are not blank nodes. Fixes Overview implies literals are blank nodes #226.
• Improve definition of @nest. Fixes @nested keyword definition does not describe what it does #227.
• Update @none definition. Fixes Definition of @none could be more specific #228.
• sccope => scope. Fixes Typo: sccope for scope in definition of @propagate #229.
• Clarify that @version is set to 1.1, not "json-ld-1.1". Fixes Potential for confusion of @version syntax? #230.
• Improve requirements of terms. Improve requirements of terms.
• Reference security considerations for remote contexts. Fixes Refer to privacy / security concern of context deref in 3.1? #232.
• Update local dfns to not be links by removing data-cite. Fixes Links in TR/ refer to github.io version not internal anchors #233.
• Add a missing description of list objects and set objects. Fixes "List Objects and Set objects" ... ? #234.
• Fix wording of nested properties. Fixes Nested properties in section 4 #235.
• Add forward references for other things that affect the context in section 4.1. Fixes Forward ref in 4.1 to 4.1.7-10 ? #236.
• Better describe example 25. Fixes Text before example 25 should describe the result #237.
• Move subsection on using the document base for the default vocabulary until after the section on the document base (4.1.2.1 => 4.1.4). Fixes 4.1.2.1 should come after 4.1.3 #238.
• Fix grammar in Scoped Contexts section. Fixes Bad grammar in intro to 4.1.7 #240.
• Split example 46 into separate examples. Fixes Move text inside example 46 to immediately before it #241.
• Re-defined => Redefined. Fixes redefine / redefinition doesn't need hyphen #242.
• limits => limit. Fixes Grammar in 4.1.8 #243.
• Fix grammar in Imported Contexts section. Fixes Typo and confusion in 4.1.9 intro #244.
• effect => affect. Fixes Typo: effect -> affect after example 50 #245.
• Further clarify that type coercion takes place only on strings, not maps. Fixes Note in 4.2.1 should clarify not setting node type via context #247.
• Make examples clearer. Fixes Example 63 is still hard to understand #248.
• Remove old warning in note about redefining IRIs to have a different meaning, which is now disallowed. Fixes Note at end of 4.2.3 is out of date #249.
• Use a scoped, rather than an embedded context for default language example. Fixes example 67 uses not best practice of node embedded context #250.
• Note that indexing of language tags depends on their not using sub-tags other than the primary language-tag. Fixes 4.2.4 or 4.6.2 to note challenge of "en-us" and dot-property notation code #251.
• Remove uninformative note on type coercion from 4.5. Fixes Delete type coercion reference from 4.5 #252.

---

Preview | Diff

[gkellogg]

Actually, there are several more I'll add on to this PR tomorrow.

[gkellogg]

Still a couple of more to go.

[gkellogg]

I'll do the rest in another PR.

[pchampin]

Strings that [contain a colon] should not be used as terms.

Well, it is acceptable to have a term definition of the form "foaf:knows": {"@type": "@id"}.
Isn't foaf:knows a term in that case?

[pchampin]

My bad, the key for a term definition is not necessarily a term. Slightly confusing, but ok :)

[gkellogg]

We can probably improve things more, but yes, the key for an expanded definition my be an IRI, which can’t be a term.

[gkellogg]

Perhaps we should update the context definition to say that keys can be noted keywords and strings treated as terms of IRIs. The values of which may be strings, interpreted as IRIs, or expanded term definitions, or words to that effect.