W3C home > Mailing lists > Public > public-web-and-tv@w3.org > February 2013

[tt] Notes from Kick-off teleconference.

From: Giuseppe Pascale <giuseppep@opera.com>
Date: Tue, 26 Feb 2013 16:40:53 +0100
To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <op.ws4duflx6ugkrk@giuseppep-x220>
Hi all,
these are some rough notes from the TT kick-off call.
Participants are welcome to point out errors or significant omissions.



                                - DRAFT -

                 Web and TV Interest Group Teleconference

26 Feb 2013


           pal, Kazuyuki, mike, Giuseppe, Mark_Vickers, Yosuke,
           BobLund, glenn, clarke, Sheau




      * [3]Topics
          1. [4]Timed Text Task Force
          2. [5]introduction
      * [6]Summary of Action Items

    <trackbot> Date: 26 February 2013

Timed Text Task Force

    <kaz> Meeting: TT


    pal: kickoff meeting, we will try to work over mail but was
    good to have an initial call


    pal: (going through the agenda)

<pal> [8]http://www.w3.org/2011/webtv/wiki/Tt

    pal: let's start with our objectives
    ... let's review them
    ... any comment? none

<pal> [9]http://www.w3.org/2011/webtv/wiki/Timed_Text_Efforts

    pal: first step is to try list all various efforts in this area
    ... not sure what to write about webvtt since not very
    familiar, so would like to ask others to fill it in

    giuseppe: would be good to list all the info we have about
    ongoing work, as far as it is public

    mike: will provide a pointer to a collection of SMPTE document

    all: providing links on IRC of onoging efforts

    mark: what about europe, other than the DTG effort?

    giuseppe: yes, EBU, already listed on the wiki

    mark: what about Asia?

    yosuke: Japan is using a spec based on original SMPTE standards
    ... switching to new one is considered but a lot of effort is

    mark: ok this is Japan, what about other areas? Korea/China?

    yosuke: I'll investigate and send out links

    mark: are there other TTML/SMPTE based profiles?
    ... (or extensions?)

    pal: I think netflix use some profile of ttml, not sure if is

    bob: I think there is an effort for a TTML 2.0 spec, anybody
    know more?

    mark/giuseppe: no

    glen: there is no 2.0, but a 1.1 work
    ... and also an errata being worked on

    bob: is it done in the TT WG?

    glenn: yes

    pal: ok, let's move on to the next agenda item, people can keep
    adding link to the wiki if they have more

    pal: next item is discuss use cases

    pal: one use case is to rendering tt in UA
    ... Ultraviolet have decided to use a subset of smpte-tt


    pal: maybe not exactly a subset but anyway based on that
    ... there is a link in the wiki
    ... since ultraviolet has a larg number of members and a large
    ... I would expect large support for this format

    giuseppe: is important to distinguish between the browser and
    the player on the TV, they are usually not from the same

    glenn: this cause problems when trying to use new HTML5 API for
    ... what do people think about TTML support in browsers?
    ... I think only IE supports it

    glenn: I made a proposal to webkit to add TTML support
    ... some negative reponses
    ... I would like to ask people to also comment on that bug

    glenn: another useful task would would be to try to map the
    html5 interfaces also for TTML or other formats

    mark: isn't this part of the TT WG charter? Isn't a deliverable
    of that group?

    glenn: yes but maybe this TF could provide some input

    pal: contributing to webkit is probably out of scope for this
    group, but providing a mapping could be in scope

    mark: the most useful mapping would be the smpte-tt one since
    it is in the regulation

    giuseppe: is it useful to ask other groups planning to use
    HTMl5 how they plan to solve this issue?

    mark: we want to reach all devices, but we are facing issues
    due to this fragmentation
    ... all content companies in us are using smpte-tt, but there
    are devices only supporting webvtt
    ... so we have to do translation
    ... we would like to see the 2 groups to work togheter to make
    the spec closer
    ... anyway we shoudl focus on the requirements first, later we
    could investigate the technical solutions

    glenn: I'm not sure that supporting multiple formats is costly,
    devices support multiple different formats for other features

    giuseppe: what are the objections from the webkit community?

    glenn: from my understanding is just about avoid multiple
    ... there is also a comment that would be difficult to
    ... probably comment based due to the lack of open

    pal: mark/glenn can you start writing down something about the
    current issues, for the group to review?

    glenn: yes

    mark: yes

List of standards or other info mentioned during the call

<Mark_Vic_> WebVTT "Living Standard:

<Mark_Vic_> Web Media Text Tracks Community Group (Working on WebVTT):

<pal> [10]http://dev.w3.org/html5/webvtt/

<yosuke> FYI: ISDB-Tmm (mobile DTV service) has adopted TTML. NTT-Docomo  
and some CE manufactures has already released smart phones with TTML  
enabled HTML5 browsers.

<Mark_Vic_> WebVTT in WebM:

<Mark_Vic_> WebVTT in Appleā€™s HTTP Live Streaming:

<glenn> [27]https://bugs.webkit.org/show_bug.cgi?id=110479

<mike> SMPTE 2052-x series for SMPTE-TT,

<mike> CEA Technical Report (TR-3) Closed Captioning in IP-delivered Video  

<glenn> [19]http://www.w3.org/TR/2013/NOTE-ttml10-sdp-us-20130205/

<mike> BBC YouView profile of TTML,

<Mark_Vic_> Conversion of 608/708 captions to WebVTT:

<BobLund> 608 mapping to webvtt


<sheau> Found this link on ARIB, but it's in Japanese

<yosuke> That's right, Sheau. Arib has English version of B-37 but not for  

<yosuke> Here is a part of the spec of CC for Japanese DTV:

<mike> DECE/UV profile of TTML:

Giuseppe Pascale
Product Manager TV & Connected Devices
Opera Software
Received on Tuesday, 26 February 2013 15:41:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:15 UTC