The CIDOC CRM Harmonized models for the Digital

The CIDOC CRM Harmonized models for the Digital World: CIDOC CRM, FRBROO, CRMDig, EDM. Martin Dörr Stephen Stead Center for Cultural Informatics, Institute of Computer Science Foundation for Research and Technology – Hellas Paveprime Ltd London, Uk Helsinki, Finland June 10, 2012 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 CIDOC June 10, 2012 2

The CIDOC CRM Cultural Diversity and Data Standards The Cultural information is more than a domain: ¡ 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 documentation standard? ¡ ¡ ¡ Each aspect needs its own methods, forms, communication means Data overlap, but do not fit in one schema Understanding lives from relationships, but how to express them? CIDOC June 10, 2012 3

The CIDOC CRM 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… CIDOC June 10, 2012 Historical Archives… “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… CIDOC June 10, 2012 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 CIDOC June 10, 2012 6

The CIDOC CRM The Integration Problem (1) n Problem 1: identification of things ¡ Actors, Roles, proper names: n ¡ Places n n ¡ Jalta, Yalta Krym, Crimea Events n ¡ The Premier of the Union of Soviet Socialist Republics Allied leader, Allied power Joseph Stalin…. Crimea Conference, “Allied Leaders at Yalta”, “… conference powers” “Postwar division” between Allied Objects and Documents: n The photo, the agreement text CIDOC June 10, 2012 7

The CIDOC CRM The Integration Problem (2) n Problem 2: hidden (implicit) entities (typically under “title”) ¡ Actors n ¡ Places n ¡ Yalta, Crimea Events n n Allied leader, Allied power Crimea Conference, “Allied Leaders at Yalta”, “… conference powers” “Postwar division” between Allied Solution: ¡ Make better metadata structures: but what are the relevant elements? CIDOC June 10, 2012 8

The CIDOC CRM Explicit Events, Object Identity, Symmetry E 52 Time-Span E 39 Actor E 53 Place 7012124 February 1945 P 11 pa P 82 at some time within rtic ipa ted in P 7 took place at E 7 Activity “Crimea Conference” E 39 Actor E 38 Image P 6 P 86 falls within 7 i s re fer E 65 Creation Event red E 39 Actor ed p P 14 rm o f r e * P 81 ongoing throughout E 52 Time-Span P 9 4 h to by E 31 Document as cr ea ted “Yalta Agreement” 1945 -02 -11 CIDOC June 10, 2012 9

The CIDOC CRM… ¡ …captures the underlying semantics of relevant documentation structures in a formal ontology. ¡ …is a radical abstraction of a wide range of specialized databases to the basic relationships (the CRM) and open sets of terminologies (to appear as data). ¡ Ontologies are formalized knowledge: clearly defined concepts and relationships about possible states of affairs in a domain ¡ Ontologies can be understood by people and processed by machines to enable data exchange, data integration, query mediation etc. n Ontologies can be approximated by data structures (RDF, XML. . . ) n Data structures can be explained by ontologies intellectually n Data can be transformed from and to ontology instances (sets of atomic statements, “triples”) automatically CIDOC June 10, 2012 10

The CIDOC CRM Utility of the CIDOC CRM… ¡ ¡ Good ontologies can be extended without affecting interoperability. Semantic interoperability in cultural heritage can be achieved with an “extensible ontology of relationships” and explicit event modeling The CRM provides a shared explanation rather than the prescription of a common data structure. The ontology is the language that S/W developers and museum experts can share. Therefore it needed interdisciplinary work. That is what CIDOC has provided. CIDOC June 10, 2012 11

The CIDOC CRM Outcomes The CIDOC Conceptual Reference Model ¡ A collaboration with the International Council of Museums ¡ An ontology of 86 classes and 137 properties for culture and more ¡ With the capacity to explain hundreds of (meta)data formats ¡ Accepted by ISO TC 46 in September 2000 ¡ International standard since 2006 - ISO 21127: 2006 ¡ To be revised 2011/2012 (minor extensions) Serving as: ¡ ¡ intellectual guide to create schemata, formats, profiles A language for analysis of existing sources for integration/mediation “Identify elements with common meaning” ¡ Transportation format for data integration / migration / Internet CIDOC June 10, 2012 12

The CIDOC CRM The Intellectual Role of the CRM Conceptualization ? ab str ac ts approximates fro m explains, motivates Data structures & Presentation models organize to er f e r World Phenomena CIDOC June 10, 2012 Data Legacy bases systems Data in various forms 13

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, oo. DBMS, XML, RDF(S) Uses Multiple is. A – 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 is. A for properties to capture different abstraction of relationships Methodological aspects: ¡ Entities are introduced as anchors of properties (and if structurally relevant) ¡ Frequent joins (short-cuts) of complex data paths for data found in different degrees of detail are modeled explicitly CIDOC June 10, 2012 14

The CIDOC CRM Justifying Multiple Inheritance Single Inheritance form: Multiple Inheritance form: Museum Artefact museum number collection material Ecclesiastical item Canister container belongs to church lid Holy Bread Basket Generalization Museum Artefact Canister Ecclesiastical item container lid belongs to church Holy Bread Basket container lid Repetition of properties necessary CIDOC June 10, 2012 Unique identity of properties 15

The CIDOC CRM Data example (RDF-like form) Epitaphios GE 34604 (entity E 22 Man-Made Object) P 30 custody transferred through, P 24 changed ownership through Transfer of Epitaphios GE 34604 (entity E 10 Transfer of Custody, E 8 Acquisition Event) Multiple P 28 custody surrendered by Metropolitan Church of the Greek Community of Ankara (entity E 39 Actor) P 23 transferred title from Metropolitan Church of the Greek Community of Ankara (entity E 39 Actor) P 29 custody received by Museum Benaki (entity E 39 Actor) P 22 transferred title to Exchangeable Fund of Refugees (entity E 40 Legal Body) P 2 has type national foundation (entity E 55 Type) P 14 carried out by Exchangeable Fund of Refugees (entity E 39 Actor) P 4 has time-span GE 34604_transfer_time (entity E 52 Time-Span) P 82 at some time within 1923 – 1928 (entity E 61 Time Primitive) P 7 took place at Greece (entity E 53 Place) P 2 has type nation (entity E 55 Type) republic (entity E 55 Type) TGN data P 89 falls within Europe (entity E 53 Place) P 2 has type continent (entity E 55 Type) CIDOC June 10, 2012 Instantiation 16

The CIDOC CRM Top-level classes useful for integration refer to / refine refer to / identify E 41 Appellations E 55 Types E 39 Actors E 28 Conceptual Objects E 18 Physical Thing participate in affect or / refer to location E 2 Temporal Entities E 52 Time-Spans within CIDOC June 10, 2012 at E 53 Places 17

The CIDOC CRM The types of relationships ¡ ¡ Identification of real world items by real world names Observation and 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 n 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 CIDOC June 10, 2012 18

The CIDOC CRM The E 2 Temporal Entity Hierarchy E 68 Dissolution E 69 Death E 64 End of Existence E 6 Destruction E 81 Transformation E 67 Birth E 4 Period E 5 Event E 63 Beginning of Existence E 66 Formation E 65 Creation E 12 Production E 83 Type Creation E 2 Temporal Entity E 11 Modification E 80 Part Removal E 9 Move E 3 Condition State E 79 Part Addition E 10 Transfer of Custody E 8 Acquisition E 7 Activity Generalization E 17 Type Assignment E 87 Curation Activity E 14 Condition Assessment E 13 Attribute Assignment E 15 Identifier Assignment E 86 Leaving E 16 Measurement E 85 Joining CIDOC June 10, 2012 19

The CIDOC CRM Scope note example: E 2 Temporal Entity Scope Note: This class comprises all phenomena, such as the instances of E 4 Periods, E 5 Events and states, which happen over a limited extent in time. In some contexts, these are also called perdurants. This class is disjoint from E 77 Persistent Item. This is an abstract class and has no direct instances. E 2 Temporal Entity is specialized into E 4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E 3 Condition State, which applies to instances of E 18 Physical Thing. Comments: n n n E 2 is limited in time, is the only link to time, but is not time itself spreads out over a place or object the core of a model of physical history, open for unlimited specialisation CIDOC June 10, 2012 20

The CIDOC CRM Temporal Entity- Subclasses ¡ ¡ ¡ E 4 Period n binds together related phenomena n introduces inclusion topologies - parts etc. n Is confined in space and time n the basic unit for temporal-spatial reasoning E 5 Event n looks at the input and the outcome n introduces participation of people and presence of things n the basic unit for weak causal reasoning n each event is a period if we study the details of the process E 7 Activity n adds intention, influence and purpose n adds tools CIDOC June 10, 2012 21

The CIDOC CRM Temporal Entity-Main Properties ¡ E 2 Temporal Entity n ¡ Properties: P 7 took place at (witnessed): P 9 consists of (forms part of): P 10 falls within (contains): E 53 Place E 4 Period E 5 Event n ¡ E 52 Time-Span E 4 Period n ¡ Properties: P 4 has time-span (is time-span of): Properties: P 12 occurred in the presence of (was present at): E 77 Persistent Item P 11 had participant (participated in): E 39 Actor E 7 Activity n Properties: P 14 carried out by (performed): E 39 Actor P 20 had specific purpose (was purpose of): E 5 Event P 21 had general purpose (was purpose of): E 55 Type P 16 used specific object (was used for): E 70 Thing P 125 used object of type (was type of object used in) E 55 Type CIDOC June 10, 2012 22

The CIDOC CRM The Participation Properties P 33 used specific technique (was used by) P 16 used specific object (was used for) P 142 used constituent (was used in) P 146 separated from (lost member by) P 25 moved (moved by) P 96 by mother (gave birth) P 14 carried out by (performed) P 143 joined (was joined by) P 145 separated (left by) P 29 custody received by (received custody through) P 22 transferred title to (acquired title through) P 23 transferred title from (surrendered title through) P 28 custody surrendered by (surrendered custody through P 11 had participant (participated in) P 144 joined with (gained member by) P 99 dissolved (was dissolved by) P 12 occurred in the presence of (was present at) P 13 destroyed (was destroyed by) P 93 took out of existence (was taken out of existence by) P 124 transformed (was transformed by) P 100 was death of (died in) P 112 diminished (was diminished by) P 31 has modified (was modified by) P 110 augmented (was augmented by) P 108 has produced (was produced by) P 123 resulted in (resulted from) Generalization P 92 brought into existence (was brought into existence by)P 95 has formed (was formed by) CIDOC June 10, 2012 P 98 brought into life (was born) P 94 has created (was created by) P 135 created type (was created by) 23

The CIDOC CRM Historical Events as Meetings t Brutus was present at! Caesar’s mother “coherence volume” of Caesar’s death was present at! Caesar was present at! Brutus’ dagger “coherence volume” of Caesar’s birth ? Forum Romanum, Rome CIDOC June 10, 2012 S 24

The CIDOC CRM Depositional events as meetings t lava and ruins ancient Santorinian coherence volume of volcano eruption house volcano coherence volume of house building CIDOC June 10, 2012 Santorini - Akrotiti S 25

The CIDOC CRM Exchanges of information as meetings t coherence volume of second announcement Victory!!! coherence volume of first announcement other Soldiers 2 nd Athenian Victory!!! 1 st Athenian runner coherence volume of the battle of Marathon CIDOC June 10, 2012 Athens S 26

The CIDOC CRM 3 D Model Creation as Meetings t 3 D model coherence volume of rendering coherence volume of mesh-creation mesh-data 2 nd Computer scanner museum object scan-data 1 st Computer operator coherence volume of acquisition Museum CIDOC June 10, 2012 It-Lab S 27

The CIDOC CRM Termini postquos/ antequos AD 461 P 82 at some time within * P 4 h a (is time-sp me-s a pan n of) Death of Leo I P 11 had participant: of h t ea d P 92 brought i. existence: was in) before 00 (died 1 P P 93 took o. o. existence: P 82 at some time within * P 4 has time-span (is time- span of) P 14 carried out by (performed) Pope Leo I P 9 Death of Attila meeting Leo I 8 b ro (w ugh before as t i bo nt rn o li fe ) Birth of Leo I CIDOC June 10, 2012 Birth of Attila n * -spa e m i t as of) P 4 h e-span m (is ti P 82 at some time AD 453 within P 1 AD 452 before 00 w (d as d ied ea in th of ) P 14 carried out by (performed) Attila ife l o int t before gh orn) u o b br as 8 (w P 9 Properties: Deduction: before 28

The CIDOC CRM Time Uncertainty, Certainty and Duration P 81 ongoing throughout Duration (P 83, P 84) after “intensity” before time P 82 at some time within CIDOC June 10, 2012 29

The CIDOC CRM E 1 CRM Entity P 86 falls with in (contains) 0, n P 4 has time-span E 52 Time-Span E 2 Temporal Entity (is time-span of) 1, n 1, 1 0, n E 53 Place 0, n P 7 took place at (witnessed) 0, n P 1 is identified by (identifies) P 81 ongoing throughout 0, n 1, 1 0, n E 61 Time Primitive P 82 at some time within E 77 Persistent Item P 78 is identified by (identifies) P 9 consists of (forms part of) 0, n 1, n E 52 Time-Span E 4 Period 0, n P 10 falls with in (contains) E 5 Event CIDOC June 10, 2012 0, n P 5 consists of (forms part of) 0, 1 E 3 Condition State 0, 1 E 41 Appellation 0, n E 44 Time Appellation property Generalization E 50 Date 30

The CIDOC CRM E 7 Activity and inherited properties E 59 Primitive Value E 62 String 0, 1 P 3 has note 0, n E 1 CRM Entity 0, n P 3. 1 has type P 2 has type (is type of) E 55 Type 0, n E 5 Event E 55 Type E. g. , “Field Collection” E 55 Type E. g. , “photographer” property P 14. 1 in the role of Generalization Indirect Generalization CIDOC June 10, 2012 E 7 Activity 0, n P 14 carried out by 1, n (performed) E 39 Actor 31

The CIDOC CRM Activities: E 16 Measurement 0, n P 140 assigned attribute to E 1 CRM Entity E 13 Attribute Assignment (was attribute by) E 70 Thing 0, n P 39 measured (was measured by) 0, n 1, 1 E 16 Measurement 1, n 0, n P 141 assigned (was assigned by) 0, n P 40 observed dimension (was observed in) 0, n E 1 CRM Entity E 54 Dimension 1, 1 P 43 has dimension (is dimension of) property Generalization Shortcut P 91 has unit (is unit of) 0, n E 58 Measurement Unit P 90 has value 0, n E 60 Number Indirect Generalization CIDOC June 10, 2012 32

The CIDOC CRM Activities: E 14 Condition Assessment P 2 has type (is type of) 0, n E 1 CRM Entity An Assessment may include many different sub-activities E 2 Temporal Entity 0, n E 55 Type E 39 Actor 1, n P 14 carried out by (performed) E 7 Activity P 14. 1 in the role of P 34 concerned 1, n (was assessed by) E 14 Condition Assessment 1, n P 35 has identified (identified by) property Generalization Indirect Generalization 0, n E 18 Physical Thing CIDOC June 10, 2012 0, n P 44 has condition (condition of) 1, 1 E 3 Condition State is a Situation. Its type is the “condition” 33

The CIDOC CRM 0, 1 E 62 String 0, n P 3 has note Activities: E 8 Acquisition 0, n E 1 CRM Entity P 3. 1 has type E 55 Type P 14 carried out by (performed) 0, n P 23 transferred title from (surrendered title through) 0, n 0, n E 55 Type E 5 Event P 14. 1 in the role of 1, n P 22 transferred title to (acquired title through) P 2 has type (is type of) No buying and selling, just one transfer E 7 Activity E 8 Acquisition 1, n P 24 transferred title of (changed ownership through) 0, n P 51 has former or current owner (is former or current owner of) 0, n E 18 Physical Thing E 39 Actor 0, n CIDOC June 10, 2012 P 52 has current owner (is current owner of) 0, n 34

The CIDOC CRM E 53 Place ¡ ¡ A place is an extent in space, determined diachronically with regard to 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: n figures from the bow of a ship n African dinosaur foot-prints appearing in Portugal by continental drift n where Nelson died CIDOC June 10, 2012 35

The CIDOC CRM Properties of E 53 Place 0, n P 89 falls within (contains) 0, n P 88 consists of (forms part of) 0, n E 53 Place 0, n P 87 is identified by (identifies) 0, n P 27 moved from (was origin of) 0, n E 44 Place Appellation 1, 1 1, n E 4 Period 0, n E 9 Move 1, n E 12 Production 1, n P 25 moved (moved by) P 108 has produced (was pro duced by) 0, n 1, n 0, n P 58 has section definition E 18 Physical Thing (defines section) E 47 Spatial Coordinates E 48 Place Name E 45 Address Where was Lord Nelson’s ring when he died? CIDOC June 10, 2012 1, n P 5 (is 3 ha for s f me orm r o er r c or ur cu (is P 5 re loc 9 h nt rren a ate s loc t l d o sec ati oca on tio n o tio of n rw n ) ith in) 0, 1 E 46 Section Definition 0, n P 26 moved to (was destination of) P 7 took place at (witnessed) 0, n 1, 1 E 24 Physical Man-Made Thing E 19 Physical Object 0, n P 8 took place on or within (witnessed) 36

The CIDOC CRM 1, n P 7 took place at (witnessed) E 5 Period P 20 had specific purpose (was purpose of) 0, n 1, n P 26 moved to (was destination of) P 27 moved from (was origin of) Activities: E 9 Move 0, n P 21 had general purpose (was purpose of) E 7 Activity E 9 Move 0, n 1, n 0, n P 25 moved (moved by) 1, n P 53 has former or current location (is former or current location of) 0, n 1, n E 18 Physical Thing 0, n E 53 Place E 55 Type P 55 has current location (currently holds) 0, n CIDOC June 10, 2012 0, 1 E 19 Physical Object 0, 1 P 54 has current permanent location (is current permanent location of) 37

The CIDOC CRM An Instance of E 9 Move E 20 Person E 19 Physical Object Martin Doerr Spanair EC-IYG P 2 How I came to Madrid… P 2 5 m P 59 B has section ov ed E 9 Move My walk 16 -9 -2006 13: 45 P 27 moved from ove d E 9 Move Flight JK 126 P 26 moved to E 53 Place Frankfurt Airport-B 10 EC-IYG seat 4 A Madrid Airport P 27 moved from CIDOC June 10, 2012 38

The CIDOC CRM Activities: E 11 Modification/E 12 Production E 7 Activity 0, n P 16 used specific object (was used for) E 70 Thing P 125 used object of type (was type of object used in) 0, n E 11 Modification P 32 used general technique (was technique of) 0, n 1, n E 12 Production P 31 has modified (was mod ified by) P 33 used specific technique (was used by) 1, n 1, 1 E 24 Physical Man-Made Thing P 69 is associated with 0, n CIDOC June 10, 2012 P 45 co nsists of (is incor porated in) P 108 has produced (was produ ced by) 0, n E 29 Design or Procedure E 55 Type E 18 Physical Thing 0, n Things may be different from their plans 0, n P 68 usually employs (is usually employed by) P 126 employed (was employed in) 0, n E 57 Materials may be lost or altered 0, n 39

The CIDOC CRM Ways of Changing Things E 64 End of Existence E 63 Beginning of Existence P 123 resulted in (resulted from) P 93 took out of existence (was taken o. o. e. by) E 81 Transformation E 11 Modification E 79 Part Addition E 80 Part Removal CIDOC June 10, 2012 P 92 brought into existence (was brought into existence by) P 31 has m (was mo odified by ) E 77 Persistent Item P 124 transformed (was transformed by) P 111 added (was added by) P 11 ed 0 v o ( m w re as a augmen 3 1 ) 1 y b P ugm t ed ente ed emov r s d a by) (w P 112 diminished (was diminished by) E 18 Physical Thing E 24 Ph. M. -Made Thing 40

The CIDOC CRM E 26 Physical Feature E 70 Thing E 27 Site E 25 Man-Made Feature E 19 Physical Object E 72 Legal Object E 18 Physical Thing E 20 Biological Object E 22 Man-Made Object E 24 Physical M-M Thing E 21 Person E 84 Information Carrier material E 78 Collection E 82 Actor Appellation immaterial E 58 Measurement Unit E 70 Thing E 57 Material E 55 Type E 56 Language E 41 Appellation E 71 Man-Made Thing E 28 Conceptual Object E 90 Symbolic Object E 89 Propositional Object Generalization E 73 Information Object E 30 Right E 42 Identifier E 50 Date E 49 Time Appellation E 48 Place Name E 75 Conceptual Object Appellation 47 Spatial Coordinates E 44 Place Appellation E 46 Section Definition E 51 Contact Point E 45 Address E 31 Document E 32 Authority Document E 29 Design or Procedure E 35 Title E 34 Inscription E 33 Linguistic Object E 37 Mark CIDOC June 10, 2012 E 36 Visual Item E 38 Image 41

The CIDOC CRM E 39 Actor E 74 Group E 40 Legal Body E 39 Actor E 21 Person CIDOC June 10, 2012 42

The CIDOC CRM Taxonomic Discourse E 7 Activity E 1 CRM Entity E 65 Creation Event E 83 Type Creation E 17 Type Assignment P 94 ha s c (was cre reated by) on ed tion) s a ea s b wa pe cr 6 3 ty P 1 orted pp (su E 28 Conceptual Object P 13 d ) 5 e i if by (was created s type crea las ified t c e d 1 ss by) 4 a P cl as (w P 42 assigned (was assigned by) P 136. 1 in the taxonomic role CIDOC June 10, 2012 P 137 is exemplified by (exemplifies) E 55 Type P 137. 1 in the taxonomic role 43

The CIDOC CRM Visual Content and Subject P 62. 1 mode of depiction ts P 62 depic d by) (is depicte E 24 Physical Man-Made Thing E 55 Type E 1 CRM Entity P 67 refers to (is referred to by) P 128 carries (is carried by) E 73 Information Object P 138. 1 mode of depiction P 65 shows visual item (is shown by) E 84 Information Carrier P 138 represents (has representation) E 36 Visual Item E 38 Image CIDOC June 10, 2012 E 37 Mark E 34 Inscription 44

The CIDOC CRM Data Example in Graphical Style (Taiwan) E 55 Type Technology Crop P 138 has representation P 32 used general technique P 62 depicts E 11 Modification E 22 Man-Made Object Modif. -crop#7901 P 108 has produced E 74 Group Da-Wu Tribe P 74 b is current residence of P 138 has representation E 53 Place Lanyu P 70 is docu mented in E 31 Document Map P 138 has representation CIDOC June 10, 2012 P 14 B performed P 62 depicts P 108 has produced E 12 Production E 22 Man-Made Object Prod. -Pottery#035 P 32 used general technique E 55 Type P 138 has representation Da-Wu Tool-Pottery 45

The CIDOC CRM Application: Mapping DC to the CRM (1) Example: 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 CIDOC June 10, 2012 46

The CIDOC CRM Application: Mapping DC to the CRM (2) E 41 Appellation y db Name: Mapping of the Dublin Core Metadata Element Set to the CIDOC CRM ie is E 33 Linguistic Object: FORTH-ICS / TR-274 July 2000 tif en id ated by e r c s a w wa su se df or E 65 Creation carried out by Event: 0001 E 7 Activity has Actor: 0001 E 39 Actor: 0002 ed tifi den is i by age angu has l Lang. : English CIDOC June 10, 2012 E 82 Actor Appellation Name: Martin Doerr is identified by E 82 Actor Appellation Name: ICS-FORTH E 55 Type: Publication E 75 Conceptual Object Appellation Name: FORTH-ICS / TR-274 July 2000 E 56 Language is identified by type Event: 0002 carried out by E 39 Actor has type E 55 Type: FORTH Identifier (background knowledge not in the DC record) 47

The CIDOC CRM Application: Mapping DC to the CRM (3) Example: DC Record about a Painting Type. DCT 1: image Type: painting Title: Garden of Paradise Creator: Master of the Paradise Garden Publisher: Staedelsches Kunstitut CIDOC June 10, 2012 48

The CIDOC CRM Application: Mapping DC to the CRM (4) E 41 Appellation by i E 73 Information Object: PA 310 -1 A? ? was pr y uced b od is d oc um in ente d fied car ried E 12 Production Event: 0003 out by y nti fie db has type AAT: painting Event: 0004 carried out by E 82 Actor Appellation Name: Staedelsches Kunstitut is ide was created by E 55 image Type DCT 1: Paradise Garden ULAN: 4162 Docu: 0001 E 55 Type Name: Master of the E 39 Actor E 31 Document E 65 Creation E 82 Actor Appellation enti en d si by Name: Garden of Paradise is id ed i f ti E 39 Actor: 0003 has typ e E 55 Type (AAT: background knowledge not in the DC record) CIDOC June 10, 2012 Type: Publication Creation 49

The CIDOC CRM Lessons learned from mapping ¡ ¡ Semantic Interoperability can defined by the capability of mapping Mapping for epistemic networks is relatively simple: n n ¡ Domain experts easily learn schema mapping n ¡ IT experts may not understand meaning, underestimate it or are bored by it! Intuitive tools for domain experts needed: n n Specialist / primary information databases frequently employ a flat schema, reducing complex relationships into simple fields a Source fields frequently map to composite paths under the CRM, making their semantics explicit using a small set of CRM primitives Intermediate nodes are postulated or induced (e. g. , “birth” from “person”). They are the hooks for integration with complementary sources Cardinality constraints must not be enforced = alternative or incomplete knowledge Separate identifier matching from schema mapping Separate terminology mediation from schema mapping CIDOC June 10, 2012 50

The CIDOC CRM Challenge: Integrating Poor and Rich… CIDOC Conceptual Reference Model (CRM) Access all data from any level: Few concepts, high recall Thing Actor was present at subsumption Special concepts, high precision Dublin Core Event happened at LIDO Acquisition used object MIDAS automatic data export CIDOC June 10, 2012 Data 51

The CIDOC CRM Data-flow between different kinds of CRM-compatible systems export by reduction to CRM concepts CRM import-compatible data structure C e. g. , RDF/OWL transform back e. g. , XML or RDF CRM-Compatible Form transform into CRM export-compatible data structure B’ data export e. g. , British Museum Local Information System A CIDOC June 10, 2012 trans form into data import data export Local Information System B e. g. , Europeana Materialized Access System D 52

The CIDOC CRM Application: An Export-Compatible Data Structure E 84 Information Carrier The “Monument to Balzac”(S 1296) P 108 B was produced by E 21 Person Honoré de Balzac P 62 depicts E 84 Information Carrier The “Monument to Balzac” (plaster) P 16 B was used for P 134 continued E 12 Production P 2 has type P 62 depicts Bronze casting“Monument to Balzac” in 1925 P 14 carried out by E 55 Type P 108 B was produced by E 12 Production Rodin making “Monument to Balzac” in 1898 E 40 Legal Body P 2 has type Rudier (Vve Alexis) et Fils E 55 Type bronze plaster P 4 has time-span P 4 has time-span P 2 has type E 52 Time-Span 1925 P 120 B occurs after P 7 took place at E 55 Type E 52 Time-Span E 53 Place companies 1898 France (nation) E 55 Type sculptors P 2 has type E 52 Time-Span 1917 P 4 has time-span CIDOC June 10, 2012 E 69 Death Rodin’s death P 100 B died in P 14 carried out by E 21 Person E 67 Birth Rodin Auguste E 52 Time-Span 1840 Rodin’s birth P 98 B was born P 4 has time-span 53

The CIDOC CRM Core: An Export-Compatible Data Structure CIDOC June 10, 2012 54

Work (CRM Core). Category = E 84 Information Carrier Classification =sculpture (visual work) Classification =plaster Identification =The Monument to Balzac (plaster) Description =Commissioned to honor one of France's greatest novelists, Rodin spent seven years preparing for Monument to Balzac. When the plaster original was exhibited in Paris in 1898, it was widely attacked. Rodin retired the plaster model to his home in the Paris suburbs. It was not cast in bronze until years after his death. Event Role in Event =P 108 B was produced by Identification= Rodin making Monument to Balzac in 1898 Event Type = E 12 Production Participant Identification =Rodin, Auguste Identification =ID: 500016619 Participant Type = artists Participant Type = sculptors Date = 1898 Place = France (nation) Related event Role in Event =P 134 B was continued by Identification= Bronze casting Monument to Balzac in 1925 Event Role in Event =P 16 B was used for The CIDOC CRM Core Instances Artist (CRM Core). Category = E 21 Person Classification = artists Classification = sculptors Identification =Rodin, Auguste Identification =ID: 500016619 Event Role in Event =P 98 B was born Identification= Rodin‘s birth Event Type = E 67 Birth Date = 1840 Event Role in Event =P 100 B died in Identification= Rodin‘s death Event Type = E 69_Death Date = 1917 Related event Role in Event =P 120 occurs before Identification= Bronze casting Monument to Balzac in 1925 CIDOC June 10, 2012 Identification= Bronze casting Monument to Balzac in 1925 Event Type = E 12 Production Participant Identification =Rudier (Vve Alexis) et Fils Participant Type = companies Thing Present Identification =The Monument to Balzac (S. 1296) Thing Present Type =bronze Thing Present Type =sculpture (visual work) Date = 1925 Related event Role in Event =P 120 B occurs after Identification= Rodin's death Relation To = Honore de Balzac Relation type refers to 55

The CIDOC CRM Knowledge Management Knowledge management has 3 levels: ¡ Acquisition needs: (your database, can be derived from CRM) n n ¡ Integration / comprehension needs: (target of the CRM): n n ¡ 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 interoperability needs capability of your database to be mapped! break up document boundaries, relate facts to wider context match shared identifiers of items, aggregate alternatives explore contexts, no preference direction of search, no cardinality constraints interoperability needs a global schema Reasoning, presentation, story-telling needs: (can be based on CRM) n n n represent contexts orthogonal to data acquisition present in order, allow for digestion support deduction and induction CIDOC June 10, 2012 56

The CIDOC CRM Information Integration: Relations & Co-reference Linking documents via co-reference, not hyperlinks! Primary link extracted from one document Time. Span Actor CRM Thing Event Deductions Place Integration of Factual Relations Discovery of Lucy Johanson's Expedition Donald Johanson Cleveland Museum of Natural History AL 288 -1 Lucy Ethiopia Hadar Documents & Metadata CIDOC June 10, 2012 57

The CIDOC CRM The Scholarly Process Publications Stories exhibitions Refer interpret present Johanson's Donald Johanson Expedition Search, correlate, integrate Discovery of Lucy Ethiopia Cleveland Museum of Natural History discover collect aggregate update CIDOC June 10, 2012 Lucy AL 288 -1 Layer of “Latest Knowledge” Hadar “Evidence layer” Things Sources Collections Corpora 58

The CIDOC CRM Information Integration: Relations & Terms global relationships and core entities CIDOC CRM detailed terminology thesauri extend CRM classes (e. g. , SKOS) integrated knowledge local collection data CIDOC June 10, 2012 & extensions Actors Events Objects CRM instances (metadata repository, Lo. D) content & metadata (XML/RDBMS) 59

The CIDOC CRM The Scholarly Process Publications Stories exhibitions Refer interpret present Johanson's Donald Johanson Expedition Search, correlate, integrate Discovery of Lucy Ethiopia Cleveland Museum of Natural History discover collect aggregate update CIDOC June 10, 2012 Lucy AL 288 -1 Layer of “Latest Knowledge” Hadar “Evidence layer” Things Sources Collections Corpora 60

The CIDOC CRM ¡ ¡ ¡ Publication as ISO 21127: 2006 in October 2006 Revision (based on version 5. 0) foreseen for 2011/2012 Some major extensions: n n n ¡ ¡ Development “FRBROO”, approved by IFLA and CIDOC, being continued by modeling FRAD/FRSAD CRM Dig: Digital Provenance UK “Centre for Archaeology” model Ongoing work on TEI – CRM harmonization RDF and OWL versions available CIDOC June 10, 2012 61

The CIDOC CRM n Major Recent Users ¡ ¡ ¡ ¡ n n Use and Links CLAROS, UK: www. clarosnet. org British Museum: http: //collection. britishmuseum. org Research. Space: www. researchspace. org German Digital Library DDB: http: //www. deutsche-digitale-bibliothek. de/ Europeana will accept CRM instances in RDF German Project WISSKI (research database integration): http: //wiss-ki. eu/ ATHENA Project: LIDO Data Harvesting and Interchange Format: www. lidoschema. org CRM Home page: http: //www. cidoc-crm. org/ Recommended RDFS: http: //www. cidoc-crm. org/rdfs/cidoc-crm CIDOC June 10, 2012 62

The CIDOC CRM ¡ After analyzing many specialized data structures for their key concepts, we encounter a surprise compared with common preconceptions: n n ¡ Conclusions Nearly no domain specificity, generic concepts appear in medicine, biodiversity etc. Rather a notion of scientific method emerges, such as “retrospective analysis”, “taxonomic discourse” etc. Extraordinary small set of concepts Extraordinary convergence: adding dozens of new formats hardly introduces any new concept This approach is economic, investment pays off Ø The CRM should become our language for semantic interoperability CIDOC June 10, 2012 63