SKOS hands-on workshop (tutorial) by Regine Stein

Deutsches Dokumentationszentrum für Kunstgeschichte -gBildarchiv Foto Marburg

Publishing Cultural Collectionswith SKOS and LIDO:with SKOS and LIDO:An Introductory Workshop

Regine Stein

Tel Aviv, Eretz Israel Museum, 11.01.2010

Zina Dizengoff Circle, Genia Averbouch, 1934‐1949, Tel AvivTel Aviv

Foto Marburg, Foto: Bassewitz, Gert von;Aufnahme‐Nr. LAC 44.894; (color); Aufn.‐Datum: 1993

http://www.fotomarburg.dehttp://www bildindex dehttp://www.bildindex.de

• Deutsches Dokumentationszentrum für Kunstgeschichte ‐ Bildarchiv Foto Marburg is a national and international research and service institute, supported by the Philipps University in Marburg.

• Its mission is to collect, index and make available photographs related to European art and architecture, as well as to conduct research on the

2

European art and architecture, as well as to conduct research on the history, practice and theory of how visual cultural assets are passed on.

Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History

The working group

German Museum Association / SIG Documentation

g g p

•DigiCult Schleswig‐Holstein•d:kult Düsseldorf•Bildarchiv Foto Marburg MarburgBildarchiv Foto Marburg, Marburg•Institute for Museum Research, Berlin•Libraries Service Center, Konstanz•Landesmuseum für Technik u. Arbeit Mannheim•Schloss Gottorf•University of Applied Science LeipzigUniversity of Applied Science, Leipzig•Zuse‐Institute Berlin

Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History 3

Workshop Agendap g

1. Introduction: The broad view standards

2. LIDO – Lightweight Information Describing Objects: A harvesting format for providing core data from museum holdingsmuseum holdings

3. SKOS – Simple Knowledge Organization System: A model for expressing the basic structure andA model for expressing the basic structure and content of concept schemes

4. Short presentations by Israel institutions of their4. Short presentations by Israel institutions of their vocabularies

5. Concrete mapping examples to SKOS and LIDO and pp g phow to relate them

6. Closing discussion


Workshop Agendap g


2. LIDO – Lightweight Information Describing Objects: A harvesting format for providing core data frommuseum holdingsmuseum holdings






Motivation: Why care about standards?

The broad view standards

y

• Increasing relevance of internet presence for museums and g pother collections

• Increasing necessity to integrate your data into union• Increasing necessity to integrate your data into union catalogues and portals: facilitate resource discovery in a cross‐collection and even cross‐sectoral (archives, libraries, museums) mannermuseums) manner

• Increasing requests to make your information available for the g q ySemantic Web / Linked Data initiatives


Motivation: Why care about standards?


y

• It’s all about making your information understandable outside f ll d b / h !of your collection database / your home context!

• Need for convenient instruments to provide cultural collectionNeed for convenient instruments to provide cultural collection information– from different collections / object classes– from different data structures– from different software systems

• There are different layers to be considered – Publication / Exchange ProtocolsPublication / Exchange Protocols– Data Structure Standards– Data Content StandardsData Content Standards– Data Value StandardsIntroductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010

Regine Stein, German Documentation Center for Art History 7



httphttpOAI‐PMH…

Publication / Exchange Protocols

CDWA, SpectrumCDWA Lite, museumdat,

Spectrum XML LIDO

Data Structure Standards

Data Format as XML Schema

CIDOC‐CRMprovidesreference

Spectrum XML, LIDO(or possibly as RDF Schema) model

Data ContentCCO

Data Content Standards

AAT I l SKOS idAAT, Iconclass, LCSH, ULAN, …

Data Value Standards

SKOS providesdata model forpublication

8Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History

CIDOC CRM / ISO 21127 in less than a nutshell


CIDOC‐CRM / ISO 21127 in less than a nutshell…

D l d ithi CIDOC th D t ti C itt f• Developed within CIDOC, the Documentation Committee ofthe International Council of Museums (ICOM)

• Is a formal domain ontology for cultural heritage information:− Describes the things that the cultural heritage sector− Describes the things that the cultural heritage sector

deals with and how these things relate to each other− Expressed as an “object‐oriented” schemap j

• Establishs a conceptual basis for integration and access to cultural heritage information: „semantic glue“cultural heritage information: „semantic glue

• See http://www.cidoc‐crm.org/


CIDOC CRM / ISO 21127 in less than a nutshell


CIDOC‐CRM / ISO 21127 in less than a nutshell…

Core Conceptsp

When WhereWhere

WhatWhatWho

Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History 10Events

Source: http://www.cidoc‐crm.org/

CCO C t l i C lt l Obj t


CCO – Cataloguing Cultural Objects

D l d ithi j t f th (N th i ) Vi l• Developed within a project of the (North‐american) Visual Resources Association, CCO:

− is a manual for describing, documenting, and cataloguing cultural works and their visual surrogates.

− intends to inform the decisionmaking processes of cataloguers and builders of cultural heritage systems.

− employs generic concepts that can be used with any metadata element sets. E.g. used in the MARC/AACR

ld f h ib d kworld of The Morgan Library and Museum New York

• See http://www.vrafoundation.org/ccoweb/and particularly Ten Key Principles of CCO


CDWA and CDWA Lite


Categories for the Description of Works of Art

• CDWA describes the content of art databases by articulating a conceptual framework for describing and accessing information about works of art, architecture, other material culture, groups and collections of works, and related images. It includes 532 t i d b t icategories and subcategories.

• CDWA Lite is an XML schema to describe core records for works fof art and material culture based on CDWA and CCO. CDWA Lite

records are intended for contribution to union catalogs and other repositories using the Open Archives Initiative (OAI)other repositories using the Open Archives Initiative (OAI) harvesting protocol.

• See htt // tt d / h/ d ti h/ t d d / d /• See http://www.getty.edu/research/conducting_research/standards/cdwa/Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History 12

S t d S t XML S h


Spectrum and Spectrum XML Schema

• SPECTRUM is the UK and international standard forSPECTRUM is the UK and international standard for Collections Management. It consists of two main sections:

− Procedures− Procedures

− Information requirements

• SPECTRUM XML Schema provides a standard format for exchanging object records between different collections g g jmanagement systems.

I bj i i h h l ld f d iIts objective is the whole world of museum documentation and collection management.

• See http://www.collectionstrust.org.uk/spectrumIntroductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History 14

museumdat


museumdat

It is:

• A harvesting format for providing core data from museumholdingsg

• Technically specified in an XML Schema – current version ofXSD: 1.0 of Oct 2007XSD: 1.0 of Oct 2007Published at http://www.museumdat.org

It is NOT:

• A fully developed data exchange format• A fully developed data exchange format

• A format designed for proper cataloging


From CDWA Lite to museumdat


Challenges I:Challenges I:

• CDWA Lite is very much focused on fine arts: it‘s starting• CDWA Lite is very much focused on fine arts: it s starting point was eventually delivering metadata from an art collection (the Getty museum) to a digital library on art ( y ) g y(ARTstor)

• Need of a format that covers object data of manifold provenance such as cultural history, natural history, history of technology …




Challenges II:Challenges II:

• CDWA Lite is very much focused on north american data• CDWA Lite is very much focused on north american data standards:

– CDWA as data structure standardCDWA as data structure standard

– AAT, TGN, ULAN as data value standards

– CCO as data content standard– CCO as data content standard

• Need of generalizing the scope for further standards and• Need of generalizing the scope for further standards and other languages




WG Data exchange German Museum Association:WG Data exchange, German Museum Association:

• Event oriented approach of CIDOC CRM allows for• Event‐oriented approach of CIDOC‐CRM allows for generalizing the format for use with various object data

• CIDOC‐CRM as ISO standard (ISO 21127) is the reference model – a standard metadata format should be CRMmodel a standard metadata format should be CRM compliant

museumdat is a reconfiguration of CDWA Lite based on CIDOC‐CRM analysis y


And now: LIDO Lightweight Information Describing Objects


Joint effort of the CDWA Lite museumdat and

LIDO – Lightweight Information Describing Objects

Joint effort of the CDWA Lite, museumdat, and Spectrum communities, based on a substantial review process:review process:

• Experiences and feedback after a two‐year period of practical implementation and use of CDWA Lite and museumdat

• Recommendations / results of the CDWA Lite/museumdat Working GroupLite/museumdat Working Group

• Further CIDOC‐CRM analysis

R i t f SPECTRUM• Requirements of SPECTRUM Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History 20

Why not just use Dublin Core?


y j

• Dublin Core, currently the preferred schema for lots of repositories and especially for OAI harvesting, was designed for Web resource discovery.

• It is not appropriate for describing cultural materials because: – its elements are broad and generic, usable for describing a wide range

fof resources

– but are not able to capture in a meaningful manner the semantics of cultural heritage informationg

– instead DC encourages mix‐up of semantically different information in same elements

Unsatisfying retrieval results!


Workshop Agendap g








LIDO Construction principles


• Allow for contributing data and images relating to b

LIDO Construction principles

an object

• Deliver the information in a self‐contained“ wayDeliver the information in a „self contained way

• Few mandatory elements, but semantically rich format

• Include links back to home“ context• Include links back to „home context

• Distinction of display and indexing elements

• Provide references to controlled vocabulary and authoritiesauthorities


LIDO v0 7


LIDO v0.7Descriptive and administrative elements of a LIDO record

‐Events –

Event Set

‐ Object Classifications –

Object / Work Type (mandatory)

‐Relations –

Subject SetClassification‐Object Identifications –

i l / Related Works

‐Administrative Metadata –

Title / Name (mandatory)

Inscriptions

R it / L tiRights

Record (mandatory)

Repository / Location

State / Edition

Obj t D i tiResource

Object Description

Measurements


24

No artist? No creation date? No finding place?


Museum objects may relate to any actor, date, or place in two

No artist? No creation date? No finding place?

ways:

• The object was present at an event (such as creation, find,The object was present at an event (such as creation, find, use, …)‐ having participants / carried out by some actors ‐ at some time ‐ in some place

or

• The object refers to such entity by• The object refers to such entity by‐ depicting it‐ „being about“

25

„ g


Events in LIDOExample: http://www.bildindex.de/obj20144988.html

Event

−Event IdentifierEvent Identifier

−Event Type−Role in Event−Event Name

−Event Actor objectWorkType: Orangerietitle: Oranienburg, Orangerie

−Culture−Event DateE t Pl

eventeventType ModificationeventActor

−Event Place−Event Method

−Materials / Technique

displayActorInRole Johann Conrad SchlaunactorInRole

actornameActor Schlaun, Johann ConradMaterials / Technique

−Thing Present−Event Related

roleActor ArchitekteventDate

earliestDate 1725latestDate 1733

26

−Event DescriptioneventPlace

placenamePlace Nordkirchen (Kreis Lüdinghausen)Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010

Regine Stein, German Documentation Center for Art History

Events in LIDO objectWorkType: Giebelskulpturtitle: Brauträubergruppe (H, I), Fragment

Example: http://www.bildindex.de/obj20322973.html

repositorySetrepositoryName Archäologisches MuseumrepositoryLocation

namePlace OlympianamePlace Olympia

eventeventType EntstehungeventDateeventDate

earliestDate -470latestDate -460

eventPlacedisplayPlace Olympia Zeustempel WestgiebeldisplayPlace Olympia, Zeustempel, Westgiebelplace

namePlace Zeustempel, WestgiebelpartOfPlace

namePlace ZeustempelnamePlace ZeustempelpartOfPlace

namePlace OlympiaeventMaterialsTech

materialsTechmaterialsTechtermMaterialsTech Marmor

eventeventType Fund

27

eventType FundeventPlace

placenamePlace Olympia


Subjects in LIDOLIDO – Lightweight Information Describing Objects

Subject

Example: http://www.bildindex.de/obj07010042.html

Subject

−Extent Subject−Subject Concept

objectWorkType: Druck

subject−Subject Actor−Subject Date

subjectsubjectActordisplayActorJohannes Aventinus

actor−Subject Place−Subject EventSubject Object

ac oactorID

type URL source GNDhttp://d-nb.info/gnd/11850522X−Subject Object p g

nameActorpref preferred

Aventinus, JohannesnameActor

pref alternateThurmair, Johannes

nameActorpref alternate

28

p…

vitalDatesActor 1477-1534Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History

Subjects in LIDOLIDO – Lightweight Information Describing Objects

Allows for full content description of event photographs: Example: http://www.bildindex.de/obj20051303.html

objectWorkType: Reisephotographie

title Richard Hamann auf der Insel Mallorca

subjectsubjectEvent

eventeventType AktivitäteventName

Richard Hamann auf der Insel MallorcaeventActor

nameActor Hamann, RichardeventDate

earliestDate 1932latestDate 1932

Introduct29

eventPlacenamePlace Mallorca

LIDO – who cares about?LIDO – Lightweight Information Describing Objects

“ICOMs International Committee for Documentation, provides the museum community with advice on good practice and developments in museum y g p pdocumentation.”

S b 2009 I l i f hSeptember 2009: Implementation of the newCIDOC Working Group „Data harvesting and interchange“

Chairs:Chairs: Erin Coburn (CDWA Lite Advisory Committee/ Getty Museum)Regine Stein (AG Datenaustausch/ Bildarchiv Foto Marburg)

To become the home for the internationalized, CIDOC‐CRM compliant harvesting format LIDOcompliant harvesting format LIDO


Workshop Agendap g








Background: SKOS – Simple Knowledge Organization System

RDF Resource Description Framework

Introduction to RDF

RDF – Resource Description Framework

• is in essence a simple data model

• is about writing down relations between thingsthings

• is the data format for linked data

See http://www.w3.org/RDF/

The RDF introduction slides (no. 32‐47) are taken from„The thirty minute guide to RDF and Linked Data“, by Ian Davis and Tom Heathhttp://www slideshare net/iandavis/30‐minute‐guide‐to‐rdf‐and‐linked‐data


http://www.slideshare.net/iandavis/30 minute guide to rdf and linked data

Introduction to RDF

SKOS – Simple Knowledge Organization System

What is RDF for?

Introduction to RDF

What is RDF for?

• The web is a global, universal information space for documents

• Can we do the same for data? Make the webCan we do the same for data? Make the web into a database?

RDF is the data format for that databaseRDF is the data format for that database


Source: „The thirty minute guide to RDF and Linked Data“, by Ian Davis and Tom Heath

SKOS Simple Knowledge Organization System



• Is an RDF application

• Developed within W3C – current status: pW3C Recommendation of 18 August 2009

• “Provides a model for expressing the basic structure andProvides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, folksonomies, and other similar types of controlled vocabulary.”

• See homepage at http://www.w3.org/2004/02/skos/See homepage at http://www.w3.org/2004/02/skos/


SKOS Simple Knowledge Organization System



• Its main objective is to enable easy publication of (existing!) controlled structured vocabularies for the Semantic Web.

• Its specific focus is on linking and retrieving data / concepts, not on display / navigation in the whole concept scheme.

• Does not itself specify rules on how to create concept schemes.

Note the difference in scope compared with other KOS standards such as ISO 2788/5964 for monolingual/multilingual thesaurisuch as ISO 2788/5964 for monolingual/multilingual thesauri


Using SKOS concepts can be


Using SKOS, concepts can be

1. identified using URIs

2. labeled with lexical strings in one or more natural languages

3. assigned notations (lexical codes)

4. documented with various types of note

5. linked to other concepts and organized into informal hierarchies and association networks

d h6. aggregated into concept schemes

7. grouped into labeled and/or ordered collections

8. mapped to concepts in other schemes.

Source: SKOS Reference,


see http://www.w3.org/TR/2009/REC‐skos‐reference‐20090818/

AAT record, used as example:


, p

Source: AAT online,


see http://www.getty.edu/research/conducting_research/vocabularies/aat/

1. Identifying the basic entitySKOS – Simple Knowledge Organization System

skos:Concept

• Concepts are the units of thought ‐ ideas, meanings, or categories of objects and events.

T t f id tifi ti• Two steps for identification:– creating (or reusing) a Uniform Resource Identifier (URI) to uniquely

identify the concept.y p

– asserting in RDF, using the property rdf:type, that the resource identified by this URI is of type skos:Concept.

<http://www.getty.edu/AAT/300191324> rdf:type skos:Conceptor, with namespace prefix aat: <http://www.getty.edu/AAT/>

t 300191324 df t k C taat:300191324 rdf:type skos:Concept


2. Lexical labelling:SKOS – Simple Knowledge Organization System

skos:prefLabel, skos:altLabel, skos:hiddenLabel

• labels = Expressions that are used to refer to a concept in natural language

fL b l f d l i l l b l• prefLabel = preferred lexical label

Note: Even though formally not enforced, no two concepts in h h h ld b i h f dthe same concept scheme should be given the same preferred label for any given language tag

aat:300191324 rdf:type skos:Conceptskos:prefLabel „paper money“@en

htt // tt d /AAT/300191324p „p p y

skos:prefLabel „Papiergeld“@de

paper money@enskos:prefLabel

http://www.getty.edu/AAT/300191324

rdf:about

k fL b l


Papiergeld@enskos:prefLabel



• altLabel = alternative lexical label ‐> synonyms, near‐synonyms, abbreviations, acronyms

aat:300191324 rdf:type skos:Conceptskos:prefLabel paper money“@enskos:prefLabel „paper money @enskos:altLabel „bank notes“@enskos:altLabel „banknotes“@enk ltL b l bill ( )“@skos:altLabel „bill (paper money)“@en…




• hiddenLabel = lexical label that is liked to be searchable, but not visible, e.g. misspelled variants

(invented example)aat:300191324 rdf:type skos:Conceptaat:300191324 rdf:type skos:Concept

skos:prefLabel „paper money“@enskos:hiddenLabel „ papermoney“@en


3. Assigning notations:SKOS – Simple Knowledge Organization System

skos:notation

• Some KOS, e.g. classification schemes, use notations as the primary means of access.

N t ti t i ll d f di it t ti i• Notations are typically composed of digits, punctuation signs and other character, thus independent of natural‐language contextscontexts.

E g Iconclass systemE.g. Iconclass systemiconclass:46A132 rdf:type skos:Concept

skos:notation „46 A 13 2“^^IconclassNotation <‐ specific datatype

skos:prefLabel „46 A 13 2“ <‐ no language tag

skos:prefLabel „villagers, villein“@en


4. Documentary notes:SKOS – Simple Knowledge Organization System

skos:note specified inskos:scopeNote, skos:definition,skos:scopeNote, skos:definition, skos:example, skos:historyNote

• Human readable documentation of the concept• Human‐readable documentation of the concept

aat:300191324 rdf:type skos:Conceptaat:300191324 rdf:type skos:Conceptskos:prefLabel „paper money“@enskos:scopeNote „Officially circulating media of exchange…“@en


5. Semantic relationships:SKOS – Simple Knowledge Organization System

skos:broader, skos:narrower, skos:related

• broader = has broader conceptnarrower = has narrower concept

Th ti h th ’ i• These properties are each other’s inverse.

• But NOT defined as generally transitive.

paper money@en

money@en

skos:prefLabel

paper money@en

skos:prefLabelhttp://www.getty.edu/AAT/300191324

rdf:about„Officially circulating

di f hskos:scopeNoteskos:broadermoney


media of exchange manufactured from

paper;“@en

skos:scopeNoteskos:broader

skos:narrower

…...paper money


5. Semantic relationships:SKOS – Simple Knowledge Organization System

skos:broader, skos:narrower, skos:related

• related: asserts an associative relationship between two concepts

NOT d fi d t iti t• NOT defined as transitive property.

• skos:related is disjoint from skos:broader/skos:narrower

ex:birds rdf:type skos:Conceptskos:prefLabel “birds”@enskos:prefLabel birds @enskos:related ex:ornithology

ex:ornithology rdf:type skos:Conceptk fL b l “ ith l ”@skos:prefLabel “ornithology”@en


6. Aggregation in Concept Schemes:


gg g pskos:ConceptSchemeskos:inScheme skos:hasTopConceptskos:inScheme, skos:hasTopConcept

• Usually concepts are not used as stand‐alone entities, but come i il d b l i k hin compiled vocabularies ‐> skos:ConceptScheme.

• SKOS offers no specific support for creating, but focuses on p blication of e isting concept schemespublication of existing concept schemes.

aat:AAT rdf:type skos:ConceptSchemed t titl “A t & A hit t Th ”@dct:title “Art & Architecture Thesaurus”@enskos:hasTopConcept aat:300037316 <‐ entry point to vocabulary

…

aat:300037316 rdf:type skos:Conceptskos:prefLabel “money”@enskos:inScheme aat:AAT


7. Grouping into collections


p g

AAT data is structuredAAT‐data is structuredin four typesAAT:Facet skos:CollectionAAT Hi h N k C ll iAAT:Hierarchy Name skos:CollectionAAT:Guide Term skos:CollectionAAT:Concept skos:Concept


7. Grouping into collections:


p gskos:Collection, skos:OrderedCollectionskos:member skos:memberListskos:member, skos:memberList

• Since such structures like node labels do not represent a label for i i i h ifi i i b i d da concept in its own right, specific entities are to be introduced

money@en

k fL b l

AAT-Concept Schemeskos:Concept

paper money@en

k fL b l

money by material@enskos:prefLabelrdfs:label

skos:prefLabel skos:Conceptskos:Collection

skos:prefLabelhttp://www.getty.edu/AAT/300191324

rdf:about„Officially circulating media of exchange manufactured from

paper;“@en

skos:scopeNote

skos:member

skos:broadermoney…<money by material>…...paper money


paper; @en

skos:narrower

Source: Axel Vitzthum / digiCULT


Source: Axel Vitzthum / digiCULT ‐http://www.digicult‐sh.de/

8. Mapping Concept Schemes:


pp g pskos:exactMatch, skos:closeMatch, skos:broadMatch skos:narrowMatchskos:broadMatch, skos:narrowMatch

• Allows for statements that two concepts from different h h bl iconcept schemes have comparable meanings.

• Conceptual mappings are expected to be a key advantage of making KOSs available on the Semantic Web using SKOS.

• Useful for retrieving data repositories / union catalogues thatUseful for retrieving data repositories / union catalogues that integrate data from different sources – which use multiple, but conceptually overlapping KOSs.


8 Mapping Concept Schemes:


8. Mapping Concept Schemes:



SKOS XL: SKOS eXtension for Labels


SKOS‐XL: SKOS eXtension for Labels

• This extension provides additional support for identifying, describing and linking lexical entities.

• See SKOS reference, Appendix B: http://www.w3.org/TR/2009/REC‐skos‐reference‐20090818/# l20090818/#xl


SKOS – limits


SKOS – limits

Attention with using SKOS for authority files! – Why?Attention with using SKOS for authority files! Why?

• Authority files deal only with labeling properties, usually not ith ti l ti hi b t th d ib d titiwith semantic relationships between the described entities.

• Authority files often deal with particulars / individuals – e.g. real persons, and not with concepts.

• SKOS vocabulary does not apply as a whole for particulars: y pp y pE.g. there are no broader/narrower relationships between persons.

Analyze carefully which is the appropriate vocabulary!

For real persons applies the FOAF – Friends of a Friend vocabulary.For real persons applies the FOAF Friends of a Friend vocabulary.See http://www.foaf‐project.org/docs


SKOS applications

SKOS applications

SKOS applications

• For general information see SKOS homepage athttp://www.w3.org/2004/02/skos/

• Also the SKOS resources athttp://wwwminervaisrael org il/s558 htmlhttp://www.minervaisrael.org.il/s558.html


museumsvokabular.deSKOS applications

An initiative within the German Museum Association

68Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010

Regine Stein, German Documentation Center for Art History

museumsvokabular.de –SKOS applications

museumvok ‐ format for describing controlled vocabularies

museumvok Webservices

Based on SKOS, with further refinements.

Ne ersion c rrentl nder de elopmentNew version currently under development.

in Discussion:

• Metadata for concept scheme (dc:identifier, dc:contributor, dc:creator, dcterms:created, dcterms:modified, dc:description, dc:format, dc:language, dc:rights, dc:subject, dc:title, ?)

• new: museumvok:Collection

• change museumvok:memberOfCollection tok bmuseumvok:member

• merge museumvok:prefTerm, museumvok:altTerm tomuseumvok:Term

• identifier for Terms

• notes for Terms• notes for Terms

• multiple sources for Terms

• multiple sources for notes

• mappingRelation, subproperties: closeMatch, exactMatch, broadMatch narrowMatch and relatedMatchbroadMatch, narrowMatch and relatedMatch

• rename museumvok:equivRelationship tomuseumvok:mappingRelationship

• museumvok:definition as sub‐property of museumvok:noteIntroductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History 69

SKOS applications

Includesmuseumvok XML

and SKOS RDF/XML

SKOS applications

museumsvokabular.de –museumvok Webservices

Basic definitions:

• Web Service

„The W3C defines a Web service (…) as a software system designed to supportinteroperable Machine to Machine interaction over a network. (…) “

• SOAP

( ) is a protocol for exchanging XML‐based messages over computer„(…) is a protocol for exchanging XML‐based messages over computernetworks, normally using HTTP/HTTPS. (…)“

Source: http://en.wikipedia.org/wiki/Web_serviceshttp://en.wikipedia.org/wiki/SOAP


SKOS applications

museumsvokabular.de –

3 l f i d fi d i SOAP W b i

museumvok Webservices

3 central functions defined in a SOAP Webservice

• searchConceptsById:• searchConceptsById: retrieves for every ID from a given list the pertainingconcepts

• searchConceptsByTerm: retrieves for every term from a given list the pertainingy g p gconcepts

• fetchHierarchy:• fetchHierarchy: provides for a given ID the requested „tree“ of thehierarchy. Depth of search and direction of search areparameterised.


SKOS applications

Implemented in several museumImplemented in several museum documentation systems. Currently some extensions are being implemented


being implemented.For technical information see www.museumsvokabular.de

Connecting the „Bildindex“ with AAT through museumvok ws

SKOS applications

through museumvok‐ws

alternatively: S OS ( / )

<classification><conceptID museumdat:type="URL">

htt // t k b l d /300041365

SKOS (RDF/XML)

http://aat.museumsvokabular.de/300041365</conceptID><conceptID museumdat:type="local"

museumdat:source="http://www.getty.edu/research/conducting_research/vocabularies/aat/">Etchings (prints)

</conceptID><term museumdat:pref="preferred" xml:lang="en">

Etchings (prints)</term><term museumdat:pref="preferred" xml:lang="de">term museumdat:pref preferred xml:lang de

Druckgraphik</term>

</classification>

Or through any other webservice to any th t ll d b l I l

SKOS applications

other controlled vocabulary, e.g. Iconclass

<subject>< tID d t t "URL">htt //i l / /44G1231</ tID>

Source: Bert Degenhart Drenth, Using Webservices for Terminology Control (CIDOC Annual Meeting 2008 Athens)

<conceptID museumdat:type="URL">http://iconclass.org/sw/44G1231</conceptID><term museumdat:pref="preferred”>44 G 12 3</term><term museumdat:pref="preferred” xml:lang=“en”>market cross</term></subject>

museumvok Webservices: Demo applicationSKOS applications

See http://museum.zib.de/museumsvokabular/index.php?main=demo‐sgml


Workshop Agendap g








Mapping example to SKOSMapping examples

pp g p

Icebox@en

Lexicondct:title

Kitchenware / culinary

equipment & accessoires@

en

skos:prefLabelskos:Conceptskos:ConceptScheme

skos:inSchemeIcebox@en

skos:prefLabelhttp://www.example.org.il/Lexicon/T16924

rdf:about

skos:broader

skos:inScheme

חרק זגרא @heskos:prefLabel

skos:broader

skos:narrower


Mapping example to LIDOMapping examples

See http://www.imj.org.il/imagine/item.asp?itemNum=194552http://www.imj.org.il/imagine


Mapping example to LIDOS htt //j l h ji il/dl/k t bb t/ht l/k0460 ht

Mapping examples

See http://jnul.huji.ac.il/dl/ketubbot/html/k0460.htm


Mapping example to LIDO// / /

Mapping examples

Object Work TypeKragenflasche

See http://www.museen‐sh.de/ml/digi_einzBild.php?pi=1300_temp47861

dating of Production -4000 - -2800

Period NameNeolithic

Find spotCemetery Ohlsdorf (Hamburg)(Hamburg)

FinderCemetery staff

CultureFunnelbeaker culture



Mapping examples

Mapping example to LIDO



Linking mechanism to vocabularies and th iti Id tifi i LIDOauthorities: Identifier in LIDO

•Each element referencing anotheri i l d id ifi lentity includes an identifier element

•Main Entities: − Thing− Event− Actor− Place− Concept

•Identifiers are repeatable

Example:

<subject>

84

<conceptID museumdat:type="URL">http://iconclass.org/sw/44G1231</conceptID><term museumdat:pref="preferred”>villagers, villein</term></subject>Introductory Workshop on SKOS and LIDO – Tel Aviv 11.01.2010 Regine Stein, German Documentation Center for Art History

LIDO elements linking to concepts (= skos:concept)( skos:concept)

• Object Type• Classification

• Event Type*• Culture

• Subject

• Role Actor• Materials / Technique

* To be based on CIDOC‐CRM Subclasses of E5

Event


Connecting Data Repositories withT i l S iTerminology Services

Terminology Web Service e.g. museumvok-wsRepositoryLocal User

http, (X)HTMLgRepositoryLocal User

http, [SOAP,REST], RDF/XML

[[htt ] OAI PMH XMPP[[http], OAI-PMH, XMPP, SRU/SRW], XML

Museum IMuseum II..Museum V Used Format:

e.g. museumvok/SKOS

Museum V..

Used Format:museumdat/LIDO

Workshop Agendap g








Summarizing…

• LIDO and SKOS/museumvok provide a practical mechanism for publishing collection information and connecting data

g

publishing collection information and connecting data repositories with terminology services

• Designed for use with “Non‐Semantic Web‐Experts” based on SKOS and CIDOC‐CRM

• Thus bridging a gap and linking back to museum documentation practice:

Use controlled vocabularies!

Publish them with SKOS if appropriate! ub s e S OS app op a e

Refer your documentation to CIDOC‐CRM!


Deutsches Dokumentationszentrum für Kunstgeschichte -gBildarchiv Foto Marburg

Thank you for your attention!

Regine Stein

German Documentation Center for Art History ‐Art History Bildarchiv Foto Marburg

German Museum Association, Documentation CommitteeHaus Braun‐Rabinski, Josef Berlin, 1932‐1933,

Tel Aviv, Rothschild Boulevard 82

Email: [email protected] Marburg, Foto: Bassewitz, Gert von;Aufnahme‐Nr. LAC 44.958; (color); Aufn.‐Datum: 1993;Fotoinhalt: Fenster des Treppenhauses

SKOS hands-on workshop (tutorial) by Regine Stein

Documents

Transcript of SKOS hands-on workshop (tutorial) by Regine Stein