ISSUE-11: Inconsistency with regard to time container defaults

time-defaults

Inconsistency with regard to time container defaults

State:
CLOSED
Product:
TTML 1.0
Raised by:
Philippe Le Hégaret
Opened on:
2008-12-03
Description:
The specification is inconsistent with regard to time container defaults. It claims:
"If a timeContainer attribute is not specified on an element that has time container semantics, then par time container semantics must apply."

whereas in body for example it states:
"If no timeContainer attribute is specified, then a body element must be interpreted as having sequential time containment semantics".
This needs clarification.

It is proposed to amend the specification so that elements which currently say nothing bout their time container semantics (region, p and span) explicitly call out they have par semantics. And to remove the blanket clause in timecontainer as it is not clear which has precedence.
Related Actions Items:
Related emails:
  1. [minutes] teleconference 20090123 (from plh@w3.org on 2009-01-26)

Related notes:

No additional notes.

Changelog:

Created issue 'Inconsistency with regard to time container defaults' nickname time-defaults owned by Philippe Le Hégaret on product , description 'The specification is inconsistent with regard to time container defaults. It claims:
"If a timeContainer attribute is not specified on an element that has time container semantics, then par time container semantics must apply."

whereas in body for example it states:
"If no timeContainer attribute is specified, then a body element must be interpreted as having sequential time containment semantics".
This needs clarification.
' non-public

Philippe Le Hégaret, 3 Dec 2008, 16:43:27

Product changed to DFXP 1.0

Philippe Le Hégaret, 5 Dec 2008, 18:09:22

Description changed to 'The specification is inconsistent with regard to time container defaults. It claims:
"If a timeContainer attribute is not specified on an element that has time container semantics, then par time container semantics must apply."

whereas in body for example it states:
"If no timeContainer attribute is specified, then a body element must be interpreted as having sequential time containment semantics".
This needs clarification.

It is proposed to amend the specification so that elements which currently say nothing bout their time container semantics (region, p and span) explicitly call out they have par semantics. And to remove the blanket clause in timecontainer as it is not clear which has precedence.
'

Philippe Le Hégaret, 5 Dec 2008, 20:03:10

Status changed to 'closed'

Philippe Le Hégaret, 23 Jan 2009, 15:42:22


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: index.php,v 1.323 2013-12-19 14:47:09 dom Exp $