Beef up contact resource contents in REST API
There are a few areas where the the contents of Contacts in the REST API could use some work:
1) There are fields (phone numbers, anniversary, others) that are in the client apps and even in the CSV export output on office.com that are not in the responses provided by the API and these should be added to the response/resource
2) The client apps allow one to select/define the "type" of email address and physical address yet this select is not reflected in the API response
3) The client apps allow one to select/define an email address as "default"; similarly it is allowed for a physical address. In neither cases is that attributed reflected in the API response.