Ignore:
Timestamp:
Jul 23, 2010, 2:19:25 AM (9 years ago)
Author:
julian.reschke@…
Message:

change citing style to match RFC Editor expectations (see <http://www.rfc-editor.org/rfc-style-guide/rfc-style>, Section 3.3)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r874 r879  
    330330</t>
    331331<t>
    332    A "weak entity-tag," indicated by the "W/" prefix, &MAY; be shared by
     332   A "weak entity-tag", indicated by the "W/" prefix, &MAY; be shared by
    333333   two representations of a resource only if the representations are equivalent and
    334334   could be substituted for each other with no significant change in
     
    460460   header fields and representation body) changes in any way, then the
    461461   associated validator would change as well. If this is true, then we
    462    call this validator a "strong validator."
     462   call this validator a "strong validator".
    463463</t>
    464464<t>
     
    466466   validator only on semantically significant changes, and not when
    467467   insignificant aspects of the representation change. A validator that does not
    468    always change when the representation changes is a "weak validator."
     468   always change when the representation changes is a "weak validator".
    469469</t>
    470470<t>
    471471   An entity-tag is normally a strong validator, but the protocol
    472    provides a mechanism to tag an entity-tag as "weak." One can think of
     472   provides a mechanism to tag an entity-tag as "weak". One can think of
    473473   a strong validator as one that changes whenever the sequence of bits
    474474   in a representation changes, while a weak value changes whenever the
Note: See TracChangeset for help on using the changeset viewer.