3 bits in the first byte of the NDEF = NFC Data Exchange Format record header
-
tells you how to interpret the type field of the NDEF = NFC Data Exchange Format record header
-
TNF values:
-
Absolut URI - TNF 3 is misleading: the type-content-field is a URI like: “windows.com/LaunchApp”
- and not the payload
- to send a URL payload you use the Well-Known - TNF 1 with a “U” in thy type-content-field
-
Android… Android breaks the NDEF specification a bit with Absolute URI records. Although the NDEF specification says the type describes the payload, Android devices handle TNF 03 (Absolute URI) records by opening the browser with the URI in the type field; basically, Android treats the URI in the type field as if it were the payload. BlackBerry and Windows Phone do not open the browser when an Absolute URI tag is scanned.