W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2010

Messaging API status and next steps

From: María Ángeles Oteo <maoteo@novanotio.es>
Date: Tue, 2 Nov 2010 18:37:51 +0100
To: <public-device-apis@w3.org>
Message-ID: <031901cb7ab4$ae98e9f0$0bcabdd0$@es>

 After the publication of the PFWD few comments [1] have been received about
the Messaging API [2]. 

Formerly, we decided to split messaging API in 3 parts:

   A) Sending and Subscription
   B) Reading messages from the device memory
   C) Managing messages in device memory (e.g. folder management)

 Based on the comments about security and the need to provide multipart
handling capability for reception we suggest to change the structure of the

   A) Sending: Simple API with no MIME multipart support.
   B) Subscribing and reading: We need to add MIME multipart support for
this one and filters (hopefully the same) for both subscription and message
retrieval: subscribe only to SMSs coming from a particular number or
retrieve from the device memory only the messages that match that filter.
   C) Message management.

  The priority for us is:
   1) Create a version of the "Message Sending API" during the week after
TPAC based on our FPWD.
   2) Create a version of the "Message Subscribing and Reading API":
Starting after we have finished with 1). I am not very familiar with MIME
multipart, so any help would be extremely appreciated. 

  The only pending comment from [1] is about Email syntax, and I think we
should follow Robin's suggestion: "just give a DOMString, leaving it up to a
library to expose the vicious intricacies of email syntax (and letting the
vast majority of people not care about what is essentially a steaming pile
of corner cases)?"

Best Regards

[1] http://lists.w3.org/Archives/Public/public-device-apis/2010Aug/0019.html
[2] http://www.w3.org/TR/messaging-api/
Received on Tuesday, 2 November 2010 17:38:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:24 UTC