Markus Sabadello

I agree with @wip-abramson 's suggestion above. This should say something like "resolve did:example:123" with "versionTime" passed to the resolver in the resolutionOptions. Unassigning myself from this for now, maybe...

Looks useful @mccown , thanks. > DID documents contain data elements, such as: public keys, service endpoints, and verification methods **(i.e., DID Method)** associated with a DID. This sounds like...

Also, I propose to add the following paragraph to the first answer: > In addition to exposing the DID document, the DID Resolution specification also defines two metadata structures. One...

I think the questionnaire has been filled out.. Can we close this?

@erdemonal11 This makes sense to me.. Do you perhaps want to try and write a Pull Request which addresses this?

We have some language about this in a section about DID Document Metadata: https://www.w3.org/TR/did-resolution/#output-documentmetadata (Actually this section should probably be merged into https://www.w3.org/TR/did-resolution/#did-document-metadata). > The sources of this metadata are...

> > (Actually this section should probably be merged into https://www.w3.org/TR/did-resolution/#did-document-metadata). > > Is this true of the whole section 8 - https://www.w3.org/TR/did-resolution/#did-resolution-result And potentially section 9 - https://www.w3.org/TR/did-resolution/#did-url-dereferencing-result Yes,...

> Since [#164](https://github.com/w3c/did-resolution/pull/164) has been merged, marking this pending close That PR re-arranged and consolidated some information about metadata, but I don't think it really addressed this issue here. The...

In my mind there should be a distinction between the resolve() function and a DID method's "Read" operation. The former is how a client invokes a resolver, and the latter...

> so it's clear that `Remote` and `Local` qualify the DIDs and not the Resolvers. Hmm that's not my understanding.. I don't know what a "remote DID" or a "local...