Updates to QR page

[esune]

Initial redesign of QR code page

[swcurran]

Not a huge fan of the "What's being asked for" section, but John needs to drive that. I've offered a suggestion on the layout. The rest looks good.

I'll leave the code review to Wade.

[swcurran]

Suggestion for cleanup of the "What's being asked for" -

• Get rid "claim" everywhere.
• Collapse the triplet into "Source Credential"
• Make the DID a link that on click pops up the DID
  • could put a link to resolve the DID on the popup.
• Put an "OR" between the triplets.

Something like:

Field: email
Restrictions:
 - Source Credential: verified-email:1.2.2 DID -OR-
 - Source Credential: iiw_attendance:1.2.4 DID -OR-
 - Source Credential: verified_person:1.22 DID

Would have to handle things like no restrictions, restrictions by schema, restrictions by cred def, restrictions by name, restrictions by value, etc.

[esune]

...
Would have to handle things like no restrictions, restrictions by schema, restrictions by cred def, restrictions by name, restrictions by value, etc.

I need to put some thought into this, as I believe it ties in with the updates described in #34 (we don't currently support restrictions by value). We also need to be able to show requested_predicates.

@swcurran would it be okay to track those changes in a separate issue?

[swcurran]

Yup. That would be best. Just didn't want to leave it in Rocketchat.

…

On Tue, Jan 21, 2020 at 3:55 PM Emiliano Suñé ***@***.***> wrote: ... Would have to handle things like no restrictions, restrictions by schema, restrictions by cred def, restrictions by name, restrictions by value, etc. I need to put some thought into this, as I believe it ties in with the updates described in #34 <#34> (we don't currently support restrictions by value). We also need to be able to show requested_predicates. @swcurran <https://github.com/swcurran> would it be okay to track those changes in a separate issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#35?email_source=notifications&email_token=AAHYRQXP5HSWDTNONWFBA3TQ66DOTA5CNFSM4KJ36S4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJRXCSI#issuecomment-576942409>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHYRQTCSQ4UMWZGFDK5T3DQ66DOTANCNFSM4KJ36S4A> .

-- Stephen Curran Principal, Cloud Compass Computing, Inc. (C3I) Technical Governance Board Member - Sovrin Foundation (sovrin.org) *Schedule a Meeting: **https://calendly.com/swcurran <https://calendly.com/swcurran>*