{minutes} TTWG Meeting 20/3/2014

Minutes available at http://www.w3.org/2014/03/20-tt-minutes.html


   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

                Timed Text Working Group Teleconference

20 Mar 2014

   See also: [2]IRC log

      [2] http://www.w3.org/2014/03/20-tt-irc

Attendees

   Present
          Frans_EBU, nigel, pal, jdsmith, plh, tmichel

   Regrets
          glenn

   Chair
          nigel

   Scribe
          nigel

Contents

     * [3]Topics
         1. [4]Charter
         2. [5]TPAC 2014
         3. [6]Docs from other groups
         4. [7]Change Proposals
         5. [8]AOB
     * [9]Summary of Action Items
     __________________________________________________________

   <trackbot> Date: 20 March 2014

   trackbot, start meeting

   <trackbot> Meeting: Timed Text Working Group Teleconference

   <trackbot> Date: 20 March 2014

   <scribe> chair: nigel

   <scribe> scribeNick: nigel

Charter

   [10]https://www.w3.org/2002/09/wbs/33280/timed-text-2014/result
   s

     [10] https://www.w3.org/2002/09/wbs/33280/timed-text-2014/results

   frans: describes EBU request for a change

TPAC 2014

   [11]http://www.w3.org/2014/11/TPAC/

     [11] http://www.w3.org/2014/11/TPAC/

   nigel: any requests for f2f?

   jdsmith: we should be fairly far along by October

   nigel: Could be a good opportunity with a relative stable TTML2
   and IMSC to work with the WebVTT folk on the mapping
   deliverable, whatever form that might take.
   ... I will propose that we have a f2f meeting - the question
   will be how many days do we need, and which days should we hold
   the meeting on?
   ... Monday, Tuesday, Thursday and Friday are the options.

   jdsmith: travel is an important factor, otherwise it could be
   any one of those days.

   nigel: bear in mind also CSSWG and HTMLWG meetings.

   <scribe> ACTION: nigel to discuss with david singer
   possibilities for f2f before going ahead and adding TTWG to
   TPAC agenda. [recorded in
   [12]http://www.w3.org/2014/03/20-tt-minutes.html#action01]

   <trackbot> Created ACTION-274 - Discuss with david singer
   possibilities for f2f before going ahead and adding ttwg to
   tpac agenda. [on Nigel Megitt - due 2014-03-27].

Docs from other groups

   nigel: iterates through docs from other groups as listed in the
   agenda.
   ... since the agenda there's also been a reversion to LC for
   CSS Flexible Box Layout Module Level 1
   ... We plan to use this!
   ... URL is [13]http://www.w3.org/TR/css3-flexbox/ and Editor's
   Draft is [14]http://dev.w3.org/csswg/css-flexbox-1/
   ... I encourage all to review this and I will collate any
   comments. They suggest a 4 week review period ending April 22.
   ... therefore comments back to me (I'll add an agenda item for
   this) by 17th April at very latest.

     [13] http://www.w3.org/TR/css3-flexbox/
     [14] http://dev.w3.org/csswg/css-flexbox-1/

   pal: Suggests process to put together comments and submit our
   comments to reflector.
   ... would be good to have a feedback comments document from the
   group for TTWG review prior to submission to CSS WG by the
   chair.

   nigel: agrees

   pal: one comment is based on change proposal 15 - it would be
   helpful to get consensus on CP15 before submitting comments
   based on it.
   ... of course individuals can always comment anyway.

Change Proposals

   nigel: CP15 is the only one with any movement I'm aware of so
   I'll walk through the changes

   [15]https://www.w3.org/wiki/TTML/changeProposal015

     [15] https://www.w3.org/wiki/TTML/changeProposal015

   nigel: Peter Linss of the CSS WG responded that " the
   box-decoration-break property was moved to the CSS
   Fragmentation spec"
   ... and "we expect that spec to reach CR before the end of the
   year. Hopefully this satisfies your needs."

   [16]http://drafts.csswg.org/css-break/#break-decoration

     [16] http://drafts.csswg.org/css-break/#break-decoration

   nigel: the timescales are quite close to those for TTML2 so we
   may consider making a response to this.

   jdsmith: what's the purpose of the Fragmentation spec

   [17]https://www.w3.org/wiki/TTML/changeProposal015#box-decorati
   on-break

     [17] https://www.w3.org/wiki/TTML/changeProposal015#box-decoration-break

   nigel: we intend to use css box-decoration-break: clone
   property to achieve the desired effect. This is in the CSS
   Fragmentation spec now.
   ... walks through the Issue-286 proposal in CP15, opens up for
   comments, noting that Glenn is particularly interested.

   pal: TTML1 processors that see that attribute - is the
   expectation that they ignore it and not add padding?

   nigel: yes because they'd use the profile and feature mechanism
   for processors to work out if they need to support it
   ... so processors would ignore it if they don't know it.

   pal: that would be a nice way around it

   nigel: if it is ignored then impact is slightly less readable
   text but no unpleasant text wrapping impacts.

   pal: it would be good to verify that existing implementations
   quietly ignore attributes (without complaining) in the tts
   namespace that they do not recognise.

   nigel: happy for implementors to verify this or we could
   alternatively put this and other new TTML2 features into a new
   namespace

   pal: yes that's another possibility.
   ... having an ignorable attribute provides a nice way forward
   for any new attribute in the TTML2 namespace

   nigel: yes, I'd be interested in glenn's views on this and the
   interaction between this and profile features
   ... that's all on CP15 for this week - I'm looking at the use
   of flex for multiple row alignment too, which is work in
   progress.

   <scribe> ACTION: pal review issues in CP12 and if one is needed
   for handling new attributes in TTML2 in same namespace as TTML1
   then raise it, and link to issue-286. [recorded in
   [18]http://www.w3.org/2014/03/20-tt-minutes.html#action02]

   <trackbot> Created ACTION-275 - Review issues in cp12 and if
   one is needed for handling new attributes in ttml2 in same
   namespace as ttml1 then raise it, and link to issue-286. [on
   Pierre-Anthony Lemieux - due 2014-03-27].

AOB

   nigel: we seem to have an option on the tracker to send emails
   on changes to issues and actions by default - the current
   default is not to send emails.
   ... I propose changing this default to 'do send emails unless
   member has opted out'
   ... this may give a more positive experience than people have
   now.

   <tmichel> no objection.

   Action nigel Request tracker default change to 'email'

   <trackbot> Created ACTION-276 - Request tracker default change
   to 'email' [on Nigel Megitt - due 2014-03-27].

   nigel: There's going to be some service outage at MIT next week
   - not sure of the impact to W3C..

   tmichel: should be a short outage.

   nigel: Outages likely on Sat 29th March to servers

   rrsagent. publish minutes

Summary of Action Items

   [NEW] ACTION: nigel to discuss with david singer possibilities
   for f2f before going ahead and adding TTWG to TPAC agenda.
   [recorded in
   [19]http://www.w3.org/2014/03/20-tt-minutes.html#action01]
   [NEW] ACTION: pal review issues in CP12 and if one is needed
   for handling new attributes in TTML2 in same namespace as TTML1
   then raise it, and link to issue-286. [recorded in
   [20]http://www.w3.org/2014/03/20-tt-minutes.html#action02]

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [21]scribe.perl version
    1.138 ([22]CVS log)
    $Date: 2014-03-20 14:57:40 $
     __________________________________________________________

     [21] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [22] http://dev.w3.org/cvsweb/2002/scribe/




----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------

Received on Thursday, 20 March 2014 15:35:10 UTC