Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Select top-level properties from Resolver #59

Open
BernhardFuchs opened this issue Nov 26, 2020 · 1 comment
Open

Select top-level properties from Resolver #59

BernhardFuchs opened this issue Nov 26, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@BernhardFuchs
Copy link

Did resolvers can return a number of properties in addition to the didDocument. The Universal Resolver hosted by DIF returns e.g.:

  • didDocument
  • resolverMetadata
  • methodMetadata
  • content
  • contentType

Atm there is no standardized way to selectively include/exclude those top-level properties. Depending on the use case or available resources this could be a useful feature.

It could be implemented by introducing a query parameter e.g.

# include for whitelisting properties
?include=didDocument,resolverMetadata,contentType

# exclude for blacklisting properties
?exclude=didDocument,methodMetadata

The reasoning of making the didDocument also configurable are use cases where the interest are details about e.g. the used resolver or method.

@peacekeeper
Copy link
Collaborator

Coming back to this issue.. In the section on HTTP(S) Binding, it is possible to either retrieve just the DID document, or the full DID resolution result (DID document + metadata), by using the HTTP "Accept" header to request a certain media type:
https://w3c.github.io/did-resolution/#bindings-https

It would definitely also be possible to introduce one or more DID resolution options that allow more fine-grained selection of what should be returned. Not sure though if there is enough demand for such a feature though.

@peacekeeper peacekeeper added the enhancement New feature or request label Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants