Closed c2bo closed 5 months ago
Besides the open point with the context for the DID Communication service, I think this is a valuable PR. It is really painful to see lots of invalid JSON-LD examples everywhere
Do we want to merge this in its current state as an example and adjust it once we start touching these points in the aries implementations (and need a valid context for the service endpoint according to https://github.com/hyperledger/aries-rfcs/tree/main/features/0067-didcomm-diddoc-conventions) ?
I think it would be good to merge it. Those that know more about contexts and the state of the DIDComm contexts can weigh in before or after. Let's wait a few more days for feedback or other approaches to this one.
@TelegramSam -- comments?
The main focus was to try to create fully resolvable json-ld and updating to be compliant to the examples given in did-core Fixes #51
Signed-off-by: Christian Bormann ChristianCarl.Bormann@de.bosch.com