- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 May 2019 11:53:16 +0000
- To: public-web-nfc@w3.org
@kenchris so the rationale for NDEFCompatibility is that the page can tell it only wants standard tags or it wants to implementation to consider also non-standard tags if the implementation/underlying platform can deal with it. However, why wouldn't a page always opt for the widest compatibility available from the platform? Do we have a use case when a page explicitly does not want to read/write non-standard tags? Otherwise I suggest we take the "widest possible" compatibility and for the time being remove NDEFCompatibility and explain the handling of various compatibility scenarios in prose. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/160#issuecomment-496904345 using your GitHub account
Received on Wednesday, 29 May 2019 11:53:23 UTC