- From: Eric Uhrhane via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 17 Apr 2012 00:03:13 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/file-system/pub/FileWriter
In directory hutz:/tmp/cvs-serv28174/pub/FileWriter
Modified Files:
Overview.html
Log Message:
Update references to the latest editors' drafts for various refs.
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/file-system/pub/FileWriter/Overview.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- Overview.html 16 Apr 2012 20:56:59 -0000 1.14
+++ Overview.html 17 Apr 2012 00:03:11 -0000 1.15
@@ -17,7 +17,7 @@
This <acronym title="Application Programming
Interface">API</acronym> is designed to be used in conjunction with, and depends on
definitions in, other APIs and elements on the web platform. Most
- relevant among these are [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API">FILE-API</a></cite>] and [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBWORKERS">WEBWORKERS</a></cite>].
+ relevant among these are [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API-ED">FILE-API-ED</a></cite>] and [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBWORKERS-ED">WEBWORKERS-ED</a></cite>].
</p>
<p>
This <acronym title="Application Programming
@@ -132,7 +132,7 @@
<code>e.cancelable</code> <em class="rfc2119" title="must">must</em> be false [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>].</li>
<li>The term "fire an event" is defined in DOM4 [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>].
Progress events are defined in Progress Events
- [<cite><a class="bibref" rel="biblioentry" href="#bib-PROGRESS-EVENTS">PROGRESS-EVENTS</a></cite>].</li>
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-PROGRESS-EVENTS-ED">PROGRESS-EVENTS-ED</a></cite>].</li>
</ul>
<p></p>
The term <dfn id="dfn-throw">throw</dfn> in this specification, as it pertains to
@@ -142,7 +142,7 @@
<p>
The term <dfn id="dfn-blob">Blob</dfn> is defined by the File <acronym title="Application Programming
Interface">API</acronym> specification
- [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API">FILE-API</a></cite>].
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API-ED">FILE-API-ED</a></cite>].
</p>
<p>
The term <dfn id="dfn-arraybuffer">ArrayBuffer</dfn> is defined by the Typed Arrays
@@ -168,8 +168,8 @@
generated or downloaded files.
</p>
<p>
- The [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API">FILE-API</a></cite>] defined interfaces for reading files, manipulation of
- <a>Blobs</a> of data, and errors raised by file accesses. This
+ The [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API-ED">FILE-API-ED</a></cite>] defined interfaces for reading files, manipulation
+ of <a>Blobs</a> of data, and errors raised by file accesses. This
specification extends that work with a way to construct <a>Blobs</a> and
with synchronous and asynchronous file-writing interfaces. As with
reading, writing files on the main thread should happen asynchronously
@@ -310,13 +310,13 @@
<!--OddPage--><h2><span class="secno">5. </span>The <a href="#idl-def-FileSaver" class="idlType"><code>FileSaver</code></a> interface</h2>
<p>
This interface provides methods to monitor the asynchronous writing of
- blobs to disk using progress events [<cite><a class="bibref" rel="biblioentry" href="#bib-PROGRESS-EVENTS">PROGRESS-EVENTS</a></cite>] and <a href="#dfn-event-handler-attributes" class="internalDFN">event
+ blobs to disk using progress events [<cite><a class="bibref" rel="biblioentry" href="#bib-PROGRESS-EVENTS-ED">PROGRESS-EVENTS-ED</a></cite>] and <a href="#dfn-event-handler-attributes" class="internalDFN">event
handler attributes</a>.
</p>
<p>
This interface is specified to be used within the context of the global
object (Window [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]) and within Web Workers (WorkerUtils
- [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBWORKERS">WEBWORKERS</a></cite>]).
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBWORKERS-ED">WEBWORKERS-ED</a></cite>]).
</p>
<pre class="idl"><span class="idlInterface" id="idl-def-FileSaver">[<span class="extAttr">Constructor(Blob data)</span>]
interface <span class="idlInterfaceID">FileSaver</span> : <span class="idlSuperclass"><a>EventTarget</a></span> {
@@ -748,7 +748,7 @@
</p>
<p>
This interface is specified to be used only within Web Workers
- (WorkerUtils [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBWORKERS">WEBWORKERS</a></cite>]).
+ (WorkerUtils [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBWORKERS-ED">WEBWORKERS-ED</a></cite>]).
</p>
<div class="issue">
Since this is intended to be used only with the sandboxed filesystem,
@@ -871,8 +871,8 @@
See <a href="#dfn-syntaxerror" class="internalDFN">SyntaxError</a>.
</p>
<p>
- As documented in [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API">FILE-API</a></cite>], various errors may occur during reading
- from the Blob that is the source of the data to be written.
+ As documented in [<cite><a class="bibref" rel="biblioentry" href="#bib-FILE-API-ED">FILE-API-ED</a></cite>], various errors may occur during
+ reading from the Blob that is the source of the data to be written.
These include <a href="#dfn-notfounderror" class="internalDFN">NotFoundError</a>, <a href="#dfn-securityerror" class="internalDFN">SecurityError</a>, and
<a href="#dfn-notreadableerror" class="internalDFN">NotReadableError</a>.
</p></div>
@@ -1027,10 +1027,10 @@
<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">B. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-DOM4">[DOM4]</dt><dd>Anne van Kesteren; Aryeh Gregor; Ms2ger. <a href="http://www.w3.org/TR/2012/WD-dom-20120105/"><cite>DOM4.</cite></a> 5 January 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-dom-20120105/">http://www.w3.org/TR/2012/WD-dom-20120105/</a>
-</dd><dt id="bib-FILE-API">[FILE-API]</dt><dd>Arun Ranganathan; Jonas Sicking. <a href="http://www.w3.org/TR/2011/WD-FileAPI-20111020/"><cite>File API.</cite></a> 20 October 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/WD-FileAPI-20111020/">http://www.w3.org/TR/2011/WD-FileAPI-20111020/</a>
-</dd><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/html5"><cite>HTML5.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/html5">http://www.w3.org/TR/html5</a>
-</dd><dt id="bib-PROGRESS-EVENTS">[PROGRESS-EVENTS]</dt><dd>Charles McCathieNevile. <a href="http://www.w3.org/TR/2011/CR-progress-events-20110922/"><cite>Progress Events 1.0.</cite></a> 22 September 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/CR-progress-events-20110922/">http://www.w3.org/TR/2011/CR-progress-events-20110922/</a>
+</dd><dt id="bib-FILE-API-ED">[FILE-API-ED]</dt><dd>Arun Ranganathan; Jonas Sicking. <a href="http://dev.w3.org/2006/webapi/FileAPI/"><cite>File API.</cite></a> W3C Editor's Draft. (Work in progress.) URL: <a href="http://dev.w3.org/2006/webapi/FileAPI/">http://dev.w3.org/2006/webapi/FileAPI/</a>
+</dd><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson. <a href="http://www.w3.org/TR/html5"><cite>HTML5.</cite></a> 29 March 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/html5">http://www.w3.org/TR/html5</a>
+</dd><dt id="bib-PROGRESS-EVENTS-ED">[PROGRESS-EVENTS-ED]</dt><dd>Anne van Kesteren. <a href="http://dvcs.w3.org/hg/progress/raw-file/tip/Overview.html"><cite>Progress Events 1.0.</cite></a> W3C Editor's Draft. (Work in progress.) URL: <a href="http://dvcs.w3.org/hg/progress/raw-file/tip/Overview.html">http://dvcs.w3.org/hg/progress/raw-file/tip/Overview.html</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-TYPED-ARRAYS">[TYPED-ARRAYS]</dt><dd>David Herman, Kenneth Russell. <a href="https://www.khronos.org/registry/typedarray/specs/latest/"><cite>Typed Arrays</cite></a> Khronos Working Draft. (Work in progress.) URL: <a href="https://www.khronos.org/registry/typedarray/specs/latest/">https://www.khronos.org/registry/typedarray/specs/latest/</a>
-</dd><dt id="bib-WEBWORKERS">[WEBWORKERS]</dt><dd>Ian Hickson. <a href="http://www.w3.org/TR/2011/WD-workers-20110901/"><cite>Web Workers.</cite></a> 1 September 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/WD-workers-20110901/">http://www.w3.org/TR/2011/WD-workers-20110901/</a>
+</dd><dt id="bib-WEBWORKERS-ED">[WEBWORKERS-ED]</dt><dd>Ian Hickson. <a href="http://dev.w3.org/html5/workers/"><cite>Web Workers.</cite></a> W3C Editor's Draft. (Work in progress.) URL: <a href="http://dev.w3.org/html5/workers/">http://dev.w3.org/html5/workers/</a>
</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
Received on Tuesday, 17 April 2012 00:03:17 UTC