- From: Maxime C. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Feb 2016 13:20:15 +0000
- To: public-web-nfc@w3.org
Got your points here. I can agree with the scope that should be limited in its first version to see faster a real implementation ; with the risk that a second version would takes decade ; but I'm more skeptic about security and privacy arguments here. Basically Web NFC API provides read/write capabilities to external devices. When we talk only about tags, there is millions of RFID chips out there using the same technologies that what we call today NFC is based on, for e-ticketing, access control and banking industries. If you don't provide a `low level NFC API` then there is good probabilities that you will see the birth of a new de-facto Web NFC API Wrapping protocol based on HCE emulation, JCOP applet and new RFID/NFC chips. Coming from these industries I would be at least one of these guys going this way so I'm pretty sure there will be others. My thoughts is that you will just delay the problem if this is one, and divide at little bit more the industry which already has some difficulties to stay on standardized roads. -- GitHub Notification of comment by Maxhy Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/101#issuecomment-182859692 using your GitHub account
Received on Thursday, 11 February 2016 13:20:19 UTC