W3C home > Mailing lists > Public > public-html@w3.org > April 2012

RE: Issue 188 changes ("Generic Text Track")

From: Frank Olivier <Frank.Olivier@microsoft.com>
Date: Sun, 22 Apr 2012 19:03:04 +0000
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
CC: public-html <public-html@w3.org>
Message-ID: <91175A762AB48840AF1473514B26B4755296576E@TK5EX14MBXC262.redmond.corp.microsoft.com>
I agree. "Text track file" is a more generic and apt description for all the use cases you mentioned.

-----Original Message-----
From: Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com] 
Sent: Thursday, April 19, 2012 6:39 PM
To: Frank Olivier
Cc: public-html
Subject: Issue 188 changes ("Generic Text Track")

Hi Frank,

Ian made the below changes to the HTML spec where he replaced the use of "WebVTT file" with "caption file" because of the change proposal that was accepted for issue 188 [1].

I'd like to raise my concerns about the term "caption file" and would prefer we used something like "text track file", so we can continue to mark up chapters and descriptions with such a file, too. Otherwise the HTML spec can really only use <track> for captions and not for other kinds of data (including subtitles, descriptions, chapters and metadata).

Would you agree?

Regards,
Silvia.

[1] http://www.w3.org/wiki/ISSUE188/GenericTextTrack

On Fri, Apr 20, 2012 at 9:42 AM:
> Author: ianh
> Date: 2012-04-19 16:42:42 -0700 (Thu, 19 Apr 2012) New Revision: 7060
>
> Modified:
>   complete.html
>   index
>   source
> Log:
> [e] (0) apply wg decision
> Affected topics: HTML
>
> Modified: complete.html
> ===================================================================
> --- complete.html       2012-04-19 22:54:19 UTC (rev 7059)
> +++ complete.html       2012-04-19 23:42:42 UTC (rev 7060)
> @@ -240,7 +240,7 @@
>
>   <header class=head id=head><p><a class=logo 
> href=http://www.whatwg.org/><img alt=WHATWG height=101 
> src=/images/logo width=101></a></p>
>    <hgroup><h1 class=allcaps>HTML</h1>
> -    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 18 
> April 2012</h2>
> +    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 19 
> + April 2012</h2>
>    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
>     <dd><strong><a 
> href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></
> strong></dd>
>     <dt>Multiple-page version:</dt>
> @@ -1525,6 +1525,10 @@
>    the "they're ugly" use case), because of a <a 
> href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0786.html
> >working
>    group chair decision from March 2012</a>.</li>
>
> +   <li>The W3C HTML specification uses the term "caption file" in
> +   place of "WebVTT file" in certain places, because of a <a 
> + href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0557.ht
> + ml>working
> +   group chair decision from March 2012</a>.</li>
> +
>   </ul><p>The following sections are only published in the WHATWG
>   specifications and are not currently available anywhere else:</p>
>
> @@ -26953,12 +26957,17 @@
>   provided, either as a separate track embedded in the video stream,
>   or a separate audio track in an <code><a 
> href=#the-audio-element>audio</a></code> element <a 
> href=#slaved-media-elements title="slaved media elements">slaved</a> 
> to the same controller
>   as the <code><a href=#the-video-element>video</a></code> element(s), 
> or in text form using a
> -  <a href=#webvtt-file>WebVTT file</a> referenced using the <code><a 
> href=#the-track-element>track</a></code>
> -  element and synthesized into speech by the user agent. WebVTT can
> -  also be used to provide chapter titles. For users who would rather
> -  not use a media element at all, transcripts or other textual
> -  alternatives can be provided by simply linking to them in the prose
> -  near the <code><a href=#the-video-element>video</a></code> element. 
> <a href=#refsWEBVTT>[WEBVTT]</a></p>
> +  <a href=#webvtt-file>WebVTT file</a> <!--FORK-->
> +  referenced using the <code><a 
> +href=#the-track-element>track</a></code> element and synthesized into
> +  speech by the user agent. WebVTT can also be used to provide 
> +chapter
> +  titles. For users who would rather not use a media element at all,
> +  transcripts or other textual alternatives can be provided by simply
> +  linking to them in the prose near the <code><a href=#the-video-element>video</a></code> element.
> +<!--FORK-->
> +  <a href=#refsWEBVTT>[WEBVTT]</a>
> +<!--FORK-->
> +  </p>
>
>   <p>The <code><a href=#the-video-element>video</a></code> element is 
> a <a href=#media-element>media element</a>
>   whose <a href=#media-data>media data</a> is ostensibly video data, 
> possibly @@ -27311,9 +27320,16 @@
>   instead of the <code><a href=#the-audio-element>audio</a></code> 
> element to play the audio,
>   allowing users to enable the visual alternatives. Chapter titles can
>   be provided to aid navigation, using the <code><a 
> href=#the-track-element>track</a></code> element
> -  and a WebVTT file. And, naturally, transcripts or other textual
> -  alternatives can be provided by simply linking to them in the prose
> -  near the <code><a href=#the-audio-element>audio</a></code> element. 
> <a href=#refsWEBVTT>[WEBVTT]</a></p>
> +  and a
> +  <a href=#webvtt-file>WebVTT file</a>.
> +<!--FORK-->
> +  And, naturally, transcripts or other textual alternatives can be
> +  provided by simply linking to them in the prose near the
> +  <code><a href=#the-audio-element>audio</a></code> element.
> +<!--FORK-->
> +  <a href=#refsWEBVTT>[WEBVTT]</a>
> +<!--FORK-->
> +  </p>
>
>   <p>The <code><a href=#the-audio-element>audio</a></code> element is 
> a <a href=#media-element>media element</a>
>   whose <a href=#media-data>media data</a> is ostensibly audio 
> data.</p>
>
> Modified: index
> ===================================================================
> --- index       2012-04-19 22:54:19 UTC (rev 7059)
> +++ index       2012-04-19 23:42:42 UTC (rev 7060)
> @@ -240,7 +240,7 @@
>
>   <header class=head id=head><p><a class=logo 
> href=http://www.whatwg.org/><img alt=WHATWG height=101 
> src=/images/logo width=101></a></p>
>    <hgroup><h1 class=allcaps>HTML</h1>
> -    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 18 
> April 2012</h2>
> +    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 19 
> + April 2012</h2>
>    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
>     <dd><strong><a 
> href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></
> strong></dd>
>     <dt>Multiple-page version:</dt>
> @@ -1525,6 +1525,10 @@
>    the "they're ugly" use case), because of a <a 
> href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0786.html
> >working
>    group chair decision from March 2012</a>.</li>
>
> +   <li>The W3C HTML specification uses the term "caption file" in
> +   place of "WebVTT file" in certain places, because of a <a 
> + href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0557.ht
> + ml>working
> +   group chair decision from March 2012</a>.</li>
> +
>   </ul><p>The following sections are only published in the WHATWG
>   specifications and are not currently available anywhere else:</p>
>
> @@ -26953,12 +26957,17 @@
>   provided, either as a separate track embedded in the video stream,
>   or a separate audio track in an <code><a 
> href=#the-audio-element>audio</a></code> element <a 
> href=#slaved-media-elements title="slaved media elements">slaved</a> 
> to the same controller
>   as the <code><a href=#the-video-element>video</a></code> element(s), 
> or in text form using a
> -  <a href=#webvtt-file>WebVTT file</a> referenced using the <code><a 
> href=#the-track-element>track</a></code>
> -  element and synthesized into speech by the user agent. WebVTT can
> -  also be used to provide chapter titles. For users who would rather
> -  not use a media element at all, transcripts or other textual
> -  alternatives can be provided by simply linking to them in the prose
> -  near the <code><a href=#the-video-element>video</a></code> element. 
> <a href=#refsWEBVTT>[WEBVTT]</a></p>
> +  <a href=#webvtt-file>WebVTT file</a> <!--FORK-->
> +  referenced using the <code><a 
> +href=#the-track-element>track</a></code> element and synthesized into
> +  speech by the user agent. WebVTT can also be used to provide 
> +chapter
> +  titles. For users who would rather not use a media element at all,
> +  transcripts or other textual alternatives can be provided by simply
> +  linking to them in the prose near the <code><a href=#the-video-element>video</a></code> element.
> +<!--FORK-->
> +  <a href=#refsWEBVTT>[WEBVTT]</a>
> +<!--FORK-->
> +  </p>
>
>   <p>The <code><a href=#the-video-element>video</a></code> element is 
> a <a href=#media-element>media element</a>
>   whose <a href=#media-data>media data</a> is ostensibly video data, 
> possibly @@ -27311,9 +27320,16 @@
>   instead of the <code><a href=#the-audio-element>audio</a></code> 
> element to play the audio,
>   allowing users to enable the visual alternatives. Chapter titles can
>   be provided to aid navigation, using the <code><a 
> href=#the-track-element>track</a></code> element
> -  and a WebVTT file. And, naturally, transcripts or other textual
> -  alternatives can be provided by simply linking to them in the prose
> -  near the <code><a href=#the-audio-element>audio</a></code> element. 
> <a href=#refsWEBVTT>[WEBVTT]</a></p>
> +  and a
> +  <a href=#webvtt-file>WebVTT file</a>.
> +<!--FORK-->
> +  And, naturally, transcripts or other textual alternatives can be
> +  provided by simply linking to them in the prose near the
> +  <code><a href=#the-audio-element>audio</a></code> element.
> +<!--FORK-->
> +  <a href=#refsWEBVTT>[WEBVTT]</a>
> +<!--FORK-->
> +  </p>
>
>   <p>The <code><a href=#the-audio-element>audio</a></code> element is 
> a <a href=#media-element>media element</a>
>   whose <a href=#media-data>media data</a> is ostensibly audio 
> data.</p>
>
> Modified: source
> ===================================================================
> --- source      2012-04-19 22:54:19 UTC (rev 7059)
> +++ source      2012-04-19 23:42:42 UTC (rev 7060)
> @@ -252,6 +252,11 @@
>    
> href="http://lists.w3.org/Archives/Public/public-html/2012Mar/0786.htm
> l">working
>    group chair decision from March 2012</a>.</li>
>
> +   <li>The W3C HTML specification uses the term "caption file" in
> +   place of "WebVTT file" in certain places, because of a <a
> +   
> + href="http://lists.w3.org/Archives/Public/public-html/2012Mar/0557.h
> + tml">working
> +   group chair decision from March 2012</a>.</li>
> +
>   </ul>
>
>   <p>The following sections are only published in the WHATWG @@ 
> -29024,12 +29029,20 @@
>   or a separate audio track in an <code>audio</code> element <span
>   title="slaved media elements">slaved</span> to the same controller
>   as the <code>video</code> element(s), or in text form using a
> -  <span>WebVTT file</span> referenced using the <code>track</code>
> -  element and synthesized into speech by the user agent. WebVTT can
> -  also be used to provide chapter titles. For users who would rather
> -  not use a media element at all, transcripts or other textual
> -  alternatives can be provided by simply linking to them in the prose
> -  near the <code>video</code> element. <a 
> href="#refsWEBVTT">[WEBVTT]</a></p>
> +<!--END dev-html--><!--END complete--><!--FORK-->
> +  caption file
> +<!--START dev-html--><!--START complete--><!--END 
> +w3c-html--><!--FORK-->
> +  <span>WebVTT file</span>
> +<!--START w3c-html--><!--FORK-->
> +  referenced using the <code>track</code> element and synthesized 
> +into
> +  speech by the user agent. WebVTT can also be used to provide 
> +chapter
> +  titles. For users who would rather not use a media element at all,
> +  transcripts or other textual alternatives can be provided by simply
> +  linking to them in the prose near the <code>video</code> element.
> +<!--END w3c-html--><!--FORK-->
> +  <a href="#refsWEBVTT">[WEBVTT]</a>
> +<!--START w3c-html--><!--FORK-->
> +  </p>
>
>   <p>The <code>video</code> element is a <span>media element</span>
>   whose <span>media data</span> is ostensibly video data, possibly @@ 
> -29425,9 +29438,19 @@
>   instead of the <code>audio</code> element to play the audio,
>   allowing users to enable the visual alternatives. Chapter titles can
>   be provided to aid navigation, using the <code>track</code> element
> -  and a WebVTT file. And, naturally, transcripts or other textual
> -  alternatives can be provided by simply linking to them in the prose
> -  near the <code>audio</code> element. <a 
> href="#refsWEBVTT">[WEBVTT]</a></p>
> +  and a
> +<!--END dev-html--><!--END complete--><!--FORK-->
> +  caption file.
> +<!--START dev-html--><!--START complete--><!--END 
> +w3c-html--><!--FORK-->
> +  <span>WebVTT file</span>.
> +<!--START w3c-html--><!--FORK-->
> +  And, naturally, transcripts or other textual alternatives can be
> +  provided by simply linking to them in the prose near the
> +  <code>audio</code> element.
> +<!--END w3c-html--><!--FORK-->
> +  <a href="#refsWEBVTT">[WEBVTT]</a>
> +<!--START w3c-html--><!--FORK-->
> +  </p>
>
>   <p>The <code>audio</code> element is a <span>media element</span>
>   whose <span>media data</span> is ostensibly audio data.</p>
>
> _______________________________________________
> Commit-Watchers mailing list
> Commit-Watchers@lists.whatwg.org
> http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org
Received on Sunday, 22 April 2012 19:03:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:31 UTC