Definition of the
Table of Contents
Definition of the CIDOC Conceptual Reference Model
This document is the formal definition of the CIDOC Conceptual Reference Model (“CRM”), a formal ontology intended to facilitate the integration, mediation and interchange of heterogeneous cultural heritage information. The CRM is the culmination of more than a decade of standards development work by the International Committee for Documentation (CIDOC) of the International Council of Museums (ICOM). Work on the CRM itself began in 1996 under the auspices of the ICOM-CIDOC Documentation Standards Working Group. Since 2000, development of the CRM has been officially delegated by ICOM-CIDOC to the CIDOC CRM Special Interest Group, which collaborates with the ISO working group ISO/TC46/SC4/WG9 to bring the CRM to the form and status of an International Standard.
The primary role of the CRM is to enable information exchange and integration between heterogeneous sources of cultural heritage information. It aims at providing the semantic definitions and clarifications needed to transform disparate, localised information sources into a coherent global resource, be it within a larger institution, in intranets or on the Internet.
Its perspective is supra-institutional and abstracted from any specific local context. This goal determines the constructs and level of detail of the CRM.
More specifically, it defines and is restricted to the underlying semantics of database schemata and document structures used in cultural heritage and museum documentation in terms of a formal ontology. It does not define any of the terminology appearing typically as data in the respective data structures; however it foresees the characteristic relationships for its use. It does not aim at proposing what cultural institutions should document. Rather it explains the logic of what they actually currently document, and thereby enables semantic interoperability.
It intends to provide an optimal analysis of the intellectual structure of cultural documentation in logical terms. As such, it is not optimised to implementation-specific storage and processing aspects. Rather, it provides the means to understand the effects of such optimisations to the semantic accessibility of the respective contents.
The CRM aims to support the following specific functionalities:
Users of the CRM should be aware that the definition of data entry systems requires support of community-specific terminology, guidance to what should be documented and in which sequence, and application-specific consistency controls. The CRM does not provide such notions.
By its very structure and formalism, the CRM is extensible and users are encouraged to create extensions for the needs of more specialized communities and applications.
The overall scope of the CIDOC CRM can be summarised in simple terms as the curated knowledge of museums.
However, a more detailed and useful definition can be articulated by defining both the Intended Scope, a broad and maximally-inclusive definition of general application principles, and the Practical Scope, which is expressed by the overall scope of a reference set of specific identifiable museum documentation standards and practices that the CRM aims to encompass, however restricted in its details to the limitations of the Intended Scope.
The Intended Scope of the CRM may be defined as all information required for the exchange and integration of heterogeneous scientific documentation of museum collections. This definition requires further elaboration:
The Practical Scope of the CRM is expressed in terms of the current reference standards for museum documentation that have been used to guide and validate the CRM’s development. The CRM covers the same domain of discourse as the union of these reference standards; this means that data for data correctly encoded according to these museum documentation standards there can be a CRM-compatible expression that conveys the same meaning.
The goal of the CRM is to enable the integration of the largest number of information resources. Therefore it aims to provide the greatest flexibility of systems to become compatible, rather than imposing one particular solution.
Users intending to take advantage of the semantic interoperability offered by the CRM may want to make parts of their data structures compatible with the CRM. Compatibility may pertain either to the associations by which users would like their data to be accessible in an integrated environment, or to the contents intended for transport to other environments, allowing encoded meaning to be preserved in a target system
The CRM does not require complete matching of all user documentation structures with the CRM, nor that systems should always implement all CRM concepts and associations; instead it leaves room both for extensions, needed to capture the full richness of cultural information, and for simplifications, required for reasons of economy.
Furthermore, the CRM provides a means of interpreting structured information so that large amounts of data can be transformed or mediated automatically. It does not require unstructured or semi-structured free text information to be analysed into a formal logical representation. In other words, it does not aim to provide more structure than users have previously provided. The interpretation of information in the form of free text falls outside the scope of compatibility considerations. The CRM does, however, allow free text information to be integrated with structured information.
The notion of CRM compatibility is based on interoperability. Interoperability is best defined on the basis of specific communication practices between information systems. Following current practice, we distinguish the following types of information integration environments pertaining to information systems:
a. Materialized access systems, which physically import data provided by local systems, using a data warehouse approach. Such systems may employ so-called metadata harvesting techniques or rely on data submission. Data may be transformed to respect the schema of the access system before being merged.
b. Mediation systems, [Gio Wiederholt] which send out queries, formulated according to a virtual global schema, to multiple local systems and then collect and integrate the answers. The queries may be transformed to a local schema either by the mediation system or by the receiving local system itself.
Local systems may also import data from other systems, in order to complement collections, or to merge information from other systems. An information system may export information for migration and preservation.
Compatibility with the CRM pertains to one or more of the following data communication capabilities or use cases:
Any declaration of CRM compatibility must specify one or more of the above use cases. System and data structure providers shall not declare their products as “CRM compatible” without specifying the appropriate use cases as detailed below.
In the context of this chapter, the expression “without loss of meaning with respect to the CRM concepts” means the following: The CRM concepts are used to classify items of discourse and their relationships. By virtue of this classification, data can be understood as propositions of a kind declared by the CRM about real world facts, such as “Object x. forms part of: Object y”. In case the encoding, i.e. the language used to describe a fact, is changed, only an expert conversant with both languages can assess if the two propositions do indeed describe the same fact. If this is the case, then there is no loss of meaning with respect to CRM concepts. Communities of practice requiring fewer concepts than the CRM declares may restrict CRM compatibility with respect to an explicitly declared subset of the CRM.
Users of this standard may communicate CRM compatible data, as detailed below, with data structures and systems that are either more detailed and specialized than the CRM or whose scope extends beyond that of the CRM. In such cases, the standard guarantees only the preservation of meaning with respect to CRM concepts. However, additional information that can be regarded as extending CRM concepts may be communicated and preserved in CRM compatible systems through the appropriate use of controlled terminology. The specification of the latter techniques does not fall under the scope of this standard. Communities of practice requiring extensions to the CRM are encouraged to declare their extensions as CRM-compatible standards.
The CRM is a formal ontology which can be expressed in terms of logic or a suitable knowledge representation language. Its concepts can be instantiated as sets of statements that provide a model of reality. We call any encoding of such CRM instances in a formal language that preserves the relations between the CRM classes, properties and inheritance rules a “CRM-compatible form”. Hence data expressed in any CRM-compatible form can be automatically transformed into any other CRM-compatible form without loss of meaning. Classes and properties of the CRM are identified by their initial codes, such as “E55” or “P12”. The names of classes and properties of a CRM-compatible form may be translated into any local language, but the identifying codes must be preserved. A CRM-compatible form should not implement the quantifiers of CRM properties as cardinality constraints for the encoded instances. Quantifiers may be implemented in an informative way, or not at all. Statements that violate quantifiers should be treated as alternative knowledge.
Any encoding of CRM instances in a formal language that preserves the relations within a consistent subset of CRM classes, properties and inheritance rules is regarded a “reduced CRM-compatible form”, if:
A data structure is export-compatible with the CRM if it is possible to transform any data from this data structure into a CRM-compatible form without loss of meaning. Implicit concepts may be present in elements of the data structure that are not supported by the CRM. As long as these concepts can be encoded as instances of E55 Type (i.e. as terminology) and attached unambiguously to their respective data items with suitable properties, the data structure is still regarded as export compatible.
Note that not all CRM concepts may be represented by elements of an export-compatible data structure. All data from export-compatible data structures can be transported in a CRM-compatible form. In particular any CRM compatible form or reduced CRM-compatible form is export-compatible with the CRM.
A data structure is import-compatible with the CRM if it is possible to automatically transform any data from a CRM-compatible form into this data structure without loss of meaning, simply on the basis of knowledge about the data structure elements being used. This implies that a data record transformed into this data structure from a CRM-compatible form can be transformed back into the CRM-compatible form without loss of meaning. Note that the back-transformation into a CRM-compatible form may result in a data record that is semantically equivalent but not identical with the original.
Any CRM-compatible form is automatically import-compatible with the CRM. Note that an import-compatible data structure may be semantically richer than the CRM. It may contain elements that, through the use of a transformation algorithm, can be made to correspond to CRM concepts or specializations thereof or that contain elements with meanings that fall outside the scope of the CRM. However, it must not contain elements that overlap in meaning with CRM concepts and which cannot be subsumed via transformation by a CRM concept other than E1 CRM Entity and E77 Persistent Item.
Import-compatible data structures may be used to transport data for applications that require concepts that lie beyond the scope of the CRM, as well as data from any export-compatible data structure. Note that, in general, applications may make use of data from a CRM import-compatible data structure that has been exported into a CRM compatible form by semantic reduction to CRM concepts, i.e. by generalizing all subsumed concepts to the most specific CRM concept applicable, and by discarding elements that fall outside the scope of the CRM.
A data structure is partially import-compatible with the CRM if the above holds for a reduced CRM-compatible form.
An information system is export-compatible with the CRM if it is possible to export all user data from this information system into an import-compatible data structure. This capability is the recommended kind of CRM-compatibility for local information systems.
An information system is partially export compatible if it is possible to export all user data from this information system into a partially import-compatible data structure. This is not the recommended kind of CRM-compatibility, but it may not be feasible for legacy systems to acquire a higher level of CRM compatibility without unreasonable effort. This reduced level of CRM compatibility is nonetheless highly useful.
Note that there is no minimum requirement for the classes and properties that must be present in the exported user data. Therefore it is possible that the data may pertain to instances of just a single property, such as E21 Person. P131 is identified by: E82 Actor Appellation.
An information system is import-compatible with the CRM if it is possible to import data encoded in a CRM-compatible form and to access the data in a manner equivalent to and homogeneous with all generic data of this system that fall under the same concepts. This capability is considered as the normal kind of CRM compatibility for integrated access systems that physically copy source data in a data warehouse style (materialized access systems).
An information system is partially import-compatible with the CRM if it is possible to import data encoded in a reduced CRM-compatible form and to access the data in a manner equivalent to and homogeneous with all generic data of this system that fall under the same concepts. Depending on the functional requirements, it makes sense for integrated access systems to offer access services of reduced complexity by being only partially import-compatible with the CRM.
Note that it makes sense for integrated access systems to import data from extended data structures by semantic reduction to CRM defined concepts.
Note that local information system providers may choose to make their systems import-compatible with the CRM to be import-compatible with the CRM in order to exchange data, for example in the case of museum object loans or for system migration purposes. Communities of practice may choose to agree on import compatibility for extended data structures.
Some local information systems are likely to focus on specialized subject areas, such as inscriptions. For these specialized systems, the ability to import a specific data structure is recommended. This should be export-compatible with the CRM, and encompass the concepts that are required by the subject matter (“dedicated import compatibility”).
An information system is access-compatible with the CRM if it is possible to access the user data in the information system by querying with CRM classes and properties so that the meaning of the answers to the queries corresponds to the query terms used. It is not regarded as a reduction of compatibility if access is limited to data deemed to be exchanged.
An information system is partially access-compatible with the CRM if it is possible to access the user data in the information system by querying with a consistent subset of CRM classes and properties, corresponding to a reduced CRM-compatible form, so that the meaning of the answers to the queries corresponds to the query terms used.
An access-compatible system may be export-compatible with respect to the query answers. Note that it may make sense for an access-compatible content management system to return only content items in response to queries rather than being export compatible.
fig. 1: Possible data flow between different kinds of CRM-compatible systems and data structures
Fig. 1 shows a symbolic representation of some of the data flow patterns defined above between different kinds of CRM-compatible systems and data structures. In this figure it is assumed that the Local System B exports data into a CRM export-compatible data structure, which implies that it can be exported into a CRM-compatible form or any other CRM import-compatible data structure. Therefore Local System B is export-compatible with the CRM. For Local System A, the figure symbolizes the case where the exported data contain elements that correspond to specializations of the CRM or fall out of its scope.
A provider of a data structure or information system claiming compatibility with the CRM has to provide a declaration that describes the kind of compatibility and, depending on the kind, the following additional information:
The subset of CRM concepts directly instantiated by any possible data in this data structure after transformation into a CRM-compatible form.
The subset of CRM concepts under which data can be imported into the system.
The provider should be able to demonstrate the claim with suitable test data. The provider should be able to demonstrate its claim according to certain procedures included in any applicable certificate practice related statement.
The provider should either make evidence of these procedures publicly available on the Internet on a site nominated by the ISO community of use, so that any third party is able to verify the claim with suitable test data, or acquire a certificate by a certification authority (CA).
A trusted third party recognised and authorised by a competent regulatory authority to act as a CA in this practice area, should be able to verify the credentials of the provider applying for such certificate and thus, of its claim with suitable test data, before issuing the certificate so that the users can trust the information in the CA certificates.
The CA will grant the provider of the certified system the right to use the “CRM compatible” logo.
The CRM is an ontology in the sense used in computer science. It has been expressed as an object-oriented semantic model, in the hope that this formulation will be comprehensible to both documentation experts and information scientists alike, while at the same time being readily converted to machine-readable formats such as RDF Schema, KIF, DAML+OIL, OWL, STEP, etc. It can be implemented in any Relational or object-oriented schema. CRM instances can also be encoded in RDF, XML, DAML+OIL, OWL and others.
Although the definition of the CRM provided here is complete, it is an intentionally compact and concise presentation of the CRM’s 86 classes and 137 unique properties. It does not attempt to articulate the inheritance of properties by subclasses throughout the class hierarchy (this would require the declaration of several thousand properties, as opposed to 137). However, this definition does contain all of the information necessary to infer and automatically generate a full declaration of all properties, including inherited properties.
The following definitions of key terminology used in this document are provided both as an aid to readers unfamiliar with object-oriented modelling terminology, and to specify the precise usage of terms that are sometimes applied inconsistently across the object oriented modelling community for the purpose of this document. Where applicable, the editors have tried to consistently use terminology that is compatible with that of the Resource Description Framework (RDF), a recommendation of the World Wide Web Consortium. The editors have tried to find a language which is comprehensible to the non-computer expert and precise enough for the computer expert so that both understand the intended meaning.
Quantifiers for properties are provided for the purpose of semantic clarification only, and should not be treated as implementation recommendations. The CRM has been designed to accommodate alternative opinions and incomplete information, and therefore all properties should be implemented as optional and repeatable for their domain and range (“many to many (0,n:0,n)”). Therefore the term “cardinality constraints” is avoided here, as it typically pertains to implementations.
The following table lists all possible property quantifiers occurring in this document by their notation, together with an explanation in plain words. In order to provide optimal clarity, two widely accepted notations are used redundantly in this document, a verbal and a numeric one. The verbal notation uses phrases such as “one to many”, and the numeric one, expressions such as “(0,n:0,1)”. While the terms “one”, “many” and “necessary” are quite intuitive, the term “dependent” denotes a situation where a range instance cannot exist without an instance of the respective property. In other words, the property is “necessary” for its range.
The CRM defines some properties as being necessary for their domain or as being dependent from their range, following the definitions in the table above. Note that if such a property is not specified for an instance of the respective domain or range, it means that the property exists, but the value on one side of the property is unknown. In the case of optional properties, the methodology proposed by the CRM does not distinguish between a value being unknown or the property not being applicable at all. For example, one may know that an object has an owner, but the owner is unknown. In a CRM instance this case cannot be distinguished from the fact that the object has no owner at all. Of course, such details can always be specified by a textual note.
The following naming conventions have been applied throughout the CRM:
The following modelling principles have guided and informed the development of the CIDOC CRM.
Because the CRM’s primary role is the meaningful integration of information in an Open World, it aims to be monotonic in the sense of Domain Theory. That is, the existing CRM constructs and the deductions made from them must always remain valid and well-formed, even as new constructs are added by extensions to the CRM.
One may add a subclass of E7 Activity to describe the practice of an instance of group to use a certain name for a place over a certain time-span. By this extension, no existing IsA Relationships or property inheritances are compromised.
In addition, the CRM aims to enable the formal preservation of monotonicity when augmenting a particular CRM compatible system. That is, existing CRM instances, their properties and deductions made from them, should always remain valid and well-formed, even as new instances, regarded as consistent by the domain expert, are added to the system.
If someone describes correctly that an item is an instance of E19 Physical Object, and later it is correctly characterized as an instance of E20 Biological Object, the system should not stop treating it as an instance of E19 Physical Object.
In order to formally preserve monotonicity for the frequent cases of alternative opinions, all formally defined properties should be implemented as unconstrained (many: many) so that conflicting instances of properties are merely accumulated. Thus knowledge integrated following the CRM serves as a research base, accumulating relevant alternative opinions around well-defined entities, whereas conclusions about the truth are the task of open-ended scientific or scholarly hypothesis building.
El Greco and even King Arthur should always remain an instance of E21 Person and be dealt with as existing within the sense of our discourse, once they are entered into our knowledge base. Alternative opinions about properties, such as their birthplaces and their living places, should be accumulated without validity decisions being made during data compilation.
Although the scope of the CRM is very broad, the model itself is constructed as economically as possible.
· A class is not declared unless it is required as the domain or range of a property not appropriate to its superclass, or it is a key concept in the practical scope.
· CRM classes and properties that share a superclass are non-exclusive by default. For example, an object may be both an instance of E20 Biological Object and E22 Man-made Object.
· CRM classes and properties are either primitive, or they are key concepts in the practical scope.
· Complements of CRM classes are not declared.
Some properties are declared as shortcuts of longer, more comprehensively articulated paths that connect the same domain and range classes as the shortcut property via one or more intermediate classes. For example, the property E18 Physical Thing. P52 has current owner (is current owner of): E39 Actor, is a shortcut for a fully articulated path from E18 Physical Thing through E8 Acquisition to E39 Actor. An instance of the fully-articulated path always implies an instance of the shortcut property. However, the inverse may not be true; an instance of the fully-articulated path cannot always be inferred from an instance of the shortcut property.
The class E13 Attribute Assignment allows for the documentation of how the assignment of any property came about, and whose opinion it was, even in cases of properties not explicitly characterized as “shortcuts”.
Classes are disjoint if they share no common instances in any possible world. There are many examples of disjoint classes in the CRM.
A comprehensive declaration of all possible disjoint class combinations afforded by the CRM has not been provided here; it would be of questionable practical utility, and may easily become inconsistent with the goal of providing a concise definition. However, there are two key examples of disjoint class pairs that are fundamental to effective comprehension of the CRM:
· E2 Temporal Entity is disjoint from E77 Persistent Item. Instances of the class E2 Temporal Entity are perdurants, whereas instances of the class E77 Persistent Item are endurants. Even though instances of E77 Persistent Item have a limited existence in time, they are fundamentally different in nature from instances of E2 Temporal Entity, because they preserve their identity between events. Declaring endurants and perdurants as disjoint classes is consistent with the distinctions made in data structures that fall within the CRM’s practical scope.
· E18 Physical Thing is disjoint from E28 Conceptual Object. The distinction is between material and immaterial items, the latter being exclusively man-made. Instances of E18 Physical Thing and E28 Conceptual Object differ in many fundamental ways; for example, the production of instances of E18 Physical Thing implies the incorporation of physical material, whereas the production of instances of E28 Conceptual Object does not. Similarly, instances of E18 Physical Thing cease to exist when destroyed, whereas an instance of E28 Conceptual Object perishes when it is forgotten or its last physical carrier is destroyed.
Virtually all structured descriptions of museum objects begin with a unique object identifier and information about the "type" of the object, often in a set of fields with names like "Classification", "Category", "Object Type", "Object Name", etc. All these fields are used for terms that declare that the object belongs to a particular category of items. In the CRM the class E55 Type comprises such terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts (universals) in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
For this purpose the CRM provides two basic properties that describe classification with terminology, corresponding to what is the current practice in the majority of information systems. The class E1 CRM Entity is the domain of the property P2 has type (is type of), which has the range E55 Type. Consequently, every class in the CRM, with the exception of E59 Primitive Value, inherits the property P2 has type (is type of). This provides a general mechanism for simulating a specialization of the classification of CRM instances to any level of detail, by linking to external vocabulary sources, thesauri, classification schema or ontologies.
Analogous to the function of the P2 has type (is type of) property, some properties in the CRM are associated with an additional property. These are numbered in the CRM documentation with a ‘.1’ extension. The range of these properties of properties always falls under E55 Type. Their purpose is to simulate a specialization of their parent property through the use of property subtypes declared as instances of E55 Type. They do not appear in the property hierarchy list but are included as part of the property declarations and referred to in the class declarations. For example, P62.1 mode of depiction: E55 Type is associated with E24 Physical Man-made Thing. P62 depicts (is depicted by): E1 CRM Entity.
The class E55 Type also serves as the range of properties that relate to categorical knowledge commonly found in cultural documentation. For example, the property P125 used object of type (was type of object used in) enables the CRM to express statements such as “this casting was produced using a mould”, meaning that there has been an unknown or unmentioned object, a mould, that was actually used. This enables the specific instance of the casting to be associated with the entire type of manufacturing devices known as moulds. Further, the objects of type “mould” would be related via P2 has type (is type of) to this term. This indirect relationship may actually help in detecting the unknown object in an integrated environment. On the other side, some casting may refer directly to a known mould via P16 used specific object (was used for). So a statistical question to how many objects in a certain collection are made with moulds could be answered correctly (following both paths through P16 used specific object (was used for) - P2 has type (is type of) and P125 used object of type (was type of object used in). This consistent treatment of categorical knowledge enhances the CRM’s ability to integrate cultural knowledge.
In addition to being an interface to external thesauri and classification systems E55 Type is an ordinary class in the CRM and a subclass of E28 Conceptual Object. E55 Type and its subclasses inherit all properties from this superclass. Thus together with the CRM class E83 Type Creation the rigorous scholarly or scientific process that ensures a type is exhaustively described and appropriately named can be modelled inside the CRM. In some cases, particularly in archaeology and the life sciences, E83 Type Creation requires the identification of an exemplary specimen and the publication of the type definition in an appropriate scholarly forum. This is very central to research in the life sciences, where a type would be referred to as a “taxon,” the type description as a “protologue,” and the exemplary specimens as “original element” or “holotype”.
Finally, types, that is, instances of E55 Type and its subclasses, are used to characterize the instances of a CRM class and hence refine the meaning of the class. A type ‘artist’ can be used to characterize persons through P2 has type (is type of). On the other hand, in an art history application of the CRM it can be adequate to extend the CRM class E21 Person with a subclass E21.xx Artist. What is the difference of the type ‘artist’ and the class Artist? From an everyday conceptual point of view there is no difference. Both denote the concept ‘artist’ and identify the same set of persons. Thus in this setting a type could be seen as a class and the class of types may be seen as a metaclass. Since current systems do not provide an adequate control of user defined metaclasses, the CRM prefers to model instances of E55 Type as if they were particulars, with the relationships described in the previous paragraphs.
Users may decide to implement a concept either as a subclass extending the CRM class system or as an instance of E55 Type. A new subclass should only be created in case the concept is sufficiently stable and associated with additional explicitly modeled properties specific to it. Otherwise, an instance of E55 Type provides more flexibility of use. Users that may want to describe a discourse not only using a concept extending the CRM but also describing the history of this concept itself, may chose to model the same concept both as subclass and as an instance of E55 Type with the same name. Similarly it should be regarded as good practice to foresee for each term hierarchy refining a CRM class a term equivalent of this class as top term. For instance, a term hierarchy for instances of E21 Person may begin with “Person”.
Since the intended scope of the CRM is a subset of the “real” world and is therefore potentially infinite, the model has been designed to be extensible through the linkage of compatible external type hierarchies.
Compatibility of extensions with the CRM means that data structured according to an extension must also remain valid as a CRM instance. In practical terms, this implies query containment: any queries based on CRM concepts should retrieve a result set that is correct according to the CRM’s semantics, regardless of whether the knowledge base is structured according to the CRM’s semantics alone, or according to the CRM plus compatible extensions. For example, a query such as “list all events” should recall 100% of the instances deemed to be events by the CRM, regardless of how they are classified by the extension.
A sufficient condition for the compatibility of an extension with the CRM is that CRM classes subsume all classes of the extension, and all properties of the extension are either subsumed by CRM properties, or are part of a path for which a CRM property is a shortcut. Obviously, such a condition can only be tested intellectually.
Of necessity, some concepts covered by the CRM are less thoroughly elaborated than others: E39 Actor and E30 Right, for example. This is a natural consequence of staying within the CRM’s clearly articulated practical scope in an intrinsically unlimited domain of discourse. These ‘underdeveloped’ concepts can be considered as hooks for compatible extensions.
The CRM provides a number of mechanisms to ensure that coverage of the intended scope is complete:
In mechanisms 1 and 2 the CRM concepts subsume and thereby cover the extensions.
In mechanism 3, the information is accessible at the appropriate point in the respective knowledge base. This approach is preferable when detailed, targeted queries are not expected; in general, only those concepts used for formal querying need to be explicitly modelled.
fig. 2 reasoning about spatial information
The diagram above shows a partial view of the CRM, representing reasoning about spatial information. Five of the main hierarchy branches are included in this view: E39 Actor, E51 Contact Point, E41 Appellation, E53 Place, and E70 Thing. The relationships between these main classes and their subclasses are shown as arrows. Properties between classes are shown as green rectangles. A ‘shortcut’ property is included in this view: P59 has section (is located on or within) between E53 Place and E18 Physical Thing is a shortcut of the path through E46 Section Definition. In some cases the order of priority for property names has been modified in order to facilitate reading the diagram from left to right.
As can be seen, an instance of E53 Place is identified by an instance of E44 Place Appellation, which may be an instance of E45 Address, E47 Spatial Coordinates, E48 Place Name, or E46 Section Definition such as ‘basement’, ‘prow’, or ‘lower left-hand corner.’ An instance of E53 Place may consist of or form part of another instance of E53 Place, thereby allowing a hierarchy of physical ‘containers’ to be constructed.
An instance of E45 Address can be considered both as an E44 Place Appellation–a way of referring to an E53 Place–and as an E51 Contact Point for an E39 Actor. An E39 Actor may have any number of instances of E51 Contact Point. E18 Physical Thing is found on locations as a consequence of being created there or being moved there. Therefore the properties P53 has former or current location (is former or current location of) (and P55 has current location (currently holds) are regarded as shortcuts of the fully articulated paths through the respective events. P55 has current location (currently holds) is a subproperty of P53 has former or current location (is former or current location of). The latter is a container for location information in the absence of knowledge about time of validity and related events.
An interesting aspect of the model is the P58 has section definition (defines section) property between E46 Section Definition and E18 Physical Thing (and the corresponding shortcut from E53 Place to E19 Physical Object). This allows an instance of E53 Place to be defined as a section of an instance of E19 Physical Object. For example, we may know that Nelson fell at a particular spot on the deck of H.M.S. Victory, without knowing the exact position of the vessel in geospatial terms at the time of the fatal shooting of Nelson. Similarly, a signature or inscription can be located “in the lower right corner of” a painting, regardless of where the painting is hanging.
fig. 3 reasoning about temporal information
This second example shows how the CRM handles reasoning about temporal information. Four of the main hierarchy branches are included in this view: E2 Temporal Entity, E52 Time-Span, E77 Persistent Item and E53 Place.
The E2 Temporal Entity class is an abstract class (i.e. it has no instances) that serves to group together all classes with a temporal component, such as instances of E4 Period, E5 Event and E3 Condition State.
An instance of E52 Time-Span is simply a temporal interval that does not make any reference to cultural or geographical contexts (unlike instances of E4 Period, which took place at a particular instance of E53 Place). Instances of E52 Time-Span are sometimes identified by instances of E49 Time Appellation, often in the form of E50 Date.
Both E52 Time-Span and E4 Period have transitive properties. E52 Time-Span has the transitive property P86 falls within (contains), denoting a purely incidental inclusion, whereas E4 Period has the transitive property P9 consists of (forms part of) that supports the decomposition of instances of E4 Period into their constituent parts. For example, the E52 Time-Span during which a building is constructed might falls within the E52 Time-Span of a particular government, although there is no causal or contextual connection between the two instances of E52 Time-Span; conversely, the E4 Period of the Chinese Song Dynasty consists of the Northern Song Period and the Southern Song Period.
Instances of E52 Time-Span are related to their outer bounds (i.e. their indeterminacy interval) by the property P82 at some time within, and to their inner bounds via the property P81 ongoing throughout. The range of these properties is the E61 Time Primitive class, instances of which are treated by the CRM as application or system specific date intervals that are not further analysed.
 The ICOM Statutes provide a definition of the term “museum” at http://icom.museum/statutes.html#2
 The Practical Scope of the CIDOC CRM, including a list of the relevant museum documentation standards, is discussed in more detail on the CIDOC CRM website at http://cidoc.ics.forth.gr/scope.html
 Information about the Resource Description Framework (RDF) can be found at http://www.w3.org/RDF/