- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 06 Apr 2011 14:34:50 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/messaging
In directory hutz:/tmp/cvs-serv31148
Modified Files:
Overview.html
Log Message:
note on request for comparison
note on no feature detection
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/messaging/Overview.html,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- Overview.html 6 Apr 2011 13:50:31 -0000 1.37
+++ Overview.html 6 Apr 2011 14:34:48 -0000 1.38
@@ -33,6 +33,10 @@
</p>
</section>
+
+ <section id="sotd">
+ <p><strong>This draft proposes a vastly different approach to the <a href="http://www.w3.org/TR/2011/WD-messaging-api-20110120/">previously published version</a>, using URI schemes as a way to address different messaging protocols instead of using separate methods. The group is specifically looking for feedback on which approach is felt like the most useful.</strong></p>
+ </section>
<section id='conformance'></section>
<p>
@@ -105,6 +109,10 @@
<h1>Supported messaging types</h1>
<p>The specification supports sending messages on top of protocols for which a URI scheme has been defined, including SMS, MMS and emails.</p>
</p>
+
+ <p class="issue">Using a single method to send message across many protocols make it impossible to detect whether a given user agent supports a specific messaging protocol.</p>
+
+
<section>
<h2>SMS specific concerns</h2>
<p>
@@ -120,6 +128,7 @@
<p>
The <a href='#devicemessaging'>DeviceMessaging</a> object is exposed on the <code>navigator.device</code> object, as defined in [[!CORE-DEVICE]].
</p>
+
<div class='idl' title='Device implements DeviceMessaging'></div>
Received on Wednesday, 6 April 2011 14:34:51 UTC