| TOC |
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright © The Internet Society (1997). All Rights Reserved.
This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications.
| TOC |
3. Registration Information
4. Security Considerations
5. Interoperability Considerations
6. Published Specification
7. References (BOILERPLATE)
8. Author's Address (BOILERPLATE)
9. Full Copyright Statement (BOILERPLATE)
§ Author's Address
§ Intellectual Property and Copyright Statements
The MARC formats are sets of codes and content designators defined for encoding metadata for five types of data: bibliographic, holdings, authority, classification, and community information. The structure of MARC records is an implementation of national and international standards, ANSI Z39.2 (Information Interchange Format) and ISO 2709 (Format for Information Interchange). Codes and conventions in the formats identify and characterize data elements within a record and support the manipulation of those data.
MARC formats are communication formats, primarily designed to provide specification for the exchange of bibliographic and related information between systems. They are widely used in a variety of exchange and processing environments. They do not mandate internal storage or display formats to be used by different systems.
Since there are different flavors of MARC which would be processed by different applications, this content-type/subtype refers to the harmonized USMARC/CANMARC specification. Additional content- types/subtypes may be defined in the future (e.g. application/unimarc).
MARC records involve three elements: the record structure, content designation, and data content. Only those records that contain all three elements according to the standard would use this content- type/subtype, i.e. content extracted from the structure would not. Since MARC does not mandate an internal storage format, parameters have not been assigned to specific implementations (e.g. OCLC-MARC, LC-MARC, etc.). In addition, parameters have not been defined for the specific type of MARC format (e.g. bibliographic, authority, holdings), since the information is contained in the Leader portion of the record.
Media type name: application
Media subtype name: marc
Required parameters: None
Optional parameters: None
Encoding considerations: MARC records may contain long lines and/or arbitrary octet values. The base64 content-transfer-encoding is recommended for transmission of MARC over electronic mail.
There are no known security risks associated with the use or viewing of MARC data. A MARC record may have security classification associated with the document it describes or metadata in that record. Although this does not present any security risk to the user of MARC data, it may provide an opportunity for a security breach for the source of classified MARC data.
MARC is a communication format and is designed for interoperability between different systems that may store data in local formats internally.
"USMARC Format for Bibliographic Data"; "USMARC Format for Authority Data"; "USMARC Format for Holdings Data"; "USMARC Format for Classification Data"; "USMARC Format for Community Information".
File extension: .mrc OID: 1.2.840.10003.5.10
Person & email address to contact for further information:
Network Development & MARC Standards Office <email@example.com> 101 Independence Ave. SE Library of Congress Washington, DC 20540-4102 U.S.A.
This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "References."
This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "Author's Address."
This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "Full Copyright Statement."
|Network Development & MARC Standards Office|
|Library of Congress|
|101 Independence Ave.|
|DC 20540-4102 U.S.A.|
|Phone:||+1 (202) 707-5092|
|Fax:||+1 (202) 707-0115|
Copyright © The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP 11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.