W3C home > Mailing lists > Public > public-nfc@w3.org > March 2013

Towards a common NFC draft...

From: Yriarte, Luc <luc.yriarte@intel.com>
Date: Tue, 5 Mar 2013 10:04:44 +0000
To: "public-nfc@w3.org" <public-nfc@w3.org>
CC: "hans@ambiesense.com" <hans@ambiesense.com>, "stefano.vercelli@telecomitalia.it" <stefano.vercelli@telecomitalia.it>
Message-ID: <8A6036327A83774CAEB939CB8A720E831912C6A0@IRSMSX101.ger.corp.intel.com>
Hi all,

It really was a pleasure to meet you guys last week at MWC, I hope you had a nice trip back. Working towards a common NFC draft, I'd like to setup a list of items that every side wants, so that they would be included in the spec. Feel free to add stuff as appropriate. For reference, the existing APIs are here:
http://w3c.github.com/nfc/proposals/intel/nfc.html
http://w3c.github.com/nfc/proposals/webinos/nfc.html


What I'd like to take from the Tizen API:
- A NDEFMessage interface that's an array of NDEFRecords, and the inheritance hierarchy of NDEFRecord types
- Separate NFCTag and NFCPeer interfaces, each having their own methods for reading / writing or sending / receiving NDEF Messages. That allows registering a listener for NDEF messages on a peer device, that could send a bulk of messages, but just invoking a "read" method on a tag. Also, all the pairing / handover stuff is done at the NFCPeer interface level. BTW last week's slides, including the updated spec with BT handover, are accessible there:
https://github.com/01org/cloud-neard/wiki


What I'd like to take from the Webinos API:
- It's event-based. Right now the Tizen-based API uses only callbacks, and that would not work well with the Webinos / node.js framework. If I understood correctly what Hans explained the node.js implementation uses HTML5 server-sent events. The Javascript code runs on the device, raise a very light http server, and the UI code in the web browser registers for server events. Please correct me if I'm wrong. 
Anyway I believe it would make sense to align with the EventTarget / EventHandler model of the Sysapps group proposals like Telephony, Messaging and so on
http://www.w3.org/2012/sysapps/


As far as I'm concerned that's what I consider is important to get right, I have no strong opinion on what to do with MIME / binary data, lower level comms (LLCP), read only tags... please add your opinions and what you feel strongly about. 

Cheers,

Luc

Luc YRIARTE - OTC Software Engineer
INTEL Corp. Montpellier, France

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Received on Tuesday, 5 March 2013 10:05:16 UTC

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