You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to recent changes in the DID Core context file, we now need to make sure that the key suite contexts are getting added to the outputted DID Document on resolution. In ION specifically, DID Documents are limited to JWKs so I believe we should be able to add the URL https://w3id.org/security/suites/jws-2020/v1 for LDS-JWS2020 which includes the context definition for JsonWebKey2020.
For service endpoints, we may need to allow the service endpoint to pass a context URL in as well in the internal sidetree data model so that the contexts are properly working. However, this introduces some difficulties on preventing garbage-in-garbage-out scenarios and more thought will be needed on it.
Not sure if this should be filed here or in https://github.com/decentralized-identity/sidetree/ so going to post in both and cross link.
Due to recent changes in the DID Core context file, we now need to make sure that the key suite contexts are getting added to the outputted DID Document on resolution. In ION specifically, DID Documents are limited to JWKs so I believe we should be able to add the URL
https://w3id.org/security/suites/jws-2020/v1
for LDS-JWS2020 which includes the context definition for JsonWebKey2020.For service endpoints, we may need to allow the service endpoint to pass a context URL in as well in the internal sidetree data model so that the contexts are properly working. However, this introduces some difficulties on preventing garbage-in-garbage-out scenarios and more thought will be needed on it.
Cross post link: decentralized-identity/sidetree#1144
The text was updated successfully, but these errors were encountered: