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

Use Case: student cards as Verifiable Credentials #8

Open
jchartrand opened this issue Aug 26, 2021 · 2 comments
Open

Use Case: student cards as Verifiable Credentials #8

jchartrand opened this issue Aug 26, 2021 · 2 comments

Comments

@jchartrand
Copy link
Contributor

@dmitrizagidulin as requested, putting this use case in as an issue for now.

Description

Issue student cards (student identity) as a Verifiable Credential that can live in a Wallet (like the DCC wallet).

For backwards compatibility, include (or generate as needed) a barcode that can be scanned by current readers on campus.

For future use, and for off campus use, include (or generate at verification time) a QR that likely encodes a URL that in turn when dereferenced will return the VC.

The student card VC will have to include a photo of the student, thereby making the VC too big to directly pass in a QR, hence the indirect passing via a URL.

Would be great if the wallet could provide a 'dead-drop' service whereby the wallet uploads a VC (more likely a VP) to some server that hosts the VP for just long enough that the verifier can retrieve it (a minute or two). And the wallet generates and shows a QR for that URL.

The wallet would have to be able to show the barcode (again, for backwards compatibility), and it would probably be nice to also show the student photo (although it is more important to show the photo within the verifier since that is where it can be confirmed to be real). The DCC Wallet uses React, so a kind of 'plug-in' react component for a student card VC would likely work well (as suggested by Dmitri on the DCC TWG call today - aug 26 2021)

@mlisle
Copy link

mlisle commented Aug 27, 2021

Rather than create a separate use case, I'd like to add a comment to @jchartrand -- it's pretty similar.

We'd like to grant access to our campus makerspaces using VCs. Theoretically, a VP could contain a credential that represents a skill/requirement (e.g. safety training completed) and a credential that represents some type of membership (e.g. student in X program/course).

@jchartrand
Copy link
Contributor Author

@mlisle Good point - we've also talked about similar kinds of authorizations at McMaster. The safety training often comes up, and things like having registered for a spin class in the gym for a term. Also bus passes on city buses - students can now take a bus by showing their student card, so an instantly verifiable version would be pretty cool.

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

No branches or pull requests

2 participants