Define Universal Wallet objects for presentation submissions in the universal wallet interop spec about traceability-interop HOT 12 CLOSED

An alternative to preserving the "challenge" is "issuing a challenge token from the verifier"... that can then be verified instead of looked up...

this approach is taken in https://github.com/decentralized-identity/waci-presentation-exchange

from traceability-interop.

Feels like we have answered this question, by saying: "anyone can present anything"

... for now.

Noting that this is different than the authorization strategy for the channel... this is:

"Can this holder present these credentials"... or "is this holder presenting credentials that I expect them too"

from traceability-interop.

Leave this open until we can untangle the "VP" authorization vs "HTTP" authorization issues.

from traceability-interop.

@OR13 to retitle the issue and provide concrete examples of what we mean.

from traceability-interop.

I can make an example for this to make it more tangible

from traceability-interop.

I don't grok the question. The other repos don't help me much. Maybe the relevant chunks of those other pages could be brought inline to the question, and some meat added to the question itself?

from traceability-interop.

@nissimsan

from traceability-interop.

Discussed on Aug 24 call, @nissimsan to provide examples

from traceability-interop.

Incorrect interpretation:
How does a holder acting like a verifier store their data structure.
CCG doesn't bother with this, universal wallet does. Meta data should include: who presented, when did I store it.
Seems not relevant for this group.

from traceability-interop.

To be closed.

from traceability-interop.

We can't actually enforce this.

from traceability-interop.

Out of scope, because we can't enforce. (Might be fodder for a Best Practices doc.)

from traceability-interop.