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

Timestamp:

31/07/10 01:06:01 (12 years ago)

Author:

fielding@…

Message:

Replace lowercase should with less normative words, where possible.

File:

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

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

@@ -729 +729 @@
 <iref item="Safe Methods" primary="true"/>
 <t>
-   Implementors should be aware that the software represents the user in
-   their interactions over the Internet, and should be careful to allow
+   Implementors need to be aware that the software represents the user in
+   their interactions over the Internet, and need to allow
    the user to be aware of any actions they take which might have an
    unexpected significance to themselves or others.
@@ -1329 +1329 @@
     <x:h>Note:</x:h> An earlier version of this specification recommended a
     maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>).
-    Content developers should be aware that there might be clients that
+    Content developers need to be aware that some clients might
     implement such a fixed limitation.
   </t>
@@ -2179 +2179 @@
    obsolete or mistyped links to be traced for maintenance. Some servers use
    Referer as a means of controlling where they allow links from (so-called
-   "deep linking"), but it should be noted that legitimate requests are not
-   required to contain a Referer header field.
+   "deep linking"), but legitimate requests do not always
+   contain a Referer header field.
 </t>
 <t>
@@ -2329 +2329 @@
 </t>
 <t>
-   The HTTP Method Registry should be created at <eref target="http://www.iana.org/assignments/http-methods"/>
+   The HTTP Method Registry shall be created at <eref target="http://www.iana.org/assignments/http-methods"/>
    and be populated with the registrations below:
 </t>
@@ -2391 +2391 @@
 <t>
    The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
-   should be updated with the registrations below:
+   shall be updated with the registrations below:
 </t>
 <?BEGININC p2-semantics.iana-status-codes ?>
@@ -2585 +2585 @@
 <section title="Header Field Registration" anchor="header.field.registration">
 <t>
-   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> should be updated
+   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    with the permanent registrations below (see <xref target="RFC3864"/>):
 </t>
@@ -2744 +2744 @@
 </t>
 <t>
-   Authors of services should not use GET-based forms for the submission of
-   sensitive data because that data will be encoded in the request-target. Many
+   Authors of services &SHOULD-NOT; use GET-based forms for the submission of
+   sensitive data because that data will be placed in the request-target. Many
    existing servers, proxies, and user agents log or display the request-target
    in places where it might be visible to third parties. Such services can