Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

app directory with capabilities: first draft #266

Open
wants to merge 17 commits into
base: main
Choose a base branch
from

Conversation

isaacvetter
Copy link
Contributor

Maybe makes sense to split into verifiers and wallets/PHRs.

@isaacvetter isaacvetter changed the title create app directory with capabilities: first draft Oct 29, 2021
Copy link
Contributor

@jmandel jmandel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a page like this is useful -- would be good to factor into separate sections for "Wallet" and "Verifier" apps because I think they're almost entirely disjoint.

@isaacvetter
Copy link
Contributor Author

Are CommonPass and CLEAR wallets/holders? Apps with in-app verification will always tend to also have wallet features.

@jmandel
Copy link
Contributor

jmandel commented Oct 29, 2021

The split you've made in ca840ca helps from my perspective, thanks!

Apps with in-app verification will always tend to also have wallet features.

Sure -- I think the key question is whether it's an app designed to be run by the data subject, to store/manage/share their own records.... or an app designed to be run by a third party to validate the records of customers/guests/clients.

@isaacvetter
Copy link
Contributor Author

So, for example, a Marriott app that could both access, store, verify and display an SHC that was downloaded onto a consumer's device would be a verifier; because, it's primary purpose is verification. Makes sense to me!

@jmandel
Copy link
Contributor

jmandel commented Oct 29, 2021

I think that's a good principle (though you've read more into my words than I meant; I'm sure this is a taxonomy we'll need to keep thinking about and revising and it won't be perfect, but we'll keep chipping away).

@jmandel
Copy link
Contributor

jmandel commented Nov 1, 2021

@jpp9 @jdkizer9 are you comfortable merging this? If not

  • Are there changes you want to see?
  • Is there someplace else you'd like this to live?

@jpp9
Copy link
Contributor

jpp9 commented Nov 3, 2021

sorry for being slow on this. i like the addition. my one hangup: i think some of the info in the table may not be right, and i don't want to speak for other app makers. can we reach out and get them to provide the info? or leave them out, reach out, and ask them to update the table via PRs?

@jmandel
Copy link
Contributor

jmandel commented Nov 3, 2021

Maybe some disclaimer language that this is a best-effort compilation and that we invite PRs / feedback / corrections / additions?

@jpp9
Copy link
Contributor

jpp9 commented Nov 3, 2021

that would work for me

@jmandel
Copy link
Contributor

jmandel commented Nov 9, 2021

This looks good to me! @jpp9 are you able to merge?

verifiers & apps.md Outdated Show resolved Hide resolved
@jmandel
Copy link
Contributor

jmandel commented Dec 1, 2021

I think we should merge this and we can improve it over time.

@christianpaquin
Copy link
Contributor

FYI, the demo portals's source is located in the health-cards-tests repository, under the MIT license.

verifiers & apps.md Outdated Show resolved Hide resolved
@p9g
Copy link
Contributor

p9g commented Jan 10, 2022

remove spaces and ampersand from the filename. suggest "verifiers-and-apps.md"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants