IRC log of media on 2012-05-17

Timestamps are in UTC.

21:38:33 [RRSAgent]
RRSAgent has joined #media
21:38:33 [RRSAgent]
logging to http://www.w3.org/2012/05/17-media-irc
21:38:35 [trackbot]
RRSAgent, make logs world
21:38:35 [Zakim]
Zakim has joined #media
21:38:37 [trackbot]
Zakim, this will be 2119
21:38:37 [Zakim]
I do not see a conference matching that name scheduled within the next hour, trackbot
21:38:38 [trackbot]
Meeting: HTML Accessibility Task Force Teleconference
21:38:38 [trackbot]
Date: 17 May 2012
21:39:08 [JF]
zakim, room for 10
21:39:08 [Zakim]
I don't understand 'room for 10', JF
21:39:31 [silvia]
zakim, code?
21:39:31 [Zakim]
sorry, silvia, I don't know what conference this is
21:39:49 [JF]
\
21:41:26 [JF]
hmmm... her number has changed?
21:46:04 [Judy]
Judy has joined #media
21:46:09 [JF]
waves hi
21:46:42 [Judy]
zakim, room for 6?
21:46:43 [Zakim]
ok, Judy; conference Team_(media)21:46Z scheduled with code 2119 (A11Y) for 60 minutes until 2246Z
21:47:54 [Judy]
chair: John_Foliot
21:48:17 [Judy]
meeting: Media SubTeam of HTML5 A11Y Task Force
21:48:19 [JF]
Meeting: HTML-A11Y teleconference
21:48:21 [JF]
Chair:John_Foliot
21:48:22 [JF]
Scribe:Janina_Sajka
21:48:24 [JF]
agenda: this
21:48:25 [JF]
agenda+Time Tracks, Transcripts, and Issue-194
21:48:27 [JF]
agenda+Other Business?
21:48:28 [JF]
agenda+ be done
21:49:14 [Judy]
hi Silvia, sorry I cannot join you directly at this time, but thanks for continuing to work on this issue
21:49:54 [silvia]
hi Judy, no problem - thanks for getting us started
21:49:59 [silvia]
zakim, code?
21:49:59 [Zakim]
the conference code is 2119 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), silvia
21:50:45 [Zakim]
Team_(media)21:46Z has now started
21:50:50 [Zakim]
+silvia
21:50:52 [Zakim]
+JF
21:55:56 [JF]
<video transcript="jf">
21:55:58 [JF]
</video>
21:55:59 [JF]
<transcript class="off-screen">
21:56:01 [JF]
<a href="transcript.pdf">transcript</a>
21:56:02 [JF]
</transcript>
21:59:06 [JF]
<video transcript="jf">
21:59:08 [JF]
</video>
21:59:09 [JF]
<div class="off-screen">
21:59:11 [JF]
<a href="transcript.pdf" id="jf">transcript</a>
21:59:11 [silvia]
… I would instead do this:
21:59:12 [JF]
</div>
21:59:30 [silvia]
<video transcript="sp">
21:59:34 [silvia]
</video>
21:59:53 [silvia]
<trasncript id="sp" src="transcript.pdf"></transcript>
22:00:32 [silvia]
multiple links:
22:00:40 [silvia]
<video transcript="sp1 sp2">
22:00:42 [silvia]
</video>
22:01:03 [silvia]
<transcript id="sp1" src="trans1.pdf" lang="en"></transcript>
22:01:20 [silvia]
<transcript id="sp2" src="trans2.doc" lang="de"></transcript>
22:03:21 [Zakim]
+??P2
22:03:24 [janina]
janina has joined #media
22:04:26 [silvia]
multiple links:
22:04:26 [silvia]
<video transcript="sp1 sp2">
22:04:26 [silvia]
</video>
22:04:26 [silvia]
<transcript id="sp1" src="trans1.pdf" lang="en"></transcript>
22:04:26 [silvia]
<transcript id="sp2" src="trans2.doc" lang="de"></transcript>
22:04:46 [silvia]
Question we are discussing: why we need the transcript element
22:05:05 [silvia]
My reply: I'd like a consistent way of authoring transcripts for all use cases
22:05:12 [silvia]
* URL off-page
22:05:16 [silvia]
* text on-page
22:05:22 [silvia]
* interactive transcript with video
22:05:32 [silvia]
* transcript-only (without video)
22:05:44 [JF]
in this case:
22:05:47 [JF]
<video transcript="jf">
22:05:49 [JF]
</video>
22:05:50 [JF]
<transcript class="off-screen">
22:05:52 [JF]
<a href="transcript.html" id="jf">transcript</a>
22:05:54 [JF]
</transcript>
22:06:10 [JF]
scratch that
22:06:37 [silvia]
Since anchors can get focus, we'll try to avoid using anchors inside <transcript>
22:06:47 [JF]
<video transcript="sp1">
22:06:47 [silvia]
so put the url directly on the <transcript> element
22:06:49 [JF]
</video>
22:06:50 [JF]
<transcript id="sp1" src="trans1.pdf" lang="en">
22:06:52 [JF]
</transcript>
22:08:20 [silvia]
this instance would be rendered like a <a>
22:09:00 [JF]
so: <transcript id="sp1" src="trans1.pdf" lang="en"></transcript>acts like a link
22:09:19 [JF]
it would render a "control" (button, dropdown, equiv)
22:10:44 [silvia]
<video transcript="on-page">
22:10:47 [silvia]
</video>
22:11:01 [silvia]
<transcript lang="en" id="on-page">
22:11:07 [silvia]
This is the transcript for the above element.
22:11:12 [silvia]
</transcript>
22:11:41 [JF]
how would that be populated dynamically?
22:14:00 [silvia]
JF explains a use case where the on-page transcript is rendered from an external html page
22:14:29 [silvia]
silvia: this can either be linked as above
22:14:32 [JF]
so if dynamically populated, would be done via scripting
22:14:40 [silvia]
or if you really need to render it on page, you need to use JS
22:15:01 [silvia]
set the innerHTML of the <transcript> element to it
22:15:13 [JF]
so we;ve coverd th elink scenario, and the static on screen scenario, what about interactive?
22:16:04 [JF]
s/we;ve coverd th elink/we've covered the link/
22:26:13 [silvia]
sp: interactive transcripts will be the killer app for video and will cause authors to want to create more captions
22:32:27 [JF]
Q+ Janina
22:32:40 [JF]
Q+
22:33:22 [JF]
ack janina
22:36:55 [JF]
<transcript id="sp1" src="trans1.vtt" lang="en"></transcript>
22:37:11 [silvia]
rather:
22:37:27 [silvia]
<transcript id="sp1">
22:37:43 [silvia]
<track src="trans1.vtt" srlang="en">
22:37:46 [silvia]
</transcript>
22:38:48 [JF]
ack jf
22:40:19 [silvia]
that would be rendered on page as an interactive transcript
22:46:10 [JF]
after looking at this, I think we have some solutions that work for accessiblity concerns
22:48:25 [JF]
discoverability: the @transcript attribute will trigger some form of control - a button or menu dialog or (to be determined by device/platform considerations)
22:48:54 [JF]
2) option to consume or not consume: covered by discoverabiliyt/control above
22:49:06 [JF]
3) supports semantically rich content
22:50:00 [Zakim]
-silvia
22:50:09 [silvia]
I dropped out
22:50:26 [JF]
can you try calling bck in?
22:50:29 [silvia]
my phone ran out of battery :-(
22:50:38 [JF]
oh noe
22:50:58 [silvia]
it's been playing up and not showing the correct battery status - it may not be fully dead
22:51:08 [JF]
ok, well we were wrapping up
22:51:16 [JF]
next steps? update wiki?
22:51:27 [JF]
I can make some contributes if you want
22:51:51 [silvia]
I can't dial back in, sorry
22:51:59 [JF]
OK
22:52:08 [silvia]
I will want to completely rework that CP
22:52:24 [JF]
OK, let me know how I can asssist
22:52:25 [silvia]
we have a lot more information now than when I wrote it
22:52:34 [JF]
agreed
22:52:39 [silvia]
were you going to add to it?
22:52:45 [JF]
I can
22:53:05 [silvia]
can you write a paragraph on why you think the approach is workable - as you started above?
22:53:10 [JF]
I can add a section on accessiblity considerations and how/why this solves those issues
22:53:32 [silvia]
I'd like to add that after the tech descriptions so we have that viewpoint captured
22:53:39 [janina]
I'll let the H5 CC's know we're agreed in principle. We need only to get it written up and socialized for objections, etc.
22:54:01 [silvia]
"only"!
22:54:07 [janina]
We expect to have TF support by next Friday and a single CP for the WG.
22:54:08 [JF]
Agreed. can you re-share the final wiki url?
22:54:11 [silvia]
it's the implementers I'm concerned about now...
22:54:27 [janina]
Yes, that's the socializing task for next week.
22:54:28 [silvia]
sure, let's create a new one
22:54:58 [JF]
OK, well if you start the page, I will go in tonight and add to it
22:55:12 [JF]
leave me a place holder <grin>
22:55:50 [silvia]
will do, no problem
22:55:53 [JF]
OK... are we done for now?
22:55:54 [silvia]
I'll email it to you
22:55:59 [JF]
thank you
22:56:01 [janina]
I'll push minutes
22:56:03 [silvia]
I think so … Janina?
22:56:10 [janina]
Excellent stuff, Silvia!
22:56:22 [JF]
let's call it a day. thank you silvia and janina
22:56:25 [silvia]
no worries - we need to get this right :-)
22:56:46 [silvia]
awesome, thanks everyone
22:56:49 [silvia]
and sorry for dropping out
22:56:56 [JF]
no worries
22:57:08 [silvia]
I need to buy a new phone
22:57:25 [silvia]
or we use Google hangout next time!
22:59:21 [silvia]
rrsagent, make minutes
22:59:21 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/05/17-media-minutes.html silvia
23:00:44 [Zakim]
-JF
23:00:44 [JF]
lost the call
23:00:59 [janina]
OK. We're done anyway!
23:01:06 [JF]
trying your cell
23:01:22 [janina]
Cell broke. My main 202.494 number is good
23:01:34 [JF]
7040?
23:01:36 [janina]
I can push, if you like
23:01:51 [janina]
Yes, Silvia, I will do minutes push
23:01:59 [janina]
rrsagent, make log public
23:02:09 [janina]
rrsagent, make minutes
23:02:09 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/05/17-media-minutes.html janina
23:02:33 [janina]
That's funny. That's still my number. Let me call you
23:02:40 [janina]
Are you on your cell?
23:02:44 [JF]
yes
23:02:52 [janina]
Give me about 60 seconds
23:03:32 [Zakim]
-??P2
23:03:33 [Zakim]
Team_(media)21:46Z has ended
23:03:33 [Zakim]
Attendees were silvia, JF