{minutes} TTWG Meeting 2018-09-20

Thanks all for attending today's TTWG meeting. Minutes can be found in HTML format at https://www.w3.org/2018/09/20-tt-minutes.html


In text format:


   [1]W3C

      [1] http://www.w3.org/


                Timed Text Working Group Teleconference

20 Sep 2018

   See also: [2]IRC log

      [2] https://www.w3.org/2018/09/20-tt-irc


Attendees

   Present
          Nigel, Pierre, Thierry, Glenn, Cyril, Andreas

   Regrets
          None

   Chair
          Nigel

   Scribe
          nigel

Contents

     * [3]Topics
         1. [4]This meeting
         2. [5]CfC Update
         3. [6]TTML2 Implementation Report
         4. [7]TTML1 3rd Edition Implementation Report.
         5. [8]Updated references to W3C Specifications
         6. [9]IMSC vNext Requirements
         7. [10]TTML Profile Registry
         8. [11]TPAC 2018
         9. [12]Meeting close
     * [13]Summary of Action Items
     * [14]Summary of Resolutions
     __________________________________________________________

   <scribe> scribe: nigel

   Glenn: [Only available for 30 minutes]

This meeting

   Nigel: Today we have CfC update, implementation report, IMSC
   vNext Reqs publication status
   ... TPAC 2018 agenda, that's it I think. Any more?

   group: [no more for the agenda]

CfC Update

   Nigel: I sent the CfCs for IMSC 1.1, TTML1 3rd Ed and TTML2 as
   per our plan. They expire
   ... on 26th September. So far I have had no objections.
   ... Further, I see that we are in a good state in terms of
   document readiness for publication.
   ... Thanks to the Editors and Thierry for preparing the docs.
   ... Is there any more to do regarding document preparation?

   Thierry: I think it is all done. The two drafts are ready for
   TTML1 3rd Ed and IMSC 1.1
   ... unless comments come in.

   Nigel: Yes.
   ... So still need to complete the prep for TTML2?

   Thierry: I'm not aware of that being ready yet.

   Glenn: I will give that to Thierry over the weekend.

   Thierry: That's great.

   Nigel: Thank you

TTML2 Implementation Report

   Glenn: I will be wrapping up the tests for the IR as well as
   moving the spreadsheet data
   ... over to the wiki over the weekend, so we should be all set
   to go next week.
   ... Thanks for your effort on #embedded audio. I saw your two
   pull requests so I will process
   ... those as well.

   Nigel: Thank you.
   ... On the audio tests, we have completed work on almost all of
   them.
   ... Our implementation now only needs to be updated to pass the
   clipEnd part of the
   ... clipBegin and clipEnd tests, and the animate element.

   Glenn: Could you update the column for the adhere data in the
   IR spreadsheet for TTML2?

   Nigel: Yes, I will complete that by the end of tomorrow.
   ... Looking at the rest of the TTML2 IR, are there more tests
   that need implementations?

   Glenn: We're all set for the other features - Pierre recently
   added entries for luminanceGain
   ... and disparity.

   Nigel: Does that mean we have green on the T column for
   everything?

   Glenn: There are a few for us [skynav] to do which we will
   complete over the weekend.
   ... About 10 or so. We have done the work, just need to verify
   a few things and then
   ... update the spreadsheet. Everything is green on there or
   will be by the weekend. I don't
   ... have any other external dependencies right now.

   Nigel: That's great news.

TTML1 3rd Edition Implementation Report.

   Glenn: I updated our columns last night, so we have verified
   all of those tests passing
   ... through the TTT tools so we are all set for 2
   implementations.

   Pierre: The only one missing is for Cyril to report what he
   mentioned verbally last week
   ... that the Netflix implementation passes the anamorphic
   tests.

   Cyril: I will update it today.

   Nigel: Great.

Updated references to W3C Specifications

   Glenn: One thing I have to do on TTML2 over the weekend is
   update some references
   ... with newer URLs for W3C references.
   ... For example the CSS Fonts module finally made it to Rec
   today, so I'll update that and
   ... a couple of other URLs.

   Nigel: I was going to mention that also!

   Glenn: I don't recall, offhand, but we should check if we have
   any informative references
   ... in TTML1 that need updating too, Pierre.

   Pierre: I'll do a quick pass through all the normative
   references in IMSC1.1 and TTML1.

   Glenn: Check the informative references. I don't think any of
   the normative ones have
   ... changed and we don't want to raise the substantive change
   flag if they have changed.

   Pierre: Alright, I'll check the informative section because
   they are easy to update.

   Nigel: Yes

   Pierre: Thierry, can you send me the URL for the TTML2
   reference that we need to make
   ... from IMSC 1.1? When do we update it? After PR just before
   Rec?

   Thierry: It's a tricky one. Right now I don't have that URI.

   Nigel: I think we should do it on going to PR and then again on
   going to Rec.

   Pierre: Thierry can you send me the URI?

   Thierry: Can I assume they all are to be published on October
   4?

   Nigel: Yes

   Pierre: Yes

   Glenn: I've checked the TTML1 references and nothing needs
   updating there.

   Pierre: Thank you. I'm checking IMSC 1.1 also.

   Glenn: At least there are no W3C references to be updated.
   ... It's possible the Unicode references have been revved, but
   we should not change the
   ... normative references at this point.

   Pierre: Alright.

   Glenn: I noticed the Web Audio API went to CR, so we can update
   that one also.

   Nigel: Yes, that's right.

   Pierre: A quick question, in IMSC 1.1, the normative references
   to namespaces in XML 1.0
   ... has a generic URL to TR/XMLNames undated. Do we want to
   freeze that to 3rd edition?
   ... It's this issue with specref where it imports the full name
   but it uses the generic URL.
   ... I'm thinking we should update the URL to point to the
   specific 3rd edition that we actually
   ... reference.

   Glenn: Whatever TTML1 3rd Ed references IMSC should match, do
   you think?

   Pierre: Yes, let's check that...
   ... Yes, 3rd Edition, specifically. I'll update that in IMSC
   1.1.

   Nigel: Yes, that's the right thing to do.

   Pierre: I'll update the PR, please review to make sure there
   isn't a mistake.

   Nigel: We've covered TTML2 IR, TTML1 3rd Ed IR, there's nothing
   to do on IMSC 1.1 IR.
   ... Is there anything else on those three documents or their
   test suites or IRs to cover?

   group: [nothing else to cover]

IMSC vNext Requirements

   Nigel: We resolved to publish this as a WG Note last week.
   Thierry, what's the status of
   ... that publication?

   Thierry: The issue remains the short name that Pierre suggested
   to change, and I think you
   ... asked the working group. If I have that approval then I
   will request that name to Philippe.

   Nigel: Right, I kind of told the group what it would be and
   gave a small opportunity to
   ... ask for something different, and nobody responded, so I
   think we can safely go ahead
   ... with that short name of imsc-1.1-reqs

   [15]Email where I proposed that short name

     [15] https://lists.w3.org/Archives/Public/public-tt/2018Sep/0101.html


   Nigel: Thank you Pierre for actually proposing it to me!
   ... Anyone have any comments on that short name?

   group: [silence]

   Nigel: Thierry, you can take that as a resolution.

   Thierry: Can you restate the resolution please?

   RESOLUTION: Publish the IMSC vNext Requirements for IMSC 1.1 as
   a WG Note with the short name imsc-1.1-reqs

   Nigel: There you have it!

   Thierry: Thank you

TTML Profile Registry

   Nigel: Just flagging up that we will need to make changes to
   the profile registry quite soon
   ... to include the new short codes for IMSC 1.1, TTML2 and any
   other requests that come in.

   Glenn: [I have to drop off, bye]

   Nigel: Raising awareness now, we need some issues and pull
   requests for this.
   ... And reminder we need to deal with TTML2 content profiles as
   well as processor profiles.
   ... I'm not sure what we'll actually do there!

   Pierre: I've had no time to spend on this so I have zero
   opinion!

   Nigel: OK! I think we're all in that boat, but we need to look
   at it.
   ... We should have it updated around the time we publish the
   Recs.

TPAC 2018

   Nigel: It looks like only Glenn and I are attending but I know
   lots of other people have
   ... registered.
   ... Agenda?

   Pierre: We should just celebrate if we make it! Champagne for
   the agenda!

   Nigel: [amusement]
   ... Right, the existing draft agenda at:

   [16]TPAC TTWG page

     [16] https://www.w3.org/wiki/TimedText/tpac2018


   Nigel: shows us covering IRs and PRs but we're on schedule to
   do that earlier.
   ... It also shows joint meeting with M&E IG on the Monday, and
   the Chairs of that group
   ... have proposed to me an afternoon slot. I think that works.
   ... They did ask what we would like to cover.
   ... Any thoughts on that?
   ... Also TTML <--> WebVTT mapping

   Andreas: We discussed this for some time. I see no requirement
   to restart the activity.
   ... If we want to bring this up to date to the current
   specifications it may need a bit more
   ... than fixing the errors in relation to the latest WebVTT and
   TTML documents. We may
   ... need to restructure the complete work. Also we have
   received little feedback on that
   ... work. It was useful if you have the requirement to do the
   mapping regardless of the
   ... inconsistency. We did not see a lot of interest in that
   work. If nobody strongly makes
   ... a request to do this then I do not see a requirement to
   restart it.
   ... We still have the problem for WebVTT that we still need to
   think about what kind of
   ... mapping do we want, one that works in current
   implementations, one that works in to
   ... the latest standard according to the newest changes? There
   are a lot of questions.

   Nigel: Should we remove it from the agenda for TPAC?

   Andreas: Yes

   Nigel: OK
   ... What should we have on the agenda for TPAC?

   Pierre: We don't have all the right people.
   ... There's a flurry of activity on WebVTT then nothing. Any
   insights?

   Nigel: I don't have any insights.

   Thierry: I don't know any more.

   Nigel: I would like to begin thinking about any requirements
   for TTML2 2nd Ed that are not
   ... yet met, and possibly things like audio and live
   contribution, which we've long said we
   ... would try to cover but have given little attention to.
   ... We've given some attention to audio of course.

   Pierre: One topic I would like to understand better is live
   subtitling. Maybe now is a good
   ... time to do a deep dive and understand what should and
   should not be done by TTWG.

   Nigel: I'd be happy to do that and take the group through the
   existing work.

   Pierre: There's a lot of confusion about the use of subtitles
   in the live environment and
   ... what constraints it imposes on the live stream multiplex.

   Nigel: Yes, I'd be happy to cover that.

   Andreas: I would support that. It's a good topic.

   Pierre: People are starting to get more subtle with
   implementations and are finally running
   ... into these issues.

   Andreas: Yes and it's also good to think about how to explain
   the relation with what EBU
   ... did with EBU-TT Live and IMSC and W3C.
   ... It would be very helpful for the community to know what the
   TTWG position on the topic
   ... and on the EBU-TT Live activity is.

   Nigel: Good point.
   ... Consider that added to the agenda.

   Andreas: One comment on TPAC. The agenda is a bit unfortunate
   this year. I plan to
   ... participate in the M&E IG meeting so I may miss most of the
   TTWG meeting on Monday,
   ... and will be there on Tuesday morning. But in the afternoon
   there's the AC meeting, so
   ... I'm not sure. I will only definitely be there on the
   Tuesday morning. The other slots
   ... are not very good for me.

   Nigel: I share the same conflicts.
   ... It seems like our agenda is relatively light, so I would
   propose that we gather on the
   ... Monday morning to agree what we want to discuss with the
   M&E IG, then spend as
   ... much time as possible with M&E IG, then cover live TTML and
   future edition requirements
   ... on Tuesday morning. Obviously there may be topics that we
   also need to cover, for example
   ... AC review comments, anything arising out of the transition
   requests, or WebVTT might
   ... be on the agenda if there is any movement on it.
   ... So Tuesday afternoon remains available. I will happily
   prioritise the agenda topics
   ... based on their urgency and importance at the time.

   Pierre: I think that makes sense.

Meeting close

   Nigel: We've hit the end of our agenda today so let's adjourn
   early. Thank you everyone! [adjourns meeting]

Summary of Action Items

Summary of Resolutions

    1. [17]Publish the IMSC vNext Requirements for IMSC 1.1 as a
       WG Note with the short name imsc-1.1-reqs

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [18]scribe.perl version
    1.153 ([19]CVS log)
    $Date: 2018/09/20 14:53:36 $

     [18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm

     [19] http://dev.w3.org/cvsweb/2002/scribe/






----------------------------

http://www.bbc.co.uk

This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------

Received on Thursday, 20 September 2018 14:55:08 UTC