Closed EzequielPostan closed 1 year ago
It was brought to our attention that
based on W3C DID Spec the service Endpoint can be a string, a map or a set. And based on DIDComm v2 spec, for the routing protocol, the serviceEndpoint should be as a list of objects like: "serviceEndpoint": [{ "uri": "https://example.com/path", "accept": [ "didcomm/v2", "didcomm/aip2;env=rfc587" ], "routingKeys": ["did:example:somemediator#somekey"] }]
based on W3C DID Spec the service Endpoint can be a string, a map or a set. And based on DIDComm v2 spec, for the routing protocol, the serviceEndpoint should be as a list of objects like:
"serviceEndpoint": [{ "uri": "https://example.com/path", "accept": [ "didcomm/v2", "didcomm/aip2;env=rfc587" ], "routingKeys": ["did:example:somemediator#somekey"] }]
We need to update the prism method spec to support these maps
It was brought to our attention that
We need to update the prism method spec to support these maps