INTERNET DRAFT R. Denenberg Intended status: Standards Track Library of Congress Expires: November 8, 2009 May 7, 2009 The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, application/sru+xml draft-denenberg-mods-etc-media-types-00 This Document: http://www.loc.gov/standards/sru/internet-drafts/draft-denenberg-mods-etc-media-types-00.txt html: http://www.loc.gov/standards/sru/internet-drafts/draft-denenberg-mods-etc-media-types-00.html word: http://www.loc.gov/standards/sru/internet-drafts/draft-denenberg-mods-etc-media-types-00.doc pdf: http://www.loc.gov/standards/sru/internet-drafts/draft-denenberg-mods-etc-media-types-00.pdf Status of this Memo 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/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Abstract This document specifies Media Types for the following formats: MODS (Metadata Object Description Schema), MADS (Metadata Authority Description Schema), METS (Metadata Encoding and Transmission Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve via URL Response Format) Protocol response XML schema. These are all XML schemas providing representations of various forms of information including metadata and search results. 1. Introduction The Library of Congress, on behalf of and in collaboration with various components of the metadata and information retrieval community, has issued specifications which define formats for representation of various forms of information including metadata and search results. This memo provides information about the Media Types associated with several of these formats, all of which are XML schemas. o MODS: Metadata Object Description Schema. An XML schema for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. o MADS: Metadata Authority Description Schema An XML schema for an authority element set used to provide metadata about agents (people, organizations), events, and terms (topics, geographics, genres, etc.). It is a companion to the MODS Schema. o METS: Metadata Encoding and Transmission Standard An XML schema for encoding descriptive, administrative, and structural metadata regarding objects within a digital library. o MARCXML MARC21 XML Schema An XML schema for the direct XML representation of the MARC format (for which there already exists a media type, application/marc; see http://www.faqs.org/rfcs/rfc2220.html.) By "direct XML representation" we mean that it encodes the actual MARC data within XML. (This is in contrast to MODS: MARC uses codes for its element names; MODS represents the same information but uses semantically meaningful names while MARCXML uses the MARC codes.) o SRU: Search/Retrieve via URL Response Format An XML schema for the SRU response. SRU is a protocol, and the media type sru+xml pertains specifically to the default SRU response. the SRU response may be supplied in any of a number of suitable schemas, RSS, ATOM, for example, and the client identifies the desired format in the request, hence the need for a media type. This mechanism will be introduced in SRU 2.0; in previous versions (that is, all versions to date; 2.0 is in development) all responses are supplied in the existing default format, so no media type was necessary. SRU 2.0 is being developed within OASIS. 2. Registration Information for mods+xml o Type name: application o Subtype name: mods+xml o Required parameters: none o Optional parameters: charset: This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in RFC 3023. o Encoding considerations: Identical to those of "application/xml" as described in RFC 3023. o Security considerations: The same security considerations as described in RFC 3023, Section 10. o Interoperability considerations: There are no known interoperability issues. o Published specifications: The MODS XML schema is at: http://www.loc.gov/standards/mods/mods.xsd. The home page for the MODS specification is http://www.loc.gov/standards/mods/ o Applications that use this media type: Various MODS conformant toolkits use these respective media type. o Additional information: None. o Magic number(s): None o File extension(s): .mods o Macintosh file type code(s): TEXT o Person & email address to contact for further information: Ray Denenberg, rden@loc.gov o Intended usage: common o Restrictions on usage: none o Author/Change controller The MODS specification was developed by the Library of Congress and is maintained by the Library of Congress in conjunction with the MODS Editorial Committee which has change control over the specification. 3. Registration Information for mads+xml o Type name: application o Subtype name: mads+xml o Required parameters: none o Optional parameters: charset: This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in RFC 3023. o Encoding considerations: Identical to those of "application/xml" as described in RFC 3023. o Security considerations: The same security considerations as described in RFC 3023, Section 10. o Interoperability considerations: There are no known interoperability issues. o Published specifications: The MADS XML schema is at: http://www.loc.gov/standards/mads/mads.xsd. The home page for the MADS specification is http://www.loc.gov/standards/mads/ o Applications that use this media type: Various MADS conformant toolkits use these respective media type. o Additional information: None. o Magic number(s): None o File extension: .mads o Macintosh file type code(s): TEXT o Person & email address to contact for further information: Ray Denenberg, rden@loc.gov o Intended usage: common o Restrictions on usage: none o Author/Change controller: The MADS specification, similarly, was developed by the Library of Congress and is maintained by the Library of Congress in conjunction with the MODS Editorial Committee which has change control over the specification. 4. Registration Information for mets+xml o Type name: application o Subtype name: mets+xml o Required parameters: none o Optional parameters: charset: This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in RFC 3023. o Encoding considerations: Identical to those of "application/xml" as described in RFC 3023. o Security considerations: The same security considerations as described in RFC 3023, Section 10. o Interoperability considerations: There are no known interoperability issues. o Published specifications: .. The METS XML schema is at: http://www.loc.gov/standards/mets/mets.xsd .. The home page for the METS specification is http://www.loc.gov/standards/mets/ o Applications that use this media type: Various METS conformant toolkits use these respective media type. o Additional information: None. o Magic number(s): None o File extension: .mets o Macintosh file type code(s): TEXT o Person & email address to contact for further information: Ray Denenberg, rden@loc.gov o Intended usage: common o Restrictions on usage: none o Author/Change controller: The METS standard is maintained by the Library of Congress in conjunction with the METS Editorial Board as an initiative of the Digital Library Federation. 5. Registration Information for marcxml+xml o Type name: application o Subtype name: marcxml+xml o Required parameters: none o Optional parameters: charset: This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in RFC 3023. o Encoding considerations: Identical to those of "application/xml" as described in RFC 3023. o Security considerations: The same security considerations as described in RFC 3023, Section 10. o Interoperability considerations: There are no known interoperability issues. o Published specifications: The MARCXML XML schema is at: http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd The home page for the MARCXML specification is http://www.loc.gov/standards/marcxml/; o Applications that use this media type: Various MARCXML conformant toolkits use these respective media type. o Additional information: None. o Magic number(s): None o File extension: .mrcx o Macintosh file type code(s): TEXT o Person & email address to contact for further information: Ray Denenberg, rden@loc.gov o Intended usage: common o Restrictions on usage: none o Author/Change controller The MARCXML standard is driven by the MARC standards, maintained at the Library of Congress. 6. Registration Information for sru+xml o Type name: application o Subtype name: sru+xml o Required parameters: none o Optional parameters: charset: This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in RFC 3023. o Encoding considerations: Identical to those of "application/xml" as described in RFC 3023. o Security considerations: The same security considerations as described in RFC 3023, Section 10. o Interoperability considerations: There are no known interoperability issues. o Published specifications: The OASIS Search Web Services Technical Committee public page is at http://www.oasis- open.org/committees/tc_home.php?wg_abbrev=search-ws The current draft of SRU 2.0 is at http://www.oasis- open.org/apps/org/workgroup/search-ws/download.php/32233/sru-2- 0%20%20sixth%20draft.doc The media type application/sru+xml is described in Annex A, and the XML schema is in A.3. Versions earlier than 2.0 are maintained at http://www.loc.gov/standards/sru/. o Applications that use this media type: Various SRU conformant toolkits use these respective media type. o Additional information: None. o Magic number(s): None o File extension: .sru o Macintosh file type code(s): TEXT o Person & email address to contact for further information: Ray Denenberg, rden@loc.gov o Intended usage: common o Restrictions on usage: none o Author/Change controller The SRU specification for versions earlier than 2.0 is maintained at the Library of Congress, in conjunction with the SRU Editorial Board. Version 2.0 (for which the sru+xml media type pertains) is being developed within OASIS. 7. Editor's Address Ray Denenberg Library of Congress Washington DC 20540 Phone: (202) 707-5795 Email: rden@loc.gov Full Copyright Statement 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. All IETF Documents and the information contained therein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.