Owner Contact Information
Is there any reason why the owner's contact information is so limited? We can use the contact API to fetch name, address, email, and all other personal information about everyone BUT the user in question.
The sample use case in the documentation talks about getting shipping information for a friend on your contacts list. Well, yes, that will work, but don't you want the USER's address 99% of the time?
I realize there's some privacy concerns here, but isn't that handled with the prompting to release contact info? Isn't the release of a user's entire contact list more damaging than the user's contact info?
Or, is there going to be another Live Data API to handle the user's own contact information? I'm sure that users would appreciate having to enter their shipping information only once rather than having to do it on every site they shop at, especially if they move and only have to update it once.
Bill:
You are absolutely right. It makes sense to include the owner information as part of the information returned with the Address BGook. The reason this is not currently the case with the contacts API is that the Address Book does not store the user profile information.
We are working to expose the user profile the same way we expose contacts. Your question generated a lot of discussions inside our team to see how we can provide the user profile as part of the contact information soon.
I for one would love to see this, especallity the "LiveID for your website" signup scenerios.
So the users wouldnt have to re-type duplicate signup details each time.
Would this feature be a high priority for the WL Data team?