- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2017 13:30:53 +0000
- To: public-web-nfc@w3.org
NDEF with exception of [`opaque`](https://w3c.github.io/web-nfc/#dom-nfcrecordtype-opaque) record types could be validated. Android does just basic validation, so implementations need to take care of that. Even with opaque records NDEF frame is required. In turn, with ISODep etc we open a point-blank Pandora box and let it be used. However, if the user agrees... there are also other [powerful features](https://www.w3.org/TR/2014/WD-powerful-features-20141204/) as well. > I'm advocating a dedicated, locked-down, write-only Web-NFC variant That sounds good, please create an issue/feature request with use case and proposal. Could you elaborate on the locked-down part? Need to understand how different/stricter would it be from the current API. Also, whether it fits the charter. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/101#issuecomment-305787439 using your GitHub account
Received on Friday, 2 June 2017 13:31:00 UTC