- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Jul 2010 11:44:25 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/camera
In directory hutz:/tmp/cvs-serv20005
Modified Files:
Overview.html
Log Message:
typos
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/camera/Overview.html,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -d -r1.90 -r1.91
--- Overview.html 16 Jul 2010 11:24:29 -0000 1.90
+++ Overview.html 16 Jul 2010 11:44:23 -0000 1.91
@@ -46,8 +46,8 @@
<h2>Introduction</h2>
<p>The HTML Form Based Media Capturing specification defines a new
- interface for media files, a new paramer the accept attribute of the HTML input element in file upload state, and recommendations for
- providing optimised access to the microphone and camera of a
+ interface for media files, a new parameter for the accept attribute of the HTML input element in file upload state, and recommendations for
+ providing optimized access to the microphone and camera of a
hosting device.</p>
<p>Providing streaming access to these capabilities is outside of the scope of this specification.</p>
@@ -70,7 +70,7 @@
<section id="security">
<h2>Security and Privacy Considerations</h2>
- <p>This specification builds upon the security and privacy protections provided by the [[!HTML5]] <code><input type="file"></code> and the [[!FILE-API]] specifications; in particular, it is expected that any offer to start capturing content from the user’s device would require a specific user interaction on an HTML element that is entirely controled by the user agent.</p>
+ <p>This specification builds upon the security and privacy protections provided by the [[!HTML5]] <code><input type="file"></code> and the [[!FILE-API]] specifications; in particular, it is expected that any offer to start capturing content from the user’s device would require a specific user interaction on an HTML element that is entirely controlled by the user agent.</p>
<p>In addition to the requirements already highlighted in the [[!HTML5]] and [[!FILE-API]] specifications, 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.</p>
Received on Friday, 16 July 2010 11:44:27 UTC