-
Notifications
You must be signed in to change notification settings - Fork 45
Create JSON-LD context for DID spec #9
Comments
A preliminary JSON-LD Context has been created and is published here: https://w3id.org/did/v1 The repo link is here: https://github.com/w3c-ccg/did-spec/blob/05af3fe12eae7c8818ff2b039e1d52a1babd9b28/did-v1.jsonld The issue has been addressed, closing. |
My JSON-LD library doesn't support 1.1 and throws an error on the |
No, we can't do that /and/ generate the properly structured claims and signatures for DIDs or Verifiable Credentials. There are multiple problems that we'd recreate by using JSON-LD 1.0 -- we've been wanting to move to named graphs for signatures for a while -- much cleaner. There is full 1.1 support in the Javascript and Python packages. I expect Java will follow suit as soon as they can. The better option may be to add named graph support in your JSON-LD library in an experimental branch because I think that's the only 1.1 option you'd need. @gkellogg -- any ideas on if the Java implementation is planning an upgrade to 1.1? |
I’ve seen various 1.1 updates on https://github.com/jsonld-java/jsonld-java, but I don’t know if there’s a concerted effort here (see jsonld-java/jsonld-java#219). Also, I haven’t seen them on the CG calls. Lobbying be the user base is probably most effective, short of doing a PR. There are enogh examples of 1.1 compliant systems out there that updating jsonld-java should be straightforward. Cc /@ansell |
Hi Greg/all, I have been out of the space for a while (>2 years), but have been accepting and merging PR's and doing trivial fixes to keep it going. Would appreciate any help with maintenance or PR's to keep it up to scratch with upcoming/new standards. Thanks, Peter |
Closing this issue, noting that the Java implementation doesn't support JSON-LD 1.1 and that that is a separate issue. This issue was about having a DID JSON-LD context, which we have now. Closing. |
We need to create a JSON-LD context for the DID spec.
The text was updated successfully, but these errors were encountered: