{Minutes} TTWG Meeting 2020-06-18

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


In text format:

   [1]W3C

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


                Timed Text Working Group Teleconference

18 June 2020

   [2]Previous meeting. [3]Agenda. [4]IRC log.

      [2] https://www.w3.org/2020/06/11-tt-minutes.html

      [3] https://github.com/w3c/ttwg/issues/122

      [4] https://www.w3.org/2020/06/18-tt-irc


Attendees

   Present
          Andreas, atsushi, Gary, Nigel

   Regrets
          Cyril, Pierre

   Chair
          Gary, Nigel

   Scribe
          nigel

Contents

    1. [5]This meeting
    2. [6]Where should "headers" go relative to the `WEBVTT` magic
       string? webvtt#485
    3. [7]IMSC 1.2 PR Published
    4. [8]CSS font-matching algorithm may introduce fingerprinting
       issues w3c/ttml2#1202 (PING review)
    5. [9]Meeting close

Meeting minutes

  This meeting

   Nigel: Today we have WebVTT headers, IMSC 1.2 PR.
   … We also have the ARIB liaison tickets to complete our
   iteration over, and TTML2 2nd Ed IR,
   … but I note that we have no Editor of IMSC or TTML2 present.
   … Any other business, or points to raise?

  Where should "headers" go relative to the `WEBVTT` magic string?
  webvtt#485

   github: [10]https://github.com/w3c/webvtt/issues/485


     [10] https://github.com/w3c/webvtt/issues/485


   Gary: We discussed this last week. We put it back on this week
   because Roger Pantos,
   … the main editor of HLS, replied saying that they should
   specify the header location in HLS.
   … I kinda agree with him except that there are some feature
   requests for WebVTT for the
   … future that might use headers. We don't want to be in a
   situation where there are
   … incompatible header specifications in different specs. At the
   same time, until we add
   … features that use headers I'm not sure that WebVTT should
   describe what headers are.

   Nigel: I agree with the concern that incompatible definitions
   would be a bad thing.
   … Since WebVTT previously defined this, I think it would make
   sense at least for WebVTT
   … to define header conceptually even if with a note saying it
   isn't directly used by WebVTT
   … yet, but may be in the future, and is available as an
   extension point for other uses.

   Gary: Yes, actually having it as an extension/feature and
   calling it out as that makes sense.
   … I hadn't thought of that as a possibility.
   … Then HLS could potentially still specify it but also still
   point to WebVTT.
   … We could also try going with the most minimal definition of
   header.
   … As I said last time, it was removed because someone was
   asking for clarification of usage,
   … and it was removed rather than trying to iron out the issues.
   We either need to iron
   … out the issues or pare down the definition so it doesn't
   really matter.

   Nigel: Makes sense to me.

   Gary: I'll take a look at that as Editor.
   … I'll try to reply to the HLS mailing list (I have to join it
   first!)

   SUMMARY: @gkatsev to draft pull request bringing pared-down
   header definition back into WebVTT.

  IMSC 1.2 PR Published

   Nigel: We published the PR on 16th June.

   [11]IMSC 1.2 PR

     [11] https://www.w3.org/TR/2020/PR-ttml-imsc1.2-20200616/

   Nigel: Need to make the group aware of some late changes.
   … First the link to Liberation Mono fonts no longer worked so
   had to be changed.
   … Second, the URLs to EBU specs seem to be wrong. There was an
   email thread with
   … Frans from EBU who advised us. This change has not yet been
   made but I believe we can
   … make it prior to Rec publication, since it is only URLs that
   are changing, not the referenced
   … documents themselves.
   … That's w3c/imsc#561.
   … Also the BBC's AC rep, Chris Needham proposed some editorial
   changes to the Changes
   … section to clarify them. They are in w3c/imsc#560.
   … I am not expecting any process issue with those changes.

  CSS font-matching algorithm may introduce fingerprinting issues
  w3c/ttml2#1202 (PING review)

   github: [12]https://github.com/w3c/ttml2/issues/1202


     [12] https://github.com/w3c/ttml2/issues/1202


   Nigel: Just to note I did contact PING last week after the call
   and have not had a reply yet.
   … Aside from that I'd note that we have no proposals on the
   table for resolving the impasse.
   … The proposal from PING has objections from TTWG, and the
   proposal from TTWG that
   … has consensus seems to have an objection from PING!
   … I would really appreciate any other proposals if anyone can
   contribute them.

   SUMMARY: Awaiting PING response to the Chair, other proposals
   for resolving this issue are welcome.

  Meeting close

   Nigel: We've completed our agenda for today, so I'll adjourn
   until next week. Thanks everyone. [adjourns meeting]


    Minutes manually created (not a transcript), formatted by
    [13]scribe.perl version 121 (Mon Jun 8 14:50:45 2020 UTC).

     [13] https://w3c.github.io/scribe2/scribedoc.html






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

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.

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