Re: Verifiable Claims/DID User Needs and Use cases

Thank you, Josh, for starting this discussion. It seems to me that the Verifiable Credentials specification is written quite generally, but in order for a use case to apply, there should be parties corresponding to the various roles:

Who or what would be the credential subject, about which the claims are asserted?

Who would be the issuer of the credential (if I'm reading correctly, this could but usually wouldn't also be the credential subject)?

Who would be the verifiers - the parties who wish to determine that a credential has been validly issued?

Who would be the credential holder - the person who has the digital "wallet" from which credentials are retrieved at the request of a verifier?

I think it's clear that the genuine use cases will have answers to all of the above questions.

The format of the credential will depend on the use case (i.e., what kinds of claims can be asserted), and this, I think, is what would be put forward for standardization/registration so that there are common expectations among applications that use it.

Do these clarifications assist in clarifying your thinking? If not, let's discuss further.


On 1/13/20, 05:38, "Joshue O Connor" <joconnor@w3.org> wrote:

    Hi all,

    For me, while looking at the Verifiable Claims/DID specs with the view
    of thinking of user needs/use cases, as they relate to the needs of
    people with disabilities a question that comes to mind is why are
    VerClaims/DID user needs/cases, really any different from any secure,
    anonymous/private data transfer and verification requirements?

    The more I read about it I'm thinking that many of the issues around
    trust and the mechanisms to support them are pretty generic and broadly
    applicable to everyone.

    I'm happy to tease this out, thoughts?

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




________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Monday, 13 January 2020 12:52:49 UTC