From: http://www.ietf.org/internet-drafts/draft-snell-atompub-transitional-atom-00.txt Title: Transitional Atom Format Reference: IETF Working Group, Internet-Draft 'draft-snell-atompub-transitional-atom-00.txt' Date: December 6, 2005 See: "Atom Publishing Format and Protocol" http://xml.coverpages.org/atom.html Other Atom specifications: The Atom Syndication Format http://xml.coverpages.org/draft-ietf-atompub-format-11.txt http://xml.coverpages.org/Atom-RFC4287.txt The Atom Publishing Protocol http://xml.coverpages.org/draft-ietf-atompub-protocol-06.txt Atom Feed Autodiscovery http://xml.coverpages.org/draft-ietf-atompub-autodiscovery-01.txt ------- Feed History: Enabling Incremental Syndication http://xml.coverpages.org/draft-nottingham-atompub-feed-history-04.txt Atom Entry Expiration: Specifying Expiration Timestamps for Atom Entry Metadata http://xml.coverpages.org/draft-snell-atompub-feed-expires-06.txt Feed Rank [Feed Index: Enabling Ordered Entries in Atom] http://xml.coverpages.org/draft-snell-atompub-feed-index-04.txt Feed License Link Relation http://xml.coverpages.org/draft-snell-atompub-feed-license-04.txt Feed Thread: Enabling Threaded Entries in Atom http://xml.coverpages.org/draft-snell-atompub-feed-thread-03.txt The Atom Notification Protocol http://xml.coverpages.org/draft-snell-atompub-notification-01.txt XHTML Microformats for the Atom Publishing Protocol http://xml.coverpages.org/draft-sayre-atompub-xhtml-micro-00.txt Transporting Atom Notifications over the Extensible Messaging and Presence Protocol (XMPP) http://xml.coverpages.org/draft-saintandre-atompub-notify-04.txt Atom Link No Follow http://xml.coverpages.org/draft-snell-atompub-feed-nofollow-04.txt APP Service Description Format http://xml.coverpages.org/draft-sayre-atompub-protocol-outline-01.txt The Atom Publishing Protocol (Basic). http://xml.coverpages.org/draft-sayre-atompub-protocol-basic-05.txt Atom Publishing Protocol - Introspection http://xml.coverpages.org/draft-snell-atompub-app-introspection-00.txt Atom Syndication Format Link Extensions http://xml.coverpages.org/draft-snell-atompub-link-extensions-01.txt Transitional Atom Format http://xml.coverpages.org/draft-snell-atompub-transitional-atom-00.txt Atom Syndication Format Tombstones http://xml.coverpages.org/draft-snell-atompub-tombstones-00.txt Atom mailing list: http://www.imc.org/atom-syntax/index.html Atom Wiki Web site: http://www.intertwingly.net/wiki/pie/FrontPage IETF Atom Publishing Format and Protocol (atompub) WG: http://www.ietf.org/html.charters/atompub-charter.html ======================================================================== Network Working Group J. Snell Internet-Draft December 6, 2005 Expires: June 9, 2006 Transitional Atom Format draft-snell-atompub-transitional-atom-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on June 9, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This specification defines a transitional form of the Atom 1.0 Entry Document that may be used during the production lifecycle of Atom 1.0 Entry Documents. Snell Expires June 9, 2006 [Page 1] Internet-Draft Transitional Atom December 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 3. Transitional Atom Entry Documents . . . . . . . . . . . . . . . 3 4. The 't:entry' Element . . . . . . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . . . 7 Snell Expires June 9, 2006 [Page 2] Internet-Draft Transitional Atom December 2005 1. Introduction This specification defines a transitional form of Atom Entry Document [RFC4287] that may be used during the production lifecycle of an Atom Entry. 2. Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, [RFC2119]. This specification uses XML Namespaces [W3C.REC-xml-names-19990114] to uniquely identify XML element names. "atom": "http://www.w3.org/2005/Atom" "t" : "http://www.w3.org/2005/Atom-transitional" This specification uses terms from the XML Infoset [W3C.REC-xml- infoset-20040204]. However, this specification uses a shorthand; the phrase "Information Item" is omitted when naming Element Information Items. Therefore, when this specification uses the term "element," it is referring to an Element Information Item in Infoset terms. 3. Transitional Atom Entry Documents The Transitional Atom Entry Document is a well-formed XML document derived from the Atom Entry Document defined by the Atom Syndication Format [RFC4287]. It's root is the t:entry element. namespace tatom = "http://www.w3.org/2005/Atom-transitional" start = tatomEntry Transitional Atom allows the use of IRI's [RFC3987], xml:base and xml:lang in the same fashion described in Section 2 of the Atom Syndication Format specification. Transitional Atom is an extensible format adhering to the same mechanisms described in Section 6 of the Atom Syndication Format. 4. The 't:entry' Element The "t:entry" element represents an individual Transitional Atom Entry. Snell Expires June 9, 2006 [Page 3] Internet-Draft Transitional Atom December 2005 transitional-entry = element t:entry { atomCommonAttributes, (atomAuthor* & atomCategory* & atomContent? & atomContributor* & atomId? & atomLink* & atomPublished? & atomRights? & atomSummary? & atomTitle? & atomUpdated? & extensionElement* ) } This specification assigns no significance to the order of the child elements of t:entry. The children of the 't:atom' element are defined by [RFC4287]. o t:entry elements MAY contain one or more atom:author elements. o t:entry elements MAY contain any number of atom:category elements. o t:entry elements MUST NOT contain more than one atom:content element. o t:entry elements MAY contain any number of atom:contributor elements. o t:entry elements MAY contain exactly one atom:id element. o t:entry elements that contain no child atom:content element SHOULD contain at least one atom:link element with a rel attribute value of "alternate". o t:entry elements MUST NOT contain more than one atom:link element with a rel attribute value of "alternate" that has the same combination of type and hreflang attribute values. o t:entry elements MAY contain additional atom:link elements beyond those described above. o t:entry elements MUST NOT contain more than one atom:published element. o t:entry elements MUST NOT contain more than one atom:rights element. o t:entry elements MUST NOT contain more than one atom:source element. o t:entry elements SHOULD contain an atom:summary element in either of the following cases: Snell Expires June 9, 2006 [Page 4] Internet-Draft Transitional Atom December 2005 * the t:entry contains an atom:content that has a "src" attribute (and is thus empty). * the t:entry contains content that is encoded in Base64; i.e. the "type" attribute of atom:content is a MIME media type [RFC4288], but is not an XML media type [RFC3023], does not begin with "text/", and does not end with "/xml" or "+xml". o t:entry elements MUST NOT contain more than one atom:summary element. o t:entry elements MAY contain exactly one atom:title element. o t:entry elements MAY contain exactly one atom:updated element. 5. Security Considerations There are no security considerations introduced by this specification. 6. IANA Considerations There are no IANA considerations introduced by this specification. 7. References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001. [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005. [RFC4287] Nottingham, M. and R. Sayre, "The Atom Syndication Format", RFC 4287, December 2005. [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005. [W3C.REC-xml-infoset-20040204] Tobin, R. and J. Cowan, "XML Information Set (Second Edition)", W3C REC REC-xml-infoset-20040204, February 2004. [W3C.REC-xml-names-19990114] Hollander, D., Bray, T., and A. Layman, "Namespaces in XML", W3C REC REC-xml-names-19990114, January 1999. Snell Expires June 9, 2006 [Page 5] Internet-Draft Transitional Atom December 2005 Author's Address James M Snell Phone: Email: jasnell@gmail.com URI: http://snellspace.com Snell Expires June 9, 2006 [Page 6] Internet-Draft Transitional Atom December 2005 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 (2005). 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. Snell Expires June 9, 2006 [Page 7]