anchor.diff:  
   *HTML element*: <a>
   
  -*Special semantics*: class="xref"footnote:[From DocBook; no close match in EPUB 3 Structural Semantics Vocabulary]
  +*Attribute requirements*: class="xref"footnote:[From DocBook]; an href attribute that should point to the id of a
  +local HTMLBook resource referenced
   
   Example:
   
  
positive.code: sect4 title -> h4
  sect5 title -> h5
  sidebar title -> h5
  example title -> h5
  equation title -> h5
  admon title -> h5
  ----
  
  I'm advocating we use h1 for book title, part title, and chapter-level titles because I think it's important to have consistency across all books, regardless of whether they have Parts or not. I think it would be confusing and potentially problematic if in a book that had parts, <h1> was used for part titles and <h2> was used for chapter titles, and then in a book that had no parts, <h1> was used for chapter titles. 
  
  I also like the idea of having heading level match the section class semantics, such that sect1 = <h1>, sect2 = <h2>, etc. I think doing anything else would be confusing.
  
  Look forward to discussing all this further, though.
  
  ==== Equation
  
  
  *HTML element*: <div>
  
  *Special semantics*: class="equation"footnote:[From DocBook; no close match in EPUB 3 Structural Semantics Vocabulary]
  
  *Note: Support embedded MathML or LaTex, as well as images
  
  *Example*:
  
  
negative.code: 
  *HTML element*: <ul>
  
  *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*:
  
  