W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2009

html5/spec Overview.html,1.2487,1.2488

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 01 Jul 2009 21:38:56 +0000
To: public-html-commits@w3.org
Message-Id: <E1MM7W4-0002FN-Cq@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv8623

Modified Files:
	Overview.html 
Log Message:
Mark impl-specific mirodata sections as such. Make some non-normative text more obviously non-normative. Make location.assign() act like .replace() when performed on the initial about:blank document. Fix markup error. (whatwg r3350)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2487
retrieving revision 1.2488
diff -u -d -r1.2487 -r1.2488
--- Overview.html	1 Jul 2009 04:36:24 -0000	1.2487
+++ Overview.html	1 Jul 2009 21:38:53 -0000	1.2488
@@ -39137,12 +39137,20 @@
   </div><h4 id="rdf"><span class="secno">5.4.4 </span>RDF</h4><p>The <dfn id="md-about" title="md-about"><code>about</code></dfn> property can
   be used to name an <a href="#concept-item" title="concept-item">item</a> for the
   purposes of refering to the data defined in that item from RDF.<p>A single property with the name <code title="md-about"><a href="#md-about">about</a></code> may be present within each <a href="#concept-item" title="concept-item">item</a>. Its <a href="#concept-property-value" title="concept-property-value">value</a> must be an
-  <a href="#absolute-url">absolute URL</a>.<h3 id="converting-html-to-other-formats"><span class="secno">5.5 </span>Converting HTML to other formats</h3><p>In all these algorithms, unless otherwise stated, operations that
+  <a href="#absolute-url">absolute URL</a>.<div class="impl">
+
+  <h3 id="converting-html-to-other-formats"><span class="secno">5.5 </span>Converting HTML to other formats</h3>
+
+  <p>In all these algorithms, unless otherwise stated, operations that
   iterate over a series of elements (whether items, properties, or
-  otherwise) must do so in <a href="#tree-order">tree order</a>.<p>A generic API upon which the vocaulary-specific conversions
+  otherwise) must do so in <a href="#tree-order">tree order</a>.</p>
+
+  <p>A generic API upon which the vocaulary-specific conversions
   defined below (vCard, iCalendar, BibTeX) can be built will need to
   provide the following information when given a <code>Document</code>
-  (or equivalent):<ul><li><a href="#the-document-s-current-address">The document's current address</a>.</li>
+  (or equivalent):</p>
+
+  <ul><li><a href="#the-document-s-current-address">The document's current address</a>.</li>
 
    <li>The <code>textContent</code> of <a href="#the-title-element-0">the <code>title</code>
    element</a>, if any.</li>
@@ -39169,10 +39177,14 @@
    that adds the property.</li>
 -->
 
-  </ul><h4 id="json"><span class="secno">5.5.1 </span>JSON</h4><p>Given a list of nodes <var title="">nodes</var> in a
+  </ul><h4 id="json"><span class="secno">5.5.1 </span>JSON</h4>
+
+  <p>Given a list of nodes <var title="">nodes</var> in a
   <code>Document</code>, a user agent must run the following algorithm
   to <dfn id="extracting-json" title="extracting JSON">extract the microdata from those
-  nodes into a JSON form</dfn>:<ol><li><p>Let <var title="">result</var> be an empty object.</li>
+  nodes into a JSON form</dfn>:</p>
+
+  <ol><li><p>Let <var title="">result</var> be an empty object.</li>
 
    <li><p>Let <var title="">items</var> be an empty array.</li>
 
@@ -39197,7 +39209,9 @@
    to JSON.</li>
 
   </ol><p>When the user agent is to <dfn id="get-the-object">get the object</dfn> for an item
-  <var title="">item</var>, it must run the following substeps:<ol><li><p>Let <var title="">result</var> be an empty object.</li>
+  <var title="">item</var>, it must run the following substeps:</p>
+
+  <ol><li><p>Let <var title="">result</var> be an empty object.</li>
 
    <li><p>Let <var title="">types</var> be an empty array.</li>
 
@@ -39240,8 +39254,12 @@
 
    <li><p>Return <var title="">result</var>.</li>
 
-  </ol><h4 id="rdf-0"><span class="secno">5.5.2 </span>RDF</h4><p>To convert a <code>Document</code> to RDF, a user agent must run
-  the following algorithm:<ol><li>
+  </ol><h4 id="rdf-0"><span class="secno">5.5.2 </span>RDF</h4>
+
+  <p>To convert a <code>Document</code> to RDF, a user agent must run
+  the following algorithm:</p>
+
+  <ol><li>
 
     <p>If <a href="#the-title-element-0">the <code>title</code> element</a> is not null,
     then generate the following triple:</p>
@@ -39365,7 +39383,9 @@
 
   </ol><p>When the user agent is to <dfn id="generate-the-triples-for-an-item">generate the triples for an
   item</dfn> <var title="">item</var>, it must follow the following
-  steps:<ol><li><p>If of the elements whose <a href="#concept-item-corresponding" title="concept-item-corresponding">corresponding item</a> is
+  steps:</p>
+
+  <ol><li><p>If of the elements whose <a href="#concept-item-corresponding" title="concept-item-corresponding">corresponding item</a> is
    <var title="">item</var>, there are any with a <a href="#property-names" title="property names">property name</a> equal to the string
    "<code title="md-about"><a href="#md-about">about</a></code>", and the first such element
    is a <a href="#url-property-elements" title="URL property elements">URL property
@@ -39444,10 +39464,14 @@
 
    <li><p>Return <var title="">subject</var>.</li>
 
-  </ol><h4 id="vcard-0"><span class="secno">5.5.3 </span>vCard</h4><p>Given a list of nodes <var title="">nodes</var> in a
+  </ol><h4 id="vcard-0"><span class="secno">5.5.3 </span>vCard</h4>
+
+  <p>Given a list of nodes <var title="">nodes</var> in a
   <code>Document</code>, a user agent must run the following algorithm
   to <dfn id="extracting-a-vcard" title="extracting a vCard">extract any <code title="md-vcard">vcard</code> data represented by those nodes</dfn>
-  (only the first vCard is returned):<ol><li><p>If none of the nodes in <var title="">nodes</var> are <a href="#concept-item" title="concept-item">items</a> with the type <code title="md-vcard"><a href="#md-vcard">vcard</a></code>, then there is no vCard. Abort the
+  (only the first vCard is returned):</p>
+
+  <ol><li><p>If none of the nodes in <var title="">nodes</var> are <a href="#concept-item" title="concept-item">items</a> with the type <code title="md-vcard"><a href="#md-vcard">vcard</a></code>, then there is no vCard. Abort the
    algorithm, returning nothing.</li>
 
    <li><p>Let <var title="">node</var> be the first node in <var title="">nodes</var> that is an <a href="#concept-item" title="concept-item">item</a> with the type <code title="md-vcard"><a href="#md-vcard">vcard</a></code>.</li>
@@ -39827,7 +39851,9 @@
   a vCard line</dfn> consisting of a type <var title="">type</var>,
   optionally some parameters, and a value <var title="">value</var> to
   a string <var title="">output</var>, it must run the following
-  steps:<ol><li><p>Let <var title="">line</var> be an empty string.
+  steps:</p>
+
+  <ol><li><p>Let <var title="">line</var> be an empty string.
 
    <li><p>Append <var title="">type</var>, <a href="#converted-to-ascii-uppercase">converted to
    ASCII uppercase</a>, to <var title="">line</var>.</li>
@@ -39882,7 +39908,9 @@
 
   </ol><p>When the steps above require the user agent to obtain the result
   of <dfn id="collecting-vcard-subproperties">collecting vCard subproperties</dfn> named <var title="">subname</var> in <var title="">subitem</var>, the user
-  agent must run the following steps:<ol><li><p>Let <var title="">value</var> be the empty string.</li>
+  agent must run the following steps:</p>
+
+  <ol><li><p>Let <var title="">value</var> be the empty string.</li>
 
    <li>
 
@@ -39907,7 +39935,9 @@
 
   </ol><p>When the steps above require the user agent to obtain the result
   of <dfn id="collecting-the-first-vcard-subproperty">collecting the first vCard subproperty</dfn> named <var title="">subname</var> in <var title="">subitem</var>, the user
-  agent must run the following steps:<ol><li><p>If there are no properties named <var title="">subname</var>
+  agent must run the following steps:</p>
+
+  <ol><li><p>If there are no properties named <var title="">subname</var>
    in <var title="">subitem</var>, then abort these substeps,
    returning the empty string.</li>
 
@@ -39921,7 +39951,9 @@
 
   </ol><p>When the above algorithms say the user agent is to <dfn id="escaping-the-vcard-text-string" title="escaping the vCard text string">escape the vCard text
   string</dfn> <var title="">value</var>, the user agent must use the
-  following steps:<ol><li><p>Prefix every U+005C REVERSE SOLIDUS character (\) in <var title="">value</var> with another U+005C REVERSE SOLIDUS character
+  following steps:</p>
+
+  <ol><li><p>Prefix every U+005C REVERSE SOLIDUS character (\) in <var title="">value</var> with another U+005C REVERSE SOLIDUS character
    (\).</li>
 
    <li><p>Prefix every U+002C COMMA character (,) in <var title="">value</var> with a U+005C REVERSE SOLIDUS character
@@ -39944,11 +39976,18 @@
 
   </ol><p class="note">This algorithm can generate invalid vCard output, if
   the input does not conform to the rules described for the <code title="md-vcard"><a href="#md-vcard">vcard</a></code> <a href="#predefined-type">predefined type</a> and <a href="#predefined-property-name" title="predefined property name">predefined property
-  names</a>.</p><!-- of course since vcard doesn't define error
-  handling, this is somewhat problematic. --><h4 id="icalendar"><span class="secno">5.5.4 </span>iCalendar</h4><p>Given a list of nodes <var title="">nodes</var> in a
+  names</a>.</p> <!-- of course since vcard doesn't define error
+  handling, this is somewhat problematic. -->
+
+
+  <h4 id="icalendar"><span class="secno">5.5.4 </span>iCalendar</h4>
+
+  <p>Given a list of nodes <var title="">nodes</var> in a
   <code>Document</code>, a user agent must run the following algorithm
   to <dfn id="extracting-vevent-data" title="extracting vEvent data">extract any <code title="md-vevent">vevent</code> data represented by those
-  nodes</dfn>:<ol><li><p>If none of the nodes in <var title="">nodes</var> are <a href="#concept-item" title="concept-item">items</a> with the type <code title="md-vevent"><a href="#md-vevent">vevent</a></code>, then there is no vEvent
+  nodes</dfn>:</p>
+
+  <ol><li><p>If none of the nodes in <var title="">nodes</var> are <a href="#concept-item" title="concept-item">items</a> with the type <code title="md-vevent"><a href="#md-vevent">vevent</a></code>, then there is no vEvent
    data. Abort the algorithm, returning nothing.</li>
 
    <li><p>Let <var title="">output</var> be an empty string.</li>
@@ -40046,7 +40085,9 @@
   </ol><p>When the above algorithm says that the user agent is to <dfn id="add-an-icalendar-line">add
   an iCalendar line</dfn> consisting of a type <var title="">type</var>, a value <var title="">value</var>, and
   optinally an annotation, to a string <var title="">output</var>, it
-  must run the following steps:<ol><li><p>Let <var title="">line</var> be an empty string.</li>
+  must run the following steps:</p>
+
+  <ol><li><p>Let <var title="">line</var> be an empty string.</li>
 
    <li><p>Append <var title="">type</var>, <a href="#converted-to-ascii-uppercase">converted to
    ASCII uppercase</a>, to <var title="">line</var>.</li>
@@ -40118,11 +40159,19 @@
   output, if the input does not conform to the rules described for the
   <code title="md-vevent"><a href="#md-vevent">vevent</a></code> <a href="#predefined-type">predefined type</a>
   and <a href="#predefined-property-name" title="predefined property name">predefined property
-  names</a>.</p><!-- of course since icalendar doesn't define
-  error handling, this is somewhat problematic. --><h4 id="bibtex-0"><span class="secno">5.5.5 </span>BibTeX</h4><p>Given a node <var title="">node</var> in a <code>Document</code>,
+  names</a>.</p> <!-- of course since icalendar doesn't define
+  error handling, this is somewhat problematic. -->
+
+
+
+  <h4 id="bibtex-0"><span class="secno">5.5.5 </span>BibTeX</h4>
+
+  <p>Given a node <var title="">node</var> in a <code>Document</code>,
   a user agent must run the following algorithm to <dfn id="extracting-bibtex" title="extracting BibTeX">extract any <code title="md-bibtex">bibtex</code> data represented by that node into a
   form that vaguely resembles the format used by BibTeX
-  processors</dfn>:<ol><li>
+  processors</dfn>:</p>
+
+  <ol><li>
 
     <p>If <var title="">node</var> is not an element that is an <a href="#concept-item" title="concept-item">item</a> with the type <code title="md-bibtex"><a href="#md-bibtex">bibtex</a></code>, then run these substeps:</p>
 
@@ -40206,7 +40255,9 @@
    <li><p>Append a U+007D RIGHT CURLY BRACKET character (}) to <var title="">output</var>.</li>
 
   </ol><p>When the user agent is to <dfn id="output-the-bibtex-name-value-pair">output the BibTeX name-value
-  pair</dfn> given by <var title="">name</var> and <var title="">value</var>, it must run the following steps:<ol><li><p>Append two U+0020 SPACE characters to <var title="">output</var>.</li>
+  pair</dfn> given by <var title="">name</var> and <var title="">value</var>, it must run the following steps:</p>
+
+  <ol><li><p>Append two U+0020 SPACE characters to <var title="">output</var>.</li>
 
    <li><p>Append <var title="">name</var> to <var title="">output</var>.</li>
 
@@ -40228,9 +40279,13 @@
    <li><p>Append a U+002C COMMA character (,) and a U+000A LINE FEED
    (LF) character to <var title="">output</var>.</li>
 
-  </ol><h4 id="atom"><span class="secno">5.5.6 </span>Atom</h4><p>Given a <code>Document</code> <var title="">source</var>, a user
+  </ol><h4 id="atom"><span class="secno">5.5.6 </span>Atom</h4>
+
+  <p>Given a <code>Document</code> <var title="">source</var>, a user
   agent must run the following algorithm to <dfn id="extracting-atom" title="extracting
-  Atom">extract an Atom feed</dfn>:<ol><li><p>If the <code>Document</code> <var title="">source</var> does
+  Atom">extract an Atom feed</dfn>:</p>
+
+  <ol><li><p>If the <code>Document</code> <var title="">source</var> does
    not contain any <code><a href="#the-article-element">article</a></code> elements, then return nothing
    and abort these steps. This algorithm can only be used with
    documents that contain distinct articles.</p>
@@ -40656,7 +40711,9 @@
 
    <li><p>Return the Atom document <var title="">R</var>.</li>
 
-  </ol><p>The <dfn id="atom-namespace">Atom namespace</dfn> is: <code>http://www.w3.org/2005/Atom</code><h2 id="browsers"><span class="secno">6 </span>Web browsers</h2><div class="impl">
+  </ol><p>The <dfn id="atom-namespace">Atom namespace</dfn> is: <code>http://www.w3.org/2005/Atom</code></p>
+
+  </div><h2 id="browsers"><span class="secno">6 </span>Web browsers</h2><div class="impl">
 
   <p>This section describes features that apply most directly to Web
   browsers. Having said that, unless specified elsewhere, the
@@ -40728,8 +40785,10 @@
   <code><a href="#about:blank">about:blank</a></code>, which is marked as being an <a href="#html-documents" title="HTML documents">HTML document</a>, and whose <a href="#document-s-character-encoding" title="document's character encoding">character encoding</a> is
   UTF-8. The <code>Document</code> must have a single child
   <code><a href="#the-html-element">html</a></code> node, which itself has a single child
-  <code><a href="#the-body-element">body</a></code> node. If the <a href="#browsing-context">browsing context</a> is
-  created specifically to be immediately navigated, then that initial
+  <code><a href="#the-body-element">body</a></code> node.</p>
+
+  <p class="note">If the <a href="#browsing-context">browsing context</a> is created
+  specifically to be immediately navigated, then that initial
   navigation will have <a href="#replacement-enabled">replacement enabled</a>.</p>
 
   <p id="about-blank-origin">The <a href="#origin-0">origin</a> of the
@@ -40981,7 +41040,7 @@
      the <a href="#sandboxed-navigation-browsing-context-flag">sandboxed navigation browsing context flag</a>
      set.</dt>
 
-     <dd>The user agent may offer to create a new <a href="#top-level-browsing-context">top-level
+     <dd><p>The user agent may offer to create a new <a href="#top-level-browsing-context">top-level
      browsing context</a> or reuse an existing <a href="#top-level-browsing-context">top-level
      browsing context</a>. If the user picks one of those options,
      then the designated browsing context must be the chosen one (the
@@ -40995,35 +41054,40 @@
      browsing context is being requested as part of <a href="#following-hyperlinks" title="following hyperlinks">following a hyperlink</a> whose
      <a href="#linkTypes">link types</a> include the <code title="rel-noreferrer"><a href="#link-type-noreferrer">noreferrer</a></code> keyword</dt>
 
-     <dd>A new <a href="#top-level-browsing-context">top-level browsing context</a> must be
+     <dd><p>A new <a href="#top-level-browsing-context">top-level browsing context</a> must be
      created. If the given browsing context name is not <code title="">_blank</code>, then the new top-level browsing context's
      name must be the given browsing context name (otherwise, it has
      no name). The chosen browsing context must be this new browsing
-     context. If it is immediately <a href="#navigate" title="navigate">navigated</a>, then the navigation will be
+     context.</p>
+
+     <p class="note">If it is immediately <a href="#navigate" title="navigate">navigated</a>, then the navigation will be
      done with <a href="#replacement-enabled">replacement enabled</a>.</dd>
 
      <dt>If the user agent has been configured such that in this
      instance it will create a new browsing context, and the <code title="rel-noreferrer"><a href="#link-type-noreferrer">noreferrer</a></code> keyword doesn't
      apply</dt>
 
-     <dd>A new <a href="#auxiliary-browsing-context">auxiliary browsing context</a> must be
+     <dd><p>A new <a href="#auxiliary-browsing-context">auxiliary browsing context</a> must be
      created, with the <a href="#opener-browsing-context">opener browsing context</a> being the
      current one. If the given browsing context name is not <code title="">_blank</code>, then the new auxiliary browsing context's
      name must be the given browsing context name (otherwise, it has
      no name). The chosen browsing context must be this new browsing
-     context. If it is immediately <a href="#navigate" title="navigate">navigated</a>, then the navigation will be
-     done with <a href="#replacement-enabled">replacement enabled</a>.</dd>
+     context.</p>
+
+     <p>If it is immediately <a href="#navigate" title="navigate">navigated</a>,
+     then the navigation will be done with <a href="#replacement-enabled">replacement
+     enabled</a>.</dd>
 
      <dt>If the user agent has been configured such that in this
      instance it will reuse the current browsing context</dt>
 
-     <dd>The chosen browsing context is the current browsing
+     <dd><p>The chosen browsing context is the current browsing
      context.</dd>
 
      <dt>If the user agent has been configured such that in this
      instance it will not find a browsing context</dt>
 
-     <dd>There must not be a chosen browsing context.</dd>
+     <dd><p>There must not be a chosen browsing context.</dd>
 
     </dl><p>User agent implementors are encouraged to provide a way for
     users to configure the user agent to always reuse the current
@@ -46175,12 +46239,15 @@
   <a href="#resolve-a-url" title="resolve a url">resolve</a> the argument, relative to
   the <a href="#first-script">first script</a>'s <a href="#script-s-base-url" title="script's base URL">base
   URL</a>, and if that is successful, must <a href="#navigate">navigate</a>
-  the <a href="#browsing-context">browsing context</a> to the specified <var title="">url</var>.</p> <!-- READ ME WHEN EDITING THIS: browsers
-  seem to treat this as having <span>replacement enabled</span> if the
-  browsing context has only one entry and that entry is
-  about:blank. IE and Firefox only seem to treat it that way if the
-  DOM is still a virgin DOM; Safari doesn't check that. Thus this
-  might need changing if testing shows their behaviour is required
+  the <a href="#browsing-context">browsing context</a> to the specified <var title="">url</var>. If the <a href="#browsing-context">browsing context</a>'s
+  <a href="#session-history">session history</a> contains only one
+  <code>Document</code>, and that was the <code><a href="#about:blank">about:blank</a></code>
+  <code>Document</code> created when the <a href="#browsing-context">browsing context</a>
+  was created, then the navigation must be done with
+  <a href="#replacement-enabled">replacement enabled</a>.</p> <!-- READ ME WHEN EDITING
+  THIS: IE and Firefox only seem to treat it that way if the DOM is
+  still a virgin DOM; Safari doesn't check that. Thus this might need
+  changing if testing shows the IE/Firefox behaviour is required
   here. -->
 
   <p>When the <dfn id="dom-location-replace" title="dom-location-replace"><code>replace(<var title="">url</var>)</code></dfn> method is invoked, the UA must
@@ -50103,10 +50170,10 @@
     and <a href="#extracting-json" title="extracting JSON">extract the microdata from those
     nodes into a JSON form</a>, and then must add the resulting
     string to the <code title="dom-DragEvent-dataTransfer"><a href="#dom-dragevent-datatransfer">dataTransfer</a></code> member,
-    associated with the <code title="">application/microdata+json</code> format.</li> <!-- XXX
+    associated with the <code title="">application/microdata+json</code> format.</p> <!-- XXX
     register -->
 
-   <li>
+   </li>
 
    <li>
 
Received on Wednesday, 1 July 2009 21:39:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 July 2009 21:39:08 GMT