Ignore:
Timestamp:
Jul 22, 2010, 2:09:14 AM (9 years ago)
Author:
fielding@…
Message:

(editorial) replace "metainformation" with more common "metadata"

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r866 r867  
    878878<t>
    879879   The HEAD method is identical to GET except that the server &MUST-NOT;
    880    return a message-body in the response. The metainformation contained
     880   return a message-body in the response. The metadata contained
    881881   in the HTTP headers in response to a HEAD request &SHOULD; be identical
    882882   to the information sent in response to a GET request. This method can
    883    be used for obtaining metainformation about the representation implied by the
     883   be used for obtaining metadata about the representation implied by the
    884884   request without transferring the representation body. This method is
    885885   often used for testing hypertext links for validity, accessibility,
     
    10871087<section title="Status Code Definitions" anchor="status.codes">
    10881088<t>
    1089    Each Status-Code is described below, including any metainformation required
     1089   Each Status-Code is described below, including any metadata required
    10901090   in the response.
    10911091</t>
     
    12321232  <iref primary="true" item="Status Codes" subitem="203 Non-Authoritative Information" x:for-anchor=""/>
    12331233<t>
    1234    The returned metainformation in the entity-header is not the
     1234   The returned metadata in the entity-header is not the
    12351235   definitive set as available from the origin server, but is gathered
    12361236   from a local or a third-party copy. The set presented &MAY; be a subset
    12371237   or superset of the original version. For example, including local
    12381238   annotation information about the resource might result in a superset
    1239    of the metainformation known by the origin server. Use of this
     1239   of the metadata known by the origin server. Use of this
    12401240   response code is not required and is only appropriate when the
    12411241   response would otherwise be 200 (OK).
Note: See TracChangeset for help on using the changeset viewer.