JWKs are a foundational component of many identity and credentialing systems.
The did:jwk method could be extended with "longer form" identitifer schemes that address these specific use cases.
For example:
Content Addressing
Its possible to compress a did:jwk using content addressing... this can be accomplished without overloading did:jwk but leveraging the naming convention used for multiple network based methods, for example:
did:jwk:ipfs:cid -> cid -> did:jwk:encoded
This would leverage any content id based storage network to shorten the did, but at the cost of a different resolution process for jwk:ipfs when compared to jwk.
JWKs are a foundational component of many identity and credentialing systems.
The did:jwk method could be extended with "longer form" identitifer schemes that address these specific use cases.
For example:
Content Addressing
Its possible to compress a
did:jwk
using content addressing... this can be accomplished without overloadingdid:jwk
but leveraging the naming convention used for multiple network based methods, for example:did:jwk:ipfs:cid
-> cid ->did:jwk:encoded
This would leverage any content id based storage network to shorten the did, but at the cost of a different resolution process for
jwk:ipfs
when compared tojwk
.WebAuthN
TODO ?
OIDC
TODO ?