W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2011

hixie: try to clarify what is normative and what is not in the definition of the appcache stuff. (whatwg r5811)

From: poot <cvsmail@w3.org>
Date: Mon, 31 Jan 2011 19:38:10 -0500
To: public-html-diffs@w3.org
Message-Id: <E1Pk4G2-0008J2-9A@jay.w3.org>
hixie: try to clarify what is normative and what is not in the
definition of the appcache stuff. (whatwg r5811)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4669&r2=1.4670&f=h
http://html5.org/tools/web-apps-tracker?from=5810&to=5811

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4669
retrieving revision 1.4670
diff -u -d -r1.4669 -r1.4670
--- Overview.html	1 Feb 2011 00:13:38 -0000	1.4669
+++ Overview.html	1 Feb 2011 00:36:54 -0000	1.4670
@@ -45595,30 +45595,33 @@
 
     <dl><dt><dfn id="concept-appcache-master" title="concept-appcache-master">Master entries</dfn>
 
-     <dd>Documents that were added to the cache because a
-     <a href="#browsing-context">browsing context</a> was <a href="#navigate" title="navigate">navigated</a> to that document and the
-     document indicated that this was its cache, using the <code title="attr-html-manifest"><a href="#attr-html-manifest">manifest</a></code> attribute.
+     <dd><p class="note">These are documents that were added to the
+     cache because a <a href="#browsing-context">browsing context</a> was <a href="#navigate" title="navigate">navigated</a> to that document and the
+     document indicated that this was its cache, using the <code title="attr-html-manifest"><a href="#attr-html-manifest">manifest</a></code> attribute.</p>
 
 
      <dt><dfn id="concept-appcache-manifest" title="concept-appcache-manifest">The manifest</dfn>
 
-     <dd>The resource corresponding to the URL that was given in a
-     master entry's <code><a href="#the-html-element-0">html</a></code> element's <code title="attr-html-manifest"><a href="#attr-html-manifest">manifest</a></code> attribute. The
+     <dd><p class="note">This is the resource corresponding to the URL
+     that was given in a master entry's <code><a href="#the-html-element-0">html</a></code> element's
+     <code title="attr-html-manifest"><a href="#attr-html-manifest">manifest</a></code> attribute. The
      manifest is fetched and processed during the <a href="#application-cache-download-process">application
-     cache download process</a>. All the <a href="#concept-appcache-master" title="concept-appcache-master">master entries</a> have
-     the <a href="#same-origin" title="same origin">same origin</a> as the manifest.
+     cache download process</a>. All the <a href="#concept-appcache-master" title="concept-appcache-master">master entries</a> have the
+     <a href="#same-origin" title="same origin">same origin</a> as the manifest.</p>
 
 
      <dt><dfn id="concept-appcache-explicit" title="concept-appcache-explicit">Explicit entries</dfn>
 
-     <dd>Resources that were listed in the cache's <a href="#concept-appcache-manifest" title="concept-appcache-manifest">manifest</a> in an <a href="#concept-appcache-manifest-explicit" title="concept-appcache-manifest-explicit">explicit
-     section</a>.
+     <dd><p class="note">These are the resources that were listed in
+     the cache's <a href="#concept-appcache-manifest" title="concept-appcache-manifest">manifest</a> in an <a href="#concept-appcache-manifest-explicit" title="concept-appcache-manifest-explicit">explicit
+     section</a>.</p>
 
 
      <dt><dfn id="concept-appcache-fallback" title="concept-appcache-fallback">Fallback entries</dfn>
 
-     <dd>Resources that were listed in the cache's <a href="#concept-appcache-manifest" title="concept-appcache-manifest">manifest</a> in a <a href="#concept-appcache-manifest-fallback" title="concept-appcache-manifest-fallback">fallback
-     section</a>.
+     <dd><p class="note">These are the resources that were listed in
+     the cache's <a href="#concept-appcache-manifest" title="concept-appcache-manifest">manifest</a> in a <a href="#concept-appcache-manifest-fallback" title="concept-appcache-manifest-fallback">fallback
+     section</a>.</p>
 
 
     </dl><p><a href="#concept-appcache-explicit" title="concept-appcache-explicit">Explicit entries</a>
@@ -45635,23 +45638,42 @@
 
    </li>
 
-   <li>Zero or more <dfn id="concept-appcache-fallback-ns" title="concept-appcache-fallback-ns">fallback
-   namespaces</dfn>: URLs, used as <a href="#concept-appcache-matches-fallback" title="concept-appcache-matches-fallback">prefix match
-   patterns</a>, each of which is mapped to a <a href="#concept-appcache-fallback" title="concept-appcache-fallback">fallback entry</a>. Each
-   namespace URL has the <a href="#same-origin">same origin</a> as <a href="#concept-appcache-manifest" title="concept-appcache-manifest">the manifest</a>.</li>
+   <li>
 
-   <li>Zero or more URLs that form the <dfn id="concept-appcache-onlinewhitelist" title="concept-appcache-onlinewhitelist">online whitelist
-   namespaces</dfn>: URLs, used as prefix match patterns, that the
-   user agent will never load from the cache but will instead always
-   attempt to obtain from the network.</li>
+    <p>Zero or more <dfn id="concept-appcache-fallback-ns" title="concept-appcache-fallback-ns">fallback
+    namespaces</dfn>, each of which is mapped to a <a href="#concept-appcache-fallback" title="concept-appcache-fallback">fallback entry</a>.</p>
 
-   <li>An <dfn id="concept-appcache-onlinewhitelist-wildcard" title="concept-appcache-onlinewhitelist-wildcard">online whitelist
-   wildcard flag</dfn>, which is either <i title="">open</i>
-   (indicating that any URL not listed as cached is to be implicitly
-   treated as being in the <a href="#concept-appcache-onlinewhitelist" title="concept-appcache-onlinewhitelist">online whitelist
-   namespaces</a>) or <i title="">blocking</i> (indicating that
-   URLs not listed explicitly in the manifest are to be treated as
-   unavailable).</li>
+    <p class="note">These are URLs used as <a href="#concept-appcache-matches-fallback" title="concept-appcache-matches-fallback">prefix match
+    patterns</a> for resources that are to be fetched from the
+    network if possible, or to be replaced by the corresponding <a href="#concept-appcache-fallback" title="concept-appcache-fallback">fallback entry</a> if not.
+    Each namespace URL has the <a href="#same-origin">same origin</a> as <a href="#concept-appcache-manifest" title="concept-appcache-manifest">the manifest</a>.</p>
+
+   </li>
+
+   <li>
+
+    <p>Zero or more URLs that form the <dfn id="concept-appcache-onlinewhitelist" title="concept-appcache-onlinewhitelist">online whitelist
+    namespaces</dfn>.</p>
+
+    <p class="note">These are used as prefix match patterns, and
+    declare URLs that the user agent will never load from the cache
+    but will instead always attempt to obtain from the network.</p>
+
+   </li>
+
+   <li>
+
+    <p>An <dfn id="concept-appcache-onlinewhitelist-wildcard" title="concept-appcache-onlinewhitelist-wildcard">online whitelist
+    wildcard flag</dfn>, which is either <i title="">open</i> or <i title="">blocking</i>.</p>
+
+    <p class="note">The <i title="">open</i> state indicates that any
+    URL not listed as cached is to be implicitly treated as being in
+    the <a href="#concept-appcache-onlinewhitelist" title="concept-appcache-onlinewhitelist">online
+    whitelist namespaces</a>; the <i title="">blocking</i> state
+    indicates that URLs not listed explicitly in the manifest are to
+    be treated as unavailable.</p>
+
+   </li>
 
   </ul><p>Each <a href="#application-cache">application cache</a> has a <dfn id="concept-appcache-completeness" title="concept-appcache-completeness">completeness flag</dfn>, which is
   either <i>complete</i> or <i>incomplete</i>.</p>
Received on Tuesday, 1 February 2011 00:38:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 February 2011 00:38:12 GMT