- From: Adrian Hope-Bailie <adrian@hopebailie.com>
- Date: Tue, 14 Apr 2015 06:48:07 -0700
- To: Anders Rundgren <anders.rundgren.net@gmail.com>
- Cc: "Web NFC (W3C)" <public-web-nfc@w3.org>
Received on Tuesday, 14 April 2015 13:48:38 UTC
Hi Anders, How is this any different to the Geolocation API which is widely used and has been for many years? http://www.w3.org/TR/geolocation-API/ I agree with your assertion that there is a need for a generic native-Web bridge but that shouldn't prevent specialised API's for access to device hardware from being developed should it? I would encourage this group to work closely with the Web Payments IG, specifically with regards to the payments use cases they are dealing with. Adrian On 14 April 2015 at 04:41, Anders Rundgren <anders.rundgren.net@gmail.com> wrote: > When I read issues like https://github.com/w3c/web-nfc/issues/16 > I get the impression that you expect connecting clients to use > Web-technology. > > IMO, this assumption will severely limit the value of Web NFC. > The only "standard" that's really lacking, is a way for untrusted > Web-pages to interact with connecting client devices. > http://ipt.intel.com/Home/How-it-works/network-security- > identity-management/ipt-with-near-field-communications > > How Web-based OSes expose NFC to the outer world should IMO be left to > another forum to cater for including > security considerations. > > Cheers, > Anders > > > >
Received on Tuesday, 14 April 2015 13:48:38 UTC