Re: Reviewing our issues

Might be that I am advocating for what should be a separate spec here. This
will be Media Overlays in JSON, and that is of course fine.
I have just been planning for a more dynamic usage model for
synchronization in Audiobooks etc. I guess we can use WebAnnotations for
images etc in Audiobooks and Video.

On Thu, Nov 14, 2019 at 3:45 PM <kerscher@montana.com> wrote:

> I like Synchronized Narration
>
>
>
> Best
>
> George
>
> *From:* AUDRAIN LUC <LAUDRAIN@hachette-livre.fr>
> *Sent:* Thursday, November 14, 2019 6:38 AM
> *To:* lars@mywomags.com; Laurent Le Meur <laurent.lemeur@edrlab.org>
> *Cc:* Marisa DeMeglio <marisa.demeglio@gmail.com>; W3C Synchronized
> Multimedia for Publications CG <public-sync-media-pub@w3.org>
> *Subject:* Re: Reviewing our issues
>
>
>
> I don’t know if this is French only, but I think “narration” encompasses
> any kind of media: text, image, audio, vidéo…
>
> “Synchronized Narration” means then telling the same story using different
> sort of media and synchronizing between them.
>
> It’s not the media that is synchronized but the narration.
>
>
>
> Luc
>
>
>
> *De : *Lars Wallin <lars@sharemyworld.se>
> *Répondre à : *"lars@mywomags.com" <lars@mywomags.com>
> *Date : *jeudi 14 novembre 2019 à 14:29
> *À : *Laurent Le Meur <laurent.lemeur@edrlab.org>
> *Cc : *Marisa DeMeglio <marisa.demeglio@gmail.com>, W3C Synchronized
> Multimedia for Publications CG <public-sync-media-pub@w3.org>
> *Objet : *Re: Reviewing our issues
> *Renvoyer - De : *<public-sync-media-pub@w3.org>
> *Renvoyer - Date : *jeudi 14 novembre 2019 à 14:29
>
>
>
> Just a reminder that we want to use for audiobooks etc as well.
> "Narration" will feel really strange to people (I don't think it's only a
> me thing).
>
>
>
> And if we can not use the word "Media" anymore within specs such as this,
> then we really have a problem 😉
>
>
>
> On Thu, 14 Nov 2019, 13:09 Laurent Le Meur, <laurent.lemeur@edrlab.org>
> wrote:
>
> +1 for Sync Narration.
>
> -1 for the addition of for Publications.
>
>
>
> With Sync *Narration* we use a term which source is clearly the
> publishing culture. Plus, *narration* is one of the main properties in
> the JSON document representing the alternate rendition of the source
> content.
>
> The issue with Sync *Media* is its proximity (in the W3C) with terms like
> *Media* Queries and *Media* & Entertainment Activity.
>
>
>
> Laurent
>
>
>
> Le 12 nov. 2019 à 22:14, Marisa DeMeglio <marisa.demeglio@gmail.com> a
> écrit :
>
>
>
> Ok, let’s try this again - issue #24 is about naming. We should pick a
> name because audiobooks is likely going to CR, and our note is referenced
> by that spec. I do understand that as a CG note, we can rename our document
> with little consequence, but as we will be referenced informatively by a
> rec track document, it would be really nice to choose now and stick with
> it.
>
>
>
> Based on this issue:
>
> https://github.com/w3c/sync-media-pub/issues/24
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fsync-media-pub%2Fissues%2F24&data=02%7C01%7Claudrain%40hachette-livre.fr%7C588d3c3e79334d38118108d769069fc8%7Cf881a2c50a89483181b1c7846c49594d%7C0%7C0%7C637093349487471876&sdata=%2ByZSH%2BEENK3PwPrL%2FJQWVVyeEMMSpKf9rVOsYH3%2BvN8%3D&reserved=0>
>
>
>
> I see these options:
>
>
>
> Synchronized Media
>
> Synchronized Narration
>
> Synchronized Alternative Media
>
>
>
> Any of them could be appended with “for Publications”.
>
>
>
> Let’s vote. Please indicate:
>
>
>
> 1. Which of the three choices you like the most.
>
> 2. Whether you prefer to append with “for Publications” or not
>
>
>
> We don’t need new ideas or other variations at this point. We’re a small
> group, so your one vote could change everything!! Voting closes by the end
> of this week (Nov 15 end of day in California).
>
>
>
> Thanks
>
> Marisa
>
>
>
>
>
>
>
>
>
> On Oct 11, 2019, at 15:07, Marisa DeMeglio <marisa.demeglio@gmail.com>
> wrote:
>
>
>
> Yep, that was the idea! And I see that it worked - thanks for chiming in.
>
>
>
> And now for something completely different — I won’t call it baseurl but
> …
>
> https://github.com/w3c/sync-media-pub/issues/26
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fsync-media-pub%2Fissues%2F26&data=02%7C01%7Claudrain%40hachette-livre.fr%7C588d3c3e79334d38118108d769069fc8%7Cf881a2c50a89483181b1c7846c49594d%7C0%7C0%7C637093349487471876&sdata=4CVV2Y7F5ADrKJlRT5aRG%2F%2BGM2hgTvNw29K3dEcKCTw%3D&reserved=0>
>
>
>
> Marisa
>
>
>
>
>
>
>
> On Oct 11, 2019, at 01:30, Romain <rdeltour@gmail.com> wrote:
>
>
>
> Stirring up participation with a bikeshedding naming issue, I see what you
> did there… well played (grin).
>
>
>
> More seriously, +1 to using GitHub directly. Possibly with an email
> reminder from time to time for pressing issues which lack any comments.
>
>
>
> Best,
>
> Romain.
>
>
>
>
>
>
>
> On 10 Oct 2019, at 23:03, Marisa DeMeglio <marisa.demeglio@gmail.com>
> wrote:
>
>
>
> Hi all,
>
>
>
> I plan to work in the coming days and weeks on resolving the remaining
> issues in our tracker, and cleaning up the draft reports.
>
>
>
> I’d also like to engage the CG more as I do this work. Does it work best
> to discuss the issues on this list, or would it be preferable to use the
> github tracker directly?
>
>
>
> Here’s the first issue. It’s a relatively easy one, I think:
>
> https://github.com/w3c/sync-media-pub/issues/24
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fsync-media-pub%2Fissues%2F24&data=02%7C01%7Claudrain%40hachette-livre.fr%7C588d3c3e79334d38118108d769069fc8%7Cf881a2c50a89483181b1c7846c49594d%7C0%7C0%7C637093349487471876&sdata=%2ByZSH%2BEENK3PwPrL%2FJQWVVyeEMMSpKf9rVOsYH3%2BvN8%3D&reserved=0>
>
>
>
> Thanks
>
> Marisa
>
>
>
>
>
>
>
>
>
>
>
>