W3C home > Mailing lists > Public > public-nfc@w3.org > January 2014

NDEF Record

From: Don Coleman <dcoleman@chariotsolutions.com>
Date: Wed, 8 Jan 2014 11:00:44 -0500
Message-ID: <CAK5tL-gnMj0qO7qRmbJCrkCEGZCROSMxzjQswE1uH8Z2q=s4LA@mail.gmail.com>
To: "public-nfc@w3.org" <public-nfc@w3.org>
Section 12 - NDEF Record

Can we remove the recordType attribute from the NDEFRecord interface? The
record's TNF and type tell us this information.

The TNF tell how to interpret the Type. The Type tells how to interpret the
Payload.

Section 12.1 - Attributes TNF

Edits
    3 (URI) should be 3 (Absolute URI)
    2 (Media) should be 2 (Media-type)
    add 6 (Unchanged)

TNF is 3 bits when setting the value. When the TNF is read from the
Message, it contains additional data.
https://github.com/don/ndef-js/blob/master/lib/ndef.js#L274

Should we refer to the NFC Forum Specs?

----

Can we specify the TNF and Type in each of the Record Interface
definitions?

Section 13 - NDEF Record Text

    TNF Well-known (0x1)
    Type T

Section 14 - NDEF Record URI

    TNF Well-known (0x1)
    Type U

It should be clear that this is not a TNF Absolute URI (0x3) record.

Section 15 - NDEF Record Media

    TNF Mime Media-type (0x2)
    Type - set by user

Section 16 - NDEF Record Smart Poster

    TNF Well-known (0x1)
    Type Sp

Can we note that the payload of a Smart Poster is another NDEF Record?

I'd like to see Smart Poster record grouped with the other Well-known
record types.

Section 17 - Enumerations

Suggest removing this section, since the TNF and type tell us the same
thing and offer more flexibility. "unknown" is confusing for a general
record since there is also a TNF Unknown (0x5).
Received on Wednesday, 8 January 2014 16:01:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:43:37 UTC