Media overlays and the definition of the links object

[dauwhe]

Should we really create a dedicated element for media-overlay? Can we design something more generic instead that could also handle other use cases? EPUB 3.1 introduces duration, do we need other media specific attributes?

As Element

{
        "href": "xhtml/chapter01.xhtml",
        "type": "application/xhtml+xml",
        "media-overlay": "chapter1_audio.smil"
      }

As nested link element

{
        "href": "xhtml/chapter03.xhtml",
        "type": "application/xhtml+xml",
        "links": {
            "type:": "application/smil+xml",
            "href": "chapter3_audio.smil",
            "rel": "media-overlay"
         }
      }

[HadrienGardeur]

I think we need to explore that as a solution for resource level alternate representations (vs document level with renditions). Is it limited to media overlay and fallbacks? Probably not.

[HadrienGardeur]

I'm also wondering if media overlays couldn't behave more like CSS:

• we reference them in the manifest (renamed "resources" in BFF)
• but the link between HTML and a SMIL file is made in the HTML resource itself using a element

@dauwhe thoughts?