You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. This meeting 2. TTML2
2.1 Remove constraint on presence of xml:id (#989). w3c/ttml2#1162
2.2 Add informative note to tts:fontStyle recommending use of tts:shear instead of tts:fontStyle="italic" for Japanese text. w3c/ttml2#1120 3. IMSC
3.1 Add support for #font w3c/imsc#485 4. AOB – please notify of any other AOB now!
4.1 TTWG Charter status
4.2 Daylight Savings Time change
Time
15:00 - 16:00 (1 hour) UTC
Please be ready for a prompt start at 15:03am UTC time.
Our teleconference is scheduled with reference to UTC Time, the correct time of this teleconference in your locale may change.
See individual agenda items for recent activity on specific products.
See the TTWG home page for links to repositories and recent activity.
Agenda+ This meeting
Assign Roles
Chairs: Nigel Megitt
Scribe: not Cyril
Regrets:
Prioritise discussion for this meeting and look ahead
Check-point for order of topics and any other business.
Note I did not raise w3c/tt-profile-registry#71 on this agenda because I suspect that we will not have all of @mikedo , @cconcolato and @skynavga on the call - if that suspicion is wrong, we will try to cover that long-standing issue.
Agenda+ TTML2
Remove constraint on presence of xml:id (#989). w3c/ttml2#1162
Add informative note to tts:fontStyle recommending use of tts:shear instead of tts:fontStyle="italic" for Japanese text. w3c/ttml2#1120
The significant upcoming dates for our active members are:
Place
Date when DST ends
China
no DST
Europe + UK
2019-10-27
Japan
no DST
US
2019-11-03
Proposal 1: Adjust regular UTC meeting time by +1 hour (to 1600) beginning on the 2019-11-07 call.
This keeps the apparent meeting time the same in places with DST, except for the 2019-10-31 call in Europe and the UK, which would be 1 hour earlier than normal. However it means that members joining in Japan for whom the current time is already late would need to be up even later.
If we do this, and an exceptional 2 hour meeting is needed, the 2 hour meeting would begin 1 hour earlier than the usual time, and the end time would be the same.
Proposal 2: Retain current UTC time of 1500.
This makes the apparent meeting time 1 hour earlier beginning on 2019-10-31 in Europe and the UK, and beginning on 2019-11-07 in the US. For members joining in the west coast of the US, this is an early start. For members joining in Japan, it avoids a very late end to the day.
If we do this, and an exceptional 2 hour meeting is needed, the 2 hour meeting would begin at the same time as a 1 hour meeting and the end time would be extended to be an hour later.
The text was updated successfully, but these errors were encountered:
Agenda
1. This meeting
2. TTML2
2.1 Remove constraint on presence of xml:id (#989). w3c/ttml2#1162
2.2 Add informative note to tts:fontStyle recommending use of tts:shear instead of tts:fontStyle="italic" for Japanese text. w3c/ttml2#1120
3. IMSC
3.1 Add support for #font w3c/imsc#485
4. AOB – please notify of any other AOB now!
4.1 TTWG Charter status
4.2 Daylight Savings Time change
Time
15:00 - 16:00 (1 hour) UTC
Please be ready for a prompt start at 15:03am UTC time.
Our teleconference is scheduled with reference to UTC Time, the correct time of this teleconference in your locale may change.
Check https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191003T15&p1=1440
Joining details:
see https://lists.w3.org/Archives/Member/member-tt/2016Oct/0009.html
(members-only link – if you can't see this and wish to join please contact me)
Future meetings and recent activity:
See the TTWG project board for upcoming meetings.
See individual agenda items for recent activity on specific products.
See the TTWG home page for links to repositories and recent activity.
Agenda+ This meeting
Assign Roles
Chairs: Nigel Megitt
Scribe: not Cyril
Regrets:
Prioritise discussion for this meeting and look ahead
Check-point for order of topics and any other business.
Note I did not raise w3c/tt-profile-registry#71 on this agenda because I suspect that we will not have all of @mikedo , @cconcolato and @skynavga on the call - if that suspicion is wrong, we will try to cover that long-standing issue.
Agenda+ TTML2
Remove constraint on presence of xml:id (#989). w3c/ttml2#1162
Add informative note to tts:fontStyle recommending use of tts:shear instead of tts:fontStyle="italic" for Japanese text. w3c/ttml2#1120
Do we have consensus to move this to IMSC?
Agenda+ IMSC
Add support for #font w3c/imsc#485
What is the basis for measuring the size of loaded resources, relative to de-compression?
Agenda+ AOB
TTWG Charter status update
Daylight savings time changes
See https://www.timeanddate.com/time/dst/events.html for details of when DST changes in the next 4 weeks, and https://www.timeanddate.com/time/dst/2019.html for DST per country during 2019.
The significant upcoming dates for our active members are:
Proposal 1: Adjust regular UTC meeting time by +1 hour (to 1600) beginning on the 2019-11-07 call.
This keeps the apparent meeting time the same in places with DST, except for the 2019-10-31 call in Europe and the UK, which would be 1 hour earlier than normal. However it means that members joining in Japan for whom the current time is already late would need to be up even later.
If we do this, and an exceptional 2 hour meeting is needed, the 2 hour meeting would begin 1 hour earlier than the usual time, and the end time would be the same.
Proposal 2: Retain current UTC time of 1500.
This makes the apparent meeting time 1 hour earlier beginning on 2019-10-31 in Europe and the UK, and beginning on 2019-11-07 in the US. For members joining in the west coast of the US, this is an early start. For members joining in Japan, it avoids a very late end to the day.
If we do this, and an exceptional 2 hour meeting is needed, the 2 hour meeting would begin at the same time as a 1 hour meeting and the end time would be extended to be an hour later.
The text was updated successfully, but these errors were encountered: