- From: CVS User fhirsch3 <cvsmail@w3.org>
- Date: Thu, 18 Jun 2015 16:25:19 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/api-perms
In directory roscoe:/var/tmp/cvs-serv11653
Modified Files:
Overview.html
Log Message:
leave editors draft alone
--- /sources/public/2009/dap/api-perms/Overview.html 2015/06/18 16:20:25 1.7
+++ /sources/public/2009/dap/api-perms/Overview.html 2015/06/18 16:25:19 1.8
@@ -49,14 +49,108 @@
for consensus to shelve</a>) on the original Permissions API.
</p>
- <p>Further development of this specification is being performed
- by the <a href="http://www.w3.org/2011/webappsec/">Web
- Application Security Working Group</a> which has
- <a href="http://www.w3.org/TR/permissions/">published an
- updated version of the Permissions API</a>. Please refer to
- that version.
- </p>
+ <section id='introduction'>
+ <h2>Introduction</h2>
+ <p>A number of Web APIs, in particular those used to access private or
+ sensitive data from the hosting device, are meant to be discoverable,
+ as well as disabled or enabled on a site-by-site or
+ application-by-application basis, depending on the security
+ context.</p>
+ <p>For instance, the <a
+ href="http://www.w3.org/TR/2009/CR-widgets-20091201/#the-feature-element">feature
+ element</a> as defined in the Widget Packaging and
+ Configuration specification [[WIDGETS]] allows a widget runtime
+ engine to grant access only to the specific APIs that the
+ configuration file of the widget listed.</p>
+ <p>This document identifies and names the various permissions that are attached to existing Web APIs.</p>
+
+ </section> <!-- introduction -->
+ <section id="permissions">
+ <h2>Permissions</h2>
+ <p>Each permission described in this document is identified using a string specified in this document. </p>
+ <p>Where these permissions needed to be identified as a URI (e.g. in a widget configuration file [[WIDGETS]]), a URI can be built from these strings by
+ appending that string to the base
+ <code>http://www.w3.org/ns/api-perms/</code>.</p>
+ <p class="note">The DAP base URI is entirely tentative at this stage.</p>
+
+ <section id="geolocation">
+ <h3>Geolocation API</h3>
+
+ <p>The <code>geolocation</code> identifier corresponds to the
+ access to both or either of the <code><a
+ href="http://www.w3.org/TR/geolocation-API/#get-current-position">Geolocation::getCurrentPosition</a></code>
+ and <code><a
+ href="http://www.w3.org/TR/geolocation-API/#watch-position">Geolocation::watchPosition</a></code>
+ methods defined in the Geolocation API [[!GEOLOCATION-API]].</p>
+
+ <p>In the Web browser environment, this permission is usually granted through explicit user’s consent, and is retained for later access in the same session.</p>
+
+ </section>
+ <section id="contact">
+ <h3>Contact API</h3>
+ <p>The <code>contacts.read</code> identifier corresponds to the access to the <code><a href="http://www.w3.org/TR/contacts-api/#widl-Contacts-find">Contacts::find</a></code> method defined in the Contacts API [[!CONTACTS-API]].</p>
+ <p>In the Web browser environment, this permission is usually granted implicitly by asking the user to select what data of which contacts should be shared, for each call to the said method.</p>
+
+ </section>
+ <section id="capture">
+ <h3>Capture API</h3>
+ <p>The <code>mediacapture</code> identifier corresponds to the access to the <code><a href="http://dev.w3.org/2009/dap/camera/Overview-API.html#widl-Capture-captureImage">Capture::captureImage</a></code>, <code><a href="http://dev.w3.org/2009/dap/camera/Overview-API.html#widl-Capture-captureVideo">Capture::captureVideo</a></code> and <code><a href="http://dev.w3.org/2009/dap/camera/Overview-API.html#widl-Capture-captureAudio">Capture::captureAudio</a></code> methods defined in Media Capture API [[!MEDIACAPTURE-API]]. </p>
+ <p>In the Web browser environment, this permission is usually granted implicitly by asking the user to activate a button to start and stop the recording operations, for each call to the said methods.</p>
+
+ </section>
+ <section id="capture">
+ <h3>File API</h3>
+ <p>The <code>file.read</code> identifier corresponds to
+ the access to the <code><a
+ href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-readAsArrayBuffer">FileReader::readAsArrayBuffer</a></code>,
+ <code><a
+ href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-readAsArrayBuffer">FileReader::readAsBinaryString</a></code>,
+ <code><a
+ href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-readAsText">FileReader::readAsText</a></code> and <code><a href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-readAsArrayBuffer">FileReader::readAsDataURL</a></code> methods defined in the File API [[!FILE-API]]. </p>
+ <p>In the Web browser environment, this permission is usually granted implicitly once the <code>File</code> object has been created, after the user has selected a file from a file picker, and is retained for later access in the same browsing context.</p>
+
+ <p>The <code>file.write</code> identifier corresponds to
+ the access to
+ the <code><a href="http://dev.w3.org/2009/dap/file-system/file-writer.html#widl-FileWriter-write">FileWriter::write</a></code>, <code><a href="http://dev.w3.org/2009/dap/file-system/file-writer.html#widl-FileWriter-truncate">FileWriter::truncate</a></code>, <code><a href="http://dev.w3.org/2009/dap/file-system/file-writer.html#widl-FileWriterSync-write">FileWriterSync::write</a></code>
+ and <code><a href="http://dev.w3.org/2009/dap/file-system/file-writer.html#widl-FileWriterSync-truncate">FileWriterSync::truncate</a></code>
+ methods defined in the File Writer API [[!FILE-WRITER]]. </p>
+
+ <p>In the Web browser environment, this permission is usually granted implicitly once the <code>FileSaver</code> object has been created, after the user has selected a path to which the data can be saved (e.g. through a “Save As” dialog).</p>
- </section> <!-- sotd -->
+ </section>
+
+
+ <!--
+ <section id="messaging">
+ <h3>Messaging API</h3>
+ <p>The <code>messaging.sms.send</code> identifier corresponds to the access to the <code><a href="http://dev.w3.org/2009/dap/messaging/#widl-SMSMessage-send">SMSMessage::send</a></code> method defined in [[!MESSAGING-API]].</p>
+ <p>The <code>messaging.mms.send</code> identifier corresponds to the access to the <code><a href="http://dev.w3.org/2009/dap/messaging/#widl-MMSMessage-send">MMSMessage::send</a></code> and <code><a href="http://dev.w3.org/2009/dap/messaging/#widl-SMSMessage-send">SMSMessage::send</a></code> methods defined in [[!MESSAGING-API]].</p>
+ <p>The <code>messaging.email.send</code> identifier corresponds to the access to the <code><a href="http://dev.w3.org/2009/dap/messaging/#widl-EmailMessage-send">EmailMessage::send</a></code> method defined in [[!MESSAGING-API]].</p>
+ Commenting out — the model for granting permissions in that spec is not very clear yet.
+ </section>
+
+ -->
+ <section id="sysinfo">
+ <h3>System Information API</h3>
+ <p>The <code>deviceinfo</code> identifier corresponds to the access to the data of the <code>Power</code>, <code>CPU</code>, <code>Thermal</code>, <code>AVCodecs</code>, <code>Storage</code>, <code>OutputDevices</code>, <code>InputDevices</code> properties available through the <code><a href="http://www.w3.org/TR/system-info-api/#widl-SystemInfo-get">SystemInfo::get</a></code> and <code><a href="http://www.w3.org/TR/system-info-api/#widl-SystemInfo-watch">SystemInfo::watch</a></code> methods defined in the System Information API [[!SYSINFOAPI]].</p>
+
+ <p>The <code>networkinfo</code> identifier corresponds to the access to the data of the <code>Network</code> property available through the <code><a href="http://www.w3.org/TR/system-info-api/#widl-SystemInfo-get">SystemInfo::get</a></code> and <code><a href="http://www.w3.org/TR/system-info-api/#widl-SystemInfo-watch">SystemInfo::watch</a></code> methods defined in the System Information API [[!SYSINFOAPI]].</p>
+
+ <p>The <code>sensorinfo</code> identifier corresponds to the access to the data of the <code>AmbientLight</code>, <code>AmbientNoise</code>, <code>AmbientTemperature</code>, <code>AmbientAtmosphericPressure</code> and <code>Proximity</code> properties available through the <code><a href="http://www.w3.org/TR/system-info-api/#widl-SystemInfo-get">SystemInfo::get</a></code> and <code><a href="http://www.w3.org/TR/system-info-api/#widl-SystemInfo-watch">SystemInfo::watch</a></code> methods defined in the System Information API [[!SYSINFOAPI]].</p>
+
+ <p>In the Web browser environment, these permissions are usually granted through explicit user’s consent, and are retained for later access in the same session.</p>
+ </section>
+ </section>
+
+
+ <section class="appendix">
+ <h2>Mapping to BONDI features and Android permissions</h2>
+ <p>This section maps the permissions defined in this document to BONDI 1.11 feature strings
+ [[BONDI-FEATURES1-11]] and corresponding
+ <a href="http://developer.android.com/reference/android/Manifest.permission.html">
+ Android permissions</a>.</p>
+ <p>BONDI 1.11 feature URIs are formed by appending the BONDI
+ string to the base URI: <code>http://bondi.omtp.org/api/1.1/</code>.
+ </p>
</body>
</html>
Received on Thursday, 18 June 2015 16:25:26 UTC