Changeset 2502

Timestamp:

04/12/13 11:17:28 (9 years ago)

Author:

julian.reschke@…

Message:

s/filesystem/file system/ (see #234)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (2 diffs)
• p4-conditional.html (modified) (5 diffs)
• p4-conditional.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -448 +448 @@
   }
   @bottom-center {
-       content: "Expires June 4, 2014";
+       content: "Expires June 7, 2014";
   }
   @bottom-right {
@@ -493 +493 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-12-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-12-04">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
@@ -521 +521 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">December 1, 2013</td>
+               <td class="right">December 4, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: June 4, 2014</td>
+               <td class="left">Expires: June 7, 2014</td>
                <td class="right"></td>
             </tr>
@@ -553 +553 @@
             in progress”.
          </p>
-         <p>This Internet-Draft will expire on June 4, 2014.</p>
+         <p>This Internet-Draft will expire on June 7, 2014.</p>
       </div>
       <div id="rfc.copyrightnotice">
@@ -1469 +1469 @@
                   people speak of retrieving some identifiable information via HTTP, they are generally referring to making a GET request.
                </p>
-               <p id="rfc.section.4.3.1.p.2">It is tempting to think of resource identifiers as remote filesystem pathnames, and of representations as being a copy of
+               <p id="rfc.section.4.3.1.p.2">It is tempting to think of resource identifiers as remote file system pathnames, and of representations as being a copy of
                   the contents of such files. In fact, that is how many resources are implemented (see <a href="#attack.pathname" title="Attacks Based On File and Path Names">Section&nbsp;9.1</a> for related security considerations). However, there are no such limitations in practice. The HTTP interface for a resource
                   is just as likely to be implemented as a tree of content objects, a programmatic view on various database records, or a gateway
-                  to other information systems. Even when the URI mapping mechanism is tied to a filesystem, an origin server might be configured
+                  to other information systems. Even when the URI mapping mechanism is tied to a file system, an origin server might be configured
                   to execute the files with the request as input and send the output as the representation, rather than transfer the files directly.
                   Regardless, only the origin server needs to know how each of its resource identifiers corresponds to an implementation, and

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1298 +1298 @@
 </t>
 <t>
-   It is tempting to think of resource identifiers as remote filesystem
+   It is tempting to think of resource identifiers as remote file system
    pathnames, and of representations as being a copy of the contents of such
    files. In fact, that is how many resources are implemented (see
@@ -1306 +1306 @@
    objects, a programmatic view on various database records, or a gateway to
    other information systems. Even when the URI mapping mechanism is tied to a
-   filesystem, an origin server might be configured to execute the files with
+   file system, an origin server might be configured to execute the files with
    the request as input and send the output as the representation, rather than
    transfer the files directly. Regardless, only the origin server needs to

draft-ietf-httpbis/latest/p4-conditional.html

@@ -448 +448 @@
   }
   @bottom-center {
-       content: "Expires June 4, 2014";
+       content: "Expires June 7, 2014";
   }
   @bottom-right {
@@ -491 +491 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-12-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-12-04">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
@@ -517 +517 @@
             </tr>
             <tr>
-               <td class="left">Expires: June 4, 2014</td>
-               <td class="right">December 1, 2013</td>
+               <td class="left">Expires: June 7, 2014</td>
+               <td class="right">December 4, 2013</td>
             </tr>
          </tbody>
@@ -546 +546 @@
             in progress”.
          </p>
-         <p>This Internet-Draft will expire on June 4, 2014.</p>
+         <p>This Internet-Draft will expire on June 7, 2014.</p>
       </div>
       <div id="rfc.copyrightnotice">
@@ -826 +826 @@
                <p id="rfc.section.2.3.1.p.2">For example, a resource that has implementation-specific versioning applied to all changes might use an internal revision
                   number, perhaps combined with a variance identifier for content negotiation, to accurately differentiate between representations.
-                  Other implementations might use a collision-resistant hash of representation content, a combination of various filesystem
+                  Other implementations might use a collision-resistant hash of representation content, a combination of various files system
                   attributes, or a modification timestamp that has sub-second resolution.
                </p>

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -477 +477 @@
    accurately differentiate between representations.
    Other implementations might use a collision-resistant hash of
-   representation content,
-   a combination of various filesystem attributes, or a modification
-   timestamp that has sub-second resolution.
+   representation content, a combination of various files system attributes, or
+   a modification timestamp that has sub-second resolution.
 </t>
 <t>