IRC log of ad on 2018-10-25

Timestamps are in UTC.

08:41:45 [RRSAgent]
RRSAgent has joined #ad
08:41:45 [RRSAgent]
logging to https://www.w3.org/2018/10/25-ad-irc
08:41:50 [Zakim]
Zakim has joined #ad
08:41:54 [nigel]
rrsagent, make logs public
08:42:18 [onishi]
onishi has joined #ad
08:42:52 [ericc]
ericc has joined #ad
08:43:50 [nigel]
scribe: nigel
08:44:23 [nigel]
Chair: Nigel
08:45:14 [nigel]
Present+ Nigel_Megitt, Marise_Demeglio, Eric_Carlson, Andreas_Tai, Masayoshi_Onishi, Matt_Simpson
08:45:18 [nigel]
Topic: Introductions
08:46:12 [nigel]
Nigel: Welcome everyone to the first face to face meeting of the AD CG.
08:47:41 [nigel]
.. Run through of agenda
08:47:59 [nigel]
-> https://www.w3.org/community/audio-description/files/2018/10/AD-CG-F2F-2018-10-25.pdf Slides
08:48:35 [nigel]
Nigel: In the room we have:
08:48:42 [nigel]
.. Nigel Megitt (BBC)
08:49:10 [nigel]
.. Marisa Demeglio (DAISY consortium), in the Publishing WG and interested in accessibility
08:50:21 [nigel]
.. Eric Carlson (Apple), on the Webkit team, mostly working on media in the web, and
08:50:28 [nigel]
.. of course very interested in accessibility solutions.
08:50:55 [nigel]
Andreas: Andreas Tai (IRT), mainly work on subtitles and captions and also look at other
08:51:10 [nigel]
.. accessibility. Unfortunately not yet resources for dedicating time to this, but interested
08:51:13 [nigel]
.. in the status.
08:51:25 [nigel]
s/.. Eric/ericc: Eric
08:51:50 [nigel]
onishi: Onishi (NHK), NHK use 4K and 8K broadcast service and this uses TTML. I'd like
08:51:56 [nigel]
.. to research use case for TTML.
08:52:17 [nigel]
Matt: Matt Simpson (Red Bee), Head of Portfolio for Access Services, probably one of the
08:52:32 [nigel]
.. biggest producers of audio description by volume for a number of clients around the world.
08:52:37 [nigel]
Nigel: Thank you all
08:53:54 [nigel]
Regrets: John_Birch
08:54:03 [nigel]
Topic: Current and future status
08:54:21 [nigel]
.. AD CG set up earlier in the year, we have a repo, an Editor, and participants.
08:55:29 [nigel]
Nigel: Goal: Get to good enough for Rec Track, add to TTWG Charter 1st half 2019
08:55:35 [nigel]
s/.. AD/Nigel: AD
08:55:59 [nigel]
marisa: Timeline for TTML2?
08:56:19 [nigel]
Nigel: TTML2 is in Proposed Rec status, the TTWG is targeting Rec publication on 13th November.
08:56:48 [nigel]
.. The AC poll is open until 1st November. Please vote if you haven't already!
08:56:58 [nigel]
Topic: Requirements
08:57:10 [nigel]
Nigel: Goal: To create an open standard exchange format to support audio description all the way from scripting to mixing.
08:58:06 [nigel]
ericc: You should look at what 3PlayMedia has.
08:58:12 [nigel]
Nigel: Thanks I will
08:58:23 [nigel]
.. Are they delivering accessible text versions of AD?
08:58:39 [nigel]
ericc: Yes, both AD and extended, both pre-recorded and synthetic text, and they have
08:58:49 [nigel]
.. a javascript based plug-in that works in modern browsers.
08:58:55 [nigel]
Nigel: That sounds great, I didn't know about that, thank you.
08:58:57 [atai]
atai has joined #ad
08:59:06 [nigel]
ericc: I haven't played with it much but it seems to work quite well.
08:59:35 [nigel]
marisa: When you talk about an accessible text what makes it accessible?
08:59:52 [nigel]
Nigel: It's delivered as text and the player can present it in an aria live region so that
08:59:57 [nigel]
.. accessibility tools can pick it up.
09:00:02 [nigel]
marisa: And TTML makes that happen?
09:00:11 [nigel]
Nigel: It needs the player to make it happen.
09:00:45 [nigel]
Present+ Mark_Watson
09:01:17 [nigel]
Nigel: Existing Requirements - I published a wiki page of requirements a while back.
09:01:34 [nigel]
-> https://github.com/w3c/ttml2/wiki/Audio-Description- Requirements AD requirements
09:01:49 [nigel]
Nigel: Those requirements got some feedback which led to changes.
09:02:05 [nigel]
.. In particular to relate them to the W3C MAUR requirements, which they align with.
09:02:27 [marisa]
https://github.com/w3c/ttml2/wiki/Audio-Description-Requirements
09:02:53 [nigel]
.. Those requirements describe the process that the document needs to support
09:03:28 [nigel]
.. but not the specifics of what the document itself needs to support.
09:05:43 [nigel]
.. I've done a first pass review, the main body of the spec work would be to validate that
09:05:55 [nigel]
.. those TTML2 feature designators are the correct set.
09:06:31 [markw]
markw has joined #ad
09:06:54 [ericc]
https://www.w3.org/community/audio-description/files/2018/10/AD-CG-F2F-2018-10-25.pdf
09:07:43 [nigel]
Nigel: In looking at those requirements I thought there were some constraints to consider.
09:07:53 [nigel]
.. Two questions from me:
09:08:02 [nigel]
.. 1. Do we ever need to be able to have more than one “description” active at the same time?
09:08:44 [nigel]
Matt: I can't see a reason for needing this - it would have to be a variation of the primary language.
09:08:53 [nigel]
.. Multiple localised versions might be needed.
09:09:02 [nigel]
.. I imagine that would be a single track per file.
09:09:07 [nigel]
Matt: Yes, interesting thought.
09:09:19 [nigel]
marisa: A variation on a use case, if you have a deaf-blind user who is following the
09:09:34 [nigel]
.. captions they also need the information from the description and the captions.
09:09:44 [nigel]
markw: They would have both description and captions available at the same time.
09:11:11 [nigel]
Nigel: Assumptions on my part:
09:11:16 [nigel]
.. Separate AD and captions files
09:11:29 [nigel]
.. No AD over dialogue so not a significant issue of overlap
09:11:49 [nigel]
marisa: If viewer needs to pause AD to read it on a braille display...
09:11:56 [nigel]
Nigel: My assumption: that would also pause media.
09:12:01 [nigel]
ericc: [nods]
09:12:11 [nigel]
marisa: That's the trickiest use case I can think of
09:12:15 [nigel]
Nigel: Me too
09:12:30 [nigel]
atai: I'm not sure if immersive environments are in scope.
09:12:47 [nigel]
.. A European project that IRT is involved with is exploring requirements for AD in 360º videos.
09:12:57 [nigel]
.. I'm not sure if they implemented it, but one idea is to have some parts of the AD only
09:13:10 [nigel]
.. activated if the user looks in a certain direction, so if this is happening in one document
09:13:21 [nigel]
.. then there would be certain AD parts with the same timing but maybe not active at
09:13:24 [nigel]
.. the same time.
09:13:32 [nigel]
marisa: Great use case!
09:13:50 [nigel]
.. Now a deaf blind user in a 360º is now the trickiest use case in the world I can think of!
09:14:04 [nigel]
ericc: That means in addition to a time range, in the case of a 360º video you may also
09:14:17 [nigel]
.. want to have an additional selector for the viewport in which it is active.
09:14:30 [nigel]
markw: Or the location of the object it is associated with.
09:14:40 [nigel]
atai: This is very similar to the subtitle use case we showed before where you stick
09:14:51 [nigel]
.. subtitles to a location. You need the same location information for AD.
09:15:08 [nigel]
markw: The user could have selections about the width of the viewport they want.
09:15:25 [nigel]
Nigel: That's a great use case - can I suggest it's a v2 thing based on the solution for
09:15:30 [nigel]
.. subtitles, which we also don't know yet?
09:15:53 [nigel]
atai: I agree the solution for subtitles should apply here. That makes sense, but it would be
09:16:04 [nigel]
.. good to discuss it and understand the dependencies.
09:16:51 [nigel]
atai: I will check with the people working on this. I don't know any technical group working
09:17:03 [nigel]
.. on audio description so it would be a good forum for working on requirements.
09:17:12 [nigel]
.. If they want to contribute something they can post it on the CG reflector.
09:17:14 [nigel]
Nigel: Good plan.
09:18:47 [nigel]
.. Summarising, I don't think I've heard any requirement for multiple descriptions to be
09:18:54 [nigel]
.. active at the same time, within a single language.
09:19:24 [nigel]
.. My next constraint question is:
09:19:32 [nigel]
.. Do we need to set media time ranges (clipBegin and clipEnd) on embedded audio?
09:19:46 [nigel]
.. TTML2 allows audio to be embedded, but in our implementation work we hit a snag.
09:23:17 [nigel]
.. applying media fragment URIs to a data URL is tricky.
09:23:33 [nigel]
ericc: Embedding audio as text is a terrible idea.
09:23:46 [nigel]
markw: Any reason other than the amount of data?
09:24:36 [nigel]
ericc: You have to keep the text and the decoded audio in memory at the same time,
09:24:40 [nigel]
.. which is additional overhead.
09:25:08 [nigel]
ericc: Technically it should be straightforward to seek to a point.
09:25:31 [nigel]
marisa: I don't want to implement it!
09:25:37 [nigel]
ericc: It's terrible.
09:27:14 [nigel]
atai: Is it then debatable to leave out this feature of embedded audio?
09:27:32 [nigel]
Nigel: I think so, yes, the result would be that distribution of recorded audio would have
09:27:33 [marisa]
marisa has joined #ad
09:27:49 [nigel]
.. to be additional files alongside the TTML2 file. That has an asset management impact,
09:27:57 [nigel]
.. but it also seems like good practice.
09:28:19 [nigel]
ericc: High level question: I talked with Ken Harenstein who does YouTube captions, last week,
09:28:33 [nigel]
.. and he told me about 3PlayMedia. He said that from their research and from talking to
09:28:47 [nigel]
.. users of audio descriptions and from talking to 3PlayMedia, it was his understanding that
09:28:59 [nigel]
.. many users of audio descriptions prefer speech synthesis to pre-recorded because
09:29:13 [nigel]
.. partly it allows them to set the speed like they're used to doing with screen readers
09:29:29 [nigel]
.. and it made extended audio descriptions less disruptive because it reduces the likelihood
09:29:42 [nigel]
.. of interrupting playback of the main resource. I wonder if you have heard that too and if
09:30:01 [nigel]
.. it is true it seems that there should be information in a spec helping people who make
09:30:06 [nigel]
.. these make the right kind.
09:31:19 [nigel]
Nigel: TTML2 supports text to speech, and also players can switch off the audio
09:31:32 [nigel]
.. and expose the text to screen readers instead to allow the user's screen reader to take
09:31:33 [nigel]
.. over.
09:31:51 [nigel]
marisa: I've heard that most screen readers speed up the speech.
09:32:08 [nigel]
markw: I've heard it works better speeding up synthesised speech
09:32:20 [nigel]
marisa: Of course if there's no language support for text to speech then you may still
09:32:32 [nigel]
.. need pre-recorded audio.
09:34:18 [nigel]
atai: You may need to know how long the text to speech will take to author the rate correctly.
09:34:39 [nigel]
Nigel: There's a whole other world of pain in terms of distributability of web voices for text to speech.
09:34:56 [nigel]
ericc: I think the requirement is that the player pauses to allow for completion of the
09:35:05 [nigel]
.. audio description, so it doesn't matter how long it takes.
09:35:30 [nigel]
marisa: What if you're switching language of AD and some are more verbose than others?
09:35:43 [nigel]
ericc: Yes, as long as the description accurately identifies the section of the media file
09:35:54 [nigel]
.. that it describes then it is easy enough for the player to take care of, or at least it is the
09:35:58 [nigel]
.. player's responsibility.
09:36:10 [nigel]
markw: The player could do other things like tweaking the playback speed to fit.
09:36:29 [nigel]
ericc: The Web Speech API doesn't allow access to predicting the duration of the speech.
09:36:46 [nigel]
atai: Is player behaviour in scope for this document?
09:36:49 [nigel]
ericc: Absolutely.
09:37:01 [nigel]
.. It seems to me that it is because if you don't describe the behaviour of the player you
09:37:12 [nigel]
.. are going to get different incompatible or non-interoperable implementations and that
09:37:14 [nigel]
.. is an anti-goal.
09:37:28 [nigel]
markw: You want to describe the space of possible player behaviours, we just need to
09:37:31 [nigel]
.. provide the information.
09:37:47 [nigel]
ericc: Yes, give guidelines to help implementers do the right thing, and people who create the descriptions.
09:39:32 [nigel]
Nigel: I agree, this is somewhat informative relative to the document format, but for example
09:39:47 [nigel]
.. our UX people suggested that users would want to direct AD text to a screen reader
09:39:59 [nigel]
.. and switch off audio presentation sometimes, or at least be able to select that.
09:40:17 [nigel]
marisa: Maybe have both audio and braille display to check spellings or do some other text-related processing.
09:40:19 [nigel]
Nigel: Yes
09:41:27 [nigel]
Nigel: In terms of user preference for synthesised or pre-recorded speech, one data point
09:41:44 [nigel]
.. I learned recently is that the intelligibility of synthesised speech degrades more quickly
09:41:59 [nigel]
.. in the presence of ambient sounds than human speech. The reasons are not clear.
09:42:12 [nigel]
markw: Suggests that some users would want to receive the AD in a separate earpiece
09:42:19 [nigel]
.. from other audience members watching the same programme.
09:42:48 [nigel]
Matt: I think this is like dubbing vs subtitling, there may be cultural reasons for preferences.
09:43:02 [nigel]
.. Our experience is it is harder to automate variable reading rate descriptions, and we find
09:43:18 [nigel]
.. that invaluable to squeeze a description into a short period or let it "breathe".
09:43:24 [nigel]
.. It's probably down to historical experience.
09:43:50 [nigel]
Present+ Francois_Beaufort
09:44:04 [nigel]
Francois: I work at Google on the developer relations team.
09:44:36 [fbeaufort]
fbeaufort has joined #ad
09:44:41 [nigel]
nigel has changed the topic to: Channel for the Audio Description Community group. Slides: https://www.w3.org/community/audio-description/files/2018/10/AD-CG-F2F-2018-10-25.pdf
09:44:55 [nigel]
nigel has changed the topic to: Channel for the Audio Description Community group. Slides: https://www.w3.org/community/audio-description/files/2018/10/AD-CG-F2F-2018-10-25.pdf Webex: https://ebu.webex.com/ebu/e.php?MTID=m8453309dd2136cedb50a126ec3aeff98
09:45:17 [nigel]
s/Francois/fbeaufort
09:45:30 [nigel]
Nigel: Any other constraints or requirements?
09:45:41 [nigel]
group: [silence]
09:45:56 [nigel]
Topic: TTML2 in more detail
09:47:11 [notabene]
notabene has joined #ad
09:50:44 [nigel]
Nigel: [slide on Audio Model]
09:51:04 [nigel]
.. I just added this to try to explain because I've found it can be tricky to get across to developers
09:51:19 [nigel]
.. that there is an analogy with HTML/CSS and the audio model in TTML.
09:53:16 [nigel]
markw: Players may or may not do this based on user preference, if for example someone
09:53:30 [nigel]
.. is listening on a headset and there's main programme audio in the room the mixing
09:53:34 [nigel]
.. preferences might change.
09:53:37 [nigel]
.. [slide on the Web Audio Graph]
09:53:51 [nigel]
.. This allows the audio mixing to happen with all the options that are needed in general
09:54:02 [nigel]
.. in TTML2 - it may be that we only exercise a part of that solution space.
09:54:33 [nigel]
Topic: Proposed Solution
09:55:48 [nigel]
Nigel: The solution that I'm proposing is a profile of TTML2
09:55:56 [nigel]
.. [slide for Profile of TTML2]
09:56:11 [nigel]
ericc: Also add that a UI should be provided for controlling the speed of audio descriptions
09:56:18 [nigel]
nigel: Yes
09:56:24 [nigel]
s/n/N
09:56:35 [nigel]
Nigel: The other things on this slide we already discussed.
09:57:14 [nigel]
Nigel: Is anyone thinking this is a great problem to solve but it should look completely different?
09:57:46 [nigel]
ericc: Is it a goal to define a guide for how this should work in a web browser?
09:59:26 [nigel]
Nigel: The TTML2 features are done in terms of Web Audio, Web Speech etc. so yes.
09:59:42 [nigel]
.. The mixing might happen server side but the client side mixing options allow for a better
09:59:49 [nigel]
.. range of accessible experiences.
10:00:21 [nigel]
ericc: It seems to me that a really detailed guide to implementation would be the most useful thing.
10:00:47 [nigel]
.. An explicit goal should be to help producers to create content in the right way, but also
10:01:05 [nigel]
.. to help people that want to deliver that to know how to make it available to the people that need it.
10:01:16 [nigel]
.. Not distribution, the playback experience.
10:01:27 [nigel]
.. Nicely constructed audio descriptions are not useful unless the people that need them are
10:01:29 [nigel]
.. able to consume them.
10:01:35 [nigel]
Nigel: [nods]
10:01:47 [nigel]
atai: It might be interesting to identify what is missing to get a good implementation in a browser
10:01:51 [nigel]
.. environment.
10:02:03 [nigel]
.. It might be interesting to hear how much browser communities are interested in that
10:02:15 [nigel]
.. case. A possible way to do this would be to implement a javascript polyfill or something
10:02:22 [nigel]
.. I'm not sure how much interest there is in native support.
10:02:37 [nigel]
ericc: Both are extremely useful. I don't know anything about 3PlayMedia but they have
10:02:50 [nigel]
.. a javascript based player that uses text to speech API so we know that it is possible.
10:03:02 [nigel]
.. There's is a commercial solution. We should have a description of ...
10:03:14 [nigel]
.. and as a data point I was at a conference last week about media in the web and this was
10:03:24 [nigel]
.. one of the breakouts, audio descriptions and extended audio descriptions.
10:03:39 [nigel]
.. It was well attended and people in the room were very interested in coming up with a
10:03:47 [nigel]
.. solution that browsers could implement natively.
10:03:53 [nigel]
Nigel: I'd love to be in touch with those people.
10:04:14 [nigel]
Topic: Implementation Experience
10:06:13 [nigel]
Nigel: BBC implemented a prototype to support TTML2 Rec track work
10:06:17 [nigel]
-> https://bbc.github.io/Adhere/ BBC implementation
10:12:28 [nigel]
Nigel: The point here is that it is possible to do this with current browser technologies,
10:12:47 [nigel]
.. even if there are some minor issues that I should raise as issues, like on Web Speech.
10:13:16 [nigel]
.. Question: Any other implementation work, or people who would like to do that at this time?
10:13:44 [nigel]
marisa: I would say no, we don't have the bandwidth but I'm keeping my eye on this for
10:13:54 [nigel]
.. the long term. The use cases come up all the time from the APA group. I think it is
10:14:03 [nigel]
.. on the horizon, but I can't commit to anything on the same timeline as this spec.
10:14:19 [nigel]
atai: Does BBC plan to publish this software as a reference implementation?
10:14:35 [nigel]
Nigel: I would say first we should publish as open source, and then allow for some
10:14:50 [nigel]
.. scrutiny, and if people agree it's at that level then great. I don't think it is now.
10:14:55 [nigel]
.. It would need more work.
10:15:18 [nigel]
atai: The question is if the BBC could be motivated to provide it as a reference
10:15:26 [nigel]
.. implementation. It would help if you have a complete reference implementation.
10:15:35 [nigel]
Nigel: I would like to, but I don't think the code is good enough yet.
10:17:22 [nigel]
.. I'm interested in other implementations too, for example it is possible that some
10:18:30 [nigel]
.. participants in AD CG might make authoring tools.
10:18:37 [nigel]
ericc: You should talk to 3Play also.
10:18:49 [nigel]
Nigel: Yes, I will. It'd be great if they would join us here.
10:19:07 [nigel]
Topic: Roles, Tools, Timelines, Next Steps
10:19:32 [nigel]
Nigel: In terms of tools, we have a GitHub repo w3c/adpt
10:20:42 [nigel]
.. We have the reflector, and EBU has kindly offered to facilitate web meetings with their WebEx.
10:22:47 [nigel]
.. [Next steps slide]
10:24:20 [nigel]
atai: Regarding the next steps, to move over to WG and Rec track, does it necessarily have
10:24:27 [nigel]
.. to end up in the TTWG? Could it be another group?
10:24:39 [nigel]
.. Could it be somewhere else?
10:24:48 [nigel]
.. To make sure the right set of people are involved.
10:25:33 [nigel]
Nigel: I'm not dogmatic about this - it seems like the home of TTML is a good place for
10:25:46 [nigel]
.. profiles of TTML, but if there's a better chance of getting to Rec doing it somewhere else
10:25:52 [nigel]
.. then I don't mind where it happens.
10:26:19 [nigel]
atai: One other idea: when the TTML2 feature set is there it may be useful to have a
10:26:30 [nigel]
.. gap listing relative to IMSC 1.1 so that if people want to reuse implementations and
10:26:40 [nigel]
.. start from IMSC 1.1 rather than TTML2 then they can see what they already have.
10:26:51 [nigel]
ericc: Or which features they prefer not to use.
10:26:56 [nigel]
Nigel: Because they had implementation difficulty?
10:27:10 [nigel]
ericc: Yes, for example someone targeting IMSC 1.1 support, if you list the features that
10:28:06 [nigel]
.. are only supported in one and not the other, it could inform.
10:28:20 [nigel]
Nigel: Of course the significant features in IMSC are about visual presentation and here
10:28:40 [nigel]
.. we are interested in audio features, so the common core of timing is all that's really left.
10:30:09 [nigel]
Topic: Discussion and close
10:30:18 [nigel]
Nigel: We've had good discussion all the way through, so thank you everyone.
10:30:46 [nigel]
ericc: Defining this using those TTML2 features is interesting and its good.
10:31:08 [nigel]
.. It sets a fairly high bar to implement.
10:31:11 [atai]
atai has left #ad
10:31:16 [nigel]
Nigel: It took a couple of weeks to implement.
10:31:34 [nigel]
ericc: It makes me wonder if it would be possible to have something that is more like a
10:31:52 [nigel]
.. minor variation in a caption format.
10:31:56 [nigel]
Nigel: I think that's what this is.
10:32:04 [nigel]
ericc: Except for the ability to embed audio.
10:32:52 [nigel]
Nigel: That maybe took about half a day to implement. We could remove it from scope.
10:33:12 [nigel]
atai: It would be good to know what problems there are bringing this to a browser environment.
10:33:38 [nigel]
ericc: That's true. At the most basic it seems that what we have is some text and a range
10:33:51 [nigel]
.. of time that it applies to in another file.
10:35:43 [nigel]
Nigel: I'm thinking of high production values where detailed audio mixing is needed.
10:35:51 [nigel]
ericc: Is that something we need for the web?
10:36:13 [nigel]
Nigel: I am aiming for a single open standard file format that content producers can use
10:36:23 [nigel]
.. all the way through from content creation to broadcast and web use.
10:36:28 [nigel]
Matt: I would agree.
10:36:47 [nigel]
markw: Thinking about our chain, we create premixed versions and they seem quite high
10:37:02 [nigel]
.. quality, so this might be worth considering.
10:37:19 [nigel]
atai: Thinking about the history of TTML, it started out as an authoring format and then
10:37:32 [nigel]
.. began to be used for distribution and playback, which lead to IMSC. I understand the
10:37:45 [nigel]
.. purpose for one file for the whole chain, that's perfect, it's ideal, we should just avoid the
10:37:47 [nigel]
.. pitfalls.
10:38:05 [nigel]
ericc: If the goal is to have native implementation in a browser it may be worth looking
10:38:13 [nigel]
.. at the complexity with that goal in mind.
10:38:34 [nigel]
.. If it is not a goal then that's fine, but if it is then keep that goal in mind.
10:39:43 [nigel]
Nigel: I am not sure. It an be done with a polyfill but would browser makers like to supprot
10:42:09 [nigel]
.. the primitives to allow that or to implement it natively?
10:42:16 [nigel]
atai: The playback experience would be better natively.
10:42:36 [nigel]
fbeaufort: If the playback was the same would you still want native implementation?
10:42:54 [nigel]
Nigel: It would be great to avoid sending polyfill js to every page in that case, and it would
10:43:06 [nigel]
.. make adoption easier if the page author just had to include a track in the video element
10:43:10 [nigel]
.. and then it would play.
10:43:48 [nigel]
ericc: Your polyfill is about 50KB of unminified uncompressed js so it's not very big.
10:43:58 [nigel]
Nigel: Thank you everyone! [adjourns meeting]
10:44:16 [nigel]
rrsagent, make minutes
10:44:16 [RRSAgent]
I have made the request to generate https://www.w3.org/2018/10/25-ad-minutes.html nigel
11:55:28 [nigel]
nigel has joined #ad
11:57:20 [nigel]
Meeting: Audio Description Community Group
11:58:16 [nigel]
s/.. Marisa/marisa: Marisa
11:59:27 [nigel]
s|https://github.com/w3c/ttml2/wiki/Audio-Description- Requirements|https://github.com/w3c/ttml2/wiki/Audio-Description-Requirements
12:02:00 [ericc]
ericc has joined #ad
12:03:11 [Zakim]
Zakim has left #ad
12:09:36 [ericc]
ericc has joined #ad
12:10:05 [nigel]
rrsagent, make minutes
12:10:05 [RRSAgent]
I have made the request to generate https://www.w3.org/2018/10/25-ad-minutes.html nigel
12:10:15 [nigel]
nigel has changed the topic to: Channel for the Audio Description Community group. Slides: https://www.w3.org/community/audio-description/files/2018/10/AD-CG-F2F-2018-10-25.pdf
12:13:43 [nigel]
Log: https://www.w3.org/2018/10/25-ad-irc
12:14:27 [nigel]
s/Marise/Marisa/g
12:14:48 [nigel]
rrsagent, make minutes
12:14:48 [RRSAgent]
I have made the request to generate https://www.w3.org/2018/10/25-ad-minutes.html nigel
12:16:24 [nigel]
scribeOptions: -final -noEmbedDiagnostics
12:16:25 [nigel]
rrsagent, make logs public
12:16:39 [nigel]
rrsagent, make minutes
12:16:39 [RRSAgent]
I have made the request to generate https://www.w3.org/2018/10/25-ad-minutes.html nigel
12:18:39 [nigel]
s/It an be done/It can be done
12:18:50 [nigel]
s/supprot/support
12:18:53 [nigel]
rrsagent, make minutes
12:18:53 [RRSAgent]
I have made the request to generate https://www.w3.org/2018/10/25-ad-minutes.html nigel
12:44:08 [ericc]
ericc has joined #ad
14:11:30 [ericc]
ericc has joined #ad
14:11:40 [nigel]
nigel has joined #ad
15:07:39 [notabene]
notabene has left #ad
16:25:11 [ericc]
ericc has joined #ad