W3C home > Mailing lists > Public > public-sysapps@w3.org > April 2014

RE: Request to report the status of the specs

Date: Mon, 07 Apr 2014 10:31:02 +0000
To: "Kis, Zoltan" <zoltan.kis@intel.com>, Wonsuk Lee <wonsuk73@gmail.com>
Cc: "public-sysapps@w3.org" <public-sysapps@w3.org>
Message-id: <A52BC7FE998B7E43BB74213DE5CD36906DAA0CA1@EX10-MB1-MAD.hi.inet>

I was going to attend the F2F meeting but personal issues have finally prevented me from traveling.

Please see more comments inline.


On 4 abr 2014 at 21:23:20, Kis, Zoltan wrote:
> Hi Wonsuk,
> On Fri, Apr 4, 2014 at 9:48 PM, Wonsuk Lee <wonsuk73@gmail.com> wrote:
>>> Regarding the Messaging spec, the latest developments with DataStore
>>> have not been applied yet - waiting for the DataStore spec to
>>> stabilize. This also applies to the Contacts API.
>> I think we already had enough time to review for DataStore API. I guess
>> so far we didn't have much comments on that from other editors for
>> contacts and messaging APIs and other members of the group. So if we
>> have a consensus about  there are no outstanding issue and objection
>> within the group, we need to apply that to contacts and messaging APIs.
>> What do you think?
> Yes, we have discussed the DataStore API extensively.
> The use cases we have for backends:
> - messages coming from device/built-in modem
> - messages coming from paired Bluetooth devices via MAP (multiple
> devices should be supported)
> - contacts coming from device (multiple address books need to be supported)
> - contacts coming from paired Bluetooth devices via PBAP (multiple
> devices should be supported)
> - similarly, local call history
> - and call history coming from paired Bluetooth devices via PBAP and
> HFP (multiple devices should be supported).

Some of these use cases, basically the Bluetooth-related ones, are out of the current scope of Messaging / Contacts APIs

> We need to discuss how to solve these use cases with the existing
> DataStore spec. It would be good if the spec would contain some
> guidelines for implementations regarding the use cases above.
> Basically it boils down to support service id's for messaging and call
> history, and address book id for contacts. If these are part of the
> data, then no issues.
> Anyway, I hope that after this F2F we can go and implement DataStore,
> then give feedback and run another cycle.

I agree it is time to implement DataStore in Messaging / Contacts APIs.

> Best regards,
> Zoltan


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 Monday, 7 April 2014 10:31:32 UTC

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