-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the definition of named graphs without @ keywords #481
Comments
I think this is very important for the Verifiable Claims work and would like to see it happen as well. |
Nanopublications are another use case. |
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. |
I've pasted a link to a patch to jsonld.js to support simple |
@dlongley can you correct that reference? |
Issue #549 mostly addresses this. |
@gkellogg, is a reference broken? Not sure what you mean. |
No, it seemed broken when checking at TPAC, it's fine. |
@gkellogg Thanks—could you clarify “mostly”? |
@RubenVerborgh perhaps not the issues themselves, but @dlongley's implementation limits these to anonymously named graphs, without even a BNode identifier. That fit's the Verifiable Credentials use case, but does not support actually named graphs. Doing this would require fixing the name in the term definition using a new keyword, such as |
Closed via #549. |
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:
where
metadata
andcontrols
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.
The text was updated successfully, but these errors were encountered: