2009/dap/messaging Overview.html,1.15,1.16

Update of /sources/public/2009/dap/messaging
In directory hutz:/tmp/cvs-serv18785

Modified Files:
	Overview.html 
Log Message:
noted issues from Suresh's email <http://www.w3.org/mid/D37CC1B151BD57489F4F89609F168FE804FEC4EA@XCH01DFW.rim.net>


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/messaging/Overview.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- Overview.html	8 Apr 2010 20:49:51 -0000	1.15
+++ Overview.html	14 Apr 2010 12:58:10 -0000	1.16
@@ -43,7 +43,7 @@
     Since not all devices will have all messaging functionality (e.g. a phone may have only SMS and MMS while a PC may have only email) there is a need to indicate that conformant implementations need only expose available functionality.
     </p>
 
-	<p>Implementations that use ECMAScript to implement the APIs defined in this specification must implement them in a manner consistent with the ECMAScript Bindings defined in the Web IDL specification [[!WEBIDL]], as this specification uses that specificationŐs terminology.</p> 
+	<p>Implementations that use ECMAScript to implement the APIs defined in this specification must implement them in a manner consistent with the ECMAScript Bindings defined in the Web IDL specification [[!WEBIDL]], as this specification uses that specification's terminology.</p> 
     
     
     <section id='informative'>
@@ -97,9 +97,11 @@
     <section>
     	<h1>Scope</h1>
     	<p>
-    	This specification is limited to providing a scripting API for creating, sending and receiving messages; as well as inspection and manipulation of message folders on a device. The supported messaging types include SMS, MMS and Email.
+    	This specification is limited to providing a scripting API for creating, sending and receiving messages. The supported messaging types include SMS, MMS and Email.
     	</p>
     	
+      <p class="issue">Should we add functionality for inspection and manipulation of message folders on a device, including save and delete functions?</p>
+
     	<p class='note'>
     	The specification does not replace RFCs for Mail or SMS URLs. The specification includes complementary functionality to these.
     	</p>
@@ -352,6 +354,10 @@
 							<dd>
 							</dd>
 						</dl>
+            <div class='exception' title='MessageSendException'>
+              Raised when an error has occured sending this message.
+              <div class="issue">we need to specify this exception further</div>
+            </div>
 					</dd>
 			</dl>
 		</section>
@@ -405,6 +411,9 @@
 				</dd>	
 				
 			</dl>	
+
+      <p class="issue">Should there be functionality to add recipients as Contacts (as defined in this Working Group's Contacts specification), as opposed to simple strings. Or should it be left to the user agent?</p>
+
 		</section>

Received on Wednesday, 14 April 2010 12:58:14 UTC