- From: CVS User pjgenste <cvsmail@w3.org>
- Date: Mon, 29 Sep 2014 08:19:09 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/webvtt
In directory roscoe:/tmp/cvs-serv25626
Modified Files:
Overview.html
Log Message:
Sync WebVTT with Git commit 04c4ad061a83eb8f4e6715184c63401a97569515
--- /sources/public/html5/webvtt/Overview.html 2014/09/08 09:29:03 1.168
+++ /sources/public/html5/webvtt/Overview.html 2014/09/29 08:19:09 1.169
@@ -1,16 +1,16 @@
<!DOCTYPE html>
<html lang="en-US-x-hixie">
<head>
- <title>WebVTT: The Web Video Text Tracks Format</title>
- <meta charset="utf-8">
-
-
- <!-- script to register bugs -->
- <script src="https://dvcs.w3.org/hg/webcomponents/raw-file/tip/assets/scripts/bug-assist.js"></script>
- <meta name="bug.short_desc" content="[WebVTT] ">
- <meta name="bug.product" content="TextTracks CG">
- <meta name="bug.component" content="WebVTT">
- <style>
+ <title>WebVTT: The Web Video Text Tracks Format</title>
+ <meta charset="utf-8">
+
+
+ <!-- script to register bugs -->
+ <script src="https://dvcs.w3.org/hg/webcomponents/raw-file/tip/assets/scripts/bug-assist.js"></script>
+ <meta name="bug.short_desc" content="[WebVTT] ">
+ <meta name="bug.product" content="TextTracks CG">
+ <meta name="bug.component" content="WebVTT">
+ <style>
body {
line-height: 1.35;
}
@@ -113,8 +113,8 @@
#respec-ui{
top: 100px !important;
}
- </style>
- <style>/*****************************************************************
+ </style>
+ <style>/*****************************************************************
* ReSpec 3 CSS
* Robin Berjon - http://berjon.com/
*****************************************************************/
@@ -157,7 +157,7 @@
}
code {
- color: #ff4500;
+ color: #C83500;
}
/* --- TOC --- */
@@ -269,13 +269,13 @@
</style><link rel="stylesheet" href="https://www.w3.org/community/src/css/spec/cg-draft.css"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
- <body style="" class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+ <body style="" class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
<p>
<a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
</p>
<h1 class="title p-name" id="title">WebVTT: The Web Video Text Tracks Format</h1>
- <h2 id="draft-community-group-report-08-september-2014">Draft Community Group Report <time class="dt-published" datetime="2014-09-08">08 September 2014</time></h2>
+ <h2 id="draft-community-group-report-29-september-2014">Draft Community Group Report <time class="dt-published" datetime="2014-09-29">29 September 2014</time></h2>
<dl>
@@ -310,11 +310,11 @@
<hr>
</div>
<section id="abstract" class="introductory" property="dcterms:abstract" datatype=""><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
- <p>This is the specification of WebVTT, the Web Video Text Tracks format.</p>
+ <p>This is the specification of WebVTT, the Web Video Text Tracks format.</p>
- <p>If you wish to make comments or file bugs regarding this document in a manner
- that is tracked by the W3C, please submit them via <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=TextTracks%20CG&component=WebVTT&short_desc=%5BWebVTT%5D%20">our
- public bug database</a>.</p>
+ <p>If you wish to make comments or file bugs regarding this document in a manner that is tracked
+ by the W3C, please submit them via <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=TextTracks%20CG&component=WebVTT&short_desc=%5BWebVTT%5D%20">our
+ public bug database</a>.</p>
</section><section id="sotd" class="introductory"><h2 aria-level="1" role="heading" id="h2_sotd">Status of This Document</h2>
<p>
@@ -329,24 +329,25 @@
<a href="http://www.w3.org/community/">W3C Community and Business Groups</a>.
</p>
- <p>This specification is being developed as a Living Specification. There is a plan to take a snapshot and publish it as a W3C Recommendation through the <a href="http://www.w3.org/AudioVideo/TT/">W3C Timed Text Working Group</a>.</p>
+ <p>This specification is being developed as a Living Specification. There is a plan to take a
+ snapshot and publish it as a W3C Recommendation through the <a href="http://www.w3.org/AudioVideo/TT/">W3C Timed Text Working Group</a>.</p>
</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#cues-with-multiple-lines" class="tocxref"><span class="secno">1.1 </span>Cues with multiple lines</a></li><li class="tocline"><a href="#comments" class="tocxref"><span class="secno">1.2 </span>Comments</a></li><li class="tocline"><a href="#other-features" class="tocxref"><span class="secno">1.3 </span>Other features</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a><ul class="toc"><li class="tocline"><a href="#document-conformance" class="tocxref"><span class="secno">2.1 </span>Document Conformance</a></li><li class="tocline"><a href="#dependencies" class="tocxref"><span class="secno">2.2 </span>Dependencies</a></li></u></li><li class="tocline"><a href="#data-model" class="tocxref"><span class="secno">3. </span>Data model</a><ul class="toc"><li class="tocline"><a href="#text-track-cues" class="tocxref"><span class="secno">3.1 </span>Text track cues</a></li><li class="tocline"><a href="#text-track-regions" class="tocxref"><span class="secno">3.2 </span>Text track regions</a></li></ul></li><li class="tocline"><a href="#syntax" class="tocxref"><span class="secno">4. </span>Syntax</a><ul class="toc"><li class="tocline"><a href="#webvtt-file-structure" class="tocxref"><span class="secno">4.1 </span>WebVTT file structure</a></li><li class="tocline"><a href="#webvtt-comments" class="tocxref"><span class="secno">4.2 </span>WebVTT comments</a></li><li class="tocline"><a href="#types-of-webvtt-cue-payload" class="tocxref"><span class="secno">4.3 </span>Types of WebVTT cue payload</a><ul class="toc"><li class="tocline"><a href="#webvtt-metadata-text" class="tocxref"><span class="secno">4.3.1 </span>WebVTT metadata text</a></li><li cass="tocline"><a href="#webvtt-cue-text" class="tocxref"><span class="secno">4.3.2 </span>WebVTT cue text</a></li></ul></li><li class="tocline"><a href="#webvtt-cue-settings" class="tocxref"><span class="secno">4.4 </span>WebVTT cue settings</a><ul class="toc"><li class="tocline"><a href="#webvtt-region-definition" class="tocxref"><span class="secno">4.4.1 </span>WebVTT region definition</a></li><li class="tocline"><a href="#webvtt-cue-settings-1" class="tocxref"><span class="secno">4.4.2 </span>WebVTT cue settings</a></li></ul></li><li class="tocline"><a href="#properties-of-cue-sequences" class="tocxref"><span class="secno">4.5 </span>Properties of cue sequences</a><ul class="toc"><li class="tocline"><a href="#webvtt-file-using-only-nested-cues" class="tocxref"><span class="secno">4.5.1 </span>WebVTT file using only nested cues</a></li></ul></li><li class="tocline"><a href="#types-of-webvtt-files" class="tocxref"><span class="secno">4.6 </span>Types of WebVTT files</a><ul class="toc"><li class="tocline">< href="#webvtt-file-using-metadata-content" class="tocxref"><span class="secno">4.6.1 </span>WebVTT file using metadata content</a></li><li class="tocline"><a href="#webvtt-file-using-chapter-title-text" class="tocxref"><span class="secno">4.6.2 </span>WebVTT file using chapter title text</a></li><li class="tocline"><a href="#webvtt-file-using-cue-text" class="tocxref"><span class="secno">4.6.3 </span>WebVTT file using cue text</a></li></ul></li></ul></li><li class="tocline"><a href="#parsing" class="tocxref"><span class="secno">5. </span>Parsing</a><ul class="toc"><li class="tocline"><a href="#webvtt-file-parsing" class="tocxref"><span class="secno">5.1 </span>WebVTT file parsing</a></li><li class="tocline"><a href="#webvtt-region-settings-parsing" class="tocxref"><span class="secno">5.2 </span>WebVTT region settings parsing</a></li><li class="tocline"><a href="#webvtt-cue-timings-and-settings-parsing" class="tocxref"><span class="secno">5.3 </span>WebVTT cue timings and settings parsing</a></li><li class=tocline"><a href="#webvtt-cue-text-parsing-rules" class="tocxref"><span class="secno">5.4 </span><span>WebVTT cue text parsing rules</span></a></li><li class="tocline"><a href="#webvtt-cue-text-dom-construction-rules" class="tocxref"><span class="secno">5.5 </span><span>WebVTT cue text DOM construction rules</span></a></li></ul></li><li class="tocline"><a href="#rendering" class="tocxref"><span class="secno">6. </span>Rendering</a><ul class="toc"><li class="tocline"><a href="#cues-in-isolation" class="tocxref"><span class="secno">6.1 </span>Cues in isolation</a></li><li class="tocline"><a href="#cues-with-video" class="tocxref"><span class="secno">6.2 </span>Cues with video</a><ul class="toc"><li class="tocline"><a href="#processing-model" class="tocxref"><span class="secno">6.2.1 </span>Processing model</a></li><li class="tocline"><a href="#applying-css-properties-to-webvtt-node-objects" class="tocxref"><span class="secno">6.2.2 </span>Applying CSS properties to <span title="WebVTT Node Object" class="formrLink">WebVTT Node Objects</span></a></li><li class="tocline"><a href="#css-extensions" class="tocxref"><span class="secno">6.2.3 </span>CSS extensions</a><ul class="toc"><li class="tocline"><a href="#the-cue-pseudo-element" class="tocxref"><span class="secno">6.2.3.1 </span>The '::cue' pseudo-element</a></li><li class="tocline"><a href="#the-past-and-future-pseudo-classes" class="tocxref"><span class="secno">6.2.3.2 </span>The ':past' and ':future' pseudo-classes</a></li><li class="tocline"><a href="#the-cue-region-pseudo-element" class="tocxref"><span class="secno">6.2.3.3 </span>The '::cue-region' pseudo-element</a></li></ul></li></ul></li></ul></li><li class="tocline"><a href="#api" class="tocxref"><span class="secno">7. </span>API</a><ul class="toc"><li class="tocline"><a href="#the-vttcue-interface" class="tocxref"><span class="secno">7.1 </span>The <span class="formerLink"><code>VTTCue</code></span> interface</a></li><li class="tocline"><a href="#the-vttregion-interface" class="tocxref"><span class="ecno">7.2 </span>The <span class="formerLink"><code>VTTRegion</code></span> interface</a></li></ul></li><li class="tocline"><a href="#iana-considerations" class="tocxref"><span class="secno">8. </span>IANA considerations</a><ul class="toc"><li class="tocline"><a href="#text-vtt" class="tocxref"><span class="secno">8.1 </span><span><code>text/vtt</code></span></a></li></ul></li><li class="tocline"><a href="#references-1" class="tocxref"><span class="secno">9. </span>References</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">10. </span>Acknowledgements</a></li></ul></section>
<section id="introduction">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_introduction"><span class="secno">1. </span>Introduction</h2>
+ <!--OddPage--><h2 aria-level="1" role="heading" id="h2_introduction"><span class="secno">1. </span>Introduction</h2>
- <p><i>This section is non-normative.</i></p>
+ <p><i>This section is non-normative.</i></p>
- <p>The <dfn id="dfn-webvtt">WebVTT</dfn> (Web Video Text Tracks) format is
- intended for marking up external text track resources.</p>
+ <p>The <dfn id="dfn-webvtt">WebVTT</dfn> (Web Video Text Tracks) format is intended for marking up external text
+ track resources.</p>
- <p>The main use for WebVTT files is captioning video content. Here
- is a sample file that captions an interview:</p>
+ <p>The main use for WebVTT files is captioning video content. Here is a sample file that captions
+ an interview:</p>
- <pre>WEBVTT
+ <pre>WEBVTT
00:11.000 --> 00:13.000
<v Roger Bingham>We are in New York City
@@ -387,21 +388,21 @@
00:35.500 --> 00:38.000
<v Roger Bingham>You know I'm so excited my glasses are falling off here.</pre>
- <section id="cues-with-multiple-lines">
- <h3 aria-level="2" role="heading" id="h3_cues-with-multiple-lines"><span class="secno">1.1 </span>Cues with multiple lines</h3>
+ <section id="cues-with-multiple-lines">
+ <h3 aria-level="2" role="heading" id="h3_cues-with-multiple-lines"><span class="secno">1.1 </span>Cues with multiple lines</h3>
- <p><i>This section is non-normative.</i></p>
+ <p><i>This section is non-normative.</i></p>
- <p>Line breaks in cues are honored. User agents will also insert extra line breaks if necessary to
- fit the cue in the cue's width. In general, therefore, authors are encouraged to write cues all on
- one line except when a line break is definitely necessary, and to not manually line-wrap for
- aesthetic reasons alone.</p>
+ <p>Line breaks in cues are honored. User agents will also insert extra line breaks if necessary
+ to fit the cue in the cue's width. In general, therefore, authors are encouraged to write cues
+ all on one line except when a line break is definitely necessary, and to not manually line-wrap
+ for aesthetic reasons alone.</p>
- <div class="example">
+ <div class="example">
- <p>These captions on a public service announcement video demonstrate line breaking:</p>
+ <p>These captions on a public service announcement video demonstrate line breaking:</p>
- <pre>WEBVTT
+ <pre>WEBVTT
00:01.000 --> 00:04.000
Never drink liquid nitrogen.
@@ -413,12 +414,12 @@
00:10.000 --> 00:14.000
The Organisation for Sample Public Service Announcements accepts no liability for the content of this advertisement, or for the consequences of any actions taken on the basis of the information provided.</pre>
- <p>The first cue is simple, it will probably just display on one line. The second will take two
- lines, one for each speaker. The third will wrap to fit the width of the video, possibly taking
- multiple lines. For example, the three cues could look like this:</p>
+ <p>The first cue is simple, it will probably just display on one line. The second will take two
+ lines, one for each speaker. The third will wrap to fit the width of the video, possibly taking
+ multiple lines. For example, the three cues could look like this:</p>
-<!-- 50 -->
- <pre> Never drink liquid nitrogen.
+ <!-- 50 -->
+ <pre> Never drink liquid nitrogen.
— It will perforate your stomach.
— You could die.
@@ -429,11 +430,11 @@
consequences of any actions taken on the
basis of the information provided.</pre>
- <p>If the width of the cues is smaller, the first two cues could wrap as well, as in the following
- example. Note how the second cue's explicit line break is still honored, however:</p>
+ <p>If the width of the cues is smaller, the first two cues could wrap as well, as in the
+ following example. Note how the second cue's explicit line break is still honored, however:</p>
-<!-- 25 -->
- <pre> Never drink
+ <!-- 25 -->
+ <pre> Never drink
liquid nitrogen.
— It will perforate
@@ -451,27 +452,26 @@
the basis of the
information provided.</pre>
- <p>Also notice how the wrapping is done so as to keep the line lengths balanced.</p>
+ <p>Also notice how the wrapping is done so as to keep the line lengths balanced.</p>
- </div>
- </section>
+ </div>
+ </section>
- <section id="comments">
- <h3 aria-level="2" role="heading" id="h3_comments"><span class="secno">1.2 </span>Comments</h3>
+ <section id="comments">
+ <h3 aria-level="2" role="heading" id="h3_comments"><span class="secno">1.2 </span>Comments</h3>
- <p><i>This section is non-normative.</i></p>
+ <p><i>This section is non-normative.</i></p>
- <p>Comments can be included in WebVTT files.</p>
+ <p>Comments can be included in WebVTT files.</p>
- <p>Comments are just blocks that are preceded by a blank line,
- start with the word "<code>NOTE</code>" (followed by a
- space or newline), and end at the first blank line.</p>
+ <p>Comments are just blocks that are preceded by a blank line, start with the word
+ "<code>NOTE</code>" (followed by a space or newline), and end at the first blank line.</p>
- <div class="example">
+ <div class="example">
- <p>Here, a one-line comment is used to note a possible problem with a cue.</p>
+ <p>Here, a one-line comment is used to note a possible problem with a cue.</p>
- <pre>WEBVTT
+ <pre>WEBVTT
00:01.000 --> 00:04.000
Never drink liquid nitrogen.
@@ -482,13 +482,13 @@
— It will perforate your stomach.
— You could die.</pre>
- </div>
+ </div>
- <div class="example">
+ <div class="example">
- <p>In this example, the author has written many comments.</p>
+ <p>In this example, the author has written many comments.</p>
- <pre>WEBVTT
+ <pre>WEBVTT
NOTE
This file was written by Jill. I hope
@@ -510,21 +510,21 @@
NOTE end of file</pre>
- </div>
- </section>
+ </div>
+ </section>
- <section id="other-features">
- <h3 aria-level="2" role="heading" id="h3_other-features"><span class="secno">1.3 </span>Other features</h3>
+ <section id="other-features">
+ <h3 aria-level="2" role="heading" id="h3_other-features"><span class="secno">1.3 </span>Other features</h3>
- <p><i>This section is non-normative.</i></p>
+ <p><i>This section is non-normative.</i></p>
- <p>WebVTT also supports some less-often used features.</p>
+ <p>WebVTT also supports some less-often used features.</p>
- <div class="example">
+ <div class="example">
- <p>In this example, the cues have an identifier:</p>
+ <p>In this example, the cues have an identifier:</p>
- <pre>WEBVTT
+ <pre>WEBVTT
1
00:00.000 --> 00:02.000
@@ -534,22 +534,22 @@
00:04.000 --> 00:05.000
Transcribed by Celestials™</pre>
- <p>This allows a style sheet to specifically target the cues (notice the use
- of CSS character escape sequences):</p>
+ <p>This allows a style sheet to specifically target the cues (notice the use of CSS character
+ escape sequences):</p>
- <pre>::cue(#\31) { color: green; }
+ <pre>::cue(#\31) { color: green; }
::cue(#transcript\ credit) { color: red; }</pre>
- </div>
+ </div>
- <div class="example">
+ <div class="example">
- <p>In this example, each cue says who is talking using voice spans. In the first cue, the span
- specifying the speaker is also annotated with two classes, "first" and "loud". In the third cue,
- there is also some italics text (not associated with a specific speaker). The last cue is
- annotated with just the class "loud".</p>
+ <p>In this example, each cue says who is talking using voice spans. In the first cue, the span
+ specifying the speaker is also annotated with two classes, "first" and "loud". In the third
+ cue, there is also some italics text (not associated with a specific speaker). The last cue is
+ annotated with just the class "loud".</p>
- <pre>WEBVTT
+ <pre>WEBVTT
00:00.000 --> 00:02.000
<v.first.loud Esme>It's a blue apple tree!
@@ -563,22 +563,22 @@
00:06.000 --> 00:08.000
<v.loud Mary>That's awesome!</pre>
- <p>Notice that as a special exception, the voice spans don't have to be closed if they cover the
- entire cue text.</p>
+ <p>Notice that as a special exception, the voice spans don't have to be closed if they cover
+ the entire cue text.</p>
- <p>Style sheets can style these spans:</p>
+ <p>Style sheets can style these spans:</p>
- <pre>::cue(v[voice="Esme"]) { color: blue }
+ <pre>::cue(v[voice="Esme"]) { color: blue }
::cue(v[voice="Mary"]) { color: green }
::cue(i) { font-style: italic }
::cue(.loud) { font-size: 2em }</pre>
- </div>
+ </div>
- <div class="example">
- <p>This example shows how to position cues at explicit positions in the video viewport.</p>
+ <div class="example">
+ <p>This example shows how to position cues at explicit positions in the video viewport.</p>
- <pre>WEBVTT
+ <pre>WEBVTT
00:00:00.000 --> 00:00:04.000 position:10%,start align:start size:35%
Where did he go?
@@ -589,13 +589,23 @@
00:00:04.000 --> 00:00:06.500 position:45%,end align:middle size:35%
What are you waiting for?</pre>
- <p>The cues cover only 35% of the video viewport's width. The first cue has its <a title="text track cue box" href="#dfn-text-track-cue-box" class="internalDFN">cue box</a> left aligned at the 10% mark of the video viewport width and the text is left aligned within that box - probably underneath a speaker on the left of the video image. "start" alignment of the cue box is the default for start aligned text, so does not need to be specified in "position". The second cue has its <a title="text track cue box" href="#dfn-text-track-cue-box" class="internalDFN">cue box</a> right aligned at the 90% mark of the video viewport width. The same effect can be achieved with "position:55%,start", which explicitly positions the cue box. The third cue has middle aligned text within the same type of cue box as the first cue.</p>
- </div>
+ <p>The cues cover only 35% of the video viewport's width. The first cue has its <a title="text
+ track cue box" href="#dfn-text-track-cue-box" class="internalDFN">cue box</a> left aligned at the 10% mark of the video viewport width and the
+ text is left aligned within that box - probably underneath a speaker on the left of the video
+ image. "start" alignment of the cue box is the default for start aligned text, so does not need
+ to be specified in "position". The second cue has its <a title="text track cue box" href="#dfn-text-track-cue-box" class="internalDFN">cue box</a>
+ right aligned at the 90% mark of the video viewport width. The same effect can be achieved with
+ "position:55%,start", which explicitly positions the cue box. The third cue has middle aligned
+ text within the same type of cue box as the first cue.</p>
+ </div>
+
+ <div class="example">
+ <p>This example shows two regions containing rollup captions for two different speakers. Fred's
+ cues scroll up in a region in the left half of the video, Bill's cues scroll up in a region on
+ the right half of the video. Fred's first cue disappears at 12.5sec even though it is defined
+ until 20sec because its region is limited to 3 lines and at 12.5sec a fourth cue appears:</p>
- <div class="example">
- <p>This example shows two regions containing rollup captions for two different speakers. Fred's cues scroll up in a region in the left half of the video, Bill's cues scroll up in a region on the right half of the video. Fred's first cue disappears at 12.5sec even though it is defined until 20sec because its region is limited to 3 lines and at 12.5sec a fourth cue appears:</p>
-
- <pre>WEBVTT
+ <pre>WEBVTT
Region: id=fred width=40% lines=3 regionanchor=0%,100% viewportanchor=10%,90% scroll=up
Region: id=bill width=40% lines=3 regionanchor=100%,100% viewportanchor=90%,90% scroll=up
@@ -617,316 +627,348 @@
00:00:12.500 --> 00:00:32.500 region:fred align:left
<v Fred>OK, let's go.</pre>
- <p>Note that regions are only defined for horizontal cues.</p>
+ <p>Note that regions are only defined for horizontal cues.</p>
- </div>
+ </div>
- </section>
+ </section>
</section>
<section id="conformance">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">2. </span>Conformance</h2>
+ <!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">2. </span>Conformance</h2>
- <h2 id="conformance-for-authors">Conformance for authors</h2>
+ <h2 id="conformance-for-authors">Conformance for authors</h2>
- <section>
- <p>The <a href="#h2_syntax">Syntax</a> section of this specification defines
- what consists a valid WebVTT document. Authors need to follow the
- <a href="#h2_syntax">Syntax</a> specification and are encouraged to use a
- validator.</p>
-
- <p>The <a href="#h2_parser">Parser</a> section of this specification defines
- in some detail the required processing for valid and also for invalid
- documents. It is a little more tolerant to author errors than the syntax
- allows, so as to reject less documents and provide for extensibility.
- However, authors must not take advantage of it. Only documents that follow
- the <a href="#h2_syntax">Syntax</a> specification are valid.</p>
- </section>
+ <section>
[9397 lines skipped]
Received on Monday, 29 September 2014 08:19:11 UTC