- From: CVS User akostiai <cvsmail@w3.org>
- Date: Thu, 06 Jun 2013 07:04:14 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/vibration
In directory roscoe:/tmp/cvs-serv25540
Modified Files:
Overview.html Overview.src.html
Log Message:
clarify introduction
--- /sources/public/2009/dap/vibration/Overview.html 2013/05/29 15:28:46 1.40
+++ /sources/public/2009/dap/vibration/Overview.html 2013/06/06 07:04:14 1.41
@@ -430,7 +430,7 @@
</p>
<h1 class="title p-name" id="title">Vibration API</h1>
- <h2 id="w3c-editor-s-draft-29-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-05-29">29 May 2013</time></h2>
+ <h2 id="w3c-editor-s-draft-06-june-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-06-06">06 June 2013</time></h2>
<dl>
<dt>This version:</dt>
@@ -551,10 +551,11 @@
<p>
The API is specifically designed to address use cases that require
simple tactile feedback only. Use cases requiring more fine-grained
- control are out of scope for this specification. In addition, the API
- is not meant to be used as a generic notification mechanism. Use cases
- requiring notifying the user may be met by another specification,
- <cite>Web Notifications</cite> [<cite><a class="bibref" href="#bib-notifications">notifications</a></cite>].
+ control are out of scope for this specification. This API is not meant
+ to be used as a generic notification mechanism. Such use cases may be
+ handled using the <cite>Web Notifications</cite> [<cite><a class="bibref" href="#bib-notifications">notifications</a></cite>]
+ specification. In addition, determining whether vibration is enabled
+ is out of scope for this specification.
</p>
</section>
@@ -731,7 +732,7 @@
</section>
-<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-HTML5">[HTML5]</dt><dd>Robin Berjon et al. <a href="http://www.w3.org/TR/html5/"><cite>HTML5.</cite></a>. 17 December 2012. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a>
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-HTML5">[HTML5]</dt><dd>Robin Berjon et al. <a href="http://www.w3.org/TR/html5/"><cite>HTML5</cite></a>. 17 December 2012. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a>
</dd><dt id="bib-PAGE-VISIBILITY">[PAGE-VISIBILITY]</dt><dd>Jatinder Mann; Arvind Jain. <a href="http://www.w3.org/TR/page-visibility/"><cite>Page Visibility</cite></a>. 14 May 2013. W3C Recommendation. URL: <a href="http://www.w3.org/TR/page-visibility/">http://www.w3.org/TR/page-visibility/</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
</dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd>Cameron McCormack. <a href="http://www.w3.org/TR/WebIDL/"><cite>Web IDL</cite></a>. 19 April 2012. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/WebIDL/">http://www.w3.org/TR/WebIDL/</a>
--- /sources/public/2009/dap/vibration/Overview.src.html 2013/05/29 15:28:46 1.3
+++ /sources/public/2009/dap/vibration/Overview.src.html 2013/06/06 07:04:14 1.4
@@ -48,10 +48,11 @@
<p>
The API is specifically designed to address use cases that require
simple tactile feedback only. Use cases requiring more fine-grained
- control are out of scope for this specification. In addition, the API
- is not meant to be used as a generic notification mechanism. Use cases
- requiring notifying the user may be met by another specification,
- <cite>Web Notifications</cite> [[notifications]].
+ control are out of scope for this specification. This API is not meant
+ to be used as a generic notification mechanism. Such use cases may be
+ handled using the <cite>Web Notifications</cite> [[notifications]]
+ specification. In addition, determining whether vibration is enabled
+ is out of scope for this specification.
</p>
</section>
Received on Thursday, 6 June 2013 07:04:28 UTC