Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JSON-LD Parsing Error Blocking VC Data Model Integration
See original GitHub issuehttps://uniresolver.io/#did:btcr:xxcl-lzpq-q83a-0d5
https://raw.githubusercontent.com/OR13/self/master/ddo.jsonld
Per https://www.w3.org/TR/vc-data-model/#proofs-signatures-0
If the cryptographic suite expects a proofPurpose property, it is expected to exist and be a valid value, such as assertionMethod.
However, assertionMethod is stripped from the btcr did document above by the universal resolver… this cause verification of credentials to fail when using the universal resolver as a document loader.
The solution is not to remove any of the properties defined in https://www.w3.org/ns/did/v1
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ran into this while using this context:
"https://w3id.org/security/v2"since it has"version": 1.1. Maybe it should use https://github.com/filip26/titanium-json-ld instead since that supports json-ld 1.1?https://raw.githubusercontent.com/OR13/self/master/ddo.jsonld seems to have these
@contexts:Neither of those define
assertionMethod.