- From: Max Froumentin via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 25 Mar 2010 16:11:20 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/messaging
In directory hutz:/tmp/cvs-serv31128
Modified Files:
Overview.html
Added Files:
requirements.html
Log Message:
separate out requirements
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/messaging/Overview.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- Overview.html 24 Mar 2010 14:03:39 -0000 1.8
+++ Overview.html 25 Mar 2010 16:11:18 -0000 1.9
@@ -476,41 +476,6 @@
</section>
- <section>
- <h2>Use-cases and Requirements</h2>
- <section>
- <h3>Use-cases</h3>
- <section>
- <h4>Use case 1: Create and send message</h4>
- <p>The user wants to create and send a message (of any configured type). The Messaging API allows creation and sending of messages all performed within the web application, without distracting change to other application. The Messaging API also allows progress feedback to the web application on whether the message was sent or not.
- </p>
- <p class=note>(The SMS and Mailto URL schemes satisfy the "create" and "enable send" part of this use case.) </p>
- </section>
- <section>
- <h4>Use case 2: Create and send message from particular account</h4>
- A user has multiple messaging accounts configured on a device (e.g. "personal", "work"). The user wants to send a message through the "personal" account. The Messaging API allows selection of messaging account for outgoing messages.
- </section>
- <section>
- <h4>Use case 3: New message event</h4>
- A web page can register to be informed when a new message arrives at a local inbox. There is no need to poll for new messages in this case.
-
- </section>
- </section>
-
- <section>
- <h3>Requirements</h3>
- <p>
- This interface:
- </p>
- <ul>
- <li><em title="must" class="rfc2119">must</em> support messages in one or several formats and transports supported by the platform (email, SMS, MMS...);</li>
- <li><em title="must" class="rfc2119">must</em> allow creating and sending messages;</li>
- <li><em title="must" class="rfc2119">must</em> support multiple accounts for each transport/format type;</li>
- <li><em title="must" class="rfc2119">must</em> support setting various envelope fields corresponding to the message type (email, SMS...);</li>
- <li><em title="must" class="rfc2119">must</em> support attaching files when the format allows it.</li>
- </ul>
- </section>
- </section>
<section class='appendix'>
--- NEW FILE: requirements.html ---
<!DOCTYPE html>
<html>
<head>
<title>Requirements & Use Cases for The Messaging API</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<script src='../ReSpec.js/js/respec.js' class='remove'></script>
<script class='remove'>
var respecConfig = {
specStatus: "ED",
shortName: "messaging-api-req",
publishDate: "2010-02-02",
// previousPublishDate: "1977-03-15",
edDraftURI: "http://dev.w3.org/2009/dap/messaging-api-req/",
// lcEnd: "2009-08-05",
maxTocLevel: 2,
noIDLSorting: true,
noIDLIn: true,
editors: [{name:"Dzung Tran",company:"Intel",companyURL:"http://intel.com"},
{name:"Max Froumentin",company:"Opera Software ASA",companyURL:"http://www.opera.com"}]
};
</script>
<script src='../common/config.js' class='remove'></script>
<style type="text/css">
table { border: 1px solid black }
th { border: 1px solid black }
tr.interface { background-color: #ddd }
</style>
</head>
<body>
<section id='abstract'>
<p>This specification defines the requirements and introduces use cases for the Messaging API [[DAPMESSAGING]]</p>
</section>
<section id="sotd">
<p>This document represents the early consensus of the group on
the requirements and use cases of the proposed Messaging
API. Issues and editors notes in the document highlight some of
the points on which the group is still working and would
particularly like to get feedback.</p>
</section>
<section class='introduction'>
<h2>Introduction</h2>
<p>
The Messaging API defines a high-level interface to Messaging
functionality, including SMS, MMS and Email. It includes APIs to
create, send and receive messages, and to inspect and manipulate
the folders where the messages are kept.
</p>
</section>
<section>
<h2>Use-cases and Requirements</h2>
<section>
<h3>Use-cases</h3>
<section>
<h4>Use case 1: Create and send message</h4>
<p>The user wants to create and send a message (of any configured type). The Messaging API allows creation and sending of messages all performed within the web application, without distracting change to other application. The Messaging API also allows progress feedback to the web application on whether the message was sent or not.
</p>
<p class="note">(The SMS and Mailto URL schemes satisfy the "create" and "enable send" part of this use case.) </p>
</section>
<section>
<h4>Use case 2: Create and send message from particular account</h4>
A user has multiple messaging accounts configured on a device (e.g. "personal", "work"). The user wants to send a message through the "personal" account. The Messaging API allows selection of messaging account for outgoing messages.
</section>
<section>
<h4>Use case 3: New message event</h4>
A web page can register to be informed when a new message arrives at a local inbox. There is no need to poll for new messages in this case.
</section>
</section>
<section>
<h3>Requirements</h3>
<p>
This interface:
</p>
<ul>
<li><em title="must" class="rfc2119">must</em> support messages in one or several formats and transports supported by the platform (email, SMS, MMS...);</li>
<li><em title="must" class="rfc2119">must</em> allow creating and sending messages;</li>
<li><em title="must" class="rfc2119">must</em> support multiple accounts for each transport/format type;</li>
<li><em title="must" class="rfc2119">must</em> support setting various envelope fields corresponding to the message type (email, SMS...);</li>
<li><em title="must" class="rfc2119">must</em> support attaching files when the format allows it.</li>
</ul>
</section>
</section>
<!--************************************* /Requirements ******************************************-->
</body>
</html>
Received on Thursday, 25 March 2010 16:11:25 UTC