Details on Product Contacts API

All Issues

New issues for this product are notified to public-device-apis@w3.org (change it).

There are 12 issues listed in the system.

ID	State	Title	Raised on	Product	Open Actions
ISSUE-10 ContactsReq	CLOSED	Gathering requirements for Contacts API	2009-08-25	Contacts API	0
ISSUE-72 uriSchemesInContacts	CLOSED	Usage of URIs for sms, tel:, etc in PIM APIs	2010-01-27	Contacts API	0
ISSUE-86 contactsSharing	CLOSED	Privacy issue about sharing other users contact information from own address book	2010-07-13	Contacts API	0
ISSUE-93 contactsWrite	CLOSED	Do we want to stage the release of contacts API between read and write access?	2010-07-14	Contacts API	0
ISSUE-98 contactsDatamodel	CLOSED	On what data model should the contacts API be based?	2010-08-25	Contacts API	0
ISSUE-106 tzContacts	CLOSED	Does Contacts API having a timezone field make sense, should it be utfOffset or utcOffset and tz to better match vCard?	2011-01-19	Contacts API	0
ISSUE-110 contactEventLoop	CLOSED	Contacts API needs to integrate HTML Event Loop	2011-03-16	Contacts API	0
ISSUE-111 urlInContacts	CLOSED	Should (some of the) ContactField objects use URLs rather than free-form strings?	2011-06-01	Contacts API	0
ISSUE-119 customErrorObjects	CLOSED	Should we have different Error objects for each spec, or should we go the way that Exceptions are going and only have one object	2011-08-31	Contacts API	0
ISSUE-43 storageAwareness	POSTPONED	Should we make the contacts API data-storage-aware?	2009-11-03	Contacts API	0
ISSUE-77 addressBookManagement	POSTPONED	Contacts need management of address book, different role than contacts user	2010-03-16	Contacts API	0
ISSUE-99 contactsForms	POSTPONED	Integration of Contacts API in the DOM (e.g. through <input type=contacts>)	2010-08-25	Contacts API	0

All Actions

There are 0 actions.

Add a new action item.

See only open and raised issues and actions.