idnits 2.17.1 draft-reschke-rfc2731bis-03.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC2731, but the abstract doesn't seem to directly say this. It does mention RFC2731 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 8, 2009) is 5312 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2731 (Obsoleted by RFC 5791) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Reschke 3 Internet-Draft greenbytes 4 Obsoletes: 2731 (if approved) J. Kunze 5 Intended status: Informational University of California 6 Expires: April 11, 2010 October 8, 2009 8 RFC 2731 ("Encoding Dublin Core Metadata in HTML") is Obsolete 9 draft-reschke-rfc2731bis-03 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and 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 April 11, 2010. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents in effect on the date of 41 publication of this document (http://trustee.ietf.org/license-info). 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 This document recommends that RFC 2731, on Encoding Dublin Core 48 Metadata in HTML, be reclassified as Historic, as further development 49 of this specification has moved to the Dublin Core Metadata 50 Initiative. 52 Editorial Note (To be removed by RFC Editor before publication) 54 Distribution of this document is unlimited. 56 Please send feedback to either the DC-Architecture mailing list 57 () or the IETF 58 Apps Area mailing list 59 (). 61 XML versions and latest edits for this document are available from 62 . 64 1. Introduction 66 [RFC2731] defines "Encoding Dublin Core Metadata in HTML". Newer 67 specifications published by the Dublin Core Metadata Initiative [1] 68 (DCMI) over the last decade, in particular "Expressing Dublin Core 69 metadata using HTML/XHTML meta and link elements" (DC-HTML, 70 ), have obsoleted this 71 work. 73 Note: Implementers of RFC 2731 should note that DC-HTML introduces 74 a new requirement with respect to the use of the "head" element's 75 "profile" attribute. 77 2. Recommendation to Reclassify RFC 2731 79 This document recommends that the IESG reclassify [RFC2731] as 80 Historic. 82 3. Security Considerations 84 This document is of adminstrative nature only and therefore there are 85 no security relations related to it. 87 4. IANA Considerations 89 There are no IANA considerations related to this document. 91 5. Informative References 93 [RFC2731] Kunze, J., "Encoding Dublin Core Metadata in HTML", 94 RFC 2731, December 1999. 96 [1] 98 Appendix A. Related Discussion on DC-ARCHITECTURE Mailing list (to be 99 removed by RFC Editor before publication) 101 This proposal has been discussed and approved on the DC-ARCHITECTURE 102 mailing list (, ). 106 Appendix B. Change Log (to be removed by RFC Editor before publication) 108 B.1. Since draft-reschke-rfc2732bis-02 110 Added John Kunze as Co-Author. Expand Security Considerations to say 111 why there aren't any. Include title of RFC 2731 into this document's 112 title. Mention that Dublin Core has maintained its version of the 113 spec for the last decade. Add open issue "historic", which is 114 waiting for community feedback. 116 Appendix C. Resolved issues (to be removed by RFC Editor before 117 publication) 119 Issues that were either rejected or resolved in this version of this 120 document. 122 C.1. edit 124 Type: edit 126 julian.reschke@greenbytes.de (2009-09-09): Umbrella issue for 127 editorial fixes/enhancements. 129 C.2. title 131 Type: edit 133 ietfdbh@comcast.net (2009-09-09): Include the title of RFC 2731 into 134 this document's title. 136 Resolution (2009-10-04): Done. 138 C.3. sec 140 In Section 3: 142 Type: edit 144 sm@resistor.net (2009-09-10): LC feedback: explain why there are no 145 Security Considerations. 147 Resolution: Done. 149 Appendix D. Open issues (to be removed by RFC Editor prior to 150 publication) 152 D.1. historic 154 In Section 2: 156 Type: change 158 julian.reschke@greenbytes.de (2009-10-08): It's not clear whether 159 this case is really a candidate for reclassification as "historic". 160 After all, the format that was described in RFC 2731 is still in use 161 in Dublin Core's DC-HTML; it just got revised. So simply stating 162 that it is obsolete (which would be implied by publishing this 163 document) should be enough. 165 Authors' Addresses 167 Julian F. Reschke 168 greenbytes GmbH 169 Hafenweg 16 170 Muenster, NW 48155 171 Germany 173 Email: julian.reschke@greenbytes.de 174 URI: http://greenbytes.de/tech/webdav/ 175 John A. Kunze 176 University of California 177 Office of the President 178 415 20th Street, #406 179 Oakland, CA 94612-3550 180 U.S.A. 182 Email: jak@ucop.edu