Transcript Authority services Interthesaurus correlations

CIDOC CRM, a Standard for the
Integration of Cultural Information
The
Martin Doerr
Center for Cultural Informatics
Institute of Computer Science
Foundation for Research and Technology - Hellas
Rethymno, Crete,
October 21-26, 2002
ICS-FORTH October 21-26, 2002
1
The CIDOC CRM
Outline
 Problem statement – information diversity
 Motivation example – the Yalta Conference
 The goal and form of the CIDOC CRM
 Presentation of contents
 About using the CIDOC CRM
 State of development
 Conclusion
ICS-FORTH October 21-26, 2002
2
The CIDOC CRM
Cultural Diversity and Data Standards
 Aspects of cultural information:
Collection description (art, archeology, natural history….)
 Archives and literature (records, treaties, letters, artful works..)
 Administration, preservation, conservation of material heritage
 Science and scholarship – investigation, interpretation
 Presentation – exhibition making, teaching, publication
 But how to make a data standard ?
 Each aspect needs its methods, forms, communication means
 Data overlap, but do not fit in one schema
 Understanding lives from relationships, but how to express them?
ICS-FORTH October 21-26, 2002
3
The CIDOC CRM
Historical Archives….
Type:
Title:
Title.Subtitle:
Date:
Creator:
Publisher:
Subject:
Text
Protocol of Proceedings of Crimea Conference
II. Declaration of Liberated Europe
February 11, 1945.
The Premier of the Union of Soviet Socialist Republics
The Prime Minister of the United Kingdom
The President of the United States of America
State Department
Postwar division of Europe and Japan
Metadata
Documents
About…
ICS-FORTH October 21-26, 2002
“The following declaration has been approved:
The Premier of the Union of Soviet Socialist Republics,
the Prime Minister of the United Kingdom and the President
of the United States of America have consulted with each
other in the common interests of the people of their countries
and those of liberated Europe. They jointly declare their mutual
agreement to concert…
….and to ensure that Germany will never again be able to
disturb the peace of the world…… “
4
The CIDOC CRM
Images, non-verbose…
Type:
Title:
Date:
Publisher:
Source:
Copyright:
References:
Image
Allied Leaders at Yalta
1945
United Press International (UPI)
The Bettmann Archive
Corbis
Churchill, Roosevelt, Stalin
Photos, Persons
Metadata
About…
ICS-FORTH October 21-26, 2002
5
The CIDOC CRM
Places and Objects
TGN Id: 7012124
Names: Yalta (C,V), Jalta (C,V)
Types:
inhabited place(C), city (C)
Position: Lat: 44 30 N,Long: 034 10 E
Hierarchy: Europe (continent) <– Ukrayina (nation) <– Krym (autonomous republic)
Note:
…Site of conference between Allied powers in WW II in 1945; ….
Source: TGN, Thesaurus of Geographic Names
Places, Objects
About…
Title:
Yalta, Crimean Peninsula
Publisher: Kurgan-Lisnet
Source:
Liaison Agency
ICS-FORTH October 21-26, 2002
6
The CIDOC CRM
Capture Underlying Semantics…
 Diversity requires many (meta)data standards


Related Information does not match one format or query
We have recognized (already 1994 with Museum Benaki):
Event-centric models can integrate many kinds of retrospective
(historical) information (and may be more).
 CIDOC has engaged in interdisciplinary work
to create semantic content models, so-called: domain ontologies

Ontologies are formalized knowledge: clearly defined concepts
and relationships about possible states of affairs of the domain
ICS-FORTH October 21-26, 2002
7
The CIDOC CRM
Explicit Events, Object Identity, Symmetry
E39 Actor
E52 TimeSpan1945
February
P82 at some
time
within
E39 Actor
E53 Place
7012124
E7 Activity
“Crimea Conference”
E38 Image
P86 falls within
E65 Creation
Event
E39 Actor
*
P81 ongoing
throughout
E31 Document
“Yalta Agreement”
E52 Time-Span
11-2-1945
ICS-FORTH October 21-26, 2002
8
The CIDOC CRM
Outcomes
 The CIDOC Conceptual Reference Model
 A collaboration with the International Council of Museums
 An ontology of 85 classes and 130 properties for culture and more
 With the capacity to explain dozens of (meta)data formats
 Accepted by ISO TC46 in Sept. 2000, now
ISO/AWI 21127 proposed Committee Draft
 Serving as:


intellectual guide to create schemata, formats, profiles
A language for analysis of existing sources for integration
“Identify elements with common meaning”
 Transportation format for data integration / migration / Internet
ICS-FORTH October 21-26, 2002
9
The CIDOC CRM
The Intellectual Role of the CRM
Conceptualization
?
approximates
explains,
motivates
Data structures &
Presentation models
organize
World Phenomena
ICS-FORTH October 21-26, 2002
Data
Legacy
Legacy
bases
systems
systems
Data in various forms
10
The CIDOC CRM
Encoding of the CIDOC CRM
 The CIDOC CRM is a formal ontology (defined in TELOS)
 But
CRM instances can be encoded in many forms: RDBMS, ooDBMS,
XML, RDF(S).
 Uses Multiple isa – to achieve uniqueness of properties in the schema.
 Uses multiple instantiation - to be able to combine not always valid
combinations (e.g. destruction – activity).
 Uses
Multiple isA for properties to capture different abstraction of
relationships.
 Methodological aspects:
 Entities are introduced only if anchor of property ( if structurally relevant).
 Frequent joins (shot-cuts) of complex data paths for data found in
different degrees of detail are modeled explicitly.
ICS-FORTH October 21-26, 2002
11
Justifying Multiple Inheritance:
achieving uniqueness of properties
Single Inheritance form:
Multiple Inheritance form:
Museum Artefact
Canister
museum number
museum number
collection
collection
material
material
Ecclesiastical item
container
lid
Museum Artefact
belongs to church
Holy Bread Basket
Ecclesiastical item
Canister
container
lid
belongs to church
Holy Bread Basket
container
lid
Repetition of properties !
ICS-FORTH October 21-26, 2002
Unique identity of properties !
Possible Encoding of Data
as CIDOC CRM instance (XML-style)
Epitaphios GE34604 (entity E22 Man-Made Object )
P30 custody changed by, P24 changed ownership by
E10 Transfer of Custody, E8 Acquisition Event )
Transfer of Epitaphios GE34604 (entity
P28 custody surrendered by
Metropolitan Church of the Greek Community of Ankara
(entity E39 Actor )
P23 transferred title from
Metropolitan Church of the Greek Community of Ankara
(entity E39 Actor )
P29 custody received by
Museum Benaki (entity E39 Actor )
P22 transferred title to
Exchangable Fund of Refugees (entity P40 Legal Body )
P2 has type
national foundation (entity E55 Type )
P14 carried out by
(entity E39 Actor )
Exchangable Fund of Refugees
P4 has time-span
GE34604_transfer_time (entity
E52 Time-Span )
P82 at some time within
1923 - 1928 (entity E59 Time Primitive )
P7 took place at
Greece (entity E53 Place )
P2 has type
(entity E55 Type )
nation
republic (entity E55 Type )
P86 falls within
Europe (entity E53 Place )
P2 has type
continent (entity E55 Type )
ICS-FORTH October 21-26, 2002
TGN data
13
The CIDOC CRM
What does and what it does not
 Idea: Not being prescriptive creates much flexibility !
 The CRM can be used as data format for transport / migration /
presentation (but for not designed for data entry)
 It does not propose what to describe
 It allows to interprete what museums, archives actually describe
 It tries to formalize concepts which help data integration and resource
discovery (not all information)
 Focused on data structure semantics, integration, information about
the past
ICS-FORTH October 21-26, 2002
14
The CIDOC CRM
Top-level Entities relevant for Integration
E55 Types
refer to / refine
E39 Actors
E28 Conceptual Objects
E18 Physical Stuff
participate in
affect or / refer to
location
E2 Temporal Entities
E52 Time-Spans
ICS-FORTH October 21-26, 2002
at
E53 Places
15
The CIDOC CRM
A Classification of its Relationships
 Identification of real world items by real world names.
 Classification of real world items.
 Part-decomposition and structural properties of Conceptual &
Physical Objects, Periods, Actors, Places and Times.
 Participation of persistent items in temporal entities.
— creates a notion of history: “world-lines” meeting in space-time.
 Location of periods in space-time and physical objects in space.
 Influence of objects on activities and products and vice-versa.
 Reference of information objects to any real-world item.
ICS-FORTH October 21-26, 2002
16
The CIDOC CRM
Example: The Temporal Entity Hierarchy
ICS-FORTH October 21-26, 2002
17
The CIDOC CRM
Example: Temporal Entity
E2 Temporal Entity
Scope Note:
This is an abstract entity and has no examples. It groups together
things such as events, states and other phenomena which are
limited in time. It is specialized into Period, which holds on some
geographic area, and Condition State, which holds for, on, or over
a certain object.
— consists of related or similar phenomena,
— Is limited in time, is the only link to time, but not time itself
— spreads out over a place or object (physical or not).
— the core of a model of physical history, open for unlimited
specialisation.
ICS-FORTH October 21-26, 2002
18
The CIDOC CRM
Example: Temporal Entity- Subclasses
E4 Period
 binds together related phenomena
 introduces inclusion topologies - parts etc.
 Is confined in space and time
 the basic unit for temporal-spatial reasoning
 E5 Event
 looks at the input and the outcome
 the basic unit for causal reasoning
 each event is a period if we study the process
 E7 Activity
 brings the people in
 adds purpose
ICS-FORTH October 21-26, 2002
19
The CIDOC CRM
Temporal Entity- Main Properties
E2 Temporal Entity
 Properties: P4 has time-span (is time-span of):
E52 Time-Span
 Properties: P7 took place at (witnessed):
E53 Place
E4 Period
E4 Period
E4 Period
E5 Event

P9 consists of (forms part of):
P10 falls within (contains):
Properties: P11 had participant (participated in):
E39 Actor
P12 occurred in the presence of (was present at): E77 Persistent Item
E7 Activity
 Properties: P14 carried out by (performed):
E39 Actor
P20 had specific purpose (was purpose of): E7 Activity
P21 had general purpose (was purpose of): E55 Type
ICS-FORTH October 21-26, 2002
20
The CIDOC CRM
Termini postquem / antequem
P82 at some time
AD461
within
*
*
Death of
Leo I
P11 had participant:
P93 took o.o.existence:
P92 brought i. existence:
Pope Leo I
before
P14 carried out by
(performed)
Death of
Attila
P82 at some time
* within
P4 has time-span
(is time- span of)
Attila
meeting
Leo I
before
AD452
before
P14 carried out by
(performed)
Attila
before
Birth of
Leo I
ICS-FORTH October 21-26, 2002
P82 at some time
AD453
within
Birth of
Attila
Deduction: before
21
The CIDOC CRM
The Participation Properties
P12 occurred in the presence of (was present at)
E5 Event 
E77 Persistent Item
 P11 had participant (participated in)
E5 Event 
E39 Actor
E7 Activity 
E39 Actor
 P22 transferred title to (acquired title of)
E8 Acquisition Event 
E39 Actor
 P23 transferred title from (surrendered title of)
E8 Acquisition Event 
E39 Actor
 P28 custody surrendered by (surrendered custody)
E10 Transfer of Custody  E39 Actor
 P29 custody received by (received custody)
E10 Transfer of Custody  E39 Actor
 P14 carried out by (performed)
 P95 has formed (was formed by)
E66 Formation Event 
E74 Group
 P96 by mother (gave birth)
E67 Birth 
E21 Person
 P98 brought into life (was born)
E67 Birth 
E21 Person
 P99 dissolved (was dissolved by)
E68 Dissolution 
E74 Group
 P100 was death of (died in)
E69 Death 
E21 Person
ICS-FORTH October 21-26, 2002
22
The CIDOC CRM
Activities
CIDOC Notion
E59 Primitive Value
E1 CRM Entity
0,n
0,n
P2 has type
(is type of)
P3 has note
0,n
E62 String
0,1
E55 Type
E5 Event
E7 Activity
1,n
P14 carried out by (performed)
0,n
E39 Actor
P14.1 in the role of
ICS-FORTH October 21-26, 2002
23
The CIDOC CRM
Activities: Measurement Event
E13 Attribute Assignment
E16 Measurement Event
1,1
1,n
P40 observed dimension
(was observed by)
P39 was measured by
(measured)
0,n
E18 Physical Stuff
0,n
0,n
ICS-FORTH October 21-26, 2002
P43 has dimension
(is dimension of)
1,1
E54 Dimension
P90 has value
P91 unit
24
The CIDOC CRM
Activities: Condition Assessment
E7 Activity
1,n
P14 carried out by (performed)
0,n
E39 Actor
P14.1 in the role of
E14 Condition Assessment
E2 Temporal Entity
1,n
1,n
P34 was assessed by (concerns)
P35 has identified (identified by)
0,n
0,n
E18 Physical Stuff
E3 Condition State
P44 has condition (condition of)
0,n
ICS-FORTH October 21-26, 2002
1,1
25
The CIDOC CRM
Activities: Acquisition Event
E7 Activity
P22 acquired title of (transferred title to)
0,n E8 Acquisition Event
0,n
0,n
1,n
P23 surrendered title of (transferred title from)
P24 transferred title of (changed ownership by)
0,n
E39 Actor
0,n
0,n
P52 is current owner of (has current owner)
0,n
0,n
0,n
E18 Physical Stuff
0,n
P51 is former or current owner of (has former or current owner)
ICS-FORTH October 21-26, 2002
26
The CIDOC CRM
Activities: Move
P20 had specific purpose (was purpose of)
0,n
0,n
E7 Activity
0,n
P21 had general purpose (was purpose of)
0,n
E55 Type
E9 Move
1,n
1,n
P25 moved by (moved)
1,n
P26 moved to (was destination of)
P27 moved from (was origin of)
0,n
0,n
P55 has current location (currently holds)
0,n
0,n
E19 Physical Object
1,n
0,n
0,n
P53 has former or current location (is ~ of)
P54 has current permanent location (is ~ of)
ICS-FORTH October 21-26, 2002
E53 Place
0,n
0,n
27
The CIDOC CRM
Activities: Modification/Production Event
E7 Activity
P14 carried out by (performed)
in the role of
1,n
E11 Modification Event
0,n
0,n
0,n
E39 Actor
1,n
E55 Type
0,n
P32 used general technique (was technique of)
E18 Physical Stuff
P126 employed (was employed by)
P31 has modified (was modified by)
1,n
P45 consists of (is incorporated in)
P33 used specific technique (was used by)
0,n
E24 Physical Man-Made Stuff
0,n
0,n
E29 Design or Procedure
0,n
ICS-FORTH October 21-26, 2002
P68 usually employs (is usually employed by)
0,n
E57 Material
28
The CIDOC CRM
Entity: Modification Event
Properties:
P1 is identified by (identifies): E41 Appellation
P2 has type (is type of): E55 Type
P11 had participant (participated in): E39 Actor
P14 carried out by (performed): E39 Actor
(P14.1 in the role of : E55 Type)
P31 has modified (was modified by): E24 Physical Man-Made Stuff
P12 occurred in the presence of (was present at): E77 Persistent Item
P16 used specific object (was used for): E70 Stuff
(P16.1 mode of use: E62 String)
P32 used general technique (was technique of): E55 Type
P33 used specific technique (was used by): E29 Design or Procedure
P17 was motivated by (motivated): E1 CRM Entity
P19 was intended use of (was made for): E71 Man-Made Stuff
(P19.1 mode of use: E62 String)
P20 had specific purpose (was purpose of): E7 Activity
P21 had general purpose (was purpose of): E55 Type
P126 employed (was employed by): E57 Material
ICS-FORTH October 21-26, 2002
inherited properties
declared properties
inherited properties
declared properties
inherited properties
declared properties
29
The CIDOC CRM
Time Uncertainty, Certainty and Duration
P81 ongoing
throughout
Duration (P83,P84)
after
“intensity”
before
time
P82 at some
time within
ICS-FORTH October 21-26, 2002
30
The CIDOC CRM
Time-Span
E1 CRM Entity
E53 Place
E2 Temporal Entity
E77 Persistent Item
E52 Time Span
P86 falls within
(contains)
P10 falls within
(contains)
E3 Condition State
P7 took place at
(witnessed)
E4 Period
P9 consists of
(forms part of)
E41 Appellation
P82 at some
time within
P81 ongoing
throughout
E49 Time Appellation
E61 Time Primitive
E50 Date
E5 Event
ICS-FORTH October 21-26, 2002
31
The CIDOC CRM
Example: Place
E53 Place
 A place is an extent in space, determined diachronically wrt a larger,
persistent constellation of matter, often continents by coordinates, geophysical features, artefacts, communities, political
systems, objects - but not identical to.
 A “CRM Place” is not a landscape, not a seat - it is an abstraction from
temporal changes - “the place where…”
 A means to reason about the “where” in multiple reference systems.
 Examples: figures from the bow of a ship, African dinosaur foot-prints in
Portugal
ICS-FORTH October 21-26, 2002
32
The CIDOC CRM
Place
P88 consists of
(forms part of)
P7 took place at
(witnessed)
P26 moved to
(was destination of)
E53 Place
E12 Production Event
E9 Move
P27 moved from
(was origin of)
P108 has produced
(was produced by)
P25 moved
(moved by)
E44 Place Appellation
E46 Section Definition
E47 Spatial Coordinates
E48 Place Name
E45 Address
ICS-FORTH October 21-26, 2002
P58 defines section of
(has section definition)
E18 Physical Stuff
E24 Ph. M.-Made Stuff
E19 Physical Object
33
The CIDOC CRM
Extension Example: Getty’s TGN
P89 falls within
E53 Place
E39 Actor
E74 Group
P87 is identified by
(identifies)
E44 Place Appellation
E13 Attribute Assignment
carries
out
E52 Time-Span
ICS-FORTH October 21-26, 2002
Place Naming
P4 has time-span
E4 Period
Community
34
Example from the TGN
TGN1001441
P89 falls within
Kuyunjik
TGN7017998
Nineveh
People of Iraq
carry
out
Nineveh naming
Nineveh naming
20th century
1st mill. BC
ICS-FORTH October 21-26, 2002
P4 has time-span
City of Nineveh
35
The CIDOC CRM
Stuff
ICS-FORTH October 21-26, 2002
36
The CIDOC CRM
Physical Stuff
ICS-FORTH October 21-26, 2002
37
The CIDOC CRM
Conceptual Object
ICS-FORTH October 21-26, 2002
38
The CIDOC CRM
Actor
ICS-FORTH October 21-26, 2002
39
The CIDOC CRM
Appellation
ICS-FORTH October 21-26, 2002
40
The CIDOC CRM -Application
Mapping DC to the CIDOC CRM
Example: Partial DC Record about a Technical Report
Type: text
Title: Mapping of the Dublin Core Metadata Element Set to the CIDOC CRM
Creator: Martin Doerr
Publisher: ICS-FORTH
Identifier: FORTH-ICS / TR 274 July 2000
Language: English
ICS-FORTH October 21-26, 2002
41
The CIDOC CRM -Application
Mapping DC to the CIDOC CRM (RDF style)
…..
E41 Appellation
Name: Mapping of the Dublin Core Metadata Element Set to the CIDOC CRM
E65 Creation Event
E33 Linguistic Object
carried
out by
E39 Actor
is identified
by
Actor:0001
Event: 0001
E82 Actor Appellation
Name: Martin Doerr
Object: FORTH-ICS /
TR-274 July 2000
E7 Activity
Event: 0002
carried out by
E39 Actor
is identified
by
Actor:0002
E82 Actor Appellation
Name: ICS-FORTH
E55 Type
Type: Publication
E75 Conceptual Object Appellation
Name: FORTH-ICS / TR-274 July 2000
E56 Language
Lang.: English
ICS-FORTH October 21-26, 2002
has type
E55 Type
Type:FORTH Identifier
(background knowledge
not in the DC record)
42
The CIDOC CRM -Application
Mapping DC to the CIDOC CRM
Example: Partial DC Record about a painting
Type.DCT1: image
Type: painting
Title: Garden of Paradise
Creator: Master of the Paradise Garden
Publisher: Staedelsches Kunstinstitut
ICS-FORTH October 21-26, 2002
43
The CIDOC CRM -Application
Mapping DC to the CIDOC CRM
…..
E41 Appellation
Name: Garden of Paradise
E82 Actor Appellation
Name: Master of the
Paradise Garden
E12 Production
E23 Information Carrier
Event: 0003
E39 Actor
ULAN: 4162
Object: PA 310-1A??
E31 Document
Docu: 0001
E82 Actor Appellation
has type
Name: Staedelsches Kunstinstitut
was created by
E55 Type
E65 Creation Event
E55image
Type
DCT1:
Event: 0004
carried out
by
E39 Actor
Actor: 0003
AAT: painting
E55 Type
(AAT: background knowledge
not in the DC record)
ICS-FORTH October 21-26, 2002
Type: Publication Creation
44
The CIDOC CRM -Application
Repository Indexing
Ontology
expansion
CIDOC
CRM
Actors
Background
knowledge /
Authorities
ICS-FORTH October 21-26, 2002
Events
Objects
Thesauri
extent
CRM entities
Derived
knowledge
data (e.g. RDF)
Sources
and
metadata
(XML/RDF)
45
The CIDOC CRM
Proposition about Restructuring Data
 Data acquisition needs different structure from presentation:
 Acquisition (can be motivated by the CRM):
— sequence and order, completeness, constraints to guide and control data
entry.
— ergonomic, case-specific language, optimized to specialist needs
— often working on series of analogous items
 Integration / comprehension (target of the CRM):
— restore connectivity with related subjects,
— match and relate by underlying common concepts
— no preference direction or subject
 Presentation, story-telling (can be based on CRM)
— explore context, paths, analogies orthogonal to data acquisition
— present in order, allow for digestion
— support abstraction
ICS-FORTH October 21-26, 2002
46
The CIDOC CRM
About the CRM
 As an explanatory and mediation model, the CRM:

does not enforce constraints
— optional properties, multivalued properties, multiple instantiation

contains redundant paths
— “short cuts” of secondary processes, complex indirections

contains abstractions at various levels
— of entities and
— of attributes/properties
ICS-FORTH October 21-26, 2002
47
The CIDOC CRM
Frequently asked questions
 1. Will the CRM require me to change my documentation ?
Answer:
 No. It makes no prescriptions.
 You may, however, orient your document structures according to CRM constructs,
so that an automatic transfer into a CRM-compatible form is possible.
2. What is the benefit of standardisation?
Answer:
 You can communicate the meaning of your data structures in a unique way to any
user of the CRM.
ICS-FORTH October 21-26, 2002
48
The CIDOC CRM
Frequently asked questions
 3. What does compatibility with the CRM mean?
Answer:

That the parts of my data structure with the same scope can be explained by the
CRM as:

Subset: data can be transformed into a CRM instance and back.

Superset: A CRM instance can be transformed... and back.

Overlap: equivalent parts can be transformed...

Extension: The CRM can be consistently extended by refinement or
generalization such that my data structure becomes a subset.
 Still to be defined precisely. Major consensus issue.
ICS-FORTH October 21-26, 2002
49
The CIDOC CRM
Frequently asked questions
4. What does the CRM cover?
Answer: Potentially the whole world as physical history in human
perception!

In concrete terms: CIDOC Information Categories, DC, EAD,
SPECTRUM, FRBR, fits with OPENGIS, and many proprietary
formats (wrt contents falling into the intended scope of the CRM)

The mapping exercise has verified the stability of model, its
extensibility and the effectiveness of the methodology.

Experience of 6-10 years development by interdisciplinary groups,
several implementations.
ICS-FORTH October 21-26, 2002
50
The CIDOC CRM
Benefits of the CRM
(From Tony Gill)
 Elegant and simple compared to comparable Entity-Relationship
models
 Coherently integrates information at varying degrees of detail
 Readily extensible through O-O class typing and specializations
 Richer semantic content; allows inferences to be made from
underspecified data elements
 Designed for mediation of cultural heritage information
ICS-FORTH October 21-26, 2002
51
The CIDOC CRM
State of Development
 Proposed to ISO as Committee Draft. The structure is stable since
four years.
 The SIG has elaborated minor extension to satisfy archeology,
Natural History and relationships to Digital Libraries until July. All
questions of definition have been decided until October 2002.
Elaboration of improved introduction, improvements on clarity of
some scope notes, improved presentation until end of 2002.
 Acceptance as standard expected by 2003.
ICS-FORTH October 21-26, 2002
52
The CIDOC CRM
Conclusions
 The CRM is NOT a metadata standard,
 it should become our language for semantic interoperability,
 it is a Conceptual Reference Model for analyzing and designing
cultural information systems
 The CRM is in the ISO standardization process:
 Dissemination for wide understanding and consensus
 Extended application tests
 Elaboration of details and documentation
 Consensus
ICS-FORTH October 21-26, 2002
53