Fixes for review comments

Author: Alexander Shalamov

index.bs

@@ -1568,26 +1568,24 @@ for each [=sensor types=]:
 
 <h3 id="permission-api">Extending the Permission API</h3>
 
-{{Sensor}} interface for concrete [=sensor=] must protect it's [=sensor reading|reading=]
-by associated {{PermissionName}} or more complex {{PermissionDescriptor}}.
-[=Low-level=] {{Sensor|sensor}} may use it's interface name as a {{PermissionName}}, for instance
-"gyroscope" or "accelerometer". [=sensor fusion|Fusion sensors=] must
-[=request permission to use|request permission to use=] sensors used as a source of fusion.
+An implementation of the {{Sensor}} interface for each [=sensor type=] must protect its
+[=sensor reading|reading=] by associated {{PermissionName}} or {{PermissionDescriptor}}.
+A [=Low-level=] {{Sensor|sensor}} may use its interface name as a {{PermissionName}},
+for instance, "gyroscope" or "accelerometer". [=sensor fusion|Fusion sensors=] must
+[=request permission to use|request permission to use=] sensors that are used as a source
+of fusion.
 
 Even though, it might be difficult to reconstruct [=low-level=] [=sensor readings=] from
 fused data, some of the original information might be inferred. For example, it is easy to
 deduce user's orientation in space if absolute or geomagnetic orientation sensors are used,
 therefore, those sensors must [=request permission to use|request permission to use=]
 "magnetometer" as it provides information about orientation of device in relation to Earth's
 magnetic field. In contrast, relative orientation sensor does not expose such information, thus,
-does not need to [=request permission to use|request permission to use=] "magnetometer".
+it does not need to [=request permission to use|request permission to use=] "magnetometer".
 
-In order to provide fine grained control over the sensor's data,
-{{PermissionDescriptor|permission descriptors}} may be used. For example, descriptor can contain
-settings for accuracy or [=sampling frequency=].
-
-Here is an example of {{PermissionDescriptor}} for a possible extension of the Permission API for
-accelerometer sensor.
+{{PermissionDescriptor|Permission descriptors}} can also be used to set maximum allowed limits
+for accuracy or [=sampling frequency=]. An example for a possible extension of the Permission API
+for accelerometer sensor is given below.
 
 <pre class=example>
     dictionary AccelerometerPermissionDescriptor : PermissionDescriptor {

index.html

@@ -1458,7 +1458,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">Generic Sensor API</h1>
-   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2017-09-07">7 September 2017</time></span></h2>
+   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2017-09-08">8 September 2017</time></span></h2>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version:
@@ -2972,26 +2972,27 @@ <h3 class="heading settled" data-level="10.6" id="definition-reqs"><span class="
      <p>A set of <a data-link-type="dfn" href="#identifying-parameters" id="ref-for-identifying-parameters②">identifying parameters</a>. TODO: replace that by an abstract operation.</p>
    </ul>
    <h3 class="heading settled" data-level="10.7" id="permission-api"><span class="secno">10.7. </span><span class="content">Extending the Permission API</span><a class="self-link" href="#permission-api"></a></h3>
-   <p><code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor③⓪">Sensor</a></code> interface for concrete <a data-link-type="dfn" href="#concept-sensor" id="ref-for-concept-sensor⑤①">sensor</a> must protect it’s <a data-link-type="dfn" href="#sensor-readings" id="ref-for-sensor-readings④⑥">reading</a> by associated <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#enumdef-permissionname" id="ref-for-enumdef-permissionname⑥">PermissionName</a></code> or more complex <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#dictdef-permissiondescriptor" id="ref-for-dictdef-permissiondescriptor①">PermissionDescriptor</a></code>. <a data-link-type="dfn" href="#low-level" id="ref-for-low-level①③">Low-level</a> <code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor③①">sensor</a></code> may use it’s interface name as a <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#enumdef-permissionname" id="ref-for-enumdef-permissionname⑦">PermissionName</a></code>, for instance
-"gyroscope" or "accelerometer". <a data-link-type="dfn" href="#sensor-fusion" id="ref-for-sensor-fusion⑦">Fusion sensors</a> must <a data-link-type="dfn" href="https://w3c.github.io/permissions/#request-permission-to-use" id="ref-for-request-permission-to-use①">request permission to use</a> sensors used as a source of fusion.</p>
+   <p>An implementation of the <code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor③⓪">Sensor</a></code> interface for each <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type③⑥">sensor type</a> must protect its <a data-link-type="dfn" href="#sensor-readings" id="ref-for-sensor-readings④⑥">reading</a> by associated <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#enumdef-permissionname" id="ref-for-enumdef-permissionname⑥">PermissionName</a></code> or <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#dictdef-permissiondescriptor" id="ref-for-dictdef-permissiondescriptor①">PermissionDescriptor</a></code>.
+A <a data-link-type="dfn" href="#low-level" id="ref-for-low-level①③">Low-level</a> <code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor③①">sensor</a></code> may use its interface name as a <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#enumdef-permissionname" id="ref-for-enumdef-permissionname⑦">PermissionName</a></code>,
+for instance, "gyroscope" or "accelerometer". <a data-link-type="dfn" href="#sensor-fusion" id="ref-for-sensor-fusion⑦">Fusion sensors</a> must <a data-link-type="dfn" href="https://w3c.github.io/permissions/#request-permission-to-use" id="ref-for-request-permission-to-use①">request permission to use</a> sensors that are used as a source
+of fusion.</p>
    <p>Even though, it might be difficult to reconstruct <a data-link-type="dfn" href="#low-level" id="ref-for-low-level①④">low-level</a> <a data-link-type="dfn" href="#sensor-readings" id="ref-for-sensor-readings④⑦">sensor readings</a> from
 fused data, some of the original information might be inferred. For example, it is easy to
 deduce user’s orientation in space if absolute or geomagnetic orientation sensors are used,
 therefore, those sensors must <a data-link-type="dfn" href="https://w3c.github.io/permissions/#request-permission-to-use" id="ref-for-request-permission-to-use②">request permission to use</a> "magnetometer" as it provides information about orientation of device in relation to Earth’s
 magnetic field. In contrast, relative orientation sensor does not expose such information, thus,
-does not need to <a data-link-type="dfn" href="https://w3c.github.io/permissions/#request-permission-to-use" id="ref-for-request-permission-to-use③">request permission to use</a> "magnetometer".</p>
-   <p>In order to provide fine grained control over the sensor’s data, <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#dictdef-permissiondescriptor" id="ref-for-dictdef-permissiondescriptor②">permission descriptors</a></code> may be used. For example, descriptor can contain
-settings for accuracy or <a data-link-type="dfn" href="#sampling-frequency" id="ref-for-sampling-frequency⑥">sampling frequency</a>.</p>
-   <p>Here is an example of <code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#dictdef-permissiondescriptor" id="ref-for-dictdef-permissiondescriptor③">PermissionDescriptor</a></code> for a possible extension of the Permission API for
-accelerometer sensor.</p>
+it does not need to <a data-link-type="dfn" href="https://w3c.github.io/permissions/#request-permission-to-use" id="ref-for-request-permission-to-use③">request permission to use</a> "magnetometer".</p>
+   <p><code class="idl"><a data-link-type="idl" href="https://w3c.github.io/permissions/#dictdef-permissiondescriptor" id="ref-for-dictdef-permissiondescriptor②">Permission descriptors</a></code> can also be used to set maximum allowed limits
+for accuracy or <a data-link-type="dfn" href="#sampling-frequency" id="ref-for-sampling-frequency⑥">sampling frequency</a>. An example for a possible extension of the Permission API
+for accelerometer sensor is given below.</p>
 <pre class="example" id="example-6d08453b"><a class="self-link" href="#example-6d08453b"></a>dictionary AccelerometerPermissionDescriptor : PermissionDescriptor {
     boolean highAccuracy = false;
     boolean highFrequency = false;
 };
 </pre>
    <h3 class="heading settled" data-level="10.8" id="example-webidl"><span class="secno">10.8. </span><span class="content">Example WebIDL</span><a class="self-link" href="#example-webidl"></a></h3>
    <p>Here’s example WebIDL for a possible extension of this specification
-for proximity <a data-link-type="dfn" href="#concept-sensor" id="ref-for-concept-sensor⑤②">sensors</a>.</p>
+for proximity <a data-link-type="dfn" href="#concept-sensor" id="ref-for-concept-sensor⑤①">sensors</a>.</p>
 <pre class="example" id="example-be4b13c4"><a class="self-link" href="#example-be4b13c4"></a>[Constructor(optional ProximitySensorOptions proximitySensorOptions),
  SecureContext, Exposed=Window]
 interface ProximitySensor : Sensor {
@@ -3105,8 +3106,8 @@ <h3 class="no-ref no-num heading settled" id="conventions"><span class="content"
     <a class="self-link" href="#example-f839f6c8"></a> 
     <p>This is an example of an informative example.</p>
    </div>
-   <p>Because this document doesn’t itself define APIs for specific <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type③⑥">sensor types</a>—<wbr>that is the role of extensions to this specification—<wbr>all examples are inevitably (wishful) fabrications.
-    Although all of the <a data-link-type="dfn" href="#concept-sensor" id="ref-for-concept-sensor⑤③">sensors</a> used a examples
+   <p>Because this document doesn’t itself define APIs for specific <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type③⑦">sensor types</a>—<wbr>that is the role of extensions to this specification—<wbr>all examples are inevitably (wishful) fabrications.
+    Although all of the <a data-link-type="dfn" href="#concept-sensor" id="ref-for-concept-sensor⑤②">sensors</a> used a examples
     would be great candidates for building atop the Generic Sensor API,
     their inclusion in this document does not imply that the relevant Working Groups
     are planning to do so. </p>
@@ -3662,6 +3663,7 @@ <h2 class="no-num no-ref heading settled" id="idl-index"><span class="content">I
     <li><a href="#ref-for-sensor-type②⑨">9.2. Connect to sensor</a>
     <li><a href="#ref-for-sensor-type③⓪">10. Extensibility</a> <a href="#ref-for-sensor-type③①">(2)</a>
     <li><a href="#ref-for-sensor-type③②">10.6. Definition Requirements</a> <a href="#ref-for-sensor-type③③">(2)</a> <a href="#ref-for-sensor-type③④">(3)</a> <a href="#ref-for-sensor-type③⑤">(4)</a>
+    <li><a href="#ref-for-sensor-type③⑥">10.7. Extending the Permission API</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="associated-sensors">
@@ -3710,8 +3712,7 @@ <h2 class="no-num no-ref heading settled" id="idl-index"><span class="content">I
     <li><a href="#ref-for-concept-sensor④⑤">9.15. Request sensor access</a>
     <li><a href="#ref-for-concept-sensor④⑥">10.2. Naming</a> <a href="#ref-for-concept-sensor④⑦">(2)</a> <a href="#ref-for-concept-sensor④⑧">(3)</a>
     <li><a href="#ref-for-concept-sensor④⑨">10.6. Definition Requirements</a> <a href="#ref-for-concept-sensor⑤⓪">(2)</a>
-    <li><a href="#ref-for-concept-sensor⑤①">10.7. Extending the Permission API</a>
-    <li><a href="#ref-for-concept-sensor⑤②">10.8. Example WebIDL</a>
+    <li><a href="#ref-for-concept-sensor⑤①">10.8. Example WebIDL</a>
    </ul>
   </aside>
   <aside class="dfn-panel" data-for="activated-sensor-objects">