- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Aug 2015 16:14:44 +0000
- To: public-web-nfc@w3.org
I think precision is needed when the client has to do the conversion. For the use cases of Web NFC the rest seem to be fine - it is one of the purposes of the API to map NFC to types known in the browsers. But I have no problems exposing the exact underlying information, when available. Could you give one example for conflict for JSON and text, respectively? -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/26#issuecomment-130358894
Received on Wednesday, 12 August 2015 16:14:46 UTC