Mapping LIDO v0.7 to CIDOC-CRM v5.0.1
Maria Koutraki , Martin Doerr
Institute of Computer Science, FORTH-ICS
P.O. Box 1385, GR 71110, Heraklion, Crete, Greece
{kutraki, martin}@ics.forth.gr
Working paper, ICS-FORTH, March 2010
The need to describe an extremely heterogeneous environment in the Cultural
Heritage area and more specifically in the museum sector, led to the emergence of
several metadata schemata. To a certain degree museums expose minimal metadata
in Dublin Core. However, satisfactory museum metadata are very complex, and a
general agreement has been made in the form of the CIDOC CRM (ISO21127:2006),
which declares rich common semantics of metadata elements in an RDF compatible
form, but does not, by itself, prescribe the use of any fields. CIDOC-CRM is a formal
ontology that defines cultural heritage documentation concepts and the relationships
between those concepts, and it is intended to facilitate the integration, mediation and
interchange of heterogeneous cultural heritage information [www.cidoc-crm.org].
Only recently, most important international stakeholders in the museum sector have
agreed on an explicit format for harvesting museum data, called LIDO (Lightweight
Information Describing Objects). It is CRM compatible and is already underpinned by
the production of large data sets in this format by the European Project ATHENA
[www.athenaeurope.org/getFile.php?id=535].
This document defines a mapping from LIDO v0.7 to CIDOC-CRM v5.0.1. The
mapping of the two models is defined as a sufficient specification to transform each
instance of the source model into an instance of the target model with the same
meaning. In this case, we regard LIDO as the source model while CIDOC-CRM is the
target model. LIDO contains many elements that are categorized in two basic
categories, the Descriptive Metadata and the Administrative Metadata. These
elements contain the information about the object which is described. Each of these
elements and sub-elements of LIDO, are mapped in one or more triples in CIDOCCRM. For example the first LIDO element “RecID” is mapped as the triple: “E19
Physical Object P70 is documented in E31 Document”. “E19 Physical Object” is a
CIDOC-CRM Domain class, “P70 is documented in” is a CIDOC-CRM property and
“E31 Document” is a CIDOC-CRM Range class.
Identifier
1) RecID
P70 is documented in
E19 Physical Object
E31 Document
Category
2) Category
P2 has type
E19 Physical Object
E55 Type
1
Descriptive Metadata
Object Classification Wrap
3)
Object Work Type/term
P2 has type
E19 Physical Object
E55 Type
4) Object Work Type/conceptID
P48 has preferred identifier
E19 Physical Object
E42 Identifier
5) Classification/term
P2 has type
E19 Physical Object
E55 Type
6) Classification/conceptID
P48 has preferred identifier
E19 Physical Object
E42 Identifier
Object Identification Wrap
7) TitleSet/appelationValue
P1 identified by
E19 Physical Object
E41 Appellation
8) TitleSet/sourceAppellation
P3 has note
E19 Physical Object
9) Inscriptions
E62 String
P65 shows visual item
E19 Physical Object
E36 Visual Item
10) Repository Name/Legal Body ID
P50 has current
keeper
E19 Physical Object
2
E39 Actor
P48 has
preferred
identifier
E42 Identifier
11) Repository Name/ Legal Body Name/Appellation Value
P131 is identified by
E39 Actor
E82 Actor Appellation
12) Repository Name/ Legal Body Weblink
E55 Type
“web resource”
P2 has type
P129B is subject of
E39 Actor
E73 Information Object
13) Repository Location / Name Place Set/Appellation Value
E19 Physical Object
P87 is
identified by
P55 has current
location
E53 Place
E44 Place
Appellation
14) Repository Location / Name Place Set/sourceAppellation
P3 has note
E19 Physical Object
E62 String
15) Repository Location / Place ID
P48 has preferred identifier
E53 Place
E42 Identifier
16) Repository Location/Part of Place
P88 consists of
E53 Place
E53 Place
17) Repository Location/Place Classification/term
P2 has type
E53 Place
E55 Type
3
18) Display State
P3 has note
E19 Physical Object
E62 String
19) Display Edition
P3 has note
E62 String
E19 Physical Object
20) Source Display State Edition
P3 has note
E19 Physical Object
E62 String
21) Descriptive Note Value
P3 has note
E62 String
E19 Physical Object
22) Source Descriptive Note
P3 has note
E62 String
E19 Physical Object
23) Display Object Measurements
P3 has note
E62 String
E19 Physical Object
24) Measurements Set
P43 has dimension
E19 Physical Object
E54 Dimension
25) Extent Measurements
P3 has note
E62 String
E19 Physical Object
26) Qualifier Measurements
P3 has note
E19 Physical Object
E62 String
27) Format Measurements
P2 has type
P2 has type
E54 Dimension
4
E55 Type
E55 Type
“Format”
28) Shape Measurements
P2 has type
E55 Type
“Shape”
P2 has type
E55 Type
E54 Dimension
29) Scale Measurements
P2 has type
E55 Type
“Scale”
P2 has type
E55 Type
E54 Dimension
Event Wrap
30) Display Event
P3 has note
E19 Physical Object
E62 String
31) Event Type/term
E19 Physical Object
P12B was present
at
P2 has type
E5 Event
E55 Type
32) Event Type (condition =” Herstellung” (Production))
P12B was present at
E12 Production
E19 Physical Object
33) Event ID
P48 has preferred identifier
E5 Event
E42 Identifier
34) Role in Event/term
P3 has note
E5 Event
E62 String
35) Role in Event/conceptID
5
P48 has preferred identifier
E5 Event
E42 Identifier
36) Event Name/Appellation Value
P1 is identified by
E41 Appellation
E5 Event
37) Event Name/sourceAppellation
P3 has note
E5 Event
E62 String
38) Display Actor in Role
P3 has note
E5 Event
E62 String
39) Name Actor / Appelation Value
P113 is identified
by
P11 had participant
E5 Event
E39 Actor
E82 Actor
Appelation
40) Name Actor / sourceAppelation
P3 has note
E39 Event
E62 String
41) Actor ID
P48 has preferred identifier
E39 Actor
E42 Identifier
42) Nationality Actor/term
P107 is current or former member of
E39 Actor
E74 Group
43) Nationality Actor/conceptID
P48 has preferred identifier
E39 Actor
E42 Identifier
44) Vital Dates Actor
P11B participated
in
E39 Actor
P4 has time span
E5 Event
E52 Time Span
P2 has type
6
E55 Type
“Existance”
45) Gender Actor
P2 has type
E39 Actor
E55 Type
46) Role Actor/term
P3 has note
E5 Event
E62 String
47) Attribution Qualifier Actor
P3 has note
E5 Event
E62 String
48) Extent Actor
P3 has note
E5 Event
E62 String
49) Culture/term
P10 falls within
E4 Period
E5 Event
50) Display Date
P3 has note
E5 Event
E62 String
51) Earliest Date
E5 Event
P4 has time
span
P79 beginning is
qualified by
52) Latest Date
E5 Event
P4 has time
span
E62 String
E52 Time Span
P80 end is qualified
by
E52 Time Span
E62 String
53) Period Name/term
P4 has time-span
E52 Time Span
E4 Period
54) Display Place
P3 has note
E5 Event
E62 String
7
55) Name Place set / Appellation value
P7 took place
at
P87 is identified by
E5 Event
E53 Place
E44 Place
Appellation
56) Name Place set /sourceAppellation
P3 has note
E5 Event
E62 String
57) Part Of Place
P88 consists of
E53 Place
E53 Place
58) Place Classification/term
P2 has type
59) Place ID
E53 Place
P48 has preferred identifier
E53 Place
60) Event Method/term
E55 Type
E42 Identifier
P32 used general technique
E55 Type
E5 Event
61) Display Materials Tech
P3 has note
E5 Event
E62 String
62) Term Materials Tech/term
P32 used general technique
E55 Type
E5 Event
63) Extent Materials Tech
P3 has note
E5 Event
E62 String
64) Source Materials
P71B is listed in
E32 Authority Document
E55 Type
8
65) Descriptive Note Value
P3 has note
E5 Event
E62 String
66) Source Descriptive Note
P3 has note
E5 Event
E62 String
Object Relational Wrap
67) Display Subject
P3 has note
E62 String
E19 Physical Object
68) Extent Subject
P3 has note
E62 String
E19 Physical Object
69) Subject Concept/ Concept ID
P48 has preferred identifier
E19 Physical Object
E42 Identifier
70) Subject Concept/term
P3 has note
E19 Physical Object
E62 String
71) Subject Actor/Display Actor
E19 Physical
Object
P67 refers to
E73 Information
Object
P129 is about
E39 Actor
72) Subject Date/Display Date
E19 Physical
Object
P67 refers to
E73 Information
Object
P129 is about
E50 Date
73) Subject Event/Display Event
E19 Physical
Object
P67 refers to
E73 Information
Object
9
P129 is about
E5 Event
74) Subject Place/Display Place
P67 refers to
E19 Physical
Object
E73 Information
Object
P129 is about
E53 Place
75) Subject Object
P67 refers to
E19 Physical
Object
76) Display Object
E73 Information
Object
P129 is about
E18 Physical
Thing
P3 has note
E62 String
E19 Physical Object
77) Object Web Resource
P67 is referred
to by
E19 Physical
Object
E73 Information
Object
P48 has preferred
identifier
E42 Identifier
78) Object ID
P67 refers to
E18 Physical
Thing
E19 Physical
Object
P48 has preferred
identifier
E42 Identifier
79) Object Note
P3 has note
E62 String
E18 Physical Thing
80) Related WorkRel Type
P46 forms part
of
E19 Physical
Object
P3 has note
E18 Physical
Thing
E62 String
Administrative Metadata
Rights Work Wrap
81) Rights Type
P104 is subject
to
E19 Physical
Object
P2 has type
E30 Right
82) Rights Date/ earliest Date
10
E55 Type
P3 has note
E30 Right
E62 String
83) Rights Date/ latest Date
P3 has note
E62 String
E30 Right
84) Rights Date/ Period Name/term
P3 has note
E30 Right
E62 String
85) Rights Holder/Legal Body ID
P75B is
possessed by
E30 Right
P48 has preferred
identifier
E39 Actor
E42 Identifier
86) Rights Holder/Legal Body Name/Appellation Value
P131 is identified by
E39 Actor
E82 Actor Appellation
87) Rights Holder/Legal Body Web link
E55 Type
“web resource”
P2 has type
P129B is subject of
E39 Actor
E73 Information Object
88) Credit Line
P3 has note
E62 String
E30 Right
Record Wrap
89) Record ID
P70B is
documented in
E19 Physical
Object
E31 Document
P48 has
preferred
identifier
E42 Identifier
90) Record Type
P2 has type
E31 Document
E55 Type
11
91) Record Source/Legal Body ID
P67 refers to
E31 Document
P48 has preferred
identifier
E39 Actor
E42 Identifier
92) Record Source/Legal Body Name/Appellation Value
P131 is identified by
E39 Actor
E82 Actor Appellation
93) Record Source/Legal Body Web link
P2 has type
P129B is subject of
E39 Actor
E73 Information Object
12
E55 Type
“web resource”