- From: Han Leon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Oct 2019 08:57:35 +0000
- To: public-web-nfc@w3.org
Sure we just treat it as an external type record if the type string matches the rule of external types, no matter it's in an embedded context or not. The question is for the following step, how could we tell it should be converted to external type record (TNF=4) or well-known type record (TNF=1)? > otherwise, if a string is a match for being any local type (basically just starting with lowercase) and the context exists (currently: it is defined inside a message that is payload to another record), then it is local type Probably the only case for TNF=1 should just be "the s, t and act in smart-poster", and handover types (we don't use now)? All other cases go with TNF=4? But, from https://developer.android.com/reference/android/nfc/NdefRecord.html#TNF_WELL_KNOWN, it looks like Android API does not include "the s, t and act in smart-poster" in the scope of TNF=1, i.e. no RTD_XXX definition for "the s, t and act in smart-poster". -- GitHub Notification of comment by leonhsl Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/409#issuecomment-545818990 using your GitHub account
Received on Thursday, 24 October 2019 08:57:36 UTC