RE: TTML Agenda for 26/06/13

Regrets for today.  See below for specifics.  In general, we need to put
1.0SE behind us and get on promptly with 1.1.

 

From: Sean Hayes [mailto:Sean.Hayes@microsoft.com] 
Sent: Wednesday, June 26, 2013 5:01 PM
To: 'public-tt@w3.org'
Subject: TTML Agenda for 26/06/13

 

 

our teleconference is scheduled with reference to Boston Time, the correct
time of this teleconference in your locale may change. Please check
http://timeanddate.com/worldclock/fixedtime.html?month=06
<http://timeanddate.com/worldclock/fixedtime.html?month=06&day=26&year=2013&
hour=10&min=0&sec=0&p1=43> &day=26&year=2013&hour=10&min=0&sec=0&p1=43  

 

Thursdays 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
:http://www.w3.org/2001/01/cgi-irc

 

Chair: Sean Hayes

 

Agenda+ Assign Scribe

 

Agenda+ Close out Issues and Actions pending review

 

Agenda+ ISSUE 200 https://www.w3.org/AudioVideo/TT/tracker/issues/200     

 

OK     

 

Agenda+ ISSUE 209 https://www.w3.org/AudioVideo/TT/tracker/issues/209


 

OK

 

Agenda+ ISSUE 211 https://www.w3.org/AudioVideo/TT/tracker/issues/211


 

I guess this is technically precise, but a general source of user confusion
and errors are the broad syntax permitted in TTML that has no semantic
meaning.  This is an example, where a wide range of values are syntactically
permitted, but only a smaller range is semantically meaningful - in this
case unconditionally clamped. It would be a lot better if the spec and
schema actually forbid values that have no meaning. I anticipate the
response will be that the syntax is aligned with other W3C spec X, but well.
See also 222.

 

Agenda+ ISSUE 212 https://www.w3.org/AudioVideo/TT/tracker/issues/212


 

OK

 

Agenda+ ISSUE 214 https://www.w3.org/AudioVideo/TT/tracker/issues/214


 

OK

 

Agenda+ ISSUE 215 https://www.w3.org/AudioVideo/TT/tracker/issues/215


 

OK

 

Agenda+ ISSUE 216 https://www.w3.org/AudioVideo/TT/tracker/issues/216


 

OK

 

Agenda+ ISSUE 218 https://www.w3.org/AudioVideo/TT/tracker/issues/218


 

OK

 

Agenda+ ISSUE 219 https://www.w3.org/AudioVideo/TT/tracker/issues/219


 

 OK 

 

Agenda+ ISSUE 220 https://www.w3.org/AudioVideo/TT/tracker/issues/220


 

OK

 

Agenda+ ISSUE 221 https://www.w3.org/AudioVideo/TT/tracker/issues/221


 

OK

 

Agenda+ ISSUE 222 https://www.w3.org/AudioVideo/TT/tracker/issues/222


 

See 211.

 

Agenda+ ISSUE 223 https://www.w3.org/AudioVideo/TT/tracker/issues/223


 

OK

 

Agenda+ ISSUE 251 https://www.w3.org/AudioVideo/TT/tracker/issues/251


 

OK

 

Agenda+ ISSUE 252 https://www.w3.org/AudioVideo/TT/tracker/issues/252


 

OK

 

Agenda+ ISSUE 256 https://www.w3.org/AudioVideo/TT/tracker/issues/256


 

OK

 

Agenda+ ISSUE 257 https://www.w3.org/AudioVideo/TT/tracker/issues/257


 

OK

 

Agenda+ ISSUE 258 https://www.w3.org/AudioVideo/TT/tracker/issues/258


 

OK, but this is not editorial and thus question its application to 1.0SE.

 

Tracker (Issues and Actions):  <http://www.w3.org/AudioVideo/TT/tracker>
http://www.w3.org/AudioVideo/TT/tracker

 

 

TTML 1.0 ED
https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttaf1-dfxp.html 

 

 

TTML Wiki

 <http://www.w3.org/wiki/TimedText> http://www.w3.org/wiki/TimedText

 

Second edition draft: 

 

 
<https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?conten
t-type=text/html%3bcharset=utf-8>
https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content
-type=text/html%3bcharset=utf-8