Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Applying a Dublin Core application profile to the digital Pina Bausch archive for ontology population management and data presentation purposes

SWIB14
December 02, 2014

Applying a Dublin Core application profile to the digital Pina Bausch archive for ontology population management and data presentation purposes

Authors: Kerstin Diwisch / Bernhard Thull (Hochschule Darmstadt, Germany)

Abstract:
In recent years, it has become common practice in Linked Data application development to utilize application profiles for describing and constraining metadata and structure of these applications. Description Set Profiles (DSP), as proposed by the Dublin Core Metadata Initiative (DCMI) as a means of machine readable formalizations of application profiles, take this development into account. However, even with the use of application profiles, Linked Data application developers are still left with challenges concerning data input or presentation of data, especially for large datasets. An example of a large dataset is the digital Pina Bausch archive which is realized as a Linked Data archive containing data on diverse materials such as manuscripts, choreography notes, programmes, photographs, posters, drawings and videos related to Pina Bausch’s work, adding up to about 20 million triples. To address this topic, we developed and implemented a Description Set Profile in RDF containing metadata structure and constraints for the Pina Bausch archive ontology. Initially, the DSP was mostly used as a controller for an interactive form-based data editor. In the course of the project, we enhanced the DSP with information about frontend data presentation in a form that by now, it is not only used for controlling the data input flow but also as part of a controller for our archive browser. In this talk, we will provide an insight into the development of the DSP and discuss the approach.

SWIB14

December 02, 2014
Tweet

More Decks by SWIB14

Other Decks in Technology

Transcript

  1. A Dublin Core Application Profile
    for the digital Pina Bausch Archive
    Kerstin Diwisch
    Bernhard Thull

    View Slide

  2. The digital archive
    • Why an archive?
    – Pina Bausch had already started to
    archive her work
    – Formation of the Pina Bausch Foundation
    – Aim: create a digital archive for
    • restaging of plays
    • scientific purposes
    • facilitate access to the public
    Dec-02 2

    View Slide

  3. The digital archive
    Dec-02 3

    View Slide

  4. The digital archive
    Dec-02 4
    • 600 persons
    • 54 plays
    • 3.010 scenes
    • 68 different sequences
    • 3.096 performances
    • 31.969 objects
    • 606 programmes
    • 3.300 videos
    • 26.959 photographs
    • 2.838 costumes
    • 79 props
    • 355 venues in 162 cities and 46 countries
    • 37 shared memories

    View Slide

  5. Reuse of vocabularies
    Vocabulary URL
    FRBR http://purl.org/vocab/frbr/core#
    SKOS http://www.w3.org/2004/02/skos/core#
    FOAF http://xmlns.com/foaf/0.1/
    WGS84 Geo
    Positioning
    http://www.w3.org/2003/01/geo/wgs84_pos#
    Dublin Core http://purl.org/dc/elements/1.1/,
    http://purl.org/dc/terms/
    Media http://purl.org/media#
    Places http://purl.org/ontology/places#
    Event http://purl.org/NET/c4dm/event.owl#
    Timeline http://purl.org/NET/c4dm/timeline.owl#
    Dec-02 5

    View Slide

  6. Software architecture
    Dec-02 6

    View Slide

  7. Why a Dublin Core
    Application Profile?
    • Strict distinction between the actual
    data and the data constraints
    • Whole package and guidelines for an
    application profile
    Dec-02 7 Source: http://dublincore.org/documents/2008/01/14/singapore-framework/singapore-framework.png

    View Slide

  8. DSP
    Dec-02 8 Source: http://dublincore.org/moinmoin-wiki-archive/architecturewiki/pages/DescriptionSetProfile_files/DescriptionSetProfile.png
    _:descriptionTemplate_paperPrint a
    dsp:DescriptionTemplate
    dsp:standalone "false";
    dsp:minOccur "0";
    dsp:maxOccur "Infinity";
    dsp:resourceClass pbao:PaperPrint;
    dsp:statementTemplate
    _:litST_labelOriginal,
    _:nonlitST_exemplarOfPhoto,
    _:litST_description,
    _:litST_identifier,
    _:nonlitST_reproductionOf,
    _:litST_inscription,
    _:litST_originalLocation,
    _:litST_preservationNote,
    _:litST_sourceNote .

    View Slide

  9. DSP
    Dec-02 9 Source: http://dublincore.org/moinmoin-wiki-archive/architecturewiki/pages/DescriptionSetProfile_files/DescriptionSetProfile.png
    _:litST_homepage a
    dsp:LiteralStatementTemplate;
    dsp:minOccur "0";
    dsp:maxOccur „Infinity";
    dsp:property foaf:homepage;
    dsp:literalConstraint
    _:urlConstraint;
    rdfs:label "Webseite"@de,
    "Website"@en.

    View Slide

  10. DSP
    Dec-02 10 Source: http://dublincore.org/moinmoin-wiki-archive/architecturewiki/pages/DescriptionSetProfile_files/DescriptionSetProfile.png
    _:manifestationConstraint a
    dsp:NonLiteralConstraint;
    dsp:valueClass
    frbr:Manifestation.

    View Slide

  11. Why extend the DSP?
    Dec-02 11

    View Slide

  12. Why extend the DSP?
    Dec-02 12

    View Slide

  13. Extended DSP
    Dec-02 13

    View Slide

  14. Usage scenario:
    Archiving a video file
    Dec-02 14

    View Slide

  15. Usage scenario:
    Archiving a video file
    Dec-02
    _:descriptionTemplate_video
    a :EditDescriptionTemplate;
    dsp:minOccur "0";
    dsp:maxOccur "Infinity";
    dsp:resourceClass pbao:Video;
    dsp:statementTemplate
    _:litST_title,
    _:litST_mediaPosition,
    _:nonlitST_depicts,
    _:nonlitST_embodimentPerformance.
    15

    View Slide

  16. Usage scenario:
    Archiving a video file
    Dec-02 16

    View Slide

  17. Usage scenario:
    Archiving a video file
    Dec-02 17

    View Slide

  18. Usage scenario:
    Archiving a video file
    Dec-02 18
    _:nonlitST_depicts a
    dsp:NonLiteralStatementTemplate;
    dsp:property pbao:depicts;
    dsp:nonLiteralConstraint
    _:depictedPersonConstraint.
    _:depictedPersonConstraint a
    dsp:NonLiteralConstraint;
    dsp:descriptionTemplateRef
    _:descriptionTemplate_depicts_persons.
    _:descriptionTemplate_depicts_persons
    a dsp:DescriptionTemplate ;
    dsp:resourceClass rdf:Seq;
    dsp:statementTemplate
    _:nonlitST_li_persons .

    View Slide

  19. Usage scenario:
    Displaying a resource
    Dec-02 19

    View Slide

  20. Usage scenario:
    Displaying a resource
    Dec-02 20

    View Slide

  21. Usage scenario:
    Displaying a resource
    Dec-02 21

    View Slide

  22. Conclusion and outlook
    • DCAP with a machine-readable DSP is
    a viable way for data mapping and
    data format validation
    • Needed: Editor for the DSP
    • View templates?
    • Waiting for a W3C recommendation
    Dec-02 22

    View Slide

  23. Thank you!

    View Slide