Input to Contacts property list decision

Re the decision today, as should be noted in the chat log:

RESOLUTION: the Contacts API provides a set of core properties that need
to be supported, and suggests a prefix-based extensions mechanism for
additional properties

Re the likelyhood of extensions appearing quickly, give that W3C adopts
a limited set of fixed property names. We expect that there will be
extensions quickly if the basic set of properties is not extensible in a
web runtime - independent way. We need the ability to support
vocabularies such as OMA CAB (Converged Address Book) through this API.
This is needed without having to design each device web runtime to
support the specific properties of the native client (which can change,
and be a "default" or other as the "current" client). In essence we
should have the ability to deploy web runtimes on any device, and have
the property vocabulary supported by the (current) address book client
transparently supported by the API. This is the approach to be taken by
AT&T in our products and devices, at least.

Best regards,
Bryan Sullivan | AT&T

Received on Wednesday, 2 December 2009 15:33:00 UTC