search

IDunion / indy-did-resolver

Resolver for the did:indy method
Apache License 2.0
8 stars 7 forks source link

DID Document / Ledger Object metadata #10

Closed domwoe closed 2 years ago

domwoe commented 2 years ago

The resolver should be able to not only return the actual DID Document or Ledger Object, but also metadata.

We need to define what metadata would be useful for a consumer and provide an option to resolve with metadata.

For example, the did:sov universal resolver driver provides the following metadata:

Map<String, Object> didDocumentMetadata = new LinkedHashMap<> ();
        didDocumentMetadata.put("network", indyConnection.getPoolConfigName());
        didDocumentMetadata.put("poolVersion", indyConnection.getPoolVersion());
        didDocumentMetadata.put("submitterDid", indyConnection.getSubmitterDid());
        didDocumentMetadata.put("nymResponse", gson.fromJson(jsonGetNymResponse, Map.class));
        didDocumentMetadata.put("attrResponse", gson.fromJson(jsonGetAttrResponse, Map.class));

Source

There's also a section in the DID core spec about recommended properties: https://www.w3.org/TR/did-core/#did-document-metadata

paulbastian commented 2 years ago

This should be addressed in the Indy DID Method Spec first.

paulbastian commented 2 years ago

We should include metadata from the Indy-VDR RequestResult data