Re: Publishing updated working drafts to match the editor's drafts before TPAC

As for the Messaging API: it is quite stable for sending and receiving
messages. However, the parts that are dealing with messages data model
(storage, conversations, search etc) need more proofing, which should
be based on implementations.

Similarly, the implied data model in the Contacts API would need more
proofing, and we need implementations for that.

In principle, Call History has the same problems, although not part of
the current scope.

We need to consider additional use cases for all of the above:
accessing messages, contacts and calls in Bluetooth-paired deviced,
via MAP and PBAP profiles (and for Telephony, HFP). These can be
either transient, or with persistent storage. This is a critical use
case for us.

Since the DataStore spec has been dropped, these issues have not been discussed.

Best regards,
Zoltan


On Thu, Oct 9, 2014 at 6:45 AM, Wonsuk Lee <wonsuk73@gmail.com> wrote:
> Forks,
> Regarding below working drafts in SysApps, I would propose to publish
> updated working drafts sync with current editor's draft before TPAC. I will
> send CfC email for each specs as a process.
>
> - Task Scheduler
> - Contacts Manager APIs
> - Messaging APIs
> - Telephony APIs
> - TCP UDP Socket APIs
>
>
> Kr, Wonsuk.
> =========================================
> 이 원 석 (Wonsuk, Lee) / Principal Engineer, Ph.D
> SAMSUNG ELECTRONICS Co., LTD. (三星電子)
> Mobile: +82-10-5800-3997
> E-mail: wonsuk11.lee@samsung.com, wonsuk73@gmail.com
> http://www.wonsuk73.com/, twitter: @wonsuk73
> -----------------------------------------
> Inspire the World, Create the Future !!!
> =========================================

Received on Friday, 10 October 2014 13:41:07 UTC