Re: {agenda} TTWG Meeting 2017-10-05

Hi Nigel,

Below are a couple of IMSCvNEXT-related topics:

- FPWD of IMSCvNEXT
- liaison to external organizations re: IMSCvNEXT
- questions raised by Mike Dolan
(https://lists.w3.org/Archives/Public/public-tt/2017Oct/0023.html)
    - deprecation of IMSC1 features such as smpte:backgoundImage
    - replacing references from TTML1 to TTML2

Best,

-- Pierre

On Tue, Oct 3, 2017 at 10:13 AM, Nigel Megitt <nigel.megitt@bbc.co.uk> wrote:
> This meeting is scheduled for up to 120m. Please be ready for a prompt start
> at 10:03am Boston time.
>
> We have a lot to cover, including IMSCvNext requirements, TTML2 wide review
> comments and WebVTT wide review comments so we are likely to use the whole 2
> hours.
>
> Our teleconference is scheduled with reference to Boston Time, the correct
> time of this teleconference in your locale may change.
>
> Check
> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171005T10&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. TPAC advanced planning
> 2. TTML2 Wide & Horizontal Review
> 3. IMSC including vNext requirements
> 4. TTML issue assignment and progress tracking
> 5. TTML1 & TTML2 issues, actions, PRs, editorial actions etc
> 6. WebVTT feedback (David Singer to Chair if present)
> 7. HDR in PNG (placeholder)
> 8. Progress on HTMLCue proposal (placeholder)
> 9. AOB – please notify of any other AOB now!
>
>
>
> Reminder re future milestones and meetings:
>
> October meetings:
>
> Thursday 12th October: TTWG phone meeting 2 Hour(s)
> Thursday 19th October: TTWG phone meeting ? Hour(s)
> Thursday 26th October: TTWG phone meeting ? Hour(s)
>
> 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
>
> Further ahead:
>
> Thursday 2nd November TTWG phone meeting 2 Hours (finalise TPAC agenda)
> Thursday 9th November: TTWG Face to Face meeting at TPAC
> Friday 10th November: TTWG Face to Face meeting at TPAC
> Thursday 16th November: TTWG phone meeting ? Hour(s)
> Thursday 23rd November: TTWG phone meeting ? Hour(s)
> Thursday 30th November: TTWG phone meeting ? Hour(s)
>
> Agenda+ TPAC 2017 Advanced planning
>
> Please be ready to discuss TPAC scheduling of agenda items
>
> W3C TPAC 2017 event page: https://www.w3.org/2017/11/TPAC/Overview.html
> TTWG TPAC2017 wiki page: https://www.w3.org/wiki/TimedText/tpac2017
>
> I have requested a Polycom phone and flipchart.
>
> We will jointly meet the Web & TV IG on the Monday, and have invited CSS WG
> to attend our meeting on the Friday, times to be confirmed.
>
> Agenda+ TTML2 Wide and Horizontal Review
>
> All TTML2 Wide Review comments are now on the TTML2 GitHub repository with
> links to the comment emails, and are labelled appropriately. Thank you
> Thierry!
>
> ID State Title Person Due Date Associated with
> ACTION-506 open Draft a wiki page explaining our review and disposition
> steps and labels Thierry Michel 2017-09-21
>
> Collate list of the issues we want to open with CSS WG
>
> Minutes from CSS WG Paris F2F that Nigel attended remotely on Friday 4th
> August: https://lists.w3.org/Archives/Public/www-style/2017Sep/0000.html
> This is at https://www.w3.org/wiki/TTML/CSSRequirements
> The CSS WG has been invited to meet us at TPAC on the Friday.
> We also need to explain what the use case is for the features, rather than
> just each styling feature itself.
>
> TAG design review issue: https://github.com/w3ctag/design-reviews/issues/138
>
> CSS Review of TTML2, threads: FW: TTML2 horizontal review with CSS and Fwd:
> Subtitle/caption styling + TTML + CSS
>
> Internationalisation review by r12a has generated several 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 When can we schedule a review and gather feedback?
>
>
> Agenda+ IMSC (now incorporates Unicode ticket)
>
> ID State Title Person Due Date Associated with
> ACTION-507 open Add imsc vnext repo to agenda, board, github-bot etc Nigel
> Megitt 2017-10-05
>
> IMSC Tests released as v1.0.0 at
> https://github.com/w3c/imsc-tests/releases/tag/v1.0.0 .
>
> IMSC 1.0.1
> IMSC 1.0.1 CR published at
> https://www.w3.org/TR/2017/CR-ttml-imsc1.0.1-20170713/
> IMSC 1.0.1 Implementation report at
> https://www.w3.org/wiki/TimedText/IMSC1_0_1_Implementation_Report
> 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.
> IMSC Tests repository: https://github.com/w3c/imsc-tests
>
> vNext Requirements
>
> IMSCvNext Requirements editor's draft:
> https://w3c.github.io/imsc-vnext-reqs/
> IMSCvNext Requirements repository: https://github.com/w3c/imsc-vnext-reqs
>
> 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 IMSC pull requests: None
>
> Open IMSC pull requests: None
>
> New or discussed IMSC issues: None
>
> Closed IMSC issues: None
>
> Merged IMSC Tests pull requests: None
>
> Open IMSC Tests pull requests: None
>
> New or discussed IMSC Tests issues: None
>
> Closed IMSC Tests issues: None
>
> Merged IMSCvNext pull requests: None
>
> Open IMSCvNext pull requests: None
>
> New or discussed IMSCvNext issues:
>
> Is #textEmphasis necessary, or is #textEmphasis-minimal sufficient?
> Is #ruby necessary, or #ruby-non-nested sufficient?
>
> Closed IMSCvNext issues: None
>
> Agenda+ TTML issue assignment and progress tracking (20 minutes maximum)
>
> We have now published the WD for WR however there are still many issues
> open, and we intend also to apply multiple fixes as already agreed for
> TTML1.
>
> At the moment of writing this agenda, there are:
>
> TTML1 issues:
>
> 3 open issues with no milestone, none marked as discussed and agreed
> 37 open issues in "3rd Ed" milestone, 15 marked as discussed and agreed
> 11 open issues in "3rd Ed Test Suite" milestone, none marked as discussed
> and agreed
>
> TTML2 issues:
>
> 2 open issues on the Editor's CR Work List milestone, none of which has a PR
> and both of which are horizontal review comments marked WR-pending;
> 101 open issues with no milestone, none of which has a PR open label.
>
>
> Agenda+ TTML1 & TTML2 issues, actions, PRs, editorial actions etc
>
> Actions:
> ID State Title Person Due Date Associated with
> ACTION-443 open Prepare a document showing mapping arib ruby extension
> features to ttml2 for use as a liaison document to arib. Glenn Adams
> 2016-08-26 TTML2
> ACTION-462 open Create issue on ttml2 to add "mapping from other versions
> and profiles of ttml" Glenn Adams 2016-04-28 TTML2
>
> Most recent WD published at https://www.w3.org/TR/2017/WD-ttml2-20170630/
>
> Merged TTML1 Pull Requests: None
>
> Merged TTML2 Pull Requests: None
> Open TTML1 Pull Requests: None
>
> Open TTML2 Pull Requests: None
> New TTML1 Issues: None
>
> New TTML2 Issues:
>
> Definition of ttp:activeArea does not match ittp:activeArea defined in
> IMSC1.0.1.
> Definition of tts:fillLineGap does not match itts:fillLineGap as specified
> in IMSC 1.0.1.
> Feature #textOutline should be specified as a union of #textOutline-blurred
> and #textOutline-unblurred.
> Feature #writingMode should be specified as the union of
> #writingMode-vertical and #writingMode-horizontal.
> Content Profile Semantics (5.2.4.2) refers to
> ttp:contentProfiles="any(...)".
> Definition of [construct effective content profile] does not take into
> account `ttp:profile` attribute value.
> Specification of ttp:contentProfileCombination does not specify an
> initial/default value.
> Is ttp:version="2" required if ttp:contentProfiles is present?
> Definition of [external data resource] does not include src attribute on
> image element.
> Change summary not up to date.
> Duplicated text for attributes in TT Style Namespace.
> Foreign namespace elements not reflected in syntax.
> Condition attribute missing in Core catalog.
> Clarify use of whitespace in style attribute values.
> Make backward compatibility normative.
> Support for roll-up and paint-on captions.
>
> Change styling to use CSS.
>
> [ttml2] TTML2 wide review comment: styling
>
> 3GPP review of TTML2
>
> ITU-T Group 16 IPTV r review of TTML2
>
> CTA r review of TTML2
>
> DASH-IF review of TTML2
>
> ISO JTC1/SC 29 review of TTML2
>
> ARIB review of TTML2
>
> SMPTE response as TTML2 review
>
> Closed TTML1 Issues:
>
> Unspecified font size can't fit a region extent if it's specified in pixels
>
> Closed TTML2 Issues:
>
> Review by APA WG.
>
> Discussed TTML1 Issues: None
> Discussed TTML2 Issues:
>
> Privacy review umbrella issue
>
>
> Focus topic(s) for this week
>
> Issues
>
> Iterate through open issues with no PR – decide action to take on each, e.g.
> defer to CR, defer to TTML.next, close etc.
>
> If there are any issues that we decide need to be resolved before WR a
> proposal for the fix is needed ASAP (basically, it's too late already unless
> it can easily be agreed by the group).
>
>
> 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+ WebVTT review feedback
>
> ID State Title Person Due Date Associated with
> ACTION-396 open Produce evidence of request for wide review for webvtt, for
> the archive David Singer 2015-04-17 WebVTT 1.0
> ACTION-502 open Explain to david that we need a more consistent disposition
> of comments for webvtt. Thierry Michel 2017-08-10 WebVTT 1.0
>
>
> Discussion on WebVTT review feedback and next steps.
>
> What are the WG's views on the dispositions generated by the CG?
>
> Resolve to publish a new WD? (not strictly necessary)
>
> WebVTT Wide review wiki page: https://www.w3.org/wiki/WebVTT_Wide_Review
>
> Open Pull requests:
>
> Fix #270: Add classes to specify text color
>
> Clarify the "WebVTT cue settings list" definition.
>
> Add a "User agents that do not support CSS" conformance class.
>
> Move definition of chapter title text
>
> Merged Pull requests:
>
> Update editor
> Add Silvia as editor
>
> New issues:
>
> Wide Review Comment 2017: serialisation and parsing
> Wide Review Comment 2017: Content signalling
> Wide Review Comment 2017: Timing
> Wide Review Comment 2017: Timestamp syntax
> Wide Review Comment 2017: default font size and line heights
> Wide Review Comment 2017: default background colour
> Wide Review Comment 2017: future styling options mechanism
> Wide Review Comment 2017: No style property list for ::cue-region
> Wide Review Comment 2017: position and size reference is video or video
> viewport?
> Wide Review Comment 2017: positioning with cue box vs region
> Wide Review Comment 2017: Positioning - are region height and width used?
> Wide Review Comment 2017: Use of lines as positioning constructs
> Wide Review Comment 2017: unspecified edge margins make accurate positioning
> impossible
> Wide Review Comment 2017: Metadata delimiters
> Wide Review Comment 2017: hard to understand because of terminology
> Wide Review Comment 2017: line cue setting direction
> Wide Review Comment 2017: positioning model
> Wide Review Comment 2017: Algorithmic specification
> Wide Review Comment 2017: formatting issues
> Change alt text for region diagram
>
> Closed issues: None
>
> Recently discussed issues:
>
> Wide Review Comment 2017: Text color must be mandatory
> Wide Review Comment 2017: Chapter location for defining WebVTT chapter title
> text
> Need tests for :cue-region(id) pseudo-class
> Wide Review Comment 2017: Conformance Classes not complete
> Wide Review Comment 2017: Term "WebVTT cue settings list" defined twice
> Wide Review Comment 2017: Term definition with empty content
> Wide Review Comment 2017: Distinction between cue payload types
>
>
> Agenda+ HDR in PNG [placeholder agenda item]
>
> We published this Note at https://www.w3.org/TR/png-hdr-pq/ (republished
> 25th July incorporating fix for typo)
>
> Repo for PQ HDR in PNG: https://github.com/w3c/png-hdr-pq
> Draft WG Note: https://w3c.github.io/png-hdr-pq/
>
> Merged pull requests: None
>
> Open pull requests: None
>
> New or discussed issues: None
>
> Closed issues: None
>
> Agenda+ HTMLCue proposal progress update. [placeholder agenda item]
>
>
> ID State Title Person Due Date Associated with
> ACTION-441 open Kick off the analysis work on the vttcue carrying html idea.
> 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? email from 2016-09-06.
>
> See also the notes from the TAG meeting (see agenda item above) at which the
> inability to instantiate TextTrackCue objects in most browsers was
> mentioned.
>
>
>
> 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.
>
> ---------------------

Received on Tuesday, 3 October 2017 17:21:35 UTC