| Dublin-Core currently has 15 recommended tags and uses the DC prefix to distinguish it from other schemas (see also http://purl.org/metadata/dublin_core). |
|
| 1. Title |
| The name given to the resource by the CREATOR or PUBLISHER. |
|
| 2. Creator |
| The person(s) or organisation(s) primarily responsible for the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources. |
|
| 3. Subject |
| The topic of the resource, or keywords or phrases that describe the subject or content of the resource. The intent of the specification of this element is to promote the use of controlled vocabularies and keywords. This element might well include scheme-qualified classification data (for example, Library of Congress Classification Numbers or Dewey Decimal numbers) or scheme-qualified controlled vocabularies (such as MEdical Subject Headings or Art and Architecture Thesaurus descriptors) as well. |
|
| 4. Description |
| A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources. Future metadata collections might well include computational content description (spectral analysis of a visual resource, for example) that may not be embeddable in current network systems. In such a case this field might contain a link to such a description rather than the description itself. |
|
| 5. Publisher |
| The entity responsible for making the resource available in its present form, such as a publisher, a university department, or a corporate entity. The intent of specifying this field is to identify the entity that provides access to the resource. |
|
| 6. Contributor |
| Person(s) or organisation(s) in addition to those specified in the CREATOR element who have made significant intellectual contributions to the resource but whose contribution is secondary to the individuals or entities specified in the CREATOR element (for example, editors, transcribers, illustrators, and conveners). |
|
| 7. Date |
| The date the resource was made available in its present form. The recommended best practice is an 8-digit number in the form YYYYMMDD as defined by ANSI X3.30-1985. In this scheme, the date element for the day this is written would be 19961203, or December 3, 1996. Many other schemas are possible, but if used, they should be identified in an unambiguous manner. |
|
| 8. Type |
| The category of the resource, such as home page, novel, poem, working paper, preprint, technical report, essay, dictionary. |
|
| 9. Format |
| The data representation of the resource, such as text/html, ASCII, Postscript file, executable application, or JPEG image. The intent of specifying this element is to provide information necessary to allow people or machines to make decisions about the usability of the encoded data (what hardware and software might be required to display or execute it, for example). As with TYPE, FORMAT will be assigned from enumerated lists such as registered Internet Media Types (MIME types). In principal, formats can include physical media such as books, serials, or other non-electronic media. |
|
| 10. Identifier |
| String or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). Other globally-unique identifiers, such as International Standard Book Numbers (ISBN) or other formal names would also be candidates for this element. |
|
| 11. Source |
| The work, either print or electronic, from which this resource is derived, if applicable. For example, an html encoding of a Shakespearian sonnet might identify the paper version of the sonnet from which the electronic version was transcribed. |
|
| 12. Language |
| Language(s) of the intellectual content of the resource. Where practical, the content of this field should coincide with the Z39.53 three character codes for written languages (see http://www.sil.org/sgml/nisoLang3-1994.html). |
|
| 13. Relation |
| Relationship to other resources. The intent of specifying this element is to provide a means to express relationships among resources that have formal relationships to others, but exist as discrete resources themselves. For example, images in a document, chapters in a book, or items in a collection. |
|
| 14. Coverage |
| The spatial locations and temporal durations characteristic of the resource. |
|
| 15. Rights |
| The content of this element is intended to be a link (a URL or other suitable URI as appropriate) to a copyright notice, a rights management statement, or perhaps a server that would provide such information in a dynamic way. The intent of specifying this field is to allow providers a means to associate terms and conditions or copyright statements with a resource or collection of resources. No assumptions should be made by users if such a field is empty or not present. |
|
