14:00:01 RRSAgent has joined #tt 14:00:01 logging to http://www.w3.org/2014/05/15-tt-irc 14:00:03 RRSAgent, make logs public 14:00:03 Zakim has joined #tt 14:00:05 Zakim, this will be TTML 14:00:05 ok, trackbot; I see SYMM_TTWG()10:00AM scheduled to start now 14:00:06 Meeting: Timed Text Working Group Teleconference 14:00:06 Date: 15 May 2014 14:00:15 SYMM_TTWG()10:00AM has now started 14:00:24 + +44.192.341.aaaa 14:00:38 +pal 14:00:49 zakim, +44.192.341.aaaa is me 14:00:49 +nigel; got it 14:00:51 mike has joined #tt 14:00:54 chair: nigel 14:01:25 +Mike 14:01:54 Present: nigel. pal, Mike 14:02:07 jdsmith has joined #tt 14:02:08 +[Microsoft] 14:02:39 Present+ jdsmith 14:04:23 Regrets: Frans de Jong, Glenn Adams 14:06:30 topic: MPEG liaison re MIME Codecs parameter 14:06:34 scribeNick: nigel 14:07:13 nigel: Can't cover this topic fully today as we need Glenn and David to contribute to the conversation, but we can summarise the state of the debate to date. 14:08:05 mike: I'm concerned that we haven't addressed my email that described the points of disagreement. 14:08:41 ... the thread seems to have evolved towards document conformance profiles, i.e. documents conform to all of the profiles that are signalled. Then a decoder only needs to know that it can support one of the listed profiles 14:09:12 ... in order to proceed. This is useful but not sufficient. The proposal requires registration of the profile, which is fine, but it doesn't allow 3rd party namespaces to be added and signalled like the current 14:09:46 ... 14496 does. That forces the industry to register all separate combinations of namespaces. That's not the end of the world but the discussion hasn't solved that. 14:11:23 nigel: It's a point of dispute in the reflector whether namespace signalling is needed at all - they're features of specifications already. 14:12:20 mike: It would be a problem for Ultraviolet if all the features needed for processing a document can't be defined, e.g. TTML subset plus image processing subset. 14:12:33 pal: Why can't we delegate that combinatorial logic to the registration? 14:13:12 mike: Yes that will work for the profiles defines by Ultraviolet. But it does not solve the problem when the document contains 608 and 708 data. There's no way to signal that. Someone would have to register 14:13:29 ... the Ultraviolet profile that includes 608 or the one that includes 708 or the one that includes both. 14:13:41 pal: When you say 608 is that a separate specification? 14:13:45 mike: yes. 14:13:59 pal: So another row in the specification table could contain m608 and reference that other specification. 14:14:32 mike: Yes. It forces anyone using a combination of namespaces to register with W3C the combination. There's no concept in the current proposal to say 'processor needs both X and Y'. 14:15:14 ... The proposal is necessary but not sufficient - it would say 'doc conforms to X, Y and Z so if you support any of those you can decode the document'. This doesn't cover other namespaces 14:15:30 ... which would have to be combined and the combination registered with W3C. 14:16:11 pal: So you'd like a way to signal 'document conforms to A+B or C or D' to create on the fly new combinations of conformance by combination. 14:16:51 mike; Right. The argument on the thread was that this allows custom profiles to be created on the fly. Today that's already possible in the ISO specs. We were only really dealing with the unwieldiness of the long strings. 14:17:13 ... It's not the end of the world as long as the registration process is lightweight. 14:18:21 nigel: It would be really helpful Mike if you could point the discussion to where the requirement for combinations of profiles comes from in the ISO specs. 14:22:33 mike: It would also be helpful to talk about the registration process. If the bar is really low then it's much more compelling to force people to register the combinatorial profiles they want. 14:24:22 nigel: Describes lightweight process. 14:24:43 mike: Maybe we could codify reasons why a registration may be rejected, e.g. Not TTML, Already Registered etc. 14:25:44 topic: F2F planning 14:26:15 nigel: It's for me and David to work on the agenda. The goal is to work on our deliverable of the TTML <--> WebVTT mapping. 14:26:57 topic: Issues discussed and raised over the past week 14:27:22 issue-307? 14:27:22 issue-307 -- Conformance language and processor profile rather than content profile. -- open 14:27:22 http://www.w3.org/AudioVideo/TT/tracker/issues/307 14:27:37 issue-308? 14:27:37 issue-308 -- It is unclear how a document is associated with a related video object -- open 14:27:37 http://www.w3.org/AudioVideo/TT/tracker/issues/308 14:27:58 pal: We're awaiting glenn's input on issue-307. 14:28:25 pal: I think nigel wanted to think more about 308. 14:28:44 pal: my action item now is to fix the typo re Related Media Object. 14:29:01 ... I believe the current document does not mandate that a document be attached to a single frame rate. 14:29:14 nigel: okay I'll review more. 14:30:01 pal: I propose to make the change to Related Video Object either by defining it or changing it. Then I'll close the issue and if there's an issue related to frame rate we can open a new ticket. 14:30:44 mike: Historically we made it 'media object' to be more generic than video and the link is external to TTML. 14:31:19 pal: my plan is to define Related Video Object as the video component of the Related Media Object. 14:33:13 nigel: We need to clarify that frameRate in an IMSC document does not need to be identical to the frame rate of the related media object. 14:33:18 pal: Would a note be sufficient? 14:33:22 nigel: yes, possibly. 14:33:50 -pal 14:34:45 topic: Change Proposals 14:34:47 https://www.w3.org/wiki/TTML/changeProposal002 14:34:58 +pal 14:34:59 nigel: I've got a feeling we may need Glenn to review this before we can close it. 14:36:03 nigel: In fact Glenn has put a note at the bottom showing he's implemented it so it's for jdsmith to verify that the implementation meets the expectation. 14:36:20 https://dvcs.w3.org/hg/ttml/rev/c9fd49837446 14:36:31 nigel: that's the change set on TTML2 14:36:57 ... The editor's draft for TTML2 is at https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html 14:38:05 jdsmith: I have a question about change proposal 5. It's not really a change, but a representative way to map to HTML. 14:38:21 plh has joined #tt 14:38:29 +Plh 14:38:57 ... We've reviewed that here, and it's pretty much what we do. What's the destination for the change? 14:39:34 nigel: It can be an appendix to TTML2, or striped all the way through TTML2 per feature, or a separate note altogether. 14:41:44 nigel: If the whole world is moving away from XSL-FO towards CSS then it would make sense to add it throughout TTML2 on a feature by feature basis. 14:42:09 jdsmith: I could map the rendering to the sections in TTML2. 14:42:17 plh: I think this would be extremely useful. 14:43:03 pal: If it applies both to TTML1 and TTML2 it should not be an appendix to TTML2. 14:43:18 s/both/equally both 14:43:30 pal: In that case a separate document would be useful. 14:43:47 plh: I can see it either way. You can use it for TTML1 additionally to TTML2. 14:44:55 nigel: I would prefer it to be striped through TTML2 to encourage new implementers to start there not at TTML1. 14:45:12 jdsmith: I'll start working on the mapping to sections. 14:45:23 plh: We don't want to overload the editor. 14:45:33 ... You could potentially become another editor for this purpose. 14:46:06 ... By the way some features may not be mappable if CSS doesn't have the features, and it's important to highlight them. That will probably give rise to a sub-profile of TTML2 that avoids non-CSS features. 14:46:26 jdsmith: Let me look at the work of striping it through, see what Glenn thinks and hopefully confirm next week. 14:48:30 ACTION: nigel to create a wiki page for the September F2F with a draft agenda and an 'intention to attend' section. 14:48:30 Created ACTION-289 - Create a wiki page for the september f2f with a draft agenda and an 'intention to attend' section. [on Nigel Megitt - due 2014-05-22]. 14:49:00 plh: We're also looking at setting up an Extensible Web Summit in Berlin in September just beforehand. This would give people a good reason to be in Europe around that time. 14:50:09 plh: The dates aren't final yet - our German office is looking for a host. The location will be Berlin because on the 13/14th Sep there's a Javascript conference. Once it's settled I'll report that back here. 14:50:19 ... It may help people to attend. 14:52:09 plh: On the testing front, there are lots of good movements there. We have a test suite for WebVTT - I'll add the links to it to our wiki dashboard. At some point we need to look at what we can do for TTML. 14:52:27 plh: The old tests are still valid but we may need to refactor them so they can be run automatically. 14:53:12 nigel: Change Proposal 26 is our home for this https://www.w3.org/wiki/TTML/changeProposal026 14:54:52 plh: Waiting until September before diving into the tests will be really helpful. Any progress with scripting languages and declarative languages that help automatic testing is good for us. 14:56:35 Re Codecs we're tentatively scheduled for the 29th. 14:56:44 plh: regrets for the next 2 weeks. 14:57:01 -Plh 14:57:02 -[Microsoft] 14:57:02 -pal 14:57:04 rrsagent, make logs public 14:57:05 -Mike 14:57:09 -nigel 14:57:10 SYMM_TTWG()10:00AM has ended 14:57:10 Attendees were pal, nigel, Mike, [Microsoft], Plh 14:57:22 rrsagent, generate minutes 14:57:22 I have made the request to generate http://www.w3.org/2014/05/15-tt-minutes.html nigel 14:58:56 nigel has left #tt 16:50:43 Zakim has left #tt