Ignore:
Timestamp:
Jul 16, 2012, 9:32:55 AM (7 years ago)
Author:
julian.reschke@…
Message:

Remove mentions of "seven" parts.

Location:
draft-ietf-httpbis/latest
Files:
6 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.html

    r1807 r1808  
    495495      <meta name="dct.issued" scheme="ISO8601" content="2012-07-16">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests.">
    498       <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests.">
     497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     498      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
    499499   </head>
    500500   <body onload="init();">
     
    535535      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    536536      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
    537          systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
    538          seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    539       </p> 
    540       <p>Part 5 defines range requests and the rules for constructing and combining responses to those requests.</p>
     537         systems. This document defines range requests and the rules for constructing and combining responses to those requests.
     538      </p>
    541539      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    542540      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
  • draft-ietf-httpbis/latest/p5-range.xml

    r1807 r1808  
    101101<t>
    102102   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
    103    distributed, collaborative, hypertext information systems. HTTP has been in
    104    use by the World Wide Web global information initiative since 1990. This
    105    document is Part 5 of the seven-part specification that defines the protocol
    106    referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    107 </t>
    108 <t>
    109    Part 5 defines range requests and the rules for constructing and
    110    combining responses to those requests.
     103   distributed, collaborative, hypertext information systems. This document
     104   defines range requests and the rules for constructing and combining
     105   responses to those requests.
    111106</t>
    112107</abstract>
  • draft-ietf-httpbis/latest/p6-cache.html

    r1807 r1808  
    501501      <meta name="dct.issued" scheme="ISO8601" content="2012-07-16">
    502502      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    503       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
    504       <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     503      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     504      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
    505505   </head>
    506506   <body onload="init();">
     
    549549      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    550550      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
    551          systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the
    552          seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    553       </p> 
    554       <p>Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable
    555          response messages.
     551         systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or
     552         indicate cacheable response messages.
    556553      </p>
    557554      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1807 r1808  
    122122<t>
    123123   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
    124    distributed, collaborative, hypertext information systems. HTTP has been in
    125    use by the World Wide Web global information initiative since 1990. This
    126    document is Part 6 of the seven-part specification that defines the protocol
    127    referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    128 </t>
    129 <t>
    130    Part 6 defines requirements on HTTP caches and the associated header fields
     124   distributed, collaborative, hypertext information systems. This document
     125   defines requirements on HTTP caches and the associated header fields
    131126   that control cache behavior or indicate cacheable response messages.
    132127</t>
  • draft-ietf-httpbis/latest/p7-auth.html

    r1807 r1808  
    492492      <meta name="dct.issued" scheme="ISO8601" content="2012-07-16">
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    494       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework.">
    495       <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework.">
     494      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
     495      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
    496496   </head>
    497497   <body onload="init();">
     
    533533      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    534534      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    535          systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
    536          seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    537       </p> 
    538       <p>Part 7 defines the HTTP Authentication framework.</p>
     535         systems. This document defines the HTTP Authentication framework.
     536      </p>
    539537      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    540538      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1807 r1808  
    100100<t>
    101101   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
    102    distributed, collaborative, hypermedia information systems. HTTP has been in
    103    use by the World Wide Web global information initiative since 1990. This
    104    document is Part 7 of the seven-part specification that defines the protocol
    105    referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    106 </t>
    107 <t>
    108    Part 7 defines the HTTP Authentication framework.
     102   distributed, collaborative, hypermedia information systems. This document
     103   defines the HTTP Authentication framework.
    109104</t>
    110105</abstract>
Note: See TracChangeset for help on using the changeset viewer.