See also: IRC log
<trackbot> Date: 06 March 2014
<glenn> https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml2/spec/ttml2.html#cea708-mapping
<scribe> scribeNick: nigel
No comments on this agenda item at this time.
action-268?
<trackbot> action-268 -- Nigel Megitt to Estimate timelines for ttml 2 deliberables with glenn -- due 2014-02-27 -- OPEN
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/268
nigel: Glenn and I discussed this, main determining factor is Glenn's availability and resource scheduling.
http://www.w3.org/2013/10/timed-text-charter.html
nigel: Getting to TTML2 LC by April looks very ambitious at this point.
glenn: would like to target June
1 for 1st WD, then August 1 for LC
... taking into account my availability, and conservative
scheduling.
... The CR period is 6 months, whereas 3 months would probably
be adequate.
... PR to Rec shouldn't take more than 2 weeks.
... The only thing needed is to poll the membership.
... The average is no more than 1 month.
... I propose for TTML2 August 2014 LC, Oct 2014 CR, Jan 2015
PR, Feb 2015 Rec.
... The work is not process work but is implementation and
technical work, which should be prior to or during LC or CR
period.
... That gives us overall 6 months for LC/CR period, which is
very generous.
nigel: We're still dependent on contributions, but as we have one editor whom everything has to go through this is important.
action-269
<trackbot> action-269 -- Glenn Adams to Implement issue-282 changes on ttml2 text also -- due 2014-03-06 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/269
glenn: now Pending Review. Implemented this morning.
close action-269
<trackbot> Closed action-269.
action-270
<trackbot> action-270 -- Glenn Adams to Add informative appendix to ttml2 on subject of 708 mapping, where it refers to st2052-11 as starting point, and provides place to extend or elaborate mapping information -- due 2014-03-06 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/270
nigel: currently a placeholder.
glenn: marked as an Editor note,
which is a placeholder to do this later. We don't put actions
on Editor notes - two record keeping mechanisms aren't
needed.
... There are 29 such notes, which is a backlog to process.
jdsmith: it would be useful to have a broad review of all the updates on editors notes later.
glenn: when I make the updates I
put them in the repository and inform the group asynchronously.
We generally in the past haven't created actions, though
... some of them are associated with issues - we typically
close the issue when we've accepted the editor's changes.
close action-270
<trackbot> Closed action-270.
action-271?
<trackbot> action-271 -- Nigel Megitt to Draft email to css wg chair requesting box-decoration-break in css3 -- due 2014-03-06 -- OPEN
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/271
nigel: I've done the action but had no response.
glenn: I have an update because
it was on the agenda in yesterday's CSSWG meeting. I had
independently submitted a request from Cox to move it into
Level 3.
... After a fair amount of discussion it was decided to leave
it where it is now in the CSS Fragmentation spec on the basis
that the group believes it will move to Rec in about
... the same timeframe as background and borders level 3.
There's concern over delays to this: backgrounds and borders L3
is further along the process. But most of the group
... believes it's more logically associated with Fragmentation,
so this is probably the best place for it.
... Peter Linss yesterday was supposed to draft a response.
When this happens we should thank them and say we'll hold them
to publishing Fragmentation on an expedited schedule
... aligned with the schedule for Backgrounds and Borders.
close action-271
<trackbot> Closed action-271.
issue-300?
<trackbot> issue-300 -- Prior interpretation of the correct fallback for tts:origin -- open
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/300
no comments on the issues on the agenda from those present
https://www.w3.org/wiki/TTML/changeProposal015
nigel: I edited the box-decoration-break section to reference the EBU-TT-D syntax.
glenn: I wouldn't be averse to introducing a linePadding style property that maps to CSS box-decoration-break. It gives us some logical independence for mapping purposes.
<glenn> ACTION: glenn to add notes to CP15 for those items that have already been implemented, where notes point at relevant change set [recorded in http://www.w3.org/2014/03/06-tt-minutes.html#action01]
<trackbot> Created ACTION-272 - Add notes to cp15 for those items that have already been implemented, where notes point at relevant change set [on Glenn Adams - due 2014-03-13].
nigel: for box-decoration-break
need to add example syntax in TTML2 and proposed mapping to
CSS. Will do this for a single value for both start and end, in
units identical to those that padding takes now.
... multiple row alignment
glenn: want to think about the name, but not expose the CSS directly. Prefer to have a TTML property that focuses on the usage.
nigel: agreed. FIts with the general style of TTML.
glenn: The indirection may reduce
spec-dependencies on publication. We don't know when flex will
get to Rec. If the mapping document has dependencies on CSS
features that are not in Rec we could
... put the mapping document outside TTML2 to allow us to
publish.
thierry: administrative point: next week US switches to summer time.
action nigel to add DST note to next agenda
<trackbot> Created ACTION-273 - Add dst note to next agenda [on Nigel Megitt - due 2014-03-13].
rrsagent. make logs public
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: nigel Inferring Scribes: nigel Default Present: nigel, glenn, [Microsoft], Thierry Present: nigel glenn jdsmith Thierry Regrets: pal frans_de_jong Found Date: 06 Mar 2014 Guessing minutes URL: http://www.w3.org/2014/03/06-tt-minutes.html People with action items: glenn[End of scribe.perl diagnostic output]