Body: <p>I'm manually converting a book from HTML to ePub. The book is an anthology of works: a work of three volumes with each volume comprising several chapters.</p>
  
  <p>I'd like to use the <a href="https://idpf.github.io/epub-vocabs/structure/" rel="nofollow noreferrer">Structural Semantic Vocabulary (SSV)</a> to describe the components—let's just say for arbitrary purposes for now. However, I also I intend to split the content into HTML files per-chapter with an additional title page per-volume:</p>
  
  <pre><code>volume-i-titlepage.xhtml
  volume-i-chapter-i.xhtml
  volume-i-chapter-ii.xhtml
  volume-ii-titlepage.xhtml
  volume-ii-chapter-i.xhtml
  volume-ii-chapter-ii.xhtml
  </code></pre>
  
  <p>Thus I'm unsure where you would identify <code>epub:type="volume"</code> in a way that would mark all relevant content as being a child of that volume.</p>
  
  <p><em>Another example of this would be if you split a chapter over two content documents, I'm not sure where you would apply <code>epub:type="chapter"</code>.</em></p>
  
  <p>If it were a single content document, I suppose I'd use markup like so:</p>
  
  <pre><code>&lt;section epub:type="volume"&gt;
    &lt;header epub:type="titlepage"/&gt;
    &lt;section epub:type="chapter"/&gt;
    &lt;section epub:type="chapter"/&gt;
  &lt;/section&gt;
  
  &lt;section epub:type="volume"&gt;
    &lt;header epub:type="titlepage"/&gt;
    &lt;section epub:type="chapter"/&gt;
    &lt;section epub:type="chapter"/&gt;
  &lt;/section&gt;
  </code></pre>
  
  <p>Looking at more strict '<a href="http://idpf.org/epub/profiles/edu/spec/" rel="nofollow noreferrer">edupub</a>' compliance, would on cursory reading suggest that such semantic blocks not be split between content documents.</p>
  
  <p>A secondary concern is whether the implied root semantics here is compliant as would be a challenge for any anthology/compilation:</p>
  
  <pre><code>bodymatter
      frontmatter
      bodymatter
      bodymatter
  /bodymatter
  
  bodymatter
      frontmatter
      bodymatter
      bodymatter
  /bodymatter
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-19T12:54:47.330Z
Comments.Text: This [edupub sample](https://github.com/IDPF/education/tree/master/samples/structure-sample-01) perhaps reflects intended practice.
Comments.UserDisplayName: rgchris
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-19T18:12:54.957Z
Comments.Text: The section [content chunking](https://web.archive.org/web/20140601002912/http://epubzone.org/news/epub-3-content-documents#_content_chunking) in this article suggests the best option is to remove all children from parents where some children will appear in separate content documents.
Comments.UserDisplayName: rgchris
Tags: <epub><chapters>
Title: What is the correct way to apply Structural Semantic Vocabulary over multiple content documents?
UserDisplayName: rgchris
ThreadText: # What is the correct way to apply Structural Semantic Vocabulary over multiple content documents?
  
  (Asked by: username_0 on 2020-05-18)
  
  I'm manually converting a book from HTML to ePub. The book is an anthology of works: a work of three volumes with each volume comprising several chapters.
  
  I'd like to use the [Structural Semantic Vocabulary (SSV)](https://idpf.github.io/epub-vocabs/structure/) to describe the components—let's just say for arbitrary purposes for now. However, I also I intend to split the content into HTML files per-chapter with an additional title page per-volume:
  
  ```
  volume-i-titlepage.xhtml
  volume-i-chapter-i.xhtml
  volume-i-chapter-ii.xhtml
  volume-ii-titlepage.xhtml
  volume-ii-chapter-i.xhtml
  volume-ii-chapter-ii.xhtml
  
  ```
  
  Thus I'm unsure where you would identify `epub:type="volume"` in a way that would mark all relevant content as being a child of that volume.
  
  *Another example of this would be if you split a chapter over two content documents, I'm not sure where you would apply `epub:type="chapter"`.*
  
  If it were a single content document, I suppose I'd use markup like so:
  
  ```
  <section epub:type="volume">
    <header epub:type="titlepage"/>
    <section epub:type="chapter"/>
    <section epub:type="chapter"/>
  </section>
  
  <section epub:type="volume">
    <header epub:type="titlepage"/>
    <section epub:type="chapter"/>
    <section epub:type="chapter"/>
  </section>
  
  ```
  
  Looking at more strict '[edupub](http://idpf.org/epub/profiles/edu/spec/)' compliance, would on cursory reading suggest that such semantic blocks not be split between content documents.
  
  A secondary concern is whether the implied root semantics here is compliant as would be a challenge for any anthology/compilation:
  
  ```
  bodymatter
      frontmatter
      bodymatter
      bodymatter
  /bodymatter
  
  bodymatter
      frontmatter
      bodymatter
      bodymatter
  /bodymatter
  
  ```
  
  **Tags:** epub, chapters
  
  > **Comments:**
  > **username_0**: This [edupub sample](https://github.com/IDPF/education/tree/master/samples/structure-sample-01) perhaps reflects intended practice.  
  > **username_0**: The section [content chunking](https://web.archive.org/web/20140601002912/http://epubzone.org/news/epub-3-content-documents#_content_chunking) in this article suggests the best option is to remove all children from parents where some children will appear in separate content documents.  
  
  ---
  
  ## 0 answers
  
  