Gregg Kellogg

In the frame, you’ll need to use some other term expanding to the same IRI for “driving_privilages”; other the full IRI it expands to, itself, or a compact IRI form....

The key is that the Framing algorithm works by first expanding the frame, which in the original case, results in the following: ```json [ { "http://example.org/vocab#info": [ { "@type": "@json",...

Sorry, comments messed up. If you put the full example in the playground, you can use the Permalink button to capture the state and add to this comment.

I see there's the problem you describe with the playground, but I'm not sure it's a spec bug. If you try it in my [Ruby distiller](http://rdf.greggkellogg.net/distiller?command=frame&format=jsonld&output_format=jsonld), you'll get the following...

The history of `@type` is long and complicated. In JSON-LD, the value of `@type` within the body of a document is typically used for holding an IRI, either of the...

@pasquale95 Sorry, we're both quite caught up in work on other specifications at the moment, haven't been able to devote more time to your issue. When I checked, it seemed...

Using the first frame, it the expanded "info" and "other" IRIs, the [playground seems to get the right output](https://json-ld.org/playground/#startTab=tab-framed&json-ld=%7B%22%40context%22%3A%7B%22ex%22%3A%22http%3A%2F%2Fexample.org%2Fvocab%23%22%2C%22ex%3Ainfo%22%3A%7B%22%40type%22%3A%22%40json%22%7D%2C%22ex%3Aother%22%3A%7B%22%40type%22%3A%22%40json%22%7D%7D%2C%22%40id%22%3A%22http%3A%2F%2Fexample.org%2Ftest%2F%23library%22%2C%22%40type%22%3A%22ex%3ALibrary%22%2C%22ex%3Ainfo%22%3A%7B%22author%22%3A%22JOHN%22%2C%22pages%22%3A200%7D%2C%22ex%3Aother%22%3A%7B%22publisher%22%3A%22JANE%22%7D%7D&frame=%7B%22%40context%22%3A%7B%22ex%22%3A%22http%3A%2F%2Fexample.org%2Fvocab%23%22%2C%22ex%3Ainfo%22%3A%7B%22%40type%22%3A%22%40json%22%7D%2C%22ex%3Aother%22%3A%7B%22%40type%22%3A%22%40json%22%7D%7D%2C%22http%3A%2F%2Fexample.org%2Fvocab%23info%22%3A%7B%7D%7D): ```json { "@context": { "ex": "http://example.org/vocab#", "ex:info": { "@type": "@json" },...

If the spec should be changed as suggested in https://github.com/digitalbazaar/jsonld.js/pull/506, that would be non-editorial. Probably the case for matching JSON Literals is more involved and requires something more than can...

What do you think this might look like? Framing serves as a "program by example", and I'm not sure what such a frame might look like.

This isn't a framing issue, rather it's a compaction issue. The issue should probably be moved to https://github.com/w3c/json-ld-api/issues for future tracking, but would constitute a normative change that would have...