[web-nfc] Verify how we should handle TNF=3 (#248)

• From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
• Date: Tue, 30 Jul 2019 09:32:37 +0000
• To: public-web-nfc@w3.org
• Message-ID: <issues.opened-474476901-1564479156-sysbot+gh@w3.org>

kenchris has just created a new issue for https://github.com/w3c/web-nfc:

== Verify how we should handle TNF=3 ==
![image](https://user-images.githubusercontent.com/1101339/62118131-726fbf80-b2bd-11e9-9e34-be9707c6084e.png)

I am not sure we are able to actually read these as Android most likely will just try opening them in Chrome. Would be good to verify. On Android these are considered "action URLs" basically URLs that the OS will try launching. I assume they could be Android app URIs as well (good to verify).

Even if we cannot read these (should probably be noted in the spec) then we should probably be able to write them.

Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/248 using your GitHub account

Received on Tuesday, 30 July 2019 09:32:39 UTC