[cvs-annodex] commit (/annodex): standards/draft-pfeiffer-temporal-fragments-current.xml

[silvia]

Update of /annodex (new revision 884)

Modified files:
   standards/draft-pfeiffer-temporal-fragments-current.xml

Log Message:
Improved some introductory sentences.



Modified: standards/draft-pfeiffer-temporal-fragments-current.xml
===================================================================
--- standards/draft-pfeiffer-temporal-fragments-current.xml	2005-02-13 01:22:31 UTC (rev 883)
+++ standards/draft-pfeiffer-temporal-fragments-current.xml	2005-02-13 04:20:06 UTC (rev 884)
@@ -76,29 +76,17 @@
       information.
       </t>
 
-      <t>The URI query specification of this syntax implies
-      that a Web server is capable to extract the given time
-      subsections from the Web resource and serve that as another
-      Web resource of the same type. Specifying a time point
+      <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 resource and serve that 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 Web resource - instead it is up to the
-      application and the resource type as to what action is
+      a subpart of the resource - instead it is up to the
+      user agent and the resource type as to what action is
       invoked. Examples are a fast forward to a time point, or a zoom
       into a time interval.
       </t>
 
-      <t>The temporal URI queries and fragments specified in this
-      document have been implemented and proven to work with 
-      <xref target="ANX">Annodex</xref> and <xref
-      target="CMML">CMML</xref> format Web resources over
-      <xref target="HTTP">HTTP</xref>. A possible implementation
-      over <xref target="RTSP">RTP/RTSP</xref> for Internet
-      streaming is being specified. Usage with other protocols
-      is possible, but has not been explored yet.
-      Also note that RealNetworks is using an different syntax
-      for the query case for RealMedia over RTP/RTSP.
-      </t>
-      
       <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
       NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
       "OPTIONAL" in this document are to be interpreted as described
@@ -128,21 +116,41 @@
       subparts e.g. for reusing them.
       </t>
       
-      <t>Files containing commands for creating time-continuous
+      <t>The temporal URI interval specifications are to be
+      used on resources that represent a specific timeline. An example
+      of such resources are most resources of MIME types "audio/*" and
+      "video/*". Files containing commands for creating time-continuous
       experiences (such as SMIL files for authoring interactive
       multimedia, or VRML files for authoring 3D worlds) cannot be
-      addressed in this manner - however, if one particular user
+      addressed in this manner. However, if one particular user
       interaction (i.e. one experience) is recorded, the recording
-      contains information that relates to a single timeline and can
+      contains data that relates to a single timeline and can
       be addressed with the manner described in this specification.
       </t>
       
-      <t>The temporal URI interval specifications are to be
-      used on resources that represent a specific timeline. An example
-      of such resources are most resources of MIME types "audio/*" and
-      "video/*".
+      <t>The temporal URI queries and fragments specified in this
+      document have been implemented and proven to work with 
+      <xref target="ANX">Annodex</xref> and <xref
+      target="CMML">CMML</xref> format Web resources over
+      <xref target="HTTP">HTTP</xref>. A possible implementation
+      over <xref target="RTSP">RTP/RTSP</xref> for Internet
+      streaming is being specified. Usage with other protocols
+      is possible, but has not been explored yet.
       </t>
 
+      <t>Also note that RealNetworks is using a different syntax
+      for querying temporal intervals of RealMedia over RTP/RTSP.
+      </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>
 
 


-- 
silvia