Changeset 391 for draft-ietf-httpbis/latest/p3-payload.xml

Timestamp:

15/11/08 00:44:55 (14 years ago)

Author:

julian.reschke@…

Message:

Merge in Roy's changes wrt Introduction and HTTP Architecture, replace Request-URI by request-target and relative-URI by partial-URI throughout.

File:

• draft-ietf-httpbis/latest/p3-payload.xml (modified) (6 diffs)

draft-ietf-httpbis/latest/p3-payload.xml

@@ -281 +281 @@
   <x:anchor-alias value="Last-Modified"/>
   <x:anchor-alias value="message-header"/>
-  <x:anchor-alias value="relativeURI"/>
+  <x:anchor-alias value="partial-URI"/>
   The ABNF rules below are defined in other parts: 
 </t>
@@ -287 +287 @@
   <x:ref>absolute-URI</x:ref>   = &lt;absolute-URI, defined in &uri;&gt;
   <x:ref>Content-Length</x:ref> = &lt;Content-Length, defined in &header-content-length;&gt;
-  <x:ref>relativeURI</x:ref>    = &lt;relativeURI, defined in &uri;&gt;
   <x:ref>message-header</x:ref> = &lt;message-header, defined in &message-headers;&gt;
+  <x:ref>partial-URI</x:ref>    = &lt;partial-URI, defined in &uri;&gt;
 </artwork></figure>
 <figure><!--Part4--><artwork type="abnf2616">
@@ -1284 +1284 @@
 <t>
    The content-coding is a characteristic of the entity identified by
-   the Request-URI. Typically, the entity-body is stored with this
+   the request-target. Typically, the entity-body is stored with this
    encoding and is only decoded before rendering or analogous usage.
    However, a non-transparent proxy &MAY; modify the content-coding if the
@@ -1382 +1382 @@
                     <x:ref>Content-Location-v</x:ref>
   <x:ref>Content-Location-v</x:ref> =
-                    <x:ref>absolute-URI</x:ref> / <x:ref>relativeURI</x:ref>
+                    <x:ref>absolute-URI</x:ref> / <x:ref>partial-URI</x:ref>
 </artwork></figure>
 <t>
@@ -1392 +1392 @@
    requested URI; it is only a statement of the location of the resource
    corresponding to this particular entity at the time of the request.
-   Future requests &MAY; specify the Content-Location URI as the request-URI
+   Future requests &MAY; specify the Content-Location URI as the request-target
    if the desire is to identify the source of that particular
    entity.
@@ -1405 +1405 @@
 <t>
    If the Content-Location is a relative URI, the relative URI is
-   interpreted relative to the Request-URI.
+   interpreted relative to the request-target.
 </t>
 <t>