Skip to content

Commit

Permalink
editorial: Capitalize first letter in notes (#462)
Browse files Browse the repository at this point in the history 
SHA: 0072c4d
Reason: push, by rakuco

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
@rakuco @github-actions
rakuco and github-actions[bot] committed Jul 7, 2023
1 parent c75d7e4 commit a1729b1
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
<link href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED" rel="stylesheet">
<meta content="Bikeshed version 5edf5e459, updated Thu Jun 22 11:28:01 2023 -0700" name="generator">
<link href="https://www.w3.org/TR/generic-sensor/" rel="canonical">
<meta content="75e66cf6e46cb7d92d93c545caa089fdea7a54e0" name="document-revision">
<meta content="0072c4d6cb65a468c42b2924782652b24eb1b092" name="document-revision">
<style>
svg g.edge text {
font-size: 8px;
Expand Down Expand Up @@ -911,7 +911,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/2021/logos/W3C" width="72"> </a> </p>
<h1 class="p-name no-ref" id="title">Generic Sensor API</h1>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2023-07-06">6 July 2023</time></p>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2023-07-07">7 July 2023</time></p>
<details open>
<summary>More details about this document</summary>
<div data-fill-with="spec-metadata">
Expand Down Expand Up @@ -1383,20 +1383,20 @@ <h4 class="heading settled dfn-paneled" data-dfn-type="dfn" data-level="4.3.4" d
discarded.</p>
<p>Implementations of concrete sensors may define a <a data-link-type="dfn" href="#reading-quantization-algorithm" id="ref-for-reading-quantization-algorithm">reading quantization
algorithm</a> to reduce the accuracy of the <a data-link-type="dfn" href="#sensor-reading" id="ref-for-sensor-reading①④">sensor readings</a> received from a <a data-link-type="dfn" href="#concept-device-sensor" id="ref-for-concept-device-sensor⑤">device sensor</a>.</p>
<p class="note" role="note"><span class="marker">Note:</span> these two mitigation measures often complement each other. An
<p class="note" role="note"><span class="marker">Note:</span> These two mitigation measures often complement each other. An
implementation that only executes the <a data-link-type="dfn" href="#threshold-check-algorithm" id="ref-for-threshold-check-algorithm①">threshold check algorithm</a> might
expose readings that are too precise, while an implementation that only rounds
readings up may provide attackers with information about more precise readings
when raw readings are rounded to different values.</p>
<p class="note" role="note"><span class="marker">Note:</span> Inaccuracies will further increase for operations carried out on the <a data-link-type="dfn" href="#sensor-reading" id="ref-for-sensor-reading①⑤">sensor readings</a>, or time deltas calculated from the <a data-link-type="dfn" href="#reading-timestamp" id="ref-for-reading-timestamp①">timestamps</a>.
So, this mitigation strategy can affect certain use cases.</p>
<p class="note" role="note"><span class="marker">Note:</span> while adding random bias to <a data-link-type="dfn" href="#sensor-reading" id="ref-for-sensor-reading①⑥">sensor readings</a> has similar effects,
<p class="note" role="note"><span class="marker">Note:</span> While adding random bias to <a data-link-type="dfn" href="#sensor-reading" id="ref-for-sensor-reading①⑥">sensor readings</a> has similar effects,
it shouldn’t be used in practice
as it is easy to filter out the added noise.</p>
<h4 class="heading settled" data-level="4.3.5" id="inform-user"><span class="secno">4.3.5. </span><span class="content">Keep the user informed about API use</span><a class="self-link" href="#inform-user"></a></h4>
<p>User agents may choose to keep the user informed
about current and past use of the API.</p>
<p class="note" role="note"><span class="marker">Note:</span> this does not imply keeping a log of the actual <a data-link-type="dfn" href="#sensor-reading" id="ref-for-sensor-reading①⑦">sensor readings</a> which would have issues of its own.</p>
<p class="note" role="note"><span class="marker">Note:</span> This does not imply keeping a log of the actual <a data-link-type="dfn" href="#sensor-reading" id="ref-for-sensor-reading①⑦">sensor readings</a> which would have issues of its own.</p>
<h2 class="heading settled" data-level="5" id="concepts"><span class="secno">5. </span><span class="content">Concepts</span><a class="self-link" href="#concepts"></a></h2>
<h3 class="heading settled" data-level="5.1" id="concepts-sensors"><span class="secno">5.1. </span><span class="content">Sensors</span><a class="self-link" href="#concepts-sensors"></a></h3>
<p>The term <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="concept-device-sensor">device sensor</dfn> refers to a device’s underlying
Expand Down Expand Up @@ -1431,7 +1431,7 @@ <h3 class="heading settled" data-level="5.1" id="concepts-sensors"><span class="
<p>Discrepancies between a <a data-link-type="dfn" href="#sensor-reading" id="ref-for-sensor-reading②③">sensor reading</a> and the corresponding physical quantity being measured
are corrected through <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="calibration">calibration</dfn> that can happen at manufacturing time.
Some sensors can require dynamic calibration to compensate unknown discrepancies.</p>
<p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#concept-platform-sensor" id="ref-for-concept-platform-sensor⑤">platform sensors</a> created through <a data-link-type="dfn" href="#sensor-fusion" id="ref-for-sensor-fusion②">sensor fusion</a> are sometimes
<p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#concept-platform-sensor" id="ref-for-concept-platform-sensor⑤">Platform sensors</a> created through <a data-link-type="dfn" href="#sensor-fusion" id="ref-for-sensor-fusion②">sensor fusion</a> are sometimes
called virtual or synthetic sensors. However, the specification doesn’t
make any practical distinction between them.</p>
<h3 class="heading settled" data-level="5.2" id="concepts-sensor-types"><span class="secno">5.2. </span><span class="content">Sensor Types</span><a class="self-link" href="#concepts-sensor-types"></a></h3>
Expand Down Expand Up @@ -1499,7 +1499,7 @@ <h3 class="heading settled" data-level="5.3" id="concepts-default-sensor"><span
sensor<c- p>.</c->start<c- p>();</c->
</pre>
</div>
<p class="note" role="note"><span class="marker">Note:</span> extension to this specification may choose not to define a <a data-link-type="dfn" href="#default-sensor" id="ref-for-default-sensor②">default sensor</a> when doing so wouldn’t make sense.
<p class="note" role="note"><span class="marker">Note:</span> Extensions to this specification may choose not to define a <a data-link-type="dfn" href="#default-sensor" id="ref-for-default-sensor②">default sensor</a> when doing so wouldn’t make sense.
For example, it does not make sense to explicitly define a default <a data-link-type="dfn" href="#concept-device-sensor" id="ref-for-concept-device-sensor②②">sensor</a> for geolocation <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type①⑦">sensor type</a> as the
implementation of its interface can use multiple backends.</p>
<p>In cases where
Expand Down Expand Up @@ -1565,7 +1565,7 @@ <h3 class="heading settled" data-level="6.1" id="model-sensor-type"><span class=
<p>A <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type②①">sensor type</a> has a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set">set</a> of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="associated-sensors">associated sensors</dfn>.</p>
<p>A <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type②②">sensor type</a> may have a <a data-link-type="dfn" href="#default-sensor" id="ref-for-default-sensor③">default sensor</a>.</p>
<p>A <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type②③">sensor type</a> has a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#list-is-empty" id="ref-for-list-is-empty">nonempty</a> <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#ordered-set" id="ref-for-ordered-set①">set</a> of associated <a data-link-type="dfn" href="https://w3c.github.io/permissions/#dfn-name" id="ref-for-dfn-name">names</a> referred to as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="sensor-permission-names">sensor permission names</dfn>.</p>
<p class="note" role="note"><span class="marker">Note:</span> multiple <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type②④">sensor types</a> may share the same <a data-link-type="dfn" href="https://w3c.github.io/permissions/#dfn-name" id="ref-for-dfn-name①">name</a>.</p>
<p class="note" role="note"><span class="marker">Note:</span> Multiple <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type②④">sensor types</a> may share the same <a data-link-type="dfn" href="https://w3c.github.io/permissions/#dfn-name" id="ref-for-dfn-name①">name</a>.</p>
<p>A <a data-link-type="dfn" href="#sensor-type" id="ref-for-sensor-type②⑤">sensor type</a> has a <a data-link-type="dfn" href="#generic-sensor-permission-revocation-algorithm" id="ref-for-generic-sensor-permission-revocation-algorithm">permission revocation algorithm</a>.</p>
<div class="algorithm" data-algorithm="generic sensor permission revocation algorithm">
<p>To invoke the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-local-lt="permission revocation algorithm" data-lt="generic sensor permission revocation algorithm" id="generic-sensor-permission-revocation-algorithm"> generic sensor permission revocation algorithm</dfn> with <a data-link-type="dfn" href="https://w3c.github.io/permissions/#dfn-name" id="ref-for-dfn-name②">name</a> <var>permission_name</var>, run the following steps:</p>
Expand Down Expand Up @@ -1766,7 +1766,7 @@ <h4 class="heading settled" data-level="7.1.1" id="sensor-lifecycle"><span class
</g>
</g>
</svg>
<p class="note" role="note"><span class="marker">Note:</span> the nodes in the diagram above represent the states of a <code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor①⓪">Sensor</a></code> object and they should not be
<p class="note" role="note"><span class="marker">Note:</span> The nodes in the diagram above represent the states of a <code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor①⓪">Sensor</a></code> object and they should not be
confused with the possible states of the underlying <a data-link-type="dfn" href="#concept-platform-sensor" id="ref-for-concept-platform-sensor②②">platform sensor</a> or <a data-link-type="dfn" href="#concept-device-sensor" id="ref-for-concept-device-sensor②⑦">device sensor</a>.</p>
<h4 class="heading settled" data-level="7.1.2" id="sensor-garbage-collection"><span class="secno">7.1.2. </span><span class="content">Sensor garbage collection</span><a class="self-link" href="#sensor-garbage-collection"></a></h4>
<p>A <code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor①①">Sensor</a></code> object whose <code class="idl"><a data-link-type="idl" href="#dom-sensor-state-slot" id="ref-for-dom-sensor-state-slot">[[state]]</a></code> is "activating" must not be garbage collected
Expand Down Expand Up @@ -1970,7 +1970,7 @@ <h3 class="heading settled dfn-paneled" data-dfn-type="dfn" data-export data-lev
<li data-md>
<p>Set <var>sensor_instance</var>.<code class="idl"><a data-link-type="idl" href="#dom-sensor-frequency-slot" id="ref-for-dom-sensor-frequency-slot②">[[frequency]]</a></code> to <var>options</var>["<code class="idl"><a class="idl-code" data-link-type="dict-member" href="#dom-sensoroptions-frequency" id="ref-for-dom-sensoroptions-frequency②">frequency</a></code>"].</p>
</ol>
<p class="note" role="note"><span class="marker">Note:</span> there is not guarantee that the requested <var>options</var>["<code class="idl"><a class="idl-code" data-link-type="dict-member" href="#dom-sensoroptions-frequency" id="ref-for-dom-sensoroptions-frequency③">frequency</a></code>"]
<p class="note" role="note"><span class="marker">Note:</span> There is no guarantee that the requested <var>options</var>["<code class="idl"><a class="idl-code" data-link-type="dict-member" href="#dom-sensoroptions-frequency" id="ref-for-dom-sensoroptions-frequency③">frequency</a></code>"]
can be respected. The actual <a data-link-type="dfn" href="#sampling-frequency" id="ref-for-sampling-frequency⑨">sampling frequency</a> can be calculated using <code class="idl"><a data-link-type="idl" href="#sensor" id="ref-for-sensor②⓪">Sensor</a></code> <code class="idl"><a class="idl-code" data-link-type="attribute" href="#dom-sensor-timestamp" id="ref-for-dom-sensor-timestamp①">timestamp</a></code> attributes.</p>
</ol>
</div>
Expand Down

0 comments on commit a1729b1

Please sign in to comment.