Is "DID Resolver" the correct name for the piece of software that performs DID resolution?

[mwherman2000]

1. Is "DID Resolver" the correct name for the piece of software that performs DID resolution (element 41 in the INDY -ARM)?

I know the above question may seem like trivia but it's important because I next want to ask the following architectural question:

2. If so, what does a DID Resolver always return? Is the object/structure that is returned by a DID Resolver always going to be known as a DID Resolver Response (element 42)?

Related Issues:

• 'remote' vs 'local' DID Resolvers #28

[peacekeeper]

1. Yes, the piece of software that performs DID Resolution is called a DID Resolver

2. This is an open question, but I'd say DID Resolution can return different things, e.g. just the DID Document, or a DID Resolution Result (containing a DID Document plus metadata), or just part of a DID Document (such as a key or service endpoint). The type of output will probably depend on input parameters, e.g. a resultType input parameter. But it's really a bit too early for a definitive answer...

[mwherman2000]

I'd say DID Resolution can return different things

This is the specific reason I asked the first question:

• "DID Resolver" refers to a specific software component (and as such, has more specific boundaries and outputs)
• "DID Resolution" refers to a "process" and I feel it doesn't have well-defined boundaries and hence, it doesn't have well-defined (inputs and) outputs.

As developer, I want to see consistent outer wrapper/object (e.g. DID Resolver Response) ...and not a situation where it is sometimes one thing (a DID Resolver Response) and sometimes something else (a DID Document).

it's really a bit too early for a definitive answer...

Perhaps at the moment ...but do you believe this needs to be defined within the scope of this iteration of the DID Resolution spec?