W3C home > Mailing lists > Public > public-tt@w3.org > February 2013

RE: TTML Agenda for 28/2/13

From: Michael Dolan <mdolan@newtbt.com>
Date: Thu, 28 Feb 2013 06:16:36 -0800
To: "'Monica Martin \(MS OPEN TECH\)'" <momartin@microsoft.com>, <public-tt@w3.org>
Cc: "'Glenn Adams'" <glenn@skynav.com>
Message-ID: <00d101ce15be$3b212300$b1636900$@newtbt.com>
Probably regrets for today - on the road....

-----Original Message-----
From: Monica Martin (MS OPEN TECH) [mailto:momartin@microsoft.com] 
Sent: Wednesday, February 27, 2013 11:12 PM
To: 'public-tt@w3.org'; Philippe Hegaret (plh@w3.org)
Subject: TTML Agenda for 28/2/13

Our teleconference is scheduled with reference to Boston Time, the correct
time of this teleconference in your locale may change. Please
Thursdays 15:00-15:00 UTC (10:00am-11:00am Boston local) 

Zakim Bridge +1.617.761.6200, conference 8865 ("TTML")
IRC: server: irc.w3.org, port: 6665, channel: #tt Web gateway to

Chair: Monica J. Martin, Philippe Hegaret 

Agenda+ Assign Scribe

Agenda+ Update links to SDP-US Working Group Note on WIKI

Agenda+ continue open issues on TTML 1.0 SE [1]

ISSUE-156 semantics of missing #feature OPEN semantics of missing
#feature... (Action-148 Glenn) Draft text for 2 resolutions: RESOLVED: in
1.1, add value of "prohibited" for feature definitions, also add attribute
"disposition" with values "error" and "ignore" and RESOLVED: in SE, add text
indicating that absence of a feature in profile means same as "optional".
[on Glenn Adams - due 2013-02-28].

ISSUE-157 transformation profile OPEN transformation profile [Action-147
Glenn] Create definitions for presentation and transformation in Section 2.2
to handle Issue-157.

ISSUE-179 px measure OPEN Interpreting the pixel measure Some properties
need clarification (Action-149 Glenn) Review CSS pixels and SVG to suggest a
resolution to Issue-179. [on Glenn Adams - due 2013-02-28].

Issue-163 Clarify use of cell units in certain properties OPEN (Action-148
Glenn) Clarify cell units as Sean specified as follows: .Style properties
that operate in both the horizontal and vertical direction, such as border,
outline thickness etc. may be specified using a single value which is based
on the cell unit. When the cell is non-square, the computed value is
calculated based on the height of the cell. For example: Given a root extent
of 852px 480px and a ttp:cellResolution="30 20"; then in pixels the
horizontal cell size is : 852/30 = 28.4 pixels, in the vertical 480/20 = 24
pixels. The relative unit to be used is 28.4px

ISSUE-170 5.2-para8 OPEN Section 5.2 para 8 is vague regarding optionality
of specifying profile in case where profile is negotiated/determined by
'document interchange process'   
Issue indicates Glenn added text to TTML 1.0 SE. Delete, "then the DFXP
Transformation profile applies"? Take further comments.

Issue-201 Open How to specify aspect ratio to understand positioning that
may apply for display or video.

ISSUE-168 OPEN Padding on tt:p and tt:span elements
ISSUE-172 OPEN REGION-OF(E) pseudo-code doesn't match prose
ISSUE-180 OPEN regions relative to the root container
ISSUE-183 OPEN semantics of using profile in a document
ISSUE-184 When does set happen OPEN set animation is not taken is not
account in the computed style set
ISSUE-189 OPEN do regions scroll their flowed content? 
ISSUE-197 OPEN charset/encoding unconstrained 

Regrets: Sean Hayes

Tracker (Issues and Actions): http://www.w3.org/AudioVideo/TT/tracker
Profile draft:  http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10-sdp-us

Change proposals:


Second edition draft:
[1] http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html
Received on Thursday, 28 February 2013 14:17:18 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:08 UTC