- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sun, 11 Oct 2015 14:44:20 +0200
- To: "Web NFC (W3C)" <public-web-nfc@w3.org>
F.Y.I. After a pretty successful PoC ( https://test.webpki.org/webpay-merchant ) exploring the navigator.nativeConnect() API ( https://github.com/cyberphone/web2native-bridge#api ), the time has come to unify the Web2Native Bridge with its NFC/BLE counterpart ( https://cyberphone.github.io/openkeystore/resources/docs/webnfc--web2device-bridge.pdf ) through an API tentatively called navigator.tapConnect(). That is, applications based on this concept are _without_changes_ callable from Web-pages as well as from NFC/BLE connections. If the latter is provisioned from a Web-page it would use navigator.tapConnect(), whereas a POS terminal or similar would not necessarily need to use Web-technology at all, only the on-the-wire protocol must (of course) be adhered to. That the security/trust models differ is a "problem" but I do not see that there is much you can do about that since the trustworthiness of unknown hosts isn't possible to verify except through moderately established methods like remote attestations using TPMs. Anders
Received on Sunday, 11 October 2015 12:44:54 UTC