-
Notifications
You must be signed in to change notification settings - Fork 10
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
versionId
/versionTime
are not defined for DID resolution
#66
Comments
I think this specification implies that DID parameters can be used as DID Resolution Input Metadata properties (now called DID Resolution Options in DID Core), in https://w3c-ccg.github.io/did-resolution/#dereferencing-algorithm:
These properties/options are then passed to the DID method for a Read operation: https://w3c-ccg.github.io/did-resolution/#resolving-algorithm
Maybe it would help to propose registering |
Hello, I agree with @clehner 's interpretation.. The intention is that And yes the idea was also that if you dereference() a DID URL, then the DID parameters in the DID URL are passed as resolution options to the resolve() / resolveRepresentation() functions. I just pushed some commits that harmonizes the language in this spec with DID Core (e.g. "input metadata properties" -> "resolution options"). |
I wonder if we can address @clehner's proposal by adding a sentence to the DID Resolution Options - https://w3c.github.io/did-extensions/resolution/#did-resolution-options - that states something like.
|
I like this suggestion @wip-abramson |
Happy to submit a PR for this to DID extensions, if we are happy this is the direction to go in. |
https://w3c-ccg.github.io/did-resolution/#versioning says:
DID resolution is defined for a DID, not a DID URL, so the only place where such parameters could go is in the DID Resolution Input Metadata, but currently the only property defined there is
accept
.Am I missing something?
The text was updated successfully, but these errors were encountered: