1034492 - NFC: How to handle NDEF with multiple types.

Status: RESOLVED INVALID

(Firefox OS Graveyard :: NFC, defect)

Description

[Yoshi Cheng-Hao Huang [:allstars.chh][:allstarschh][:yoshi]]

During the NFC Work Week (6.23) in Taipei we discussed that currently we only check the type field of the *first* NDEFRecord.

However we might need to discuss if there's some NDEF with different type fields in the same NDEF Message, for example, the type of first NDEF Record is type A, and the type of the 2nd is type B.

Comment 1

[Dimi Lee [:dimi]]

According to Spec "NFC Data Exchange Format (NDEF) 2.4.2 Payload type", it says:

The type of the first record, by convention, SHOULD provide the processing context not only for
the first record but for the whole NDEF message.

So I wonder if we need to handle this case.

Comment 2

[Kamil Leszczuk [:kamituel]]

The only case I know where non-first record would take precedence, is in a smart poster message - and it's true only for URI records (if I understand the spec correctly). Section 3.4:

> If an NDEF message contains one or multiple URI [URI] records in addition
> to the Smart Poster record at the top level (i.e., not nested), the Smart Poster
> record overrides them. The NDEF application MUST use only the Smart Poster record.

I'm working on handling this situation in https://bugzilla.mozilla.org/show_bug.cgi?id=1021267.