CVS html5/html-sourcing-inband-tracks

Update of /sources/public/html5/html-sourcing-inband-tracks
In directory roscoe:/tmp/cvs-serv9580

Modified Files:
	Overview.html 
Log Message:
Sync HTML sourcing inband tracks spec with Git commit 5401da3dee7fe15cb8e9e332dde96a6ab2ad0054

--- /sources/public/html5/html-sourcing-inband-tracks/Overview.html	2014/11/08 07:59:43	1.9
+++ /sources/public/html5/html-sourcing-inband-tracks/Overview.html	2015/02/01 02:59:14	1.10
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
-<html lang="en" dir="ltr" typeof="bibo:Document " about="" property="dcterms:language" content="en">
-<head>
+<html lang="en" dir="ltr" typeof="bibo:Document " prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#">
+<head><meta lang="" property="dc:language" content="en">
     <title>Sourcing In-band Media Resource Tracks from Media Containers into HTML</title>
     <meta charset="utf-8">
     
@@ -158,33 +158,34 @@
     }
 }
 </style><style>/* --- ISSUES/NOTES --- */
-div.issue-title, div.note-title {
+div.issue-title, div.note-title , div.warning-title {
     padding-right:  1em;
     min-width: 7.5em;
     color: #b9ab2d;
 }
 div.issue-title { color: #e05252; }
 div.note-title { color: #2b2; }
-div.issue-title span, div.note-title span {
+div.warning-title { color: #f22; }
+div.issue-title span, div.note-title span, div.warning-title span {
     text-transform: uppercase;
 }
-div.note, div.issue {
+div.note, div.issue, div.warning {
     margin-top: 1em;
     margin-bottom: 1em;
 }
-.note > p:first-child, .issue > p:first-child { margin-top: 0 }
-.issue, .note {
+.note > p:first-child, .issue > p:first-child, .warning > p:first-child { margin-top: 0 }
+.issue, .note, .warning {
     padding: .5em;
     border-left-width: .5em;
     border-left-style: solid;
 }
-div.issue, div.note {
+div.issue, div.note , div.warning {
     padding: 1em 1.2em 0.5em;
     margin: 1em 0;
     position: relative;
     clear: both;
 }
-span.note, span.issue { padding: .1em .5em .15em; }
+span.note, span.issue, span.warning { padding: .1em .5em .15em; }
 
 .issue {
     border-color: #e05252;
@@ -195,7 +196,24 @@
     background: #e9fbe9;
 }
 
+.warning {
+    border-color: #f11;
+    border-right-width: .2em;
+    border-top-width: .2em;
+    border-bottom-width: .2em;
+    border-style: solid;
+    background: #fbe9e9;
+}
 
+.warning-title:before{
+    content: "⚠"; /*U+26A0 WARNING SIGN*/
+    font-size: 3em;
+    float: left;
+    height: 100%;
+    padding-right: .3em;
+    vertical-align: top;
+    margin-top: -0.5em;
+}
 </style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/w3c-unofficial"><!--[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">
   <p>
@@ -205,7 +223,7 @@
   </p>
   <h1 class="title p-name" id="title" property="dcterms:title">Sourcing In-band Media Resource Tracks from Media Containers into HTML</h1>
   
-  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-11-07T20:58:50.000Z" id="unofficial-draft-08-november-2014">Unofficial Draft <time class="dt-published" datetime="2014-11-08">08 November 2014</time></h2>
+  <h2 id="unofficial-draft-01-february-2015">Unofficial Draft <time property="dcterms:issued" class="dt-published" datetime="2015-02-01">01 February 2015</time></h2>
   <dl>
     
     
@@ -219,9 +237,11 @@
     
     
     <dt>Editors:</dt>
-    <dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Silvia Pfeiffer" href="mailto:silviapfeiffer1@gmail.com">Silvia Pfeiffer</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://nicta.com.au/">NICTA</a></span>
+    <dd class="p-author h-card vcard" property="bibo:editor" resource="_:editor0"><span property="rdf:first" typeof="foaf:Person"><meta property="foaf:name" content="Silvia Pfeiffer"><a class="u-url url p-name fn" property="foaf:homepage" href="mailto:silviapfeiffer1@gmail.com">Silvia Pfeiffer</a>, <a property="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://nicta.com.au/">NICTA</a></span>
+<span property="rdf:rest" resource="_:editor1"></span>
 </dd>
-<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><span property="foaf:name" class="p-name fn">Bob Lund</span>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.cablelabs.com/">CableLabs Inc</a></span>
+<dd class="p-author h-card vcard" resource="_:editor1"><span property="rdf:first" typeof="foaf:Person"><span property="foaf:name" class="p-name fn">Bob Lund</span>, <a property="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.cablelabs.com/">CableLabs Inc</a></span>
+<span property="rdf:rest" resource="rdf:nil"></span>
 </dd>
 
     
@@ -243,14 +263,14 @@
   
   <hr>
 </div>
-    <section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:Chapter"><h2 role="heading" id="h2_abstract">Abstract</h2>
+    <section id="abstract" class="introductory" property="dc:abstract"><h2 id="h-abstract" resource="#h-abstract"><span property="xhv:role" resource="xhv:heading">Abstract</span></h2>
       <p>
         This specification is provided to promote interoperability among implementations and users of in-band text tracks sourced for [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]/[<cite><a class="bibref" href="#bib-HTML">HTML</a></cite>] from media resource containers. The specification provides guidelines for the creation of video, audio and text tracks and their attribute values as mapped from in-band tracks from media resource types typically supported by User Agents. It also explains how the UA should map in-band text track content into text track cues.
       </p>
       <p>
         Mappings are defined for [<cite><a class="bibref" href="#bib-MPEGDASH">MPEGDASH</a></cite>], [<cite><a class="bibref" href="#bib-ISOBMFF">ISOBMFF</a></cite>], [<cite><a class="bibref" href="#bib-MPEG2TS">MPEG2TS</a></cite>], [<cite><a class="bibref" href="#bib-OGGSKELETON">OGGSKELETON</a></cite>] and [<cite><a class="bibref" href="#bib-WebM">WebM</a></cite>].
       </p>
-    </section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:Chapter"><h2 role="heading" id="h2_sotd">Status of This Document</h2>
+    </section><section id="sotd" class="introductory"><h2 id="h-sotd" resource="#h-sotd"><span property="xhv:role" resource="xhv:heading">Status of This Document</span></h2>
   
     <p>
       This document is merely a public working draft of a potential specification. It has
@@ -263,24 +283,24 @@
       </p>
     
   
-</section><section id="toc"><h2 class="introductory" 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></li><li class="tocline"><a href="#mpegdash" class="tocxref"><span class="secno">2. </span>MPEG DASH</a></li><li class="tocline"><a href="#mpeg2ts" class="tocxref"><span class="secno">3. </span>MPEG-2 Transport Streams</a></li><li class="tocline"><a href="#mpeg4" class="tocxref"><span class="secno">4. </span>MPEG-4 ISOBMFF</a></li><li class="tocline"><a href="#webm" class="tocxref"><span class="secno">5. </span>WebM</a></li><li class="tocline"><a href="#ogg" class="tocxref"><span class="secno">6. </span>Ogg</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><l class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.1 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory" id="h-toc" resource="#h-toc"><span property="xhv:role" resource="xhv:heading">Table of Contents</span></h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#mpegdash" class="tocxref"><span class="secno">2. </span>MPEG DASH</a></li><li class="tocline"><a href="#mpeg2ts" class="tocxref"><span class="secno">3. </span>MPEG-2 Transport Streams</a></li><li class="tocline"><a href="#mpeg4" class="tocxref"><span class="secno">4. </span>MPEG-4 ISOBMFF</a></li><li class="tocline"><a href="#webm" class="tocxref"><span class="secno">5. </span>WebM</a></li><li class="tocline"><a href="#ogg" class="tocxref"><span class="secno">6. </span>Ogg</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><spa class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.1 </span>Informative references</a></li></ul></li></ul></section>
 
     
 
-    <section id="introduction">
-      <!--OddPage--><h2 role="heading" id="h2_introduction"><span class="secno">1. </span>Introduction</h2>
+    <section id="introduction" typeof="bibo:Chapter" resource="#introduction" property="bibo:hasPart">
+      <!--OddPage--><h2 id="h-introduction" resource="#h-introduction"><span property="xhv:role" resource="xhv:heading"><span class="secno">1. </span>Introduction</span></h2>
       <p>
         The specification maintains mappings from in-band audio, video and other data tracks of media resources to HTML <code>VideoTrack</code>, <code>AudioTrack</code>, and <code>TextTrack</code> objects and their attribute values.
       </p>
       <p>
         A generic rule to follow is that a track as exposed in HTML only ever represents a single semantic concept. When mapping from a media resource, sometimes an in-band track does not relate 1-to-1 to a HTML text, audio or video track.
       </p>
-      <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_1"><span>Note</span></div><p class="">For example, a HTML <code>TextTrack</code> object is either a subtitle track or a caption track, never both. However, in-band text tracks may encapsulate caption and subtitle cues of the same language as a single in-band track. Since a caption track is essentially a subtitle track with additional cues of transcripts of audio-only information, such an encapsulation in a single in-band track can save space. In HTML, these tracks should be exposed as two <code>TextTrack</code> objects, since they represent different semantic concepts. The cues appear in their relevant tracks - subtitle cues would be present in both. This allows users to choose between the two tracks and activate the desired one in the same manner that they do when the two tracks are provided through two track elements.
+      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note1"><span>Note</span></div><p class="">For example, a HTML <code>TextTrack</code> object is either a subtitle track or a caption track, never both. However, in-band text tracks may encapsulate caption and subtitle cues of the same language as a single in-band track. Since a caption track is essentially a subtitle track with additional cues of transcripts of audio-only information, such an encapsulation in a single in-band track can save space. In HTML, these tracks should be exposed as two <code>TextTrack</code> objects, since they represent different semantic concepts. The cues appear in their relevant tracks - subtitle cues would be present in both. This allows users to choose between the two tracks and activate the desired one in the same manner that they do when the two tracks are provided through two track elements.
       </p></div>
-      <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_2"><span>Note</span></div><p class="">
+      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note2"><span>Note</span></div><p class="">
         A similar logic applies to in-band text tracks that have subtitle cues of different languages mixed together in one track. They, too, should be exposed in a track of their own language each.
       </p></div>
-      <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_3"><span>Note</span></div><p class="">
+      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note3"><span>Note</span></div><p class="">
         A further example is when a UA decides to implement rendering for a caption track but without exposing the caption track through the <code>TextTrack</code> API. To the Web developer and the Web page user, such a video appears as though it has burnt-in captions. Therefore, the UA could expose two video tracks on the HTMLMediaElement - one with captions and a <code>kind</code> attribute set to <code>captions</code> and one without captions with a <code>kind</code> attribute set to <code>main</code>. In this way, the user and the Web developer still get the choice of whether to see the video with or without captions.
       </p></div>
       <p>
@@ -291,22 +311,20 @@
       </p>
       <ol>
         <li>Track order.
-        <p>Tracks sourced according to this specification are referenced by HTML <code>TrackList</code> objects (<code>audioTracks</code>, <code>videoTracks</code> or <code>textTracks</code>). The [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]/[<cite><a class="bibref" href="#bib-HTML">HTML</a></cite>] specification mandates that the tracks in those objects be consistently ordered. This requirement insures that the order of tracks is not changed when a track is added or removed, e.g. that <code>videoTracks[3]</code> points to the same object if the tracks with indices 0, 1, 2 and 3 were not removed. This also insures a deterministic result when calls to <code>getTrackById</code> are made with media resources, possibly invalid, that declares two tracks with the same id. This specification defines a consistent ordering of tracks between the media resource and <code>TrackList</code> objects when the media resource is consumed by the user agent.</p>
-        <p>Note that in some media workflows, the order of tracks in a media resource may be subject to changes (e.g. tracks may be added or removed) between authoring and publication. Applications associated with a media resource should not rely on an order of tracks being the same between when the media resource was authored and when it is consumed by the user agent.</p>
-        <p>All media resource formats used in this specification support identifying tracks using a unique identifier. This specification defines how those unique identifiers are mapped onto the <code>id</code> attribute of HTML Track objects. Application authors are encouraged to use the <code>id</code> attribute to identify tracks, rather than the index in a <code>TrackList</code> object.</p>
+        <p>Tracks sourced according to this specification are referenced by HTML <code>TrackList</code> objects (<code>audioTracks</code>, <code>videoTracks</code> or <code>textTracks</code>). The [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]/[<cite><a class="bibref" href="#bib-HTML">HTML</a></cite>] specification mandates that the tracks in those objects be consistently ordered. This requirement insures that the order of tracks is not changed when a track is added or removed, e.g. that <code>videoTracks[3]</code> points to the same object if the tracks with indices 0, 1, 2 and 3 were not removed. This also insures a deterministic result when calls to <code>getTrackById</code> are made with media resources, possibly invalid, that declares two tracks with the same id. This specification defines a consistent ordering of tracks between the media resource and <code>TrackList</code> objects when the media resource is consumed by the user agent. However, in some media workflows, the order of track in a media resource may be subject to changes (e.g. tracks may be added or removed) between authoring and publication. Applications associated with a media resource should not rely on this order of tracks being the same between when the media resource was authored and when it consumed by the user agent. All media resource formats used in this specification support identifying tracks using a unique identifier. This specification defines how those unique identifiers are mapped onto the <code>id</code> attribute of HTML Track objects. Application authors are encouraged to use the <code>id</code> attribute to identify tracks, rather than the index in a <code>TrackList</code> object.</p>
         </li>
-        <li>How to identify the type of tracks - one of audio, video or text.</li>
+        <li>How to identify the type of tracks.</li>
         <li>Setting the attributes <code>id</code>, <code>kind</code>, <code>language</code> and <code>label</code> for sourced <code>TextTrack</code> objects.</li>
         <li>Setting the attributes <code>id</code>, <code>kind</code>, <code>language</code> and <code>label</code> for sourced <code>AudioTrack</code> and <code>VideoTrack</code> objects.</li>
         <li>Mapping Text Track content into text track cues.</li>
       </ol>
     </section>
 
-    <section id="mpegdash" typeof="bibo:Chapter" resource="#mpegdash" rel="bibo:Chapter">
-      <!--OddPage--><h2 role="heading" id="h2_mpegdash"><span class="secno">2. </span>MPEG DASH</h2>
+    <section id="mpegdash" typeof="bibo:Chapter" resource="#mpegdash" property="bibo:hasPart">
+      <!--OddPage--><h2 id="h-mpegdash" resource="#h-mpegdash"><span property="xhv:role" resource="xhv:heading"><span class="secno">2. </span>MPEG DASH</span></h2>
       <b>MIME type/subtype: <code>application/dash+xml</code></b>
       <p>
-        [<cite><a class="bibref" href="#bib-MPEGDASH">MPEGDASH</a></cite>] defines formats for a media manifest, called MPD (Media Presentation Description), which references media containers, called media segments. [<cite><a class="bibref" href="#bib-MPEGDASH">MPEGDASH</a></cite>] also defines some media segments formats based on [<cite><a class="bibref" href="#bib-MPEG2TS">MPEG2TS</a></cite>] or [<cite><a class="bibref" href="#bib-ISOBMFF">ISOBMFF</a></cite>]. Processing of media manifests and segments to expose tracks to Web applications can be done by the user agent. Alternatively, a web application can process the manifests and segments to expose tracks. When the user agent processes MPD and media segments directly, it exposes tracks for <code>AdaptationSet</code> and <code>ContentComponent</code> elements, as defined in this document. When the Web application processes the MPD and media segments, it passes media segments to the user agent according to the MediaSource Extension [<cite><a class="bibref href="#bib-MSE">MSE</a></cite>] specification. In this case, the tracks are exposed by the user agent according to [<cite><a class="bibref" href="#bib-MSE">MSE</a></cite>]. The Web application may set default track attributes from MPD data, using the <code>trackDefaults</code> object, that will be used by the user agent to set attributes not set from initialization segment data.
+        [<cite><a class="bibref" href="#bib-MPEGDASH">MPEGDASH</a></cite>] defines formats for a media manifest, called MPD (Media Presentation Description), which references media containers, called media segments. [<cite><a class="bibref" href="#bib-MPEGDASH">MPEGDASH</a></cite>] also defines some media segments formats based on [<cite><a class="bibref" href="#bib-MPEG2TS">MPEG2TS</a></cite>] or [<cite><a class="bibref" href="#bib-ISOBMFF">ISOBMFF</a></cite>]. Processing of media manifests and segments to expose tracks to Web applications can be done by the user agent. Alternatively, a web application can process the manifests and segments to expose tracks. When the user agent processes MPD and media segments directly, it exposes tracks for <code>AdaptationSet</code> and <code>ContentComponent</code> elements, as defined in this document. When the Web application processes the MPD and media segments, it passes media segments to the user agent according to the MediaSource Extension ([MSE]) specification. n this case, the tracks are exposed by the user agent according to MSE. The Web application may set default track attributes from MPD data, using the <code>trackDefaults</code> object, that will be used by the user agent to set attributes not set from initialization segment data.
       </p>
       <ol>
         <li><p>Track Order</p>
@@ -317,7 +335,7 @@
 
         <li><p>Determining the type of track</p>
           <p>
-            A user agent recognises and supports data from a MPEG DASH media resource as being equivalent to a HTML track based on the <code>AdaptationSet</code> or <code>ContentComponent</code> <code>mimeType</code>:
+            A user agent recognises and supports data from a MPEG DASH media resource as being equivalent to a HTML track based on the AdaptationSet or ContentComponent mimeType:
           </p>
           <ul>
             <li>text track: the <code>mimeType</code> is of main type "<code>application</code>" or "<code>text</code>"</li>
@@ -367,7 +385,7 @@
             <tr>
               <th><code>inBandMetadataTrackDispatchType</code></th>
               <td>
-                If <code>kind</code> is "<code>metadata</code>", the concatenation of the <code>AdaptationSet</code> element and all child <code>Role</code> descriptors. The empty string otherwise.
+                If <code>kind</code> is "<code>metadata</code>" the concatenation of the <code>AdaptationSet</code> element and all child <code>Role</code> descriptors. The empty string otherwise.
               </td>
             </tr>
             <tr>
@@ -435,7 +453,7 @@
             Media content with the MIME type "<code>text/vtt</code>" is in the WebVTT format and should be exposed as a <code>VTTCue</code> object as defined in [<cite><a class="bibref" href="#bib-WEBVTT">WEBVTT</a></cite>].
           </p>
           <p>
-            Media content with the MIME type "<code>application/ttml+xml</code>" is in the TTML format and should be exposed as an as yet to be defined <code>TTMLCue</code> object. Alternatively, browsers can also map the TTML features to <code>VTTCue</code> objects [<cite><a class="bibref" href="#bib-WEBVTT">WEBVTT</a></cite>]. Finally, browsers that cannot render TTML [<cite><a class="bibref" href="#bib-ttaf1-dfxp">ttaf1-dfxp</a></cite>] format data should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML51">HTML51</a></cite>]. In this case, the TTML file must be parsed in its entirety and then converted into a sequence of TTML Intermediate Synchronic Documents (ISDs). Each ISD creates a <code>DataCue</code> object with attributes sourced as follows:
+            Media content with the MIME type "<code>application/ttml+xml</code>" is in the TTML format and should be exposed as an as yet to be defined <code>TTMLCue</code> object. Alternatively, browsers can also map the TTML features to <code>VTTCue</code> objects. Finally, browsers that cannot render TTML [<cite><a class="bibref" href="#bib-ttaf1-dfxp">ttaf1-dfxp</a></cite>] format data should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]. In this case, the TTML file must be parsed in its entirety and then converted into a sequence of TTML Intermediate Synchronic Documents (ISDs). Each ISD creates a <code>DataCue</code> object with attributes sourced as follows: 
             </p><p>
               </p><table>
                 <thead>
@@ -480,8 +498,8 @@
 
     </section>
 
-    <section id="mpeg2ts" typeof="bibo:Chapter" resource="#mpeg2ts" rel="bibo:Chapter">
-      <!--OddPage--><h2 role="heading" id="h2_mpeg2ts"><span class="secno">3. </span>MPEG-2 Transport Streams</h2>
+    <section id="mpeg2ts" typeof="bibo:Chapter" resource="#mpeg2ts" property="bibo:hasPart">
+      <!--OddPage--><h2 id="h-mpeg2ts" resource="#h-mpeg2ts"><span property="xhv:role" resource="xhv:heading"><span class="secno">3. </span>MPEG-2 Transport Streams</span></h2>
       <b>MIME type/subtype: <code>audio/mp2t</code>, <code>video/mp2t</code></b>
 
       <ol>
@@ -489,7 +507,7 @@
           <p>
             Tracks are called "elementary streams" in a MPEG-2 Transport Stream (TS) [<cite><a class="bibref" href="#bib-MPEG2TS">MPEG2TS</a></cite>]. The order in which elementary streams are listed in the "Program Map Table" (PMT) of a MPEG-2 TS is maintained when sourcing multiple MPEG-2 tracks into HTML. Additions or deletions of elementary streams in the PMT should invoke <code>addtrack</code> or <code>removetrack</code> events in the user agent.
           </p>
-          <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_4"><span>Note</span></div><p class="">The order of elementary streams in the PMT may change between when the media resource was created and when it is received by the user agent. Scripts should not infer any information from the ordering, or rely on any particular ordering being present.</p></div>
+          <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note4"><span>Note</span></div><p class="">The order of elementary streams in the PMT may change between when the media resource was created and when it is received by the user agent. Scripts should not infer any information from the ordering, or rely on any particular ordering being present.</p></div>
         </li>
 
         <li><p>Determining the type of track</p>
@@ -507,7 +525,7 @@
                     <li>For <code>stream_type</code> 0x1B, the presence of caption data in the <code>ATSC1_data()</code> field [<cite><a class="bibref" href="#bib-SCTE128-1">SCTE128-1</a></cite>].</li>
                   </ul>
                 </li>
-                <li>a DVB subtitle component [<cite><a class="bibref" href="#bib-DVB-SUB">DVB-SUB</a></cite>] as identified by a <code>subtitling_descriptor</code> [<cite><a class="bibref" href="#bib-DVB-SI">DVB-SI</a></cite>] in the 'Elementary Stream Descriptors' in the PMT entry for a stream with a <code>stream_type</code> of "0x06"</li>
+                <li>a DVB subtitle component [<cite><a class="bibref" href="#bib-DVB-SUB">DVB-SUB</a></cite>] as identified by a <code>subtitling_descriptor</code> [<cite><a class="bibref" href="#bib-DVB-SI">DVB-SI</a></cite>]in the 'Elementary Stream Descriptors' in the PMT entry for a stream with a <code>stream_type</code> of "0x06"</li>
                 <li>an ITU-R System B Teletext component [<cite><a class="bibref" href="#bib-DVB-TXT">DVB-TXT</a></cite>] as identified by an <code>teletext_descriptor</code> [<cite><a class="bibref" href="#bib-DVB-SI">DVB-SI</a></cite>] in the 'Elementary Stream Descriptors' in the PMT entry for a stream with a <code>stream_type</code> of "0x06"</li>
                 <li>a VBI data component [<cite><a class="bibref" href="#bib-DVB-VBI">DVB-VBI</a></cite>] as identified by a <code>VBI_data_descriptor</code> [<cite><a class="bibref" href="#bib-DVB-SI">DVB-SI</a></cite>] or a <code>VBI_teletext_descriptor</code> [<cite><a class="bibref" href="#bib-DVB-SI">DVB-SI</a></cite>] in the 'Elementary Stream Descriptors' in the PMT entry for a stream with a <code>stream_type</code> of "0x06"</li>
               </ul>
@@ -666,7 +684,7 @@
                   <li>If a <code>supplementary_audio_descriptor</code> [<cite><a class="bibref" href="#bib-DVB-SI">DVB-SI</a></cite>] is present in the PMT for an audio component, the value is derived according to the audio purpose defined in table&nbsp;J.3 of [<cite><a class="bibref" href="#bib-DVB-SI">DVB-SI</a></cite>] using the following rules:
                     <ul>
                       <li>"<code>main</code>" if PSI signalling of audio purpose indicates "Main audio" for the audio track that the user agent would select by default, otherwise to "<code>translation</code>"
-                      <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_5"><span>Note</span></div><p class="">Need to define how UA would select track by default.</p></div>
+                      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note5"><span>Note</span></div><p class="">Need to define how UA would select track by default.</p></div>
                       </li>
                       <li>components with an audio purpose of "Audio description (broadcast-mix)" map to "<code>main-desc</code>"</li>
                       <li>components with an audio purpose of "Audio description (receiver-mix)":
@@ -732,7 +750,7 @@
           <ol type="a">
             <li><p>Metadata cues</p>
               <p>
-                Cues on an MPEG-2 metadata text track are created as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML51">HTML51</a></cite>]. Each <code>section</code> in an elementary stream identified as a text track creates a <code>DataCue</code> object with its <code>TextTrackCue</code> attributes sourced as follows:
+                Cues on an MPEG-2 metadata text track are created as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]. Each <code>section</code> in an elementary stream identified as a text track creates a <code>DataCue</code> object with its <code>TextTrackCue</code> attributes sourced as follows:
               </p>
               <table>
                 <thead>
@@ -772,7 +790,7 @@
               </p><ul>
                 <li>CEA 708
                   <p>
-                    MPEG-2 TS captions in the CEA 708 format [<cite><a class="bibref" href="#bib-CEA708">CEA708</a></cite>] are carried in the video stream in Picture User Data [<cite><a class="bibref" href="#bib-ATSC53-4">ATSC53-4</a></cite>] for <code>stream_type</code> 0x02 and in Supplemental Enhancement Information [<cite><a class="bibref" href="#bib-ATSC72-1">ATSC72-1</a></cite>] for <code>stream_type</code> 0x1B. Browsers that can render the CEA 708 format should expose them in as yet to be specified <code>CEA708Cue</code> objects. Alternatively, browsers can also map the CEA 708 features to <code>VTTCue</code> objects [<cite><a class="bibref" href="#bib-VTT708">VTT708</a></cite>]. Finally, browsers that cannot render CEA 708 captions should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML51">HTML51</a></cite>]. In this case, each <code>service_block</code> in a digital TV closed caption (DTVCC) transport channel creates a <code>DataCue</code> object with <code>TetTrackCue</code> attributes sourced as follows:
+                    MPEG-2 TS captions in the CEA 708 format [<cite><a class="bibref" href="#bib-CEA708">CEA708</a></cite>] are carried in the video stream in Picture User Data [<cite><a class="bibref" href="#bib-ATSC53-4">ATSC53-4</a></cite>] for <code>stream_type</code> 0x02 and in Supplemental Enhancement Information [<cite><a class="bibref" href="#bib-ATSC72-1">ATSC72-1</a></cite>] for <code>stream_type</code> 0x1B. Browsers that can render the CEA 708 format should expose them in as yet to be specified <code>CEA708Cue</code> objects. Alternatively, browsers can also map the CEA 708 features to <code>VTTCue</code> objects [<cite><a class="bibref" href="#bib-VTT708">VTT708</a></cite>]. Finally, browsers that cannot render CEA 708 captions should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]. In this case, each <code>service_block</code> in a digital TV closed caption (DTVCC) transport channel creates a <code>DataCue</code> object with <code>TextrackCue</code> attributes sourced as follows:
                   </p>
                   <table>
                     <thead>
@@ -793,7 +811,7 @@
                       <th><code>endTime</code></th>
                       <td>
                         The sum of the <code>startTime</code> and 4 seconds.
-                        <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_6"><span>Note</span></div><p class="">
+                        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note6"><span>Note</span></div><p class="">
                           CEA 708 captions do not have an explicit end time - a rendering device derives the end time for a caption based on subsequent caption data. Setting <code>endTime</code> equal to <code>startTime</code> might be more appropriate but this would require better support for zero-length cues, as proposed in <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=25693">HTML Bug 25693</a>.
                         </p></div>
                       </td>
@@ -820,7 +838,7 @@
               <ul>
                 <li>SCTE 27
                   <p>
-                    MPEG-2 TS subtitles in the SCTE 27 format [<cite><a class="bibref" href="#bib-SCTE27">SCTE27</a></cite>] should should be exposed in an as yet to be specified <code>SCTE27Cue</code> objects. Alternatively, browsers can also map the SCTE 27 features to <code>VTTCue</code> object via an as yet to be specified mapping process. Finally, browsers that cannot render SCTE 27 subtitles, should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML51">HTML51</a></cite>]. In this case, each <code>section</code> in an elementary stream identified as a subtitles text track creates a <code>DataCue</code> object with <code>TextTrackCue</code> attributes sourced as follows:
+                    MPEG-2 TS subtitles in the SCTE 27 format [<cite><a class="bibref" href="#bib-SCTE27">SCTE27</a></cite>] should should be exposed in an as yet to be specified <code>SCTE27Cue</code> objects. Alternatively, browsers can also map the SCTE 27 features to <code>VTTCue</code> object via an as yet to be specified mapping process. Finally, browsers that cannot render SCTE 27 subtitles, should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]. In this case, each <code>section</code> in an elementary stream identified as a subtitles text track creates a <code>DataCue</code> object with <code>TextTrackCue</code> attributes sourced as follows:
                   </p>
                   <table>
                     <thead>
@@ -870,8 +888,8 @@
 
     </section>
 
-    <section id="mpeg4" typeof="bibo:Chapter" resource="#mpeg4" rel="bibo:Chapter">
-      <!--OddPage--><h2 role="heading" id="h2_mpeg4"><span class="secno">4. </span>MPEG-4 ISOBMFF</h2>
+    <section id="mpeg4" typeof="bibo:Chapter" resource="#mpeg4" property="bibo:hasPart">
+      <!--OddPage--><h2 id="h-mpeg4" resource="#h-mpeg4"><span property="xhv:role" resource="xhv:heading"><span class="secno">4. </span>MPEG-4 ISOBMFF</span></h2>
       <b>MIME type/subtype: <code>audio/mp4</code>, <code>video/mp4</code>, <code>application/mp4</code></b>
 
       <ol>
@@ -912,7 +930,7 @@
                     <ul>
                       <li><dfn id="WebVTTcaption">WebVTT caption</dfn>: <code>handler_type</code> is "<code>text</code>" and <code>SampleEntry</code> format is <code>WVTTSampleEntry</code> [<cite><a class="bibref" href="#bib-ISO14496-30">ISO14496-30</a></cite>] and the VTT metadata header <code>Kind</code> is "<code>captions</code>"</li>
                       <li><dfn id="SMPTETTcaption">SMPTE-TT caption</dfn>: <code>handler_type</code> is "<code>subt</code>" and <code>SampleEntry</code> format is <code>XMLSubtitleSampleEntry</code> [<cite><a class="bibref" href="#bib-ISO14496-30">ISO14496-30</a></cite>] and the <code>namespace</code> is set to "<code>http://www.smpte-ra.org/schemas/2052-1/2013/smpte-tt#cea708</code>" [<cite><a class="bibref" href="#bib-SMPTE2052-11">SMPTE2052-11</a></cite>].</li>
-                      <li></li><li><dfn id="3GPPcaption">3GPP caption</dfn>: <code>handler_type</code> is "<code>text</code>" and the <code>SampleEntry</code> code (<code>format</code> field) is "<code>tx3g</code>". <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_7"><span>Note</span></div><p class="">Are all sample entries of this type "<code>captions</code>"?</p></div></li>
+                      <li></li><li><dfn id="3GPPcaption">3GPP caption</dfn>: <code>handler_type</code> is "<code>text</code>" and the <code>SampleEntry</code> code (<code>format</code> field) is "<code>tx3g</code>". <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note7"><span>Note</span></div><p class="">Are all sample entries of this type "<code>captions</code>"?</p></div></li>
                     </ul>
                   </li>
                   <li>"subtitles":
@@ -1054,7 +1072,7 @@
             </tbody></table>
           <p></p>
           <p>
-            ISOBMFF text tracks carry TTML data if the media handler type is "<code>subt</code>" and an <code>XMLSubtileSampleEntry</code> format is used with a TTML-based <code>name_space</code> field, as described in [<cite><a class="bibref" href="#bib-ISO14496-30">ISO14496-30</a></cite>]. Browsers that can render text tracks in the TTML format should expose an as yet to be defined <code>TTMLCue</code>. Alternatively, browsers can also map the TTML features to <code>VTTCue</code> objects. Finally, browsers that cannot render TTML [<cite><a class="bibref" href="#bib-ttaf1-dfxp">ttaf1-dfxp</a></cite>] format data should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML51">HTML51</a></cite>]. Each TTML subtitle sample consists of an XML document and creates a <code>DataCue</code> object with attributes sourced as follows:
+            ISOBMFF text tracks carry TTML data if the media handler type is "<code>subt</code>" and an <code>XMLSubtileSampleEntry</code> format is used with a TTML-based <code>name_space</code> field, as described in [<cite><a class="bibref" href="#bib-ISO14496-30">ISO14496-30</a></cite>]. Browsers that can render text tracks in the TTML format should expose an as yet to be defined <code>TTMLCue</code>. Alternatively, browsers can also map the TTML features to <code>VTTCue</code> objects. Finally, browsers that cannot render TTML [<cite><a class="bibref" href="#bib-ttaf1-dfxp">ttaf1-dfxp</a></cite>] format data should expose them as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]. Each TTML subtitle sample consists of an XML document and creates a <code>DataCue</code> object with attributes sourced as follows: 
             </p><p>
               </p><table>
                 <thead>
@@ -1099,8 +1117,8 @@
 
     </section>
 
-    <section id="webm" typeof="bibo:Chapter" resource="#webm" rel="bibo:Chapter">
-      <!--OddPage--><h2 role="heading" id="h2_webm"><span class="secno">5. </span>WebM</h2>
+    <section id="webm" typeof="bibo:Chapter" resource="#webm" property="bibo:hasPart">
+      <!--OddPage--><h2 id="h-webm" resource="#h-webm"><span property="xhv:role" resource="xhv:heading"><span class="secno">5. </span>WebM</span></h2>
       <b>MIME type/subtype: <code>audio/webm</code>, <code>video/webm</code></b>
 
       <ol>
@@ -1178,7 +1196,7 @@
           <p>
             Tracks of <code>kind</code> "<code>chapters</code>" are found in the "<code>Chapters</code>" section of the WebM file Segment, which are all at the beginning of the WebM file, such that chapters can be used for navigation. The details of this mapping have not been specified yet and simply point to the more powerful Matroska chapter specification [<cite><a class="bibref" href="#bib-Matroska">Matroska</a></cite>]. Presumably, the <code>id</code> attribute could be found in <code>EditionUID</code>, <code>label</code> is empty, and <code>language</code> can come from the first ChapterAtom's <code>ChapLanguage</code> value.
           </p>
-          <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_8"><span>Note</span></div><p class="">
+          <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note8"><span>Note</span></div><p class="">
             The Matroska container format, which is the basis for WebM, has specifications for other text tracks, in particular SRT, SSA/ASS, and VOBSUB. The described attribute mappings can be applied to these, too, except that the <code>kind</code> field will always be "<code>subtitles</code>". The information of their <code>CodecPrivate</code> field is exposed in the <code>inBandMetadataTrackDispatchType</code> attribute.
           </p></div>
         </li>
@@ -1271,15 +1289,15 @@
               </td>
             </tr>
           </tbody></table>
-          <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_9"><span>Note</span></div><p class="">Other Matroska container format's text tracks can also be mapped to <code>TextTrackCue</code> objects. These will be created as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML51">HTML51</a></cite>] with <code>id</code>, <code>startTime</code>, <code>endTime</code>, and <code>pauseOnExit</code> attributes filled identically to the <code>VTTCue</code> objects, and the <code>data</code> attribute containing the Block's data.
+          <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note9"><span>Note</span></div><p class="">Other Matroska container format's text tracks can also be mapped to <code>TextTrackCue</code> objects. These will be created as <code>DataCue</code> objects [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>] with <code>id</code>, <code>startTime</code>, <code>endTime</code>, and <code>pauseOnExit</code> attributes filled identically to the <code>VTTCue</code> objects, and the <code>data</code> attribute containing the Block's data.
           </p></div>
         </li>
       </ol>
 
     </section>
 
-    <section id="ogg" typeof="bibo:Chapter" resource="#ogg" rel="bibo:Chapter">
-      <!--OddPage--><h2 role="heading" id="h2_ogg"><span class="secno">6. </span>Ogg</h2>
+    <section id="ogg" typeof="bibo:Chapter" resource="#ogg" property="bibo:hasPart">
+      <!--OddPage--><h2 id="h-ogg" resource="#h-ogg"><span property="xhv:role" resource="xhv:heading"><span class="secno">6. </span>Ogg</span></h2>
       <b>MIME type/subtype: <code>audio/ogg</code>, <code>video/ogg</code></b>
 
       <ol>
@@ -1392,7 +1410,7 @@
             <tr>
               <th><code>label</code></th>
               <td>
-                Content of the <code>title</code> message header field of the fisbone header. If no Skeleton header is available, the empty string.
+                Content of the &lt;<code>title</code> message header field of the fisbone header. If no Skeleton header is available, the empty string.
               </td>
             </tr>
             <tr>
@@ -1411,8 +1429,8 @@
 
     </section>
 
-    <section class="appendix" id="acknowledgements">
-      <!--OddPage--><h2 role="heading" id="h2_acknowledgements"><span class="secno">A. </span>Acknowledgements</h2>
+    <section class="appendix" id="acknowledgements" typeof="bibo:Chapter" resource="#acknowledgements" property="bibo:hasPart">
+      <!--OddPage--><h2 id="h-acknowledgements" resource="#h-acknowledgements"><span property="xhv:role" resource="xhv:heading"><span class="secno">A. </span>Acknowledgements</span></h2>
       <p>
         Thanks to all In-band Track Community Group members in helping to create this specification.
       </p>
@@ -1421,34 +1439,32 @@
     </section>
   
 
-<form id="bug-assist-form" action="//www.w3.org/Bugs/Public/enter_bug.cgi" target="_blank">See a problem? Select text and <input type="submit" accesskey="f" style="font-family: Tahoma, sans-serif; font-size: 10px; " value="file a bug"><input type="hidden" name="comment" value=""><input type="hidden" name="short_desc" value="[InbandTracks] "><input type="hidden" name="product" value="HTML WG"><input type="hidden" name="component" value="Sourcing In-band Media Resource Tracks">.</form><section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:Chapter"><!--OddPage--><h2 role="heading" id="h2_references"><span class="secno">B. </span>References</h2><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:Chapter"><h3 role="heading" id="h3_informative-references"><span class="secno">B.1 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-3GPP-TT">[3GPP-TT]</dt><dd rel="dcterms:references"><a href="htp: //www.3gpp.org/ftp/Specs/archive/26_series/26.245/26245-c00.zip"><cite>Transparent end-to-end Packet switched Streaming Service (PSS) Timed text format (Release 12)</cite></a>. URL: <a href="http: //www.3gpp.org/ftp/Specs/archive/26_series/26.245/26245-c00.zip">http: //www.3gpp.org/ftp/Specs/archive/26_series/26.245/26245-c00.zip</a>
-</dd><dt id="bib-ATSC52">[ATSC52]</dt><dd rel="dcterms:references"><a href="http://www.atsc.org/cms/standards/A52-2012(12-17).pdf"><cite>Digital Audio Compression (AC-3, E-AC-3)</cite></a>. 17 December 2012. URL: <a href="http://www.atsc.org/cms/standards/A52-2012(12-17).pdf">http://www.atsc.org/cms/standards/A52-2012(12-17).pdf</a>
-</dd><dt id="bib-ATSC53-4">[ATSC53-4]</dt><dd rel="dcterms:references"><a href="http://www.atsc.org/cms/standards/a53/a_53-Part-4-2009.pdf"><cite>MPEG-2 Video System Characteristics</cite></a>. 7 August 2009. URL: <a href="http://www.atsc.org/cms/standards/a53/a_53-Part-4-2009.pdf">http://www.atsc.org/cms/standards/a53/a_53-Part-4-2009.pdf</a>
-</dd><dt id="bib-ATSC65">[ATSC65]</dt><dd rel="dcterms:references"><a href="http://www.atsc.org/cms/standards/A65_2013.pdf"><cite>Program and System Information Protocol for Terrestrial Broadcast and Cable</cite></a>. 7 August 2013. URL: <a href="http://www.atsc.org/cms/standards/A65_2013.pdf">http://www.atsc.org/cms/standards/A65_2013.pdf</a>
-</dd><dt id="bib-ATSC72-1">[ATSC72-1]</dt><dd rel="dcterms:references"><a href="http://www.atsc.org/cms/standards/a72/A72-Part-1-2014.pdf"><cite>Video System Characteristics of AVC in the ATSC Digital Television System</cite></a>. 18 February 2014. URL: <a href="http://www.atsc.org/cms/standards/a72/A72-Part-1-2014.pdf">http://www.atsc.org/cms/standards/a72/A72-Part-1-2014.pdf</a>
-</dd><dt id="bib-CEA708">[CEA708]</dt><dd rel="dcterms:references"><a href="http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx"><cite>Digital Television (DTV) Closed Captioning CEA-708-B</cite></a>. URL: <a href="http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx">http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx</a>
-</dd><dt id="bib-DVB-SI">[DVB-SI]</dt><dd rel="dcterms:references"><a href="http://www.etsi.org/deliver/etsi_en/300400_300499/300468/01.14.01_60/en_300468v011401p.pdf"><cite>ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems"</cite></a>. URL: <a href="http://www.etsi.org/deliver/etsi_en/300400_300499/300468/01.14.01_60/en_300468v011401p.pdf">http://www.etsi.org/deliver/etsi_en/300400_300499/300468/01.14.01_60/en_300468v011401p.pdf</a>
-</dd><dt id="bib-DVB-SUB">[DVB-SUB]</dt><dd rel="dcterms:references"><a href="http://www.etsi.org/deliver/etsi_en/300700_300799/300743/01.05.01_60/en_300743v010501p.pdf"><cite>ETSI EN 300 743: "Digital Video Broadcasting (DVB); Subtitling systems"</cite></a>. URL: <a href="http://www.etsi.org/deliver/etsi_en/300700_300799/300743/01.05.01_60/en_300743v010501p.pdf">http://www.etsi.org/deliver/etsi_en/300700_300799/300743/01.05.01_60/en_300743v010501p.pdf</a>
-</dd><dt id="bib-DVB-TXT">[DVB-TXT]</dt><dd rel="dcterms:references"><a href="http://www.etsi.org/deliver/etsi_en/300400_300499/300472/01.03.01_60/en_300472v010301p.pdf"><cite>ETSI EN 300 472: "Digital Video Broadcasting (DVB); Specification for conveying ITU-R System B Teletext in DVB bitstreams"</cite></a>. URL: <a href="http://www.etsi.org/deliver/etsi_en/300400_300499/300472/01.03.01_60/en_300472v010301p.pdf">http://www.etsi.org/deliver/etsi_en/300400_300499/300472/01.03.01_60/en_300472v010301p.pdf</a>
-</dd><dt id="bib-DVB-VBI">[DVB-VBI]</dt><dd rel="dcterms:references"><a href="http://www.etsi.org/deliver/etsi_en/301700_301799/301775/01.02.01_60/en_301775v010201p.pdf"><cite>ETSI EN 301 775: ""Digital Video Broadcasting (DVB); Specification for the carriage of Vertical Blanking Information (VBI) data in DVB bitstreams</cite></a>. URL: <a href="http://www.etsi.org/deliver/etsi_en/301700_301799/301775/01.02.01_60/en_301775v010201p.pdf">http://www.etsi.org/deliver/etsi_en/301700_301799/301775/01.02.01_60/en_301775v010201p.pdf</a>
-</dd><dt id="bib-HTML">[HTML]</dt><dd rel="dcterms:references">Ian Hickson. <a href="https://html.spec.whatwg.org/"><cite>HTML</cite></a>. Living Standard. URL: <a href="https://html.spec.whatwg.org/">https://html.spec.whatwg.org/</a>
-</dd><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:references">Robin Berjon; Steve Faulkner; Travis Leithead; Erika Doyle Navara; Edward O'Connor; Silvia Pfeiffer. <a href="http://www.w3.org/TR/html5/"><cite>HTML5</cite></a>. 28 October 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a>
-</dd><dt id="bib-HTML51">[HTML51]</dt><dd rel="dcterms:references">Robin Berjon; Steve Faulkner; Travis Leithead; Erika Doyle Navara; Edward O'Connor; Silvia Pfeiffer. <a href="http://www.w3.org/TR/html51/"><cite>HTML 5.1</cite></a>. 17 June 2014. W3C Working Draft. URL: <a href="http://www.w3.org/TR/html51/">http://www.w3.org/TR/html51/</a>
-</dd><dt id="bib-ISO14496-30">[ISO14496-30]</dt><dd rel="dcterms:references"><a href="http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=63107"><cite>Information technology — Coding of audio-visual objects — Part 30: Timed text and other visual overlays in ISO base media file format</cite></a>. 11 March 2014. URL: <a href="http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=63107">http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=63107</a>
-</dd><dt id="bib-ISOBMFF">[ISOBMFF]</dt><dd rel="dcterms:references"><a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c061988_ISO_IEC_14496-12_2012.zip"><cite>Information technology -- Coding of audio-visual objects -- Part 12: ISO base media file format</cite></a> ISO/IEC 14496-12:2012. URL: <a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c061988_ISO_IEC_14496-12_2012.zip">http://standards.iso.org/ittf/PubliclyAvailableStandards/c061988_ISO_IEC_14496-12_2012.zip</a> 
-</dd><dt id="bib-MPEG2TS">[MPEG2TS]</dt><dd rel="dcterms:references"><a href="http://www.itu.int/rec/T-REC-H.222.0-201206-I"><cite>Information technology -- Generic coding of moving pictures and associated audio information: Systems ITU-T Rec. H.222.0 / ISO/IEC 13818-1:2013</cite></a>. URL: <a href="http://www.itu.int/rec/T-REC-H.222.0-201206-I">http://www.itu.int/rec/T-REC-H.222.0-201206-I</a>
-</dd><dt id="bib-MPEGDASH">[MPEGDASH]</dt><dd rel="dcterms:references"><a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip"><cite>ISO/IEC 23009-1:2014 Information technology -- Dynamic adaptive streaming over HTTP (DASH) -- Part 1: Media presentation description and segment formats</cite></a>. URL: <a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip">http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip</a>
-</dd><dt id="bib-MSE">[MSE]</dt><dd rel="dcterms:references">Aaron Colwell; Adrian Bateman; Mark Watson. <a href="http://www.w3.org/TR/media-source/"><cite>Media Source Extensions</cite></a>. 17 July 2014. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/media-source/">http://www.w3.org/TR/media-source/</a>
-</dd><dt id="bib-Matroska">[Matroska]</dt><dd rel="dcterms:references"><a href="http://matroska.org/technical/specs/index.html"><cite>Matroska Specifications</cite></a>. 9 January 2014. URL: <a href="http://matroska.org/technical/specs/index.html">http://matroska.org/technical/specs/index.html</a>
-</dd><dt id="bib-OGG">[OGG]</dt><dd rel="dcterms:references">S. Pfeiffer. <a href="http://www.ietf.org/rfc/rfc3533.txt"><cite>The Ogg Encapsulation Format Version 0</cite></a>. May 2003. Informational. URL: <a href="http://www.ietf.org/rfc/rfc3533.txt">http://www.ietf.org/rfc/rfc3533.txt</a>
-</dd><dt id="bib-OGGSKELETON">[OGGSKELETON]</dt><dd rel="dcterms:references"><a href="http://wiki.xiph.org/SkeletonHeaders"><cite>Ogg Skeleton 4 Message Headers</cite></a>. 17 March 2014. URL: <a href="http://wiki.xiph.org/SkeletonHeaders">http://wiki.xiph.org/SkeletonHeaders</a>
-</dd><dt id="bib-SCTE128-1">[SCTE128-1]</dt><dd rel="dcterms:references"><a href="http://www.scte.org/documents/pdf/Standards/ANSI_SCTE%20128-1%202013.pdf"><cite>ANSI/SCTE 128-1 2013 AVC Constraints for Cable Television Part 1- Coding</cite></a>. URL: <a href="http://www.scte.org/documents/pdf/Standards/ANSI_SCTE%20128-1%202013.pdf">http://www.scte.org/documents/pdf/Standards/ANSI_SCTE%20128-1%202013.pdf</a>
-</dd><dt id="bib-SCTE193-2">[SCTE193-2]</dt><dd rel="dcterms:references"><a href="http://www.scte.org/documents/pdf/standards/SCTE%20193-2%202014.pdf"><cite>SCTE 193-2 2014 MPEG-4 AAC Family Audio System – Part 2 Constraints for Carriage over MPEG-2 Transport</cite></a>. URL: <a href="http://www.scte.org/documents/pdf/standards/SCTE%20193-2%202014.pdf">http://www.scte.org/documents/pdf/standards/SCTE%20193-2%202014.pdf</a>
-</dd><dt id="bib-SCTE27">[SCTE27]</dt><dd rel="dcterms:references"><a href="http://www.scte.org/documents/pdf/Standards/ANSI_SCTE_27_2011.pdf"><cite>Subtitling Methods For Broadcast Cable</cite></a>. URL: <a href="http://www.scte.org/documents/pdf/Standards/ANSI_SCTE_27_2011.pdf">http://www.scte.org/documents/pdf/Standards/ANSI_SCTE_27_2011.pdf</a>
-</dd><dt id="bib-SMPTE2052-11">[SMPTE2052-11]</dt><dd rel="dcterms:references"><a href="https: //www.smpte.org/sites/default/files/RP2052-11-2013.pdf"><cite>Conversion from CEA-708 Caption Data to SMPTE-TT</cite></a>. URL: <a href="https: //www.smpte.org/sites/default/files/RP2052-11-2013.pdf">https: //www.smpte.org/sites/default/files/RP2052-11-2013.pdf</a>
-</dd><dt id="bib-VTT708">[VTT708]</dt><dd rel="dcterms:references">Silvia Pfeiffer. <a href="https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/608toVTT.html"><cite>Conversion of 608/708 captions to WebVTT</cite></a>. Draft Community Group Report. URL: <a href="https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/608toVTT.html">https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/608toVTT.html</a>
-</dd><dt id="bib-WEBVTT">[WEBVTT]</dt><dd rel="dcterms:references">Silvia Pfeiffer; Philip Jägenstedt; Ian Hickson. <a href="http://dev.w3.org/html5/webvtt/"><cite>WebVTT: The Web Video Text Tracks Format</cite></a>. 16 May 2014. W3C Editor's Draft. URL: <a href="http://dev.w3.org/html5/webvtt/">http://dev.w3.org/html5/webvtt/</a>
-</dd><dt id="bib-WEBVTT-WEBM">[WEBVTT-WEBM]</dt><dd rel="dcterms:references">Matthew Heaney; Frank Galligan. <a href="http://wiki.webmproject.org/webm-metadata/temporal-metadata/webvtt-in-webm"><cite>Embedding WebVTT in WebM</cite></a>. 1 February 2012. URL: <a href="http://wiki.webmproject.org/webm-metadata/temporal-metadata/webvtt-in-webm">http://wiki.webmproject.org/webm-metadata/temporal-metadata/webvtt-in-webm</a>
-</dd><dt id="bib-WebM">[WebM]</dt><dd rel="dcterms:references"><a href="http://www.webmproject.org/code/specs/container/"><cite>WebM Container Guidelines</cite></a>. 28 April 2014. URL: <a href="http://www.webmproject.org/code/specs/container/">http://www.webmproject.org/code/specs/container/</a>
-</dd><dt id="bib-ttaf1-dfxp">[ttaf1-dfxp]</dt><dd rel="dcterms:references">Glenn Adams. <a href="http://www.w3.org/TR/ttaf1-dfxp/"><cite>Timed Text Markup Language (TTML) 1.0 (Second Edition)</cite></a>. 9 July 2013. W3C Proposed Edited Recommendation. URL: <a href="http://www.w3.org/TR/ttaf1-dfxp/">http://www.w3.org/TR/ttaf1-dfxp/</a>

[30 lines skipped]

Received on Sunday, 1 February 2015 02:59:19 UTC