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

Timestamp:

22/10/10 02:05:57 (10 years ago)

Author:

mnot@…

Message:

Remove RFC2119 language from method considerations, tweak text; for #230

File:

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

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

@@ -489 +489 @@
 </t>
 <t>
-   New methods &SHOULD; be potentially applicable to any resource. I.e.,
-   they should not be specific to any particular media type, "type" of
-   resource, or application.
+   HTTP methods are generic; that is, they are potentially applicable to any
+   resource, not just one particular media type, "type" of resource, or
+   application. As such, it is preferred that new HTTP methods be registered
+   in a document that isn't specific to a single application, so that this is
+   clear.
 </t>
 <t>
@@ -501 +503 @@
 </t>
 <t>
-   New methods &MUST; define whether they are safe (<xref
+   New method definitions need to indicate whether they are safe (<xref
    target="safe.methods"/>) and whether they are idempotent (<xref
-   target="idempotent.methods"/>). They &MUST; also state whether they can be
+   target="idempotent.methods"/>). They also need to state whether they can be
    cached (&caching;); in particular what conditions a cache may store the
    response, and under what conditions such a stored response may be used to
    satisfy a subsequent request.
-</t>
-<t>
-   New methods &SHOULD; explain how conditional request headers
-   (&conditional;) affect the response (if there is any effect).
-</t>
-<t>
-   HTTP methods &SHOULD; be registered in a document that isn't specific to
-   a single application or other use of HTTP, so that it's clear that they are
-   not specific to that application or extension.
 </t>
 </section>