Compelling Credentials Use Cases
Earlier this year, your organization noted their interest in a standardized ecosystem for issuing, storing, and consuming independently verifiable credentials related to education, finance, government, job training, healthcare, and a variety of other market verticals.
The purpose of this questionnaire is to gather the most compelling credentials use case from your organization. Hearing use cases directly from your organization is an important part of expressing the need for standards work in this area to W3C management.
If you are unsure about what a Credential is, this document may help you frame your response:
1. What is the name of your organization?
2. What is your name?
3. How can we contact you about your use case?
Please provide an email address (preferred), or a phone number.
4. What is the most compelling Credentials use case that your organization would like to see better integrated into the Web that would be helped by one or more new standards in the space?
We are looking for business-driven use cases, not "neat ideas". Please make sure your use case includes the following information: 1) A 1-2 sentence summary of the actions the person in the scenario performs, 2) Any pertinent details about what the person is trying to accomplish in your ecosystem
5. Are there other use cases that your organization feels are important? If so, what are they?
6. What types of stakeholders would need to cooperate for your use cases to be achievable?
7. What digital credentialing capabilities does your organization see as valuable?
Pick as many as applies to your organization
Issuing verifiable credentials (e.g. educational transcripts, professional licenses, digital government IDs, etc.)
Storing verifiable credentials at arbitrary identity providers/vaults
Requesting verifiable credentials from people and organizations
Revoking issued credentials
Web Browser APIs for issuing, storing, and consuming credentials
User-centric credentials (credential holder is in control of their own credentials)
Privacy-enhanced credentials (ensuring privacy when sharing certain credentials)
Credential portability (credential holder should be able to easily move credentials from one provider to another)
8. Which of these technologies do you use today to achieve your current credentialing needs?
I don't know
Open Badges (e.g. expressing credentials)
SAML 2.0 (e.g. Federated SSO, Shibboleth)
OpenID Connect (e.g. federated login)
OAuth 2.0 (e.g. security)
SAML 1.0 (e.g. SSO, Shibboleth)
OpenID 1.0 (e.g. federated login)
OAuth 1.0 (e.g. LTI)
Secure FTP (e.g. transmitting credentials, scanned credential documents, etc.)
PDF (e.g. scanned credential documents, digitally signed credential documents, etc.)
Email (e.g. transmitting PDFs of credentials)
x.509 Certificates (e.g. authentication)
9. Of the technologies that you use above, do they address all of the capabilities your organization sees as valuable, or are new technologies needed?
The technologies listed above meet the credentialing needs of my organization.
The technologies listed above meet some of my organizations credentialing needs, but not all of them
The technologies listed above DO NOT meet the credentialing needs of my organization.
I don't know
10. What are the limitations (if any) of the current technologies that you use for credentials?
11. If the W3C were to start a Working Group to address your credentials use cases, would you likely participate?
Yes, and my organization is a W3C member
Yes, and my organization would become a W3C member to do so
Maybe, it depends on staff and funding availability for W3C membership
No, we do not have the available staff or funding to participate in standards work at W3C
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google.
Terms of Service