- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Aug 2015 16:33:30 +0000
- To: public-web-nfc@w3.org
We don't hide TNF=4, but expose it as ArrayBuffer without MIME type. Did you mean why do we hide the NDEF fields from developers (e.g. the TNF value), IOW why don't we present a low level interface? That is done by the earlier WG spec pretty well. Should we expose these NFC-specific terms/details for any web page? One assumption in Web NFC was that we don't have to be compliant with legacy NFC tags - when we started the CG people wanted to have a web-specific NFC, even so much as total separation between NFC content available for web pages and low level interfaces available through native platforms. This was a security issue from the start. Not having to expose all low level details allowed us to simplify the interfaces, and focus on the us cases by not having to care too much about exact formats. > Well, text is a string and JSON can be too. It is possible to write a string as "application/json" or "text/plain", and read a string as "application/json" or "text/html". I'm not sure I understand the problem. Here I don't see we lose type information that has been written using Web NFC (or even by "legacy" writers). -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/26#issuecomment-130363815
Received on Wednesday, 12 August 2015 16:33:31 UTC