Dublin Core Description Set Profiles (DC-2009)
- 1. Dublin Core Description Set Profiles DC-2009, Seoul, Korea
- 3. Dublin Core & the DCMI Abstract Model DC metadata Making statements “about” things Statements grouped into logically bounded units e.g. “description of document” v “description of person” DCMI Abstract Model DCMI Recommendation June 2007 http://dublincore.org/documents/2007/06/04/abstract-model/
- 4. Resource URI Resource URI Description Statement Property URI Non-Literal Value Surrogate Vocab Enc Scheme URI Value URI Value string Value string Syntax Enc Scheme URI Language Description Statement Property URI Literal Value Surrogate Value string Syntax Enc Scheme URI Description Set Statement Property URI Literal Value Surrogate Value string Language Statement Statement
- 5. Beyond DCAM Specify a “pattern” of terms used within description set structure by a community for some purpose Repeatability “ Recipe” for distributed data creation Disclosure/discovery of nature of dataset Provider can give potential consumer “advance notice” of patterns in use Form/editor/database configuration Conformance testing/“Validation” Documentation as part of DC Application Profile “ To support this set of requirements, this set of patterns is useful”
- 6. DCMI Description Set Profile (DSP) Description Set Profiles: A constraint language for Dublin Core Application Profiles http://dublincore.org/documents/dc-dsp / Specifying “structural constraints” on a description set the resources that may be described by descriptions in the description set the properties that may be referenced in statements the ways a value surrogate may be given
- 7. DCMI Description Set Profile (DSP) Description templates Statement templates Templates contain constraints of specified types e.g. Property URI List Vocabulary Encoding Scheme Occurrence Literal List XML format for expressing a DSP
- 8. Description Templates & Statement Templates Description template description set must contain exactly one description of a Book; may contain one or more descriptions of a Agent Statement template description of Book must contain exactly one statement referring to property dcterms:title, with a plain literal value in English description of Book may contain zero or more statements referring to property dcterms:subject, with a non-literal value, from the dcterms:LCSH VES
- 9. Design Patterns and DSPs
- 10. Patterns Uncontrolled text string (literal)
- 11. Patterns Uncontrolled text string (literal) Structured text string (SES)
- 12. Patterns Uncontrolled text string (literal) Structured text string (SES) Controlled vocabulary (local)
- 13. Patterns Uncontrolled text string (literal) Structured text string (SES) Controlled vocabulary (local) Controlled vocabulary (external VES)
- 14. Patterns Uncontrolled text string (literal) Structured text string (SES) Controlled vocabulary (local) Controlled vocabulary (external VES) Controlled vocabulary (URIs, external VES)
- 15. DSP Statement Template in XML <StatementTemplate type="literal"> <Property>http://purl.org/dc/terms/created</Property> <LiteralConstraint> <SyntaxEncodingSchemeOccurrence> Required </SyntaxEncodingSchemeOccurrence> <SyntaxEncodingScheme> http://purl.org/dc/terms/W3CDTF </SyntaxEncodingScheme> </LiteralConstraint> </StatementTemplate>
- 16. Pattern Library Description Template/Statement Template Pattern Library http://dublincore.org/dcmirdataskgroup/apDesigns Please browse/contribute!
- 17. Summary DCMI Abstract Model defines structure of description set A DSP describes a pattern for using that structure Enables shared use by community, validation, tool configuration, etc Caution: DSP spec still work-in-progress! Discussion on DC-Architecture Jiscmail list
- 18. Pete Johnston Technical Researcher Eduserv Bath, UK Work Email: mailto:pete.johnston@eduserv.org.uk Work Home: http://www.eduserv.org.uk/research/people/petejohnston/ Work Weblog (with Andy Powell): http://efoundations.typepad.com/ Twitter: http:// twitter.com/repetej Photo “ P1010285” by Flickr user andypowe11 See http://www.flickr.com/photos/andypowe11/261892349/ Made available under CC Attribution 2.0 Generic license
- 19. Dublin Core Description Set Profiles Title slide photo “ Euljiro SK Building Seoul” by Flickr user swisscan See http://www.flickr.com/photos/swisscan/2286781443/ Made available under CC Attribution- NonCommercial -Share-Alike 2.0 license
- 20. Dublin Core Description Set Profiles DC-2009, Seoul, Korea
Editor's Notes
- #10: Although the DC application profile design allows for a wide variety of metadata choices, there are some common patterns that can be defined. Many metadata elements can be defined using these common patterns, and by defining them on the site we can satisfy a certain number of application profile needs.
- #11: One of the more common patterns is that of a literal string. This is used for data elements that have no pre-defined structure or content. For example, titles of documents are generally recorded as literal strings.
- #12: Some metadata value strings have structure, such as the structure of a date or currency. These patterns can be defined for all to use.
- #13: A common pattern is a list of controlled vocabulary terms that are defined internally in the AP.
- #14: Often one wants to use a controlled vocabulary that has been defined elsewhere. This vocabulary can be identified in the AP.
- #15: You can also use a controlled vocabulary whose values are identified with URIs.