search

aviarytech / jff-didcomm-issuance

1 stars 0 forks source link

How is your flow? #2

Open vongohren opened 1 year ago

vongohren commented 1 year ago

Please make a simple swimlane work like Brian have and add it here, so we can map things out.

Here is Diwala flow.

Screenshot 2022-10-14 at 15 57 58 Screenshot 2022-10-14 at 15 58 09

@brianorwhatever can you add yours here as well? So we have a simple issue to scroll and compare on. Just felt easier than doing a PR

brianorwhatever commented 1 year ago

Issue Credential image

nklomp commented 1 year ago

Sphereon:

jmarquez-cs commented 1 year ago

Fathom 195895352-70a5d764-5cd8-4629-9335-991320e1d914

keichiri commented 1 year ago

Pocket. This might change soon, as acapy is transitioning between protocols

swimlanes-770e4d877cf59c3c7820f13965c6793e

vongohren commented 1 year ago

It seems that we have a very heavy leaning towards WACI exchange.

Where everyone have offer, request and issue.

But it is the first two messages that is currently a bit out of bounds. Diwala can change this to align to the three actors in this group. But how flexible are you guys @keichiri ?

Or are there other ways we can go around this? With multi support of messages, which might sound complex?

AlexAndrei98 commented 1 year ago

sequenceDiagram issuer->>holder: https://didcomm.org/out-of-band/2.0/invitation holder->>issuer: https://didcomm.org/issue-credential/3.0/request-credential issuer->>holder: https://didcomm.org/issue-credential/3.0/issue-credential holder->>issuer: https://didcomm.org/issue-credential/3.0/ack

vongohren commented 1 year ago

Decsision from 31st of October

We will go with WACI profile since it is A profile, and we are not making anything up, and we wont spend time making a new one to cater to everyone. That adds to much time.

Diwala and RootsID will cater to WACI as Spehron, AviaryTech and Fathom supports from their pictures.

@keichiri how much controll do you guys have on the implementation you are running to upgrade the code?