RE: Message API Status

Hi Frederick

I did the split and created the simplified version which already includes a
more detailed security section so the action-221 can be closed. Dom already
sent the FPWD Cfc [1].

Now we are working in the new specs for MessageFinder and Folder Management
API.

Best regards
María

[1] http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0111.html

-----Original Message-----
From: public-device-apis-request@w3.org
[mailto:public-device-apis-request@w3.org] On Behalf Of
Frederick.Hirsch@nokia.com
Sent: lunes, 02 de agosto de 2010 23:56
To: public-device-apis@w3.org
Cc: Frederick.Hirsch@nokia.com
Subject: Message API Status

Is the following accurate and complete? Do the editors or WG have any
updates or corrections?

(1) Messaging API status (as of DAP F2F) [1]

The Messaging API editors draft was updated in advance of the F2F to split
the APIs for different messaging technologies. APIs were added  for listing
messages, methods added for folder management and moving messages between
folders. The following resolution was reached during the F2F: RESOLUTION:
Split Messaging, try to reach FPWD with just create/send/receive ASAP; have
a separate MessageFinder API mirroring Contacts and Gallery; build folder
management on top of that.

(2) Open Actions

This means there is an editorial action to perform this split, to simplify
the Messaging API draft and move material into a new MessageFinder API draft
(as well as removing folder functionality from the Messaging API draft).
There was no explicit editorial action assigned, perhaps there should be.

The WG also agreed to add a security section before publishing, with the
following related actions:

ACTION-221 -- Maria Angeles Oteo to draft a security section for Messaging

ACTION-222 -- Thomas Roessler to review the Messaging security section

regards, Frederick

Frederick Hirsch, Nokia
Co-Chair, W3C DAP Working Group

[1] http://dev.w3.org/2009/dap/messaging/

Received on Tuesday, 3 August 2010 09:53:24 UTC