Include a new codec from EBSI implementation

[samu-gataca]

Hi there,
I'm reaching out you to try to include the EBSI specification into the did key specification.
https://api-pilot.ebsi.eu/docs/specs/did-methods/did-method-for-natural-person#schema-of-the-method-specific-identifier

As you can see in the implementation, there is a multicodec approach

With this public key P-256
{ "crv": "P-256", "kty": "EC", "x": "Lyzu4hajYTyIBGeg31gneDkID1iiUapPONRPIrG8l4Y", "y": "iMLobYRurzjfgfJS-CbAPMA8xrVsA8QgQdimEu_W-yo" }
The DID generated is
did:key:z2dmzD81cgPx8Vki7JbuuMmFYrWPgYoytykUZ3eyqht1j9KbpaxuVPhKtEdpKCagY9XhyyyzNUPwwd4ookwVpAMkkMnKkNWWUJrSYPuShZp8dPKs17kBZqqfz3vDn3QQUT9EEiZN59AGSnDFxYLaRb2DawMkRhJth6U76FuKuWPZJE3v2G

In your specification there is the possibility to use this kind of codifications, so we are requesting to add this new one to the list included into the did method.

[alenhorvat]

Thank you @samu-gataca

[dmitrizagidulin]

@samu-gataca fascinating approach...

[samu-gataca]

Hi there, any new about this topic?
Regards

[reinkrul]

I'm opposed to this. It would make did:key implementations very cumbersome to make "complete": the DID method specification limits what you need to support (NIST-EC and RSA-family, and some other curves), but now you're including a container type (JWK) which can be anything JWK supports, including symmetric or private keys.

I.m.o., if you're handling JWKs, use did:jwk.