- From: <sylvain.lalande@orange.com>
- Date: Tue, 13 Mar 2012 10:19:39 +0000
- To: <Frederick.Hirsch@nokia.com>
- CC: <public-device-apis@w3.org>
Hello everyone, I'm a web developer. I'm working for France Telecom (Orange Labs) with the NFC Teams in order to propose web solutions for NFC applications. I'm really interested in both following the current API's discussions and participating to the possibly new NFC's APIs. I would also be happy to start a discussion on an API to enable the access to a SecureElement. I know that NFC is a topic recently introduced and I saw that "SIM Access" was also part of DAP FutureWork. NFC and "SE (SecureElement) access" can be closely related because the SE is a sealed execution environment which can bring up a variety of services, and is not only a specific implementation for high level services. We can use the SE in order to propose NFC services, crypto services, identity services for example, and thus take the benefit offered by it. Furthermore it could still provide services while running the web app offline. And I think also that the SE is not focused solely on mobile, it's for me a good argument for standardization: a SE can be a Secure SD card, an embedded card, or a SIM card and why not, tomorrow, a Secure USB card. Among the use cases proposed through the NFC discussion, it seems to me that some of these are already covered by exiting implementations; it can be a food for thought. I have in mind the Tizen NFC Web APIs, the OpenSource project named 'seek-for-android' which implements the OpenMobileAPI and the Google Wallet that enables NFC card emulation and payment (http://www.google..com/wallet/how-it-works-security.html). When I'm looking at Tran's use case, I'm tempted to say that they're very close: "Tap and Pay", "Tap and Share" coupons and manage my loyalty cards, "Tap and Read" tags that could allow me to travel or to facilitate interaction with the point of sale. Once again, a SecureElement API would certainly help with those use cases. Unfortunately, I won't be able to attend the F2F meeting, but I will try to follow the discussions on these topics. Please keep in mind that I'm a newbie in W3C process and I'm not very comfortable with English, so don't blame me for that :) Regards Sylvain -----Message d'origine----- De : Frederick.Hirsch@nokia.com [mailto:Frederick.Hirsch@nokia.com] Envoyé : lundi 12 mars 2012 21:52 À : yuan.ji@nokia.com; snowboy@sk.com; jungkee.song@samsung.com; LALANDE Sylvain RD-SIRP-CAE; jiyeon0402.kim@samsung.com; jan.lindquist@ericsson.com; kenta.yasukawa@ericsson.com; samarth.d@samsung.com; wayne.carr@intel.com; dongyoung.lee@lge.com; soonbo.han@lge.com; diana.cheng@vodafone.com Cc : Frederick.Hirsch@nokia.com Objet : Welcome to the DAP working group! Ji, MoonOK, Jungkee, Sylvain, Jiyeon, Jan, Kenta, Samarth, Wayne, Dong-Young, Soonbo, Diana: Welcome to the Device APIs Working Group! If you have not already done so, please review the group charter [1], the public working group page and its roadmap [2], and the approved and draft meeting minutes [3]. The working group page has information on our meetings [4], including our weekly teleconferences. You will want to use IRC at meetings [5] and if a dedicated IRC client does not work you can use the web client [6]. All of our technical work is to be done on our public mailing list ( public-device-apis@w3.org ) [7] and in our Media Capture task force [8] and WebIntents task force [9]. Please note that mail for the task forces does not appear on the DAP mailing list, so you have to join the task forces explicitly to participate. The task forces may also have additional teleconferences. Our next face-face meeting is scheduled for next week in Shenzhen China, 20-22 March, please review the draft agenda and logistics information [10]. Please introduce yourself on this mailing list, indicating who you are, why you are interested in participating in the Device APIs WG, which parts of the charter are of particular interest, your expectations, and where you might be able to contribute. Thank you, and welcome to the working group. It is good to see so much interest in the work of the working group. regards, Frederick Frederick Hirsch, Nokia; Co-Chair, W3C DAP Working Group [1] http://www.w3.org/2011/07/DeviceAPICharter [2] http://www.w3.org/2009/dap/ [3] http://www.w3.org/2009/dap/minutes [4] http://www.w3.org/2009/dap/#meetings [5] http://www.w3.org/Project/IRC/ [6] http://irc.w3.org/?channels=#dap [7] http://www.w3.org/2009/dap/#comm [8] http://www.w3.org/2009/dap/#mediacapture [9] http://www.w3.org/2009/dap/#webintents [10] http://www.w3.org/2009/dap/wiki/F2F_Agenda_20-22_March_2012,_Shenzhen,_China
Received on Tuesday, 13 March 2012 12:12:09 UTC