- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Feb 2016 11:48:04 +0000
- To: public-web-nfc@w3.org
When it comes to the SE API, that's for v2, needing web-specific use cases. NFC Forum Type 4 is mentioned in the spec. If there is support for it in the underlying platform, implementations may support it, but this API does not intend to provide a low level access. Security is one of the main reasons the Web NFC API is a more like a special way of using NFC, and not a low level NFC API. The Web NFC API should be usable from web pages, using the _browser_ security model. When you have a _web runtime_ with well defined application and store security, you can use a low level API such as the [W3C NFC API](https://www.w3.org/TR/nfc/) -- although that doesn't support SE either. But in browsers it's a different, slower developing story. The Web NFC API is extended based on use cases, and not so much on generic mapping of protocols to the Web. When considering support for a use case, we need to analyze how does it affect security and privacy, and how can we expose it in a simple way to web pages. So rather than providing a generic low level secure element API, we'd prefer focusing on a few key use cases concerning SEs. If you have use cases in mind, please open issues for them. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/101#issuecomment-182824552 using your GitHub account
Received on Thursday, 11 February 2016 11:48:07 UTC