1 / 13

DC-Text: a simple text-based format for DC metadata

DC-Text: a simple text-based format for DC metadata . DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico. DC-Text: a text format for DC metadata. Context & motivation DCMI Abstract Model DCMI “encoding guidelines” DC-Text Basic structure Features

roshaun
Télécharger la présentation

DC-Text: a simple text-based format for DC metadata

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DC-Text: a simple text-based format for DC metadata DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  2. DC-Text: a text format for DC metadata • Context & motivation • DCMI Abstract Model • DCMI “encoding guidelines” • DC-Text • Basic structure • Features • Some reflections, issues still to be discussed DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  3. Why DC-Text? Context & Motivation • Historical separation of DC description model from representation/encoding • “Grammatical Principles” v “Encoding Guidelines” • Formalised in development of DCMI Abstract Model • DCMI Recommendation March 2005 • DCAM describes • Components and constructs that make up an information structure (“DC description set”) • How that information structure is to be interpreted • DCAM does not describe how to represent a DC description set in concrete form DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  4. DCAM Description Model • a description set is made up of one or more descriptions • a description is made up of • zero or one resource URI and • one or more statements • a statement is made up of • exactly one property URI and • zero or one reference to a value in the form of a value URI • zero or more representations of a value, each in the form of a value representation • zero or one vocabulary encoding scheme URI • a value representation is either • a value string or • a rich representation • a value string may have an associated value string language • a value string may have an associated syntax encoding scheme URI • a value may be the subject of a related description DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  5. Description Set Description Resource URI Property URI Property URI Value URI Value URI Vocab Enc Scheme URI Vocab Enc Scheme URI Property URI Value string Value string Value string Syntax Enc Scheme URI Syntax Enc Scheme URI Syntax Enc Scheme URI Statement Property URI Property URI Rich representation Rich representation Resource URI Property URI

  6. Why DC-Text? Context & Motivation • DCMI “Encoding Guidelines” specs • Pre-date development of DCAM • Use earlier, simpler “DC abstract models” • Not fully compatible with DCAM description model • Currently, no machine-readable format for full DCAM description model • Updating of specs in progress (2006) • Also, demand for human-readable format • Examples to support discussion of DCAM • Examples in “encoding guidelines” documents • Similar role for N3, Turtle etc for RDF model DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  7. Design Principles • Plain text format • Avoid complexity of XML, XML Namespaces etc • Easily human-readable, human-writable • Suitable for use in e.g. email, Wiki pages • Support full DCAM description model • DC-Text document = single description set • Clear (to human reader) representation of DCAM description model • Conciseness not major consideration • But support useful abbreviation mechanisms where possible DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  8. DC-Text: Syntactic Structure label ( label ( content ) label ( label ( content ) ) ) • label • DescriptionSet • Description • ResourceURI • Statement • PropertyURI • etc • content • label (content) • “literal” • <URI> • prefix:name • language tag • description id/idref DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  9. DescriptionSet ( Description ( ResourceURI ( <http://example.org/page/home> ) Statement ( PropertyURI ( <http://purl.org/dc/elements/1.1/title> ) ValueString ( “My Home Page” Language ( en ) ) ) Statement ( PropertyURI ( <http://purl.org/dc/elements/1.1/creator> ) ValueURI ( <http://example.org/person/fred> ) ) ) Description ( ResourceURI ( <http://example.org/person/fred> ) Statement ( PropertyURI ( <http://xmlns.com/foaf/0.1/knows> ) ValueURI ( <http://example.org/person/tom> ) ) ) )

  10. http://example.org/person/fred @prefix dc <http://purl.org/dc/elements/1.1/> . @prefix foaf <http://xmlns.com/foaf/0.1/> . @prefix page <http://example.org/page/> . @prefix person <http://example.org/person/> . DescriptionSet ( Description ( ResourceURI ( page:home ) Statement ( PropertyURI ( dc:title ) ValueString ( “My Home Page” Language ( en ) ) ) Statement ( PropertyURI ( dc:creator ) ValueURI ( person:fred ) ) ) Description ( ResourceURI ( person:fred ) Statement ( PropertyURI ( foaf:knows ) ValueURI ( person:tom ) ) ) ) URIs abbreviated as Qualified Names

  11. @prefix dc <http://purl.org/dc/elements/1.1/> . @prefix foaf <http://xmlns.com/foaf/0.1/> . @prefix page <http://example.org/page/> . DescriptionSet ( Description ( ResourceURI ( page:home ) Statement ( PropertyURI ( dc:title ) ValueString ( “My Home Page” Language ( en ) ) ) Statement ( PropertyURI ( dc:creator ) DescriptionRef ( fred ) ) ) Description ( DescriptionId ( fred ) Statement ( PropertyURI ( foaf:mbox ) ValueURI ( <mailto:fred@example.org> ) ) ) ) (“Related”) description of value linked by id/idref

  12. Some reflections, issues • Several conventions taken from Turtle (Dave Beckett) • Draft circulated to DCMI Architecture WG (May 2006) • Used for human-readable examples in • DC in XML, DC in RDF drafts • DCMI IEEE LTSC Task Force documents • supporting email discussions • DC-Text as machine-readable format? • BNF provided • Use YAML? • Use JSON? DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

  13. DC-Text: a simple text-based format for DC metadata DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

More Related