- From: SULLIVAN, BRYAN L <bs3131@att.com>
- Date: Wed, 22 Aug 2012 20:26:53 +0000
- To: "public-nfc@w3.org" <public-nfc@w3.org>
Dave, Here are the AT&T comments to the charter, with suggested changes, mostly editorial. Old: "The NFC Forum defines standards for how cards and tags are formatted and the protocols for communicating with them. There are three modes:" New: "The NFC Forum defines base standards for how smart cards are emulated by NFC devices and NFC Forum tags are formatted and the protocols for communicating with them. There are three modes of operation:" Old: " . read/write mode - the NFC device can read or write records, each of which has a type. There are currently 4 defined record types (Text, URI, Smart Poster, and Generic Control)..." New: " . read/write mode - the NFC device can read or write records, each of which has a type. There are currently several defined record types (Text, URI, Smart Poster, etc.)..." (comment only: The Generic Control RTD specification has been recently deprecated by NFC Forum. Better to leave it out.) Old: " . card emulation mode - where a device acts in the same way as an NFC card, e.g. enabling an NFC enabled phone to be used for contactless ticketing and payment applications. NFC cards have limited storage capabilities, e.g. the MiFare Classic 1K with 1024 bytes of data storage split across 16 sectors." New: " . card emulation mode - where an NFC device emulates a smart card, e.g. enabling an NFC enabled phone to be used for contactless ticketing and payment applications. Emulated cards may have limited storage capabilities, e.g. the MiFare Classic 1K with 1024 bytes of data storage split across 16 sectors." Old: "The NFC APIs should be able to selectively write to NFC cards when several are in range of the NFC device, e.g. when the user has several such cards in their wallet." New: "The NFC APIs should be able to selectively write to a specific emulated NFC card when several are embedded in a single NFC device, e.g. when the user has several such cards in their wallet application." Old: "The Near field communication Working Group will define an API for Web page scripts to use the NFC data exchange format, enabling a range of use cases for reading, writing and data exchange with NFC devices." New: "The Near Field Communication Working Group will define an API for Web page scripts to use the NFC data exchange format and APDUs, enabling a range of use cases for reading, writing, emulating cards and data exchange with peer NFC devices." Old: "The NFC API will be designed to be compatible with the NFC Forum's NDEF specifications." New: "The NFC API will be designed to be compatible with current NFC specifications." (comment only: NFC Forum is one of several bodies responsible for NFC related specifications. Other bodies like Global Platform, EMVCo, ETSI, ISO, etc. have important contributions to the NFC ecosystem. For example, an NFC API accessing the Secure Element (SE) inside an UICC may need to take into account secure access criteria established by Global Platform.) Old: ". NFC Card emulation mode for NFC devices, e.g. to emulate a card supporting APDU operations to allow the use of a phone for payments or for unlocking electronic door locks" New: ". Initiation of NFC Card emulation mode for NFC devices, e.g. to emulate a card supporting APDU operations to allow the use of a phone for payments or for unlocking electronic door locks" Old: "The very short range of NFC devices requires users to make a conscious decision to put one of the devices into the appropriate mode and to bring the devices physically together, and this should enable a simpler security model that minimizes the need for applications to ask for explicit user permission." New: "The very short range of NFC devices requires users to make a conscious decision to put one of the devices into the appropriate mode and to bring the devices physically together, and this should enable a simpler security model that minimizes the need for applications to ask for explicit user permission. The need for direct user involvement under certain circumstances will need to be explored." Thanks, Bryan Sullivan +++++ From: Dave Raggett <dsr@w3.org> Date: Fri, 27 Jul 2012 09:55:18 +0100 Message-ID: <50125776.90107@w3.org> To: "public-nfc@w3.org" <public-nfc@w3.org> The W3C Advisory Committee has been asked to review the NFC Charter. This is a good moment to contact your AC Rep and ensure that he or she responds to the review on behalf of your organization, so that we get enough responses to launch the group. The charter: http://www.w3.org/2012/05/nfc-wg-charter.html The Call for Review: https://lists.w3.org/Archives/Member/w3c-ac-members/2012JulSep/0018.html How to find the contact details for your AC Representative: https://www.w3.org/Member/ACList The deadline for responses is 23:59, Boston time on 24 August 2012. -- Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Wednesday, 22 August 2012 20:27:48 UTC