Orie Steele

TL;DR; this work is older, and does not reflect the current wg consensus.

Yes please, there needs to be a very clear encoding and signature documentation. I would say starting with JWE is a requirement for adoption of any sort. Regarding bloat/size... its...

Related work on edv using JWE as well... would be nice to sync all of this: https://github.com/digitalbazaar/encrypted-data-vaults/issues/5

Note the kid format... ``` keyAgreementKey.id = `${did}#${keyAgreementKey.fingerprint()}`; ``` I think we really need to get this id handling stuff into the did spec with some `SHOULD` language... I see...

PR is up https://github.com/decentralized-identity/.well-known/pull/92

Assuming you use the universal wallet interop spec, or similar... ``` const getDidConfiguration = async (wallet) => { const dids = Array.from( new Set([ ...wallet.contents.map((k) => { return k.controller; }),...

The current resource structure: ```json { "@context": "https://identity.foundation/.well-known/contexts/did-configuration-v0.0.jsonld", "entries": [ VC_DATA_MODELs ] } ``` Proposed structure: ```json { "@context": "https://identity.foundation/.well-known/contexts/did-configuration-v0.0.jsonld", "linked_dids": [ VC_DATA_MODELs ], "supported_protocols": [ PROTOCOLs], "credential_manifests": [ CREDENTIAL_MANIFESTS]...

potential issue is that the supported protocols implicitly apply to all linked dids...

Link to related hackmd...https://hackmd.io/QCJ3WDcLSXWp8t3hAQ387A

We can resolve this issue by adding a member of the `supported_protocols` objects called `linked_dids`... which tells you which linked did support which protocols... in the future... this kind of...