- From: Wayne Carr <wayne.carr@linux.intel.com>
- Date: Wed, 25 Mar 2015 14:05:29 -0700
- To: "public-nfc@w3.org" <public-nfc@w3.org>
- Message-ID: <55132319.2000604@linux.intel.com>
We're finished with the clean up work we needed to do and are leaving the NFC WG. The previous email had a link to the final draft of the approach in the published First Public Working Draft [1] in the form that would be needed to publish it as a WG Note. We don't see how that could advance to a Recommendation due to lack of implementations, so a WG Note seems the way to publish. The NFC WG charter expired 1 November 2014. We don't think the Charter should be extended or renewed because the WG was never able to attract multiple implementers. We tried our best, as Chair and Editors, but as in SysApps WG, the issue is whether it will have implementations that are used broadly. The Web NFC Community Group [2] is developing a Web NFC API for the usual Web security model used in Web Browsers (with a couple of the Browser companies in it already). This approach is very similar to and likely will benefit from the work in the Web Bluetooth Community Group [3]. For a more powerful API used in standalone apps (like the NFC WG and SysApps WG, not using the Web security model), an extension API that builds on top of the Web API could be developed for use outside the Web Security model. That would likely be in a different CG, since the people joining the new Web NFC CG weren't interested in that, at least not at this point. In the future, developments coming out of the Trust and Permissions Community Group [4] may enable more powerful APIs under a new Web Security model in the future. [1] https://lists.w3.org/Archives/Public/public-nfc/2015Mar/0020.html [2] https://www.w3.org/community/web-nfc/ [3] https://www.w3.org/community/web-bluetooth/ [4] https://www.w3.org/community/trustperms/
Received on Wednesday, 25 March 2015 21:05:57 UTC