s-o-1036 June 1994

[< Prev] [TOC] [ Next >]
6.9. Summary

The Summary header content is a short phrase summarizing the
article's content:

     Summary-content = nonblank-text

As with the subject, no restriction is placed on the content
since it is intended solely for display to humans.

     NOTE: Reading agents should be aware that the Sum-
     mary  header  is often used as a sort of secondary
     Subject header,  and  (if  present)  its  contents
     should  perhaps  be  displayed when the subject is
     displayed.

The summary SHOULD be terse.  Posters SHOULD avoid trying to
cram  their  entire  article into the headers; even the sim-
plest query usually benefits from a sentence or two of elab-
oration  and context, and not all reading agents display all
headers.
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usefor May 2005
usefor-usefor April 2005
usefor-usefor November 2004
usefor-usefor September 2004
News Article Format and Transmission May 2004
News Article Format and Transmission November 2003
News Article Format June 2003
News Article Format April 2003
News Article Format February 2003
News Article Format August 2002
News Article Format May 2002
News Article Format November 2001
News Article Format July 2001
News Article Format April 2001
News Article Format February 2000
RFC 1036 December 1987

--- ../rfc1036/Summary.out          December 1987
+++ ../s-o-1036/Summary.out          June 1994
@@ -1,7 +1,22 @@
-2.2.10.  Summary
+6.9. Summary
 
-    This line should contain a brief summary of the message.  It is
-    usually used as part of a follow-up to another message.  Again, it
-    is very useful to the reader in determining whether to read the
-    message.
+The Summary header content is a short phrase summarizing the
+article's content:
+
+     Summary-content = nonblank-text
+
+As with the subject, no restriction is placed on the content
+since it is intended solely for display to humans.
+
+     NOTE: Reading agents should be aware that the Sum-
+     mary  header  is often used as a sort of secondary
+     Subject header,  and  (if  present)  its  contents
+     should  perhaps  be  displayed when the subject is
+     displayed.
+
+The summary SHOULD be terse.  Posters SHOULD avoid trying to
+cram  their  entire  article into the headers; even the sim-
+plest query usually benefits from a sentence or two of elab-
+oration  and context, and not all reading agents display all
+headers.
 

Documents were processed to this format by Forrest J. Cavalier III