idnits 2.17.1 draft-sneddon-atom-export-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 23, 2009) is 5451 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Sneddon 3 Internet-Draft May 23, 2009 4 Intended status: Experimental 5 Expires: November 24, 2009 7 Atom Export Format 8 draft-sneddon-atom-export-01 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on November 24, 2009. 33 Copyright Notice 35 Copyright (c) 2009 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents in effect on the date of 40 publication of this document (http://trustee.ietf.org/license-info). 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. 44 Abstract 46 This document specifies a method of using the Atom Syndication Format 47 as an export format. 49 1. Introduction 51 [[anchor2: This section is yet to be written.]] 53 2. Conformance Requirements 55 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 56 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 57 document are to be interpreted as described in [RFC2119]. 59 3. Atom Export Documents 61 An Atom Export Document is an Atom Feed Document [RFC4287]. 63 atom:entry elements are given purpose within the document by an atom: 64 category element whose the scheme attribute is equal to "XXX-to-be- 65 decided" and whose term attribute matches one of the below: 67 1. "post" signifies the entry represents a blog post. Furthermore, 68 an atom:category with scheme 69 "http://schemas.google.com/g/2005#kind" and term 70 "http://schemas.google.com/blogger/2008/kind#post" SHOULD be 71 treated as equivalent. 73 2. "comment" signifies the entry represents a reply to a post which 74 MUST be in the same Atom Export Document and which MUST be 75 specified by an thr:in-reply-to element [RFC4685] within the 76 entry. Furthermore, an atom:category with scheme 77 "http://schemas.google.com/g/2005#kind" and term 78 "http://schemas.google.com/blogger/2008/kind#comment" SHOULD be 79 treated as equivalent. 81 Such an atom:category element MUST be the first element child of the 82 atom:entry. If it is not, implementations MUST NOT incur any meaning 83 from it. 85 Any atom:entry which does not have such an atom:category element is 86 assigned absolutely no meaning by this specification. 88 4. Further Recommendations 90 This section is informative. 92 If an implementation wishes to store data beyond what is easily 93 representable within Atom for importing/exporting state, it is 94 recommended that a namespace is created to contain this extra 95 metadata, and it is not coerced in an over-engineered manner into 96 Atom. 98 5. Security Considerations 100 As Atom Export Documents are just Atom Feed Documents, please see the 101 "Security Considerations" section of [RFC4287]. 103 Furthermore, as they can contain extensions from [RFC4685], please 104 see that document too. 106 6. IANA Considerations 108 This document has no IANA considerations. 110 7. Normative References 112 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 113 Requirement Levels", BCP 14, RFC 2119, March 1997. 115 [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom 116 Syndication Format", RFC 4287, December 2005. 118 [RFC4685] Snell, J., "Atom Threading Extensions", RFC 4685, 119 September 2006. 121 Author's Address 123 Geoffrey Sneddon 125 Email: me@gsnedders.com 126 URI: http://gsnedders.com/