- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Thu, 2 Jul 2015 23:18:36 +0200
- To: public-rww <public-rww@w3.org>
- Message-ID: <CAKaEYhKiSMk-tcHEkRGWKCEqSYr5O4_iZSHUV8DS_OZ1V2VF4w@mail.gmail.com>
FYI: ---------- Forwarded message ---------- From: Manu Sporny <msporny@digitalbazaar.com> Date: 2 July 2015 at 23:13 Subject: Browser-based Credential API To: Credentials Community Group <public-credentials@w3.org> Hi all, We were able to finally get around to documenting the browser-based Credentials API. The Credentials API enables a Web developer to create new DIDs for an entity, store credentials, and request credentials. The basic API is outlined below, separated by different actors in the system: Credential issuer API: * navigator.credentials.store(identity, options) Credential consumer API: * navigator.credentials.request(query, options) Identity provider APIs: * navigator.credentials.registerDid(options) * navigator.credentials.transmit(identity, options) The complete docs go into much more detail about the data sent and received from each API call above: https://github.com/digitalbazaar/credentials-polyfill#identity-credentials-api -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: Web Payments: The Architect, the Sage, and the Moral Voice https://manu.sporny.org/2015/payments-collaboration/
Received on Thursday, 2 July 2015 21:19:06 UTC