Ignore:
Timestamp:
Jan 11, 2008, 6:21:34 PM (12 years ago)
Author:
fielding@…
Message:

editorial: write preliminary introduction to p3 noting future reorg

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r153 r161  
    214214<section title="Introduction" anchor="introduction">
    215215<t>
    216    This document will define aspects of HTTP related to the payload of
    217    messages (message content), including metadata and media types, along
    218    with HTTP content negotiation.  Right now it only includes the extracted
    219    relevant sections of RFC 2616 without edit.
     216   This document defines HTTP message payloads (a.k.a., content), the
     217   associated metadata header fields that define how the payload is intended
     218   to be interpreted by a recipient, the request header fields that
     219   may influence content selection, and the various selection algorithms
     220   that are collectively referred to as HTTP content negotiation.
     221</t>
     222<t>
     223   This document is currently disorganized in order to minimize the changes
     224   between drafts and enable reviewers to see the smaller errata changes.
     225   The next draft will reorganize the sections to better reflect the content.
     226   In particular, the sections on entities will be renamed payload and moved
     227   to the first half of the document, while the sections on content negotiation
     228   and associated request header fields will be moved to the second half.  The
     229   current mess reflects how widely dispersed these topics and associated
     230   requirements had become in <xref target="RFC2616"/>.
    220231</t>
    221232
Note: See TracChangeset for help on using the changeset viewer.