+1 to Marcos' comment. In my opinion, the approach Marcos took for installable webapps is the best one: 1) document how it is approached in current solutions 2) try to quantify how common he different approaches are 3) extract use cases and requirements from what was learnt in steps 1 and 2 On Thu, Mar 27, 2014 at 6:43 PM, Marcos Caceres <w3c@marcosc.com> wrote: > On March 26, 2014 at 7:59:00 PM, Natasha Rooney (nrooney@gsma.com) wrote: >> > Hi all! >> >> I have done some work to the github repo! You can now find ‘use-cases’ >> and ‘considerations for standards’ in their own files and I have >> added a references section for the references I have found (please >> add more!). >> IDENTITY REPO: https://github.com/w3c-webmob/identity/ >> >> Please send pull requests as you see fit, and when we have an update >> from the Payments CG (and a report from the Payments Workshop) >> we’ll get the next set of actions sorted. > Thanks for getting this started, Natasha. > Some initial reactions... > Personally, I would prefer that we don't use hypothetical use cases (as they then to set up unrealistic strawpersons). Identity is a fairly well understood problem - so it should be possible to just look at various mainstream solutions and how they are integrated into various OSs and systems.
Received on Thursday, 27 March 2014 19:02:03 UTC