idnits 2.17.1 draft-denenberg-mods-etc-media-types-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 16, 2010) is 4878 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) -- Obsolete informational reference (is this intentional?): RFC 4288 (Obsoleted by RFC 6838) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Denenberg, Ed. 3 Internet-Draft Library of Congress 4 Intended status: Informational P. Saint-Andre, Ed. 5 Expires: June 19, 2011 Cisco 6 December 16, 2010 8 The Media Types application/mods+xml, application/mads+xml, application/ 9 mets+xml, application/marcxml+xml, application/sru+xml 10 draft-denenberg-mods-etc-media-types-03 12 Abstract 14 This document specifies Media Types for the following formats: MODS 15 (Metadata Object Description Schema), MADS (Metadata Authority 16 Description Schema), METS (Metadata Encoding and Transmission 17 Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve 18 via URL Response Format) Protocol response XML schema. These are all 19 XML schemas providing representations of various forms of information 20 including metadata and search results. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on June 19, 2011. 39 Copyright Notice 41 Copyright (c) 2010 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Registration for mods+xml . . . . . . . . . . . . . . . . . . 4 58 3. Registration for mads+xml . . . . . . . . . . . . . . . . . . 5 59 4. Registration for mets+xml . . . . . . . . . . . . . . . . . . 6 60 5. Registration for marcxml+xml . . . . . . . . . . . . . . . . . 7 61 6. Registration for sru+xml . . . . . . . . . . . . . . . . . . . 8 62 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 63 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 64 8.1. Harmful Content . . . . . . . . . . . . . . . . . . . . . 9 65 8.2. Authenticity and Confidentiality . . . . . . . . . . . . . 9 66 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 67 9.1. Normative References . . . . . . . . . . . . . . . . . . . 10 68 9.2. Informative References . . . . . . . . . . . . . . . . . . 11 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 71 1. Introduction 73 The Library of Congress, on behalf of and in collaboration with 74 various components of the metadata and information retrieval 75 community, has issued specifications which define formats for 76 representation of various forms of information including metadata and 77 search results. This memo provides information about the Media Types 78 associated with several of these formats, all of which are XML 79 schemas. 81 MODS: Metadata Object Description Schema. An XML schema for a 82 bibliographic element set that may be used for a variety of 83 purposes, and particularly for library applications. 85 MADS: Metadata Authority Description Schema. An XML schema for an 86 authority element set used to provide metadata about agents 87 (people, organizations), events, and terms (topics, geographics, 88 genres, etc.). It is a companion to the MODS Schema. 90 METS: Metadata Encoding and Transmission Standard. An XML schema for 91 encoding descriptive, administrative, and structural metadata 92 regarding objects within a digital library. 94 MARCXML MARC21 XML Schema. An XML schema for the direct XML 95 representation of the MARC format (for which there already exists 96 a media type, application/marc; see [RFC2220]). By "direct XML 97 representation" we mean that it encodes the actual MARC data 98 within XML. (This is in contrast to MODS: MARC uses codes for its 99 element names; MODS represents the same information but uses 100 semantically meaningful names while MARCXML uses the MARC codes.) 102 SRU: Search/Retrieve via URL Response Format. An XML schema for the 103 SRU response. SRU is a protocol, and the media type sru+xml 104 pertains specifically to the default SRU response. The SRU 105 response may be supplied in any of a number of suitable schemas, 106 RSS, ATOM, for example, and the client identifies the desired 107 format in the request, hence the need for a media type. This 108 mechanism will be introduced in SRU 2.0; in previous versions 109 (that is, all versions to date; 2.0 is in development) all 110 responses are supplied in the existing default format, so no media 111 type was necessary. SRU 2.0 is being developed within the 112 Organization for the Advancement of Structured Information 113 Standards (OASIS). 115 2. Registration for mods+xml 117 MIME media type name: application 119 MIME subtype name: mods+xml 121 Required parameters: None 123 Optional parameters: (charset) This parameter has semantics 124 identical to the charset parameter of the "application/xml" media 125 type as specified in [RFC3023]. 127 Encoding considerations: Identical to those of "application/xml" as 128 described in [RFC3023]. 130 Security considerations: See Section 8 of RFC XXXX. 132 [[NOTE TO RFC EDITOR: Please replace "XXXX" with the number issued 133 to this specification.]] 135 Interoperability considerations: There are no known interoperability 136 issues. 138 Published specification: [MODS-SCHEMA], [MODS] 140 Applications which use this media type: Various MODS conformant 141 toolkits use this media type. 143 Additional information: 145 Magic number(s): None 147 File extension(s): .mods 149 Macintosh file type code(s): TEXT 151 Person and email address to contact for further information: Ray 152 Denenberg 154 Intended usage: COMMON 156 Restrictions on usage: None 158 Author/Change controller: The MODS specification was developed by 159 the Library of Congress and is maintained by the Library of 160 Congress in conjunction with the MODS Editorial Committee which 161 has change control over the specification. 163 3. Registration for mads+xml 165 MIME media type name: application 167 MIME subtype name: mads+xml 169 Required parameters: None 171 Optional parameters: (charset) This parameter has semantics 172 identical to the charset parameter of the "application/xml" media 173 type as specified in [RFC3023]. 175 Encoding considerations: Identical to those of "application/xml" as 176 described in [RFC3023]. 178 Security considerations: See Section 8 of RFC XXXX. 180 [[NOTE TO RFC EDITOR: Please replace "XXXX" with the number issued 181 to this specification.]] 183 Interoperability considerations: There are no known interoperability 184 issues. 186 Published specification: [MADS-SCHEMA], [MADS] 188 Applications which use this media type: Various MADS conformant 189 toolkits use this media type. 191 Additional information: 193 Magic number(s): None 195 File extension(s): .mads 197 Macintosh file type code(s): TEXT 199 Person and email address to contact for further information: Ray 200 Denenberg 202 Intended usage: COMMON 204 Restrictions on usage: None 206 Author/Change controller: The MADS specification was developed by 207 the Library of Congress and is maintained by the Library of 208 Congress in conjunction with the MODS Editorial Committee which 209 has change control over the specification. 211 4. Registration for mets+xml 213 MIME media type name: application 215 MIME subtype name: mets+xml 217 Required parameters: None 219 Optional parameters: (charset) This parameter has semantics 220 identical to the charset parameter of the "application/xml" media 221 type as specified in [RFC3023]. 223 Encoding considerations: Identical to those of "application/xml" as 224 described in [RFC3023]. 226 Security considerations: See Section 8 of RFC XXXX. 228 [[NOTE TO RFC EDITOR: Please replace "XXXX" with the number issued 229 to this specification.]] 231 Interoperability considerations: There are no known interoperability 232 issues. 234 Published specification: [METS-SCHEMA], [METS] 236 Applications which use this media type: Various METS conformant 237 toolkits use this media type. 239 Additional information: 241 Magic number(s): None 243 File extension(s): .mets 245 Macintosh file type code(s): TEXT 247 Person and email address to contact for further information: Ray 248 Denenberg 250 Intended usage: COMMON 252 Restrictions on usage: None 254 Author/Change controller: The METS specification was developed by 255 the Library of Congress and is maintained by the Library of 256 Congress in conjunction with the METS Editorial Board as an 257 initiative of the Digital Library Federation. 259 5. Registration for marcxml+xml 261 MIME media type name: application 263 MIME subtype name: marcxml+xml 265 Required parameters: None 267 Optional parameters: (charset) This parameter has semantics 268 identical to the charset parameter of the "application/xml" media 269 type as specified in [RFC3023]. 271 Encoding considerations: Identical to those of "application/xml" as 272 described in [RFC3023]. 274 Security considerations: See Section 8 of RFC XXXX. 276 [[NOTE TO RFC EDITOR: Please replace "XXXX" with the number issued 277 to this specification.]] 279 Interoperability considerations: There are no known interoperability 280 issues. 282 Published specification: [MARCXML-SCHEMA], [MARCXML] 284 Applications which use this media type: Various MARCXML conformant 285 toolkits use this media type. 287 Additional information: 289 Magic number(s): None 291 File extension(s): .mrcx 293 Macintosh file type code(s): TEXT 295 Person and email address to contact for further information: Ray 296 Denenberg 298 Intended usage: COMMON 300 Restrictions on usage: None 302 Author/Change controller: The MARCXML standard is driven by the MARC 303 standards, maintained at the Library of Congress. 305 6. Registration for sru+xml 307 MIME media type name: application 309 MIME subtype name: sru+xml 311 Required parameters: None 313 Optional parameters: (charset) This parameter has semantics 314 identical to the charset parameter of the "application/xml" media 315 type as specified in [RFC3023]. 317 Encoding considerations: Identical to those of "application/xml" as 318 described in [RFC3023]. 320 Security considerations: See Section 8 of RFC XXXX. 322 [[NOTE TO RFC EDITOR: Please replace "XXXX" with the number issued 323 to this specification.]] 325 Interoperability considerations: There are no known interoperability 326 issues. 328 Published specification: [SRU-SCHEMA], [SRU] 330 Applications which use this media type: Various SRU conformant 331 toolkits use this media type. 333 Additional information: 335 Magic number(s): None 337 File extension(s): .sru 339 Macintosh file type code(s): TEXT 341 Person and email address to contact for further information: Ray 342 Denenberg 344 Intended usage: COMMON 346 Restrictions on usage: None 348 Author/Change controller: The SRU specification for versions earlier 349 than 2.0 is maintained at the Library of Congress, in conjunction 350 with the SRU Editorial Board. Version 2.0 (for which the sru+xml 351 media type pertains) is being developed within OASIS. 353 7. IANA Considerations 355 IANA is requested to register five media types described in Sections 356 2, 3, 4, 5, and 6 in the MIME media type registry (in the Standards 357 Tree). 359 8. Security Considerations 361 An XML resource does not in itself compromise data security. 362 Applications that retrieve XML files over a network by means of 363 dereferencing a Uniform Resource Identifier [RFC3986] are advised to 364 properly interpret the data so as to prevent unintended access. 365 Hence the security issues described in Section 7 of [RFC3986] apply. 367 Because the media types described in this document use the "+xml" 368 convention, they share the security considerations described in 369 Section 10 of [RFC3023]. 371 In general, security issues related to the use of XML in IETF 372 protocols are discussed in Section 7 of [RFC3470] also apply. In the 373 following sections we review but review some aspects that are 374 important for document-centric XML as applied to text encoding. 376 8.1. Harmful Content 378 Any application that retrieves the XML media types described in this 379 specification needs to be aware of risks connected with injection of 380 harmful scripts and executable XML (i.e., "active content" as 381 described in [RFC4288]). Although XML inclusion mechanisms and the 382 use of external entities can introduce vulnerabilities to various 383 forms of spoofing and also reveal aspects of a service in a way that 384 may compromise its security, such vulnerabilities are application- 385 specific. In any case, MODS documents do not contain "active 386 content". 388 8.2. Authenticity and Confidentiality 390 Historical and bibliographical information can be often encoded in 391 MODS documents, and such information might even have legal force in 392 some jurisdictions. Digitization and encoding of such information 393 might require technologies for assuring authenticity, such as 394 cryptographic check sums and electronic signatures. Similarly, 395 historical documents might in part or in their entirety be 396 confidential. Such confidentiality might be required by law or by 397 the terms and conditions such as in the case of donated or deposited 398 text from private sources. A text archive might need content 399 filtering or cryptographic technologies to meet such requirements. 401 9. References 403 9.1. Normative References 405 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 406 Types", RFC 3023, January 2001. 408 [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for 409 the Use of Extensible Markup Language (XML) 410 within IETF Protocols", BCP 70, RFC 3470, January 2003. 412 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 413 Resource Identifier (URI): Generic Syntax", STD 66, 414 RFC 3986, January 2005. 416 [MADS-SCHEMA] 417 Denenberg, R., "MADS Schema", 418 . 420 [MADS] Denenberg, R., "Metadata Authority Description Schema", 421 . 423 [MARCXML-SCHEMA] 424 Denenberg, R., "MARCXML Schema", . 427 [MARCXML] Denenberg, R., "MARCXML MARC21 XML Schema", 428 . 430 [METS-SCHEMA] 431 Denenberg, R., "METS Schema", 432 . 434 [METS] Denenberg, R., "Metadata Encoding and Transmission 435 Standard", . 437 [MODS-SCHEMA] 438 Denenberg, R., "MODS Schema", 439 . 441 [MODS] Denenberg, R., "Metadata Object Description Schema", 442 . 444 [SRU-SCHEMA] 445 Denenberg, R., "SRU Schema", . 448 [SRU] Denenberg, R., "Search/Retrieve via URL Response Format", 449 . 451 9.2. Informative References 453 [RFC2220] Guenther, R., "The Application/MARC Content-type", 454 RFC 2220, October 1997. 456 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 457 Registration Procedures", BCP 13, RFC 4288, December 2005. 459 Authors' Addresses 461 Ray Denenberg (editor) 462 Library of Congress 463 101 Independence Ave, SE 464 Washington, DC 20540 465 USA 467 Phone: (202) 707-5795 468 Email: rden@loc.gov 470 Peter Saint-Andre (editor) 471 Cisco 473 Email: psaintan@cisco.com