Allow the definition of named graphs without @ keywords

[RubenVerborgh]

I'd like named graphs to become first-class citizens of JSON-LD 1.1, such that it becomes really straightforward to separate things in graphs. One reason is the separation of data, metadata, and controls, but there are several others.

If I'm not mistaken, at the moment it's not possible to define something like:

{
    "members": [ { "@id": "x" }, { "@id": "y" } ],
    "metadata": {
       "memberCount": 12300
    },
    "controls": {
        "nextPage": "/members/?page=2"
    }
}

where metadata and controls in fact correspond to different graphs.

Note also the similarly of this use case with what application/hal+json does with _links and _embedded.

It seems that #195 discusses something related, but that one seems specific for containers.

[dlongley]

I think this is very important for the Verifiable Claims work and would like to see it happen as well.

[RubenVerborgh]

Nanopublications are another use case.

[msporny]

Agreed. This is also very important for the Linked Data signatures work:

{
    "graphData": [ ... ],
    "graphProvenanceData": { ... },
    "graphSignatureData": { ... }
}

... which is important for the Verifiable Claims work and the Linked Data and Distributed Ledgers work. I'd really like to see a solution for this in JSON-LD 1.1 as our current approach requires the use of '@graph', which has been balked at, which ends up being a distraction, by a number of JSON developers.

[dlongley]

I've pasted a link to a patch to jsonld.js to support simple @graph containers here:

#195 (comment)

[gkellogg]

@dlongley can you correct that reference?

[gkellogg]

Issue #549 mostly addresses this.

[dlongley]

@gkellogg, is a reference broken? Not sure what you mean.

[gkellogg]

No, it seemed broken when checking at TPAC, it's fine.