- From: Marisa DeMeglio <marisa.demeglio@gmail.com>
- Date: Mon, 28 Sep 2020 12:33:58 -0700
- To: Matt Garrish <matt.garrish@gmail.com>
- Cc: Ivan Herman <ivan@w3.org>, public-epub-wg@w3.org
- Message-Id: <D348E5A9-1628-4D73-9F6E-B07D7525C530@gmail.com>
I wonder how it would work with the future of Sync Media [1], which is looking more and more like an evolution of MO - would having a merged EPUB + MO slow us down in the future if we wanted to incorporate these ideas into a future (beyond 3.3) MO spec? Marisa 1. Proposed draft, waiting for CG feedback: https://raw.githack.com/w3c/sync-media-pub/wip/docs/new/sync-media.html <https://raw.githack.com/w3c/sync-media-pub/wip/docs/new/sync-media.html> > On Sep 28, 2020, at 07:03, matt.garrish@gmail.com wrote: > > I’m slowly coming around to the idea of merging media overlays with the rest of the core, even if it is a bolt-on optional technology. The fact it was assigned a core 3.X incrementing number does make it stick out if not incorporated, but more usefully it just harmonizes things like the schema and vocabulary definitions together, and doesn’t require cross-referencing all the terminology. > > Here’s what it looks like merged: https://mattgarrish.github.io/publ-epub-revision/epub33x/spec/epub-core.html <https://mattgarrish.github.io/publ-epub-revision/epub33x/spec/epub-core.html> > > The one oddity is that the reading system behaviours are much better spelled out for media overlays than for the core specs, so we kind of go from almost bullet form things a reading system is required to do to prose explanations. But maybe that’s part of what we need to fix in terms of testing, too. > > Matt
Received on Monday, 28 September 2020 19:34:14 UTC