usefor-article-06 November 2001

6.18.1.  Examples

      User-Agent: tin/1.2-PL2
      User-Agent: tin/1.3-950621beta-PL0 (Unix)
      User-Agent: tin/unoff-1.3-BETA-970813 (UNIX) (Linux/2.0.30 (i486))
      User-Agent: tin/pre-1.4-971106 (UNIX) (Linux/2.0.30 (i486))
      User-Agent: Mozilla/4.02b7 (X11; I; en; HP-UX B.10.20 9000/712)
      User-Agent: Microsoft-Internet-News/4.70.1161
      User-Agent: Gnus/5.4.64 XEmacs/20.3beta17 ("Bucharest")
      User-Agent: Pluto/1.05h (RISC-OS/3.1) NewsHound/1.30
      User-Agent: inn/1.7.2
      User-Agent: telnet

        NOTE: This header supersedes the role performed redundantly by
        experimental headers such as X-Newsreader, X-Mailer, X-Posting-
        Agent, X-Http-User-Agent, and other headers previously used on
        Usenet for this purpose. Use of these experimental headers
        SHOULD be discontinued in favor of the single, standard User-
        Agent header which can be used freely both in Netnews and mail.

--- ../usefor-article-05/4_Examples.out          July 2001
+++ ../usefor-article-06/4_Examples.out          November 2001
@@ -1,57 +1,20 @@
-6.15.2.4.  Examples
+6.18.1.  Examples
 
-   Example 1. The first edition of a FAQ is posted with a message
-   identifier of the form:  <examplegroup-faq@faq-site.example>. The
-   next (but identical) version, a month later, has:
-
-      Message-ID: <examplegroup-faq$v=1$A1b@faq-site.example>
-      Replaces: <examplegroup-faq@faq-site.example>; disposition=repost
-      Supersedes: <examplegroup-faq@faq-site.example>
-   Observe the inclusion of a Supersedes header as well, it being
-   presumed that the Replaces header was not yet widely implemented at
-   that time.
-
-   The next one, another month later (and with some significant changes
-   justifying the use of "replace" rather than "repost") has:
-
-      Message-ID: <examplegroup-faq$v=2$B2b@faq-site.example>
-      Replaces: <examplegroup-faq$v=1$A1b@faq-site.example>
-         <examplegroup-faq@faq-site.example>; disposition=replace
-      Supersedes: <examplegroup-faq$v=1$A1b@faq-site.example>
-
-   The next one, another month later, has:
-
-      Message-ID: <examplegroup-faq$v=3$C3c@faq-site.example>
-      Replaces: <examplegroup-faq$v=2$B2b@faq-site.example>
-         <examplegroup-faq$v=1$A1b@faq-site.example>; disposition=repost
-      Supersedes: <examplegroup-faq$v=2$B2b@faq-site.example>
-
-   Note that the only reason to include more than one message identifier
-   in the Replaces is in case a site had missed the previous
-   Replacement. It is hardly necessary with such a long interval between
-   the postings.
-
-   Under the above, on systems using the version-number system (which is
-   optional) requests for any message identifier in the chain will
-   always return the most recent. As such the URL "news:examplegroup-
-   faq@faq-site.example" will always work, making it suitable to appear
-   in HTML documents.
-
-   Example 2. A user posts a message <myuniquepart@mysite.example> to
-   the net.  She notices a typo and, 2 minutes later, posts with:
-
-      Message-ID: <myuniquepart$v=1$xxx@mysite.example>
-      Replaces: <myuniquepart@mysite.example>; disposition=revise
-
-   3 minutes later she sees another typo, and posts:
-
-      Message-ID: <myuniquepart$v=2$yyy@mysite.example>
-      Replaces: <myuniquepart$v=1$xxx@mysite.example>
-         <myuniquepart@mysite.example>; disposition=revise
-
-   The two bad versions will be replaced with the 3rd, even if a site
-   never sees the 2nd due to batching or feed problems (thus the use of
-   two message identifiers is quite useful in this case, in
-   contradistinction to the first example). Requests for the original
-   will return the 3rd.
+      User-Agent: tin/1.2-PL2
+      User-Agent: tin/1.3-950621beta-PL0 (Unix)
+      User-Agent: tin/unoff-1.3-BETA-970813 (UNIX) (Linux/2.0.30 (i486))
+      User-Agent: tin/pre-1.4-971106 (UNIX) (Linux/2.0.30 (i486))
+      User-Agent: Mozilla/4.02b7 (X11; I; en; HP-UX B.10.20 9000/712)
+      User-Agent: Microsoft-Internet-News/4.70.1161
+      User-Agent: Gnus/5.4.64 XEmacs/20.3beta17 ("Bucharest")
+      User-Agent: Pluto/1.05h (RISC-OS/3.1) NewsHound/1.30
+      User-Agent: inn/1.7.2
+      User-Agent: telnet
+
+        NOTE: This header supersedes the role performed redundantly by
+        experimental headers such as X-Newsreader, X-Mailer, X-Posting-
+        Agent, X-Http-User-Agent, and other headers previously used on
+        Usenet for this purpose. Use of these experimental headers
+        SHOULD be discontinued in favor of the single, standard User-
+        Agent header which can be used freely both in Netnews and mail.