The CIDOC CRM a Standard for the Integration

The CIDOC CRM, a Standard for the Integration of Cultural Information 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 l Problem statement – information diversity l Motivation example – the Yalta Conference l The goal and form of the CIDOC CRM l Presentation of contents l About using the CIDOC CRM l State of development l Conclusion ICS-FORTH October 21 -26, 2002 2

The CIDOC CRM Cultural Diversity and Data Standards q Aspects of cultural information: u. Collection description (art, archeology, natural history…. ) u Archives and literature (records, treaties, letters, artful works. . ) u Administration, preservation, conservation of material heritage u Science and scholarship – investigation, interpretation u Presentation – exhibition making, teaching, publication q But how to make a data standard ? u Each aspect needs its methods, forms, communication means u Data overlap, but do not fit in one schema u 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… q Diversity requires many (meta)data standards Þ Related Information does not match one format or query q We have recognized (already 1994 with Museum Benaki): Event-centric models can integrate many kinds of retrospective (historical) information (and may be more). q CIDOC has engaged in interdisciplinary work to create semantic content models, so-called: domain ontologies q 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 E 52 Time. Span 1945 February E 39 Actor P 11 E 53 Place 7012124 P 82 at some pa time rtic ipa within ted in P 7 took place at E 7 Activity “Crimea Conference” E 39 Actor P 86 falls within E 38 Image P 6 by 7 is r e fer E 65 Creation Event E 39 Actor ed rm o f r e p P 14 * P 81 ongoing throughout E 52 Time-Span P 9 cre 4 ha ate s d red to E 31 Document “Yalta Agreement” 11 -2 -1945 ICS-FORTH October 21 -26, 2002 8

The CIDOC CRM Outcomes q The CIDOC Conceptual Reference Model u A collaboration with the International Council of Museums u An ontology of 85 classes and 130 properties for culture and more u With the capacity to explain dozens of (meta)data formats u Accepted by ISO TC 46 in Sept. 2000, now ISO/AWI 21127 proposed Committee Draft q Serving as: u intellectual guide to create schemata, formats, profiles u A language for analysis of existing sources for integration “Identify elements with common meaning” u Transportation format for data integration / migration / Internet ICS-FORTH October 21 -26, 2002 9

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 ICS-FORTH October 21 -26, 2002 Data Legacy bases systems Data in various forms 10

The CIDOC CRM Encoding of the CIDOC CRM q The CIDOC CRM is a formal ontology (defined in TELOS) u But CRM instances can be encoded in many forms: RDBMS, oo. DBMS, XML, RDF(S). u Uses Multiple isa – to achieve uniqueness of properties in the schema. u Uses multiple instantiation - to be able to combine not always valid combinations (e. g. destruction – activity). u Uses Multiple is. A for properties to capture different abstraction of relationships. q Methodological aspects: u Entities are introduced only if anchor of property ( if structurally relevant). u 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 collection material Ecclesiastical item container lid Museum Artefact belongs to church Holy Bread Basket Canister Ecclesiastical item 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 GE 34604 (entity E 22 Man-Made Object ) P 30 custody changed by, P 24 changed ownership by E 10 Transfer of Custody, E 8 Acquisition Event ) Transfer of Epitaphios GE 34604 (entity 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 Exchangable Fund of Refugees (entity P 40 Legal Body ) P 2 has type national foundation (entity E 55 Type ) P 14 carried out by (entity E 39 Actor ) Exchangable Fund of Refugees P 4 has time-span GE 34604_transfer_time (entity E 52 Time-Span ) P 82 at some time within 1923 - 1928 (entity E 59 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 ) P 86 falls within Europe (entity E 53 Place ) P 2 has type continent (entity E 55 Type ) ICS-FORTH October 21 -26, 2002 TGN data 13

The CIDOC CRM What does and what it does not q 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 refer to / identifie E 41 Appellations E 55 Types refer to / refine E 39 Actors E 28 Conceptual Objects E 18 Physical Stuff participate in affect or / refer to location E 2 Temporal Entities E 52 Time-Spans within ICS-FORTH October 21 -26, 2002 at E 53 Places 15

The CIDOC CRM A Classification of its Relationships u Identification of real world items by real world names. u Classification of real world items. u Part-decomposition and structural properties of Conceptual & Physical Objects, Periods, Actors, Places and Times. u Participation of persistent items in temporal entities. — creates a notion of history: “world-lines” meeting in space-time. u Location of periods in space-time and physical objects in space. u Influence of objects on activities and products and vice-versa. u 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 q. E 2 Temporal Entity u. 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 q. E 4 Period u binds together related phenomena u introduces inclusion topologies - parts etc. u Is confined in space and time u the basic unit for temporal-spatial reasoning q E 5 Event u looks at the input and the outcome u the basic unit for causal reasoning u each event is a period if we study the process q E 7 Activity u brings the people in u adds purpose ICS-FORTH October 21 -26, 2002 19

The CIDOC CRM Temporal Entity- Main Properties q. E 2 Temporal Entity u Properties: P 4 has time-span (is time-span of): E 52 Time-Span q. E 4 Period u Properties: P 7 took place at (witnessed): E 53 Place q. E 5 Event P 9 consists of (forms part of): E 4 Period P 10 falls within (contains): E 4 Period u Properties: P 11 had participant (participated in): E 39 Actor P 12 occurred in the presence of (was present at): E 77 Persistent Item q. E 7 Activity u Properties: P 14 carried out by (performed): E 39 Actor P 20 had specific purpose (was purpose of): E 7 Activity P 21 had general purpose (was purpose of): E 55 Type ICS-FORTH October 21 -26, 2002 20

The CIDOC CRM Termini postquem / antequem 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 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 e lif o t t in ) before h n g ou bor r 8 b (was 9 P 8 b ro (w ugh before as t i bo nt rn o li fe ) Birth of Leo I ICS-FORTH October 21 -26, 2002 n * -spa e m i t as of) P 4 h e-span m (is ti Birth of Attila Deduction: before 21

The CIDOC CRM The Participation Properties P 12 occurred in the presence of (was present at) E 5 Event E 77 Persistent Item P 11 had participant (participated in) E 5 Event E 39 Actor P 14 carried out by (performed) E 7 Activity E 39 Actor P 22 transferred title to (acquired title of) E 8 Acquisition Event E 39 Actor P 23 transferred title from (surrendered title of) E 8 Acquisition Event E 39 Actor P 28 custody surrendered by (surrendered custody) E 10 Transfer of Custody E 39 Actor P 29 custody received by (received custody) E 10 Transfer of Custody E 39 Actor P 95 has formed (was formed by) E 66 Formation Event E 74 Group P 96 by mother (gave birth) E 67 Birth E 21 Person P 98 brought into life (was born) E 67 Birth E 21 Person P 99 dissolved (was dissolved by) E 68 Dissolution E 74 Group P 100 was death of (died in) E 69 Death E 21 Person ICS-FORTH October 21 -26, 2002 22

The CIDOC CRM Activities CIDOC Notion E 1 CRM Entity E 59 Primitive Value 0, n P 2 has type (is type of) P 3 has note 0, n E 62 String 0, 1 E 55 Type E 5 Event E 7 Activity 1, n P 14 carried out by (performed) 0, n E 39 Actor P 14. 1 in the role of ICS-FORTH October 21 -26, 2002 23

The CIDOC CRM Activities: Measurement Event E 13 Attribute Assignment E 16 Measurement Event 1, 1 1, n P 40 observed dimension (was observed by) P 39 was measured by (measured) 0, n E 18 Physical Stuff 0, n ICS-FORTH October 21 -26, 2002 P 43 has dimension (is dimension of) 1, 1 E 54 Dimension P 90 has value P 91 unit 24

The CIDOC CRM Activities: Condition Assessment E 7 Activity 1, n P 14 carried out by (performed) 0, n E 39 Actor P 14. 1 in the role of E 14 Condition Assessment 1, n E 2 Temporal Entity 1, n P 34 was assessed by (concerns) P 35 has identified (identified by) 0, n E 18 Physical Stuff 0, n ICS-FORTH October 21 -26, 2002 P 44 has condition (condition of) E 3 Condition State 1, 1 25

The CIDOC CRM Activities: Acquisition Event E 7 Activity P 22 acquired title of (transferred title to) 0, n E 8 Acquisition Event 0, n P 23 surrendered title of (transferred title from) 0, n E 39 Actor 0, n 1, n P 24 transferred title of (changed ownership by) 0, n P 52 is current owner of (has current owner) 0, n E 18 Physical Stuff 0, n P 51 is former or current owner of (has former or current owner) ICS-FORTH October 21 -26, 2002 26

The CIDOC CRM Activities: Move P 20 had specific purpose (was purpose of) 0, n E 7 Activity 0, n P 21 had general purpose (was purpose of) 0, n E 55 Type E 9 Move 1, n P 25 moved by (moved) 1, n P 26 moved to (was destination of) P 27 moved from (was origin of) 0, n E 19 Physical Object P 55 has current location (currently holds) 0, n 1, n 0, n P 53 has former or current location (is ~ of) P 54 has current permanent location (is ~ of) ICS-FORTH October 21 -26, 2002 E 53 Place 0, n 27

The CIDOC CRM Activities: Modification/Production Event E 7 Activity P 14 carried out by (performed) 0, n E 39 Actor in the role of 1, n E 11 Modification Event 0, n 1, n E 55 Type 0, n P 32 used general technique (was technique of) E 18 Physical Stuff P 126 employed (was employed by) P 31 has modified (was modified by) 1, n P 45 consists of (is incorporated in) P 33 used specific technique (was used by) E 24 Physical Man-Made Stuff 0, n E 29 Design or Procedure ICS-FORTH October 21 -26, 2002 0, n P 68 usually employs (is usually employed by) 0, n E 57 Material 28

The CIDOC CRM Entity: Modification Event Properties: P 1 is identified by (identifies): E 41 Appellation P 2 has type (is type of): E 55 Type P 11 had participant (participated in): E 39 Actor P 14 carried out by (performed): E 39 Actor (P 14. 1 in the role of : E 55 Type) P 31 has modified (was modified by): E 24 Physical Man-Made Stuff P 12 occurred in the presence of (was present at): E 77 Persistent Item P 16 used specific object (was used for): E 70 Stuff (P 16. 1 mode of use: E 62 String) P 32 used general technique (was technique of): E 55 Type P 33 used specific technique (was used by): E 29 Design or Procedure P 17 was motivated by (motivated): E 1 CRM Entity P 19 was intended use of (was made for): E 71 Man-Made Stuff (P 19. 1 mode of use: E 62 String) P 20 had specific purpose (was purpose of): E 7 Activity P 21 had general purpose (was purpose of): E 55 Type P 126 employed (was employed by): E 57 Material inherited properties declared properties ICS-FORTH October 21 -26, 2002 29

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 ICS-FORTH October 21 -26, 2002 30

The CIDOC CRM Time-Span E 1 CRM Entity E 53 Place E 2 Temporal Entity P 10 falls within (contains) E 3 Condition State P 7 took place at (witnessed) P 4 (is has ti tim me e-s -sp pa a n o n f) E 52 Time Span P 86 falls within (contains) E 4 Period P 9 consists of (forms part of) P 82 at some time within E 77 Persistent Item P 78 is id e (ide ntified ntif ies) by P 81 ongoing throughout E 41 Appellation E 49 Time Appellation E 61 Time Primitive E 50 Date E 5 Event ICS-FORTH October 21 -26, 2002 31

The CIDOC CRM Example: Place q. E 53 Place u 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. u A “CRM Place” is not a landscape, not a seat - it is an abstraction from temporal changes - “the place where…” u A means to reason about the “where” in multiple reference systems. u 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 P 88 consists of (forms part of) P 7 took place at (witnessed) P 26 moved to (was destination of) E 53 Place es it fi by) n de fied i 7 ti P 8 den i (is E 44 Place Appellation E 46 Section Definition E 47 Spatial Coordinates E 48 Place Name E 45 Address ICS-FORTH October 21 -26, 2002 E 12 Production Event E 9 Move P 27 moved from (was origin of) P 5 (is 3 ha fo s f rm or P 5 er me P 25 moved 9 i or r o s l oc (moved by) cu r c rr ur (h ated en re as t l nt se on oc lo cti or ati ca on w on tio ) ith of n in ) P 58 defines section of (has section definition) P 108 has produced (was produced by) E 18 Physical Stuff E 24 Ph. M. -Made Stuff E 19 Physical Object 33

The CIDOC CRM Extension Example: Getty’s TGN P 89 falls within P 87 is identified by (identifies) E 53 Place E 39 Actor E 44 Place Appellation gn s t Place Naming an -sp e m s ti P a 4 h E 52 Time-Span ICS-FORTH October 21 -26, 2002 to c identified by carries out e a E 74 Group ac pl ok as si to P 7 e ac pl na m e to E 13 Attribute Assignment E 4 Period om mu nit y P 4 has time-span Community 34

Example from the TGN P 89 falls within y Kuyunjik P 87 is identified b (identifies) P 87 is identifi ed by (identifies) Nineveh TGN 7017998 20 th century 1 st mill. BC ICS-FORTH October 21 -26, 2002 me ass t e a ac n ha P 4 identified by assi pl ok carry out s n a gns ce nam e pla to P 7 People of Iraq ign TGN 1001441 -spa e m i Nineveh naming s t to c om P 4 has time-span mu nit y 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) 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 Event 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 ICS-FORTH October 21 -26, 2002 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) 42

The CIDOC CRM -Application Mapping DC to the CIDOC CRM Example: Partial DC Record about a painting Type. DCT 1: image Type: painting Title: Garden of Paradise Creator: Master of the Paradise Garden Publisher: Staedelsches Kunstitut ICS-FORTH October 21 -26, 2002 43

The CIDOC CRM -Application Mapping DC to the CIDOC CRM E 41 Appellation E 23 Information Carrier Object: PA 310 -1 A? ? ied n de i ced by du was pro is d by Name: Garden of Paradise E 12 Production carr Event: 0003 ied en tif is by Name: Master of the out b Paradise Garden y E 39 Actor ULAN: 4162 oc um in ente d E 31 Document nti fie db y Docu: 0001 has type E 65 Creation Event E 55 image Type DCT 1: AAT: painting Event: 0004 carried out by E 82 Actor Appellation Name: Staedelsches Kunstitut is ide was created by E 55 Type E 82 Actor Appellation id ed i f ti is …. . E 39 Actor: 0003 has typ e E 55 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 q Data acquisition needs different structure from presentation: u 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 u Integration / comprehension (target of the CRM): — restore connectivity with related subjects, — match and relate by underlying common concepts — no preference direction or subject u 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 q As an explanatory and mediation model, the CRM: u does not enforce constraints — optional properties, multivalued properties, multiple instantiation u contains redundant paths — “short cuts” of secondary processes, complex indirections u contains abstractions at various levels — of entities and — of attributes/properties ICS-FORTH October 21 -26, 2002 47

The CIDOC CRM Frequently asked questions q 1. Will the CRM require me to change my documentation ? Answer: u No. It makes no prescriptions. u You may, however, orient your document structures according to CRM constructs, so that an automatic transfer into a CRM-compatible form is possible. q 2. What is the benefit of standardisation? Answer: u 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 q 3. What does compatibility with the CRM mean? Answer: u That the parts of my data structure with the same scope can be explained by the CRM as: u u 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. q Still to be defined precisely. Major consensus issue. ICS-FORTH October 21 -26, 2002 49

The CIDOC CRM Frequently asked questions q 4. What does the CRM cover? Answer: Potentially the whole world as physical history in human perception! u 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) u The mapping exercise has verified the stability of model, its extensibility and the effectiveness of the methodology. u Experience of 6 -10 years development by interdisciplinary groups, sev implementations. ICS-FORTH October 21 -26, 2002 50

The CIDOC CRM Benefits of the CRM (From Tony Gill) q Elegant and simple compared to comparable Entity-Relationship models q Coherently integrates information at varying degrees of detail q Readily extensible through O-O class typing and specializations q Richer semantic content; allows inferences to be made from underspecified data elements q Designed for mediation of cultural heritage information ICS-FORTH October 21 -26, 2002 51

The CIDOC CRM State of Development q Proposed to ISO as Committee Draft. The structure is stable since four years. q 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. q. Elaboration of improved introduction, improvements on clarity of some scope notes, improved presentation until end of 2002. q Acceptance as standard expected by 2003. ICS-FORTH October 21 -26, 2002 52

The CIDOC CRM Conclusions q 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 q The CRM is in the ISO standardization process: u Dissemination for wide understanding and consensus u Extended application tests u Elaboration of details and documentation u Consensus ICS-FORTH October 21 -26, 2002 53