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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
The reason will be displayed to describe this comment to others. Learn more.
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.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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