22:10:21 RRSAgent has joined #htmla
22:10:21 logging to http://www.w3.org/2010/12/01-htmla-irc
22:10:34 zakim, room for 10?
22:10:35 ok, plh; conference Team_(htmla)22:10Z scheduled with code 26631 (CONF1) for 60 minutes until 2310Z
22:10:45 zakim, call janina
22:10:45 ok, janina; the call is being made
22:10:46 Team_(htmla)22:10Z has now started
22:10:47 +Janina
22:10:49 gfreed has joined #htmla
22:10:54 kenny_j has joined #htmla
22:10:59 zakim, passcode?
22:10:59 the conference code is 26631 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), plh
22:11:12 Sean has joined #htmla
22:11:23 +Geoff_Freed
22:11:28 zakim, passcode?
22:11:28 the conference code is 26631 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), plh
22:11:57 +[IPcaller]
22:12:42 zakim, +ip is Kenny_Johar
22:12:42 sorry, janina, I do not recognize a party named '+ip'
22:13:04 zakim, +[IP is Kenny_Johar
22:13:04 sorry, janina, I do not recognize a party named '+[IP'
22:13:20 Meeting: HTML-A11Y telecon
22:13:21 Chair: Janina_Sajka
22:13:21 agenda: this
22:13:21 agenda+ Identify Scribe
22:13:21 agenda+ Actions Review http://www.w3.org/WAI/PF/HTML/track/actions/open
22:13:21 agenda+ Candidate Formats Report
22:13:23 agenda+ Strategy for Synchronizing binary alternative media
22:13:25 agenda+ Other Business?
22:13:27 agenda+ Meeting Scheduling Through January 5
22:13:28 +Sean_Hayes
22:13:29 agenda+ be done
22:13:31
22:13:49 zakim, who's here?
22:13:49 On the phone I see Janina, Geoff_Freed, [IPcaller], Sean_Hayes
22:13:50 On IRC I see Sean, kenny_j, gfreed, RRSAgent, janina, Zakim, plh
22:13:52 silvia has joined #htmla
22:14:09 zakim, passcode?
22:14:09 the conference code is 26631 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), plh
22:14:14 zakim, [IPcaller] is Kenny_Johar
22:14:14 +Kenny_Johar; got it
22:14:49 Hi, Silvia, yes, please join #htmla
22:15:43 +Plh
22:16:51 + +28012aaaa
22:16:58 zakim, aaaa is me
22:16:58 +silvia; got it
22:19:13 zakim, mute me
22:19:13 silvia should now be muted
22:20:29 scribe: silvia
22:20:33 topic: Actions Review http://www.w3.org/WAI/PF/HTML/track/actions/open
22:21:17 action-22?
22:21:32 zakim, action-68
22:21:32 I don't understand 'action-68', silvia
22:21:54 close action-68
22:22:18 gah, we are missing trackbot
22:23:05 action-88
22:23:09 action-89
22:23:18 Topic: Fallbacks http://lists.w3.org/Archives/Public/public-html-a11y/2010Nov/0246.html
22:23:38 sorry, I'm wrong
22:23:51 topic: Candidate Formats Report
22:24:07 zakim, unmute me
22:24:07 silvia should no longer be muted
22:24:34 trackbot has joined #htmla
22:24:34 Sorry... I don't know anything about this channel
22:24:34 If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group)
22:24:47 zakim, make minutes
22:24:48 I don't understand 'make minutes', janina
22:24:53 trackbot, init
22:25:14 I have made the request to generate http://www.w3.org/2010/12/01-htmla-minutes.html plh
22:25:49 trackbot, associate this channel with #html-a11y
22:25:49 Associating this channel with #html-a11y...
22:25:56 action-88?
22:25:56 ACTION-88 -- Sean Hayes to review Media Fragment URI 1.0 http://www.w3.org/TR/2010/WD-media-frags-20100624/ -- due 2010-11-24 -- OPEN
22:25:56 http://www.w3.org/WAI/PF/HTML/track/actions/88
22:26:13 topic: Candidate Formats Report
22:26:21 agenda+ Candidate Formats Report
22:26:21 agenda+ Strategy for Synchronizing binary alternative media
22:26:21 agenda+ Other Business?
22:26:21 agenda+ Meeting Scheduling Through January 5
22:26:21 agenda+ be done
22:26:55 http://www.w3.org/2001/12/zakim-irc-bot.html
22:27:21 http://www.w3.org/2002/03/RRSAgent
22:27:28 http://www.w3.org/2005/06/tracker/irc
22:28:02 http://www.w3.org/WAI/PF/HTML/wiki/TextFormat_Pros_Cons_Overview
22:28:13 thanks.
22:30:52 after reviewing the long list of requirements last week on http://www.w3.org/WAI/PF/HTML/wiki/TextFormat_Mapping_to_Requirements in became apparent that we need a short summary that we can use as a basis for recommendation
22:31:03 John has started preparing this in the above document
22:31:22 this may become the basis for the potential chartering of a new working group
22:31:36 it should lead to a work plan for the new working group
22:32:27 (this was Janina)
22:32:33 geoff: is there a timeline?
22:33:00 janina: it would be good if we can conclude it this week - it is a lot of desire to move quickly
22:33:03 geoff: I can help
22:36:07 silvia: I am working on several inputs from diverse parties towards missing features around captions etc
22:36:15 silvia: I wonder what the urgency is
22:37:35 plh: seems to be a lack of coordination between the a11y WG and the HTML WG
22:38:08 plh: the HTML WG has an action item to investigate WebSRT further
22:38:29 plh: I don't want to have work on multiple formats for the same problem solution
22:38:53 janina: what we're not ready to say in this group is that we are perfectly comfortable with WebSRT to the exclusion of TTML
22:39:40 geoff: I agree - but given the statement of the browser vendors to support WebSRT, the question is whether we should spend time on TTML
22:40:04 janina: I am not clear whether all browser vendors object to TTML
22:40:46 … it sounds to me like MS may use WebSRT
22:41:07 sean: they will not oppose a common solution, but that doesn't mean they will oppose TTML
22:41:21 janina: I think I also heard there will be support from Adobe for TTML
22:41:49 … and others may announce this support, too
22:42:04 what I said is that IE want a common solution, and will do webSRT if that its ot
22:42:18 that does not imply opposition to TTML
22:42:43 s/its ot/is it/
22:43:10 k. well just being clear
22:43:43 silvia: if the browser have decided to support WebSRT, does it make sense for W3C to focus just on that
22:43:57 janina: well, we know that it doesn't yet provide for all needs
22:44:05 when it is a W3C soec
22:44:07 spec
22:44:17 geoff: when it's in w3c, we can get it into shape
22:44:45 besides we dont have to wait for browser mftrs to do TTML
22:44:52 janina: I am uncomfortabel until I see solutions
22:45:07 http://www.cwmwenallt.com/ttml/ttml-demo.htm
22:45:37 http://yayquery.github.com/jquery-singalong/
22:46:08 nice demo.
22:47:32 silvia: it's not quite true there are no implementations for websrt
22:48:00 … there are implementations like the one above
22:48:14 yayquery demo not working in IE9
22:48:32 http://www.w3.org/WAI/PF/HTML/wiki/TextFormat_Mapping_to_Requirements
22:49:56 janina: are we ready to make a recommendation for something that hasn't proven to work for all our requirements?
22:50:14 silvia: I have added examples in the gap analysis for how to do it now or how to fix it
22:50:30 … if we get control of websrt, we can make it support all needs
22:50:44 janina: what is the feeling in the group?
22:51:06 sean: if TTML is not allowed to win, then what's the point?
22:51:26 q+
22:51:40 geoff: I agree - making a recommendation by us doesn't seem to make much sense
22:51:56 plh: we need input from this group soon before decisions are being made in the html wg
22:52:22 janina: so what recommendation are we going to make?
22:53:03 geoff: it just doesn't seem like TTML is going to go anywhere here, so we should probably move with websrt or rather an improved version of it
22:53:41 kenny: do we have a clear indication from browser vendors that they will not support TTML?
22:53:48 janina: we heard it from a couple
22:54:05 kenny: can we do a quick check with the browser vendors?
22:54:30 geoff makes this recommendation reluctantly.
22:54:37 silvia: I think the indications we got from the vendors was very clear
22:55:13 Mozilla, Safari, Opera in particular
22:55:44 kenny_j: we should ask for official responses
22:56:04 … we don't have formal statements about what they are prepared to implement
22:56:30 janina: also if they are ready to provide the engineering resources to fix the gaps
22:57:16 q-
22:58:36 plh: another way of doing this is to point out the gaps and that websrt needs to support these for us to make a recommendation
22:59:10 janina: identifying the gaps is important
22:59:21 I need to drop off the call now. Janina, I will call you in half an hour.
23:00:41 silvia: we don't make the decision, so we can extend John's page and say that givne these things are fixed, we are happy to accept either format
23:00:56 plh: or we can propose to create a WG that will sort out those issues
23:01:17 If we have a clear statement from the browser vendors that they will support web srt going forward + the additional features we introduce, then web srt is the logical choice.
23:01:30 geoff: I feel we are going to end up with a non-xml version of TTML
23:01:36 bye all.
23:01:41 -Kenny_Johar
23:02:11 geoff: it will add a lot of time to the process
23:02:21 .. in the meantime the caption world will move forward
23:03:08 sean: TTML is already done
23:03:11 zakim, mute me
23:03:11 silvia should now be muted
23:04:27 geoff: a single format would be preferrable
23:05:02 plh: it is not clear to me if the html wg wants to point to one single format
23:05:02 +Eric_Carlson
23:06:27 … only if we want a single format do we have to push the HTML WG towards that
23:06:40 sean: the track format is the most important thing - the rest can be left open
23:06:44 zakim, unmute me
23:06:44 silvia should no longer be muted
23:07:48 q?
23:08:01 silvia: I think we need a common baseline format supported by all browsers
23:08:27 Judy has joined #htmla
23:08:31 zakim, code?
23:08:31 the conference code is 26631 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), Judy
23:08:55 sean: we can decouple the decision on what is the baseline format and what we standardize
23:09:03 +Judy
23:09:11 … we don't want to hold up the HTML5 spec by insisting on a baseline format
23:12:31 zakim, who's here?
23:12:31 On the phone I see Janina, Geoff_Freed, Sean_Hayes, Plh, silvia, Eric_Carlson, Judy
23:12:33 On IRC I see Judy, trackbot, silvia, Sean, gfreed, RRSAgent, janina, Zakim, plh
23:14:35 plh: we need some recommendation to the HTML WG
23:14:47 … my fear is that the two groups are out of sync
23:15:44 janina: do we agree that a high level summary/gap analysis document would be good to return to the HTML WG
23:15:53 silvia: I'd be happy with that
23:16:18 geoff: if a WebSRT group is chartered, we will want to make sure that the requirements are met
23:17:19 janina: a new requirement just evolved in the mailing list on how to synchronize chunks binary and text
23:18:19 … if text and audio chunks are being synchronized at very different locations in the code, I am concerned whether this is smart
23:18:31 eric: I don't understand
23:21:21 silvia here it is http://lists.w3.org/Archives/Public/public-html-a11y/2010Dec/0025.html
23:21:32 JF has joined #htmla
23:21:48 rrsagent, make minutes
23:21:48 I have made the request to generate http://www.w3.org/2010/12/01-htmla-minutes.html Judy
23:22:01 eric: David Singer sent a concern about what we really want to support in browsers
23:23:29 is there a different number for calling in? I go to a11y# and am told i am the first to join
23:23:46 geoff: no browser is supporting TTS natively
23:24:18 silvia: the screen reader would support this through the browser's accessibility API, which is already in place
23:24:26 geoff: is it going to be in sync
23:27:18 silvia: it's at a different level - the need to synchronize audio from resources and from TTS is not in the markup level
23:27:59 q+
23:28:31 janina: what about synchronizing sign language and main video synchronization
23:28:46 eric: when the sign language takes longer than the speech, there needs to be some additional information
23:29:23 janina: I am also concerned that everything needs to pause at the same time
23:30:16 q?
23:30:34 silvia: I think that's possible when implemented and controlled by the browser
23:30:59 judy: will we share the summary with the HTML WG?
23:31:11 janina: I think we should do that today
23:31:17 judy: are there edits missing?
23:31:38 judy: also the request from kenny to ask for positions by browser vendors
23:31:50 … there are foregone conclusions
23:32:19 judy: what will we be saying to the broader html wg and wrt to a Websrt charter?
23:32:37 … there is an urgent timeline
23:32:47 janina: I don't think we have a conclusion on any of these
23:33:48 judy: let's come to an agreement
23:33:59 1. John's summary
23:34:11 judy: do people feel this can be shared with the HTML WG tomorrow?
23:34:36 Sean: no
23:34:51 … my comments are on the mailing list
23:35:21 silvia: I'd like to add a bit more on the websrt side
23:35:27 judy: can we get this done by tomorrow?
23:36:39 plh: we can report to the html wg and give feedback that we are going to provide a document
23:36:59 judy: janina can provide an interim statement
23:37:23 judy: how will we get it finalized?
23:37:49 janina: if Sean and Silvia simply added their input to the wiki page, that would be ok by me
23:38:09 … I'd rather have the edits directly than lost in emails
23:38:46 judy: can we have the edits by Friday?
23:38:58 sean: yes
23:39:00 silvia: yes
23:39:26 geoff: do you want all the comments on the wiki?
23:39:45 janina: keep it terse and at the summary level - no details
23:40:03 … link to the details
23:41:01 2. Kenny's suggestion for vendor positions
23:41:17 judy: is there concensus from the group that this should happen?
23:41:28 … and how we could go about it?
23:42:20 janina: not sure there is concensus - I wonder how difficult it will be to get people on record
23:42:29 plh: let's ask eric :)
23:42:57 eric: committing the company's resources is way above my pay grade ;-)
23:43:54 eric: I am happy to ask the question to others in the company
23:43:58 silvia: what is the question?
23:44:31 how strongly do the browser vendors feel about a xml based solution?
23:46:01 judy: maybe it's a very sensitive question to answer
23:46:52 eric: if we are going to ask a question, it should not be about xml vs non-xml, but more directly whether a vendor plans implementing support for WebSRT or TTML or both
23:47:02 … whether there is a preference
23:47:07 judy: also whether there is an aversion
23:47:42 geoff: also needs to be about the extensions for websrt
23:48:34 silvia: maybe make a questionnaire with multiple questions
23:48:43 … TTML vs WebSRT
23:48:52 … whether generally XML
23:49:08 … whether support for WebSRT extensions
23:49:30 judy: might be something to raise tomorrow at html wg meeting
23:50:12 janina: might be difficult to summarize tomorrow
23:51:48 judy: we should mention that if websrt is the format, we need extensions
23:52:09 janina: the wider exploration had merit
23:52:34 … taking it all into a separate wg makes a lot of sense
23:53:47 judy: should the new wg be websrt specific or have a wider focus?
23:55:23 s/should the new wg be/was there a consensus with regard to whether the new wg should be/
23:55:44 silvia: my opinion is the new wg should specifically look at websrt - there's already a wg for ttml
23:56:19 … the decision which format to use is not one that would be done in the wg
23:57:01 judy: there are other needs that go beyond the mere format that need to be resolved
23:57:10