Remove the precedence and processing requirements for linked records #2512
Conversation
| <p id="confreq-rs-pkg-link-rendering">Reading systems MUST ignore any instructions contained in | ||
| linked resources related to the layout and rendering of the EPUB publication.</p> |
There was a problem hiding this comment.
This sentence looks a bit different from the previous ones. Was it also discussed that this should go?
(Although... we do not seem to have any test for it anyway, so we may just well remove it...)
There was a problem hiding this comment.
It reads like another case of precedence over what might have been expressed in a browser-friendly package document -- don't use the layout behaviours that were defined for a browser rendering.
You can add properties to the package metadata if you want to control layout and rendering, or create custom attributes in xhtml, so explicitly banning from linked resources when we no longer expect the bff format seems a bit paranoid. No one's going to go through the effort of defining instructions through linked records when the simpler methods exist.
As discussed on the 2023-01-05 telecon, this PR removes the precedence rules and processing requirements for linked records.
These rules were added in EPUB 3.1 when there was an expectation that there might be linked browser-friendly json records in the container that reading systems could harvest additional information from. The test results have proven that without that format materializing, support for bibliographic records has not taken off, leaving the precedence and processing rules an unnecessary complexity. This change moves the specification back to its original purpose of allowing linked records for use, for example, with library systems.
Preview | Diff