...
...
...
...
| Warning |
|---|
The Contact service is deprecated. Contact records can be added via selected services, such as Person and Organization, that support Contacts as a sub-resource. |
| Include Page | ||||
|---|---|---|---|---|
|
| HTML Table | ||||||
|---|---|---|---|---|---|---|
| ||||||
Brief Description
| Wiki Markup |
|---|
{multi-excerpt-include:Contact Service Description and Assumptions|name=brief-description|nopanel=true} |
...
...
a
...
full
...
desciption,
...
visit
...
the
...
...
...
...
...
page.
...
Assumptions
| Wiki Markup |
|---|
{multi-excerpt-include:Contact Service Description and Assumptions|name=brief-assumptions|nopanel=true} |
...
...
a
...
complete
...
list
...
of
...
assumptions,
...
visit
...
the
...
...
...
...
...
page.
...
References
Contact Service Description and Assumptions
Contact Service Entity Diagrams
REST Interfaces - CRUD Operations
The Contact Service offers a RESTful interface to CRUD (create, read, update, and delete) operations on individual Contact items. Because contact info is always associated to a Person or Organization, the resource model will reflect this. Applications will not read individual items but rather will search for items associated to a given person or organization. These will then be organized by media type and priority. Create operations will similarly add an item associated to a person or organization. Update, and Delete operations could reference individual items, but we may preserve the association path for consistency and as an additional sanity check.
For full details, visit Contact REST APIs - Release v0.1.
RPC-Style Setup/Metadata Operations
TBD