usefor-article-06 November 2001

6.15.  Supersedes

   The Supersedes header contains a message identifier specifying an
   article to be superseded upon the arrival of this one. The specified
   article MUST be treated as though a "cancel" control message had
   arrived for the article (but observe that a site MAY choose not to
   honour a "cancel" message, especially if its authenticity is in
   doubt). The content syntax makes use of syntax defined in [RFC 2822].

      Supersedes-content  = msg-id

        NOTE: There is no "c" in "Supersedes".

   If an article contains a Supersedes header, then the old article
   mentioned SHOULD be withdrawn from circulation or access, as in a
   cancel message (7.3), and the new article inserted into the system as
   any other new article would have been.

   Whatever security or authentication checks are normally applied to a
   Control cancel message (or may be prescribed for such messages by
   some extension to this standard - see the remarks in 7.1 and 7.3)
   MUST also be applied to an article with a Supersedes header. In the
   event of the failure of such checks, the article SHOULD be discarded,
   or at most stored as an ordinary article.

--- ../s-o-1036/Supersedes.out          June 1994
+++ ../usefor-article-06/Supersedes.out          November 2001
@@ -1,24 +1,25 @@
-6.14. Supersedes
+6.15.  Supersedes
 
-The  Supersedes header content specifies articles to be can-
-celled on arrival of this one:
+   The Supersedes header contains a message identifier specifying an
+   article to be superseded upon the arrival of this one. The specified
+   article MUST be treated as though a "cancel" control message had
+   arrived for the article (but observe that a site MAY choose not to
+   honour a "cancel" message, especially if its authenticity is in
+   doubt). The content syntax makes use of syntax defined in [RFC 2822].
 
-     Supersedes-content = message-id *( space message-id )
-
-Supersedes is equivalent to Also-Control (section 6.15) with
-an implicit verb of "cancel" (section 7.1).
-
-     NOTE:  Supersedes is normally used where the arti-
-     cle is an updated version of the one(s) being can-
-     celled.
-
-     NOTE: Although the ability to use multiple message
-     IDs in Supersedes is highly desirable (see section
-     7.1), posters are warned that existing implementa-
-     tions often do not correctly handle more than one.
+      Supersedes-content  = msg-id
 
      NOTE: There is no "c" in "Supersedes".
 
-An  article  with a Supersedes header MUST not have an Also-
-Control or Control header.
+   If an article contains a Supersedes header, then the old article
+   mentioned SHOULD be withdrawn from circulation or access, as in a
+   cancel message (7.3), and the new article inserted into the system as
+   any other new article would have been.
+
+   Whatever security or authentication checks are normally applied to a
+   Control cancel message (or may be prescribed for such messages by
+   some extension to this standard - see the remarks in 7.1 and 7.3)
+   MUST also be applied to an article with a Supersedes header. In the
+   event of the failure of such checks, the article SHOULD be discarded,
+   or at most stored as an ordinary article.