Changeset 1680


Ignore:
Timestamp:
20/06/12 18:21:44 (10 years ago)
Author:
julian.reschke@…
Message:

remove temporary TODO markers (see #351)

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

Legend:

Unmodified
Added
Removed

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

    r1667 r1680  
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 3, 2012";
     451       content: "Expires December 22, 2012";
    452452  }
    453453  @bottom-right {
    … …  
    497497      <meta name="dct.creator" content="Reschke, J. F.">
    498498      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    499       <meta name="dct.issued" scheme="ISO8601" content="2012-06-01">
     499      <meta name="dct.issued" scheme="ISO8601" content="2012-06-20">
    500500      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    501       <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation. #351">
    502       <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation. #351">
     501      <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation.">
     502      <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation.">
    503503   </head>
    504504   <body onload="init();">
    … …  
    528528            </tr>
    529529            <tr>
    530                <td class="left">Expires: December 3, 2012</td>
     530               <td class="left">Expires: December 22, 2012</td>
    531531               <td class="right">greenbytes</td>
    532532            </tr>
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">June 1, 2012</td>
     535               <td class="right">June 20, 2012</td>
    536536            </tr>
    537537         </tbody>
    … …  
    544544      </p> 
    545545      <p>Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes,
    546          and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation. <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: #351]</span>
     546         and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation.
    547547      </p>
    548548      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    … …  
    563563         in progress”.
    564564      </p>
    565       <p>This Internet-Draft will expire on December 3, 2012.</p>
     565      <p>This Internet-Draft will expire on December 22, 2012.</p>
    566566      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    567567      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    821821      <p id="rfc.section.1.p.2">Furthermore, it defines HTTP/1.1 message payloads (a.k.a., content), the associated metadata header fields that define how
    822822         the payload is intended to be interpreted by a recipient, the request header fields that might influence content selection,
    823          and the various selection algorithms that are collectively referred to as HTTP content negotiation. <span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: #351]</span>
     823         and the various selection algorithms that are collectively referred to as HTTP content negotiation.
    824824      </p>
    825825      <p id="rfc.section.1.p.3">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
    … …  
    23702370      <p id="rfc.section.7.p.3">Request and Response messages <em class="bcp14">MAY</em> transfer a representation if not otherwise restricted by the request method or response status code. A representation consists
    23712371         of metadata (representation header fields) and data (representation body). When a complete or partial representation is enclosed
    2372          in an HTTP message, it is referred to as the payload of the message. <span class="comment" id="rfc.comment.3">[<a href="#rfc.comment.3" class="smpl">rfc.comment.3</a>: #351]</span>
     2372         in an HTTP message, it is referred to as the payload of the message.
    23732373      </p>
    23742374      <p id="rfc.section.7.p.4">A representation body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any Transfer-Encoding that might have been applied
    2375          to ensure safe and proper transfer of the message. <span class="comment" id="rfc.comment.4">[<a href="#rfc.comment.4" class="smpl">rfc.comment.4</a>: #351]</span>
     2375         to ensure safe and proper transfer of the message.
    23762376      </p>
    23772377      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="identifying.response.associated.with.representation" href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2>

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

    r1667 r1680  
    197197   fields. Furthermore, it defines HTTP message content, metadata, and content
    198198   negotiation.
    199    <cref>#351</cref>
    200199</t>
    201200</abstract>
    … …  
    236235   might influence content selection, and the various selection algorithms
    237236   that are collectively referred to as HTTP content negotiation.
    238    <cref>#351</cref>
    239237</t>
    240238<t>
    … …  
    26162614   body).  When a complete or partial representation is enclosed in an HTTP message,
    26172615   it is referred to as the payload of the message.
    2618    <cref>#351</cref>
    26192616</t>
    26202617<t>
    … …  
    26232620   from the message body by decoding any Transfer-Encoding that might
    26242621   have been applied to ensure safe and proper transfer of the message.
    2625    <cref>#351</cref>
    26262622</t>
    26272623
Note: See TracChangeset for help on using the changeset viewer.