[html5] r7531 - [e] (0) More clean-up. Also, recast the microdata vocabs as primarily sample voc [...]

whatwg at whatwg.org whatwg at whatwg.org
Sat Nov 24 09:39:21 PST 2012


Author: ianh
Date: 2012-11-24 09:39:19 -0800 (Sat, 24 Nov 2012)
New Revision: 7531

Modified:
   complete.html
   index
   source
Log:
[e] (0) More clean-up. Also, recast the microdata vocabs as primarily sample vocabs rather than widely-used ones.
Affected topics: HTML, Microdata, Security

Modified: complete.html
===================================================================
--- complete.html	2012-11-24 04:51:58 UTC (rev 7530)
+++ complete.html	2012-11-24 17:39:19 UTC (rev 7531)
@@ -852,7 +852,7 @@
      <li><a href=#associating-names-with-items><span class=secno>5.2.5 </span>Associating names with items</a></li>
      <li><a href=#microdata-and-other-namespaces><span class=secno>5.2.6 </span>Microdata and other namespaces</a></ol></li>
    <li><a href=#microdata-dom-api><span class=secno>5.3 </span>Microdata DOM API</a></li>
-   <li><a href=#mdvocabs><span class=secno>5.4 </span>Microdata vocabularies</a>
+   <li><a href=#mdvocabs><span class=secno>5.4 </span>Sample microdata vocabularies</a>
     <ol>
      <li><a href=#vcard><span class=secno>5.4.1 </span>vCard</a>
       <ol>
@@ -1614,7 +1614,7 @@
    <li>The <code title=attr-inert><a href=#the-inert-attribute>inert</a></code> global attribute to disable subtrees.</li><!--INERT-->
    <li>The <code title=attr-fs-method-dialog-keyword><a href=#attr-fs-method-dialog-keyword>dialog</a></code> keyword on the <code><a href=#the-form-element>form</a></code> element's <code title=attr-fs-method><a href=#attr-fs-method>method</a></code> attribute, for a simpler way to close dialogs.</li><!--FORM-DIALOG-->
    <li>The <code title=dom-document-cssElementMap><a href=#dom-document-csselementmap>cssElementMap</a></code> feature for defining <a href=#css-element-reference-identifier title="CSS element reference identifier">CSS element reference identifiers</a>.</li> <!--CSSREF-->
-   <li>Some predefined <a href=#mdvocabs>Microdata vocabularies</a>.</li>
+   <li>Some predefined sample <a href=#mdvocabs>Microdata vocabularies</a>.</li>
    <li>The <code><a href=#the-data-element>data</a></code> element for marking up machine-readable data.</li><!--DATA--><!--FORK-->
    <li>The <a href=#application-cache>application cache</a> feature's <a href=#concept-appcache-mode-prefer-online title=concept-appcache-mode-prefer-online>prefer-online</a> mode.</li><!--FORK--><!--APPCACHE-PREFER-ONLINE-->
    <li>The <code title=dom-TextTrack-inBandMetadataTrackDispatchType><a href=#dom-texttrack-inbandmetadatatrackdispatchtype>TextTrack.inBandMetadataTrackDispatchType</a></code> feature for Internet-based TV broadcast.</li>
@@ -59938,7 +59938,6 @@
   attribute, on getting, must return the last value to which it was
   set. On setting, it must be set to the new value. When the element
   is created, it must be set to the empty string.</p>
-
 <!--TOPIC:HTML-->
 
   <hr><p><strong>Canceling dialogs</strong>: When a
@@ -62836,6 +62835,7 @@
   </div>
 
 
+<!--TOPIC:Microdata-->
 
   <h2 id=microdata><span class=secno>5 </span><dfn>Microdata</dfn></h2>
 
@@ -62878,20 +62878,17 @@
 
 <!-- v2
 
-  * <itemref itemprop="foo" src="url#id"> to import the item with
-    id="id" from url into the current microdata block as the value of
-    property foo?
+  * <itemref itemprop="foo" src="url#id"> to import the item with id="id" from url into the current
+    microdata block as the value of property foo?
 
-  * splitting the 'content' part of a property into multiple sub-bits,
-    as in:
+  * splitting the 'content' part of a property into multiple sub-bits, as in:
 
      <span itemprop="tel" item-content-in-bits>
        Telephone:
        <span content-bit>+44</span> (0) <span content-bit>1223 123 123</span>
      </span>
 
-    maybe vocabs that need this can use a sub vocabulary specifically
-    for this:
+    maybe vocabs that need this can use a sub vocabulary specifically for this:
 
      <span itemprop="tel" itemscope itemtype="http://bits.example/">
        Telephone:
@@ -62906,32 +62903,27 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Sometimes, it is desirable to annotate content with specific
-  machine-readable labels, e.g. to allow generic scripts to provide
-  services that are customised to the page, or to enable content from
-  a variety of cooperating authors to be processed by a single script
-  in a consistent manner.</p>
+  <p>Sometimes, it is desirable to annotate content with specific machine-readable labels, e.g. to
+  allow generic scripts to provide services that are customised to the page, or to enable content
+  from a variety of cooperating authors to be processed by a single script in a consistent
+  manner.</p>
 
-  <p>For this purpose, authors can use the microdata features
-  described in this section. Microdata allows nested groups of
-  name-value pairs to be added to documents, in parallel with the
-  existing content.</p>
+  <p>For this purpose, authors can use the microdata features described in this section. Microdata
+  allows nested groups of name-value pairs to be added to documents, in parallel with the existing
+  content.</p>
 
 
-
   <h4 id=the-basic-syntax><span class=secno>5.1.2 </span>The basic syntax</h4>
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>At a high level, microdata consists of a group of name-value
-  pairs. The groups are called <a href=#concept-item title=concept-item>items</a>, and each name-value pair is a
-  property. Items and properties are represented by regular
-  elements.</p>
+  <p>At a high level, microdata consists of a group of name-value pairs. The groups are called <a href=#concept-item title=concept-item>items</a>, and each name-value pair is a property. Items and properties
+  are represented by regular elements.</p>
 
   <p>To create an item, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is used.</p>
 
-  <p>To add a property to an item, the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is used on one of
-  the <a href=#concept-item title=concept-item>item's</a> descendants.</p>
+  <p>To add a property to an item, the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is used
+  on one of the <a href=#concept-item title=concept-item>item's</a> descendants.</p>
 
   <div class=example>
 
@@ -62947,13 +62939,12 @@
 
   </div>
 
-  <p>Markup without microdata attributes has no effect on
-  microdata.</p>
+  <p>Markup without microdata attributes has no effect on microdata.</p>
 
   <div class=example>
 
-   <p>These two examples are exactly equivalent, at a microdata level,
-   as the previous two examples respectively:</p>
+   <p>These two examples are exactly equivalent, at a microdata level, as the previous two examples
+   respectively:</p>
 
    <pre><div itemscope>
  <p>My <em>name</em> is <span itemprop="name">E<strong>liz</strong>abeth</span>.</p>
@@ -62983,15 +62974,14 @@
 
   </div>
 
-  <p>When a string value is a <a href=#url title=URL>URLs</a>, it is
-  expressed using the <code><a href=#the-a-element>a</a></code> element and its <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute, the
-  <code><a href=#the-img-element>img</a></code> element and its <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute, or other elements that
-  link to or embed external resources.</p>
+  <p>When a string value is a <a href=#url title=URL>URLs</a>, it is expressed using the
+  <code><a href=#the-a-element>a</a></code> element and its <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute, the
+  <code><a href=#the-img-element>img</a></code> element and its <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute, or other
+  elements that link to or embed external resources.</p>
 
   <div class=example>
 
-   <p>In this example, the item has one property, "image", whose value
-   is a URL:</p>
+   <p>In this example, the item has one property, "image", whose value is a URL:</p>
 
    <pre><div itemscope>
  <img itemprop="image" src="google-logo.png" alt="Google">
@@ -63006,9 +62996,8 @@
 
   <div class=example>
 
-   <p>Here, there is an item with a property whose value is a product
-   ID. The ID is not human-friendly, so the product's name is used
-   the human-visible text instead of the ID.</p>
+   <p>Here, there is an item with a property whose value is a product ID. The ID is not
+   human-friendly, so the product's name is used the human-visible text instead of the ID.</p>
 
    <pre><h1 itemscope>
  <data itemprop="product-id" value="9678AOU879">The Instigator 2000</data>
@@ -63016,14 +63005,11 @@
 
   </div>
 
-  <p>For date- and time-related data, the <code><a href=#the-time-element>time</a></code> element
-  and its <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> attribute
-  can be used instead.</p>
+  <p>For date- and time-related data, the <code><a href=#the-time-element>time</a></code> element and its <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> attribute can be used instead.</p>
 
   <div class=example>
 
-   <p>In this example, the item has one property, "birthday", whose
-   value is a date:</p>
+   <p>In this example, the item has one property, "birthday", whose value is a date:</p>
 
    <pre><div itemscope>
  I was born on <time itemprop="birthday" datetime="2009-05-10">May 10th 2009</time>.
@@ -63031,44 +63017,35 @@
 
   </div>
 
-  <p>Properties can also themselves be groups of name-value pairs, by
-  putting the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute
-  on the element that declares the property.</p>
+  <p>Properties can also themselves be groups of name-value pairs, by putting the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute on the element that declares the property.</p>
 
-  <p>Items that are not part of others are called <a href=#top-level-microdata-items>top-level
-  microdata items</a>.</p>
+  <p>Items that are not part of others are called <a href=#top-level-microdata-items>top-level microdata items</a>.</p>
 
   <div class=example>
 
-   <p>In this example, the outer item represents a person, and the
-   inner one represents a band:</p>
+   <p>In this example, the outer item represents a person, and the inner one represents a band:</p>
 
    <pre><div itemscope>
  <p>Name: <span itemprop="name">Amanda</span></p>
  <p>Band: <span itemprop="band" itemscope> <span itemprop="name">Jazz Band</span> (<span itemprop="size">12</span> players)</span></p>
 </div></pre>
 
-   <p>The outer item here has two properties, "name" and
-   "band". The "name" is "Amanda", and the
-   "band" is an item in its own right, with two
-   properties, "name" and "size". The
-   "name" of the band is "Jazz Band", and the
-   "size" is "12".</p>
+   <p>The outer item here has two properties, "name" and "band". The "name" is "Amanda", and the
+   "band" is an item in its own right, with two properties, "name" and "size". The "name" of the
+   band is "Jazz Band", and the "size" is "12".</p>
 
-   <p>The outer item in this example is a top-level microdata
-   item.</p>
+   <p>The outer item in this example is a top-level microdata item.</p>
 
   </div>
 
-  <p>Properties that are not descendants of the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute can be associated
-  with the <a href=#concept-item title=concept-item>item</a> using the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute. This attribute takes
-  a list of IDs of elements to crawl in addition to crawling the
-  children of the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
+  <p>Properties that are not descendants of the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute can be associated with the <a href=#concept-item title=concept-item>item</a> using the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute.
+  This attribute takes a list of IDs of elements to crawl in addition to crawling the children of
+  the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
 
   <div class=example>
 
-   <p>This example is the same as the previous one, but all the
-   properties are separated from their <a href=#concept-item title=concept-item>items</a>:</p>
+   <p>This example is the same as the previous one, but all the properties are separated from their
+   <a href=#concept-item title=concept-item>items</a>:</p>
 
    <pre><div itemscope id="amanda" itemref="a b"></div>
 <p id="a">Name: <span itemprop="name">Amanda</span></p>
@@ -63078,15 +63055,14 @@
  <p>Size: <span itemprop="size">12</span> players</p>
 </div></pre>
 
-   <p>This gives the same result as the previous example. The first
-   item has two properties, "name", set to "Amanda", and "band", set
-   to another item. That second item has two further properties,
+   <p>This gives the same result as the previous example. The first item has two properties, "name",
+   set to "Amanda", and "band", set to another item. That second item has two further properties,
    "name", set to "Jazz Band", and "size", set to "12".</p>
 
   </div>
 
-  <p>An <a href=#concept-item title=concept-item>item</a> can have multiple
-  properties with the same name and different values.</p>
+  <p>An <a href=#concept-item title=concept-item>item</a> can have multiple properties with the same name and
+  different values.</p>
 
   <div class=example>
 
@@ -63100,21 +63076,18 @@
  </ul>
 </div></pre>
 
-   <p>This thus results in an item with two properties, both
-   "flavor", having the values "Lemon sorbet" and "Apricot
-   sorbet".</p>
+   <p>This thus results in an item with two properties, both "flavor", having the values "Lemon
+   sorbet" and "Apricot sorbet".</p>
 
   </div>
 
-  <p>An element introducing a property can also introduce multiple
-  properties at once, to avoid duplication when some of the properties
-  have the same value.</p>
+  <p>An element introducing a property can also introduce multiple properties at once, to avoid
+  duplication when some of the properties have the same value.</p>
 
   <div class=example>
 
-   <p>Here we see an item with two properties,
-   "favorite-color" and "favorite-fruit", both
-   set to the value "orange":</p>
+   <p>Here we see an item with two properties, "favorite-color" and "favorite-fruit", both set to
+   the value "orange":</p>
 
    <pre><div itemscope>
  <span itemprop="favorite-color favorite-fruit">orange</span>
@@ -63122,14 +63095,12 @@
 
   </div>
 
-  <p>It's important to note that there is no relationship between the
-  microdata and the content of the document where the microdata is
-  marked up.</p>
+  <p>It's important to note that there is no relationship between the microdata and the content of
+  the document where the microdata is marked up.</p>
 
   <div class=example>
 
-   <p>There is no semantic difference, for instance, between the
-   following two examples:</p>
+   <p>There is no semantic difference, for instance, between the following two examples:</p>
 
    <pre><figure>
  <img src="castle.jpeg">
@@ -63142,13 +63113,11 @@
  <figcaption>The Castle (1986)</figcaption>
 </figure></pre>
 
-   <p>Both have a figure with a caption, and both, completely
-   unrelated to the figure, have an item with a name-value pair with
-   the name "name" and the value "The Castle". The only
-   difference is that if the user drags the caption out of the
-   document, in the former case, the item will be included in the
-   drag-and-drop data. In neither case is the image in any way
-   associated with the item.</p>
+   <p>Both have a figure with a caption, and both, completely unrelated to the figure, have an item
+   with a name-value pair with the name "name" and the value "The Castle". The only difference is
+   that if the user drags the caption out of the document, in the former case, the item will be
+   included in the drag-and-drop data. In neither case is the image in any way associated with the
+   item.</p>
 
   </div>
 
@@ -63157,19 +63126,15 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>The examples in the previous section show how information could
-  be marked up on a page that doesn't expect its microdata to be
-  re-used. Microdata is most useful, though, when it is used in
-  contexts where other authors and readers are able to cooperate to
-  make new uses of the markup.</p>
+  <p>The examples in the previous section show how information could be marked up on a page that
+  doesn't expect its microdata to be re-used. Microdata is most useful, though, when it is used in
+  contexts where other authors and readers are able to cooperate to make new uses of the markup.</p>
 
-  <p>For this purpose, it is necessary to give each <a href=#concept-item title=concept-item>item</a> a type, such as
-  "http://example.com/person", or "http://example.org/cat", or
-  "http://band.example.net/". Types are identified as <a href=#url title=URL>URLs</a>.</p>
+  <p>For this purpose, it is necessary to give each <a href=#concept-item title=concept-item>item</a> a type,
+  such as "http://example.com/person", or "http://example.org/cat", or "http://band.example.net/".
+  Types are identified as <a href=#url title=URL>URLs</a>.</p>
 
-  <p>The type for an <a href=#concept-item title=concept-item>item</a> is given
-  as the value of an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code>
-  attribute on the same element as the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
+  <p>The type for an <a href=#concept-item title=concept-item>item</a> is given as the value of an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute on the same element as the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
 
   <div class=example>
 
@@ -63182,45 +63147,34 @@
  <img itemprop="img" src="hedral.jpeg" alt="" title="Hedral, age 18 months">
 </section></pre>
 
-   <p>In this example the "http://example.org/animals#cat" item has three
-   properties, a "name" ("Hedral"), a "desc" ("Hedral is..."), and an
-   "img" ("hedral.jpeg").</p>
+   <p>In this example the "http://example.org/animals#cat" item has three properties, a "name"
+   ("Hedral"), a "desc" ("Hedral is..."), and an "img" ("hedral.jpeg").</p>
 
   </div>
 
-  <p>The type gives the context for the properties, thus selecting a
-  vocabulary: a property named "class" given for an item with the type
-  "http://census.example/person" might refer to the economic class of
-  an individual, while a property named "class" given for an item with
-  the type "http://example.com/school/teacher" might refer to the
-  classroom a teacher has been assigned. Several types can share a
-  vocabulary. For example, the types "<code title="">http://example.org/people/teacher</code>" and "<code title="">http://example.org/people/engineer</code>" could be defined
-  to use the same vocabulary (though maybe some properties would not
-  be especially useful in both cases, e.g. maybe the "<code title="">http://example.org/people/engineer</code>" type might not
-  typically be used with the "<code title="">classroom</code>"
-  property). Multiple types defined to use the same vocabulary can be
-  given for a single item by listing the URLs as a space-separated
-  list in the attribute' value. An item cannot be given two types if
-  they do not use the same vocabulary, however.</p>
+  <p>The type gives the context for the properties, thus selecting a vocabulary: a property named
+  "class" given for an item with the type "http://census.example/person" might refer to the economic
+  class of an individual, while a property named "class" given for an item with the type
+  "http://example.com/school/teacher" might refer to the classroom a teacher has been assigned.
+  Several types can share a vocabulary. For example, the types "<code title="">http://example.org/people/teacher</code>" and "<code title="">http://example.org/people/engineer</code>" could be defined to use the same vocabulary
+  (though maybe some properties would not be especially useful in both cases, e.g. maybe the "<code title="">http://example.org/people/engineer</code>" type might not typically be used with the
+  "<code title="">classroom</code>" property). Multiple types defined to use the same vocabulary can
+  be given for a single item by listing the URLs as a space-separated list in the attribute' value.
+  An item cannot be given two types if they do not use the same vocabulary, however.</p>
 
 
   <h4 id=global-identifiers-for-items><span class=secno>5.1.4 </span>Global identifiers for items</h4>
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Sometimes, an <a href=#concept-item title=concept-item>item</a> gives
-  information about a topic that has a global identifier. For example,
-  books can be identified by their ISBN number.</p>
+  <p>Sometimes, an <a href=#concept-item title=concept-item>item</a> gives information about a topic that has a
+  global identifier. For example, books can be identified by their ISBN number.</p>
 
-  <p>Vocabularies (as identified by the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute) can be designed
-  such that <a href=#concept-item title=concept-item>items</a> get associated
-  with their global identifier in an unambiguous way by expressing the
-  global identifiers as <a href=#url title=URL>URLs</a> given in an
-  <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute.</p>
+  <p>Vocabularies (as identified by the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute) can
+  be designed such that <a href=#concept-item title=concept-item>items</a> get associated with their global
+  identifier in an unambiguous way by expressing the global identifiers as <a href=#url title=URL>URLs</a> given in an <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute.</p>
 
-  <p>The exact meaning of the <a href=#url title=URL>URLs</a> given in
-  <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attributes depends on the
-  vocabulary used.</p>
+  <p>The exact meaning of the <a href=#url title=URL>URLs</a> given in <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attributes depends on the vocabulary used.</p>
 
   <div class=example>
 
@@ -63237,24 +63191,20 @@
  <dd><time itemprop="pubdate" datetime="1996-01-26">26 January 1996</time>
 </dl></pre>
 
-   <p>The "<code title="">http://vocab.example.net/book</code>"
-   vocabulary in this example would define that the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute takes a <code title="">urn:</code> <a href=#url>URL</a> pointing to the ISBN of the
-   book.</p>
+   <p>The "<code title="">http://vocab.example.net/book</code>" vocabulary in this example would
+   define that the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute takes a <code title="">urn:</code> <a href=#url>URL</a> pointing to the ISBN of the book.</p>
 
   </div>
 
   <!-- (commented out since itemtype="" defines the meaning of the
         identifier for now)
-  <p>Although it is common practice, authors are encouraged not to use
-  the same URL to identify multiple topics; in particular, an HTTP URL
-  usually identifies a specific resource (such as an image or
-  document), and authors are encouraged to not use them to identify
-  people, non-Web resources like companies, movies, and products, or
-  other abstract concepts. Using an HTTP URL as a global identifier
-  for something other than the resource actually designated by the URL
-  leads to a situation where it is ambiguous whether the identifier,
-  and thus the set of properties specified in the microdata,
-  references the page or something else.</p>
+  <p>Although it is common practice, authors are encouraged not to use the same URL to identify
+  multiple topics; in particular, an HTTP URL usually identifies a specific resource (such as an
+  image or document), and authors are encouraged to not use them to identify people, non-Web
+  resources like companies, movies, and products, or other abstract concepts. Using an HTTP URL as a
+  global identifier for something other than the resource actually designated by the URL leads to a
+  situation where it is ambiguous whether the identifier, and thus the set of properties specified
+  in the microdata, references the page or something else.</p>
   -->
 
 
@@ -63263,16 +63213,13 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Using microdata means using a vocabulary. For some purposes, an
-  ad-hoc vocabulary is adequate. For others, a vocabulary will need to
-  be designed. Where possible, authors are encouraged to re-use
-  existing vocabularies, as this makes content re-use easier.</p>
+  <p>Using microdata means using a vocabulary. For some purposes, an ad-hoc vocabulary is adequate.
+  For others, a vocabulary will need to be designed. Where possible, authors are encouraged to
+  re-use existing vocabularies, as this makes content re-use easier.</p>
 
-  <p>When designing new vocabularies, identifiers can be created
-  either using <a href=#url title=URL>URLs</a>, or, for properties, as
-  plain words (with no dots or colons). For URLs, conflicts with other
-  vocabularies can be avoided by only using identifiers that
-  correspond to pages that the author has control over.</p>
+  <p>When designing new vocabularies, identifiers can be created either using <a href=#url title=URL>URLs</a>, or, for properties, as plain words (with no dots or colons). For URLs,
+  conflicts with other vocabularies can be avoided by only using identifiers that correspond to
+  pages that the author has control over.</p>
 
   <div class=example>
 
@@ -63283,22 +63230,18 @@
 
   </div>
 
-  <p>Properties whose names are just plain words can only be used
-  within the context of the types for which they are intended;
-  properties named using URLs can be reused in items of any type. If
-  an item has no type, and is not part of another item, then if its
-  properties have names that are just plain words, they are not
-  intended to be globally unique, and are instead only intended for
-  limited use. Generally speaking, authors are encouraged to use
-  either properties with globally unique names (URLs) or ensure that
-  their items are typed.</p>
+  <p>Properties whose names are just plain words can only be used within the context of the types
+  for which they are intended; properties named using URLs can be reused in items of any type. If an
+  item has no type, and is not part of another item, then if its properties have names that are just
+  plain words, they are not intended to be globally unique, and are instead only intended for
+  limited use. Generally speaking, authors are encouraged to use either properties with globally
+  unique names (URLs) or ensure that their items are typed.</p>
 
   <div class=example>
 
-   <p>Here, an item is an "http://example.org/animals#cat", and most of the
-   properties have names that are words defined in the context of that
-   type. There are also a few additional properties whose names come
-   from other vocabularies.</p>
+   <p>Here, an item is an "http://example.org/animals#cat", and most of the properties have names
+   that are words defined in the context of that type. There are also a few additional properties
+   whose names come from other vocabularies.</p>
 
 <pre><section itemscope itemtype="http://example.org/animals#cat">
  <h1 itemprop="name http://example.com/fn">Hedral</h1>
@@ -63309,8 +63252,8 @@
  <img itemprop="img" src="hedral.jpeg" alt="" title="Hedral, age 18 months">
 </section></pre>
 
-   <p>This example has one item with the type "http://example.org/animals#cat"
-   and the following properties:</p>
+   <p>This example has one item with the type "http://example.org/animals#cat" and the following
+   properties:</p>
 
    <table><thead><tr><td>Property
       <td>Value
@@ -63334,69 +63277,61 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>The microdata becomes even more useful when scripts can use it to
-  expose information to the user, for example offering it in a form
-  that can be used by other applications.</p>
+  <p>The microdata becomes even more useful when scripts can use it to expose information to the
+  user, for example offering it in a form that can be used by other applications.</p>
 
-  <p>The <code title=dom-document-getItems><a href=#dom-document-getitems>document.getItems(<var title="">typeNames</var>)</a></code> method provides access to the
-  <a href=#top-level-microdata-items>top-level microdata items</a>. It returns a
-  <code><a href=#nodelist>NodeList</a></code> containing the items with the specified types,
-  or all types if no argument is specified.</p>
+  <p>The <code title=dom-document-getItems><a href=#dom-document-getitems>document.getItems(<var title="">typeNames</var>)</a></code>
+  method provides access to the <a href=#top-level-microdata-items>top-level microdata items</a>. It returns a
+  <code><a href=#nodelist>NodeList</a></code> containing the items with the specified types, or all types if no argument
+  is specified.</p>
 
-  <p>Each <a href=#concept-item title=concept-item>item</a> is represented in the
-  DOM by the element on which the relevant <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is found. These
-  elements have their <code title=dom-itemScope><a href=#dom-itemscope>element.itemScope</a></code> IDL attribute set to
-  true.</p>
+  <p>Each <a href=#concept-item title=concept-item>item</a> is represented in the DOM by the element on which
+  the relevant <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is found. These elements have
+  their <code title=dom-itemScope><a href=#dom-itemscope>element.itemScope</a></code> IDL attribute set to true.</p>
 
-  <p>The type(s) of <a href=#concept-item title=concept-item>items</a> can be
-  obtained using the <code title=dom-itemType><a href=#dom-itemtype>element.itemType</a></code> IDL attribute on the
-  element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute.</p>
+  <p>The type(s) of <a href=#concept-item title=concept-item>items</a> can be obtained using the <code title=dom-itemType><a href=#dom-itemtype>element.itemType</a></code> IDL attribute on the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
 
   <div class=example>
 
-   <p>This sample shows how the <code title=dom-document-getItems><a href=#dom-document-getitems>getItems()</a></code> method can be used
-   to obtain a list of all the top-level microdata items of a
-   particular type given in the document:</p>
+   <p>This sample shows how the <code title=dom-document-getItems><a href=#dom-document-getitems>getItems()</a></code> method can be
+   used to obtain a list of all the top-level microdata items of a particular type given in the
+   document:</p>
 
    <pre>var cats = document.getItems("http://example.com/feline");</pre>
 
   </div>
 
-  <p>Once an element representing an <a href=#concept-item title=concept-item>item</a> has been obtained, its properties
-  can be extracted using the <code title=dom-properties><a href=#dom-properties>properties</a></code> IDL attribute. This
-  attribute returns an <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code>, which can
-  be enumerated to go through each element that adds one or more
-  properties to the item. It can also be indexed by name, which will
-  return an object with a list of the elements that add properties
-  with that name.</p>
+  <p>Once an element representing an <a href=#concept-item title=concept-item>item</a> has been obtained, its
+  properties can be extracted using the <code title=dom-properties><a href=#dom-properties>properties</a></code> IDL
+  attribute. This attribute returns an <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code>, which can be
+  enumerated to go through each element that adds one or more properties to the item. It can also be
+  indexed by name, which will return an object with a list of the elements that add properties with
+  that name.</p>
 
-  <p>Each element that adds a property also has an <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL attribute that returns
-  its value.</p>
+  <p>Each element that adds a property also has an <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL
+  attribute that returns its value.</p>
 
   <div class=example>
 
-   <p>This sample gets the first item of type "http://example.net/user" and
-   then pops up an alert using the "name" property from
-   that item.</p>
+   <p>This sample gets the first item of type "http://example.net/user" and then pops up an alert
+   using the "name" property from that item.</p>
 
    <pre>var user = document.getItems('http://example.net/user')[0];
 alert('Hello ' + user.properties['name'][0].itemValue + '!');</pre>
 
   </div>
 
-  <p>The <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object, when indexed by
-  name in this way, actually returns a <code><a href=#propertynodelist>PropertyNodeList</a></code>
-  object with all the matching properties. The
-  <code><a href=#propertynodelist>PropertyNodeList</a></code> object can be used to obtain all the
-  values at once using <em>its</em> <code title=dom-PropertyNodeList-getValues><a href=#dom-propertynodelist-getvalues>getValues</a></code> method,
-  which returns an array of all the values.</p>
+  <p>The <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object, when indexed by name in this way, actually
+  returns a <code><a href=#propertynodelist>PropertyNodeList</a></code> object with all the matching properties. The
+  <code><a href=#propertynodelist>PropertyNodeList</a></code> object can be used to obtain all the values at once using
+  <em>its</em> <code title=dom-PropertyNodeList-getValues><a href=#dom-propertynodelist-getvalues>getValues</a></code> method, which returns
+  an array of all the values.</p>
 
   <div class=example>
 
    <p>In an earlier example, a "http://example.org/animals#cat" item had two
-   "http://example.com/color" values. This script looks up the first such
-   item and then lists all its values.</p>
+   "http://example.com/color" values. This script looks up the first such item and then lists all
+   its values.</p>
 
    <pre>var cat = document.getItems('http://example.org/animals#cat')[0];
 var colors = cat.properties['http://example.com/color'].getValues();
@@ -63413,15 +63348,13 @@
 
   </div>
 
-  <p>It's also possible to get a list of all the <a href=#property-names>property
-  names</a> using the object's <code title=dom-HTMLPropertiesCollection-names><a href=#dom-htmlpropertiescollection-names>names</a></code> IDL
-  attribute.</p>
+  <p>It's also possible to get a list of all the <a href=#property-names>property names</a> using the object's
+  <code title=dom-HTMLPropertiesCollection-names><a href=#dom-htmlpropertiescollection-names>names</a></code> IDL attribute.</p>
 
   <div class=example>
 
-   <p>This example creates a big list with a nested list for each item
-   on the page, each with of all the property names used in that
-   item.</p>
+   <p>This example creates a big list with a nested list for each item on the page, each with of all
+   the property names used in that item.</p>
 
    <pre>var outer = document.createElement('ul');
 var items = document.getItems();
@@ -63458,8 +63391,7 @@
       <li>http://example.com/color</li>
       <li>img</li>
      </ul></li>
-   </ul><p>(The duplicate occurrence of "http://example.com/color" is not included
-   in the list.)</p>
+   </ul><p>(The duplicate occurrence of "http://example.com/color" is not included in the list.)</p>
 
   </div>
 
@@ -63469,142 +63401,110 @@
 
   <h4 id=the-microdata-model><span class=secno>5.2.1 </span>The microdata model</h4>
 
-  <p>The microdata model consists of groups of name-value pairs known
-  as <a href=#concept-item title=concept-item>items</a>.</p>
+  <p>The microdata model consists of groups of name-value pairs known as <a href=#concept-item title=concept-item>items</a>.</p>
 
-  <p>Each group is known as an <a href=#concept-item title=concept-item>item</a>.
-  Each <a href=#concept-item title=concept-item>item</a> can have <a href=#item-types>item
-  types</a>, a <a href=#global-identifier>global identifier</a> (if the vocabulary
-  specified by the <a href=#item-types>item types</a> <a href=#support-global-identifiers-for-items>support global
-  identifiers for items</a>), and a list of name-value pairs. Each
-  name in the name-value pair is known as a <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a>, and each <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a> has one or more <a href=#concept-property-value title=concept-property-value>values</a>. Each <a href=#concept-property-value title=concept-property-value>value</a> is either a string or
-  itself a group of name-value pairs (an <a href=#concept-item title=concept-item>item</a>). The names are unordered relative
-  to each other, but if a particular name has multiple values, they do
-  have a relative order.</p>
+  <p>Each group is known as an <a href=#concept-item title=concept-item>item</a>. Each <a href=#concept-item title=concept-item>item</a> can have <a href=#item-types>item types</a>, a <a href=#global-identifier>global
+  identifier</a> (if the vocabulary specified by the <a href=#item-types>item types</a> <a href=#support-global-identifiers-for-items>support global
+  identifiers for items</a>), and a list of name-value pairs. Each name in the name-value pair is
+  known as a <a href=#the-properties-of-an-item title="the properties of an item">property</a>, and each <a href=#the-properties-of-an-item title="the
+  properties of an item">property</a> has one or more <a href=#concept-property-value title=concept-property-value>values</a>. Each <a href=#concept-property-value title=concept-property-value>value</a> is either a string or itself a group of name-value
+  pairs (an <a href=#concept-item title=concept-item>item</a>). The names are unordered relative to each other,
+  but if a particular name has multiple values, they do have a relative order.</p>
 
-  <p>An <a href=#concept-item title=concept-item>item</a> is said to be a
-  <dfn id=typed-item>typed item</dfn> when either it has an <a href=#item-types title="item
-  types">item type</a>, or it is the <a href=#concept-property-value title=concept-property-value>value</a> of a <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a> of a <a href=#typed-item>typed item</a>.
-  The <dfn id=relevant-types>relevant types</dfn> for a <a href=#typed-item>typed item</a> is the
-  <a href=#concept-item title=concept-item>item</a>'s <a href=#item-types>item types</a>, if
-  it has one, or else is the <a href=#relevant-types>relevant types</a> of the <a href=#concept-item title=concept-item>item</a> for which it is a <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a>'s <a href=#concept-property-value title=concept-property-value>value</a>.</p>
+  <p>An <a href=#concept-item title=concept-item>item</a> is said to be a <dfn id=typed-item>typed item</dfn> when either it
+  has an <a href=#item-types title="item types">item type</a>, or it is the <a href=#concept-property-value title=concept-property-value>value</a> of a <a href=#the-properties-of-an-item title="the properties of an
+  item">property</a> of a <a href=#typed-item>typed item</a>. The <dfn id=relevant-types>relevant types</dfn> for a
+  <a href=#typed-item>typed item</a> is the <a href=#concept-item title=concept-item>item</a>'s <a href=#item-types>item types</a>,
+  if it has one, or else is the <a href=#relevant-types>relevant types</a> of the <a href=#concept-item title=concept-item>item</a> for which it is a <a href=#the-properties-of-an-item title="the properties of an
+  item">property</a>'s <a href=#concept-property-value title=concept-property-value>value</a>.</p>
 
 
 
   <h4 id=items><span class=secno>5.2.2 </span>Items</h4>
 
-  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an
-  <dfn id=attr-itemscope title=attr-itemscope><code>itemscope</code></dfn> attribute
-  specified. The <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute is a <a href=#boolean-attribute>boolean attribute</a>.</p>
+  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an <dfn id=attr-itemscope title=attr-itemscope><code>itemscope</code></dfn> attribute specified. The <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is a <a href=#boolean-attribute>boolean attribute</a>.</p>
 
-  <p>An element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute specified creates a new <dfn id=concept-item title=concept-item>item</dfn>, a group of name-value pairs.</p>
+  <p>An element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified creates a
+  new <dfn id=concept-item title=concept-item>item</dfn>, a group of name-value pairs.</p>
 
-  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute may have an <dfn id=attr-itemtype title=attr-itemtype><code>itemtype</code></dfn> attribute
-  specified, to give the <a href=#item-types>item types</a> of the <a href=#concept-item title=concept-item>item</a>.</p>
+  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute may have an <dfn id=attr-itemtype title=attr-itemtype><code>itemtype</code></dfn> attribute specified, to give the <a href=#item-types>item
+  types</a> of the <a href=#concept-item title=concept-item>item</a>.</p>
 
-  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute, if
-  specified, must have a value that is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of
-  unique space-separated tokens</a> that are
-  <a href=#case-sensitive>case-sensitive</a>, each of which is a <a href=#valid-url>valid
-  URL</a> that is an <a href=#absolute-url>absolute URL</a>, and all of which
-  are defined to use the same vocabulary. The attribute's value must
+  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute, if specified, must have a value that
+  is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are
+  <a href=#case-sensitive>case-sensitive</a>, each of which is a <a href=#valid-url>valid URL</a> that is an <a href=#absolute-url>absolute
+  URL</a>, and all of which are defined to use the same vocabulary. The attribute's value must
   have at least one token.</p>
 
-  <p>The <dfn id=item-types>item types</dfn> of an <a href=#concept-item title=concept-item>item</a> are the tokens obtained by <a href=#split-a-string-on-spaces title="split a string on spaces">splitting the element's <code title=attr-itemtype>itemtype</code> attribute's value on
-  spaces</a>. If the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code>
-  attribute is missing or parsing it in this way finds no tokens, the
-  <a href=#concept-item title=concept-item>item</a> is said to have no <a href=#item-types>item
-  types</a>.</p>
+  <p>The <dfn id=item-types>item types</dfn> of an <a href=#concept-item title=concept-item>item</a> are the tokens obtained
+  by <a href=#split-a-string-on-spaces title="split a string on spaces">splitting the element's <code title=attr-itemtype>itemtype</code> attribute's value on spaces</a>. If the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute is missing or parsing it in this way finds no
+  tokens, the <a href=#concept-item title=concept-item>item</a> is said to have no <a href=#item-types>item types</a>.</p>
 
-  <p>The <a href=#item-types>item types</a> must all be types defined in <a href=#other-applicable-specifications title="other applicable specifications">applicable
-  specifications</a> and must all be defined to use the same
+  <p>The <a href=#item-types>item types</a> must all be types defined in <a href=#other-applicable-specifications title="other applicable
+  specifications">applicable specifications</a> and must all be defined to use the same
   vocabulary.</p>
 
   <div class=impl>
 
-   <p>Except if otherwise specified by that specification, the <a href=#url title=URL>URLs</a> given as the <a href=#item-types>item types</a> should
-   not be automatically dereferenced.</p>
+   <p>Except if otherwise specified by that specification, the <a href=#url title=URL>URLs</a> given
+   as the <a href=#item-types>item types</a> should not be automatically dereferenced.</p>
 
-   <p class=note>A specification could define that its <a href=#item-types title="item types">item type</a> can be derefenced to provide
-   the user with help information, for example. In fact, vocabulary
-   authors are encouraged to provide useful information at the given
-   <a href=#url>URL</a>.</p>
+   <p class=note>A specification could define that its <a href=#item-types title="item types">item type</a>
+   can be derefenced to provide the user with help information, for example. In fact, vocabulary
+   authors are encouraged to provide useful information at the given <a href=#url>URL</a>.</p>
 
-   <p><a href=#item-types>Item types</a> are opaque identifiers, and user agents
-   must not dereference unknown <a href=#item-types>item types</a>, or otherwise
-   deconstruct them, in order to determine how to process <a href=#concept-item title=concept-item>items</a> that use them.</p>
+   <p><a href=#item-types>Item types</a> are opaque identifiers, and user agents must not dereference unknown
+   <a href=#item-types>item types</a>, or otherwise deconstruct them, in order to determine how to process
+   <a href=#concept-item title=concept-item>items</a> that use them.</p>
 
   </div>
 
-  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute must
-  not be specified on elements that do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
+  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute must not be specified on elements
+  that do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
 
-  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code>
-  attribute that references a vocabulary that is defined to
-  <dfn id=support-global-identifiers-for-items>support global identifiers for items</dfn> may also have an
-  <dfn id=attr-itemid title=attr-itemid><code>itemid</code></dfn> attribute
-  specified, to give a global identifier for the <a href=#concept-item title=concept-item>item</a>, so that it can be related to other
-  <a href=#concept-item title=concept-item>items</a> on pages elsewhere on the
-  Web.</p>
+  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute that references a vocabulary that is defined to
+  <dfn id=support-global-identifiers-for-items>support global identifiers for items</dfn> may also have an <dfn id=attr-itemid title=attr-itemid><code>itemid</code></dfn> attribute specified, to give a global identifier for
+  the <a href=#concept-item title=concept-item>item</a>, so that it can be related to other <a href=#concept-item title=concept-item>items</a> on pages elsewhere on the Web.</p>
 
-  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if
-  specified, must have a value that is a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially
-  surrounded by spaces</a>.</p>
+  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if specified, must have a value that is
+  a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially surrounded by spaces</a>.</p>
 
-  <p>The <dfn id=global-identifier>global identifier</dfn> of an <a href=#concept-item title=concept-item>item</a> is the value of its element's <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if it has one, <a href=#resolve-a-url title="resolve a url">resolved</a> relative to the element on
-  which the attribute is specified. If the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute is missing or if
-  resolving it fails, it is said to have no <a href=#global-identifier>global
-  identifier</a>.</p>
+  <p>The <dfn id=global-identifier>global identifier</dfn> of an <a href=#concept-item title=concept-item>item</a> is the value of
+  its element's <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if it has one, <a href=#resolve-a-url title="resolve a url">resolved</a> relative to the element on which the attribute is specified.
+  If the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute is missing or if resolving it fails, it
+  is said to have no <a href=#global-identifier>global identifier</a>.</p>
 
-  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute must not be
-  specified on elements that do not have both an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specified, and must
-  not be specified on elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute whose <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specifies a
-  vocabulary that does not <a href=#support-global-identifiers-for-items>support global identifiers for
-  items</a>, as defined by that vocabulary's specification.</p>
+  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute must not be specified on elements that do
+  not have both an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specified, and must not be specified on elements
+  with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute whose <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specifies a vocabulary that does not <a href=#support-global-identifiers-for-items>support
+  global identifiers for items</a>, as defined by that vocabulary's specification.</p>
 
-  <p>The exact meaning of a <a href=#global-identifier>global identifier</a> is
-  determined by the vocabulary's specification. It is up to such
-  specifications to define whether multiple items with the same global
-  identifier (whether on the same page or on different pages) are
-  allowed to exist, and what the processing rules for that vocabulary
-  are with respect to handling the case of multiple items with the
-  same ID.</p>
+  <p>The exact meaning of a <a href=#global-identifier>global identifier</a> is determined by the vocabulary's
+  specification. It is up to such specifications to define whether multiple items with the same
+  global identifier (whether on the same page or on different pages) are allowed to exist, and what
+  the processing rules for that vocabulary are with respect to handling the case of multiple items
+  with the same ID.</p>
 
-  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute may have an <dfn id=attr-itemref title=attr-itemref><code>itemref</code></dfn> attribute specified,
-  to give a list of additional elements to crawl to find the
-  name-value pairs of the <a href=#concept-item title=concept-item>item</a>.</p>
+  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute may have an <dfn id=attr-itemref title=attr-itemref><code>itemref</code></dfn> attribute specified, to give a list of additional
+  elements to crawl to find the name-value pairs of the <a href=#concept-item title=concept-item>item</a>.</p>
 
-  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, if
-  specified, must have a value that is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of
-  unique space-separated tokens</a> that are
-  <a href=#case-sensitive>case-sensitive</a>, consisting of <a href=#concept-id title=concept-ID>IDs</a> of elements in the same <a href=#home-subtree>home
-  subtree</a>.</p>
+  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, if specified, must have a value that
+  is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are
+  <a href=#case-sensitive>case-sensitive</a>, consisting of <a href=#concept-id title=concept-ID>IDs</a> of elements in the
+  same <a href=#home-subtree>home subtree</a>.</p>
 
-  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute must not
-  be specified on elements that do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
+  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute must not be specified on elements that
+  do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
 
-  <p class=note>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code>
-  attribute is not part of the microdata data model. It is merely a
-  syntactic construct to aid authors in adding annotations to pages
-  where the data to be annotated does not follow a convenient tree
-  structure. For example, it allows authors to mark up data in a table
-  so that each column defines a separate <a href=#concept-item title=concept-item>item</a>, while keeping the properties in
-  the cells.</p>
+  <p class=note>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute is not part of the
+  microdata data model. It is merely a syntactic construct to aid authors in adding annotations to
+  pages where the data to be annotated does not follow a convenient tree structure. For example, it
+  allows authors to mark up data in a table so that each column defines a separate <a href=#concept-item title=concept-item>item</a>, while keeping the properties in the cells.</p>
 
   <div class=example>
 
-   <p>This example shows a simple vocabulary used to describe the
-   products of a model railway manufacturer. The vocabulary has just
-   five property names:</p>
+   <p>This example shows a simple vocabulary used to describe the products of a model railway
+   manufacturer. The vocabulary has just five property names:</p>
 
    <dl><dt>product-code</dt>
     <dd>An integer that names the product in the manufacturer's catalog.</dd>
@@ -63631,9 +63531,8 @@
     <dd>Track pieces</dd>
     <dt>http://md.example.com/lighting</dt>
     <dd>Equipment with lighting</dd>
-   </dl><p>Each <a href=#concept-item title=concept-item>item</a> that uses this
-   vocabulary can be given one or more of these types, depending on
-   what the product is.</p>
+   </dl><p>Each <a href=#concept-item title=concept-item>item</a> that uses this vocabulary can be given one or more
+   of these types, depending on what the product is.</p>
 
    <p>Thus, a locomotive might be marked up as:</p>
 
@@ -63673,51 +63572,41 @@
  <dd itemprop="scale">Z
 </dl></pre>
 
-   <p>Great care is necessary when creating new vocabularies. Often, a
-   hierarchical approach to types can be taken that results in a
-   vocabulary where each item only ever has a single type, which is
-   generally much simpler to manage.</p>
+   <p>Great care is necessary when creating new vocabularies. Often, a hierarchical approach to
+   types can be taken that results in a vocabulary where each item only ever has a single type,
+   which is generally much simpler to manage.</p>
 
   </div>
 
 
   <h4 id=names:-the-itemprop-attribute><span class=secno>5.2.3 </span>Names: the <dfn title=attr-itemprop><code>itemprop</code></dfn> attribute</h4>
 
-  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an
-  <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute specified, if
-  doing so <a href=#the-properties-of-an-item title="the properties of an item">adds one or more
-  properties</a> to one or more <a href=#concept-item title=concept-item>items</a> (as defined below).</p>
+  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute specified, if doing so <a href=#the-properties-of-an-item title="the properties
+  of an item">adds one or more properties</a> to one or more <a href=#concept-item title=concept-item>items</a> (as defined below).</p>
 
-  <p>The <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute, if
-  specified, must have a value that is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of
-  unique space-separated tokens</a> that are
-  <a href=#case-sensitive>case-sensitive</a>, representing the names of the
-  name-value pairs that it adds. The attribute's value must have at
-  least one token.</p>
+  <p>The <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute, if specified, must have a value that
+  is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are
+  <a href=#case-sensitive>case-sensitive</a>, representing the names of the name-value pairs that it adds. The
+  attribute's value must have at least one token.</p>
 
   <p>Each token must be either:</p>
 
-  <ul><li>A <a href=#valid-url>valid URL</a> that is an <a href=#absolute-url>absolute URL</a>,
-   or</li>
+  <ul><li>A <a href=#valid-url>valid URL</a> that is an <a href=#absolute-url>absolute URL</a>, or</li>
 
-   <li>If the item is a <a href=#typed-item>typed item</a>: a <dfn id=defined-property-name>defined
-   property name</dfn> allowed in this situation according to the
-   specification that defines the <a href=#relevant-types>relevant types</a> for the
+   <li>If the item is a <a href=#typed-item>typed item</a>: a <dfn id=defined-property-name>defined property name</dfn> allowed in this
+   situation according to the specification that defines the <a href=#relevant-types>relevant types</a> for the
    item, or</li>
 
-   <li>If the item is not a <a href=#typed-item>typed item</a>: a string that
-   contains no U+002E FULL STOP characters (.) and no U+003A COLON
-   characters (:).</li>
+   <li>If the item is not a <a href=#typed-item>typed item</a>: a string that contains no U+002E FULL STOP
+   characters (.) and no U+003A COLON characters (:).</li>
 
-  </ul><p>Specifications that introduce <a href=#defined-property-name title="defined property
-  name">defined property names</a> that are not <a href=#absolute-url title="absolute URL">absolute URLs</a> must ensure all such
-  property names contain no U+002E FULL STOP characters (.), no U+003A
-  COLON characters (:), and no <a href=#space-character title="space character">space
-  characters</a>.</p>
+  </ul><p>Specifications that introduce <a href=#defined-property-name title="defined property name">defined property names</a>
+  that are not <a href=#absolute-url title="absolute URL">absolute URLs</a> must ensure all such property names
+  contain no U+002E FULL STOP characters (.), no U+003A COLON characters (:), and no <a href=#space-character title="space character">space characters</a>.</p>
 
   <p>When an element with an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute <a href=#the-properties-of-an-item title="the
-  properties of an item">adds a property</a> to multiple <a href=#concept-item title=concept-item>items</a>, the requirement above regarding
-  the tokens applies for each <a href=#concept-item title=concept-item>item</a>
+  properties of an item">adds a property</a> to multiple <a href=#concept-item title=concept-item>items</a>,
+  the requirement above regarding the tokens applies for each <a href=#concept-item title=concept-item>item</a>
   individually.</p>
 
   <!--
@@ -63732,23 +63621,17 @@
 
   -->
 
-  <p>The <dfn id=property-names>property names</dfn> of an element are the tokens that
-  the element's <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute
-  is found to contain when its value is <a href=#split-a-string-on-spaces title="split a string on
-  spaces">split on spaces</a>, with the order preserved but with
-  duplicates removed (leaving only the first occurrence of each
-  name).</p>
+  <p>The <dfn id=property-names>property names</dfn> of an element are the tokens that the element's <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is found to contain when its value is <a href=#split-a-string-on-spaces title="split a string on spaces">split on spaces</a>, with the order preserved but with
+  duplicates removed (leaving only the first occurrence of each name).</p>
 
-  <p>Within an <a href=#concept-item title=concept-item>item</a>, the properties
-  are unordered with respect to each other, except for properties with
-  the same name, which are ordered in the order they are given by the
-  algorithm that defines <a href=#the-properties-of-an-item>the properties of an item</a>.</p>
+  <p>Within an <a href=#concept-item title=concept-item>item</a>, the properties are unordered with respect to
+  each other, except for properties with the same name, which are ordered in the order they are
+  given by the algorithm that defines <a href=#the-properties-of-an-item>the properties of an item</a>.</p>
 
   <div class=example>
 
-   <p>In the following example, the "a" property has the values "1"
-   and "2", <em>in that order</em>, but whether the "a" property comes
-   before the "b" property or not is not important:</p>
+   <p>In the following example, the "a" property has the values "1" and "2", <em>in that order</em>,
+   but whether the "a" property comes before the "b" property or not is not important:</p>
 
    <pre><div itemscope>
  <p itemprop="a">1</p>
@@ -63789,16 +63672,15 @@
 
   <h4 id=values><span class=secno>5.2.4 </span>Values</h4>
 
-  <p>The <dfn id=concept-property-value title=concept-property-value>property value</dfn> of a
-  name-value pair added by an element with an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is as given for the
-  first matching case in the following list:</p>
+  <p>The <dfn id=concept-property-value title=concept-property-value>property value</dfn> of a name-value pair added by an
+  element with an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is as given for the first
+  matching case in the following list:</p>
 
   <dl class=switch><dt>If the element also has an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute</dt>
 
    <dd>
 
-    <p>The value is the <a href=#concept-item title=concept-item>item</a> created
-    by the element.</p>
+    <p>The value is the <a href=#concept-item title=concept-item>item</a> created by the element.</p>
 
    </dd>
 
@@ -63807,39 +63689,33 @@
 
    <dd>
 
-    <p>The value is the value of the element's <code title=attr-content>content</code> attribute, if any, or the
-    empty string if there is no such attribute.</p>
+    <p>The value is the value of the element's <code title=attr-content>content</code> attribute,
+    if any, or the empty string if there is no such attribute.</p>
 
    </dd>
 
 
-   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>,
-   <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>,
+   <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
 
    <dd>
 
-    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from
-    <a href=#resolve-a-url title="resolve a url">resolving</a> the value of the
-    element's <code title="">src</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <a href=#resolve-a-url title="resolve a
-    url">resolving</a> it results in an error.</p>
+    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from <a href=#resolve-a-url title="resolve a
+    url">resolving</a> the value of the element's <code title="">src</code> attribute relative to
+    the element at the time the attribute is set, or the empty string if there is no such attribute
+    or if <a href=#resolve-a-url title="resolve a url">resolving</a> it results in an error.</p>
 
    </dd>
 
 
-   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or
-   <code><a href=#the-link-element>link</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or <code><a href=#the-link-element>link</a></code> element</dt>
 
    <dd>
 
-    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from
-    <a href=#resolve-a-url title="resolve a url">resolving</a> the value of the
-    element's <code title="">href</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <a href=#resolve-a-url title="resolve a
-    url">resolving</a> it results in an error.</p>
+    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from <a href=#resolve-a-url title="resolve a
+    url">resolving</a> the value of the element's <code title="">href</code> attribute relative
+    to the element at the time the attribute is set, or the empty string if there is no such
+    attribute or if <a href=#resolve-a-url title="resolve a url">resolving</a> it results in an error.</p>
 
    </dd>
 
@@ -63848,12 +63724,10 @@
 
    <dd>
 
-    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from
-    <a href=#resolve-a-url title="resolve a url">resolving</a> the value of the
-    element's <code title="">data</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <a href=#resolve-a-url title="resolve a
-    url">resolving</a> it results in an error.</p>
+    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from <a href=#resolve-a-url title="resolve a
+    url">resolving</a> the value of the element's <code title="">data</code> attribute relative
+    to the element at the time the attribute is set, or the empty string if there is no such
+    attribute or if <a href=#resolve-a-url title="resolve a url">resolving</a> it results in an error.</p>
 
    </dd>
 
@@ -63862,8 +63736,8 @@
 
    <dd>
 
-    <p>The value is the value of the element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> attribute, if it has one, or
-    the empty string otherwise.</p>
+    <p>The value is the value of the element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> attribute,
+    if it has one, or the empty string otherwise.</p>
 
    </dd>
 
@@ -63885,121 +63759,98 @@
 
    </dd>
 
-  </dl><p>The <dfn id=url-property-elements>URL property elements</dfn> are the <code><a href=#the-a-element>a</a></code>,
-  <code><a href=#the-area-element>area</a></code>, <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-  <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-link-element>link</a></code>,
-  <code><a href=#the-object-element>object</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, and
-  <code><a href=#the-video-element>video</a></code> elements.</p>
+  </dl><p>The <dfn id=url-property-elements>URL property elements</dfn> are the <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>,
+  <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-link-element>link</a></code>,
+  <code><a href=#the-object-element>object</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, and <code><a href=#the-video-element>video</a></code> elements.</p>
 
-  <p>If a property's <a href=#concept-property-value title=concept-property-value>value</a>, as defined by the
-  property's definition, is an <a href=#absolute-url>absolute URL</a>, the property
-  must be specified using a <a href=#url-property-elements title="URL property elements">URL
-  property element</a>.</p>
+  <p>If a property's <a href=#concept-property-value title=concept-property-value>value</a>, as defined by the property's
+  definition, is an <a href=#absolute-url>absolute URL</a>, the property must be specified using a <a href=#url-property-elements title="URL property elements">URL property element</a>.</p>
 
-  <p class=note>These requirements do not apply just because a
-  property value happens to match the syntax for a URL. They only
-  apply if the property is explicitly defined as taking such a
+  <p class=note>These requirements do not apply just because a property value happens to match the
+  syntax for a URL. They only apply if the property is explicitly defined as taking such a
   value.</p>
 
-  <p class=example>For example, a book about the first moon landing
-  <!-- 1969-07-20 --> could be called "mission:moon". A "title"
-  property from a vocabulary that defines a title as being a string
-  would not expect the title to be given in an <code><a href=#the-a-element>a</a></code> element,
-  even though it looks like a <a href=#url>URL</a>. On the other hand, if
-  there was a (rather narrowly scoped!) vocabulary for "books whose
-  titles look like URLs" which had a "title" property defined to take
-  a URL, then the property <em>would</em> expect the title to be given
-  in an <code><a href=#the-a-element>a</a></code> element (or one of the other <a href=#url-property-elements>URL property
-  elements</a>), because of the requirement above.</p>
+  <p class=example>For example, a book about the first moon landing <!-- 1969-07-20 --> could be
+  called "mission:moon". A "title" property from a vocabulary that defines a title as being a string
+  would not expect the title to be given in an <code><a href=#the-a-element>a</a></code> element, even though it looks like a
+  <a href=#url>URL</a>. On the other hand, if there was a (rather narrowly scoped!) vocabulary for
+  "books whose titles look like URLs" which had a "title" property defined to take a URL, then the
+  property <em>would</em> expect the title to be given in an <code><a href=#the-a-element>a</a></code> element (or one of the
+  other <a href=#url-property-elements>URL property elements</a>), because of the requirement above.</p>
 
 
   <div class=impl>
 
   <h4 id=associating-names-with-items><span class=secno>5.2.5 </span>Associating names with items</h4>
 
-  <p>To find <dfn id=the-properties-of-an-item>the properties of an item</dfn> defined by the
-  element <var title="">root</var>, the user agent must run the
-  following steps. These steps are also used to flag <a href=#microdata-error title="microdata error">microdata errors</a>.</p>
+  <p>To find <dfn id=the-properties-of-an-item>the properties of an item</dfn> defined by the element <var title="">root</var>,
+  the user agent must run the following steps. These steps are also used to flag <a href=#microdata-error title="microdata error">microdata errors</a>.</p>
 
-  <ol><li><p>Let <var title="">results</var>, <var title="">memory</var>,
-   and <var title="">pending</var> be empty lists of
-   elements.</li>
+  <ol><li><p>Let <var title="">results</var>, <var title="">memory</var>, and <var title="">pending</var> be empty lists of elements.</li>
 
    <li><p>Add the element <var title="">root</var> to <var title="">memory</var>.</li>
 
-   <li><p>Add the child elements of <var title="">root</var>, if any,
-   to <var title="">pending</var>.</li>
+   <li><p>Add the child elements of <var title="">root</var>, if any, to <var title="">pending</var>.</li>
 
-   <li><p>If <var title="">root</var> has an <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, <a href=#split-a-string-on-spaces title="split a
-   string on spaces">split the value of that <code title=attr-itemref>itemref</code> attribute on spaces</a>. For
-   each resulting token <var title="">ID</var>, if there is an element
-   in the <a href=#home-subtree>home subtree</a> of <var title="">root</var> with
-   the <a href=#concept-id title=concept-ID>ID</a> <var title="">ID</var>, then
-   add the first such element to <var title="">pending</var>.</li>
+   <li><p>If <var title="">root</var> has an <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute,
+   <a href=#split-a-string-on-spaces title="split a string on spaces">split the value of that <code title=attr-itemref>itemref</code> attribute on spaces</a>. For each resulting token <var title="">ID</var>, if there is an element in the <a href=#home-subtree>home subtree</a> of <var title="">root</var> with the <a href=#concept-id title=concept-ID>ID</a> <var title="">ID</var>, then add
+   the first such element to <var title="">pending</var>.</li>
 
-   <li><p><i>Loop</i>: If <var title="">pending</var> is empty, jump
-   to the step labeled <i>end of loop</i>.</li>
+   <li><p><i>Loop</i>: If <var title="">pending</var> is empty, jump to the step labeled <i>end of
+   loop</i>.</li>
 
-   <li><p>Remove an element from <var title="">pending</var> and let
-   <var title="">current</var> be that element.</li>
+   <li><p>Remove an element from <var title="">pending</var> and let <var title="">current</var> be
+   that element.</li>
 
-   <li><p>If <var title="">current</var> is already in <var title="">memory</var>, there is a <a href=#microdata-error>microdata error</a>;
-   return to the step labeled <i>loop</i>.</li>
+   <li><p>If <var title="">current</var> is already in <var title="">memory</var>, there is a
+   <a href=#microdata-error>microdata error</a>; return to the step labeled <i>loop</i>.</li>
 
    <li><p>Add <var title="">current</var> to <var title="">memory</var>.</li>
 
-   <li><p>If <var title="">current</var> does not
-   have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute,
-   then: add all the child elements of <var title="">current</var> to
-   <var title="">pending</var>.</li>
+   <li><p>If <var title="">current</var> does not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute, then: add all the child elements of <var title="">current</var> to <var title="">pending</var>.</li>
 
-   <li><p>If <var title="">current</var> has an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute specified and has
-   one or more <a href=#property-names>property names</a>, then add <var title="">current</var> to <var title="">results</var>.</li>
+   <li><p>If <var title="">current</var> has an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>
+   attribute specified and has one or more <a href=#property-names>property names</a>, then add <var title="">current</var> to <var title="">results</var>.</li>
 
    <li><p>Return to the step labeled <i>loop</i>.</li>
 
-   <li><p><i>End of loop</i>: Sort <var title="">results</var> in
-   <a href=#tree-order>tree order</a>.</li>
+   <li><p><i>End of loop</i>: Sort <var title="">results</var> in <a href=#tree-order>tree order</a>.</li>
 
    <li><p>Return <var title="">results</var>.</li>
 
-  </ol><p>A document must not contain any <a href=#concept-item title=concept-item>items</a> for which the algorithm to find
-  <a href=#the-properties-of-an-item>the properties of an item</a> finds any <dfn id=microdata-error title="microdata error">microdata errors</dfn>.</p>
+  </ol><p>A document must not contain any <a href=#concept-item title=concept-item>items</a> for which the algorithm
+  to find <a href=#the-properties-of-an-item>the properties of an item</a> finds any <dfn id=microdata-error title="microdata error">microdata
+  errors</dfn>.</p>
 
-  <p>An <a href=#concept-item title=concept-item>item</a> is a <dfn id=top-level-microdata-items title="top-level microdata items">top-level microdata item</dfn> if
-  its element does not have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute.</p>
+  <p>An <a href=#concept-item title=concept-item>item</a> is a <dfn id=top-level-microdata-items title="top-level microdata items">top-level
+  microdata item</dfn> if its element does not have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>
+  attribute.</p>
 
 <!--(this is currently redundant with "requirement itemprop" below)
-  <p>An <span title="concept-item">item</span> is a <dfn title="used
-  microdata items">used microdata item</dfn> if it is a <span
-  title="top-level microdata items">top-level microdata item</span>,
-  or if it has an <code title="attr-itemprop">itemprop</code>
-  attribute and would be <span title="the properties of an item">found
-  to be the property</span> of an <span
-  title="concept-item">item</span> that is itself a <span title="used
-  microdata items">used microdata item</span>.</p>
+  <p>An <span title="concept-item">item</span> is a <dfn title="used microdata items">used microdata
+  item</dfn> if it is a <span title="top-level microdata items">top-level microdata item</span>, or
+  if it has an <code title="attr-itemprop">itemprop</code> attribute and would be <span title="the
+  properties of an item">found to be the property</span> of an <span
+  title="concept-item">item</span> that is itself a <span title="used microdata items">used
+  microdata item</span>.</p>
 
-  <p>All <span title="concept-item">items</span> in a document must be
-  <span>used microdata items</span>.</p>
+  <p>All <span title="concept-item">items</span> in a document must be <span>used microdata
+  items</span>.</p>
 -->
 
-  <p>All <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attributes in a
-  <code><a href=#document>Document</a></code> must be such that there are no cycles in the
-  graph formed from representing each <a href=#concept-item title=concept-item>item</a> in the <code><a href=#document>Document</a></code> as a
-  node in the graph and each <a href=#the-properties-of-an-item title="the properties of an
-  item">property</a> of an item whose <a href=#concept-property-value title=concept-property-value>value</a> is another item as an
-  edge in the graph connecting those two items.</p>
+  <p>All <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attributes in a <code><a href=#document>Document</a></code> must be
+  such that there are no cycles in the graph formed from representing each <a href=#concept-item title=concept-item>item</a> in the <code><a href=#document>Document</a></code> as a node in the graph and each
+  <a href=#the-properties-of-an-item title="the properties of an item">property</a> of an item whose <a href=#concept-property-value title=concept-property-value>value</a> is another item as an edge in the graph connecting
+  those two items.</p>
 
   <!-- "requirement itemprop" (see above) -->
-  <p>A document must not contain any elements that have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute that would not be
-  found to be a property of any of the <a href=#concept-item title=concept-item>items</a> in that document were their <a href=#the-properties-of-an-item title="the properties of an item">properties</a> all to be
-  determined.</p>
+  <p>A document must not contain any elements that have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute that would not be found to be a property of any of
+  the <a href=#concept-item title=concept-item>items</a> in that document were their <a href=#the-properties-of-an-item title="the
+  properties of an item">properties</a> all to be determined.</p>
 
   <div class=example>
 
-   <p>In this example, a single license statement is applied to two
-   works, using <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> from the
-   items representing the works:</p>
+   <p>In this example, a single license statement is applied to two works, using <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> from the items representing the works:</p>
 
    <pre><!DOCTYPE HTML>
 <html>
@@ -64024,7 +63875,8 @@
  </body>
 </html></pre>
 
-   <p>The above results in two items with the type "<code title="">http://n.whatwg.org/work</code>", one with:</p>
+   <p>The above results in two items with the type "<code title="">http://n.whatwg.org/work</code>",
+   one with:</p>
 
    <dl class=brief><dt>work
     <dd><code title="">images/house.jpeg</code>
@@ -64047,12 +63899,9 @@
 
   <h4 id=microdata-and-other-namespaces><span class=secno>5.2.6 </span>Microdata and other namespaces</h4>
 
-  <p>Currently, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>,
-  <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>, and other microdata
-  attributes are only defined for <a href=#html-elements>HTML elements</a>. This
-  means that attributes with the literal names "<code title="">itemscope</code>", "<code title="">itemprop</code>", etc,
-  do not cause microdata processing to occur on elements in other
-  namespaces, such as SVG.</p>
+  <p>Currently, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>, <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>, and other microdata attributes are only defined for
+  <a href=#html-elements>HTML elements</a>. This means that attributes with the literal names "<code title="">itemscope</code>", "<code title="">itemprop</code>", etc, do not cause microdata
+  processing to occur on elements in other namespaces, such as SVG.</p>
 
   <div class=example>
 
@@ -64071,7 +63920,9 @@
 
    <dd>
 
-    <p>Returns a <code><a href=#nodelist>NodeList</a></code> of the elements in the <code><a href=#document>Document</a></code> that create <a href=#concept-item title=concept-item>items</a>, that are not part of other <a href=#concept-item title=concept-item>items</a>, and that are of the types given in the argument, if any are listed.</p>
+    <p>Returns a <code><a href=#nodelist>NodeList</a></code> of the elements in the <code><a href=#document>Document</a></code> that create
+    <a href=#concept-item title=concept-item>items</a>, that are not part of other <a href=#concept-item title=concept-item>items</a>, and that are of the types given in the argument, if any are
+    listed.</p>
 
     <p>The <var title="">types</var> argument is interpreted as a space-separated list of types.</p>
 
@@ -64082,9 +63933,8 @@
    <dd>
 
     <p>If the element has an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute, returns an
-    <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object with all the element's
-    properties. Otherwise, an empty
-    <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object.</p>
+    <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object with all the element's properties. Otherwise, an
+    empty <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object.</p>
 
    </dd>
 
@@ -64094,55 +63944,43 @@
 
     <p>Returns the element's <a href=#concept-property-value title=concept-property-value>value</a>.</p>
 
-    <p>Can be set, to change the element's <a href=#concept-property-value title=concept-property-value>value</a>. Setting the <a href=#concept-property-value title=concept-property-value>value</a> when the element has
-    no <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute or when
-    the element's value is an <a href=#concept-item title=concept-item>item</a>
-    throws an <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception.</p>
+    <p>Can be set, to change the element's <a href=#concept-property-value title=concept-property-value>value</a>.
+    Setting the <a href=#concept-property-value title=concept-property-value>value</a> when the element has no <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute or when the element's value is an <a href=#concept-item title=concept-item>item</a> throws an <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception.</p>
 
    </dd>
 
   </dl><div class=impl>
 
-  <p>The <dfn id=dom-document-getitems title=dom-document-getItems><code>document.getItems(<var title="">typeNames</var>)</code></dfn> method takes an optional
-  string that contains an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique
-  space-separated tokens</a> that are <a href=#case-sensitive>case-sensitive</a>,
-  representing types. When called, the method must return a
-  <a href=#live>live</a> <code><a href=#nodelist>NodeList</a></code> object containing all the
-  elements in the document, in <a href=#tree-order>tree order</a>, that are each
-  <a href=#top-level-microdata-items>top-level microdata items</a> whose <a href=#item-types title="item
-  types">types</a> include all the types specified in the method's
-  argument, having obtained the types by <a href=#split-a-string-on-spaces title="split a string
-  on spaces">splitting the string on spaces</a>. If there are no
-  tokens specified in the argument, or if the argument is missing,
-  then the method must return a <code><a href=#nodelist>NodeList</a></code> containing all
-  the <a href=#top-level-microdata-items>top-level microdata items</a> in the document. When the
-  method is invoked on a <code><a href=#document>Document</a></code> object again with the
-  same argument, the user agent may return the same object as the
-  object returned by the earlier call. In other cases, a new
+  <p>The <dfn id=dom-document-getitems title=dom-document-getItems><code>document.getItems(<var title="">typeNames</var>)</code></dfn> method takes an optional string that contains an
+  <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are <a href=#case-sensitive>case-sensitive</a>,
+  representing types. When called, the method must return a <a href=#live>live</a> <code><a href=#nodelist>NodeList</a></code>
+  object containing all the elements in the document, in <a href=#tree-order>tree order</a>, that are each
+  <a href=#top-level-microdata-items>top-level microdata items</a> whose <a href=#item-types title="item types">types</a> include all the
+  types specified in the method's argument, having obtained the types by <a href=#split-a-string-on-spaces title="split a string
+  on spaces">splitting the string on spaces</a>. If there are no tokens specified in the
+  argument, or if the argument is missing, then the method must return a <code><a href=#nodelist>NodeList</a></code>
+  containing all the <a href=#top-level-microdata-items>top-level microdata items</a> in the document. When the method is
+  invoked on a <code><a href=#document>Document</a></code> object again with the same argument, the user agent may return
+  the same object as the object returned by the earlier call. In other cases, a new
   <code><a href=#nodelist>NodeList</a></code> object must be returned.</p>
 
-  <p>The <dfn id=dom-itemscope title=dom-itemScope><code>itemScope</code></dfn> IDL
-  attribute on <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a>
-  the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> content attribute.
-  The <dfn id=dom-itemtype title=dom-itemType><code>itemType</code></dfn> IDL
-  attribute on <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a>
-  the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> content attribute.
-  The <dfn id=dom-itemid title=dom-itemId><code>itemId</code></dfn> IDL attribute
-  on <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> content attribute. The <dfn id=dom-itemprop title=dom-itemProp><code>itemProp</code></dfn> IDL attribute on
-  <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> content attribute. The <dfn id=dom-itemref title=dom-itemRef><code>itemRef</code></dfn> IDL attribute on
-  <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> content attribute.</p>
+  <p>The <dfn id=dom-itemscope title=dom-itemScope><code>itemScope</code></dfn> IDL attribute on <a href=#html-elements>HTML
+  elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
+  content attribute. The <dfn id=dom-itemtype title=dom-itemType><code>itemType</code></dfn> IDL attribute on
+  <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> content attribute. The <dfn id=dom-itemid title=dom-itemId><code>itemId</code></dfn> IDL attribute on <a href=#html-elements>HTML elements</a> must
+  <a href=#reflect>reflect</a> the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> content attribute. The <dfn id=dom-itemprop title=dom-itemProp><code>itemProp</code></dfn> IDL attribute on <a href=#html-elements>HTML elements</a> must
+  <a href=#reflect>reflect</a> the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> content attribute. The <dfn id=dom-itemref title=dom-itemRef><code>itemRef</code></dfn> IDL attribute on <a href=#html-elements>HTML elements</a> must
+  <a href=#reflect>reflect</a> the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> content attribute.</p>
 
-  <p>The <dfn id=dom-properties title=dom-properties><code>properties</code></dfn> IDL
-  attribute on <a href=#html-elements>HTML elements</a> must return an
-  <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> rooted at the
-  <code><a href=#document>Document</a></code> node, whose filter matches only elements that
-  are <a href=#the-properties-of-an-item title="the properties of an item">the properties of the
-  item</a> created by the element on which the attribute was
-  invoked, while that element is an <a href=#concept-item title=concept-item>item</a>, and matches nothing the rest of
-  the time.</p>
+  <p>The <dfn id=dom-properties title=dom-properties><code>properties</code></dfn> IDL attribute on <a href=#html-elements>HTML
+  elements</a> must return an <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> rooted at the
+  <code><a href=#document>Document</a></code> node, whose filter matches only elements that are <a href=#the-properties-of-an-item title="the
+  properties of an item">the properties of the item</a> created by the element on which the
+  attribute was invoked, while that element is an <a href=#concept-item title=concept-item>item</a>, and
+  matches nothing the rest of the time.</p>
 
-  <p>The <dfn id=dom-itemvalue title=dom-itemValue><code>itemValue</code></dfn> IDL
-  attribute's behavior depends on the element, as follows:</p>
+  <p>The <dfn id=dom-itemvalue title=dom-itemValue><code>itemValue</code></dfn> IDL attribute's behavior depends on
+  the element, as follows:</p>
 
   <dl><dt>If the element has no <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute</dt>
 
@@ -64152,68 +63990,65 @@
 
    <dt>If the element has an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute</dt>
 
-   <dd><p>The attribute must return the element itself on getting and
-   must throw an <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception on
-   setting.</p>
+   <dd><p>The attribute must return the element itself on getting and must throw an
+   <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception on setting.</p>
 
 
    <dt>If the element is a <code><a href=#the-meta-element>meta</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> content
-   attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> content attribute.</dd>
 
 
-   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>,
-   <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>,
+   <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">src</code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title="">src</code> content attribute.</dd>
 
 
-   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or
-   <code><a href=#the-link-element>link</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or <code><a href=#the-link-element>link</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">href</code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title="">href</code> content attribute.</dd>
 
 
    <dt>If the element is an <code><a href=#the-object-element>object</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">data</code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title="">data</code> content attribute.</dd>
 
 
    <dt>If the element is a <code><a href=#the-data-element>data</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> content attribute.</dd>
 
 
    <dt>If the element is a <code><a href=#the-time-element>time</a></code> element</dt>
 
-   <dd><p>On getting, if the element has a <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content attribute, the
-   IDL attribute must return that content attribute's value;
-   otherwise, it must return the element's <code><a href=#textcontent>textContent</a></code>.
-   On setting, the IDL attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content
-   attribute.</dd>
+   <dd><p>On getting, if the element has a <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content
+   attribute, the IDL attribute must return that content attribute's value; otherwise, it must
+   return the element's <code><a href=#textcontent>textContent</a></code>. On setting, the IDL attribute must act as it would
+   if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content attribute.</dd>
 
 
    <dt>Otherwise</dt>
 
-   <dd><p>The attribute must act the same as the element's
-   <code><a href=#textcontent>textContent</a></code> attribute.</dd>
+   <dd><p>The attribute must act the same as the element's <code><a href=#textcontent>textContent</a></code>
+   attribute.</dd>
 
-  </dl><p>When the <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL
-  attribute is <a href=#reflect title=reflect>reflecting</a> a content
-  attribute or acting like the element's <code><a href=#textcontent>textContent</a></code>
-  attribute, the user agent must, on setting, convert the new value to
-  the IDL <code title="">DOMString</code> value before using it
-  according to the mappings described above.</p>
+  </dl><p>When the <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL attribute is <a href=#reflect title=reflect>reflecting</a> a content attribute or acting like the element's
+  <code><a href=#textcontent>textContent</a></code> attribute, the user agent must, on setting, convert the new value to the
+  IDL <code title="">DOMString</code> value before using it according to the mappings described
+  above.</p>
 
   </div>
 
   <div class=example>
 
-   <p>In this example, a script checks to see if a particular element
-   <var title="">element</var> is declaring a particular property, and
-   if it is, it increments a counter:</p>
+   <p>In this example, a script checks to see if a particular element <var title="">element</var> is
+   declaring a particular property, and if it is, it increments a counter:</p>
 
    <pre>if (element.itemProp.contains('color'))
   count += 1;</pre>
@@ -64222,9 +64057,8 @@
 
   <div class=example>
 
-   <p>This script iterates over each of the values of an element's
-   <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, calling a
-   function for each referenced element:</p>
+   <p>This script iterates over each of the values of an element's <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, calling a function for each referenced
+   element:</p>
 
    <pre>for (var index = 0; index < element.itemRef.length; index += 1)
   process(document.getElementById(element.itemRef[index]));</pre>
@@ -64232,21 +64066,22 @@
   </div>
 
 
-  <h3 id=mdvocabs><span class=secno>5.4 </span>Microdata vocabularies</h3>
+  <h3 id=mdvocabs><span class=secno>5.4 </span>Sample microdata vocabularies</h3>
 
+  <p>The vocabularies in this section are primarily intended to demonstrate how a vocabulary is
+  specified, though they are also usable in their own right.</p>
+
+
   <h4 id=vcard><span class=secno>5.4.1 </span>vCard</h4>
 
-  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vcard title=md-vcard><code>http://microformats.org/profile/hcard</code></dfn>
-  represents a person's or organization's contact information.</p>
+  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vcard title=md-vcard><code>http://microformats.org/profile/hcard</code></dfn> represents a person's or
+  organization's contact information.</p>
 
-  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for
-  items</a>.</p>
+  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for items</a>.</p>
 
-  <p>The following are the type's <a href=#defined-property-name title="defined property
-  name">defined property names</a>. They are based on the
-  vocabulary defined in the vCard 4.0 specification and its
-  extensions, where more information on how to interpret the values
-  can be found. <a href=#refsRFC6350>[RFC6350]</a></p>
+  <p>The following are the type's <a href=#defined-property-name title="defined property name">defined property names</a>.
+  They are based on the vocabulary defined in the vCard 4.0 specification and its extensions, where
+  more information on how to interpret the values can be found. <a href=#refsRFC6350>[RFC6350]</a></p>
 
   <dl><dt><dfn id=md-vcard-kind title=md-vcard-kind><code>kind</code></dfn></dt>
 
@@ -65224,11 +65059,9 @@
    <!-- update this when http://www.iana.org/assignments/vcard-elements/vcard-elements.xml#parameter-values is updated -->
   </dl><h5 id=conversion-to-vcard><span class=secno>5.4.1.1 </span>Conversion to vCard</h5>
 
-  <p>Given a list of nodes <var title="">nodes</var> in a
-  <code><a href=#document>Document</a></code>, a user agent must run the following algorithm
-  to <dfn id=extracting-a-vcard title="extracting a vCard">extract any vCard data
-  represented by those nodes</dfn> (only the first vCard is
-  returned):</p>
+  <p>Given a list of nodes <var title="">nodes</var> in a <code><a href=#document>Document</a></code>, a user agent must
+  run the following algorithm to <dfn id=extracting-a-vcard title="extracting a vCard">extract any vCard data represented
+  by those nodes</dfn> (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 <a href=#item-types title="item
    types">item type</a> <code title=md-vcard><a href=#md-vcard>http://microformats.org/profile/hcard</a></code>, then
@@ -65535,11 +65368,8 @@
    <li><p><a href=#add-a-vcard-line>Add a vCard line</a> with the type "<code title="">END</code>" and the value "<code title="">VCARD</code>"
    to <var title="">output</var>.</li>
 
-  </ol><p>When the above algorithm says that the user agent is to <dfn id=add-a-vcard-line>add
-  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:</p>
+  </ol><p>When the above algorithm says that the user agent is to <dfn id=add-a-vcard-line>add 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:</p>
 
   <ol><li><p>Let <var title="">line</var> be an empty string.
 
@@ -65594,8 +65424,8 @@
 
    <li><p>Append a U+000A LINE FEED character (LF) to <var title="">output</var>.</li>
 
-  </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
+  </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:</p>
 
   <ol><li><p>Let <var title="">value</var> be the empty string.</li>
@@ -65621,8 +65451,8 @@
 
    <li><p>Return <var title="">value</var>.</li>
 
-  </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
+  </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:</p>
 
   <ol><li><p>If there are no properties named <var title="">subname</var>
@@ -65637,8 +65467,8 @@
    string</a> given by the <a href=#concept-property-value title=concept-property-value>value</a> of the first property
    named <var title="">subname</var> in <var title="">subitem</var>.</li>
 
-  </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
+  </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:</p>
 
   <ol><li><p>Prefix every U+005C REVERSE SOLIDUS character (\) in <var title="">value</var> with another U+005C REVERSE SOLIDUS character
@@ -65662,10 +65492,10 @@
 
    <li><p>Return the mutated <var title="">value</var>.</li>
 
-  </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>http://microformats.org/profile/hcard</a></code> <a href=#item-types title="item types">item type</a> and <a href=#defined-property-name title="defined
-  property name">defined property names</a>.</p> <!-- of course
-  since vcard doesn't define error handling, this is somewhat
+  </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>http://microformats.org/profile/hcard</a></code>
+  <a href=#item-types title="item types">item type</a> and <a href=#defined-property-name title="defined property name">defined property
+  names</a>.</p> <!-- of course since vcard doesn't define error handling, this is somewhat
   problematic. -->
 
 
@@ -65676,8 +65506,7 @@
 
   <div class=example>
 
-   <p>Here is a long example vCard for a fictional character called
-   "Jack Bauer":</p>
+   <p>Here is a long example vCard for a fictional character called "Jack Bauer":</p>
 
    <pre><section id="jack" itemscope itemtype="http://microformats.org/profile/hcard">
  <h1 itemprop="fn">
@@ -65724,17 +65553,15 @@
  </ins>
 </section></pre>
 
-   <p>The odd line wrapping is needed because newlines are meaningful
-   in microdata: newlines would be preserved in a conversion to, for
-   example, the vCard format.</p>
+   <p>The odd line wrapping is needed because newlines are meaningful in microdata: newlines would
+   be preserved in a conversion to, for example, the vCard format.</p>
 
   </div>
 
   <div class=example>
 
-   <p>This example shows a site's contact details (using the
-   <code><a href=#the-address-element>address</a></code> element) containing an address with two street
-   components:</p>
+   <p>This example shows a site's contact details (using the <code><a href=#the-address-element>address</a></code> element)
+   containing an address with two street components:</p>
 
    <pre><address itemscope itemtype="http://microformats.org/profile/hcard">
  <strong itemprop="fn"><span itemprop="n" itemscope><span itemprop="given-name">Alfred</span>
@@ -65751,20 +65578,17 @@
 
   <div class=example>
 
-   <p>The vCard vocabulary can be used to just mark up people's
-   names:</p>
+   <p>The vCard vocabulary can be used to just mark up people's names:</p>
 
    <pre><span itemscope itemtype="http://microformats.org/profile/hcard"
 ><span itemprop=fn><span itemprop="n" itemscope><span itemprop="given-name"
 >George</span> <span itemprop="family-name">Washington</span></span
 ></span></span></pre>
 
-   <p>This creates a single item with a two name-value pairs, one with
-   the name "fn" and the value "George Washington", and the other with
-   the name "n" and a second item as its value, the second item having
-   the two name-value pairs "given-name" and "family-name" with the
-   values "George" and "Washington" respectively. This is defined to
-   map to the following vCard:</p>
+   <p>This creates a single item with a two name-value pairs, one with the name "fn" and the value
+   "George Washington", and the other with the name "n" and a second item as its value, the second
+   item having the two name-value pairs "given-name" and "family-name" with the values "George" and
+   "Washington" respectively. This is defined to map to the following vCard:</p>
 
    <pre>BEGIN:VCARD
 PROFILE:VCARD
@@ -65779,20 +65603,17 @@
 
   <h4 id=vevent><span class=secno>5.4.2 </span>vEvent</h4>
 
-  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vevent title=md-vevent><code>http://microformats.org/profile/hcalendar#vevent</code></dfn>
-  represents an event.</p>
+  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vevent title=md-vevent><code>http://microformats.org/profile/hcalendar#vevent</code></dfn> represents
+  an event.</p>
 
-  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for
-  items</a>.</p>
+  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for items</a>.</p>
 
-  <p>The following are the type's <a href=#defined-property-name title="defined property
-  name">defined property names</a>. They are based on the
-  vocabulary defined in the iCalendar specification, where more
-  information on how to interpret the values can be found. <a href=#refsRFC2445>[RFC2445]</a></p>
+  <p>The following are the type's <a href=#defined-property-name title="defined property name">defined property names</a>.
+  They are based on the vocabulary defined in the iCalendar specification, where more information on
+  how to interpret the values can be found. <a href=#refsRFC2445>[RFC2445]</a></p>
 
-  <p class=note>Only the parts of the iCalendar vocabulary relating
-  to events are used here; this vocabulary cannot express a complete
-  iCalendar instance.</p>
+  <p class=note>Only the parts of the iCalendar vocabulary relating to events are used here; this
+  vocabulary cannot express a complete iCalendar instance.</p>
 
   <dl><dt><dfn id=md-vevent-attach title=md-vevent-attach><code>attach</code></dfn></dt>
 
@@ -66315,9 +66136,8 @@
 
   </ol><h5 id=conversion-to-icalendar><span class=secno>5.4.2.1 </span>Conversion to iCalendar</h5>
 
-  <p>Given a list of nodes <var title="">nodes</var> in a
-  <code><a href=#document>Document</a></code>, a user agent must run the following algorithm
-  to <dfn id=extracting-vevent-data title="extracting vEvent data">extract any vEvent data
+  <p>Given a list of nodes <var title="">nodes</var> in a <code><a href=#document>Document</a></code>, a user agent must
+  run the following algorithm to <dfn id=extracting-vevent-data title="extracting vEvent data">extract any vEvent data
   represented by those 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>http://microformats.org/profile/hcalendar#vevent</a></code>,
@@ -66407,10 +66227,9 @@
 
    <li><p><a href=#add-an-icalendar-line>Add an iCalendar line</a> with the type "<code title="">END</code>" and the value "<code title="">VCALENDAR</code>" to <var title="">output</var>.</li>
 
-  </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
-  optionally an annotation, to a string <var title="">output</var>, it
-  must run the following steps:</p>
+  </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 optionally
+  an annotation, to a string <var title="">output</var>, it must run the following steps:</p>
 
   <ol><li><p>Let <var title="">line</var> be an empty string.</li>
 
@@ -66480,13 +66299,10 @@
 
    <li><p>Append a U+000A LINE FEED character (LF) to <var title="">output</var>.</li>
 
-  </ol><p class=note>This algorithm can generate invalid iCalendar
-  output, if the input does not conform to the rules described for the
-  <code title=md-vevent><a href=#md-vevent>http://microformats.org/profile/hcalendar#vevent</a></code>
-  <a href=#item-types title="item types">item type</a> and <a href=#defined-property-name title="defined property
-  name">defined property names</a>.</p> <!-- of course since
-  iCalendar doesn't define error handling, this is somewhat
-  problematic. -->
+  </ol><p class=note>This algorithm can generate invalid iCalendar output, if the input does not
+  conform to the rules described for the <code title=md-vevent><a href=#md-vevent>http://microformats.org/profile/hcalendar#vevent</a></code> <a href=#item-types title="item
+  types">item type</a> and <a href=#defined-property-name title="defined property name">defined property names</a>.</p>
+  <!-- of course since iCalendar doesn't define error handling, this is somewhat problematic. -->
 
 
 
@@ -66498,8 +66314,7 @@
 
   <div class=example>
 
-   <p>Here is an example of a page that uses the vEvent vocabulary to
-   mark up an event:</p>
+   <p>Here is an example of a page that uses the vEvent vocabulary to mark up an event:</p>
 
    <pre><body itemscope itemtype="http://microformats.org/profile/hcalendar#vevent">
  ...
@@ -66580,13 +66395,12 @@
 
   <h4 id=licensing-works><span class=secno>5.4.3 </span>Licensing works</h4>
 
-  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-work title=md-work><code>http://n.whatwg.org/work</code></dfn>
-  represents a work (e.g. an article, an image, a video, a song,
-  etc). This type is primarily intended to allow authors to include
+  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-work title=md-work><code>http://n.whatwg.org/work</code></dfn> represents a work (e.g. an article, an
+  image, a video, a song, etc). This type is primarily intended to allow authors to include
   licensing information for works.</p>
 
-  <p>The following are the type's <a href=#defined-property-name title="defined property
-  name">defined property names</a>.</p>
+  <p>The following are the type's <a href=#defined-property-name title="defined property name">defined property
+  names</a>.</p>
 
   <dl><dt><dfn id=md-work-work title=md-work-work><code>work</code></dfn></dt>
 
@@ -66653,9 +66467,8 @@
 
   <div class=example>
 
-   <p>This example shows an embedded image entitled <cite>My
-   Pond</cite>, licensed under the Creative Commons Attribution-Share
-   Alike 3.0 United States License and the MIT license
+   <p>This example shows an embedded image entitled <cite>My Pond</cite>, licensed under the
+   Creative Commons Attribution-Share Alike 3.0 United States License and the MIT license
    simultaneously.</p>
 
    <pre><figure <strong>itemscope itemtype="http://n.whatwg.org/work"</strong>>
@@ -66680,10 +66493,9 @@
 
   <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><a href=#document>Document</a></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>:</p>
+  <p>Given a list of nodes <var title="">nodes</var> in a <code><a href=#document>Document</a></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>:</p>
 
   <ol><li><p>Let <var title="">result</var> be an empty object.</li>
 
@@ -66702,13 +66514,13 @@
    dedicated escape sequence), and with a lowercase "<code title="">e</code>" used, when appropriate, in the representation of
    any numbers. <a href=#refsJSON>[JSON]</a></li>
 
-  </ol><p class=note>This algorithm returns an object with a single
-  property that is an array, instead of just returning an array, so
-  that it is possible to extend the algorithm in the future if
+  </ol><p class=note>This algorithm returns an object with a single property that is an array, instead
+  of just returning an array, so that it is possible to extend the algorithm in the future if
   necessary.</p>
 
-  <p>When the user agent is to <dfn id=get-the-object>get the object</dfn> for an item
-  <var title="">item</var>, optionally with a list of elements <var title="">memory</var>, it must run the following substeps:</p>
+  <p>When the user agent is to <dfn id=get-the-object>get the object</dfn> for an item <var title="">item</var>,
+  optionally with a list of elements <var title="">memory</var>, it must run the following
+  substeps:</p>
 
   <ol><li><p>Let <var title="">result</var> be an empty object.</li>
 
@@ -66765,14 +66577,17 @@
   </ol></div>
 
 
+
+
+<!--TOPIC:HTML-->
+
   <h2 id=browsers><span class=secno>6 </span>Loading Web pages</h2>
 
   <div class=impl>
 
-  <p>This section describes features that apply most directly to Web
-  browsers. Having said that, except where specified otherwise, the
-  requirements defined in this section <em>do</em> apply to all user
-  agents, whether they are Web browsers or not.</p>
+  <p>This section describes features that apply most directly to Web browsers. Having said that,
+  except where specified otherwise, the requirements defined in this section <em>do</em> apply to
+  all user agents, whether they are Web browsers or not.</p>
 
   </div>
 
@@ -66780,65 +66595,51 @@
 
   <h3 id=windows><span class=secno>6.1 </span>Browsing contexts</h3>
 
-  <p>A <dfn id=browsing-context>browsing context</dfn> is an environment in which
-  <code><a href=#document>Document</a></code> objects are presented to the user.</p>
+  <p>A <dfn id=browsing-context>browsing context</dfn> is an environment in which <code><a href=#document>Document</a></code> objects are
+  presented to the user.</p>
 
-  <p class=note>A tab or window in a Web browser typically contains
-  a <a href=#browsing-context>browsing context</a>, as does an <code><a href=#the-iframe-element>iframe</a></code><span class=impl> or <code><a href=#frame>frame</a></code>s in a
+  <p class=note>A tab or window in a Web browser typically contains a <a href=#browsing-context>browsing
+  context</a>, as does an <code><a href=#the-iframe-element>iframe</a></code><span class=impl> or <code><a href=#frame>frame</a></code>s in a
   <code><a href=#frameset>frameset</a></code></span>.</p>
 
-  <p>Each <a href=#browsing-context>browsing context</a> has a corresponding
-  <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+  <p>Each <a href=#browsing-context>browsing context</a> has a corresponding <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
 
-  <p>A <a href=#browsing-context>browsing context</a> has a <a href=#session-history>session
-  history</a>, which lists the <code><a href=#document>Document</a></code> objects that
-  that <a href=#browsing-context>browsing context</a> has presented, is presenting, or
-  will present. At any time, one <code><a href=#document>Document</a></code> in each
-  <a href=#browsing-context>browsing context</a> is designated the <dfn id=active-document>active
-  document</dfn>. A <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing
-  context</a> is that <a href=#browsing-context>browsing context</a> whose
-  <a href=#session-history>session history</a> contains the <code><a href=#document>Document</a></code>, if
-  any. (A <code><a href=#document>Document</a></code> created using an API such as <code title=dom-DOMImplementation-createDocument><a href=#dom-domimplementation-createdocument>createDocument()</a></code>
-  has no <a href=#browsing-context>browsing context</a>.)</p>
+  <p>A <a href=#browsing-context>browsing context</a> has a <a href=#session-history>session history</a>, which lists the
+  <code><a href=#document>Document</a></code> objects that that <a href=#browsing-context>browsing context</a> has presented, is
+  presenting, or will present. At any time, one <code><a href=#document>Document</a></code> in each <a href=#browsing-context>browsing
+  context</a> is designated the <dfn id=active-document>active document</dfn>. A <code><a href=#document>Document</a></code>'s
+  <a href=#browsing-context>browsing context</a> is that <a href=#browsing-context>browsing context</a> whose <a href=#session-history>session
+  history</a> contains the <code><a href=#document>Document</a></code>, if any. (A <code><a href=#document>Document</a></code> created using
+  an API such as <code title=dom-DOMImplementation-createDocument><a href=#dom-domimplementation-createdocument>createDocument()</a></code> has no
+  <a href=#browsing-context>browsing context</a>.)</p>
 
-  <p>Each <code><a href=#document>Document</a></code> is associated with a
-  <code><a href=#window>Window</a></code> object. A <a href=#browsing-context>browsing context</a>'s
-  <code><a href=#windowproxy>WindowProxy</a></code> object forwards everything to the
-  <a href=#browsing-context>browsing context</a>'s <a href=#active-document>active document</a>'s
-  <code><a href=#window>Window</a></code> object.</p>
+  <p>Each <code><a href=#document>Document</a></code> is associated with a <code><a href=#window>Window</a></code> object. A <a href=#browsing-context>browsing
+  context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object forwards everything to the <a href=#browsing-context>browsing
+  context</a>'s <a href=#active-document>active document</a>'s <code><a href=#window>Window</a></code> object.</p>
 
-  <p class=note>In general, there is a 1-to-1 mapping from the
-  <code><a href=#window>Window</a></code> object to the <code><a href=#document>Document</a></code> object.
-  There are two exceptions. First, a <code><a href=#window>Window</a></code> can be reused
-  for the presentation of a second <code><a href=#document>Document</a></code> in the same
-  <a href=#browsing-context>browsing context</a>, such that the mapping is then 1-to-2.
-  This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial
-  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> to another, with
-  <a href=#replacement-enabled>replacement enabled</a>. Second, a <code><a href=#document>Document</a></code>
-  can end up being reused for several <code><a href=#window>Window</a></code> objects when
-  the <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> method is
-  used, such that the mapping is then many-to-1.</p>
+  <p class=note>In general, there is a 1-to-1 mapping from the <code><a href=#window>Window</a></code> object to the
+  <code><a href=#document>Document</a></code> object. There are two exceptions. First, a <code><a href=#window>Window</a></code> can be reused
+  for the presentation of a second <code><a href=#document>Document</a></code> in the same <a href=#browsing-context>browsing context</a>,
+  such that the mapping is then 1-to-2. This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code>
+  to another, with <a href=#replacement-enabled>replacement enabled</a>. Second, a <code><a href=#document>Document</a></code> can end up
+  being reused for several <code><a href=#window>Window</a></code> objects when the <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> method is used, such that the mapping is then
+  many-to-1.</p>
 
-  <p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a
-  <a href=#browsing-context>browsing context</a> associated with it. In particular,
-  data mining tools are likely to never instantiate browsing
+  <p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a <a href=#browsing-context>browsing context</a>
+  associated with it. In particular, data mining tools are likely to never instantiate browsing
   contexts.</p>
 
-  <hr><p>A <a href=#browsing-context>browsing context</a> can have a <dfn id=creator-browsing-context>creator browsing
-  context</dfn>, the <a href=#browsing-context>browsing context</a> that was
-  responsible for its creation. If a <a href=#browsing-context>browsing context</a> has
-  a <a href=#parent-browsing-context>parent browsing context</a>, then that is its
-  <a href=#creator-browsing-context>creator browsing context</a>. Otherwise, if the
-  <a href=#browsing-context>browsing context</a> has an <a href=#opener-browsing-context>opener browsing
-  context</a>, then <em>that</em> is its <a href=#creator-browsing-context>creator browsing
-  context</a>. Otherwise, the <a href=#browsing-context>browsing context</a> has no
-  <a href=#creator-browsing-context>creator browsing context</a>.</p>
+  <hr><p>A <a href=#browsing-context>browsing context</a> can have a <dfn id=creator-browsing-context>creator browsing context</dfn>, the
+  <a href=#browsing-context>browsing context</a> that was responsible for its creation. If a <a href=#browsing-context>browsing
+  context</a> has a <a href=#parent-browsing-context>parent browsing context</a>, then that is its <a href=#creator-browsing-context>creator browsing
+  context</a>. Otherwise, if the <a href=#browsing-context>browsing context</a> has an <a href=#opener-browsing-context>opener browsing
+  context</a>, then <em>that</em> is its <a href=#creator-browsing-context>creator browsing context</a>. Otherwise, the
+  <a href=#browsing-context>browsing context</a> has no <a href=#creator-browsing-context>creator browsing context</a>.</p>
 
-  <p>If a <a href=#browsing-context>browsing context</a> <var title="">A</var> has a
-  <a href=#creator-browsing-context>creator browsing context</a>, then the
-  <code><a href=#document>Document</a></code> that was the <a href=#active-document>active document</a> of
-  that <a href=#creator-browsing-context>creator browsing context</a> at the time <var title="">A</var> was created is the <dfn id=creator-document>creator
-  <code>Document</code></dfn>.</p>
+  <p>If a <a href=#browsing-context>browsing context</a> <var title="">A</var> has a <a href=#creator-browsing-context>creator browsing
+  context</a>, then the <code><a href=#document>Document</a></code> that was the <a href=#active-document>active document</a> of that
+  <a href=#creator-browsing-context>creator browsing context</a> at the time <var title="">A</var> was created is the
+  <dfn id=creator-document>creator <code>Document</code></dfn>.</p>
 
   <div class=impl>
 
@@ -66852,147 +66653,110 @@
   <code><a href=#document>Document</a></code> is created, the user agent must <a href=#implement-the-sandboxing>implement the sandboxing</a> for
   it.</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 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>origin</a> and
-  <a href=#effective-script-origin>effective script origin</a> of the <code><a href=#about:blank>about:blank</a></code>
-  <code><a href=#document>Document</a></code> are set when the <code><a href=#document>Document</a></code> is
-  created. If the new <a href=#browsing-context>browsing context</a> has a
-  <a href=#creator-browsing-context>creator browsing context</a>, then the <a href=#origin>origin</a>
-  of the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#origin>origin</a>
-  of the <a href=#creator-document>creator <code>Document</code></a> and the
-  <a href=#effective-script-origin>effective script origin</a> of the <code><a href=#about:blank>about:blank</a></code>
-  <code><a href=#document>Document</a></code> is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#effective-script-origin>effective
-  script origin</a> of the <a href=#creator-document>creator
-  <code>Document</code></a>. Otherwise, the <a href=#origin>origin</a> of
-  the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is a globally
-  unique identifier assigned when the new <a href=#browsing-context>browsing
-  context</a> is created and the <a href=#effective-script-origin>effective script
-  origin</a> of the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code>
-  is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to
-  its <a href=#origin>origin</a>.</p>
+  <p id=about-blank-origin>The <a href=#origin>origin</a> and <a href=#effective-script-origin>effective script origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> are set when the <code><a href=#document>Document</a></code> is created.
+  If the new <a href=#browsing-context>browsing context</a> has a <a href=#creator-browsing-context>creator browsing context</a>, then the
+  <a href=#origin>origin</a> of the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#origin>origin</a> of the <a href=#creator-document>creator
+  <code>Document</code></a> and the <a href=#effective-script-origin>effective script origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#effective-script-origin>effective script origin</a> of the
+  <a href=#creator-document>creator <code>Document</code></a>. Otherwise, the <a href=#origin>origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is a globally unique identifier assigned when the
+  new <a href=#browsing-context>browsing context</a> is created and the <a href=#effective-script-origin>effective script origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to its <a href=#origin>origin</a>.</p>
 
   </div>
 
 
   <h4 id=nested-browsing-contexts><span class=secno>6.1.1 </span>Nested browsing contexts</h4>
 
-  <p>Certain elements (for example, <code><a href=#the-iframe-element>iframe</a></code> elements) can
-  instantiate further <a href=#browsing-context title="browsing context">browsing
-  contexts</a>. These are called <dfn id=nested-browsing-context title="nested browsing
-  context">nested browsing contexts</dfn>. If a browsing context <var title="">P</var> has a <code><a href=#document>Document</a></code> <var title="">D</var>
-  with an element <var title="">E</var> that nests another browsing
-  context <var title="">C</var> inside it, then <var title="">C</var>
-  is said to be <dfn id=browsing-context-nested-through title="browsing context nested through">nested
-  through</dfn> <var title="">D</var>, and <var title="">E</var> is
-  said to be the <dfn id=browsing-context-container>browsing context container</dfn> of <var title="">C</var>. If the <a href=#browsing-context-container>browsing context container</a>
-  element <var title="">E</var> is <a href=#in-a-document title="in a
-  Document">in</a> the <code><a href=#document>Document</a></code> <var title="">D</var>,
-  then <var title="">P</var> is said to be the <dfn id=parent-browsing-context>parent browsing
-  context</dfn> of <var title="">C</var> and <var title="">C</var> is
-  said to be a <dfn id=child-browsing-context>child browsing context</dfn> of <var title="">P</var>. Otherwise, the <a href=#nested-browsing-context>nested browsing
-  context</a> <var title="">C</var> has no <a href=#parent-browsing-context>parent browsing
-  context</a>.</p>
+  <p>Certain elements (for example, <code><a href=#the-iframe-element>iframe</a></code> elements) can instantiate further <a href=#browsing-context title="browsing context">browsing contexts</a>. These are called <dfn id=nested-browsing-context title="nested browsing
+  context">nested browsing contexts</dfn>. If a browsing context <var title="">P</var> has a
+  <code><a href=#document>Document</a></code> <var title="">D</var> with an element <var title="">E</var> that nests
+  another browsing context <var title="">C</var> inside it, then <var title="">C</var> is said to be
+  <dfn id=browsing-context-nested-through title="browsing context nested through">nested through</dfn> <var title="">D</var>, and <var title="">E</var> is said to be the <dfn id=browsing-context-container>browsing context container</dfn> of <var title="">C</var>.
+  If the <a href=#browsing-context-container>browsing context container</a> element <var title="">E</var> is <a href=#in-a-document title="in a
+  Document">in</a> the <code><a href=#document>Document</a></code> <var title="">D</var>, then <var title="">P</var> is
+  said to be the <dfn id=parent-browsing-context>parent browsing context</dfn> of <var title="">C</var> and <var title="">C</var> is said to be a <dfn id=child-browsing-context>child browsing context</dfn> of <var title="">P</var>.
+  Otherwise, the <a href=#nested-browsing-context>nested browsing context</a> <var title="">C</var> has no <a href=#parent-browsing-context>parent
+  browsing context</a>.</p>
 
-  <p>A browsing context <var title="">A</var> is said to be an <dfn id=ancestor-browsing-context title="ancestor browsing context">ancestor</dfn> of a browsing
-  context <var title="">B</var> if there exists a browsing context
-  <var title="">A'</var> that is a <a href=#child-browsing-context>child browsing context</a>
-  of <var title="">A</var> and that is itself an <a href=#ancestor-browsing-context title="ancestor
-  browsing context">ancestor</a> of <var title="">B</var>, or if
-  there is a browsing context <var title="">P</var> that is a
-  <a href=#child-browsing-context>child browsing context</a> of <var title="">A</var> and
-  that is the <a href=#parent-browsing-context>parent browsing context</a> of <var title="">B</var>.</p>
+  <p>A browsing context <var title="">A</var> is said to be an <dfn id=ancestor-browsing-context title="ancestor browsing
+  context">ancestor</dfn> of a browsing context <var title="">B</var> if there exists a browsing
+  context <var title="">A'</var> that is a <a href=#child-browsing-context>child browsing context</a> of <var title="">A</var> and that is itself an <a href=#ancestor-browsing-context title="ancestor browsing context">ancestor</a> of
+  <var title="">B</var>, or if there is a browsing context <var title="">P</var> that is a
+  <a href=#child-browsing-context>child browsing context</a> of <var title="">A</var> and that is the <a href=#parent-browsing-context>parent browsing
+  context</a> of <var title="">B</var>.</p>
 
-  <p>A browsing context that is not a <a href=#nested-browsing-context>nested browsing
-  context</a> has no <a href=#parent-browsing-context>parent browsing context</a>, and is
-  the <dfn id=top-level-browsing-context>top-level browsing context</dfn> of all the browsing
-  contexts for which it is an <a href=#ancestor-browsing-context>ancestor browsing
-  context</a>.</p>
+  <p>A browsing context that is not a <a href=#nested-browsing-context>nested browsing context</a> has no <a href=#parent-browsing-context>parent
+  browsing context</a>, and is the <dfn id=top-level-browsing-context>top-level browsing context</dfn> of all the browsing
+  contexts for which it is an <a href=#ancestor-browsing-context>ancestor browsing context</a>.</p>
 
-  <p>The transitive closure of <a href=#parent-browsing-context title="parent browsing
-  context">parent browsing contexts</a> for a <a href=#nested-browsing-context>nested browsing
-  context</a> gives the list of <a href=#ancestor-browsing-context title="ancestor browsing
+  <p>The transitive closure of <a href=#parent-browsing-context title="parent browsing context">parent browsing contexts</a>
+  for a <a href=#nested-browsing-context>nested browsing context</a> gives the list of <a href=#ancestor-browsing-context title="ancestor browsing
   context">ancestor browsing contexts</a>.</p>
 
-  <p>The <dfn id=list-of-the-descendant-browsing-contexts>list of the descendant browsing contexts</dfn> of a
-  <code><a href=#document>Document</a></code> <var title="">d</var> is the (ordered) list
-  returned by the following algorithm:</p>
+  <p>The <dfn id=list-of-the-descendant-browsing-contexts>list of the descendant browsing contexts</dfn> of a <code><a href=#document>Document</a></code> <var title="">d</var> is the (ordered) list returned by the following algorithm:</p>
 
   <ol><li><p>Let <var title="">list</var> be an empty list.</li>
 
    <li>
 
-    <p>For each <a href=#child-browsing-context>child browsing context</a> of <var title="">d</var> that is <a href=#browsing-context-nested-through title="browsing context nested
-    through">nested through</a> an element that is <a href=#in-a-document title="in
-    a document">in the <code>Document</code></a> <var title="">d</var>, in the <a href=#tree-order>tree order</a> of the elements
-    nesting those <a href=#browsing-context title="browsing context">browsing
+    <p>For each <a href=#child-browsing-context>child browsing context</a> of <var title="">d</var> that is <a href=#browsing-context-nested-through title="browsing context nested through">nested through</a> an element that is <a href=#in-a-document title="in
+    a document">in the <code>Document</code></a> <var title="">d</var>, in the <a href=#tree-order>tree
+    order</a> of the elements nesting those <a href=#browsing-context title="browsing context">browsing
     contexts</a>, run these substeps:</p>
 
-    <ol><li><p>Append that <a href=#child-browsing-context>child browsing context</a> to the
-     list <var title="">list</var>.</p>
+    <ol><li><p>Append that <a href=#child-browsing-context>child browsing context</a> to the list <var title="">list</var>.</p>
 
-     <li><p>Append the <a href=#list-of-the-descendant-browsing-contexts>list of the descendant browsing
-     contexts</a> of the <a href=#active-document>active document</a> of that
-     <a href=#child-browsing-context>child browsing context</a> to the list <var title="">list</var>.</li>
+     <li><p>Append the <a href=#list-of-the-descendant-browsing-contexts>list of the descendant browsing contexts</a> of the <a href=#active-document>active
+     document</a> of that <a href=#child-browsing-context>child browsing context</a> to the list <var title="">list</var>.</li>
 
     </ol></li>
 
    <li><p>Return the constructed <var title="">list</var>.</li>
 
-  </ol><p>A <code><a href=#document>Document</a></code> is said to be <dfn id=fully-active>fully active</dfn>
-  when it is the <a href=#active-document>active document</a> of its <a href=#browsing-context>browsing
-  context</a>, and either its browsing context is a <a href=#top-level-browsing-context>top-level
-  browsing context</a>, or it has a <a href=#parent-browsing-context>parent browsing
-  context</a> and the <code><a href=#document>Document</a></code> <a href=#browsing-context-nested-through title="browsing
-  context nested through">through which</a> it is <a href=#nested-browsing-context title="nested browsing context">nested</a> is itself <a href=#fully-active>fully
-  active</a>.</p>
+  </ol><p>A <code><a href=#document>Document</a></code> is said to be <dfn id=fully-active>fully active</dfn> when it is the <a href=#active-document>active
+  document</a> of its <a href=#browsing-context>browsing context</a>, and either its browsing context is a
+  <a href=#top-level-browsing-context>top-level browsing context</a>, or it has a <a href=#parent-browsing-context>parent browsing context</a> and the
+  <code><a href=#document>Document</a></code> <a href=#browsing-context-nested-through title="browsing context nested through">through which</a> it is
+  <a href=#nested-browsing-context title="nested browsing context">nested</a> is itself <a href=#fully-active>fully active</a>.</p>
 
-  <p>Because they are nested through an element, <a href=#child-browsing-context title="child
-  browsing context">child browsing contexts</a> are always tied to
-  a specific <code><a href=#document>Document</a></code> in their <a href=#parent-browsing-context>parent browsing
-  context</a>. User agents must not allow the user to interact with
-  <a href=#child-browsing-context title="child browsing context">child browsing contexts</a>
-  of elements that are in <code><a href=#document>Document</a></code>s that are not
-  themselves <a href=#fully-active>fully active</a>.</p>
+  <p>Because they are nested through an element, <a href=#child-browsing-context title="child browsing context">child browsing
+  contexts</a> are always tied to a specific <code><a href=#document>Document</a></code> in their <a href=#parent-browsing-context>parent browsing
+  context</a>. User agents must not allow the user to interact with <a href=#child-browsing-context title="child browsing
+  context">child browsing contexts</a> of elements that are in <code><a href=#document>Document</a></code>s that are
+  not themselves <a href=#fully-active>fully active</a>.</p>
 
-  <p>A <a href=#nested-browsing-context>nested browsing context</a> can have a <a href=#seamless-browsing-context-flag>seamless
-  browsing context flag</a> set, if it is embedded through an
-  <code><a href=#the-iframe-element>iframe</a></code> element with a <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute.</p>
+  <p>A <a href=#nested-browsing-context>nested browsing context</a> can have a <a href=#seamless-browsing-context-flag>seamless browsing context flag</a>
+  set, if it is embedded through an <code><a href=#the-iframe-element>iframe</a></code> element with a <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute.</p>
 
   <p>A <a href=#nested-browsing-context>nested browsing context</a> can be put into a <dfn id=delaying-load-events-mode>delaying <code title=event-load>load</code> events mode</dfn>. This is used when it is <a href=#navigate title=navigate>navigated</a>, to <a href=#delay-the-load-event>delay the load event</a> of the <a href=#browsing-context-container>browsing
   context container</a> <code><a href=#the-iframe-element>iframe</a></code> element before the new <code><a href=#document>Document</a></code> is
   created.</p>
 
 <!--(There's no current way for this to happen, since removing an iframe from a document discards its browsing context)
-  <p class="note">A <span>nested browsing context</span> can in some
-  cases be taken out of its <span>parent browsing context</span> (e.g.
-  if an <code>iframe</code> element is removed from its
-  <code>Document</code>). In such a situation, the <span>nested
-  browsing context</span> has no <span>parent browsing context</span>,
-  but it still has the same <span>browsing context container</span>
-  and is still <span title="browsing context nested through">nested
-  through</span> that element's <code>Document</code>. Such a
-  <span>nested browsing context</span> is <em>not</em> a
-  <span>top-level browsing context</span>, and cannot contain
-  <code>Document</code>s that are <span>fully active</span>.
-  Furthermore, if a <span>browsing context container</span> (such as
-  an <code>iframe</code>) is moved to another <code>Document</code>,
-  then the <span>parent browsing context</span> of its <span>nested
-  browsing context</span> will change.</p>
+  <p class="note">A <span>nested browsing context</span> can in some cases be taken out of its
+  <span>parent browsing context</span> (e.g. if an <code>iframe</code> element is removed from its
+  <code>Document</code>). In such a situation, the <span>nested browsing context</span> has no
+  <span>parent browsing context</span>, but it still has the same <span>browsing context
+  container</span> and is still <span title="browsing context nested through">nested through</span>
+  that element's <code>Document</code>. Such a <span>nested browsing context</span> is <em>not</em>
+  a <span>top-level browsing context</span>, and cannot contain <code>Document</code>s that are
+  <span>fully active</span>. Furthermore, if a <span>browsing context container</span> (such as an
+  <code>iframe</code>) is moved to another <code>Document</code>, then the <span>parent browsing
+  context</span> of its <span>nested browsing context</span> will change.</p>
 -->
 
-  <p>The <dfn id=document-family>document family</dfn> of a <a href=#browsing-context>browsing context</a>
-  consists of the union of all the <code><a href=#document>Document</a></code> objects in
-  that <a href=#browsing-context>browsing context</a>'s <a href=#session-history>session history</a>
-  and the <a href=#document-family title="document family">document families</a> of
-  all those <code><a href=#document>Document</a></code> objects. The <a href=#document-family>document
-  family</a> of a <code><a href=#document>Document</a></code> object consists of the
-  union of all the <a href=#document-family title="document family">document
-  families</a> of the <a href=#browsing-context title="browsing context">browsing
-  contexts</a> that are <a href=#browsing-context-nested-through title="browsing context nested
-  through">nested through</a> the <code><a href=#document>Document</a></code> object.</p>
+  <p>The <dfn id=document-family>document family</dfn> of a <a href=#browsing-context>browsing context</a> consists of the union of all
+  the <code><a href=#document>Document</a></code> objects in that <a href=#browsing-context>browsing context</a>'s <a href=#session-history>session
+  history</a> and the <a href=#document-family title="document family">document families</a> of all those
+  <code><a href=#document>Document</a></code> objects. The <a href=#document-family>document family</a> of a <code><a href=#document>Document</a></code> object
+  consists of the union of all the <a href=#document-family title="document family">document families</a> of the
+  <a href=#browsing-context title="browsing context">browsing contexts</a> that are <a href=#browsing-context-nested-through title="browsing context
+  nested through">nested through</a> the <code><a href=#document>Document</a></code> object.</p>
 
 
   <h5 id=navigating-nested-browsing-contexts-in-the-dom><span class=secno>6.1.1.1 </span>Navigating nested browsing contexts in the DOM</h5>
@@ -67027,43 +66791,33 @@
 
   </dl><div class=impl>
 
-  <p>The <dfn id=dom-top title=dom-top><code>top</code></dfn> IDL attribute on
-  the <code><a href=#window>Window</a></code> object of a <code><a href=#document>Document</a></code> in a
-  <a href=#browsing-context>browsing context</a> <var title="">b</var> must return the
-  <code><a href=#windowproxy>WindowProxy</a></code> object of its <a href=#top-level-browsing-context>top-level browsing
-  context</a> (which would be its own <code><a href=#windowproxy>WindowProxy</a></code>
-  object if it was a <a href=#top-level-browsing-context>top-level browsing context</a> itself),
-  if it has one, or its own <code><a href=#windowproxy>WindowProxy</a></code> object otherwise
-  (e.g. if it was a detached <a href=#nested-browsing-context>nested browsing
-  context</a>).</p>
+  <p>The <dfn id=dom-top title=dom-top><code>top</code></dfn> IDL attribute on the <code><a href=#window>Window</a></code> object
+  of a <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> <var title="">b</var> must return
+  the <code><a href=#windowproxy>WindowProxy</a></code> object of its <a href=#top-level-browsing-context>top-level browsing context</a> (which would be
+  its own <code><a href=#windowproxy>WindowProxy</a></code> object if it was a <a href=#top-level-browsing-context>top-level browsing context</a>
+  itself), if it has one, or its own <code><a href=#windowproxy>WindowProxy</a></code> object otherwise (e.g. if it was a
+  detached <a href=#nested-browsing-context>nested browsing context</a>).</p>
 
-  <p>The <dfn id=dom-parent title=dom-parent><code>parent</code></dfn> IDL
-  attribute on the <code><a href=#window>Window</a></code> object of a
-  <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> <var title="">b</var> must return the <code><a href=#windowproxy>WindowProxy</a></code> object of
-  the <a href=#parent-browsing-context>parent browsing context</a>, if there is one (i.e. if
-  <var title="">b</var> is a <a href=#child-browsing-context>child browsing context</a>), or
-  the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
-  context</a> <var title="">b</var> itself, otherwise (i.e. if it
-  is a <a href=#top-level-browsing-context>top-level browsing context</a> or a detached
-  <a href=#nested-browsing-context>nested browsing context</a>).</p>
+  <p>The <dfn id=dom-parent title=dom-parent><code>parent</code></dfn> IDL attribute on the <code><a href=#window>Window</a></code>
+  object of a <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> <var title="">b</var> must
+  return the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#parent-browsing-context>parent browsing context</a>, if there
+  is one (i.e. if <var title="">b</var> is a <a href=#child-browsing-context>child browsing context</a>), or the
+  <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing context</a> <var title="">b</var> itself,
+  otherwise (i.e. if it is a <a href=#top-level-browsing-context>top-level browsing context</a> or a detached <a href=#nested-browsing-context>nested
+  browsing context</a>).</p>
 
-  <p>The <dfn id=dom-frameelement title=dom-frameElement><code>frameElement</code></dfn>
-  IDL attribute on the <code><a href=#window>Window</a></code> object of a
-  <code><a href=#document>Document</a></code> <var title="">d</var>, on getting, must run
+  <p>The <dfn id=dom-frameelement title=dom-frameElement><code>frameElement</code></dfn> IDL attribute on the
+  <code><a href=#window>Window</a></code> object of a <code><a href=#document>Document</a></code> <var title="">d</var>, on getting, must run
   the following algorithm:</p>
 
-  <ol><li><p>If <var title="">d</var> is not a <code><a href=#document>Document</a></code> in a
-   <a href=#nested-browsing-context>nested browsing context</a>, return null and abort these
-   steps.</li>
+  <ol><li><p>If <var title="">d</var> is not a <code><a href=#document>Document</a></code> in a <a href=#nested-browsing-context>nested browsing
+   context</a>, return null and abort these steps.</li>
 
-   <li><p>If the <a href=#browsing-context-container>browsing context container</a>'s
-   <code><a href=#document>Document</a></code> does not have the <a href=#same-origin title="same
-   origin">same</a> <a href=#effective-script-origin>effective script origin</a> as the
-   <a href=#entry-script>entry script</a>, then throw a <code><a href=#securityerror>SecurityError</a></code>
-   exception.</li>
+   <li><p>If the <a href=#browsing-context-container>browsing context container</a>'s <code><a href=#document>Document</a></code> does not have the
+   <a href=#same-origin title="same origin">same</a> <a href=#effective-script-origin>effective script origin</a> as the <a href=#entry-script>entry
+   script</a>, then throw a <code><a href=#securityerror>SecurityError</a></code> exception.</li>
 
-   <li><p>Otherwise, return the <a href=#browsing-context-container>browsing context
-   container</a> for <var title="">b</var>.</li>
+   <li><p>Otherwise, return the <a href=#browsing-context-container>browsing context container</a> for <var title="">b</var>.</li>
 
   </ol></div>
 
@@ -67071,31 +66825,24 @@
 
   <h4 id=auxiliary-browsing-contexts><span class=secno>6.1.2 </span>Auxiliary browsing contexts</h4>
 
-  <p>It is possible to create new browsing contexts that are related
-  to a <a href=#top-level-browsing-context>top-level browsing context</a> without being nested
-  through an element. Such browsing contexts are called <dfn id=auxiliary-browsing-context title="auxiliary browsing context">auxiliary browsing
-  contexts</dfn>. Auxiliary browsing contexts are always <a href=#top-level-browsing-context title="top-level browsing context">top-level browsing
-  contexts</a>.</p>
+  <p>It is possible to create new browsing contexts that are related to a <a href=#top-level-browsing-context>top-level browsing
+  context</a> without being nested through an element. Such browsing contexts are called <dfn id=auxiliary-browsing-context title="auxiliary browsing context">auxiliary browsing contexts</dfn>. Auxiliary browsing contexts
+  are always <a href=#top-level-browsing-context title="top-level browsing context">top-level browsing contexts</a>.</p>
 
-  <p>An <a href=#auxiliary-browsing-context>auxiliary browsing context</a> has an <dfn id=opener-browsing-context>opener
-  browsing context</dfn>, which is the <a href=#browsing-context>browsing context</a>
-  from which the <a href=#auxiliary-browsing-context>auxiliary browsing context</a> was
+  <p>An <a href=#auxiliary-browsing-context>auxiliary browsing context</a> has an <dfn id=opener-browsing-context>opener browsing context</dfn>, which is
+  the <a href=#browsing-context>browsing context</a> from which the <a href=#auxiliary-browsing-context>auxiliary browsing context</a> was
   created.</p>
 
 
   <h5 id=navigating-auxiliary-browsing-contexts-in-the-dom><span class=secno>6.1.2.1 </span>Navigating auxiliary browsing contexts in the DOM</h5>
 
-  <p>The <dfn id=dom-opener title=dom-opener><code>opener</code></dfn> IDL
-  attribute on the <code><a href=#window>Window</a></code> object, on getting, must return
-  the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
-  context</a> from which the current <a href=#browsing-context>browsing context</a>
-  was created (its <a href=#opener-browsing-context>opener browsing context</a>), if there is
-  one, if it is still available, and if the current <a href=#browsing-context>browsing
-  context</a> has not <i><a href=#disowned-its-opener>disowned its opener</a></i>; otherwise, it
-  must return null. On setting, if the new value is null then the
-  current <a href=#browsing-context>browsing context</a> must <dfn id=disowned-its-opener title="disowned its
-  opener">disown its opener</dfn>; if the new value is anything else
-  then the user agent must ignore the new value.</p>
+  <p>The <dfn id=dom-opener title=dom-opener><code>opener</code></dfn> IDL attribute on the <code><a href=#window>Window</a></code>
+  object, on getting, must return the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
+  context</a> from which the current <a href=#browsing-context>browsing context</a> was created (its <a href=#opener-browsing-context>opener
+  browsing context</a>), if there is one, if it is still available, and if the current
+  <a href=#browsing-context>browsing context</a> has not <i><a href=#disowned-its-opener>disowned its opener</a></i>; otherwise, it must return null.
+  On setting, if the new value is null then the current <a href=#browsing-context>browsing context</a> must <dfn id=disowned-its-opener title="disowned its opener">disown its opener</dfn>; if the new value is anything else then the
+  user agent must ignore the new value.</p>
 
 
 
@@ -67106,9 +66853,9 @@
      http://www.w3.org/Bugs/Public/show_bug.cgi?id=11183
   and then moved to the wiki -->
 
-  <p>User agents may support <dfn id=secondary-browsing-context title="secondary browsing
-  context">secondary browsing contexts</dfn>, which are <a href=#browsing-context title="browsing context">browsing contexts</a> that form part of
-  the user agent's interface, apart from the main content area.</p>
+  <p>User agents may support <dfn id=secondary-browsing-context title="secondary browsing context">secondary browsing
+  contexts</dfn>, which are <a href=#browsing-context title="browsing context">browsing contexts</a> that form part
+  of the user agent's interface, apart from the main content area.</p>
 
 
 <!--ADD-TOPIC:Security-->
@@ -67116,42 +66863,33 @@
 
   <h4 id=security-nav><span class=secno>6.1.4 </span>Security</h4>
 
-  <p id=security-1>A <a href=#browsing-context>browsing context</a> <var title="">A</var> is <dfn id=allowed-to-navigate>allowed to navigate</dfn> a second
-  <a href=#browsing-context>browsing context</a> <var title="">B</var> if one of the
+  <p id=security-1>A <a href=#browsing-context>browsing context</a> <var title="">A</var> is <dfn id=allowed-to-navigate>allowed to
+  navigate</dfn> a second <a href=#browsing-context>browsing context</a> <var title="">B</var> if one of the
   following conditions is true:</p>
 
-  <ul><li>Either the <a href=#origin>origin</a> of the <a href=#active-document>active
-   document</a> of <var title="">A</var> is the <a href=#same-origin title="same
-   origin">same</a> as the <a href=#origin>origin</a> of the <a href=#active-document>active
+  <ul><li>Either the <a href=#origin>origin</a> of the <a href=#active-document>active document</a> of <var title="">A</var>
+   is the <a href=#same-origin title="same origin">same</a> as the <a href=#origin>origin</a> of the <a href=#active-document>active
    document</a> of <var title="">B</var>, or</li>
 
-   <li>The browsing context <var title="">A</var> is a <a href=#nested-browsing-context>nested
-   browsing context</a> with a <a href=#top-level-browsing-context>top-level browsing
-   context</a>, and its <a href=#top-level-browsing-context>top-level browsing context</a> is
-   <var title="">B</var>, or</li>
+   <li>The browsing context <var title="">A</var> is a <a href=#nested-browsing-context>nested browsing context</a> with a
+   <a href=#top-level-browsing-context>top-level browsing context</a>, and its <a href=#top-level-browsing-context>top-level browsing context</a> is <var title="">B</var>, or</li>
 
-   <li>The browsing context <var title="">B</var> is an
-   <a href=#auxiliary-browsing-context>auxiliary browsing context</a> and <var title="">A</var>
-   is <a href=#allowed-to-navigate>allowed to navigate</a> <var title="">B</var>'s
-   <a href=#opener-browsing-context>opener browsing context</a>, or</li>
+   <li>The browsing context <var title="">B</var> is an <a href=#auxiliary-browsing-context>auxiliary browsing context</a> and
+   <var title="">A</var> is <a href=#allowed-to-navigate>allowed to navigate</a> <var title="">B</var>'s <a href=#opener-browsing-context>opener
+   browsing context</a>, or</li>
 
-   <li>The browsing context <var title="">B</var> is not a
-   <a href=#top-level-browsing-context>top-level browsing context</a>, but there exists an
-   <a href=#ancestor-browsing-context>ancestor browsing context</a> of <var title="">B</var>
-   whose <a href=#active-document>active document</a> has the <a href=#same-origin title="same
-   origin">same</a> <a href=#origin>origin</a> as the <a href=#active-document>active
-   document</a> of <var title="">A</var> (possibly in fact being
-   <var title="">A</var> itself).</li>
+   <li>The browsing context <var title="">B</var> is not a <a href=#top-level-browsing-context>top-level browsing context</a>,
+   but there exists an <a href=#ancestor-browsing-context>ancestor browsing context</a> of <var title="">B</var> whose
+   <a href=#active-document>active document</a> has the <a href=#same-origin title="same origin">same</a> <a href=#origin>origin</a> as
+   the <a href=#active-document>active document</a> of <var title="">A</var> (possibly in fact being <var title="">A</var> itself).</li>
 
-  </ul><hr><p>An element has a <dfn id=browsing-context-scope-origin>browsing context scope origin</dfn> if its
-  <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a> is a
-  <a href=#top-level-browsing-context>top-level browsing context</a> or if all of its
-  <code><a href=#document>Document</a></code>'s <a href=#ancestor-browsing-context title="ancestor browsing
-  context">ancestor browsing contexts</a> all have <a href=#active-document title="active document">active documents</a> whose
-  <a href=#origin>origin</a> are the <a href=#same-origin>same origin</a> as the
-  element's <code><a href=#document>Document</a></code>'s <a href=#origin>origin</a>. If an element
-  has a <a href=#browsing-context-scope-origin>browsing context scope origin</a>, then its value is
-  the <a href=#origin>origin</a> of the element's <code><a href=#document>Document</a></code>.</p>
+  </ul><hr><p>An element has a <dfn id=browsing-context-scope-origin>browsing context scope origin</dfn> if its <code><a href=#document>Document</a></code>'s
+  <a href=#browsing-context>browsing context</a> is a <a href=#top-level-browsing-context>top-level browsing context</a> or if all of its
+  <code><a href=#document>Document</a></code>'s <a href=#ancestor-browsing-context title="ancestor browsing context">ancestor browsing contexts</a>
+  all have <a href=#active-document title="active document">active documents</a> whose <a href=#origin>origin</a> are the
+  <a href=#same-origin>same origin</a> as the element's <code><a href=#document>Document</a></code>'s <a href=#origin>origin</a>. If an
+  element has a <a href=#browsing-context-scope-origin>browsing context scope origin</a>, then its value is the
+  <a href=#origin>origin</a> of the element's <code><a href=#document>Document</a></code>.</p>
 
   </div>
 <!--REMOVE-TOPIC:Security-->
@@ -67161,44 +66899,35 @@
 
   <h4 id=groupings-of-browsing-contexts><span class=secno>6.1.5 </span>Groupings of browsing contexts</h4>
 
-  <p>Each <a href=#browsing-context>browsing context</a> is defined as having a list of
-  one or more <dfn id=directly-reachable-browsing-contexts>directly reachable browsing contexts</dfn>. These
-  are:</p>
+  <p>Each <a href=#browsing-context>browsing context</a> is defined as having a list of one or more <dfn id=directly-reachable-browsing-contexts>directly
+  reachable browsing contexts</dfn>. These are:</p>
 
   <ul><li>The <a href=#browsing-context>browsing context</a> itself.</li>
 
-   <li>All the <a href=#browsing-context>browsing context</a>'s <a href=#child-browsing-context title="child
-   browsing context">child browsing contexts</a>.</li>
+   <li>All the <a href=#browsing-context>browsing context</a>'s <a href=#child-browsing-context title="child browsing context">child browsing
+   contexts</a>.</li>
 
-   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#parent-browsing-context>parent browsing
-   context</a>.</li>
+   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#parent-browsing-context>parent browsing context</a>.</li>
 
-   <li>All the <a href=#browsing-context title="browsing context">browsing contexts</a>
-   that have the <a href=#browsing-context>browsing context</a> as their <a href=#opener-browsing-context>opener
-   browsing context</a>.</li>
+   <li>All the <a href=#browsing-context title="browsing context">browsing contexts</a> that have the <a href=#browsing-context>browsing
+   context</a> as their <a href=#opener-browsing-context>opener browsing context</a>.</li>
 
-   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#opener-browsing-context>opener browsing
-   context</a>.</li>
+   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#opener-browsing-context>opener browsing context</a>.</li>
 
-  </ul><p>The transitive closure of all the <a href=#browsing-context title="browsing
-  context">browsing contexts</a> that are <a href=#directly-reachable-browsing-contexts>directly reachable
-  browsing contexts</a> forms a <dfn id=unit-of-related-browsing-contexts>unit of related browsing
+  </ul><p>The transitive closure of all the <a href=#browsing-context title="browsing context">browsing contexts</a> that
+  are <a href=#directly-reachable-browsing-contexts>directly reachable browsing contexts</a> forms a <dfn id=unit-of-related-browsing-contexts>unit of related browsing
   contexts</dfn>.</p>
 
-  <p>Each <a href=#unit-of-related-browsing-contexts>unit of related browsing contexts</a> is then
-  further divided into the smallest number of groups such that every
-  member of each group has an <a href=#active-document>active document</a> with an
-  <a href=#effective-script-origin>effective script origin</a> that, through appropriate
-  manipulation of the <code title=dom-document-domain><a href=#dom-document-domain>document.domain</a></code> attribute, could
-  be made to be the same as other members of the group, but could not
-  be made the same as members of any other group. Each such group is a
-  <dfn id=unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</dfn>.</p>
+  <p>Each <a href=#unit-of-related-browsing-contexts>unit of related browsing contexts</a> is then further divided into the smallest
+  number of groups such that every member of each group has an <a href=#active-document>active document</a> with an
+  <a href=#effective-script-origin>effective script origin</a> that, through appropriate manipulation of the <code title=dom-document-domain><a href=#dom-document-domain>document.domain</a></code> attribute, could be made to be the same as
+  other members of the group, but could not be made the same as members of any other group. Each
+  such group is a <dfn id=unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</dfn>.</p>
 
-  <p class=note>There is also at most one <a href=#event-loop>event loop</a>
-  per <a href=#unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</a>
-  (though several <a href=#unit-of-related-similar-origin-browsing-contexts title="unit of related similar-origin browsing
-  contexts">units of related similar-origin browsing contexts</a>
-  can have a shared <a href=#event-loop>event loop</a>).</p>
+  <p class=note>There is also at most one <a href=#event-loop>event loop</a> per <a href=#unit-of-related-similar-origin-browsing-contexts>unit of related
+  similar-origin browsing contexts</a> (though several <a href=#unit-of-related-similar-origin-browsing-contexts title="unit of related
+  similar-origin browsing contexts">units of related similar-origin browsing contexts</a> can
+  have a shared <a href=#event-loop>event loop</a>).</p>
 
   </div>
 
@@ -67206,34 +66935,29 @@
 
   <h4 id=browsing-context-names><span class=secno>6.1.6 </span>Browsing context names</h4>
 
-  <p>Browsing contexts can have a <dfn id=browsing-context-name>browsing context name</dfn>. By
-  default, a browsing context has no name (its name is not set).</p>
+  <p>Browsing contexts can have a <dfn id=browsing-context-name>browsing context name</dfn>. By default, a browsing context
+  has no name (its name is not set).</p>
 
-  <p>A <dfn id=valid-browsing-context-name>valid browsing context name</dfn> is any string with at
-  least one character that does not start with a U+005F LOW LINE
-  character. (Names starting with an underscore are reserved for
+  <p>A <dfn id=valid-browsing-context-name>valid browsing context name</dfn> is any string with at least one character that does
+  not start with a U+005F LOW LINE character. (Names starting with an underscore are reserved for
   special keywords.)</p>
 
-  <p>A <dfn id=valid-browsing-context-name-or-keyword>valid browsing context name or keyword</dfn> is any string
-  that is either a <a href=#valid-browsing-context-name>valid browsing context name</a> or that is
-  an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for one of: <code title="">_blank</code>, <code title="">_self</code>, <code title="">_parent</code>, or <code title="">_top</code>.</p>
+  <p>A <dfn id=valid-browsing-context-name-or-keyword>valid browsing context name or keyword</dfn> is any string that is either a <a href=#valid-browsing-context-name>valid
+  browsing context name</a> or that is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for one of:
+  <code title="">_blank</code>, <code title="">_self</code>, <code title="">_parent</code>, or <code title="">_top</code>.</p>
 
-  <p>These values have different meanings based on whether the page is
-  sandboxed or not, as summarized in the following (non-normative)
-  table. In this table, "current" means the <a href=#browsing-context>browsing
-  context</a> that the link or script is in, "parent" means the
-  <a href=#parent-browsing-context>parent browsing context</a> of the one the link or script
-  is in, "master" means the nearest <a href=#ancestor-browsing-context>ancestor browsing
-  context</a> of the one the link or script is in that is not
-  itself in a <a href=#attr-iframe-seamless title=attr-iframe-seamless>seamless
-  iframe</a>, "top" means the <a href=#top-level-browsing-context>top-level browsing
-  context</a> of the one the link or script is in, "new" means a
-  new <a href=#top-level-browsing-context>top-level browsing context</a> or <a href=#auxiliary-browsing-context>auxiliary
-  browsing context</a> is to be created, subject to various user
-  preferences and user agent policies, "none" means that nothing will
-  happen, and "maybe new" means the same as "new" if the "<code title=attr-iframe-sandbox-allow-popups><a href=#attr-iframe-sandbox-allow-popups>allow-popups</a></code>"
-  keyword is also specified on the <code title=attr-iframe-sandbox><a href=#attr-iframe-sandbox>sandbox</a></code> attribute (or if the user
-  overrode the sandboxing), and the same as "none" otherwise.</p>
+  <p>These values have different meanings based on whether the page is sandboxed or not, as
+  summarized in the following (non-normative) table. In this table, "current" means the
+  <a href=#browsing-context>browsing context</a> that the link or script is in, "parent" means the <a href=#parent-browsing-context>parent
+  browsing context</a> of the one the link or script is in, "master" means the nearest
+  <a href=#ancestor-browsing-context>ancestor browsing context</a> of the one the link or script is in that is not itself in a
+  <a href=#attr-iframe-seamless title=attr-iframe-seamless>seamless iframe</a>, "top" means the <a href=#top-level-browsing-context>top-level
+  browsing context</a> of the one the link or script is in, "new" means a new <a href=#top-level-browsing-context>top-level
+  browsing context</a> or <a href=#auxiliary-browsing-context>auxiliary browsing context</a> is to be created, subject to
+  various user preferences and user agent policies, "none" means that nothing will happen, and
+  "maybe new" means the same as "new" if the "<code title=attr-iframe-sandbox-allow-popups><a href=#attr-iframe-sandbox-allow-popups>allow-popups</a></code>" keyword is also specified on the
+  <code title=attr-iframe-sandbox><a href=#attr-iframe-sandbox>sandbox</a></code> attribute (or if the user overrode the
+  sandboxing), and the same as "none" otherwise.</p>
 
   <table><thead><tr><th rowspan=2>Keyword
      <th rowspan=2>Ordinary effect
@@ -67368,151 +67092,129 @@
 
   <div class=impl>
 
-  <hr><p>An algorithm is <dfn id=allowed-to-show-a-pop-up>allowed to show a pop-up</dfn> if, in the
-  <a href=#concept-task title=concept-task>task</a> in which the algorithm is
-  running, either:</p>
+  <hr><p>An algorithm is <dfn id=allowed-to-show-a-pop-up>allowed to show a pop-up</dfn> if, in the <a href=#concept-task title=concept-task>task</a> in which the algorithm is running, either:</p>
 
-  <ul class=brief><li>an <a href=#activation-behavior>activation behavior</a> is currently being
-   processed whose <code title=event-click><a href=#event-click>click</a></code> event was
-   <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>, or</li>
+  <ul class=brief><li>an <a href=#activation-behavior>activation behavior</a> is currently being processed whose <code title=event-click><a href=#event-click>click</a></code> event was <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>,
+   or</li>
 
    <li>the event listener for a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> <code title=event-click><a href=#event-click>click</a></code> event is being handled.</li>
 
-  </ul><hr><p><dfn id=the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name>The rules for choosing a browsing context given a browsing
-  context name</dfn> are as follows. The rules assume that they are
-  being applied in the context of a <a href=#browsing-context>browsing context</a>.</p>
+  </ul><hr><p><dfn id=the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name>The rules for choosing a browsing context given a browsing context name</dfn> are as
+  follows. The rules assume that they are being applied in the context of a <a href=#browsing-context>browsing
+  context</a>.</p>
 
   <ol><li>
 
-    <p>If the given browsing context name is the empty string or <code title="">_self</code>, then the chosen browsing context must be
-    the current one.</p>
+    <p>If the given browsing context name is the empty string or <code title="">_self</code>, then
+    the chosen browsing context must be the current one.</p>
 
-    <p>If the given browsing context name is <code title="">_self</code>, then this is an <a href=#explicit-self-navigation-override>explicit
-    self-navigation override</a>, which overrides the behavior of
-    the <a href=#seamless-browsing-context-flag>seamless browsing context flag</a> set by the <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute on
-    <code><a href=#the-iframe-element>iframe</a></code> elements.</p>
+    <p>If the given browsing context name is <code title="">_self</code>, then this is an
+    <a href=#explicit-self-navigation-override>explicit self-navigation override</a>, which overrides the behavior of the
+    <a href=#seamless-browsing-context-flag>seamless browsing context flag</a> set by the <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute on <code><a href=#the-iframe-element>iframe</a></code> elements.</p>
 
    </li>
 
-   <li><p>If the given browsing context name is <code title="">_parent</code>, then the chosen browsing context must be
-   the <a href=#parent-browsing-context><em>parent</em> browsing context</a> of the current
-   one, unless there isn't one, in which case the chosen browsing
-   context must be the current browsing context.</li>
+   <li><p>If the given browsing context name is <code title="">_parent</code>, then the chosen
+   browsing context must be the <a href=#parent-browsing-context><em>parent</em> browsing context</a> of the current one,
+   unless there isn't one, in which case the chosen browsing context must be the current browsing
+   context.</li>
 
-   <li><p>If the given browsing context name is <code title="">_top</code>, then the chosen browsing context must be the
-   <a href=#top-level-browsing-context>top-level browsing context</a> of the current one, if
-   there is one, or else the current browsing context.</li>
+   <li><p>If the given browsing context name is <code title="">_top</code>, then the chosen browsing
+   context must be the <a href=#top-level-browsing-context>top-level browsing context</a> of the current one, if there is one,
+   or else the current browsing context.</li>
 
    <li>
 
-    <p>If the given browsing context name is not <code title="">_blank</code> and there exists a browsing context whose
-    <a href=#browsing-context-name title="browsing context name">name</a> is the same as the
-    given browsing context name, and the current browsing context is
-    <a href=#allowed-to-navigate>allowed to navigate</a> that browsing context, and the
-    user agent determines that the two browsing contexts are related
-    enough that it is ok if they reach each other, then that browsing
-    context must be the chosen one. If there are multiple matching
-    browsing contexts, the user agent should select one in some
-    arbitrary consistent manner, such as the most recently opened,
-    most recently focused, or more closely related.</p>
+    <p>If the given browsing context name is not <code title="">_blank</code> and there exists a
+    browsing context whose <a href=#browsing-context-name title="browsing context name">name</a> is the same as the given
+    browsing context name, and the current browsing context is <a href=#allowed-to-navigate>allowed to navigate</a> that
+    browsing context, and the user agent determines that the two browsing contexts are related
+    enough that it is ok if they reach each other, then that browsing context must be the chosen
+    one. If there are multiple matching browsing contexts, the user agent should select one in some
+    arbitrary consistent manner, such as the most recently opened, most recently focused, or more
+    closely related.</p>
 
-    <p>If the browsing context is chosen by this step to be the
-    current browsing context, then this is also an <a href=#explicit-self-navigation-override>explicit
-    self-navigation override</a>.</p>
+    <p>If the browsing context is chosen by this step to be the current browsing context, then this
+    is also an <a href=#explicit-self-navigation-override>explicit self-navigation override</a>.</p>
 
    </li>
 
    <li>
 
-    <p>Otherwise, a new browsing context is being requested, and what
-    happens depends on the user agent's configuration and/or abilities
-    — it is determined by the rules given for the first
+    <p>Otherwise, a new browsing context is being requested, and what happens depends on the user
+    agent's configuration and/or abilities — it is determined by the rules given for the first
     applicable option from the following list:</p>
 
-    <dl class=switch><dt id=sandboxWindowOpen>If the current browsing context's
-     <a href=#active-document>active document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag
-     set</a> has the <a href=#sandboxed-auxiliary-navigation-browsing-context-flag>sandboxed auxiliary navigation browsing
+    <dl class=switch><dt id=sandboxWindowOpen>If the current browsing context's <a href=#active-document>active document</a>'s
+     <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> has the <a href=#sandboxed-auxiliary-navigation-browsing-context-flag>sandboxed auxiliary navigation browsing
      context flag</a> set.</dt>
 
      <dd>
 
       <p>Typically, there is no chosen browsing context.</p>
 
-      <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
-      browsing context's name isn't set to the given browsing context
-      name). The default behaviour (if the user agent doesn't offer
-      the option to the user, or if the user declines to allow a
-      browsing context to be used) must be that there must not be a
-      chosen browsing context.</p>
+      <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 browsing context's name isn't
+      set to the given browsing context name). The default behaviour (if the user agent doesn't
+      offer the option to the user, or if the user declines to allow a browsing context to be used)
+      must be that there must not be a chosen browsing context.</p>
 
-      <p class=warning>If this case occurs, it means that an author
-      has explicitly sandboxed the document that is trying to open a
-      link.</p>
+      <p class=warning>If this case occurs, it means that an author has explicitly sandboxed the
+      document that is trying to open a link.</p>
 
      </dd>
 
 
-     <dt id=noopener>If the user agent has been configured such that
-     in this instance it will create a new browsing context, and the
-     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>
+     <dt id=noopener>If the user agent has been configured such that in this instance it will
+     create a new browsing context, and the 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><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. The creation of such a <a href=#browsing-context>browsing context</a> is
-     <dfn id=a-new-start-for-session-storage>a new start for session storage</dfn>.</p>
+     <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. The creation of such a <a href=#browsing-context>browsing context</a>
+     is <dfn id=a-new-start-for-session-storage>a new start for session storage</dfn>.</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>
+     <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
+     <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><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.</p>
+     <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.</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>
+     <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 reuse the current browsing context</dt>
+     <dt>If the user agent has been configured such that in this instance it will reuse the current
+     browsing context</dt>
 
-     <dd><p>The chosen browsing context is the current browsing
-     context.</dd>
+     <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>
+     <dt>If the user agent has been configured such that in this instance it will not find a
+     browsing context</dt>
 
      <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
-    browsing context.</p>
+    </dl><p>User agent implementors are encouraged to provide a way for users to configure the user agent
+    to always reuse the current browsing context.</p>
 
-    <p>If the current browsing context's <a href=#active-document>active
-    document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> has the
-    <a href=#sandboxed-navigation-browsing-context-flag>sandboxed navigation browsing context flag</a> set and
-    chosen browsing context picked above, if any, is a new browsing
-    context (whether top-level or auxiliary), then all the flags that
-    are set in the current browsing context's <a href=#active-document>active
-    document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> when the
-    new browsing context is created must be set in the new browsing
-    context's <a href=#popup-sandboxing-flag-set>popup sandboxing flag set</a>, and the current
-    browsing context must be set as the new browsing context's
-    <a href=#one-permitted-sandboxed-navigator>one permitted sandboxed navigator</a>.</p>
+    <p>If the current browsing context's <a href=#active-document>active document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag
+    set</a> has the <a href=#sandboxed-navigation-browsing-context-flag>sandboxed navigation browsing context flag</a> set and chosen
+    browsing context picked above, if any, is a new browsing context (whether top-level or
+    auxiliary), then all the flags that are set in the current browsing context's <a href=#active-document>active
+    document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> when the new browsing context is
+    created must be set in the new browsing context's <a href=#popup-sandboxing-flag-set>popup sandboxing flag set</a>, and
+    the current browsing context must be set as the new browsing context's <a href=#one-permitted-sandboxed-navigator>one permitted
+    sandboxed navigator</a>.</p>
 
    </li>
 

Modified: index
===================================================================
--- index	2012-11-24 04:51:58 UTC (rev 7530)
+++ index	2012-11-24 17:39:19 UTC (rev 7531)
@@ -852,7 +852,7 @@
      <li><a href=#associating-names-with-items><span class=secno>5.2.5 </span>Associating names with items</a></li>
      <li><a href=#microdata-and-other-namespaces><span class=secno>5.2.6 </span>Microdata and other namespaces</a></ol></li>
    <li><a href=#microdata-dom-api><span class=secno>5.3 </span>Microdata DOM API</a></li>
-   <li><a href=#mdvocabs><span class=secno>5.4 </span>Microdata vocabularies</a>
+   <li><a href=#mdvocabs><span class=secno>5.4 </span>Sample microdata vocabularies</a>
     <ol>
      <li><a href=#vcard><span class=secno>5.4.1 </span>vCard</a>
       <ol>
@@ -1614,7 +1614,7 @@
    <li>The <code title=attr-inert><a href=#the-inert-attribute>inert</a></code> global attribute to disable subtrees.</li><!--INERT-->
    <li>The <code title=attr-fs-method-dialog-keyword><a href=#attr-fs-method-dialog-keyword>dialog</a></code> keyword on the <code><a href=#the-form-element>form</a></code> element's <code title=attr-fs-method><a href=#attr-fs-method>method</a></code> attribute, for a simpler way to close dialogs.</li><!--FORM-DIALOG-->
    <li>The <code title=dom-document-cssElementMap><a href=#dom-document-csselementmap>cssElementMap</a></code> feature for defining <a href=#css-element-reference-identifier title="CSS element reference identifier">CSS element reference identifiers</a>.</li> <!--CSSREF-->
-   <li>Some predefined <a href=#mdvocabs>Microdata vocabularies</a>.</li>
+   <li>Some predefined sample <a href=#mdvocabs>Microdata vocabularies</a>.</li>
    <li>The <code><a href=#the-data-element>data</a></code> element for marking up machine-readable data.</li><!--DATA--><!--FORK-->
    <li>The <a href=#application-cache>application cache</a> feature's <a href=#concept-appcache-mode-prefer-online title=concept-appcache-mode-prefer-online>prefer-online</a> mode.</li><!--FORK--><!--APPCACHE-PREFER-ONLINE-->
    <li>The <code title=dom-TextTrack-inBandMetadataTrackDispatchType><a href=#dom-texttrack-inbandmetadatatrackdispatchtype>TextTrack.inBandMetadataTrackDispatchType</a></code> feature for Internet-based TV broadcast.</li>
@@ -59938,7 +59938,6 @@
   attribute, on getting, must return the last value to which it was
   set. On setting, it must be set to the new value. When the element
   is created, it must be set to the empty string.</p>
-
 <!--TOPIC:HTML-->
 
   <hr><p><strong>Canceling dialogs</strong>: When a
@@ -62836,6 +62835,7 @@
   </div>
 
 
+<!--TOPIC:Microdata-->
 
   <h2 id=microdata><span class=secno>5 </span><dfn>Microdata</dfn></h2>
 
@@ -62878,20 +62878,17 @@
 
 <!-- v2
 
-  * <itemref itemprop="foo" src="url#id"> to import the item with
-    id="id" from url into the current microdata block as the value of
-    property foo?
+  * <itemref itemprop="foo" src="url#id"> to import the item with id="id" from url into the current
+    microdata block as the value of property foo?
 
-  * splitting the 'content' part of a property into multiple sub-bits,
-    as in:
+  * splitting the 'content' part of a property into multiple sub-bits, as in:
 
      <span itemprop="tel" item-content-in-bits>
        Telephone:
        <span content-bit>+44</span> (0) <span content-bit>1223 123 123</span>
      </span>
 
-    maybe vocabs that need this can use a sub vocabulary specifically
-    for this:
+    maybe vocabs that need this can use a sub vocabulary specifically for this:
 
      <span itemprop="tel" itemscope itemtype="http://bits.example/">
        Telephone:
@@ -62906,32 +62903,27 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Sometimes, it is desirable to annotate content with specific
-  machine-readable labels, e.g. to allow generic scripts to provide
-  services that are customised to the page, or to enable content from
-  a variety of cooperating authors to be processed by a single script
-  in a consistent manner.</p>
+  <p>Sometimes, it is desirable to annotate content with specific machine-readable labels, e.g. to
+  allow generic scripts to provide services that are customised to the page, or to enable content
+  from a variety of cooperating authors to be processed by a single script in a consistent
+  manner.</p>
 
-  <p>For this purpose, authors can use the microdata features
-  described in this section. Microdata allows nested groups of
-  name-value pairs to be added to documents, in parallel with the
-  existing content.</p>
+  <p>For this purpose, authors can use the microdata features described in this section. Microdata
+  allows nested groups of name-value pairs to be added to documents, in parallel with the existing
+  content.</p>
 
 
-
   <h4 id=the-basic-syntax><span class=secno>5.1.2 </span>The basic syntax</h4>
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>At a high level, microdata consists of a group of name-value
-  pairs. The groups are called <a href=#concept-item title=concept-item>items</a>, and each name-value pair is a
-  property. Items and properties are represented by regular
-  elements.</p>
+  <p>At a high level, microdata consists of a group of name-value pairs. The groups are called <a href=#concept-item title=concept-item>items</a>, and each name-value pair is a property. Items and properties
+  are represented by regular elements.</p>
 
   <p>To create an item, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is used.</p>
 
-  <p>To add a property to an item, the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is used on one of
-  the <a href=#concept-item title=concept-item>item's</a> descendants.</p>
+  <p>To add a property to an item, the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is used
+  on one of the <a href=#concept-item title=concept-item>item's</a> descendants.</p>
 
   <div class=example>
 
@@ -62947,13 +62939,12 @@
 
   </div>
 
-  <p>Markup without microdata attributes has no effect on
-  microdata.</p>
+  <p>Markup without microdata attributes has no effect on microdata.</p>
 
   <div class=example>
 
-   <p>These two examples are exactly equivalent, at a microdata level,
-   as the previous two examples respectively:</p>
+   <p>These two examples are exactly equivalent, at a microdata level, as the previous two examples
+   respectively:</p>
 
    <pre><div itemscope>
  <p>My <em>name</em> is <span itemprop="name">E<strong>liz</strong>abeth</span>.</p>
@@ -62983,15 +62974,14 @@
 
   </div>
 
-  <p>When a string value is a <a href=#url title=URL>URLs</a>, it is
-  expressed using the <code><a href=#the-a-element>a</a></code> element and its <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute, the
-  <code><a href=#the-img-element>img</a></code> element and its <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute, or other elements that
-  link to or embed external resources.</p>
+  <p>When a string value is a <a href=#url title=URL>URLs</a>, it is expressed using the
+  <code><a href=#the-a-element>a</a></code> element and its <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute, the
+  <code><a href=#the-img-element>img</a></code> element and its <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute, or other
+  elements that link to or embed external resources.</p>
 
   <div class=example>
 
-   <p>In this example, the item has one property, "image", whose value
-   is a URL:</p>
+   <p>In this example, the item has one property, "image", whose value is a URL:</p>
 
    <pre><div itemscope>
  <img itemprop="image" src="google-logo.png" alt="Google">
@@ -63006,9 +62996,8 @@
 
   <div class=example>
 
-   <p>Here, there is an item with a property whose value is a product
-   ID. The ID is not human-friendly, so the product's name is used
-   the human-visible text instead of the ID.</p>
+   <p>Here, there is an item with a property whose value is a product ID. The ID is not
+   human-friendly, so the product's name is used the human-visible text instead of the ID.</p>
 
    <pre><h1 itemscope>
  <data itemprop="product-id" value="9678AOU879">The Instigator 2000</data>
@@ -63016,14 +63005,11 @@
 
   </div>
 
-  <p>For date- and time-related data, the <code><a href=#the-time-element>time</a></code> element
-  and its <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> attribute
-  can be used instead.</p>
+  <p>For date- and time-related data, the <code><a href=#the-time-element>time</a></code> element and its <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> attribute can be used instead.</p>
 
   <div class=example>
 
-   <p>In this example, the item has one property, "birthday", whose
-   value is a date:</p>
+   <p>In this example, the item has one property, "birthday", whose value is a date:</p>
 
    <pre><div itemscope>
  I was born on <time itemprop="birthday" datetime="2009-05-10">May 10th 2009</time>.
@@ -63031,44 +63017,35 @@
 
   </div>
 
-  <p>Properties can also themselves be groups of name-value pairs, by
-  putting the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute
-  on the element that declares the property.</p>
+  <p>Properties can also themselves be groups of name-value pairs, by putting the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute on the element that declares the property.</p>
 
-  <p>Items that are not part of others are called <a href=#top-level-microdata-items>top-level
-  microdata items</a>.</p>
+  <p>Items that are not part of others are called <a href=#top-level-microdata-items>top-level microdata items</a>.</p>
 
   <div class=example>
 
-   <p>In this example, the outer item represents a person, and the
-   inner one represents a band:</p>
+   <p>In this example, the outer item represents a person, and the inner one represents a band:</p>
 
    <pre><div itemscope>
  <p>Name: <span itemprop="name">Amanda</span></p>
  <p>Band: <span itemprop="band" itemscope> <span itemprop="name">Jazz Band</span> (<span itemprop="size">12</span> players)</span></p>
 </div></pre>
 
-   <p>The outer item here has two properties, "name" and
-   "band". The "name" is "Amanda", and the
-   "band" is an item in its own right, with two
-   properties, "name" and "size". The
-   "name" of the band is "Jazz Band", and the
-   "size" is "12".</p>
+   <p>The outer item here has two properties, "name" and "band". The "name" is "Amanda", and the
+   "band" is an item in its own right, with two properties, "name" and "size". The "name" of the
+   band is "Jazz Band", and the "size" is "12".</p>
 
-   <p>The outer item in this example is a top-level microdata
-   item.</p>
+   <p>The outer item in this example is a top-level microdata item.</p>
 
   </div>
 
-  <p>Properties that are not descendants of the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute can be associated
-  with the <a href=#concept-item title=concept-item>item</a> using the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute. This attribute takes
-  a list of IDs of elements to crawl in addition to crawling the
-  children of the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
+  <p>Properties that are not descendants of the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute can be associated with the <a href=#concept-item title=concept-item>item</a> using the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute.
+  This attribute takes a list of IDs of elements to crawl in addition to crawling the children of
+  the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
 
   <div class=example>
 
-   <p>This example is the same as the previous one, but all the
-   properties are separated from their <a href=#concept-item title=concept-item>items</a>:</p>
+   <p>This example is the same as the previous one, but all the properties are separated from their
+   <a href=#concept-item title=concept-item>items</a>:</p>
 
    <pre><div itemscope id="amanda" itemref="a b"></div>
 <p id="a">Name: <span itemprop="name">Amanda</span></p>
@@ -63078,15 +63055,14 @@
  <p>Size: <span itemprop="size">12</span> players</p>
 </div></pre>
 
-   <p>This gives the same result as the previous example. The first
-   item has two properties, "name", set to "Amanda", and "band", set
-   to another item. That second item has two further properties,
+   <p>This gives the same result as the previous example. The first item has two properties, "name",
+   set to "Amanda", and "band", set to another item. That second item has two further properties,
    "name", set to "Jazz Band", and "size", set to "12".</p>
 
   </div>
 
-  <p>An <a href=#concept-item title=concept-item>item</a> can have multiple
-  properties with the same name and different values.</p>
+  <p>An <a href=#concept-item title=concept-item>item</a> can have multiple properties with the same name and
+  different values.</p>
 
   <div class=example>
 
@@ -63100,21 +63076,18 @@
  </ul>
 </div></pre>
 
-   <p>This thus results in an item with two properties, both
-   "flavor", having the values "Lemon sorbet" and "Apricot
-   sorbet".</p>
+   <p>This thus results in an item with two properties, both "flavor", having the values "Lemon
+   sorbet" and "Apricot sorbet".</p>
 
   </div>
 
-  <p>An element introducing a property can also introduce multiple
-  properties at once, to avoid duplication when some of the properties
-  have the same value.</p>
+  <p>An element introducing a property can also introduce multiple properties at once, to avoid
+  duplication when some of the properties have the same value.</p>
 
   <div class=example>
 
-   <p>Here we see an item with two properties,
-   "favorite-color" and "favorite-fruit", both
-   set to the value "orange":</p>
+   <p>Here we see an item with two properties, "favorite-color" and "favorite-fruit", both set to
+   the value "orange":</p>
 
    <pre><div itemscope>
  <span itemprop="favorite-color favorite-fruit">orange</span>
@@ -63122,14 +63095,12 @@
 
   </div>
 
-  <p>It's important to note that there is no relationship between the
-  microdata and the content of the document where the microdata is
-  marked up.</p>
+  <p>It's important to note that there is no relationship between the microdata and the content of
+  the document where the microdata is marked up.</p>
 
   <div class=example>
 
-   <p>There is no semantic difference, for instance, between the
-   following two examples:</p>
+   <p>There is no semantic difference, for instance, between the following two examples:</p>
 
    <pre><figure>
  <img src="castle.jpeg">
@@ -63142,13 +63113,11 @@
  <figcaption>The Castle (1986)</figcaption>
 </figure></pre>
 
-   <p>Both have a figure with a caption, and both, completely
-   unrelated to the figure, have an item with a name-value pair with
-   the name "name" and the value "The Castle". The only
-   difference is that if the user drags the caption out of the
-   document, in the former case, the item will be included in the
-   drag-and-drop data. In neither case is the image in any way
-   associated with the item.</p>
+   <p>Both have a figure with a caption, and both, completely unrelated to the figure, have an item
+   with a name-value pair with the name "name" and the value "The Castle". The only difference is
+   that if the user drags the caption out of the document, in the former case, the item will be
+   included in the drag-and-drop data. In neither case is the image in any way associated with the
+   item.</p>
 
   </div>
 
@@ -63157,19 +63126,15 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>The examples in the previous section show how information could
-  be marked up on a page that doesn't expect its microdata to be
-  re-used. Microdata is most useful, though, when it is used in
-  contexts where other authors and readers are able to cooperate to
-  make new uses of the markup.</p>
+  <p>The examples in the previous section show how information could be marked up on a page that
+  doesn't expect its microdata to be re-used. Microdata is most useful, though, when it is used in
+  contexts where other authors and readers are able to cooperate to make new uses of the markup.</p>
 
-  <p>For this purpose, it is necessary to give each <a href=#concept-item title=concept-item>item</a> a type, such as
-  "http://example.com/person", or "http://example.org/cat", or
-  "http://band.example.net/". Types are identified as <a href=#url title=URL>URLs</a>.</p>
+  <p>For this purpose, it is necessary to give each <a href=#concept-item title=concept-item>item</a> a type,
+  such as "http://example.com/person", or "http://example.org/cat", or "http://band.example.net/".
+  Types are identified as <a href=#url title=URL>URLs</a>.</p>
 
-  <p>The type for an <a href=#concept-item title=concept-item>item</a> is given
-  as the value of an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code>
-  attribute on the same element as the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
+  <p>The type for an <a href=#concept-item title=concept-item>item</a> is given as the value of an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute on the same element as the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
 
   <div class=example>
 
@@ -63182,45 +63147,34 @@
  <img itemprop="img" src="hedral.jpeg" alt="" title="Hedral, age 18 months">
 </section></pre>
 
-   <p>In this example the "http://example.org/animals#cat" item has three
-   properties, a "name" ("Hedral"), a "desc" ("Hedral is..."), and an
-   "img" ("hedral.jpeg").</p>
+   <p>In this example the "http://example.org/animals#cat" item has three properties, a "name"
+   ("Hedral"), a "desc" ("Hedral is..."), and an "img" ("hedral.jpeg").</p>
 
   </div>
 
-  <p>The type gives the context for the properties, thus selecting a
-  vocabulary: a property named "class" given for an item with the type
-  "http://census.example/person" might refer to the economic class of
-  an individual, while a property named "class" given for an item with
-  the type "http://example.com/school/teacher" might refer to the
-  classroom a teacher has been assigned. Several types can share a
-  vocabulary. For example, the types "<code title="">http://example.org/people/teacher</code>" and "<code title="">http://example.org/people/engineer</code>" could be defined
-  to use the same vocabulary (though maybe some properties would not
-  be especially useful in both cases, e.g. maybe the "<code title="">http://example.org/people/engineer</code>" type might not
-  typically be used with the "<code title="">classroom</code>"
-  property). Multiple types defined to use the same vocabulary can be
-  given for a single item by listing the URLs as a space-separated
-  list in the attribute' value. An item cannot be given two types if
-  they do not use the same vocabulary, however.</p>
+  <p>The type gives the context for the properties, thus selecting a vocabulary: a property named
+  "class" given for an item with the type "http://census.example/person" might refer to the economic
+  class of an individual, while a property named "class" given for an item with the type
+  "http://example.com/school/teacher" might refer to the classroom a teacher has been assigned.
+  Several types can share a vocabulary. For example, the types "<code title="">http://example.org/people/teacher</code>" and "<code title="">http://example.org/people/engineer</code>" could be defined to use the same vocabulary
+  (though maybe some properties would not be especially useful in both cases, e.g. maybe the "<code title="">http://example.org/people/engineer</code>" type might not typically be used with the
+  "<code title="">classroom</code>" property). Multiple types defined to use the same vocabulary can
+  be given for a single item by listing the URLs as a space-separated list in the attribute' value.
+  An item cannot be given two types if they do not use the same vocabulary, however.</p>
 
 
   <h4 id=global-identifiers-for-items><span class=secno>5.1.4 </span>Global identifiers for items</h4>
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Sometimes, an <a href=#concept-item title=concept-item>item</a> gives
-  information about a topic that has a global identifier. For example,
-  books can be identified by their ISBN number.</p>
+  <p>Sometimes, an <a href=#concept-item title=concept-item>item</a> gives information about a topic that has a
+  global identifier. For example, books can be identified by their ISBN number.</p>
 
-  <p>Vocabularies (as identified by the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute) can be designed
-  such that <a href=#concept-item title=concept-item>items</a> get associated
-  with their global identifier in an unambiguous way by expressing the
-  global identifiers as <a href=#url title=URL>URLs</a> given in an
-  <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute.</p>
+  <p>Vocabularies (as identified by the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute) can
+  be designed such that <a href=#concept-item title=concept-item>items</a> get associated with their global
+  identifier in an unambiguous way by expressing the global identifiers as <a href=#url title=URL>URLs</a> given in an <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute.</p>
 
-  <p>The exact meaning of the <a href=#url title=URL>URLs</a> given in
-  <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attributes depends on the
-  vocabulary used.</p>
+  <p>The exact meaning of the <a href=#url title=URL>URLs</a> given in <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attributes depends on the vocabulary used.</p>
 
   <div class=example>
 
@@ -63237,24 +63191,20 @@
  <dd><time itemprop="pubdate" datetime="1996-01-26">26 January 1996</time>
 </dl></pre>
 
-   <p>The "<code title="">http://vocab.example.net/book</code>"
-   vocabulary in this example would define that the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute takes a <code title="">urn:</code> <a href=#url>URL</a> pointing to the ISBN of the
-   book.</p>
+   <p>The "<code title="">http://vocab.example.net/book</code>" vocabulary in this example would
+   define that the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute takes a <code title="">urn:</code> <a href=#url>URL</a> pointing to the ISBN of the book.</p>
 
   </div>
 
   <!-- (commented out since itemtype="" defines the meaning of the
         identifier for now)
-  <p>Although it is common practice, authors are encouraged not to use
-  the same URL to identify multiple topics; in particular, an HTTP URL
-  usually identifies a specific resource (such as an image or
-  document), and authors are encouraged to not use them to identify
-  people, non-Web resources like companies, movies, and products, or
-  other abstract concepts. Using an HTTP URL as a global identifier
-  for something other than the resource actually designated by the URL
-  leads to a situation where it is ambiguous whether the identifier,
-  and thus the set of properties specified in the microdata,
-  references the page or something else.</p>
+  <p>Although it is common practice, authors are encouraged not to use the same URL to identify
+  multiple topics; in particular, an HTTP URL usually identifies a specific resource (such as an
+  image or document), and authors are encouraged to not use them to identify people, non-Web
+  resources like companies, movies, and products, or other abstract concepts. Using an HTTP URL as a
+  global identifier for something other than the resource actually designated by the URL leads to a
+  situation where it is ambiguous whether the identifier, and thus the set of properties specified
+  in the microdata, references the page or something else.</p>
   -->
 
 
@@ -63263,16 +63213,13 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Using microdata means using a vocabulary. For some purposes, an
-  ad-hoc vocabulary is adequate. For others, a vocabulary will need to
-  be designed. Where possible, authors are encouraged to re-use
-  existing vocabularies, as this makes content re-use easier.</p>
+  <p>Using microdata means using a vocabulary. For some purposes, an ad-hoc vocabulary is adequate.
+  For others, a vocabulary will need to be designed. Where possible, authors are encouraged to
+  re-use existing vocabularies, as this makes content re-use easier.</p>
 
-  <p>When designing new vocabularies, identifiers can be created
-  either using <a href=#url title=URL>URLs</a>, or, for properties, as
-  plain words (with no dots or colons). For URLs, conflicts with other
-  vocabularies can be avoided by only using identifiers that
-  correspond to pages that the author has control over.</p>
+  <p>When designing new vocabularies, identifiers can be created either using <a href=#url title=URL>URLs</a>, or, for properties, as plain words (with no dots or colons). For URLs,
+  conflicts with other vocabularies can be avoided by only using identifiers that correspond to
+  pages that the author has control over.</p>
 
   <div class=example>
 
@@ -63283,22 +63230,18 @@
 
   </div>
 
-  <p>Properties whose names are just plain words can only be used
-  within the context of the types for which they are intended;
-  properties named using URLs can be reused in items of any type. If
-  an item has no type, and is not part of another item, then if its
-  properties have names that are just plain words, they are not
-  intended to be globally unique, and are instead only intended for
-  limited use. Generally speaking, authors are encouraged to use
-  either properties with globally unique names (URLs) or ensure that
-  their items are typed.</p>
+  <p>Properties whose names are just plain words can only be used within the context of the types
+  for which they are intended; properties named using URLs can be reused in items of any type. If an
+  item has no type, and is not part of another item, then if its properties have names that are just
+  plain words, they are not intended to be globally unique, and are instead only intended for
+  limited use. Generally speaking, authors are encouraged to use either properties with globally
+  unique names (URLs) or ensure that their items are typed.</p>
 
   <div class=example>
 
-   <p>Here, an item is an "http://example.org/animals#cat", and most of the
-   properties have names that are words defined in the context of that
-   type. There are also a few additional properties whose names come
-   from other vocabularies.</p>
+   <p>Here, an item is an "http://example.org/animals#cat", and most of the properties have names
+   that are words defined in the context of that type. There are also a few additional properties
+   whose names come from other vocabularies.</p>
 
 <pre><section itemscope itemtype="http://example.org/animals#cat">
  <h1 itemprop="name http://example.com/fn">Hedral</h1>
@@ -63309,8 +63252,8 @@
  <img itemprop="img" src="hedral.jpeg" alt="" title="Hedral, age 18 months">
 </section></pre>
 
-   <p>This example has one item with the type "http://example.org/animals#cat"
-   and the following properties:</p>
+   <p>This example has one item with the type "http://example.org/animals#cat" and the following
+   properties:</p>
 
    <table><thead><tr><td>Property
       <td>Value
@@ -63334,69 +63277,61 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>The microdata becomes even more useful when scripts can use it to
-  expose information to the user, for example offering it in a form
-  that can be used by other applications.</p>
+  <p>The microdata becomes even more useful when scripts can use it to expose information to the
+  user, for example offering it in a form that can be used by other applications.</p>
 
-  <p>The <code title=dom-document-getItems><a href=#dom-document-getitems>document.getItems(<var title="">typeNames</var>)</a></code> method provides access to the
-  <a href=#top-level-microdata-items>top-level microdata items</a>. It returns a
-  <code><a href=#nodelist>NodeList</a></code> containing the items with the specified types,
-  or all types if no argument is specified.</p>
+  <p>The <code title=dom-document-getItems><a href=#dom-document-getitems>document.getItems(<var title="">typeNames</var>)</a></code>
+  method provides access to the <a href=#top-level-microdata-items>top-level microdata items</a>. It returns a
+  <code><a href=#nodelist>NodeList</a></code> containing the items with the specified types, or all types if no argument
+  is specified.</p>
 
-  <p>Each <a href=#concept-item title=concept-item>item</a> is represented in the
-  DOM by the element on which the relevant <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is found. These
-  elements have their <code title=dom-itemScope><a href=#dom-itemscope>element.itemScope</a></code> IDL attribute set to
-  true.</p>
+  <p>Each <a href=#concept-item title=concept-item>item</a> is represented in the DOM by the element on which
+  the relevant <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is found. These elements have
+  their <code title=dom-itemScope><a href=#dom-itemscope>element.itemScope</a></code> IDL attribute set to true.</p>
 
-  <p>The type(s) of <a href=#concept-item title=concept-item>items</a> can be
-  obtained using the <code title=dom-itemType><a href=#dom-itemtype>element.itemType</a></code> IDL attribute on the
-  element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute.</p>
+  <p>The type(s) of <a href=#concept-item title=concept-item>items</a> can be obtained using the <code title=dom-itemType><a href=#dom-itemtype>element.itemType</a></code> IDL attribute on the element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute.</p>
 
   <div class=example>
 
-   <p>This sample shows how the <code title=dom-document-getItems><a href=#dom-document-getitems>getItems()</a></code> method can be used
-   to obtain a list of all the top-level microdata items of a
-   particular type given in the document:</p>
+   <p>This sample shows how the <code title=dom-document-getItems><a href=#dom-document-getitems>getItems()</a></code> method can be
+   used to obtain a list of all the top-level microdata items of a particular type given in the
+   document:</p>
 
    <pre>var cats = document.getItems("http://example.com/feline");</pre>
 
   </div>
 
-  <p>Once an element representing an <a href=#concept-item title=concept-item>item</a> has been obtained, its properties
-  can be extracted using the <code title=dom-properties><a href=#dom-properties>properties</a></code> IDL attribute. This
-  attribute returns an <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code>, which can
-  be enumerated to go through each element that adds one or more
-  properties to the item. It can also be indexed by name, which will
-  return an object with a list of the elements that add properties
-  with that name.</p>
+  <p>Once an element representing an <a href=#concept-item title=concept-item>item</a> has been obtained, its
+  properties can be extracted using the <code title=dom-properties><a href=#dom-properties>properties</a></code> IDL
+  attribute. This attribute returns an <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code>, which can be
+  enumerated to go through each element that adds one or more properties to the item. It can also be
+  indexed by name, which will return an object with a list of the elements that add properties with
+  that name.</p>
 
-  <p>Each element that adds a property also has an <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL attribute that returns
-  its value.</p>
+  <p>Each element that adds a property also has an <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL
+  attribute that returns its value.</p>
 
   <div class=example>
 
-   <p>This sample gets the first item of type "http://example.net/user" and
-   then pops up an alert using the "name" property from
-   that item.</p>
+   <p>This sample gets the first item of type "http://example.net/user" and then pops up an alert
+   using the "name" property from that item.</p>
 
    <pre>var user = document.getItems('http://example.net/user')[0];
 alert('Hello ' + user.properties['name'][0].itemValue + '!');</pre>
 
   </div>
 
-  <p>The <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object, when indexed by
-  name in this way, actually returns a <code><a href=#propertynodelist>PropertyNodeList</a></code>
-  object with all the matching properties. The
-  <code><a href=#propertynodelist>PropertyNodeList</a></code> object can be used to obtain all the
-  values at once using <em>its</em> <code title=dom-PropertyNodeList-getValues><a href=#dom-propertynodelist-getvalues>getValues</a></code> method,
-  which returns an array of all the values.</p>
+  <p>The <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object, when indexed by name in this way, actually
+  returns a <code><a href=#propertynodelist>PropertyNodeList</a></code> object with all the matching properties. The
+  <code><a href=#propertynodelist>PropertyNodeList</a></code> object can be used to obtain all the values at once using
+  <em>its</em> <code title=dom-PropertyNodeList-getValues><a href=#dom-propertynodelist-getvalues>getValues</a></code> method, which returns
+  an array of all the values.</p>
 
   <div class=example>
 
    <p>In an earlier example, a "http://example.org/animals#cat" item had two
-   "http://example.com/color" values. This script looks up the first such
-   item and then lists all its values.</p>
+   "http://example.com/color" values. This script looks up the first such item and then lists all
+   its values.</p>
 
    <pre>var cat = document.getItems('http://example.org/animals#cat')[0];
 var colors = cat.properties['http://example.com/color'].getValues();
@@ -63413,15 +63348,13 @@
 
   </div>
 
-  <p>It's also possible to get a list of all the <a href=#property-names>property
-  names</a> using the object's <code title=dom-HTMLPropertiesCollection-names><a href=#dom-htmlpropertiescollection-names>names</a></code> IDL
-  attribute.</p>
+  <p>It's also possible to get a list of all the <a href=#property-names>property names</a> using the object's
+  <code title=dom-HTMLPropertiesCollection-names><a href=#dom-htmlpropertiescollection-names>names</a></code> IDL attribute.</p>
 
   <div class=example>
 
-   <p>This example creates a big list with a nested list for each item
-   on the page, each with of all the property names used in that
-   item.</p>
+   <p>This example creates a big list with a nested list for each item on the page, each with of all
+   the property names used in that item.</p>
 
    <pre>var outer = document.createElement('ul');
 var items = document.getItems();
@@ -63458,8 +63391,7 @@
       <li>http://example.com/color</li>
       <li>img</li>
      </ul></li>
-   </ul><p>(The duplicate occurrence of "http://example.com/color" is not included
-   in the list.)</p>
+   </ul><p>(The duplicate occurrence of "http://example.com/color" is not included in the list.)</p>
 
   </div>
 
@@ -63469,142 +63401,110 @@
 
   <h4 id=the-microdata-model><span class=secno>5.2.1 </span>The microdata model</h4>
 
-  <p>The microdata model consists of groups of name-value pairs known
-  as <a href=#concept-item title=concept-item>items</a>.</p>
+  <p>The microdata model consists of groups of name-value pairs known as <a href=#concept-item title=concept-item>items</a>.</p>
 
-  <p>Each group is known as an <a href=#concept-item title=concept-item>item</a>.
-  Each <a href=#concept-item title=concept-item>item</a> can have <a href=#item-types>item
-  types</a>, a <a href=#global-identifier>global identifier</a> (if the vocabulary
-  specified by the <a href=#item-types>item types</a> <a href=#support-global-identifiers-for-items>support global
-  identifiers for items</a>), and a list of name-value pairs. Each
-  name in the name-value pair is known as a <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a>, and each <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a> has one or more <a href=#concept-property-value title=concept-property-value>values</a>. Each <a href=#concept-property-value title=concept-property-value>value</a> is either a string or
-  itself a group of name-value pairs (an <a href=#concept-item title=concept-item>item</a>). The names are unordered relative
-  to each other, but if a particular name has multiple values, they do
-  have a relative order.</p>
+  <p>Each group is known as an <a href=#concept-item title=concept-item>item</a>. Each <a href=#concept-item title=concept-item>item</a> can have <a href=#item-types>item types</a>, a <a href=#global-identifier>global
+  identifier</a> (if the vocabulary specified by the <a href=#item-types>item types</a> <a href=#support-global-identifiers-for-items>support global
+  identifiers for items</a>), and a list of name-value pairs. Each name in the name-value pair is
+  known as a <a href=#the-properties-of-an-item title="the properties of an item">property</a>, and each <a href=#the-properties-of-an-item title="the
+  properties of an item">property</a> has one or more <a href=#concept-property-value title=concept-property-value>values</a>. Each <a href=#concept-property-value title=concept-property-value>value</a> is either a string or itself a group of name-value
+  pairs (an <a href=#concept-item title=concept-item>item</a>). The names are unordered relative to each other,
+  but if a particular name has multiple values, they do have a relative order.</p>
 
-  <p>An <a href=#concept-item title=concept-item>item</a> is said to be a
-  <dfn id=typed-item>typed item</dfn> when either it has an <a href=#item-types title="item
-  types">item type</a>, or it is the <a href=#concept-property-value title=concept-property-value>value</a> of a <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a> of a <a href=#typed-item>typed item</a>.
-  The <dfn id=relevant-types>relevant types</dfn> for a <a href=#typed-item>typed item</a> is the
-  <a href=#concept-item title=concept-item>item</a>'s <a href=#item-types>item types</a>, if
-  it has one, or else is the <a href=#relevant-types>relevant types</a> of the <a href=#concept-item title=concept-item>item</a> for which it is a <a href=#the-properties-of-an-item title="the
-  properties of an item">property</a>'s <a href=#concept-property-value title=concept-property-value>value</a>.</p>
+  <p>An <a href=#concept-item title=concept-item>item</a> is said to be a <dfn id=typed-item>typed item</dfn> when either it
+  has an <a href=#item-types title="item types">item type</a>, or it is the <a href=#concept-property-value title=concept-property-value>value</a> of a <a href=#the-properties-of-an-item title="the properties of an
+  item">property</a> of a <a href=#typed-item>typed item</a>. The <dfn id=relevant-types>relevant types</dfn> for a
+  <a href=#typed-item>typed item</a> is the <a href=#concept-item title=concept-item>item</a>'s <a href=#item-types>item types</a>,
+  if it has one, or else is the <a href=#relevant-types>relevant types</a> of the <a href=#concept-item title=concept-item>item</a> for which it is a <a href=#the-properties-of-an-item title="the properties of an
+  item">property</a>'s <a href=#concept-property-value title=concept-property-value>value</a>.</p>
 
 
 
   <h4 id=items><span class=secno>5.2.2 </span>Items</h4>
 
-  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an
-  <dfn id=attr-itemscope title=attr-itemscope><code>itemscope</code></dfn> attribute
-  specified. The <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute is a <a href=#boolean-attribute>boolean attribute</a>.</p>
+  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an <dfn id=attr-itemscope title=attr-itemscope><code>itemscope</code></dfn> attribute specified. The <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute is a <a href=#boolean-attribute>boolean attribute</a>.</p>
 
-  <p>An element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute specified creates a new <dfn id=concept-item title=concept-item>item</dfn>, a group of name-value pairs.</p>
+  <p>An element with the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified creates a
+  new <dfn id=concept-item title=concept-item>item</dfn>, a group of name-value pairs.</p>
 
-  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute may have an <dfn id=attr-itemtype title=attr-itemtype><code>itemtype</code></dfn> attribute
-  specified, to give the <a href=#item-types>item types</a> of the <a href=#concept-item title=concept-item>item</a>.</p>
+  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute may have an <dfn id=attr-itemtype title=attr-itemtype><code>itemtype</code></dfn> attribute specified, to give the <a href=#item-types>item
+  types</a> of the <a href=#concept-item title=concept-item>item</a>.</p>
 
-  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute, if
-  specified, must have a value that is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of
-  unique space-separated tokens</a> that are
-  <a href=#case-sensitive>case-sensitive</a>, each of which is a <a href=#valid-url>valid
-  URL</a> that is an <a href=#absolute-url>absolute URL</a>, and all of which
-  are defined to use the same vocabulary. The attribute's value must
+  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute, if specified, must have a value that
+  is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are
+  <a href=#case-sensitive>case-sensitive</a>, each of which is a <a href=#valid-url>valid URL</a> that is an <a href=#absolute-url>absolute
+  URL</a>, and all of which are defined to use the same vocabulary. The attribute's value must
   have at least one token.</p>
 
-  <p>The <dfn id=item-types>item types</dfn> of an <a href=#concept-item title=concept-item>item</a> are the tokens obtained by <a href=#split-a-string-on-spaces title="split a string on spaces">splitting the element's <code title=attr-itemtype>itemtype</code> attribute's value on
-  spaces</a>. If the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code>
-  attribute is missing or parsing it in this way finds no tokens, the
-  <a href=#concept-item title=concept-item>item</a> is said to have no <a href=#item-types>item
-  types</a>.</p>
+  <p>The <dfn id=item-types>item types</dfn> of an <a href=#concept-item title=concept-item>item</a> are the tokens obtained
+  by <a href=#split-a-string-on-spaces title="split a string on spaces">splitting the element's <code title=attr-itemtype>itemtype</code> attribute's value on spaces</a>. If the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute is missing or parsing it in this way finds no
+  tokens, the <a href=#concept-item title=concept-item>item</a> is said to have no <a href=#item-types>item types</a>.</p>
 
-  <p>The <a href=#item-types>item types</a> must all be types defined in <a href=#other-applicable-specifications title="other applicable specifications">applicable
-  specifications</a> and must all be defined to use the same
+  <p>The <a href=#item-types>item types</a> must all be types defined in <a href=#other-applicable-specifications title="other applicable
+  specifications">applicable specifications</a> and must all be defined to use the same
   vocabulary.</p>
 
   <div class=impl>
 
-   <p>Except if otherwise specified by that specification, the <a href=#url title=URL>URLs</a> given as the <a href=#item-types>item types</a> should
-   not be automatically dereferenced.</p>
+   <p>Except if otherwise specified by that specification, the <a href=#url title=URL>URLs</a> given
+   as the <a href=#item-types>item types</a> should not be automatically dereferenced.</p>
 
-   <p class=note>A specification could define that its <a href=#item-types title="item types">item type</a> can be derefenced to provide
-   the user with help information, for example. In fact, vocabulary
-   authors are encouraged to provide useful information at the given
-   <a href=#url>URL</a>.</p>
+   <p class=note>A specification could define that its <a href=#item-types title="item types">item type</a>
+   can be derefenced to provide the user with help information, for example. In fact, vocabulary
+   authors are encouraged to provide useful information at the given <a href=#url>URL</a>.</p>
 
-   <p><a href=#item-types>Item types</a> are opaque identifiers, and user agents
-   must not dereference unknown <a href=#item-types>item types</a>, or otherwise
-   deconstruct them, in order to determine how to process <a href=#concept-item title=concept-item>items</a> that use them.</p>
+   <p><a href=#item-types>Item types</a> are opaque identifiers, and user agents must not dereference unknown
+   <a href=#item-types>item types</a>, or otherwise deconstruct them, in order to determine how to process
+   <a href=#concept-item title=concept-item>items</a> that use them.</p>
 
   </div>
 
-  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute must
-  not be specified on elements that do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
+  <p>The <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute must not be specified on elements
+  that do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
 
-  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code>
-  attribute that references a vocabulary that is defined to
-  <dfn id=support-global-identifiers-for-items>support global identifiers for items</dfn> may also have an
-  <dfn id=attr-itemid title=attr-itemid><code>itemid</code></dfn> attribute
-  specified, to give a global identifier for the <a href=#concept-item title=concept-item>item</a>, so that it can be related to other
-  <a href=#concept-item title=concept-item>items</a> on pages elsewhere on the
-  Web.</p>
+  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute that references a vocabulary that is defined to
+  <dfn id=support-global-identifiers-for-items>support global identifiers for items</dfn> may also have an <dfn id=attr-itemid title=attr-itemid><code>itemid</code></dfn> attribute specified, to give a global identifier for
+  the <a href=#concept-item title=concept-item>item</a>, so that it can be related to other <a href=#concept-item title=concept-item>items</a> on pages elsewhere on the Web.</p>
 
-  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if
-  specified, must have a value that is a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially
-  surrounded by spaces</a>.</p>
+  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if specified, must have a value that is
+  a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially surrounded by spaces</a>.</p>
 
-  <p>The <dfn id=global-identifier>global identifier</dfn> of an <a href=#concept-item title=concept-item>item</a> is the value of its element's <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if it has one, <a href=#resolve-a-url title="resolve a url">resolved</a> relative to the element on
-  which the attribute is specified. If the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute is missing or if
-  resolving it fails, it is said to have no <a href=#global-identifier>global
-  identifier</a>.</p>
+  <p>The <dfn id=global-identifier>global identifier</dfn> of an <a href=#concept-item title=concept-item>item</a> is the value of
+  its element's <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute, if it has one, <a href=#resolve-a-url title="resolve a url">resolved</a> relative to the element on which the attribute is specified.
+  If the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute is missing or if resolving it fails, it
+  is said to have no <a href=#global-identifier>global identifier</a>.</p>
 
-  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute must not be
-  specified on elements that do not have both an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specified, and must
-  not be specified on elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute whose <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specifies a
-  vocabulary that does not <a href=#support-global-identifiers-for-items>support global identifiers for
-  items</a>, as defined by that vocabulary's specification.</p>
+  <p>The <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> attribute must not be specified on elements that do
+  not have both an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute and an <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specified, and must not be specified on elements
+  with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute whose <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> attribute specifies a vocabulary that does not <a href=#support-global-identifiers-for-items>support
+  global identifiers for items</a>, as defined by that vocabulary's specification.</p>
 
-  <p>The exact meaning of a <a href=#global-identifier>global identifier</a> is
-  determined by the vocabulary's specification. It is up to such
-  specifications to define whether multiple items with the same global
-  identifier (whether on the same page or on different pages) are
-  allowed to exist, and what the processing rules for that vocabulary
-  are with respect to handling the case of multiple items with the
-  same ID.</p>
+  <p>The exact meaning of a <a href=#global-identifier>global identifier</a> is determined by the vocabulary's
+  specification. It is up to such specifications to define whether multiple items with the same
+  global identifier (whether on the same page or on different pages) are allowed to exist, and what
+  the processing rules for that vocabulary are with respect to handling the case of multiple items
+  with the same ID.</p>
 
-  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
-  attribute may have an <dfn id=attr-itemref title=attr-itemref><code>itemref</code></dfn> attribute specified,
-  to give a list of additional elements to crawl to find the
-  name-value pairs of the <a href=#concept-item title=concept-item>item</a>.</p>
+  <hr><p>Elements with an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute may have an <dfn id=attr-itemref title=attr-itemref><code>itemref</code></dfn> attribute specified, to give a list of additional
+  elements to crawl to find the name-value pairs of the <a href=#concept-item title=concept-item>item</a>.</p>
 
-  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, if
-  specified, must have a value that is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of
-  unique space-separated tokens</a> that are
-  <a href=#case-sensitive>case-sensitive</a>, consisting of <a href=#concept-id title=concept-ID>IDs</a> of elements in the same <a href=#home-subtree>home
-  subtree</a>.</p>
+  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, if specified, must have a value that
+  is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are
+  <a href=#case-sensitive>case-sensitive</a>, consisting of <a href=#concept-id title=concept-ID>IDs</a> of elements in the
+  same <a href=#home-subtree>home subtree</a>.</p>
 
-  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute must not
-  be specified on elements that do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
+  <p>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute must not be specified on elements that
+  do not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute specified.</p>
 
-  <p class=note>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code>
-  attribute is not part of the microdata data model. It is merely a
-  syntactic construct to aid authors in adding annotations to pages
-  where the data to be annotated does not follow a convenient tree
-  structure. For example, it allows authors to mark up data in a table
-  so that each column defines a separate <a href=#concept-item title=concept-item>item</a>, while keeping the properties in
-  the cells.</p>
+  <p class=note>The <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute is not part of the
+  microdata data model. It is merely a syntactic construct to aid authors in adding annotations to
+  pages where the data to be annotated does not follow a convenient tree structure. For example, it
+  allows authors to mark up data in a table so that each column defines a separate <a href=#concept-item title=concept-item>item</a>, while keeping the properties in the cells.</p>
 
   <div class=example>
 
-   <p>This example shows a simple vocabulary used to describe the
-   products of a model railway manufacturer. The vocabulary has just
-   five property names:</p>
+   <p>This example shows a simple vocabulary used to describe the products of a model railway
+   manufacturer. The vocabulary has just five property names:</p>
 
    <dl><dt>product-code</dt>
     <dd>An integer that names the product in the manufacturer's catalog.</dd>
@@ -63631,9 +63531,8 @@
     <dd>Track pieces</dd>
     <dt>http://md.example.com/lighting</dt>
     <dd>Equipment with lighting</dd>
-   </dl><p>Each <a href=#concept-item title=concept-item>item</a> that uses this
-   vocabulary can be given one or more of these types, depending on
-   what the product is.</p>
+   </dl><p>Each <a href=#concept-item title=concept-item>item</a> that uses this vocabulary can be given one or more
+   of these types, depending on what the product is.</p>
 
    <p>Thus, a locomotive might be marked up as:</p>
 
@@ -63673,51 +63572,41 @@
  <dd itemprop="scale">Z
 </dl></pre>
 
-   <p>Great care is necessary when creating new vocabularies. Often, a
-   hierarchical approach to types can be taken that results in a
-   vocabulary where each item only ever has a single type, which is
-   generally much simpler to manage.</p>
+   <p>Great care is necessary when creating new vocabularies. Often, a hierarchical approach to
+   types can be taken that results in a vocabulary where each item only ever has a single type,
+   which is generally much simpler to manage.</p>
 
   </div>
 
 
   <h4 id=names:-the-itemprop-attribute><span class=secno>5.2.3 </span>Names: the <dfn title=attr-itemprop><code>itemprop</code></dfn> attribute</h4>
 
-  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an
-  <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute specified, if
-  doing so <a href=#the-properties-of-an-item title="the properties of an item">adds one or more
-  properties</a> to one or more <a href=#concept-item title=concept-item>items</a> (as defined below).</p>
+  <p>Every <a href=#html-elements title="HTML elements">HTML element</a> may have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute specified, if doing so <a href=#the-properties-of-an-item title="the properties
+  of an item">adds one or more properties</a> to one or more <a href=#concept-item title=concept-item>items</a> (as defined below).</p>
 
-  <p>The <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute, if
-  specified, must have a value that is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of
-  unique space-separated tokens</a> that are
-  <a href=#case-sensitive>case-sensitive</a>, representing the names of the
-  name-value pairs that it adds. The attribute's value must have at
-  least one token.</p>
+  <p>The <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute, if specified, must have a value that
+  is an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are
+  <a href=#case-sensitive>case-sensitive</a>, representing the names of the name-value pairs that it adds. The
+  attribute's value must have at least one token.</p>
 
   <p>Each token must be either:</p>
 
-  <ul><li>A <a href=#valid-url>valid URL</a> that is an <a href=#absolute-url>absolute URL</a>,
-   or</li>
+  <ul><li>A <a href=#valid-url>valid URL</a> that is an <a href=#absolute-url>absolute URL</a>, or</li>
 
-   <li>If the item is a <a href=#typed-item>typed item</a>: a <dfn id=defined-property-name>defined
-   property name</dfn> allowed in this situation according to the
-   specification that defines the <a href=#relevant-types>relevant types</a> for the
+   <li>If the item is a <a href=#typed-item>typed item</a>: a <dfn id=defined-property-name>defined property name</dfn> allowed in this
+   situation according to the specification that defines the <a href=#relevant-types>relevant types</a> for the
    item, or</li>
 
-   <li>If the item is not a <a href=#typed-item>typed item</a>: a string that
-   contains no U+002E FULL STOP characters (.) and no U+003A COLON
-   characters (:).</li>
+   <li>If the item is not a <a href=#typed-item>typed item</a>: a string that contains no U+002E FULL STOP
+   characters (.) and no U+003A COLON characters (:).</li>
 
-  </ul><p>Specifications that introduce <a href=#defined-property-name title="defined property
-  name">defined property names</a> that are not <a href=#absolute-url title="absolute URL">absolute URLs</a> must ensure all such
-  property names contain no U+002E FULL STOP characters (.), no U+003A
-  COLON characters (:), and no <a href=#space-character title="space character">space
-  characters</a>.</p>
+  </ul><p>Specifications that introduce <a href=#defined-property-name title="defined property name">defined property names</a>
+  that are not <a href=#absolute-url title="absolute URL">absolute URLs</a> must ensure all such property names
+  contain no U+002E FULL STOP characters (.), no U+003A COLON characters (:), and no <a href=#space-character title="space character">space characters</a>.</p>
 
   <p>When an element with an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute <a href=#the-properties-of-an-item title="the
-  properties of an item">adds a property</a> to multiple <a href=#concept-item title=concept-item>items</a>, the requirement above regarding
-  the tokens applies for each <a href=#concept-item title=concept-item>item</a>
+  properties of an item">adds a property</a> to multiple <a href=#concept-item title=concept-item>items</a>,
+  the requirement above regarding the tokens applies for each <a href=#concept-item title=concept-item>item</a>
   individually.</p>
 
   <!--
@@ -63732,23 +63621,17 @@
 
   -->
 
-  <p>The <dfn id=property-names>property names</dfn> of an element are the tokens that
-  the element's <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute
-  is found to contain when its value is <a href=#split-a-string-on-spaces title="split a string on
-  spaces">split on spaces</a>, with the order preserved but with
-  duplicates removed (leaving only the first occurrence of each
-  name).</p>
+  <p>The <dfn id=property-names>property names</dfn> of an element are the tokens that the element's <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is found to contain when its value is <a href=#split-a-string-on-spaces title="split a string on spaces">split on spaces</a>, with the order preserved but with
+  duplicates removed (leaving only the first occurrence of each name).</p>
 
-  <p>Within an <a href=#concept-item title=concept-item>item</a>, the properties
-  are unordered with respect to each other, except for properties with
-  the same name, which are ordered in the order they are given by the
-  algorithm that defines <a href=#the-properties-of-an-item>the properties of an item</a>.</p>
+  <p>Within an <a href=#concept-item title=concept-item>item</a>, the properties are unordered with respect to
+  each other, except for properties with the same name, which are ordered in the order they are
+  given by the algorithm that defines <a href=#the-properties-of-an-item>the properties of an item</a>.</p>
 
   <div class=example>
 
-   <p>In the following example, the "a" property has the values "1"
-   and "2", <em>in that order</em>, but whether the "a" property comes
-   before the "b" property or not is not important:</p>
+   <p>In the following example, the "a" property has the values "1" and "2", <em>in that order</em>,
+   but whether the "a" property comes before the "b" property or not is not important:</p>
 
    <pre><div itemscope>
  <p itemprop="a">1</p>
@@ -63789,16 +63672,15 @@
 
   <h4 id=values><span class=secno>5.2.4 </span>Values</h4>
 
-  <p>The <dfn id=concept-property-value title=concept-property-value>property value</dfn> of a
-  name-value pair added by an element with an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is as given for the
-  first matching case in the following list:</p>
+  <p>The <dfn id=concept-property-value title=concept-property-value>property value</dfn> of a name-value pair added by an
+  element with an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute is as given for the first
+  matching case in the following list:</p>
 
   <dl class=switch><dt>If the element also has an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute</dt>
 
    <dd>
 
-    <p>The value is the <a href=#concept-item title=concept-item>item</a> created
-    by the element.</p>
+    <p>The value is the <a href=#concept-item title=concept-item>item</a> created by the element.</p>
 
    </dd>
 
@@ -63807,39 +63689,33 @@
 
    <dd>
 
-    <p>The value is the value of the element's <code title=attr-content>content</code> attribute, if any, or the
-    empty string if there is no such attribute.</p>
+    <p>The value is the value of the element's <code title=attr-content>content</code> attribute,
+    if any, or the empty string if there is no such attribute.</p>
 
    </dd>
 
 
-   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>,
-   <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>,
+   <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
 
    <dd>
 
-    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from
-    <a href=#resolve-a-url title="resolve a url">resolving</a> the value of the
-    element's <code title="">src</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <a href=#resolve-a-url title="resolve a
-    url">resolving</a> it results in an error.</p>
+    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from <a href=#resolve-a-url title="resolve a
+    url">resolving</a> the value of the element's <code title="">src</code> attribute relative to
+    the element at the time the attribute is set, or the empty string if there is no such attribute
+    or if <a href=#resolve-a-url title="resolve a url">resolving</a> it results in an error.</p>
 
    </dd>
 
 
-   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or
-   <code><a href=#the-link-element>link</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or <code><a href=#the-link-element>link</a></code> element</dt>
 
    <dd>
 
-    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from
-    <a href=#resolve-a-url title="resolve a url">resolving</a> the value of the
-    element's <code title="">href</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <a href=#resolve-a-url title="resolve a
-    url">resolving</a> it results in an error.</p>
+    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from <a href=#resolve-a-url title="resolve a
+    url">resolving</a> the value of the element's <code title="">href</code> attribute relative
+    to the element at the time the attribute is set, or the empty string if there is no such
+    attribute or if <a href=#resolve-a-url title="resolve a url">resolving</a> it results in an error.</p>
 
    </dd>
 
@@ -63848,12 +63724,10 @@
 
    <dd>
 
-    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from
-    <a href=#resolve-a-url title="resolve a url">resolving</a> the value of the
-    element's <code title="">data</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <a href=#resolve-a-url title="resolve a
-    url">resolving</a> it results in an error.</p>
+    <p>The value is the <a href=#absolute-url>absolute URL</a> that results from <a href=#resolve-a-url title="resolve a
+    url">resolving</a> the value of the element's <code title="">data</code> attribute relative
+    to the element at the time the attribute is set, or the empty string if there is no such
+    attribute or if <a href=#resolve-a-url title="resolve a url">resolving</a> it results in an error.</p>
 
    </dd>
 
@@ -63862,8 +63736,8 @@
 
    <dd>
 
-    <p>The value is the value of the element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> attribute, if it has one, or
-    the empty string otherwise.</p>
+    <p>The value is the value of the element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> attribute,
+    if it has one, or the empty string otherwise.</p>
 
    </dd>
 
@@ -63885,121 +63759,98 @@
 
    </dd>
 
-  </dl><p>The <dfn id=url-property-elements>URL property elements</dfn> are the <code><a href=#the-a-element>a</a></code>,
-  <code><a href=#the-area-element>area</a></code>, <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-  <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-link-element>link</a></code>,
-  <code><a href=#the-object-element>object</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, and
-  <code><a href=#the-video-element>video</a></code> elements.</p>
+  </dl><p>The <dfn id=url-property-elements>URL property elements</dfn> are the <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>,
+  <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-link-element>link</a></code>,
+  <code><a href=#the-object-element>object</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, and <code><a href=#the-video-element>video</a></code> elements.</p>
 
-  <p>If a property's <a href=#concept-property-value title=concept-property-value>value</a>, as defined by the
-  property's definition, is an <a href=#absolute-url>absolute URL</a>, the property
-  must be specified using a <a href=#url-property-elements title="URL property elements">URL
-  property element</a>.</p>
+  <p>If a property's <a href=#concept-property-value title=concept-property-value>value</a>, as defined by the property's
+  definition, is an <a href=#absolute-url>absolute URL</a>, the property must be specified using a <a href=#url-property-elements title="URL property elements">URL property element</a>.</p>
 
-  <p class=note>These requirements do not apply just because a
-  property value happens to match the syntax for a URL. They only
-  apply if the property is explicitly defined as taking such a
+  <p class=note>These requirements do not apply just because a property value happens to match the
+  syntax for a URL. They only apply if the property is explicitly defined as taking such a
   value.</p>
 
-  <p class=example>For example, a book about the first moon landing
-  <!-- 1969-07-20 --> could be called "mission:moon". A "title"
-  property from a vocabulary that defines a title as being a string
-  would not expect the title to be given in an <code><a href=#the-a-element>a</a></code> element,
-  even though it looks like a <a href=#url>URL</a>. On the other hand, if
-  there was a (rather narrowly scoped!) vocabulary for "books whose
-  titles look like URLs" which had a "title" property defined to take
-  a URL, then the property <em>would</em> expect the title to be given
-  in an <code><a href=#the-a-element>a</a></code> element (or one of the other <a href=#url-property-elements>URL property
-  elements</a>), because of the requirement above.</p>
+  <p class=example>For example, a book about the first moon landing <!-- 1969-07-20 --> could be
+  called "mission:moon". A "title" property from a vocabulary that defines a title as being a string
+  would not expect the title to be given in an <code><a href=#the-a-element>a</a></code> element, even though it looks like a
+  <a href=#url>URL</a>. On the other hand, if there was a (rather narrowly scoped!) vocabulary for
+  "books whose titles look like URLs" which had a "title" property defined to take a URL, then the
+  property <em>would</em> expect the title to be given in an <code><a href=#the-a-element>a</a></code> element (or one of the
+  other <a href=#url-property-elements>URL property elements</a>), because of the requirement above.</p>
 
 
   <div class=impl>
 
   <h4 id=associating-names-with-items><span class=secno>5.2.5 </span>Associating names with items</h4>
 
-  <p>To find <dfn id=the-properties-of-an-item>the properties of an item</dfn> defined by the
-  element <var title="">root</var>, the user agent must run the
-  following steps. These steps are also used to flag <a href=#microdata-error title="microdata error">microdata errors</a>.</p>
+  <p>To find <dfn id=the-properties-of-an-item>the properties of an item</dfn> defined by the element <var title="">root</var>,
+  the user agent must run the following steps. These steps are also used to flag <a href=#microdata-error title="microdata error">microdata errors</a>.</p>
 
-  <ol><li><p>Let <var title="">results</var>, <var title="">memory</var>,
-   and <var title="">pending</var> be empty lists of
-   elements.</li>
+  <ol><li><p>Let <var title="">results</var>, <var title="">memory</var>, and <var title="">pending</var> be empty lists of elements.</li>
 
    <li><p>Add the element <var title="">root</var> to <var title="">memory</var>.</li>
 
-   <li><p>Add the child elements of <var title="">root</var>, if any,
-   to <var title="">pending</var>.</li>
+   <li><p>Add the child elements of <var title="">root</var>, if any, to <var title="">pending</var>.</li>
 
-   <li><p>If <var title="">root</var> has an <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, <a href=#split-a-string-on-spaces title="split a
-   string on spaces">split the value of that <code title=attr-itemref>itemref</code> attribute on spaces</a>. For
-   each resulting token <var title="">ID</var>, if there is an element
-   in the <a href=#home-subtree>home subtree</a> of <var title="">root</var> with
-   the <a href=#concept-id title=concept-ID>ID</a> <var title="">ID</var>, then
-   add the first such element to <var title="">pending</var>.</li>
+   <li><p>If <var title="">root</var> has an <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute,
+   <a href=#split-a-string-on-spaces title="split a string on spaces">split the value of that <code title=attr-itemref>itemref</code> attribute on spaces</a>. For each resulting token <var title="">ID</var>, if there is an element in the <a href=#home-subtree>home subtree</a> of <var title="">root</var> with the <a href=#concept-id title=concept-ID>ID</a> <var title="">ID</var>, then add
+   the first such element to <var title="">pending</var>.</li>
 
-   <li><p><i>Loop</i>: If <var title="">pending</var> is empty, jump
-   to the step labeled <i>end of loop</i>.</li>
+   <li><p><i>Loop</i>: If <var title="">pending</var> is empty, jump to the step labeled <i>end of
+   loop</i>.</li>
 
-   <li><p>Remove an element from <var title="">pending</var> and let
-   <var title="">current</var> be that element.</li>
+   <li><p>Remove an element from <var title="">pending</var> and let <var title="">current</var> be
+   that element.</li>
 
-   <li><p>If <var title="">current</var> is already in <var title="">memory</var>, there is a <a href=#microdata-error>microdata error</a>;
-   return to the step labeled <i>loop</i>.</li>
+   <li><p>If <var title="">current</var> is already in <var title="">memory</var>, there is a
+   <a href=#microdata-error>microdata error</a>; return to the step labeled <i>loop</i>.</li>
 
    <li><p>Add <var title="">current</var> to <var title="">memory</var>.</li>
 
-   <li><p>If <var title="">current</var> does not
-   have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute,
-   then: add all the child elements of <var title="">current</var> to
-   <var title="">pending</var>.</li>
+   <li><p>If <var title="">current</var> does not have an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute, then: add all the child elements of <var title="">current</var> to <var title="">pending</var>.</li>
 
-   <li><p>If <var title="">current</var> has an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute specified and has
-   one or more <a href=#property-names>property names</a>, then add <var title="">current</var> to <var title="">results</var>.</li>
+   <li><p>If <var title="">current</var> has an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>
+   attribute specified and has one or more <a href=#property-names>property names</a>, then add <var title="">current</var> to <var title="">results</var>.</li>
 
    <li><p>Return to the step labeled <i>loop</i>.</li>
 
-   <li><p><i>End of loop</i>: Sort <var title="">results</var> in
-   <a href=#tree-order>tree order</a>.</li>
+   <li><p><i>End of loop</i>: Sort <var title="">results</var> in <a href=#tree-order>tree order</a>.</li>
 
    <li><p>Return <var title="">results</var>.</li>
 
-  </ol><p>A document must not contain any <a href=#concept-item title=concept-item>items</a> for which the algorithm to find
-  <a href=#the-properties-of-an-item>the properties of an item</a> finds any <dfn id=microdata-error title="microdata error">microdata errors</dfn>.</p>
+  </ol><p>A document must not contain any <a href=#concept-item title=concept-item>items</a> for which the algorithm
+  to find <a href=#the-properties-of-an-item>the properties of an item</a> finds any <dfn id=microdata-error title="microdata error">microdata
+  errors</dfn>.</p>
 
-  <p>An <a href=#concept-item title=concept-item>item</a> is a <dfn id=top-level-microdata-items title="top-level microdata items">top-level microdata item</dfn> if
-  its element does not have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute.</p>
+  <p>An <a href=#concept-item title=concept-item>item</a> is a <dfn id=top-level-microdata-items title="top-level microdata items">top-level
+  microdata item</dfn> if its element does not have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>
+  attribute.</p>
 
 <!--(this is currently redundant with "requirement itemprop" below)
-  <p>An <span title="concept-item">item</span> is a <dfn title="used
-  microdata items">used microdata item</dfn> if it is a <span
-  title="top-level microdata items">top-level microdata item</span>,
-  or if it has an <code title="attr-itemprop">itemprop</code>
-  attribute and would be <span title="the properties of an item">found
-  to be the property</span> of an <span
-  title="concept-item">item</span> that is itself a <span title="used
-  microdata items">used microdata item</span>.</p>
+  <p>An <span title="concept-item">item</span> is a <dfn title="used microdata items">used microdata
+  item</dfn> if it is a <span title="top-level microdata items">top-level microdata item</span>, or
+  if it has an <code title="attr-itemprop">itemprop</code> attribute and would be <span title="the
+  properties of an item">found to be the property</span> of an <span
+  title="concept-item">item</span> that is itself a <span title="used microdata items">used
+  microdata item</span>.</p>
 
-  <p>All <span title="concept-item">items</span> in a document must be
-  <span>used microdata items</span>.</p>
+  <p>All <span title="concept-item">items</span> in a document must be <span>used microdata
+  items</span>.</p>
 -->
 
-  <p>All <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attributes in a
-  <code><a href=#document>Document</a></code> must be such that there are no cycles in the
-  graph formed from representing each <a href=#concept-item title=concept-item>item</a> in the <code><a href=#document>Document</a></code> as a
-  node in the graph and each <a href=#the-properties-of-an-item title="the properties of an
-  item">property</a> of an item whose <a href=#concept-property-value title=concept-property-value>value</a> is another item as an
-  edge in the graph connecting those two items.</p>
+  <p>All <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attributes in a <code><a href=#document>Document</a></code> must be
+  such that there are no cycles in the graph formed from representing each <a href=#concept-item title=concept-item>item</a> in the <code><a href=#document>Document</a></code> as a node in the graph and each
+  <a href=#the-properties-of-an-item title="the properties of an item">property</a> of an item whose <a href=#concept-property-value title=concept-property-value>value</a> is another item as an edge in the graph connecting
+  those two items.</p>
 
   <!-- "requirement itemprop" (see above) -->
-  <p>A document must not contain any elements that have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute that would not be
-  found to be a property of any of the <a href=#concept-item title=concept-item>items</a> in that document were their <a href=#the-properties-of-an-item title="the properties of an item">properties</a> all to be
-  determined.</p>
+  <p>A document must not contain any elements that have an <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute that would not be found to be a property of any of
+  the <a href=#concept-item title=concept-item>items</a> in that document were their <a href=#the-properties-of-an-item title="the
+  properties of an item">properties</a> all to be determined.</p>
 
   <div class=example>
 
-   <p>In this example, a single license statement is applied to two
-   works, using <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> from the
-   items representing the works:</p>
+   <p>In this example, a single license statement is applied to two works, using <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> from the items representing the works:</p>
 
    <pre><!DOCTYPE HTML>
 <html>
@@ -64024,7 +63875,8 @@
  </body>
 </html></pre>
 
-   <p>The above results in two items with the type "<code title="">http://n.whatwg.org/work</code>", one with:</p>
+   <p>The above results in two items with the type "<code title="">http://n.whatwg.org/work</code>",
+   one with:</p>
 
    <dl class=brief><dt>work
     <dd><code title="">images/house.jpeg</code>
@@ -64047,12 +63899,9 @@
 
   <h4 id=microdata-and-other-namespaces><span class=secno>5.2.6 </span>Microdata and other namespaces</h4>
 
-  <p>Currently, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>,
-  <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>, and other microdata
-  attributes are only defined for <a href=#html-elements>HTML elements</a>. This
-  means that attributes with the literal names "<code title="">itemscope</code>", "<code title="">itemprop</code>", etc,
-  do not cause microdata processing to occur on elements in other
-  namespaces, such as SVG.</p>
+  <p>Currently, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>, <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>, and other microdata attributes are only defined for
+  <a href=#html-elements>HTML elements</a>. This means that attributes with the literal names "<code title="">itemscope</code>", "<code title="">itemprop</code>", etc, do not cause microdata
+  processing to occur on elements in other namespaces, such as SVG.</p>
 
   <div class=example>
 
@@ -64071,7 +63920,9 @@
 
    <dd>
 
-    <p>Returns a <code><a href=#nodelist>NodeList</a></code> of the elements in the <code><a href=#document>Document</a></code> that create <a href=#concept-item title=concept-item>items</a>, that are not part of other <a href=#concept-item title=concept-item>items</a>, and that are of the types given in the argument, if any are listed.</p>
+    <p>Returns a <code><a href=#nodelist>NodeList</a></code> of the elements in the <code><a href=#document>Document</a></code> that create
+    <a href=#concept-item title=concept-item>items</a>, that are not part of other <a href=#concept-item title=concept-item>items</a>, and that are of the types given in the argument, if any are
+    listed.</p>
 
     <p>The <var title="">types</var> argument is interpreted as a space-separated list of types.</p>
 
@@ -64082,9 +63933,8 @@
    <dd>
 
     <p>If the element has an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute, returns an
-    <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object with all the element's
-    properties. Otherwise, an empty
-    <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object.</p>
+    <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object with all the element's properties. Otherwise, an
+    empty <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> object.</p>
 
    </dd>
 
@@ -64094,55 +63944,43 @@
 
     <p>Returns the element's <a href=#concept-property-value title=concept-property-value>value</a>.</p>
 
-    <p>Can be set, to change the element's <a href=#concept-property-value title=concept-property-value>value</a>. Setting the <a href=#concept-property-value title=concept-property-value>value</a> when the element has
-    no <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute or when
-    the element's value is an <a href=#concept-item title=concept-item>item</a>
-    throws an <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception.</p>
+    <p>Can be set, to change the element's <a href=#concept-property-value title=concept-property-value>value</a>.
+    Setting the <a href=#concept-property-value title=concept-property-value>value</a> when the element has no <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute or when the element's value is an <a href=#concept-item title=concept-item>item</a> throws an <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception.</p>
 
    </dd>
 
   </dl><div class=impl>
 
-  <p>The <dfn id=dom-document-getitems title=dom-document-getItems><code>document.getItems(<var title="">typeNames</var>)</code></dfn> method takes an optional
-  string that contains an <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique
-  space-separated tokens</a> that are <a href=#case-sensitive>case-sensitive</a>,
-  representing types. When called, the method must return a
-  <a href=#live>live</a> <code><a href=#nodelist>NodeList</a></code> object containing all the
-  elements in the document, in <a href=#tree-order>tree order</a>, that are each
-  <a href=#top-level-microdata-items>top-level microdata items</a> whose <a href=#item-types title="item
-  types">types</a> include all the types specified in the method's
-  argument, having obtained the types by <a href=#split-a-string-on-spaces title="split a string
-  on spaces">splitting the string on spaces</a>. If there are no
-  tokens specified in the argument, or if the argument is missing,
-  then the method must return a <code><a href=#nodelist>NodeList</a></code> containing all
-  the <a href=#top-level-microdata-items>top-level microdata items</a> in the document. When the
-  method is invoked on a <code><a href=#document>Document</a></code> object again with the
-  same argument, the user agent may return the same object as the
-  object returned by the earlier call. In other cases, a new
+  <p>The <dfn id=dom-document-getitems title=dom-document-getItems><code>document.getItems(<var title="">typeNames</var>)</code></dfn> method takes an optional string that contains an
+  <a href=#unordered-set-of-unique-space-separated-tokens>unordered set of unique space-separated tokens</a> that are <a href=#case-sensitive>case-sensitive</a>,
+  representing types. When called, the method must return a <a href=#live>live</a> <code><a href=#nodelist>NodeList</a></code>
+  object containing all the elements in the document, in <a href=#tree-order>tree order</a>, that are each
+  <a href=#top-level-microdata-items>top-level microdata items</a> whose <a href=#item-types title="item types">types</a> include all the
+  types specified in the method's argument, having obtained the types by <a href=#split-a-string-on-spaces title="split a string
+  on spaces">splitting the string on spaces</a>. If there are no tokens specified in the
+  argument, or if the argument is missing, then the method must return a <code><a href=#nodelist>NodeList</a></code>
+  containing all the <a href=#top-level-microdata-items>top-level microdata items</a> in the document. When the method is
+  invoked on a <code><a href=#document>Document</a></code> object again with the same argument, the user agent may return
+  the same object as the object returned by the earlier call. In other cases, a new
   <code><a href=#nodelist>NodeList</a></code> object must be returned.</p>
 
-  <p>The <dfn id=dom-itemscope title=dom-itemScope><code>itemScope</code></dfn> IDL
-  attribute on <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a>
-  the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> content attribute.
-  The <dfn id=dom-itemtype title=dom-itemType><code>itemType</code></dfn> IDL
-  attribute on <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a>
-  the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> content attribute.
-  The <dfn id=dom-itemid title=dom-itemId><code>itemId</code></dfn> IDL attribute
-  on <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> content attribute. The <dfn id=dom-itemprop title=dom-itemProp><code>itemProp</code></dfn> IDL attribute on
-  <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> content attribute. The <dfn id=dom-itemref title=dom-itemRef><code>itemRef</code></dfn> IDL attribute on
-  <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> content attribute.</p>
+  <p>The <dfn id=dom-itemscope title=dom-itemScope><code>itemScope</code></dfn> IDL attribute on <a href=#html-elements>HTML
+  elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>
+  content attribute. The <dfn id=dom-itemtype title=dom-itemType><code>itemType</code></dfn> IDL attribute on
+  <a href=#html-elements>HTML elements</a> must <a href=#reflect>reflect</a> the <code title=attr-itemtype><a href=#attr-itemtype>itemtype</a></code> content attribute. The <dfn id=dom-itemid title=dom-itemId><code>itemId</code></dfn> IDL attribute on <a href=#html-elements>HTML elements</a> must
+  <a href=#reflect>reflect</a> the <code title=attr-itemid><a href=#attr-itemid>itemid</a></code> content attribute. The <dfn id=dom-itemprop title=dom-itemProp><code>itemProp</code></dfn> IDL attribute on <a href=#html-elements>HTML elements</a> must
+  <a href=#reflect>reflect</a> the <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> content attribute. The <dfn id=dom-itemref title=dom-itemRef><code>itemRef</code></dfn> IDL attribute on <a href=#html-elements>HTML elements</a> must
+  <a href=#reflect>reflect</a> the <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> content attribute.</p>
 
-  <p>The <dfn id=dom-properties title=dom-properties><code>properties</code></dfn> IDL
-  attribute on <a href=#html-elements>HTML elements</a> must return an
-  <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> rooted at the
-  <code><a href=#document>Document</a></code> node, whose filter matches only elements that
-  are <a href=#the-properties-of-an-item title="the properties of an item">the properties of the
-  item</a> created by the element on which the attribute was
-  invoked, while that element is an <a href=#concept-item title=concept-item>item</a>, and matches nothing the rest of
-  the time.</p>
+  <p>The <dfn id=dom-properties title=dom-properties><code>properties</code></dfn> IDL attribute on <a href=#html-elements>HTML
+  elements</a> must return an <code><a href=#htmlpropertiescollection>HTMLPropertiesCollection</a></code> rooted at the
+  <code><a href=#document>Document</a></code> node, whose filter matches only elements that are <a href=#the-properties-of-an-item title="the
+  properties of an item">the properties of the item</a> created by the element on which the
+  attribute was invoked, while that element is an <a href=#concept-item title=concept-item>item</a>, and
+  matches nothing the rest of the time.</p>
 
-  <p>The <dfn id=dom-itemvalue title=dom-itemValue><code>itemValue</code></dfn> IDL
-  attribute's behavior depends on the element, as follows:</p>
+  <p>The <dfn id=dom-itemvalue title=dom-itemValue><code>itemValue</code></dfn> IDL attribute's behavior depends on
+  the element, as follows:</p>
 
   <dl><dt>If the element has no <code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute</dt>
 
@@ -64152,68 +63990,65 @@
 
    <dt>If the element has an <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code> attribute</dt>
 
-   <dd><p>The attribute must return the element itself on getting and
-   must throw an <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception on
-   setting.</p>
+   <dd><p>The attribute must return the element itself on getting and must throw an
+   <code><a href=#invalidaccesserror>InvalidAccessError</a></code> exception on setting.</p>
 
 
    <dt>If the element is a <code><a href=#the-meta-element>meta</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> content
-   attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> content attribute.</dd>
 
 
-   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>,
-   <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-audio-element>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>,
+   <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, or <code><a href=#the-video-element>video</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">src</code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title="">src</code> content attribute.</dd>
 
 
-   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or
-   <code><a href=#the-link-element>link</a></code> element</dt>
+   <dt>If the element is an <code><a href=#the-a-element>a</a></code>, <code><a href=#the-area-element>area</a></code>, or <code><a href=#the-link-element>link</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">href</code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title="">href</code> content attribute.</dd>
 
 
    <dt>If the element is an <code><a href=#the-object-element>object</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">data</code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title="">data</code> content attribute.</dd>
 
 
    <dt>If the element is a <code><a href=#the-data-element>data</a></code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> content attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the
+   element's <code title=attr-data-value><a href=#attr-data-value>value</a></code> content attribute.</dd>
 
 
    <dt>If the element is a <code><a href=#the-time-element>time</a></code> element</dt>
 
-   <dd><p>On getting, if the element has a <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content attribute, the
-   IDL attribute must return that content attribute's value;
-   otherwise, it must return the element's <code><a href=#textcontent>textContent</a></code>.
-   On setting, the IDL attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content
-   attribute.</dd>
+   <dd><p>On getting, if the element has a <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content
+   attribute, the IDL attribute must return that content attribute's value; otherwise, it must
+   return the element's <code><a href=#textcontent>textContent</a></code>. On setting, the IDL attribute must act as it would
+   if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content attribute.</dd>
 
 
    <dt>Otherwise</dt>
 
-   <dd><p>The attribute must act the same as the element's
-   <code><a href=#textcontent>textContent</a></code> attribute.</dd>
+   <dd><p>The attribute must act the same as the element's <code><a href=#textcontent>textContent</a></code>
+   attribute.</dd>
 
-  </dl><p>When the <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL
-  attribute is <a href=#reflect title=reflect>reflecting</a> a content
-  attribute or acting like the element's <code><a href=#textcontent>textContent</a></code>
-  attribute, the user agent must, on setting, convert the new value to
-  the IDL <code title="">DOMString</code> value before using it
-  according to the mappings described above.</p>
+  </dl><p>When the <code title=dom-itemValue><a href=#dom-itemvalue>itemValue</a></code> IDL attribute is <a href=#reflect title=reflect>reflecting</a> a content attribute or acting like the element's
+  <code><a href=#textcontent>textContent</a></code> attribute, the user agent must, on setting, convert the new value to the
+  IDL <code title="">DOMString</code> value before using it according to the mappings described
+  above.</p>
 
   </div>
 
   <div class=example>
 
-   <p>In this example, a script checks to see if a particular element
-   <var title="">element</var> is declaring a particular property, and
-   if it is, it increments a counter:</p>
+   <p>In this example, a script checks to see if a particular element <var title="">element</var> is
+   declaring a particular property, and if it is, it increments a counter:</p>
 
    <pre>if (element.itemProp.contains('color'))
   count += 1;</pre>
@@ -64222,9 +64057,8 @@
 
   <div class=example>
 
-   <p>This script iterates over each of the values of an element's
-   <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, calling a
-   function for each referenced element:</p>
+   <p>This script iterates over each of the values of an element's <code title=attr-itemref><a href=#attr-itemref>itemref</a></code> attribute, calling a function for each referenced
+   element:</p>
 
    <pre>for (var index = 0; index < element.itemRef.length; index += 1)
   process(document.getElementById(element.itemRef[index]));</pre>
@@ -64232,21 +64066,22 @@
   </div>
 
 
-  <h3 id=mdvocabs><span class=secno>5.4 </span>Microdata vocabularies</h3>
+  <h3 id=mdvocabs><span class=secno>5.4 </span>Sample microdata vocabularies</h3>
 
+  <p>The vocabularies in this section are primarily intended to demonstrate how a vocabulary is
+  specified, though they are also usable in their own right.</p>
+
+
   <h4 id=vcard><span class=secno>5.4.1 </span>vCard</h4>
 
-  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vcard title=md-vcard><code>http://microformats.org/profile/hcard</code></dfn>
-  represents a person's or organization's contact information.</p>
+  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vcard title=md-vcard><code>http://microformats.org/profile/hcard</code></dfn> represents a person's or
+  organization's contact information.</p>
 
-  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for
-  items</a>.</p>
+  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for items</a>.</p>
 
-  <p>The following are the type's <a href=#defined-property-name title="defined property
-  name">defined property names</a>. They are based on the
-  vocabulary defined in the vCard 4.0 specification and its
-  extensions, where more information on how to interpret the values
-  can be found. <a href=#refsRFC6350>[RFC6350]</a></p>
+  <p>The following are the type's <a href=#defined-property-name title="defined property name">defined property names</a>.
+  They are based on the vocabulary defined in the vCard 4.0 specification and its extensions, where
+  more information on how to interpret the values can be found. <a href=#refsRFC6350>[RFC6350]</a></p>
 
   <dl><dt><dfn id=md-vcard-kind title=md-vcard-kind><code>kind</code></dfn></dt>
 
@@ -65224,11 +65059,9 @@
    <!-- update this when http://www.iana.org/assignments/vcard-elements/vcard-elements.xml#parameter-values is updated -->
   </dl><h5 id=conversion-to-vcard><span class=secno>5.4.1.1 </span>Conversion to vCard</h5>
 
-  <p>Given a list of nodes <var title="">nodes</var> in a
-  <code><a href=#document>Document</a></code>, a user agent must run the following algorithm
-  to <dfn id=extracting-a-vcard title="extracting a vCard">extract any vCard data
-  represented by those nodes</dfn> (only the first vCard is
-  returned):</p>
+  <p>Given a list of nodes <var title="">nodes</var> in a <code><a href=#document>Document</a></code>, a user agent must
+  run the following algorithm to <dfn id=extracting-a-vcard title="extracting a vCard">extract any vCard data represented
+  by those nodes</dfn> (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 <a href=#item-types title="item
    types">item type</a> <code title=md-vcard><a href=#md-vcard>http://microformats.org/profile/hcard</a></code>, then
@@ -65535,11 +65368,8 @@
    <li><p><a href=#add-a-vcard-line>Add a vCard line</a> with the type "<code title="">END</code>" and the value "<code title="">VCARD</code>"
    to <var title="">output</var>.</li>
 
-  </ol><p>When the above algorithm says that the user agent is to <dfn id=add-a-vcard-line>add
-  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:</p>
+  </ol><p>When the above algorithm says that the user agent is to <dfn id=add-a-vcard-line>add 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:</p>
 
   <ol><li><p>Let <var title="">line</var> be an empty string.
 
@@ -65594,8 +65424,8 @@
 
    <li><p>Append a U+000A LINE FEED character (LF) to <var title="">output</var>.</li>
 
-  </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
+  </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:</p>
 
   <ol><li><p>Let <var title="">value</var> be the empty string.</li>
@@ -65621,8 +65451,8 @@
 
    <li><p>Return <var title="">value</var>.</li>
 
-  </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
+  </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:</p>
 
   <ol><li><p>If there are no properties named <var title="">subname</var>
@@ -65637,8 +65467,8 @@
    string</a> given by the <a href=#concept-property-value title=concept-property-value>value</a> of the first property
    named <var title="">subname</var> in <var title="">subitem</var>.</li>
 
-  </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
+  </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:</p>
 
   <ol><li><p>Prefix every U+005C REVERSE SOLIDUS character (\) in <var title="">value</var> with another U+005C REVERSE SOLIDUS character
@@ -65662,10 +65492,10 @@
 
    <li><p>Return the mutated <var title="">value</var>.</li>
 
-  </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>http://microformats.org/profile/hcard</a></code> <a href=#item-types title="item types">item type</a> and <a href=#defined-property-name title="defined
-  property name">defined property names</a>.</p> <!-- of course
-  since vcard doesn't define error handling, this is somewhat
+  </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>http://microformats.org/profile/hcard</a></code>
+  <a href=#item-types title="item types">item type</a> and <a href=#defined-property-name title="defined property name">defined property
+  names</a>.</p> <!-- of course since vcard doesn't define error handling, this is somewhat
   problematic. -->
 
 
@@ -65676,8 +65506,7 @@
 
   <div class=example>
 
-   <p>Here is a long example vCard for a fictional character called
-   "Jack Bauer":</p>
+   <p>Here is a long example vCard for a fictional character called "Jack Bauer":</p>
 
    <pre><section id="jack" itemscope itemtype="http://microformats.org/profile/hcard">
  <h1 itemprop="fn">
@@ -65724,17 +65553,15 @@
  </ins>
 </section></pre>
 
-   <p>The odd line wrapping is needed because newlines are meaningful
-   in microdata: newlines would be preserved in a conversion to, for
-   example, the vCard format.</p>
+   <p>The odd line wrapping is needed because newlines are meaningful in microdata: newlines would
+   be preserved in a conversion to, for example, the vCard format.</p>
 
   </div>
 
   <div class=example>
 
-   <p>This example shows a site's contact details (using the
-   <code><a href=#the-address-element>address</a></code> element) containing an address with two street
-   components:</p>
+   <p>This example shows a site's contact details (using the <code><a href=#the-address-element>address</a></code> element)
+   containing an address with two street components:</p>
 
    <pre><address itemscope itemtype="http://microformats.org/profile/hcard">
  <strong itemprop="fn"><span itemprop="n" itemscope><span itemprop="given-name">Alfred</span>
@@ -65751,20 +65578,17 @@
 
   <div class=example>
 
-   <p>The vCard vocabulary can be used to just mark up people's
-   names:</p>
+   <p>The vCard vocabulary can be used to just mark up people's names:</p>
 
    <pre><span itemscope itemtype="http://microformats.org/profile/hcard"
 ><span itemprop=fn><span itemprop="n" itemscope><span itemprop="given-name"
 >George</span> <span itemprop="family-name">Washington</span></span
 ></span></span></pre>
 
-   <p>This creates a single item with a two name-value pairs, one with
-   the name "fn" and the value "George Washington", and the other with
-   the name "n" and a second item as its value, the second item having
-   the two name-value pairs "given-name" and "family-name" with the
-   values "George" and "Washington" respectively. This is defined to
-   map to the following vCard:</p>
+   <p>This creates a single item with a two name-value pairs, one with the name "fn" and the value
+   "George Washington", and the other with the name "n" and a second item as its value, the second
+   item having the two name-value pairs "given-name" and "family-name" with the values "George" and
+   "Washington" respectively. This is defined to map to the following vCard:</p>
 
    <pre>BEGIN:VCARD
 PROFILE:VCARD
@@ -65779,20 +65603,17 @@
 
   <h4 id=vevent><span class=secno>5.4.2 </span>vEvent</h4>
 
-  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vevent title=md-vevent><code>http://microformats.org/profile/hcalendar#vevent</code></dfn>
-  represents an event.</p>
+  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-vevent title=md-vevent><code>http://microformats.org/profile/hcalendar#vevent</code></dfn> represents
+  an event.</p>
 
-  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for
-  items</a>.</p>
+  <p>This vocabulary does not <a href=#support-global-identifiers-for-items>support global identifiers for items</a>.</p>
 
-  <p>The following are the type's <a href=#defined-property-name title="defined property
-  name">defined property names</a>. They are based on the
-  vocabulary defined in the iCalendar specification, where more
-  information on how to interpret the values can be found. <a href=#refsRFC2445>[RFC2445]</a></p>
+  <p>The following are the type's <a href=#defined-property-name title="defined property name">defined property names</a>.
+  They are based on the vocabulary defined in the iCalendar specification, where more information on
+  how to interpret the values can be found. <a href=#refsRFC2445>[RFC2445]</a></p>
 
-  <p class=note>Only the parts of the iCalendar vocabulary relating
-  to events are used here; this vocabulary cannot express a complete
-  iCalendar instance.</p>
+  <p class=note>Only the parts of the iCalendar vocabulary relating to events are used here; this
+  vocabulary cannot express a complete iCalendar instance.</p>
 
   <dl><dt><dfn id=md-vevent-attach title=md-vevent-attach><code>attach</code></dfn></dt>
 
@@ -66315,9 +66136,8 @@
 
   </ol><h5 id=conversion-to-icalendar><span class=secno>5.4.2.1 </span>Conversion to iCalendar</h5>
 
-  <p>Given a list of nodes <var title="">nodes</var> in a
-  <code><a href=#document>Document</a></code>, a user agent must run the following algorithm
-  to <dfn id=extracting-vevent-data title="extracting vEvent data">extract any vEvent data
+  <p>Given a list of nodes <var title="">nodes</var> in a <code><a href=#document>Document</a></code>, a user agent must
+  run the following algorithm to <dfn id=extracting-vevent-data title="extracting vEvent data">extract any vEvent data
   represented by those 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>http://microformats.org/profile/hcalendar#vevent</a></code>,
@@ -66407,10 +66227,9 @@
 
    <li><p><a href=#add-an-icalendar-line>Add an iCalendar line</a> with the type "<code title="">END</code>" and the value "<code title="">VCALENDAR</code>" to <var title="">output</var>.</li>
 
-  </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
-  optionally an annotation, to a string <var title="">output</var>, it
-  must run the following steps:</p>
+  </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 optionally
+  an annotation, to a string <var title="">output</var>, it must run the following steps:</p>
 
   <ol><li><p>Let <var title="">line</var> be an empty string.</li>
 
@@ -66480,13 +66299,10 @@
 
    <li><p>Append a U+000A LINE FEED character (LF) to <var title="">output</var>.</li>
 
-  </ol><p class=note>This algorithm can generate invalid iCalendar
-  output, if the input does not conform to the rules described for the
-  <code title=md-vevent><a href=#md-vevent>http://microformats.org/profile/hcalendar#vevent</a></code>
-  <a href=#item-types title="item types">item type</a> and <a href=#defined-property-name title="defined property
-  name">defined property names</a>.</p> <!-- of course since
-  iCalendar doesn't define error handling, this is somewhat
-  problematic. -->
+  </ol><p class=note>This algorithm can generate invalid iCalendar output, if the input does not
+  conform to the rules described for the <code title=md-vevent><a href=#md-vevent>http://microformats.org/profile/hcalendar#vevent</a></code> <a href=#item-types title="item
+  types">item type</a> and <a href=#defined-property-name title="defined property name">defined property names</a>.</p>
+  <!-- of course since iCalendar doesn't define error handling, this is somewhat problematic. -->
 
 
 
@@ -66498,8 +66314,7 @@
 
   <div class=example>
 
-   <p>Here is an example of a page that uses the vEvent vocabulary to
-   mark up an event:</p>
+   <p>Here is an example of a page that uses the vEvent vocabulary to mark up an event:</p>
 
    <pre><body itemscope itemtype="http://microformats.org/profile/hcalendar#vevent">
  ...
@@ -66580,13 +66395,12 @@
 
   <h4 id=licensing-works><span class=secno>5.4.3 </span>Licensing works</h4>
 
-  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-work title=md-work><code>http://n.whatwg.org/work</code></dfn>
-  represents a work (e.g. an article, an image, a video, a song,
-  etc). This type is primarily intended to allow authors to include
+  <p>An item with the <a href=#item-types title="item types">item type</a> <dfn id=md-work title=md-work><code>http://n.whatwg.org/work</code></dfn> represents a work (e.g. an article, an
+  image, a video, a song, etc). This type is primarily intended to allow authors to include
   licensing information for works.</p>
 
-  <p>The following are the type's <a href=#defined-property-name title="defined property
-  name">defined property names</a>.</p>
+  <p>The following are the type's <a href=#defined-property-name title="defined property name">defined property
+  names</a>.</p>
 
   <dl><dt><dfn id=md-work-work title=md-work-work><code>work</code></dfn></dt>
 
@@ -66653,9 +66467,8 @@
 
   <div class=example>
 
-   <p>This example shows an embedded image entitled <cite>My
-   Pond</cite>, licensed under the Creative Commons Attribution-Share
-   Alike 3.0 United States License and the MIT license
+   <p>This example shows an embedded image entitled <cite>My Pond</cite>, licensed under the
+   Creative Commons Attribution-Share Alike 3.0 United States License and the MIT license
    simultaneously.</p>
 
    <pre><figure <strong>itemscope itemtype="http://n.whatwg.org/work"</strong>>
@@ -66680,10 +66493,9 @@
 
   <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><a href=#document>Document</a></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>:</p>
+  <p>Given a list of nodes <var title="">nodes</var> in a <code><a href=#document>Document</a></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>:</p>
 
   <ol><li><p>Let <var title="">result</var> be an empty object.</li>
 
@@ -66702,13 +66514,13 @@
    dedicated escape sequence), and with a lowercase "<code title="">e</code>" used, when appropriate, in the representation of
    any numbers. <a href=#refsJSON>[JSON]</a></li>
 
-  </ol><p class=note>This algorithm returns an object with a single
-  property that is an array, instead of just returning an array, so
-  that it is possible to extend the algorithm in the future if
+  </ol><p class=note>This algorithm returns an object with a single property that is an array, instead
+  of just returning an array, so that it is possible to extend the algorithm in the future if
   necessary.</p>
 
-  <p>When the user agent is to <dfn id=get-the-object>get the object</dfn> for an item
-  <var title="">item</var>, optionally with a list of elements <var title="">memory</var>, it must run the following substeps:</p>
+  <p>When the user agent is to <dfn id=get-the-object>get the object</dfn> for an item <var title="">item</var>,
+  optionally with a list of elements <var title="">memory</var>, it must run the following
+  substeps:</p>
 
   <ol><li><p>Let <var title="">result</var> be an empty object.</li>
 
@@ -66765,14 +66577,17 @@
   </ol></div>
 
 
+
+
+<!--TOPIC:HTML-->
+
   <h2 id=browsers><span class=secno>6 </span>Loading Web pages</h2>
 
   <div class=impl>
 
-  <p>This section describes features that apply most directly to Web
-  browsers. Having said that, except where specified otherwise, the
-  requirements defined in this section <em>do</em> apply to all user
-  agents, whether they are Web browsers or not.</p>
+  <p>This section describes features that apply most directly to Web browsers. Having said that,
+  except where specified otherwise, the requirements defined in this section <em>do</em> apply to
+  all user agents, whether they are Web browsers or not.</p>
 
   </div>
 
@@ -66780,65 +66595,51 @@
 
   <h3 id=windows><span class=secno>6.1 </span>Browsing contexts</h3>
 
-  <p>A <dfn id=browsing-context>browsing context</dfn> is an environment in which
-  <code><a href=#document>Document</a></code> objects are presented to the user.</p>
+  <p>A <dfn id=browsing-context>browsing context</dfn> is an environment in which <code><a href=#document>Document</a></code> objects are
+  presented to the user.</p>
 
-  <p class=note>A tab or window in a Web browser typically contains
-  a <a href=#browsing-context>browsing context</a>, as does an <code><a href=#the-iframe-element>iframe</a></code><span class=impl> or <code><a href=#frame>frame</a></code>s in a
+  <p class=note>A tab or window in a Web browser typically contains a <a href=#browsing-context>browsing
+  context</a>, as does an <code><a href=#the-iframe-element>iframe</a></code><span class=impl> or <code><a href=#frame>frame</a></code>s in a
   <code><a href=#frameset>frameset</a></code></span>.</p>
 
-  <p>Each <a href=#browsing-context>browsing context</a> has a corresponding
-  <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+  <p>Each <a href=#browsing-context>browsing context</a> has a corresponding <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
 
-  <p>A <a href=#browsing-context>browsing context</a> has a <a href=#session-history>session
-  history</a>, which lists the <code><a href=#document>Document</a></code> objects that
-  that <a href=#browsing-context>browsing context</a> has presented, is presenting, or
-  will present. At any time, one <code><a href=#document>Document</a></code> in each
-  <a href=#browsing-context>browsing context</a> is designated the <dfn id=active-document>active
-  document</dfn>. A <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing
-  context</a> is that <a href=#browsing-context>browsing context</a> whose
-  <a href=#session-history>session history</a> contains the <code><a href=#document>Document</a></code>, if
-  any. (A <code><a href=#document>Document</a></code> created using an API such as <code title=dom-DOMImplementation-createDocument><a href=#dom-domimplementation-createdocument>createDocument()</a></code>
-  has no <a href=#browsing-context>browsing context</a>.)</p>
+  <p>A <a href=#browsing-context>browsing context</a> has a <a href=#session-history>session history</a>, which lists the
+  <code><a href=#document>Document</a></code> objects that that <a href=#browsing-context>browsing context</a> has presented, is
+  presenting, or will present. At any time, one <code><a href=#document>Document</a></code> in each <a href=#browsing-context>browsing
+  context</a> is designated the <dfn id=active-document>active document</dfn>. A <code><a href=#document>Document</a></code>'s
+  <a href=#browsing-context>browsing context</a> is that <a href=#browsing-context>browsing context</a> whose <a href=#session-history>session
+  history</a> contains the <code><a href=#document>Document</a></code>, if any. (A <code><a href=#document>Document</a></code> created using
+  an API such as <code title=dom-DOMImplementation-createDocument><a href=#dom-domimplementation-createdocument>createDocument()</a></code> has no
+  <a href=#browsing-context>browsing context</a>.)</p>
 
-  <p>Each <code><a href=#document>Document</a></code> is associated with a
-  <code><a href=#window>Window</a></code> object. A <a href=#browsing-context>browsing context</a>'s
-  <code><a href=#windowproxy>WindowProxy</a></code> object forwards everything to the
-  <a href=#browsing-context>browsing context</a>'s <a href=#active-document>active document</a>'s
-  <code><a href=#window>Window</a></code> object.</p>
+  <p>Each <code><a href=#document>Document</a></code> is associated with a <code><a href=#window>Window</a></code> object. A <a href=#browsing-context>browsing
+  context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object forwards everything to the <a href=#browsing-context>browsing
+  context</a>'s <a href=#active-document>active document</a>'s <code><a href=#window>Window</a></code> object.</p>
 
-  <p class=note>In general, there is a 1-to-1 mapping from the
-  <code><a href=#window>Window</a></code> object to the <code><a href=#document>Document</a></code> object.
-  There are two exceptions. First, a <code><a href=#window>Window</a></code> can be reused
-  for the presentation of a second <code><a href=#document>Document</a></code> in the same
-  <a href=#browsing-context>browsing context</a>, such that the mapping is then 1-to-2.
-  This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial
-  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> to another, with
-  <a href=#replacement-enabled>replacement enabled</a>. Second, a <code><a href=#document>Document</a></code>
-  can end up being reused for several <code><a href=#window>Window</a></code> objects when
-  the <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> method is
-  used, such that the mapping is then many-to-1.</p>
+  <p class=note>In general, there is a 1-to-1 mapping from the <code><a href=#window>Window</a></code> object to the
+  <code><a href=#document>Document</a></code> object. There are two exceptions. First, a <code><a href=#window>Window</a></code> can be reused
+  for the presentation of a second <code><a href=#document>Document</a></code> in the same <a href=#browsing-context>browsing context</a>,
+  such that the mapping is then 1-to-2. This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code>
+  to another, with <a href=#replacement-enabled>replacement enabled</a>. Second, a <code><a href=#document>Document</a></code> can end up
+  being reused for several <code><a href=#window>Window</a></code> objects when the <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> method is used, such that the mapping is then
+  many-to-1.</p>
 
-  <p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a
-  <a href=#browsing-context>browsing context</a> associated with it. In particular,
-  data mining tools are likely to never instantiate browsing
+  <p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a <a href=#browsing-context>browsing context</a>
+  associated with it. In particular, data mining tools are likely to never instantiate browsing
   contexts.</p>
 
-  <hr><p>A <a href=#browsing-context>browsing context</a> can have a <dfn id=creator-browsing-context>creator browsing
-  context</dfn>, the <a href=#browsing-context>browsing context</a> that was
-  responsible for its creation. If a <a href=#browsing-context>browsing context</a> has
-  a <a href=#parent-browsing-context>parent browsing context</a>, then that is its
-  <a href=#creator-browsing-context>creator browsing context</a>. Otherwise, if the
-  <a href=#browsing-context>browsing context</a> has an <a href=#opener-browsing-context>opener browsing
-  context</a>, then <em>that</em> is its <a href=#creator-browsing-context>creator browsing
-  context</a>. Otherwise, the <a href=#browsing-context>browsing context</a> has no
-  <a href=#creator-browsing-context>creator browsing context</a>.</p>
+  <hr><p>A <a href=#browsing-context>browsing context</a> can have a <dfn id=creator-browsing-context>creator browsing context</dfn>, the
+  <a href=#browsing-context>browsing context</a> that was responsible for its creation. If a <a href=#browsing-context>browsing
+  context</a> has a <a href=#parent-browsing-context>parent browsing context</a>, then that is its <a href=#creator-browsing-context>creator browsing
+  context</a>. Otherwise, if the <a href=#browsing-context>browsing context</a> has an <a href=#opener-browsing-context>opener browsing
+  context</a>, then <em>that</em> is its <a href=#creator-browsing-context>creator browsing context</a>. Otherwise, the
+  <a href=#browsing-context>browsing context</a> has no <a href=#creator-browsing-context>creator browsing context</a>.</p>
 
-  <p>If a <a href=#browsing-context>browsing context</a> <var title="">A</var> has a
-  <a href=#creator-browsing-context>creator browsing context</a>, then the
-  <code><a href=#document>Document</a></code> that was the <a href=#active-document>active document</a> of
-  that <a href=#creator-browsing-context>creator browsing context</a> at the time <var title="">A</var> was created is the <dfn id=creator-document>creator
-  <code>Document</code></dfn>.</p>
+  <p>If a <a href=#browsing-context>browsing context</a> <var title="">A</var> has a <a href=#creator-browsing-context>creator browsing
+  context</a>, then the <code><a href=#document>Document</a></code> that was the <a href=#active-document>active document</a> of that
+  <a href=#creator-browsing-context>creator browsing context</a> at the time <var title="">A</var> was created is the
+  <dfn id=creator-document>creator <code>Document</code></dfn>.</p>
 
   <div class=impl>
 
@@ -66852,147 +66653,110 @@
   <code><a href=#document>Document</a></code> is created, the user agent must <a href=#implement-the-sandboxing>implement the sandboxing</a> for
   it.</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 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>origin</a> and
-  <a href=#effective-script-origin>effective script origin</a> of the <code><a href=#about:blank>about:blank</a></code>
-  <code><a href=#document>Document</a></code> are set when the <code><a href=#document>Document</a></code> is
-  created. If the new <a href=#browsing-context>browsing context</a> has a
-  <a href=#creator-browsing-context>creator browsing context</a>, then the <a href=#origin>origin</a>
-  of the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#origin>origin</a>
-  of the <a href=#creator-document>creator <code>Document</code></a> and the
-  <a href=#effective-script-origin>effective script origin</a> of the <code><a href=#about:blank>about:blank</a></code>
-  <code><a href=#document>Document</a></code> is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#effective-script-origin>effective
-  script origin</a> of the <a href=#creator-document>creator
-  <code>Document</code></a>. Otherwise, the <a href=#origin>origin</a> of
-  the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is a globally
-  unique identifier assigned when the new <a href=#browsing-context>browsing
-  context</a> is created and the <a href=#effective-script-origin>effective script
-  origin</a> of the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code>
-  is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to
-  its <a href=#origin>origin</a>.</p>
+  <p id=about-blank-origin>The <a href=#origin>origin</a> and <a href=#effective-script-origin>effective script origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> are set when the <code><a href=#document>Document</a></code> is created.
+  If the new <a href=#browsing-context>browsing context</a> has a <a href=#creator-browsing-context>creator browsing context</a>, then the
+  <a href=#origin>origin</a> of the <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#origin>origin</a> of the <a href=#creator-document>creator
+  <code>Document</code></a> and the <a href=#effective-script-origin>effective script origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to the <a href=#effective-script-origin>effective script origin</a> of the
+  <a href=#creator-document>creator <code>Document</code></a>. Otherwise, the <a href=#origin>origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is a globally unique identifier assigned when the
+  new <a href=#browsing-context>browsing context</a> is created and the <a href=#effective-script-origin>effective script origin</a> of the
+  <code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> is initially an <a href=#concept-origin-alias title=concept-origin-alias>alias</a> to its <a href=#origin>origin</a>.</p>
 
   </div>
 
 
   <h4 id=nested-browsing-contexts><span class=secno>6.1.1 </span>Nested browsing contexts</h4>
 
-  <p>Certain elements (for example, <code><a href=#the-iframe-element>iframe</a></code> elements) can
-  instantiate further <a href=#browsing-context title="browsing context">browsing
-  contexts</a>. These are called <dfn id=nested-browsing-context title="nested browsing
-  context">nested browsing contexts</dfn>. If a browsing context <var title="">P</var> has a <code><a href=#document>Document</a></code> <var title="">D</var>
-  with an element <var title="">E</var> that nests another browsing
-  context <var title="">C</var> inside it, then <var title="">C</var>
-  is said to be <dfn id=browsing-context-nested-through title="browsing context nested through">nested
-  through</dfn> <var title="">D</var>, and <var title="">E</var> is
-  said to be the <dfn id=browsing-context-container>browsing context container</dfn> of <var title="">C</var>. If the <a href=#browsing-context-container>browsing context container</a>
-  element <var title="">E</var> is <a href=#in-a-document title="in a
-  Document">in</a> the <code><a href=#document>Document</a></code> <var title="">D</var>,
-  then <var title="">P</var> is said to be the <dfn id=parent-browsing-context>parent browsing
-  context</dfn> of <var title="">C</var> and <var title="">C</var> is
-  said to be a <dfn id=child-browsing-context>child browsing context</dfn> of <var title="">P</var>. Otherwise, the <a href=#nested-browsing-context>nested browsing
-  context</a> <var title="">C</var> has no <a href=#parent-browsing-context>parent browsing
-  context</a>.</p>
+  <p>Certain elements (for example, <code><a href=#the-iframe-element>iframe</a></code> elements) can instantiate further <a href=#browsing-context title="browsing context">browsing contexts</a>. These are called <dfn id=nested-browsing-context title="nested browsing
+  context">nested browsing contexts</dfn>. If a browsing context <var title="">P</var> has a
+  <code><a href=#document>Document</a></code> <var title="">D</var> with an element <var title="">E</var> that nests
+  another browsing context <var title="">C</var> inside it, then <var title="">C</var> is said to be
+  <dfn id=browsing-context-nested-through title="browsing context nested through">nested through</dfn> <var title="">D</var>, and <var title="">E</var> is said to be the <dfn id=browsing-context-container>browsing context container</dfn> of <var title="">C</var>.
+  If the <a href=#browsing-context-container>browsing context container</a> element <var title="">E</var> is <a href=#in-a-document title="in a
+  Document">in</a> the <code><a href=#document>Document</a></code> <var title="">D</var>, then <var title="">P</var> is
+  said to be the <dfn id=parent-browsing-context>parent browsing context</dfn> of <var title="">C</var> and <var title="">C</var> is said to be a <dfn id=child-browsing-context>child browsing context</dfn> of <var title="">P</var>.
+  Otherwise, the <a href=#nested-browsing-context>nested browsing context</a> <var title="">C</var> has no <a href=#parent-browsing-context>parent
+  browsing context</a>.</p>
 
-  <p>A browsing context <var title="">A</var> is said to be an <dfn id=ancestor-browsing-context title="ancestor browsing context">ancestor</dfn> of a browsing
-  context <var title="">B</var> if there exists a browsing context
-  <var title="">A'</var> that is a <a href=#child-browsing-context>child browsing context</a>
-  of <var title="">A</var> and that is itself an <a href=#ancestor-browsing-context title="ancestor
-  browsing context">ancestor</a> of <var title="">B</var>, or if
-  there is a browsing context <var title="">P</var> that is a
-  <a href=#child-browsing-context>child browsing context</a> of <var title="">A</var> and
-  that is the <a href=#parent-browsing-context>parent browsing context</a> of <var title="">B</var>.</p>
+  <p>A browsing context <var title="">A</var> is said to be an <dfn id=ancestor-browsing-context title="ancestor browsing
+  context">ancestor</dfn> of a browsing context <var title="">B</var> if there exists a browsing
+  context <var title="">A'</var> that is a <a href=#child-browsing-context>child browsing context</a> of <var title="">A</var> and that is itself an <a href=#ancestor-browsing-context title="ancestor browsing context">ancestor</a> of
+  <var title="">B</var>, or if there is a browsing context <var title="">P</var> that is a
+  <a href=#child-browsing-context>child browsing context</a> of <var title="">A</var> and that is the <a href=#parent-browsing-context>parent browsing
+  context</a> of <var title="">B</var>.</p>
 
-  <p>A browsing context that is not a <a href=#nested-browsing-context>nested browsing
-  context</a> has no <a href=#parent-browsing-context>parent browsing context</a>, and is
-  the <dfn id=top-level-browsing-context>top-level browsing context</dfn> of all the browsing
-  contexts for which it is an <a href=#ancestor-browsing-context>ancestor browsing
-  context</a>.</p>
+  <p>A browsing context that is not a <a href=#nested-browsing-context>nested browsing context</a> has no <a href=#parent-browsing-context>parent
+  browsing context</a>, and is the <dfn id=top-level-browsing-context>top-level browsing context</dfn> of all the browsing
+  contexts for which it is an <a href=#ancestor-browsing-context>ancestor browsing context</a>.</p>
 
-  <p>The transitive closure of <a href=#parent-browsing-context title="parent browsing
-  context">parent browsing contexts</a> for a <a href=#nested-browsing-context>nested browsing
-  context</a> gives the list of <a href=#ancestor-browsing-context title="ancestor browsing
+  <p>The transitive closure of <a href=#parent-browsing-context title="parent browsing context">parent browsing contexts</a>
+  for a <a href=#nested-browsing-context>nested browsing context</a> gives the list of <a href=#ancestor-browsing-context title="ancestor browsing
   context">ancestor browsing contexts</a>.</p>
 
-  <p>The <dfn id=list-of-the-descendant-browsing-contexts>list of the descendant browsing contexts</dfn> of a
-  <code><a href=#document>Document</a></code> <var title="">d</var> is the (ordered) list
-  returned by the following algorithm:</p>
+  <p>The <dfn id=list-of-the-descendant-browsing-contexts>list of the descendant browsing contexts</dfn> of a <code><a href=#document>Document</a></code> <var title="">d</var> is the (ordered) list returned by the following algorithm:</p>
 
   <ol><li><p>Let <var title="">list</var> be an empty list.</li>
 
    <li>
 
-    <p>For each <a href=#child-browsing-context>child browsing context</a> of <var title="">d</var> that is <a href=#browsing-context-nested-through title="browsing context nested
-    through">nested through</a> an element that is <a href=#in-a-document title="in
-    a document">in the <code>Document</code></a> <var title="">d</var>, in the <a href=#tree-order>tree order</a> of the elements
-    nesting those <a href=#browsing-context title="browsing context">browsing
+    <p>For each <a href=#child-browsing-context>child browsing context</a> of <var title="">d</var> that is <a href=#browsing-context-nested-through title="browsing context nested through">nested through</a> an element that is <a href=#in-a-document title="in
+    a document">in the <code>Document</code></a> <var title="">d</var>, in the <a href=#tree-order>tree
+    order</a> of the elements nesting those <a href=#browsing-context title="browsing context">browsing
     contexts</a>, run these substeps:</p>
 
-    <ol><li><p>Append that <a href=#child-browsing-context>child browsing context</a> to the
-     list <var title="">list</var>.</p>
+    <ol><li><p>Append that <a href=#child-browsing-context>child browsing context</a> to the list <var title="">list</var>.</p>
 
-     <li><p>Append the <a href=#list-of-the-descendant-browsing-contexts>list of the descendant browsing
-     contexts</a> of the <a href=#active-document>active document</a> of that
-     <a href=#child-browsing-context>child browsing context</a> to the list <var title="">list</var>.</li>
+     <li><p>Append the <a href=#list-of-the-descendant-browsing-contexts>list of the descendant browsing contexts</a> of the <a href=#active-document>active
+     document</a> of that <a href=#child-browsing-context>child browsing context</a> to the list <var title="">list</var>.</li>
 
     </ol></li>
 
    <li><p>Return the constructed <var title="">list</var>.</li>
 
-  </ol><p>A <code><a href=#document>Document</a></code> is said to be <dfn id=fully-active>fully active</dfn>
-  when it is the <a href=#active-document>active document</a> of its <a href=#browsing-context>browsing
-  context</a>, and either its browsing context is a <a href=#top-level-browsing-context>top-level
-  browsing context</a>, or it has a <a href=#parent-browsing-context>parent browsing
-  context</a> and the <code><a href=#document>Document</a></code> <a href=#browsing-context-nested-through title="browsing
-  context nested through">through which</a> it is <a href=#nested-browsing-context title="nested browsing context">nested</a> is itself <a href=#fully-active>fully
-  active</a>.</p>
+  </ol><p>A <code><a href=#document>Document</a></code> is said to be <dfn id=fully-active>fully active</dfn> when it is the <a href=#active-document>active
+  document</a> of its <a href=#browsing-context>browsing context</a>, and either its browsing context is a
+  <a href=#top-level-browsing-context>top-level browsing context</a>, or it has a <a href=#parent-browsing-context>parent browsing context</a> and the
+  <code><a href=#document>Document</a></code> <a href=#browsing-context-nested-through title="browsing context nested through">through which</a> it is
+  <a href=#nested-browsing-context title="nested browsing context">nested</a> is itself <a href=#fully-active>fully active</a>.</p>
 
-  <p>Because they are nested through an element, <a href=#child-browsing-context title="child
-  browsing context">child browsing contexts</a> are always tied to
-  a specific <code><a href=#document>Document</a></code> in their <a href=#parent-browsing-context>parent browsing
-  context</a>. User agents must not allow the user to interact with
-  <a href=#child-browsing-context title="child browsing context">child browsing contexts</a>
-  of elements that are in <code><a href=#document>Document</a></code>s that are not
-  themselves <a href=#fully-active>fully active</a>.</p>
+  <p>Because they are nested through an element, <a href=#child-browsing-context title="child browsing context">child browsing
+  contexts</a> are always tied to a specific <code><a href=#document>Document</a></code> in their <a href=#parent-browsing-context>parent browsing
+  context</a>. User agents must not allow the user to interact with <a href=#child-browsing-context title="child browsing
+  context">child browsing contexts</a> of elements that are in <code><a href=#document>Document</a></code>s that are
+  not themselves <a href=#fully-active>fully active</a>.</p>
 
-  <p>A <a href=#nested-browsing-context>nested browsing context</a> can have a <a href=#seamless-browsing-context-flag>seamless
-  browsing context flag</a> set, if it is embedded through an
-  <code><a href=#the-iframe-element>iframe</a></code> element with a <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute.</p>
+  <p>A <a href=#nested-browsing-context>nested browsing context</a> can have a <a href=#seamless-browsing-context-flag>seamless browsing context flag</a>
+  set, if it is embedded through an <code><a href=#the-iframe-element>iframe</a></code> element with a <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute.</p>
 
   <p>A <a href=#nested-browsing-context>nested browsing context</a> can be put into a <dfn id=delaying-load-events-mode>delaying <code title=event-load>load</code> events mode</dfn>. This is used when it is <a href=#navigate title=navigate>navigated</a>, to <a href=#delay-the-load-event>delay the load event</a> of the <a href=#browsing-context-container>browsing
   context container</a> <code><a href=#the-iframe-element>iframe</a></code> element before the new <code><a href=#document>Document</a></code> is
   created.</p>
 
 <!--(There's no current way for this to happen, since removing an iframe from a document discards its browsing context)
-  <p class="note">A <span>nested browsing context</span> can in some
-  cases be taken out of its <span>parent browsing context</span> (e.g.
-  if an <code>iframe</code> element is removed from its
-  <code>Document</code>). In such a situation, the <span>nested
-  browsing context</span> has no <span>parent browsing context</span>,
-  but it still has the same <span>browsing context container</span>
-  and is still <span title="browsing context nested through">nested
-  through</span> that element's <code>Document</code>. Such a
-  <span>nested browsing context</span> is <em>not</em> a
-  <span>top-level browsing context</span>, and cannot contain
-  <code>Document</code>s that are <span>fully active</span>.
-  Furthermore, if a <span>browsing context container</span> (such as
-  an <code>iframe</code>) is moved to another <code>Document</code>,
-  then the <span>parent browsing context</span> of its <span>nested
-  browsing context</span> will change.</p>
+  <p class="note">A <span>nested browsing context</span> can in some cases be taken out of its
+  <span>parent browsing context</span> (e.g. if an <code>iframe</code> element is removed from its
+  <code>Document</code>). In such a situation, the <span>nested browsing context</span> has no
+  <span>parent browsing context</span>, but it still has the same <span>browsing context
+  container</span> and is still <span title="browsing context nested through">nested through</span>
+  that element's <code>Document</code>. Such a <span>nested browsing context</span> is <em>not</em>
+  a <span>top-level browsing context</span>, and cannot contain <code>Document</code>s that are
+  <span>fully active</span>. Furthermore, if a <span>browsing context container</span> (such as an
+  <code>iframe</code>) is moved to another <code>Document</code>, then the <span>parent browsing
+  context</span> of its <span>nested browsing context</span> will change.</p>
 -->
 
-  <p>The <dfn id=document-family>document family</dfn> of a <a href=#browsing-context>browsing context</a>
-  consists of the union of all the <code><a href=#document>Document</a></code> objects in
-  that <a href=#browsing-context>browsing context</a>'s <a href=#session-history>session history</a>
-  and the <a href=#document-family title="document family">document families</a> of
-  all those <code><a href=#document>Document</a></code> objects. The <a href=#document-family>document
-  family</a> of a <code><a href=#document>Document</a></code> object consists of the
-  union of all the <a href=#document-family title="document family">document
-  families</a> of the <a href=#browsing-context title="browsing context">browsing
-  contexts</a> that are <a href=#browsing-context-nested-through title="browsing context nested
-  through">nested through</a> the <code><a href=#document>Document</a></code> object.</p>
+  <p>The <dfn id=document-family>document family</dfn> of a <a href=#browsing-context>browsing context</a> consists of the union of all
+  the <code><a href=#document>Document</a></code> objects in that <a href=#browsing-context>browsing context</a>'s <a href=#session-history>session
+  history</a> and the <a href=#document-family title="document family">document families</a> of all those
+  <code><a href=#document>Document</a></code> objects. The <a href=#document-family>document family</a> of a <code><a href=#document>Document</a></code> object
+  consists of the union of all the <a href=#document-family title="document family">document families</a> of the
+  <a href=#browsing-context title="browsing context">browsing contexts</a> that are <a href=#browsing-context-nested-through title="browsing context
+  nested through">nested through</a> the <code><a href=#document>Document</a></code> object.</p>
 
 
   <h5 id=navigating-nested-browsing-contexts-in-the-dom><span class=secno>6.1.1.1 </span>Navigating nested browsing contexts in the DOM</h5>
@@ -67027,43 +66791,33 @@
 
   </dl><div class=impl>
 
-  <p>The <dfn id=dom-top title=dom-top><code>top</code></dfn> IDL attribute on
-  the <code><a href=#window>Window</a></code> object of a <code><a href=#document>Document</a></code> in a
-  <a href=#browsing-context>browsing context</a> <var title="">b</var> must return the
-  <code><a href=#windowproxy>WindowProxy</a></code> object of its <a href=#top-level-browsing-context>top-level browsing
-  context</a> (which would be its own <code><a href=#windowproxy>WindowProxy</a></code>
-  object if it was a <a href=#top-level-browsing-context>top-level browsing context</a> itself),
-  if it has one, or its own <code><a href=#windowproxy>WindowProxy</a></code> object otherwise
-  (e.g. if it was a detached <a href=#nested-browsing-context>nested browsing
-  context</a>).</p>
+  <p>The <dfn id=dom-top title=dom-top><code>top</code></dfn> IDL attribute on the <code><a href=#window>Window</a></code> object
+  of a <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> <var title="">b</var> must return
+  the <code><a href=#windowproxy>WindowProxy</a></code> object of its <a href=#top-level-browsing-context>top-level browsing context</a> (which would be
+  its own <code><a href=#windowproxy>WindowProxy</a></code> object if it was a <a href=#top-level-browsing-context>top-level browsing context</a>
+  itself), if it has one, or its own <code><a href=#windowproxy>WindowProxy</a></code> object otherwise (e.g. if it was a
+  detached <a href=#nested-browsing-context>nested browsing context</a>).</p>
 
-  <p>The <dfn id=dom-parent title=dom-parent><code>parent</code></dfn> IDL
-  attribute on the <code><a href=#window>Window</a></code> object of a
-  <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> <var title="">b</var> must return the <code><a href=#windowproxy>WindowProxy</a></code> object of
-  the <a href=#parent-browsing-context>parent browsing context</a>, if there is one (i.e. if
-  <var title="">b</var> is a <a href=#child-browsing-context>child browsing context</a>), or
-  the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
-  context</a> <var title="">b</var> itself, otherwise (i.e. if it
-  is a <a href=#top-level-browsing-context>top-level browsing context</a> or a detached
-  <a href=#nested-browsing-context>nested browsing context</a>).</p>
+  <p>The <dfn id=dom-parent title=dom-parent><code>parent</code></dfn> IDL attribute on the <code><a href=#window>Window</a></code>
+  object of a <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> <var title="">b</var> must
+  return the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#parent-browsing-context>parent browsing context</a>, if there
+  is one (i.e. if <var title="">b</var> is a <a href=#child-browsing-context>child browsing context</a>), or the
+  <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing context</a> <var title="">b</var> itself,
+  otherwise (i.e. if it is a <a href=#top-level-browsing-context>top-level browsing context</a> or a detached <a href=#nested-browsing-context>nested
+  browsing context</a>).</p>
 
-  <p>The <dfn id=dom-frameelement title=dom-frameElement><code>frameElement</code></dfn>
-  IDL attribute on the <code><a href=#window>Window</a></code> object of a
-  <code><a href=#document>Document</a></code> <var title="">d</var>, on getting, must run
+  <p>The <dfn id=dom-frameelement title=dom-frameElement><code>frameElement</code></dfn> IDL attribute on the
+  <code><a href=#window>Window</a></code> object of a <code><a href=#document>Document</a></code> <var title="">d</var>, on getting, must run
   the following algorithm:</p>
 
-  <ol><li><p>If <var title="">d</var> is not a <code><a href=#document>Document</a></code> in a
-   <a href=#nested-browsing-context>nested browsing context</a>, return null and abort these
-   steps.</li>
+  <ol><li><p>If <var title="">d</var> is not a <code><a href=#document>Document</a></code> in a <a href=#nested-browsing-context>nested browsing
+   context</a>, return null and abort these steps.</li>
 
-   <li><p>If the <a href=#browsing-context-container>browsing context container</a>'s
-   <code><a href=#document>Document</a></code> does not have the <a href=#same-origin title="same
-   origin">same</a> <a href=#effective-script-origin>effective script origin</a> as the
-   <a href=#entry-script>entry script</a>, then throw a <code><a href=#securityerror>SecurityError</a></code>
-   exception.</li>
+   <li><p>If the <a href=#browsing-context-container>browsing context container</a>'s <code><a href=#document>Document</a></code> does not have the
+   <a href=#same-origin title="same origin">same</a> <a href=#effective-script-origin>effective script origin</a> as the <a href=#entry-script>entry
+   script</a>, then throw a <code><a href=#securityerror>SecurityError</a></code> exception.</li>
 
-   <li><p>Otherwise, return the <a href=#browsing-context-container>browsing context
-   container</a> for <var title="">b</var>.</li>
+   <li><p>Otherwise, return the <a href=#browsing-context-container>browsing context container</a> for <var title="">b</var>.</li>
 
   </ol></div>
 
@@ -67071,31 +66825,24 @@
 
   <h4 id=auxiliary-browsing-contexts><span class=secno>6.1.2 </span>Auxiliary browsing contexts</h4>
 
-  <p>It is possible to create new browsing contexts that are related
-  to a <a href=#top-level-browsing-context>top-level browsing context</a> without being nested
-  through an element. Such browsing contexts are called <dfn id=auxiliary-browsing-context title="auxiliary browsing context">auxiliary browsing
-  contexts</dfn>. Auxiliary browsing contexts are always <a href=#top-level-browsing-context title="top-level browsing context">top-level browsing
-  contexts</a>.</p>
+  <p>It is possible to create new browsing contexts that are related to a <a href=#top-level-browsing-context>top-level browsing
+  context</a> without being nested through an element. Such browsing contexts are called <dfn id=auxiliary-browsing-context title="auxiliary browsing context">auxiliary browsing contexts</dfn>. Auxiliary browsing contexts
+  are always <a href=#top-level-browsing-context title="top-level browsing context">top-level browsing contexts</a>.</p>
 
-  <p>An <a href=#auxiliary-browsing-context>auxiliary browsing context</a> has an <dfn id=opener-browsing-context>opener
-  browsing context</dfn>, which is the <a href=#browsing-context>browsing context</a>
-  from which the <a href=#auxiliary-browsing-context>auxiliary browsing context</a> was
+  <p>An <a href=#auxiliary-browsing-context>auxiliary browsing context</a> has an <dfn id=opener-browsing-context>opener browsing context</dfn>, which is
+  the <a href=#browsing-context>browsing context</a> from which the <a href=#auxiliary-browsing-context>auxiliary browsing context</a> was
   created.</p>
 
 
   <h5 id=navigating-auxiliary-browsing-contexts-in-the-dom><span class=secno>6.1.2.1 </span>Navigating auxiliary browsing contexts in the DOM</h5>
 
-  <p>The <dfn id=dom-opener title=dom-opener><code>opener</code></dfn> IDL
-  attribute on the <code><a href=#window>Window</a></code> object, on getting, must return
-  the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
-  context</a> from which the current <a href=#browsing-context>browsing context</a>
-  was created (its <a href=#opener-browsing-context>opener browsing context</a>), if there is
-  one, if it is still available, and if the current <a href=#browsing-context>browsing
-  context</a> has not <i><a href=#disowned-its-opener>disowned its opener</a></i>; otherwise, it
-  must return null. On setting, if the new value is null then the
-  current <a href=#browsing-context>browsing context</a> must <dfn id=disowned-its-opener title="disowned its
-  opener">disown its opener</dfn>; if the new value is anything else
-  then the user agent must ignore the new value.</p>
+  <p>The <dfn id=dom-opener title=dom-opener><code>opener</code></dfn> IDL attribute on the <code><a href=#window>Window</a></code>
+  object, on getting, must return the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
+  context</a> from which the current <a href=#browsing-context>browsing context</a> was created (its <a href=#opener-browsing-context>opener
+  browsing context</a>), if there is one, if it is still available, and if the current
+  <a href=#browsing-context>browsing context</a> has not <i><a href=#disowned-its-opener>disowned its opener</a></i>; otherwise, it must return null.
+  On setting, if the new value is null then the current <a href=#browsing-context>browsing context</a> must <dfn id=disowned-its-opener title="disowned its opener">disown its opener</dfn>; if the new value is anything else then the
+  user agent must ignore the new value.</p>
 
 
 
@@ -67106,9 +66853,9 @@
      http://www.w3.org/Bugs/Public/show_bug.cgi?id=11183
   and then moved to the wiki -->
 
-  <p>User agents may support <dfn id=secondary-browsing-context title="secondary browsing
-  context">secondary browsing contexts</dfn>, which are <a href=#browsing-context title="browsing context">browsing contexts</a> that form part of
-  the user agent's interface, apart from the main content area.</p>
+  <p>User agents may support <dfn id=secondary-browsing-context title="secondary browsing context">secondary browsing
+  contexts</dfn>, which are <a href=#browsing-context title="browsing context">browsing contexts</a> that form part
+  of the user agent's interface, apart from the main content area.</p>
 
 
 <!--ADD-TOPIC:Security-->
@@ -67116,42 +66863,33 @@
 
   <h4 id=security-nav><span class=secno>6.1.4 </span>Security</h4>
 
-  <p id=security-1>A <a href=#browsing-context>browsing context</a> <var title="">A</var> is <dfn id=allowed-to-navigate>allowed to navigate</dfn> a second
-  <a href=#browsing-context>browsing context</a> <var title="">B</var> if one of the
+  <p id=security-1>A <a href=#browsing-context>browsing context</a> <var title="">A</var> is <dfn id=allowed-to-navigate>allowed to
+  navigate</dfn> a second <a href=#browsing-context>browsing context</a> <var title="">B</var> if one of the
   following conditions is true:</p>
 
-  <ul><li>Either the <a href=#origin>origin</a> of the <a href=#active-document>active
-   document</a> of <var title="">A</var> is the <a href=#same-origin title="same
-   origin">same</a> as the <a href=#origin>origin</a> of the <a href=#active-document>active
+  <ul><li>Either the <a href=#origin>origin</a> of the <a href=#active-document>active document</a> of <var title="">A</var>
+   is the <a href=#same-origin title="same origin">same</a> as the <a href=#origin>origin</a> of the <a href=#active-document>active
    document</a> of <var title="">B</var>, or</li>
 
-   <li>The browsing context <var title="">A</var> is a <a href=#nested-browsing-context>nested
-   browsing context</a> with a <a href=#top-level-browsing-context>top-level browsing
-   context</a>, and its <a href=#top-level-browsing-context>top-level browsing context</a> is
-   <var title="">B</var>, or</li>
+   <li>The browsing context <var title="">A</var> is a <a href=#nested-browsing-context>nested browsing context</a> with a
+   <a href=#top-level-browsing-context>top-level browsing context</a>, and its <a href=#top-level-browsing-context>top-level browsing context</a> is <var title="">B</var>, or</li>
 
-   <li>The browsing context <var title="">B</var> is an
-   <a href=#auxiliary-browsing-context>auxiliary browsing context</a> and <var title="">A</var>
-   is <a href=#allowed-to-navigate>allowed to navigate</a> <var title="">B</var>'s
-   <a href=#opener-browsing-context>opener browsing context</a>, or</li>
+   <li>The browsing context <var title="">B</var> is an <a href=#auxiliary-browsing-context>auxiliary browsing context</a> and
+   <var title="">A</var> is <a href=#allowed-to-navigate>allowed to navigate</a> <var title="">B</var>'s <a href=#opener-browsing-context>opener
+   browsing context</a>, or</li>
 
-   <li>The browsing context <var title="">B</var> is not a
-   <a href=#top-level-browsing-context>top-level browsing context</a>, but there exists an
-   <a href=#ancestor-browsing-context>ancestor browsing context</a> of <var title="">B</var>
-   whose <a href=#active-document>active document</a> has the <a href=#same-origin title="same
-   origin">same</a> <a href=#origin>origin</a> as the <a href=#active-document>active
-   document</a> of <var title="">A</var> (possibly in fact being
-   <var title="">A</var> itself).</li>
+   <li>The browsing context <var title="">B</var> is not a <a href=#top-level-browsing-context>top-level browsing context</a>,
+   but there exists an <a href=#ancestor-browsing-context>ancestor browsing context</a> of <var title="">B</var> whose
+   <a href=#active-document>active document</a> has the <a href=#same-origin title="same origin">same</a> <a href=#origin>origin</a> as
+   the <a href=#active-document>active document</a> of <var title="">A</var> (possibly in fact being <var title="">A</var> itself).</li>
 
-  </ul><hr><p>An element has a <dfn id=browsing-context-scope-origin>browsing context scope origin</dfn> if its
-  <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a> is a
-  <a href=#top-level-browsing-context>top-level browsing context</a> or if all of its
-  <code><a href=#document>Document</a></code>'s <a href=#ancestor-browsing-context title="ancestor browsing
-  context">ancestor browsing contexts</a> all have <a href=#active-document title="active document">active documents</a> whose
-  <a href=#origin>origin</a> are the <a href=#same-origin>same origin</a> as the
-  element's <code><a href=#document>Document</a></code>'s <a href=#origin>origin</a>. If an element
-  has a <a href=#browsing-context-scope-origin>browsing context scope origin</a>, then its value is
-  the <a href=#origin>origin</a> of the element's <code><a href=#document>Document</a></code>.</p>
+  </ul><hr><p>An element has a <dfn id=browsing-context-scope-origin>browsing context scope origin</dfn> if its <code><a href=#document>Document</a></code>'s
+  <a href=#browsing-context>browsing context</a> is a <a href=#top-level-browsing-context>top-level browsing context</a> or if all of its
+  <code><a href=#document>Document</a></code>'s <a href=#ancestor-browsing-context title="ancestor browsing context">ancestor browsing contexts</a>
+  all have <a href=#active-document title="active document">active documents</a> whose <a href=#origin>origin</a> are the
+  <a href=#same-origin>same origin</a> as the element's <code><a href=#document>Document</a></code>'s <a href=#origin>origin</a>. If an
+  element has a <a href=#browsing-context-scope-origin>browsing context scope origin</a>, then its value is the
+  <a href=#origin>origin</a> of the element's <code><a href=#document>Document</a></code>.</p>
 
   </div>
 <!--REMOVE-TOPIC:Security-->
@@ -67161,44 +66899,35 @@
 
   <h4 id=groupings-of-browsing-contexts><span class=secno>6.1.5 </span>Groupings of browsing contexts</h4>
 
-  <p>Each <a href=#browsing-context>browsing context</a> is defined as having a list of
-  one or more <dfn id=directly-reachable-browsing-contexts>directly reachable browsing contexts</dfn>. These
-  are:</p>
+  <p>Each <a href=#browsing-context>browsing context</a> is defined as having a list of one or more <dfn id=directly-reachable-browsing-contexts>directly
+  reachable browsing contexts</dfn>. These are:</p>
 
   <ul><li>The <a href=#browsing-context>browsing context</a> itself.</li>
 
-   <li>All the <a href=#browsing-context>browsing context</a>'s <a href=#child-browsing-context title="child
-   browsing context">child browsing contexts</a>.</li>
+   <li>All the <a href=#browsing-context>browsing context</a>'s <a href=#child-browsing-context title="child browsing context">child browsing
+   contexts</a>.</li>
 
-   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#parent-browsing-context>parent browsing
-   context</a>.</li>
+   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#parent-browsing-context>parent browsing context</a>.</li>
 
-   <li>All the <a href=#browsing-context title="browsing context">browsing contexts</a>
-   that have the <a href=#browsing-context>browsing context</a> as their <a href=#opener-browsing-context>opener
-   browsing context</a>.</li>
+   <li>All the <a href=#browsing-context title="browsing context">browsing contexts</a> that have the <a href=#browsing-context>browsing
+   context</a> as their <a href=#opener-browsing-context>opener browsing context</a>.</li>
 
-   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#opener-browsing-context>opener browsing
-   context</a>.</li>
+   <li>The <a href=#browsing-context>browsing context</a>'s <a href=#opener-browsing-context>opener browsing context</a>.</li>
 
-  </ul><p>The transitive closure of all the <a href=#browsing-context title="browsing
-  context">browsing contexts</a> that are <a href=#directly-reachable-browsing-contexts>directly reachable
-  browsing contexts</a> forms a <dfn id=unit-of-related-browsing-contexts>unit of related browsing
+  </ul><p>The transitive closure of all the <a href=#browsing-context title="browsing context">browsing contexts</a> that
+  are <a href=#directly-reachable-browsing-contexts>directly reachable browsing contexts</a> forms a <dfn id=unit-of-related-browsing-contexts>unit of related browsing
   contexts</dfn>.</p>
 
-  <p>Each <a href=#unit-of-related-browsing-contexts>unit of related browsing contexts</a> is then
-  further divided into the smallest number of groups such that every
-  member of each group has an <a href=#active-document>active document</a> with an
-  <a href=#effective-script-origin>effective script origin</a> that, through appropriate
-  manipulation of the <code title=dom-document-domain><a href=#dom-document-domain>document.domain</a></code> attribute, could
-  be made to be the same as other members of the group, but could not
-  be made the same as members of any other group. Each such group is a
-  <dfn id=unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</dfn>.</p>
+  <p>Each <a href=#unit-of-related-browsing-contexts>unit of related browsing contexts</a> is then further divided into the smallest
+  number of groups such that every member of each group has an <a href=#active-document>active document</a> with an
+  <a href=#effective-script-origin>effective script origin</a> that, through appropriate manipulation of the <code title=dom-document-domain><a href=#dom-document-domain>document.domain</a></code> attribute, could be made to be the same as
+  other members of the group, but could not be made the same as members of any other group. Each
+  such group is a <dfn id=unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</dfn>.</p>
 
-  <p class=note>There is also at most one <a href=#event-loop>event loop</a>
-  per <a href=#unit-of-related-similar-origin-browsing-contexts>unit of related similar-origin browsing contexts</a>
-  (though several <a href=#unit-of-related-similar-origin-browsing-contexts title="unit of related similar-origin browsing
-  contexts">units of related similar-origin browsing contexts</a>
-  can have a shared <a href=#event-loop>event loop</a>).</p>
+  <p class=note>There is also at most one <a href=#event-loop>event loop</a> per <a href=#unit-of-related-similar-origin-browsing-contexts>unit of related
+  similar-origin browsing contexts</a> (though several <a href=#unit-of-related-similar-origin-browsing-contexts title="unit of related
+  similar-origin browsing contexts">units of related similar-origin browsing contexts</a> can
+  have a shared <a href=#event-loop>event loop</a>).</p>
 
   </div>
 
@@ -67206,34 +66935,29 @@
 
   <h4 id=browsing-context-names><span class=secno>6.1.6 </span>Browsing context names</h4>
 
-  <p>Browsing contexts can have a <dfn id=browsing-context-name>browsing context name</dfn>. By
-  default, a browsing context has no name (its name is not set).</p>
+  <p>Browsing contexts can have a <dfn id=browsing-context-name>browsing context name</dfn>. By default, a browsing context
+  has no name (its name is not set).</p>
 
-  <p>A <dfn id=valid-browsing-context-name>valid browsing context name</dfn> is any string with at
-  least one character that does not start with a U+005F LOW LINE
-  character. (Names starting with an underscore are reserved for
+  <p>A <dfn id=valid-browsing-context-name>valid browsing context name</dfn> is any string with at least one character that does
+  not start with a U+005F LOW LINE character. (Names starting with an underscore are reserved for
   special keywords.)</p>
 
-  <p>A <dfn id=valid-browsing-context-name-or-keyword>valid browsing context name or keyword</dfn> is any string
-  that is either a <a href=#valid-browsing-context-name>valid browsing context name</a> or that is
-  an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for one of: <code title="">_blank</code>, <code title="">_self</code>, <code title="">_parent</code>, or <code title="">_top</code>.</p>
+  <p>A <dfn id=valid-browsing-context-name-or-keyword>valid browsing context name or keyword</dfn> is any string that is either a <a href=#valid-browsing-context-name>valid
+  browsing context name</a> or that is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for one of:
+  <code title="">_blank</code>, <code title="">_self</code>, <code title="">_parent</code>, or <code title="">_top</code>.</p>
 
-  <p>These values have different meanings based on whether the page is
-  sandboxed or not, as summarized in the following (non-normative)
-  table. In this table, "current" means the <a href=#browsing-context>browsing
-  context</a> that the link or script is in, "parent" means the
-  <a href=#parent-browsing-context>parent browsing context</a> of the one the link or script
-  is in, "master" means the nearest <a href=#ancestor-browsing-context>ancestor browsing
-  context</a> of the one the link or script is in that is not
-  itself in a <a href=#attr-iframe-seamless title=attr-iframe-seamless>seamless
-  iframe</a>, "top" means the <a href=#top-level-browsing-context>top-level browsing
-  context</a> of the one the link or script is in, "new" means a
-  new <a href=#top-level-browsing-context>top-level browsing context</a> or <a href=#auxiliary-browsing-context>auxiliary
-  browsing context</a> is to be created, subject to various user
-  preferences and user agent policies, "none" means that nothing will
-  happen, and "maybe new" means the same as "new" if the "<code title=attr-iframe-sandbox-allow-popups><a href=#attr-iframe-sandbox-allow-popups>allow-popups</a></code>"
-  keyword is also specified on the <code title=attr-iframe-sandbox><a href=#attr-iframe-sandbox>sandbox</a></code> attribute (or if the user
-  overrode the sandboxing), and the same as "none" otherwise.</p>
+  <p>These values have different meanings based on whether the page is sandboxed or not, as
+  summarized in the following (non-normative) table. In this table, "current" means the
+  <a href=#browsing-context>browsing context</a> that the link or script is in, "parent" means the <a href=#parent-browsing-context>parent
+  browsing context</a> of the one the link or script is in, "master" means the nearest
+  <a href=#ancestor-browsing-context>ancestor browsing context</a> of the one the link or script is in that is not itself in a
+  <a href=#attr-iframe-seamless title=attr-iframe-seamless>seamless iframe</a>, "top" means the <a href=#top-level-browsing-context>top-level
+  browsing context</a> of the one the link or script is in, "new" means a new <a href=#top-level-browsing-context>top-level
+  browsing context</a> or <a href=#auxiliary-browsing-context>auxiliary browsing context</a> is to be created, subject to
+  various user preferences and user agent policies, "none" means that nothing will happen, and
+  "maybe new" means the same as "new" if the "<code title=attr-iframe-sandbox-allow-popups><a href=#attr-iframe-sandbox-allow-popups>allow-popups</a></code>" keyword is also specified on the
+  <code title=attr-iframe-sandbox><a href=#attr-iframe-sandbox>sandbox</a></code> attribute (or if the user overrode the
+  sandboxing), and the same as "none" otherwise.</p>
 
   <table><thead><tr><th rowspan=2>Keyword
      <th rowspan=2>Ordinary effect
@@ -67368,151 +67092,129 @@
 
   <div class=impl>
 
-  <hr><p>An algorithm is <dfn id=allowed-to-show-a-pop-up>allowed to show a pop-up</dfn> if, in the
-  <a href=#concept-task title=concept-task>task</a> in which the algorithm is
-  running, either:</p>
+  <hr><p>An algorithm is <dfn id=allowed-to-show-a-pop-up>allowed to show a pop-up</dfn> if, in the <a href=#concept-task title=concept-task>task</a> in which the algorithm is running, either:</p>
 
-  <ul class=brief><li>an <a href=#activation-behavior>activation behavior</a> is currently being
-   processed whose <code title=event-click><a href=#event-click>click</a></code> event was
-   <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>, or</li>
+  <ul class=brief><li>an <a href=#activation-behavior>activation behavior</a> is currently being processed whose <code title=event-click><a href=#event-click>click</a></code> event was <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>,
+   or</li>
 
    <li>the event listener for a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> <code title=event-click><a href=#event-click>click</a></code> event is being handled.</li>
 
-  </ul><hr><p><dfn id=the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name>The rules for choosing a browsing context given a browsing
-  context name</dfn> are as follows. The rules assume that they are
-  being applied in the context of a <a href=#browsing-context>browsing context</a>.</p>
+  </ul><hr><p><dfn id=the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name>The rules for choosing a browsing context given a browsing context name</dfn> are as
+  follows. The rules assume that they are being applied in the context of a <a href=#browsing-context>browsing
+  context</a>.</p>
 
   <ol><li>
 
-    <p>If the given browsing context name is the empty string or <code title="">_self</code>, then the chosen browsing context must be
-    the current one.</p>
+    <p>If the given browsing context name is the empty string or <code title="">_self</code>, then
+    the chosen browsing context must be the current one.</p>
 
-    <p>If the given browsing context name is <code title="">_self</code>, then this is an <a href=#explicit-self-navigation-override>explicit
-    self-navigation override</a>, which overrides the behavior of
-    the <a href=#seamless-browsing-context-flag>seamless browsing context flag</a> set by the <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute on
-    <code><a href=#the-iframe-element>iframe</a></code> elements.</p>
+    <p>If the given browsing context name is <code title="">_self</code>, then this is an
+    <a href=#explicit-self-navigation-override>explicit self-navigation override</a>, which overrides the behavior of the
+    <a href=#seamless-browsing-context-flag>seamless browsing context flag</a> set by the <code title=attr-iframe-seamless><a href=#attr-iframe-seamless>seamless</a></code> attribute on <code><a href=#the-iframe-element>iframe</a></code> elements.</p>
 
    </li>
 
-   <li><p>If the given browsing context name is <code title="">_parent</code>, then the chosen browsing context must be
-   the <a href=#parent-browsing-context><em>parent</em> browsing context</a> of the current
-   one, unless there isn't one, in which case the chosen browsing
-   context must be the current browsing context.</li>
+   <li><p>If the given browsing context name is <code title="">_parent</code>, then the chosen
+   browsing context must be the <a href=#parent-browsing-context><em>parent</em> browsing context</a> of the current one,
+   unless there isn't one, in which case the chosen browsing context must be the current browsing
+   context.</li>
 
-   <li><p>If the given browsing context name is <code title="">_top</code>, then the chosen browsing context must be the
-   <a href=#top-level-browsing-context>top-level browsing context</a> of the current one, if
-   there is one, or else the current browsing context.</li>
+   <li><p>If the given browsing context name is <code title="">_top</code>, then the chosen browsing
+   context must be the <a href=#top-level-browsing-context>top-level browsing context</a> of the current one, if there is one,
+   or else the current browsing context.</li>
 
    <li>
 
-    <p>If the given browsing context name is not <code title="">_blank</code> and there exists a browsing context whose
-    <a href=#browsing-context-name title="browsing context name">name</a> is the same as the
-    given browsing context name, and the current browsing context is
-    <a href=#allowed-to-navigate>allowed to navigate</a> that browsing context, and the
-    user agent determines that the two browsing contexts are related
-    enough that it is ok if they reach each other, then that browsing
-    context must be the chosen one. If there are multiple matching
-    browsing contexts, the user agent should select one in some
-    arbitrary consistent manner, such as the most recently opened,
-    most recently focused, or more closely related.</p>
+    <p>If the given browsing context name is not <code title="">_blank</code> and there exists a
+    browsing context whose <a href=#browsing-context-name title="browsing context name">name</a> is the same as the given
+    browsing context name, and the current browsing context is <a href=#allowed-to-navigate>allowed to navigate</a> that
+    browsing context, and the user agent determines that the two browsing contexts are related
+    enough that it is ok if they reach each other, then that browsing context must be the chosen
+    one. If there are multiple matching browsing contexts, the user agent should select one in some
+    arbitrary consistent manner, such as the most recently opened, most recently focused, or more
+    closely related.</p>
 
-    <p>If the browsing context is chosen by this step to be the
-    current browsing context, then this is also an <a href=#explicit-self-navigation-override>explicit
-    self-navigation override</a>.</p>
+    <p>If the browsing context is chosen by this step to be the current browsing context, then this
+    is also an <a href=#explicit-self-navigation-override>explicit self-navigation override</a>.</p>
 
    </li>
 
    <li>
 
-    <p>Otherwise, a new browsing context is being requested, and what
-    happens depends on the user agent's configuration and/or abilities
-    — it is determined by the rules given for the first
+    <p>Otherwise, a new browsing context is being requested, and what happens depends on the user
+    agent's configuration and/or abilities — it is determined by the rules given for the first
     applicable option from the following list:</p>
 
-    <dl class=switch><dt id=sandboxWindowOpen>If the current browsing context's
-     <a href=#active-document>active document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag
-     set</a> has the <a href=#sandboxed-auxiliary-navigation-browsing-context-flag>sandboxed auxiliary navigation browsing
+    <dl class=switch><dt id=sandboxWindowOpen>If the current browsing context's <a href=#active-document>active document</a>'s
+     <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> has the <a href=#sandboxed-auxiliary-navigation-browsing-context-flag>sandboxed auxiliary navigation browsing
      context flag</a> set.</dt>
 
      <dd>
 
       <p>Typically, there is no chosen browsing context.</p>
 
-      <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
-      browsing context's name isn't set to the given browsing context
-      name). The default behaviour (if the user agent doesn't offer
-      the option to the user, or if the user declines to allow a
-      browsing context to be used) must be that there must not be a
-      chosen browsing context.</p>
+      <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 browsing context's name isn't
+      set to the given browsing context name). The default behaviour (if the user agent doesn't
+      offer the option to the user, or if the user declines to allow a browsing context to be used)
+      must be that there must not be a chosen browsing context.</p>
 
-      <p class=warning>If this case occurs, it means that an author
-      has explicitly sandboxed the document that is trying to open a
-      link.</p>
+      <p class=warning>If this case occurs, it means that an author has explicitly sandboxed the
+      document that is trying to open a link.</p>
 
      </dd>
 
 
-     <dt id=noopener>If the user agent has been configured such that
-     in this instance it will create a new browsing context, and the
-     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>
+     <dt id=noopener>If the user agent has been configured such that in this instance it will
+     create a new browsing context, and the 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><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. The creation of such a <a href=#browsing-context>browsing context</a> is
-     <dfn id=a-new-start-for-session-storage>a new start for session storage</dfn>.</p>
+     <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. The creation of such a <a href=#browsing-context>browsing context</a>
+     is <dfn id=a-new-start-for-session-storage>a new start for session storage</dfn>.</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>
+     <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
+     <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><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.</p>
+     <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.</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>
+     <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 reuse the current browsing context</dt>
+     <dt>If the user agent has been configured such that in this instance it will reuse the current
+     browsing context</dt>
 
-     <dd><p>The chosen browsing context is the current browsing
-     context.</dd>
+     <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>
+     <dt>If the user agent has been configured such that in this instance it will not find a
+     browsing context</dt>
 
      <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
-    browsing context.</p>
+    </dl><p>User agent implementors are encouraged to provide a way for users to configure the user agent
+    to always reuse the current browsing context.</p>
 
-    <p>If the current browsing context's <a href=#active-document>active
-    document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> has the
-    <a href=#sandboxed-navigation-browsing-context-flag>sandboxed navigation browsing context flag</a> set and
-    chosen browsing context picked above, if any, is a new browsing
-    context (whether top-level or auxiliary), then all the flags that
-    are set in the current browsing context's <a href=#active-document>active
-    document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> when the
-    new browsing context is created must be set in the new browsing
-    context's <a href=#popup-sandboxing-flag-set>popup sandboxing flag set</a>, and the current
-    browsing context must be set as the new browsing context's
-    <a href=#one-permitted-sandboxed-navigator>one permitted sandboxed navigator</a>.</p>
+    <p>If the current browsing context's <a href=#active-document>active document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag
+    set</a> has the <a href=#sandboxed-navigation-browsing-context-flag>sandboxed navigation browsing context flag</a> set and chosen
+    browsing context picked above, if any, is a new browsing context (whether top-level or
+    auxiliary), then all the flags that are set in the current browsing context's <a href=#active-document>active
+    document</a>'s <a href=#active-sandboxing-flag-set>active sandboxing flag set</a> when the new browsing context is
+    created must be set in the new browsing context's <a href=#popup-sandboxing-flag-set>popup sandboxing flag set</a>, and
+    the current browsing context must be set as the new browsing context's <a href=#one-permitted-sandboxed-navigator>one permitted
+    sandboxed navigator</a>.</p>
 
    </li>
 

Modified: source
===================================================================
--- source	2012-11-24 04:51:58 UTC (rev 7530)
+++ source	2012-11-24 17:39:19 UTC (rev 7531)
@@ -326,7 +326,7 @@
    <li>The <code title="attr-inert">inert</code> global attribute to disable subtrees.</li><!--INERT-->
    <li>The <code title="attr-fs-method-dialog-keyword">dialog</code> keyword on the <code>form</code> element's <code title="attr-fs-method">method</code> attribute, for a simpler way to close dialogs.</li><!--FORM-DIALOG-->
    <li>The <code title="dom-document-cssElementMap">cssElementMap</code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
-   <li>Some predefined <a href="#mdvocabs">Microdata vocabularies</a>.</li>
+   <li>Some predefined sample <a href="#mdvocabs">Microdata vocabularies</a>.</li>
    <li>The <code>data</code> element for marking up machine-readable data.</li><!--DATA--><!--FORK-->
    <li>The <span>application cache</span> feature's <span title="concept-appcache-mode-prefer-online">prefer-online</span> mode.</li><!--FORK--><!--APPCACHE-PREFER-ONLINE-->
    <li>The <code title="dom-TextTrack-inBandMetadataTrackDispatchType">TextTrack.inBandMetadataTrackDispatchType</code> feature for Internet-based TV broadcast.</li>
@@ -70171,13 +70171,11 @@
   </ol>
 
 <!--TOPIC:DOM APIs-->
-
   <p>The <dfn
   title="dom-dialog-returnValue"><code>returnValue</code></dfn> IDL
   attribute, on getting, must return the last value to which it was
   set. On setting, it must be set to the new value. When the element
   is created, it must be set to the empty string.</p>
-
 <!--TOPIC:HTML-->
 
   <hr>
@@ -73525,6 +73523,7 @@
   </div>
 
 
+<!--TOPIC:Microdata-->
 
   <h2 id="microdata"><dfn>Microdata</dfn></h2>
 
@@ -73567,20 +73566,17 @@
 
 <!-- v2
 
-  * <itemref itemprop="foo" src="url#id"> to import the item with
-    id="id" from url into the current microdata block as the value of
-    property foo?
+  * <itemref itemprop="foo" src="url#id"> to import the item with id="id" from url into the current
+    microdata block as the value of property foo?
 
-  * splitting the 'content' part of a property into multiple sub-bits,
-    as in:
+  * splitting the 'content' part of a property into multiple sub-bits, as in:
 
      <span itemprop="tel" item-content-in-bits>
        Telephone:
        <span content-bit>+44</span> (0) <span content-bit>1223 123 123</span>
      </span>
 
-    maybe vocabs that need this can use a sub vocabulary specifically
-    for this:
+    maybe vocabs that need this can use a sub vocabulary specifically for this:
 
      <span itemprop="tel" itemscope itemtype="http://bits.example/">
        Telephone:
@@ -73595,35 +73591,28 @@
 
   <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
 
-  <p>Sometimes, it is desirable to annotate content with specific
-  machine-readable labels, e.g. to allow generic scripts to provide
-  services that are customised to the page, or to enable content from
-  a variety of cooperating authors to be processed by a single script
-  in a consistent manner.</p>
+  <p>Sometimes, it is desirable to annotate content with specific machine-readable labels, e.g. to
+  allow generic scripts to provide services that are customised to the page, or to enable content
+  from a variety of cooperating authors to be processed by a single script in a consistent
+  manner.</p>
 
-  <p>For this purpose, authors can use the microdata features
-  described in this section. Microdata allows nested groups of
-  name-value pairs to be added to documents, in parallel with the
-  existing content.</p>
+  <p>For this purpose, authors can use the microdata features described in this section. Microdata
+  allows nested groups of name-value pairs to be added to documents, in parallel with the existing
+  content.</p>
 
 
-
   <h4>The basic syntax</h4>
 
   <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
 
-  <p>At a high level, microdata consists of a group of name-value
-  pairs. The groups are called <span
-  title="concept-item">items</span>, and each name-value pair is a
-  property. Items and properties are represented by regular
-  elements.</p>
+  <p>At a high level, microdata consists of a group of name-value pairs. The groups are called <span
+  title="concept-item">items</span>, and each name-value pair is a property. Items and properties
+  are represented by regular elements.</p>
 
-  <p>To create an item, the <code
-  title="attr-itemscope">itemscope</code> attribute is used.</p>
+  <p>To create an item, the <code title="attr-itemscope">itemscope</code> attribute is used.</p>
 
-  <p>To add a property to an item, the <code
-  title="attr-itemprop">itemprop</code> attribute is used on one of
-  the <span title="concept-item">item's</span> descendants.</p>
+  <p>To add a property to an item, the <code title="attr-itemprop">itemprop</code> attribute is used
+  on one of the <span title="concept-item">item's</span> descendants.</p>
 
   <div class="example">
 
@@ -73639,13 +73628,12 @@
 
   </div>
 
-  <p>Markup without microdata attributes has no effect on
-  microdata.</p>
+  <p>Markup without microdata attributes has no effect on microdata.</p>
 
   <div class="example">
 
-   <p>These two examples are exactly equivalent, at a microdata level,
-   as the previous two examples respectively:</p>
+   <p>These two examples are exactly equivalent, at a microdata level, as the previous two examples
+   respectively:</p>
 
    <pre><div itemscope>
  <p>My <em>name</em> is <span itemprop="name">E<strong>liz</strong>abeth</span>.</p>
@@ -73675,17 +73663,14 @@
 
   </div>
 
-  <p>When a string value is a <span title="URL">URLs</span>, it is
-  expressed using the <code>a</code> element and its <code
-  title="attr-hyperlink-href">href</code> attribute, the
-  <code>img</code> element and its <code
-  title="attr-img-src">src</code> attribute, or other elements that
-  link to or embed external resources.</p>
+  <p>When a string value is a <span title="URL">URLs</span>, it is expressed using the
+  <code>a</code> element and its <code title="attr-hyperlink-href">href</code> attribute, the
+  <code>img</code> element and its <code title="attr-img-src">src</code> attribute, or other
+  elements that link to or embed external resources.</p>
 
   <div class="example">
 
-   <p>In this example, the item has one property, "image", whose value
-   is a URL:</p>
+   <p>In this example, the item has one property, "image", whose value is a URL:</p>
 
    <pre><div itemscope>
  <img itemprop="image" src="google-logo.png" alt="Google">
@@ -73701,9 +73686,8 @@
 
   <div class="example">
 
-   <p>Here, there is an item with a property whose value is a product
-   ID. The ID is not human-friendly, so the product's name is used
-   the human-visible text instead of the ID.</p>
+   <p>Here, there is an item with a property whose value is a product ID. The ID is not
+   human-friendly, so the product's name is used the human-visible text instead of the ID.</p>
 
    <pre><h1 itemscope>
  <data itemprop="product-id" value="9678AOU879">The Instigator 2000</data>
@@ -73711,14 +73695,12 @@
 
   </div>
 
-  <p>For date- and time-related data, the <code>time</code> element
-  and its <code title="attr-time-datetime">datetime</code> attribute
-  can be used instead.</p>
+  <p>For date- and time-related data, the <code>time</code> element and its <code
+  title="attr-time-datetime">datetime</code> attribute can be used instead.</p>
 
   <div class="example">
 
-   <p>In this example, the item has one property, "birthday", whose
-   value is a date:</p>
+   <p>In this example, the item has one property, "birthday", whose value is a date:</p>
 
    <pre><div itemscope>
  I was born on <time itemprop="birthday" datetime="2009-05-10">May 10th 2009</time>.
@@ -73726,48 +73708,38 @@
 
   </div>
 
-  <p>Properties can also themselves be groups of name-value pairs, by
-  putting the <code title="attr-itemscope">itemscope</code> attribute
-  on the element that declares the property.</p>
+  <p>Properties can also themselves be groups of name-value pairs, by putting the <code
+  title="attr-itemscope">itemscope</code> attribute on the element that declares the property.</p>
 
-  <p>Items that are not part of others are called <span>top-level
-  microdata items</span>.</p>
+  <p>Items that are not part of others are called <span>top-level microdata items</span>.</p>
 
   <div class="example">
 
-   <p>In this example, the outer item represents a person, and the
-   inner one represents a band:</p>
+   <p>In this example, the outer item represents a person, and the inner one represents a band:</p>
 
    <pre><div itemscope>
  <p>Name: <span itemprop="name">Amanda</span></p>
  <p>Band: <span itemprop="band" itemscope> <span itemprop="name">Jazz Band</span> (<span itemprop="size">12</span> players)</span></p>
 </div></pre>
 
-   <p>The outer item here has two properties, "name" and
-   "band". The "name" is "Amanda", and the
-   "band" is an item in its own right, with two
-   properties, "name" and "size". The
-   "name" of the band is "Jazz Band", and the
-   "size" is "12".</p>
+   <p>The outer item here has two properties, "name" and "band". The "name" is "Amanda", and the
+   "band" is an item in its own right, with two properties, "name" and "size". The "name" of the
+   band is "Jazz Band", and the "size" is "12".</p>
 
-   <p>The outer item in this example is a top-level microdata
-   item.</p>
+   <p>The outer item in this example is a top-level microdata item.</p>
 
   </div>
 
   <p>Properties that are not descendants of the element with the <code
-  title="attr-itemscope">itemscope</code> attribute can be associated
-  with the <span title="concept-item">item</span> using the <code
-  title="attr-itemref">itemref</code> attribute. This attribute takes
-  a list of IDs of elements to crawl in addition to crawling the
-  children of the element with the <code
-  title="attr-itemscope">itemscope</code> attribute.</p>
+  title="attr-itemscope">itemscope</code> attribute can be associated with the <span
+  title="concept-item">item</span> using the <code title="attr-itemref">itemref</code> attribute.
+  This attribute takes a list of IDs of elements to crawl in addition to crawling the children of
+  the element with the <code title="attr-itemscope">itemscope</code> attribute.</p>
 
   <div class="example">
 
-   <p>This example is the same as the previous one, but all the
-   properties are separated from their <span
-   title="concept-item">items</span>:</p>
+   <p>This example is the same as the previous one, but all the properties are separated from their
+   <span title="concept-item">items</span>:</p>
 
    <pre><div itemscope id="amanda" itemref="a b"></div>
 <p id="a">Name: <span itemprop="name">Amanda</span></p>
@@ -73777,15 +73749,14 @@
  <p>Size: <span itemprop="size">12</span> players</p>
 </div></pre>
 
-   <p>This gives the same result as the previous example. The first
-   item has two properties, "name", set to "Amanda", and "band", set
-   to another item. That second item has two further properties,
+   <p>This gives the same result as the previous example. The first item has two properties, "name",
+   set to "Amanda", and "band", set to another item. That second item has two further properties,
    "name", set to "Jazz Band", and "size", set to "12".</p>
 
   </div>
 
-  <p>An <span title="concept-item">item</span> can have multiple
-  properties with the same name and different values.</p>
+  <p>An <span title="concept-item">item</span> can have multiple properties with the same name and
+  different values.</p>
 
   <div class="example">
 
@@ -73799,21 +73770,18 @@
  </ul>
 </div></pre>
 
-   <p>This thus results in an item with two properties, both
-   "flavor", having the values "Lemon sorbet" and "Apricot
-   sorbet".</p>
+   <p>This thus results in an item with two properties, both "flavor", having the values "Lemon
+   sorbet" and "Apricot sorbet".</p>
 
   </div>
 
-  <p>An element introducing a property can also introduce multiple
-  properties at once, to avoid duplication when some of the properties
-  have the same value.</p>
+  <p>An element introducing a property can also introduce multiple properties at once, to avoid
+  duplication when some of the properties have the same value.</p>
 
   <div class="example">
 
-   <p>Here we see an item with two properties,
-   "favorite-color" and "favorite-fruit", both
-   set to the value "orange":</p>
+   <p>Here we see an item with two properties, "favorite-color" and "favorite-fruit", both set to
+   the value "orange":</p>
 
    <pre><div itemscope>
  <span itemprop="favorite-color favorite-fruit">orange</span>
@@ -73821,14 +73789,12 @@
 
   </div>
 
-  <p>It's important to note that there is no relationship between the
-  microdata and the content of the document where the microdata is
-  marked up.</p>
+  <p>It's important to note that there is no relationship between the microdata and the content of
+  the document where the microdata is marked up.</p>
 
   <div class="example">
 
-   <p>There is no semantic difference, for instance, between the
-   following two examples:</p>
+   <p>There is no semantic difference, for instance, between the following two examples:</p>
 
    <pre><figure>
  <img src="castle.jpeg">
@@ -73841,13 +73807,11 @@
  <figcaption>The Castle (1986)</figcaption>
 </figure></pre>
 
-   <p>Both have a figure with a caption, and both, completely
-   unrelated to the figure, have an item with a name-value pair with
-   the name "name" and the value "The Castle". The only
-   difference is that if the user drags the caption out of the
-   document, in the former case, the item will be included in the
-   drag-and-drop data. In neither case is the image in any way
-   associated with the item.</p>
+   <p>Both have a figure with a caption, and both, completely unrelated to the figure, have an item
+   with a name-value pair with the name "name" and the value "The Castle". The only difference is
+   that if the user drags the caption out of the document, in the former case, the item will be
+   included in the drag-and-drop data. In neither case is the image in any way associated with the
+   item.</p>
 
   </div>
 
@@ -73856,21 +73820,16 @@
 
   <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
 
-  <p>The examples in the previous section show how information could
-  be marked up on a page that doesn't expect its microdata to be
-  re-used. Microdata is most useful, though, when it is used in
-  contexts where other authors and readers are able to cooperate to
-  make new uses of the markup.</p>
+  <p>The examples in the previous section show how information could be marked up on a page that
+  doesn't expect its microdata to be re-used. Microdata is most useful, though, when it is used in
+  contexts where other authors and readers are able to cooperate to make new uses of the markup.</p>
 
-  <p>For this purpose, it is necessary to give each <span
-  title="concept-item">item</span> a type, such as
-  "http://example.com/person", or "http://example.org/cat", or
-  "http://band.example.net/". Types are identified as <span
-  title="URL">URLs</span>.</p>
+  <p>For this purpose, it is necessary to give each <span title="concept-item">item</span> a type,
+  such as "http://example.com/person", or "http://example.org/cat", or "http://band.example.net/".
+  Types are identified as <span title="URL">URLs</span>.</p>
 
-  <p>The type for an <span title="concept-item">item</span> is given
-  as the value of an <code title="attr-itemtype">itemtype</code>
-  attribute on the same element as the <code
+  <p>The type for an <span title="concept-item">item</span> is given as the value of an <code
+  title="attr-itemtype">itemtype</code> attribute on the same element as the <code
   title="attr-itemscope">itemscope</code> attribute.</p>
 
   <div class="example">
@@ -73884,49 +73843,39 @@
  <img itemprop="img" src="hedral.jpeg" alt="" title="Hedral, age 18 months">
 </section></pre>
 
-   <p>In this example the "http://example.org/animals#cat" item has three
-   properties, a "name" ("Hedral"), a "desc" ("Hedral is..."), and an
-   "img" ("hedral.jpeg").</p>
+   <p>In this example the "http://example.org/animals#cat" item has three properties, a "name"
+   ("Hedral"), a "desc" ("Hedral is..."), and an "img" ("hedral.jpeg").</p>
 
   </div>
 
-  <p>The type gives the context for the properties, thus selecting a
-  vocabulary: a property named "class" given for an item with the type
-  "http://census.example/person" might refer to the economic class of
-  an individual, while a property named "class" given for an item with
-  the type "http://example.com/school/teacher" might refer to the
-  classroom a teacher has been assigned. Several types can share a
-  vocabulary. For example, the types "<code
+  <p>The type gives the context for the properties, thus selecting a vocabulary: a property named
+  "class" given for an item with the type "http://census.example/person" might refer to the economic
+  class of an individual, while a property named "class" given for an item with the type
+  "http://example.com/school/teacher" might refer to the classroom a teacher has been assigned.
+  Several types can share a vocabulary. For example, the types "<code
   title="">http://example.org/people/teacher</code>" and "<code
-  title="">http://example.org/people/engineer</code>" could be defined
-  to use the same vocabulary (though maybe some properties would not
-  be especially useful in both cases, e.g. maybe the "<code
-  title="">http://example.org/people/engineer</code>" type might not
-  typically be used with the "<code title="">classroom</code>"
-  property). Multiple types defined to use the same vocabulary can be
-  given for a single item by listing the URLs as a space-separated
-  list in the attribute' value. An item cannot be given two types if
-  they do not use the same vocabulary, however.</p>
+  title="">http://example.org/people/engineer</code>" could be defined to use the same vocabulary
+  (though maybe some properties would not be especially useful in both cases, e.g. maybe the "<code
+  title="">http://example.org/people/engineer</code>" type might not typically be used with the
+  "<code title="">classroom</code>" property). Multiple types defined to use the same vocabulary can
+  be given for a single item by listing the URLs as a space-separated list in the attribute' value.
+  An item cannot be given two types if they do not use the same vocabulary, however.</p>
 
 
   <h4>Global identifiers for items</h4>
 
   <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
 
-  <p>Sometimes, an <span title="concept-item">item</span> gives
-  information about a topic that has a global identifier. For example,
-  books can be identified by their ISBN number.</p>
+  <p>Sometimes, an <span title="concept-item">item</span> gives information about a topic that has a
+  global identifier. For example, books can be identified by their ISBN number.</p>
 
-  <p>Vocabularies (as identified by the <code
-  title="attr-itemtype">itemtype</code> attribute) can be designed
-  such that <span title="concept-item">items</span> get associated
-  with their global identifier in an unambiguous way by expressing the
-  global identifiers as <span title="URL">URLs</span> given in an
-  <code title="attr-itemid">itemid</code> attribute.</p>
+  <p>Vocabularies (as identified by the <code title="attr-itemtype">itemtype</code> attribute) can
+  be designed such that <span title="concept-item">items</span> get associated with their global
+  identifier in an unambiguous way by expressing the global identifiers as <span
+  title="URL">URLs</span> given in an <code title="attr-itemid">itemid</code> attribute.</p>
 
-  <p>The exact meaning of the <span title="URL">URLs</span> given in
-  <code title="attr-itemid">itemid</code> attributes depends on the
-  vocabulary used.</p>
+  <p>The exact meaning of the <span title="URL">URLs</span> given in <code
+  title="attr-itemid">itemid</code> attributes depends on the vocabulary used.</p>
 
   <div class="example">
 
@@ -73943,26 +73892,21 @@
  <dd><time itemprop="pubdate" datetime="1996-01-26">26 January 1996</time>
 </dl></pre>
 
-   <p>The "<code title="">http://vocab.example.net/book</code>"
-   vocabulary in this example would define that the <code
-   title="attr-itemid">itemid</code> attribute takes a <code
-   title="">urn:</code> <span>URL</span> pointing to the ISBN of the
-   book.</p>
+   <p>The "<code title="">http://vocab.example.net/book</code>" vocabulary in this example would
+   define that the <code title="attr-itemid">itemid</code> attribute takes a <code
+   title="">urn:</code> <span>URL</span> pointing to the ISBN of the book.</p>
 
   </div>
 
   <!-- (commented out since itemtype="" defines the meaning of the
         identifier for now)
-  <p>Although it is common practice, authors are encouraged not to use
-  the same URL to identify multiple topics; in particular, an HTTP URL
-  usually identifies a specific resource (such as an image or
-  document), and authors are encouraged to not use them to identify
-  people, non-Web resources like companies, movies, and products, or
-  other abstract concepts. Using an HTTP URL as a global identifier
-  for something other than the resource actually designated by the URL
-  leads to a situation where it is ambiguous whether the identifier,
-  and thus the set of properties specified in the microdata,
-  references the page or something else.</p>
+  <p>Although it is common practice, authors are encouraged not to use the same URL to identify
+  multiple topics; in particular, an HTTP URL usually identifies a specific resource (such as an
+  image or document), and authors are encouraged to not use them to identify people, non-Web
+  resources like companies, movies, and products, or other abstract concepts. Using an HTTP URL as a
+  global identifier for something other than the resource actually designated by the URL leads to a
+  situation where it is ambiguous whether the identifier, and thus the set of properties specified
+  in the microdata, references the page or something else.</p>
   -->
 
 
@@ -73971,16 +73915,14 @@
 
   <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
 
-  <p>Using microdata means using a vocabulary. For some purposes, an
-  ad-hoc vocabulary is adequate. For others, a vocabulary will need to
-  be designed. Where possible, authors are encouraged to re-use
-  existing vocabularies, as this makes content re-use easier.</p>
+  <p>Using microdata means using a vocabulary. For some purposes, an ad-hoc vocabulary is adequate.
+  For others, a vocabulary will need to be designed. Where possible, authors are encouraged to
+  re-use existing vocabularies, as this makes content re-use easier.</p>
 
-  <p>When designing new vocabularies, identifiers can be created
-  either using <span title="URL">URLs</span>, or, for properties, as
-  plain words (with no dots or colons). For URLs, conflicts with other
-  vocabularies can be avoided by only using identifiers that
-  correspond to pages that the author has control over.</p>
+  <p>When designing new vocabularies, identifiers can be created either using <span
+  title="URL">URLs</span>, or, for properties, as plain words (with no dots or colons). For URLs,
+  conflicts with other vocabularies can be avoided by only using identifiers that correspond to
+  pages that the author has control over.</p>
 
   <div class="example">
 
@@ -73994,22 +73936,18 @@
 
   </div>
 
-  <p>Properties whose names are just plain words can only be used
-  within the context of the types for which they are intended;
-  properties named using URLs can be reused in items of any type. If
-  an item has no type, and is not part of another item, then if its
-  properties have names that are just plain words, they are not
-  intended to be globally unique, and are instead only intended for
-  limited use. Generally speaking, authors are encouraged to use
-  either properties with globally unique names (URLs) or ensure that
-  their items are typed.</p>
+  <p>Properties whose names are just plain words can only be used within the context of the types
+  for which they are intended; properties named using URLs can be reused in items of any type. If an
+  item has no type, and is not part of another item, then if its properties have names that are just
+  plain words, they are not intended to be globally unique, and are instead only intended for
+  limited use. Generally speaking, authors are encouraged to use either properties with globally
+  unique names (URLs) or ensure that their items are typed.</p>
 
   <div class="example">
 
-   <p>Here, an item is an "http://example.org/animals#cat", and most of the
-   properties have names that are words defined in the context of that
-   type. There are also a few additional properties whose names come
-   from other vocabularies.</p>
+   <p>Here, an item is an "http://example.org/animals#cat", and most of the properties have names
+   that are words defined in the context of that type. There are also a few additional properties
+   whose names come from other vocabularies.</p>
 
 <pre><section itemscope itemtype="http://example.org/animals#cat">
  <h1 itemprop="name http://example.com/fn">Hedral</h1>
@@ -74020,8 +73958,8 @@
  <img itemprop="img" src="hedral.jpeg" alt="" title="Hedral, age 18 months">
 </section></pre>
 
-   <p>This example has one item with the type "http://example.org/animals#cat"
-   and the following properties:</p>
+   <p>This example has one item with the type "http://example.org/animals#cat" and the following
+   properties:</p>
 
    <table>
     <thead>
@@ -74057,78 +73995,63 @@
 
   <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
 
-  <p>The microdata becomes even more useful when scripts can use it to
-  expose information to the user, for example offering it in a form
-  that can be used by other applications.</p>
+  <p>The microdata becomes even more useful when scripts can use it to expose information to the
+  user, for example offering it in a form that can be used by other applications.</p>
 
-  <p>The <code title="dom-document-getItems">document.getItems(<var
-  title="">typeNames</var>)</code> method provides access to the
-  <span>top-level microdata items</span>. It returns a
-  <code>NodeList</code> containing the items with the specified types,
-  or all types if no argument is specified.</p>
+  <p>The <code title="dom-document-getItems">document.getItems(<var title="">typeNames</var>)</code>
+  method provides access to the <span>top-level microdata items</span>. It returns a
+  <code>NodeList</code> containing the items with the specified types, or all types if no argument
+  is specified.</p>
 
-  <p>Each <span title="concept-item">item</span> is represented in the
-  DOM by the element on which the relevant <code
-  title="attr-itemscope">itemscope</code> attribute is found. These
-  elements have their <code
-  title="dom-itemScope">element.itemScope</code> IDL attribute set to
-  true.</p>
+  <p>Each <span title="concept-item">item</span> is represented in the DOM by the element on which
+  the relevant <code title="attr-itemscope">itemscope</code> attribute is found. These elements have
+  their <code title="dom-itemScope">element.itemScope</code> IDL attribute set to true.</p>
 
-  <p>The type(s) of <span title="concept-item">items</span> can be
-  obtained using the <code
-  title="dom-itemType">element.itemType</code> IDL attribute on the
-  element with the <code title="attr-itemscope">itemscope</code>
-  attribute.</p>
+  <p>The type(s) of <span title="concept-item">items</span> can be obtained using the <code
+  title="dom-itemType">element.itemType</code> IDL attribute on the element with the <code
+  title="attr-itemscope">itemscope</code> attribute.</p>
 
   <div class="example">
 
-   <p>This sample shows how the <code
-   title="dom-document-getItems">getItems()</code> method can be used
-   to obtain a list of all the top-level microdata items of a
-   particular type given in the document:</p>
+   <p>This sample shows how the <code title="dom-document-getItems">getItems()</code> method can be
+   used to obtain a list of all the top-level microdata items of a particular type given in the
+   document:</p>
 
    <pre>var cats = document.getItems("http://example.com/feline");</pre>
 
   </div>
 
-  <p>Once an element representing an <span
-  title="concept-item">item</span> has been obtained, its properties
-  can be extracted using the <code
-  title="dom-properties">properties</code> IDL attribute. This
-  attribute returns an <code>HTMLPropertiesCollection</code>, which can
-  be enumerated to go through each element that adds one or more
-  properties to the item. It can also be indexed by name, which will
-  return an object with a list of the elements that add properties
-  with that name.</p>
+  <p>Once an element representing an <span title="concept-item">item</span> has been obtained, its
+  properties can be extracted using the <code title="dom-properties">properties</code> IDL
+  attribute. This attribute returns an <code>HTMLPropertiesCollection</code>, which can be
+  enumerated to go through each element that adds one or more properties to the item. It can also be
+  indexed by name, which will return an object with a list of the elements that add properties with
+  that name.</p>
 
-  <p>Each element that adds a property also has an <code
-  title="dom-itemValue">itemValue</code> IDL attribute that returns
-  its value.</p>
+  <p>Each element that adds a property also has an <code title="dom-itemValue">itemValue</code> IDL
+  attribute that returns its value.</p>
 
   <div class="example">
 
-   <p>This sample gets the first item of type "http://example.net/user" and
-   then pops up an alert using the "name" property from
-   that item.</p>
+   <p>This sample gets the first item of type "http://example.net/user" and then pops up an alert
+   using the "name" property from that item.</p>
 
    <pre>var user = document.getItems('http://example.net/user')[0];
 alert('Hello ' + user.properties['name'][0].itemValue + '!');</pre>
 
   </div>
 
-  <p>The <code>HTMLPropertiesCollection</code> object, when indexed by
-  name in this way, actually returns a <code>PropertyNodeList</code>
-  object with all the matching properties. The
-  <code>PropertyNodeList</code> object can be used to obtain all the
-  values at once using <em>its</em> <code
-  title="dom-PropertyNodeList-getValues">getValues</code> method,
-  which returns an array of all the values.</p>
+  <p>The <code>HTMLPropertiesCollection</code> object, when indexed by name in this way, actually
+  returns a <code>PropertyNodeList</code> object with all the matching properties. The
+  <code>PropertyNodeList</code> object can be used to obtain all the values at once using
+  <em>its</em> <code title="dom-PropertyNodeList-getValues">getValues</code> method, which returns
+  an array of all the values.</p>
 
   <div class="example">
 
    <p>In an earlier example, a "http://example.org/animals#cat" item had two
-   "http://example.com/color" values. This script looks up the first such
-   item and then lists all its values.</p>
+   "http://example.com/color" values. This script looks up the first such item and then lists all
+   its values.</p>
 
    <pre>var cat = document.getItems('http://example.org/animals#cat')[0];
 var colors = cat.properties['http://example.com/color'].getValues();
@@ -74145,16 +74068,13 @@
 
   </div>
 
-  <p>It's also possible to get a list of all the <span>property
-  names</span> using the object's <code
-  title="dom-HTMLPropertiesCollection-names">names</code> IDL
-  attribute.</p>
+  <p>It's also possible to get a list of all the <span>property names</span> using the object's
+  <code title="dom-HTMLPropertiesCollection-names">names</code> IDL attribute.</p>
 
   <div class="example">
 
-   <p>This example creates a big list with a nested list for each item
-   on the page, each with of all the property names used in that
-   item.</p>
+   <p>This example creates a big list with a nested list for each item on the page, each with of all
+   the property names used in that item.</p>
 
    <pre>var outer = document.createElement('ul');
 var items = document.getItems();
@@ -74196,8 +74116,7 @@
     </li>
    </ul>
 
-   <p>(The duplicate occurrence of "http://example.com/color" is not included
-   in the list.)</p>
+   <p>(The duplicate occurrence of "http://example.com/color" is not included in the list.)</p>
 
   </div>
 
@@ -74207,178 +74126,135 @@
 
   <h4>The microdata model</h4>
 
-  <p>The microdata model consists of groups of name-value pairs known
-  as <span title="concept-item">items</span>.</p>
+  <p>The microdata model consists of groups of name-value pairs known as <span
+  title="concept-item">items</span>.</p>
 
-  <p>Each group is known as an <span title="concept-item">item</span>.
-  Each <span title="concept-item">item</span> can have <span>item
-  types</span>, a <span>global identifier</span> (if the vocabulary
-  specified by the <span>item types</span> <span>support global
-  identifiers for items</span>), and a list of name-value pairs. Each
-  name in the name-value pair is known as a <span title="the
-  properties of an item">property</span>, and each <span title="the
+  <p>Each group is known as an <span title="concept-item">item</span>. Each <span
+  title="concept-item">item</span> can have <span>item types</span>, a <span>global
+  identifier</span> (if the vocabulary specified by the <span>item types</span> <span>support global
+  identifiers for items</span>), and a list of name-value pairs. Each name in the name-value pair is
+  known as a <span title="the properties of an item">property</span>, and each <span title="the
   properties of an item">property</span> has one or more <span
   title="concept-property-value">values</span>. Each <span
-  title="concept-property-value">value</span> is either a string or
-  itself a group of name-value pairs (an <span
-  title="concept-item">item</span>). The names are unordered relative
-  to each other, but if a particular name has multiple values, they do
-  have a relative order.</p>
+  title="concept-property-value">value</span> is either a string or itself a group of name-value
+  pairs (an <span title="concept-item">item</span>). The names are unordered relative to each other,
+  but if a particular name has multiple values, they do have a relative order.</p>
 
-  <p>An <span title="concept-item">item</span> is said to be a
-  <dfn>typed item</dfn> when either it has an <span title="item
-  types">item type</span>, or it is the <span
-  title="concept-property-value">value</span> of a <span title="the
-  properties of an item">property</span> of a <span>typed item</span>.
-  The <dfn>relevant types</dfn> for a <span>typed item</span> is the
-  <span title="concept-item">item</span>'s <span>item types</span>, if
-  it has one, or else is the <span>relevant types</span> of the <span
-  title="concept-item">item</span> for which it is a <span title="the
-  properties of an item">property</span>'s <span
-  title="concept-property-value">value</span>.</p>
+  <p>An <span title="concept-item">item</span> is said to be a <dfn>typed item</dfn> when either it
+  has an <span title="item types">item type</span>, or it is the <span
+  title="concept-property-value">value</span> of a <span title="the properties of an
+  item">property</span> of a <span>typed item</span>. The <dfn>relevant types</dfn> for a
+  <span>typed item</span> is the <span title="concept-item">item</span>'s <span>item types</span>,
+  if it has one, or else is the <span>relevant types</span> of the <span
+  title="concept-item">item</span> for which it is a <span title="the properties of an
+  item">property</span>'s <span title="concept-property-value">value</span>.</p>
 
 
 
   <h4>Items</h4>
 
-  <p>Every <span title="HTML elements">HTML element</span> may have an
-  <dfn title="attr-itemscope"><code>itemscope</code></dfn> attribute
-  specified. The <code title="attr-itemscope">itemscope</code>
-  attribute is a <span>boolean attribute</span>.</p>
+  <p>Every <span title="HTML elements">HTML element</span> may have an <dfn
+  title="attr-itemscope"><code>itemscope</code></dfn> attribute specified. The <code
+  title="attr-itemscope">itemscope</code> attribute is a <span>boolean attribute</span>.</p>
 
-  <p>An element with the <code title="attr-itemscope">itemscope</code>
-  attribute specified creates a new <dfn
-  title="concept-item">item</dfn>, a group of name-value pairs.</p>
+  <p>An element with the <code title="attr-itemscope">itemscope</code> attribute specified creates a
+  new <dfn title="concept-item">item</dfn>, a group of name-value pairs.</p>
 
   <hr>
 
-  <p>Elements with an <code title="attr-itemscope">itemscope</code>
-  attribute may have an <dfn
-  title="attr-itemtype"><code>itemtype</code></dfn> attribute
-  specified, to give the <span>item types</span> of the <span
-  title="concept-item">item</span>.</p>
+  <p>Elements with an <code title="attr-itemscope">itemscope</code> attribute may have an <dfn
+  title="attr-itemtype"><code>itemtype</code></dfn> attribute specified, to give the <span>item
+  types</span> of the <span title="concept-item">item</span>.</p>
 
-  <p>The <code title="attr-itemtype">itemtype</code> attribute, if
-  specified, must have a value that is an <span>unordered set of
-  unique space-separated tokens</span> that are
-  <span>case-sensitive</span>, each of which is a <span>valid
-  URL</span> that is an <span>absolute URL</span>, and all of which
-  are defined to use the same vocabulary. The attribute's value must
+  <p>The <code title="attr-itemtype">itemtype</code> attribute, if specified, must have a value that
+  is an <span>unordered set of unique space-separated tokens</span> that are
+  <span>case-sensitive</span>, each of which is a <span>valid URL</span> that is an <span>absolute
+  URL</span>, and all of which are defined to use the same vocabulary. The attribute's value must
   have at least one token.</p>
 
-  <p>The <dfn>item types</dfn> of an <span
-  title="concept-item">item</span> are the tokens obtained by <span
-  title="split a string on spaces">splitting the element's <code
-  title="attr-itemtype">itemtype</code> attribute's value on
-  spaces</span>. If the <code title="attr-itemtype">itemtype</code>
-  attribute is missing or parsing it in this way finds no tokens, the
-  <span title="concept-item">item</span> is said to have no <span>item
-  types</span>.</p>
+  <p>The <dfn>item types</dfn> of an <span title="concept-item">item</span> are the tokens obtained
+  by <span title="split a string on spaces">splitting the element's <code
+  title="attr-itemtype">itemtype</code> attribute's value on spaces</span>. If the <code
+  title="attr-itemtype">itemtype</code> attribute is missing or parsing it in this way finds no
+  tokens, the <span title="concept-item">item</span> is said to have no <span>item types</span>.</p>
 
-  <p>The <span>item types</span> must all be types defined in <span
-  title="other applicable specifications">applicable
-  specifications</span> and must all be defined to use the same
+  <p>The <span>item types</span> must all be types defined in <span title="other applicable
+  specifications">applicable specifications</span> and must all be defined to use the same
   vocabulary.</p>
 
   <div class="impl">
 
-   <p>Except if otherwise specified by that specification, the <span
-   title="URL">URLs</span> given as the <span>item types</span> should
-   not be automatically dereferenced.</p>
+   <p>Except if otherwise specified by that specification, the <span title="URL">URLs</span> given
+   as the <span>item types</span> should not be automatically dereferenced.</p>
 
-   <p class="note">A specification could define that its <span
-   title="item types">item type</span> can be derefenced to provide
-   the user with help information, for example. In fact, vocabulary
-   authors are encouraged to provide useful information at the given
-   <span>URL</span>.</p>
+   <p class="note">A specification could define that its <span title="item types">item type</span>
+   can be derefenced to provide the user with help information, for example. In fact, vocabulary
+   authors are encouraged to provide useful information at the given <span>URL</span>.</p>
 
-   <p><span>Item types</span> are opaque identifiers, and user agents
-   must not dereference unknown <span>item types</span>, or otherwise
-   deconstruct them, in order to determine how to process <span
-   title="concept-item">items</span> that use them.</p>
+   <p><span>Item types</span> are opaque identifiers, and user agents must not dereference unknown
+   <span>item types</span>, or otherwise deconstruct them, in order to determine how to process
+   <span title="concept-item">items</span> that use them.</p>
 
   </div>
 
-  <p>The <code title="attr-itemtype">itemtype</code> attribute must
-  not be specified on elements that do not have an <code
-  title="attr-itemscope">itemscope</code> attribute specified.</p>
+  <p>The <code title="attr-itemtype">itemtype</code> attribute must not be specified on elements
+  that do not have an <code title="attr-itemscope">itemscope</code> attribute specified.</p>
 
   <hr>
 
-  <p>Elements with an <code title="attr-itemscope">itemscope</code>
-  attribute and an <code title="attr-itemtype">itemtype</code>
-  attribute that references a vocabulary that is defined to
-  <dfn>support global identifiers for items</dfn> may also have an
-  <dfn title="attr-itemid"><code>itemid</code></dfn> attribute
-  specified, to give a global identifier for the <span
-  title="concept-item">item</span>, so that it can be related to other
-  <span title="concept-item">items</span> on pages elsewhere on the
-  Web.</p>
+  <p>Elements with an <code title="attr-itemscope">itemscope</code> attribute and an <code
+  title="attr-itemtype">itemtype</code> attribute that references a vocabulary that is defined to
+  <dfn>support global identifiers for items</dfn> may also have an <dfn
+  title="attr-itemid"><code>itemid</code></dfn> attribute specified, to give a global identifier for
+  the <span title="concept-item">item</span>, so that it can be related to other <span
+  title="concept-item">items</span> on pages elsewhere on the Web.</p>
 
-  <p>The <code title="attr-itemid">itemid</code> attribute, if
-  specified, must have a value that is a <span>valid URL potentially
-  surrounded by spaces</span>.</p>
+  <p>The <code title="attr-itemid">itemid</code> attribute, if specified, must have a value that is
+  a <span>valid URL potentially surrounded by spaces</span>.</p>
 
-  <p>The <dfn>global identifier</dfn> of an <span
-  title="concept-item">item</span> is the value of its element's <code
-  title="attr-itemid">itemid</code> attribute, if it has one, <span
-  title="resolve a url">resolved</span> relative to the element on
-  which the attribute is specified. If the <code
-  title="attr-itemid">itemid</code> attribute is missing or if
-  resolving it fails, it is said to have no <span>global
-  identifier</span>.</p>
+  <p>The <dfn>global identifier</dfn> of an <span title="concept-item">item</span> is the value of
+  its element's <code title="attr-itemid">itemid</code> attribute, if it has one, <span
+  title="resolve a url">resolved</span> relative to the element on which the attribute is specified.
+  If the <code title="attr-itemid">itemid</code> attribute is missing or if resolving it fails, it
+  is said to have no <span>global identifier</span>.</p>
 
-  <p>The <code title="attr-itemid">itemid</code> attribute must not be
-  specified on elements that do not have both an <code
-  title="attr-itemscope">itemscope</code> attribute and an <code
-  title="attr-itemtype">itemtype</code> attribute specified, and must
-  not be specified on elements with an <code
-  title="attr-itemscope">itemscope</code> attribute whose <code
-  title="attr-itemtype">itemtype</code> attribute specifies a
-  vocabulary that does not <span>support global identifiers for
-  items</span>, as defined by that vocabulary's specification.</p>
+  <p>The <code title="attr-itemid">itemid</code> attribute must not be specified on elements that do
+  not have both an <code title="attr-itemscope">itemscope</code> attribute and an <code
+  title="attr-itemtype">itemtype</code> attribute specified, and must not be specified on elements
+  with an <code title="attr-itemscope">itemscope</code> attribute whose <code
+  title="attr-itemtype">itemtype</code> attribute specifies a vocabulary that does not <span>support
+  global identifiers for items</span>, as defined by that vocabulary's specification.</p>
 
-  <p>The exact meaning of a <span>global identifier</span> is
-  determined by the vocabulary's specification. It is up to such
-  specifications to define whether multiple items with the same global
-  identifier (whether on the same page or on different pages) are
-  allowed to exist, and what the processing rules for that vocabulary
-  are with respect to handling the case of multiple items with the
-  same ID.</p>
+  <p>The exact meaning of a <span>global identifier</span> is determined by the vocabulary's
+  specification. It is up to such specifications to define whether multiple items with the same
+  global identifier (whether on the same page or on different pages) are allowed to exist, and what
+  the processing rules for that vocabulary are with respect to handling the case of multiple items
+  with the same ID.</p>
 
   <hr>
 
-  <p>Elements with an <code title="attr-itemscope">itemscope</code>
-  attribute may have an <dfn
-  title="attr-itemref"><code>itemref</code></dfn> attribute specified,
-  to give a list of additional elements to crawl to find the
-  name-value pairs of the <span title="concept-item">item</span>.</p>
+  <p>Elements with an <code title="attr-itemscope">itemscope</code> attribute may have an <dfn
+  title="attr-itemref"><code>itemref</code></dfn> attribute specified, to give a list of additional
+  elements to crawl to find the name-value pairs of the <span title="concept-item">item</span>.</p>
 
-  <p>The <code title="attr-itemref">itemref</code> attribute, if
-  specified, must have a value that is an <span>unordered set of
-  unique space-separated tokens</span> that are
-  <span>case-sensitive</span>, consisting of <span
-  title="concept-ID">IDs</span> of elements in the same <span>home
-  subtree</span>.</p>
+  <p>The <code title="attr-itemref">itemref</code> attribute, if specified, must have a value that
+  is an <span>unordered set of unique space-separated tokens</span> that are
+  <span>case-sensitive</span>, consisting of <span title="concept-ID">IDs</span> of elements in the
+  same <span>home subtree</span>.</p>
 
-  <p>The <code title="attr-itemref">itemref</code> attribute must not
-  be specified on elements that do not have an <code
-  title="attr-itemscope">itemscope</code> attribute specified.</p>
+  <p>The <code title="attr-itemref">itemref</code> attribute must not be specified on elements that
+  do not have an <code title="attr-itemscope">itemscope</code> attribute specified.</p>
 
-  <p class="note">The <code title="attr-itemref">itemref</code>
-  attribute is not part of the microdata data model. It is merely a
-  syntactic construct to aid authors in adding annotations to pages
-  where the data to be annotated does not follow a convenient tree
-  structure. For example, it allows authors to mark up data in a table
-  so that each column defines a separate <span
-  title="concept-item">item</span>, while keeping the properties in
-  the cells.</p>
+  <p class="note">The <code title="attr-itemref">itemref</code> attribute is not part of the
+  microdata data model. It is merely a syntactic construct to aid authors in adding annotations to
+  pages where the data to be annotated does not follow a convenient tree structure. For example, it
+  allows authors to mark up data in a table so that each column defines a separate <span
+  title="concept-item">item</span>, while keeping the properties in the cells.</p>
 
   <div class="example">
 
-   <p>This example shows a simple vocabulary used to describe the
-   products of a model railway manufacturer. The vocabulary has just
-   five property names:</p>
+   <p>This example shows a simple vocabulary used to describe the products of a model railway
+   manufacturer. The vocabulary has just five property names:</p>
 
    <dl>
     <dt>product-code</dt>
@@ -74411,9 +74287,8 @@
     <dd>Equipment with lighting</dd>
    </dl>
 
-   <p>Each <span title="concept-item">item</span> that uses this
-   vocabulary can be given one or more of these types, depending on
-   what the product is.</p>
+   <p>Each <span title="concept-item">item</span> that uses this vocabulary can be given one or more
+   of these types, depending on what the product is.</p>
 
    <p>Thus, a locomotive might be marked up as:</p>
 
@@ -74453,59 +74328,48 @@
  <dd itemprop="scale">Z
 </dl></pre>
 
-   <p>Great care is necessary when creating new vocabularies. Often, a
-   hierarchical approach to types can be taken that results in a
-   vocabulary where each item only ever has a single type, which is
-   generally much simpler to manage.</p>
+   <p>Great care is necessary when creating new vocabularies. Often, a hierarchical approach to
+   types can be taken that results in a vocabulary where each item only ever has a single type,
+   which is generally much simpler to manage.</p>
 
   </div>
 
 
   <h4>Names: the <dfn title="attr-itemprop"><code>itemprop</code></dfn> attribute</h4>
 
-  <p>Every <span title="HTML elements">HTML element</span> may have an
-  <code title="attr-itemprop">itemprop</code> attribute specified, if
-  doing so <span title="the properties of an item">adds one or more
-  properties</span> to one or more <span
+  <p>Every <span title="HTML elements">HTML element</span> may have an <code
+  title="attr-itemprop">itemprop</code> attribute specified, if doing so <span title="the properties
+  of an item">adds one or more properties</span> to one or more <span
   title="concept-item">items</span> (as defined below).</p>
 
-  <p>The <code title="attr-itemprop">itemprop</code> attribute, if
-  specified, must have a value that is an <span>unordered set of
-  unique space-separated tokens</span> that are
-  <span>case-sensitive</span>, representing the names of the
-  name-value pairs that it adds. The attribute's value must have at
-  least one token.</p>
+  <p>The <code title="attr-itemprop">itemprop</code> attribute, if specified, must have a value that
+  is an <span>unordered set of unique space-separated tokens</span> that are
+  <span>case-sensitive</span>, representing the names of the name-value pairs that it adds. The
+  attribute's value must have at least one token.</p>
 
   <p>Each token must be either:</p>
 
   <ul>
 
-   <li>A <span>valid URL</span> that is an <span>absolute URL</span>,
-   or</li>
+   <li>A <span>valid URL</span> that is an <span>absolute URL</span>, or</li>
 
-   <li>If the item is a <span>typed item</span>: a <dfn>defined
-   property name</dfn> allowed in this situation according to the
-   specification that defines the <span>relevant types</span> for the
+   <li>If the item is a <span>typed item</span>: a <dfn>defined property name</dfn> allowed in this
+   situation according to the specification that defines the <span>relevant types</span> for the
    item, or</li>
 
-   <li>If the item is not a <span>typed item</span>: a string that
-   contains no U+002E FULL STOP characters (.) and no U+003A COLON
-   characters (:).</li>
+   <li>If the item is not a <span>typed item</span>: a string that contains no U+002E FULL STOP
+   characters (.) and no U+003A COLON characters (:).</li>
 
   </ul>
 
-  <p>Specifications that introduce <span title="defined property
-  name">defined property names</span> that are not <span
-  title="absolute URL">absolute URLs</span> must ensure all such
-  property names contain no U+002E FULL STOP characters (.), no U+003A
-  COLON characters (:), and no <span title="space character">space
-  characters</span>.</p>
+  <p>Specifications that introduce <span title="defined property name">defined property names</span>
+  that are not <span title="absolute URL">absolute URLs</span> must ensure all such property names
+  contain no U+002E FULL STOP characters (.), no U+003A COLON characters (:), and no <span
+  title="space character">space characters</span>.</p>
 
-  <p>When an element with an <code
-  title="attr-itemprop">itemprop</code> attribute <span title="the
-  properties of an item">adds a property</span> to multiple <span
-  title="concept-item">items</span>, the requirement above regarding
-  the tokens applies for each <span title="concept-item">item</span>
+  <p>When an element with an <code title="attr-itemprop">itemprop</code> attribute <span title="the
+  properties of an item">adds a property</span> to multiple <span title="concept-item">items</span>,
+  the requirement above regarding the tokens applies for each <span title="concept-item">item</span>
   individually.</p>
 
   <!--
@@ -74520,23 +74384,19 @@
 
   -->
 
-  <p>The <dfn>property names</dfn> of an element are the tokens that
-  the element's <code title="attr-itemprop">itemprop</code> attribute
-  is found to contain when its value is <span title="split a string on
-  spaces">split on spaces</span>, with the order preserved but with
-  duplicates removed (leaving only the first occurrence of each
-  name).</p>
+  <p>The <dfn>property names</dfn> of an element are the tokens that the element's <code
+  title="attr-itemprop">itemprop</code> attribute is found to contain when its value is <span
+  title="split a string on spaces">split on spaces</span>, with the order preserved but with
+  duplicates removed (leaving only the first occurrence of each name).</p>
 
-  <p>Within an <span title="concept-item">item</span>, the properties
-  are unordered with respect to each other, except for properties with
-  the same name, which are ordered in the order they are given by the
-  algorithm that defines <span>the properties of an item</span>.</p>
+  <p>Within an <span title="concept-item">item</span>, the properties are unordered with respect to
+  each other, except for properties with the same name, which are ordered in the order they are
+  given by the algorithm that defines <span>the properties of an item</span>.</p>
 
   <div class="example">
 
-   <p>In the following example, the "a" property has the values "1"
-   and "2", <em>in that order</em>, but whether the "a" property comes
-   before the "b" property or not is not important:</p>
+   <p>In the following example, the "a" property has the values "1" and "2", <em>in that order</em>,
+   but whether the "a" property comes before the "b" property or not is not important:</p>
 
    <pre><div itemscope>
  <p itemprop="a">1</p>
@@ -74577,20 +74437,17 @@
 
   <h4>Values</h4>
 
-  <p>The <dfn title="concept-property-value">property value</dfn> of a
-  name-value pair added by an element with an <code
-  title="attr-itemprop">itemprop</code> attribute is as given for the
-  first matching case in the following list:</p>
+  <p>The <dfn title="concept-property-value">property value</dfn> of a name-value pair added by an
+  element with an <code title="attr-itemprop">itemprop</code> attribute is as given for the first
+  matching case in the following list:</p>
 
   <dl class="switch">
 
-   <dt>If the element also has an <code
-   title="attr-itemscope">itemscope</code> attribute</dt>
+   <dt>If the element also has an <code title="attr-itemscope">itemscope</code> attribute</dt>
 
    <dd>
 
-    <p>The value is the <span title="concept-item">item</span> created
-    by the element.</p>
+    <p>The value is the <span title="concept-item">item</span> created by the element.</p>
 
    </dd>
 
@@ -74599,40 +74456,33 @@
 
    <dd>
 
-    <p>The value is the value of the element's <code
-    title="attr-content">content</code> attribute, if any, or the
-    empty string if there is no such attribute.</p>
+    <p>The value is the value of the element's <code title="attr-content">content</code> attribute,
+    if any, or the empty string if there is no such attribute.</p>
 
    </dd>
 
 
-   <dt>If the element is an <code>audio</code>, <code>embed</code>,
-   <code>iframe</code>, <code>img</code>, <code>source</code>,
-   <code>track</code>, or <code>video</code> element</dt>
+   <dt>If the element is an <code>audio</code>, <code>embed</code>, <code>iframe</code>,
+   <code>img</code>, <code>source</code>, <code>track</code>, or <code>video</code> element</dt>
 
    <dd>
 
-    <p>The value is the <span>absolute URL</span> that results from
-    <span title="resolve a url">resolving</span> the value of the
-    element's <code title="">src</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <span title="resolve a
-    url">resolving</span> it results in an error.</p>
+    <p>The value is the <span>absolute URL</span> that results from <span title="resolve a
+    url">resolving</span> the value of the element's <code title="">src</code> attribute relative to
+    the element at the time the attribute is set, or the empty string if there is no such attribute
+    or if <span title="resolve a url">resolving</span> it results in an error.</p>
 
    </dd>
 
 
-   <dt>If the element is an <code>a</code>, <code>area</code>, or
-   <code>link</code> element</dt>
+   <dt>If the element is an <code>a</code>, <code>area</code>, or <code>link</code> element</dt>
 
    <dd>
 
-    <p>The value is the <span>absolute URL</span> that results from
-    <span title="resolve a url">resolving</span> the value of the
-    element's <code title="">href</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <span title="resolve a
-    url">resolving</span> it results in an error.</p>
+    <p>The value is the <span>absolute URL</span> that results from <span title="resolve a
+    url">resolving</span> the value of the element's <code title="">href</code> attribute relative
+    to the element at the time the attribute is set, or the empty string if there is no such
+    attribute or if <span title="resolve a url">resolving</span> it results in an error.</p>
 
    </dd>
 
@@ -74641,12 +74491,10 @@
 
    <dd>
 
-    <p>The value is the <span>absolute URL</span> that results from
-    <span title="resolve a url">resolving</span> the value of the
-    element's <code title="">data</code> attribute relative to the
-    element at the time the attribute is set, or the empty string if
-    there is no such attribute or if <span title="resolve a
-    url">resolving</span> it results in an error.</p>
+    <p>The value is the <span>absolute URL</span> that results from <span title="resolve a
+    url">resolving</span> the value of the element's <code title="">data</code> attribute relative
+    to the element at the time the attribute is set, or the empty string if there is no such
+    attribute or if <span title="resolve a url">resolving</span> it results in an error.</p>
 
    </dd>
 
@@ -74655,9 +74503,8 @@
 
    <dd>
 
-    <p>The value is the value of the element's <code
-    title="attr-data-value">value</code> attribute, if it has one, or
-    the empty string otherwise.</p>
+    <p>The value is the value of the element's <code title="attr-data-value">value</code> attribute,
+    if it has one, or the empty string otherwise.</p>
 
    </dd>
 
@@ -74681,143 +74528,116 @@
 
   </dl>
 
-  <p>The <dfn>URL property elements</dfn> are the <code>a</code>,
-  <code>area</code>, <code>audio</code>, <code>embed</code>,
-  <code>iframe</code>, <code>img</code>, <code>link</code>,
-  <code>object</code>, <code>source</code>, <code>track</code>, and
-  <code>video</code> elements.</p>
+  <p>The <dfn>URL property elements</dfn> are the <code>a</code>, <code>area</code>,
+  <code>audio</code>, <code>embed</code>, <code>iframe</code>, <code>img</code>, <code>link</code>,
+  <code>object</code>, <code>source</code>, <code>track</code>, and <code>video</code> elements.</p>
 
-  <p>If a property's <span
-  title="concept-property-value">value</span>, as defined by the
-  property's definition, is an <span>absolute URL</span>, the property
-  must be specified using a <span title="URL property elements">URL
-  property element</span>.</p>
+  <p>If a property's <span title="concept-property-value">value</span>, as defined by the property's
+  definition, is an <span>absolute URL</span>, the property must be specified using a <span
+  title="URL property elements">URL property element</span>.</p>
 
-  <p class="note">These requirements do not apply just because a
-  property value happens to match the syntax for a URL. They only
-  apply if the property is explicitly defined as taking such a
+  <p class="note">These requirements do not apply just because a property value happens to match the
+  syntax for a URL. They only apply if the property is explicitly defined as taking such a
   value.</p>
 
-  <p class="example">For example, a book about the first moon landing
-  <!-- 1969-07-20 --> could be called "mission:moon". A "title"
-  property from a vocabulary that defines a title as being a string
-  would not expect the title to be given in an <code>a</code> element,
-  even though it looks like a <span>URL</span>. On the other hand, if
-  there was a (rather narrowly scoped!) vocabulary for "books whose
-  titles look like URLs" which had a "title" property defined to take
-  a URL, then the property <em>would</em> expect the title to be given
-  in an <code>a</code> element (or one of the other <span>URL property
-  elements</span>), because of the requirement above.</p>
+  <p class="example">For example, a book about the first moon landing <!-- 1969-07-20 --> could be
+  called "mission:moon". A "title" property from a vocabulary that defines a title as being a string
+  would not expect the title to be given in an <code>a</code> element, even though it looks like a
+  <span>URL</span>. On the other hand, if there was a (rather narrowly scoped!) vocabulary for
+  "books whose titles look like URLs" which had a "title" property defined to take a URL, then the
+  property <em>would</em> expect the title to be given in an <code>a</code> element (or one of the
+  other <span>URL property elements</span>), because of the requirement above.</p>
 
 
   <div class="impl">
 
   <h4>Associating names with items</h4>
 
-  <p>To find <dfn>the properties of an item</dfn> defined by the
-  element <var title="">root</var>, the user agent must run the
-  following steps. These steps are also used to flag <span
+  <p>To find <dfn>the properties of an item</dfn> defined by the element <var title="">root</var>,
+  the user agent must run the following steps. These steps are also used to flag <span
   title="microdata error">microdata errors</span>.</p>
 
   <ol>
 
-   <li><p>Let <var title="">results</var>, <var title="">memory</var>,
-   and <var title="">pending</var> be empty lists of
-   elements.</p></li>
+   <li><p>Let <var title="">results</var>, <var title="">memory</var>, and <var
+   title="">pending</var> be empty lists of elements.</p></li>
 
-   <li><p>Add the element <var title="">root</var> to <var
-   title="">memory</var>.</p></li>
+   <li><p>Add the element <var title="">root</var> to <var title="">memory</var>.</p></li>
 
-   <li><p>Add the child elements of <var title="">root</var>, if any,
-   to <var title="">pending</var>.</p></li>
+   <li><p>Add the child elements of <var title="">root</var>, if any, to <var
+   title="">pending</var>.</p></li>
 
-   <li><p>If <var title="">root</var> has an <code
-   title="attr-itemref">itemref</code> attribute, <span title="split a
-   string on spaces">split the value of that <code
-   title="attr-itemref">itemref</code> attribute on spaces</span>. For
-   each resulting token <var title="">ID</var>, if there is an element
-   in the <span>home subtree</span> of <var title="">root</var> with
-   the <span title="concept-ID">ID</span> <var title="">ID</var>, then
-   add the first such element to <var title="">pending</var>.</p></li>
+   <li><p>If <var title="">root</var> has an <code title="attr-itemref">itemref</code> attribute,
+   <span title="split a string on spaces">split the value of that <code
+   title="attr-itemref">itemref</code> attribute on spaces</span>. For each resulting token <var
+   title="">ID</var>, if there is an element in the <span>home subtree</span> of <var
+   title="">root</var> with the <span title="concept-ID">ID</span> <var title="">ID</var>, then add
+   the first such element to <var title="">pending</var>.</p></li>
 
-   <li><p><i>Loop</i>: If <var title="">pending</var> is empty, jump
-   to the step labeled <i>end of loop</i>.</p></li>
+   <li><p><i>Loop</i>: If <var title="">pending</var> is empty, jump to the step labeled <i>end of
+   loop</i>.</p></li>
 
-   <li><p>Remove an element from <var title="">pending</var> and let
-   <var title="">current</var> be that element.</p></li>
+   <li><p>Remove an element from <var title="">pending</var> and let <var title="">current</var> be
+   that element.</p></li>
 
-   <li><p>If <var title="">current</var> is already in <var
-   title="">memory</var>, there is a <span>microdata error</span>;
-   return to the step labeled <i>loop</i>.</p></li>
+   <li><p>If <var title="">current</var> is already in <var title="">memory</var>, there is a
+   <span>microdata error</span>; return to the step labeled <i>loop</i>.</p></li>
 
-   <li><p>Add <var title="">current</var> to <var
-   title="">memory</var>.</p></li>
+   <li><p>Add <var title="">current</var> to <var title="">memory</var>.</p></li>
 
-   <li><p>If <var title="">current</var> does not
-   have an <code title="attr-itemscope">itemscope</code> attribute,
-   then: add all the child elements of <var title="">current</var> to
-   <var title="">pending</var>.</p></li>
+   <li><p>If <var title="">current</var> does not have an <code
+   title="attr-itemscope">itemscope</code> attribute, then: add all the child elements of <var
+   title="">current</var> to <var title="">pending</var>.</p></li>
 
-   <li><p>If <var title="">current</var> has an <code
-   title="attr-itemprop">itemprop</code> attribute specified and has
-   one or more <span>property names</span>, then add <var
+   <li><p>If <var title="">current</var> has an <code title="attr-itemprop">itemprop</code>
+   attribute specified and has one or more <span>property names</span>, then add <var
    title="">current</var> to <var title="">results</var>.</p></li>
 
    <li><p>Return to the step labeled <i>loop</i>.</p></li>
 
-   <li><p><i>End of loop</i>: Sort <var title="">results</var> in
-   <span>tree order</span>.</p></li>
+   <li><p><i>End of loop</i>: Sort <var title="">results</var> in <span>tree order</span>.</p></li>
 
    <li><p>Return <var title="">results</var>.</p></li>
 
   </ol>
 
-  <p>A document must not contain any <span
-  title="concept-item">items</span> for which the algorithm to find
-  <span>the properties of an item</span> finds any <dfn
-  title="microdata error">microdata errors</dfn>.</p>
+  <p>A document must not contain any <span title="concept-item">items</span> for which the algorithm
+  to find <span>the properties of an item</span> finds any <dfn title="microdata error">microdata
+  errors</dfn>.</p>
 
-  <p>An <span title="concept-item">item</span> is a <dfn
-  title="top-level microdata items">top-level microdata item</dfn> if
-  its element does not have an <code
-  title="attr-itemprop">itemprop</code> attribute.</p>
+  <p>An <span title="concept-item">item</span> is a <dfn title="top-level microdata items">top-level
+  microdata item</dfn> if its element does not have an <code title="attr-itemprop">itemprop</code>
+  attribute.</p>
 
 <!--(this is currently redundant with "requirement itemprop" below)
-  <p>An <span title="concept-item">item</span> is a <dfn title="used
-  microdata items">used microdata item</dfn> if it is a <span
-  title="top-level microdata items">top-level microdata item</span>,
-  or if it has an <code title="attr-itemprop">itemprop</code>
-  attribute and would be <span title="the properties of an item">found
-  to be the property</span> of an <span
-  title="concept-item">item</span> that is itself a <span title="used
-  microdata items">used microdata item</span>.</p>
+  <p>An <span title="concept-item">item</span> is a <dfn title="used microdata items">used microdata
+  item</dfn> if it is a <span title="top-level microdata items">top-level microdata item</span>, or
+  if it has an <code title="attr-itemprop">itemprop</code> attribute and would be <span title="the
+  properties of an item">found to be the property</span> of an <span
+  title="concept-item">item</span> that is itself a <span title="used microdata items">used
+  microdata item</span>.</p>
 
-  <p>All <span title="concept-item">items</span> in a document must be
-  <span>used microdata items</span>.</p>
+  <p>All <span title="concept-item">items</span> in a document must be <span>used microdata
+  items</span>.</p>
 -->
 
-  <p>All <code title="attr-itemref">itemref</code> attributes in a
-  <code>Document</code> must be such that there are no cycles in the
-  graph formed from representing each <span
-  title="concept-item">item</span> in the <code>Document</code> as a
-  node in the graph and each <span title="the properties of an
-  item">property</span> of an item whose <span
-  title="concept-property-value">value</span> is another item as an
-  edge in the graph connecting those two items.</p>
+  <p>All <code title="attr-itemref">itemref</code> attributes in a <code>Document</code> must be
+  such that there are no cycles in the graph formed from representing each <span
+  title="concept-item">item</span> in the <code>Document</code> as a node in the graph and each
+  <span title="the properties of an item">property</span> of an item whose <span
+  title="concept-property-value">value</span> is another item as an edge in the graph connecting
+  those two items.</p>
 
   <!-- "requirement itemprop" (see above) -->
   <p>A document must not contain any elements that have an <code
-  title="attr-itemprop">itemprop</code> attribute that would not be
-  found to be a property of any of the <span
-  title="concept-item">items</span> in that document were their <span
-  title="the properties of an item">properties</span> all to be
-  determined.</p>
+  title="attr-itemprop">itemprop</code> attribute that would not be found to be a property of any of
+  the <span title="concept-item">items</span> in that document were their <span title="the
+  properties of an item">properties</span> all to be determined.</p>
 
   <div class="example">
 
-   <p>In this example, a single license statement is applied to two
-   works, using <code title="attr-itemref">itemref</code> from the
-   items representing the works:</p>
+   <p>In this example, a single license statement is applied to two works, using <code
+   title="attr-itemref">itemref</code> from the items representing the works:</p>
 
    <pre><!DOCTYPE HTML>
 <html>
@@ -74842,8 +74662,8 @@
  </body>
 </html></pre>
 
-   <p>The above results in two items with the type "<code
-   title="">http://n.whatwg.org/work</code>", one with:</p>
+   <p>The above results in two items with the type "<code title="">http://n.whatwg.org/work</code>",
+   one with:</p>
 
    <dl class="brief">
     <dt>work
@@ -74872,13 +74692,11 @@
 
   <h4>Microdata and other namespaces</h4>
 
-  <p>Currently, the <code title="attr-itemscope">itemscope</code>,
-  <code title="attr-itemprop">itemprop</code>, and other microdata
-  attributes are only defined for <span>HTML elements</span>. This
-  means that attributes with the literal names "<code
-  title="">itemscope</code>", "<code title="">itemprop</code>", etc,
-  do not cause microdata processing to occur on elements in other
-  namespaces, such as SVG.</p>
+  <p>Currently, the <code title="attr-itemscope">itemscope</code>, <code
+  title="attr-itemprop">itemprop</code>, and other microdata attributes are only defined for
+  <span>HTML elements</span>. This means that attributes with the literal names "<code
+  title="">itemscope</code>", "<code title="">itemprop</code>", etc, do not cause microdata
+  processing to occur on elements in other namespaces, such as SVG.</p>
 
   <div class="example">
 
@@ -74899,7 +74717,10 @@
 
    <dd>
 
-    <p>Returns a <code>NodeList</code> of the elements in the <code>Document</code> that create <span title="concept-item">items</span>, that are not part of other <span title="concept-item">items</span>, and that are of the types given in the argument, if any are listed.</p>
+    <p>Returns a <code>NodeList</code> of the elements in the <code>Document</code> that create
+    <span title="concept-item">items</span>, that are not part of other <span
+    title="concept-item">items</span>, and that are of the types given in the argument, if any are
+    listed.</p>
 
     <p>The <var title="">types</var> argument is interpreted as a space-separated list of types.</p>
 
@@ -74909,11 +74730,9 @@
 
    <dd>
 
-    <p>If the element has an <code
-    title="attr-itemscope">itemscope</code> attribute, returns an
-    <code>HTMLPropertiesCollection</code> object with all the element's
-    properties. Otherwise, an empty
-    <code>HTMLPropertiesCollection</code> object.</p>
+    <p>If the element has an <code title="attr-itemscope">itemscope</code> attribute, returns an
+    <code>HTMLPropertiesCollection</code> object with all the element's properties. Otherwise, an
+    empty <code>HTMLPropertiesCollection</code> object.</p>
 
    </dd>
 
@@ -74921,15 +74740,12 @@
 
    <dd>
 
-    <p>Returns the element's <span
-    title="concept-property-value">value</span>.</p>
+    <p>Returns the element's <span title="concept-property-value">value</span>.</p>
 
-    <p>Can be set, to change the element's <span
-    title="concept-property-value">value</span>. Setting the <span
-    title="concept-property-value">value</span> when the element has
-    no <code title="attr-itemprop">itemprop</code> attribute or when
-    the element's value is an <span title="concept-item">item</span>
-    throws an <code>InvalidAccessError</code> exception.</p>
+    <p>Can be set, to change the element's <span title="concept-property-value">value</span>.
+    Setting the <span title="concept-property-value">value</span> when the element has no <code
+    title="attr-itemprop">itemprop</code> attribute or when the element's value is an <span
+    title="concept-item">item</span> throws an <code>InvalidAccessError</code> exception.</p>
 
    </dd>
 
@@ -74937,54 +74753,41 @@
 
   <div class="impl">
 
-  <p>The <dfn
-  title="dom-document-getItems"><code>document.getItems(<var
-  title="">typeNames</var>)</code></dfn> method takes an optional
-  string that contains an <span>unordered set of unique
-  space-separated tokens</span> that are <span>case-sensitive</span>,
-  representing types. When called, the method must return a
-  <span>live</span> <code>NodeList</code> object containing all the
-  elements in the document, in <span>tree order</span>, that are each
-  <span>top-level microdata items</span> whose <span title="item
-  types">types</span> include all the types specified in the method's
-  argument, having obtained the types by <span title="split a string
-  on spaces">splitting the string on spaces</span>. If there are no
-  tokens specified in the argument, or if the argument is missing,
-  then the method must return a <code>NodeList</code> containing all
-  the <span>top-level microdata items</span> in the document. When the
-  method is invoked on a <code>Document</code> object again with the
-  same argument, the user agent may return the same object as the
-  object returned by the earlier call. In other cases, a new
+  <p>The <dfn title="dom-document-getItems"><code>document.getItems(<var
+  title="">typeNames</var>)</code></dfn> method takes an optional string that contains an
+  <span>unordered set of unique space-separated tokens</span> that are <span>case-sensitive</span>,
+  representing types. When called, the method must return a <span>live</span> <code>NodeList</code>
+  object containing all the elements in the document, in <span>tree order</span>, that are each
+  <span>top-level microdata items</span> whose <span title="item types">types</span> include all the
+  types specified in the method's argument, having obtained the types by <span title="split a string
+  on spaces">splitting the string on spaces</span>. If there are no tokens specified in the
+  argument, or if the argument is missing, then the method must return a <code>NodeList</code>
+  containing all the <span>top-level microdata items</span> in the document. When the method is
+  invoked on a <code>Document</code> object again with the same argument, the user agent may return
+  the same object as the object returned by the earlier call. In other cases, a new
   <code>NodeList</code> object must be returned.</p>
 
-  <p>The <dfn title="dom-itemScope"><code>itemScope</code></dfn> IDL
-  attribute on <span>HTML elements</span> must <span>reflect</span>
-  the <code title="attr-itemscope">itemscope</code> content attribute.
-  The <dfn title="dom-itemType"><code>itemType</code></dfn> IDL
-  attribute on <span>HTML elements</span> must <span>reflect</span>
-  the <code title="attr-itemtype">itemtype</code> content attribute.
-  The <dfn title="dom-itemId"><code>itemId</code></dfn> IDL attribute
-  on <span>HTML elements</span> must <span>reflect</span> the <code
-  title="attr-itemid">itemid</code> content attribute. The <dfn
-  title="dom-itemProp"><code>itemProp</code></dfn> IDL attribute on
+  <p>The <dfn title="dom-itemScope"><code>itemScope</code></dfn> IDL attribute on <span>HTML
+  elements</span> must <span>reflect</span> the <code title="attr-itemscope">itemscope</code>
+  content attribute. The <dfn title="dom-itemType"><code>itemType</code></dfn> IDL attribute on
   <span>HTML elements</span> must <span>reflect</span> the <code
-  title="attr-itemprop">itemprop</code> content attribute. The <dfn
-  title="dom-itemRef"><code>itemRef</code></dfn> IDL attribute on
-  <span>HTML elements</span> must <span>reflect</span> the <code
-  title="attr-itemref">itemref</code> content attribute.</p>
+  title="attr-itemtype">itemtype</code> content attribute. The <dfn
+  title="dom-itemId"><code>itemId</code></dfn> IDL attribute on <span>HTML elements</span> must
+  <span>reflect</span> the <code title="attr-itemid">itemid</code> content attribute. The <dfn
+  title="dom-itemProp"><code>itemProp</code></dfn> IDL attribute on <span>HTML elements</span> must
+  <span>reflect</span> the <code title="attr-itemprop">itemprop</code> content attribute. The <dfn
+  title="dom-itemRef"><code>itemRef</code></dfn> IDL attribute on <span>HTML elements</span> must
+  <span>reflect</span> the <code title="attr-itemref">itemref</code> content attribute.</p>
 
-  <p>The <dfn title="dom-properties"><code>properties</code></dfn> IDL
-  attribute on <span>HTML elements</span> must return an
-  <code>HTMLPropertiesCollection</code> rooted at the
-  <code>Document</code> node, whose filter matches only elements that
-  are <span title="the properties of an item">the properties of the
-  item</span> created by the element on which the attribute was
-  invoked, while that element is an <span
-  title="concept-item">item</span>, and matches nothing the rest of
-  the time.</p>
+  <p>The <dfn title="dom-properties"><code>properties</code></dfn> IDL attribute on <span>HTML
+  elements</span> must return an <code>HTMLPropertiesCollection</code> rooted at the
+  <code>Document</code> node, whose filter matches only elements that are <span title="the
+  properties of an item">the properties of the item</span> created by the element on which the
+  attribute was invoked, while that element is an <span title="concept-item">item</span>, and
+  matches nothing the rest of the time.</p>
 
-  <p>The <dfn title="dom-itemValue"><code>itemValue</code></dfn> IDL
-  attribute's behavior depends on the element, as follows:</p>
+  <p>The <dfn title="dom-itemValue"><code>itemValue</code></dfn> IDL attribute's behavior depends on
+  the element, as follows:</p>
 
   <dl>
 
@@ -74996,83 +74799,69 @@
 
    <dt>If the element has an <code title="attr-itemscope">itemscope</code> attribute</dt>
 
-   <dd><p>The attribute must return the element itself on getting and
-   must throw an <code>InvalidAccessError</code> exception on
-   setting.</p>
+   <dd><p>The attribute must return the element itself on getting and must throw an
+   <code>InvalidAccessError</code> exception on setting.</p>
 
 
    <dt>If the element is a <code>meta</code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <span
-   title="reflect">reflecting</span> the element's <code
-   title="attr-meta-content">content</code> content
-   attribute.</p></dd>
+   <dd><p>The attribute must act as it would if it was <span title="reflect">reflecting</span> the
+   element's <code title="attr-meta-content">content</code> content attribute.</p></dd>
 
 
-   <dt>If the element is an <code>audio</code>, <code>embed</code>,
-   <code>iframe</code>, <code>img</code>, <code>source</code>,
-   <code>track</code>, or <code>video</code> element</dt>
+   <dt>If the element is an <code>audio</code>, <code>embed</code>, <code>iframe</code>,
+   <code>img</code>, <code>source</code>, <code>track</code>, or <code>video</code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <span
-   title="reflect">reflecting</span> the element's <code
-   title="">src</code> content attribute.</p></dd>
+   <dd><p>The attribute must act as it would if it was <span title="reflect">reflecting</span> the
+   element's <code title="">src</code> content attribute.</p></dd>
 
 
-   <dt>If the element is an <code>a</code>, <code>area</code>, or
-   <code>link</code> element</dt>
+   <dt>If the element is an <code>a</code>, <code>area</code>, or <code>link</code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <span
-   title="reflect">reflecting</span> the element's <code
-   title="">href</code> content attribute.</p></dd>
+   <dd><p>The attribute must act as it would if it was <span title="reflect">reflecting</span> the
+   element's <code title="">href</code> content attribute.</p></dd>
 
 
    <dt>If the element is an <code>object</code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <span
-   title="reflect">reflecting</span> the element's <code
-   title="">data</code> content attribute.</p></dd>
+   <dd><p>The attribute must act as it would if it was <span title="reflect">reflecting</span> the
+   element's <code title="">data</code> content attribute.</p></dd>
 
 
    <dt>If the element is a <code>data</code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <span
-   title="reflect">reflecting</span> the element's <code
-   title="attr-data-value">value</code> content attribute.</p></dd>
+   <dd><p>The attribute must act as it would if it was <span title="reflect">reflecting</span> the
+   element's <code title="attr-data-value">value</code> content attribute.</p></dd>
 
 
    <dt>If the element is a <code>time</code> element</dt>
 
-   <dd><p>On getting, if the element has a <code
-   title="attr-time-datetime">datetime</code> content attribute, the
-   IDL attribute must return that content attribute's value;
-   otherwise, it must return the element's <code>textContent</code>.
-   On setting, the IDL attribute must act as it would if it was <span
-   title="reflect">reflecting</span> the element's <code
-   title="attr-time-datetime">datetime</code> content
-   attribute.</p></dd>
+   <dd><p>On getting, if the element has a <code title="attr-time-datetime">datetime</code> content
+   attribute, the IDL attribute must return that content attribute's value; otherwise, it must
+   return the element's <code>textContent</code>. On setting, the IDL attribute must act as it would
+   if it was <span title="reflect">reflecting</span> the element's <code
+   title="attr-time-datetime">datetime</code> content attribute.</p></dd>
 
 
    <dt>Otherwise</dt>
 
-   <dd><p>The attribute must act the same as the element's
-   <code>textContent</code> attribute.</p></dd>
+   <dd><p>The attribute must act the same as the element's <code>textContent</code>
+   attribute.</p></dd>
 
   </dl>
 
-  <p>When the <code title="dom-itemValue">itemValue</code> IDL
-  attribute is <span title="reflect">reflecting</span> a content
-  attribute or acting like the element's <code>textContent</code>
-  attribute, the user agent must, on setting, convert the new value to
-  the IDL <code title="">DOMString</code> value before using it
-  according to the mappings described above.</p>
+  <p>When the <code title="dom-itemValue">itemValue</code> IDL attribute is <span
+  title="reflect">reflecting</span> a content attribute or acting like the element's
+  <code>textContent</code> attribute, the user agent must, on setting, convert the new value to the
+  IDL <code title="">DOMString</code> value before using it according to the mappings described
+  above.</p>
 
   </div>
 
   <div class="example">
 
-   <p>In this example, a script checks to see if a particular element
-   <var title="">element</var> is declaring a particular property, and
-   if it is, it increments a counter:</p>
+   <p>In this example, a script checks to see if a particular element <var title="">element</var> is
+   declaring a particular property, and if it is, it increments a counter:</p>
 
    <pre>if (element.itemProp.contains('color'))
   count += 1;</pre>
@@ -75081,9 +74870,9 @@
 
   <div class="example">
 
-   <p>This script iterates over each of the values of an element's
-   <code title="attr-itemref">itemref</code> attribute, calling a
-   function for each referenced element:</p>
+   <p>This script iterates over each of the values of an element's <code
+   title="attr-itemref">itemref</code> attribute, calling a function for each referenced
+   element:</p>
 
    <pre>for (var index = 0; index < element.itemRef.length; index += 1)
   process(document.getElementById(element.itemRef[index]));</pre>
@@ -75091,22 +74880,24 @@
   </div>
 
 
-  <h3 id="mdvocabs">Microdata vocabularies</h3>
+  <h3 id="mdvocabs">Sample microdata vocabularies</h3>
 
+  <p>The vocabularies in this section are primarily intended to demonstrate how a vocabulary is
+  specified, though they are also usable in their own right.</p>
+
+
   <h4>vCard</h4>
 
   <p>An item with the <span title="item types">item type</span> <dfn
-  title="md-vcard"><code>http://microformats.org/profile/hcard</code></dfn>
-  represents a person's or organization's contact information.</p>
+  title="md-vcard"><code>http://microformats.org/profile/hcard</code></dfn> represents a person's or
+  organization's contact information.</p>
 
-  <p>This vocabulary does not <span>support global identifiers for
-  items</span>.</p>
+  <p>This vocabulary does not <span>support global identifiers for items</span>.</p>
 
-  <p>The following are the type's <span title="defined property
-  name">defined property names</span>. They are based on the
-  vocabulary defined in the vCard 4.0 specification and its
-  extensions, where more information on how to interpret the values
-  can be found. <a href="#refsRFC6350">[RFC6350]</a></p>
+  <p>The following are the type's <span title="defined property name">defined property names</span>.
+  They are based on the vocabulary defined in the vCard 4.0 specification and its extensions, where
+  more information on how to interpret the values can be found. <a
+  href="#refsRFC6350">[RFC6350]</a></p>
 
   <dl>
 
@@ -76287,11 +76078,9 @@
 
   <h5>Conversion to vCard</h5>
 
-  <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 title="extracting a vCard">extract any vCard data
-  represented by those nodes</dfn> (only the first vCard is
-  returned):</p>
+  <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 title="extracting a vCard">extract any vCard data represented
+  by those nodes</dfn> (only the first vCard is returned):</p>
 
   <ol>
 
@@ -76740,11 +76529,9 @@
 
   </ol>
 
-  <p>When the above algorithm says that the user agent is to <dfn>add
-  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:</p>
+  <p>When the above algorithm says that the user agent is to <dfn>add 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:</p>
 
   <ol>
 
@@ -76825,9 +76612,8 @@
 
   </ol>
 
-  <p>When the steps above require the user agent to obtain the result
-  of <dfn>collecting vCard subproperties</dfn> named <var
-  title="">subname</var> in <var title="">subitem</var>, the user
+  <p>When the steps above require the user agent to obtain the result of <dfn>collecting vCard
+  subproperties</dfn> named <var title="">subname</var> in <var title="">subitem</var>, the user
   agent must run the following steps:</p>
 
   <ol>
@@ -76864,9 +76650,8 @@
 
   </ol>
 
-  <p>When the steps above require the user agent to obtain the result
-  of <dfn>collecting the first vCard subproperty</dfn> named <var
-  title="">subname</var> in <var title="">subitem</var>, the user
+  <p>When the steps above require the user agent to obtain the result of <dfn>collecting the first
+  vCard subproperty</dfn> named <var title="">subname</var> in <var title="">subitem</var>, the user
   agent must run the following steps:</p>
 
   <ol>
@@ -76889,9 +76674,8 @@
 
   </ol>
 
-  <p>When the above algorithms say the user agent is to <dfn
-  title="escaping the vCard text string">escape the vCard text
-  string</dfn> <var title="">value</var>, the user agent must use the
+  <p>When the above algorithms say the user agent is to <dfn title="escaping the vCard text
+  string">escape the vCard text string</dfn> <var title="">value</var>, the user agent must use the
   following steps:</p>
 
   <ol>
@@ -76922,12 +76706,10 @@
 
   </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">http://microformats.org/profile/hcard</code> <span
-  title="item types">item type</span> and <span title="defined
-  property name">defined property names</span>.</p> <!-- of course
-  since vcard doesn't define error handling, this is somewhat
+  <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">http://microformats.org/profile/hcard</code>
+  <span title="item types">item type</span> and <span title="defined property name">defined property
+  names</span>.</p> <!-- of course since vcard doesn't define error handling, this is somewhat
   problematic. -->
 
 
@@ -76938,8 +76720,7 @@
 
   <div class="example">
 
-   <p>Here is a long example vCard for a fictional character called
-   "Jack Bauer":</p>
+   <p>Here is a long example vCard for a fictional character called "Jack Bauer":</p>
 
    <pre><section id="jack" itemscope itemtype="http://microformats.org/profile/hcard">
  <h1 itemprop="fn">
@@ -76986,17 +76767,15 @@
  </ins>
 </section></pre>
 
-   <p>The odd line wrapping is needed because newlines are meaningful
-   in microdata: newlines would be preserved in a conversion to, for
-   example, the vCard format.</p>
+   <p>The odd line wrapping is needed because newlines are meaningful in microdata: newlines would
+   be preserved in a conversion to, for example, the vCard format.</p>
 
   </div>
 
   <div class="example">
 
-   <p>This example shows a site's contact details (using the
-   <code>address</code> element) containing an address with two street
-   components:</p>
+   <p>This example shows a site's contact details (using the <code>address</code> element)
+   containing an address with two street components:</p>
 
    <pre><address itemscope itemtype="http://microformats.org/profile/hcard">
  <strong itemprop="fn"><span itemprop="n" itemscope><span itemprop="given-name">Alfred</span>
@@ -77013,20 +76792,17 @@
 
   <div class="example">
 
-   <p>The vCard vocabulary can be used to just mark up people's
-   names:</p>
+   <p>The vCard vocabulary can be used to just mark up people's names:</p>
 
    <pre><span itemscope itemtype="http://microformats.org/profile/hcard"
 ><span itemprop=fn><span itemprop="n" itemscope><span itemprop="given-name"
 >George</span> <span itemprop="family-name">Washington</span></span
 ></span></span></pre>
 
-   <p>This creates a single item with a two name-value pairs, one with
-   the name "fn" and the value "George Washington", and the other with
-   the name "n" and a second item as its value, the second item having
-   the two name-value pairs "given-name" and "family-name" with the
-   values "George" and "Washington" respectively. This is defined to
-   map to the following vCard:</p>
+   <p>This creates a single item with a two name-value pairs, one with the name "fn" and the value
+   "George Washington", and the other with the name "n" and a second item as its value, the second
+   item having the two name-value pairs "given-name" and "family-name" with the values "George" and
+   "Washington" respectively. This is defined to map to the following vCard:</p>
 
    <pre>BEGIN:VCARD
 PROFILE:VCARD
@@ -77042,21 +76818,17 @@
   <h4>vEvent</h4>
 
   <p>An item with the <span title="item types">item type</span> <dfn
-  title="md-vevent"><code>http://microformats.org/profile/hcalendar#vevent</code></dfn>
-  represents an event.</p>
+  title="md-vevent"><code>http://microformats.org/profile/hcalendar#vevent</code></dfn> represents
+  an event.</p>
 
-  <p>This vocabulary does not <span>support global identifiers for
-  items</span>.</p>
+  <p>This vocabulary does not <span>support global identifiers for items</span>.</p>
 
-  <p>The following are the type's <span title="defined property
-  name">defined property names</span>. They are based on the
-  vocabulary defined in the iCalendar specification, where more
-  information on how to interpret the values can be found. <a
-  href="#refsRFC2445">[RFC2445]</a></p>
+  <p>The following are the type's <span title="defined property name">defined property names</span>.
+  They are based on the vocabulary defined in the iCalendar specification, where more information on
+  how to interpret the values can be found. <a href="#refsRFC2445">[RFC2445]</a></p>
 
-  <p class="note">Only the parts of the iCalendar vocabulary relating
-  to events are used here; this vocabulary cannot express a complete
-  iCalendar instance.</p>
+  <p class="note">Only the parts of the iCalendar vocabulary relating to events are used here; this
+  vocabulary cannot express a complete iCalendar instance.</p>
 
   <dl>
 
@@ -77679,9 +77451,8 @@
 
   <h5>Conversion to iCalendar</h5>
 
-  <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 title="extracting vEvent data">extract any vEvent data
+  <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 title="extracting vEvent data">extract any vEvent data
   represented by those nodes</dfn>:</p>
 
   <ol>
@@ -77812,11 +77583,9 @@
 
   </ol>
 
-  <p>When the above algorithm says that the user agent is to <dfn>add
-  an iCalendar line</dfn> consisting of a type <var
-  title="">type</var>, a value <var title="">value</var>, and
-  optionally an annotation, to a string <var title="">output</var>, it
-  must run the following steps:</p>
+  <p>When the above algorithm says that the user agent is to <dfn>add an iCalendar line</dfn>
+  consisting of a type <var title="">type</var>, a value <var title="">value</var>, and optionally
+  an annotation, to a string <var title="">output</var>, it must run the following steps:</p>
 
   <ol>
 
@@ -77912,14 +77681,11 @@
 
   </ol>
 
-  <p class="note">This algorithm can generate invalid iCalendar
-  output, if the input does not conform to the rules described for the
-  <code
-  title="md-vevent">http://microformats.org/profile/hcalendar#vevent</code>
-  <span title="item types">item type</span> and <span title="defined property
-  name">defined property names</span>.</p> <!-- of course since
-  iCalendar doesn't define error handling, this is somewhat
-  problematic. -->
+  <p class="note">This algorithm can generate invalid iCalendar output, if the input does not
+  conform to the rules described for the <code
+  title="md-vevent">http://microformats.org/profile/hcalendar#vevent</code> <span title="item
+  types">item type</span> and <span title="defined property name">defined property names</span>.</p>
+  <!-- of course since iCalendar doesn't define error handling, this is somewhat problematic. -->
 
 
 
@@ -77931,8 +77697,7 @@
 
   <div class="example">
 
-   <p>Here is an example of a page that uses the vEvent vocabulary to
-   mark up an event:</p>
+   <p>Here is an example of a page that uses the vEvent vocabulary to mark up an event:</p>
 
    <pre><body itemscope itemtype="http://microformats.org/profile/hcalendar#vevent">
  ...
@@ -78014,13 +77779,12 @@
   <h4>Licensing works</h4>
 
   <p>An item with the <span title="item types">item type</span> <dfn
-  title="md-work"><code>http://n.whatwg.org/work</code></dfn>
-  represents a work (e.g. an article, an image, a video, a song,
-  etc). This type is primarily intended to allow authors to include
+  title="md-work"><code>http://n.whatwg.org/work</code></dfn> represents a work (e.g. an article, an
+  image, a video, a song, etc). This type is primarily intended to allow authors to include
   licensing information for works.</p>
 
-  <p>The following are the type's <span title="defined property
-  name">defined property names</span>.</p>
+  <p>The following are the type's <span title="defined property name">defined property
+  names</span>.</p>
 
   <dl>
 
@@ -78105,9 +77869,8 @@
 
   <div class="example">
 
-   <p>This example shows an embedded image entitled <cite>My
-   Pond</cite>, licensed under the Creative Commons Attribution-Share
-   Alike 3.0 United States License and the MIT license
+   <p>This example shows an embedded image entitled <cite>My Pond</cite>, licensed under the
+   Creative Commons Attribution-Share Alike 3.0 United States License and the MIT license
    simultaneously.</p>
 
    <pre><figure <strong>itemscope itemtype="http://n.whatwg.org/work"</strong>>
@@ -78132,10 +77895,9 @@
 
   <h4>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 title="extracting JSON">extract the microdata from those
-  nodes into a JSON form</dfn>:</p>
+  <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 title="extracting JSON">extract the microdata from those nodes
+  into a JSON form</dfn>:</p>
 
   <ol>
 
@@ -78163,14 +77925,13 @@
 
   </ol>
 
-  <p class="note">This algorithm returns an object with a single
-  property that is an array, instead of just returning an array, so
-  that it is possible to extend the algorithm in the future if
+  <p class="note">This algorithm returns an object with a single property that is an array, instead
+  of just returning an array, so that it is possible to extend the algorithm in the future if
   necessary.</p>
 
-  <p>When the user agent is to <dfn>get the object</dfn> for an item
-  <var title="">item</var>, optionally with a list of elements <var
-  title="">memory</var>, it must run the following substeps:</p>
+  <p>When the user agent is to <dfn>get the object</dfn> for an item <var title="">item</var>,
+  optionally with a list of elements <var title="">memory</var>, it must run the following
+  substeps:</p>
 
   <ol>
 
@@ -78253,14 +78014,17 @@
   </div>
 
 
+
+
+<!--TOPIC:HTML-->
+
   <h2 id="browsers">Loading Web pages</h2>
 
   <div class="impl">
 
-  <p>This section describes features that apply most directly to Web
-  browsers. Having said that, except where specified otherwise, the
-  requirements defined in this section <em>do</em> apply to all user
-  agents, whether they are Web browsers or not.</p>
+  <p>This section describes features that apply most directly to Web browsers. Having said that,
+  except where specified otherwise, the requirements defined in this section <em>do</em> apply to
+  all user agents, whether they are Web browsers or not.</p>
 
   </div>
 
@@ -78268,71 +78032,55 @@
 
   <h3 id="windows">Browsing contexts</h3>
 
-  <p>A <dfn>browsing context</dfn> is an environment in which
-  <code>Document</code> objects are presented to the user.</p>
+  <p>A <dfn>browsing context</dfn> is an environment in which <code>Document</code> objects are
+  presented to the user.</p>
 
-  <p class="note">A tab or window in a Web browser typically contains
-  a <span>browsing context</span>, as does an <code>iframe</code><span
-  class="impl"> or <code>frame</code>s in a
+  <p class="note">A tab or window in a Web browser typically contains a <span>browsing
+  context</span>, as does an <code>iframe</code><span class="impl"> or <code>frame</code>s in a
   <code>frameset</code></span>.</p>
 
-  <p>Each <span>browsing context</span> has a corresponding
-  <code>WindowProxy</code> object.</p>
+  <p>Each <span>browsing context</span> has a corresponding <code>WindowProxy</code> object.</p>
 
-  <p>A <span>browsing context</span> has a <span>session
-  history</span>, which lists the <code>Document</code> objects that
-  that <span>browsing context</span> has presented, is presenting, or
-  will present. At any time, one <code>Document</code> in each
-  <span>browsing context</span> is designated the <dfn>active
-  document</dfn>. A <code>Document</code>'s <span>browsing
-  context</span> is that <span>browsing context</span> whose
-  <span>session history</span> contains the <code>Document</code>, if
-  any. (A <code>Document</code> created using an API such as <code
-  title="dom-DOMImplementation-createDocument">createDocument()</code>
-  has no <span>browsing context</span>.)</p>
+  <p>A <span>browsing context</span> has a <span>session history</span>, which lists the
+  <code>Document</code> objects that that <span>browsing context</span> has presented, is
+  presenting, or will present. At any time, one <code>Document</code> in each <span>browsing
+  context</span> is designated the <dfn>active document</dfn>. A <code>Document</code>'s
+  <span>browsing context</span> is that <span>browsing context</span> whose <span>session
+  history</span> contains the <code>Document</code>, if any. (A <code>Document</code> created using
+  an API such as <code title="dom-DOMImplementation-createDocument">createDocument()</code> has no
+  <span>browsing context</span>.)</p>
 
-  <p>Each <code>Document</code> is associated with a
-  <code>Window</code> object. A <span>browsing context</span>'s
-  <code>WindowProxy</code> object forwards everything to the
-  <span>browsing context</span>'s <span>active document</span>'s
-  <code>Window</code> object.</p>
+  <p>Each <code>Document</code> is associated with a <code>Window</code> object. A <span>browsing
+  context</span>'s <code>WindowProxy</code> object forwards everything to the <span>browsing
+  context</span>'s <span>active document</span>'s <code>Window</code> object.</p>
 
-  <p class="note">In general, there is a 1-to-1 mapping from the
-  <code>Window</code> object to the <code>Document</code> object.
-  There are two exceptions. First, a <code>Window</code> can be reused
-  for the presentation of a second <code>Document</code> in the same
-  <span>browsing context</span>, such that the mapping is then 1-to-2.
-  This occurs when a <span>browsing context</span> is <span
-  title="navigate">navigated</span> from the initial
-  <code>about:blank</code> <code>Document</code> to another, with
-  <span>replacement enabled</span>. Second, a <code>Document</code>
-  can end up being reused for several <code>Window</code> objects when
-  the <code title="dom-document-open">document.open()</code> method is
-  used, such that the mapping is then many-to-1.</p>
+  <p class="note">In general, there is a 1-to-1 mapping from the <code>Window</code> object to the
+  <code>Document</code> object. There are two exceptions. First, a <code>Window</code> can be reused
+  for the presentation of a second <code>Document</code> in the same <span>browsing context</span>,
+  such that the mapping is then 1-to-2. This occurs when a <span>browsing context</span> is <span
+  title="navigate">navigated</span> from the initial <code>about:blank</code> <code>Document</code>
+  to another, with <span>replacement enabled</span>. Second, a <code>Document</code> can end up
+  being reused for several <code>Window</code> objects when the <code
+  title="dom-document-open">document.open()</code> method is used, such that the mapping is then
+  many-to-1.</p>
 
-  <p class="note">A <code>Document</code> does not necessarily have a
-  <span>browsing context</span> associated with it. In particular,
-  data mining tools are likely to never instantiate browsing
+  <p class="note">A <code>Document</code> does not necessarily have a <span>browsing context</span>
+  associated with it. In particular, data mining tools are likely to never instantiate browsing
   contexts.</p>
 
   <hr>
 
-  <p>A <span>browsing context</span> can have a <dfn>creator browsing
-  context</dfn>, the <span>browsing context</span> that was
-  responsible for its creation. If a <span>browsing context</span> has
-  a <span>parent browsing context</span>, then that is its
-  <span>creator browsing context</span>. Otherwise, if the
-  <span>browsing context</span> has an <span>opener browsing
-  context</span>, then <em>that</em> is its <span>creator browsing
-  context</span>. Otherwise, the <span>browsing context</span> has no
-  <span>creator browsing context</span>.</p>
+  <p>A <span>browsing context</span> can have a <dfn>creator browsing context</dfn>, the
+  <span>browsing context</span> that was responsible for its creation. If a <span>browsing
+  context</span> has a <span>parent browsing context</span>, then that is its <span>creator browsing
+  context</span>. Otherwise, if the <span>browsing context</span> has an <span>opener browsing
+  context</span>, then <em>that</em> is its <span>creator browsing context</span>. Otherwise, the
+  <span>browsing context</span> has no <span>creator browsing context</span>.</p>
 
-  <p>If a <span>browsing context</span> <var title="">A</var> has a
-  <span>creator browsing context</span>, then the
-  <code>Document</code> that was the <span>active document</span> of
-  that <span>creator browsing context</span> at the time <var
-  title="">A</var> was created is the <dfn>creator
-  <code>Document</code></dfn>.</p>
+  <p>If a <span>browsing context</span> <var title="">A</var> has a <span>creator browsing
+  context</span>, then the <code>Document</code> that was the <span>active document</span> of that
+  <span>creator browsing context</span> at the time <var title="">A</var> was created is the
+  <dfn>creator <code>Document</code></dfn>.</p>
 
   <div class="impl">
 
@@ -78346,80 +78094,60 @@
   <code>Document</code> is created, the user agent must <span>implement the sandboxing</span> for
   it.</p>
 
-  <p class="note">If the <span>browsing context</span> is created
-  specifically to be immediately navigated, then that initial
-  navigation will have <span>replacement enabled</span>.</p>
+  <p class="note">If the <span>browsing context</span> is created specifically to be immediately
+  navigated, then that initial navigation will have <span>replacement enabled</span>.</p>
 
-  <p id="about-blank-origin">The <span>origin</span> and
-  <span>effective script origin</span> of the <code>about:blank</code>
-  <code>Document</code> are set when the <code>Document</code> is
-  created. If the new <span>browsing context</span> has a
-  <span>creator browsing context</span>, then the <span>origin</span>
-  of the <code>about:blank</code> <code>Document</code> is an <span
-  title="concept-origin-alias">alias</span> to the <span>origin</span>
-  of the <span>creator <code>Document</code></span> and the
-  <span>effective script origin</span> of the <code>about:blank</code>
-  <code>Document</code> is initially an <span
-  title="concept-origin-alias">alias</span> to the <span>effective
-  script origin</span> of the <span>creator
-  <code>Document</code></span>. Otherwise, the <span>origin</span> of
-  the <code>about:blank</code> <code>Document</code> is a globally
-  unique identifier assigned when the new <span>browsing
-  context</span> is created and the <span>effective script
-  origin</span> of the <code>about:blank</code> <code>Document</code>
-  is initially an <span title="concept-origin-alias">alias</span> to
-  its <span>origin</span>.</p>
+  <p id="about-blank-origin">The <span>origin</span> and <span>effective script origin</span> of the
+  <code>about:blank</code> <code>Document</code> are set when the <code>Document</code> is created.
+  If the new <span>browsing context</span> has a <span>creator browsing context</span>, then the
+  <span>origin</span> of the <code>about:blank</code> <code>Document</code> is an <span
+  title="concept-origin-alias">alias</span> to the <span>origin</span> of the <span>creator
+  <code>Document</code></span> and the <span>effective script origin</span> of the
+  <code>about:blank</code> <code>Document</code> is initially an <span
+  title="concept-origin-alias">alias</span> to the <span>effective script origin</span> of the
+  <span>creator <code>Document</code></span>. Otherwise, the <span>origin</span> of the
+  <code>about:blank</code> <code>Document</code> is a globally unique identifier assigned when the
+  new <span>browsing context</span> is created and the <span>effective script origin</span> of the
+  <code>about:blank</code> <code>Document</code> is initially an <span
+  title="concept-origin-alias">alias</span> to its <span>origin</span>.</p>
 
   </div>
 
 
   <h4>Nested browsing contexts</h4>
 
-  <p>Certain elements (for example, <code>iframe</code> elements) can
-  instantiate further <span title="browsing context">browsing
-  contexts</span>. These are called <dfn title="nested browsing
-  context">nested browsing contexts</dfn>. If a browsing context <var
-  title="">P</var> has a <code>Document</code> <var title="">D</var>
-  with an element <var title="">E</var> that nests another browsing
-  context <var title="">C</var> inside it, then <var title="">C</var>
-  is said to be <dfn title="browsing context nested through">nested
-  through</dfn> <var title="">D</var>, and <var title="">E</var> is
-  said to be the <dfn>browsing context container</dfn> of <var
-  title="">C</var>. If the <span>browsing context container</span>
-  element <var title="">E</var> is <span title="in a
-  Document">in</span> the <code>Document</code> <var title="">D</var>,
-  then <var title="">P</var> is said to be the <dfn>parent browsing
-  context</dfn> of <var title="">C</var> and <var title="">C</var> is
-  said to be a <dfn>child browsing context</dfn> of <var
-  title="">P</var>. Otherwise, the <span>nested browsing
-  context</span> <var title="">C</var> has no <span>parent browsing
-  context</span>.</p>
+  <p>Certain elements (for example, <code>iframe</code> elements) can instantiate further <span
+  title="browsing context">browsing contexts</span>. These are called <dfn title="nested browsing
+  context">nested browsing contexts</dfn>. If a browsing context <var title="">P</var> has a
+  <code>Document</code> <var title="">D</var> with an element <var title="">E</var> that nests
+  another browsing context <var title="">C</var> inside it, then <var title="">C</var> is said to be
+  <dfn title="browsing context nested through">nested through</dfn> <var title="">D</var>, and <var
+  title="">E</var> is said to be the <dfn>browsing context container</dfn> of <var title="">C</var>.
+  If the <span>browsing context container</span> element <var title="">E</var> is <span title="in a
+  Document">in</span> the <code>Document</code> <var title="">D</var>, then <var title="">P</var> is
+  said to be the <dfn>parent browsing context</dfn> of <var title="">C</var> and <var
+  title="">C</var> is said to be a <dfn>child browsing context</dfn> of <var title="">P</var>.
+  Otherwise, the <span>nested browsing context</span> <var title="">C</var> has no <span>parent
+  browsing context</span>.</p>
 
-  <p>A browsing context <var title="">A</var> is said to be an <dfn
-  title="ancestor browsing context">ancestor</dfn> of a browsing
-  context <var title="">B</var> if there exists a browsing context
-  <var title="">A'</var> that is a <span>child browsing context</span>
-  of <var title="">A</var> and that is itself an <span title="ancestor
-  browsing context">ancestor</span> of <var title="">B</var>, or if
-  there is a browsing context <var title="">P</var> that is a
-  <span>child browsing context</span> of <var title="">A</var> and
-  that is the <span>parent browsing context</span> of <var
-  title="">B</var>.</p>
+  <p>A browsing context <var title="">A</var> is said to be an <dfn title="ancestor browsing
+  context">ancestor</dfn> of a browsing context <var title="">B</var> if there exists a browsing
+  context <var title="">A'</var> that is a <span>child browsing context</span> of <var
+  title="">A</var> and that is itself an <span title="ancestor browsing context">ancestor</span> of
+  <var title="">B</var>, or if there is a browsing context <var title="">P</var> that is a
+  <span>child browsing context</span> of <var title="">A</var> and that is the <span>parent browsing
+  context</span> of <var title="">B</var>.</p>
 
-  <p>A browsing context that is not a <span>nested browsing
-  context</span> has no <span>parent browsing context</span>, and is
-  the <dfn>top-level browsing context</dfn> of all the browsing
-  contexts for which it is an <span>ancestor browsing
-  context</span>.</p>
+  <p>A browsing context that is not a <span>nested browsing context</span> has no <span>parent
+  browsing context</span>, and is the <dfn>top-level browsing context</dfn> of all the browsing
+  contexts for which it is an <span>ancestor browsing context</span>.</p>
 
-  <p>The transitive closure of <span title="parent browsing
-  context">parent browsing contexts</span> for a <span>nested browsing
-  context</span> gives the list of <span title="ancestor browsing
+  <p>The transitive closure of <span title="parent browsing context">parent browsing contexts</span>
+  for a <span>nested browsing context</span> gives the list of <span title="ancestor browsing
   context">ancestor browsing contexts</span>.</p>
 
-  <p>The <dfn>list of the descendant browsing contexts</dfn> of a
-  <code>Document</code> <var title="">d</var> is the (ordered) list
-  returned by the following algorithm:</p>
+  <p>The <dfn>list of the descendant browsing contexts</dfn> of a <code>Document</code> <var
+  title="">d</var> is the (ordered) list returned by the following algorithm:</p>
 
   <ol>
 
@@ -78427,22 +78155,19 @@
 
    <li>
 
-    <p>For each <span>child browsing context</span> of <var
-    title="">d</var> that is <span title="browsing context nested
-    through">nested through</span> an element that is <span title="in
-    a document">in the <code>Document</code></span> <var
-    title="">d</var>, in the <span>tree order</span> of the elements
-    nesting those <span title="browsing context">browsing
+    <p>For each <span>child browsing context</span> of <var title="">d</var> that is <span
+    title="browsing context nested through">nested through</span> an element that is <span title="in
+    a document">in the <code>Document</code></span> <var title="">d</var>, in the <span>tree
+    order</span> of the elements nesting those <span title="browsing context">browsing
     contexts</span>, run these substeps:</p>
 
     <ol>
 
-     <li><p>Append that <span>child browsing context</span> to the
-     list <var title="">list</var>.</p>
+     <li><p>Append that <span>child browsing context</span> to the list <var
+     title="">list</var>.</p>
 
-     <li><p>Append the <span>list of the descendant browsing
-     contexts</span> of the <span>active document</span> of that
-     <span>child browsing context</span> to the list <var
+     <li><p>Append the <span>list of the descendant browsing contexts</span> of the <span>active
+     document</span> of that <span>child browsing context</span> to the list <var
      title="">list</var>.</p></li>
 
     </ol>
@@ -78453,26 +78178,20 @@
 
   </ol>
 
-  <p>A <code>Document</code> is said to be <dfn>fully active</dfn>
-  when it is the <span>active document</span> of its <span>browsing
-  context</span>, and either its browsing context is a <span>top-level
-  browsing context</span>, or it has a <span>parent browsing
-  context</span> and the <code>Document</code> <span title="browsing
-  context nested through">through which</span> it is <span
-  title="nested browsing context">nested</span> is itself <span>fully
-  active</span>.</p>
+  <p>A <code>Document</code> is said to be <dfn>fully active</dfn> when it is the <span>active
+  document</span> of its <span>browsing context</span>, and either its browsing context is a
+  <span>top-level browsing context</span>, or it has a <span>parent browsing context</span> and the
+  <code>Document</code> <span title="browsing context nested through">through which</span> it is
+  <span title="nested browsing context">nested</span> is itself <span>fully active</span>.</p>
 
-  <p>Because they are nested through an element, <span title="child
-  browsing context">child browsing contexts</span> are always tied to
-  a specific <code>Document</code> in their <span>parent browsing
-  context</span>. User agents must not allow the user to interact with
-  <span title="child browsing context">child browsing contexts</span>
-  of elements that are in <code>Document</code>s that are not
-  themselves <span>fully active</span>.</p>
+  <p>Because they are nested through an element, <span title="child browsing context">child browsing
+  contexts</span> are always tied to a specific <code>Document</code> in their <span>parent browsing
+  context</span>. User agents must not allow the user to interact with <span title="child browsing
+  context">child browsing contexts</span> of elements that are in <code>Document</code>s that are
+  not themselves <span>fully active</span>.</p>
 
-  <p>A <span>nested browsing context</span> can have a <span>seamless
-  browsing context flag</span> set, if it is embedded through an
-  <code>iframe</code> element with a <code
+  <p>A <span>nested browsing context</span> can have a <span>seamless browsing context flag</span>
+  set, if it is embedded through an <code>iframe</code> element with a <code
   title="attr-iframe-seamless">seamless</code> attribute.</p>
 
   <p>A <span>nested browsing context</span> can be put into a <dfn>delaying <code
@@ -78482,33 +78201,25 @@
   created.</p>
 
 <!--(There's no current way for this to happen, since removing an iframe from a document discards its browsing context)
-  <p class="note">A <span>nested browsing context</span> can in some
-  cases be taken out of its <span>parent browsing context</span> (e.g.
-  if an <code>iframe</code> element is removed from its
-  <code>Document</code>). In such a situation, the <span>nested
-  browsing context</span> has no <span>parent browsing context</span>,
-  but it still has the same <span>browsing context container</span>
-  and is still <span title="browsing context nested through">nested
-  through</span> that element's <code>Document</code>. Such a
-  <span>nested browsing context</span> is <em>not</em> a
-  <span>top-level browsing context</span>, and cannot contain
-  <code>Document</code>s that are <span>fully active</span>.
-  Furthermore, if a <span>browsing context container</span> (such as
-  an <code>iframe</code>) is moved to another <code>Document</code>,
-  then the <span>parent browsing context</span> of its <span>nested
-  browsing context</span> will change.</p>
+  <p class="note">A <span>nested browsing context</span> can in some cases be taken out of its
+  <span>parent browsing context</span> (e.g. if an <code>iframe</code> element is removed from its
+  <code>Document</code>). In such a situation, the <span>nested browsing context</span> has no
+  <span>parent browsing context</span>, but it still has the same <span>browsing context
+  container</span> and is still <span title="browsing context nested through">nested through</span>
+  that element's <code>Document</code>. Such a <span>nested browsing context</span> is <em>not</em>
+  a <span>top-level browsing context</span>, and cannot contain <code>Document</code>s that are
+  <span>fully active</span>. Furthermore, if a <span>browsing context container</span> (such as an
+  <code>iframe</code>) is moved to another <code>Document</code>, then the <span>parent browsing
+  context</span> of its <span>nested browsing context</span> will change.</p>
 -->
 
-  <p>The <dfn>document family</dfn> of a <span>browsing context</span>
-  consists of the union of all the <code>Document</code> objects in
-  that <span>browsing context</span>'s <span>session history</span>
-  and the <span title="document family">document families</span> of
-  all those <code>Document</code> objects. The <span>document
-  family</span> of a <code>Document</code> object consists of the
-  union of all the <span title="document family">document
-  families</span> of the <span title="browsing context">browsing
-  contexts</span> that are <span title="browsing context nested
-  through">nested through</span> the <code>Document</code> object.</p>
+  <p>The <dfn>document family</dfn> of a <span>browsing context</span> consists of the union of all
+  the <code>Document</code> objects in that <span>browsing context</span>'s <span>session
+  history</span> and the <span title="document family">document families</span> of all those
+  <code>Document</code> objects. The <span>document family</span> of a <code>Document</code> object
+  consists of the union of all the <span title="document family">document families</span> of the
+  <span title="browsing context">browsing contexts</span> that are <span title="browsing context
+  nested through">nested through</span> the <code>Document</code> object.</p>
 
 
   <h5>Navigating nested browsing contexts in the DOM</h5>
@@ -78547,46 +78258,36 @@
 
   <div class="impl">
 
-  <p>The <dfn title="dom-top"><code>top</code></dfn> IDL attribute on
-  the <code>Window</code> object of a <code>Document</code> in a
-  <span>browsing context</span> <var title="">b</var> must return the
-  <code>WindowProxy</code> object of its <span>top-level browsing
-  context</span> (which would be its own <code>WindowProxy</code>
-  object if it was a <span>top-level browsing context</span> itself),
-  if it has one, or its own <code>WindowProxy</code> object otherwise
-  (e.g. if it was a detached <span>nested browsing
-  context</span>).</p>
+  <p>The <dfn title="dom-top"><code>top</code></dfn> IDL attribute on the <code>Window</code> object
+  of a <code>Document</code> in a <span>browsing context</span> <var title="">b</var> must return
+  the <code>WindowProxy</code> object of its <span>top-level browsing context</span> (which would be
+  its own <code>WindowProxy</code> object if it was a <span>top-level browsing context</span>
+  itself), if it has one, or its own <code>WindowProxy</code> object otherwise (e.g. if it was a
+  detached <span>nested browsing context</span>).</p>
 
-  <p>The <dfn title="dom-parent"><code>parent</code></dfn> IDL
-  attribute on the <code>Window</code> object of a
-  <code>Document</code> in a <span>browsing context</span> <var
-  title="">b</var> must return the <code>WindowProxy</code> object of
-  the <span>parent browsing context</span>, if there is one (i.e. if
-  <var title="">b</var> is a <span>child browsing context</span>), or
-  the <code>WindowProxy</code> object of the <span>browsing
-  context</span> <var title="">b</var> itself, otherwise (i.e. if it
-  is a <span>top-level browsing context</span> or a detached
-  <span>nested browsing context</span>).</p>
+  <p>The <dfn title="dom-parent"><code>parent</code></dfn> IDL attribute on the <code>Window</code>
+  object of a <code>Document</code> in a <span>browsing context</span> <var title="">b</var> must
+  return the <code>WindowProxy</code> object of the <span>parent browsing context</span>, if there
+  is one (i.e. if <var title="">b</var> is a <span>child browsing context</span>), or the
+  <code>WindowProxy</code> object of the <span>browsing context</span> <var title="">b</var> itself,
+  otherwise (i.e. if it is a <span>top-level browsing context</span> or a detached <span>nested
+  browsing context</span>).</p>
 
-  <p>The <dfn title="dom-frameElement"><code>frameElement</code></dfn>
-  IDL attribute on the <code>Window</code> object of a
-  <code>Document</code> <var title="">d</var>, on getting, must run
+  <p>The <dfn title="dom-frameElement"><code>frameElement</code></dfn> IDL attribute on the
+  <code>Window</code> object of a <code>Document</code> <var title="">d</var>, on getting, must run
   the following algorithm:</p>
 
   <ol>
 
-   <li><p>If <var title="">d</var> is not a <code>Document</code> in a
-   <span>nested browsing context</span>, return null and abort these
-   steps.</p></li>
+   <li><p>If <var title="">d</var> is not a <code>Document</code> in a <span>nested browsing
+   context</span>, return null and abort these steps.</p></li>
 
-   <li><p>If the <span>browsing context container</span>'s
-   <code>Document</code> does not have the <span title="same
-   origin">same</span> <span>effective script origin</span> as the
-   <span>entry script</span>, then throw a <code>SecurityError</code>
-   exception.</p></li>
+   <li><p>If the <span>browsing context container</span>'s <code>Document</code> does not have the
+   <span title="same origin">same</span> <span>effective script origin</span> as the <span>entry
+   script</span>, then throw a <code>SecurityError</code> exception.</p></li>
 
-   <li><p>Otherwise, return the <span>browsing context
-   container</span> for <var title="">b</var>.</p></li>
+   <li><p>Otherwise, return the <span>browsing context container</span> for <var
+   title="">b</var>.</p></li>
 
   </ol>
 
@@ -78596,33 +78297,26 @@
 
   <h4>Auxiliary browsing contexts</h4>
 
-  <p>It is possible to create new browsing contexts that are related
-  to a <span>top-level browsing context</span> without being nested
-  through an element. Such browsing contexts are called <dfn
-  title="auxiliary browsing context">auxiliary browsing
-  contexts</dfn>. Auxiliary browsing contexts are always <span
-  title="top-level browsing context">top-level browsing
-  contexts</span>.</p>
+  <p>It is possible to create new browsing contexts that are related to a <span>top-level browsing
+  context</span> without being nested through an element. Such browsing contexts are called <dfn
+  title="auxiliary browsing context">auxiliary browsing contexts</dfn>. Auxiliary browsing contexts
+  are always <span title="top-level browsing context">top-level browsing contexts</span>.</p>
 
-  <p>An <span>auxiliary browsing context</span> has an <dfn>opener
-  browsing context</dfn>, which is the <span>browsing context</span>
-  from which the <span>auxiliary browsing context</span> was
+  <p>An <span>auxiliary browsing context</span> has an <dfn>opener browsing context</dfn>, which is
+  the <span>browsing context</span> from which the <span>auxiliary browsing context</span> was
   created.</p>
 
 
   <h5>Navigating auxiliary browsing contexts in the DOM</h5>
 
-  <p>The <dfn title="dom-opener"><code>opener</code></dfn> IDL
-  attribute on the <code>Window</code> object, on getting, must return
-  the <code>WindowProxy</code> object of the <span>browsing
-  context</span> from which the current <span>browsing context</span>
-  was created (its <span>opener browsing context</span>), if there is
-  one, if it is still available, and if the current <span>browsing
-  context</span> has not <i>disowned its opener</i>; otherwise, it
-  must return null. On setting, if the new value is null then the
-  current <span>browsing context</span> must <dfn title="disowned its
-  opener">disown its opener</dfn>; if the new value is anything else
-  then the user agent must ignore the new value.</p>
+  <p>The <dfn title="dom-opener"><code>opener</code></dfn> IDL attribute on the <code>Window</code>
+  object, on getting, must return the <code>WindowProxy</code> object of the <span>browsing
+  context</span> from which the current <span>browsing context</span> was created (its <span>opener
+  browsing context</span>), if there is one, if it is still available, and if the current
+  <span>browsing context</span> has not <i>disowned its opener</i>; otherwise, it must return null.
+  On setting, if the new value is null then the current <span>browsing context</span> must <dfn
+  title="disowned its opener">disown its opener</dfn>; if the new value is anything else then the
+  user agent must ignore the new value.</p>
 
 
 
@@ -78633,10 +78327,9 @@
      http://www.w3.org/Bugs/Public/show_bug.cgi?id=11183
   and then moved to the wiki -->
 
-  <p>User agents may support <dfn title="secondary browsing
-  context">secondary browsing contexts</dfn>, which are <span
-  title="browsing context">browsing contexts</span> that form part of
-  the user agent's interface, apart from the main content area.</p>
+  <p>User agents may support <dfn title="secondary browsing context">secondary browsing
+  contexts</dfn>, which are <span title="browsing context">browsing contexts</span> that form part
+  of the user agent's interface, apart from the main content area.</p>
 
 
 <!--ADD-TOPIC:Security-->
@@ -78644,50 +78337,41 @@
 
   <h4 id="security-nav">Security</h4>
 
-  <p id="security-1">A <span>browsing context</span> <var
-  title="">A</var> is <dfn>allowed to navigate</dfn> a second
-  <span>browsing context</span> <var title="">B</var> if one of the
+  <p id="security-1">A <span>browsing context</span> <var title="">A</var> is <dfn>allowed to
+  navigate</dfn> a second <span>browsing context</span> <var title="">B</var> if one of the
   following conditions is true:</p>
 
   <ul>
 
-   <li>Either the <span>origin</span> of the <span>active
-   document</span> of <var title="">A</var> is the <span title="same
-   origin">same</span> as the <span>origin</span> of the <span>active
+   <li>Either the <span>origin</span> of the <span>active document</span> of <var title="">A</var>
+   is the <span title="same origin">same</span> as the <span>origin</span> of the <span>active
    document</span> of <var title="">B</var>, or</li>
 
-   <li>The browsing context <var title="">A</var> is a <span>nested
-   browsing context</span> with a <span>top-level browsing
-   context</span>, and its <span>top-level browsing context</span> is
-   <var title="">B</var>, or</li>
+   <li>The browsing context <var title="">A</var> is a <span>nested browsing context</span> with a
+   <span>top-level browsing context</span>, and its <span>top-level browsing context</span> is <var
+   title="">B</var>, or</li>
 
-   <li>The browsing context <var title="">B</var> is an
-   <span>auxiliary browsing context</span> and <var title="">A</var>
-   is <span>allowed to navigate</span> <var title="">B</var>'s
-   <span>opener browsing context</span>, or</li>
+   <li>The browsing context <var title="">B</var> is an <span>auxiliary browsing context</span> and
+   <var title="">A</var> is <span>allowed to navigate</span> <var title="">B</var>'s <span>opener
+   browsing context</span>, or</li>
 
-   <li>The browsing context <var title="">B</var> is not a
-   <span>top-level browsing context</span>, but there exists an
-   <span>ancestor browsing context</span> of <var title="">B</var>
-   whose <span>active document</span> has the <span title="same
-   origin">same</span> <span>origin</span> as the <span>active
-   document</span> of <var title="">A</var> (possibly in fact being
-   <var title="">A</var> itself).</li>
+   <li>The browsing context <var title="">B</var> is not a <span>top-level browsing context</span>,
+   but there exists an <span>ancestor browsing context</span> of <var title="">B</var> whose
+   <span>active document</span> has the <span title="same origin">same</span> <span>origin</span> as
+   the <span>active document</span> of <var title="">A</var> (possibly in fact being <var
+   title="">A</var> itself).</li>
 
   </ul>
 
   <hr>
 
-  <p>An element has a <dfn>browsing context scope origin</dfn> if its
-  <code>Document</code>'s <span>browsing context</span> is a
-  <span>top-level browsing context</span> or if all of its
-  <code>Document</code>'s <span title="ancestor browsing
-  context">ancestor browsing contexts</span> all have <span
-  title="active document">active documents</span> whose
-  <span>origin</span> are the <span>same origin</span> as the
-  element's <code>Document</code>'s <span>origin</span>. If an element
-  has a <span>browsing context scope origin</span>, then its value is
-  the <span>origin</span> of the element's <code>Document</code>.</p>
+  <p>An element has a <dfn>browsing context scope origin</dfn> if its <code>Document</code>'s
+  <span>browsing context</span> is a <span>top-level browsing context</span> or if all of its
+  <code>Document</code>'s <span title="ancestor browsing context">ancestor browsing contexts</span>
+  all have <span title="active document">active documents</span> whose <span>origin</span> are the
+  <span>same origin</span> as the element's <code>Document</code>'s <span>origin</span>. If an
+  element has a <span>browsing context scope origin</span>, then its value is the
+  <span>origin</span> of the element's <code>Document</code>.</p>
 
   </div>
 <!--REMOVE-TOPIC:Security-->
@@ -78697,49 +78381,40 @@
 
   <h4>Groupings of browsing contexts</h4>
 
-  <p>Each <span>browsing context</span> is defined as having a list of
-  one or more <dfn>directly reachable browsing contexts</dfn>. These
-  are:</p>
+  <p>Each <span>browsing context</span> is defined as having a list of one or more <dfn>directly
+  reachable browsing contexts</dfn>. These are:</p>
 
   <ul>
 
    <li>The <span>browsing context</span> itself.</li>
 
-   <li>All the <span>browsing context</span>'s <span title="child
-   browsing context">child browsing contexts</span>.</li>
+   <li>All the <span>browsing context</span>'s <span title="child browsing context">child browsing
+   contexts</span>.</li>
 
-   <li>The <span>browsing context</span>'s <span>parent browsing
-   context</span>.</li>
+   <li>The <span>browsing context</span>'s <span>parent browsing context</span>.</li>
 
-   <li>All the <span title="browsing context">browsing contexts</span>
-   that have the <span>browsing context</span> as their <span>opener
-   browsing context</span>.</li>
+   <li>All the <span title="browsing context">browsing contexts</span> that have the <span>browsing
+   context</span> as their <span>opener browsing context</span>.</li>
 
-   <li>The <span>browsing context</span>'s <span>opener browsing
-   context</span>.</li>
+   <li>The <span>browsing context</span>'s <span>opener browsing context</span>.</li>
 
   </ul>
 
-  <p>The transitive closure of all the <span title="browsing
-  context">browsing contexts</span> that are <span>directly reachable
-  browsing contexts</span> forms a <dfn>unit of related browsing
+  <p>The transitive closure of all the <span title="browsing context">browsing contexts</span> that
+  are <span>directly reachable browsing contexts</span> forms a <dfn>unit of related browsing
   contexts</dfn>.</p>
 
-  <p>Each <span>unit of related browsing contexts</span> is then
-  further divided into the smallest number of groups such that every
-  member of each group has an <span>active document</span> with an
-  <span>effective script origin</span> that, through appropriate
-  manipulation of the <code
-  title="dom-document-domain">document.domain</code> attribute, could
-  be made to be the same as other members of the group, but could not
-  be made the same as members of any other group. Each such group is a
-  <dfn>unit of related similar-origin browsing contexts</dfn>.</p>
+  <p>Each <span>unit of related browsing contexts</span> is then further divided into the smallest
+  number of groups such that every member of each group has an <span>active document</span> with an
+  <span>effective script origin</span> that, through appropriate manipulation of the <code
+  title="dom-document-domain">document.domain</code> attribute, could be made to be the same as
+  other members of the group, but could not be made the same as members of any other group. Each
+  such group is a <dfn>unit of related similar-origin browsing contexts</dfn>.</p>
 
-  <p class="note">There is also at most one <span>event loop</span>
-  per <span>unit of related similar-origin browsing contexts</span>
-  (though several <span title="unit of related similar-origin browsing
-  contexts">units of related similar-origin browsing contexts</span>
-  can have a shared <span>event loop</span>).</p>
+  <p class="note">There is also at most one <span>event loop</span> per <span>unit of related
+  similar-origin browsing contexts</span> (though several <span title="unit of related
+  similar-origin browsing contexts">units of related similar-origin browsing contexts</span> can
+  have a shared <span>event loop</span>).</p>
 
   </div>
 
@@ -78747,38 +78422,31 @@
 
   <h4>Browsing context names</h4>
 
-  <p>Browsing contexts can have a <dfn>browsing context name</dfn>. By
-  default, a browsing context has no name (its name is not set).</p>
+  <p>Browsing contexts can have a <dfn>browsing context name</dfn>. By default, a browsing context
+  has no name (its name is not set).</p>
 
-  <p>A <dfn>valid browsing context name</dfn> is any string with at
-  least one character that does not start with a U+005F LOW LINE
-  character. (Names starting with an underscore are reserved for
+  <p>A <dfn>valid browsing context name</dfn> is any string with at least one character that does
+  not start with a U+005F LOW LINE character. (Names starting with an underscore are reserved for
   special keywords.)</p>
 
-  <p>A <dfn>valid browsing context name or keyword</dfn> is any string
-  that is either a <span>valid browsing context name</span> or that is
-  an <span>ASCII case-insensitive</span> match for one of: <code
-  title="">_blank</code>, <code title="">_self</code>, <code
-  title="">_parent</code>, or <code title="">_top</code>.</p>
+  <p>A <dfn>valid browsing context name or keyword</dfn> is any string that is either a <span>valid
+  browsing context name</span> or that is an <span>ASCII case-insensitive</span> match for one of:
+  <code title="">_blank</code>, <code title="">_self</code>, <code title="">_parent</code>, or <code
+  title="">_top</code>.</p>
 
-  <p>These values have different meanings based on whether the page is
-  sandboxed or not, as summarized in the following (non-normative)
-  table. In this table, "current" means the <span>browsing
-  context</span> that the link or script is in, "parent" means the
-  <span>parent browsing context</span> of the one the link or script
-  is in, "master" means the nearest <span>ancestor browsing
-  context</span> of the one the link or script is in that is not
-  itself in a <span title="attr-iframe-seamless">seamless
-  iframe</span>, "top" means the <span>top-level browsing
-  context</span> of the one the link or script is in, "new" means a
-  new <span>top-level browsing context</span> or <span>auxiliary
-  browsing context</span> is to be created, subject to various user
-  preferences and user agent policies, "none" means that nothing will
-  happen, and "maybe new" means the same as "new" if the "<code
-  title="attr-iframe-sandbox-allow-popups">allow-popups</code>"
-  keyword is also specified on the <code
-  title="attr-iframe-sandbox">sandbox</code> attribute (or if the user
-  overrode the sandboxing), and the same as "none" otherwise.</p>
+  <p>These values have different meanings based on whether the page is sandboxed or not, as
+  summarized in the following (non-normative) table. In this table, "current" means the
+  <span>browsing context</span> that the link or script is in, "parent" means the <span>parent
+  browsing context</span> of the one the link or script is in, "master" means the nearest
+  <span>ancestor browsing context</span> of the one the link or script is in that is not itself in a
+  <span title="attr-iframe-seamless">seamless iframe</span>, "top" means the <span>top-level
+  browsing context</span> of the one the link or script is in, "new" means a new <span>top-level
+  browsing context</span> or <span>auxiliary browsing context</span> is to be created, subject to
+  various user preferences and user agent policies, "none" means that nothing will happen, and
+  "maybe new" means the same as "new" if the "<code
+  title="attr-iframe-sandbox-allow-popups">allow-popups</code>" keyword is also specified on the
+  <code title="attr-iframe-sandbox">sandbox</code> attribute (or if the user overrode the
+  sandboxing), and the same as "none" otherwise.</p>
 
   <table>
    <thead>
@@ -78938,178 +78606,147 @@
 
   <hr>
 
-  <p>An algorithm is <dfn>allowed to show a pop-up</dfn> if, in the
-  <span title="concept-task">task</span> in which the algorithm is
-  running, either:</p>
+  <p>An algorithm is <dfn>allowed to show a pop-up</dfn> if, in the <span
+  title="concept-task">task</span> in which the algorithm is running, either:</p>
 
   <ul class="brief">
 
-   <li>an <span>activation behavior</span> is currently being
-   processed whose <code title="event-click">click</code> event was
-   <span title="concept-events-trusted">trusted</span>, or</li>
+   <li>an <span>activation behavior</span> is currently being processed whose <code
+   title="event-click">click</code> event was <span title="concept-events-trusted">trusted</span>,
+   or</li>
 
-   <li>the event listener for a <span
-   title="concept-events-trusted">trusted</span> <code
+   <li>the event listener for a <span title="concept-events-trusted">trusted</span> <code
    title="event-click">click</code> event is being handled.</li>
 
   </ul>
 
   <hr>
 
-  <p><dfn>The rules for choosing a browsing context given a browsing
-  context name</dfn> are as follows. The rules assume that they are
-  being applied in the context of a <span>browsing context</span>.</p>
+  <p><dfn>The rules for choosing a browsing context given a browsing context name</dfn> are as
+  follows. The rules assume that they are being applied in the context of a <span>browsing
+  context</span>.</p>
 
   <ol>
 
    <li>
 
-    <p>If the given browsing context name is the empty string or <code
-    title="">_self</code>, then the chosen browsing context must be
-    the current one.</p>
+    <p>If the given browsing context name is the empty string or <code title="">_self</code>, then
+    the chosen browsing context must be the current one.</p>
 
-    <p>If the given browsing context name is <code
-    title="">_self</code>, then this is an <span>explicit
-    self-navigation override</span>, which overrides the behavior of
-    the <span>seamless browsing context flag</span> set by the <code
-    title="attr-iframe-seamless">seamless</code> attribute on
-    <code>iframe</code> elements.</p>
+    <p>If the given browsing context name is <code title="">_self</code>, then this is an
+    <span>explicit self-navigation override</span>, which overrides the behavior of the
+    <span>seamless browsing context flag</span> set by the <code
+    title="attr-iframe-seamless">seamless</code> attribute on <code>iframe</code> elements.</p>
 
    </li>
 
-   <li><p>If the given browsing context name is <code
-   title="">_parent</code>, then the chosen browsing context must be
-   the <span><em>parent</em> browsing context</span> of the current
-   one, unless there isn't one, in which case the chosen browsing
-   context must be the current browsing context.</p></li>
+   <li><p>If the given browsing context name is <code title="">_parent</code>, then the chosen
+   browsing context must be the <span><em>parent</em> browsing context</span> of the current one,
+   unless there isn't one, in which case the chosen browsing context must be the current browsing
+   context.</p></li>
 
-   <li><p>If the given browsing context name is <code
-   title="">_top</code>, then the chosen browsing context must be the
-   <span>top-level browsing context</span> of the current one, if
-   there is one, or else the current browsing context.</p></li>
+   <li><p>If the given browsing context name is <code title="">_top</code>, then the chosen browsing
+   context must be the <span>top-level browsing context</span> of the current one, if there is one,
+   or else the current browsing context.</p></li>
 
    <li>
 
-    <p>If the given browsing context name is not <code
-    title="">_blank</code> and there exists a browsing context whose
-    <span title="browsing context name">name</span> is the same as the
-    given browsing context name, and the current browsing context is
-    <span>allowed to navigate</span> that browsing context, and the
-    user agent determines that the two browsing contexts are related
-    enough that it is ok if they reach each other, then that browsing
-    context must be the chosen one. If there are multiple matching
-    browsing contexts, the user agent should select one in some
-    arbitrary consistent manner, such as the most recently opened,
-    most recently focused, or more closely related.</p>
+    <p>If the given browsing context name is not <code title="">_blank</code> and there exists a
+    browsing context whose <span title="browsing context name">name</span> is the same as the given
+    browsing context name, and the current browsing context is <span>allowed to navigate</span> that
+    browsing context, and the user agent determines that the two browsing contexts are related
+    enough that it is ok if they reach each other, then that browsing context must be the chosen
+    one. If there are multiple matching browsing contexts, the user agent should select one in some
+    arbitrary consistent manner, such as the most recently opened, most recently focused, or more
+    closely related.</p>
 
-    <p>If the browsing context is chosen by this step to be the
-    current browsing context, then this is also an <span>explicit
-    self-navigation override</span>.</p>
+    <p>If the browsing context is chosen by this step to be the current browsing context, then this
+    is also an <span>explicit self-navigation override</span>.</p>
 
    </li>
 
    <li>
 
-    <p>Otherwise, a new browsing context is being requested, and what
-    happens depends on the user agent's configuration and/or abilities
-    — it is determined by the rules given for the first
+    <p>Otherwise, a new browsing context is being requested, and what happens depends on the user
+    agent's configuration and/or abilities — it is determined by the rules given for the first
     applicable option from the following list:</p>
 
     <dl class="switch">
 
-     <dt id="sandboxWindowOpen">If the current browsing context's
-     <span>active document</span>'s <span>active sandboxing flag
-     set</span> has the <span>sandboxed auxiliary navigation browsing
+     <dt id="sandboxWindowOpen">If the current browsing context's <span>active document</span>'s
+     <span>active sandboxing flag set</span> has the <span>sandboxed auxiliary navigation browsing
      context flag</span> set.</dt>
 
      <dd>
 
       <p>Typically, there is no chosen browsing context.</p>
 
-      <p>The user agent may offer to create a new <span>top-level
-      browsing context</span> or reuse an existing <span>top-level
-      browsing context</span>. If the user picks one of those options,
-      then the designated browsing context must be the chosen one (the
-      browsing context's name isn't set to the given browsing context
-      name). The default behaviour (if the user agent doesn't offer
-      the option to the user, or if the user declines to allow a
-      browsing context to be used) must be that there must not be a
-      chosen browsing context.</p>
+      <p>The user agent may offer to create a new <span>top-level browsing context</span> or reuse
+      an existing <span>top-level browsing context</span>. If the user picks one of those options,
+      then the designated browsing context must be the chosen one (the browsing context's name isn't
+      set to the given browsing context name). The default behaviour (if the user agent doesn't
+      offer the option to the user, or if the user declines to allow a browsing context to be used)
+      must be that there must not be a chosen browsing context.</p>
 
-      <p class="warning">If this case occurs, it means that an author
-      has explicitly sandboxed the document that is trying to open a
-      link.</p>
+      <p class="warning">If this case occurs, it means that an author has explicitly sandboxed the
+      document that is trying to open a link.</p>
 
      </dd>
 
 
-     <dt id="noopener">If the user agent has been configured such that
-     in this instance it will create a new browsing context, and the
-     browsing context is being requested as part of <span
-     title="following hyperlinks">following a hyperlink</span> whose
-     <a href="#linkTypes">link types</a> include the <code
-     title="rel-noreferrer">noreferrer</code> keyword</dt>
+     <dt id="noopener">If the user agent has been configured such that in this instance it will
+     create a new browsing context, and the browsing context is being requested as part of <span
+     title="following hyperlinks">following a hyperlink</span> whose <a href="#linkTypes">link
+     types</a> include the <code title="rel-noreferrer">noreferrer</code> keyword</dt>
 
-     <dd><p>A new <span>top-level browsing context</span> 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. The creation of such a <span>browsing context</span> is
-     <dfn>a new start for session storage</dfn>.</p>
+     <dd><p>A new <span>top-level browsing context</span> 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. The creation of such a <span>browsing context</span>
+     is <dfn>a new start for session storage</dfn>.</p>
 
-     <p class="note">If it is immediately <span
-     title="navigate">navigated</span>, then the navigation will be
-     done with <span>replacement enabled</span>.</p></dd>
+     <p class="note">If it is immediately <span title="navigate">navigated</span>, then the
+     navigation will be done with <span>replacement enabled</span>.</p></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">noreferrer</code> keyword doesn't
+     <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">noreferrer</code> keyword doesn't
      apply</dt>
 
-     <dd><p>A new <span>auxiliary browsing context</span> must be
-     created, with the <span>opener browsing context</span> 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.</p>
+     <dd><p>A new <span>auxiliary browsing context</span> must be created, with the <span>opener
+     browsing context</span> 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.</p>
 
-     <p class="note">If it is immediately <span
-     title="navigate">navigated</span>, then the navigation will be
-     done with <span>replacement enabled</span>.</p></dd>
+     <p class="note">If it is immediately <span title="navigate">navigated</span>, then the
+     navigation will be done with <span>replacement enabled</span>.</p></dd>
 
 
-     <dt>If the user agent has been configured such that in this
-     instance it will reuse the current browsing context</dt>
+     <dt>If the user agent has been configured such that in this instance it will reuse the current
+     browsing context</dt>
 
-     <dd><p>The chosen browsing context is the current browsing
-     context.</p></dd>
+     <dd><p>The chosen browsing context is the current browsing context.</p></dd>
 
 
-     <dt>If the user agent has been configured such that in this
-     instance it will not find a browsing context</dt>
+     <dt>If the user agent has been configured such that in this instance it will not find a
+     browsing context</dt>
 
      <dd><p>There must not be a chosen browsing context.</p></dd>
 
     </dl>
 
-    <p>User agent implementors are encouraged to provide a way for
-    users to configure the user agent to always reuse the current
-    browsing context.</p>
+    <p>User agent implementors are encouraged to provide a way for users to configure the user agent
+    to always reuse the current browsing context.</p>
 
-    <p>If the current browsing context's <span>active
-    document</span>'s <span>active sandboxing flag set</span> has the
-    <span>sandboxed navigation browsing context flag</span> set and
-    chosen browsing context picked above, if any, is a new browsing
-    context (whether top-level or auxiliary), then all the flags that
-    are set in the current browsing context's <span>active
-    document</span>'s <span>active sandboxing flag set</span> when the
-    new browsing context is created must be set in the new browsing
-    context's <span>popup sandboxing flag set</span>, and the current
-    browsing context must be set as the new browsing context's
-    <span>one permitted sandboxed navigator</span>.</p>
+    <p>If the current browsing context's <span>active document</span>'s <span>active sandboxing flag
+    set</span> has the <span>sandboxed navigation browsing context flag</span> set and chosen
+    browsing context picked above, if any, is a new browsing context (whether top-level or
+    auxiliary), then all the flags that are set in the current browsing context's <span>active
+    document</span>'s <span>active sandboxing flag set</span> when the new browsing context is
+    created must be set in the new browsing context's <span>popup sandboxing flag set</span>, and
+    the current browsing context must be set as the new browsing context's <span>one permitted
+    sandboxed navigator</span>.</p>
 
    </li>
 




More information about the Commit-Watchers mailing list