Deprecate Media Overlays embedded media#2402
Conversation
In the core spec: Removed 9.3.2.4 entirely, added note to MO text element about how referring to embedded timed media with the MO text element is possible but unspecified. In the RS spec: Removed 9.3.2 and added a note about deprecation to the top of 9.3.
|
I wonder if we should give this the TTS treatment and instead of making it like it never existed, move the authoring and reading system requirements to a note? (Maybe including the TTS section.) It might never get implemented, but publishing as a note leaves it as an option. |
I honestly don't think it's worth the effort. I don't think it will ever get implemented and to specify it properly, even as a note, would be a not-insignificant time investment. |
iherman
left a comment
There was a problem hiding this comment.
@marisademeglio (also answering your question) the entries in the change sections are added by hand. Copy-paste-modify is your friend...
I agree. The TTS seems to be on much more stable foundations, using external and, mainly, more widely known standards. Although MO is based on SMIL, the latter is, alas!, a completely unknown standard and probably the only reason it has not been deprecated is EPUB's usage of (a small subset of) SMIL. A WG note, to be made worthy of publication, would require quite some work. |
Look out for multiple renditions, in that case... At any rate, if we don't, then this introduces ambiguity onto the authoring side, as it doesn't say what's supposed to happen now if you do reference an audio or video element. It might be helpful to add a note where media elements are mentioned that previous version of the specification defined auto-playback of these elements, but it's no longer the case (if audio is not provided, then TTS kicks in). Authors should consider alerting users that these elements exist and they need to go back and find them after listening to the work. |
epub33/rs/index.html
Outdated
| <p class="note">Earlier versions of this specification included some information about embedded audio and | ||
| video [epubmediaoverlays-32]. This feature has been deprecated.</p> |
There was a problem hiding this comment.
We can't deprecate in a note, otherwise the deprecation doesn't have normative standing. I'd recreate 9.3.2 rather than completely deleting the section so it matches other deprecated features. I can't suggest a fix through the github interface, but put back something like:
<section id="sec-embedded-media">
<h4>Embedded audio and video (deprecated)</h4>
<p>Automatic playback of embedded audio and video is now <a data-cite="epub-33#deprecated">deprecated</a>.</p>
<p>Refer to its definition in [[epubmediaoverlays-32]] for more information.</p>
</section>
There was a problem hiding this comment.
This change should also be integrated before merging.
Actually, re-reading the note that's there I can probably live with it as-is. I was trying to read the line in the diff and it looked like it was only referring to video. |
Co-authored-by: Ivan Herman <ivan@ivan-herman.net>
There is such a mention in the RS spec. Do you mean to add something similar in the core spec as well? |
|
The issue was discussed in a meeting on 2022-08-26 List of resolutions:
View the transcript1. Deprecate embedded audio or video as targets for Media Overlay
|
|
@marisademeglio @mattgarrish we have now a WG resolution to merge this after we all agree on the textual details. From my point of view, it is a go; I do not have any strong feeling about #2402 (comment) |
Great, no more changes needed then ? |
Well, you should wait for @mattgarrish : he seems to have proposed some changes and those seem to be open still. Once that is settled it is a go... |
Co-authored-by: Matt Garrish <mattgarrish@users.noreply.github.com>
|
This looks fine to me now but looks like we need to add a biblio entry for MO 3.2 to the RS file. I'm going to merge and manually correct that now. |
Fixes #2397
In the core spec:
Removed 9.3.2.4 entirely, added note to MO text element about how referring to embedded timed media with the MO text element is possible but unspecified.
In the RS spec:
Removed 9.3.2 and added a note about deprecation to the top of 9.3.
See:
Preview | Diff