Your SlideShare is downloading. ×
0
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
DC-Text: a simple text-based format for DC metadata
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

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

1,852

Published on

A description of DC-Text, a text format for the representation of DC metadata description sets. …

A description of DC-Text, a text format for the representation of DC metadata description sets.

Short paper presented to DC-2006 Conference, Manzanillo, Colima, Mexico on 3 October 2006.

Published in: Business, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,852
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
46
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Eduserv Foundation established in July 2003 mission to support the effective application of information and communication technology in education largely achieved thru external grant making activities to date desire to develop in-house resource, developing standards, specifications, demonstrators – software and services
  • 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 <ul><li>Context & motivation </li></ul><ul><ul><li>DCMI Abstract Model </li></ul></ul><ul><ul><li>DCMI “encoding guidelines” </li></ul></ul><ul><li>DC-Text </li></ul><ul><ul><li>Basic structure </li></ul></ul><ul><ul><li>Features </li></ul></ul><ul><li>Some reflections, issues still to be discussed </li></ul>
    • 3. Why DC-Text? Context & Motivation <ul><li>Historical separation of DC description model from representation/encoding </li></ul><ul><ul><li>“ Grammatical Principles” v “Encoding Guidelines” </li></ul></ul><ul><li>Formalised in development of DCMI Abstract Model </li></ul><ul><ul><li>DCMI Recommendation March 2005 </li></ul></ul><ul><li>DCAM describes </li></ul><ul><ul><li>Components and constructs that make up an information structure (“DC description set”) </li></ul></ul><ul><ul><li>How that information structure is to be interpreted </li></ul></ul><ul><li>DCAM does not describe how to represent a DC description set in concrete form </li></ul>
    • 4. DCAM Description Model <ul><li>a description set is made up of one or more descriptions </li></ul><ul><li>a description is made up of </li></ul><ul><ul><li>zero or one resource URI and </li></ul></ul><ul><ul><li>one or more statements </li></ul></ul><ul><li>a statement is made up of </li></ul><ul><ul><li>exactly one property URI and </li></ul></ul><ul><ul><li>zero or one reference to a value in the form of a value URI </li></ul></ul><ul><ul><li>zero or more representations of a value, each in the form of a value representation </li></ul></ul><ul><ul><li>zero or one vocabulary encoding scheme URI </li></ul></ul><ul><li>a value representation is either </li></ul><ul><ul><li>a value string or </li></ul></ul><ul><ul><li>a rich representation </li></ul></ul><ul><li>a value string may have an associated value string language </li></ul><ul><li>a value string may have an associated syntax encoding scheme URI </li></ul><ul><li>a value may be the subject of a related description </li></ul>
    • 5. Resource URI Property URI Rich representation Property URI Value URI Vocab Enc Scheme URI Property URI Value string Syntax Enc Scheme URI Value string Syntax Enc Scheme URI Resource URI Property URI Rich representation Property URI Value URI Vocab Enc Scheme URI Property URI Value string Syntax Enc Scheme URI Statement Description Description Set
    • 6. Why DC-Text? Context & Motivation <ul><li>DCMI “Encoding Guidelines” specs </li></ul><ul><ul><li>Pre-date development of DCAM </li></ul></ul><ul><ul><li>Use earlier, simpler “DC abstract models” </li></ul></ul><ul><ul><li>Not fully compatible with DCAM description model </li></ul></ul><ul><li>Currently, no machine-readable format for full DCAM description model </li></ul><ul><ul><li>Updating of specs in progress (2006) </li></ul></ul><ul><li>Also, demand for human-readable format </li></ul><ul><ul><li>Examples to support discussion of DCAM </li></ul></ul><ul><ul><li>Examples in “encoding guidelines” documents </li></ul></ul><ul><li>Similar role for N3, Turtle etc for RDF model </li></ul>
    • 7. Design Principles <ul><li>Plain text format </li></ul><ul><li>Avoid complexity of XML, XML Namespaces etc </li></ul><ul><li>Easily human-readable, human-writable </li></ul><ul><ul><li>Suitable for use in e.g. email, Wiki pages </li></ul></ul><ul><li>Support full DCAM description model </li></ul><ul><li>DC-Text document = single description set </li></ul><ul><li>Clear (to human reader) representation of DCAM description model </li></ul><ul><li>Conciseness not major consideration </li></ul><ul><ul><li>But support useful abbreviation mechanisms where possible </li></ul></ul>
    • 8. DC-Text: Syntactic Structure <ul><li>label </li></ul><ul><ul><li>DescriptionSet </li></ul></ul><ul><ul><li>Description </li></ul></ul><ul><ul><li>ResourceURI </li></ul></ul><ul><ul><li>Statement </li></ul></ul><ul><ul><li>PropertyURI </li></ul></ul><ul><ul><li>etc </li></ul></ul>label ( label ( content ) label ( label ( content ) ) ) <ul><li>content </li></ul><ul><ul><li>label (content) </li></ul></ul><ul><ul><li>“ literal” </li></ul></ul><ul><ul><li><URI> </li></ul></ul><ul><ul><li>prefix:name </li></ul></ul><ul><ul><li>language tag </li></ul></ul><ul><ul><li>description id/idref </li></ul></ul>
    • 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. @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 http://example.org/person/fred
    • 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 <ul><li>Several conventions taken from Turtle (Dave Beckett) </li></ul><ul><li>Draft circulated to DCMI Architecture WG (May 2006) </li></ul><ul><li>Used for human-readable examples in </li></ul><ul><ul><li>DC in XML, DC in RDF drafts </li></ul></ul><ul><ul><li>DCMI IEEE LTSC Task Force documents </li></ul></ul><ul><ul><li>supporting email discussions </li></ul></ul><ul><li>DC-Text as machine-readable format? </li></ul><ul><ul><li>BNF provided </li></ul></ul><ul><ul><li>Use YAML? </li></ul></ul><ul><ul><li>Use JSON? </li></ul></ul>
    • 13. DC-Text: a simple text-based format for DC metadata DC-2006: Metadata for Knowledge & Learning, Manzanillo, Mexico

    ×