RE: common NFC API draft / base for discussion

Hi Sunil,

A browser will access the NFC radio through the APIs provided by the underlying OS, whatever system it is. Now, if I understand correctly where you want to get, there should definitely be a way for a e-wallet type web application to take advantage of NFC secure elements through the browser.

The approach here - and it's pretty much work in progress - is to have two separate set of APIs, one for NFC, another for secure elements. The rationale being that different types of hardware could provide secure services, so it would be better to access these services with a unified API.

The Secure Elements API is part of the W3C SysApps group charter:
http://www.w3.org/2012/sysapps/

Secure Elements draft APIs from W3C and Webinos:
http://www.w3.org/wiki/Draft_APDU_API
http://dev.webinos.org/specifications/draft/secureelements.html

Tizen OS provides independant NFC and Secure Elements html5 APIs:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/se.html
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/nfc.html

Again this is work in progress, but indeed with the cloud wallet objective in mind.

Best Regards,

Luc Yriarte

> -----Original Message-----
> From: Jain, Sunil K
> Sent: Thursday, May 30, 2013 3:26 AM
> To: Yriarte, Luc; 'Luc Yriarte'; public-nfc@w3.org
> Subject: RE: common NFC API draft / base for discussion
> 
> Hi Guys
> May I ask a rather novice question: Can a browser in a mobile device
> directly talk to the NFC radio -- bypassing any OS or needing to broker
> thru any secure element on the side of the NFC radio?  I see this usage
> becoming very compelling as the cloud wallet and services will grow,
> especially when latency is not an issue. Please advise if and how this
> usage can be addressed?
> 
> Thanks
> -Sunil Jain
> NFC Forum SIG Co-Chair
> 503.705.5096
>

Received on Thursday, 30 May 2013 08:36:47 UTC