You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.html
+55-36Lines changed: 55 additions & 36 deletions
Original file line number
Diff line number
Diff line change
@@ -76,11 +76,13 @@
76
76
<h2>Notes on the HTMLBook Specification</h2>
77
77
<p>Requirements for HTML5 elements in the HTMLBook specification are below. Special semantic inflections for <code>data-type</code> attributes, unless otherwise noted, come from <ahref="http://idpf.org/epub/vocab/structure/">EPUB 3 Structural Semantics Vocabulary</a></p>
78
78
<p>Many content models refer to “Block elements” or “Inline elements”; please see <ahref="#block_elements">Block Elements</a> and <ahref="#inline_elements">Inline Elements</a> for the corresponding list of HTML5 elements that belong to each of these categories.</p>
79
-
<p>If no content model or attribute requirements are explicitly specified, then HTMLBook adopts the corresponding requirements in the [[!HTML5]] Specification</a></p>
79
+
<p>If no content model or attribute requirements are explicitly specified, then HTMLBook adopts the corresponding requirements in the [[!HTML5]] Specification</p>
80
80
</section>
81
81
<section>
82
82
<h2>Revision History and Notes</h2>
83
83
<dl>
84
+
<dt>8 April 2014</dt>
85
+
<dd>Updated specifications for section subtitles to comply with best practices set forth in <ahref="http://www.w3.org/TR/html5/common-idioms.html#common-idioms">“Common idioms without dedicated elements”</a> in [[!HTML5]] Specification.</dd>
<p><strong>Attribute requirements</strong>: <code>data-type="book"</code><spandata-type="footnote">(Not in [[EPUB3SSV]]; from [[DOCBOOK]])</span></p>
101
-
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains book title; then zero or more <code><h2></code> elements for subtitle content; then one or more Book Component elements as children (<code><div></code> for Part elements, <code><nav></code> for Table of Contents, and <code><section></code> elements for all other book divisions)</p>
103
+
<p><strong>Content model</strong>: Optional <code><h1></code> that contains book titleor <ahref="#header_block">Header block</a> that contains book title and optional subtitle content; then one or more Book Component elements as children (<code><div></code> for Part elements, <code><nav></code> for Table of Contents, and <code><section></code> elements for all other book divisions)</p>
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains chapter title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
119
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains chapter titleor <ahref="#header_block">Header block</a> that contains chapter title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
<p><strong>Attribute requirements</strong>: <code>data-type="appendix"</code> or <code>data-type="afterword"</code>, depending on content</p>
134
-
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains appendix title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
136
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains appendix titleor <ahref="#header_block">Header block</a> that contains appendix title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains bibliography title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
152
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains bibliography titleor <ahref="#header_block">Header block</a> that contains bibliography title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains glossary title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
168
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains glossary titleor <ahref="#header_block">Header block</a> that contains glossary title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
167
169
<p><strong>Best practices</strong>: List of glossary terms should be marked up using <code><dl></code> elements with a <code>data-type</code> of "glossary", with <code><dt></code> children with a <code>data-type</code> of "glossterm" and <code><dd></code> children with a <code>data-type</code> of "glossdef". Term text should be wrapped in a <code><dfn></code>. However, none of this is formally required by the spec.</p>
<p><strong>Attribute requirements</strong>: <code>data-type="preface"</code>, <code>data-type="foreword"</code>, or <code>data-type="introduction"</code>, depending on content</p>
187
-
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains preface title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
189
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains preface titleor <ahref="#header_block">Header block</a> that contains preface title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
<p><strong>Attribute requirements</strong>: <code>data-type="halftitlepage"</code>, <code>data-type="titlepage"</code>, <code>data-type="copyright-page"</code>, or <code>data-type="dedication"</code>, depending on content</p>
203
-
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains frontmatter section title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
205
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains frontmatter section titleor <ahref="#header_block">Header block</a> that contains frontmatter title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
<p><strong>Attribute requirements</strong>: <code>data-type="colophon"</code>, <code>data-type="acknowledgments"</code>, <code>data-type="afterword"</code>, or <code>data-type="conclusion"</code>, depending on content</p>
216
-
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains backmatter section title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
218
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains backmatter section titleor <ahref="#header_block">Header block</a> that contains backmatter title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains part title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements that compose the optional Part introduction; then one or more <code><section></code> elements representing Book Component children other than a Part</p>
234
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains part titleor <ahref="#header_block">Header block</a> that contains part title and optional subtitle content; then zero or more Block Elements that compose the optional Part introduction; then one or more <code><section></code> elements representing Book Component children other than a Part</p>
<p><strong>Content model</strong>: First child must be <code><h1></code> that contains index title; then zero or more <code><h2></code> elements for subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
272
+
<p><strong>Content model</strong>: First child must be either <code><h1></code> that contains index titleor <ahref="#header_block">Header block</a> that contains index title and optional subtitle content; then zero or more Block Elements; then zero or more Sect1 children (<code><section data-type="sect1"></code>)</p>
271
273
<p><strong>Best practices</strong>: HTMLBook recommends following the [[EPUBINDEX]] specification and using <code><ol></code>/<code><li></code> elements for marking up index entries, with <code>data-type</code> attributes used for semantic inflection as appropriate, but none of this is a formal spec requirement</p>
<p><strong>Attribute requirements</strong>: <code>data-type="sect1"</code>, <code>data-type="sect2"</code>, <code>data-type="sect3"</code>, <code>data-type="sect4"</code>, <code>data-type="sect5"</code><spandata-type="footnote">(From [[DOCBOOK]] vocabulary)</span>, depending on hierarchy level. <code>sect1</code> is used for <code><section></code> elements nested directly in main Book components ("chapter", "appendix", etc.). <code>sect2</code> is used for <code><section></code> elements nested in a <code>sect1</code><code><section></code>, <code>sect3</code> is used for <code><section></code> elements nested in a <code>sect2</code><code><section></code>, and so on.</p>
294
-
<p><strong>Content model</strong>: The first child must be a main heading element corresponding to the hierarchy level indicated by <code>data-type</code> value, as follows:</p>
296
+
<p><strong>Content model</strong>: The first child must either be a main heading element corresponding to the hierarchy level indicated by <code>data-type</code> value, as follows:</p>
295
297
<predata-type="programlisting">"sect1" -> h1
296
298
"sect2" -> h2
297
299
"sect3" -> h3
298
300
"sect4" -> h4
299
301
"sect5" -> h5</pre>
300
-
<p>The heading is followed by zero or more subheading elements whose hierarchy level is one lower than the main heading (e.g., <code><h2></code> for a <code>sect1</code>), folloed by zero or more Block elements, followed by zero or more <code><section></code> elements with a <code>data-type</code> value one level lower in the hierarchy, as long as the parent section is a "sect4" or higher (e.g., <code><section data-type="sect4"></code> nested in <code><section data-type="sect3"></code>)</p>
302
+
<p>or a <ahref="#header_block">Header block</a> that contains section title and optional subtitle content. This is followed by zero or more Block elements, followed by zero or more <code><section></code> elements with a <code>data-type</code> value one level lower in the hierarchy, as long as the parent section is a "sect4" or higher (e.g., <code><section data-type="sect4"></code> nested in <code><section data-type="sect3"></code>)</p>
<p><strong>Content Model</strong>: A Heading element at the proper level designated (<code>h1</code>–<code>h5</code>)
665
+
for the parent Book Component, as outlined in the previous <ahref="#_headings">Headings</a> section (e.g., an <code><h1></code> for a chapter <code><header></code>); then zero or more <code><p></code> elements for subtitles or author attributions, each of which must have a <code>data-type</code> of either <code>subtitle</code> or <code>author</code></p>
0 commit comments