Representation of codes to trigger a data exchange
Currently, there are 2 different "common" ways to represent the code for triggering a data exchange from the holder wallet and the RP/issuer. Depending on the use case the way of doing change, so in cross-device environments the chosen mechanism is the QR code and in the same-device environments the chosen mechanism is the Deep Link. About the Deep Link, there is another issue in the following link: #35 About the cross-device environment, we are very familiar with the QR code, and it's something we use to use in the real life. The problem comes when the information we want to represent is too big. This is the case when we want to represents a concrete protocol trigger avoiding one step. I mean, using OIDC4VCI as example, there are 2 different representations of the protocol: credential-offer and credential-offer-uri. In the first one we get all the information directly, and in the second one, we need to get the information from a concrete endpoint so we are calling an extra request. The problem comes, when the data we are representing is too big, most of the Scanning libraries are not able to read that QR codes, so the process is blocked.