> On Jan 26, 2016, at 2:58 PM, Shane McCarron <shane@halindrome.com> wrote: > > As we discussed briefly in the call today, we are gaining traction on the use cases document. Gregg, Brian, Daniel, and I will be working on it going forward. > > The general approach I have taken to get this rolling is: > • Start from the CCG use case document at [1] Hi Shane, Is there emerging consensus from interviews on core use cases (that may be a subset of the CG use cases doc)? Ian > • Restructure to be more like the Web Payments Working Group use cases document at [2] > • Organize around the major operations that can be peformed on / with a Verifiable Claim. > • Extract core requirements with associated use cases from the CCG Google Doc use case document [3] and the CCG anonymized use cases that came in from the industry survey as reflected at [4] > • In parallel, write up a *simple* illustration of a basic flow for a Verifiable Claim in the wild that we can use as an introduction to the concepts. > There is still a lot of work to do here. I will be coordinating closely with the other volunteer editors. We are operating on github, using branches and pull requests. Feel free to observe, comment, or assist! > > [1] http://www.opencreds.org/specs/source/use-cases > [2] https://www.w3.org/TR/web-payments-use-cases/ > [3] https://docs.google.com/document/d/1GySrTXAYpwa4vDPsGE3BMA42FwIAqAyLGigKuKUTGks/edit# > [4] http://opencreds.org/presentations/2015/w3c-tpac/anonymized.html > -- > -Shane -- Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs Tel: +1 718 260 9447
Received on Tuesday, 26 January 2016 21:01:42 UTC