element.
Receiving software which displays the content MAY use the markup to
aid in displaying it.
If the value of "type" is "XHTML", the content of the Text construct
MAY contain child elements. The content SHOULD be XHTML text and
markup that could validly appear directly within an xhtml:div
element. Receiving software which displays the content MAY use the
markup to aid in displaying it.
3.2 Person Constructs
A Person construct is an element that describes a person,
Nottingham & Sayre Expires April 20, 2005 [Page 8]
Internet-Draft Atom Format October 2004
corporation, or similar entity.
Person constructs MAY be extended by namespace-qualified element
children.
This specification assigns no significance to the order of appearance
of the child elements of atom:entry.
3.2.1 "atom:name" Element
The "atom:name" element's content conveys a human-readable name for
the person. Person constructs MUST contain exactly one "atom:name"
element.
3.2.2 "atom:uri" Element
The "atom:uri" element's content conveys a URI associated with the
person. Person constructs MAY contain an atom:uri element, but MUST
NOT contain more than one. The content of atom:uri in a Person
construct MUST be a URI [RFC2396].
xml:base [W3C.REC-xmlbase-20010627] processing MUST be applied to the
atom:uri element's content.
3.2.3 "atom:email" Element
The "atom:email" element's content conveys an e-mail address
associated with the persons. Person constructs MAY contain an
atom:email element, but MUST NOT contain more than one. Its content
MUST be an e-mail address [RFC2822].
3.3 Date Constructs
A Date construct is an element whose content MUST conform to the
date-time BNF rule in [RFC3339].
3.4 Service Constructs
A Service construct is an empty element that conveys the URI of an
Atom Publishing Protocol [Atom-protocol] service associated with an
entry or feed.
A Service construct has the following attribute:
3.4.1 "href" Attribute
The "href" attribute contains the a URI pointing to the endpoint of
the service named by the name attribute. atom:service elements MUST
Nottingham & Sayre Expires April 20, 2005 [Page 9]
Internet-Draft Atom Format October 2004
have a "href" attribute, whose value MUST be a URI.
xml:base processing MUST be applied to the "href" attribute.
3.5 Link Constructs
A Link construct is an empty element that describes a connection from
an Atom document to another Web resource.
3.5.1 "rel" Attribute
The "rel" attribute indicates the type of relationship that the link
represents. Link constructs MAY have a rel attribute, whose value
MUST be a string, and MUST be one of the following values:
"alternate", "related".
If the "rel" attribute is not present, the link element MUST be
interpreted as if the value "alternate" had been supplied.
3.5.2 "type" Attribute
The "type" attribute indicates an advisory media type; it MAY be used
as a hint to determine the type of the representation which should be
returned when the URI in the href attribute is dereferenced. Note
that the type attribute does not override the actual media type
returned with the representation.
Link constructs MAY have a type attribute, whose value MUST be a
registered media type [RFC2045].
3.5.3 "href" Attribute
The "href" attribute contains the link's URI. Link constructs MUST
have a href attribute, whose value MUST be a URI [RFC2396].
xml:base [W3C.REC-xmlbase-20010627] processing MUST be applied to the
href attribute's content.
3.5.4 "hreflang" Attribute
The "hreflang" attribute's content describes the language of the
resource pointed to by the href attribute. When used together with
the rel="alternate", it implies a translated version of the entry.
Link constructs MAY have an hreflang attribute, whose value MUST be a
language tag [RFC3066].
Nottingham & Sayre Expires April 20, 2005 [Page 10]
Internet-Draft Atom Format October 2004
3.5.5 "title" Attribute
The "title" attribute conveys human-readable information about the
link. Link constructs MAY have a title attribute.
3.6 Identity Constructs
An Identity construct is an element whose content conveys a
permanent, universally unique identifier for the construct's parent.
Its content MUST be an absolute URI [RFC2396].
When an Atom document is relocated, migrated, syndicated,
republished, exported or imported, the content of its Identity
construct MUST NOT change. Put another way, an Identity construct
pertains to all instantiations of a particular Atom entry or feed;
revisions retain the same content in their Identity constructs.
3.6.1 Dereferencing Identity Constructs
The content of an Identity construct MAY be dereferencable (e.g. an
HTTP URI). However, processors MUST NOT assume it to be
dereferencable.
The content of an Identity construct MUST be created in a way that
assures uniqueness, and it is suggested that the Identity construct
be stored along with the associated resource.
Because of the risk of confusion between URIs that would be
equivalent if dereferenced, the following normalization strategy is
strongly encouraged when generating Identity constructs:
o Provide the scheme in lowercase characters.
o Provide the host, if any, in lowercase characters.
o Only perform percent-encoding where it is essential.
o Use uppercase A-through-F characters when percent-encoding.
o Prevent dot-segments appearing in paths.
o For schemes that define a default authority, use an empty
authority if the default is desired.
o For schemes that define an empty path to be equivalent to a path
of "/", use "/".
o For schemes that define a port, use an empty port if the default
is desired.
o Preserve empty fragment identifiers and queries.
o Ensure that all portions of the URI are utf-8 encoded NFC form
Unicode strings.
Nottingham & Sayre Expires April 20, 2005 [Page 11]
Internet-Draft Atom Format October 2004
3.6.2 Comparing Identity Constructs
Instances of Identity constructs can be compared to determine whether
an entry or feed is the same as one seen before. Processors MUST
compare Identity constructs on a character-by-character basis in a
case-sensitive fashion.
As a result, two URIs that resolve to the same resource but are not
character-for-character identical will be considered different for
the purposes of Identifier comparison.
For example, "http://www.example.org/thing",
"http://www.example.org/Thing", "http://www.EXAMPLE.org/thing" and
"HTTP://www.example.org/thing" will all be considered different
identifiers, despite their differences in case.
Likewise, "http://www.example.com/~bob",
"http://www.example.com/%7ebob" and "http://www.example.com/%7Ebob"
will all be considered different identifiers, because URI %-escaping
is significant for the purposes of comparison.
Nottingham & Sayre Expires April 20, 2005 [Page 12]
Internet-Draft Atom Format October 2004
4. The "atom:feed" Element
The "atom:feed" element is the document (i.e., top-level) element of
an Atom Feed Document, acting as a container for metadata and data
associated with the feed. Its first element child MUST be atom:head,
which MAY be followed zero or more atom:entry child elements.
4.1 "version" Attribute
atom:feed elements MUST have a "version" attribute whose content
indicates the version of the Atom specification that the feed
conforms to. The content of this attribute is unstructured text.
The version identifier for this specification is
"draft-ietf-atompub-format-03: do not deploy".
4.2 The "atom:head" Element
The atom:head element acts as a container for metadata about the feed
itself.
The atom:head element MAY contain any namespace-qualified
[W3C.REC-xml-names-19990114] elements as children. This
specification assigns no significance to the order of appearance of
the child elements of atom:head.
The following child elements are defined by this specification (note
that the presence of some of these elements is required):
4.2.1 "atom:title" Element
The "atom:title" element is a Text construct that conveys a
human-readable title for the feed. atom:head elements MUST contain
exactly one atom:title element.
4.2.2 "atom:link" Element
The "atom:link" element is a Link construct that conveys a URI
associated with the feed. The nature of the relationship is
determined by the construct's rel attribute.
atom:head elements MUST contain at least one atom:link element with a
rel attribute value of "alternate".
atom:head elements MUST NOT contain more than one atom:link element
with a rel attribute value of "alternate" that has the same type
attribute value.
Nottingham & Sayre Expires April 20, 2005 [Page 13]
Internet-Draft Atom Format October 2004
If a feed's atom:link element with type="alternate" resolves to an
HTML document, then that document SHOULD have a autodiscovery link
element [Atom-autodiscovery] that reflects back to the feed.
atom:head elements MAY contain additional atom:link elements beyond
those described above.
4.2.3 "atom:introspection" Element
The "atom:introspection" element is a Service construct that conveys
the URI of an introspection file associated with the feed. atom:head
elements MUST NOT contain more than one atom:introspection element.
4.2.4 "atom:post" Element
The "atom:post" element is a Service construct that conveys the URI
used to add entries to the feed. atom:head elements MUST NOT contain
more than one atom:post element.
4.2.5 "atom:author" Element
The "atom:author" element is a Person construct that indicates the
default author of the feed. atom:head elements MUST contain exactly
one atom:author element, UNLESS all of the atom:feed element's child
atom:entry elements contain an atom:author element. atom:head
elements MUST NOT contain more than one atom:author element.
[[explain inheritance]]
4.2.6 "atom:contributor" Element
The "atom:contributor" element is a Person construct that indicates a
person or other entity who contributes to the feed. atom:head
elements MAY contain one or more atom:contributor elements.
4.2.7 "atom:tagline" Element
The "atom:tagline" element is a Text construct that conveys a
human-readable description or tagline for the feed. atom:head
elements MAY contain an atom:tagline element, but MUST NOT contain
more than one.
4.2.8 "atom:id" Element
The "atom:id" element is an Identity construct that conveys a
permanent, universally unique identifier for a feed. atom:head
elements MAY contain an atom:id element, but MUST NOT contain more
than one.
Nottingham & Sayre Expires April 20, 2005 [Page 14]
Internet-Draft Atom Format October 2004
4.2.9 "atom:generator" Element
The "atom:generator" element's content identifies the software agent
used to generate the feed, for debugging and other purposes.
atom:head elements MAY contain an atom:generator element, but MUST
NOT contain more than one.
The content of this element, when present, MUST be a string that is a
human-readable name for the generating agent.
The atom:generator element MAY have a "uri" attribute whose value
MUST be a URI. When dereferenced, that URI SHOULD produce a
representation that is relevant to that agent.
The atom:generator element MAY have a "version" attribute that
indicates the version of the generating agent. When present, its
value is unstructured text.
4.2.10 "atom:copyright" Element
The "atom:copyright" element is Text construct that conveys a
human-readable copyright statement for the feed. atom:head elements
MAY contain an atom:copyright element, but MUST NOT contain more than
one.
The atom:copyright element SHOULD NOT be used to convey
machine-readable licensing information.
[[Is the following paragraph bogus amateur lawyering? The first
paragraph seems sufficient.]]
The atom:copyright element may be assumed to apply to all entries
contained by the feed except those entries which contain
atom:copyright elements. The atom:copyright element MUST, if
present, be considered to apply to the feed as a collection of
entries.
4.2.11 "atom:info" Element
The "atom:info" element is a Text construct that conveys a
human-readable explanation of the feed format itself. atom:head
elements MAY contain an atom:info element, but MUST NOT contain more
than one.
The atom:info element SHOULD NOT considered meaningful by processors;
it is a convenience to publishers in certain situations.
Nottingham & Sayre Expires April 20, 2005 [Page 15]
Internet-Draft Atom Format October 2004
4.2.12 "atom:updated" Element
The "atom:updated" element is a Date construct indicating the most
recent instant in time when a change to the feed was made that the
publisher wishes to bring to the attention of subscribers. For
example, such changes might not include minor adjustments like
spelling and grammatical corrections.
atom:head elements MUST contain exactly one atom:updated element.
Nottingham & Sayre Expires April 20, 2005 [Page 16]
Internet-Draft Atom Format October 2004
5. The "atom:entry" Element
The "atom:entry" element represents an individual entry. This
element can appear as a child of the atom:feed element, or it can
appear as the document (i.e., top-level) element of a standalone Atom
Entry Document.
When appearing in an Atom Entry Document, atom:entry elements MUST
have a "version" attribute whose content indicates the version of the
Atom specification that the entry conforms to.
The version identifier for this specification is
"draft-ietf-atompub-format-03: do not deploy".
The atom:entry element MAY contain any namespace-qualified
[W3C.REC-xml-names-19990114] elements as children. This
specification assigns no significance to the order of appearance of
the child elements of atom:entry.
The following child elements are defined by this specification (note
that it requires the presence of some of these elements):
5.1 "atom:title" Element
The "atom:title" element is a Text construct that conveys a
human-readable title for the entry. atom:entry elements MUST have
exactly one "atom:title" element.
5.2 "atom:link" Element
The "atom:link" element is a Link construct that conveys a URI
associated with the entry. The nature of the relationship as well as
the link itself is determined by the element's content.
atom:entry elements MUST contain at least one atom:link element with
a rel attribute value of "alternate".
atom:entry elements MUST NOT contain more than one atom:link element
with a rel attribute value of "alternate" that has the same type
attribute value.
atom:entry elements MAY contain additional atom:link elements beyond
those described above.
5.3 "atom:edit" Element
The "atom:edit" element is a Service construct that conveys the URI
used to retrieve and edit the source representation of the entry.
Nottingham & Sayre Expires April 20, 2005 [Page 17]
Internet-Draft Atom Format October 2004
atom:entry elements MUST NOT contain more than one atom:edit element.
5.4 "atom:author" Element
The "atom:author" element is a Person construct that indicates the
default author of the entry. atom:entry elements MUST contain
exactly one atom:author element, unless, in an Atom Feed Document,
the atom:head element contains an atom:author element itself.
atom:entry elements MUST NOT contain more than one atom:author
element.
5.5 "atom:contributor" Element
The "atom:contributor" element is a Person construct that indicates a
person or other entity who contributes to the entry. atom:entry
elements MAY contain one or more atom:contributor elements.
5.6 "atom:id" Element
The "atom:id" element is an Identity construct that conveys a
permanent, universally unique identifier for an entry. atom:entry
elements MUST contain exactly one atom:id element.
5.7 "atom:updated" Element
The "atom:updated" element is a Date construct indicating the most
recent instant in time when a change to the entry was made that the
publisher wishes to bring to the attention of subscribers. For
example, such changes might not include minor adjustments like
spelling and grammatical corrections.
atom:entry elements MUST contain exactly one atom:updated element.
Publishers MAY change the value of this element over time.
Processors MAY present entries sorted using this value. Processors
MAY choose not to present entries until the instant in time specified
in the atom:updated element has passed.
5.8 "atom:published" Element
The "atom:published" element is a Date construct indicating an
instant in time associated with an event early in the life cycle of
the entry. Typically, atom:published will be associated with the
initial creation or first availability of the resource.
atom:entry elements MAY contain an atom:published element, but MUST
NOT contain more than one.
Nottingham & Sayre Expires April 20, 2005 [Page 18]
Internet-Draft Atom Format October 2004
Processors MAY present entries sorted using this value. Processors
MAY choose not to present entries until the instant in time specified
in the atom:published element has passed.
5.9 "atom:summary" Element
The "atom:summary" element is a Text construct that conveys a short
summary, abstract or excerpt of the entry. atom:entry elements MAY
contain an atom:summary element, but MUST NOT contain more than one.
atom:entry elements MUST contain an atom:summary element in any of
the following cases:
o the atom:entry element contains no atom:content element.
o the atom:entry contains an atom:content which has a "src"
attribute (and is thus empty).
o the atom:entry contains content which is encoded in Base64; i.e.
the "type" attribute of atom:content is a MIME media type
[RFC2045] and does not begin with "text/" nor end with "+xml".
5.10 "atom:content" Element
The "atom:content" element either contains or links to the content of
the entry. atom:entry elements MUST contain zero or one atom:content
elements.
5.10.1 "type" attribute
atom:content MAY have a "type" attribute, When present, the value MAY
be one of "TEXT", "HTML", or "XHTML". Failing that, it MUST be a
MIME media type [RFC2045] in which, to use the terminology of Section
5 of [RFC2045], the top level is a discrete type. If the type
attribute is not provided, software MUST behave as though it were
present with a value of "TEXT".
5.10.2 "src" attribute
atom:content MAY have a "src" attribute, whose value MUST be a URI.
If the "src" attribute is present, software MAY use the URI to
retrieve the content. If the "src" attribute is present,
atom:content MUST be empty. That is to say, the content may be
retrievable using "src=" URI, or it may be contained within
atom:content, but not both.
If the "src" attribute is present, the "type" attribute MUST be
provided and MUST be a MIME media type [RFC2045], rather than "TEXT",
"HTML", or "XHTML". The value is advisory; that is to say, upon
dereferencing the URI to retrieve the content, if the server
Nottingham & Sayre Expires April 20, 2005 [Page 19]
Internet-Draft Atom Format October 2004
providing that content also provides a media type, the
server-provided media type is authoritative.
If the value of type begins with "text/" or ends with "+xml", the
content SHOULD be local; that is to say, no "src" attribute should be
provided.
5.10.3 Processing Model
Software MUST apply the following rules in succession in the order
below to ascertain the rules governing the content of "atom:content".
1. If the value is "TEXT", the content of atom:content MUST NOT
contain child elements. Such text is intended to be presented to
humans in a readable fashion. Thus, software MAY display it
using normal text rendering techniques such as proportional
fonts, white-space collapsing, and justification.
2. If the value of "type" is "HTML", the content of atom:content
MUST NOT contain child elements, and SHOULD be suitable for
handling by software that knows HTML. The HTML markup must be
encoded; for example, "
" as "<br>". The HTML markup
SHOULD be such that it could validly appear directly within an
HTML
element. Receiving software which displays the
content SHOULD use the markup to aid in displaying it.
3. If the value of "type" is "XHTML", the content of atom:content
MAY contain child elements. The content SHOULD be XHTML text and
markup that could validly appear directly within an xhtml:div
element. Receiving software which displays the content SHOULD
use the markup to aid in displaying it.
4. If the value of "type" ends with "+xml" or "/xml", the content of
atom:content may include child elements, and SHOULD be suitable
for handling by software that knows the indicated media type. If
the "src" attribute is not provided, this would normally mean
that the "atom:content" element would contain a single child
element which would serve as the root element of the XML document
of the indicated type.
5. If the value of "type" begins with "text/" the content of
atom:content MUST NOT contain child elements.
6. For all other values of "type", the content of atom:content MUST
be a valid Base64 encoding [RFC3548], which when decoded SHOULD
be suitable for handling by software that knows the indicated
media type. In this case, the characters in the Base64 encoding
may be preceded and followed in the atom:content element by
whitespace, and lines are separated by a single newline (U+000A)
character, as required by XML.
Nottingham & Sayre Expires April 20, 2005 [Page 20]
Internet-Draft Atom Format October 2004
5.11 "atom:copyright" Element
The "atom:copyright" element is a Text construct that conveys a
human-readable copyright statement for the entry. atom:entry
elements MAY contain an atom:copyright element, but MUST NOT contain
more than one.
The atom:copyright element SHOULD NOT be used to convey
machine-readable licensing information.
If an atom:entry element does not contain an atom:copyright element,
then the atom:copyright element of the containing atom:feed element's
atom:head element, if present, should be considered to apply to the
entry.
5.12 "atom:origin" Element
The "atom:origin" element's content conveys the original source of
the entry; e.g., the feed where the entry was first published.
If the source is an Atom Feed Document, then the content of
atom:origin MUST be the same, character-for-character, as that of the
atom:id element in that document's atom:head section (i.e., the XPath
expression "/atom:feed/atom:head/atom:id").
The content of this element MUST be a URI. atom:entry elements MAY
contain an atom:origin element, but MUST NOT contain more than one.
Nottingham & Sayre Expires April 20, 2005 [Page 21]
Internet-Draft Atom Format October 2004
6. Managing Feed State
[[ talk about what it means to keep a view of a feed ]]
Nottingham & Sayre Expires April 20, 2005 [Page 22]
Internet-Draft Atom Format October 2004
7. Securing Atom Documents
Because Atom is an XML-based format, existing XML security mechanisms
can be used to secure its content.
Note that while these mechanisms are available to secure Atom
documents, they should not be used indiscriminately.
7.1 Digital Signatures
The document element of an Atom document (i.e., atom:feed in an Atom
Feed Document, atom:entry in an Atom Entry Document) MAY have an
Enveloped Signature, as described by XML-Signature and Syntax
Processing [W3C.REC-xmldsig-core-20020212]. Other XML signature
mechanisms MUST NOT be used on the document element of an Atom
document.
Processors MUST NOT reject an Atom document containing such a
signature because they are not capable of verifying it; they MUST
continue processing and MAY inform the user of their failure to
validate the signature.
In other words, the presence of an element with the namespace URI
"http://www.w3.org/2000/09/xmldsig#" and a local name of "Signature"
as a child of the document element must not cause a processor to fail
merely because of its presence.
Other elements in an Atom document MUST NOT be signed unless their
definitions explicitly specify such a capability.
7.2 Encryption
The document element of an Atom document (i.e., atom:feed in an Atom
Feed Document, atom:entry in an Atom Entry Document) MAY be
encrypted, using the mechanisms described by XML Encryption Syntax
and Processing [W3C.REC-xmlenc-core-20021210]. Other XML encryption
mechanisms MUST NOT be used on the document element of an Atom
document.
Nottingham & Sayre Expires April 20, 2005 [Page 23]
Internet-Draft Atom Format October 2004
8. Embedding Atom in Other Formats
[[ ... ]]
Nottingham & Sayre Expires April 20, 2005 [Page 24]
Internet-Draft Atom Format October 2004
9. Extending Atom
[[ ... ]]
Nottingham & Sayre Expires April 20, 2005 [Page 25]
Internet-Draft Atom Format October 2004
10. IANA Considerations
An Atom Document, when serialized as XML 1.0, can be identified with
the following media type:
MIME media type name: application
MIME subtype name: atom+xml
Mandatory parameters: None.
Optional parameters:
"charset": This parameter has identical semantics to the charset
parameter of the "application/xml" media type as specified in
RFC 3023 [RFC3023]. [RFC3023].
Encoding considerations: Identical to those of "application/xml" as
described in RFC 3023 [RFC3023], section 3.2.
Security considerations: As defined in this specification. [[update
upon publication]]
In addition, as this media type uses the "+xml" convention, it
shares the same security considerations as described in RFC 3023
[RFC3023], section 10.
Interoperability considerations: There are no known interoperability
issues.
Published specification: This specification. [[update upon
publication]]
Applications which use this media type: No known applications
currently use this media type.
Additional information:
Magic number(s): As specified for "application/xml" in RFC 3023
[RFC3023], section 3.2.
File extension: .atom
Fragment identifiers: As specified for "application/xml" in RFC 3023
[RFC3023], section 5.
Base URI: As specified in RFC 3023 [RFC3023], section 6.
Macintosh File Type code: TEXT
Person and email address to contact for further information: Mark
Nottingham
Intended usage: COMMON
Author/Change controller: This specification's author(s). [[update
upon publication]]
Nottingham & Sayre Expires April 20, 2005 [Page 26]
Internet-Draft Atom Format October 2004
11. Security Considerations
Atom document can be encrypted and signed using
[W3C.REC-xmlenc-core-20021210] and [W3C.REC-xmldsig-core-20020212],
respectively, and is subject to the security considerations implied
by their use.
12 Normative References
[Atom-autodiscovery]
Pilgrim, M., "Atom Feed Autodiscovery", work-in-progress,
August 2004.
[Atom-protocol]
Gregorio, J. and R. Sayre, "The Atom Publishing Protocol",
work-in-progress, July 2004.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396,
August 1998.
[RFC2822] Resnick, P., "Internet Message Format", RFC 2822, April
2001.
[RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media
Types", RFC 3023, January 2001.
[RFC3066] Alvestrand, H., "Tags for the Identification of
Languages", BCP 47, RFC 3066, January 2001.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, July 2002.
[RFC3548] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 3548, July 2003.
[W3C.NOTE-datetime-19980827]
Wolf, M. and C. Wicksteed, "Date and Time Formats", W3C
NOTE NOTE-datetime-19980827, August 1998.
[W3C.REC-xml-20040204]
Nottingham & Sayre Expires April 20, 2005 [Page 27]
Internet-Draft Atom Format October 2004
Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T. and
E. Maler, "Extensible Markup Language (XML) 1.0 (Third
Edition)", W3C REC REC-xml-20040204, February 2004.
[W3C.REC-xml-infoset-20011024]
Tobin, R. and J. Cowan, "XML Information Set", W3C
FirstEdition REC-xml-infoset-20011024, October 2001.
[W3C.REC-xml-names-19990114]
Hollander, D., Bray, T. and A. Layman, "Namespaces in
XML", W3C REC REC-xml-names-19990114, January 1999.
[W3C.REC-xmlbase-20010627]
Marsh, J., "XML Base", W3C REC REC-xmlbase-20010627, June
2001.
[W3C.REC-xmldsig-core-20020212]
Solo, D., Reagle, J. and D. Eastlake, "XML-Signature
Syntax and Processing", W3C REC REC-xmldsig-core-20020212,
February 2002.
[W3C.REC-xmlenc-core-20021210]
Reagle, J. and D. Eastlake, "XML Encryption Syntax and
Processing", W3C REC REC-xmlenc-core-20021210, December
2002.
[1]
[2]
Authors' Addresses
Mark Nottingham (editor)
EMail: mnot@pobox.com
URI: http://www.mnot.net/
Robert Sayre (editor)
Boswijck Memex Consulting
EMail: rfsayre@boswijck.com
URI: http://boswijck.com
Nottingham & Sayre Expires April 20, 2005 [Page 28]
Internet-Draft Atom Format October 2004
Appendix A. Contributors
The following people contributed to preliminary drafts of this
document: Tim Bray, Mark Pilgrim, and Sam Ruby. The content and
concepts within are a product of the Atom community and the Atom
Publishing Format and Protocol Working Group.
Nottingham & Sayre Expires April 20, 2005 [Page 29]
Internet-Draft Atom Format October 2004
Appendix B. Revision History
[[ this section should be removed before final publication. ]]
-03: Move definition of Link @rel to format spec, restrict
acceptable values (PaceMoveLinkElement, PaceLinkAttrDefaults).
Add Service Construct, head/post, head/introspection, entry/edit
(PaceServiceElement).
Add Text Construct, entry/content (PaceReformedContent3).
Add entry/published (PaceDatePublished).
Adjust definition of Identity Construct per chairs' direction to
"fix it."
Add Sayre to editors.
-02: Removed entry/modified, entry/issued, entry/created; added
entry/updated (PaceDateUpdated).
Changed date construct from W3C date-time to RFC3339
(PaceDateUpdated).
Feed links to HTML pages should be reflected back
(PaceLinkReflection).
Added Identity construct (PaceIdConstruct).
Changed feed/id and entry/id to be Identity constructs
(PaceIdConstruct).
Changed entry/origin's content so that it's the same as the feed's
id, rather than its link/@rel="alternate" (PaceIdConstruct).
Added "Securing Atom Documents" (PaceDigitalSignatures).
-01: Constrained omission of "Information Item" to just elements and
attributes.
Clarified xml:lang inheritence.
Removed entry- and feed-specific langauge about xml:lang (covered
by general discussion of xml:lang)
Changed xml:lang to reference XML for normative requirements.
Changed "... MUST be a string" to "... is unstructued text."
Remomved langauge about DOCTYPEs, PIs, Comments, Entities.
Changed atom:url to atom:uri, @url to @uri
Introduced atom:head
Introduced "Atom Feed Document" and "Atom Entry Document".
Removed requirement for all elements and attributes to be
namespace-qualified; now children of selective elements
Added extensibility to Person constructs.
Removed requirement for media types to be registered
(non-registered media types are legal)
Added atom:origin (PaceEntryOrigin)
Added requirement for entry/id to be present and a URI
(PaceEntryIdRequired).
Clarified approach to Comments, PIs and well-formedness, as per
RFC3470.
Nottingham & Sayre Expires April 20, 2005 [Page 30]
Internet-Draft Atom Format October 2004
Referenced escaping algorithm in XML.
Assorted editorial nits and cleanup, refactoring
-00: Initial IETF Internet-Draft submission.
Added optional version attribute to entry
(PaceEntryElementNeedsVersionAttribute).
Added hreflang attribute (PaceHrefLang).
Clarified inheritence of copyright element (PaceItemCopyright).
Added xml:lang to entries (PaceItemLang).
Tweaked Infoset-related language (PaceNoInfoSet).
Clarified lack of structure in version attribute
(PaceVersionAsText).
Changed approach to XML Base (PaceXmlBaseEverywhere).
Added XML Base processing to atom:id (PaceXmlBaseId).
Various editorial cleanup and adjustments for IETF publication.
Nottingham & Sayre Expires April 20, 2005 [Page 31]
Internet-Draft Atom Format October 2004
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Nottingham & Sayre Expires April 20, 2005 [Page 32]