title: Custom (NFC) NDEF format
body: <p>I would like to transport over the LLCP a custom data within the NDEF message in one NDEF record (or possibly the payload will be chunked across several NDEF records). The transported content is a file with a specific format that has meaning only in specific application. So, what is the best approach for specifying the NDEF header?</p>
  
  <p>1) Set TNF to 0x04 (NFC Forum External Type), 0x03 (Absolute URI) or 0x05 (Unknown)? The 0x04 will have in the TYPE field custom relative URI and in the case of 0x03 absolute URI. The 0x05 I do not like much, since the receiving device cannot identify the application for processing data, because the TYPE must be empty in that case (here only the ID field can help).</p>
  
  <p>2) The ID field is for the NDEF message uniqueness, so can be either empty or will contain the custom identifier in a form e.g. <code>com.company.nfc.application_name&amp;id=message_generated_uuid</code></p>
  
  <p>My opinion is - use of the TNF 0x03 or 0x04 is a preferred way, with leaving the ID empty unless the messages will need some additional identification, which will be better to transport outside of the payload.</p>
  
  <p>BR
  STeN</p>