- From: Marcos Caceres <w3c@marcosc.com>
- Date: Sun, 29 Sep 2013 19:41:46 +0100
- To: POTONNIEE Olivier <Olivier.POTONNIEE@gemalto.com>
- Cc: Anders Rundgren <anders.rundgren.net@gmail.com>, Marcos Caceres <mcaceres@mozilla.com>, sysapps <public-sysapps@w3.org>
On Thursday, September 26, 2013 at 11:17 PM, POTONNIEE Olivier wrote: > Hi Marcos, > > As Anders mentioned PC/SC is the de facto standard on desktop environments to access secure element, as it is present on Windows, Linux and MacOS. > On Mobile, there is no such universal standard. Each platform developed its own native API: > - Android: > https://code.google.com/p/seek-for-android/ > - Windows Phone: > http://msdn.microsoft.com/en-US/library/windowsphone/develop/microsoft.phone.secureelement(v=vs.105).aspx > - BlackBerry: > http://developer.blackberry.com/native/documentation/core/com.qnx.doc.nfc/topic/manual/t_nfcdevguide_connect_app_on_SIM_SE.html > (not exhaustive list) > > Of course the W3C secure element API should not be a copy of the PC/SC specifications, which have a wider scope of features than needed by web applications, and is very low level. What we are willing to expose in the SE API is only a subset of PC/SC part 5, through a slightly higher level API. Thanks Olivier for the additional links and clarifications. -- Marcos Caceres
Received on Sunday, 29 September 2013 18:42:18 UTC