| Network Working Group | J. Reschke |
| Internet-Draft | greenbytes |
| Obsoletes: 2731 (if approved) | J. Kunze |
| Intended status: Informational | University of California |
| Expires: April 11, 2010 | October 8, 2009 |
This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and 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 April 11, 2010.¶
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.¶
This document recommends that RFC 2731, on Encoding Dublin Core Metadata in HTML, be reclassified as Historic, as further development of this specification has moved to the Dublin Core Metadata Initiative.¶
Distribution of this document is unlimited.¶
Please send feedback to either the DC-Architecture mailing list (<http://www.jiscmail.ac.uk/lists/dc-architecture.html>) or the IETF Apps Area mailing list (<https://www.ietf.org/mailman/listinfo/apps-discuss>).¶
XML versions and latest edits for this document are available from <http://greenbytes.de/tech/webdav/#draft-reschke-rfc2731bis>.¶
| I edit (type: edit, status: closed) | ||
| julian.reschke@greenbytes.de | 2009-09-09 | Umbrella issue for editorial fixes/enhancements. |
| Associated changes in this document: 1, <#rfc.change.edit.2>. | ||
| I title (type: edit, status: closed) | ||
| ietfdbh@comcast.net | 2009-09-09 | Include the title of RFC 2731 into this document's title. |
| 2009-10-04 | Resolution: Done. | |
| Associated changes in this document: <#rfc.change.title.1>. | ||
[RFC2731] defines "Encoding Dublin Core Metadata in HTML". Newer specifications published by the Dublin Core Metadata Initiative (DCMI)↓over the last decade, in particular "Expressing Dublin Core metadata using HTML/XHTML meta and link elements" (DC-HTML, <http://dublincore.org/documents/dc-html/>), have obsoleted this work.¶
| I historic (type: change, status: open) | ||
| julian.reschke@greenbytes.de | 2009-10-08 | It's not clear whether this case is really a candidate for reclassification as "historic". After all, the format that was described in RFC 2731 is still in use in Dublin Core's DC-HTML; it just got revised. So simply stating that it is obsolete (which would be implied by publishing this document) should be enough. |
| I sec (type: edit, status: closed) | ||
| sm@resistor.net | 2009-09-10 | LC feedback: explain why there are no Security Considerations. |
| Resolution: Done. | ||
| Associated changes in this document: 3. | ||
There are no security considerations related to this document.This document is of adminstrative nature only and therefore there are no security relations related to it. ¶
There are no IANA considerations related to this document.¶
This proposal has been discussed and approved on the DC-ARCHITECTURE mailing list (<DC-ARCHITECTURE@JISCMAIL.AC.UK>, <https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=DC-ARCHITECTURE;XwVOng;20090818152516%2B0200>).¶
Added John Kunze as Co-Author. Expand Security Considerations to say why there aren't any. Include title of RFC 2731 into this document's title. Mention that Dublin Core has maintained its version of the spec for the last decade. Add open issue "historic", which is waiting for community feedback.