Changeset 1152

Show
Ignore:
Timestamp:
2005-03-18 16:29:38 (4 years ago)
Author:
silvia
Message:

The Internet-Draft Editor requires now conformance to RFC 3667,
which I had to include.
Updates to all I-Ds sent to the IETF.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • standards/anx-ids/draft-pfeiffer-annodex-02.html

    r1130 r1152  
    33<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 
    44<meta name="description" content="The Annodex exchange format for time-continuous bitstreams, Version 3.0"> 
    5 <meta name="generator" content="xml2rfc v1.25 (http://xml.resource.org/)"> 
     5<meta name="generator" content="xml2rfc v1.28 (http://xml.resource.org/)"> 
    66<style type='text/css'> 
    77<!-- 
    …… 
    6161    span.emph { font-style: italic; } 
    6262    span.strong { font-weight: bold; } 
    63     span.verb { font-family: "Courier New", Courier, monospace ; } 
     63    span.verb, span.vbare { font-family: "Courier New", Courier, monospace ; } 
     64 
     65    span.vemph { font-style: italic; font-family: "Courier New", Courier, monospace ; } 
     66    span.vstrong { font-weight: bold; font-family: "Courier New", Courier, monospace ; } 
     67    span.vdeluxe { font-weight: bold; font-style: italic; font-family: "Courier New", Courier, monospace ; } 
    6468 
    6569    ol.text { margin-left: 2em; margin-right: 2em; } 
    …… 
    110114<tr><td class="header">Network Working Group</td><td class="header">S. Pfeiffer</td></tr> 
    111115<tr><td class="header">Internet-Draft</td><td class="header">C. Parker</td></tr> 
    112 <tr><td class="header">Expires: September 13, 2005</td><td class="header">A. Pang</td></tr> 
     116<tr><td class="header">Expires: September 20, 2005</td><td class="header">A. Pang</td></tr> 
    113117<tr><td class="header">&nbsp;</td><td class="header">CSIRO</td></tr> 
    114 <tr><td class="header">&nbsp;</td><td class="header">March 15, 2005</td></tr> 
     118<tr><td class="header">&nbsp;</td><td class="header">March 19, 2005</td></tr> 
    115119</table></td></tr></table> 
    116120<div align="right"><span class="title"><br />The Annodex exchange format for time-continuous bitstreams, Version 3.0</span></div> 
    …… 
    119123<h3>Status of this Memo</h3> 
    120124<p> 
    121 This document is an Internet-Draft and is 
    122 in full conformance with all provisions of Section 10 of RFC2026.</p> 
     125This document is an Internet-Draft and is subject to all provisions 
     126of Section&nbsp;3 of RFC&nbsp;3667. 
     127By submitting this Internet-Draft, 
     128each author represents that any applicable patent or other IPR claims of which 
     129he or she is aware have been or will be disclosed, 
     130and any of which he or she become aware will be disclosed, 
     131in accordance with RFC&nbsp;3668.</p> 
    123132<p> 
    124133Internet-Drafts are working documents of the Internet Engineering 
    …… 
    138147<a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p> 
    139148<p> 
    140 This Internet-Draft will expire on September 13, 2005.</p> 
     149This Internet-Draft will expire on September 20, 2005.</p> 
    141150 
    142151<h3>Copyright Notice</h3> 
    143152<p> 
    144 Copyright (C) The Internet Society (2005). All Rights Reserved.</p> 
     153Copyright (C) The Internet Society (2005).</p> 
    145154 
    146155<h3>Abstract</h3> 
    …… 
    151160      time-continuous bitstreams and textual meta information attached 
    152161      to temporal fragments of the binary bitstreams. The meta information 
    153       is described in the <a class="info" href="#CMML">Continuous Media Markup 
    154       Language (CMML)<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17]. Annodex enables integration of 
     162      is given in the Continuous Media Markup Language (CMML). 
     163      Annodex enables integration of 
    155164      time-continuous bitstreams into the browsing and searching 
    156165      functionality of the World Wide Web. 
    …… 
    167176      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 
    168177      "OPTIONAL" in this document are to be interpreted as described 
    169       in <a class="info" href="#KEYWORDS">RFC 2119<span>Bradner, S., Key words for use in RFCs to Indicate Requirements Levels, March 1997.</span></a>[1]. 
     178      in RFC 2119. 
    170179       
    171180</p><a name="toc"></a><br /><hr /> 
    …… 
    181190Features of Annodex<br /> 
    182191<a href="#anchor5">3.</a>&nbsp; 
    183 Authoring the Annodex exchange format<br /> 
     192Authoring exchange format<br /> 
    184193<a href="#anchor6">4.</a>&nbsp; 
    185194The Ogg skeleton logical bitstream<br /> 
    …… 
    249258</p> 
    250259<p>Text documents were enabled for the Web through definition of a 
    251       markup language (<a class="info" href="#HTML">HTML<span>World Wide Web Consortium, HTML 4.01 Specification, December 1999.</span></a>[3]) for text documents 
     260      markup language (<a class="info" href="#HTML">HTML<span>World Wide Web Consortium, HTML 4.01 Specification, December 1999.</span></a>[1]) for text documents 
    252261      to enable description of the structure of a document, and thus 
    253262      allow for the separation of content from presentation. This 
    254263      specification takes the same approach for time-continuous documents. 
    255264      The markup language for time-continuous documents is called CMML, 
    256       short for <a class="info" href="#CMML">Continuous Media Markup Language<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17]. 
     265      short for <a class="info" href="#CMML">Continuous Media Markup Language<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2]. 
    257266      It describes the structure of time-continuous documents and allows 
    258267      for a clean separation of content from presentation. 
    …… 
    277286      that are further up in functionality. The container format of 
    278287      Annodex is the <a class="info" href="#Ogg">Ogg encapsulation format version 
    279       0<span>Pfeiffer, S., The Ogg encapsulation format version 0, May 2003.</span></a>[13]. Annodex is an Ogg bitstream containing a "skeleton" and a 
     288      0<span>Pfeiffer, S., The Ogg encapsulation format version 0, May 2003.</span></a>[3]. Annodex is an Ogg bitstream containing a "skeleton" and a 
    280289      CMML logical bitstream, in addition to other temporally interleaved 
    281290      data bitstreams. Ogg skeleton is a logical bitstream that describes all 
    …… 
    291300      logical bitstream, which is still valuable as a multitrack media 
    292301      format that can be addressed through <a class="info" href="#timedURI">temporal 
    293       hyperlinks<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[16], however it is not a first class citizen on the 
     302      hyperlinks<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[4], however it is not a first class citizen on the 
    294303      Web because Web search engines cannot index and crawl it. 
    295304       
    …… 
    306315<p>Please note that this document assumes that the reader understands 
    307316      the <a class="info" href="#Ogg">Ogg encapsulation format 
    308       version 0<span>Pfeiffer, S., The Ogg encapsulation format version 0, May 2003.</span></a>[13]. Also, knowledge of the network protocols <a class="info" href="#HTTP">HTTP<span>Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P. and T. Berners-Lee, Hypertext Transfer Protocol -- HTTP/1.1, June 1999.</span></a>[6] and <a class="info" href="#RTSP">RTP/RTSP<span>Schulzrinne, H., Rao, A. and R. Lanphier, Real Time Streaming Protocol (RTSP), April 1998.</span></a>[9] 
    309       as well as the extension of URIs to address <a class="info" href="#timedURI">temporal offsets into Web resources<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[16] are 
     317      version 0<span>Pfeiffer, S., The Ogg encapsulation format version 0, May 2003.</span></a>[3]. Also, knowledge of the network protocols <a class="info" href="#HTTP">HTTP<span>Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P. and T. Berners-Lee, Hypertext Transfer Protocol -- HTTP/1.1, June 1999.</span></a>[5] and <a class="info" href="#RTSP">RTP/RTSP<span>Schulzrinne, H., Rao, A. and R. Lanphier, Real Time Streaming Protocol (RTSP), April 1998.</span></a>[6] 
     318      as well as the extension of URIs to address <a class="info" href="#timedURI">temporal offsets into Web resources<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[4] are 
    310319      a prerequisite to understanding this document. To find out more about 
    311320      the use of Annodex for creating searchable and surfable Web resources, 
    312321      refer to the specification of the <a class="info" href="#CMML">Continuous Media 
    313       Markup Language (CMML Version 2.0)<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17]. 
     322      Markup Language (CMML Version 2.0)<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2]. 
    314323       
    315324</p> 
    …… 
    342351 
    343352D1  |    |   |        |         |    |        |      |       |   |   | 
    344     __________________________________________________________________   
     353    __________________________________________________________________ 
    345354 
    346355D2  |          |            |            |             |          |  | 
    …… 
    356365    |-----------------------------------------------------------------> 
    357366 
    358         </pre> 
     367</pre> 
    359368 
    360369<p>Bitstreams of time-continuous data are being regarded as a sequence 
    …… 
    388397</p> 
    389398<p>Distribution of Annodex format bitstreams is performed using a 
    390       network protocol such as <a class="info" href="#HTTP">HTTP<span>Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P. and T. Berners-Lee, Hypertext Transfer Protocol -- HTTP/1.1, June 1999.</span></a>[6] or 
    391       <a class="info" href="#RTSP">RTP/RTSP<span>Schulzrinne, H., Rao, A. and R. Lanphier, Real Time Streaming Protocol (RTSP), April 1998.</span></a>[9]. The basic process is the 
     399      network protocol such as <a class="info" href="#HTTP">HTTP<span>Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P. and T. Berners-Lee, Hypertext Transfer Protocol -- HTTP/1.1, June 1999.</span></a>[5] or 
     400      <a class="info" href="#RTSP">RTP/RTSP<span>Schulzrinne, H., Rao, A. and R. Lanphier, Real Time Streaming Protocol (RTSP), April 1998.</span></a>[6]. The basic process is the 
    392401      following: The client dispatches a download or streaming request 
    393402      to the server with a certain URI. The server resolves the URI 
    …… 
    427436    _____________________________________________ 
    428437 
    429         </pre> 
     438</pre> 
    430439 
    431440<p>The Annodex format has been designed to accommodate for 
    …… 
    475484<a name="anchor5"></a><br /><hr /> 
    476485<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table> 
    477 <a name="rfc.section.3"></a><h3>3.&nbsp;Authoring the Annodex exchange format</h3> 
    478  
    479 <p>For authoring of Annodex bitstream information, the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17] is defined. CMML's "stream" tag has 
     486<a name="rfc.section.3"></a><h3>3.&nbsp;Authoring exchange format</h3> 
     487 
     488<p>For authoring of Annodex bitstream information, the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2] is defined. CMML's "stream" tag has 
    480489      been designed to author the skeleton bitstream and describe the data 
    481490      bitstreams to be interleaved into an Ogg bitstream. All other 
    …… 
    517526       
    518527</p> 
    519 <p>The CMML media mapping is defined in the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17] specification. However, for identification 
     528<p>The CMML media mapping is defined in the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2] specification. However, for identification 
    520529      of an Annodex bitstream, the bos page of the CMML logical bitstream 
    521530      needs to be identifiable, which is provided through the first 12 Bytes 
    522531      of the CMML ident packet containing the magic numbers and the version 
    523       information: Other fields exists and are described in the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17] specification. 
     532      information: Other fields exists and are described in the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2] specification. 
    524533      </p> 
    525534<ol class="text"> 
    …… 
    576585   | ... 
    577586 
    578          </pre> 
     587</pre> 
    579588 
    580589<a name="anchor6"></a><br /><hr /> 
    …… 
    613622      specifies the content of the "skeleton" logical bitstream and how 
    614623      it is mapped into Ogg. Knowledge of the Ogg bitstream format as 
    615       specified in the <a class="info" href="#Ogg">Ogg RFC<span>Pfeiffer, S., The Ogg encapsulation format version 0, May 2003.</span></a>[13] is presumed. 
     624      specified in the <a class="info" href="#Ogg">Ogg RFC<span>Pfeiffer, S., The Ogg encapsulation format version 0, May 2003.</span></a>[3] is presumed. 
    616625      Please also refer to that document for descriptions of the terms 
    617626      used in this document. 
    …… 
    656665</ul> 
    657666 
    658 <p>For authoring of the skeleton bitstream information the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17] can be used. CMML's "stream" tag has 
     667<p>For authoring of the skeleton bitstream information the <a class="info" href="#CMML">CMML<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2] can be used. CMML's "stream" tag has 
    659668      been designed with that purpose in mind. However, it is not mandatory 
    660669      to use CMML for authoring of skeleton information - that information 
    …… 
    706715   |                                                               | 60-63 
    707716   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    708            </pre> 
     717</pre> 
    709718 
    710719<p>Fields with more than one Byte length are encoded LSB (least 
    …… 
    838847   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    839848 
    840            </pre> 
     849</pre> 
    841850 
    842851<p>Fields with more than one Byte length are encoded LSB 
    …… 
    10741083                        ------------------------------- 
    10751084                        video bitstream 2 
    1076            </pre> 
     1085</pre> 
    10771086 
    10781087<p>The time point at which an Annodex bitstream starts (t_0 in the 
    …… 
    10901099      be any positive time. For example, in professional video production, 
    10911100      the first frame of video of a program normally refers to a SMPTE 
    1092       basetime of 01:00:00:00, not 00:00:00:00 (see also the <a class="info" href="#timedURI">temporal URI addressing<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[16] specification). 
     1101      basetime of 01:00:00:00, not 00:00:00:00 (see also the <a class="info" href="#timedURI">temporal URI addressing<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[4] specification). 
    10931102      Associating such a practice to a digital video resource requires 
    10941103      a way to store that basetime with the resource and interpreting it 
    …… 
    11581167        |  keyindex               |  keyoffset         | 
    11591168        ------------------------------------------------ 
    1160        </pre> 
     1169</pre> 
    11611170 
    11621171<p>The granuleshift field of the skeleton secondary header packets 
    …… 
    11831192<pre> 
    11841193t_page = basetime + ((keyindex + keyoffset) / granulerate) 
    1185       </pre> 
     1194</pre> 
    11861195<p> 
    11871196 
    …… 
    11991208<pre> 
    12001209t_page = 4 + ((88200 + 0) / 44100) = 6 
    1201       </pre> 
     1210</pre> 
    12021211<p> 
    12031212 
    …… 
    12171226<pre> 
    12181227t_page = 0 + ((62 + 5) / 25) = 2.68 sec 
    1219       </pre> 
     1228</pre> 
    12201229<p> 
    12211230 
    …… 
    12711280<p>Addressing into an Annodex bitstream is 
    12721281      possible with the <a class="info" href="#timedURI">temporal URI 
    1273       addressing<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[16] scheme. Time is specified as a temporal offset 
     1282      addressing<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[4] scheme. Time is specified as a temporal offset 
    12741283      from the "beginning" of the stream, making use of the basetime 
    12751284      field. Time offsets can also be specified as calendar dates and 
    …… 
    13731382      important also to allow caching of such files as is required for Web 
    13741383      proxies and described in <a class="info" href="#timedURI">temporal URI 
    1375       addressing<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[16]. 
     1384      addressing<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[4]. 
    13761385       
    13771386</p> 
    …… 
    14441453        hyperlinking into Annodex bitstreams via URIs is possible 
    14451454        with the <a class="info" href="#timedURI">temporal URI query and 
    1446         fragment specification<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[16]. For the query case, an Annodex 
     1455        fragment specification<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[4]. For the query case, an Annodex 
    14471456        server must supports the "X-Accept-TimeURI" http header field 
    14481457        (see the <a class="info" href="#timedURI">temporal URI query 
    1449         specification<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[16] for more details). The 
     1458        specification<span>Pfeiffer, S., Parker, C. and A. Pang, Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress), March 2005.</span></a>[4] for more details). The 
    14501459        "X-Accept-Range-Redirect" and "X-Range-Redirect" http header 
    14511460        fields MAY also be supported by an Annodex server and user agent. 
    …… 
    14551464        addressing of clips via their name given in the "id" tag is 
    14561465        also supported. The same mechanisms as specified in the 
    1457         <a class="info" href="#CMML">CMML specification<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17] apply to 
     1466        <a class="info" href="#CMML">CMML specification<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2] apply to 
    14581467        Annodex analogously. In particular, the id addressing is also 
    14591468        regarded as an alias for a time offset and an Annodex conformant 
    14601469        server that supports Annodex temporal URI addressing MUST also 
    14611470        support named URI addressing (see the <a class="info" href="#CMML">CMML 
    1462         specification<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[17] for more details). 
     1471        specification<span>Pfeiffer, S., Parker, C. and A. Pang, The Continuous Media Markup Language (CMML), Version 2.0 (work in progress), March 2005.</span></a>[2] for more details). 
    14631472         
    14641473</p> 
    …… 
    15211530<pre> 
    15221531Accpet: text/x-cmml; q=1, application/x-annodex; q=0.5 
    1523       </pre> 
     1532</pre> 
    15241533<p> 
    15251534 
    …… 
    16871696<a name="rfc.references1"></a><br /><hr /> 
    16881697<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table> 
    1689 <h3>9&nbsp;References</h3> 
     1698<h3>9.&nbsp;References</h3> 
    16901699<table width="99%" border="0"> 
    1691 <tr><td class="author-text" valign="top"><a name="KEYWORDS">[1]</a></td> 
    1692 <td class="author-text"><a href="mailto:sob@harvard.edu">Bradner, S.</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirements Levels</a>", RFC 2119, BCP 14, March 1997.</td></tr> 
    1693 <tr><td class="author-text" valign="top"><a name="XML">[2]</a></td> 
    1694 <td class="author-text"><a href="http://www.w3c.org">World Wide Web Consortium</a>, "<a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0</a>", W3C XML, October 2000.</td></tr> 
    1695 <tr><td class="author-text" valign="top"><a name="HTML">[3]</a></td> 
    1696 <td class="author-text"><a href="http://www.w3c.org">World Wide Web Consortium</a>, "<a href="http://www.w3.org/TR/html4/">HTML 4.01 Specification</a>", W3C HTML, December 1999.</td></tr> 
    1697 <tr><td class="author-text" valign="top"><a name="XHTML">[4]</a></td> 
    1698 <td class="author-text"><a href="http://www.w3c.org">World Wide Web Consortium</a>, "<a href="http://www.w3.org/TR/xhtml1/">XHTML(TM) 1.0 The Extensible Hyper Text Markup Language</a>", W3C XHTML, January 2000.</td></tr> 
    1699 <tr><td class="author-text" valign="top"><a name="URI">[5]</a></td> 
     1700<tr><td class="author-text" valign="top"><a name="HTML">[1]</a></td> 
     1701<td class="author-text"><a href="http://www.w3c.org">World Wide Web Consortium</a>, "<a href="http://www.w3.org/TR/html4/">HTML 4.01 Specification</a>", W3C&nbsp;HTML, December 1999.</td></tr> 
     1702<tr><td class="author-text" valign="top"><a name="CMML">[2]</a></td> 
     1703<td class="author-text"><a href="mailto:Silvia.Pfeiffer@csiro.au">Pfeiffer, S.</a>, <a href="mailto:Conrad.Parker@csiro.au">Parker, C.</a> and <a href="mailto:Andre.Pang@csiro.au">A. Pang</a>, "<a href="http://www.annodex.net/TR/cmml.txt">The Continuous Media Markup Language (CMML), Version 2.0 (work in progress)</a>", I-D&nbsp;draft-pfeiffer-cmml-02.txt, March 2005.</td></tr> 
     1704<tr><td class="author-text" valign="top"><a name="Ogg">[3]</a></td> 
     1705<td class="author-text"><a href="mailto:Silvia.Pfeiffer@csiro.au">Pfeiffer, S.</a>, "<a href="http://www.ietf.org/rfc/rfc3533.txt">The Ogg encapsulation format version 0</a>", RFC&nbsp;3533, May 2003.</td></tr> 
     1706<tr><td class="author-text" valign="top"><a name="timedURI">[4]</a></td> 
     1707<td class="author-text"><a href="mailto:Silvia.Pfeiffer@csiro.au">Pfeiffer, S.</a>, <a href="mailto:Conrad.Parker@csiro.au">Parker, C.</a> and <a href="mailto:Andre.Pang@csiro.au">A. Pang</a>, "<a href="http://www.annodex.net/TR/URI_fragments.txt">Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress)</a>", I-D&nbsp;draft-pfeiffer-temporal-fragments-03.txt, March 2005.</td></tr> 
     1708<tr><td class="author-text" valign="top"><a name="HTTP">[5]</a></td> 
     1709<td class="author-text"><a href="mailto:fielding@ics.uci.edu">Fielding, R.</a>, <a href="mailto:jg@w3.org">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com">Mogul, J.</a>, <a href="mailto:frystyk@w3.org">Nielsen, H.</a>, <a href="mailto:masinter@parc.xerox.com">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com">Leach, P.</a> and <a href="mailto:timbl@w3.org">T. Berners-Lee</a>, "<a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext Transfer Protocol -- HTTP/1.1</a>", RFC&nbsp;2616, June 1999.</td></tr> 
     1710<tr><td class="author-text" valign="top"><a name="RTSP">[6]</a></td> 
     1711<td class="author-text"><a href="mailto:schulzrinne@cs.columbia.edu">Schulzrinne, H.</a>, <a href="mailto:anup@netscape.com">Rao, A.</a> and <a href="mailto:robla@real.com">R. Lanphier</a>, "<a href="http://www.ietf.org/rfc/rfc2326.txt">Real Time Streaming Protocol (RTSP)</a>", RFC&nbsp;2326, April 1998.</td></tr> 
     1712<tr><td class="author-text" valign="top"><a name="Headers">[7]</a></td> 
     1713<td class="author-text"><a href="mailto:presnick@qualcomm.com">Resnick, P.</a>, "<a href="http://www.ietf.org/rfc/rfc2822.txt">Internet Message Format</a>", RFC&nbsp;2822, April 2001.</td></tr> 
     1714<tr><td class="author-text" valign="top"><a name="I18N">[8]</a></td> 
     1715<td class="author-text"><a href="mailto:Harald.T.Alvestrand@uninett.no">Alvestrand, H.</a>, "<a href="http://www.ietf.org/rfc/rfc2277.txt">IETF Policy on Character Sets and Languages</a>", RFC&nbsp;2277, January 1998.</td></tr> 
     1716<tr><td class="author-text" valign="top"><a name="KEYWORDS">[9]</a></td> 
     1717<td class="author-text"><a href="mailto:sob@harvard.edu">Bradner, S.</a>, "Key words for use in RFCs to Indicate Requirements Levels", RFC&nbsp;2119, BCP&nbsp;14, March 1997.</td></tr> 
     1718<tr><td class="author-text" valign="top"><a name="XML">[10]</a></td> 
     1719<td class="author-text"><a href="http://www.w3c.org">World Wide Web Consortium</a>, "<a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0</a>", W3C&nbsp;XML, October 2000.</td></tr> 
     1720<tr><td class="author-text" valign="top"><a name="XHTML">[11]</a></td> 
     1721<td class="author-text"><a href="http://www.w3c.org">World Wide Web Consortium</a>, "<a href="http://www.w3.org/TR/xhtml1/">XHTML(TM) 1.0 The Extensible Hyper Text Markup Language</a>", W3C&nbsp;XHTML, January 2000.</td></tr> 
     1722<tr><td class="author-text" valign="top"><a name="URI">[12]</a></td> 
    17001723<td class="author-text"><a href="mailto:timbl@w3.org">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com">Fielding, R.</a> and <a href="mailto:LMM@acm.org">L. Masinter</a>, "<a href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifiers (URI): Generic 
    1701           Syntax</a>", RFC 3986, January 2005.</td></tr> 
    1702 <tr><td class="author-text" valign="top"><a name="HTTP">[6]</a></td> 
    1703 <td class="author-text"><a href="mailto:fielding@ics.uci.edu">Fielding, R.</a>, <a href="mailto:jg@w3.org">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com">Mogul, J.</a>, <a href="mailto:frystyk@w3.org">Nielsen, H.</a>, <a href="mailto:masinter@parc.xerox.com">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com">Leach, P.</a> and <a href="mailto:timbl@w3.org">T. Berners-Lee</a>, "<a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext Transfer Protocol -- HTTP/1.1</a>", RFC 2616, June 1999.</td></tr> 
    1704 <tr><td class="author-text" valign="top"><a name="Headers">[7]</a></td> 
    1705 <td class="author-text"><a href="mailto:presnick@qualcomm.com">Resnick, P.</a>, "<a href="http://www.ietf.org/rfc/rfc2822.txt">Internet Message Format</a>", RFC 2822, April 2001.</td></tr> 
    1706 <tr><td class="author-text" valign="top"><a name="I18N">[8]</a></td> 
    1707 <td class="author-text"><a href="mailto:Harald.T.Alvestrand@uninett.no">Alvestrand, H.</a>, "<a href="http://www.ietf.org/rfc/rfc2277.txt">IETF Policy on Character Sets and Languages</a>", RFC 2277, January 1998.</td></tr> 
    1708 <tr><td class="author-text" valign="top"><a name="RTSP">[9]</a></td> 
    1709 <td class="author-text"><a href="mailto:schulzrinne@cs.columbia.edu">Schulzrinne, H.</a>, <a href="mailto:anup@netscape.com">Rao, A.</a> and <a href="mailto:robla@real.com">R. Lanphier</a>, "<a href="http://www.ietf.org/rfc/rfc2326.txt">Real Time Streaming Protocol (RTSP)</a>", RFC 2326, April 1998.</td></tr> 
    1710 <tr><td class="author-text" valign="top"><a name="LANG">[10]</a></td> 
    1711 <td class="author-text"><a href="mailto:Harald.T.Alvestrand@uninett.no">Alvestrand, H.</a>, "<a href="http://www.ietf.org/rfc/rfc1766.txt">Tags for the Identification of Languages</a>", RFC 1766, March 1995.</td></tr> 
    1712 <tr><td class="author-text" valign="top"><a name="MIME">[11]</a></td> 
    1713 <td class="author-text"><a href="mailto:ned@innosoft.com">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com">N. Borenstein</a>, "<a href="http://www.ietf.org/rfc/rfc2046.txt">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>", RFC 2046, November 1996.</td></tr> 
    1714 <tr><td class="author-text" valign="top"><a name="text/xml">[12]</a></td> 
    1715 <td class="author-text"><a href="mailto:ejw@ics.uci.edu">Whitehead, E.</a> and <a href="mailto:murata@fxis.fujixerox.co.jp">M. Murata</a>, "<a href="http://www.ietf.org/rfc/rfc2376.txt">XML Media Types</a>", RFC 2376, July 1998.</td></tr> 
    1716 <tr><td class="author-text" valign="top"><a name="Ogg">[13]</a></td> 
    1717 <td class="author-text"><a href="mailto:Silvia.Pfeiffer@csiro.au">Pfeiffer, S.</a>, "<a href="http://www.ietf.org/rfc/rfc3533.txt">The Ogg encapsulation format version 0</a>", RFC 3533, May 2003.</td></tr> 
    1718 <tr><td class="author-text" valign="top"><a name="SMPTE">[14]</a></td> 
    1719 <td class="author-text"><a href="mailto:smpte@smpte.org">The Society of Motion Picture and Television Engineers</a>, "SMPTE STANDARD for Television, Audio and Film - Time and Control Code", ANSI 12M-1999, September 1999.</td></tr> 
    1720 <tr><td class="author-text" valign="top"><a name="ISO8601">[15]</a></td> 
    1721 <td class="author-text"><a href="mailto:central@iso.org">ISO, TC154.</a>, "Data elements and interchange formats -- Information interchange -- Representation of dates and times", ISO 8601, 2000.</td></tr> 
    1722 <tr><td class="author-text" valign="top"><a name="timedURI">[16]</a></td> 
    1723 <td class="author-text"><a href="mailto:Silvia.Pfeiffer@csiro.au">Pfeiffer, S.</a>, <a href="mailto:Conrad.Parker@csiro.au">Parker, C.</a> and <a href="mailto:Andre.Pang@csiro.au">A. Pang</a>, "<a href="http://www.annodex.net/TR/URI_fragments.txt">Specifying time intervals in URI queries and fragments of time-based Web resources (work in progress)</a>", I-D draft-pfeiffer-temporal-fragments-03.txt, March 2005.</td></tr> 
    1724 <tr><td class="author-text" valign="top"><a name="CMML">[17]</a></td> 
    1725 <td class="author-text"><a href="mailto:Silvia.Pfeiffer@csiro.au">Pfeiffer, S.</a>, <a href="mailto:Conrad.Parker@csiro.au">Parker, C.</a> and <a href="mailto:Andre.Pang@csiro.au">A. Pang</a>, "<a href="http://www.annodex.net/TR/cmml.txt">The Continuous Media Markup Language (CMML), Version 2.0 (work in progress)</a>", I-D draft-pfeiffer-cmml-02.txt, March 2005.</td></tr> 
     1724          Syntax</a>", RFC&nbsp;3986, January 2005.</td></tr> 
     1725<tr><td class="author-text" valign="top"><a name="LANG">[13]</a></td> 
     1726<td class="author-text"><a href="mailto:Harald.T.Alvestrand@uninett.no">Alvestrand, H.</a>, "<a href="http://www.ietf.org/rfc/rfc1766.txt">Tags for the Identification of Languages</a>", RFC&nbsp;1766, March 1995.</td></tr> 
     1727<tr><td class="author-text" valign="top"><a name="MIME">[14]</a></td> 
     1728<td class="author-text"><a href="mailto:ned@innosoft.com">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com">N. Borenstein</a>, "<a href="http://www.ietf.org/rfc/rfc2046.txt">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>", RFC&nbsp;2046, November 1996.</td></tr> 
     1729<tr><td class="author-text" valign="top"><a name="text/xml">[15]</a></td> 
     1730<td class="author-text"><a href="mailto:ejw@ics.uci.edu">Whitehead, E.</a> and <a href="mailto:murata@fxis.fujixerox.co.jp">M. Murata</a>, "<a href="http://www.ietf.org/rfc/rfc2376.txt">XML Media Types</a>", RFC&nbsp;2376, July 1998.</td></tr> 
     1731<tr><td class="author-text" valign="top"><a name="SMPTE">[16]</a></td> 
     1732<td class="author-text"><a href="mailto:smpte@smpte.org">The Society of Motion Picture and Television Engineers</a>, "SMPTE STANDARD for Television, Audio and Film - Time and Control Code", ANSI&nbsp;12M-1999, September 1999.</td></tr> 
     1733<tr><td class="author-text" valign="top"><a name="ISO8601">[17]</a></td> 
     1734<td class="author-text"><a href="mailto:central@iso.org">ISO, TC154.</a>, "Data elements and interchange formats -- Information interchange -- Representation of dates and times", ISO&nbsp;8601, 2000.</td></tr> 
    17261735</table> 
    17271736 
    …… 
    17441753<tr><td class="author" align="right">Phone:&nbsp;</td> 
    17451754<td class="author-text">+61 2 9372 4180</td></tr> 
    1746 <tr><td class="author" align="right">EMail:&nbsp;</td> 
     1755<tr><td class="author" align="right">Email:&nbsp;</td> 
    17471756<td class="author-text"><a href="mailto:Silvia.Pfeiffer@csiro.au">Silvia.Pfeiffer@csiro.au</a></td></tr> 
    17481757<tr><td class="author" align="right">URI:&nbsp;</td> 
    …… 
    17631772<tr><td class="author" align="right">Phone:&nbsp;</td> 
    17641773<td class="author-text">+61 2 9372 4222</td></tr> 
    1765 <tr><td class="author" align="right">EMail:&nbsp;</td> 
     1774<tr><td class="author" align="right">Email:&nbsp;</td> 
    17661775<td class="author-text"><a href="mailto:Conrad.Parker@csiro.au">Conrad.Parker@csiro.au</a></td></tr> 
    17671776<tr><td class="author" align="right">URI:&nbsp;</td> 
    …… 
    17821791<tr><td class="author" align="right">Phone:&nbsp;</td> 
    17831792<td class="author-text">+61 2 9372 4222</td></tr> 
    1784 <tr><td class="author" align="right">EMail:&nbsp;</td> 
     1793<tr><td class="author" align="right">Email:&nbsp;</td> 
    17851794<td class="author-text"><a href="mailto:Andre.Pang@csiro.au">Andre.Pang@csiro.au</a></td></tr> 
    17861795<tr><td class="author" align="right">URI:&nbsp;</td> 
    …… 
    19101919<h3>Intellectual Property Statement</h3> 
    19111920<p class='copyright'> 
    1912 The IETF takes no position regarding the validity or scope of 
    1913 any intellectual property or other rights that might be claimed 
    1914 to  pertain to the implementation or use of the technology 
    1915 described in this document or the extent to which any license 
    1916 under such rights might or might not be available; neither does 
    1917 it represent that it has made any effort to identify any such 
    1918 rights. Information on the IETF's procedures with respect to 
    1919 rights in standards-track and standards-related documentation 
    1920 can be found in BCP-11. Copies of claims of rights made 
    1921 available for publication and any assurances of licenses to 
    1922 be made available, or the result of an attempt made 
    1923 to obtain a general license or permission for the use of such 
    1924 proprietary rights by implementors or users of this 
    1925 specification can be obtained from the IETF Secretariat.</p> 
     1921The IETF takes no position regarding the validity or scope of any 
     1922Intellectual Property Rights or other rights that might be claimed 
     1923to pertain to the implementation or use of the technology  
     1924described in this document or the extent to which any license  
     1925under such rights might or might not be available; nor does it 
     1926represent that it has made any independent effort to identify any 
     1927such rights. 
     1928Information on the procedures with respect to 
     1929rights in RFC documents can be found in BCP&nbsp;78 and BCP&nbsp;79.</p> 
    19261930<p class='copyright'> 
    1927 The IETF invites any interested party to bring to its 
    1928 attention any copyrights, patents or patent applications, or 
    1929 other proprietary rights which may cover technology that may be 
    1930 required to practice this standard. Please address the 
    1931 information to the IETF Executive Director.</p> 
    1932 <h3>Full Copyright Statement</h3> 
     1931Copies of IPR disclosures made to the IETF Secretariat and any 
     1932assurances of licenses to be made available, 
     1933or the result of an attempt made to obtain a general license or 
     1934permission for the use of such proprietary rights by implementers or 
     1935users of this specification can be obtained from the IETF on-line IPR 
     1936repository at http://www.ietf.org/ipr.</p> 
    19331937<p class='copyright'> 
    1934 Copyright (C) The Internet Society (2005). All Rights Reserved.</p> 
     1938The IETF invites any interested party to bring to its attention 
     1939any copyrights, 
     1940patents or patent applications, 
     1941or other 
     1942proprietary rights that may cover technology that may be required 
     1943to implement this standard. 
     1944Please address the information to the IETF at ietf-ipr@ietf.org.</p> 
     1945<h3>Disclaimer of Validity</h3> 
    19351946<p class='copyright'> 
    1936 This document and translations of it may be copied and furnished to 
    1937 others, and derivative works that comment on or otherwise explain it 
    1938 or assist in its implementation may be prepared, copied, published and 
    1939 distributed, in whole or in part, without restriction of any kind, 
    1940 provided that the above copyright notice and this paragraph are 
    1941 included on all such copies and derivative works. However, this 
    1942 document itself may not be modified in any way, such as by removing 
    1943 the copyright notice or references to the Internet Society or other 
    1944 Internet organizations, except as needed for the purpose of 
    1945 developing Internet standards in which case the procedures for 
    1946 copyrights defined in the Internet Standards process must be 
    1947 followed, or as required to translate it into languages other than 
    1948 English.</p> 
     1947This document and the information contained herein are provided 
     1948on an &quot;AS IS&quot; basis and THE CONTRIBUTOR, 
     1949THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), 
     1950THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 
     1951ALL WARRANTIES,  
     1952EXPRESS OR IMPLIED, 
     1953INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 
     1954INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 
     1955WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</p> 
     1956<h3>Copyright Statement</h3> 
    19491957<p class='copyright'> 
    1950 The limited permissions granted above are perpetual and will not be 
    1951 revoked by the Internet Society or its successors or assignees.</p> 
    1952 <p class='copyright'> 
    1953 This document and the information contained herein is provided on an 
    1954 &quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 
    1955 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 
    1956 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 
    1957 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 
    1958 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</p> 
     1958Copyright (C) The Internet Society (2005). 
     1959This document is subject to the rights, 
     1960licenses and restrictions contained in BCP&nbsp;78, 
     1961and except as set forth therein, 
     1962the authors retain all their rights.</p> 
    19591963<h3>Acknowledgment</h3> 
    19601964<p class='copyright'> 

  • standards/anx-ids/draft-pfeiffer-annodex-02.txt

    r1130 r1152  
     1 
    12 
    23 
    34Network Working Group                                        S. Pfeiffer 
    45Internet-Draft                                                 C. Parker 
    5 Expires: September 13, 2005                                      A. Pang 
     6Expires: September 20, 2005                                      A. Pang 
    67                                                                   CSIRO 
    7                                                           March 15, 2005 
     8                                                          March 19, 2005 
    89 
    910 
    …… 
    1415Status of this Memo 
    1516 
    16    This document is an Internet-Draft and is in full conformance with 
    17    all provisions of Section 10 of RFC2026. 
     17   This document is an Internet-Draft and is subject to all provisions 
     18   of Section 3 of RFC 3667.  By submitting this Internet-Draft, each 
     19   author represents that any applicable patent or other IPR claims of 
     20   which he or she is aware have been or will be disclosed, and any of 
     21   which he or she become aware will be disclosed, in accordance with 
     22   RFC 3668. 
    1823 
    1924   Internet-Drafts are working documents of the Internet Engineering 
    …… 
    3338   http://www.ietf.org/shadow.html. 
    3439 
    35    This Internet-Draft will expire on September 13, 2005. 
     40   This Internet-Draft will expire on September 20, 2005. 
    3641 
    3742Copyright Notice 
    3843 
    39    Copyright (C) The Internet Society (2005).  All Rights Reserved. 
     44   Copyright (C) The Internet Society (2005). 
    4045 
    4146Abstract 
    …… 
    4550   bitstream format for exchanging multitrack interleaved 
    4651   time-continuous bitstreams and textual meta information attached to 
     52 
     53 
     54 
     55Pfeiffer, et al.       Expires September 20, 2005               [Page 1] 
     56  
     57Internet-Draft                   ANNODEX                      March 2005 
     58 
     59 
    4760   temporal fragments of the binary bitstreams.  The meta information is 
    48    described in the Continuous Media Markup Language (CMML) [17]. 
    49    Annodex enables integration of time-continuous bitstreams into the 
    50    browsing and searching functionality of the World Wide Web. 
    51  
    52  
    53  
    54  
    55 Pfeiffer, et al.       Expires September 13, 2005               [Page 1] 
    56   
    57 Internet-Draft                  ANNODEX                       March 2005 
    58  
     61   given in the Continuous Media Markup Language (CMML).  Annodex 
     62   enables integration of time-continuous bitstreams into the browsing 
     63   and searching functionality of the World Wide Web. 
    5964 
    6065   The specification is not encumbered by patents.  The Annodex format 
    …… 
    6671   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
    6772   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
    68    document are to be interpreted as described in RFC 2119 [1]. 
     73   document are to be interpreted as described in RFC 2119. 
    6974 
    7075Table of Contents 
    …… 
    7479     1.2   Overview . . . . . . . . . . . . . . . . . . . . . . . . .  3 
    7580   2.  Features of Annodex  . . . . . . . . . . . . . . . . . . . . .  5 
    76    3.  Authoring the Annodex exchange format . . . . . . . . . . . .  8 
     81   3.  Authoring exchange format  . . . . . . . . . . . . . . . . . .  8 
    7782   4.  The Ogg skeleton logical bitstream . . . . . . . . . . . . . . 10 
    7883     4.1   The format of the skeleton ident header  . . . . . . . . . 11 
    …… 
    104109 
    105110 
    106  
    107  
    108  
    109  
    110  
    111 Pfeiffer, et al.       Expires September 13, 2005               [Page 2] 
    112   
    113 Internet-Draft                  ANNODEX                       March 2005 
     111Pfeiffer, et al.       Expires September 20, 2005               [Page 2] 
     112  
     113Internet-Draft                   ANNODEX                      March 2005 
    114114 
    115115 
    …… 
    129129 
    130130   Text documents were enabled for the Web through definition of a 
    131    markup language (HTML [3]) for text documents to enable description 
     131   markup language (HTML [1]) for text documents to enable description 
    132132   of the structure of a document, and thus allow for the separation of 
    133133   content from presentation.  This specification takes the same 
    134134   approach for time-continuous documents.  The markup language for 
    135135   time-continuous documents is called CMML, short for Continuous Media 
    136    Markup Language [17].  It describes the structure of time-continuous 
     136   Markup Language [2].  It describes the structure of time-continuous 
    137137   documents and allows for a clean separation of content from 
    138138   presentation. 
    …… 
    154154   solves a specific problem without being dependent on layers that are 
    155155   further up in functionality.  The container format of Annodex is the 
    156    Ogg encapsulation format version 0 [13].  Annodex is an Ogg bitstream 
     156   Ogg encapsulation format version 0 [3].  Annodex is an Ogg bitstream 
    157157   containing a "skeleton" and a CMML logical bitstream, in addition to 
    158158   other temporally interleaved data bitstreams.  Ogg skeleton is a 
    …… 
    165165 
    166166 
    167 Pfeiffer, et al.       Expires September 13, 2005               [Page 3] 
    168   
    169 Internet-Draft                  ANNODEX                       March 2005 
     167Pfeiffer, et al.       Expires September 20, 2005               [Page 3] 
     168  
     169Internet-Draft                  ANNODEX                      March 2005 
    170170 
    171171 
    …… 
    175175   not an Annodex bitstream, but only an Ogg bitstream with a "skeleton" 
    176176   logical bitstream, which is still valuable as a multitrack media 
    177    format that can be addressed through temporal hyperlinks [16], 
    178    however it is not a first class citizen on the Web because Web search 
    179    engines cannot index and crawl it. 
     177   format that can be addressed through temporal hyperlinks [4], however 
     178   it is not a first class citizen on the Web because Web search engines 
     179   cannot index and crawl it. 
    180180 
    181181   The file extension of Annodex files is ".anx".  This document also 
    182182   applies for registration of the MIME type "application/annodex" for 
    183183   Annodex format bitstreams.  In the meantime, "text/x-annodex" will be 
    184    used.  Further MIME types that this document applies for are "video/ 
    185    annodex" for Annodex format (possibly multitrack) video and "audio/ 
    186    annodex" for Annodex format (possibly multitrack) audio. 
     184   used.  Further MIME types that this document applies for are 
     185   "video/annodex" for Annodex format (possibly multitrack) video and 
     186   "audio/annodex" for Annodex format (possibly multitrack) audio. 
    187187 
    188188   Please note that this document assumes that the reader understands 
    189    the Ogg encapsulation format version 0 [13].  Also, knowledge of the 
    190    network protocols HTTP [6] and RTP/RTSP [9] as well as the extension 
    191    of URIs to address temporal offsets into Web resources [16] are a 
     189   the Ogg encapsulation format version 0 [3].  Also, knowledge of the 
     190   network protocols HTTP [5] and RTP/RTSP [6] as well as the extension 
     191   of URIs to address temporal offsets into Web resources [4] are a 
    192192   prerequisite to understanding this document.  To find out more about 
    193193   the use of Annodex for creating searchable and surfable Web 
    194194   resources, refer to the specification of the Continuous Media Markup 
    195    Language (CMML Version 2.0) [17]. 
    196  
    197  
    198  
    199  
    200  
    201  
    202  
    203  
    204  
    205  
    206  
    207  
    208  
    209  
    210  
    211  
    212  
    213  
    214  
    215  
    216  
    217  
    218  
    219  
    220  
    221  
    222  
    223 Pfeiffer, et al.       Expires September 13, 2005               [Page 4] 
    224   
    225 Internet-Draft                  ANNODEX                       March 2005 
     195   Language (CMML Version 2.0) [2]. 
     196 
     197 
     198 
     199 
     200 
     201 
     202 
     203 
     204 
     205 
     206 
     207 
     208 
     209 
     210 
     211 
     212 
     213 
     214 
     215 
     216 
     217 
     218 
     219 
     220 
     221 
     222 
     223Pfeiffer, et al.       Expires September 20, 2005               [Page 4] 
     224  
     225Internet-Draft                  ANNODEX                      March 2005 
    226226 
    227227 
    …… 
    277277 
    278278 
    279 Pfeiffer, et al.       Expires September 13, 2005               [Page 5] 
    280   
    281 Internet-Draft                  ANNODEX                       March 2005 
     279Pfeiffer, et al.       Expires September 20, 2005               [Page 5] 
     280  
     281Internet-Draft                  ANNODEX                      March 2005 
    282282 
    283283 
    …… 
    295295 
    296296   Distribution of Annodex format bitstreams is performed using a 
    297    network protocol such as HTTP [6] or RTP/RTSP [9].  The basic process 
     297   network protocol such as HTTP [5] or RTP/RTSP [6].  The basic process 
    298298   is the following: The client dispatches a download or streaming 
    299299   request to the server with a certain URI.  The server resolves the 
    …… 
    333333 
    334334 
    335 Pfeiffer, et al.       Expires September 13, 2005               [Page 6] 
    336   
    337 Internet-Draft                  ANNODEX                       March 2005 
     335Pfeiffer, et al.       Expires September 20, 2005               [Page 6] 
     336  
     337Internet-Draft                  ANNODEX                      March 2005 
    338338 
    339339 
    …… 
    389389 
    390390 
    391 Pfeiffer, et al.       Expires September 13, 2005               [Page 7] 
    392   
    393 Internet-Draft                  ANNODEX                       March 2005 
    394  
    395  
    396 3.  Authoring the Annodex exchange format 
    397  
    398    For authoring of Annodex bitstream information, the CMML [17] is 
     391Pfeiffer, et al.       Expires September 20, 2005               [Page 7] 
     392  
     393Internet-Draft                  ANNODEX                      March 2005 
     394 
     395 
     3963.  Authoring exchange format 
     397 
     398   For authoring of Annodex bitstream information, the CMML [2] is 
    399399   defined.  CMML's "stream" tag has been designed to author the 
    400400   skeleton bitstream and describe the data bitstreams to be interleaved 
    …… 
    426426   which is a sensible restriction. 
    427427 
    428    The CMML media mapping is defined in the CMML [17] specification. 
     428   The CMML media mapping is defined in the CMML [2] specification. 
    429429   However, for identification of an Annodex bitstream, the bos page of 
    430430   the CMML logical bitstream needs to be identifiable, which is 
    431431   provided through the first 12 Bytes of the CMML ident packet 
    432432   containing the magic numbers and the version information: Other 
    433    fields exists and are described in the CMML [17] specification. 
     433   fields exists and are described in the CMML [2] specification. 
    434434   1.  Identifier: a 8 Byte field that identifies this file to be of a 
    435435       CMML logical input bitstream.  It contains the magic numbers: 
    …… 
    445445 
    446446 
    447 Pfeiffer, et al.       Expires September 13, 2005               [Page 8] 
    448   
    449 Internet-Draft                  ANNODEX                       March 2005 
     447Pfeiffer, et al.       Expires September 20, 2005               [Page 8] 
     448  
     449Internet-Draft  &nb