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

Re: Data Types - AbsoluteURI

From: Stephen Tiedemann <tiedemann@sony.de>
Date: Tue, 16 Dec 2014 11:56:01 +0100
Message-ID: <54900FC1.8000103@eu.sony.com>
To: Don Coleman <dcoleman@chariotsolutions.com>, "public-nfc@w3.org" <public-nfc@w3.org>
That's correct, although the example Windows LaunchApp record 
unfortunately also represents a violation of the TNF=3 type string 
construction rules - it should in fact be an Absolute URI.

Beyont that, shouldn't the Blob message type not actually apply to *any* 
NDEF record type that is not covered by DOMString | URL | JSON ? I would 
else wonder how other NFC Forum Well-Known Types or NFC Forum External 
Types (TNF=4) could be accessed.


On 12/15/2014 10:12 PM, Don Coleman wrote:
> "Absolute URI as defined in RFC 3986 (TNF=3)" should be a Blob message 
> type instead of a URL type.
> http://w3c.github.io/nfc/index.html#data-types
> The URI in the Absolute URI record is used to *describe* the payload, 
> rather than deliver a URI as a payload.
> For example, a Windows LaunchApp Record uses TNF=3, the URI 
> "windows.com/LaunchApp <http://windows.com/LaunchApp>" and binary 
> content as the payload.

Stephen Tiedemann, Principal Engineer
European Technology Center (EuTEC)
Sony Deutschland GmbH
Hedelfinger Strasse 61
D-70327 Stuttgart, Germany

Office: +49-711-5858773
Mobile: +49-172-7425784
Fax:    +49-711-585899773

Sony Deutschland GmbH
Registersitz: Kemperplatz 1, 10785 Berlin
Geschäftsführung: Markus Zumkeller
Rechtsform GmbH, HRB Berlin-Charlottenburg 107677 B

"To solve an interesting problem, start by finding
a problem that is interesting to you."
Received on Tuesday, 16 December 2014 10:56:32 UTC

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