Changeset 908


Ignore:
Timestamp:
24/07/10 08:30:41 (12 years ago)
Author:
fielding@…
Message:

(editorial) use might instead of may where it might be confused with MAY

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p3-payload.xml

    r882 r908  
    230230   associated metadata header fields that define how the payload is intended
    231231   to be interpreted by a recipient, the request header fields that
    232    may influence content selection, and the various selection algorithms
     232   might influence content selection, and the various selection algorithms
    233233   that are collectively referred to as HTTP content negotiation.
    234234</t>
    … …  
    394394   method used with one or more tables to convert a sequence of octets
    395395   into a sequence of characters. Note that unconditional conversion in
    396    the other direction is not required, in that not all characters may
    397    be available in a given character set and a character set may provide
     396   the other direction is not required, in that not all characters might
     397   be available in a given character set and a character set might provide
    398398   more than one sequence of octets to represent a particular character.
    399399   This definition is intended to allow various kinds of character
    … …  
    434434   value of a parameter in a Content-Type header (within a request or
    435435   response), in which case the parameter value of the charset parameter
    436    may be quoted.
     436   can be quoted.
    437437</t>
    438438<t>
    … …  
    583583</t>
    584584<t>
    585    A parameter value that matches the <x:ref>token</x:ref> production may be
     585   A parameter value that matches the <x:ref>token</x:ref> production can be
    586586   transmitted as either a token or within a quoted-string. The quoted and
    587587   unquoted values are equivalent.
    … …  
    790790</t>
    791791<t>
    792    Clients that do so risk drawing incorrect conclusions, which may expose
     792   Clients that do so risk drawing incorrect conclusions, which might expose
    793793   additional security risks (e.g., "privilege escalation"). Implementers are
    794794   encouraged to provide a means of disabling such "content sniffing" when it
    … …  
    796796</t>
    797797<t>
    798    Content-Encoding may be used to indicate any additional content
     798   Content-Encoding is used to indicate any additional content
    799799   codings applied to the data, usually for the purpose of data
    800800   compression, that are a property of the representation.  There is
    … …  
    840840   capabilities to be expressed by a client are large (such as when many
    841841   different formats are supported by a user-agent), server-driven
    842    negotiation becomes unwieldy, and may not be appropriate. Conversely,
     842   negotiation becomes unwieldy, and might not be appropriate. Conversely,
    843843   when the number of representations to choose from is very large,
    844    agent-driven negotiation may not be appropriate.
     844   agent-driven negotiation might not be appropriate.
    845845</t>
    846846<t>
    … …  
    892892    </t>
    893893    <t>
    894          It may limit a public cache's ability to use the same response
     894         It might limit a public cache's ability to use the same response
    895895         for multiple user's requests.
    896896    </t>
    … …  
    929929   header fields or body of the initial response, with each
    930930   representation identified by its own URI. Selection from among the
    931    representations may be performed automatically (if the user agent is
     931   representations can be performed automatically (if the user agent is
    932932   capable of doing so) or manually by the user selecting from a
    933933   generated (possibly hypertext) menu.
    … …  
    14551455   contains a report on the action's status and the same report is
    14561456   available (for future access with GET) at the given URI.  For
    1457    example, a purchase transaction made via the POST method may
     1457   example, a purchase transaction made via the POST method might
    14581458   include a receipt document as the payload of the 200 response;
    14591459   the Content-Location value provides an identifier for retrieving
    … …  
    20642064  <seriesInfo name="RFC" value="1950"/>
    20652065  <annotation>
    2066     RFC 1950 is an Informational RFC, thus it may be less stable than
     2066    RFC 1950 is an Informational RFC, thus it might be less stable than
    20672067    this specification. On the other hand, this downward reference was
    20682068    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
    … …  
    20832083  <seriesInfo name="RFC" value="1951"/>
    20842084  <annotation>
    2085     RFC 1951 is an Informational RFC, thus it may be less stable than
     2085    RFC 1951 is an Informational RFC, thus it might be less stable than
    20862086    this specification. On the other hand, this downward reference was
    20872087    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
    … …  
    21142114  <seriesInfo name="RFC" value="1952"/>
    21152115  <annotation>
    2116     RFC 1952 is an Informational RFC, thus it may be less stable than
     2116    RFC 1952 is an Informational RFC, thus it might be less stable than
    21172117    this specification. On the other hand, this downward reference was
    21182118    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),

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

    r879 r908  
    357357</artwork></figure>
    358358<t>
    359    In this case, the response may or may not use the gzip content coding.
     359   In this case, the response might or might not use the gzip content coding.
    360360   If it does not, the response might look like:
    361361</t>
    … …  
    10741074   The exact meaning of this header field depends on the implementation
    10751075   of the origin server and the nature of the original resource. For
    1076    files, it may be just the file system last-modified time. For
    1077    representations with dynamically included parts, it may be the most recent
     1076   files, it might be just the file system last-modified time. For
     1077   representations with dynamically included parts, it might be the most recent
    10781078   of the set of last-modify times for its component parts. For database
    1079    gateways, it may be the last-update time stamp of the record. For
    1080    virtual objects, it may be the last time the internal state changed.
     1079   gateways, it might be the last-update time stamp of the record. For
     1080   virtual objects, it might be the last time the internal state changed.
    10811081</t>
    10821082<t>

  • draft-ietf-httpbis/latest/p5-range.xml

    r874 r908  
    12871287      Notes:
    12881288  <list style="numbers">
    1289       <t>Additional CRLFs may precede the first boundary string in the body.</t>
     1289      <t>Additional CRLFs &MAY; precede the first boundary string in the body.</t>
    12901290
    12911291      <t>Although <xref target="RFC2046"/> permits the boundary string to be

  • draft-ietf-httpbis/latest/p6-cache.xml

    r897 r908  
    237237  controls its message storage, retrieval, and deletion. A cache stores cacheable responses
    238238  in order to reduce the response time and network bandwidth consumption on future,
    239   equivalent requests. Any client or server may include a cache, though a cache cannot be
     239  equivalent requests. Any client or server &MAY; employ a cache, though a cache cannot be
    240240  used by a server that is acting as a tunnel.
    241241</t>
    … …  
    262262  <list>
    263263    <t>A response is cacheable if a cache is allowed to store a copy of the response message
    264       for use in answering subsequent requests. Even when a response is cacheable, there may
     264      for use in answering subsequent requests. Even when a response is cacheable, there might
    265265      be additional constraints on whether a cache can use the cached copy to satisfy a
    266266      particular request.</t>
    … …  
    537537  assign an explicit expiration time in the past. This means that the response is always
    538538  stale, so that caches should validate it before using it for subsequent requests.
    539   <cref anchor="TODO-response-stale">This wording may cause confusion, because the response may still be served stale.</cref>
    540 </t>
    541 <t>
    542   Since origin servers do not always provide explicit expiration times, HTTP caches may
    543   also assign heuristic expiration times when they are not specified, employing algorithms that
     539  <cref anchor="TODO-response-stale">This wording might cause confusion, because the response might still be served stale.</cref>
     540</t>
     541<t>
     542  Since origin servers do not always provide explicit expiration times, HTTP caches &MAY;
     543  assign heuristic expiration times when explicit times are not specified, employing algorithms that
    544544  use other header values (such as the Last-Modified time) to estimate a plausible
    545545  expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does
    … …  
    559559</t>
    560560<t>
    561   Additionally, clients may need to influence freshness calculation. They can do this using
     561  Additionally, clients might need to influence freshness calculation. They can do this using
    562562  several request cache directives, with the effect of either increasing or loosening
    563563  constraints on freshness. See <xref target="cache-request-directive" />.
    … …  
    874874</t>
    875875<t>
    876   If (after any normalisation that may take place) a header field is absent
     876  If (after any normalization that might take place) a header field is absent
    877877  from a request, it can only match another request if it is also absent there.
    878878</t>
    … …  
    899899<t>
    900900  If the new response contains an ETag, it identifies the stored 
    901   response to use. <cref anchor="TODO-mention-CL">may need language about Content-Location 
     901  response to use. <cref anchor="TODO-mention-CL">might need language about Content-Location 
    902902  here</cref><cref anchor="TODO-inm-mult-etags">cover case where INM with multiple etags was sent</cref>
    903903</t>
    … …  
    973973<t>
    974974  The presence of an Age header field in a response implies that a response is not
    975   first-hand. However, the converse is not true, since HTTP/1.0 caches may not implement the
     975  first-hand. However, the converse is not true, since HTTP/1.0 caches might not implement the
    976976  Age header field.
    977977</t>
    … …  
    10571057    <t>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In
    10581058      particular, malicious or compromised caches might not recognize or obey this
    1059       directive, and communications networks may be vulnerable to eavesdropping.</t>
     1059      directive, and communications networks might be vulnerable to eavesdropping.</t>
    10601060  </list>
    10611061</t>
    … …  
    11591159      cache, whereas the remainder of the response message &MAY; be.</t>
    11601160    <t>
    1161       <x:h>Note:</x:h> This usage of the word private only controls where the response may
    1162       be stored, and cannot ensure the privacy of the message content.
     1161      <x:h>Note:</x:h> This usage of the word private only controls where the response can
     1162      be stored; it cannot ensure the privacy of the message content.
    11631163      Also, private response directives with field-names are often handled by
    11641164      implementations as if an unqualified private directive was received; i.e.,
    … …  
    12031203    <t>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In
    12041204      particular, malicious or compromised caches might not recognize or obey this
    1205       directive, and communications networks may be vulnerable to eavesdropping.</t>
     1205      directive, and communications networks might be vulnerable to eavesdropping.</t>
    12061206  </list>
    12071207</t>
    … …  
    14511451  request-headers (e.g., the network address of the client), play a role in the selection of
    14521452  the response representation; therefore, a cache cannot determine whether this response is
    1453   appropriate. The "*" value &MUST-NOT; be generated by a proxy server;
    1454   it may only be generated by an origin server.
     1453  appropriate. The "*" value &MUST-NOT; be generated by a proxy server.
    14551454</t>
    14561455<t>
Note: See TracChangeset for help on using the changeset viewer.