W3C home > Mailing lists > Public > public-sysapps@w3.org > November 2012

RE: Contacts API draft

Date: Wed, 07 Nov 2012 09:03:45 +0000
To: "Dumez, Christophe" <christophe.dumez@intel.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>
Cc: Wayne Carr <wayne.carr@intel.com>, Sakari Poussa <sakari.poussa@intel.com>, JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>
Message-id: <A52BC7FE998B7E43BB74213DE5CD369008B25943@EX10-MB2-MAD.hi.inet>
Hi Christophe, all,

I have been comparing the two proposals on the table for Contacts API, and they happen to have more similarities than differences what is good news in order to reach a consolidated proposal. Let me comment on the main differences:

-Filtering: Intel's proposal allows applying virtually any type of filter as it allows the definition of composite filters. Note though that in order to have an appropriate performance the runtime will need to define indexes for the different filtering operations. Having so flexible filtering implies creating a virtually unlimited set of indexes. Christophe, what is the performance you expect the implementation to have? and how do you propose to solve that issue?

-ContactChangeEvent: Intel's proposal allows notifying changes in multiple contacts simultaneously indicating which contacts have been deleted, created and modified. Is the system expected to wait for some time before firing an event with multiple changes or do these notifications of multiple changes apply just to really simultaneous changes (e.g. sync with an external address book).

-getSimContacts(): Our proposal included this method to be able to retrieve the contacts from the SIM card (e.g. to copy them to the device address book). It is not the intention to deal in any other way with the SIM's address book, so neither the rest of the methods (find, remove, etc) nor the ContactChangeEvent apply in principle to SIM contacts.

-read-only contacts in Intel's proposal: Christophe, could you elaborate what is the use case for that?

-Additional fields in Intel's proposal: relationship, phoneticGivenName; phoneticFamilyName; favorite; ringtone

-Additional fields in our proposal: genderIdentity; carrier attribute in tel field

Any other relevant difference that I am missing?

Best regards,

De: Dumez, Christophe [mailto:christophe.dumez@intel.com]
Enviado el: viernes, 26 de octubre de 2012 11:01
Para: public-sysapps@w3.org
CC: Wayne Carr; Sakari Poussa
Asunto: Contacts API draft


We have uploaded an initial draft proposal of the Contact API to:

It is based on the corresponding Tizen and B2G APIs:

For now, the Contacts and Filtering APIs are merged in one document (as requested by Adam Barth). However, the filtering API is generic and could be moved out of this specification if we wish to use it in other specifications as well.

We are looking forward to your feedback.

Christophe Dumez
Linux Software Engineer, PhD
Intel Finland Oy - Open Source Technology Center


Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
Received on Wednesday, 7 November 2012 09:04:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:10 UTC