public-tt@w3.org from May 2014 by date

Friday, 30 May 2014

• Re: {minutes} TTWG Meeting 29/5/2014 Pierre-Anthony Lemieux
• Re: {minutes} TTWG Meeting 29/5/2014 Glenn Adams

Thursday, 29 May 2014

• Re: {minutes} TTWG Meeting 29/5/2014 Silvia Pfeiffer
• {minutes} TTWG Meeting 29/5/2014 Nigel Megitt
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Glenn Adams

Wednesday, 28 May 2014

• {agenda} TTWG Meeting 29/5/2014 Nigel Megitt

Tuesday, 27 May 2014

• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-312 (forcedDisplay should be in ttm): forcedDisplay attribute is metadata so should be in ttm not tts namespace [TTML IMSC 1.0] Nigel Megitt

Saturday, 24 May 2014

• [ttml2] expressing feature/extension restriction/extension Glenn Adams
• ISSUE-321: typo - s/ttp:feature/ttp:extension/ in 5th paragraph of 6.1.5 [TTML 1.0 (Editorial)] Timed Text Working Group Issue Tracker
• Re: ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Glenn Adams
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Glenn Adams
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Glenn Adams

Friday, 23 May 2014

• Re: ISSUE-312 (forcedDisplay should be in ttm): forcedDisplay attribute is metadata so should be in ttm not tts namespace [TTML IMSC 1.0] Glenn Adams
• Re: ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Pierre-Anthony Lemieux
• Re: ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Pierre-Anthony Lemieux
• RE: ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Michael Dolan
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Pierre-Anthony Lemieux
• ISSUE-320 (Is normative SMPTE 2052 reference okay?): Is normative SMPTE 2052 reference okay? [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt
• RE: ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Michael Dolan
• RE: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Michael Dolan
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Nigel Megitt
• RE: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Michael Dolan
• ISSUE-319 (HRM should be a processor compliance test): HRM should be a processor compliance test and allow different levels of complexity for different use cases [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• Update to ISSUE-305 Nigel Megitt
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt

Thursday, 22 May 2014

• RE: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Michael Dolan
• RE: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Michael Dolan
• Re: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Nigel Megitt
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt
• RE: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Michael Dolan
• Re: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Nigel Megitt
• {minutes} TTWG Meeting 22/5/2014 Nigel Megitt
• RE: ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Michael Dolan
• RE: ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Michael Dolan
• ISSUE-318 (HRM glyph copy assumes no sub-pixel positioning): Hypothetical Render Model glyph copy assumes no sub-pixel positioning [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• ISSUE-317 (IMSC should not require frame alignment): IMSC should not require frame alignment [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• RE: ISSUE-309 (Image profile fails WCAG 1.2): Image profile needs to permit text equivalent [TTML IMSC 1.0] John Birch
• Re: ISSUE-309 (Image profile fails WCAG 1.2): Image profile needs to permit text equivalent [TTML IMSC 1.0] Nigel Megitt
• RE: ISSUE-309 (Image profile fails WCAG 1.2): Image profile needs to permit text equivalent [TTML IMSC 1.0] John Birch

Wednesday, 21 May 2014

• RE: ISSUE-309 (Image profile fails WCAG 1.2): Image profile needs to permit text equivalent [TTML IMSC 1.0] Michael Dolan
• RE: ISSUE-312 (forcedDisplay should be in ttm): forcedDisplay attribute is metadata so should be in ttm not tts namespace [TTML IMSC 1.0] Michael Dolan
• {agenda} TTWG Meeting 22/5/2014 Nigel Megitt
• Re: [ttml2] major update to profile related material Nigel Megitt
• Re: [ttml2] major update to profile related material Glenn Adams
• Re: ISSUE-316 (Wording if 5.2): Nigel Megitt
• ISSUE-316 (Wording if 5.2): Timed Text Working Group Issue Tracker
• ISSUE-315 (Maximum number of regions should be a processor constraint): Maximum number of regions should be a processor constraint [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• ISSUE-314 (Temporally active is not defined for regions): Temporally active is not defined for regions [TTML 1.0] Timed Text Working Group Issue Tracker
• ISSUE-313 (Presented Region is informative only): Presented Region section is informative only [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• ISSUE-312 (forcedDisplay should be in ttm): forcedDisplay attribute is metadata so should be in ttm not tts namespace [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• ISSUE-311 (Note on progressivelyDecodable): Note on progressivelyDecodable is not a sentence [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• ISSUE-310 (progressivelyDecodable needs hierarchical definition): Forward reference rule doesn't take into account child elements [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• Re: [ttml2] major update to profile related material Nigel Megitt
• RE: ISSUE-309 (Image profile fails WCAG 1.2): Image profile needs to permit text equivalent [TTML IMSC 1.0] John Birch
• Re: ISSUE-309 (Image profile fails WCAG 1.2): Image profile needs to permit text equivalent [TTML IMSC 1.0] Glenn Adams
• ISSUE-309 (Image profile fails WCAG 1.2): Image profile needs to permit text equivalent [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• [ttml2] major update to profile related material Glenn Adams

Tuesday, 20 May 2014

• Re: Draft TTML Codecs Registry - Issue-305 Cyril Concolato
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• RE: Draft TTML Codecs Registry - Issue-305 John Birch
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• RE: Draft TTML Codecs Registry - Issue-305 John Birch
• RE: Draft TTML Codecs Registry - Issue-305 John Birch
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams

Monday, 19 May 2014

• RE: Draft TTML Codecs Registry - Issue-305 Michael Dolan
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 David Singer
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• Re: Draft TTML Codecs Registry - Issue-305 David Singer
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• RE: Draft TTML Codecs Registry - Issue-305 John Birch
• RE: Draft TTML Codecs Registry - Issue-305 John Birch
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• RE: Draft TTML Codecs Registry - Issue-305 John Birch
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• RE: Draft TTML Codecs Registry - Issue-305 John Birch
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• RE: Draft TTML Codecs Registry - Issue-305 John Birch

Sunday, 18 May 2014

• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 John Birch
• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams

Friday, 16 May 2014

• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt

Thursday, 15 May 2014

• Re: Draft TTML Codecs Registry - Issue-305 Glenn Adams
• Re: Draft TTML Codecs Registry - Issue-305 Nigel Megitt
• Re: Draft TTML Codecs Registry David Singer
• RE: Draft TTML Codecs Registry Michael Dolan
• Re: Draft TTML Codecs Registry Glenn Adams
• Re: Draft TTML Codecs Registry Nigel Megitt
• Re: Draft TTML Codecs Registry Glenn Adams
• Re: Draft TTML Codecs Registry David Singer
• {minutes} TTWG Meeting 15/5/2014 Nigel Megitt
• RE: Draft TTML Codecs Registry Michael Dolan
• Re: Draft TTML Codecs Registry David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Andreas Tai
• Re: Draft TTML Codecs Registry Cyril Concolato
• Re: Draft TTML Codecs Registry Nigel Megitt
• Draft TTML Codecs Registry Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText David Singer

Wednesday, 14 May 2014

• Re: Liaison response - template on MIME type parameter for TimedText Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• {agenda} TTWG Meeting 15/5/2014 Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText David Singer

Tuesday, 13 May 2014

• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText - ISSUE 305 Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText David Singer

Monday, 12 May 2014

• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText David Singer

Sunday, 11 May 2014

• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams

Thursday, 8 May 2014

• RE: {minutes} TTWG Meeting 8/5/2014 - ISSUE-308 John Birch
• Re: {minutes} TTWG Meeting 8/5/2014 - ISSUE-308 Nigel Megitt
• RE: {minutes} TTWG Meeting 8/5/2014 John Birch
• {minutes} TTWG Meeting 8/5/2014 Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText - ISSUE-305 Nigel Megitt
• Re: {agenda} TTWG Meeting 8/5/2014 Thierry MICHEL
• Re: Liaison response - template on MIME type parameter for TimedText David Singer

Wednesday, 7 May 2014

• RE: Liaison response - template on MIME type parameter for TimedText - ISSUE-305 Michael Dolan
• {agenda} TTWG Meeting 8/5/2014 Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText - ISSUE-305 Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText Cyril Concolato
• RE: Liaison response - template on MIME type parameter for TimedText Michael Dolan
• Re: Liaison response - template on MIME type parameter for TimedText Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText Cyril Concolato

Tuesday, 6 May 2014

• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Nigel Megitt
• RE: Liaison response - template on MIME type parameter for TimedText Michael Dolan
• Re: Liaison response - template on MIME type parameter for TimedText Nigel Megitt
• RE: Liaison response - template on MIME type parameter for TimedText Michael Dolan
• Re: Liaison response - template on MIME type parameter for TimedText Nigel Megitt

Monday, 5 May 2014

• RE: Liaison response - template on MIME type parameter for TimedText Michael Dolan
• Re: Liaison response - template on MIME type parameter for TimedText Cyril Concolato

Saturday, 3 May 2014

• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• Re: Liaison response - template on MIME type parameter for TimedText Glenn Adams

Friday, 2 May 2014

• Re: Liaison response - template on MIME type parameter for TimedText David Singer
• ISSUE-308 (Related video object reference missing): It is unclear how a document is associated with a related video object [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• ISSUE-307 (Profile and conformance terminology): Conformance language and processor profile rather than content profile. [TTML IMSC 1.0] Timed Text Working Group Issue Tracker
• ISSUE-306 (Fractional time expressions in N.2 media timeBase): Appendix N.2 omits fractional time expressions [TTML 1.0] Timed Text Working Group Issue Tracker

Thursday, 1 May 2014

• Call for Exclusions: TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0 Ian Jacobs
• ISSUE-305 (Profile short names): Register of TTML profiles and short names Timed Text Working Group Issue Tracker
• {minutes} TTWG Meeting 1/5/2014 Nigel Megitt
• Re: Liaison response - template on MIME type parameter for TimedText Nigel Megitt
• [transition announcement] FPWD for "TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0" Nigel Megitt

Last message date: Friday, 30 May 2014 04:00:16 UTC