RE: {agenda} TTWG Meeting 2017-03-23

Regrets

From: Nigel Megitt [mailto:nigel.megitt@bbc.co.uk]
Sent: Tuesday, March 21, 2017 10:48 AM
To: Timed Text Working Group <public-tt@w3.org>
Subject: {agenda} TTWG Meeting 2017-03-23

This meeting is scheduled for up to 60m. Please be ready for a prompt start at 10:03am Boston time.

As agreed on March 2, during March we will begin at the "old" time of 10am Boston.

Our teleconference is scheduled with reference to Boston Time, the correct time of this teleconference in your locale may change.

Note that DST has now come in for the US, please check the following link!
Check https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170323T10&p1=43


Thursdays 10:03am-12:00pm Boston local

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)

Agenda+ Assign Roles

Chairs: Nigel Megitt

Scribe: usually Nigel – open to offers!

Regrets: none

Activity since last meeting:
See individual agenda items for recent activity on specific products

Cross-product TTWG board: http://www.w3.org/AudioVideo/TT/board/

We are still using tracker for actions unrelated to issues.
Please do not add or modify issues in tracker!

IMSC: https://github.com/w3c/imsc/pulse

TTML1: https://github.com/w3c/ttml1/pulse
TTML2: https://github.com/w3c/ttml2/pulse

TTML Profile Registry: https://github.com/w3c/tt-profile-registry/pulse

TTML-WebVTT mapping: https://github.com/w3c/ttml-webvtt-mapping/pulse

WebVTT: https://github.com/w3c/webvtt/pulse


Agenda+ Prioritise discussion for this meeting and look ahead

Check-point for order of topics – I'd suggest, subject to reordering:
1. TTML issues, actions, etc
2. IMSC
3. Progress on HTMLCue proposal (placeholder)
4. WebVTT comments (placeholder)
5. AOB – please notify of any other AOB now!


Reminder re future milestones and meetings:

March Meetings:

Thursday 30th March: TTWG phone meeting 2 hours

Further ahead:

Thursday 6th April: TTWG phone meeting 2 Hours (Nigel away)
Thursday 13th April: TTWG phone meeting 2 Hours
Thursday 20th April: TTWG phone meeting 2 Hours
Thursday 27th April: TTWG phone meeting 2 Hours

IMSC 2 and TTML2 publication events: see the timeline of upcoming work at https://www.w3.org/wiki/TimedText/Publications#Timeline_of_TTML2_and_IMSC2_work



Agenda+ TTML1 & TTML2 issues, actions, PRs, editorial actions etc

Horizontal Review:

CSS Review of TTML2, threads: FW: TTML2 horizontal review with CSS<https://lists.w3.org/Archives/Public/public-tt/2016Dec/0013.html> and Fwd: Subtitle/caption styling + TTML + CSS<https://lists.w3.org/Archives/Public/public-tt/2016Dec/0019.html>

Internationalisation review by r12a has generated several new issues on TTML2 and comments on existing issues (see below), this week mainly about alignment with relatively recent CSS developments.

CSS 2.2 request for reviews from TTWG et al: Pre-announcement of CR for CSS 2.2 & request for reviews<https://lists.w3.org/Archives/Public/public-tt/2016Dec/0017.html> When can we schedule a review and gather feedback?

Actions:
ID

State

Title

Person

Due Date

Associated with

ACTION-443<https://www.w3.org/AudioVideo/TT/tracker/actions/443>[(edit)]<https://www.w3.org/AudioVideo/TT/tracker/actions/443/edit>

open

Prepare a document showing mapping arib ruby extension features to ttml2 for use as a liaison document to arib.<https://www.w3.org/AudioVideo/TT/tracker/actions/443>

Glenn Adams

2016-08-26

TTML2<https://www.w3.org/AudioVideo/TT/tracker/products/4>

ACTION-462<https://www.w3.org/AudioVideo/TT/tracker/actions/462>[(edit)]<https://www.w3.org/AudioVideo/TT/tracker/actions/462/edit>

open

Create issue on ttml2 to add "mapping from other versions and profiles of ttml"<https://www.w3.org/AudioVideo/TT/tracker/actions/462>

Glenn Adams

2016-04-28

TTML2<https://www.w3.org/AudioVideo/TT/tracker/products/4>


Most recent WD published at https://www.w3.org/TR/2017/WD-ttml2-20170106/

Merged Pull Requests: None
Open TTML1 Pull Requests:
Clarify application of padding (#221)<https://github.com/w3c/ttml1/pull/233>
Open TTML2 Pull Requests:
Issue 0203 add examples of ja features part 2<https://github.com/w3c/ttml2/pull/273>
New TTML1 Issues: none
New TTML2 Issues: none
Closed TTML1 Issues: none
Closed TTML2 Issues:
Use of offset-time expression in smpte mode<https://github.com/w3c/ttml2/issues/160>
3D and images<https://github.com/w3c/ttml2/issues/239>
Inline space.<https://github.com/w3c/ttml2/issues/53>
Discussed TTML1 Issues: none
Discussed TTML2 Issues:
<emphasis-position> vs CSS text-emphasis-position + Mongolian<https://github.com/w3c/ttml2/issues/240>
Specify date as well as hours, minutes and seconds in time expressions<https://github.com/w3c/ttml2/issues/96>
Default ruby position may be on the wrong side for tblr (eg. mongolian)<https://github.com/w3c/ttml2/issues/254>


Focus topic(s) for this week

Internationalisation

Richard Ishida has kindly offered to join us for discussion of the following two issues:

Issue #240 <emphasis-position> vs CSS text-emphasis-position + Mongolian <https://github.com/w3c/ttml2/issues/240> Can we agree on the best initial value for text emphasis position?

Issue #254 Default ruby position may be on the wrong side for tblr (eg. mongolian) <https://github.com/w3c/ttml2/issues/254>  Following #240, same question

Issue #253 Support for bopomofo ruby needed <https://github.com/w3c/ttml2/issues/253> Do we have enough data to decide whether or not we need to support this in TTML2?

There may be other internationalisation (i18n) issues that we can usefully introduce or discuss while Richard is on the call, but these are the ones that have been specifically requested for discussion.

For example the treatment of orientation and vertical text handling is also touched by TTML2 issues #281, #280 and #277 as well as #230 The term "vertical scripts" needs formal definition. <https://github.com/w3c/ttml2/issues/230>

There are a large number of ruby related issues too. I doubt we can tackle them all in the meeting; thoughts on how best to cover them all would be useful, other than "one by one" obviously!

Other stuff

Inclusion of foreign namespace elements – is it only permitted on metadata elements, or anywhere? Do we need additional conformance language? See also IMSC issue foreign namespace usage is underspecified<https://github.com/w3c/imsc/issues/213>

TTML1 Clarification of padding pull request Clarify application of padding (#221)<https://github.com/w3c/ttml1/pull/233>


Current open issues: https://github.com/w3c/ttml1/issues and https://github.com/w3c/ttml2/issues

See spreadsheet of editorial actions at https://github.com/w3c/ttml2/blob/master/spec/ednotes.xlsx

Edit/build instructions now in README in ttml2/spec/ at https://github.com/w3c/ttml2/blob/master/spec/README.md



Agenda+ IMSC (now incorporates Unicode ticket)

Last week we set some actions for publishing the WD for Wide Review + Horizontal Review: have we published it? Are there any last decisions that need to be made?

IMSC 1.0.1 FPWD published at https://www.w3.org/TR/ttml-imsc1.0.1/

IMSC 1 Rec available at https://www.w3.org/TR/2016/REC-ttml-imsc1-20160421/

Patent policy call for exclusions sent 2017-02-03, archived at https://lists.w3.org/Archives/Public/public-tt/2017Feb/0006.html


Editor's draft is directly viewable at http://w3c.github.io/imsc/imsc1/spec/ttml-ww-profiles.html

IMSC Implementation Page: https://www.w3.org/wiki/TimedText/IMSC1_implementation_page.


Unicode CLDR discussion
Unicode ticket is at http://unicode.org/cldr/trac/ticket/8915

Pierre's response to the recent update is at http://unicode.org/cldr/trac/ticket/8915#comment:9

Email response from Shervin at Unicode https://lists.w3.org/Archives/Public/public-tt/2016Dec/0018.html


Merged pull requests: Add Security and Privacy section<https://github.com/w3c/imsc/pull/220>
Open pull requests: None
New or discussed issues:
Attribute syntax definition: missing spaces<https://github.com/w3c/imsc/issues/221>
First Pass at IMSC2 to CSS Fallback<https://github.com/w3c/imsc/issues/218>
Closed issues: Add a Security and Privacy section<https://github.com/w3c/imsc/issues/219>


Agenda+ HTMLCue proposal progress update.

ID

State

Title

Person

Due Date

Associated with

ACTION-441<https://www.w3.org/AudioVideo/TT/tracker/actions/441>[(edit)]<https://www.w3.org/AudioVideo/TT/tracker/actions/441/edit>

open

Kick off the analysis work on the vttcue carrying html idea.<https://www.w3.org/AudioVideo/TT/tracker/actions/441>

Andreas Tai

2015-11-05


See https://lists.w3.org/Archives/Public/public-tt/2016Apr/0012.html for further information on this, this week.

Also HTML import and HTMLCue?<https://lists.w3.org/Archives/Public/public-tt/2016Sep/0003.html> email from 2016-09-06.

[placeholder agenda item]

Agenda+ WebVTT review feedback

ID

State

Title

Person

Due Date

Associated with

ACTION-396<https://www.w3.org/AudioVideo/TT/tracker/actions/396>[(edit)]<https://www.w3.org/AudioVideo/TT/tracker/actions/396/edit>

open

Produce evidence of request for wide review for webvtt, for the archive<https://www.w3.org/AudioVideo/TT/tracker/actions/396>

David Singer

2015-04-17

WebVTT 1.0<https://www.w3.org/AudioVideo/TT/tracker/products/8>


Discussion on WebVTT review feedback and next steps.

WebVTT Wide review wiki page: https://www.w3.org/wiki/WebVTT_Wide_Review


Open Pull requests:
Disallow external resources from data: URL resources in STYLE<https://github.com/w3c/webvtt/pull/343>
Drop line: and position: settings with invalid linealign/colalign<https://github.com/w3c/webvtt/pull/337>
Add requirements for region identifier to exist.<https://github.com/w3c/webvtt/pull/201>
Merged Pull requests: None
New issues:
webvtt-cue-timestamp, ">" character is mandatory?<https://github.com/w3c/webvtt/issues/342>
Closed issues: None
Recently discussed issues: None

Agenda+ AOB

References

Wiki http://www.w3.org/wiki/TimedText





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

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.

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