[cvs-annodex] commit (/annodex):
standards/draft-pfeiffer-temporal-fragments-current.xml
silvia
nobody at lists.annodex.net
Sat Feb 26 15:34:07 EST 2005
Update of /annodex (new revision 960)
Modified files:
standards/draft-pfeiffer-temporal-fragments-current.xml
Log Message:
Changes:
- changed date of I-D
- fixed the X-Accept-TimeURI message header field
- fixed some typos
Modified: standards/draft-pfeiffer-temporal-fragments-current.xml
===================================================================
--- standards/draft-pfeiffer-temporal-fragments-current.xml 2005-02-26 03:47:10 UTC (rev 959)
+++ standards/draft-pfeiffer-temporal-fragments-current.xml 2005-02-26 04:34:06 UTC (rev 960)
@@ -59,7 +59,7 @@
</address>
</author>
- <date month="December" year="2004"/>
+ <date month="February" year="2005"/>
<abstract>
<t>This document specifies a syntax for addressing time
@@ -68,17 +68,17 @@
<xref target="ANX">Annodex</xref> and <xref target="CMML">CMML</xref>
Web resources, though it could be picked up
by any other time-based Web resource format.
- Temporal addressing enables, e.g., direct access
- to a clip of a video stored on a Web Server, or direct jumps to a
+ Temporal addressing enables, e.g., direct access to a clip inside
+ a video stored on a Web Server, or direct jumps to a
specific event within a piece of music. The syntax is not
restricted to audio or video Web resources though, but covers all
kinds of Web resources that contain time-continuous
information.
</t>
- <t>When a server (e.g. a Web Server) supports the URI query syntax
+ <t>When a server (e.g. a Web Server) supports the URI query syntax,
it is able to extract the given time
- subsections from the base resource and serve that as another
+ subsections from the base resource and serve them as another
resource of the same type. Specifying a time point
or interval through a URI fragment in contrast does not deliver
a subpart of the resource - instead it is up to the
@@ -138,15 +138,6 @@
is possible, but has not been explored yet.
</t>
- <t>This specification starts with a general recapture about
- possibilites for incorporating temporal addressing means into
- the generic URI addressing scheme. It then specifies the syntax
- of temporal URI queries and fragments, and provides some
- time schemes. Implementation over HTTP and RTP/RTSP is
- specified subsequently and finally security considerations are
- discussed.
- </t>
-
</section>
@@ -199,9 +190,9 @@
that interpretes the query parameter reacts uniformly to it. The
particular resources which are covered in this manner
are the <xref target="ANX">Annodex</xref> and <xref
- target="CMML">CMML</xref> media types. To use this scheme for
- other media types, all that is required is to reference it in
- the media type registration for that format.
+ target="CMML">CMML</xref> media types. This scheme can be adopted
+ for other media types, by including it in the media type
+ registration for that format.
</t>
</section>
@@ -550,11 +541,12 @@
</t>
<t>To address this issue, a HTTP server that is capable of resolving
- temporal URI requests on a base resource MUST return an additional
+ temporal URI requests on a specified resource MUST return an additional
accept header field that indicates that it can handle the temporal
- URI addressing and for which resources it can handle it. The header
- field is called "X-Accept-TimeURI" and the value is a list of MIME
- types, e.g. "X-Accept-TimeURI: application/x-annodex,text/x-cmml".
+ URI addressing and for which time schemes it can handle it. The
+ header field is called "X-Accept-TimeURI" and the value is a list
+ of time schemes, e.g. "X-Accept-TimeURI: npt, smpte-24, smpte-25,
+ smpte-30, smpte-50, smpte-60".
This request header is included for all URI requests to resources
on which the HTTP server can resolve a temporal URI request. A user
agent SHOULD check the X-Accept-TimeURI field to decide whether his
@@ -602,7 +594,7 @@
<t>A request header of "X-Accept-Range-Redirect" is required to
indicate to the server that a mapping of the temporal URI query
- parameters to a byte range is requested rather than deliver of
+ parameters to a byte range is requested rather than delivery of
the complete resource. As this field initiates the server to
provide a different response than if this field was not available,
the server has to include into its response a message header of
@@ -632,9 +624,8 @@
byte ranges. If several byte ranges are required, the response will
be a multipart message as defined in <xref target="HTTP">the HTTP/1.1
specification</xref>. The response message headers include the
- "X-Accept-TimeURI" header, the "Accept-Ranges: bytes" header, and
- the "Vary: Range" header, and provides the byte range(s) in the
- "Content-Range" header.
+ "Accept-Ranges: bytes" header, and the "Vary: Range" header, and
+ provides the byte range(s) in the "Content-Range" header.
</t>
<t>This is an example HTTP message exchange:
@@ -652,11 +643,11 @@
Date: Fri Feb 11 14:47:12 EST 2005
Server: Apache/2.0(Unix)
Content-Type: application/x-annodex
-X-Range-Redirect: 777-
+X-Range-Redirect: bytes=777-
Vary: X-Accept-Range-Redirect
Accept-Ranges: bytes
Location: http://example.com/video.anx
-X-Accept-TimeURI: application/x-annodex, text/x-cmml
+X-Accept-TimeURI: npt, smpte-25
Message body: control section of video.anx?t=npt:15.2
]]></artwork>
@@ -668,7 +659,7 @@
Range: bytes=777-
]]></artwork>
</t>
- <t>User Agent HTTP request:
+ <t>Server HTTP response:
<artwork><![CDATA[
HTTP/1.1 200 OK
Date: Fri Feb 11 14:49:08 EST 2005
@@ -677,7 +668,7 @@
Content-Range: bytes 777-
Vary: Range
Accept-Ranges: bytes
-X-Accept-TimeURI: application/x-annodex, text/x-cmml
+X-Accept-TimeURI: npt, smpte-25
Message body: video.anx from byte position 777 onwards
]]></artwork>
@@ -724,22 +715,19 @@
<section title="X-Accept-TimeURI">
- <t>The X-Accept-TimeURI response header field provides
- a list of media types for which the server is capable
- of satisfying temporal URI query parameters.
+ <t>The X-Accept-TimeURI response header field returns for
+ a timed URI query what time schemes it can resolve and
+ thus implicitly also whether it has resolved it.
</t>
<artwork><![CDATA[
-X-Accept-TimeURI = "X-Accept-TimeURI" ":" #( media-range )
-media-range = ( "*/*"
- | ( type "/" "*" )
- | ( type "/" subtype )
+X-Accept-TimeURI = "X-Accept-TimeURI" ":" 1#timescheme
)
]]></artwork>
<t>An example of this field is:
<artwork><![CDATA[
-X-Accept-TimeURI: application/x-annodex, text/x-cmml
+X-Accept-TimeURI: npt, smpte-24, smpte-25, smpte-30-drop, smpte-30
]]></artwork>
</t>
--
silvia
More information about the cvs-annodex
mailing list