usefor-article-11 June 2003

6.21.1.  Syntax

   The following headers may be used within articles conforming to this
   standard.

        MIME-Version:                [RFC 2045]
        Content-Type:                [RFC 2045],[RFC 2046]
        Content-Transfer-Encoding:   [RFC 2045]
        Content-ID:                  [RFC 2045]
        Content-Description:         [RFC 2045]
        Content-Disposition:         [RFC 2183]
        Content-Location:            [RFC 2557]
        Content-Language:            [RFC 3282]
        Content-MD5:                 [RFC 1864]

   The RFCs listed are deemed to be incorporated into this standard to
   the extent necessary to facilitate their usage within Netnews,
   subject to curtailment of that usage as described in the following
   sections. Moreover, extensions to those standards registered in
   accordance with [RFC 2048] are also available for use within Netnews,
   as indeed is any other header in the Content-* series which has a
   sensible interpretation within Netnews.


   Insofar as the syntax for these headers, as given in those RFCs does
   not specify precisely where whitespace and comments may occur
   (whether in the form of WSP, FWS or CFWS), the usage defined in this
   standard, and failing that in [RFC 2822], and failing that in [RFC
   822] MUST be followed. In particular, there MUST NOT be any WSP
   between a header-name and the following colon and there MUST be a SP
   following that colon.

--- ../usefor-article-10/1_Syntax.out          April 2003
+++ ../usefor-article-11/1_Syntax.out          June 2003
@@ -3,7 +3,6 @@
    The following headers may be used within articles conforming to this
    standard.
 
-
         MIME-Version:                [RFC 2045]
         Content-Type:                [RFC 2045],[RFC 2046]
         Content-Transfer-Encoding:   [RFC 2045]
@@ -21,6 +20,7 @@
    accordance with [RFC 2048] are also available for use within Netnews,
    as indeed is any other header in the Content-* series which has a
    sensible interpretation within Netnews.
+
 
    Insofar as the syntax for these headers, as given in those RFCs does
    not specify precisely where whitespace and comments may occur