Changeset 1463 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

Oct 30, 2011, 7:36:49 PM (8 years ago)

Author:

mnot@…

Message:

Minor editorial tweaks to considerations for new headers ( #231 )

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (2 diffs)

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

@@ -545 +545 @@
    parameters (for instance, Content-Type, defined in &header-content-type;).
    Allowing both unquoted (token) and quoted (quoted-string) syntax for the
-   parameter value enables recipients to use existing parser components. Also,
-   the meaning of a value ought to be independent of the syntax variant used
-   for it (for an example, see the notes on parameter handling for media types
-   in &media-types;).
+   parameter value enables recipients to use existing parser components. When
+   allowing both forms, the meaning of a parameter value ought to be
+   independent of the syntax used for it (for an example, see the notes on
+   parameter handling for media types in &media-types;).
 </t>
 <t>
@@ -557 +557 @@
       <t>Whether the field is a single value, or whether it can be a list
       (delimited by commas; see &header-fields;).</t>
-      <t>If it does not use the list syntax, how to treat messages where the
-      header field occurs multiple times (a sensible default would be to ignore
-      the header field, but this might not always be the right choice).</t>
-      <t>Furthermore, intermediaries and software libraries might combine
+      <t>If it does not use the list syntax, document how to treat messages
+      where the header field occurs multiple times (a sensible default would
+      be to ignore the header field, but this might not always be the right
+      choice).</t>
+      <t>Note that intermediaries and software libraries might combine
       multiple header field instances into a single one, despite the header
       field not allowing this. A robust format enables recipients to discover