Changelog between August 29, 2015 and September 5, 2015

Issues | Actions.

Get changelog

Issues

ISSUE-341 (open)
ISSUE-404 (pending review)
  • 2015-09-03 03:50:00:
    *<Pierre-Anthony Lemieux> Created issue 'Where is #image feature defined?' nickname owned by Glenn Adams on product TTML IMSC 1.0, description 'Where is #image feature defined? it is referenced twice without any referent
    ' non-public
  • 2015-09-03 03:51:51:
    *<Pierre-Anthony Lemieux> Status changed to 'pending review'
    *<Pierre-Anthony Lemieux> #image is "Relative to the SMPTE-TT Extension Namespace". The latter is defined in [ST2052-1] per Section 6.3.
ISSUE-405 (pending review)
  • 2015-09-03 03:52:26:
    *<Pierre-Anthony Lemieux> Created issue 'why is #nested-span prohibited on image profile?' nickname owned by Glenn Adams on product TTML IMSC 1.0, description 'why is #nested-span prohibited on image profile when #content span is already prohibited?' non-public
  • 2015-09-03 03:56:14:
    *<Pierre-Anthony Lemieux> Status changed to 'pending review'
    *<Pierre-Anthony Lemieux> The objective is to explicitly cover all TTML1 features, i.e. reduce potential ambiguity.
ISSUE-406 (open)
  • 2015-09-03 03:56:50:
    *<Pierre-Anthony Lemieux> Created issue '#lineBreak-uax14 is never 'used' by a document?' nickname owned by Glenn Adams on product TTML IMSC 1.0, description '#lineBreak-uax14 is never 'used' by a document? it is either implemented or not implemented by a presentation processor; so it doesn't make sense to cite as MAY be used or SHALL NOT be used; it would, OTOH, be appropriate to require an implementation of the text profile to implement this feature;' non-public
  • 2015-09-03 14:43:40:
    *Status changed to 'open'
ISSUE-407 (open)
  • 2015-09-03 04:00:01:
    *<Pierre-Anthony Lemieux> Created issue 'Excluding #bidi and #direction on image profile is inconsistent' nickname owned by Glenn Adams on product TTML IMSC 1.0, description 'excluding #bidi and #direction on image profile is inconsistent, since #bidi includes #direction, #unicodeBidi and #writingMode-horizontal; better to exclude #direction and #unicodeBidi, but retain #writingMode-horizontal with lrtb or lr values;' non-public
  • 2015-09-03 14:50:39:
    *Status changed to 'open'
ISSUE-408 (pending review)
  • 2015-09-03 04:03:54:
    *<Pierre-Anthony Lemieux> Created issue 'Initial value of color' nickname owned by Glenn Adams on product TTML IMSC 1.0, description 't doesn't make sense to stipulate that the initial value of color shall be white in a context defining document usage. This is an implementation requirement (only).' non-public
  • 2015-09-03 04:06:03:
    *<Pierre-Anthony Lemieux> Description changed to 'It doesn't make sense to stipulate that the initial value of color shall be white in a context defining document usage. This is an implementation requirement (only).'
    *<Pierre-Anthony Lemieux> Status changed to 'pending review'
    *<Pierre-Anthony Lemieux> AFAIK TTML1 does not forbid an application from defining the initial value of color.
ISSUE-409 (pending review)
  • 2015-09-03 04:06:39:
    *<Pierre-Anthony Lemieux> Created issue 'Font family of default means monospaceSerif' nickname owned by Glenn Adams on product TTML IMSC 1.0, description 'Similarly, it doesn't make sense to specify that font family of default means monospaceSerif as a document requirement; it is an implementation requirement. Also, this is probably inappropriate depending on the language market; e.g., in the Japanese market, it should be monospaceSansSerif or proportionalSansSerif.' non-public
  • 2015-09-03 04:08:17:
    *<Pierre-Anthony Lemieux> Status changed to 'pending review'
    *<Pierre-Anthony Lemieux> TTML1 states "if the generic family name default is specified (or implied by an initial value), then its typographic characteristics are considered to be implementation dependent."

    IMSC1 specifies the typographic characteristics of those implementations that conform to IMSC1.
ISSUE-410 (open)
  • 2015-09-03 04:08:58:
    *<Pierre-Anthony Lemieux> Created issue 'Constraints on #linePadding and #multiRowAlign' nickname owned by Glenn Adams on product TTML IMSC 1.0, description '"shall not apply" constraints on #linePadding and #multiRowAlign in text profile apply only to implementation, not content; it is intended they be proscribed in content? if so should not use term "apply";' non-public
  • 2015-09-03 04:09:50:
    *<Pierre-Anthony Lemieux> The intent was to mimic ​TTML styles features, e.g. tts:visibility​, which use the terms "Applies to:" to specify the element(s) to which they apply.
  • 2015-09-03 04:13:02:
    *<Pierre-Anthony Lemieux> Status changed to 'open'
ISSUE-411 (open)
  • 2015-09-03 04:10:19:
    *<Pierre-Anthony Lemieux> Created issue '"shall be inherited" on #multiRowAlign' nickname owned by Glenn Adams on product TTML IMSC 1.0, description '"shall be inherited" on #multiRowAlign in text profile is an implementation constraint, not document content;' non-public
  • 2015-09-03 04:12:38:
    *<Pierre-Anthony Lemieux> Status changed to 'open'
    *<Pierre-Anthony Lemieux> The intent was to mimic ​TTML styles features, e.g. tts:visibility​, which use the terms "Inherited" to specify whether the style feature is inherited.
ISSUE-412 (open)
  • 2015-09-03 04:14:44:
    *<Pierre-Anthony Lemieux> Created issue 'The term 'SHALL' should not be used in the definition of Related Video Object' nickname owned by Glenn Adams on product TTML IMSC 1.0, description 'The term 'SHALL' should not be used in Section 6.5 in the following:

    which shall consist of a sequence of image frames, each a rectangular array of pixels, and shall be considered theRelated Media Object.

    The content of the related media object is irrelevant to IMSC/TTML, and, in any case, is not reasonably testable in the context of IMSC/TTML.' non-public
  • 2015-09-03 04:15:21:
    *<Pierre-Anthony Lemieux> Status changed to 'open'
    *<Pierre-Anthony Lemieux> Section 6.5 is intended to define "Related Video Object", which is used to specify mapping of time expressions to frames -- which is pulled from DECE.

    It probably can be moved to the "Terms and Definitions" section and reworded without conformance terms:

    """
    Related Video Object​. ​​Related Media Object​ that consist​s​ of a sequence of image frames, each a rectangular array of pixels​.
    ​"""​
ISSUE-413 (open)
  • 2015-09-03 04:15:52:
    *<Pierre-Anthony Lemieux> Created issue 'What does "reproducible without error" mean?' nickname owned by Glenn Adams on product TTML IMSC 1.0, description 'What does "reproducible without error" mean? Specifically, what does "reproducible" mean? and what does "without error" mean in this context?
    ' non-public
  • 2015-09-03 04:17:18:
    *<Pierre-Anthony Lemieux> Status changed to 'open'
    *<Pierre-Anthony Lemieux> Would the following be clearer:

    """
    ​It shall be possible to apply the Hypothetical Render Model ​process ​specified in Section 9​ to any sequence of consecutive intermediate synchronic documents, without error as defined in Section 9.2, ​.
    """

Actions

ACTION-364: Glenn Adams to Add paragraph in intro that summarizes changes from ttml1 (comment from tm) (open)
ACTION-383: Glenn Adams to Missing XML declaration (open)
ACTION-384: Glenn Adams to Ensure consistency in ttml2 w.r.t. inline progression dimension vs direction (open)
ACTION-386: Glenn Adams to Investigate whether region style inheritance from tt is necessary given the ability to redefine initial values (open)
ACTION-396: David Singer to Produce evidence of request for wide review for webvtt, for the archive (open)
ACTION-404: Glenn Adams to Add note to issue 341 to reflect his current thinking (open)
ACTION-415: Thierry Michel to Send nigel email addresses of htmlcue proposal reviewers (closed)
ACTION-416: Nigel Megitt to Edit proposal and send to htmlcue proposal reviewers as listed by tmichel, following action-415 (open)
ACTION-417: Pierre-Anthony Lemieux to Create ticket with unicode for cldr proposal, or add to existing one. (closed)
ACTION-418: Nigel Megitt to Send response back to atsc as per https://lists.w3.org/archives/member/member-tt/2015aug/0019.html (pending review)
ACTION-419: Mike Dolan to Add other ttml profiles to the codecsregistry wiki page (closed)
  • 2015-09-03 14:34:04:
    * Status changed to 'closed'
ACTION-420: Pierre-Anthony Lemieux to Follow up with glenn on issue-406 (open)
  • 2015-09-03 14:43:48:
    * Created action 'Follow up with glenn on issue-406' assigned to Pierre-Anthony Lemieux, due 2015-09-10

David Singer <singer@apple.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Chairs, Thierry Michel <tmichel@w3.org>, Philippe Le Hégaret <plh@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: changelog.php,v 1.34 2014-02-12 10:08:50 dom Exp $