canmove, Confirmed users
2,675
edits
WebAPI/ContactsAPI: Difference between revisions
Jump to navigation
Jump to search
→FAQ: How do we best converge contact data models
(use dated version URL for DAP contacts since they morphed it into something about Pick Contacts Intent - very different from before) |
(→FAQ: How do we best converge contact data models) |
||
| Line 251: | Line 251: | ||
== FAQ == | == FAQ == | ||
=== How do we best converge contact data models === | |||
The ContactsAPI is based on the popular [[vCard]]/[[hCard]] standards. | |||
For contact data models, the best way to converge is to base work on those two. We have been doing this across numerous contacts related formats/schema/API using vCard as the point of coordination, and the IETF VCARDDAV list for that. | |||
Any exceptions must be noted explicitly with reasons. | |||
One exception is the "carrier" field which has been marked experimental, and which should be proposed to VCARDDAV by someone who can justify it with real world use cases / examples, or dropped from the ContactsAPI. | |||
=== Why are givenName familyName arrays instead of optional === | === Why are givenName familyName arrays instead of optional === | ||
* could use clarification of why a number of fields are arrays instead of optional DOMString. e.g. givenName, familyName. Those seem like 0-or-1 cases, not lists. | * could use clarification of why a number of fields are arrays instead of optional DOMString. e.g. givenName, familyName. Those seem like 0-or-1 cases, not lists. | ||