Re: Credentials Use Cases document created

Good use cases overall, Manu.

My favorite feature listed is probably composability, the ability to
present multiple credentials together to gain access to a system. I see an
opportunity to use multiple credentials to get over a hump where one system
knows an individual by one identifier, and another system knows that same
person by a different identifier. I think being able to offer multiple
credentials together for an authentication/authorization request, with
verified ownership of each, could let people more naturally negotiate
multiple facets of their identity on the web. Though I think this is
suggested by composability, I wonder if it rises to the level of being a
separate use case.

I also like Pre-authorization, which represents an individual's power to
act as both credentialee and credentialer in an environment.


----

And hello to this list! -- I hope to be able to make it to some of the
credential group's telecons in the future and meet some more of the people
in this community. I'm a web applications developer at Concentric Sky in
Eugene, OR, USA, working with Open Badges. I'm also working with the Open
Badges standard group at the Badge Alliance, and I am very interested in
making sure that the best methods of indicating earner identity without
leaking private information are represented in the badges community. It
looks like some very good work has been done leading to the formation of
this group, and I hope to help move it forward.

*Nate Otto, Developer*
concentricsky.com

On Fri, Oct 3, 2014 at 2:47 PM, Manu Sporny <msporny@digitalbazaar.com>
wrote:

> The use cases that we've been discussing have been put into a use cases
> document and published on the Credentials CG website:
>
> http://opencreds.org/specs/source/use-cases/
>
> This document is very preliminary and is tracking the discussions we're
> having on use cases in the weekly teleconferences, so expect the
> document to change based on the current state of discussion. Here's what
> has been done so far:
>
> 1. Create a basic use case document skeleton for the Credentials work.
> 2. Integrate the payments use cases, rewording them to be more
>    generalized credentials use cases where possible.
> 3. Create a Glossary and Roles section to define terminology that we
>    use.
> 4. Create a design criteria section that outlines basic systems design
>    principles that the group should be aware of when designing the
>    technical solution.
>
> It would be helpful if those on the mailing list could review all the
> use cases and provide feedback to the mailing list. Just a simple
> sentence or two on the use cases you are concerned about / want to
> change / want to add would be helpful. Tim has already demonstrated the
> sort of thing we're looking for as a group.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: High-Stakes Credentials and Web Login
> http://manu.sporny.org/2014/identity-credentials/
>
>