idnits 2.17.1 draft-snell-atompub-feed-nofollow-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 280. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 257. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 264. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 270. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 2005) is 6829 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-atompub-format' is defined on line 212, but no explicit reference was found in the text Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Snell 3 Internet-Draft August 2005 4 Expires: February 2, 2006 6 Atom Link No Follow 7 draft-snell-atompub-feed-nofollow-00.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on February 2, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 This memo presents a mechanism that allows feed publishers to express 41 preferences over how a consumer processes Atom links and Content-By- 42 Reference. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 48 3. The 'x:follow' extension attribute . . . . . . . . . . . . . . 4 49 4. The 'x:index' extension attribute . . . . . . . . . . . . . . 4 50 5. The 'x:archive' extension attribute . . . . . . . . . . . . . 5 51 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 52 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 53 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 54 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6 55 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 56 Intellectual Property and Copyright Statements . . . . . . . . 7 58 1. Introduction 60 This docoument specifies a mechanism by which feed publishers MAY 61 express how applications consuming Atom documents should handle links 62 and referenced content contained within the feed. For example, a 63 publisher may include an enclosure link within a feed but may not 64 wish for applications to automatically download the enclosed file 65 when it processes the feed; or, the publisher may not wish to allow 66 applications to archive or index the enclosure in any way. The 67 'follow', 'index' and 'archive' attributes introduced herein provide 68 the means for publishers to express these preferences. 69 noFollowAttributes = { 70 attribute follow { "yes" | "no" }?, 71 attribute index { "yes" | "no" }?, 72 attribute archive { "yes" | "no" }? 73 } 75 2. Notational Conventions 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in BCP 14, [RFC2119], as 80 scoped to those conformance targets. 82 In this specification, "entry" refers to an atom:entry element. 84 In this specification, "feed" refers to an Atom Feed Document. 86 In this specification, "head section" refers to the children of a 87 feed's document-wide metadata container; e.g., the child elements of 88 the atom:feed element in an Atom Feed Document. 90 In this specification, the term "extension attribute" refers to a 91 namespace qualified element attribute. 93 In this specification, the term "link" refers to an atom:link 94 element. 96 In this specificaiton, the term "referenced content" refers to an 97 atom:content element that contains a @src attribute. 99 This specification uses XML Namespaces [W3C.REC-xml-names-19990114] 100 to uniquely identify XML element and attribute names. It uses the 101 following namespace prefix for the indicated namespace URI; 102 "x": "http://purl.org/atompub/nofollow/1.0" 104 This specification uses terms from the XML Infoset [W3C.REC-xml- 105 infoset-20040204]. However, this specification uses a shorthand; the 106 phrase "Information Item" is omitted when naming Element Information 107 Items. Therefore, when this specification uses the term "element," 108 it is referring to an Element Information Item in Infoset terms. 110 3. The 'x:follow' extension attribute 112 The 'x:follow" attribute indicates whether applications should 113 automatically attempt to follow links and referenced content (e.g., 114 whether or not enclosure links should be automatically downloaded, 115 etc). The value of the attribute is either "yes" or "no". If 116 missing, the value is considered to be "yes". A value of "no" 117 indicates that applications SHOULD NOT attempt to automatically 118 resolve the referenced resource -- rather, the application should 119 wait until a user explicitly requests the resource to be resolved. 121 For example, 122 124 ... 125 ... 126 129 ... 130 132 The 'x:follow' attribute MAY be contained by atom:link elements and 133 atom:content elements that contain a 'src' attribute. 135 4. The 'x:index' extension attribute 137 The 'x:index' attribute indicates whether applications should index 138 links and referenced content. The value of the attribute is either 139 "yes" or "no". If missing, the value is considered to be "yes". A 140 value of "no" indicates that applications SHOULD NOT index the 141 referenced resource. 142 144 ... 145 ... 146 149 ... 150 152 The 'x:index' attribute MAY also be included as a child of atom:feed 153 and atom:entry elements -- in which case it is used to indicate 154 whether or not applications should index the information content of 155 the containing atom:feed or atom:entry. 156 159 ... 160 ... 161 ... 162 164 The 'x:index' attribute MAY be contained by atom:entry, atom:feed, 165 atom:link elements and atom:content elements that contain a 'src' 166 attribute. 168 5. The 'x:archive' extension attribute 170 The 'x:archive' attribute indicates whether applications should 171 archive the targets of links and content references. The value of 172 the attribute is either "yes" or "no". If missing, the value is 173 considered to be "yes". A value of "no" indicate that applications 174 SHOULD NOT archive the referenced resource. 175 177 ... 178 ... 179 182 ... 183 185 The 'x:archive' attribute MAY also be included as a child of atom: 186 feed and atom:entry elements -- in which case it is used to indicate 187 whether or not applications should archive the information content of 188 the containing atom:feed or atom:entry. 189 192 ... 193 ... 194 ... 195 197 The 'x:archive' attribute MAY be contained by atom:entry, atom:feed, 198 atom:link elements and atom:content elements that contain a 'src' 199 attribute. 201 6. Security Considerations 203 There are no security considerations introduced by this 204 specification. 206 7. IANA Considerations 208 There are no IANA considerations introduced by this specification. 210 8. References 212 [I-D.ietf-atompub-format] 213 Sayre, R. and M. Nottingham, "The Atom Syndication 214 Format", draft-ietf-atompub-format-11 (work in progress), 215 August 2005. 217 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 218 Requirement Levels", BCP 14, RFC 2119, March 1997. 220 [W3C.REC-xml-infoset-20040204] 221 Tobin, R. and J. Cowan, "XML Information Set (Second 222 Edition)", W3C REC REC-xml-infoset-20040204, 223 February 2004. 225 [W3C.REC-xml-names-19990114] 226 Hollander, D., Bray, T., and A. Layman, "Namespaces in 227 XML", W3C REC REC-xml-names-19990114, January 1999. 229 [W3C.REC-xmlschema-2-20041028] 230 Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes 231 Second Edition", W3C REC REC-xmlschema-2-20041028, 232 October 2004. 234 Author's Address 236 James M Snell 238 Phone: 239 Email: jasnell@gmail.com 240 URI: http://snellspace.com 242 Appendix A. Acknowledgements 244 The author gratefully acknowledges the feedback from the members of 245 the Atom Publishing Format and Protocol working group during the 246 development of this specification. 248 Intellectual Property Statement 250 The IETF takes no position regarding the validity or scope of any 251 Intellectual Property Rights or other rights that might be claimed to 252 pertain to the implementation or use of the technology described in 253 this document or the extent to which any license under such rights 254 might or might not be available; nor does it represent that it has 255 made any independent effort to identify any such rights. Information 256 on the procedures with respect to rights in RFC documents can be 257 found in BCP 78 and BCP 79. 259 Copies of IPR disclosures made to the IETF Secretariat and any 260 assurances of licenses to be made available, or the result of an 261 attempt made to obtain a general license or permission for the use of 262 such proprietary rights by implementers or users of this 263 specification can be obtained from the IETF on-line IPR repository at 264 http://www.ietf.org/ipr. 266 The IETF invites any interested party to bring to its attention any 267 copyrights, patents or patent applications, or other proprietary 268 rights that may cover technology that may be required to implement 269 this standard. Please address the information to the IETF at 270 ietf-ipr@ietf.org. 272 Disclaimer of Validity 274 This document and the information contained herein are provided on an 275 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 276 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 277 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 278 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 279 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 280 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 282 Copyright Statement 284 Copyright (C) The Internet Society (2005). This document is subject 285 to the rights, licenses and restrictions contained in BCP 78, and 286 except as set forth therein, the authors retain all their rights. 288 Acknowledgment 290 Funding for the RFC Editor function is currently provided by the 291 Internet Society.