ISSUE-98: contactsDataModel (from Suresh)

[forwarding for Suresh]

From: Suresh Chitturi
Sent: Tuesday, September 28, 2010 3:14 PM
To: public-device-apis@w3.org<mailto:public-device-apis@w3.org>
Subject: ISSUE-98: contactsDataModel

Hi all,

While reviewing the Contacts API updated draft, my main concern at this point lies with the contact format used by the API. It largely continues to use/refer to the schema from Portable Contacts, but we have seen equal interest to use other formats such as vCard and OMA CAB.

ISSUE-98: http://www.w3.org/2009/dap/track/issues/98

I understand we have set a public list (thanks to Thomas) for coordination between the various groups including IETF, PoCo, and OMA CAB to discuss  on the convergence aspects, but it is not clear how close we are to convergence or how long we would need to wait before we can proceed with a decision within our group.

Can we please add this topic to this week’s agenda so we may try to discuss how this can be resolved going forward?

I’d suggest that we address this in multiple steps e.g. as below

1)      Agree on the set of fields to include
2)      Decide on the structure and semantics of the selected fields
3)      Address the mapping of these fields to other known formats
4)      Extension mechanisms (which we seem to have in place and it looks fairly ok to me)

Starting with the fields, I am generally happy with the set of contact attributes in the current spec which are compatible with fields in vCard [RFC 2426], and OMA CAB based on my checks, except the following ones:
-          updated
-          relationships
-          anniversary (not present in vCard)


Thanks,
Suresh
---------------------------------------------------------------------