RE: Contacts API: vCard vs. PoCo

Richard, and all,

My opinion is that it is need to discuss the use case of contact API.
Also, if necessary, the comparison table of the contact related 
specification is required (based on the use cases and requirements).

It will be very helpful to decide the design of contact API.
(superset vs. common denominator)

In a sense, Contact API, it is very similar situation of Media annotation works
In case of media annotation, there exists several format for media metadata,
and WG decided to support ontology, which cover the current existing media
metadata, and current API is for the ontology on media resource.

One more thing is that I suggest to support lunar calendar system on birthday 
attribute of current contact API (include date class in calendar API). 
It will be very helpful to deploy DAP's in some area(Asia/Pacific).

Also, I can help to progress contacts API.

Best Regards,


-----Original Message-----
From: [] On Behalf Of
Sent: Wednesday, November 11, 2009 5:06 AM
Subject: Contacts API: vCard vs. PoCo

Hi all,

At the TPAC we agreed to implement a superset of Contact properties as
part of the Contacts API. In this discussion we agreed around
incorporating vCard [1] as the base of this Interface. This has now been
updated and is available online [2] (once again, this is an early
editor's draft so please take with two sugars).

In the mean time, the Portable Contacts API (PoCo) [3] has come to the
attention of a few members of the group as a potential contender to
vCard for the basis of the Contacts API.

Parsing both specs, I understand that vCard represents the most closely
aligned standard to traditional offline Contact databases (E.g.
Outlook). What vCard lacks is some properties that have arisen from
online social networking over the last few years since the introduction
of the vCard standard (in 1996). The Portable Contacts API aims to merge
the traditional vCard standard with the OpenSocial specifications
resulting in a hybrid API for accessing contacts data from both
traditional address books and online social networks. 

In my understanding from reading the latest PoCo API draft spec [4] I do
see breaks from the traditional vCard specification. Largely, this spec
extends the work of IETF with the work of OpenSocial although a lot of
conventions strictly defined in vCard seem to be ignored or removed from
PoCo. Having said this, tools do exist for converting vCards to PoCo and
PoCo to vCards implying that interop and any necessary conversion is
possible [5].

As PoCo represents a larger set of Contact attributes, I'd like to
propose that we make PoCo the basis of the DAP Contacts API.

On a final note, it is worth noting that both vCard and PoCo represent a
superset of both initial Contact API inputs to the DAP WG: [6] and [7].

If anyone has further thoughts or would like to initiate further
discussion please let us know.

br/ Richard








|        |   Rich Tibbett
|        |   Orange Labs UK
| orange |   E:

Received on Wednesday, 11 November 2009 01:52:56 UTC