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: Sun, 13 May 2012 09:34:19 +0100
Message-ID: <4FAF720B.4050300@w3.org>
To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
CC: "public-nfc@w3.org" <public-nfc@w3.org>
On 12/05/12 21:57, GALINDO Virginie wrote:
> Hi Dave, 
> My comment below, marked as [VG - gemalto]. 
> Regards,
> Virginie
> gemalto
> 
> -----Original Message-----
> From: Dave Raggett [mailto:dsr@w3.org] 
> Sent: Friday, May 11, 2012 4:20 PM
> 
> 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.
> 
> [VG - gemalto] This could be a possible technical solution, which has to be further analysed. As Bryan Sullivan mentioned yesterday, the current state of web intent does not mention such payment feature. We should be able to discuss this usecase in the NFC WG (Or System Level WG, if we want to merge both), even if in the end, it is transferred to Web Intent. 
> Another remark on that one, just to make sure I got it, would you develop the same Web Intent feature for a signature usecase ? The technical components are exactly the same, but the service is slightly different : a device in reader mode is offering a webpage where the user can sign a transaction/document, the user is approaching from this device a contactless card with signature capabilities (either for legally binding signature, such as identity card for government services, or 'normal' digital signature for corporate signature, for example). In this case, you are managing the same kind of data format as payment usecase to convey your data between the contactless card and the web app (APDUs). 

Payments came up at the recent Web Intents meeting in Shenzhen, although
we didn't go into any details. Currently there are no W3C Working Groups
chartered for work on payments, although this is something on the W3C
Team radar, see:

   http://www.w3.org/wiki/Payments_Task_Force

>> 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 have added these as questions in the draft charter, see:

  http://www.w3.org/2012/05/nfc-wg-charter.html

> 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.
> 
> [VG - gemalto] For the management of APDU messages, you basically need to have a NFC controller able to extract APDUs from the ISO 14443 messages and transmit it to the Browser, which would then make it available to the web app with a specific container. This treatment of APDU messages is already something that NFC controller do support. But let me come back with a drawing in the coming days, detailing the different needed technologies, it will be easier to explain. 

Great, I will look forward to that.

Many thanks for your comments.

Best regards,
-- 
Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Sunday, 13 May 2012 08:34:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 May 2012 22:57:28 GMT