Changeset 1041

Show
Ignore:
Timestamp:
2005-03-04 23:26:01 (4 years ago)
Author:
silvia
Message:

Fixed up temporal and named URI addressing.
Please note: named URI addressing has changed!
A name of a clip now essentially represents an alias for that clip's start and end time.
Examples:
http://example.com/video.anx?id="dolphin" (-> dolphin start to dolphin end)
http://example.com/video.anx?id="dolphin/" (-> dolphin start to file end)
http://example.com/video.anx?id="intor/dolphin" (-> intro start to dolphin end)

Also fixed the BNF specifications for timed URIs and named URIs according to the new URI RFC.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • standards/draft-pfeiffer-annodex-current.xml

    r1028 r1041  
    12401240      <section title="URI addressing into Annodex bitstreams"> 
    12411241 
    1242         <t>There are two ways of hyperlinking via URIs into Annodex 
    1243         bitstreams: via specification of a temporal interval or via 
    1244         specification of a clip. Both of these ways of addressing are 
    1245         supported for URI queries and URI fragments of Annodex bitstreams. 
     1242        <t>As Annodex bitstreams are time-continuous Web resources, 
     1243        hyperlinking into Annodex bitstreams via URIs is possible 
     1244        with the <xref target="timedURI">temporal URI query and 
     1245        fragment specification</xref>. For the query case, an Annodex 
     1246        server must supports the "X-Accept-TimeURI" http header field 
     1247        (see the <xref target="timedURI">temporal URI query 
     1248        specification</xref> for more details). 
     1249        </t> 
     1250 
     1251        <t>As Annodex bistreams contain CMML logical bitstreams, URI 
     1252        addressing of clips via their name given in the "id" tag is 
     1253        also supported. The same mechanisms as specified in the 
     1254        <xref target="CMML">CMML specification</xcef> apply to 
     1255        Annodex analogously. In particular, the id addressing is also 
     1256        regarded as an alias for a time offset and an Annodex conformant 
     1257        server that supports Annodex temporal URI addressing MUST also 
     1258        support named URI addressing (see the <xref target="CMML">CMML 
     1259        specification</xref> for more details). 
    12461260        </t> 
    12471261 
    1248         <section title="Query parameters for use with the HTTP protocol server-side"> 
    1249           <t>For the purposes of URI queries on Annodex bitstreams, it is 
    1250           assumed that the query string takes the format of a CGI 
    1251           query string. The Common Gateway Interface, or CGI, is a 
    1252           convention for external gateway programs to interface with 
    1253           information servers such as HTTP servers (see 
    1254           http://hoohoo.ncsa.uiuc.edu/cgi/). This query string is 
    1255           expected to be interpreted by the HTTP server to return a 
    1256           valid Annodex bitstream that differs from the original 
    1257           Annodex bitstream only by reducing it to the specified interval. 
    1258           </t> 
    1259  
    1260           <t>Temporal query parameter specification:</t> 
    1261  
    1262           <t>Addressing of temporal intervals of Annodex bitstreams is 
    1263           possible through specification of <xref 
    1264           target="timedURI">temporal query intervals in 
    1265           URIs</xref>. An example is the following URI: 
    1266           http://example.com/sample.anx?t=npt:4 , which relates to 
    1267           a complete Annodex bitstream composed from sample.anx by 
     1262        <t>Examples for valid URI addresses:</t> 
     1263        <list style="symbols"> 
     1264          <t>http://example.com/sample.anx?t=npt:4 , which relates to 
     1265          an Annodex bitstream composed by the server from sample.anx by 
    12681266          starting it at an offset of 4 seconds. 
    12691267          </t> 
    1270  
    1271           <t>Clip specification:</t> 
    1272  
    1273           <t>Addressing of a clip is possible through specification of 
    1274           the clip's id attribute value. An example is the following 
    1275           URI: http://example.com/sample.anx?id=dolphin , which 
     1268          <t>http://example.com/sample.anx?id=dolphin --- 
    12761269          relates to the clip whose id attribute value is 
    1277           "dolphin". Note that id attribute values of all elements 
    1278           MUST be unique throughout an XML file (and thus also 
    1279           throughout an Annodex file which represents a CMML file).</t> 
    1280         </section> 
    1281          
    1282         <section title="Fragment identifiers for use with the HTTP protocol client-side"> 
    1283           <t>For the purposes of URI fragment specifications on Annodex 
    1284           bitstreams, it is assumed that the fragment gets interpreted by 
    1285           the HTTP client after the retrieval action. The HTTP client 
    1286           is expected to restrict the usage of the resource to the 
    1287           specified interval. 
    1288           </t> 
    1289  
    1290           <t>Temporal fragment specification:</t> 
    1291  
    1292           <t>Addressing of temporal intervals of Annodex bitstreams is 
    1293           possible through specification of <xref 
    1294           target="timedURI">temporal fragments in URIs</xref> An 
    1295           example is the following URI: 
    1296           http://example.com/sample.anx#npt:4 . This then relates to 
    1297           starting the Annodex bitstream at a 4 second offset. It may 
    1298           e.g. be useful to do a zoom into a retrieved Annodex resource. 
    1299           </t> 
    1300  
    1301           <t>Clip specification:</t> 
    1302  
    1303           <t>The values of the id attribute of the clip tags can be 
    1304           used for addressing media clips directly through fragment 
    1305           identifiers as in http://example.com/sample.anx#dolphin. 
    1306           </t> 
     1270          "dolphin" and all further clips after that. 
     1271          </t> 
     1272          <t>http://example.com/sample.anx?id="dolphin/" --- 
     1273          relates only to the clip whose id attribute value is "dolphin". 
     1274          </t> 
     1275          <t>http://example.com/sample.anx?id="intro/goldfish" --- 
     1276          realtes to all the clips from the "intro" clip to 
     1277          the "goldfish" clip. 
     1278          </t> 
     1279          <t>http://example.com/sample.anx#t=npt:4 --- start using the 
     1280          Annodex bitstream from a 4 second offset. 
     1281          </t> 
     1282          <t>http://example.com/sample.anx#dolphin -- use the clip with 
     1283          id="dolphin" only. 
     1284          </t> 
     1285        </list> 
    13071286        </section> 
    13081287 

  • standards/draft-pfeiffer-cmml-current.xml

    r1028 r1041  
    19641964        to its response header fields as defined in the <xref  
    19651965        target="timedURI">temporal URI query specification</xref>. 
     1966        Specifications of a clip in a URI query via the clip's name 
     1967        are regarded as an alias for a time offset. Therefore, a server 
     1968        that supports CMML temporal URI addressing MUST also support the 
     1969        named addressing. 
    19661970        </t> 
    19671971 
    …… 
    19701974          assumed that the query string takes the format of a CGI 
    19711975          query string. The Common Gateway Interface, or CGI, is a 
    1972           standard for external gateway programs to interface with 
     1976          convention for external gateway programs to interface with 
    19731977          information servers such as HTTP servers (see 
    19741978          http://hoohoo.ncsa.uiuc.edu/cgi/). This query string is 
    …… 
    19931997 
    19941998          <t>Addressing of a clip is possible through specification of 
    1995           the clip's id attribute value. An example is the following 
    1996           URI: http://example.com/sample.cmml?id="dolphin" , which 
    1997           relates to the clip whose id attribute value is 
    1998           "dolphin". Note that id attribute values of all elements 
     1999          the clip's id attribute value. The BNF for such an id URI query 
     2000          parameter is: 
     2001          </t> 
     2002 
     2003      <artwork><![CDATA[ 
     2004id-parameter = "id" "=" id-interval ["," id-interval] 
     2005 
     2006id-interval = id-name [ "/" [ id-name] ] 
     2007 
     2008id-name     = *( unreserved / pct-encoded / ":" / "?" / "#" / 
     2009              "[" / "]" / "@" / "!" / "$" / "&" / "'" / 
     2010              "(" / ")" / "*" / "+" / ";" / "=" ) 
     2011 
     2012      ]]></artwork> 
     2013 
     2014 
     2015          <t>All id-name specifications map onto a start and end time. 
     2016          Specifying just an id-name maps to just the start and end times 
     2017          of that clip. Specifying an id-name with a "/" maps to the 
     2018          document starting from the beginning of that clip until the end 
     2019          of the file or stream. Specifying an id range is inclusive and 
     2020          maps to the start time of the first clip and end time of the 
     2021          second clip. Overlapping time intervals MUST be interpreted by 
     2022          merging the intervals into one. 
     2023          </t> 
     2024 
     2025          <t>It is not valid to give several temporal URI query 
     2026          parameters in one URI query. They all need to be wrapped into a 
     2027          single specification. 
     2028          </t> 
     2029 
     2030          <t>Examples for URIs containing id queries are: 
     2031          </t> 
     2032 
     2033          <list style="symbols"> 
     2034            <t>http://example.com/sample.cmml?id="dolphin" --- sample.cmml 
     2035            is transferred from the start time of the "dolphin" clip to 
     2036            the end of the file/stream. 
     2037            </t> 
     2038            <t>http://example.com/sample.cmml?id="dolphin/" --- sample.cmml 
     2039            is transferred from the start time of the "dolphin" clip to 
     2040            the end of the file or stream. 
     2041            </t> 
     2042            <t>http://example.com/sample.cmml?id="dolphin/goldfish" --- 
     2043            sample.cmml is transferred from the start time of the 
     2044            "dolphin" clip to the end of the "goldfish" clip. 
     2045            </t> 
     2046          </list> 
     2047 
     2048          <t>Note that id attribute values of all elements 
    19992049          have to be unique throughout a XML file (and thus also 
    2000           throughout a CMML file).</t> 
     2050          throughout a CMML file). 
     2051          </t> 
    20012052        </section> 
    20022053         

  • standards/draft-pfeiffer-temporal-fragments-current.xml

    r1006 r1041  
    223223time-interval = timespec ["/" timespec] 
    224224 
    225 timescheme     = *unreserved 
    226  
    227 timespec       = *uric 
     225timescheme     = *( unreserved / pct-encoded / sub-delims / 
     226                 "/" / "?" / "#" / "[" / "]" / "@" ) 
     227 
     228timespec       = *( unreserved / pct-encoded / "?" / "#" / 
     229                 "[" / "]" / "@" / "!" / "$" / "&" / "'" / 
     230                 "(" / ")" / "*" / "+" / ";" / "=" ) 
    228231      ]]></artwork> 
    229232