Changeset 1299

Timestamp:

27/05/11 10:20:15 (9 years ago)

Author:

julian.reschke@…

Message:

AUTH48: consistency: say 'field value' throughout

Location:

draft-ietf-httpbis-content-disp/latest

Files:

• draft-ietf-httpbis-content-disp.html (modified) (1 diff)
• draft-ietf-httpbis-content-disp.xml (modified) (2 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

@@ -487 +487 @@
          the requirements associated with its role.
       </p>
-      <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field-value to be invalid, using both ABNF and prose requirements
-         (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>), but it does not define special handling of these invalid field-values.
+      <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field value to be invalid, using both ABNF and prose requirements
+         (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>), but it does not define special handling of these invalid field values.
       </p>
       <p id="rfc.section.3.p.3">Senders <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
       </p>
-      <p id="rfc.section.3.p.4">Recipients <em class="bcp14">MAY</em> take steps to recover a usable field-value from an invalid header field, but <em class="bcp14">SHOULD NOT</em> reject the message outright, unless this is explicitly desirable behavior (e.g., the implementation is a validator). As such,
+      <p id="rfc.section.3.p.4">Recipients <em class="bcp14">MAY</em> take steps to recover a usable field value from an invalid header field, but <em class="bcp14">SHOULD NOT</em> reject the message outright, unless this is explicitly desirable behavior (e.g., the implementation is a validator). As such,
          the default handling of invalid fields is to ignore them.
       </p>

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

@@ -137 +137 @@
 </t>
 <t>
-  This specification also defines certain forms of the header field-value to be
+  This specification also defines certain forms of the header field value to be
   invalid, using both ABNF and prose requirements (<xref target="header.field.definition"/>),
-  but it does not define special handling of these invalid field-values. 
+  but it does not define special handling of these invalid field values. 
 </t>
 <t>
@@ -146 +146 @@
 </t>
 <t>
-  Recipients &MAY; take steps to recover a usable field-value
+  Recipients &MAY; take steps to recover a usable field value
   from an invalid header field, but &SHOULD-NOT; reject the message outright,
   unless this is explicitly desirable behavior (e.g., the implementation is a