W3C home > Mailing lists > Public > public-tt@w3.org > March 2018

Re: {agenda} TTWG Meeting 2018-03-08

From: Nigel Megitt <nigel.megitt@bbc.co.uk>
Date: Thu, 8 Mar 2018 16:26:41 +0000
To: "public-tt@w3.org" <public-tt@w3.org>
Message-ID: <D6C71340.56EFB%nigel.megitt@bbc.co.uk>
Thanks all for attending today's TTWG meeting. Minutes can be found in HTML format at https://www.w3.org/2018/03/08-tt-minutes.html


In text format:


   [1]W3C

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


                Timed Text Working Group Teleconference

08 Mar 2018

Attendees

   Present
          Glenn, Pierre, Nigel, Philippe

   Regrets
          Cyril

   Chair
          Nigel

   Scribe
          nigel

Contents

     * [2]Topics
         1. [3]This meeting
         2. [4]TTML1 3ED CR
         3. [5]TTML2
         4. [6]IMSC
         5. [7]IMSC 1.1 signalling of conformance against
            EBU-TT-D, SMPTE-TT, SDP-US etc
         6. [8]Meeting migration
     * [9]Summary of Action Items
     * [10]Summary of Resolutions
     __________________________________________________________

   <scribe> scribe: nigel

This meeting

   Nigel: Today, we have a joint meeting with i18n 1 hour into the
   meeting.

   <Cyril_> Regrets for me. Cannot call. I will try to follow on
   IRC but unstable connection

   Nigel: That's to deal with the last remaining i18n issue on
   IMSC 1.1
   ... Today we have one TTML1 PR, may not need much discussion.
   ... Then on TTML2 there's one agenda issue, ttml2#683.
   ... For IMSC there's the i18n issue which we'll cover in the
   joint meeting.
   ... Anything else for the agenda?

   Pierre: IMSC 1.1 signalling for EBU-TT-D and SMPTE-TT and
   SDP-US.
   ... I think there's an issue we can close and a new one to open
   to describe exactly what we
   ... are trying to do.
   ... We should pick a date for TTML1 3ED CR.

TTML1 3ED CR

   [11]TTML1 3ED CR pull request ttml1#343

     [11] https://github.com/w3c/ttml1/pull/343


   Pierre: There are no substantive changes, just work to meet
   pubrules etc.

   Glenn: Part of that was making the changes for the new format
   style?

   Pierre: Yes

   Glenn: Did you copy the new code from TTML2 to do that?

   Pierre: Yes I did, porting the TTML2 DTDs and any other changes
   needed.
   ... Changing the http to https was a big change. There was no
   change to the prose.

   Glenn: Okay, go ahead then.
   ... I had to do that for TTML2, and I did it a slightly
   different way. You put it in the part of
   ... the XSL that generates style headers, whereas there was
   some equipment to generate
   ... additional header material. I will take a look - I think I
   used an XSLT parameter also.

   Pierre: Alright, we can fix that up the last minute.

TTML2

   Nigel: I've just seen an email from Ralph Swick giving approval
   to transition TTML2 to CR
   ... pending any comments on the chairs' list by end of day 12
   March
   ... He notes: "One of the actions I asked Nigel to take to the
   Working Group is to
   ... document the change policies for both the existing TTML
   Role Name
   ... Registry and the new TTML Item Name Registry in those two
   registries."
   ... We have discussed this before and our decision was to use
   Group Consensus when
   ... deciding whether to make any change. So we will need to add
   that to the registries themselves.

   Glenn: That's not enforced by the wiki

   Nigel: Correct, however we can describe the policy on the page.
   ... We discussed ttml2#683 last week so I'm removing the agenda
   label from that issue.

   Glenn: I've had to wait for travis to complete builds - now
   that it's done one I can recheck
   ... against pubrules and links.

   Philippe: Glenn, when will I get the document to publish?

   Glenn: We have until the 13th, which is 5 days. We have to get
   these two final editorial pull requests
   ... merged, and as soon as those merges happen, I will create
   the package for you.

   Philippe: I need the package from you before the 12th so I can
   install it, and check it.

   Glenn: If Nigel can approve those today or at the latest
   tomorrow morning I should be able
   ... to get them to you by tomorrow close of business.

   Philippe: I can do the work on the 12th.

   Nigel: I noticed that we can easily create the package by
   creating a release tag in GitHub.

   Glenn: There's one change to make, to rename index.html to
   Overview.html

   Philippe: I can do that on my side.

   Glenn: I'll create the release tag and check it and then send
   it to you.

   Philippe: If I find a broken link etc then I'll let you know so
   it can be fixed in the repo.

   Glenn: I changed the feedback route to include the GitHub repo
   for raising an issue, in the SOTD
   ... section, as well as the email option.
   ... Either one or the other.

   Nigel: That's great, thank you.

IMSC

   action-509?

   <trackbot> action-509 -- Pierre-Anthony Lemieux to Propose
   liaison text for the imsc 1.1 fpwd -- due 2017-10-12 -- OPEN

   <trackbot>
   [12]http://www.w3.org/AudioVideo/TT/tracker/actions/509


     [12] http://www.w3.org/AudioVideo/TT/tracker/actions/509


   Nigel: It looks like we haven't actually sent liaisons yet, but
   we published the FPWD in October.

   Pierre: I think Thierry sent a big email to lots of people.

   Nigel: That was for IMSC 1.1?

   Pierre: Yes, October 2017

   [13]https://lists.w3.org/Archives/Public/public-tt/2017Oct/0106

   .html

     [13] https://lists.w3.org/Archives/Public/public-tt/2017Oct/0106.html


   Nigel: That's a Horizontal Review one.

   Pierre: Yes, and there's another one...
   ... Thierry told us he also sent another email to external
   bodies for review.

   <plh>
   [14]https://lists.w3.org/Archives/Member/member-tt/2017Oct/0011

   .html

     [14] https://lists.w3.org/Archives/Member/member-tt/2017Oct/0011.html


   Philippe: That was BCCed to the intended recipients, so they
   are obscured.

   close action-509

   <trackbot> Closed action-509.

IMSC 1.1 signalling of conformance against EBU-TT-D, SMPTE-TT, SDP-US
etc

   Pierre: Look at pull request #322
   ... Profile signalling changes in IMSC 1.1 because it has
   changed a lot on TTML2. One of
   ... the tweaks was to address signalling of profiles, and
   there's a change needed here.
   ... I'd like to merge this pull request for everything except
   the signalling issue, and open
   ... another issue and pull request for signalling.
   ... I can try to revert the changes made for signalling, or I
   could merge this pull request
   ... as is and open a separate issue to clarify and improve
   signalling of industry profiles
   ... into IMSC 1.1.
   ... Mike Dolan opened a separate issue on this topic.

   Nigel: If we could merge in pull #337 prior to merging this
   pull request, I'd be happy to go
   ... with that second option.

   Pierre: I'm happy to do that.

   Nigel: Then we can have a separate review of signalling after
   that and discussion and see
   ... if there are any changes needed.

   Pierre: We can use imsc#331 for that.
   ... I'll merge this now.

   Nigel: I've approved #322.

   Pierre: Thank you, I'll merge that.

Meeting migration

   Nigel: We need to dial off this call and join i18n now.
   ... [adjourns meeting]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [15]scribe.perl version
    1.152 ([16]CVS log)
    $Date: 2018/03/08 16:25:03 $

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

     [16] 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, 8 March 2018 16:27:10 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 March 2018 16:27:10 UTC