comments of brady and matt incorporated

w3c · Nov 9, 2021 · 202058d · 202058d
1 parent 444a479
commit 202058d
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 10 deletions.
diff --git a/epub33/core/index.html b/epub33/core/index.html
@@ -3178,10 +3178,9 @@ <h6>The <code>itemref</code> Element</h6>
 								</dd>
 							</dl>
 
-							<p id="attrdef-itemref-idref">Each <code>itemref</code> element MUST reference the ID
-								[[XML]] of a unique <a href="#elemdef-package-item"><code>item</code></a> in the
-									<a>manifest</a> via the IDREF [[XML]] in its <code>idref</code> attribute (i.e., two
-								or more <code>itemref</code> elements MUST NOT reference the same <code>item</code>).</p>
+							<p id="attrdef-itemref-idref">Each itemref element MUST reference the ID of an <a href="#elemdef-package-item"><code>item</code></a> in the <a>manifest</a> via the IDREF [[XML]]
+								in its <code>idref</code> attribute, and item IDs MUST NOT be referenced more than once.
+							</p>
 
 							<p id="confreq-spine-itemtypes">Each referenced manifest <code>item</code> MUST be either a)
 								an <a>EPUB Content Document</a> or b) another type of <a>Publication Resource</a> which,

diff --git a/epub33/rs/index.html b/epub33/rs/index.html
@@ -550,12 +550,16 @@ <h3>Spine</h3>
 					<code>properties</code> attributes that they do not recognize.</p>
 
 				<p>
-					When presented with a single <a>Publication Resource</a> that is repeated multiple times in the linear flow 
-					of the spine, Reading Systems SHOULD do their best to display that content in the correct location of that linear flow. 
-					The Reading System SHOULD treat these as distinct pages for UI purposes (for example, each occurrence
-					could be independently bookmarked or annotated), but when following an internal link to that
-					item the Reading System SHOULD move to the position of the first occurrence of the
-					document in the linear flow.
+					<span id="confreq-rs-pkg-duplicate-item-rendering">Reading Systems MUST NOT skip spine references to duplicate manifest items when rendering the linear reading order.</span> 
+					<span id="confreq-rs-pkg-duplicate-item-ui">
+						The Reading System MUST treat these as distinct items for UI purposes (for example, each occurrence
+						could be independently bookmarked or annotated).
+					</span>
+					<span id="confreq-rs-pkg-duplicate-item-hyperlink">
+						When a Reading System follows a hyperlink to a resource referenced multiple times in the
+						spine, the Reading System MUST move to the position of the first occurrence of the
+						document in the linear reading order.
+					</span>
 				</p>
 			</section>