System Applications WG: Messaging API

From W3C Wiki
Jump to: navigation, search

This is the Wiki page for the Messaging API draft in the W3C System Applications WG


The Web Telephony API stakeholders are the following:

  • implementor: implements the API specification in a Web runtime, using the underlying platform features
  • developer: implements applications using the API specification
  • end user or user: provides input to the applications.

Use Cases (list of links)

The main use cases of the Telephony API from the end users point of view are the following:

  • send SMS message to a remote party
  • send MMS message to a remote party conform to MMS 1.3 specification
  • receive message delivery indications for SMS and MMS
  • receive SMS messages
  • receive MMS messages conform to MMS 1.3 specification
  • access messages stored on the device
  • search in saved messages (by fields and filters defined and documented by the implementations)
  • remove a message
  • mark messages as read
  • find message conversations grouped by a user given field supported by the implementation
  • remove a conversation
  • support multiple messaging services (user accounts of messaging service providers)
  • select which messaging service to use when sending messages
  • set a default messaging service to be used when the messaging service is not specified by the user

The main use cases from the developers point of view are to use the API to programmatically implement the user use cases from above. In addition, the following programmatic use cases MUST be supported

  • track the progress of asynchronous operations


Web Messaging API Editor's Draft