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

Timestamp:

May 26, 2010, 10:25:13 AM (9 years ago)

Author:

julian.reschke@…

Message:

Introduce term "effective request URI" and use it throughout; may require some more fine-tuning (see #196)

File:

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

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

@@ -33 +33 @@
   <!ENTITY qvalue                   "<xref target='Part1' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY uri                      "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY effective-request-uri    "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY compression-codings      "<xref target='Part1' x:rel='#compression.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY transfer-codings         "<xref target='Part1' x:rel='#transfer.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -1338 +1339 @@
 <t>
    The content-coding is a characteristic of the entity identified by
-   the request-target. Typically, the entity-body is stored with this
+   the Effective Request URI (&effective-request-uri;). 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
@@ -1439 +1440 @@
 </artwork></figure>
 <t>
-   The Content-Location value is not a replacement for the original
-   requested URI; it is only a statement of the location of the resource
+   The Content-Location value is not a replacement for the Effective
+   Request URI (&effective-request-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-target
+   Future requests &MAY; may be addressed to the Content-Location URI
    if the desire is to identify the source of that particular
    entity.
@@ -1458 +1459 @@
 <t>
    If the Content-Location is a relative URI, the relative URI is
-   interpreted relative to the request-target.
+   interpreted relative to the Effective Request URI.
 </t>
 <t>
@@ -3150 +3151 @@
   </list>
 </t>
+<t>
+  Partly resolved issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>:
+      "Term for the requested resource's URI"
+    </t>
+  </list>
+</t>
 </section>