-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pagination source not displayed #484
Comments
I agree with this point; it's important, but "displaying" it may not be the best approach. Some considerations that I guess lead us not to integrate it before:
That said, we should include a note or indication that the print pagination source should be identifiable (linked or displayed, depending on the audience). |
Thanks Gautier for the explanation. I agree that displaying a unique identifier, such as an ISBN, isn't very user friendly, and adding a note about this is a great idea. |
This is an interesting problem. I agree that many people will want to know the print source. Some ideas: The reading system could present this information to the user, but this would be after the publication was purchased/acquired, which is not great. The metadata could be presented, but on its own is not too useful, unless it was resolved to the medata of the source, which also could add to confusion. The print source could be to a paperback or to a hard cover version which would probably have different pages; are the identifiers different? Finally there is the accessibility summary which could be used to provide specifics. For example: the publisher could in the accessibility summary that the print source for the publication is: Then give the details. The question remains for us on what to do in the guidelines. |
Distributors often send relationships between editions through ONIX, for example:
Retailers and libraries can use these references in their catalogs in order to group editions together or provide links between them. In theory, this EPUB metadata would allow a completely different reference (to another print edition for example). In practice, I'm not sure that anyone will be able to use this EPUB metadata. The best case scenario that I can imagine:
From a reading system perspective, I don't think that they'll be able to do anything at all. Reading systems need to interact with a catalog (in OPDS for example) to do anything useful with this metadata. |
Thinking about education, the students wants the same page association in their digital version as the students using a physical print book. It would be wonderful if the student and educators could confirm this relationship prior to selecting it for the course. Today, all to often the student is even using a previous edition of the title the rest of the students are using. |
EPUB Accessibility 1.1 states:
For this, the
a11y:pageBreakSource
property exists.Recently, support for identifying the pagination source for reflowable EPUBs using this property was added to InDesign.
ONIX provides a related code (13 in Codelist 51) to identify that a digital product corresponds to a specific print edition.
However, neither the Display Guide nor the Techniques mention displaying the pagination source to users.
This raises a question: Why are content creators required to include this metadata, and why do we promote adding support for it in production software, if it is not displayed to users?
The text was updated successfully, but these errors were encountered: