idnits 2.17.1 draft-kunze-rfc2413bis-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 393. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 7 longer pages, the longest (page 2) being 63 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 8 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (20 April 2007) is 6215 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'ISO3166' is defined on line 326, but no explicit reference was found in the text == Unused Reference: 'RDF' is defined on line 332, but no explicit reference was found in the text == Unused Reference: 'RFC2731' is defined on line 343, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'DCAM' -- Possible downref: Non-RFC (?) normative reference: ref. 'DCENCOD' -- Possible downref: Non-RFC (?) normative reference: ref. 'DCNMSPC' -- Possible downref: Non-RFC (?) normative reference: ref. 'DCTERMS' -- Possible downref: Non-RFC (?) normative reference: ref. 'DCTYPE' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO3166' -- Possible downref: Non-RFC (?) normative reference: ref. 'MIME' -- Possible downref: Non-RFC (?) normative reference: ref. 'RDF' ** Obsolete normative reference: RFC 4646 (Obsoleted by RFC 5646) ** Obsolete normative reference: RFC 2413 (Obsoleted by RFC 5013) ** Obsolete normative reference: RFC 2731 (Obsoleted by RFC 5791) -- Possible downref: Non-RFC (?) normative reference: ref. 'TGN' -- Possible downref: Non-RFC (?) normative reference: ref. 'W3CDTF' Summary: 9 errors (**), 0 flaws (~~), 7 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft: draft-kunze-rfc2413bis-07.txt J. Kunze 3 Dublin Core Metadata University of California 4 Expires 20 October 2007 T. Baker 5 Dublin Core Metadata Initiative 6 20 April 2007 8 The Dublin Core Metadata Element Set 10 (http://www.ietf.org/internet-drafts/draft-kunze-rfc2413bis-07.txt) 12 Status of this Document 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 Distribution of this document is unlimited. Please send comments to 36 jak@ucop.edu 38 Copyright (C) The IETF Trust (2007). All Rights Reserved. 40 Abstract 42 Defines fifteen metadata elements for resource description in a 43 cross-disciplinary information environment. 45 1. Introduction 47 The Dublin Core Metadata Workshop Series began in 1995 with an 48 invitational workshop which brought together librarians, digital 49 library researchers, content experts, and text-markup experts to 50 promote better discovery standards for electronic resources. The 51 resulting metadata element set defines fifteen metadata elements for 52 resource description in a cross-disciplinary information environment. 54 This document contains the current text of Dublin Core "Version 1.1". 55 Version 1.1 is the basis of ANSI/NISO Z39.85-2001 [Z39.85]. The text 56 in the present RFC closely follows the text in the 2007 revision of 57 ANSI/NISO Z39.85, especially sections 2-6 and 10-12. The present RFC 58 obsoletes the Internet RFC 2413 [RFC2413], which was the first 59 published version of the Dublin Core ("Version 1.0"). The main 60 differences between the present RFC and RFC 2413 are in the wording 61 of definitions -- for Contributor and Date (semantically broadened), 62 for Relation (clarified), and in general removing redundant 63 references to "the content of" a resource. In addition, the present 64 RFC recommends lowercase element names (consistent with RDF property 65 types), remains silent about the unrestrictedness of element ordering 66 and repeatability (application profiles being the proper place to 67 discuss such topics), and references the current abstract model, 68 vocabularies, and namespace policies in which the Dublin Core is 69 embedded. 71 2. Foreword 73 The Dublin Core Metadata Element Set is a vocabulary of fifteen 74 properties for use in resource description. The name "Dublin" is due 75 to its origin at a 1995 invitational workshop in Dublin, Ohio; "core" 76 because its elements are broad and generic, usable for describing a 77 wide range of resources. 79 The fifteen element "Dublin Core" described in this standard is part 80 of a larger set of metadata vocabularies and technical specifications 81 maintained by the Dublin Core Metadata Initiative (DCMI). The full 82 set of vocabularies, DCMI Metadata Terms [DCTERMS], also includes a 83 set of resource classes, the DCMI Type Vocabulary [DCTYPE]. The 84 terms in DCMI vocabularies are intended to be used in combination 85 with terms from other, compatible vocabularies in the context of 86 application profiles and on the basis of the DCMI Abstract Model 87 [DCAM]. 89 All changes made to terms of the Dublin Core Metadata Element Set 90 since 2001 have been reviewed by a DCMI Usage Board in the context of 91 a DCMI Namespace Policy [DCNMSPC]. The namespace policy describes 92 how DCMI terms are assigned Uniform Resource Identifiers (URIs) and 93 sets limits on the range of editorial changes that may allowably be 94 made to the labels, definitions, and usage comments associated with 95 existing DCMI terms. 97 3. Scope and Purpose 99 The Dublin Core Metadata Element Set is a standard for cross-domain 100 resource description. As in Internet RFC 3986 [RFC3986], "Uniform 101 Resource Identifier (URI): Generic Syntax," this specification does 102 not limit the scope of what might be a resource. 104 The elements described in this standard are typically used in the 105 context of an application profile which constrains or specifies their 106 use in accordance with local or community-based requirements and 107 policies. The specification of such implementation detail is outside 108 the scope of this standard. 110 4. Definitions 112 DCMI -- the Dublin Core Metadata Initiative, maintenance agency for 113 Dublin Core Metadata Element Set. 115 Resource -- anything that might be identified (the same definition as 116 in Internet RFC 3986 and in the DCMI Abstract Model). 118 Lifecycle of a resource -- a sequence of events that mark the 119 development and use of a resource. Some examples of events in a 120 lifecycle are: conception of an invention, creation of a draft, 121 revision of an article, publication of a book, acquisition by a 122 library, transcription to magnetic disk, migration to optical 123 storage, translation into English, and derivation of a new work 124 (e.g., a movie). 126 5. The Element Set 128 In the element descriptions below, each element has a descriptive 129 label ("label") for human consumption and a unique token ("name") for 130 use in machine processing. 132 In accordance with the DCMI Namespace Policy [DCNMSPC], the "name" of 133 an element is appended to a DCMI namespace URI to construct a Uniform 134 Resource Identifier as a globally unique identifier for that element. 135 The use of element names and URIs in the context of different 136 implementation technologies is explained in DCMI Encoding Guidelines 137 [DCENCOD]. 139 6. The Elements 141 Element Name: title 143 Label: Title 144 Definition: A name given to the resource. 146 Element Name: creator 148 Label: Creator 149 Definition: An entity primarily responsible for making the resource. 150 Comment: Examples of a Creator include a person, an organization, 151 or a service. Typically, the name of a Creator should be 152 used to indicate the entity. 154 Element Name: subject 156 Label: Subject 157 Definition: The topic of the resource. 158 Comment: Typically, the subject will be represented using 159 keywords, key phrases, or classification codes. 160 Recommended best practice is to use a controlled 161 vocabulary. To describe the spatial or temporal 162 topic of the resource, use the Coverage element. 164 Element Name: description 166 Label: Description 167 Definition: An account of the resource. 168 Comment: Description may include but is not limited to: 169 an abstract, a table of contents, a graphical 170 representation, or a free-text account of 171 the resource. 173 Element Name: publisher 175 Label: Publisher 176 Definition: An entity responsible for making the resource available. 177 Comment: Examples of a Publisher include a person, an 178 organization, or a service. Typically, the name of 179 a Publisher should be used to indicate the entity. 181 Element Name: contributor 183 Label: Contributor 184 Definition: An entity primarily responsible for making 185 contributions to the resource. 186 Comment: Examples of a Contributor include a person, an 187 organization, or a service. Typically, the name of a 188 Contributor should be used to indicate the entity. 190 Element Name: date 192 Label: Date 193 Definition: A point or period of time associated with an event 194 in the lifecycle of the resource. 195 Comment: Date may be used to express temporal information 196 at any level of granularity. Recommended best 197 practice is to use an encoding scheme, such as 198 the W3CDTF profile of ISO 8601 [W3CDTF]. 200 Element Name: type 202 Label: Type 203 Definition: The nature or genre of the resource. 204 Comment: Recommended best practice is to use a controlled 205 vocabulary such as the the DCMI Type Vocabulary 206 [DCTYPE]. To describe the file format, physical medium, 207 or dimensions of the resource, use the Format element. 209 Element Name: format 211 Label: Format 212 Definition: The file format, physical medium, or dimensions 213 of the resource. 214 Comment: Examples of dimensions include size and duration. 215 Recommended best practice is to use a controlled 216 vocabulary such as the list of Internet Media Types 217 [MIME]. 219 Element Name: identifier 221 Label: Identifier 222 Definition: An unambiguous reference to the resource within a given 223 context. 224 Comment: Recommended best practice is to identify the 225 resource by means of a string conforming 226 to a formal identification system. 228 Element Name: source 230 Label: Source 231 Definition: A related resource from which the described resource 232 is derived. 233 Comment: The described resource may be derived from the 234 related resource in whole or in part. Recommended 235 best practice is to identify the related resource 236 by means of a string conforming to a formal 237 identification system. 239 Element Name: language 241 Label: Language 242 Definition: A language of the resource. 243 Comment: Recommended best practice is to use a controlled 244 vocabulary such as RFC 4646 [RFC4646]. 246 Element Name: relation 248 Label: Relation 249 Definition: A related resource. 250 Comment: Recommended best practice is to identify the 251 related resource by means of a string conforming 252 to a formal identification system. 254 Element Name: coverage 256 Label: Coverage 257 Definition: The spatial or temporal topic of the resource, the 258 spatial applicability of the resource, or the 259 jurisdiction under which the resource is relevant. 260 Comment: Spatial topic and spatial applicability may be a named 261 place or a location specified by its geographic 262 coordinates. Temporal period may be a named period, 263 date, or date range. A jurisdiction may be a named 264 administrative entity or a geographic place to which the 265 resource applies. Recommended best practice is to use a 266 controlled vocabulary such as the Thesaurus of 267 Geographic Names [TGN]. Where appropriate, named places 268 or time periods can be used in preference to numeric 269 identifiers such as sets of coordinates or date ranges. 271 Element Name: rights 273 Label: Rights 274 Definition: Information about rights held in and over the resource. 275 Comment: Typically, rights information includes a statement about 276 various property rights associated with the resource, 277 including intellectual property rights. 279 7. Security Considerations 281 The Dublin Core element set poses no risk to computers and networks. 282 It poses minimal risk to searchers who obtain incorrect or private 283 information due to careless mapping from rich data descriptions to 284 the Dublin Core elements. No other security concerns are likely. 286 8. IANA Considerations 288 This document has no actions for IANA. 290 9. Authors' Addresses 292 John A. Kunze 293 California Digital Library 294 University of California, Office of the President 295 415 20th St, 4th Floor 296 Oakland, CA 94612-3550, USA 298 Fax: +1 510-893-5212 299 EMail: jak@ucop.edu 301 Thomas Baker 302 Director, Specifications and Documentation 303 Dublin Core Metadata Initiative 304 c/o OCLC Research 305 Dublin, OH 43017, USA 307 Email: tbaker@tbaker.de 309 10. References 311 [DCAM] DCMI Abstract Model. 312 http://dublincore.org/documents/abstract-model/ 314 [DCENCOD] DCMI Encoding Guidelines. 315 http://dublincore.org/resources/expressions/ 317 [DCNMSPC] DCMI Namespace Policy. 318 http://dublincore.org/documents/dcmi-namespace/ 320 [DCTERMS] DCMI Metadata Terms. 321 http://dublincore.org/documents/dcmi-terms/ 323 [DCTYPE] DCMI Type Vocabulary. 324 http://dublincore.org/documents/dcmi-type-vocabulary/ 326 [ISO3166] ISO 3166 - Codes for the representation of names of 327 countries. http://www.din.de/ 329 [MIME] Internet Media Types. 330 http://www.iana.org/assignments/media-types/ 332 [RDF] Resource Description Framework. http://www.w3.org/RDF/ 334 [RFC4646] Tags for Identifying Languages, Internet RFC 4646. 335 http://www.ietf.org/rfc/rfc4646.txt 337 [RFC3986] Uniform Resource Identifier (URI): Generic Syntax, 338 Internet RFC 3986. http://www.ietf.org/rfc/rfc3986.txt 340 [RFC2413] Dublin Core Metadata for Resource Discovery. Internet RFC 341 2413. http://www.ietf.org/rfc/rfc2413.txt 343 [RFC2731] Encoding Dublin Core Metadata in HTML. Internet RFC 2731. 344 http://www.ietf.org/rfc/rfc2731.txt 346 [TGN] Getty Thesaurus of Geographic Names. 347 http://www.getty.edu/research/tools/vocabulary/tgn/index.html 349 [W3CDTF] Date and Time Formats, W3C Note. 350 http://www.w3.org/TR/NOTE-datetime 352 [Z39.85] ANSI/NISO Standard Z39.85-2001 - The Dublin Core Metadata 353 Element Set. 354 http://www.niso.org/standards/resources/Z39-85.pdf 356 11. Appendix A: Further Reading 358 (This appendix is not part of the standard. It is included for 359 information only.) 361 Further information about the Dublin Core metadata element set is 362 available at the URL, 364 http://dublincore.org/ 366 This Web site contains information about workshops, reports, working 367 group papers, projects, and new developments concerning the Dublin 368 Core Metadata Initiative (DCMI). 370 12. Appendix B: Maintenance Agency 372 (This appendix is not part of the standard. It is included for 373 information only.) 375 The Dublin Core Metadata Initiative (DCMI) is responsible for the 376 development, standardization, and promotion of the Dublin Core 377 metadata element set. Information on DCMI is available at the URL, 379 http://dublincore.org/ 381 13. Copyright Notice 383 Copyright (C) The IETF Trust (2007). This document is subject to the 384 rights, licenses and restrictions contained in BCP 78, and except as 385 set forth therein, the authors retain all their rights. 387 This document and the information contained herein are provided on an 388 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 389 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 390 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 391 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 392 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 393 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 395 Expires 20 October 2007