Hallo Nick, > Just want to clarify this - NPP is an open protocol. We've published the > spec here: > > http://source.android.com/compatibility/ndef-push-protocol.pdf
Sorry, I wasn't aware that the spec has already been published. I really like the simplicity of the protocol. Especially in comparison with NFC Forum's SNEP (Simple NDEF Exchange Protocol) which isn't quite that simple at all. Still I'm not sure what impact on compatibility between NFC devices it will have if Google/Android designs one protocol while the NFC Forum (the industry consortium around NFC) designs a totally different protocol for virtually the same purpose. Still, I have some questions and comments regarding the NPP specification: * The specification says that the service name is "com.android.npp". The LLCP specification mandates well-known service names to be URIs in the form "urn:nfc:sn:<servicename>" and external service names to be URIs in the form "urn:nfc:xsn:<domain>:<servicename>". The NPP is an external service, therefore, in my opinion this service name is not compatible with the LLCP specification. Or did I miss something? * The text says "An NPP 1.0 server MUST [...]" but the version information field suggests that the major version is 0 and the minor version is 1. In my opinion calling the protocol 1.0 is a bit misleading. * The specification refers to NFC-DEP. This seems to be in conflict with the LLCP specification which does not mandate the binding to a specific underlying protocol. Thus, LLCP could be used on top of other protocols than NFC-DEP too. br, Michael -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
