- From: SULLIVAN, BRYAN L (ATTCINW) <BS3131@att.com>
- Date: Mon, 26 Oct 2009 22:44:03 -0700
- To: "W3C Device APIs and Policy WG" <public-device-apis@w3.org>
Here is some input to the Contacts API requirements for next week: 1) There should be a requirement supporting discovery of supported fields: * It MUST be possible to discover the supported fields for Contacts entries. 2) There should be a requirement supporting clearing of a set of Contacts entries, e.g. a specific entry or the results of a search: * It MUST be possible to clear a list of Contacts entries. 3) There should be a requirement supporting clearing of all Contacts entries. * It MUST be possible to clear all Contacts entries. Re "Are there convincing use cases for supporting multiple address books in v1 (as opposed to just a default one, and maybe exposing more later)?": Yes, there are convincing use cases. It has been a standard feature in mobile phones for as long as contacts have been a feature, that there is a phone-based contact list and a SIM-based contact list. These two address books, at least, should be supported. Best regards, Bryan Sullivan | AT&T
Received on Tuesday, 27 October 2009 05:44:38 UTC