<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff background="">
<DIV><FONT face=Arial size=2>The following media types are proposed for
registration on the standards tree:
<BR> <BR>application/mods+xml<BR>application/mads+xml<BR>application/mets+xml<BR>application/marcxml+xml<BR>application/sru+xml<BR> <BR>These
are proposed by the Library of Congress on behalf of several constituencies
including the library/bibliographic and metadata communities.<BR> <BR>These
all correspond to standards maintained at the Library of Congress.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Please see the document at: <A
href="http://www.loc.gov/standards/register-media-types.doc">http://www.loc.gov/standards/register-media-types.doc</A>
</FONT><FONT face=Arial size=2>for background and for the filled-out template as
required by RFC 4288.<BR><BR><BR>According to RFC 4288, “Registration of a new
media type or types starts with the construction of a registration
proposal.” </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>This correspondence together with the above
referenced document is intended to serve as construction of the
proposal. </FONT></DIV>
<DIV><FONT face=Arial size=2> <BR>RFC 4288 further states: “Proposals for
media types registered in the standards tree by the IETF itself MUST be
published as RFCs. Standards tree registrations for media types defined in
documents produced by other standards bodies MUST be described by a formal
standards specification produced by that body.” </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> Formal specifications are cited in the
referenced document for each media type. So may I infer that an RFC is not
necessary?<BR> <BR>Further .... “Proposed registrations in the
standards tree by other standards bodies should be communicated to the
IESG (at iesg@ietf.org) and to the ietf-types list (at ietf-types@iana.org).
…… Notice of a potential media type registration in the standards tree
MUST be sent to the "ietf-types@iana.org" mailing list for
review.”<BR> <BR>Thus I an sending this correspondence to
iesg@ietf.org and <A
href="mailto:ietf-types@iana.org">ietf-types@iana.org</A>.<BR>
<BR>Further.... "Provided that the media type meets all of the relevant
requirements and has obtained whatever approval is necessary, the author may
submit the registration request to the IANA……… IESG approval in effect
submits the registration to the IANA. There is no need for an additional
registration request.”<BR> <BR>Based on this I am not sure what further
steps if any I need to take, so I await guidance. (I have not previously
registered a media type.)<BR><BR>Thank you.<BR><BR>Ray Denenberg, Library of
Congress<BR> <BR> <BR> </FONT></DIV></BODY></HTML>