1. 1 Dublin Core & DCMI – an introduction Some slides are from DCMI Training Resources at: http://dublincore.org/resources/training/

2. 2 1. The original Dublin Core: the idea A basic description mechanism that:  can be used in all domains  can be used for any type of resource  is simple, yet powerful  can be extended and can work with specific solutions Making it easier to find information wherever located (Internet/Intranets)

3. 3 2. The Dublin Core Metadata Element Set （ DCMES ） dc: Metadata elements The Dublin Core Metadata Element Set http://dublincore.org/documents/dces/ or: http://dublincore.org/documents/dcmi- terms/#H2 http://dublincore.org/documents/dces/http://dublincore.org/documents/dcmi- terms/#H2 “Core” set, simple enough for non- experts to understand and create A “library catalog card” for Web objects Based on consensus across domains Elements 1.Identifier 2.Title 3.Creator 4.Contributor 5.Publisher 6.Subject 7.Description 8.Coverage 9.Format 10.Type 11.Date 12.Relation 13.Source 14.Rights 15.Language

4. 4 The Dublin Core Metadata Element Set （ DCMES ） 15 elements all optional all repeatable

5. 5 Compiled based on Compiled according to DCMI Metadata Terms, 2008-01-14, ©mzeng

6. 6 Cont. DC Version 1.1 Elements with Refinements and Encoding Schemes

7. 7 Elements* requiring using Encoding Schemes ContentIntellectual PropertyInstantiation Coverage *Contributor Date * DescriptionCreator Format * Type * PublisherIdentifier RelationRights Language * Source Subject * Title Values assigned in some spaces should follow certain encoding schemes. An encoding scheme usually appears as a list of name tokens or terms from which values can be selected for the associated metadata elements.

8. 8 Value space that should apply controlled vocabularies / value encoding schemes : LANGUAGE Examples from values associated with LANGUAGE element found in the research samples because of failing to follow the recommendation en eng en-GB en-US English engfre new Korean Deutsch German LOCLANGUAGE:: German

9. 9 Value space that should follow syntax encoding schemes : DATE Examples from values associated with DATE element 1979 2000-03 2000-03-01 2001-01-02T21:48.00Z 200003 C1999, 2000 January, 1919 May, 1919 1987, c2000 ?1999 1952 (issued) (1982) 1930? 1823-1845 Between 1680 and 1896? 5/1/01 01 May 2008

10. 10 3. Growing the vocabulary to become DCMI Metadata Terms (dcterms:) Elements 1.Identifier 2.Title 3.Creator 4.Contributor 5.Publisher 6.Subject 7.Description 8.Coverage 9.Format 10.Type 11.Date 12.Relation 13.Source 14.Rights 15.Language Abstract Access rights Alternative Audience Available Bibliographic citation Conforms to Created Date accepted Date copyrighted Date submitted Education level Extent Has format Has part Has version Is format of Is part of Is referenced by Is replaced by Is required by Issued Is version of License Mediator Medium Modified Provenance References Replaces Requires Rights holder Spatial Table of contents Temporal Valid Refinements Box DCMIType DDC IMT ISO3166 ISO639-2 LCC LCSH MeSH Period Point RFC1766 RFC3066 TGN UDC URI W3CTDF Encodings Collection Dataset Event Image Interactive Resource Moving Image Physical Object Service Software Sound Still Image Text Types

11. 11 Note: all refinements are now also 'properties' in DCMI Terms DCMI Metadata Terms dcterms: or dct:

12. 12 5. DCMI namespaces All DCMI Metadata Terms are given a unique identity within DCMI namespaces: http://purl.org/dc/elements/1.1/ (for the legacy DC-15 elements) http://purl.org/dc/terms/ (for all elements and element refinements) http://purl.org/dc/dcmitype/ (for the DCMI Type vocabulary)

13. 13 http://purl.org/dc/elements/1.1/creatorhttp://purl.org/dc/elements/1.1/creator “dc:creator” http://purl.org/dc/terms/titlehttp://purl.org/dc/terms/title "dct:title" E.g., “title” is identified by its Uniform Resource Identifier (URI): “http://purl.org/dc/elements/1.1/title” in legacy “dc” or "http://purl.org/dc/terms/title" in “dcterms” Term URI QName (XML qualified name)

14. Term constraints: Range and Domain 14 Constraints indicate where it applies (Has Domain: “Collection”) what values to be used in the metadata statement, non-literal or literal (constant values represented by character strings). what kind of values its instances should be (Has Range: “Frequency”).

15. Literal and non-literal values 15 The values are literals* The values are non- literals (URIs) *literal (constant values represented by character strings)

16. 16 6. The Dublin Core in context: Application profiles (will be discussed later)  In practice, metadata implementers combine elements from different sources (e.g. DC plus elements from other schemas, “local” elements) refine definitions of elements constrain use of elements  Application profiles (will be discussed later) element set plus policies, guidelines some DCMI WGs developing application profiles for specific domains

17. 17 References Dublin Core Metadata Initiative: http://dublincore.org/http://dublincore.org/ DCMI Metadata Terms http://dublincore.org/documents/dcmi- terms/ http://dublincore.org/documents/dcmi- terms/ Dekkers, Makx. (2010). Dublin Core in the Early Web Revolution. http://dublincore.org/resources/training/ Baker, Thomas. (2009) The "metadata record" and DCMI Abstract Model. http://dublincore.org/resources/training/ Dempsey, Lorcan. “Scientific, Industrial, and Cultural Heritage: a shared approach” http://www.ariadne.ac.uk/issue22/dempsey/ http://www.ariadne.ac.uk/issue22/dempsey/ Johnston, Pete. (2002). An introduction to the Dublin Core and the DCMI. www.ukoln.ac.uk/interop- focus/presentations/gateway/gateway.pptwww.ukoln.ac.uk/interop- focus/presentations/gateway/gateway.ppt Baker, Thomas. (2005) Diverse vocabularies in a common model: Dublin Core at 10 years. http://dc2005.uc3m.es/program/presentations/2005-09- 12.plenary.baker-keynote.ppt http://dc2005.uc3m.es/program/presentations/2005-09- 12.plenary.baker-keynote.ppt