decentralized-identity / presentation-request

Requirements Analysis and Protocol Design for a VC Presentation Request Format
Apache License 2.0
6 stars 2 forks source link

Separate `PresentationURL` from presentation request #3

Open awoie opened 4 years ago

awoie commented 4 years ago

To allow the presentation request and responses to be sent via DIDComm and to avoid duplicate attributes in the messages, we should refactor out the PresentationURL from the presentation request.

@tplooker what do you think?

rado0x54 commented 4 years ago

Hey Oliver, I share this input and feel that the communication endpoints are ideally abstracted behind a DID and resolved via DID comms.

awoie commented 4 years ago

Think of DIDComm providing the basic common structure that includes a reply address which could be anything (e.g., HTTPS, BLE). This can then be extended using additional properties that the presentation request needs.

I guess, it might be also possible to use the same name for the reply property but this feels redundant.

tplooker commented 4 years ago

@awoie I agree some of the information in these examples is more generally information at a messaging level that something like DIDComm could supply like how to reply