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
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.
The text was updated successfully, but these errors were encountered:
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.
Did resolvers can return a number of properties in addition to the
didDocument
. The Universal Resolver hosted by DIF returns e.g.: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.
The reasoning of making the
didDocument
also configurable are use cases where the interest are details about e.g. the used resolver or method.The text was updated successfully, but these errors were encountered: