- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Thu, 12 Jun 2014 15:20:35 +0000
- To: "'Timed Text Working Group'" <public-tt@w3.org>
- Message-ID: <CFBF82BF.1EEC9%nigel.megitt@bbc.co.uk>
Minutes available at: http://www.w3.org/2014/06/12-tt-minutes.html
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Timed Text Working Group Teleconference
12 Jun 2014
See also: [2]IRC log
[2] http://www.w3.org/2014/06/12-tt-irc
Attendees
Present
nigel, jdsmith, glenn, pal, plh
Regrets
mdolan
Chair
nigel
Scribe
nigel
Contents
* [3]Topics
1. [4]TPAC
2. [5]Prioritise discussion for meeting
3. [6]SMPTE liaison
4. [7]Change Proposal 2
5. [8]Pending Review actions and issues
* [9]Summary of Action Items
__________________________________________________________
<trackbot> Date: 12 June 2014
<scribe> scribeNick: nigel
TPAC
<scribe> scribeNick: nigel
plh: Last week thierry was right that Tuesday is available as
well as Monday and Thursday.
[10]https://www.w3.org/2002/09/wbs/34314/TPAC2014Planning/resul
ts
[10] https://www.w3.org/2002/09/wbs/34314/TPAC2014Planning/results
<tmichel> trying to get in ...
nigel: the wbs survey results show we prefer Tuesday to
Thursday.
plh: Sorry about that!
RESOLUTION: We will change to meet on Monday and Tuesday at
TPAC 2014.
Prioritise discussion for meeting
nigel: In order to make progress on both IMSC and TTML2 we
could arrange a separate call to ensure we go through the
issues.
pal: If we need more time then we should schedule that.
nigel: We can also review issues offline but I try to keep
state changes on issues to meetings so there's a clear place
where resolutions are minuted.
glenn: In the recent past we have had 2 hour meetings. It may
be useful to have 2 hour meetings on an occasional basis to
handle overflow.
nigel: We'll schedule next week's meeting (the 19th) for 2
hours. I'll be absent for the next two weeks after that.
SMPTE liaison
Proposed response at
[11]https://lists.w3.org/Archives/Member/member-tt/2014Jun/0000
.html
[11] https://lists.w3.org/Archives/Member/member-tt/2014Jun/0000.html
nigel: I'll make the change proposed to request for
notification of changes to ST2052
glenn: I'll review the response - give me until the end of the
day.
nigel: I will aim to send this on Monday next week if there are
no further amendments.
Change Proposal 2
[12]https://www.w3.org/wiki/TTML/changeProposal002
[12] https://www.w3.org/wiki/TTML/changeProposal002
jdsmith: We don't need to make the change to step 6 described
in the CP because of the way that Glenn has implemented this.
... I think there's some editorial note to elaborate too.
glenn: I'm in the process of elaborating that editorial note.
The final hook is the semantics of inline regions, in
particular how the associate region algorithm works in the
context of inline regions.
... I think we can go ahead and close the CP.
jdsmith: Is there another CP that drives the editorial notes?
glenn: Inline regions was a general solution and then this
particular proposal formulated it in terms of a syntactic
shorthand.
jdsmith: I agree the syntactic element is taken care of.
issue-176?
<trackbot> issue-176 -- Adding support for extent and origin
attributes on block elements -- closed
<trackbot>
[13]http://www.w3.org/AudioVideo/TT/tracker/issues/176
[13] http://www.w3.org/AudioVideo/TT/tracker/issues/176
nigel: Issue 176 is closed at the moment.
jdsmith: The substance of the change proposal is already
implemented.
ACTION jdsmith Fix up change proposal 2 to reflect decision on
how to implement and edit out now unnecessary sections.
<trackbot> Created ACTION-299 - Fix up change proposal 2 to
reflect decision on how to implement and edit out now
unnecessary sections. [on Jerry Smith - due 2014-06-19].
RESOLUTION: Close change proposal 2 following completion of
ACTION-299
Pending Review actions and issues
action-293?
<trackbot> action-293 -- Pierre-Anthony Lemieux to Research
appropriate namespace for forceddisplay feature in imsc 1 for
issue-312 -- due 2014-06-05 -- PENDINGREVIEW
<trackbot>
[14]http://www.w3.org/AudioVideo/TT/tracker/actions/293
[14] http://www.w3.org/AudioVideo/TT/tracker/actions/293
pal: I completed this action by moving the new attributes
introduced by IMSC to an IMSC-specific namespace as proposed by
glenn.
... the prefixes used are ittp: and itts:
close action-293
<trackbot> Closed action-293.
issue-263?
<trackbot> issue-263 -- profile feature set may not match
intended feature constraints -- pending review
<trackbot>
[15]http://www.w3.org/AudioVideo/TT/tracker/issues/263
[15] http://www.w3.org/AudioVideo/TT/tracker/issues/263
nigel: mike has specifically mentioned this before so I'm
minded to hold off closing this until he has had a chance to
comment.
glenn: Do we need to go back and amend SDP-US to use the
extension and restriction of features. We don't normally update
notes post-publication.
nigel: I think we may need to consider a new version of SDP-US
based on TTML2 later in our process.
plh: It is not covered by the charter to put SDP-US on a Rec
track.
nigel: An alternative is to consider IMSC (1 or 2) as
superseding SDP-US.
plh: If we make it a sub-profile of IMSC and update the SDP-US
note to point to IMSC that might do the trick.
nigel: Do we need to make a decision on SDP-US to close this
issue?
glenn: It would be worth adding a note to the issue.
<glenn> ACTION glenn to add note to Issue 263 explaining how
TTML2 additions for @{extends,restricts} (partially) addresses
this issue
<trackbot> Created ACTION-300 - Add note to issue 263
explaining how ttml2 additions for @{extends,restricts}
(partially) addresses this issue [on Glenn Adams - due
2014-06-19].
nigel: After these edits and when Mike has had the opportunity
to verify that this meets the requirements he has previously
mentioned we can close this off, assuming no objections.
issue-312?
<trackbot> issue-312 -- forcedDisplay attribute is metadata so
should be in ttm not tts namespace -- pending review
<trackbot>
[16]http://www.w3.org/AudioVideo/TT/tracker/issues/312
[16] http://www.w3.org/AudioVideo/TT/tracker/issues/312
pal: In addition to fixing the bug and changing the namespace I
added a specific recommended processor behaviour.
nigel: Expresses concern that the approach to conditional
content is different to the approach for issue-309
... We also have change proposal 16
[17]https://www.w3.org/wiki/TTML/changeProposal016 to provide
for this requirement.
[17] https://www.w3.org/wiki/TTML/changeProposal016
glenn: When we get around to defining something like this in
TTML2 I would want to address this not as a special case so I
doubt that we will end up with a forcedDisplay style property
in TTML2.
nigel: Our options are to omit the feature, add a note in IMSC
saying that this is IMSC1 specific, or specify this feature
'properly' and carry forward into TTML2.
pal: I'd propose to do the second option and add a new issue
for IMSC 2 to log this.
glenn: By publishing this from this group it will add
legitimacy to the feature and possibly people will try to make
us carry it into TTML2.
... I think we should put a note in, if we include it in IMSC1,
to the effect that it may not be specified in the same way in
TTML2 to cover our tracks and prevent future complaints.
... I understand that we can't predict the future but it's
useful to the reader that they can not expect backward
compatibility in a future version. Notes are lightweight
anyway.
pal: Entering an issue against IMSC 2 is powerful too.
nigel: Let's do both things.
... I will add a note to the issue and re-open it immediately
after this meeting.
Summary of Action Items
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [18]scribe.perl version
1.138 ([19]CVS log)
$Date: 2014-06-12 15:03:10 $
__________________________________________________________
[18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[19] http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 12 June 2014 15:21:24 UTC