- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Oct 2019 18:22:58 +0000
- To: public-web-nfc@w3.org
> As a developer, I would like to be able to distinguish "card cannot be formatted/written to" (possibly due to e.g. MIFARE keys being set), "card has data but it's not NDEF", and "card is unformatted (no data) but can be formatted". Each of these may necessitate a different behavior in the application. These are fair requirements, however, as mentioned above, the current scope is NDEF-only, and apps are not supposed to do formatting themselves with this API, so ATM the only things that matter are how reads and writes should work and formatting would happen on need, if possible and if wanted by the app. If we want to give full control to apps, then the alternative would be a full-fledged low-level API like in Android, including formatting, tech discovery etc, but that's another API type, and there has been a WG for that: https://www.w3.org/2012/nfc/web-api/ . Of course, we could specify that kind of API in the Web NFC CG to some extent, but it's not been really [chartered](https://w3c.github.io/web-nfc/charter/) that way. @anssiko, how low-level can we go with Web NFC in the CG? Is charter change viable? -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/367#issuecomment-540711192 using your GitHub account
Received on Thursday, 10 October 2019 18:23:00 UTC