If the subject of the item is a person or an organization, use the same form of the name as you would if the person or organization were a Creator or Contributor. Select subject keywords from the Title or Description information, or from within a text resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme. Typically, a Subject will be expressed as keywords or key phrases or classification codes that describe the topic of the resource. SubjectĮlement Description: The topic of the content of the resource. Title="AOPA's Tips on Buying Used Aircraft" 4.2. Title="A Pilot's Guide to Aircraft Insurance" If the item is in HTML, view the source document and make sure that the title identified in the title header (if any) is also included as a Title. If in doubt about what constitutes the title, repeat the Title element and include the variants in second and subsequent Title iterations. Typically, a Title will be a name by which the resource is formally known. Consequently, there will occasionally be some judgment required from the person assigning the metadata.Įlement Description: The name given to the resource. While there will normally be a clear preferred choice, there is potential semantic overlap between some elements. Some information may appear to belong in more than one metadata element. Although some environments, such as HTML, are not case-sensitive, it is recommended best practice always to adhere to the case conventions in the element names given below to avoid conflicts in the event that the metadata is subsequently converted to a case-sensitive environment, such as XML. In the element descriptions below, a formal single-word label is specified to make the syntactic specification of elements simpler for encoding schemes. For each element there are guidelines to assist in creating metadata content, whether it is done "from scratch" or by converting an existing record in another format.
#Elements examples full
This section lists each element by its full name and label. Specialists may find the document a useful point of reference to the documentation of Dublin Core, as it changes and grows. For non-specialists, it will assist them in creating simple descriptive records for information resources (for example, electronic documents). This document is intended as an entry point for users of Dublin Core™.
Using Dublin Core™ - The Elements Creator: NOTE: This text was last revised in 2005.