{Minutes} TTWG Meeting 2020-04-09

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


In text format:

   [1]W3C

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


                Timed Text Working Group Teleconference

09 April 2020

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

      [2] https://www.w3.org/2020/04/02-tt-minutes.html

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

      [4] https://www.w3.org/2020/04/09-tt-irc


Attendees

   Present
          Andreas, Atsushi, Gary, Glenn, Nigel, Pierre

   Regrets
          -

   Chair
          Gary, Nigel

   Scribe
          nigel

Contents

    1. [5]This meeting
    2. [6]IMSC 1.2 /rec link
    3. [7]TTML2 2nd Edition Implementation Report
    4. [8]AOB
    5. [9]Meeting close

Meeting minutes

  This meeting

   Nigel: Only 2 things on the agenda: IMSC/Rec link and TTML2
   Tests
   … AOB?

   group: [no Other Business]

  IMSC 1.2 /rec link

   Nigel: There's been input from Atsushi, Philippe and Pierre on
   this. Status?

   Atsushi: It seems I cannot create the final product only using
   Respec, so maybe it will be
   … easiest to copy the finished public HTML and make the edits
   manually for the GitHub
   … branch and in-place publication.
   … If that is okay and we do not need to edit the Respec-based
   file on GitHub that would be easier.

   Pierre: It'd be better if GitHub matches exactly what was
   published. What is the challenge?

   Atsushi: There is no feature to add some text right after dates
   in Respec-based HTML.
   … That is the critical thing we need to do.

   Pierre: My suggestion is to file an issue with Respec.
   … In the past for issues that block publication they have fixed
   it very quickly.
   … That's my suggestion - file an issue with Respec.

   Atsushi: One question is how the current file was published. Do
   you know?
   … It seems there is some local editing of the HTML since I
   encountered the ID conflict
   … in IMSC 1.0.1.

   Pierre: The editor does not do the publication so I cannot tell
   you.
   … But by the way I see that there is a post-process Javascript,
   so we can use that to modify the title.

   Atsushi: I thought that at some point there is a difficulty in
   getting the exact element to
   … append to. It seems there is no ID for the element by
   default.

   Pierre: You might be right, but my point is still that we
   should at least file an issue with Respec
   … and give us 2-3 weeks. If there's no resolution then we'll
   have to do it manually.
   … Other things being equal it would be better to fix the tool.
   … Otherwise we will keep running into the same issue.

   Atsushi: Maybe a stupid question: do we want to keep the Respec
   version of HTML for
   … future edits? Do we have any plan to update the revisions?
   … Like 1.1 revision 2 or something?

   Pierre: That's not been the case in the past - in the case of
   1.0 we ultimately published
   … 1.0.1 instead of 1.0 v2.

   Atsushi: I wonder if we don't expect large edits on existing
   Recs then it might be okay to
   … just have the published HTML.
   … in the GitHub repository.

   Pierre: I would really rather not.
   … It seems like a huge step backward to keep track of the
   complete HTML.
   … Respec is an officially supported publishing tool.

   Nigel: I'd support Pierre in that - we don't need to keep the
   published HTML in GitHub
   … for archival purposes - that's already on /TR and backed up
   separately.
   … The GitHub repo is for us to work on, so it makes sense to
   keep the Respec version.

   Atsushi: Okay let me file a feature request to Respec and in
   parallel find a way to do something.

   Nigel: Sounds good, thank you.

   Atsushi: How do we do IMSC 1.2 CR? For CR there is no in-place
   replacement process so
   … we need to publish a new CR.

   Pierre: Just wait until PR.

   Atsushi: It's fine to keep this open until PR?

   Pierre: My understanding is that publishing a new CR is
   difficult.
   … If it is trivial then let's do it otherwise keep this open
   until PR.

   Nigel: I would ask for a pragmatic response from the team on
   this, because there's no
   … change to the document content.

   Atsushi: There's no requirement to pass reviews for an
   editorial document update, so
   … it should be fine to reissue the transition request if
   there's a CfC.

   Nigel: I will not issue a new CfC because we already have a
  minuted resolution for this.

   Atsushi: OK, let me submit that way and issue a pull request to
   update the document.

   Nigel: OK, sounds good to me. Thank you.

  TTML2 2nd Edition Implementation Report

   Nigel: Tests are still being reviewed and merged one by one.
   … We have 6 issues on ttml2-tests for 2nd Edition, and
   … 4 open Pull Requests. I have a pull request to make the audio
   in body test work with my audio implementation, which I will
   merge when the test is merged.

   Glenn: I have a couple of tweaks to make on the lineheight
   normal test, a shear test change
   … to make, a couple of possible bugs. I should be able to wrap
   those up then make a run
   … on the implementation report itself.
   … So nothing more to discuss right now I think.

  AOB

   Nigel: There's a new CSS issue on ruby offset, you may be
   interested in.

   Glenn: I had planned to put that in a future Ruby module, but
   don't plan to do any work
   … on it at the moment.

   [10][w3c/csswg-drafts] [css-ruby] Ruby offset (#4932)

     [10] https://github.com/w3c/csswg-drafts/issues/4932


   Nigel: Just for information - I pointed out that we used to
   have ruby offset in TTML2 but
   … removed it, in part because of the lack of CSS
   implementation.

  Meeting close

   Nigel: Thanks everyone, we've completed our agenda, so we'll
   close for today.
   … Do add agenda items to the agenda issue on GitHub please, by
   Tuesday, so the Chairs
   … can prepare the agenda.
   … [adjourns meeting]


    Minutes manually created (not a transcript), formatted by
    [11]scribe.perl version 114 (Tue Mar 17 13:45:45 2020 UTC).

     [11] 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.

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