NFC Working Group

Transitioning to FPWD

Editor's draft: http://htmlpreview.github.io/?https://github.com/w3c/nfc/blob/master/proposals/common/nfc.html

Luc: we are in the process of implementing the API in time for TPAC in November.

Jacques: any objections or comments on moving the spec to FPWD?

[no objections]

Jacques: I propose that the NFC WG transition the editor's draft to FPWD

David: I think that the use cases look good, and this is a good heartbeat, and I am comfortable going ahead.

RESOLUTION: The NFC WG resolves to publish the editor's draft as a FPWD

ACTION: Dave to work with Luc to publish the editor's draft as an FPWD

Testing

Luc: what process should we following for testing? Intel is planning to provide implementations on Linux native and Android.

Dave: we can read through the spec, looking for normative assertions and creating the corresponding test cases, which can be put in github.

Luc: the same repo as for the spec?

Dave: yes, that would work

We need a description for each test, and if practical a runnable test, e.g. as a script

Luc: that would be nice

Dave: FPWD is early step, and changes may occur as we move to Last Call, but having the tests early allows for test driven evolution of the API spec
... it might be worth looking at how other WGs are tackling testing, Tobie Langel is leading the effort for HTML5, for instance.

Luc: I can look at using node.js ...

TPAC

Jacques: who is attending besides me?

Dave will attend.

David E. will attend, but will be busy at times with the AC meeting

Jinsong will attend TPAC

Dave: do we want to organize a break out session on NFC at the plenary session mid-week?

Jacques: yes, we could do demos, talk about the use cases and the reasoning behind the API.

Dave: people have already asked me about the relationship between Bluetooth 4.0 low energy and NFC, we should be prepared to talk about this

Samuel: I can ask the NFC Forum for their take on this to see if we can share this.

Dave: I don't think that BLE allows you to use tap gestures to identify an individual product or even yourself to a sales assistant.

Samuel: indeed

Dave: BLE supports discovery as well as peer to peer messages containing small amounts of data, which can be encrypted if needed
... I can envisage a phone caching the broadcast notifications sent by BLE devices, and a JavaScript API to access this.
... A simple API could be used for peer to peer messaging.

We discuss where BLE could fit in W3C, e.g. the Bluetooth API work item for SysApps phase 2 which has yet to start

DAP is chartered to work on discovery, and the Geolocation WG is being rechartered to work on indoor location, and improvements for geofencing.

It would be good to discuss this further at TPAC and raise the level of interest

Any other business

Dave introduces Jinsong as a new W3C Team member at our host in China -- Beihang University in Beijing.

Jinsong looks forward to meeting everyone at TPAC in Shenzhen!

Jinsong: I would like to add something about NFC and BLE. I used to work for Nokia on NFC training.
... a key difference is that NFC is a few centimeters where as BLE is tens of meters.

This makes security a bigger challenge for BLE as it is easier to eavesdrop

scribe: lets discuss security at the TPAC session.

[general agreement]

Dave we can arrange a follow on telecon for preparation for TPAC.