anchor.diff:    <p>When in the course of human events...</p>
     <p class="attribution">U.S. Declaration of Independence</p>
   </blockquote>
  +----
  +
  +==== Sections
  +
  +*HTML element*: <section>
  +
  +*Special semantics*: class="sect1", class="sect2", class="sect3", class="sect4", class="sect5"
  +
  +*Note*: EPUB 3 Structural Semantic Vocabulary only has the term "division" for sections, and has no semantics for different section levels, so the above semantics are pulled directly from DocBook (operating on the assumption that semantics for section level are valuable in CSS, such that we don't need to write selectors like:
  +
  +----
  +section section section section { font-size: 50% }
  +----
  +
  +*Note 2*: Proposed use of HTML heading elements for sections is as follows:
  +
  +----
  +sect1 -> h1
  +sect2 -> h2
  +sect3 -> h3
  +sect4 -> h4
  +sect5 -> h5
  +----
  +
  +*Note 3*: Given the current state of EPUB 3 support, we will likely need to transform back to <div> in EPUB output order to ensure backward compatibility in EPUB 2 readers
  +
  +*Example*:
  +
  +----
  +<section class="sect1">
  +  <h1>A-Head</h1>
  +  <p>If you httpparty, you must party hard</p>
  +  <!-- Some more paragraphs -->
  +  <section class="sect2">
  +    <h2>B-Head</h2>
  +    <p>What's the frequency, Kenneth?</p>
  +    <!-- And so on... -->
  +  </section>
  +</section>
   ----
   
   ==== Headings
  
positive.code: </section>
  ----
  
  
  
  === Block Elements
  
  ==== Paragraph
  
  
  *HTML element*: <p>
  
  *Special semantics*: in most cases, none--but we may define classes in specific circumstances; e.g., <p class="biblioentry">
  
  *Example*:
  
  ----
  <p>Nothing exciting here. Move on, yo!</p>
  ----
  
  ==== Sidebar
  
  
  *HTML element*: <aside>
  
  *Special semantics*: class="sidebar"
  
  *Example*:
  
  ----
  <aside class="sidebar">
    <!-- Optional h5 for sidebar title -->
    <h5 class="title">Amusing Digression</h5>
    <p>Did you know that in Boston, they call it "soda", and in Chicago, they call it "pop"?</p>
  </aside>
  ----
  
  ==== Admonitions
  
  
  *HTML element*: <div>
  
  *Special semantics*: class="note" or class="warning" (these are the two admon values in the EPUB 3 Structural Semantics Vocabulary spec; we can always define more if note/warning do not suffice)
  
  *Note*: Given the current state of EPUB 3 support, we will likely need to transform back to <div> in EPUB output order to ensure backward compatibility in EPUB 2 readers
  
  *Example*:
  
  ----
  <div class="note">
    <p>Type "hubot kitteh" to get a picture of an adorable cat</p>
  </div>
  ----
  
  ==== Sections
  
  
  *HTML element*: <section>
  
  *Special semantics*: class="sect1", class="sect2", class="sect3", class="sect4", class="sect5"
  
  *Note*: EPUB 3 Structural Semantic Vocabulary only has the term "division" for sections, and has no semantics for different section levels, so the above semantics are pulled directly from DocBook (operating on the assumption that semantics for section level are valuable in CSS, such that we don't need to write selectors like:
  
  ----
  section section section section { font-size: 50% }
  ----
  
  *Note 2*: Proposed use of HTML heading elements for sections is as follows:
  
  ----
  sect1 -> h1
  sect2 -> h2
  sect3 -> h3
  sect4 -> h4
  sect5 -> h5
  ----
  
  *Note 3*: Given the current state of EPUB 3 support, we will likely need to transform back to <div> in EPUB output order to ensure backward compatibility in EPUB 2 readers
  
  *Example*:
  
  ----
  <section class="sect1">
    <h1>A-Head</h1>
    <p>If you httpparty, you must party hard</p>
    <!-- Some more paragraphs -->
    <section class="sect2">
      <h2>B-Head</h2>
      <p>What's the frequency, Kenneth?</p>
      <!-- And so on... -->
    </section>
  </section>
  ----
  
  ==== Tables
  
  
  *HTML element*: <table>
  
  *Special semantics*: None, but use child <caption> element for table title
  
  *Example*:
  
  ----
  <table>
  
negative.code: 
  ==== Code listings
  
  *HTML element*: <pre>
  
  *Optional HTMLBook-specific attribute*: +data-language+, used to indicate language of code listing (e.g., +data-language="python"+)
  
  *Example*:
  
  ----
  <pre class="programlisting">print "<em>Hello World</em>"</pre>
  ----
  
  ==== Ordered lists
  
  *HTML element*: <ol>
  
  *Content model*: Zero or more <li> children for each list item
  
  *Content model for <li> children*: Either of the following is acceptable:
  
  * text and/or zero or more Inline elements
  * Zero or more Block elements
  
  *Example*:
  
  ----
  <ol>
  <li>Step 1</li>
  <li>
    <p>Step 2</p>
    <p>Step 2 continued</p>
  </li>
  <!-- And so on -->
  </ol>
  ----
  
  ==== Itemized lists
  
  *HTML element*: <ul>
  
  