W3C home > Mailing lists > Public > public-dap-commits@w3.org > December 2012

CVS 2009/dap/camera

From: CVS User akostiai <cvsmail@w3.org>
Date: Mon, 10 Dec 2012 10:40:54 +0000
Message-Id: <E1Ti0n8-0005On-G8@roscoe.w3.org>
To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/camera
In directory roscoe:/tmp/cvs-serv20751

Modified Files:
	Overview.html 
Log Message:
annotate RFC terms in 'Security and privacy considerations' section

--- /sources/public/2009/dap/camera/Overview.html	2012/12/07 10:38:02	1.140
+++ /sources/public/2009/dap/camera/Overview.html	2012/12/10 10:40:54	1.141
@@ -111,11 +111,11 @@
     <section id="security">
       <h2>Security and privacy considerations</h2>
       <p>
-        The user agent should not enable any device for media capture, such as
+        The user agent SHOULD NOT enable any device for media capture, such as
         a microphone or camera, until a user interaction giving implicit
-        consent is completed. A user agent should also provide an indication
+        consent is completed. A user agent SHOULD also provide an indication
         when such an input device is enabled and make it possible to terminate
-        such capture. Similarly, the user agent should allow the user:
+        such capture. Similarly, the user agent SHOULD allow the user:
         <ul>
           <li>
             to select the exact media capture device to be used if there exists
@@ -135,7 +135,7 @@
         controlled by the user agent.
       </p>
       <p>
-        Implementors should take care of additional leakage of privacy-sensitive
+        Implementors SHOULD take care of additional leakage of privacy-sensitive
         data from captured media. For instance, embedding the user’s location in
         a captured media metadata (e.g. EXIF) might transmit more private data
         than the user might be expecting.
Received on Monday, 10 December 2012 10:40:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:33 UTC