Instead of offloading all resolution related tasks to a registry instance (e.g. when calling validation functions such as utils.validateDigestible), a simple resolution function would suffice. The end goal is to be able to resolve identities anchored on different networks (e.g. different DID method, custom deployments) without too much overhead, and to better outline the responsibilities of the Registry class.
Note: This is a long standing issue which was addressed in #327 (the comments provide valuable context), and is currently part of 4.0-beta1. In order to simplify the review and feedback process, we decided it can be re-implemented (reusing existing code where possible) as a separate PR.
For reference purposes, please see #327, and the corresponding issue, #326
Description
Instead of offloading all resolution related tasks to a registry instance (e.g. when calling validation functions such as
utils.validateDigestible
), a simple resolution function would suffice. The end goal is to be able to resolve identities anchored on different networks (e.g. different DID method, custom deployments) without too much overhead, and to better outline the responsibilities of the Registry class.Note: This is a long standing issue which was addressed in #327 (the comments provide valuable context), and is currently part of 4.0-beta1. In order to simplify the review and feedback process, we decided it can be re-implemented (reusing existing code where possible) as a separate PR.
For reference purposes, please see #327, and the corresponding issue, #326