Support for resolving other types of Ledger Objects

Hello,

Some DID Methods, e.g., Indy DID Method, store other types of objects on their ledgers, such as Credentials Schema and Revocation Registry definitions.
Currently the Universal Resolver does not support such objects. For example, executing the following command returns an error message "Cannot parse DID".
`curl -X GET http://0.0.0.0:8080/1.0/identifiers/did:indy:sovrin:F72i3Y3Q4i466efjYJYCHM/anoncreds/v1/SCHEMA/npdb/4.3.4`

Have you planned to add support for resolving other types of ledger objects?
If not, is there another DIF project or working group working on this problem?

Cheers,
Vasil Papanchev

Start by reproducing the curl request for the Indy schema identifier and trace how the resolver handles the path after the DID. Review the existing resolution flow and driver behavior for non-DID ledger objects. Done means the requested ledger object can be resolved without the “Cannot parse DID” error, with coverage for the example identifier.

Written by the indexing model from the issue text.