<Avneesh> Yes, it looks usual web ex issue. We can use DAISY line

<Avneesh> Lets use DAISY Line:

<Avneesh_> +1 712/432-7300

<Avneesh_> Pin: 25693#

<Avneesh_> Backup number if you face any problems in joining the call:

<BenSchroeter> The access code in the invite is not working for me

<Bill_Kasdorf> could you repeat the instructions? I just got on and all I see is the Pin

<BenSchroeter> Pin is not recognized

<Bill_Kasdorf> thanks

<Bill_Kasdorf> I'm just now getting the same message--pin not recognized

<BenSchroeter> third time's a charm, thanks!

<Bill_Kasdorf> third time worked for me too

<Avneesh_> Requirements:

<Avneesh_> https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-synchronized-multimedia

<scribe> scribe: clapierre

Avneesh: requirements for Silver
... combined meeting issues / requirements that may go into Silver and MO can be in other groups.
... , we thought better idea APA/Silver and PWG A11Y TF during TPAC
... , Silver Req, Matt combined these issues in the link above.

<BenSchroeter> https://github.com/w3c/publ-a11y/wiki/Publishing-issues-for-Silver

Tzvyia: those are the links for Smile

<Avneesh_> https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-synchronized-multimedia

Avneesh: Comments?

Tzviya: we need to be carful about using "EPUB" a11ymetadata support in the EPUB ecosystem as a reason to put this in now. W3C who are not in publishing that they do not understand this, and that this is supported in Schema.org and that the work is already done. I want to make sure that this is not an EPUB only.

<dkaplan3> +1 what tzviya said

Avneesh: yes we are not sticking to the old world that we are now in the W3C

Charles: again EPUB is mentioned in URL Conformance.

Tzviya: in the context with URLs may be problematic. Collection of Pages , something that is not a URL because we want to have 1 URL for the whole publication, not separate URLs.

Avneesh: mobile TF they have a req. to consider files that are not on the web.

Tzviya: so this is offline requirements.

Bill: we should use just "publications" that they consist of multiple resources multiple pages not focus on epub.
... , Matt does this in #3 actually

George: so the section #2 URL based conformance as being a problem needs to be reworded to be harmonized with the publishing WG single URL that personifies the publication.

Avneesh: is there a single URL to the publication already to the web presence.

<Bill_Kasdorf> +1 to Tzviya's suggestion

Tzviya: suggests reorganize this. we may want to start with modularization and online/offline reading which is where the problems come from.
... , then go into the details.

George: 3rd party content thing, would it be intrinsic to the publication?

Avneesh: the only thing that comes in is offline, iframe pulls in from offsite .
... , when it comes with package publication and this snipit is included will this apply?

George: you will ref. lots of things that is not part of the publication. Just because there is a link this is not part of the publication.

Tzviya: we don't need to define linking as that is already part of the web. the issue is 3rd party content that is pulled in.

Avneesh: if you have some live feed that is pulled in during the packaging will this have to be a11y?
... , will the author be responsible.

Tzviya: how can I have control over something I don't write.

George: you choose what 3rd party content you choose to link to.

Avneesh: should we have this as a question for the Silver TF?

Deborah: portability if something is external does it come into the package, from a11y if something is external but is intrinsic to the publication that others have dealt with this like security etc. If something is req. for key functionality and you don't control it, it needs some schema.org outside resource or a local copy needs to be made / verified or your own a11y metadata that outside resources do not meet your a11y claimes.

Avneesh: so we should keep this then as a question.
... navigation #6 not native to the web. achieve support navigation or other things that are not supported by web browser. Maybe a Readium plugin to enhance the web browser. There could be conflicts.

Tzviya: this is not a WCAG issue. this is a PWG with / UX

George: you must have a good UI so this is really main stream.

Tzviya: Chrome vs. Content. Reading systems that the app I develop that works well with the native gestures for example. definitely not a WCAG issue.

George: so media overlays is next question.

Avneesh: Support for MO which was not ever covered by WCAG

George: should we just leave it as a place holder.

Avneesh: we should have a discussion with Silver and open questions we should discuss with them.

George: so an Audio or Sync text/audio book would be a main stream product. I think it should/must be its a type of publicaton.

Avneesh: these kinds of publications is mainstream and a11y
... , mainstream publication break WCAG.

Tzviya: what does it not follow?

Avneesh: an audio book is not a11y to a deaf person for example.
... , WCAG talks about universal accessibility, but audio books that certain users can not access, and it is an optimized for a certain group.

Tzviya: to explain what the issue is, the basic audio book, a deaf blind user could not use the controls etc.

Deborah: we can do some user stories, and have a speculative user story for deaf / deafblind if they only had x they would be able to access this.

George: Sync media piece, there is also the issue of audio book which does not have native a11y features, text can be turned into audio, but audio can not really be turned into text at least a this time, and multiple language issues, so a text eq. for this publication, integrated with sync media or separate product with the eq. content. bring both issues forward.

Avneesh: yes, we can add some headings.

George: will we get with Matt to make these changes. Yes we will email/call tomorrow. ok sounds good.

Avneesh: MediaOverlays - Daniel can you copy/paste the requirements.

<daniel-weck> https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-synchronized-multimedia

Daniel: high level requirements, bottom page have notes design challenges and other groups we should look into.
... , blocks from Open web platform, OWP contains enough of the tools to meet our req.
... , How do we transition from SMILE meets the requirements from previous MO to the future sign language etc.
... , stable for now not a lot of feedback, Marisa and I looking for other groups sync Mulimedia group, web VTT titleing and captioning. Multi-device timing, cloud architecture is just a Note, but what does it mean to have clients/servers
... , We will finalize a draft for our meetings next week. Readium2 has a proposal JSON syntax combined with clip begin/end and text from the OWP fragments work. we haven't yet been able to dig into this, we have some prototypes.
... , desktop reading systems based on Electron and will do some tests on this, we haven't been able to test our theories if this JSON based successor or SMILE, but we will have some things to discuss a TPAC hopefully.
... , we have to figure out who we will need to meet with.

Avneesh: PWG objective, and APA and Silver. main reason Janina could help us identify the technologies and groups we should connect with.
... , PWG presentation what is the main objective there?

Daniel: we want to, some may be familia with EPUB 3 MO, and the function it fulfills, and then identify the technical gap / guideline for creators to use, so we can have an interoperable format. It is possible to create media overlay like content, but we need an easy to implement syntax.

Avneesh: audio books concept in the meeting because that is important.

Tzviya: we don't need to come up with solutions, but excellent that Daniel and Marisa has started.
... , we hope to accomplish MO into publications and packages publications in a standard manner and audio books would be a part of this. Charter we need to include this. what is not part of the charter is not to create the successor to SMILE
... , remember this is not only the Publishing WG to observe. Chaals, Ralph swick, etc. we can't call this SMILE2 or anything like that.
... , don't assume everyone knows what you are talking about but audio books need to be part of this. we are trying to recruit people to be part of this work.

George: one of the issues Janina said why is Web VTT and TML what is lacking for synchronized media? when one media is embedded in another media,
... , or linked to a text file.
... , one being text/audio or video, and they are stand alone products in their own right, and how to bring them together via synchronization and may not be embedding them into each other directly.

Avneesh: Marisa said she will be working on the document why TTML / Web VTT and identify the gaps before the meetings at TPAC.

George: where you have video and video transcripts and if you have a screen play which exists outside of the video, is a good example.

Avneesh: Janina requested, some discussion on music xml. she would like to discuss it. Do we want to have an informal email?

Tzyvia: this will have to be in email Ivan has responded to her.

Avneesh: Next call Nov. 15th and the time will be at 16:UTC and 10am Eastern / 7am Pacific.
... , thank you and looking forward to TPAC.

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/not focus on urls/not focus on epub/
Present: Avneesh tzviya dkaplan3 George mattg clapierre
Found Scribe: clapierre
Inferring ScribeNick: clapierre

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)