- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Thu, 1 Oct 2020 16:46:51 +0000
- To: TTWG <public-tt@w3.org>
- Message-ID: <CAC743F7-7A15-4134-BCFB-C34D0C6D5C9D@bbc.co.uk>
Thanks all for attending today's TTWG meeting. Minutes can be found in HTML format at https://www.w3.org/2020/10/01-tt-minutes.html
Note that we have initiated our Decision Policy on 2 resolutions:
1. Resolution: we publish the current ED of TTML Profiles Registry as a WG Note subject to editorial changes (e.g. update ReSpec)
2. Adopt /history in place of Previous Version for all future publications #145<https://github.com/w3c/ttwg/issues/145>
The review period for these will end on 15th October. For each, if there are no outstanding/unresolved objections by that date then a Chair will declare it to be a WG Decision.
We also agreed to advance our regular meeting time for meetings after 1st November by 1 hour to track the DST switch-off in USA and Europe, so that the local time of meetings in locations where DST is ending will stay the same.
There will be no TTWG teleconference on 29th October, which is the TPAC breakouts week.
Those minutes in text format:
[1]W3C
[1] https://www.w3.org/
Timed Text Working Group Teleconference
01 October 2020
[2]Previous meeting. [3]Agenda. [4]IRC log.
[2] https://www.w3.org/2020/09/17-tt-minutes.html
[3] https://github.com/w3c/ttwg/issues/149
[4] https://www.w3.org/2020/10/01-tt-irc
Attendees
Present
Andreas, atsushi, Cyril, Gary, Mike, Nigel, Pierre
Regrets
-
Chair
Gary, Nigel
Scribe
Cyril
Contents
1. [5]this meeting
2. [6]TTML2 2nd Ed
3. [7]Virtual TPAC 2020 Planning
4. [8]TTML Profiles Registry
5. [9]Adopt /history in place of Previous Version for all
future publications #145
6. [10]AOB - DST switch
7. [11]Summary of resolutions
Meeting minutes
this meeting
nigel: we have a placeholder for the IR of TTML2 2nd Ed IR
… we have our fun issue of tts:direction
… next call is dedicated to that particular issue
… then TPAC planning is getting close
… then we have an agenda item for TTML Profile Registry
… but we haven't got the PR to process
Mike: the PR you did nigel was more important
… I see the issue that I have useful but not critical, I will
get to it
nigel: we could decide to publish without waiting
Mike: I'll support that
nigel: I made a proposal a few weeks back about the header
matter that we use and the use of /history
… it got thumbs ups but I want to turn it into a call for
consensus
nigel: in AOB, we have a DST switch soon
… I made a proposal
… anything else
… ?
… no, let's move on
TTML2 2nd Ed
nigel: Glenn updated the IR earlier in the week
… sharing that his implementation passes all the validation
tests
… he's moving on to the presentation tests next
… that's 1 implementation
… I don't know what's the likelihood of having a 2nd
implementation
… it's getting to the point where we need to look into it
… I encourage everybody to look into that
… we'll review in 2 meetings
… there is a placeholder for tts:direction and tts:writingMode
pal: I read the entire thread
… and it comes down to the statement from Glenn
… that it cannot be mapped to CSS
… I'm preparing an example and if I'm proven wrong we can move
on
cyril: I have a conflict next week
pal: I don't think it's going to work
nigel: not ideal ...
pal: we could push it back
nigel: I wondered if it was a topic to raise in the joint call
with CSS
… they've thought about it carefully and we need to understand
it
cyril: Glenn's presence is more important than mine
atai: AFAIK, pierre's goal was to reach a conclusion next week
… if you agree that we can have a tentative conclusion
… we should get an agreement with those in the call next week
nigel: we'll discuss with whoever is available next week
… and then discuss it with CSS
pal: I think without cyril present we won't be able to reach a
conclusion
cyril: I'm sure you can reach a decision without me
pal: the results of the discussion will likely be implemented
in imsc.js
… and I wouldn't want your colleagues to say they disagree with
it
nigel: it is a complicated area that needs careful thought
… we need to unpack and understand why we are doing things
differently from CSS
Virtual TPAC 2020 Planning
nigel: we need to solidify the set of topics we want to discuss
in our joint meetings
… the APA discussion, they've invited us to that, so they will
lead the discussion, we don't need to drive the agenda
… the CSS discussion, we have issue 140
… we've got the viewport unit issue in WebVTT
… and I will add TTML2 1211
… if anybody has any others, please add them in the next few
days to issue 140
… and finally, we are tracking the joint meeting with MEIG and
Media WG
… with issue 139
… the agenda for that is not yet there?
… there are 6 chairs
… we will need to select 1 chair driving the meeting
… and we need the chairs to come up with an agenda
nigel: I discussed with Chris and it's my job to distribute the
information to this group
… I don't have an opinion about which chair should do it
… there are many joint meetings going on and not much for us
… happy if any chair steps in
… we scheduled that for 2h
… we expect several topics: data cue, text track cue end time,
text track cue HTML api ...
… when there is api changes, we need to decide which group
should do
… and given that we don't do much APIs, I think it'd be better
done in the Media WG
… the other topic is exposing cues through MSE
… that's all from memory, let me confirm
… anything else?
… we don't have a group meeting scheduled at TPAC
cyril: we meet every week, TPAC or not TPAC
nigel: I have created issues for meetings on the 15th and 22nd
… for regular calls
<atsushi> summary on joint at [12]https://github.com/w3c/ttwg/
issues/141
[12] https://github.com/w3c/ttwg/issues/141
nigel: but it does not mean we need to have them if they clash
with other TPAC meetings
… if anybody has any clash, that's fine, let me know
… I'm proposing that the week of the TPAC breakout session, our
meeting will clash and it's the week of the DST transition
… I'm proposing that we don't hold our meeting
cyril: fine with me
TTML Profiles Registry
nigel: the situation is: we have no open PR, we have 1 issue
about the wrong edition of TTML1 being cited, there is a respec
warning on the editor's draft
… because the version of respec has been deprecated
… and there is the other issue from Mike, about the MIME codecs
parameters from ISOBMFF
… my proposal is to fix the edition and respec version
… and then publish the result of that as a new WG note
Mike: good to me
nigel: I will do the tweaks first and do the CfC over the
reflector
Mike: they are clearly editorial, we could start the clock
today
nigel: indeed
… just looked at the issue again, do we need to make that
change (issue #77 in TTWG)
… the text in the profile registry under media type
registration says : this updated registration supercedes the
one in TTML1 1st ed after updated by TTML1 2nd ed
… the text is actually factually accurate
… however there is a reference from the profile parameter to
the ttp:profile attribute
… and that should be updated to point to the 3rd edition
<nigel> > This updated definition supersedes the initial
registration information specified in [TTML1-1e], Appendix C,
as updated by [TTML1-2e], Appendix C.
Mike: the sentences that say "this text ought to be other there
..." is not relevant anymore
… it doesn't matter any more
… maybe then that is less editorial
nigel: we did not make normative change so far, so no need to
republish with IANA
… if we do change this, there would be extra work
… I'm inclined to say that this is not so important
… we could publish without making this change
Mike: yes
… the changes we made are important
… we need to publish soon
nigel: agree
PROPOSAL: we publish the current ED of TTML Profiles Registry
as a WG Note subject to editorial changes (e.g. update ReSpec)
nigel: any questions? comments? objections? approvals?
Mike: I support it
cyril: +1
<atsushi> +1
<atai> +1
Resolution: we publish the current ED of TTML Profiles Registry
as a WG Note subject to editorial changes (e.g. update ReSpec)
nigel: we have a decision policy, 2 week period, if no
objection, that resolution is a WG decision and we'll hand over
to Atsushi
Adopt /history in place of Previous Version for all future
publications #145
github: [13]https://github.com/w3c/ttwg/issues/145
[13] https://github.com/w3c/ttwg/issues/145
nigel: we have 2 thumbs up and it is my proposal
… it's about changing the header matter
… instead of having 'previous' link, we'll have a static link
… you'll be able to see the different editions, CR, PRs ...
… I'd like to propose that we do across every document we
publish under /TR
… that is my proposal
… opened on Aug 20
… I would like to do a CfC now
… if there is no objection in 2 weeks, we'll have a decision
<atsushi> [14]https://www.w3.org/TR/css-text-4/
[14] https://www.w3.org/TR/css-text-4/
atsushi: in some cases, for ex CSS, it lists multiple previous
versions in the header part
… but usually we juste have only 1 previous version in our
publications in TR space
… it's replacing this with /history link
SUMMARY: this proposal becomes a decision if no objection
received by Oct 15th
AOB - DST switch
nigel: the plan is not to have a meeting on the 29th of october
… then on the 1st of nov, the DST switch happens in the US
… neither Europe nor USA will be in DST
… the person affected most is Atsushi
… because you don't have DST
atsushi: Europe change happens Oct 25th
… US on Nov 1st
… there is no meeting on 29th
cyril: the question is what is the time after everybody has
switched
atsushi: I prefer alignment with DST
<atai> +1
nigel: the proposal is that for our meetings after Nov 1st, we
keep the same local time in US and Europe
<atai> +1
nigel: this would make it 1h later in Japan
nigel: no objections
… the UTC time of the meeting will change, to be 1h later
Mike: it's much clearer to say we are locked to Boston time
nigel: I completely disagree on how to phrase it
Mike: as you wish
nigel: the effect on us all is that it's going to be the same
exact time for all of us except Atsushi
nigel: meeting adjourned
Summary of resolutions
1. [15]we publish the current ED of TTML Profiles Registry as
a WG Note subject to editorial changes (e.g. update ReSpec)
Minutes manually created (not a transcript), formatted by
[16]scribe.perl version 123 (Tue Sep 1 21:19:13 2020 UTC).
[16] https://w3c.github.io/scribe2/scribedoc.html
Received on Thursday, 1 October 2020 16:47:44 UTC