Issue 415 scope on type

[gkellogg]

This commit adds scoping based on @type for expansion and compaction. Also ensure that types used in type maps have any associated local context applied to their values.

Also, corrects some minor errors in id and type maps where values were not appropriately expanded ore compacted.

Fixes #415.

[lanthaler]

This URL redirects to the lower-case version, why did you change it?

[gkellogg]

Because we use upper case within [[]], it was creating two references, one normative and one informative. When I discussed this with Melvin, he felt this was appropriate behavior. To get back to a single entry in the reference section, it was necessary to unify the use within [[]] and @data-cite.

However, I didn't intend to update the json-ld-connect spec, so I'll reverse that change.

[lanthaler]

Because we use upper case within [[]], it was creating two references, one normative and one informative. When I discussed this with Melvin, he felt this was appropriate behavior.

Who is we? ReSpec? That sounds like a bug to me.

[gkellogg]

We is, we the editors of JSON-LD. For example, we use [[RDF11-CONCEPTS]], instead of [[rdf11-concepts]], and so-forth. We could, of course, change to use lower-case references uniformly.

It doesn't really matter to me, but to use @data-cite, we need to be consistent, and this seems like a pretty nice feature of ReSpec to me.

The fact that ReSpec is case-sensitive seems like a design decision, which I wasn't interested in pursuing. Feel free to take it up on spec-prod.

[gkellogg]

@lanthaler do you have an substantive feedback on this PR?

[lanthaler]

No, and unfortunately I don't have the time to properly review it. As discussed elsewhere I'm concerned about the complexity of JSON-LD but see the value of this feature. So I'm fine with this being merged.