Publication with different profiles? #70
-
|
I am wondering if it's possible to represent a publication that confirms to multiple profiles. For example a pdf can conform to the pdf profile, but also to the divina profile, where each page is converted to an image. Can this be represented in opds 2? Another case would be a comic book in epub format, that would confirm to both epub and divina profiles. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
I don't think this is possible, because a profile requires specific media types declared in the reading order. What you could have, is a link with an Or declare a main profile (say, EPUB) and add in the reading order links an What's your use case exactly (user flow)? Maybe there's a better way to handle that. |
Beta Was this translation helpful? Give feedback.
-
|
Well it's more about client support. Komga currently handles everything as images, so a pdf would be served page by page converted in jpeg. If a client cannot handle pdf, it's quite probably it can display images. Having alternate image resources (as a divina profile) would let the client display the pdf page by page, without the need to handle pdf format. The same goes for epub that are image only, even though this use case is much more limited in practice. A client which cannot handle epub could still display images from a divina profile. |
Beta Was this translation helpful? Give feedback.
-
|
This is usually handled as several acquisition links (with different media types) in the publication entry of the OPDS feed. The client app can choose which type of format it supports for the publication and download/stream just that. |
Beta Was this translation helpful? Give feedback.
-
|
Aren't acquisition links for download only? The publication in the publications feed already contain the full publication detail, including the profile and resources. |
Beta Was this translation helpful? Give feedback.
-
|
Not necessarily, if it points to a manifest it can be used for streaming. In Aldiko, we apply this approach to audiobooks. If a RWPM acquisition link is provided, we stream it. If a packaged audiobook acquisition link is available, we download it. In the user interface, we provide the option to switch between the manifest and the packaged version directly from the bookshelf. This is appreciated for offline reading. Theoretically you could have a full publication (with |
Beta Was this translation helpful? Give feedback.
-
Thanks Mickael ! You managed to shed some light on a point that is very much not clear at all in the spec, and that will really help me ! |
Beta Was this translation helpful? Give feedback.
Not necessarily, if it points to a manifest it can be used for streaming. In Aldiko, we apply this approach to audiobooks. If a RWPM acquisition link is provided, we stream it. If a packaged audiobook acquisition link is available, we download it. In the user interface, we provide the option to switch between the manifest and the packaged version directly from the bookshelf. This is appreciated for offline reading.
Theoretically you could have a full publication (with
readingOrder) in an OPDS 2 feed, but I don't know any implementation supporting this. It brings the issues we talked about with multiple profiles and the JSON payload of the feed might get quite large.