- From: Yriarte, Luc <luc.yriarte@intel.com>
- Date: Wed, 20 Feb 2013 09:31:38 +0000
- To: Samuel Ortiz <sameo@linux.intel.com>
- CC: "public-nfc@w3.org" <public-nfc@w3.org>
Hi Samuel, > I think this would be a very convenient API. It could also apply to the > Tag interface when we want to write a Handover NDEF there (Handover > select for static handover). Okay so that would mean writing handover select information about a specific device on a NFC tag. Should the API take some device-related parameter then, like a pin code or a mac address ? > Also, in order to avoid offering the same feature through several API > paths, we should forbid to build Handover NDEF if we offer this > handover specific API. Otherwise apps would be able to use both the > Handover creation + nfcpeer.sendndef API and the nfcpeer.startHandover > one, for exactly the same results. I think this is a confusion we > should avoid. This one will be pretty straightforward. Currently the only NDEF record types we support are "text" and "uri", with "media" coming next. Even if the underlying Neard Handover API is based on specific NDEF record types, we are not required to expose it this way. Conceptually we can separate Handover from NDEF record types, and design a specific set of APIs. Best, Luc --------------------------------------------------------------------- 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 Wednesday, 20 February 2013 09:32:10 UTC