Hallo Nick, > Understood. There was no choice but to create a new protocol, since the > rules of the NFC Forum are that you cannot implement a protocol until it > is ratified. And SNEP is not yet ratified. Rather than wait for ever, we > want to put it in the hands of users and application developers right now :)
Oh, I didn't know of this rule, although it makes sense ;-) > * 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? > > Well the LLCP spec is not super clear here, note language like "External > service names MAY be formatted as uniform resource names (URN)". > However, we have heard this feedback and are considering changes. You are right :-) I didn't read the "MAY". In fact it only mandates the name to be a URI reference (which, as I just learned, could be pretty much anything as it's not required to be an absolute URI). > * 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. > > This is on purpose. We require that an Android compatible device that > claims NFC hardware support must do NPP, and it must do so on top of > NFC-DEP. Alright. 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
