-
Notifications
You must be signed in to change notification settings - Fork 9
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
Requirements when distributing audiobooks #12
Comments
(First off: Congrats on the new job!) I think the current draft of the spec and the requirements you list above are close. I agree we should include the abridged/unabridged and explicit content options, which I am happy to discuss in the meeting next week, I don't think they'll be contentious. I have been thinking about the TOC question again. I'm reluctant to open that particular pandora's box but I see both sides of the argument and I've talked to people here about it too. Both options are possible and I would be open to discussing the pros/cons in a world of publication manifest. I'll add it to the agenda as well. Would like to hear options about samples, I think we have covered supplemental material as best we will manage. I don't want to be prescriptive about it in version 1. |
I've seen the following use cases in the various retailer requirements:
It's worth pointing that what Apple does (pointing to the beginning of a sample) and what Google does (define the length of the sample) would work better together than separately. Separate sample fileThis could be handled through a reference in either
Pointing to the beginning of a sampleThis could be handled through a reference in either
Length/duration of a sampleI think this has been suggested by Google before (ping @GarthConboy) as additional |
The Preview PR has been relocated to the Publishing Manifest document here |
@HadrienGardeur It is important to bear in mind that the term 'sample' is used to describe 2 different things, with 2 different purposes. The first (most commonly supplied as a separate file) is a marketing resource, effectively unrelated to the audiobook as it ships. Samples are often created before the audio is available i.e. it is more akin to a movie trailer than a sample of the book. This sample may change over the lifetime of the book, at the whims of the marketing department. The second is a snippet of audio extracted directly from the book. This is more akin to a preview. Both of these can be subject to strict contractual obligations from the author or publisher, and both can exist simultaneously. It is my understanding that Google use the 'sample' (more appropriately a 'preview') to facilitate contextual audio samples based on search results - leveraging the publishers 'you can play X seconds of this book as a sample'. It is worth emphasizing that not all publisher/author contracts allow for this type of sample (but it is becoming more common) The term 'sample' has an established meaning in the industry as the marketing resource, and it is already managed via ONIX deliveries (along with the cover image) and I do not think it appropriate to embed it in the distribution package at all. If we focus on the term |
@geoffjukes could you explain their respective use cases when they both exist simultaneously? I get your point about "trailer" (basically replaces the description or a back cover) vs "preview" (which lets me sample what the experience will be) but I would imagine that most of the time they're used the same way by a retailer. In previous discussions, we've talked about "authored samples" vs "generated samples". My guess is that a retailer should prioritize an "authored sample" over a generated one, but it doesn't hurt to offer at least some controls about the way these "generated samples" are calculated.
"Authored samples" and covers can definitely be delivered using ONIX, but it's still common to have file naming conventions for covers (this is true for both EPUB and audiobooks). "Generated samples" are usually created based on a default setting per retailer and/or contractual obligations (I've seen a lot of contracts with either 5%/10% or the first chapter, whichever is the smallest). If fine-grained controls over the way they're generated (like Apple or Google) is useful, then ONIX can't easily fulfill that role. |
Using your terms @HadrienGardeur - Prior to publishing, the "Authored Sample" will be the only one that exists, and is used to promote the book. After publishing, the "Authored sample" may (or may not) be updated any number of times (in practice, it is rarely updated after publication, unless the book is optioned for a movie or similar). It is true to say that the "Authored Samples" are most often "generated", but it is not true to say that they are always generated, and that is the distinction. I find it useful to think of "Authored Samples" as "highly-abridged versions of the book, used for marketing and promotion only". |
This issue was discussed in a meeting.
View the transcriptHadrien’s issuesWendy Reid: See Audio issue #12 Wendy Reid: The next thing was to quickly make sure we’ve covered up any additional issues with LPF - Hadrien opened up an issue regarding a minor point of metadata, should we have a field for abridged/unabridged, and “does this contain adult content” … I’ll write a PR for in the publication manifest, as they are both valid information for audiobooks or publications in general. Another is a mention of preview, which is already in manifest, but I’ll make a point of saying it’s included in audiobooks as well. … Preview, abridged, and ‘contains explicit material’. Outside of Avneesh’s issue, this is the last to address before the next draft. Ivan Herman: These will be added to publication manifest? Wendy Reid: Yes. The preview stuff is already in there. Ivan Herman: Are we sure those terms don’t exist in schema.org? Wendy Reid: They do exist in schema.org - so those are the ones we need to use. … we need to call them out as ones important to publications. Ivan Herman: One practical thing, I know that Matt (who is out today) has made a pretty big rewrite and I presume he’ll do a PR today or tomorrow. It may be worth waiting for that to get through and done as those issues have already been accepted. … otherwise we get into merge problems. Wendy Reid: I’ll wait for that Garth Conboy: I just wanted to reflect, the other issue that Hadrien raised in #12 - the HTML TOC, as we discussed historically and recently, we do not want to reopen this at this time. His point is that it didn’t map well to audio-ingest platforms. The discussion we had previously.. … was that most support epub, and this is a relic of that, so we want to stay with that HTML agreement, and if this crops up as an implementation issue, it can be re-evaluated, but at the time, we had some producer input as well that got on board with this. … we are in OK shape until we’re at the implementation stage. If we’re wrong there, we can reopen Wendy Reid: Any other questions about Audiobook or LPF work? |
Final updates before TPAC! Including abridged and preview as requested in issue #12. One minor order change to correct the position of Default Reading Order and Resources in the TOC.
Just an update here, I've added We are still discussing |
This issue was discussed in a meeting.
View the transcriptWendy Reid: #12Wendy Reid: there was a suggestion to include 3 things … abridged value … preview … how to include a preview … and the last one, which will get a new issue … the isFamilyFriendly flag … schema doesn’t have a MPAA-type rating … there isn’t a standard … the retailers tend to decide … kobo ask publishers to identify, and then verify … it depends on jurisdiction … i think the flag is worth having … it’s a terrible name, but schema doesn’t have a better one … I’d like to close this issue, and then move the isFamilyFriendly to pub manifest Proposed resolution: Close Audiobooks Issue #12, abridged and preview have been added to the specification, and isFamilyFriendly be moved to Publication Manifest (Wendy Reid) Brady Duga: +1 Charles LaPierre: +1 Wendy Reid: +1 Romain Deltour: +1 Rachel Comerford: when we say move to publication manifest, we’re really just saying that we’re going to open an issue Wendy Reid: yes, just opening an issue Garth Conboy: +1 (but don’t think we should do such a thing in pbu manifest, as I think it’s intractable) Resolution #5: Close Audiobooks Issue #12, abridged and preview have been added to the specification, and isFamilyFriendly be moved to Publication Manifest Rachel Comerford: +1 Dave Cramer: Plus one |
Context
I’ve recently started a new position as Director of R&D at De Marque, an aggregator and digital distributor connected to major ebook and audiobook retailers.
Since we’re receiving audiobooks from major publishers in Canada, France, Spain and Italy, the audiobook spec is very relevant for us as it might become the standard format that we request from them.
Given the lack of a standard format for distributing audiobooks, it felt relevant to explore what various retailers expect to receive when we deliver them an audiobook and figure out what might be different and/or missing for the proposed spec.
Documentation
Manifest Examples
Apple (XML)
Kobo (JSON)
Notes
Closing Remarks
The text was updated successfully, but these errors were encountered: