1. ICS-FORTH October 6 - 9, 2003 1 The CIDOC CRM, a Standard for the Integration of Cultural Information Martin Doerr, Stephen Stead Foundation for Research and Technology - Hellas Institute of Computer Science Prato, Italy April 12, 2004 Center for Cultural Informatics

2. ICS-FORTH October 6 - 9, 2003 2 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

3. ICS-FORTH October 6 - 9, 2003 3 The CIDOC CRM Cultural Diversity and Data Standards  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 methods, forms, communication means  Data overlap, but do not fit in one schema  Understanding lives from relationships, but how to express them?

4. ICS-FORTH October 6 - 9, 2003 4 The CIDOC CRM Historical Archives…. Type:Text Title: Protocol of Proceedings of Crimea Conference Title.Subtitle: II. Declaration of Liberated Europe Date: February 11, 1945. Creator:The Premier of the Union of Soviet Socialist Republics The Prime Minister of the United Kingdom The President of the United States of America Publisher:State Department Subject:Postwar division of Europe and Japan “ 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…… “ Documents Metadata About…

5. ICS-FORTH October 6 - 9, 2003 5 The CIDOC CRM Images, non-verbose… Type:Image Title: Allied Leaders at Yalta Date: 1945 Publisher:United Press International (UPI) Source:The Bettmann Archive Copyright:Corbis References:Churchill, Roosevelt, Stalin Photos, Persons Metadata About…

6. ICS-FORTH October 6 - 9, 2003 6 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

7. ICS-FORTH October 6 - 9, 2003 7 The CIDOC CRM Explicit Events, Object Identity, Symmetry P14 performed P11 participated in P94 has created E31 Document “Yalta Agreement” E7 Activity “Crimea Conference” E65 Creation Event * E38 Image P86 falls within P7 took place at P67 is referred to by E52 Time- Span February 1945 P81 ongoing throughout P82 at some time within E39 Actor E53 Place 7012124 E52 Time-Span 11-2-1945

8. ICS-FORTH October 6 - 9, 2003 8 The CIDOC CRM ……….  …captures the underlying semantics of relevant documentation structures in a formal ontology.  Ontologies are formalized knowledge: clearly defined concepts and relationships about possible states of affairs of a domain.  They can be understood by people and processed by machines to enable data exchange, data integration, query mediation.  Semantic interoperability in culture can be achieved by an “extensible ontology of relationships” and explicit event modeling, that provides shared explanation rather than prescription of a common data structure.  The ontology is the language S/W developers and museum experts can share. Therefore it needs interdisciplinary work. That is what CIDOC has done…

9. ICS-FORTH October 6 - 9, 2003 9 The CIDOC CRM Outcomes  The CIDOC Conceptual Reference Model  A collaboration with the International Council of Museums  An ontology of 80 classes and 132 properties for culture and more  With the capacity to explain dozens of (meta)data formats  Accepted by ISO TC46 in Sept. 2000, now ISO/CD 21127 accepted Committee Draft, proposed as DIS  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

10. ICS-FORTH October 6 - 9, 2003 10 The CIDOC CRM The Intellectual Role of the CRM Legacy systems Legacy systems Data bases World Phenomena ? Data structures & Presentation models Conceptualization abstracts from approximates explains, motivates organize refer to Data in various forms

11. ICS-FORTH October 6 - 9, 2003 11  Epistemological aspects:  Historical (also scientific, medical etc.) knowledge is incomplete and undecidable. Its elements have different statistical stability against knowledge revision: 1. Existence in discourse (London, Caesar, birth of Caesar, WW II, “take-over of Tikal”, King Arthur, Aphrodite) 2. Existence in real life (Master of the Paradise Garden) 3. Identity (London, Caesar, Aphrodite, Shakespeare) 4. Relations (where was El Greco born??) The CIDOC CRM Methodological aspects

12. ICS-FORTH October 6 - 9, 2003 12  Epistemological aspects:  Select concepts and network structure to increase monotonicity: — IsA: increase of stability / subclass: increase of knowledge — prefer transitions over states — aggregate opinions as propositions (relations) — Avoid replication of properties — Do not accept exceptions in the IsA hierarchy  Bottom-up development:  Generalization of the domain and range of relationships as driving force.  Avoid overgeneralization: Reduction of domain is not monotonic!! (such as “resource” in DC, “Manifestation” in FRBR) The CIDOC CRM Methodological aspects

13. ICS-FORTH October 6 - 9, 2003 13  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. The CIDOC CRM Encoding of the CIDOC CRM

14. ICS-FORTH October 6 - 9, 2003 Justifying Multiple Inheritance: achieving uniqueness of properties belongs to church Ecclesiastical item Holy Bread Basket container lid Museum Artefact museum number material collection Single Inheritance form: Museum Artefact museum number material collection Multiple Inheritance form: Canister container lid belongs to church Ecclesiastical item Canister container lid Holy Bread Basket Repetition of properties ! Unique identity of properties !

15. ICS-FORTH October 6 - 9, 2003 15 Transfer of Epitaphios GE34604 (entity E10 Transfer of Custody, E8 Acquisition Event ) 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 Ankar a P29 custody received by Museum Benaki P22 transferred title to Exchangable Fund of Refugees (entity P40 Legal Body ) P2 has type national foundation (entityE55 Type) P14 carried out by Exchangable Fund of Refugees P4 has time-span GE34604_transfer_time (entity E52 Time-Span) P82 at some time within 1923- 1928 (entityE61 Time Primitive) P7 took place at Greece (entityE53 Place) nation republic P86 falls within Europe (entityE53 Place ) continent Possible Encoding of Data as CIDOC CRM instance ( XML-style ) TGN data P30 custody transferred through,P24 changed ownership by Epitaphios GE34604 (entity E22 Man-Made Object ) (entity E39 Actor ) (entity E39 Actor ) (entity E39 Actor ) P2 has type (entityE55 Type) (entityE55 Type) P2 has type (entityE55 Type)

16. ICS-FORTH October 6 - 9, 2003 16 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

17. ICS-FORTH October 6 - 9, 2003 17 The CIDOC CRM Top-level Entities relevant for Integration participate in E39 Actors E55 Types E28 Conceptual Objects E18 Physical Stuff E2 Temporal Entities E41 Appellations affect or / refer to refer to / refine refer to / identifie location at within E53 Places E52 Time-Spans

18. ICS-FORTH October 6 - 9, 2003 18  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. The CIDOC CRM A Classification of its Relationships

19. ICS-FORTH October 6 - 9, 2003 19 The CIDOC CRM Example: The Temporal Entity Hierarchy

20. ICS-FORTH October 6 - 9, 2003 20 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.

21. ICS-FORTH October 6 - 9, 2003 21 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

22. ICS-FORTH October 6 - 9, 2003 22 The CIDOC CRM Temporal Entity- Main Properties  E2 Temporal Entity  Properties: P4 has time-span (is time-span of): E52 Time-Span  E4 Period  Properties: P7 took place at (witnessed): E53 Place P9 consists of (forms part of): E4 Period P10 falls within (contains): E4 Period  E5 Event  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

23. ICS-FORTH October 6 - 9, 2003 23 The CIDOC CRM Termini postquem / antequem Pope Leo I Attila meeting Leo I P14 carried out by (performed) P14 carried out by (performed) Birth of Leo I Birth of Attila Death of Leo I Death of Attila * P4 has time-span (is time-span of) * P4 has time-span (is time-span of) P100 was death of (died in) P100 was death of (died in) P98 brought into life (was born) P98 brought into life (was born) * P4 has time-span (is time- span of) P82 at some time within P82 at some time within AD453 AD461 AD452 before Deduction: before P11 had participant: P93 took o.o.existence: P92 brought i. existence: P82 at some time within

24. ICS-FORTH October 6 - 9, 2003 24 The CIDOC CRM The Participation Properties P12 occurred in the presence of (was present at)  P11 had participant (participated in)  P14 carried out by (performed)  P22 transferred title to (acquired title through)  P23 transferred title from (surrendered title of)  P28 custody surrendered by ( surrendered custody through )  P29 custody received by (received custody through)  P96 by mother (gave birth)  P99 dissolved (was dissolved by) E5 Event  E77 Persistent Item E5 Event  E39 Actor E7 Activity  E39 Actor E8 Acquisition Event  E39 Actor E10 Transfer of Custody  E39 Actor E67 Birth  E21 Person E68 Dissolution  E74 Group

25. ICS-FORTH October 6 - 9, 2003 25 P3 has note The CIDOC CRM Activities E1 CRM EntityCIDOC NotionE59 Primitive ValueE55 TypeE7 ActivityE5 Event 0,1 0,n P2 has type (is type of) 0,n E62 String 1,n 0,n E39 Actor P14 carried out by (performed) P14.1 in the role of

26. ICS-FORTH October 6 - 9, 2003 26 1,n 0,n 1,1 0,n 1,1 0,n P39 was measured by (measured) P40 observed dimension (was observed by) The CIDOC CRM Activities: Measurement Event E54 DimensionE16 Measurement EventE70 StuffE13 Attribute Assignment P43 has dimension (is dimension of) P90 has value P91 has unit (is unit of)

27. ICS-FORTH October 6 - 9, 2003 27 1,n 0,n 1,n 0,n 1,n 1,1 0,n E7 Activity E14 Condition Assessment E18 Physical Stuff E3 Condition State P44 has condition (condition of) P34 was assessed by (concerned) P35 has identified (identified by) E39 Actor P14 carried out by (performed) P14.1 in the role of E2 Temporal Entity The CIDOC CRM Activities: Condition Assessment

28. ICS-FORTH October 6 - 9, 2003 28 0,n E7 Activity E8 Acquisition Event E39 Actor E18 Physical Stuff P52 is current owner of (has current owner) P51 is former or current owner of (has former or current owner) P22 transferred title of (acquired title through) P24 transferred title of (changed ownership by) P23 transferred title from (surrendered title of) The CIDOC CRM Activities: Acquisition Event 1,n

29. ICS-FORTH October 6 - 9, 2003 29 1,n 0,n 1,n 0,n 0,1 0,n 1,n 0,n 0,1 0,n 1,n 0,n E7 Activity E9 Move E19 Physical Object E53 Place P25 moved by (moved) P26 moved to (was destination of) P55 has current location (currently holds) P27 moved from (was origin of) E55 Type P21 had general purpose (was purpose of) P20 had specific purpose (was purpose of) P54 has current permanent location (is ~ of) P53 has former or current location (is ~ of) The CIDOC CRM Activities: Move

30. ICS-FORTH October 6 - 9, 2003 30 0,n 1,n 0,n 1,n 0,n 1,n E7 Activity E11 Modification Event E18 Physical Stuff P31 has modified (was modified by) E39 Actor P14 carried out by (performed) P14.1 in the r ole of E55 Type P32 used general technique (was technique of) E24 Physical Man-Made Stuff E29 Design or Procedure P33 used specific technique (was used by) E57 Material P45 consists of (is incorporated in) P68 usually employs (is usually employed by) The CIDOC CRM Activities: Modification/Production Event P126 employed (was employed by) 0,n

31. ICS-FORTH October 6 - 9, 2003 31 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): E19 Physical Object (P16.1 mode of use: E55 Type) 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: E55 Type) P20 had specific purpose (was purpose of): E7 Activity P21 had general purpose (was purpose of): E55 Type P126 employed (was employed in): E57 Material declared properties inherited properties declared properties inherited properties declared properties

32. ICS-FORTH October 6 - 9, 2003 32 time before P82 at some time within P81 ongoing throughout after “ intensity ” The CIDOC CRM Time Uncertainty, Certainty and Duration Duration (P83,P84)

33. ICS-FORTH October 6 - 9, 2003 33 E3 Condition State E4 Period E5 Event E50 Date E49 Time Appellation E41 Appellation E2 Temporal Entity E52 Time Span E1 CRM Entity E53 Place P4 has time-span (is time-span of) P86 falls within (contains) P10 falls within (contains) P9 consists of (forms part of) P78 is identified by (identifies) The CIDOC CRM Time-Span E77 Persistent Item E61 Time Primitive P81 ongoing throughout P82 at some time within P7 took place at (witnessed)

34. ICS-FORTH October 6 - 9, 2003 34 The CIDOC CRM Example: Place  E53 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: figures from the bow of a ship, African dinosaur foot-prints in Portugal

35. ICS-FORTH October 6 - 9, 2003 35 The CIDOC CRM Place E45 Address E48 Place Name E47 Spatial Coordinates E46 Section DefinitionE18 Physical Stuff E44 Place Appellation E53 Place P88 consists of (forms part of) P58 defines section of (has section definition) P59 is located on or within (has section) P87 identifies (is identified by) P53 has former or current location (is former or current location of ) E9 Move P26 moved to (was destination of) P27 moved from (was origin of) P25 moved (moved by) E12 Production Event P108 has produced (was produced by) P7 took place at (witnessed) E19 Physical Object E24 Ph. M.-Made Stuff

36. ICS-FORTH October 6 - 9, 2003 36 E13 Attribute Assignment Place NamingE74 Group E39 Actor E53 Place E52 Time-Span Community E44 Place Appellation P89 falls within P87 is identified by (identifies) assigns name E4 Period to community identified by carries out P4 has time-span to place P7 took place at P4 has time-span The CIDOC CRM Extension Example: Getty’s TGN

37. ICS-FORTH October 6 - 9, 2003 37 Nineveh naming People of Iraq TGN7017998 1st mill. BC City of Nineveh Kuyunjik P89 falls within P87 is identified by (identifies) assigns name to community identified by carry out P4 has time-span to place P7 took place at P4 has time-span Example from the TGN 20 th century Nineveh P87 is identified by (identifies) Nineveh naming assigns name TGN1001441

38. ICS-FORTH October 6 - 9, 2003 38 The CIDOC CRM Stuff

39. ICS-FORTH October 6 - 9, 2003 39 The CIDOC CRM Physical Stuff

40. ICS-FORTH October 6 - 9, 2003 40 The CIDOC CRM Conceptual Object

41. ICS-FORTH October 6 - 9, 2003 41 The CIDOC CRM Actor

42. ICS-FORTH October 6 - 9, 2003 42 The CIDOC CRM Appellation

43. ICS-FORTH October 6 - 9, 2003 43 The CIDOC CRM Changing Stuff E18 Physical Stuff E11 Modification Event P111 added (was added by) E79 Part Addition E80 Part Removal P110 augmented (was augmented by) E24 Ph. M.-Made Stuff P113 removed (was removed by) P112 diminished (was diminished by) E77 Persistent Item E81 Transformation E64 End of ExistenceE63 Beginning of Existence P124 transformed (was transformed by) P123 resulted in (resulted from) P92 brought into existence (was brought into existence by) P93 took out of existence (was taken o.o.e. by) P31 has modified (was modified by)

44. ICS-FORTH October 6 - 9, 2003 44 The CIDOC CRM Taxonomic discourse E28 Conceptual Object E7 Activity E17 Type Assignment E55 Type P136 was based on (supported type creation) P42 assigned (was assigned by) E1 CRM Entity E83 Type Creation E65 Creation Event P137 is exemplified by (exemplifies) P41 classified (was classified by) P94 has created (was created by) P135 created type (was created by) P136.1 in the taxonomic role P137.1 in the taxonomic role

45. ICS-FORTH October 6 - 9, 2003 45 The CIDOC CRM Specific and general Use E7 Activity E70 Stuff P16 used specific object (was used by) E55 Type E1 CRM Entity P125 used object of type (was type of object used in) P101 had as general use (was use of) P15 was influenced by (influenced) E55 Type P16.1 mode of use

46. ICS-FORTH October 6 - 9, 2003 46 The CIDOC CRM Visual Contents and Subject E24 Physical Man-Made Stuff E55 Type E1 CRM Entity P62 depicts (is depicted by) P62.1 mode of depiction P65 shows visual item (is shown by) E36 Visual Item P138 represents (has representation) E73 Information Object E38 Visual Image P67 refers to (is referred to by) E84 Information Carrier P128 carries (is carried by) P138.1 mode of depiction

47. ICS-FORTH October 6 - 9, 2003 47 The CIDOC CRM -Application Mapping DC to the CIDOC CRM 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 Example: Partial DC Record about a Technical Report

48. ICS-FORTH October 6 - 9, 2003 48 was created by is identified by E41 Appellation Name: Mapping of the Dublin Core Metadata Element Set to the CIDOC CRM ….. E33 Linguistic Object Object: FORTH-ICS / TR-274 July 2000 E82 Actor Appellation Name: Martin Doerr E65 Creation Event Event: 0001 carried out by is identified by E82 Actor Appellation Name: ICS-FORTH E7 Activity Event: 0002 carried out by E55 Type Type: Publication has type was used for E75 Conceptual Object Appellation Name : FORTH-ICS / TR-274 July 2000 E55 Type Type: FORTH Identifier has type is identified by E56 Language Lang.: English has language The CIDOC CRM -Application Mapping DC to the CIDOC CRM (RDF style) E39 Actor Actor:0001 E39 Actor Actor:0002 is identified by (background knowledge not in the DC record)

49. ICS-FORTH October 6 - 9, 2003 49 Type.DCT1: image Type: painting Title: Garden of Paradise Creator: Master of the Paradise Garden Publisher: Staedelsches Kunstinstitut Example: Partial DC Record about a painting The CIDOC CRM -Application Mapping DC to the CIDOC CRM

50. ICS-FORTH October 6 - 9, 2003 50 is identified by E41 Appellation Name: Garden of Paradise ….. E73 Information Carrier Object: PA 310-1A?? E82 Actor Appellation Name: Master of the Paradise Garden E39 Actor ULAN: 4162 E12 Production Event Event: 0003 carried out by is identified by E82 Actor Appellation Name: Staedelsches Kunstinstitut E39 Actor Actor: 0003 E65 Creation Event carried out by is identified by E55 Type Type: Publication Creation has type is documented in E31 Document Docu: 0001 was created by has type was produced by The CIDOC CRM -Application Mapping DC to the CIDOC CRM E55 Type AAT: painting E55 Type DCT1: image Event: 0004 (AAT: background knowledge not in the DC record)

51. ICS-FORTH October 6 - 9, 2003 51 The CIDOC CRM -Application Repository Indexing ActorsEventsObjects Derived knowledge data (e.g. RDF) Thesauri extent CRM entities Ontology expansion Sources and metadata (XML/RDF) Background knowledge / Authorities CIDOC CRM

52. ICS-FORTH October 6 - 9, 2003 52 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

53. ICS-FORTH October 6 - 9, 2003 53  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 The CIDOC CRM About the CRM

54. ICS-FORTH October 6 - 9, 2003 54  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 The CIDOC CRM Benefits of the CRM (From Tony Gill)

55. ICS-FORTH October 6 - 9, 2003 55  Doing all that, we encounter a surprise compared with common preconceptions:  Nearly no domain specificity (e.g.“current permanent location”), generic concepts appearing 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 CIDOC CRM Conclusions

56. ICS-FORTH October 6 - 9, 2003 56  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 end of the ISO standardization process:  Dissemination for wide understanding and consensus.  Extended application tests, development of tools.  Community building for experience exchange. The CIDOC CRM Conclusions

57. ICS-FORTH October 6 - 9, 2003 57  Version 3.2.1 accepted by ISO as Committee Draft. The structure is stable since five years.  Since version 3.2.1, the SIG has elaborated extension to satisfy archeology, Natural History and relationships to Digital Libraries.  Complete review of all scope notes and introductory texts. Version 3.4.10 submitted as DIS.  Acceptance as DIS expected by begin 2004. The CIDOC CRM State of Development