- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 21 Jul 2010 07:31:11 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/features
In directory hutz:/tmp/cvs-serv1737
Modified Files:
Overview.html
Log Message:
clarified intro and definitions
fleshed out somewhat geolocation as an example
made URI syntax optional
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/features/Overview.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- Overview.html 15 Jul 2010 14:53:50 -0000 1.4
+++ Overview.html 21 Jul 2010 07:31:09 -0000 1.5
@@ -22,94 +22,89 @@
</head>
<body>
<section id='abstract'>
- This document defined Device API features and their use.
+ This document defines identifiers for Web Device APIs and their intended impact for security gating.
</section> <!-- abstract -->
<section id='introduction'>
<h2>Introduction</h2>
-<p>A <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]] and a similar concept is
- used in the security policy framework [[!DAP-ACCESS-REQS]],
- [[!DAP-POLICY-FRAMEWORK]].
-</p>
-<p>
-Note - the feature APIs listed in this draft are roughly derived from
+<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>A similar approach is used in the proposed DAP security policy framework [[DAP-ACCESS-REQS]] [[DAP-POLICY-FRAMEWORK]].</p>
+<p>To define these specific security rules, the said APIs need to be identifiable, with a specific meaning attached to each of the identifiers — this is the role of this specification.</p>
+<p class="note">The feature APIs listed in this draft are roughly derived from
the BONDI 1.1 drafts, but require discussion and are subject to change
to correspond to DAP API work.
</p>
</section> <!-- introduction -->
<section id="features">
<h2>Features</h2>
- <p>
-A feature is a reference to a logical item that may require access
-control, identified by IRI. This document defines the context in which
-features are used and the specific features for a variety of APIs.
-</p>
+ <p>A <dfn>feature</dfn> is a reference to a logical item that may require access control.</p>
+ <p>This document lists features for well-known APIs, identifies them with a string that can be used to build a URI, and defines the meaning of the feature in terms of access control.</p>
<p>
Examples include the ability to read a local file, or to discover
nearby Bluetooth devices, or to send an SMS message. </p>
-</section>
+ <section id="identifiers">
+ <h2>Identifiers</h2>
+ <p>Each feature defined below is assigned with a string as an identifier.</p>
+ <p>That string can be used to build a URI identifying the said feature in context where a URI is needed (e.g. in the Widget Packaging and Configuration specification [[WIDGETS]]) by appending that string to the base URI <code>http://www.w3.org/ns/apis/</code> (<span class="note">to be confirmed</span>).</p>
+ </section>
<section id="api-features">
<h2>API Features</h2>
- <p>
+
+ <section id="geolocation">
+ <p>The <code>geolocation</code> identifier corresponds to the access to 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</code> methods defined in the Geolocation API [[!GEOLOCATION-API]].</p>
+ </selection>
<section id="contact-feature">
<h3>Contact API</h3>
<p>
-<code>http://dev.w3.org/2009/dap/features/contacts.read</code><br />
-<code>http://dev.w3.org/2009/dap/features/contacts.write</code>
+<code>contacts.read</code><br />
+<code>contacts.write</code>
</p>
</section>
<section id="calendar-feature">
<h3>Calendar API</h3>
<p>
-<code>http://dev.w3.org/2009/dap/features/calendar.read</code><br />
-<code>http://dev.w3.org/2009/dap/features/calendar.write</code>
+<code>calendar.read</code><br />
+<code>calendar.write</code>
</p>
</section>
<section id="capture-feature">
<h3>Capture API</h3>
<p>
-<code>http://dev.w3.org/2009/dap/features/capture.access</code><br />
-<code>http://dev.w3.org/2009/dap/features/capture.capture</code><br />
-<code>http://dev.w3.org/2009/dap/features/capture.record</code>
+<code>capture.access</code><br />
+<code>capture.capture</code><br />
+<code>capture.record</code>
</p>
</section>
<section id="messaging-feature">
<h3>Messaging API</h3>
<p>
-<code>http://dev.w3.org/2009/dap/features/messaging.email.send</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.mms.send</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.sms.send</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.binarysms.send</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.email.subscribe</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.mms.subscribe</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.sms.subscribe</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.binarysms.subscribe</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.email.getAccounts</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.email.attach</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.mms.attach</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.sms.get</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.mms.get</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.email.get</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.sms.delete</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.mms.delete</code><br />
-<code>http://dev.w3.org/2009/dap/features/messaging.email.delete</code>
+<code>messaging.email.send</code><br />
+<code>messaging.mms.send</code><br />
+<code>messaging.sms.send</code><br />
+<code>messaging.email.subscribe</code><br />
+<code>messaging.mms.subscribe</code><br />
+<code>messaging.sms.subscribe</code><br />
+<code>messaging.email.attach</code><br />
+<code>messaging.mms.attach</code><br />
+<code>messaging.sms.get</code><br />
+<code>messaging.mms.get</code><br />
+<code>messaging.email.get</code><br />
</p>
</section>
<section id="sysinfo-feature">
<h3>System Information API</h3>
<p>
-<code>http://dev.w3.org/2009/dap/features/devicestatus</code>
- </p>
- </section>
- <section id="gallery-feature">
- <h3>Gallery API</h3>
- <p>
-<code>http://dev.w3.org/2009/dap/features/gallery</code>
+<code>devicestatus</code><br />
+<code>networkstatus</code><br />
+<code>sensors</code><br />
</p>
</section>
+ <section>
+ <h3>Notification API</h3>
+ <code>notification</code>
</section>
-
<section class='conformance'>
<h2>Conformance</h2>
<p>
Received on Wednesday, 21 July 2010 07:31:13 UTC