Bureaucrats, canmove, Confirmed users
2,887
edits
WebAPI/ContactsAPI: Difference between revisions
Jump to navigation
Jump to search
→Goals: clarify related work re: a more 'appy' API
(move status further up, move W3C DAP expansion near FAQ since it's not practically necessary for most folks (i.e. anyone other than standards people, ahem), add articles section) |
(→Goals: clarify related work re: a more 'appy' API) |
||
| Line 3: | Line 3: | ||
== Goals == | == Goals == | ||
Provide read/write DOM API access to the device address book, and the contacts contained therein with a simple minimal API that has a high-degree of interoperability with both device address books and commonly published web contact information ( | Provide read/write DOM API access to the device address book, and the contacts contained therein with a simple minimal API that has a high-degree of interoperability with both device address books and commonly published web contact information ([[vCard4]]/[[hCard]]). - [[User:Tantek|Tantek]] | ||
Related: | Related: | ||
* | * '''[[#W3C_DAP_Contacts|W3C DAP work]]''' - similar but problematic. See the [[#W3C_DAP_Contacts|W3C DAP section below]] for how the ContactsAPI fixes key problems with the DAP approach. | ||
* A more "appy" | * '''A more "appy" Contacts API''' - that allows web apps to both access and be providers for contacts. This [[ContactsAPI]] is focused specifically on ''device'' contacts access for reasons of design simplification and prioritization for [[B2G]]. For exploring a broader / more 'appy' Contacts API see work on [[WebActions]], [[WebActivities]], and [[Labs/Contacts/ContentAPI]]. | ||
== Status == | == Status == | ||