Gregg Kellogg

> also, test 0076 expects `http://example.com/api/things/1` to be compacted as `1` when the base is itself. Wouldn't the empty string work too and be more compact? This is been in...

I agree that the spec could be more explicit in how to perform this operation, but it is quite late to introduce such an algorithm as we're ending the Candidate...

It's common for fragment identifiers to be appended to IRIs, and the base IRI, so that when compacting you get URIs of the form `#foo`, but it certainly would carry...

There is no such registration mechanism, although the API spec does have some processing considerations for things that look like keywords. In the past, when people were trying to use...

If the notion of "Recursively repeat ..." implies a separate variable scope, then steps 3 and 8, which modify _active context_ could be considered an isolated scope and don't affect...

Also, I don't see a reasonable way to update the Compaction algorithm, so this would be a one-way transformation. Ideally, compacting a document with a context which uses a scoped-context...

@niklasl I addressed this in #388, which includes your specific example as a test case, along with a simpler on. As I mentioned, not that it doesn't support compaction. (probably...

That is indeed a problem, but I don't see how to solve it in compaction reasonably; maybe we can't support this feature.

> Just to double check - in JSON-LD 1.0, there is no way to make the following work: > > ``` > { "@context": { > "CHEBI": "http://example.org/CHEBI_" > },...

> In general, can someone verify that ALL of the behaviors below conform to the spec? > > http://tinyurl.com/wwl2yk2 Those seem correct. P1-6 all are defined using IRIs and the...