Provide a normative basis for referring to this spec as "Atom 1.0"




The somewhat-implemented pre-IETF dialect of Atom is generally known as 0.3; labeling the final product "1.0" is the clearest way to signal that this supercedes it.


Change the title to "The Atom 1.0 Syndication Format"

Enhance and redistribute the content of the current section 1.2 as follows:

1.2 Namespace and Version

    The XML Namespace URI [W3C.REC-xml-names-19990114] for the XML data
    format described in this specification is:

    [rfc.comment.1: This paragraph to be edited by the RFC Editor. The
    namespace here is a temporary one and will be changed when the IESG
    approves this document as a standard. At that time, the namespace
    will be drawn from W3C URI space. The choice of that namespace will
    be coordinated between the IETF and W3C through their respective

    For convenience, this data format may be referred to as "Atom 1.0". 
    This specification uses "Atom" internally.

1.3 Notational Conventions

    This specification describes conformance in terms of two artifacts;
    Atom Feed Documents and Atom Entry documents. Additionally, it
    places some requirements on Atom Processors.

    This specification uses the namespace prefix "atom:" for the
    Namespace URI identified in section 1.2. above.  Note that the
    choice of namespace prefix is arbitrary and not semantically

    Atom is specified using terms from the XML Infoset
    [W3C.REC-xml-infoset-20040204]. However, this specification uses a
    shorthand for two common terms; the phrase "Information Item" is
    omitted when naming Element Information Items and Attribute
    Information Items.

    Therefore, when this specification uses the term "element," it is
    referring to an Element Information Item in Infoset terms. Likewise,
    when it uses the term "attribute," it is referring to an Attribute
    Information Item.

    Some sections of this specification are illustrated with fragments
    of a non-normative RELAX NG Compact schema [RELAX-NG]. However, the
    text of this specification provides the definition of conformance. A
    complete schema appears in Appendix B.

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    document are to be interpreted as described in BCP 14, [RFC2119], as
    scoped to those conformance targets.


Simplify the marketing task a bit.