anchor.diff:  
   ==== Code listings
   
  -
   *HTML element*: <pre>
   
  -*Special semantics*: class="programlisting" or class="screen"footnote:[From DocBook; EPUB 3 Structural Semantics Vocabulary has no semantics for code blocks)]
  -
  -Also, data-language to indicate programming language, e.g., +data-language="python"+
  -
  -*Note*: May not be worth supporting semantic distinction between "screen" and "programlisting", but I can see it being valuable, if we want distinct styling for command-line environments.
  -
  -*Example*:
  -
  -----
  -<pre class="programlisting">print "Hello World"</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>
   
  -*Special semantics*: None
  -
  -*Note*: Optionally, you could add <p>s for a <li> with multiple paragraphs.
  +*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>Step 2</li>
  +<li>
  +  <p>Step 2</p>
  +  <p>Step 2 continued</p>
  +</li>
   <!-- And so on -->
   </ol>
   ----
   
   ==== Itemized lists
  -
   
   *HTML element*: <ul>
   
  
positive.code: </table>
  ----
  
  ==== Figures
  
  
  *HTML element*: <figure>
  
  *Special semantics*: None, but use child <figcaption> element for figure title
  
  *Note*: May need to transform <figure> to a <div> for EPUB output for EPUB 2 backward compatibility
  
  *Example*:
  
  ----
  <figure>
  <figcaption>Project Unicorn Logo</figcaption>
  <img src="unicorn.gif" alt="Illustration of a unicorn running."/>
  </figure>
  ----
  
  ==== Examples
  
  
  *HTML element*: <div>
  
  *Special semantics*: class="example"footnote:[From DocBook; EPUB 3 Structural Semantics Vocabulary has no good match (closest is probably "practice")]
  
  *Note*: Examples are intended to be titled in DocBook model; Would suggest using <caption>, but HTML spec reserves it exclusively for table elements.
  
  *Note*: Typically in our books, examples contain code listings, but this is not a requirement in the DocBook model, and occasionally, we'll include other block content instead (lists, paras, etc.)
  
  *Example*:
  
  
negative.code: </section>
  ----
  
  === Block elements
  
  ==== Paragraph
  
  *HTML element*: <p>
  
  *Example*:
  
  ----
  <p>This is a standard paragraph with some <em>emphasized text</em></p>
  ----
  
  ==== Sidebar
  
  *HTML element*: <aside>
  
  *Attribute requirements*: class="sidebar"
  
  *Content model*: Zero or one <h5> element that contains the sidebar title); then zero or more Block elements
  
  *Example*:
  
  ----
  <aside class="sidebar">
    <h5>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>
  
  *Attribute requirements*: class="note" or class="warning", depending on the content within
  
  *Content model*: Either of the following content models is acceptable:
  
  * text and/or zero or more Inline elements
  * Zero or more <h1>-<h6> elements (for title and subtitles), followed by zero or more Block elements
  
  *Examples*:
  
  ----
  <div class="note">
    <h1>Helpful Info</h1>
    <p>Please take note of this important information</p>
  </div>
  ----
  
  ----
  <div class="warning">Make sure to get your AsciiDoc markup right!</div>
  ----
  
  ==== Tables
  
  *HTML element*: <table>
  
  *Content model*: Zero or one <caption> elements (for titled/captioned tables); then zero or more <colgroup> elements; then zero or more <thead> elements; then a choice between either zero or more <tbody> elements, or zero or more <tr> elements; then zero or more <tfoot> elements
  
  *Content model for <caption>*: Either of the following is acceptable:
  
  * Zero or more <p> and/or <div> elements
  * Text and/or zero or more Inline elements
  
  *Content model for <colgroup>*: Mirrors HTML5 Specification
  
  *Content models for <thead>, <tbody>, and <tfoot>*: Mirror HTML5 Specification
  
  *Content model for <tr>*: Mirrors HTML5 Specification, but see content model below for rules for child +<td>+ and +<th>+ elements
  
  *Content model for <td> and <th> elements*: Either of the following is acceptable:
  
  * text and/or zero or more Inline elements
  * Zero or more Block elements
  
  *Examples*:
  
  ----
  <table>
  