idnits 2.17.1 draft-nottingham-rss-media-type-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by 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 an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** 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 (October 23, 2001) is 8221 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) ** Obsolete normative reference: RFC 3023 (ref. '1') (Obsoleted by RFC 7303) -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Non-RFC (?) normative reference: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '6' -- Possible downref: Non-RFC (?) normative reference: ref. '7' Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Nottingham 3 Internet-Draft October 23, 2001 4 Expires: April 23, 2002 6 The application/rss+xml Media Type 7 draft-nottingham-rss-media-type-00 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on April 23, 2002. 32 Copyright Notice 34 Copyright (C) The Internet Society (2001). All Rights Reserved. 36 Abstract 38 This document specifies the Media Type for the RSS format. RSS 39 allows lists of information to be exchanged in an XML-based format. 41 1. Introduction 43 RSS is a lightweight, multipurpose, extensible metadata description 44 and syndication format. RSS is an XML application. 46 RSS is currently used for a number of applications, including news 47 and other headline syndication, weblog syndication, and the 48 propogation of software update lists. It is generally used for any 49 situation when a machine-readable list of textual items and/or 50 metadata about them needs to be distributed. 52 There are a number of revisions [2][3][4][5] of the RSS format 53 defined, many of which are actively used. This memo defines a media 54 type, application/rss+xml for all versions of RSS. 56 2. Registration Information 58 To: ietf-types@iana.org 60 Subject: Registration of MIME media type application/rss+xml 62 MIME media type name: application 64 MIME subtype name: rss+xml 66 Required parameters: none 68 Optional parameters: 70 charset 72 Same as charset parameter of application/xml as specified in 73 RFC3023 [1]. 75 revision 77 The optional revision parameter indicates the version of RSS used; 78 the value is specified by the target RSS version. In practice, 79 this value should be an XML Namespace [6], if defined (e.g., 80 'http://purl.org/rss/1.0/' for RSS 1.0), or a revision number if 81 not (e.g., "0.92" for RSS 0.92). 83 Encoding considerations: 85 Same as encoding considerations of application/xml as specified in 86 RFC3023 [1]. 88 Security considerations: 90 The security considerations outlined in RFC3023 [1] apply. 92 Published specification(s): 94 RSS 0.9 [2] 96 RSS 0.91 [3] 98 RSS 0.92 [4] 100 RSS 1.0 [5] 102 Applications which use this media type: 104 RSS editors, producers and aggregators. 106 2.1 Additional information: 108 Magic number(s): 110 There is no single initial byte sequence that is always present in 111 RSS files. See RFC3023 [1] for information about the 112 identification of XML media types. 114 File extension(s): .rss 116 Macintosh File Type Code(s): "TEXT" 118 Person & email address to contact for further information: 120 The author of this memo. 122 Intended usage: COMMON 124 Author/Change controller(s): 126 RSS 0.9 was a product of Netscape Communications, and was authored 127 by: 129 Dan Libby 131 RSS 0.91 was a product of Netscape Communications, and was authored 132 by: 134 Dan Libby 136 RSS 0.92 is a product of UserLand Software, and is authored by: 138 Dave Winer 140 RSS 1.0 is a product of an ad-hoc working group, rss-dev[7], and was 141 authored by: 143 Gabe Beged-Dov 145 Dan Brickley 147 Rael Dornfest 149 Ian Davis 151 Leigh Dodds 153 Jonathan Eisenzopf 155 R.V. Guha 157 Ken MacLeod 159 Eric Miller 161 Aaron Swartz 163 Eric van der Vlist 165 References 167 [1] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC 168 3023, January 2001. 170 [2] Libby, D., "RDF Site Summary (RSS) 0.9", May 2001, 171 . 173 [3] Libby, D., "RSS 0.91 Spec, revision 3", July 1999, 174 . 176 [4] Winer, D., "RSS 0.92", December 2000, 177 . 179 [5] Beged-Dov, G., Brickley, D., Dornfest, R., Davis, I., Dodds, L., 180 Eisenzopf, J., Guha, R., MacLeod, K., Miller, E., Swartz, A. and 181 E. van der Vlist, "RDF Site Summary (RSS) 1.0", May 2001, 182 . 184 [6] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", 185 January 1999, . 187 [7] 188 Author's Address 190 Mark Nottingham 191 Burlingame, CA 94010 192 US 194 EMail: mnot-rss@mnot.net 195 URI: http://www.mnot.net/ 197 Full Copyright Statement 199 Copyright (C) The Internet Society (2001). All Rights Reserved. 201 This document and translations of it may be copied and furnished to 202 others, and derivative works that comment on or otherwise explain it 203 or assist in its implementation may be prepared, copied, published 204 and distributed, in whole or in part, without restriction of any 205 kind, provided that the above copyright notice and this paragraph are 206 included on all such copies and derivative works. However, this 207 document itself may not be modified in any way, such as by removing 208 the copyright notice or references to the Internet Society or other 209 Internet organizations, except as needed for the purpose of 210 developing Internet standards in which case the procedures for 211 copyrights defined in the Internet Standards process must be 212 followed, or as required to translate it into languages other than 213 English. 215 The limited permissions granted above are perpetual and will not be 216 revoked by the Internet Society or its successors or assigns. 218 This document and the information contained herein is provided on an 219 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 220 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 221 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 222 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 223 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 225 Acknowledgement 227 Funding for the RFC Editor function is currently provided by the 228 Internet Society.