diff options
| author | Samuel Ortiz <sameo@linux.intel.com> | 2012-01-18 19:51:12 +0100 |
|---|---|---|
| committer | Samuel Ortiz <sameo@linux.intel.com> | 2012-01-18 19:51:12 +0100 |
| commit | 37abb317fac73c7b3d352eb666f93404389f288f (patch) | |
| tree | 5e6530013eb235374b21a4b9b14b41af9d70ee04 /TODO | |
| parent | 7bf3dc11f58e463c48567a2a11f3001c87e405a6 (diff) | |
| download | neard-37abb317fac73c7b3d352eb666f93404389f288f.tar.gz neard-37abb317fac73c7b3d352eb666f93404389f288f.tar.bz2 neard-37abb317fac73c7b3d352eb666f93404389f288f.zip | |
TODO: Update
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 80 |
1 files changed, 35 insertions, 45 deletions
@@ -11,24 +11,15 @@ Background Core ==== -- NDEF building library - - Priority: High - Complexity: C4 - Owner: Ravikumar Veeramally <ravikumar.veeramally@intel.com> - - This library should provide a simple API to build NDEFs based on very high - level input, e.g. an image or an URL. - - - Writer Mode Priority: Medium Complexity: C4 Dependencies: Core:NDEF building library - Owner: Samuel Ortiz <sameo@linux.intel.com> + Owner: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com> - In writer mode, neard allows application to write to an NFC tag. + In writer mode, neard allows application to write to an NFC tag, or to push + data to a p2p device. - Card Emulation Mode @@ -49,51 +40,50 @@ Core protocol, a.k.a. tags). -- p2p Mode - - Priority: Medium - Complexity: C8 - Owner: Samuel Ortiz <sameo@linux.intel.com> - Dependencies: Core:NDEF building library - Owner: Samuel Ortiz <sameo@linux.intel.com> +Reader mode +=========== - In p2p mode, an NFC adapter can either be in target or initiator mode. - A link is established between 2 NFC adapters, and can be connection or - connection less oriented. NDEFs are exchanged through the SNEP (NFC - Forum draft) protocol. +- MIFARE tag support + Priority: Medium + Complexity: C4 + Owner: Olivier Guiter <olivier.guiter@linux.intel.com> -- Read/Write permission check +- Bluetooth Handover integration Priority: Medium - Complexity: C2 - Owner: Samuel Ortiz <sameo@linux.intel.com> + Complexity: C4 + Owner: Olivier Guiter <olivier.guiter@linux.intel.com> - A tag can be in read only or read/write mode, and that needs to be - exported trough the D-Bus interface. + The handover integration has to be done between bluetoothd, obexd and + neard. obexd should be able to expose and OOB NDEF in order for an NFC + peer to initiate a BT pairing. The potentially queued OBEX transfers + should then start once the pairing is done. + On the other hand, neard should be able to talk with bluetoothd for + pairing with a remote peer exporting an OOB NDEF. Once the pairing is + done, obexd should be able to handle the OBEX transfer. -- UID export +p2p mode +======== - Priority: Medium - Complexity: C2 - Owner: Samuel Ortiz <sameo@linux.intel.com> +- NPP client support - Many NFC tags do have a UID associated to it. This is tag type dependent - but could be exported through the D-Bus interface as well. + Priority: Low + Conplexity: C2 + Dependencies: Core:Writer mode + Owner: Samuel Ortiz <sameo@linux.intel.com> -Reader mode -=========== + For pushing NDEFs through NPP over LLCP, neard has to behave + as an NPP client. -- Type 4 tag support +- SNEP support Priority: High - Complexity: C4 - Owner: Olivier Guiter <olivier.guiter@linux.intel.com> - - -- Topaz 512 (type 1) tag support + Conplexity: C4 + Dependencies: Core:Writer mode + Owner: Samuel Ortiz <sameo@linux.intel.com> - Priority: High - Complexity: C2 - Owner: Olivier Guiter <olivier.guiter@linux.intel.com> + SNEP is the NFC Forum defined standard for exchanging NDEFs over + an LLCP link. SNEP can be run as a client or a server, respectively + to send and receive NDEFs. |