W3C home > Mailing lists > Public > public-nfc@w3.org > May 2012

Re: draft charter for a W3C NFC working group - gemalto comments

From: Dave Raggett <dsr@w3.org>
Date: Fri, 11 May 2012 15:19:55 +0100
Message-ID: <4FAD200B.2040108@w3.org>
To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
CC: "public-nfc@w3.org" <public-nfc@w3.org>
On 11/05/12 14:22, GALINDO Virginie wrote:
> Dave, and all,
> As gemalto, we welcome the W3C investigation on NFC and have some
> comments on this draft charter :
> - by treating only NDEF format, there is a de facto exclusion of
> payment/transaction applications, as this format is not suitable to
> such interaction.

My assumption is that payments would be handled via Web Intents with a
generic payment API between the web app and the payment solution. This
allows the user to select her preferred means of payment and avoids hard
wiring the web app to specific payment solutions.

> One of the immediate use case that we see, is the
> interaction between web pages running in a NFC device and a
> contactless card which is swapped closed to this device to perform a
> transaction.

I would like to understand the technical implications in more detail.
Wouldn't it be the case that the web app could use the regular NDEF API
to read NDEF formatted data, whilst the payment specific driver invoked
via Web Intents would use the payment specific protocol?

> - On the recent requests related to LLCP, I would recommend that the
> API deals only with the actual data transported thanks to LLCP, and
> is not LLCP specific. One of the rationale for that is to tailor a
> future proof API, which is not specific to the link layer (LLCP in
> that case).

I understand that LLCP can be used for TCP/IP connections, and as such
could support existing Web APIs for HTTP (XHR), Web Sockets or more
simply HTML MessageChannel. The only requirement is that the
communication channel is bidirectional and reliable in the same sense as
for TCP/IP.

> If you wish to make the WG charter consistent with my comments, you
> may implement the following changes :
> - Section 2 - scope of the API includes APDU message management
> - Section 3 - card emulation mode exclusion is removed

I would very much like to understand the implications for Web APIs. We
already have implementations based around NDEF and are confident in
developing a standard for that. It would be helpful to know about the
corresponding implementations at the level you describe.

Best regards,
Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Friday, 11 May 2012 14:20:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:43:36 UTC