Re: Verifiable Claims/DID User Needs and Use cases

Scott Hollier wrote on 15/01/2020 09:15:

Thanks for the input Scott.

> 1) Creating an identifiable credential, i.e. drivers license, passport, ID et c
> 2) Certifying an existing identifiable credential
> 3) Using multiple verifiable credentials to obtain another, e.g. using passport to open a bank account or get a drivers licence; and
> 4) Preventing identity theft of said credentials

I guess, speaking to my original point, they all seem like generic uses 
cases that are applicable to e'one.

> After reading through all the W3C documents and e-mail thread I'll admit that my knowledge is still a bit limited in this space,

We are all learning!

> but where one of the challenges may be for people with disabilities at the moment is trying to initially create an identifiable credential in the first place, especially if the creation of that credential relies on physical world information. Is the digitisation of physical credentials in scope?

That is something interesting, but raises the question to do what? If we 
can articulate the user need then we can look at some requirements.
> Apologies if this is too much of a tangent, but I’m thinking of the challenges in having to currently set up an online account with an organisation at requires inaccessible scanned PDFs

That's an interesting one. Adobe have digital certificates and a 
signature manager and what not, that may have some Verification foo 
baked in. I'm thinking now more about the provenance of any PDF, that 
can be verified as being trustworthy (slightly different from what you 
are talking about).

This could bring up requirements to meet a user need around verifying 
the provenance of any 'offline documents'.

Looking forward to discussing, thanks Scott.

Josh

> of qualifications, government ID cards, finding an appropriate person  to certify documents etc. I appreciate the endgame here is that none of these things would be necessary if identified credentials were effective and decentralised applications continue to evolve, but the logistics in getting to that point may require accessibility guidance for organisations unindividuals.


-- 
Emerging Web Technology Specialist/Accessibility (WAI/W3C)