Add DID Doc path to indy-vdr-proxy

[andrewwhitehead]

Synthesize a DID Doc by fetching the key and endpoint for a DID

[andrewwhitehead]

On hold until DID Core specification advances, to avoid getting locked into a non-standard format.

[c2bo]

There was some discussion on the topic of synthesizing a DID Doc in the scope of the did:indy implementation. My current understanding would be that the desired outcome would be for indy-vdr to directly support providing a did document (via native API calls and also via the proxy).

With the did:indy spec, there needs to be some discussion on the functionality of such an additional layer in indy-vdr:

• Should this be part of indy-vdr or somewhere further up in the aries implementations
• How much validating should be done in indy-vdr (e.g. https://github.com/dbluhm/pydid)

I think it makes sense to use this issue to discuss these aspects @domwoe @swcurran ? My opinion would be:

• Provide a call for a did doc natively in indy-vdr via additional API
• Do very minimal checking here

[c2bo]

Our current plan is to start with a did:indy compliant implementation for did docs here: https://github.com/IDunion/indy-did-resolver and move parts into indy-vdr after some testing.

[c2bo]

I guess this can be closed with #84?