Wednesday, 27 August 2014
- ISSUE-341: ambiguous definition for determination of descendant region identifier [TTML 1.0]
- ISSUE-340 (profile designator clarification): Make clear that the use of the ttp:profile attribute is not required. [TTML IMSC 1.0]
- ISSUE-339 (allow #overflow): Allow the use of #overflow [TTML IMSC 1.0]
Tuesday, 26 August 2014
Thursday, 21 August 2014
- RE: EBU liaison re IMSC 1 timeline
- {minutes} TTWG Meeting 21/8/2014
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
Wednesday, 20 August 2014
Tuesday, 19 August 2014
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- Re: FYI - Media Accessibility User Requirements WD
- FYI - Media Accessibility User Requirements WD
- DECE liaison re IMSC 1 timeline
- EBU liaison re IMSC 1 timeline
- SMPTE liaison re IMSC 1 timeline
Monday, 18 August 2014
Friday, 15 August 2014
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- ISSUE-337 (Update for TTML2): Update SDP-US for TTML2 [TTML Simple Delivery Profile for Closed Captions (US)]
Thursday, 14 August 2014
- {minutes} TTWG Meeting 14/8/2014
- ISSUE-336 (aspectRatio syntax): Syntax definition missing from ittp:aspectRatio [TTML IMSC 1.0]
- ISSUE-335 (Negative times for offsets): In order to handle offsets between start time in TTML docs and start time in video, allow negative times to be used in fragment begin times. [TTML.next]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: New Change Proposal 28 on IMSC 1: Profile refactoring
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: New Change Proposal 28 on IMSC 1: Profile refactoring
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
Wednesday, 13 August 2014
- Re: Problem with TPAC 2014 Registration
- Re: Problem with TPAC 2014 Registration
- Re: Problem with TPAC 2014 Registration
- Re: Problem with TPAC 2014 Registration
- Re: Problem with TPAC 2014 Registration
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- {agenda} TTWG Meeting 14/8/2014
- TTML2 timeline (ACTION-309)
- Re: ISSUE-334: Misuse of style property characteristics with ttp:progressivelyDecodable [TTML IMSC 1.0]
- ISSUE-334: Misuse of style property characteristics with ttp:progressivelyDecodable [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: Problem with TPAC 2014 Registration
- Problem with TPAC 2014 Registration
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-330 (Is Presented Region a synonym for temporally active region?): Is Presented Region a synonym for temporally active region? [TTML IMSC 1.0]
- Re: ISSUE-330 (Is Presented Region a synonym for temporally active region?): Is Presented Region a synonym for temporally active region? [TTML IMSC 1.0]
Tuesday, 12 August 2014
- Re: ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0]
- Re: ISSUE-311 (Note on progressivelyDecodable): Note on progressivelyDecodable is not a sentence [TTML IMSC 1.0]
- Re: ISSUE-330 (Is Presented Region a synonym for temporally active region?): Is Presented Region a synonym for temporally active region? [TTML IMSC 1.0]
Monday, 11 August 2014
- RE: Upcoming F2F Attendee Details
- Re: Upcoming F2F Attendee Details
- RE: Upcoming F2F Attendee Details
- Re: Upcoming F2F Attendee Details
Saturday, 9 August 2014
Friday, 8 August 2014
- Re: Question about ttml times
- ISSUE-333: use of application default frameRateMultipler, subFrameRate [TTML 1.0]
- Question about ttml times
- New Change Proposal 28 on IMSC 1: Profile refactoring
- Re: {minutes} TTWG Meeting 7/8/2014
Thursday, 7 August 2014
- Re: {minutes} TTWG Meeting 7/8/2014
- {minutes} TTWG Meeting 7/8/2014
- ISSUE-332 (-): #cellResolution support [TTML IMSC 1.0]
Wednesday, 6 August 2014
Monday, 4 August 2014
- Re: ACTION-318: Draft note wording for imsc conformance
- Re: ACTION-318: Draft note wording for imsc conformance
Saturday, 2 August 2014
- Re: ACTION-318: Draft note wording for imsc conformance
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
Friday, 1 August 2014
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ACTION-318: Draft note wording for imsc conformance
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ACTION-318: Draft note wording for imsc conformance
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- Re: ACTION-318: Draft note wording for imsc conformance
- ISSUE-331 (forcedDisplay region background note): An advisory note on the use of backgrounds on regions in combination with forcedDisplay [TTML IMSC 1.0]
- ACTION-318: Draft note wording for imsc conformance
- ACTION-315 and ACTION-317