- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 30 Jun 2008 00:44:48 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/pubnotes
In directory hutz:/tmp/cvs-serv5517
Modified Files:
Overview.html Overview.src.html
Log Message:
1.989 "Fetching resources" section added
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.274
retrieving revision 1.275
diff -u -d -r1.274 -r1.275
--- Overview.html 30 Jun 2008 00:21:53 -0000 1.274
+++ Overview.html 30 Jun 2008 00:44:46 -0000 1.275
@@ -100,6 +100,8 @@
</li>
<li id="urls_wd2-toc"><a href="#urls_wd2">Section 2.3, URLs</a>
</li>
+<li id="fetching_wd2-toc"><a href="#fetching_wd2">Section 2.6 [NEW], Fetching resources</a>
+</li>
</ul>
</li>
<li id="semantics_wd2-toc"><a href="#semantics_wd2">Section 4, The elements of HTML</a>
@@ -687,6 +689,33 @@
statements about resolving a URL to obtain an absolute
URL.</p>
</div>
+ <div id="fetching_wd2" class="section">
+ <h2>Section 2.6 [NEW], Fetching resources <a class="hash" href="#fetching_wd2">#</a> <a class="toc-bak" href="#fetching_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#fetching">Section 2.6 [NEW], Fetching resources</a>” in the
+ current “Editor’s Draft”
+ version of the specification.</p><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#fetching">Section 2.6 [NEW], Fetching resources</a>” in a
+ diff-marked version of the specification, showing
+ changes made between
+ 10 June 2008
+ and
+ current “Editor’s Draft”.</p></div>
+ <p>This section is newly added. It is a placeholder
+ with an editorial note that reads:</p>
+ <blockquote>
+ <p><q>replace all instances of the word ‘fetch’ or
+ ‘download’ with a reference to this section, and
+ put something here that talks about caching, that
+ redirects to the offline storage stuff when
+ appropriate, that defines that before fetching a
+ URL you have to resolve the URL, so that every
+ case of fetching doesn’t have to independently say
+ to resolve the URL, etc; “once fetched, a resource
+ might have to have its type determined”, pointing
+ to the next section but also explicitly saying
+ that it’s up to the part of the spec doing the
+ fetching to determine how the type is
+ established</q></p>
+ </blockquote>
+ </div>
</div>
<div id="semantics_wd2" class="section">
<h2>Section 4, The elements of HTML <a class="hash" href="#semantics_wd2">#</a> <a class="toc-bak" href="#semantics_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#semantics">Section 4, The elements of HTML</a>” in the
@@ -1129,6 +1158,10 @@
context.</em></q></p>
</blockquote>
</li>
+ <li>A number of other revisions were made to the
+ algorithm which specifies user-agent behavior when a
+ browsing context is navigated to a new
+ resource.</li>
</ul>
</div>
</div>
Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.261
retrieving revision 1.262
diff -u -d -r1.261 -r1.262
--- Overview.src.html 30 Jun 2008 00:21:54 -0000 1.261
+++ Overview.src.html 30 Jun 2008 00:44:46 -0000 1.262
@@ -237,6 +237,26 @@
statements about resolving a URL to obtain an absolute
URL.</p>
</section>
+ <section id=fetching_wd2>
+ <h2>Section 2.6 [NEW], Fetching resources</h2>
+ <p>This section is newly added. It is a placeholder
+ with an editorial note that reads:</p>
+ <blockquote>
+ <p><q>replace all instances of the word ‘fetch’ or
+ ‘download’ with a reference to this section, and
+ put something here that talks about caching, that
+ redirects to the offline storage stuff when
+ appropriate, that defines that before fetching a
+ URL you have to resolve the URL, so that every
+ case of fetching doesn’t have to independently say
+ to resolve the URL, etc; “once fetched, a resource
+ might have to have its type determined”, pointing
+ to the next section but also explicitly saying
+ that it’s up to the part of the spec doing the
+ fetching to determine how the type is
+ established</q></p>
+ </blockquote>
+ </section>
</section>
<section id=semantics_wd2>
<h2>Section 4, The elements of HTML</h2>
@@ -555,6 +575,10 @@
context.</em></q></p>
</blockquote>
</li>
+ <li>A number of other revisions were made to the
+ algorithm which specifies user-agent behavior when a
+ browsing context is navigated to a new
+ resource.</li>
</ul>
</section>
</section>
Received on Monday, 30 June 2008 00:45:22 UTC