W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2010

ISSUE-98: contactsDataModel

From: Suresh Chitturi <schitturi@rim.com>
Date: Tue, 28 Sep 2010 15:14:19 -0500
Message-ID: <D37CC1B151BD57489F4F89609F168FE8070EB40A@XCH01DFW.rim.net>
To: <public-device-apis@w3.org>
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)





This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 29 September 2010 12:03:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:46 UTC