Just to complement, I understand from the minutes that follow-up work of this workshop will happen within the HTML Accessibility Task Force Work http://www.w3.org/WAI/PF/html-task-force. There is a public archived mailing list people can subscribe to: http://lists.w3.org/Archives/Public/public-html-a11y/

I apologize for the misspellings – I took them from the transcript and didn’t know better. Also I apologize for mis-representing the topic of your presentation – will correct that, too.

Just to clarify a few things :
- my name is not Champain, but Champin
- my video presentation was about ACAV, a project that we (LIRIS) are just starting with Eurecom (frenche graduate school) and Dailymotion. It is about media accessibility using automatic and manual annotation. The speaker diarization is therefore just of part of it, and is not done by us, but by Eurecom.

No offence taken for these mistakes, of cours, but I didn’t want to give the impression that my presentation was denying the importance of our other partners

I’m very interested in how the baseline codec discussion plays out. Hardware support will be quick to follow any industry wide adoption. Currently, video encoding is the most time intensive process in my software, StatEasy. I’d love to have a camera record OGG video natively. At the very least, a hardware accelerator would be helpful.

I’m very much in favor of a JavaScript/CSS method to customize display of any captions.

If FOMS wasn’t so far away from Pittsburgh, PA I’d be sure to attend! Looking forward to your writeup of that event in 2010!

Mike Ressler