<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="no"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc subcompact="no"?>
<?rfc-ext allow-markup-in-artwork="yes" ?>

<rfc xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:ed="http://greenbytes.de/2002/rfcedit" obsoletes="2731" ipr="trust200902" docName="draft-reschke-rfc2731bis-03" category="info" xml:lang="en">
	<front>
  <title abbrev="RFC 2731 is Obsolete">RFC 2731<ed:replace ed:resolves="title" datetime="2009-10-04"><ed:ins> ("Encoding Dublin Core Metadata in HTML")</ed:ins></ed:replace> is Obsolete</title>

  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke">
    <organization abbrev="greenbytes">greenbytes GmbH</organization>
    <address>
      <postal>
        <street>Hafenweg 16</street>
        <city>Muenster</city><region>NW</region><code>48155</code>
        <country>Germany</country>
      </postal>
      <email>julian.reschke@greenbytes.de</email>	
      <uri>http://greenbytes.de/tech/webdav/</uri>	
    </address>
  </author>
  <author initials="J. A." surname="Kunze" fullname="John A. Kunze">
    <organization>University of California</organization>
    <address>
      <postal>
        <street>Office of the President</street>
        <street>415 20th Street, #406</street>
        <city>Oakland</city><region>CA</region><code>94612-3550</code>
        <country>U.S.A.</country>
      </postal>
      <email>jak@ucop.edu</email>	
    </address>
  </author>

  <date month="October" year="2009" day="8"/>
  
  <abstract>
    <t>
      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.
    </t>
  </abstract>
  
  <note title="Editorial Note (To be removed by RFC Editor before publication)">
    <t>
      Distribution of this document is unlimited.
    </t>
    <t>
      Please send feedback to either the DC-Architecture mailing list
      (<eref target="http://www.jiscmail.ac.uk/lists/dc-architecture.html"/>) or the IETF Apps Area
      mailing list (<eref target="https://www.ietf.org/mailman/listinfo/apps-discuss"/>).
    </t>
    <t>
      XML versions and latest edits for this document
      are available from <eref target="http://greenbytes.de/tech/webdav/#draft-reschke-rfc2731bis"/>.
    </t>
  </note>

  </front>

  <middle>

<ed:issue name="edit" type="edit" status="closed">
  <ed:item entered-by="julian.reschke@greenbytes.de" date="2009-09-09">
    Umbrella issue for editorial fixes/enhancements.
  </ed:item>
</ed:issue>

<ed:issue name="title" type="edit" status="closed">
  <ed:item entered-by="ietfdbh@comcast.net" date="2009-09-09">
    Include the title of RFC 2731 into this document's title.
  </ed:item>
  <ed:resolution datetime="2009-10-04">
    Done.
  </ed:resolution>
</ed:issue>

<section title="Introduction" anchor="introduction">
<t>
  <xref target="RFC2731"/> defines "Encoding Dublin Core Metadata in HTML". Newer
  specifications published by the <eref target="http://dublincore.org/">Dublin Core Metadata Initiative</eref>
  (DCMI)<ed:replace ed:resolves="edit" datetime="2009-10-04"><ed:ins> over the last decade</ed:ins></ed:replace>, in particular "Expressing Dublin Core metadata using HTML/XHTML meta and link elements" (DC-HTML,
  <eref target="http://dublincore.org/documents/dc-html/"/>), have obsoleted this work.
</t>
<x:note>
  <t>
    <x:h>Note:</x:h> Implementers of RFC 2731 should note that DC-HTML introduces
    a new requirement with respect to the use of the "head" element's "profile"
    attribute.
  </t>
</x:note>
</section>  

<section title="Recommendation to Reclassify RFC 2731">
<ed:issue name="historic" type="change" status="open">
  <ed:item entered-by="julian.reschke@greenbytes.de" date="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.
  </ed:item>
</ed:issue>
<t>
  This document recommends that the IESG reclassify <xref target="RFC2731"/> as Historic.
</t>
</section>

<section title="Security Considerations" anchor="security">
<ed:issue name="sec" type="edit" status="closed">
  <ed:item entered-by="sm@resistor.net" date="2009-09-10" href="http://www.ietf.org/mail-archive/web/ietf/current/msg58359.html">
    LC feedback: explain why there are no Security Considerations.
  </ed:item>
  <ed:resolution>
    Done.
  </ed:resolution>
</ed:issue>
<t><ed:replace ed:resolves="sec" datetime="2009-09-10"><ed:del>
  There are no security considerations related to this document.</ed:del><ed:ins>
  This document is of adminstrative nature only and therefore there are no security relations related to it.</ed:ins></ed:replace>
</t>
</section>  

<section title="IANA Considerations" anchor="iana">
<t>
  There are no IANA considerations related to this document.
</t>
</section>  


  </middle>
  <back>
  
<references title="Informative References">
  
<reference anchor="RFC2731">
  <front>
    <title>Encoding Dublin Core Metadata in HTML</title>
    <author initials="J. A." surname="Kunze" fullname="John A. Kunze">
      <organization>University of California, San Francisco,  Center for Knowledge Management</organization>
      <address>
        <postal>
          <street>530 Parnassus Ave</street>
          <street>Box 0840</street>
          <city>San Francisco</city>
          <region>CA</region>
          <code>94143-0840</code>
          <country>US</country>
        </postal>
        <facsimile>+1 415 476 4653</facsimile>
        <email>jak@ckm.ucsf.edu</email>
      </address>
    </author>
    <date month="December" year="1999"/>
  </front>
  <seriesInfo name="RFC" value="2731"/>
</reference>

</references>

<section title="Related Discussion on DC-ARCHITECTURE Mailing list (to be removed by RFC Editor before publication)" anchor="discussion">
<t>
  This proposal has been discussed and approved on the DC-ARCHITECTURE mailing list 
  (<eref target="DC-ARCHITECTURE@JISCMAIL.AC.UK"/>, <eref target="https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=DC-ARCHITECTURE;XwVOng;20090818152516%2B0200"/>).
</t>
</section>

<ed:replace ed:resolves="edit" datetime="2009-10-08"><ed:ins>
<section title="Change Log (to be removed by RFC Editor before publication)">
<section title="Since draft-reschke-rfc2732bis-02">
<t>
  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 "<ed:issueref>historic</ed:issueref>", which is waiting for community
  feedback.
</t>
</section>
</section></ed:ins></ed:replace>

  </back>

</rfc>