Cover Page
Definition of the CIDOC Conceptual Reference Model |
Produced by the ICOM/CIDOC Documentation Standards Group, Continued by the CIDOC CRM Special Interest Group Version 5.0.4 November 2011 Editors: Nick Crofts, Martin Doerr, Tony Gill, Stephen Stead, Matthew Stiff. Copyright © 2003 ICOM/CIDOC CRM Special Interest Group Automatically generated text about document contents |
Cover Page
Volume A: Definition of the CIDOC Conceptual Reference Model |
Produced by the CIDOC CRM Special Interest Group Version 7.2 September 2021 Editors: Chryssoula Bekiari, George Bruseker, Martin Doerr, Christian-Emil Ore, Stephen Stead, Athanasios Velios CC BY 4.0
2021 Individual Contributors to CIDOC CRM 7.2 This page is left blank on purpose Automatically generated text about document contents |
|
1 Introduction
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. |
1 Introduction
This document is the formal definition of the CIDOC Conceptual Reference Model (“CIDOC CRM”), a formal ontology intended to facilitate the integration, mediation and interchange of heterogeneous cultural heritage information and similar information from other domains, as further detailed below. The CRM is the culmination of more than two decades 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 (SIG). The SIG, in turn, collaborates with the ISO working group ISO/TC46/SC4/WG9 to bring the CRM to the form and status of an International Standard. This set of collaborations has resulted in the production of ISO21127:2004 and ISO21127:2014, the ISO standard editions of the CIDOC CRM. This collaboration will be continued in order to support the next update of the ISO standard edition. The present document belongs to the series of evolving versions of the formal definition of the CRM, which serve the ISO working group as community draft for the standard. Eventual minor differences, in semantics and notation, of the ISO standard text from the present, community CIDOC CRM version, which the ISO working group requires and implements, will be harmonized in the subsequent versions of the present, community CIDOC CRM formal definition document. |
|
2 Objectives of the CIDOC CRM
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 a model of the intellectual structure of cultural documentation in logical terms. As such, it is not optimised for implementation-specific storage and processing aspects. Implementations may lead to solutions where elements and links between relevant elements of our conceptualizations are no longer explicit in a database or other structured storage system. For instance the birth event that connects elements such as father, mother, birth date, birth place may not appear in the database, in order to save storage space or response time of the system. The CRM allows us to explain how such apparently disparate entities are intellectually interconnected, and how the ability of the database to answer certain intellectual questions is affected by the omission of such elements and links. The CRM aims to support the following specific functionalities: - Inform developers of information systems as a guide to good practice in conceptual modelling, in order to effectively structure and relate information assets of cultural documentation.
- Serve as a common language for domain experts and IT developers to formulate requirements and to agree on system functionalities with respect to the correct handling of cultural contents.
- To serve as a formal language for the identification of common information contents in different data formats; in particular to support the implementation of automatic data transformation algorithms from local to global data structures without loss of meaning. The latter being useful for data exchange, data migration from legacy systems, data information integration and mediation of heterogeneous sources.
- To support associative queries against integrated resources by providing a global model of the basic classes and their associations to formulate such queries.
- It is further believed, that advanced natural language algorithms and case-specific heuristics can take significant advantage of the CRM to resolve free text information into a formal logical form, if that is regarded beneficial. The CRM is however not thought to be a means to replace scholarly text, rich in meaning, by logical forms, but only a means to identify related data.
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. |
1.1 Objectives of the CIDOC CRM
The primary role of the CIDOC CRM is to enable the exchange and integration of information from heterogeneous sources for the reconstruction and interpretation of the past at a human scale, based on all kinds of material evidence, including texts, audio-visual material and oral tradition. It starts from, but is not limited to, the needs of museum documentation and research based on museum holdings. 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, and to make it available for scholarly interpretation and scientific evaluation. These goals determine the constructs and level of detail of the CIDOC CRM. More specifically, it defines, in terms of a formal ontology, the underlying semantics of database schemata and structured documents used in the documentation of cultural heritage and scientific activities. In particular it defines the semantics related to the study of the past and current state of our world, as it is characteristic for museums, but also or other cultural heritage institutions and disciplines. It does not define any of the terminology appearing typically as data in the respective data structures; it foresees, however, the characteristic relationships for its use. It does not aim at proposing what cultural heritage institutions should document. Rather, it explains the logic of what they actually currently document, and thereby enables semantic interoperability. The CIDOC CRM intends, moreover, to provide a model of the intellectual structure of the respective kinds of mentioned documentation in logical terms. As such, it has not been optimised for implementation specific storage and processing factors. Actual system implementations may lead to solutions where elements and links between relevant elements of our conceptualizations are no longer explicit in a database or other structured storage system. For instance, the birth event that connects elements such as father, mother, birth date, birth place may not appear in the database, in order to save storage space or response time of the system. The CIDOC CRM provides a conceptual and technical means to explain how such apparently disparate entities are semantically and logically interconnected, and how the ability of the database to answer certain intellectual questions is affected by the omission of such elements and links. The CIDOC CRM aims to support the following specific functionalities: Inform developers of information systems as a guide to good practice in conceptual modelling, in order to effectively structure and relate information assets of cultural documentation. - Serve as a common language for domain experts and IT developers to formulate requirements and to agree on system functionalities with respect to the correct handling of cultural contents.
- To serve as a formal language for the identification of common information contents in different data formats; in particular, to support the implementation of automatic data transformation algorithms from local to global data structures without loss of meaning. The latter being useful for data exchange, data migration from legacy systems, data information integration and mediation of heterogeneous sources.
- To support associative queries against integrated resources by providing a global model of the basic classes and their associations to formulate such queries.
- It is further believed that advanced natural language algorithms and case-specific heuristics can take significant advantage of the CIDOC CRM to resolve free text information into a formal logical form, if that is regarded beneficial. The CIDOC CRM is not thought, however, to be a means to replace scholarly text, rich in meaning, by logical forms, but only a means to identify related data.
Users of the CIDOC 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 CIDOC CRM does not provide such notions. By its very structure and formalism, the CIDOC CRM is extensible and users are encouraged to create extensions for the needs of more specialized communities and applications. |
|
3 Scope of the CIDOC CRM
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 term “scientific documentation” is intended to convey the requirement that the depth and quality of descriptive information that can be handled by the CRM should be sufficient for serious academic research. This does not mean that information intended for presentation to members of the general public is excluded, but rather that the CRM is intended to provide the level of detail and precision expected and required by museum professionals and researchers in the field.
- The term “museum collections” is intended to cover all types of material collected and displayed by museums and related institutions, as defined by ICOM. This includes collections, sites and monuments relating to fields such as social history, ethnography, archaeology, fine and applied arts, natural history, history of sciences and technology.
- The documentation of collections includes the detailed description of individual items within collections, groups of items and collections as a whole. The CRM is specifically intended to cover contextual information: the historical, geographical and theoretical background that gives museum collections much of their cultural significance and value.
- The exchange of relevant information with libraries and archives, and the harmonisation of the CRM with their models, falls within the Intended Scope of the CRM.
- Information required solely for the administration and management of cultural institutions, such as information relating to personnel, accounting, and visitor statistics, falls outside the Intended Scope of the CRM.
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 correctly encoded according to these museum documentation standards there can be a CRM-compatible expression that conveys the same meaning. |
1.2 Scope of the CIDOC CRM
The overall scope of the CIDOC CRM can be summarised in simple terms as the curated, factual knowledge about the past at a human scale. 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 growing reference set of specific, identifiable documentation standards and practices that the CIDOC CRM aims to semantically describe, restricted, always, in its details to the limitations of the Intended Scope. The reasons for this distinctions between Intended and Practical Scope are twofold. Firstly, the CIDOC CRM is developed in a “bottom-up” manner, starting from well-understood, actually and widely used concepts of domain experts, which are disambiguated and gradually generalized as more forms of encoding are encountered. This aims to avoid the misadaptations and vagueness that can sometimes be found in introspection-driven attempts to find overarching concepts for such a wide scope, and provides stability to the generalizations found. Secondly, it is a means to identify and keep a focus on the concepts most needed by the communities working in the scope of the CIDOC CRM and to maintain a well-defined agenda for its evolution. The Intended Scope of the CIDOC CRM may, therefore, be defined as all information required for the exchange and integration of heterogeneous scientific and scholarly documentation about the past at a human scale and the available documented and empirical evidence for this. This definition requires further elaboration: - The term “scientific and scholarly documentation” is intended to convey the requirement that the depth and quality of descriptive information that can be handled by the CIDOC CRM should be sufficient for serious academic research. This does not mean that information intended for presentation to members of the general public is excluded, but rather that the CRM is intended to provide the level of detail and precision expected and required by museum professionals and researchers in the field.
- As “available documented and material evidence” are regarded all types of material collected and displayed by museums and related institutions, as defined by ICOM, and other collections, in-situ objects, sites, monuments and intangible heritage relating to fields such as social history, ethnography, archaeology, fine and applied arts, natural history, history of sciences and technology.
- The concept “documentation” includes the detailed description of individual items, in situ or within collections, groups of items and collections as a whole, as well as practices of intangible heritage. It pertains to their current state as well as to information about their past. The CIDOC CRM is specifically intended to cover contextual information: the historical, geographical and theoretical background that gives cultural heritage collections much of their cultural significance and value.
- The documentation of collections includes the detailed description of individual items within collections, groups of items and collections as a whole. The CIDOC CRM is specifically intended to cover contextual information: the historical, geographical and theoretical background that gives museum collections much of their cultural significance and value.
- The exchange of relevant information with libraries and archives, and the harmonisation of the CIDOC CRM with their models, falls within the Intended Scope of the CIDOC CRM.
- Information required solely for the administration and management of cultural institutions, such as information relating to personnel, accounting, and visitor statistics, falls outside the Intended Scope of the CIDOC CRM.
The Practical Scope of the CIDOC CRM is expressed in terms of the set of reference standards and de facto standards for documenting factual knowledge that have been used to guide and validate the CIDOC CRM’s development and its further evolution. The CRM covers the same domain of discourse as the union of these reference standards; this means that for data correctly encoded according to these documentation formats there can be a CIDOC CRM-compatible expression that conveys the same meaning. As part of the on-going work of keep the standard up-to-date, discussions on the types of bias present in the CIDOC CRM are in progress within the CIDOC CRM community. |
|
4 Compatibility with the CRM
|
NOT MATCHED
|
|
4.1 Utility of CRM compatibility
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. |
NOT MATCHED
|
|
4.2 The Information Integration Environment
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: - Local information systems. These are either collection management systems or content management systems that constitute institutional memories and are maintained by an institution. They are used for primary data entry, i.e. a relevant part of the information, be it data or metadata, is primary information in digital form that fulfils institutional needs.
- Integrated access systems. These provide an homogeneous access layer to multiple local systems. The information they manage resides primarily on local systems. We distinguish between:
- 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.
- 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: - data falling within the scope of the CRM can be exported from an information system into an encoded form without loss of meaning with respect to CRM concepts;
- data falling within the scope of the CRM can be transformed into another encoded form without loss of meaning with respect to CRM concepts;
- data falling within the scope of the CRM can be imported from an encoded form into an information system without loss of meaning with respect to CRM concepts;
- data falling within the scope of the CRM that is contained in an information system can be queried and retrieved exhaustively in terms of CRM concepts, subject to the expressive power of a particular query language.
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. |
NOT MATCHED
|
|
4.3 CRM-Compatible Form
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: - all the conditions applicable to a CRM compatible form are respected;
- the subset does not violate the rules of subsumption and inheritance;
- any instance of the reduced CRM-compatible form is also a valid instance of a (full) CRM compatible form
- the subset contains at least the following concepts:
Automatically generated text about Classes & Properties declarations |
NOT MATCHED
|
|
4.4 CRM Compatibility of Data Structure
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. |
NOT MATCHED
|
|
4.5 CRM Compatibility of Information Systems
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 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. |
NOT MATCHED
|
|
4.6 Compatibility claim declaration
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: - For export-compatible data structures:
The subset of CRM concepts directly instantiated by any possible data in this data structure after transformation into a CRM-compatible form. - For export-compatible systems:
- A declaration of configurable user data elements, if any, that are not semantically restricted to a CRM Concept (other than E1 CRM Entity or E77 Persistent Item).
- User data elements or units that are not exported.
- The subset of CRM concepts directly instantiated by any possible data exported from the system after transformation into a CRM-compatible form.
- For partially or dedicated import-compatible systems:
The subset of CRM concepts under which data can be imported into the system. - For access-compatible systems:
- The query language by which the system can be queried.
- The subset of CRM concepts directly instantiated by any possible query answers exported from the system after transformation into a CRM-compatible form.
- For partially access-compatible systems, the subset of CRM concepts by which the system can be queried.
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.. |
NOT MATCHED
|
|
5 Applied Form
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. |
1.5 Applied Form
The CIDOC 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 or OWL. It can be implemented in Relational or Object-Oriented schema. CIDOC CRM instances can also be encoded in RDF, JSON LD, XML, OWL among and others Although the definition of the CIDOC CRM provided here is complete, it is an intentionally compact and concise presentation of the CIDOC CRM’s 81 classes and 160 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 160). However, this definition does contain all of the information necessary to infer and automatically generate a full declaration of all properties, including inherited properties. |
|
5.1 Terminology
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. Class | A class is a category of items that share one or more common traits serving as criteria to identify the items belonging to the class. These properties need not be explicitly formulated in logical terms, but may be described in a text (here called a scope note) that refers to a common conceptualisation of domain experts. The sum of these traits is called the intension of the class. A class may be the domain or range of none, one or more properties formally defined in a model. The formally defined properties need not be part of the intension of their domains or ranges: such properties are optional. An item that belongs to a class is called an instance of this class. A class is associated with an open set of real life instances, known as the extension of the class. Here “open” is used in the sense that it is generally beyond our capabilities to know all instances of a class in the world and indeed that the future may bring new instances about at any time (Open World). Therefore a class cannot be defined by enumerating its instances. A class plays a role analogous to a grammatical noun, and can be completely defined without reference to any other construct (unlike properties, which must have an unambiguously defined domain and range). In some contexts, the terms individual class, entity or node are used synonymously with class. For example: Person is a class. To be a Person may actually be determined by DNA characteristics, but we all know what a Person is. A Person may have the property of being a member of a Group, but it is not necessary to be member of a Group in order to be a Person. We shall never know all Persons of the past. There will be more Persons in the future. | subclass | A subclass is a class that is a specialization of another class (its superclass). Specialization or the IsA relationship means that: - all instances of the subclass are also instances of its superclass,
- the intension of the subclass extends the intension of its superclass, i.e. its traits are more restrictive than that of its superclass and
- the subclass inherits the definition of all of the properties declared for its superclass without exceptions (strict inheritance), in addition to having none, one or more properties of its own.
A subclass can have more than one immediate superclass and consequently inherits the properties of all of its superclasses (multiple inheritance). The IsA relationship or specialization between two or more classes gives rise to a structure known as a class hierarchy. The IsA relationship is transitive and may not be cyclic. In some contexts (e.g. the programming language C++) the term derived class is used synonymously with subclass. For example: Every Person IsA Biological Object, or Person is a subclass of Biological Object. Also, every Person IsA Actor. A Person may die. However other kinds of Actors, such as companies, don’t die (c.f. 2). Every Biological Object IsA Physical Object. A Physical Object can be moved. Hence a Person can be moved also (c.f. 3). | superclass | A superclass is a class that is a generalization of one or more other classes (its subclasses), which means that it subsumes all instances of its subclasses, and that it can also have additional instances that do not belong to any of its subclasses. The intension of the superclass is less restrictive than any of its subclasses. This subsumption relationship or generalization is the inverse of the IsA relationship or specialization. In some contexts (e.g. the programming language C++) the term parent class is used synonymously with superclass. For example: “Biological Object subsumes Person” is synonymous with “Biological Object is a superclass of Person”. It needs fewer traits to identify an item as a Biological Object than to identify it as a Person. | intension | The intension of a class or property is its intended meaning. It consists of one or more common traits shared by all instances of the class or property. These traits need not be explicitly formulated in logical terms, but may just be described in a text (here called a scope note) that refers to a conceptualisation common to domain experts. In particular the so-called primitive concepts, which make up most of the CRM, cannot be further reduced to other concepts by logical terms. | extension | The extension of a class is the set of all real life instances belonging to the class that fulfil the criteria of its intension. This set is “open” in the sense that it is generally beyond our capabilities to know all instances of a class in the world and indeed that the future may bring new instances about at any time (Open World). An information system may at any point in time refer to some instances of a class, which form a subset of its extension. | scope note | A scope note is a textual description of the intension of a class or property. Scope notes are not formal modelling constructs, but are provided to help explain the intended meaning and application of the CRM’s classes and properties. Basically, they refer to a conceptualisation common to domain experts and disambiguate between different possible interpretations. Illustrative example instances of classes and properties are also regularly provided in the scope notes for explanatory purposes. | instance | An instance of a class is a real world item that fulfils the criteria of the intension of the class. Note, that the number of instances declared for a class in an information system is typically less than the total in the real world. For example, you are an instance of Person, but you are not mentioned in all information systems describing Persons. For example: The painting known as the “The Mona Lisa” is an instance of the class Man Made Object. An instance of a property is a factual relation between an instance of the domain and an instance of the range of the property that matches the criteria of the intension of the property. For example: “The Louvre is current owner of The Mona Lisa” is an instance of the property “is current owner of”. | property | A property serves to define a relationship of a specific kind between two classes. The property is characterized by an intension, which is conveyed by a scope note. A property plays a role analogous to a grammatical verb, in that it must be defined with reference to both its domain and range, which are analogous to the subject and object in grammar (unlike classes, which can be defined independently). It is arbitrary, which class is selected as the domain, just as the choice between active and passive voice in grammar is arbitrary. In other words, a property can be interpreted in both directions, with two distinct, but related interpretations. Properties may themselves have properties that relate to other classes (This feature is used in this model only in order to describe dynamic subtyping of properties). Properties can also be specialized in the same manner as classes, resulting in IsA relationships between subproperties and their superproperties. In some contexts, the terms attribute, reference, link, role or slot are used synonymously with property. For example: “Physical Man-Made Thing depicts CRM Entity” is equivalent to “CRM Entity is depicted by Physical Man-Made Thing”. | subproperty | A subproperty is a property that is a specialization of another property (its superproperty). Specialization or IsA relationship means that: - all instances of the subproperty are also instances of its superproperty,
- the intension of the subproperty extends the intension of the superproperty, i.e. its traits are more restrictive than that of its superproperty,
- the domain of the subproperty is the same as the domain of its superproperty or a subclass of that domain,
- the range of the subproperty is the same as the range of its superproperty or a subclass of that range,
- the subproperty inherits the definition of all of the properties declared for its superproperty without exceptions (strict inheritance), in addition to having none, one or more properties of its own.
A subproperty can have more than one immediate superproperty and consequently inherits the properties of all of its superproperties (multiple inheritance). The IsA relationship or specialization between two or more properties gives rise to the structure we call a property hierarchy. The IsA relationship is transitive and may not be cyclic. Some object-oriented programming languages, such as C++, do not contain constructs that allow for the expression of the specialization of properties as sub-properties | superproperty | A superproperty is a property that is a generalization of one or more other properties (its subproperties), which means that it subsumes all instances of its subproperties, and that it can also have additional instances that do not belong to any of its subproperties. The intension of the superproperty is less restrictive than any of its subproperties. The subsumption relationship or generalization is the inverse of the IsA relationship or specialization. | domain | The domain is the class for which a property is formally defined. This means that instances of the property are applicable to instances of its domain class. A property must have exactly one domain, although the domain class may always contain instances for which the property is not instantiated. The domain class is analogous to the grammatical subject of the phrase for which the property is analogous to the verb. It is arbitrary, which class is selected as the domain and which as the range, just as the choice between active and passive voice in grammar is arbitrary. Property names in the CRM are designed to be semantically meaningful and grammatically correct when read from domain to range. In addition, the inverse property name, normally given in parentheses, is also designed to be semantically meaningful and grammatically correct when read from range to domain. | range | The range is the class that comprises all potential values of a property. That means that instances of the property can link only to instances of its range class. A property must have exactly one range, although the range class may always contain instances that are not the value of the property. The range class is analogous to the grammatical object of a phrase for which the property is analogous to the verb. It is arbitrary, which class is selected as domain and which as range, just as the choice between active and passive voice in grammar is arbitrary. Property names in the CRM are designed to be semantically meaningful and grammatically correct when read from domain to range. In addition the inverse property name, normally given in parentheses, is also designed to be semantically meaningful and grammatically correct when read from range to domain. | inheritance | Inheritance of properties from superclasses to subclasses means that if an item x is an instance of a class A, then - all properties that must hold for the instances of any of the superclasses of A must also hold for item x, and
- all optional properties that may hold for the instances of any of the superclasses of A may also hold for item x.
| strict inheritance | Strict inheritance means that there are no exceptions to the inheritance of properties from superclasses to subclasses. For instance, some systems may declare that elephants are grey, and regard a white elephant as an exception. Under strict inheritance it would hold that: if all elephants were grey, then a white elephant could not be an elephant. Obviously not all elephants are grey. To be grey is not part of the intension of the concept elephant but an optional property. The CRM applies strict inheritance as a normalization principle. | multiple inheritance | Multiple inheritance means that a class A may have more than one immediate superclass. The extension of a class with multiple immediate superclasses is a subset of the intersection of all extensions of its superclasses. The intension of a class with multiple immediate superclasses extends the intensions of all its superclasses, i.e. its traits are more restrictive than any of its superclasses. If multiple inheritance is used, the resulting “class hierarchy” is a directed graph and not a tree structure. If it is represented as an indented list, there are necessarily repetitions of the same class at different positions in the list. For example, Person is both, an Actor and a Biological Object. | endurant, perdurant | “The difference between enduring and perduring entities (which we shall also call endurants and perdurants) is related to their behaviour in time. Endurants are wholly present (i.e., all their proper parts are present) at any time they are present. Perdurants, on the other hand, just extend in time by accumulating different temporal parts, so that, at any time they are present, they are only partially present, in the sense that some of their proper temporal parts (e.g., their previous or future phases) may be not present. E.g., the piece of paper you are reading now is wholly present, while some temporal parts of your reading are not present any more. Philosophers say that endurants are entities that are in time, while lacking however temporal parts (so to speak, all their parts flow with them in time). Perdurants, on the other hand, are entities that happen in time, and can have temporal parts (all their parts are fixed in time).” (Gangemi et al. 2002, pp. 166-181). | shortcut | A shortcut is a formally defined single property that represents a deduction or join of a data path in the CRM. The scope notes of all properties characterized as shortcuts describe in words the equivalent deduction. Shortcuts are introduced for the cases where common documentation practice refers only to the deduction rather than to the fully developed path. For example, museums often only record the dimension of an object without documenting the Measurement that observed it. The CRM declares shortcuts explicitly as single properties in order to allow the user to describe cases in which he has less detailed knowledge than the full data path would need to be described. For each shortcut, the CRM contains in its schema the properties of the full data path explaining the shortcut. | monotonic reasoning | Monotonic reasoning is a term from knowledge representation. A reasoning form is monotonic if an addition to the set of propositions making up the knowledge base never determines a decrement in the set of conclusions that may be derived from the knowledge base via inference rules. In practical terms, if experts enter subsequently correct statements to an information system, the system should not regard any results from those statements as invalid, when a new one is entered. The CRM is designed for monotonic reasoning and so enables conflict-free merging of huge stores of knowledge. | disjoint | Classes are disjoint if the intersection of their extensions is an empty set. In other words, they have no common instances in any possible world. | primitive | The term primitive as used in knowledge representation characterizes a concept that is declared and its meaning is agreed upon, but that is not defined by a logical deduction from other concepts. For example, mother may be described as a female human with child. Then mother is not a primitive concept. Event however is a primitive concept. Most of the CRM is made up of primitive concepts. | Open World | The “Open World Assumption” is a term from knowledge base systems. It characterizes knowledge base systems that assume the information stored is incomplete relative to the universe of discourse they intend to describe. This incompleteness may be due to the inability of the maintainer to provide sufficient information or due to more fundamental problems of cognition in the system’s domain. Such problems are characteristic of cultural information systems. Our records about the past are necessarily incomplete. In addition, there may be items that cannot be clearly assigned to a given class. In particular, absence of a certain property for an item described in the system does not mean that this item does not have this property. For example, if one item is described as Biological Object and another as Physical Object, this does not imply that the latter may not be a Biological Object as well. Therefore complements of a class with respect to a superclass cannot be concluded in general from an information system using the Open World Assumption. For example, one cannot list “all Physical Objects known to the system that are not Biological Objects in the real world”, but one may of course list “all items known to the system as Physical Objects but that are not known to the system as Biological Objects”. | complement | The complement of a class A with respect to one of its superclasses B is the set of all instances of B that are not instances of A. Formally, it is the set-theoretic difference of the extension of B minus the extension of A. Compatible extensions of the CRM should not declare any class with the intension of them being the complement of one or more other classes. To do so will normally violate the desire to describe an Open World. For example, for all possible cases of human gender, male should not be declared as the complement of female or vice versa. What if someone is both or even of another kind? | query containment | Query containment is a problem from database theory: A query X contains another query Y, if for each possible population of a database the answer set to query X contains also the answer set to query Y. If query X and Y were classes, then X would be superclass of Y. | interoperability | Interoperability means the capability of different information systems to communicate some of their contents. In particular, it may mean that - two systems can exchange information, and/or
- multiple systems can be accessed with a single method.
Generally, syntactic interoperability is distinguished from semantic interoperability. Syntactic interoperability means that the information encoding of the involved systems and the access protocols are compatible, so that information can be processed as described above without error. However, this does not mean that each system processes the data in a manner consistent with the intended meaning. For example, one system may use a table called “Actor” and another one called “Agent”. With syntactic interoperability, data from both tables may only be retrieved as distinct, even though they may have exactly the same meaning. To overcome this situation, semantic interoperability has to be added. The CRM relies on existing syntactic interoperability and is concerned only with adding semantic interoperability. | semantic interoperability | Semantic interoperability means the capability of different information systems to communicate information consistent with the intended meaning. In more detail, the intended meaning encompasses - the data structure elements involved,
- the terminology appearing as data and
- the identifiers used in the data for factual items such as places, people, objects etc.
Obviously communication about data structure must be resolved first. In this case consistent communication means that data can be transferred between data structure elements with the same intended meaning or that data from elements with the same intended meaning can be merged. In practice, the different levels of generalization in different systems do not allow the achievement of this ideal. Therefore semantic interoperability is regarded as achieved if elements can be found that provide a reasonably close generalization for the transfer or merge. This problem is being studied theoretically as the query containment problem. The CRM is only concerned with semantic interoperability on the level of data structure elements. | property quantifiers | We use the term "property quantifiers" for the declaration of the allowed number of instances of a certain property that can refer to a particular instance of the range class or the domain class of that property. These declarations are ontological, i.e. they refer to the nature of the real world described and not to our current knowledge. For example, each person has exactly one father, but collected knowledge may refer to none, one or many. | universal | The fundamental ontological distinction between universals and particulars can be informally understood by considering their relationship with instantiation: particulars are entities that have no instances in any possible world; universals are entities that do have instances. Classes and properties (corresponding to predicates in a logical language) are usually considered to be universals. (after Gangemi et al. 2002, pp. 166-181). |
|
1.4 Terminology
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. class | A class is a category of items that share one or more common traits serving as criteria to identify the items belonging to the class. These properties need not be explicitly formulated in logical terms, but may be described in a text (here called a scope note) that refers to a common conceptualisation of domain experts. The sum of these traits is called the intension of the class. A class may be the domain or range of none, one or more properties formally defined in a model. The formally defined properties need not be part of the intension of their domains or ranges: such properties are optional. An item that belongs to a class is called an instance of this class. A class is associated with an open set of real-life instances, known as the extension of the class. Here “open” is used in the sense that it is generally beyond our capabilities to know all instances of a class in the world and indeed that the future may bring new instances about at any time (Open World). Therefore, a class cannot be defined by enumerating its instances. A class plays a role analogous to a grammatical noun, and can be completely defined without reference to any other construct (unlike properties, which must have an unambiguously defined domain and range). In some contexts, the terms individual class, entity or node are used synonymously with class. For example: Person is a class. To be a Person may actually be determined by DNA characteristics, but we all know what a Person is. A Person may have the property of being a member of a Group, but it is not necessary to be member of a Group in order to be a Person. We shall never know all Persons of the past. There will be more Persons in the future. | subclass | A subclass is a class that is a specialization of another class (its superclass). Specialization or the IsA relationship means that: - all instances of the subclass are also instances of its superclass,
- the intension of the subclass extends the intension of its superclass, i.e., its traits are more restrictive than that of its superclass and
- the subclass inherits the definition of all of the properties declared for its superclass without exceptions (strict inheritance), in addition to having none, one or more properties of its own.
A subclass can have more than one immediate superclass and consequently inherits the properties of all of its superclasses (multiple inheritance). The IsA relationship or specialization between two or more classes gives rise to a structure known as a class hierarchy. The IsA relationship is transitive and may not be cyclic. In some contexts (e.g., the programming language C++) the term derived class is used synonymously with subclass. For example: Every Person IsA Biological Object, or Person is a subclass of Biological Object. Also, every Person IsA Actor. A Person may die. However, other kinds of Actors, such as companies, don’t die (c.f. 2). Every Biological Object IsA Physical Object. A Physical Object can be moved. Hence, a Person can be moved also (c.f. 3). | superclass | A superclass is a class that is a generalization of one or more other classes (its subclasses), which means that it subsumes all instances of its subclasses, and that it can also have additional instances that do not belong to any of its subclasses. The intension of the superclass is less restrictive than any of its subclasses. This subsumption relationship or generalization is the inverse of the IsA relationship or specialization. For example: “Biological Object subsumes Person” is synonymous with “Biological Object is a superclass of Person”. It needs fewer traits to identify an item as a Biological Object than to identify it as a Person. | intension | The intension of a class or property is its intended meaning. It consists of one or more common traits shared by all instances of the class or property. These traits need not be explicitly formulated in logical terms, but may just be described in a text (here called a scope note) that refers to a conceptualisation common to domain experts. In particular, the so-called primitive concepts, which make up most of the CIDOC CRM, cannot be further reduced to other concepts by logical terms. | extension | The extension of a class is the set of all real-life instances belonging to the class that fulfil the criteria of its intension. This set is “open” in the sense that it is generally beyond our capabilities to know all instances of a class in the world and indeed that the future may bring new instances about at any time (Open World). An information system may at any point in time refer to some instances of a class, which form a subset of its extension. | scope note | A scope note is a textual description of the intension of a class or property. Scope notes are not formal modelling constructs, but are provided to help explain the intended meaning and application of the CIDOC CRM’s classes and properties. Basically, they refer to a conceptualisation common to domain experts and disambiguate between different possible interpretations. Illustrative example instances of classes and properties are also regularly provided in the scope notes for explanatory purposes. | instance | An instance of a class is a real-world item that fulfils the criteria of the intension of the class. Note, that the number of instances declared for a class in an information system is typically less than the total in the real world. For example, you are an instance of Person, but you are not mentioned in all information systems describing Persons. For example: The painting known as the “The Mona Lisa” is an instance of the class Human Made Object. An instance of a property is a factual relation between an instance of the domain and an instance of the range of the property that matches the criteria of the intension of the property. For example: The Mona Lisa has former or current owner. The Louvre is an instance of the property P51 has former or current owner (is former or current owner of). | property | A property serves to define a relationship of a specific kind between two classes. The property is characterized by an intension, which is conveyed by a scope note. A property plays a role analogous to a grammatical verb, in that it must be defined with reference to both its domain and range, which are analogous to the subject and object in grammar (unlike classes, which can be defined independently). It is arbitrary, which class is selected as the domain, just as the choice between active and passive voice in grammar is arbitrary. In other words, a property can be interpreted in both directions, with two distinct, but related interpretations. Properties may themselves have properties that relate to other classes (This feature is used in this model only in order to describe dynamic subtyping of properties). Properties can also be specialized in the same manner as classes, resulting in IsA relationships between subproperties and their superproperties. In some contexts, the terms attribute, reference, link, role or slot are used synonymously with property. For example: “Physical Human-Made Thing depicts CRM Entity” is equivalent to “CRM Entity is depicted by Physical Human-Made Thing”. | inverse of | The inverse of a property is the reinterpretation of a property from range to domain without more general or more specific meaning, similar to the choice between active and passive voice in some languages. In contrast to some knowledge representation languages, such as RDF and OWL, we regard that the inverse of a property is not a property in its own right that needs an explicit declaration of being inverse of another, but an interpretation implicitly existing for any property. The inverse of the inverse of a property is identical to the property itself, i.e., its primary sense of direction. For example: “CRM Entity is depicted by Physical Human-Made Thing” is the inverse of “Physical Human-Made Thing depicts CRM Entity” | subproperty | A subproperty is a property that is a specialization of another property (its superproperty). Specialization or IsA relationship means that: - all instances of the subproperty are also instances of its superproperty,
- the intension of the subproperty extends the intension of the superproperty, i.e., its traits are more restrictive than that of its superproperty,
- the domain of the subproperty is the same as the domain of its superproperty or a subclass of that domain,
- the range of the subproperty is the same as the range of its superproperty or a subclass of that range,
- the subproperty inherits the definition of all of the properties declared for its superproperty without exceptions (strict inheritance), in addition to having none, one or more properties of its own.
A subproperty can have more than one immediate superproperty and consequently inherits the properties of all of its superproperties (multiple inheritance). The IsA relationship or specialization between two or more properties gives rise to the structure we call a property hierarchy. The IsA relationship is transitive and may not be cyclic. Some object-oriented programming languages, such as C++, do not contain constructs that allow for the expression of the specialization of properties as sub-properties. Alternatively, a property may be subproperty of the inverse of another property, i.e., reading the property from range to domain. In that case: - all instances of the subproperty are also instances of the inverse of the other property,
- the intension of the subproperty extends the intension of the inverse of the other property, i.e., its traits are more restrictive than that of the inverse of the other property,
- the domain of the subproperty is the same as the range of the other property or a subclass of that range,
- the range of the subproperty is the same as the domain of the other property or a subclass of that domain,
- the subproperty inherits the definition of all of the properties declared for the other property without exceptions (strict inheritance), in addition to having none, one or more properties of its own. The definitions of inherited properties have to be interpreted in the inverse sense of direction of the subproperty, i.e., from range to domain.
| superproperty | A superproperty is a property that is a generalization of one or more other properties (its subproperties), which means that it subsumes all instances of its subproperties, and that it can also have additional instances that do not belong to any of its subproperties. The intension of the superproperty is less restrictive than any of its subproperties. The subsumption relationship or generalization is the inverse of the IsA relationship or specialization. A superproperty may be a generalization of the inverse of another property. | domain | The domain is the class for which a property is formally defined. This means that instances of the property are applicable to instances of its domain class. A property must have exactly one domain, although the domain class may always contain instances for which the property is not instantiated. The domain class is analogous to the grammatical subject of the phrase for which the property is analogous to the verb. It is arbitrary which class is selected as the domain and which as the range, just as the choice between active and passive voice in grammar is arbitrary. Property names in the CIDOC CRM are designed to be semantically meaningful and grammatically correct when read from domain to range. In addition, the inverse property name, normally given in parentheses, is also designed to be semantically meaningful and grammatically correct when read from range to domain. | range | The range is the class that comprises all potential values of a property. That means that instances of the property can link only to instances of its range class. A property must have exactly one range, although the range class may always contain instances that are not the value of the property. The range class is analogous to the grammatical object of a phrase for which the property is analogous to the verb. It is arbitrary which class is selected as domain and which as range, just as the choice between active and passive voice in grammar is arbitrary. Property names in the CIDOC CRM are designed to be semantically meaningful and grammatically correct when read from domain to range. In addition, the inverse property name, normally given in parentheses, is also designed to be semantically meaningful and grammatically correct when read from range to domain. | inheritance | Inheritance of properties from superclasses to subclasses means that if an item x is an instance of a class A, then: - all properties that must hold for the instances of any of the superclasses of A must also hold for item x, and
- all optional properties that may hold for the instances of any of the superclasses of A may also hold for item x.
| strict inheritance | Strict inheritance means that there are no exceptions to the inheritance of properties from superclasses to subclasses. For instance, some systems may declare that elephants are grey, and regard a white elephant as an exception. Under strict inheritance it would hold that: if all elephants were grey, then a white elephant could not be an elephant. Obviously not all elephants are grey. To be grey is not part of the intension of the concept elephant but an optional property. The CIDOC CRM applies strict inheritance as a normalization principle. | multiple inheritance | Multiple inheritance means that a class A may have more than one immediate superclass. The extension of a class with multiple immediate superclasses is a subset of the intersection of all extensions of its superclasses. The intension of a class with multiple immediate superclasses extends the intensions of all its superclasses, i.e., its traits are more restrictive than any of its superclasses. If multiple inheritance is used, the resulting “class hierarchy” is a directed graph and not a tree structure. If it is represented as an indented list, there are necessarily repetitions of the same class at different positions in the list. For example: Person is both, an Actor and a Biological Object. | multiple Instantiation | Multiple Instantiation is the term that describes the case that an instance of class A is also regarded as an instance of one or more other classes B1...n at the same time. When multiple instantiation is used, it has the effect that the properties of all these classes become available to describe this instance. For instance, some particular cases of destruction may also be activities (e.g., Herostratos’ deed), but not all destructions are activities (e.g., destruction of Herculaneum). In comparison, multiple inheritance describes the case that all instances of a class A are implicitly instances of all superclasses of A, by virtue of the definition of the class A, whereas the combination of classes used for multiple instantiation is a characteristic of particular instances only. It is important to note that multiple instantiation is not allowed using combinations of disjoint classes. | endurant, perdurant | “The difference between enduring and perduring entities (which we shall also call endurants and perdurants) is related to their behaviour in time. Endurants are wholly present (i.e., all their proper parts are present) at any time they are present. Perdurants, on the other hand, just extend in time by accumulating different temporal parts, so that, at any time they are present, they are only partially present, in the sense that some of their proper temporal parts (e.g., their previous or future phases) may be not present. E.g., the piece of paper you are reading now is wholly present, while some temporal parts of your reading are not present any more. Philosophers say that endurants are entities that are in time, while lacking however temporal parts (so to speak, all their parts flow with them in time). Perdurants, on the other hand, are entities that happen in time, and can have temporal parts (all their parts are fixed in time).” (Gangemi et al. 2002, pp. 166-181). | shortcut | A shortcut is a formally defined single property that represents a deduction or join of a data path in the CIDOC CRM. The scope notes of all properties characterized as shortcuts describe in words the equivalent deduction. Shortcuts are introduced for the cases where common documentation practice refers only to the deduction rather than to the fully developed path. For example, museums often only record the dimension of an object without documenting the Measurement that observed it. The CIDOC CRM declares shortcuts explicitly as single properties in order to allow the user to describe cases in which he has less detailed knowledge than the full data path would need to be described. For each shortcut, the CIDOC CRM contains in its schema the properties of the full data path explaining the shortcut. | monotonic reasoning | Monotonic reasoning is a term from knowledge representation. A reasoning form is monotonic if an addition to the set of propositions making up the knowledge base never determines a decrement in the set of conclusions that may be derived from the knowledge base via inference rules. In practical terms, if experts enter subsequently correct statements to an information system, the system should not regard any results from those statements as invalid, when a new one is entered. The CIDOC CRM is designed for monotonic reasoning and so enables conflict-free merging of huge stores of knowledge. | disjoint | Classes are disjoint if the intersection of their extensions is an empty set. In other words, they have no common instances in any possible world. | primitive | The term primitive as used in knowledge representation characterizes a concept that is declared and its meaning is agreed upon, but that is not defined by a logical deduction from other concepts. For example, mother may be described as a female human with child. Then mother is not a primitive concept. Event however is a primitive concept. Most of the CIDOC CRM is made up of primitive concepts. | Open World | The “Open World Assumption” is a term from knowledge base systems. It characterizes knowledge base systems that assume the information stored is incomplete relative to the universe of discourse they intend to describe. This incompleteness may be due to the inability of the maintainer to provide sufficient information or due to more fundamental problems of cognition in the system’s domain. Such problems are characteristic of cultural information systems. Our records about the past are necessarily incomplete. In addition, there may be items that cannot be clearly assigned to a given class. In particular, absence of a certain property for an item described in the system does not mean that this item does not have this property. For example, if one item is described as Biological Object and another as Physical Object, this does not imply that the latter may not be a Biological Object as well. Therefore, complements of a class with respect to a superclass cannot be concluded in general from an information system using the Open World Assumption. For example, one cannot list “all Physical Objects known to the system that are not Biological Objects in the real world”, but one may of course list “all items known to the system as Physical Objects but that are not known to the system as Biological Objects”. | complement | The complement of a class A with respect to one of its superclasses B is the set of all instances of B that are not instances of A. Formally, it is the set-theoretic difference of the extension of B minus the extension of A. Compatible extensions of the CIDOC CRM should not declare any class with the intension of them being the complement of one or more other classes. To do so will normally violate the desire to describe an Open World. For example, for all possible cases of human gender, male should not be declared as the complement of female or vice versa. What if someone is both or even of another kind? | query containment | Query containment is a problem from database theory: A query X contains another query Y, if for each possible population of a database the answer set to query X contains also the answer set to query Y. If query X and Y were classes, then X would be superclass of Y. | | | interoperability | Interoperability means the capability of different information systems to communicate some of their contents. In particular, it may mean that - two systems can exchange information, and/or
- multiple systems can be accessed with a single method.
Generally, syntactic interoperability is distinguished from semantic interoperability. Syntactic interoperability means that the information encoding of the involved systems and the access protocols are compatible, so that information can be processed as described above without error. However, this does not mean that each system processes the data in a manner consistent with the intended meaning. For example, one system may use a table called “Actor” and another one called “Agent”. With syntactic interoperability, data from both tables may only be retrieved as distinct, even though they may have exactly the same meaning. To overcome this situation, semantic interoperability has to be added. The CIDOC CRM relies on existing syntactic interoperability and is concerned only with adding semantic interoperability. | semantic interoperability | Semantic interoperability means the capability of different information systems to communicate information consistent with the intended meaning. In more detail, the intended meaning encompasses - the data structure elements involved,
- the terminology appearing as data and
- the identifiers used in the data for factual items such as places, people, objects etc.
Obviously, communication about data structure must be resolved first. In this case consistent communication means that data can be transferred between data structure elements with the same intended meaning or that data from elements with the same intended meaning can be merged. In practice, the different levels of generalization in different systems do not allow the achievement of this ideal. Therefore, semantic interoperability is regarded as achieved if elements can be found that provide a reasonably close generalization for the transfer or merge. This problem is being studied theoretically as the query containment problem. The CIDOC CRM is only concerned with semantic interoperability on the level of data structure elements. | property quantifiers | We use the term "property quantifiers" for the declaration of the allowed number of instances of a certain property that can refer to a particular instance of the range class or the domain class of that property. These declarations are ontological, i.e., they refer to the nature of the real world described and not to our current knowledge. For example, each person has exactly one father, but collected knowledge may refer to none, one or many. | universal | The fundamental ontological distinction between universals and particulars can be informally understood by considering their relationship with instantiation: particulars are entities that have no instances in any possible world; universals are entities that do have instances. Classes and properties (corresponding to predicates in a logical language) are usually considered to be universals. (after Gangemi et al. 2002, pp. 166-181). | knowledge creation process | All knowledge contained in an information system must have been introduced into that system by some human agent, either directly or indirectly. Despite this fact, many, if not most, statements within such a system will lack specific attribution of authority. That being said, in the domain of cultural heritage, it is common practice that, for the processes of collection documentation and management, there are clearly and explicitly elaborated systems of responsibility outlining by whom and how knowledge can be added and or modified in the system. Ideally these systems are specified in institutional policy and protocol documents. Thus, it is reasonable to hold that all such statements that lack explicit authority attribution within the information system can, in fact, be read as the official view of the administrating institution of that system. Such a position does not mean to imply that an information system represents at any particular moment a completed phase of knowledge that the institution promotes. Rather, it means to underline that, in a CH context, a managed set of data, at any state of elaboration, will in fact embody an adherence to some explicit code of standards which guarantees the validity of that data within the scope of said standards and all practical limitations. So long as the information is under active management it remains continuously open to revision and improvement as further research reveals further understanding surrounding the objects of concern. A distinct exception to this rule is represented by information in the data set that carries with it an explicit statement of responsibility. In CIDOC CRM such statements of responsibility are expressed though knowledge creation events such as E13 Attribute Assignment and its relevant subclasses. Any information in a CIDOC CRM model that is based on an explicit creation event for that piece of information, where the creator’s identity has been given, is attributed to the authority and assigned to the responsibility of the actor identified as causal in that event. For any information in the system connected to knowledge creation events that do not explicitly reference their creator, as well as any information not connected to creation events, the responsibility falls back to the institution responsible for the database/knowledge graph. That means that for information only expressed through shortcuts such as P2 has type, where no knowledge creation event has been explicitly specified, the originating creation event cannot be deduced and the responsibility for the information can never be any other body than the institution responsible for the whole information system. In the case of an institution taking over stewardship of a database transferred into their custody, two relations of responsibility for the knowledge therein can be envisioned. If the institution accepts the dataset and undertakes to maintain and update it, then they take on responsibility for that information and become the default authority behind its statements as described above. If, on the other hand, the institution accepts the data set and stores it without change as a closed resource, then it can be considered that the default authority remains the original steward. | transitivity | Transitivity is defined in the standard way found in mathematics or logic: A property P is transitive if the domain and range is the same class and for all instances x, y, z of this class the following is the case: If x is related by P to y and y is related by P to z, then x is related by P to z. The intention of a property as described in the scope note will decide whether a property is transitive or not. For example, the property P121 overlaps with between instances of E53 Place is not transitive, while the property P89 falls within (contains) between instances of E53 Place and the property P46 is composed of (forms part of) between instances of E18 Physical Thing are both transitive. Transitivity is especially useful when CIDOC CRM is implemented in a system with deduction. | symmetry | Symmetry is defined in the standard way found in mathematics or logic: A property P is symmetric if the domain and range are the same class and for all instances x, y of this class the following is the case: If x is related by P to y, then y is related by P to x. The intention of a property as described in the scope note will decide whether a property is symmetric or not. An example of a symmetric property is E53 Place. P122 borders with: E53 Place. The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. | reflexivity | Reflexivity is defined in the standard way found in mathematics or logic: A property P is reflexive if the domain and range are the same class and for all instances x, of this class the following is the case: x is related by P to itself. The intention of a property as described in the scope note will decide whether a property is reflexive or not. An example of a reflexive property is E53 Place. P89 falls within (contains): E53 Place. |
|
|
5.2 Property Quantifiers
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. many to many (0,n:0,n) | Unconstrained: An individual domain instance and range instance of this property can have zero, one or more instances of this property. In other words, this property is optional and repeatable for its domain and range. | one to many (0,n:0,1) | An individual domain instance of this property can have zero, one or more instances of this property, but an individual range instance cannot be referenced by more than one instance of this property. In other words, this property is optional for its domain and range, but repeatable for its domain only. In some contexts this situation is called a “fan-out”. | many to one (0,1:0,n) | An individual domain instance of this property can have zero or one instance of this property, but an individual range instance can be referenced by zero, one or more instances of this property. In other words, this property is optional for its domain and range, but repeatable for its range only. In some contexts this situation is called a “fan-in”. | many to many, necessary (1,n:0,n) | An individual domain instance of this property can have one or more instances of this property, but an individual range instance can have zero, one or more instances of this property. In other words, this property is necessary and repeatable for its domain, and optional and repeatable for its range. | one to many, necessary (1,n:0,1) | An individual domain instance of this property can have one or more instances of this property, but an individual range instance cannot be referenced by more than one instance of this property. In other words, this property is necessary and repeatable for its domain, and optional but not repeatable for its range. In some contexts this situation is called a “fan-out”. | many to one, necessary (1,1:0,n) | An individual domain instance of this property must have exactly one instance of this property, but an individual range instance can be referenced by zero, one or more instances of this property. In other words, this property is necessary and not repeatable for its domain, and optional and repeatable for its range. In some contexts this situation is called a “fan-in”. | one to many, dependent (0,n:1,1) | An individual domain instance of this property can have zero, one or more instances of this property, but an individual range instance must be referenced by exactly one instance of this property. In other words, this property is optional and repeatable for its domain, but necessary and not repeatable for its range. In some contexts this situation is called a “fan-out”. | one to many, necessary, dependent (1,n:1,1) | An individual domain instance of this property can have one or more instances of this property, but an individual range instance must be referenced by exactly one instance of this property. In other words, this property is necessary and repeatable for its domain, and necessary but not repeatable for its range. In some contexts this situation is called a “fan-out”. | many to one, necessary, dependent (1,1:1,n) | An individual domain instance of this property must have exactly one instance of this property, but an individual range instance can be referenced by one or more instances of this property. In other words, this property is necessary and not repeatable for its domain, and necessary and repeatable for its range. In some contexts this situation is called a “fan-in”. | one to one (1,1:1,1) | An individual domain instance and range instance of this property must have exactly one instance of this property. In other words, this property is necessary and not repeatable for its domain and for its range. |
The CRM defines some dependencies between properties and the classes that are their domains or ranges. These can be one or both of the following: A) the property is necessary for the domain B) the property is necessary for the range, or, in other words, the range is dependent on the property. The possible kinds of dependencies are defined in the table above. Note that if a dependent 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. |
1.5.5 Property Quantifiers
Quantifiers for properties are provided for the purpose of semantic clarification only, and should not be treated as implementation recommendations. The CIDOC 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. (Meghini, C. & Doerr, M., 2018) many to many (0,n:0,n) | Unconstrained: An individual domain instance and range instance of this property can have zero, one or more instances of this property. In other words, this property is optional and repeatable for its domain and range. | one to many (0,n:0,1) | An individual domain instance of this property can have zero, one or more instances of this property, but an individual range instance cannot be referenced by more than one instance of this property. In other words, this property is optional for its domain and range, but repeatable for its domain only. In some contexts, this situation is called a “fan-out”. | many to one (0,1:0,n) | An individual domain instance of this property can have zero or one instance of this property, but an individual range instance can be referenced by zero, one or more instances of this property. In other words, this property is optional for its domain and range, but repeatable for its range only. In some contexts, this situation is called a “fan-in”. | many to many, necessary (1,n:0,n) | An individual domain instance of this property can have one or more instances of this property, but an individual range instance can have zero, one or more instances of this property. In other words, this property is necessary and repeatable for its domain, and optional and repeatable for its range. | one to many, necessary (1,n:0,1) | An individual domain instance of this property can have one or more instances of this property, but an individual range instance cannot be referenced by more than one instance of this property. In other words, this property is necessary and repeatable for its domain, and optional but not repeatable for its range. In some contexts, this situation is called a “fan-out”. | many to one, necessary (1,1:0,n) | An individual domain instance of this property must have exactly one instance of this property, but an individual range instance can be referenced by zero, one or more instances of this property. In other words, this property is necessary and not repeatable for its domain, and optional and repeatable for its range. In some contexts, this situation is called a “fan-in”. | one to many, dependent (0,n:1,1) | An individual domain instance of this property can have zero, one or more instances of this property, but an individual range instance must be referenced by exactly one instance of this property. In other words, this property is optional and repeatable for its domain, but necessary and not repeatable for its range. In some contexts, this situation is called a “fan-out”. | one to many, necessary, dependent (1,n:1,1) | An individual domain instance of this property can have one or more instances of this property, but an individual range instance must be referenced by exactly one instance of this property. In other words, this property is necessary and repeatable for its domain, and necessary but not repeatable for its range. In some contexts, this situation is called a “fan-out”. | many to one, necessary, dependent (1,1:1,n) | An individual domain instance of this property must have exactly one instance of this property, but an individual range instance can be referenced by one or more instances of this property. In other words, this property is necessary and not repeatable for its domain, and necessary and repeatable for its range. In some contexts, this situation is called a “fan-in”. | one to one (1,1:1,1) | An individual domain instance and range instance of this property must have exactly one instance of this property. In other words, this property is necessary and not repeatable for its domain and for its range. |
The CIDOC CRM defines some dependencies between properties and the classes that are their domains or ranges. These can be one or both of the following: - the property is necessary for the domain
- the property is necessary for the range, or, in other words, the range is dependent on the property.
The possible kinds of dependencies are defined in the table above. Note that if a dependent 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 CIDOC 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 CIDOC 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. |
|
5.3 Naming Conventions
The following naming conventions have been applied throughout the CRM: - Classes are identified by numbers preceded by the letter “E” (historically classes were sometimes referred to as “Entities”), and are named using noun phrases (nominal groups) using title case (initial capitals). For example, E63 Beginning of Existence.
- Properties are identified by numbers preceded by the letter “P,” and are named in both directions using verbal phrases in lower case. Properties with the character of states are named in the present tense, such as “has type”, whereas properties related to events are named in past tense, such as “carried out.” For example, P126 employed (was employed in).
- Property names should be read in their non-parenthetical form for the domain-to-range direction, and in parenthetical form for the range-to-domain direction.
- Properties with a range that is a subclass of E59 Primitive Value (such as E1 CRM Entity. P3 has note: E62 String, for example) have no parenthetical name form, because reading the property name in the range-to-domain direction is not regarded as meaningful.
- Properties that have identical domain and range are either symmetric or transitive. Instantiating a symmetric property implies that the same relation holds for both the domain-to-range and the range-to-domain directions. An example of this is E53 Place. P122 borders with: E53 Place. The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. Transitive asymmetric properties, such as E4 Period. P9 consist of (forms part of): E4 Period, have a parenthetical form that relates to the meaning of the inverse direction.
- The choice of the domain of properties, and hence the order of their names, are established in accordance with the following priority list:
- Temporal Entity and its subclasses
- Thing and its subclasses
- Actor and its subclasses
- Other
|
1.5.1 Naming Conventions
The following naming conventions have been applied throughout the CIDOC CRM: - Classes are identified by numbers preceded by the letter “E” (historically classes were sometimes referred to as “Entities”), and are named using noun phrases (nominal groups) using title case (initial capitals). For example, E63 Beginning of Existence.
- Properties are identified by numbers preceded by the letter “P,” and are named in both directions using verbal phrases in lower case. Properties with the character of states are named in the present tense, such as “has type”, whereas properties related to events are named in past tense, such as “carried out.” For example, P126 employed (was employed in).
- Property names should be read in their non-parenthetical form for the domain-to-range direction, and in parenthetical form for the range-to-domain direction. Reading a property in range-to-domain direction is equivalent to the inverse of that property. Following a current notational practice in OWL knowledge representation language, we represent inverse properties in this text by adding a letter “i” following the identification number and the parenthetical form of the full property name, such as P59i is located on or within, which is the inverse of P59 has section (is located on or within).
- Properties with a range that is a subclass of E59 Primitive Value (such as E1 CRM Entity. P3 has note: E62 String, for example) have no parenthetical name form, because reading the property name in the range-to-domain direction is not regarded as meaningful.
- Properties that have identical domain and range are either symmetric or transitive. Instantiating a symmetric property implies that the same relation holds for both the domain-to-range and the range-to-domain directions. An example of this is E53 Place. P122 borders with: E53 Place. The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. Transitive asymmetric properties, such as E4 Period. P9 consist of (forms part of): E4 Period, have a parenthetical form that relates to the meaning of the inverse direction.
- The choice of the domain of properties, and hence the order of their names, are established in accordance with the following priority list:
- Temporal Entity and its subclasses
- Thing and its subclasses
- Actor and its subclasses
- Other
|
|
6 Modelling principles
The following modelling principles have guided and informed the development of the CIDOC CRM. |
2 Modelling principles
The following modelling principles have guided and informed the development of the CIDOC CRM. |
|
6.1 Monotonicity
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. For example: 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. For example: 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. For example: 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. |
2.5 Monotonicity
The CIDOC CRM’s primary function is to support the meaningful integration of information in an Open World. The adoption of the Open World principle means that the CIDOC CRM itself must remain fundamentally open and knowledge bases implemented using it should be flexible enough to receive new insights. At the model level, new classes and properties within the CIDOC CRM’s scope may be found in the course of integrating more documentation records or when new kinds of relevant facts come to the attention of its maintainers. At the level of the KBs, the need to add or revise information may arise due to numerous external factors. Research may open new questions; documentation may be directed to new or different phenomena; natural or social evolution may reveal new objects of study. It is the aim of the maintainers of the CIDOC CRM to respect the Open World principle and to follow the principle of monotonicity. Monotonicity requires that adding new classes and properties to the model or adding new statements to a knowledge base does not invalidate already modelled structures and existing statements. A first consequence of this commitment, at the level of the model, is that the CIDOC CRM aims to be monotonic in the sense of Domain Theory. That is to say, the existing CIDOC CRM constructs and the deductions made from them should remain valid and well-formed, even as new constructs are added by extensions to the CIDOC CRM. Any extensions should be, under this method, backwards compatible with previous models. The only exception to this rule arises when a previous construct is considered objectively incorrect by the domain experts and thus subjected to corrective revision. Adopting the principle of monotonicity has active consequences for the basic manner in which classes and properties are designed and declared in the CIDOC CRM. In particular, it forbids the declaration of complement classes, i.e., classes solely defined by excluding instances of some other classes. For example: FRBRoo (Bekiari et al (eds). 2015) extends the CIDOC CRM. In version 2.4 of FRBRoo, F51 Name Use Activity was declared as a subclass to the CIDOC CRM class E7 Activity. This class was added in order to describe a phenomenon specific to library practice and not considered within CRM base. F51 Name Use Activity describes the practice of an instance of E74 Group adopting and deploying a name within a context for a time-span. The creation of this extension is monotonic because no existing IsA relationship or inheritance of properties in CRM base are compromised and no future extension is ruled out. By way of contrast, if, to handle this situation, a subclass “Other Activity” had been declared, a non-monotonic change would have been introduced. This would be the case because the scope note of a complement class like “Other Activities” would forbid any future declaration of specializations of E7 Activity such as ‘Name Use Activity’. In the case the need arose to declare a particular specialized subclass, a non-monotonic revision would have to be made, since there would be no principled way to decide which instances of ‘Other Activity’ were instances of the new, specialized class and which were not. Such non-monotonic changes are extremely costly to end users, compromising backwards compatibility and long-term integration. As a second consequence, maintaining monotonicity is also required during revising or augmenting data within a CIDOC CRM compatible system. That is, existing CIDOC CRM instances, their properties and the 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. For example: 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. This is achieved by declaring E20 Biological Object as subclass of E19 Physical Object. This example further demonstrates that the IsA hierarchy of classes and properties can represent characteristic stages of increasing knowledge about some item during the processes of investigation and collection of evidence. Higher level classes can be used to safely classify objects whose precise characteristics are not known in the first instance. An ambiguous biological object may, for example, be classified as only a physical object. Subsequent investigation can reveal its nature as a biological object. A knowledge base constructed with CIDOC CRM classes designed to support monotonic revision allows for seeking physical objects that were not yet recognized as biological ones. This ability to integrate information with different specificity of description in a well-defined way is particularly important for large-scale information integration. Such a system supports scholars being able to integrate all information about potentially relevant phenomena into the information system without forcing an over or under commitment to knowledge about the object. Since large scale information integration always deals with different levels of knowledge of its relevant objects, this feature enables a consistent approach to data integration. A third consequence, applied at the level of the knowledge base, is that in order to formally preserve monotonicity, when it is required to record and store alternative opinions regarding phenomena all formally defined properties should be implemented as unconstrained (many: many) so that conflicting instances of properties are merely accumulated. Thus, integrated knowledge can serve as a research tool for accumulating relevant alternative opinions around well-defined entities, whereas conclusions about the truth are the task of open-ended scientific or scholarly hypothesis building. For example: King Arthur’s basic life events are highly contested. Once entered in a knowledge base, he should be defined as an instance of E21 Person and treated as having existed as such within the sense of our historical discourse. The instance of E21 Person is used as the collection point for describing possible properties and existence of this individual. Alternative opinions about properties, such as the birthplace and his living places, should be accumulated without validity decisions being made during data compilation. King Arthur may be entered as a different instance, of E28 Conceptual Object, for describing him as mythological character and accumulating possibly mythological facts. The fourth consequence of monotonicity relates to the use of time dependent properties in a knowledge base. Certain properties declared in the CIDOC CRM, such as having a part, an owner or a location, may change many times for a single item during the course of its existence. Asserting that such a property holds for some item means that that property held for some particular, undetermined time-span within the course of its existence. Consequently, one item may be the subject of multiple statements asserting the instantiation of that property without conflict or need for revision. The collection of such statements would reflect an aggregation of these instances of this property holding over the time-span of the item’s existence. If a more specific temporal knowledge is required/available, it is recommended to explicitly describe the events leading to the assertion of that property for that item. For example, in the case of acquiring or losing an item, it would be appropriate to declare the related event class such as E9 Move. By virtue of this principle, the CRM achieves monotonicity with respect to an increase of knowledge about the states of an item at different times, regardless of their temporal order. Time-neutral properties may be specialized in a future monotonic extension by time-specific properties, but not vice-versa. Also, many properties registered do not change over time or are relative to events in the model already. Therefore, the CIDOC CRM always gives priority to modelling properties as time-neutral, and rather representing changes by events. However, for some of these properties many databases may describe a “current” state relative to some property, such as “current location” or “current owner”. Using such a “current” state means that the database manager is able to verify the respective reality at the latest date of validity of the database. Obviously, this information is non-monotonic, i.e., it requires deletion when the state changes. In order to preserve a reduced monotonicity, these properties have time-neutral superproperties by which respective instances can be reclassified if the validity becomes unknown or no longer holds. Therefore, the use of such properties in the CRM is only recommended if they can be maintained consistently. Otherwise, they should be reclassified by their time-neutral superproperties. This holds in particular if data is exported to another repository, see also the paragraph “Authorship of Knowledge Base Contents” |
|
6.2 Minimality
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.
|
2.4 Minimality
Although the scope of the CIDOC CRM is very broad, the model itself is constructed as economically as possible: - CIDOC CRM classes and properties are either primitive, or they are key concepts in the practical scope.
- Complements of CIDOC CRM classes are not declared, because, considering the Open World principle, there are no properties for complements of a class (see Terminology and first consequence of Monotonicity).
A CIDOC CRM class is declared when: - It is required as the domain or range of a property not appropriate to its superclass.
- It serves as a merging point of two CIDOC CRM class branches via multiple IsA (e.g., E25 Human-Made Feature). When the branch superclasses are used for multiple instantiation of an item, this item is in the intersection of the scopes. The class resulting from multiple IsA should be narrower in scope than the intersection of the scopes of the branch superclasses.
- It is useful as a leaf class (i.e., at the end of a CIDOC CRM branch) to domain communities building CIDOC CRM extensions or matching key domain classes from other models to the CIDOC CRM (e.g., E34 Inscription).
|
|
6.3 Shortcuts
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”. |
1.5.3 Shortcuts
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 inside the frame of the actual KB 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”. |
|
6.4 Disjointness
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.
|
2.6 Disjointness
Classes are disjoint if they cannot share any common instances at any time, past, present or future. That implies that it is not possible to instantiate an item using a combination of classes that are mutually disjoint or with subclasses of them (see “multiple instantiation” in section “Terminology”). There are many examples of disjoint classes in the CIDOC CRM. A comprehensive declaration of all possible disjoint class combinations afforded by the CIDOC 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 CIDOC 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 CIDOC 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 human-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.
This page is left blank on purpose |
|
6.5 About Types
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 modelled 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”. |
3.2.1 About Types
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 CIDOC CRM the class E55 Type comprises such terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts (universals) in contrast to instances of E41 Appellation, which are used to name instances of CIDOC CRM classes. For this purpose, the CIDOC 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 CIDOC CRM, with the exception of E59 Primitive Value, inherits the property P2 has type (is type of). This provides a general alternative mechanism to specialize the classification of CIDOC CRM instances to any level of detail, by linking to external vocabulary sources, thesauri, classification schemas or ontologies. Analogous to the function of the P2 has type (is type of) property, some properties in the CIDOC CRM are associated with an additional property. These are numbered in the CIDOC CRM documentation with a ‘.1’ extension. The range of these properties of properties always falls under E55 Type. The purpose of a property of a property is to provide an alternative mechanism to specialize its domain 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 CIDOC 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 CIDOC CRM’s ability to integrate cultural knowledge. Types, that is, instances of E55 Type and its subclasses, can be used to characterize the instances of a CIDOC 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 CIDOC CRM it can be adequate to extend the CIDOC 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 CIDOC 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 CIDOC 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 modelled 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 CIDOC CRM but also describing the history of this concept itself, may choose 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 CIDOC 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”. One role of E55 Type is to be the CIDOC CRM’s interface to domain specific ontologies and thesauri or less formal terminological systems. Such sets of concepts can be represented in the CIDOC 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. Other standard models, in particular richer ones, used to describe terminological systems can also be interfaced with the CIDOC CRM by declaring their respective concept class as being equivalent to E55 Type, and their respective broader/narrower relation as being identical with P127 has broader term (has narrower term), as long as they are semantically compatible. In addition to being an interface to external thesauri and classification systems, E55 Type is an ordinary class in the CIDOC CRM and a subclass of E28 Conceptual Object. E55 Type and its subclasses inherit all properties from this superclass. Thus, together with the CIDOC 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 CIDOC 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, instances of E55 Type or suitable subclasses can describe universals from type systems not organized in thesauri or ontologies, such as industrial product names and types, defined and published by the producers themselves for each new product or product variant. |
|
6.6 Extensions
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. |
NOT MATCHED
|
|
6.7 Coverage
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: - Existing high level classes can be extended, either structurally as subclasses or dynamically using the type hierarchy.
- Existing high level properties can be extended, either structurally as subproperties, or in some cases, dynamically, using properties of properties which allow subtyping.
- Additional information that falls outside the semantics formally defined by the CRM can be recorded as unstructured data using E1 CRM Entity. P3 has note: E62 String.
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. |
NOT MATCHED
|
|
7 Examples
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. All classes are shown as blue-white rectangles. Properties are shown as single arrows. In some cases the order of priority for property names has been reversed in order to facilitate reading the diagram from left to right. Double arrows indicate IsA relations between classes and their subclasses or between properties and their subproperties. 'Shortcuts' are indicated with light grey rectangles and their names are written in italics, such as the P59 has section (is located on or within) between E53 Place and E18 Physical Thing, which is a shortcut of the path through E46 Section Definition. . 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 geometric ‘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 direct 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. |
NOT MATCHED
|
|
8 Class & Property Hierarchies
Although they do not provide comprehensive definitions, compact monohierarchical presentations of the class and property IsA hierarchies have been found to significantly aid comprehension and navigation of the CRM, and are therefore provided below. The class hierarchy presented below has the following format: - Each line begins with a unique class identifier, consisting of a number preceded by the letter “E” (originally denoting “entity,” although now replaced by convention with the term “class”).
- A series of hyphens (“-”) follows the unique class identifier, indicating the hierarchical position of the class in the IsA hierarchy.
- The English name of the class appears to the right of the hyphens.
- The index is ordered by hierarchical level, in a “depth first” manner, from the smaller to the larger subhierarchies.
- Classes that appear in more than one position in the class hierarchy as a result of multiple inheritance are shown in an italic typeface.
The property hierarchy presented below has the following format: - Each line begins with a unique property identifier, consisting of a number preceded by the letter “P” (for “property”).
- A series of hyphens (“-”) follows the unique property identifier, indicating the hierarchical position of the property in the IsA hierarchy.
- The English name of the property appears to the right of the hyphens, followed by its inverse name in parentheses for reading in the range to domain direction.
- The domain class for which the property is declared.
- The range class that the property references.
- The index is ordered by hierarchical level, in a “depth first” manner, from the smaller to the larger subhierarchies, and by property number between equal siblings.
- Properties that appear in more than one position in the property hierarchy as a result of multiple inheritance are shown in an italic typeface.
Automatically generated text about Classes & Properties declarations |
4 Class & Property Hierarchies
Although they do not provide comprehensive definitions, compact mono-hierarchical presentations of the class and property IsA hierarchies have been found to significantly aid comprehension and navigation of the CIDOC CRM. Since the CRM is poly-hierarchical, a mono-hierarchical presentation form is achieved by a top-down expansion of all inverse IsA relations regardless whether a concept has already be presented at another place in the same hierarchy. This form is provided below. The class hierarchy presented below has the following format: - Each line begins with a unique class identifier, consisting of a number preceded by the letter “E” (originally denoting “entity,” although now replaced by convention with the term “class”).
- A series of hyphens (“-”) follows the unique class identifier, indicating the hierarchical position of the class in the IsA hierarchy.
- The English name of the class appears to the right of the hyphens.
- The index is ordered by hierarchical level, in a “depth first” manner, from the smaller to the larger subhierarchies.
- Classes that appear in more than one position in the class hierarchy as a result of multiple inheritance are shown in an italic typeface.
The property hierarchy presented below has the following format: - Each line begins with a unique property identifier, consisting of a number preceded by the letter “P” (for “property”).
- A series of hyphens (“-”) follows the unique property identifier, indicating the hierarchical position of the property in the IsA hierarchy.
- The English name of the property appears to the right of the hyphens, followed by its inverse name in parentheses for reading in the range to domain direction.
- The domain class for which the property is declared.
- The range class that the property references.
- The index is ordered by hierarchical level, in a “depth first” manner, from the smaller to the larger subhierarchies, and by property number between equal siblings.
- Properties that appear in more than one position in the property hierarchy as a result of multiple inheritance are shown in an italic typeface.
Automatically generated text about Classes & Properties declarations |
|
9 CIDOC CRM Class Declarations
The classes of the CRM are comprehensively declared in this section using the following format: - Class names are presented as headings in bold face, preceded by the class’ unique identifier;
- The line “Subclass of:” declares the superclass of the class from which it inherits properties;
- The line “Superclass of:” is a cross-reference to the subclasses of this class;
- The line “Scope note:” contains the textual definition of the concept the class represents;
- The line “Examples:” contains a bulleted list of examples of instances of this class. If the example is also instance of a subclass of this class, the unique identifier of the subclass is added in parenthesis. If the example instantiates two classes, the unique identifiers of both classes is added in parenthesis. Non-fictitious examples may be followed by an explanation in brackets.
- The line “Properties:” declares the list of the class’ properties;
- Each property is represented by its unique identifier, its forward and reverse names, and the range class that it links to, separated by colons;
- Inherited properties are not represented;
- Properties of properties are provided indented and in parentheses beneath their respective domain property.
|
5 CIDOC CRM Class Declarations
The classes of the CIDOC CRM are comprehensively declared in this section using the following format: - Class names are presented as headings in bold face, preceded by the class’ unique identifier;
- The line “Subclass of:” declares the superclass of the class from which it inherits properties;
- The line “Superclass of:” is a cross-reference to the subclasses of this class;
- The line “Scope note:” contains the textual definition of the concept the class represents;
- The line “Examples:” contains a bulleted list of examples of instances of this class. If the example is also instance of a subclass of this class, the unique identifier of the subclass is added in parenthesis. If the example instantiates two classes, the unique identifiers of both classes is added in parenthesis. Non-fictitious examples may be followed by an explanation in brackets.
- The line “Properties:” declares the list of the class’ properties;
- Each property is represented by its unique identifier, its forward and reverse names, and the range class that it links to, separated by colons;
- Inherited properties are not represented;
- Properties of properties are provided indented and in parentheses beneath their respective domain property.
|
|
|
|
Superclass of:
E2 Temporal Entity
E52 Time-Span
E53 Place
E54 Dimension
E77 Persistent Item
|
Superclass of:
E2 Temporal Entity
E52 Time-Span
E53 Place
E54 Dimension
E59 Primitive Value
E77 Persistent Item
E92 Spacetime Volume
|
Scope Note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties: - Identification by name or appellation, and in particular by a preferred identifier
- Classification by type, allowing further refinement of the specific subclass an instance belongs to
- Attachment of free text for the expression of anything not captured by formal properties
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
|
Scope Note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties: - Identification by name or appellation, and in particular by a preferred identifier
- Classification by type, allowing further refinement of the specific subclass an instance belongs to
- Attachment of free text and other unstructured data for the expression of anything not captured by formal properties
All other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity.
|
Examples:
- the earthquake in Lisbon 1755 (E5)
|
Examples:
- the earthquake in Lisbon 1755 (E5) (Chester, 2001)
|
First order logic:
|
First order logic:
|
Properties:
P1 is identified by (identifies): E41 AppellationP2 has type (is type of): E55 TypeP3 has note: E62 StringP3.1 has type: E55 Type P48 has preferred identifier (is preferred identifier of): E42 IdentifierP137 exemplifies ( is exemplified by ): E55 TypeP137.1 in the taxonomic role: E55 Type
|
Properties:
P1 is identified by (identifies): E41 AppellationP2 has type (is type of): E55 TypeP3 has note: E62 StringP3.1 has type: E55 Type P48 has preferred identifier (is preferred identifier of): E42 IdentifierP137 exemplifies (is exemplified by): E55 TypeP137.1 in the taxonomic role: E55 Type
|
|
|
|
Superclass of:
E3 Condition State
E4 Period
|
Superclass of:
E3 Condition State
E4 Period
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises all phenomena, such as the instances of E4 Periods, E5 Events and states, which happen over a limited extent in time. In some contexts, these are also called perdurants. This class is disjoint from E77 Persistent Item. This is an abstract class and has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing.
|
Scope Note:
This class comprises all phenomena, such as the instances of E4 Periods and E5 Events, which happen over a limited extent in time. This extent in time must be contiguous, i.e., without gaps. In case the defining kinds of phenomena for an instance of E2 Temporal Entity cease to happen, and occur later again at another time, we regard that the former instance of E2 Temporal Entity has ended and a new instance has come into existence. In more intuitive terms, the same event cannot happen twice. In some contexts, such phenomena are also called perdurants. This class is disjoint from E77 Persistent Item and is an abstract class that typically has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing.
|
Examples:
- Bronze Age (E4)
- the earthquake in Lisbon 1755 (E5)
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 – 1946 (E3)
|
Examples:
- Bronze Age (E4) (Childe, 1963)
- the earthquake in Lisbon 1755 (E5) (Chester, 2001)
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 – 1946 (E3) (Maddox, 2015)
|
First order logic:
|
First order logic:
|
Properties:
P4 has time-span (is time-span of): E52 Time-SpanP114 is equal in time to: E2 Temporal EntityP115 finishes (is finished by): E2 Temporal EntityP116 starts (is started by): E2 Temporal EntityP117 occurs during (includes): E2 Temporal EntityP118 overlaps in time with (is overlapped in time by): E2 Temporal EntityP119 meets in time with (is met in time by): E2 Temporal EntityP120 occurs before (occurs after): E2 Temporal Entity
|
Properties:
P4 has time-span (is time-span of): E52 Time-SpanP173 starts before or with the end of (ends after or with the start of): E2 Temporal EntityP174 starts before the end of (ends after the start of): E2 Temporal EntityP175 starts before or with the start of (starts after or with the start of): E2 Temporal EntityP176 starts before the start of (starts after the start of): E2 Temporal EntityP182 ends before or with the start of (starts after or with the end of): E2 Temporal EntityP183 ends before the start of (starts after the end of): E2 Temporal EntityP184 ends before or with the end of (ends with or after the end of): E2 Temporal EntityP185 ends before the end of (ends after the end of): E2 Temporal Entity
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the states of objects characterised by a certain condition over a time-span. An instance of this class describes the prevailing physical condition of any material object or feature during a specific E52 Time Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held. The nature of that condition can be described using P2 has type. For example, the E3 Condition State “condition of the SS Great Britain between 22 September 1846 and 27 August 1847” can be characterized as E55 Type “wrecked”.
|
Scope Note:
This class comprises the states of objects characterised by a certain condition over a time-span. An instance of this class describes the prevailing physical condition of any material object or feature during a specific instance of E52 Time Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held. The nature of that condition can be described using P2 has type. For example, the instance of E3 Condition State “condition of the SS Great Britain between 22 September 1846 and 27 August 1847” can be characterized as an instance “wrecked” of E55 Type.
|
Examples:
- the “Amber Room” in Tsarskoje Selo being completely reconstructed from summer 2003 until now
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 – 1946
- the state of my turkey in the oven at 14:30 on 25 December, 2002 (P2 has type: E55 Type “still not cooked”)
|
Examples:
- the "reconstructed" state of the “Amber Room” in Tsarskoje Selo from summer 2003 until now (Owen, 2009)
- the "ruined" state of Peterhof Palace near Saint Petersburg from 1944 to 1946 (Maddox, 2015)
- the state of my turkey in the oven at 14:30 on 25 December, 2002 [P2 has type: E55 Type “still not cooked”] (fictitious)
- the topography of the leaves of Sinai Printed Book 3234.2361 on the 10th of July 2007 [described as: of type "cockled"] (fictitious)
|
First order logic:
|
First order logic:
|
Properties:
P5 consists of (forms part of): E3 Condition State
|
Properties:
P5 consists of (forms part of): E3 Condition State
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
E2 Temporal Entity
E92 Spacetime Volume
|
Scope Note:
This class comprises sets of coherent phenomena or cultural manifestations bounded in time and space. It is the social or physical coherence of these phenomena that identify an E4 Period and not the associated spatio-temporal bounds. These bounds are a mere approximation of the actual process of growth, spread and retreat. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area as a sedentary culture. Typically this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the “Ming Dynasty” or the “McCarthy Era”. There are however no assumptions about the scale of the associated phenomena. In particular all events are seen as synthetic processes consisting of coherent phenomena. Therefore E4 Period is a superclass of E5 Event. For example, a modern clinical E67 Birth can be seen as both an atomic E5 Event and as an E4 Period that consists of multiple activities performed by multiple instances of E39 Actor. There are two different conceptualisations of ‘artistic style’, defined either by physical features or by historical context. For example, “Impressionism” can be viewed as a period lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an E4 Period, and the second defines morphological object types that fall under E55 Type. Another specific case of an E4 Period is the set of activities and phenomena associated with a settlement, such as the populated period of Nineveh.
|
Scope Note:
This class comprises sets of coherent phenomena or cultural manifestations occurring in time and space. It is the social or physical coherence of these phenomena that identify an instance of E4 Period and not the associated spatiotemporal extent. This extent is only the “ground” or space in an abstract physical sense that the actual process of growth, spread and retreat has covered. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area and time as a sedentary culture. This also means that overlapping land use rights, common among first nations, amounts to overlapping periods. Often, this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the “Ming Dynasty” or the “McCarthy Era”, but also geopolitical units and activities of settlements are regarded as special cases of E4 Period. However, there are no assumptions about the scale of the associated phenomena. In particular all events are seen as synthetic processes consisting of coherent phenomena. Therefore, E4 Period is a superclass of E5 Event. For example, a modern clinical birth, an instance of E67 Birth, can be seen as both a single event, i.e., an instance of E5 Event, and as an extended period, i.e., an instance of E4 Period, that consists of multiple physical processes and complementary activities performed by multiple instances of E39 Actor. As the actual extent of an instance of E4 Period in spacetime we regard the trajectories of the participating physical things during their participation in an instance of E4 Period. This includes the open spaces via which these things have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event. Examples include the air in a meeting room transferring the voices of the participants. Since these phenomena are fuzzy, we assume the spatiotemporal extent to be contiguous, except for cases of phenomena spreading out over islands or other separated areas, including geopolitical units distributed over disconnected areas such as islands or colonies. Whether the trajectories necessary for participants to travel between these areas are regarded as part of the spatiotemporal extent or not has to be decided in each case based on a concrete analysis, taking use of the sea for other purposes than travel, such as fishing, into consideration. One may also argue that the activities to govern disconnected areas imply travelling through spaces connecting them and that these areas hence are spatially connected in a way, but it appears counterintuitive to consider for instance travel routes in international waters as extensions of geopolitical units. Consequently, an instance of E4 Period may occupy a number of disjoint spacetime volumes, however there must not be a discontinuity in the timespan covered by these spacetime volumes. This means that an instance of E4 Period must be contiguous in time. If it has ended in all areas, it has ended as a whole. However, it may end in one area before another, such as in the Polynesian migration, and it continues as long as it is ongoing in at least one area. We model E4 Period as a subclass of E2 Temporal Entity and of E92 Spacetime Volume. The latter is intended as a phenomenal spacetime volume as defined in CIDOC CRMgeo (Doerr & Hiebel, 2013). By virtue of this multiple inheritance, we can discuss the physical extent of an instance of E4 Period without representing each instance of it together with an instance of its associated spacetime volume. This model combines two quite different kinds of substance: an instance of E4 Period is a phenomenon while an instance of E92 Spacetime Volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance of E4 Period is regarded to be unique to it due to all its details and fuzziness; its identity and existence depends uniquely on the identity of the instance of E4 Period. Therefore, this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language. Typical use of this class in cultural heritage documentation is for documenting cultural and artistic periods. There are two different conceptualisations of ‘artistic style’, defined either by physical features or by historical context. For example, “Impressionism” can be viewed as a period in the European sphere of influence lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an instance of E4 Period, and the second defines morphological object types that fall under E55 Type. A geopolitical unit as a specific case of an instance of E4 Period is the set of activities and phenomena related to the claim of power, the consequences of belonging to a jurisdictional area and an administrative system that establishes a geopolitical unit. Examples from the modern period are countries or administrative areas of countries such as districts whose actions and structures define activities and phenomena in the area that they intend to govern. The borders of geopolitical units are often defined in contracts or treaties although they may deviate from the actual practice. The spatiotemporal properties of Geopolitical units can be modelled through the properties inherited from E92 Spacetime Volume. Another specific case of an instance of E4 Period is the actual extent of the set of activities and phenomena as evidenced by their physical traces that define a settlement, such as the populated period of Nineveh.
|
Examples:
- Jurassic
- European Bronze Age
- Italian Renaissance
- Thirty Years War
- Sturm und Drang
- Cubism
|
Examples:
- Jurassic (Hallam, 1975)
- Populated Period of Nineveh
- Imperial Rome under Marcus Aurelius
- European Bronze Age (Harrison, 2004)
- Italian Renaissance (Macdonald, 1992)
- Thirty Years War (Lee, 1991)
- Sturm und Drang (Berkoff, 2013)
- Cubism (Cox, 2000)
|
First order logic:
|
First order logic:
- E4(x) ⇒ E2(x)
- E4(x) ⇒ E92(x)
|
Properties:
P7 took place at (witnessed): E53 PlaceP8 took place on or within (witnessed): E19 Physical ObjectP9 consists of (forms part of): E4 PeriodP10 falls within (contains): E4 PeriodP132 overlaps with: E4 PeriodP133 is separated from: E4 Period
|
Properties:
P7 took place at (witnessed): E53 PlaceP8 took place on or within (witnessed): E18 Physical ThingP9 consists of (forms part of): E4 Period
|
|
|
|
Superclass of:
E7 Activity
E63 Beginning of Existence
E64 End of Existence
|
Superclass of:
E7 Activity
E63 Beginning of Existence
E64 End of Existence
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses. The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
|
Scope Note:
This class comprises distinct, delimited and coherent processes and interactions of a material nature, in cultural, social or physical systems, involving and affecting instances of E77 Persistent Item in a way characteristic of the kind of process. Typical examples are meetings, births, deaths, actions of decision taking, making or inventing things, but also more complex and extended ones such as conferences, elections, building of a castle, or battles. While the continuous growth of a tree lacks the limits characteristic of an event, its germination from a seed does qualify as an event. Similarly, the blowing of the wind lacks the distinctness and limits of an event, but a hurricane, flood or earthquake would qualify as an event. Mental processes are considered as events, in cases where they are connected with the material externalization of their results; for example, the creation of a poem, a performance or a change of intention that becomes obvious from subsequent actions or declarations. The effects of an instance of E5 Event may not lead to relevant permanent changes of properties or relations of the items involved in it, for example an unrecorded performance. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event. While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example, the statements made during a meeting and the listening of the audience. Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analyzed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the size of the phenomena. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy overall effect and are thus not instances of E5 Event.
|
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
|
Examples:
- the birth of Cleopatra (E67) (Pomeroy, 1984)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6) (Camardo, 2013)
- World War II (E7) (Barber, 1994)
- the Battle of Stalingrad (E7) (Hoyt, 1993)
- the Yalta Conference (E7) (Harbutt, 2010)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday (fictitious)
- the CIDOC conference 2003 (E7)
|
First order logic:
|
First order logic:
|
Properties:
P11 had participant (participated in): E39 ActorP12 occurred in the presence of (was present at): E77 Persistent Item
|
Properties:
P11 had participant (participated in): E39 ActorP12 occurred in the presence of (was present at): E77 Persistent Item
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation. Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity. The decision to document an object as destroyed, transformed or modified is context sensitive: - If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
- An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
- When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
|
Scope Note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation. Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an instance of E6 Destruction and of E7 Activity. The decision to document an object as destroyed, transformed or modified is context sensitive: - If the matter remaining from the destruction is not documented, the event is modelled solely as an instance of E6 Destruction.
- An event should also be documented as an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
- When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as an instance of E11 Modification.
|
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
|
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD (Camardo, 2013)
- the destruction of Nineveh (E6, E7) (River, 2016)
- the breaking of a champagne glass yesterday by my dog (fictitious)
|
First order logic:
|
First order logic:
|
Properties:
P13 destroyed (was destroyed by): E18 Physical Thing
|
Properties:
P13 destroyed (was destroyed by): E18 Physical Thing
|
|
|
|
Superclass of:
E8 Acquisition
E9 Move
E10 Transfer of Custody
E11 Modification
E13 Attribute Assignment
E65 Creation
E66 Formation
E85 Joining
E86 Leaving
E87 Curation Activity
|
Superclass of:
E8 Acquisition
E9 Move
E10 Transfer of Custody
E11 Modification
E13 Attribute Assignment
E65 Creation
E66 Formation
E85 Joining
E86 Leaving
E87 Curation Activity
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door.
|
Scope Note:
This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door.
|
Examples:
- the Battle of Stalingrad
- the Yalta Conference
- my birthday celebration 28-6-1995
- the writing of “Faust” by Goethe (E65)
- the formation of the Bauhaus 1919 (E66)
- calling the place identified by TGN ‘7017998’ ‘Quyunjig’ by the people of Iraq
|
Examples:
- the Battle of Stalingrad (Hoyt, 1993)
- the Yalta Conference (Harbutt, 2010)
- my birthday celebration 28-6-1995
- the writing of “Faust” by Goethe (E65) (Williams, 2020)
- the formation of the Bauhaus 1919 (E66) (Droste, 2006)
- calling the place identified by TGN ‘7017998’ ‘Quyunjig’ by the people of Iraq
- Kira Weber working in glass art from 1984 to 1993
- Kira Weber working in oil and pastel painting from 1993
|
First order logic:
|
First order logic:
|
Properties:
P14 carried out by (performed): E39 ActorP14.1 in the role of: E55 Type P15 was influenced by (influenced): E1 CRM EntityP16 used specific object (was used for): E70 ThingP16.1 mode of use: E55 Type P17 was motivated by (motivated): E1 CRM EntityP19 was intended use of (was made for): E71 Man-Made ThingP19.1 mode of use: E55 Type P20 had specific purpose (was purpose of): E5 EventP21 had general purpose (was purpose of): E55 TypeP32 used general technique (was technique of): E55 TypeP33 used specific technique (was used by): E29 Design or ProcedureP125 used object of type (was type of object used in): E55 TypeP134 continued (was continued by): E7 Activity
|
Properties:
P14 carried out by (performed): E39 ActorP14.1 in the role of: E55 Type P15 was influenced by (influenced): E1 CRM EntityP16 used specific object (was used for): E70 ThingP16.1 mode of use: E55 Type P17 was motivated by (motivated): E1 CRM EntityP19 was intended use of (was made for): E71 Human-Made ThingP19.1 mode of use: E55 Type P20 had specific purpose (was purpose of): E5 EventP21 had general purpose (was purpose of): E55 TypeP32 used general technique (was technique of): E55 TypeP33 used specific technique (was used by): E29 Design or ProcedureP125 used object of type (was type of object used in): E55 TypeP134 continued (was continued by): E7 Activity
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more other instances of E39 Actor. The class also applies to the establishment or loss of ownership of instances of E18 Physical Thing. It does not, however, imply changes of any other kinds of right. The recording of the donor and/or recipient is optional. It is possible that in an instance of E8 Acquisition there is either no donor or no recipient. Depending on the circumstances, it may describe: - the beginning of ownership
- the end of ownership
- the transfer of ownership
- the acquisition from an unknown source
- the loss of title due to destruction of the item
It may also describe events where a collector appropriates legal title, for example by annexation or field collection. The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership (E8 Acquisition) and physical custody (E10 Transfer of Custody) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
|
Scope Note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more other instances of E39 Actor. The class also applies to the establishment or loss of ownership of instances of E18 Physical Thing. It does not, however, imply changes of any other kinds of right. The recording of the donor and/or recipient is optional. It is possible that in an instance of E8 Acquisition there is either no donor or no recipient. Depending on the circumstances, it may describe: - the beginning of ownership
- the end of ownership
- the transfer of ownership
- the acquisition from an unknown source
- the loss of title due to destruction of the item
It may also describe events where a collector appropriates legal title, for example by annexation or field collection. The interpretation of the museum notion of "accession" differs between institutions. The CIDOC CRM therefore models legal ownership (E8 Acquisition) and physical custody (E10 Transfer of Custody) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
|
Examples:
- the collection of a hammer-head shark of the genus Sphyrna (Carchariniformes) XXXtbc by John Steinbeck and Edward Ricketts at Puerto Escondido in the Gulf of Mexico on March 25th, 1940
- the acquisition of El Greco’s painting entitled ‘The Apostles Peter and Paul’ by the State Hermitage in Saint Petersburg
- the loss of my stuffed chaffinch ‘Fringilla coelebs Linnaeus, 1758’ due to insect damage last year
|
Examples:
- the collection of a hammer-head shark of the genus Sphyrna Rafinesque, 1810 (Carchariniformes) by John Steinbeck and Edward Ricketts at Puerto Escondido in the Gulf of Mexico on March 25th, 1940. (Steinbeck, 2000)
- the acquisition of El Greco’s painting entitled ‘The Apostles Peter and Paul’ by the State Hermitage in Saint Petersburg. (https://hermitagemuseum.org/wps/portal/hermitage/digital-collection/01.+Paintings/32730)
- the loss of my stuffed chaffinch ‘Fringilla coelebs Linnaeus, 1758’ due to insect damage last year (fictitious)
|
First order logic:
|
First order logic:
|
Properties:
P22 transferred title to (acquired title through): E39 ActorP23 transferred title from (surrendered title through): E39 ActorP24 transferred title of (changed ownership through): E18 Physical Thing
|
Properties:
P22 transferred title to (acquired title through): E39 ActorP23 transferred title from (surrendered title through): E39 ActorP24 transferred title of (changed ownership through): E18 Physical Thing
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises changes of the physical location of the instances of E19 Physical Object. Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
|
Scope Note:
This class comprises changes of the physical location of the instances of E19 Physical Object. Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
|
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
|
Examples:
- the relocation of London Bridge from the UK to the USA. (Wildfang, 2005)
- the movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15th September and 2nd November 2019.
|
First order logic:
|
First order logic:
|
Properties:
P25 moved (moved by): E19 Physical ObjectP26 moved to (was destination of): E53 PlaceP27 moved from (was origin of): E53 Place
|
Properties:
P25 moved (moved by): E19 Physical ObjectP26 moved to (was destination of): E53 PlaceP27 moved from (was origin of): E53 Place
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises transfers of physical custody of objects between instances of E39 Actor. The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe: - the beginning of custody
- the end of custody
- the transfer of custody
- the receipt of custody from an unknown source
- the declared loss of an object
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft. The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
|
Scope Note:
This class comprises transfers of the physical custody or the legal responsibility for the physical custody of objects. The recording of the donor or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances, it may describe: - the beginning of custody (there is no previous custodian)
- the end of custody (there is no subsequent custodian)
- the transfer of custody (transfer from one custodian to the next)
- the receipt of custody from an unknown source (the previous custodian is unknown)
- the declared loss of an object (the current or subsequent custodian is unknown)
In the event that only a single kind of transfer of custody occurs, either the legal responsibility for the custody or the actual physical possession of the object but not both, this difference should be expressed using the property P2 has type (is type of). The sense of physical possession requires that the object of custody be in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. The interpretation of the museum notion of "accession" differs between institutions. The CIDOC CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these. Theft is a specific case of illegal transfer of custody.
|
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981
|
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981 (Chipp, 1988)
- the transfer of custody of the work described as “Von der Velden ein Ufer an der See” from Johann Matthäus von Merian to the Auction House Heldevier (Jacob) for the purpose of sale, ca. 1716
- the transfer of custody of the painting ‘Mrs. Fitzherbert’ to the art dealer Knoedler from Parke-Bernet Galleries (New York, NY, USA) ca. March 1941
|
First order logic:
|
First order logic:
|
Properties:
P28 custody surrendered by (surrendered custody through): E39 ActorP29 custody received by (received custody through): E39 ActorP30 transferred custody of (custody transferred through): E18 Physical Thing
|
Properties:
P28 custody surrendered by (surrendered custody through): E39 ActorP29 custody received by (received custody through): E39 ActorP30 transferred custody of (custody transferred through): E18 Physical Thing
|
|
|
|
Superclass of:
E12 Production
E79 Part Addition
E80 Part Removal
|
Superclass of:
E12 Production
E79 Part Addition
E80 Part Removal
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing. This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation. Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities. If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
|
Scope Note:
This class comprises instances of E7 Activity that are undertaken to create, alter or change instances of E24 Physical Human-Made Thing. This class includes the production of an item from raw materials and other so far undocumented objects. It also includes the conservation treatment of an object. Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in an instance of E11 Modification, and that others may be produced as a result of it. An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities. An activity undertaken on an object which was designed to alter it, but which, in fact, it did not in any seemingly significant way (such as the application of a solvent during conservation which failed to dissolve any part of the object), is still considered as an instance of E11 Modification. Typically, any such activity will leave at least forensic traces of evidence on the object. If the instance of E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.
|
Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan
|
Examples:
- the construction of the SS Great Britain (E12) (Gregor, 1971)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956 (Håfors, 2010)
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81) (Yakel, 2000)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan (Cali and Dougil, 2012)
|
First order logic:
|
First order logic:
|
Properties:
P31 has modified (was modified by): E24 Physical Man-Made ThingP126 employed (was employed in): E57 Material
|
Properties:
P31 has modified (was modified by): E18 Physical ThingP126 employed (was employed in): E57 Material
|
|
|
|
Subclass of:
E11 Modification
E63 Beginning of Existence
|
Subclass of:
E11 Modification
E63 Beginning of Existence
|
Scope Note:
This class comprises activities that are designed to, and succeed in, creating one or more new items. It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one. This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
|
Scope Note:
This class comprises activities that are designed to, and succeed in, creating one or more new items. It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one. This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event. An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
|
Examples:
- the construction of the SS Great Britain
- the first casting of the Little Mermaid from the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12,E65,E81)
|
Examples:
- the construction of the SS Great Britain (Gregor, 1971)
- the first casting of the Little Mermaid from the harbour of Copenhagen (Dewey, 2003)
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12, E65, E81) (Hind, 1923)
|
First order logic:
|
First order logic:
- E12(x) ⇒ E11(x)
- E12(x) ⇒ E63(x)
|
Properties:
P108 has produced (was produced by): E24 Physical Man-Made Thing
|
Properties:
P108 has produced (was produced by): E24 Physical Human-Made ThingP186 produced thing of product type (is produced by): E99 Product Type
|
|
|
|
Superclass of:
E14 Condition Assessment
E15 Identifier Assignment
E16 Measurement
E17 Type Assignment
|
Superclass of:
E14 Condition Assessment
E15 Identifier Assignment
E16 Measurement
E17 Type Assignment
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts. This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules. In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
|
Scope Note:
This class comprises the actions of making assertions about one property of an object or any single relation between two items or concepts. The type of the property asserted to hold between two items or concepts can be described by the property P177 assigned property type: E55 Type. For example, the class describes the actions of people making propositions and statements during certain scientific/scholarly procedures, e.g., the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on whether this information should be accessible by structured queries. This class allows for the documentation of how the respective assignment came about, and whose opinion it was. Note that all instances of properties described in a knowledge base are the opinion of someone. Per default, they are the opinion of the team maintaining the knowledge base. This fact must not individually be registered for all instances of properties provided by the maintaining team, because it would result in an endless recursion of whose opinion was the description of an opinion. Therefore, the use of instances of E13 Attribute Assignment marks the fact, that the maintaining team is in general neutral to the validity of the respective assertion, but registers someone else’s opinion and how it came about. All properties assigned in such an action can also be seen as directly relating the respective pair of items or concepts. Multiple use of instances of E13 Attribute Assignment may possibly lead to a collection of contradictory values. All cases of properties in this model that are also described indirectly through a subclass of E13 Attribute Assignment are characterised as "short cuts" of a path via this subclass. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action of assertion or the short cut, and the relation between both alternatives can be captured by simple rules.
|
Examples:
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997
|
Examples:
- the examination of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad , 2010)
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997 (fictitious)
|
First order logic:
|
First order logic:
|
Properties:
P140 assigned attribute to (was attributed by): E1 CRM EntityP141 assigned (was assigned by): E1 CRM Entity
|
Properties:
P140 assigned attribute to (was attributed by): E1 CRM EntityP141 assigned (was assigned by): E1 CRM EntityP177 assigned property of type (is type of property assigned): E55 Type
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class describes the act of assessing the state of preservation of an object during a particular period. The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
|
Scope Note:
This class describes the act of assessing the state of preservation of an object during a particular period. The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
|
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village
|
Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village (fictitious)
- the condition assessment of the endband cores of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad, 2010)
- the condition assessment of the cover of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad, 2010)
|
First order logic:
|
First order logic:
|
Properties:
P34 concerned (was assessed by): E18 Physical ThingP35 has identified (was identified by): E3 Condition State
|
Properties:
P34 concerned (was assessed by): E18 Physical ThingP35 has identified (was identified by): E3 Condition State
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
|
Scope Note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. Instances of E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure. Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item. The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
|
Examples:
- of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
- The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
|
Examples:
- replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for the respective work
- on June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” to Guillaume de Machaut (Kelly, 2014)
|
First order logic:
|
First order logic:
|
Properties:
P37 assigned (was assigned by): E42 IdentifierP38 deassigned (was deassigned by): E42 IdentifierP142 used constituent (was used in): E41 Appellation
|
Properties:
P37 assigned (was assigned by): E42 IdentifierP38 deassigned (was deassigned by): E42 IdentifierP142 used constituent (was used in): E90 Symbolic Object
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises actions measuring physical properties and other values that can be determined by a systematic procedure.
|
Scope Note:
This class comprises actions measuring quantitative physical properties and other values that can be determined by a systematic, objective procedure of direct observation of particular states of physical reality. An instance of E16 Measurement may us simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Methods and devices employed should be associated with instances of E16 Measurement by properties such as P33 used specific technique: E29 Design or Procedure, P125 used object of type: E55 Type, P16 used specific object (was used for): E70 Thing, whereas basic techniques such as "carbon 14 dating" should be encoded using P2 has type (is type of): E55 Type. Details of methods and devices reused or reusable in other instances of E16 Measurement should be documented for these entities rather than the measurements themselves, whereas details of particular execution may be documented by free text or by instantiating adequate sub-activities, if the detail may be of interest for an overarching query. Regardless whether a measurement is made by an instrument or by human senses, it represents the initial transition from physical reality to information without any other documented information object in between within the reasoning chain that would represent the result of the interaction of the observer or device with reality. Therefore, determining properties of an instance of E90 Symbolic Object is regarded as an instance of E13 Attribute Assignment, which may be inferred from observing and measuring representative carriers. In the case that the carrier can be named, the property P16 used specific object (was used for): should be used to indicate the instance(s) of E18 Physical Thing that was used as the empirical basis for the attribute assignment. For instance, inferring properties of depicted items using image material, such as satellite images, is not regarded as an instance of E16 Measurement, but as a subsequent instance of E13 Attribute Assignment. Rather, only the production of the images, understood as arrays of radiation intensities, is regarded as an instance of E16 Measurement. The same reasoning holds for other sensor data.
|
Examples:
- include measuring the monetary value of a collection of coins or the running time of a specific video cassette.
- The E16 Measurement may use simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Details of methods and devices are best handled as free text, whereas basic techniques such as "carbon 14 dating" should be encoded using P2 has type (is type of:) E55 Type.
- measurement of height of silver cup 232 on the 31st August 1997
- the carbon 14 dating of the “Schoeninger Speer II” in 1996 [an about 400.000 years old Palaeolithic complete wooden spear found in Schoeningen, Niedersachsen, Germany in 1995]
|
Examples:
- measurement of the height of silver cup 232 on the 31st August 1997 (fictitious)
- the carbon 14 dating of the “Schoeninger Speer II” in 1996 [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995.] (Kouwenhoven, 1997)
|
First order logic:
|
First order logic:
|
Properties:
P39 measured (was measured by): E1 CRM EntityP40 observed dimension (was observed in): E54 Dimension
|
Properties:
P39 measured (was measured by): E18 Physical ThingP40 observed dimension (was observed in): E54 Dimension
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions and concepts. This class allows for the documentation of the context of classification acts in cases where the value of the classification depends on the personal opinion of the classifier, and the date that the classification was made. This class also encompasses the notion of "determination," i.e. the systematic and molecular identification of a specimen in biology.
|
Scope Note:
This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions and concepts. This class allows for the documentation of the context of classification acts in cases where the value of the classification depends on the personal opinion of the classifier, and the date that the classification was made. This class also encompasses the notion of "determination," i.e., the systematic and molecular identification of a specimen in biology.
|
Examples:
- the first classification of object GE34604 as Lament Cloth, October 2nd
- the determination of a cactus in Martin Doerr’s garden as ‘Cereus hildmannianus K.Schumann’, July 2003
|
Examples:
- the first classification of object GE34604 as Lament Cloth at the Museum Benaki, Athens
- the determination of a cactus in Martin Doerr’s garden as ‘Cereus hildmannianus K.Schumann’, July 2003
|
First order logic:
|
First order logic:
|
Properties:
P41 classified (was classified by): E1 CRM EntityP42 assigned (was assigned by): E55 Type
|
Properties:
P41 classified (was classified by): E1 CRM EntityP42 assigned (was assigned by): E55 Type
|
|
|
|
Superclass of:
E19 Physical Object
E24 Physical Man-Made Thing
E26 Physical Feature
|
Superclass of:
E19 Physical Object
E24 Physical Human-Made Thing
E26 Physical Feature
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises all persistent physical items with a relatively stable form, man-made or natural. Depending on the existence of natural boundaries of such things, the CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter. The CRM is generally not concerned with amounts of matter in fluid or gaseous states.
|
Scope Note:
This class comprises all persistent physical items with a relatively stable form, human-made or natural. Depending on the existence of natural boundaries of such things, the CIDOC CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter. An instance of E18 Physical Thing occupies not only a particular geometric space at any instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces, such as the interior of a box. For the purpose of more detailed descriptions of the presence of an instance of E18 Physical Thing in space and time it can be associated with its specific instance of E92 Spacetime Volume by the property P196 defines (is defined by). The CIDOC CRM is generally not concerned with amounts of matter in fluid or gaseous states, as long as they are not confined in an identifiable way for an identifiable minimal time-span.
|
Examples:
- the Cullinan Diamond (E19)
- the cave “Ideon Andron” in Crete (E26)
- the Mona Lisa (E22)
|
Examples:
- the Cullinan Diamond (E19) (Scarratt and Shor, 2006)
- the cave “Ideon Andron” in Crete (E26) (Smith, 1844-49)
- the Mona Lisa (E22) (Mohen, 2006)
|
First order logic:
|
First order logic:
|
Properties:
P44 has condition (is condition of): E3 Condition StateP45 consists of (is incorporated in): E57 MaterialP46 is composed of (forms part of): E18 Physical ThingP49 has former or current keeper (is former or current keeper of): E39 ActorP50 has current keeper (is current keeper of): E39 ActorP51 has former or current owner (is former or current owner of): E39 ActorP52 has current owner (is current owner of): E39 ActorP53 has former or current location (is former or current location of): E53 PlaceP58 has section definition (defines section): E46 Section DefinitionP59 has section (is located on or within): E53 Place
|
Properties:
P44 has condition (is condition of): E3 Condition StateP45 consists of (is incorporated in): E57 MaterialP46 is composed of (forms part of): E18 Physical ThingP49 has former or current keeper (is former or current keeper of): E39 ActorP50 has current keeper (is current keeper of): E39 ActorP51 has former or current owner (is former or current owner of): E39 ActorP52 has current owner (is current owner of): E39 ActorP53 has former or current location (is former or current location of): E53 PlaceP59 has section (is located on or within): E53 PlaceP128 carries (is carried by): E90 Symbolic ObjectP156 occupies (is occupied by): E53 PlaceP196 defines (is defined by): E92 Spacetime VolumeP198 holds or supports (is held or supported by): E18 Physical Thing
|
|
|
|
Superclass of:
E20 Biological Object
E22 Man-Made Object
|
Superclass of:
E20 Biological Object
E22 Human-Made Object
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises items of a material nature that are units for documentation and have physical boundaries that separate them completely in an objective way from other objects. The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen. Typically, instances of E19 Physical Object can be moved (if not too heavy). In some contexts, such objects, except for aggregates, are also called “bona fide objects” (Smith & Varzi, 2000, pp.401-420), i.e. naturally defined objects. The decision as to what is documented as a complete item, rather than by its parts or components, may be a purely administrative decision or may be a result of the order in which the item was acquired.
|
Scope Note:
This class comprises items of a material nature that are units for documentation and have physical boundaries that separate them completely in an objective way from other objects. The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen. Typically, instances of E19 Physical Object can be moved (if not too heavy). In some contexts, such objects, except for aggregates, are also called “bona fide objects” (Smith & Varzi, 2000, pp.401-420), i.e., naturally defined objects. The decision as to what is documented as a complete item, rather than by its parts or components, may be a purely administrative decision or may be a result of the order in which the item was acquired.
|
Examples:
- John Smith
- Aphrodite of Milos
- the Palace of Knossos
- the Cullinan Diamond
- Apollo 13 at the time of launch
|
Examples:
- Aphrodite of Milos (E22) (Kousser, 2005)
- the Cullinan Diamond (Scarratt and Shor, 2006)
- Apollo 13 at the time of launch (E22) (Lovell and Kluger, 1994)
|
First order logic:
|
First order logic:
|
Properties:
P54 has current permanent location (is current permanent location of): E53 PlaceP55 has current location (currently holds): E53 PlaceP56 bears feature (is found on): E26 Physical FeatureP57 has number of parts: E60 Number
|
Properties:
P54 has current permanent location (is current permanent location of): E53 PlaceP55 has current location (currently holds): E53 PlaceP56 bears feature (is found on): E26 Physical FeatureP57 has number of parts: E60 Number
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises individual items of a material nature, which live, have lived or are natural products of or from living organisms. Artificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Man-Made Object.
|
Scope Note:
This class comprises individual items of a material nature, which live, have lived or are natural products of or from living organisms. Artificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Human-Made Object.
|
Examples:
- me
- Tut-Ankh-Amun
- Boukephalas [Horse of Alexander the Great]
- petrified dinosaur excrement PA1906-344
|
Examples:
- me (fictitious)
- Tut-Ankh-Amun (Edwards and Boltin, 1979)
- Boukephalus [Horse of Alexander the Great] (Lamb, 2005)
- petrified dinosaur excrement PA1906-344
|
First order logic:
|
First order logic:
|
|
|
|
Subclass of:
E20 Biological Object
E39 Actor
|
Subclass of:
E20 Biological Object
E39 Actor
|
Scope Note:
This class comprises real persons who live or are assumed to have lived. Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CRM does not propose a specific form to support reasoning about possible identity.
|
Scope Note:
This class comprises real persons who live or are assumed to have lived. Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CIDOC CRM does not propose a specific form to support reasoning about possible identity. In a bibliographic context, a name presented following the conventions usually employed for personal names will be assumed to correspond to an actual real person (an instance of E21 Person), unless evidence is available to indicate that this is not the case. The fact that a persona may erroneously be classified as an instance of E21 Person does not imply that the concept comprises personae.
|
Examples:
- Tut-Ankh-Amun
- Nelson Mandela
|
Examples:
- Tut-Ankh-Amun (Edwards and Boltin, 1979)
- Nelson Mandela (Brown and Hort, 2006)
|
First order logic:
|
First order logic:
- E21(x) ⇒ E20(x)
- E21(x) ⇒ E39(x)
|
Properties:
|
Properties:
P152 has parent (is parent of): E21 Person
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
E19 Physical Object
E24 Physical Man-Made Thing
|
Subclass of:
E19 Physical Object
E24 Physical Human-Made Thing
|
Scope Note:
This class comprises physical objects purposely created by human activity. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, an inscribed piece of rock or a preserved butterfly are both regarded as instances of E22 Man-Made Object.
|
Scope Note:
This class comprises all persistent physical objects of any size that are purposely created by human activity and have physical boundaries that separate them completely in an objective way from other objects. The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen.
|
Examples:
- Mallard (the World’s fastest steam engine)
- the Portland Vase
- the Coliseum
|
Examples:
- the Rosetta Stone (E22)
- LNER Class A4 4468 Mallard [the World’s fastest steam locomotive, preserved at the National Railway Museum of York, UK] (Solomon, 2003)
- the Portland Vase (Walker, 2004)
|
First order logic:
|
First order logic:
- E22(x) ⇒ E19(x)
- E22(x) ⇒ E24(x)
|
|
|
|
Superclass of:
E22 Man-Made Object
E25 Man-Made Feature
E78 Collection
|
Superclass of:
E22 Human-Made Object
E25 Human-Made Feature
E78 Curated Holding
|
Subclass of:
E18 Physical Thing
E71 Man-Made Thing
|
Subclass of:
E18 Physical Thing
E71 Human-Made Thing
|
Scope Note:
This class comprises all persistent physical items that are purposely created by human activity. This class comprises man-made objects, such as a swords, and man-made features, such as rock art. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Man-Made Thing.
|
Scope Note:
This class comprises all persistent physical items of any size that are purposely created by human activity. This class comprises, besides others, Human-Made objects, such as a sword, and Human-Made features, such as rock art. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Human-Made Thing. Instances of Human-Made thing may be the result of modifying pre-existing physical things, preserving larger parts or most of the original matter and structure, which poses the question if they are new or even Human-Made, the respective interventions of production made on such original material should be obvious and sufficient to regard that the product has a new, distinct identity and intended function and is human-made. Substantial continuity of the previous matter and structure in the new product can be documented by describing the production process also as an instance of E81 Transformation. Whereas interventions of conservation and repair are not regarded to produce a new Human-Made thing, the results of preparation of natural history specimens that substantially change their natural or original state should be regarded as physical Human-Made things, including the uncovering of petrified biological features from a solid piece of stone. On the other side, scribbling a museum number on a natural object should not be regarded to make it Human-Made. This notwithstanding, parts, sections, segments, or features of a physical Human-Made thing may continue to be non-Human-Made and preserved during the production process, for example natural pearls used as a part of an eardrop.
|
Examples:
- the Forth Railway Bridge (E22)
- the Channel Tunnel (E25)
- the Historical Collection of the Museum Benaki in Athens (E78)
|
Examples:
- the Forth Railway Bridge (Shipway, Bouch, Baker and Fowler, 1990).
- the Channel Tunnel (E25) (Holliday, Marcou and Vickerman, 1991)
- the Palace of Knossos (Evans, 1921)
- the Coliseum in Rome, Italy (Hopkins and Beard, 2011)
- the Historical Collection of the Museum Benaki in Athens (E78) (Georgoula, 2005)
- the Rosetta Stone (E22)
- my paperback copy of Crime & Punishment (E22) (fictitious)
- the computer disk at ICS-FORTH that stores the canonical Definition of the CIDOC CRM v.3.2 (E22)
- my empty DVD disk (E22) (fictitious)
|
First order logic:
|
First order logic:
- E24(x) ⇒ E18(x)
- E24(x) ⇒ E71(x)
|
Properties:
P62 depicts (is depicted by): E1 CRM EntityP62.1 mode of depiction: E55 Type P65 shows visual item (is shown by): E36 Visual ItemP128 carries (is carried by): E90 Symbolic Object
|
Properties:
P62 depicts (is depicted by): E1 CRM EntityP62.1 mode of depiction: E55 Type P65 shows visual item (is shown by): E36 Visual Item
|
|
|
|
Subclass of:
E24 Physical Man-Made Thing
E26 Physical Feature
|
Subclass of:
E24 Physical Human-Made Thing
E26 Physical Feature
|
Scope Note:
This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc. No assumptions are made as to the extent of modification required to justify regarding a feature as man-made. For example, rock art or even “cup and ring” carvings on bedrock a regarded as types of E25 Man-Made Feature.
|
Scope Note:
This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc. In particular, it includes the information encoding features on mechanical or digital carriers.
|
Examples:
- the Manchester Ship Canal
- Michael Jackson’s nose following plastic surgery
|
Examples:
- the Manchester Ship Canal (Farnie, 1980)
- Michael Jackson’s nose following plastic surgery
- the laser-readable “pits” engraved June 2014 on Martin Doerr’s CD-R, copying songs of Edith Piaf.
- the carved letters on the Rosetta Stone
|
First order logic:
|
First order logic:
- E25(x) ⇒ E24(x)
- E25(x) ⇒ E26(x)
|
|
|
|
Superclass of:
|
Superclass of:
E25 Human-Made Feature
E27 Site
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises identifiable features that are physically attached in an integral way to particular physical objects. Instances of E26 Physical Feature share many of the attributes of instances of E19 Physical Object. They may have a one-, two- or three-dimensional geometric extent, but there are no natural borders that separate them completely in an objective way from the carrier objects. For example, a doorway is a feature but the door itself, being attached by hinges, is not. Instances of E26 Physical Feature can be features in a narrower sense, such as scratches, holes, reliefs, surface colours, reflection zones in an opal crystal or a density change in a piece of wood. In the wider sense, they are portions of particular objects with partially imaginary borders, such as the core of the Earth, an area of property on the surface of the Earth, a landscape or the head of a contiguous marble statue. They can be measured and dated, and it is sometimes possible to state who or what is or was responsible for them. They cannot be separated from the carrier object, but a segment of the carrier object may be identified (or sometimes removed) carrying the complete feature. This definition coincides with the definition of "fiat objects" (Smith & Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”.
|
Scope Note:
This class comprises identifiable features that are physically attached in an integral way to particular physical objects. Instances of E26 Physical Feature share many of the attributes of instances of E19 Physical Object. They may have a one-, two- or three-dimensional geometric extent, but there are no natural borders that separate them completely in an objective way from the carrier objects. For example, a doorway is a feature but the door itself, being attached by hinges, is not. Instances of E26 Physical Feature can be features in a narrower sense, such as scratches, holes, reliefs, surface colours, reflection zones in an opal crystal or a density change in a piece of wood. In the wider sense, they are portions of particular objects with partially imaginary borders, such as the core of the Earth, an area of property on the surface of the Earth, a landscape or the head of a contiguous marble statue. They can be measured and dated, and it is sometimes possible to state who or what is or was responsible for them. They cannot be separated from the carrier object, but a segment of the carrier object may be identified (or sometimes removed) carrying the complete feature. This definition coincides with the definition of "fiat objects" (Smith & Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”.
|
Examples:
- the temple in Abu Simbel before its removal, which was carved out of solid rock
- Albrecht Duerer's signature on his painting of Charles the Great
- the damage to the nose of the Great Sphinx in Giza
- Michael Jackson’s nose prior to plastic surgery
|
Examples:
- the cave of Dirou, Mani, Greece (Psimenos. 2005)
- the temple in Abu Simbel before its removal, which was carved out of solid rock (E25) (Hawass, 2000)
- Albrecht Duerer's signature on his painting of Charles the Great (E25) (Strauss, 1974)
- the damage to the nose of the Great Sphinx in Giza (Temple, 2009)
- Michael Jackson’s nose prior to plastic surgery
|
First order logic:
|
First order logic:
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises pieces of land or sea floor. In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings and maps. Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location.
|
Scope Note:
This class comprises pieces of land or sea floor. In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings and maps. Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location.
|
Examples:
- the Amazon river basin
- Knossos
- the Apollo 11 landing site
- Heathrow Airport
- the submerged harbour of the Minoan settlement of Gournia, Crete
|
Examples:
- the Amazon river basin (Hegen, 1966)
- Knossos (Evans, 1921)
- the Apollo 11 landing site (Siegler and Smrekar, 2014)
- Heathrow Airport (Wicks, 2014)
- the submerged harbour of the Minoan settlement of Gournia, Crete (Watrous, 2012)
- the island of Crete
|
First order logic:
|
First order logic:
|
|
|
|
Superclass of:
E55 Type
E89 Propositional Object
E90 Symbolic Object
|
Superclass of:
E55 Type
E89 Propositional Object
E90 Symbolic Object
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation or historical implication. The production of such information may have been supported by the use of technical devices such as cameras or computers. Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc. They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost.
|
Scope Note:
This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation or historical implication. The production of such information may have been supported by the use of technical devices such as cameras or computers. Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc. They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost.
|
Examples:
- Beethoven’s “Ode an die Freude” (Ode to Joy) (E73)
- the definition of “ontology” in the Oxford English Dictionary
- the knowledge about the victory at Marathon carried by the famous runner
|
Examples:
- Beethoven’s “Ode an die Freude” (Ode to Joy) (E73) (Kershaw, 1999)
- the definition of “ontology” in the Oxford English Dictionary (E73) (Oxford University Press, 1989)
- the knowledge about the victory at Marathon carried by the famous runner (E89) (Lagos & Karyanos, 2020)
- [Explanation note: In the following examples we illustrate the distinction between a propositional object, its names and its encoded forms. The Maxwell equations (Ball, 1962) are a good example, because they belong to the fundamental laws of physics and their mathematical content yields identical, unambiguous results regardless formulation and encoding.]
- “Maxwell equations” (E41) [preferred subject access point from LCSH, http://lccn.loc.gov/sh85082387, accessed 18th April 2021. This is only the name for the Maxwell equations as standardized by the Library of Congress and not the equations themselves.]
- “Equations, Maxwell” (E41) [variant subject access point from LCSH, http://lccn.loc.gov/sh85082387, accessed 18th April 2021. This is another name for the equation standardized by the Library of Congress and not the equations themselves.]
- Maxwell's equations (E89) [This is the propositional content of the equations proper, independent of any particular notation or mathematical formalism.] (Ball, 1962)
- The encoding of Maxwells equations as in https://upload.wikimedia.org/wikipedia/commons/c/c4/Maxwell%27sEquations.svg (E73) [accessed 18th April 2021. This is one possible symbolic encoding of the propositional content of the equations.]
|
First order logic:
|
First order logic:
|
Properties:
P149 is identified by (identifies): E75 Conceptual Object Appellation
|
Properties:
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular it comprises plans for deliberate human activities that may result in the modification or production of instances of E24 Physical Thing. Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 is associated with. Designs or procedures can be seen as one of the following: - A schema for the activities it describes
- A schema of the products that result from their application.
- An independent intellectual product that may have never been applied, such as Leonardo da Vinci’s famous plans for flying machines.
Because designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product.
|
Scope Note:
This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular, it comprises plans for deliberate human activities that may result in new instances of E71 Human-Made Thing or for shaping or guiding the execution of an instance of E7 Activity. Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 has association with (is associated with): E29 Design or Procedure. Designs or procedures can be seen as one of the following - A schema for the activities it describes
- A schema of the products that result from their application.
- An independent intellectual product that may have never been applied, such as Leonardo da Vinci’s famous plans for flying machines.
Because designs or procedures may never be applied or only partially executed, the CIDOC CRM models a loose relationship between the plan and the respective product.
|
Examples:
- the ISO standardisation procedure
- the musical notation for Beethoven’s “Ode to Joy”
- the architectural drawings for the Kölner Dom in Cologne, Germany
- The drawing on the folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486-1490, kept in the Biblioteca Ambrosiana in Milan
|
Examples:
- the ISO standardisation procedure
- the musical notation for Beethoven’s “Ode to Joy” (Kershaw, 1999)
- the architectural drawings for the Kölner Dom (Cologne Cathedral) in Cologne, Germany (Wolff, 1999)
- the drawing on the folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486-1490, kept in the Biblioteca Ambrosiana in Milan
|
First order logic:
|
First order logic:
|
Properties:
P68 foresees use of (use foreseen by): E57 MaterialP69 is associated with: E29 Design or ProcedureP69.1 has type: E55 Type
|
Properties:
P68 foresees use of (use foreseen by): E57 MaterialP69 has association with (is associated with): E29 Design or ProcedureP69.1 has type: E55 Type
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises legal privileges concerning material and immaterial things or their derivatives. These include reproduction and property rights.
|
Scope Note:
This class comprises legal privileges concerning material and immaterial things or their derivatives. These include reproduction and property rights.
|
Examples:
- copyright held by ISO on ISO/CD 21127
- ownership of the “Mona Lisa” by the Louvre
|
Examples:
- copyright held by ISO on ISO/CD 21127
- ownership of the “Mona Lisa” by the museum of the Louvre, Paris, France
|
First order logic:
|
First order logic:
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises identifiable immaterial items that make propositions about reality. These propositions may be expressed in text, graphics, images, audiograms, videograms or by other similar means. Documentation databases are regarded as a special case of E31 Document. This class should not be confused with the term “document” in Information Technology, which is compatible with E73 Information Object.
|
Scope Note:
This class comprises identifiable immaterial items that make propositions about reality. These propositions may be expressed in text, graphics, images, audiograms, videograms or by other similar means. Documentation databases are regarded as instances of E31 Document. This class should not be confused with the concept “document” in Information Technology, which is compatible with E73 Information Object.
|
Examples:
- the Encyclopaedia Britannica (E32)
- the photo of the Allied Leaders at Yalta published by UPI, 1945
- the Doomsday Book
|
Examples:
- the Encyclopaedia Britannica (E32) (Kogan, 1958)
- the image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E36)
- Domesday Book [a manuscript record of the "Great Survey" of much of England and parts of Wales completed in 1086 by order of King William the Conqueror] (Hallam 1986)
|
First order logic:
|
First order logic:
|
Properties:
P70 documents (is documented in): E1 CRM Entity
|
Properties:
P70 documents (is documented in): E1 CRM Entity
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.
|
Scope Note:
This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.
|
Examples:
- Webster's Dictionary
- Getty Art and Architecture Thesaurus
- the CIDOC Conceptual Reference Model
|
Examples:
- Webster's Dictionary (Herbert, 1994)
- Getty Art and Architecture Thesaurus (Getty Trust, 1990)
- the CIDOC Conceptual Reference Model (Gergatsoulis et al., 2010)
|
First order logic:
|
First order logic:
|
Properties:
P71 lists (is listed in): E1 CRM Entity
|
Properties:
P71 lists (is listed in): E1 CRM Entity
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises identifiable expressions in natural language or languages. Instances of E33 Linguistic Object can be expressed in many ways: e.g. as written texts, recorded speech or sign language. However, the CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CRM. These should be modelled as instances of E73 Information Object. The text of an instance of E33 Linguistic Object can be documented in a note by P3 has note: E62 String
|
Scope Note:
This class comprises identifiable expressions in natural language or languages. Instances of E33 Linguistic Object can be expressed in many ways: e.g., as written texts, recorded speech or sign language. However, the CIDOC CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CIDOC CRM. These should be modelled as instances of E73 Information Object. In general, an instance of E33 Linguistic Object may also contain non-linguistic information, often of artistic or aesthetic value. Only in cases in which the content of an instance of E33 Linguistic Object can completely be expressed by a series of binary-encoded symbols, its content may be documented within a respective knowledge base by the property P190 has symbolic content: E62 String. Otherwise, it should be understood as an identifiable digital resource only available independently from the respective knowledge base. In other cases, such as pages of an illuminated manuscript or recordings containing speech in a language supported by a writing system, the linguistic part of the content of an instance of E33 Linguistic Object may be documented within a respective knowledge base in a note by P3 has note: E62 String. Otherwise, it may be described using the property P165 incorporates (is incorporated in): E73 Information Object as a different object with its own identity.
|
Examples:
- the text of the Ellesmere Chaucer manuscript
- the lyrics of the song "Blue Suede Shoes"
- the text of the Jabberwocky by Lewis Carroll
- the text of "Doktoro Jekyll kaj Sinjoro Hyde" (an Esperanto translation of Dr Jekyll and Mr Hyde)
|
Examples:
- the text of the Ellesmere Chaucer manuscript (Hilmo, 2019)
- the lyrics of the song "Blue Suede Shoes" (Cooper, 2008)
- the text of the “Jabberwocky” by Lewis Carroll (Carroll, 1981)
- the text of "Doktoro Jekyll kaj Sinjoro Hyde" [an Esperanto translation of Dr Jekyll and Mr Hyde]. (Stevenson, Morrison and Mann, 1909)
- the free dialog in the local dialect recorded in 1958, Telemark, Norway stored on tape or.7-89.s1 (00.15:46-00:34), The Language Collection at the University Library in Bergen, Norway (as by 2020)
|
First order logic:
|
First order logic:
|
Properties:
P72 has language (is language of): E56 LanguageP73 has translation (is translation of): E33 Linguistic Object
|
Properties:
P72 has language (is language of): E56 LanguageP73 has translation (is translation of): E33 Linguistic Object
|
|
|
|
Subclass of:
E33 Linguistic Object
E37 Mark
|
Subclass of:
E33 Linguistic Object
E37 Mark
|
Scope Note:
This class comprises recognisable, short texts attached to instances of E24 Physical Man-Made Thing. The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CRM as E24 Physical Man-Made Thing. The relationship of a physical copy of a book to the text it contains is modelled using E84 Information Carrier. P128 carries (is carried by): E33 Linguistic Object.
|
Scope Note:
This class comprises recognisable, texts attached to instances of E24 Physical Human-Made Thing. The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CIDOC CRM as instances of E24 Physical Human-Made Thing. The relationship of a physical copy of a book to the text it contains is modelled using E18 Physical Thing. P128 carries (is carried by): E33 Linguistic Object.
|
Examples:
- “keep off the grass” on a sign stuck in the lawn of the quad of Balliol College
- The text published in Corpus Inscriptionum Latinarum V 895
- Kilroy was here
|
Examples:
- “keep off the grass” [on a sign stuck in the lawn of the quad of Balliol College, Oxford, UK]
- the text published in Corpus Inscriptionum Latinarum V 895 (Mommsen, 1872)
- “Kilroy was here”
|
First order logic:
|
First order logic:
- E34(x) ⇒ E33(x)
- E34(x) ⇒ E37(x)
|
|
|
|
Subclass of:
E33 Linguistic Object
E41 Appellation
|
Subclass of:
E33 Linguistic Object
E41 Appellation
|
Scope Note:
This class comprises the names assigned to works, such as texts, artworks or pieces of music. Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group. This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.
|
Scope Note:
This class comprises textual strings that within a cultural context can be clearly identified as titles due to their form. Being a subclass of E41 Appellation, E35 Title can only be used when such a string is actually used as a title of a work, such as a text, an artwork, or a piece of music. Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group. This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.
|
Examples:
- “The Merchant of Venice”
- “Mona Lisa”
- “La Pie or The Magpie”
- “Lucy in the Sky with Diamonds”
|
Examples:
- “The Merchant of Venice” (McCullough, 2005)
- “Mona Lisa” (Mohen, Menu and Mottin, 2006)
- “La Pie” (Bortolatto, 1981)
- “Lucy in the Sky with Diamonds” (Lennon, 1967)
|
First order logic:
|
First order logic:
- E35(x) ⇒ E33(x)
- E35(x) ⇒ E41(x)
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the intellectual or conceptual aspects of recognisable marks and images. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support. The class E36 Visual Item provides a means of identifying and linking together instances of E24 Physical Man-Made Thing that carry the same visual symbols, marks or images etc. The property P62 depicts (is depicted by) between E24 Physical Man-Made Thing and depicted subjects (E1 CRM Entity) can be regarded as a short-cut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity, which in addition captures the optical features of the depiction.
|
Scope Note:
This class comprises the intellectual or conceptual aspects of recognisable marks, images and other visual works. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support. The class E36 Visual Item provides a means of identifying and linking together instances of E24 Physical Human-Made Thing that carry the same visual qualities (symbols, marks or images etc.). The property P62 depicts (is depicted by) between E24 Physical Human-Made Thing and depicted subjects (E1 CRM Entity) is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity, which in addition captures the optical features of the depiction.
|
Examples:
- the visual appearance of Monet’s “La Pie” (E38)
- the Coca-Cola logo (E34)
- the Chi-Rho (E37)
- the communist red star (E37)
|
Examples:
- the visual appearance of Monet’s “La Pie” (Bortolatto, 1981)
- the Coca-Cola logo (E34)
- the Chi-Rho (E37)
- the communist red star (E37)
- the surface shape of Auguste Rodin's statue "Le Penseur" [there exist more than 20 copies, even of different size. Therefore, this is a good example that it is only the common surface shape, an immaterial visual item, which justifies displaying these copies as works of Auguste Rodin. As usual practice, Rodin himself did not produce the bronze statue, but only the prototype model]
|
First order logic:
|
First order logic:
|
Properties:
P138 represents (has representation): E1 CRM EntityP138.1 mode of representation: E55 Type
|
Properties:
P138 represents (has representation): E1 CRM EntityP138.1 mode of representation: E55 Type P199 represents instance of type: E55 Type
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises symbols, signs, signatures or short texts applied to instances of E24 Physical Man-Made Thing by arbitrary techniques in order to indicate the creator, owner, dedications, purpose, etc. This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Man-Made Feature.
|
Scope Note:
This class comprises symbols, signs, signatures or short texts applied to instances of E24 Physical Human-Made Thing by arbitrary techniques, often in order to indicate such things as creator, owner, dedications, purpose or to communicate information generally. Instances of E37 Mark do not represent the actual image of a mark, but the abstract ideal (or archetype) as used for codification in reference documents forming cultural documentation. This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Human-Made Feature.
|
Examples:
|
Examples:
- Minoan double axe mark (Lowe Fri, 2011)
- ©
- ☺
|
First order logic:
|
First order logic:
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises distributions of form, tone and colour that may be found on surfaces such as photos, paintings, prints and sculptures or directly on electronic media. The degree to which variations in the distribution of form and colour affect the identity of an instance of E38 Image depends on a given purpose. The original painting of the Mona Lisa in the Louvre may be said to bear the same instance of E38 Image as reproductions in the form of transparencies, postcards, posters or T-shirts, even though they may differ in size and carrier and may vary in tone and colour. The images in a “spot the difference” competition are not the same with respect to their context, however similar they may at first appear.
|
Scope Note:
|
Examples:
- the front side of all 20 Swiss Frs notes
- the image depicted on all reproductions of the Mona Lisa
|
Examples:
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises people, either individually or in groups, who have the potential to perform intentional actions for which they can be held responsible. The CRM does not attempt to model the inadvertent actions of such actors. Individual people should be documented as instances of E21 Person, whereas groups should be documented as instances of either E74 Group or its subclass E40 Legal Body.
|
Scope Note:
This class comprises people, either individually or in groups, who have the potential to perform intentional actions of kinds for which someone may be held responsible.
|
Examples:
- London and Continental Railways (E40)
- the Governor of the Bank of England in 1975 (E21)
- Sir Ian McKellan (E21)
|
Examples:
- London and Continental Railways (E74)
- the Governor of the Bank of England in 1975 (E21)
- Sir Ian McKellan (E21) (Gibson, 1986)
|
First order logic:
|
First order logic:
|
Properties:
P74 has current or former residence (is current or former residence of): E53 PlaceP75 possesses (is possessed by): E30 RightP76 has contact point (provides access to): E51 Contact PointP131 is identified by (identifies): E82 Actor Appellation
|
Properties:
P74 has current or former residence (is current or former residence of): E53 PlaceP75 possesses (is possessed by): E30 RightP76 has contact point (provides access to): E41 Appellation
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises institutions or groups of people that have obtained a legal recognition as a group and can act collectively as agents. This means that they can perform actions, own property, create or destroy things and can be held collectively responsible for their actions like individual people. The term 'personne morale' is often used for this in French.
|
Scope Note:
|
Examples:
- Greenpeace
- Paveprime Ltd
- the National Museum of Denmark
|
Examples:
|
|
|
|
Superclass of:
E35 Title
E42 Identifier
E44 Place Appellation
E49 Time Appellation
E51 Contact Point
E75 Conceptual Object Appellation
E82 Actor Appellation
|
Superclass of:
E35 Title
E42 Identifier
E61 Time Primitive
E94 Space Primitive
E95 Spacetime Primitive
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises all sequences of signs of any nature, either meaningful or not, that are used or can be used to refer to and identify a specific instance of some class within a certain context. Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes. Specific subclasses of E41 Appellation should be used when instances of E41 Appellation of a characteristic form are used for particular objects. Instances of E49 Time Appellation, for example, which take the form of instances of E50 Date, can be easily recognised. E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment
|
Scope Note:
This class comprises signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class or category within a certain context. Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but instead by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes. Different languages may use different appellations for the same thing, such as the names of major cities. Some appellations may be formulated using a valid noun phrase of a particular language. In these cases, the respective instances of E41 Appellation should also be declared as instances of E33 Linguistic Object. Then the language using the appellation can be declared with the property P72 has language: E56 Language. Instances of E41 Appellation may be used to identify any instance of E1 CRM Entity and sometimes are characteristic for instances of more specific subclasses E1 CRM Entity, such as for instances of E52 Time-Span (for instance “dates”), E39 Actor, E53 Place or E28 Conceptual Object. Postal addresses and E-mail addresses are characteristic examples of identifiers used by services transporting things between clients. Even numerically expressed identifiers for extents in space or time are also regarded as instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though they allow for determining some time or location by a known procedure starting from a reference point and by virtue of that fact play a double role as instances of E59 Primitive Value. E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment
|
Examples:
- "Martin"
- "the Forth Bridge"
- "the Merchant of Venice" (E35)
- "Spigelia marilandica (L.) L." [not the species, just the name]
- "information science" [not the science itself, but the name through which we refer to it in an English-speaking context]
|
Examples:
- "Martin"
- “Aquae Sulis Minerva”
- "the Merchant of Venice" (E35) (McCullough, 2005)
- "Spigelia marilandica (L.) L." [not the species, just the name] (Hershberger, Robacker and Jenkins, 2015)
- "information science" [not the science itself, but the name through which we refer to it in an English-speaking context]
- “安” [Chinese “an”, meaning “peace”]
- “6°5’29”N 45°12’13”W” [example of a spatial coordinate]
- “Black queen’s bishop 4” [chess coordinate, example of an identifier in a conceptual space (E89)]
- “19-MAR-1922” [example of date]
- “+41 22 418 5571” [example of contact point]
- "weasel@paveprime.com" [example of contact point]
- “CH-1211, Genève” [example of place appellation]
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan” [example of a postal address]
- “the poop deck of H.M.S Victory” [example of a section definition on a human-made object (E22)]
- “the Venus de Milo’s left buttock” [example of a section definition on a human-made object (E22)]
|
First order logic:
|
First order logic:
|
Properties:
P139 has alternative form: E41 AppellationP139.1 has type: E55 Type
|
Properties:
P139 has alternative form: E41 AppellationP139.1 has type: E55 Type
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
|
Scope Note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. Postal addresses, telephone numbers, urls and e-mail addresses are characteristic examples of identifiers used by services transporting things between clients. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
|
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
|
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1” (fictitious)
- “ISSN 0041-5278” [Identifier for “The Unesco courier (Print)”]
- “ISRC FIFIN8900186” [Identifier for : Kraft (29 min 14 s) / Magnus Lindberg, comp. ; Toimii Ensemble ; Swedish Radio symphony orchestra ; Esa-Pekka Salonen, dir.]
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules] (Reaney, 1974)
- “+41 22 418 5571”
- weasel@paveprime.com
- “Rue David Dufour 5, CH-1211, Genève”
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
|
First order logic:
|
First order logic:
|
|
|
NOT MATCHED
|
Superclass of:
E45 Address
E46 Section Definition
E47 Spatial Coordinates
E48 Place Name
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place. Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
|
Scope Note:
|
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
|
Examples:
|
|
|
NOT MATCHED
|
Subclass of:
E44 Place Appellation
E51 Contact Point
|
Subclass of:
|
Scope Note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing. An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
|
Scope Note:
|
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
|
Examples:
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind. The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
|
Scope Note:
|
Examples:
- “the entrance lobby to the Ripley Center”
- “the poop deck of H.M.S Victory”
- “the Venus de Milo’s left buttock”
- “left inner side of my box”
|
Examples:
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification. Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
|
Scope Note:
|
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
|
Examples:
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises particular and common forms of E44 Place Appellation. Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
|
Scope Note:
|
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
|
Examples:
|
|
|
NOT MATCHED
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span. The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
|
Scope Note:
|
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
|
Examples:
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises specific forms of E49 Time Appellation. Dates may vary in their degree of precision.
|
Scope Note:
|
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
|
Examples:
|
|
|
NOT MATCHED
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
|
Scope Note:
|
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
|
Examples:
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration. Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation. Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known. Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
|
Scope Note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration. Instances of E52 Time-Span have no semantic connotations about phenomena happening within the temporal extent they represent. They do not convey any meaning other than a positioning on the “time-line” of chronology. The actual extent of an instance of E52 Time-Span can be approximated by properties of E52 Time-Span giving inner and outer bounds in the form of dates (instances of E61 Time Primitive). Comparing knowledge about time-spans is fundamental for chronological reasoning. Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr & Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which we can infer knowledge about it, such as in relative chronologies. Some instances of E52 may be defined precisely as representing a declaration of a temporal extent, as, for instance, done in a business contract. They constitute declarative time-spans as defined in CRMgeo (Doerr & Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span. When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known.
|
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
|
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- the time-span of the Ming Dynasty (Chan, 2011)
|
First order logic:
|
First order logic:
|
Properties:
P78 is identified by (identifies): E49 Time AppellationP79 beginning is qualified by: E62 StringP80 end is qualified by: E62 StringP81 ongoing throughout: E61 Time PrimitiveP82 at some time within: E61 Time PrimitiveP83 had at least duration (was minimum duration of): E54 DimensionP84 had at most duration (was maximum duration of): E54 DimensionP86 falls within (contains): E52 Time-Span
|
Properties:
P79 beginning is qualified by: E62 StringP80 end is qualified by: E62 StringP81 ongoing throughout: E61 Time PrimitiveP82 at some time within: E61 Time PrimitiveP86 falls within (contains): E52 Time-SpanP191 had duration (was duration of): E54 Dimension
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter. The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation. It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance. Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
|
Scope Note:
This class comprises extents in the natural space we live in, in particular on the surface of the Eearth, in the pure sense of physics: independent from temporal phenomena and matter. They may serve describing the physical location of things or phenomena or other areas of interest. Geometrically, instances of E53 Place constitute single contiguous areas or a finite aggregation of disjoint areas in space which are each individually contiguous. They may have fuzzy boundaries. The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks, but may also be determined by reference to mobile objects. A Place can be determined by combining a frame of reference and a location with respect to this frame. It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance. Any instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for).
|
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
|
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring (fictitious)
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <- [the place between these two arrows in one of the reader's paper copy of this document. Each copy constitutes a different place of this spot.]
|
First order logic:
|
First order logic:
|
Properties:
P87 is identified by (identifies): E44 Place AppellationP88 consists of (forms part of): E53 PlaceP89 falls within (contains): E53 PlaceP121 overlaps with: E53 PlaceP122 borders with: E53 Place
|
Properties:
P89 falls within (contains): E53 PlaceP121 overlaps with: E53 PlaceP122 borders with: E53 PlaceP157 is at rest relative to (provides reference space for): E18 Physical ThingP168 place is defined by (defines place): E94 Space PrimitiveP171 at some place within: E94 Space PrimitiveP172 contains: E94 Space PrimitiveP189 approximates (is approximated by): E53 PlaceP189.1 has type: E55 Type
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc. An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions. Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
|
Scope Note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e., by points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc. An instance of E54 Dimension represents the empirical or theoretically derived quantity, including the precision tolerances resulting from the particular method or calculation. The identity of an instance of E54 Dimension depends on the method of its determination because each method may produce different values even when determining comparable qualities. For instance, the wingspan of a bird alive or dead is a different dimension. Thermoluninescence dating and Rehydroxylation [RHX] dating are different dimensions of temporal distance from now, even if they aim at dating the same object. The method of determination should be expressed using the property P2 has type (is type of). Note that simple terms such as “diameter” or “length” are normally insufficient to unambiguously describe a respective dimension. In contrast, “maximum linear extent” may be sufficient. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension adequate to the precision of the applied method of determination. If the respective quantity belongs to a non-discrete space according to the laws of physics, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that comparability of values described in different units depends critically on the representation as value regions. Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension, as appropriate.
|
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
|
Examples:
- the weight of the Luxor Obelisk [250 metric tons]
- the vertical height of the statue of David by Michaelangelo [5.17 metres]
- the weight of the Great Star of Africa diamond [530.2 carats]
- the calibrated C14 date for the Shroud of Turin [AD1262-1312, 1303-1384]
- the horizontal diameter of the Stonehenge Sarsen Circle [33 metres] (Pryor, 2016)
- the length of the sides of the Great Pyramid at Giza [230.34 metres] (Lehner and Hawass, 2017)
- the duration of the time span of the Battle of Issos/Issus on 15th November 333 B.C.E. [less than 12 hours] (Howard, 2012)
- Christie’s hammer price, in British Pounds, for Vincent van Gogh's "Still Life: Vase with Fifteen Sunflowers" in London on 30th March 1987 (E97) [24.75 million GBP (Brithish Pounds)]
|
First order logic:
|
First order logic:
|
Properties:
P90 has value: E60 NumberP91 has unit (is unit of): E58 Measurement Unit
|
Properties:
P90 has value: E60 NumberP91 has unit (is unit of): E58 Measurement Unit
|
|
|
|
Superclass of:
E56 Language
E57 Material
E58 Measurement Unit
|
Superclass of:
E56 Language
E57 Material
E58 Measurement Unit
E99 Product Type
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts 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.
|
Scope Note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CIDOC CRM classes. E55 Type is the CIDOC CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CIDOC 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): E55 Type. Such hierarchies may be extended with additional properties.
|
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
|
Examples:
- weight, length, depth [types for instances of E54]
- portrait, sketch, animation [types for instances of E36]
- French, English, German (E56)
- excellent, good, poor [types for instances of E3]
- Ford Model T, chop stick [types for instances of E22]
- cave, doline, scratch [types for instances of E26]
- poem, short story [types for instances of E33]
- wedding, earthquake, skirmish [types for instances of E5]
|
First order logic:
|
First order logic:
|
Properties:
P127 has broader term (has narrower term): E55 Type
|
Properties:
P127 has broader term (has narrower term): E55 TypeP150 defines typical parts of (defines typical wholes for): E55 Type
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts. This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”. It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
|
Scope Note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts. This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”. It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639-1:2002 and later versions.
|
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
|
Examples:
- el [Greek] (Palmer, 1980)
- en [English] (Wilson, 1983)
- eo [Esperanto] (Nuessel, 2000)
- es [Spanish] (Pineda, 1993)
- fr [French] (Rickard, 1974)
|
First order logic:
|
First order logic:
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class is a specialization of E55 Type and comprises the concepts of materials. Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of). This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”. It is recommended that internationally or nationally agreed codes and terminology are used.
|
Scope Note:
This class is a specialization of E55 Type and comprises the concepts of materials. Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of (forms part of): E18 Physical Thing). This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”. It is recommended that internationally or nationally agreed codes and terminology are used.
|
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
|
Examples:
- brick (Gurcke, 1987)
- gold (Watson, 1990)
- aluminium (Norman, 1986)
- polycarbonate (Mhaske, 2011)
- resin (Barton, 1992)
|
First order logic:
|
First order logic:
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc. This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”. Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
|
Scope Note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc. This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”. Système International (SI) units or internationally recognized non-SI terms should be used whenever possible, such as those defined by ISO80000:2009. Archaic Measurement Units used in historical records should be preserved.
|
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
- A [Ampere]
- GRD [Greek Drachme]
- C [degrees centigrade]
|
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second] (Hau et al., 1999)
- A [Ampere]
- GRD [Greek Drachme] (E98) (Daniel, 2014)
- C [degrees centigrade] (Beckman, 1998)
|
First order logic:
|
First order logic:
|
|
|
|
Superclass of:
|
Superclass of:
E60 Number
E61 Time Primitive
E62 String
E94 Space Primitive
E95 Spacetime Primitive
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises primitive values used as documentation elements, which are not further elaborated upon within the model. As such they are not considered as elements within our universe of discourse. No specific implementation recommendations are made. It is recommended that the primitive value system from the implementation platform be used to substitute for this class and its subclasses.
|
Scope Note:
This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions. The instances of E59 Primitive Value and its subclasses are not considered elements of the universe of discourse the CIDOC CRM aims to define and analyze. Rather, they play the role of a symbolic interface between the scope of the model and the world of mathematical and computational manipulations and the symbolic objects they define and handle. In particular, they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless of the nature of their mathematical abstractions. Therefore, in an implementation, instances of E59 Primitive should be represented directly in the encoded symbolic form supported by the respective platform, such as a character string or a formatted date. They must not be represented in an implementation indirectly via, another a universal resource identifier, which in turn is linked to the actual encoded symbolic form. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
|
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
|
Examples:
- “ABCDEFG” (E62)
- 3.14 (E60)
- 0 (E60)
- 1921-01-01 (E61)
|
First order logic:
|
First order logic:
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision. Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
|
Scope Note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision. Numbers are fundamentally distinct from numerically expressed identifiers in continua, which are instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension.
|
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
|
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
|
First order logic:
|
First order logic:
|
|
|
|
Subclass of:
|
Subclass of:
E41 Appellation
E59 Primitive Value
|
Scope Note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation. E61 Time Primitive is not further elaborated upon within the model.
|
Scope Note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and references to temporal coordinate systems to express time in some context relevant to cultural and scientific documentation. Instantiating different instances of E61 Time Primitive relative to the same instance of E52 Time Span allows for the expression of multiple opinions/approximations of the same phenomenon. When representing different opinions/approximations of the E52 Time Span of some E2 Temporal Entity, multiple instances of E61 Time Primitive should be instantiated relative to one E52 Time Span. Only one E52 Time Span should be instantiated since there is only one real phenomenal time extent of any given temporal entity. The instances of E61 Time Primitive are not considered as elements of the universe of discourse that the CIDOC CRM aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle. Therefore, they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class.
|
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
|
Examples:
- “1994 – 1997”
- “13th May 1768”
- “2000/01/01 00:00:59.7”
- “85th century BCE”
|
First order logic:
|
First order logic:
- E61(x) ⇒ E41(x)
- E61(x) ⇒ E59(x)
|
Properties:
|
Properties:
P170 defines time (time is defined by): E52 Time-Span
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc. E62 String is not further elaborated upon within the model
|
Scope Note:
This class comprises coherent sequences of binary-encoded symbols. They correspond to the content of an instance of E90 Symbolic object. Instances of E62 String represent only the symbol sequence itself. They may or may not contain a language code. In contrast, instances of other subclasses of E59 Primitive value represent entities in mathematical spaces other than that of symbol sequences, by using binary-encoded symbols, such as date expressions or numbers in decimal encoding. For instance, different syntactic forms of a date expression may represent the same date but consist of different strings.
|
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
|
Examples:
- “the Quick Brown Fox Jumps Over the Lazy Dog”
- “6F 6E 54 79 70 31 0D 9E”
|
First order logic:
|
First order logic:
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises events that bring into existence any E77 Persistent Item. It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
|
Scope Note:
This class comprises events that bring into existence any instance of E77 Persistent Item. It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”.
|
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
|
Examples:
- the birth of my child (E67) (fictitious)
- the birth of Snoopy, my dog (fictitious)
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower (E12) (Tissandier, 1889)
|
First order logic:
|
First order logic:
|
Properties:
P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Properties:
P92 brought into existence (was brought into existence by): E77 Persistent Item
|
|
|
|
Superclass of:
E6 Destruction
E68 Dissolution
E69 Death
E81 Transformation
|
Superclass of:
E6 Destruction
E68 Dissolution
E69 Death
E81 Transformation
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises events that end the existence of any E77 Persistent Item. It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
|
Scope Note:
This class comprises events that end the existence of any instance of E77 Persistent Item. It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”. In cases where substance from an instance of E64 Persistent Item continues to exist in a new form, the process would be documented as instances of E81 Transformation.
|
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
|
Examples:
- the death of Snoopy, my dog (fictitious)
- the melting of the snowman (E6)
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC (E7,E6) (Trell, 1945)
|
First order logic:
|
First order logic:
|
Properties:
P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Properties:
P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
E7 Activity
E63 Beginning of Existence
|
Subclass of:
E7 Activity
E63 Beginning of Existence
|
Scope Note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
|
Scope Note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
|
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
|
Examples:
- the framing of the U.S. Constitution (Farrand, 1913)
- the drafting of U.N. resolution 1441 (United Nations Security Council, 2002)
|
First order logic:
|
First order logic:
- E65(x) ⇒ E7(x)
- E65(x) ⇒ E63(x)
|
Properties:
P94 has created (was created by): E28 Conceptual Object
|
Properties:
P94 has created (was created by): E28 Conceptual Object
|
|
|
|
Subclass of:
E7 Activity
E63 Beginning of Existence
|
Subclass of:
E7 Activity
E63 Beginning of Existence
|
Scope Note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation. E66 Formation does not include the arbitrary aggregation of people who do not act as a collective. The formation of an instance of E74 Group does not mean that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
|
Scope Note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation. E66 Formation does not include the arbitrary aggregation of people who do not act as a collective. The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
|
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
|
Examples:
- the formation of the CIDOC CRM Special Interest Group in 2000
- the formation of the Soviet Union (Pipes, 1964)
- the conspiring of the murderers of Caesar (Irwin, 1935)
|
First order logic:
|
First order logic:
- E66(x) ⇒ E7(x)
- E66(x) ⇒ E63(x)
|
Properties:
P95 has formed (was formed by): E74 Group
|
Properties:
P95 has formed (was formed by): E74 GroupP151 was formed from (participated in): E74 Group
|
|
|
|
Subclass of:
E63 Beginning of Existence
|
Subclass of:
E63 Beginning of Existence
|
Scope Note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings). Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
|
Scope Note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living being). Twins, triplets etc. are typically brought into life by the same instance of E67 Birth. The introduction of E67 Birth as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the birth.
|
Examples:
- the birth of Alexander the Great
|
Examples:
- the birth of Alexander the Great (Stoneman, 2004)
|
First order logic:
|
First order logic:
|
Properties:
P96 by mother (gave birth): E21 PersonP97 from father (was father for): E21 PersonP98 brought into life (was born): E21 Person
|
Properties:
P96 by mother (gave birth): E21 PersonP97 from father (was father for): E21 PersonP98 brought into life (was born): E21 Person
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people. If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
|
Scope Note:
This class comprises the events that result in the formal or informal termination of an instance of E74 Group. If the dissolution was deliberate, the Dissolution event should also be instantiated as an instance of E7 Activity.
|
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
|
Examples:
- the fall of the Roman Empire (Whittington, 1964)
- the liquidation of Enron Corporation (Atlas, 2001)
|
First order logic:
|
First order logic:
|
Properties:
P99 dissolved (was dissolved by): E74 Group
|
Properties:
P99 dissolved (was dissolved by): E74 Group
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the deaths of human beings. If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
|
Scope Note:
This class comprises the deaths of human beings. If a person is killed, the death should be documented as an instance of both E69 Death and E7 Activity. The death or perishing of other living beings should be documented as instances of E64 End of Existence.
|
Examples:
- the murder of Julius Caesar (E69,E7)
- the death of Senator Paul Wellstone
|
Examples:
- the murder of Julius Caesar (E69, E7) (Irwin, 1935)
- the death of Senator Paul Wellstone (Monast and Tao, 2002)
|
First order logic:
|
First order logic:
|
Properties:
P100 was death of (died in): E21 Person
|
Properties:
P100 was death of (died in): E21 Person
|
|
|
|
Superclass of:
E71 Man-Made Thing
E72 Legal Object
|
Superclass of:
E71 Human-Made Thing
E72 Legal Object
|
Subclass of:
|
Subclass of:
|
Scope Note:
This general class comprises usable discrete, identifiable, instances of E77 Persistent Item that are documented as single units. They can be either intellectual products or physical things, and are characterized by relative stability. They may for instance either have a solid physical form, an electronic encoding, or they may be logical concept or structure.
|
Scope Note:
This general class comprises discrete, identifiable, instances of E77 Persistent Item that are documented as single units, that either consist of matter or depend on being carried by matter and are characterized by relative stability. They may be intellectual products or physical things. They may for instance have a solid physical form, an electronic encoding, or they may be a logical concept or structure.
|
Examples:
- my photograph collection (E78)
- the bottle of milk in my refrigerator (E22)
- the plan of the Strassburger Muenster (E29)
- the thing on the top of Otto Hahn’s desk (E19)
- the form of the no-smoking sign (E36)
- the cave of Dirou, Mani, Greece (E27)
|
Examples:
- my photograph collection (E78) (fictitious)
- the bottle of milk in my refrigerator (E22) (fictitious)
- the Riss A1 plan of the Straßburger Münster (French: Cathédrale Notre-Dame de Strasbourg) (E29) (Liess, R., 1985)
- the thing on the top of Otto Hahn’s desk (E19)
- the form of the no-smoking sign (E36)
- the cave of Dirou, Mani, Greece (E26) (Psimenos, 2005)
|
First order logic:
|
First order logic:
|
Properties:
P43 has dimension (is dimension of): E54 DimensionP101 had as general use (was use of): E55 TypeP130 shows features of (features are also found on): E70 ThingP130.1 kind of similarity: E55 Type
|
Properties:
P43 has dimension (is dimension of): E54 DimensionP101 had as general use (was use of): E55 TypeP130 shows features of (features are also found on): E70 ThingP130.1 kind of similarity: E55 Type
|
|
|
|
Superclass of:
E24 Physical Man-Made Thing
E28 Conceptual Object
|
Superclass of:
E24 Physical Human-Made Thing
E28 Conceptual Object
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises discrete, identifiable man-made items that are documented as single units. These items are either intellectual products or man-made physical things, and are characterized by relative stability. They may for instance have a solid physical form, an electronic encoding, or they may be logical concepts or structures.
|
Scope Note:
This class comprises discrete, identifiable human-made items that are documented as single units. These items are either intellectual products or human-made physical things, and are characterized by relative stability. They may for instance have a solid physical form, an electronic encoding, or they may be logical concepts or structures.
|
Examples:
- Beethoven’s 5th Symphony (E73)
- Michelangelo’s David
- Einstein’s Theory of General Relativity (E73)
- the taxon ‘Fringilla coelebs Linnaeus,1758’ (E55)
|
Examples:
- Beethoven’s 5th Symphony (E73) (Lockwood, 2015)
- Michelangelo’s David (E22) (Paoletti and Bagemihl, 2015)
- Einstein’s Theory of General Relativity (E89) (Hartle, 2003)
- the taxon ‘Fringilla coelebs Linnaeus,1758’ (E55) (Sinkevicius and Narusevicius, 2002)
|
First order logic:
|
First order logic:
|
Properties:
P102 has title (is title of): E35 TitleP102.1 has type: E55 Type P103 was intended for (was intention of): E55 Type
|
Properties:
P102 has title (is title of): E35 TitleP102.1 has type: E55 Type P103 was intended for (was intention of): E55 Type
|
|
|
|
Superclass of:
E18 Physical Thing
E90 Symbolic Object
|
Superclass of:
E18 Physical Thing
E90 Symbolic Object
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied. This is true for all E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of the E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CRM.
|
Scope Note:
This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied. This is true for all instances of E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of an instance of E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CIDOC CRM.
|
Examples:
- the Cullinan diamond (E19)
- definition of the CIDOC Conceptual Reference Model Version 2.1 (E73)
|
Examples:
- the Cullinan diamond (E19) (Scarratt and Shor, 2006)
- definition of the CIDOC Conceptual Reference Model Version 5.0.4 (E73) (ISO 21127: 2014)
|
First order logic:
|
First order logic:
|
Properties:
P104 is subject to (applies to): E30 RightP105 right held by (has right on): E39 Actor
|
Properties:
P104 is subject to (applies to): E30 RightP105 right held by (has right on): E39 Actor
|
|
|
|
Superclass of:
E29 Design or Procedure
E31 Document
E33 Linguistic Object
E36 Visual Item
|
Superclass of:
E29 Design or Procedure
E31 Document
E33 Linguistic Object
E36 Visual Item
|
Subclass of:
E89 Propositional Object
E90 Symbolic Object
|
Subclass of:
E89 Propositional Object
E90 Symbolic Object
|
Scope Note:
This class comprises identifiable immaterial items, such as a poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. An E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression.
|
Scope Note:
This class comprises identifiable immaterial items, such as poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. The encoding structure known as a "named graph" also falls under this class, so that each "named graph" is an instance of E73 Information Object. An instance of E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression.
|
Examples:
- image BM000038850.JPG from the Clayton Herbarium in London
- E. A. Poe's "The Raven"
- the movie "The Seven Samurai" by Akira Kurosawa
- the Maxwell Equations
|
Examples:
- image BM000038850.JPG from the Clayton Herbarium in London (E31) (Natural History Museum, 2021)
- E. A. Poe's "The Raven" (Poe, 1869)
- the movie "The Seven Samurai" by Akira Kurosawa (Mellen, 2002)
- the text of Huray describing the Maxwell Equations (Huray, 2010)
- the Getty AAT as published as Linked Open Data, accessed 1/10/2014
|
First order logic:
|
First order logic:
- E73(x) ⇒ E89(x)
- E73(x) ⇒ E90(x)
|
Properties:
|
Properties:
P165 incorporates (is incorporated in): E90 Symbolic Object
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises any gatherings or organizations of two or more people that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. A gathering of people becomes an E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modeled as membership in an E74 Group (cf. HumanML markup). Married couples and other concepts of family are regarded as particular examples of E74 Group.
|
Scope Note:
This class comprises any gatherings or organizations of human individuals or groups that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. In such cases, it may happen that the group never had more than one member. A joint pseudonym (i.e., a name that seems indicative of an individual but that is actually used as a persona by two or more people) is a particular case of E74 Group. A gathering of people becomes an instance of E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modelled as membership in an instance of E74 Group. Married couples and other concepts of family are regarded as particular examples of E74 Group.
|
Examples:
- the impressionists
- the Navajo
- the Greeks
- the peace protestors in New York City on February 15 2003
- Exxon-Mobil
- King Solomon and his wives
- The President of the Swiss Confederation
|
Examples:
- the impressionists (Wilson, 1994)
- the Navajo (Correll, 1972)
- the Greeks (Williams, 1993)
- the peace protestors in New York City on 15th February 2003
- Exxon-Mobil (Raymond, 2006)
- King Solomon and his wives (Thieberger, 1947)
- the President of the Swiss Confederation
- Nicolas Bourbaki [the collective pseudonym of a group of mathematicians, predominantly French alumni of the École normale supérieure] (Aczel, 2007)
- Betty Crocker (Crocker, 2012)
- Ellery Queen [Ellery Queen is a pseudonym created in 1929 by American crime fiction writers Frederic Dannay and Manfred Bennington Lee.] (Wheat, 2005)
- Greenpeace
- Paveprime Ltd
- the National Museum of Denmark
|
First order logic:
|
First order logic:
|
Properties:
P107 has current or former member (is current or former member of): E39 ActorP107.1 kind of member: E55 Type
|
Properties:
P107 has current or former member (is current or former member of): E39 ActorP107.1 kind of member: E55 Type
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises all appellations specific to intellectual products or standardized patterns.
|
Scope Note:
|
Examples:
- “ISBN 3-7913-1418-1”
- “ISO 2788-1986 (F)”
|
Examples:
|
|
|
|
Superclass of:
|
Superclass of:
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises items that have a persistent identity, sometimes known as “endurants” in philosophy. They can be repeatedly recognized within the duration of their existence by identity criteria rather than by continuity or observation. Persistent Items can be either physical entities, such as people, animals or things, or conceptual entities such as ideas, concepts, products of the imagination or common names. The criteria that determine the identity of an item are often difficult to establish -; the decision depends largely on the judgement of the observer. For example, a building is regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria. Similarly, inanimate objects may be subject to exchange of parts and matter. The class E77 Persistent Item does not take any position about the nature of the applicable identity criteria and if actual knowledge about identity of an instance of this class exists. There may be cases, where the identity of an E77 Persistent Item is not decidable by a certain state of knowledge. The main classes of objects that fall outside the scope the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties.
|
Scope Note:
This class comprises items that have persistent characteristics of structural nature substantially related to their identity and their integrity, sometimes known as “endurants” in philosophy. Persistent Items may be physical entities, such as people, animals or things, conceptual entities such as ideas, concepts, products of the imagination or even names. Instances of E77 Persistent Item may be present or be part of interactions in different periods or events. They can repeatedly be recognized at disparate occasions during their existence by characteristics of structural nature. The respective characteristics need not be exactly the same during all the existence of an instance of E77 Persistent Item. Often, they undergo gradual change, still bearing some similarities with that of previous times, or disappear completely and new emerge. For instance, a person, from the time of being born on, will gradually change all its features and acquire new ones, such as a scar. Even the DNA in different body cells will develop defects and mutations. Nevertheless, relevant characteristics use to be sufficiently similar to recognize the instance for some substantial period of time. The more specific criteria that determine the identity of instances of subclasses of E77 Persistent Item may vary considerably and are described of referred to in the respective scope notes. The decision about which exact criteria to use depends on whether the observable behaviour of the respective part of reality such confined conforms to the reasoning the user is interested in. For example, a building can be regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria, such as being bodily separated from other persons. Similarly, inanimate objects may be subject to exchange of parts and matter. On the opposite, the identity of a (version of a) text of a scientific publication is given by the exact arrangement of its relevant symbols. The main classes of objects that fall outside the scope of the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties. An instance of E77 Persistent Item does not require actual knowledge of the identifying features of the instance being currently known. There may be cases, where the actual identifying features of an instance of E77 Persistent Item are not decidable at a particular state of knowledge.
|
Examples:
- Leonard da Vinci
- Stonehenge
- the hole in the ozone layer
- the First Law of Thermodynamics
- the Bermuda Triangle
|
Examples:
- Leonard da Vinci (E21) (Strano, 1953)
- Stonehenge (E24) (Pryor, 2016)
- the hole in the ozone layer (E4) (Hufford and Horwitz, 2005)
- the First Law of Thermodynamics (E89) (Craig and Gislason, 2002)
- the Bermuda Triangle (E53) (Dolan, 2005)
|
First order logic:
|
First order logic:
|
|
|
|
Subclass of:
E24 Physical Man-Made Thing
|
Subclass of:
E24 Physical Human-Made Thing
|
Scope Note:
This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. Items may be added or removed from an E78 Collection in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Collection often referred to with the name of the E78 Collection (e.g. “The Wallace Collection decided…”). Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Collection. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.
|
Scope Note:
This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. Typical instances of curated holdings are museum collections, archives, library holdings and digital libraries. A digital library is regarded as an instance of E18 Physical Thing because it requires keeping physical carriers of the electronic content. Items may be added or removed from an E78 Curated Holding in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Curated Holding often referred to with the name of the E78 Curated Holding (e.g., “The Wallace Collection decided…”). Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Curated Holding. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.
|
Examples:
- the John Clayton Herbarium
- the Wallace Collection
- Mikael Heggelund Foslie’s coralline red algae Herbarium at Museum of Natural History and Archaeology, Trondheim, Norway
|
Examples:
- the John Clayton Herbarium (Blake, 1918), (Natural History Museum, 2021)
- the Wallace Collection (Ingamells, 1990)
- Mikael Heggelund Foslie’s coralline red algae Herbarium at Museum of Natural History and Archaeology, Trondheim, Norway (Woelkerling et al., 2005)
- the Digital Collections of the Munich DigitiZation Center (MDZ) accessible via https://www.digitale-sammlungen.de/ at least in January 2018.
|
First order logic:
|
First order logic:
|
Properties:
P109 has current or former curator (is current or former curator of): E39 Actor
|
Properties:
P109 has current or former curator (is current or former curator of): E39 Actor
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises activities that result in an instance of E24 Physical Man-Made Thing being increased, enlarged or augmented by the addition of a part. Typical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated E78 Collection. Objects to which parts are added are, by definition, man-made, since the addition of a part implies a human activity. Following the addition of parts, the resulting man-made assemblages are treated objectively as single identifiable wholes, made up of constituent or component parts bound together either physically (for example the engine becoming a part of the car), or by sharing a common purpose (such as the 32 chess pieces that make up a chess set). This class of activities forms a basis for reasoning about the history and continuity of identity of objects that are integrated into other objects over time, such as precious gemstones being repeatedly incorporated into different items of jewellery, or cultural artifacts being added to different museum instances of E78 Collection over their lifespan.
|
Scope Note:
This class comprises activities that result in an instance of E24 Physical Human-Made Thing being increased, enlarged or augmented by the addition of a part. Typical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated instance of E78 Curated Holding. Objects to which parts are added are, by definition, human-made, since the addition of a part implies a human activity. Following the addition of parts, the resulting human-made assemblages are treated objectively as single identifiable wholes, made up of constituent or component parts bound together either physically (for example the engine becoming a part of the car), or by sharing a common purpose (such as the 32 chess pieces that make up a chess set). This class of activities forms a basis for reasoning about the history and continuity of identity of objects that are integrated into other objects over time, such as precious gemstones being repeatedly incorporated into different items of jewellery, or cultural artifacts being added to different museum instances of E78 Curated Holding over their lifespan.
|
Examples:
- the setting of the koh-i-noor diamond into the crown of Queen Elizabeth the Queen Mother
- the addition of the painting “Room in Brooklyn” by Edward Hopper to the collection of the Museum of Fine Arts, Boston
|
Examples:
- the setting of the Koh-I-Noor diamond into the crown of Queen Elizabeth the Queen Mother (Dalrymple, 2017)
- the addition of the painting “Room in Brooklyn” by Edward Hopper to the collection of the Museum of Fine Arts, Boston
|
First order logic:
|
First order logic:
|
Properties:
P110 augmented (was augmented by): E24 Physical Man-Made ThingP111 added (was added by): E18 Physical Thing
|
Properties:
P110 augmented (was augmented by): E24 Physical Human-Made ThingP111 added (was added by): E18 Physical Thing
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the activities that result in an instance of E18 Physical Thing being decreased by the removal of a part. Typical scenarios include the detachment of an accessory, the removal of a component or part of a composite object, or the deaccessioning of an object from a curated E78 Collection. If the E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an E81 Transformation, i.e. a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be regarded as both E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewelry, or cultural artifacts being deaccessioned from different museum collections over their lifespan.
|
Scope Note:
This class comprises the activities that result in an instance of E18 Physical Thing being decreased by the removal of a part. Typical scenarios include the detachment of an accessory, the removal of a component or part of a composite object, or the deaccessioning of an object from a curated collection, an instance of E78 Curated Holding. If the instance of E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an instance of E81 Transformation, i.e., a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be modelled as both an instance of E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewellry, or cultural artifacts being deaccessioned from different museum collections over their lifespan.
|
Examples:
- the removal of the engine from my car
- the disposal of object number 1976:234 from the collection
|
Examples:
- the removal of the engine from my car (fictitious)
- the disposal of object number 1976:234 from the collection (fictitious)
|
First order logic:
|
First order logic:
|
Properties:
P112 diminished (was diminished by): E24 Physical Man-Made ThingP113 removed (was removed by): E18 Physical Thing
|
Properties:
P112 diminished (was diminished by): E24 Physical Human-Made ThingP113 removed (was removed by): E18 Physical Thing
|
|
|
|
Subclass of:
E63 Beginning of Existence
E64 End of Existence
|
Subclass of:
E63 Beginning of Existence
E64 End of Existence
|
Scope Note:
This class comprises the events that result in the simultaneous destruction of one or more than one E77 Persistent Item and the creation of one or more than one E77 Persistent Item that preserves recognizable substance from the first one(s) but has fundamentally different nature and identity. Although the old and the new instances of E77 Persistent Item are treated as discrete entities having separate, unique identities, they are causally connected through the E81 Transformation; the destruction of the old E77 Persistent Item(s) directly causes the creation of the new one(s) using or preserving some relevant substance. Instances of E81 Transformation are therefore distinct from re-classifications (documented using E17 Type Assignment) or modifications (documented using E11 Modification) of objects that do not fundamentally change their nature or identity. Characteristic cases are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimen in natural history and the reorganization of a corporate body into a new one.
|
Scope Note:
This class comprises the events that result in the simultaneous destruction of one or more than one E18 Physical Thing and the creation of one or more than one E18 Physical Thing that preserves recognizable substance and structure from the first one(s) but has fundamentally different nature or identity. Although the old and the new instances of E18 Physical Thing are treated as discrete entities having separate, unique identities, they are causally connected through the E81 Transformation; the destruction of the old E18 Physical Thing(s) directly causes the creation of the new one(s) using or preserving some relevant substance and structure. Instances of E81 Transformation are therefore distinct from re-classifications (documented using E17 Type Assignment) or modifications (documented using E11 Modification) of objects that do not fundamentally change their nature or identity. Characteristic cases are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimen in natural history. Even though such instances of E81 Transformation are often motivated by a change of intended use, substantial material changes should justify the documentation of the result as a new instance of E18 Physical Thing and not just the change of function. The latter may be documented as an extended activity (instance of E7 Activity) of using it.
|
Examples:
- the death and mummification of Tut-Ankh-Amun (transformation of Tut-Ankh-Amun from a living person to a mummy) (E69,E81,E7)
|
Examples:
- the mummification of Tut-Ankh-Amun (E81, E12) [the mummification of the body of the deceased is a human production process and simultaneously preserves structures of the body at and before death] (Carter and Mace 1977)
- the death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the Eruption of Mount Vesuvius (E69, E81)
- the transformation of the Hephaisteion temple in Athens, better known as "Theseion", into a Christian church, dedicated to Saint George around AD 700 (E81,E12) [which actually helped preserving part of the antique temple structure from 449BC]
|
First order logic:
|
First order logic:
- E81(x) ⇒ E63(x)
- E81(x) ⇒ E64(x)
|
Properties:
P123 resulted in (resulted from): E77 Persistent ItemP124 transformed (was transformed by): E77 Persistent Item
|
Properties:
P123 resulted in (resulted from): E18 Physical ThingP124 transformed (was transformed by): E18 Physical Thing
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises any sort of name, number, code or symbol characteristically used to identify an E39 Actor. An E39 Actor will typically have more than one E82 Actor Appellation, and instances of E82 Actor Appellation in turn may have alternative representations. The distinction between corporate and personal names, which is particularly important in library applications, should be made by explicitly linking the E82 Actor Appellation to an instance of either E21 Person or E74 Group/E40 Legal Body. If this is not possible, the distinction can be made through the use of the P2 has type mechanism.
|
Scope Note:
|
Examples:
- “John Doe”
- “Doe, J”
- “the U.S. Social Security Number 246-14-2304”
- “the Artist Formerly Known as Prince”
- “the Master of the Flemish Madonna”
- “Raphael’s Workshop”
- “the Brontë Sisters”
- “ICOM”
- “International Council of Museums”
|
Examples:
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises activities formally defining new types of items. It is typically a rigorous scholarly or scientific process that ensures a type is exhaustively described and appropriately named. 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. The activity of E83 Type Creation is 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 “orgininal element” or “holotype”.
|
Scope Note:
This class comprises activities formally defining new types of items. It is typically a rigorous scholarly or scientific process that ensures a type is exhaustively described and appropriately named. 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. The activity modelled as an instance of E83 Type Creation is 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”.
|
Examples:
- creation of the taxon 'Penicillium brefeldianum B. O. Dodge' (1933)
- addition of class E84 Information Carrier to the CIDOC CRM
|
Examples:
- creation of the taxon 'Penicillium brefeldianum’ (Dodge, 1933)
- addition of class E85 Joining to the CIDOC CRM
|
First order logic:
|
First order logic:
|
Properties:
P135 created type (was created by): E55 TypeP136 was based on (supported type creation): E1 CRM EntityP136.1 in the taxonomic role: E55 Type
|
Properties:
P135 created type (was created by): E55 TypeP136 was based on (supported type creation): E1 CRM EntityP136.1 in the taxonomic role: E55 Type
|
|
|
NOT MATCHED
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises all instances of E22 Man-Made Object that are explicitly designed to act as persistent physical carriers for instances of E73 Information Object. This allows a relationship to be asserted between an E19 Physical Object and its immaterial information contents. An E84 Information Carrier may or may not contain information, e.g., a diskette. Note that any E18 Physical Thing may carry information, such as an E34 Inscription. However, unless it was specifically designed for this purpose, it is not an Information Carrier. Therefore the property P128 carries (is carried by) applies to E18 Physical Thing in general.
|
Scope Note:
|
Examples:
- the Rosetta Stone
- my paperback copy of Crime & Punishment
- the computer disk at ICS-FORTH that stores the canonical Definition of the CIDOC CRM
|
Examples:
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the activities that result in an instance of E39 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party. Typical scenarios include becoming a member of a social organisation, becoming employee of a company, marriage, the adoption of a child by a family and the inauguration of somebody into an official position.
|
Scope Note:
This class comprises the activities that result in an instance of E39 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party. Typical scenarios include becoming a member of a social organisation, becoming employee of a company, marriage, the adoption of a child by a family and the inauguration of somebody into an official position.
|
Examples:
- The election of Sir Isaac Newton as Member of Parliament for the University of Cambridge to the Convention Parliament of 1689
- The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985
- The implementation of the membership treaty between EU and Denmark January 1. 1973
|
Examples:
- the election of Sir Isaac Newton as Member of Parliament for the University of Cambridge to the Convention Parliament of 1689 (Gleick,2003)
- the inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (Butson, 1986)
- the implementation of the membership treaty between EU and Denmark, 1st January 1993
|
First order logic:
|
First order logic:
|
Properties:
P143 joined (was joined by): E39 ActorP144 joined with (gained member by): E74 GroupP144.1 kind of member: E55 Type
|
Properties:
P143 joined (was joined by): E39 ActorP144 joined with (gained member by): E74 GroupP144.1 kind of member: E55 Type
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party. Typical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position.
|
Scope Note:
This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party. Typical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position.
|
Examples:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702
- George Washington’s leaving office in 1797
- The implementation of the treaty regulating the termination of Greenland’s membership in EU between EU, Denmark and Greenland February 1. 1985
|
Examples:
- the end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (Gleick, 2003)
- George Washington’s leaving office in 1797 (Jones, 1979)
- the implementation of the treaty regulating the termination of Greenland’s membership in EU between EU, Denmark and Greenland February 1. 1985
|
First order logic:
|
First order logic:
|
Properties:
P145 separated (left by): E39 ActorP146 separated from (lost member by): E74 Group
|
Properties:
P145 separated (left by): E39 ActorP146 separated from (lost member by): E74 Group
|
|
|
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises the activities that result in the continuity of management and the preservation and evolution of instances of E78 Collection, following an implicit or explicit curation plan. It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded. Items are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an E78 Collection for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity.
|
Scope Note:
This class comprises the activities that result in the continuity of management and the preservation and evolution of instances of E78 Curated Holding, following an implicit or explicit curation plan. It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded. Items are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an instance of E78 Curated Holding for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity.
|
Examples:
- The curation of Mikael Heggelund Foslie’s coralline red algae Herbarium 1876 – 1909 (when Foslie died), now at Museum of Natural History and Archaeology, Norway
|
Examples:
- the curation of Mikael Heggelund Foslie’s coralline red algae Herbarium 1876 – 1909 (when Foslie died), now at Museum of Natural History and Archaeology, Norway (Woelkerling et al., 2005)
|
First order logic:
|
First order logic:
|
Properties:
P147 curated (was curated by): E78 Collection
|
Properties:
P147 curated (was curated by): E78 Curated Holding
|
|
|
|
Superclass of:
E30 Right
E73 Information Object
|
Superclass of:
E30 Right
E73 Information Object
|
Subclass of:
|
Subclass of:
|
Scope Note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse. This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
|
Scope Note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse. This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
|
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
|
Examples:
- Maxwell’s Equations (Ball, 1962)
- the ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in Oxford edition
- the underlying prototype of any “no-smoking” sign (E36)
- the common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges (Mellen, 2002)
- the image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E36)
- the character "Little Red Riding Hood", variants of which appear amongst others in Grimm brothers’ ‘Rotkäppchen’, other oral fairy tales and the film 'Hoodwinked'
- the place "Havnor" as invented by Ursula K. Le Guin for her ‘Earthsea’ book series, the related maps and appearing in derivative works based on these novels
|
First order logic:
|
First order logic:
|
Properties:
P67 refers to (is referred to by): E1 CRM EntityP67.1 has type: E55 Type P129 is about (is subject of): E1 CRM EntityP148 has component (is component of): E89 Propositional Object
|
Properties:
P67 refers to (is referred to by): E1 CRM EntityP67.1 has type: E55 Type P129 is about (is subject of): E1 CRM EntityP148 has component (is component of): E89 Propositional Object
|
|
|
|
Superclass of:
E41 Appellation
E73 Information Object
|
Superclass of:
E41 Appellation
E73 Information Object
|
Subclass of:
E28 Conceptual Object
E72 Legal Object
|
Subclass of:
E28 Conceptual Object
E72 Legal Object
|
Scope Note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units. It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
|
Scope Note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units. It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string. In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note and its subproperty P190 has symbolic content allow for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g., "bit", "Latin character", RGB pixel).
|
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
|
Examples:
- ‘ecognizabl’
- the “no-smoking” sign (E36)
- “BM000038850.JPG” (E41) [identifies a digital image] (Natural History Museum, 2021)
- image BM000038850.JPG from the Clayton Herbarium in London (E36) [depicts specimen of Verbesina virginica] (Natural History Museum, 2021)
- the distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E36)
- the Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (Petrocchi, 1967) (E33)
|
First order logic:
|
First order logic:
- E90(x) ⇒ E28(x)
- E90(x) ⇒ E72(x)
|
Properties:
P106 is composed of (forms part of): E90 Symbolic Object
|
Properties:
P106 is composed of (forms part of): E90 Symbolic ObjectP190 has symbolic content: E62 String
|
|
10 CIDOC CRM Property Declarations
The properties of the CRM are comprehensively declared in this section using the following format: - Property names are presented as headings in bold face, preceded by unique property identifiers;
- The line “Domain:” declares the class for which the property is defined;
- The line “Range:” declares the class to which the property points, or that provides the values for the property;
- The line “Superproperty of:” is a cross-reference to any subproperties the property may have;
- The line “Quantification:” declares the possible number of occurrences for domain and range class instances for the property. Possible values are: 1:many, many:many, many:1;
- The line “Scope note:” contains the textual definition of the concept the property represents;
- The line “Examples:” contains a bulleted list of examples of instances of this property. If the example is also instance of a subproperty of this property, the unique identifier of the subclass is added in parenthesis. If the example instantiates two properties, the unique identifiers of both properties is added in parenthesis.
- The line “Examples:” provides illustrative examples showing how the property should be used.
|
6 CIDOC CRM Property Declarations
The properties of the CIDOC CRM are comprehensively declared in this section using the following format: - Property names are presented as headings in bold face, preceded by unique property identifiers;
- The line “Domain:” declares the class for which the property is defined;
- The line “Range:” declares the class to which the property points, or that provides the values for the property;
- The line “Superproperty of:” is a cross-reference to any subproperties the property may have;
- The line “Quantification:” declares the possible number of occurrences for domain and range class instances for the property. Possible values are: 1:many, many:many, many:1;
- The line “Scope note:” contains the textual definition of the concept the property represents;
- The line “Examples:” contains a bulleted list of examples of instances of this property. If the example is also instance of a subproperty of this property, the unique identifier of the subclass is added in parenthesis. If the example instantiates two properties, the unique identifiers of both properties is added in parenthesis.
- The line “Examples:” provides illustrative examples showing how the property should be used.
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 IdentifierE52 Time-Span. P78 is identified by (identifies): E49 Time AppellationE53 Place. P87 is identified by (identifies): E44 Place AppellationE71 Man-Made Thing. P102 has title (is title of): E35 TitleE39 Actor. P131 is identified by (identifies): E82 Actor AppellationE28 Conceptual Object. P149 is identified by (identifies): E75 Conceptual Object Appellation
|
Superproperty of:
E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 IdentifierE71 Human-Made Thing. P102 has title (is title of): E35 TitleE53 Place. P168 place is defined by (defines place): E94 Space Primitive
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
|
Scope Note:
This property describes the naming or identification of any real-world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e., indirect) path through E15 Identifier Assignment. This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned to E42 Identifier. It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form to E41 Appellation.
|
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
|
Examples:
- The capital of Italy (E53) is identified by “Rome” (E41). (Leach, 2017)
- Text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35). (Gibbon, 2013)
|
First order logic:
|
First order logic:
- P1(x,y) ⇒ E1(x)
- P1(x,y) ⇒ E41(y)
- P1(x,y) ⇐ (∃z) [E15(z)˄ P140i(x,z) ˄ P37(z,y)]
- P1(x,y) ⇐ (∃z) [E41(z)˄ P1(x,z) ˄ P139(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E1 CRM Entity. P137 exemplifies ( is exemplified by ): E55 Type
|
Superproperty of:
E1 CRM Entity. P137 exemplifies (is exemplified by): E55 TypeE13 Attribute Assignment. P177 assigned property of type (is type of property assigned): E55 Type
|
Quantification:
|
Quantification:
|
Scope Note:
This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question.
|
Scope Note:
This property allows sub typing of CIDOC CRM entities –a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CIDOC CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CIDOC CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E41 Appellation, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CIDOC CRM hierarchy. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document. This property is a shortcut for the path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned to E55 Type.
|
Examples:
- “enquiries@cidoc-crm.org” (E51) has type e-mail address (E55)
|
Examples:
- “enquiries@cidoc-crm.org” (E41) has type e-mail address (E55). (fictitious)
|
First order logic:
|
First order logic:
- P2(x,y) ⇒ E1(x)
- P2(x,y) ⇒ E55(y)
- P2(x,y) ⇐ (∃z) [E17(z)] ˄ P41i(x,z) ˄ P42(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E52 Time-Span. P79 beginning is qualified by: E62 StringE52 Time-Span. P80 end is qualified by: E62 String
|
Superproperty of:
E52 Time-Span. P79 beginning is qualified by: E62 StringE52 Time-Span. P80 end is qualified by: E62 StringE90 Symbolic Object. P190 has symbolic content: E62 String
|
Quantification:
|
Quantification:
|
Scope Note:
This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. “construction”, “decoration” etc. An item may have many notes, but a note is attached to a specific item.
|
Scope Note:
This property is a container for all informal descriptions about an object that have not been expressed in terms of CIDOC CRM constructs. In particular, it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CIDOC CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CIDOC CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g., “construction”, “decoration” etc. An item may have many notes, but a note is attached to a specific item.
|
Examples:
- coffee mug – OXCMS:1983.1.1 (E19) has note “chipped at edge of handle” (E62) has type Condition (E55)
|
Examples:
- Coffee mug – OXCMS:1983.1.1 (E19) has note “chipped at edge of handle” (E62) has type Condition (E55). (fictitious)
|
First order logic:
|
First order logic:
- P3(x,y) ⇒ E1(x)
- P3(x,y) ⇒ E62(y)
- P3(x,y,z) ⇒ [P3(x,y) ∧ E55(z)]
|
Properties:
|
Properties:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to one, necessary, dependent (1,1:1,n)
|
Quantification:
many to one, necessary (1,1:0,n)
|
Scope Note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity. The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active, which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span, but there may exist alternative opinions about it, which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
|
Scope Note:
This property associates an instance of E2 Temporal Entity with the instance of E52 Time-Span during which it was on-going. The associated instance of E52 Time-Span is understood as the real time-span during which the phenomena making up the temporal entity instance were active. More than one instance of E2 Temporal Entity may share a common instance of E52 Time-Span only if they come into being and end being due to identical declarations or events.
|
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
|
Examples:
- The Yalta Conference (E7) has time-span Yalta Conference time-span (E52). (Harbutt, 2010)
|
First order logic:
|
First order logic:
- P4(x,y) ⇒ E2(x)
- P4(x,y) ⇒ E52(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the decomposition of an E3 Condition State into discrete, subsidiary states. It is assumed that the sub-states into which the condition state is analysed form a logical whole - although the entire story may not be completely known – and that the sub-states are in fact constitutive of the general condition state. For example, a general condition state of “in ruins” may be decomposed into the individual stages of decay.
|
Scope Note:
This property describes the decomposition of an instance of E3 Condition State into discrete, subsidiary states. It is assumed that the sub-states into which the condition state is analysed form a logical whole - although the entire story may not be completely known – and that the sub-states are in fact constitutive of the general condition state. For example, a general condition state of “in ruins” may be decomposed into the individual stages of decay. This property is transitive and non-reflexive.
|
Examples:
- The Condition State of the ruined Parthenon (E3) consists of the bombarded state after the explosion of a Venetian shell in 1687 (E3) [The Venetians in Athens and the Destruction of the Parthenon in 1687,·Theodor E. Mommsen, American Journal of Archaeology, Vol. 45, No. 4 (Oct. - Dec., 1941), pp. 544-5]
|
Examples:
- The Condition State of the ruined Parthenon (E3) consists of the bombarded state after the explosion of a Venetian shell in 1687 (E3). (Mommsen, 1941)
|
First order logic:
|
First order logic:
- P5(x,y) ⇒ E3(x)
- P5(x,y) ⇒ E3(y)
- [P5(x,y) ∧ P5(y,z)] ⇒ P5(x,z)
- P5(x,y) ⇒ ¬P5(y,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E9 Move. P26 moved to (was destination of): E53 PlaceE9 Move. P27 moved from (was origin of): E53 Place
|
Superproperty of:
E92 Spacetime Volume. P161 has spatial projection (is spatial projection of): E53 Place
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France”, the “Victorian” period, may be said to have taken place in “Britain” and its colonies, as well as other parts of Europe and north America. A period can take place at multiple locations.
|
Scope Note:
This property describes the spatial location of an instance of E4 Period. The related instance of E53 Place should be seen as a wider approximation of the geometric area within which the phenomena that characterise the period in question occurred, see below. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (frequently on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France in 1789”; the “Victorian” period may be said to have taken place in “Britain from 1837-1901” and its colonies, as well as other parts of Europe and North America. An instance of E4 Period can take place at multiple non-contiguous, non-overlapping locations. This property is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place. E4 Period is a subclass of E92 Spacetime Volume. By the definition of P161 has spatial projection an instance of E4 Period takes place on all its spatial projections, that is, instances of E53 Place. Something happening at a given place can also be considered to happen at a larger place containing the first. For example, the assault on the Bastille July 14th 1789 took place in the area covered by Paris in 1789 but also in the area covered by France in 1789.
|
Examples:
- the period “Révolution française” (E4) took place at France (E53)
|
Examples:
- The period “Révolution française” (E4) took place at the area covered by France in 1789 (E53). (Bertaud, 2004)
|
First order logic:
|
First order logic:
- P7(x,y) ⇒ E4(x)
- P7(x,y) ⇒ E53(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the location of an instance of E4 Period with respect to an E19 Physical Object. P8 took place on or within (witnessed) is a short-cut of a path defining a E53 Place with respect to the geometry of an object. cf. E46 Section Definition. This property is in effect a special case of P7 took place at. It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. For example, the French and German armistice of 22 June 1940 was signed in the same railway carriage as the armistice of 11 November 1918.
|
Scope Note:
This property describes the location of an instance of E4 Period with respect to an instance of E19 Physical Object. This property is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156i is occupied by E18 Physical Thing. It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. For example, the French and German armistice of 22 June 1940 was signed in the same railway carriage as the armistice of 11 November 1918.
|
Examples:
- the coronation of Queen Elizabeth II (E7) took place on or within Westminster Abbey (E19)
|
Examples:
- The coronation of Queen Elizabeth II (E7) took place on or within Westminster Abbey (E18). (Strong, 2005)
|
First order logic:
|
First order logic:
- P8(x,y) ⇒ E4(x)
- P8(x,y) ⇒ E18(y)
- P8(x,y) ⇐ (∃z) [E53(z) ˄ P7(x,z) ˄ P156i(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
|
Subproperty of:
E92 Spacetime Volume. P10i contains (falls within): E92 Spacetime Volume
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the decomposition of an instance of E4 Period into discrete, subsidiary periods. The sub-periods into which the period is decomposed form a logical whole - although the entire picture may not be completely known - and the sub-periods are constitutive of the general period.
|
Scope Note:
This property associates an instance of E4 Period with another instance of E4 Period that is defined by a subset of the phenomena that define the former. Therefore, the spacetime volume of the latter must fall within the spacetime volume of the former. This property is transitive and non-symmetric.
|
Examples:
- Cretan Bronze Age (E4) consists of Middle Minoan (E4)
|
Examples:
- Cretan Bronze Age (E4) consists of Middle Minoan (E4). (Hood, 1971)
|
First order logic:
|
First order logic:
- P9(x,y) ⇒ E4(x)
- P9(x,y) ⇒ E4(y)
- P9(x,y) ⇒ P10(y,x)
- [P9(x,y) ∧ P9(y,z)] ⇒ P9(x,z)
- P9(x,y) ⇒ ¬P9(y,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
|
Superproperty of:
E93 Presence. P166 was a presence of (had presence): E92 Spacetime Volume
|
Subproperty of:
|
Subproperty of:
E92 Spacetime Volume. P132 spatiotemporally overlaps with: E92 Spacetime Volume
|
Quantification:
|
Quantification:
many to many, necessary, dependent (1,n:0,n)
|
Scope Note:
This property describes an instance of E4 Period, which falls within the E53 Place and E52 Time-Span of another. The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of), P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different type.
|
Scope Note:
This property associates an instance of E92 Spacetime Volume with another instance of E92 Spacetime Volume that falls within the latter. In other words, all points in the former are also points in the latter. This property is transitive and reflexive.
|
Examples:
- the Great Plague (E4) falls within The Gothic period (E4)
|
Examples:
- The Great Plague (E4) falls within The Gothic period (E4). (Porter, 2009)
|
First order logic:
|
First order logic:
- P10(x,y) ⇒ E92(x)
- P10(x,y) ⇒ E92(y)
- P10(x,y) ⇒ P132(x,y)
- P10(x,y) ∧ P10(y,z)] ⇒ P10(x,z)
- P10(x,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E7 Activity. P14 carried out by (performed): E39 ActorE67 Birth. P96 by mother (gave birth): E21 PersonE68 Dissolution. P99 dissolved (was dissolved by): E74 GroupE85 Joining. P143 joined (was joined by): E39 ActorE85 Joining. P144 joined with (gained member by): E74 GroupE86 Leaving. P145 separated (left by): E39 ActorE86 Leaving. P146 separated from (lost member by): E74 Group
|
Superproperty of:
E7 Activity. P14 carried out by (performed): E39 ActorE67 Birth. P96 by mother (gave birth): E21 PersonE68 Dissolution. P99 dissolved (was dissolved by): E74 GroupE85 Joining. P143 joined (was joined by): E39 ActorE85 Joining. P144 joined with (gained member by): E74 GroupE86 Leaving. P145 separated (left by): E39 ActorE86 Leaving. P146 separated from (lost member by): E74 GroupE66 Formation. P151 was formed from (participated in): E74 Group
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the active or passive participation of instances of E39 Actors in an E5 Event. It connects the life-line of the related E39 Actor with the E53 Place and E50 Date of the event. The property implies that the Actor was involved in the event but does not imply any causal relationship. The subject of a portrait can be said to have participated in the creation of the portrait.
|
Scope Note:
This property describes the active or passive participation of instances of E39 Actors in an instance of E5 Event. It documents known events in which an instance of E39 Actor has participated during the course of that actor’s life or history. The instances of E53 Place and E52 Time-Span where and when these events happened provide us with constraints about the presence of the related instances of E39 Actor in the past. Collective actors, i.e., instances of E74 Group, may physically participate in events via their representing instances of E21 Persons only. The participation of multiple actors in an event is most likely an indication of their acquaintance and interaction. The property implies that the actor was involved in the event but does not imply any causal relationship. For instance, someone having been portrayed can be said to have participated in the creation of the portrait.
|
Examples:
- Napoleon (E21) participated in The Battle of Waterloo (E7)
- Maria (E21) participated in Photographing of Maria (E7)
|
Examples:
- Napoleon (E21) participated in The Battle of Waterloo (E7). (Dawson, 2018)
- Maria (E21) participated in Photographing of Maria (E7). (fictitious)
|
First order logic:
|
First order logic:
- P11(x,y) ⇒ E5(x)
- P11(x,y) ⇒ E39(y)
- P11(x,y) ⇒ P12(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E5 Event. P11 had participant (participated in): E39 ActorE7 Activity. P16 used specific object (was used for): E70 ThingE9 Move. P25 moved (moved by): E19 Physical ObjectE11 Modification. P31 has modified (was modified by): E24 Physical Man-Made ThingE63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent ItemE64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent ItemE79 Part Addition. P111 added (was added by): E18 Physical ThingE80 Part Removal. P113 removed (was removed by): E18 Physical Thing
|
Superproperty of:
E5 Event. P11 had participant (participated in): E39 ActorE7 Activity. P16 used specific object (was used for): E70 ThingE9 Move. P25 moved (moved by): E19 Physical ObjectE11 Modification. P31 has modified (was modified by): E18 Physical ThingE63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent ItemE64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent ItemE80 Part Removal. P113 removed (was removed by): E18 Physical Thing
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role. It connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers.
|
Scope Note:
This property describes the active or passive presence of an E77 Persistent Item in an instance of E5 Event without implying any specific role. It documents known events in which an instance of E77 Persistent Item was present during the course of its life or history. For example, an object may be the desk, now in a museum, on which a treaty was signed. The instance of E53 Place and the instance of E52 Time-Span where and when these events happened provide us with constraints about the presence of the related instance E77 Persistent Item in the past. Instances of E90 Symbolic Object, in particular information objects, are physically present in events via at least one of the instances of E18 Physical Thing carrying them. Note, that the human mind can be such a carrier. A precondition for a transfer of information to a person or another new physical carrier is the presence of the respective information object and this person or physical thing in one event.
|
Examples:
- Deckchair 42 (E19) was present at The sinking of the Titanic (E5)
|
Examples:
- Deckchair 42 (E19) was present at the sinking of the Titanic (E5). (Aldridge, 2008)
|
First order logic:
|
First order logic:
- P12(x,y) ⇒ E5(x)
- P12(x,y) ⇒ E77(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Subproperty of:
E64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Quantification:
one to many, necessary (1,n:0,1)
|
Quantification:
one to many, necessary (1,n:0,1)
|
Scope Note:
This property allows specific instances of E18 Physical Thing that have been destroyed to be related to a destruction event. Destruction implies the end of an item’s life as a subject of cultural documentation – the physical matter of which the item was composed may in fact continue to exist. A destruction event may be contiguous with a Production that brings into existence a derived object composed partly of matter from the destroyed object.
|
Scope Note:
This property links an instance of E6 Destruction to an instance of E18 Physical Thing that has been destroyed by it. Destruction implies the end of an item’s life as a subject of cultural documentation – the physical matter of which the item was composed may in fact continue to exist. An instance of E6 Destruction may be contiguous with an instance of E12 Production that brings into existence a derived object composed partly of matter from the destroyed object.
|
Examples:
- the Tay Bridge Disaster (E6) destroyed The Tay Bridge (E22)
|
Examples:
- The Tay Bridge Disaster (E6) destroyed The Tay Bridge (E22). (Thomas, 1972)
|
First order logic:
|
First order logic:
- P13(x,y) ⇒ E6 (x)
- P13(x,y) ⇒ E18(y)
- P13(x,y) ⇒ P93(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E8 Acquisition. P22 transferred title to (acquired title through): E39 ActorE8 Acquisition. P23 transferred title from (surrendered title through): E39 ActorE10 Transfer of Custody. P28 custody surrendered by (surrendered custody through): E39 ActorE10 Transfer of Custody. P29 custody received by (received custody through): E39 Actor
|
Superproperty of:
E8 Acquisition. P22 transferred title to (acquired title through): E39 ActorE8 Acquisition. P23 transferred title from (surrendered title through): E39 ActorE10 Transfer of Custody. P28 custody surrendered by (surrendered custody through): E39 ActorE10 Transfer of Custody. P29 custody received by (received custody through): E39 Actor
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property describes the active participation of an E39 Actor in an E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property allows the nature of an Actor’s participation to be specified.
|
Scope Note:
This property describes the active participation of an instance of E39 Actor in an instance of E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property specifies the nature of an Actor’s participation.
|
Examples:
- the painting of the Sistine Chapel (E7) carried out by Michaelangelo Buonaroti (E21) in the role of master craftsman (E55)
|
Examples:
- The painting of the Sistine Chapel (E7) carried out by Michaelangelo Buonaroti (E21) in the role of master craftsman (E55). (Goldscheider, 1953)
|
First order logic:
|
First order logic:
- P14(x,y) ⇒ E7(x)
- P14(x,y)⇒ E39(y)
- P14(x,y) ⇒ P11(x,y)
- P14(x,y,z) ⇒ [P14(x,y) ∧ E55(z)]
|
Properties:
P14.1 in the role of: E55 Type
|
Properties:
P14.1 in the role of: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E7 Activity. P16 used specific object (was used for): E70 ThingE7 Activity. P17 was motivated by (motivated): E1 CRM EntityE7 Activity. P134 continued (was continued by): E7 ActivityE83 Type Creation. P136 was based on (supported type creation): E1 CRM Entity
|
Superproperty of:
E7 Activity. P16 used specific object (was used for): E70 ThingE7 Activity. P17 was motivated by (motivated): E1 CRM EntityE7 Activity. P134 continued (was continued by): E7 ActivityE83 Type Creation. P136 was based on (supported type creation): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties.
|
Scope Note:
This is a high-level property, which captures the relationship between an instance of E7 Activity and anything, that is, an instance of E1 CRM Entity that may have had some bearing upon it. The property has more specific sub properties.
|
Examples:
- the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22)
|
Examples:
- The designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22). (Dorman Long, 1932)
|
First order logic:
|
First order logic:
- P15(x,y) ⇒ E7(x)
- P15(x,y) ⇒ E1(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E7 Activity. P33 used specific technique (was used by): E29 Design or ProcedureE79 Part Addition. P111 added (was added by): E18 Physical ThingE15 Identifier Assignment. P142 used constituent (was used in): E41 Appellation
|
Superproperty of:
E7 Activity. P33 used specific technique (was used by): E29 Design or ProcedureE79 Part Addition. P111 added (was added by): E18 Physical ThingE15 Identifier Assignment. P142 used constituent (was used in): E90 Symbolic Object
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent ItemE7 Activity. P15 was influenced by (influenced): E1 CRM Entity
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent ItemE7 Activity. P15 was influenced by (influenced): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.
|
Scope Note:
This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an instance of E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.
|
Examples:
- the writing of this scope note (E7) used specific object Nicholas Crofts’ computer (E22) mode of use Typing Tool; Storage Medium (E55)
- the people of Iraq calling the place identified by TGN ‘7017998’ (E7) used specific object “Quyunjig” (E44) mode of use Current; Vernacular (E55)
|
Examples:
- The writing of the scope note of the CIDOC CRM property “P16 used specific object” contained in the CIDOC CRM version 4.1 (E7) used specific object Nicholas Crofts’ computer (E22) mode of use Typing Tool; Storage Medium (E55). [the original scope note was later extended in the CIDOC CRM version 4.3]
- The people of Iraq calling the place identified by TGN ‘7017998’ (E7) used specific object “Quyunjig” (E41) mode of use current; vernacular (E55).
|
First order logic:
|
First order logic:
- P16(x,y) ⇒ E7(x)
- P16(x,y) ⇒ E70(y)
- P16(x,y) ⇒ P12(x,y)
- P16(x,y) ⇒ P15(x,y)
- P16(x,y,z) ⇒ [P16(x,y) ∧ E55(z)]
|
Properties:
P16.1 mode of use: E55 Type
|
Properties:
P16.1 mode of use: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P15 was influenced by (influenced): E1 CRM Entity
|
Subproperty of:
E7 Activity. P15 was influenced by (influenced): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes an item or items that are regarded as a reason for carrying out the E7 Activity. For example, the discovery of a large hoard of treasure may call for a celebration, an order from head quarters can start a military manoeuvre.
|
Scope Note:
This property describes an item or items that are regarded as a reason for carrying out the instance of E7 Activity. For example, the discovery of a large hoard of treasure may call for a celebration, an order from headquarters can start a military manoeuvre.
|
Examples:
- the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
- the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)
|
Examples:
- The resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
- The coronation of Elizabeth II (E7) was motivated by the death of George VI (E69). (Strong, 2005)
|
First order logic:
|
First order logic:
- P17(x,y) ⇒ E7(x)
- P17(x,y) ⇒ E1(y)
- P17(x,y) ⇒ P15(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property relates an E7 Activity with objects created specifically for use in the activity. This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)).
|
Scope Note:
This property relates an instance of E7 Activity with instances of E71 Human-Made Thing, created specifically for use in the activity. This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)).
|
Examples:
- Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)
|
Examples:
- Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55). (Daly, 1981)
|
First order logic:
|
First order logic:
- P19(x,y) ⇒ E7(x)
- P19(x,y) ⇒ E71(y)
- P19(x,y,z) ⇒ [P19(x,y) ∧ E55(z)]
|
Properties:
P19.1 mode of use: E55 Type
|
Properties:
P19.1 mode of use: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the relationship between a preparatory activity and the event it is intended to be preparation for. This includes activities, orders and other organisational actions, taken in preparation for other activities or events. P20 had specific purpose (was purpose of) implies that an activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, one may document the unrealized intention using P21 had general purpose (was purpose of):E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure.
|
Scope Note:
This property identifies the relationship between a preparatory activity, an instance of E7 Activity and the instance of E7 Event it is intended to be preparation for. This includes activities, orders and other organisational actions, taken in preparation for other activities or events. P20 had specific purpose (was purpose of) implies that an activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, one may document the unrealized intention using P21 had general purpose (was purpose of): E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure.
|
Examples:
- Van Eyck’s pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12)
|
Examples:
- Van Eyck’s pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12). (Borchert, 2008)
|
First order logic:
|
First order logic:
- P20(x,y) ⇒ E7(x)
- P20(x,y) ⇒ E5(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes an intentional relationship between an E7 Activity and some general goal or purpose. This may involve activities intended as preparation for some type of activity or event. P21had general purpose (was purpose of) differs from P20 had specific purpose (was purpose of) in that no occurrence of an event is implied as the purpose.
|
Scope Note:
This property describes an intentional relationship between an instance of E7 Activity and some general goal or purpose, described as an instance of E55 Type. This may involve activities intended as preparation for some type of activity or event. P21 had general purpose (was purpose of) differs from P20 had specific purpose (was purpose of) in that no occurrence of an event is implied as the purpose.
|
Examples:
- Van Eyck’s pigment grinding (E7) had general purpose painting (E55)
- The setting of trap 2742 on May 17th 1874 (E7) had general purpose Catching Moose (E55) (Activity type
|
Examples:
- Van Eyck’s pigment grinding (E7) had general purpose painting (E55). (Borchert, 2008)
- The setting of trap 2742 on 17th of May 1874 (E7) had general purpose catching moose (E55). [Activity type] (fictitious)
- The construction of the Berlin Wall starting 13th of August 1961 (E12) had general purpose preventing emigration (E55). (History.com Editors, 2020)
- The reinforcement of the Mexico-United States barrier between the United States of America and Mexico in Fall 2019 (E11) had general purpose preventing immigration (E55).
- The rebuilding of the city walls of Heraklion by the Venetian rulers starting in 1462 (E12) had general purpose preventing conquest by enemy (E55). (YouIngGreece.com, 2020)
- The building of the seawall in Hamamatsu, Shizuoka, Japan between 2014 and 2020 (E12) had general purpose preventing inland flooding by tsunami (E55).
|
First order logic:
|
First order logic:
- P21(x,y) ⇒ E7(x)
- P21(x,y) ⇒ E55(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor that acquires the legal ownership of an object as a result of an E8 Acquisition. The property will typically describe an Actor purchasing or otherwise acquiring an object from another Actor. However, title may also be acquired, without any corresponding loss of title by another Actor, through legal fieldwork such as hunting, shooting or fishing. In reality the title is either transferred to or from someone, or both.
|
Scope Note:
This property identifies the instance of E39 Actor that acquires the legal ownership of an object as a result of an instance of E8 Acquisition. The property will typically describe an Actor purchasing or otherwise acquiring an object from another Actor. However, title may also be acquired, without any corresponding loss of title by another Actor, through legal fieldwork such as hunting, shooting or fishing. In reality the title is either transferred to or from someone, or both.
|
Examples:
- acquisition of the Amoudrouz collection by the Geneva Ethnography Museum (E8) transferred title to Geneva Ethnography Museum (E74)
|
Examples:
- The acquisition of the Amoudrouz collection by the Geneva Ethnography Museum (E8) transferred title to the Geneva Ethnography Museum (E74).
|
First order logic:
|
First order logic:
- P22(x,y) ⇒ E8(x)
- P22(x,y) ⇒ E39(y)
- P22(x,y) ⇒ P14(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor or Actors who relinquish legal ownership as the result of an E8 Acquisition. The property will typically be used to describe a person donating or selling an object to a museum. In reality title is either transferred to or from someone, or both.
|
Scope Note:
This property identifies the instance(s) of E39 Actor who relinquish legal ownership as the result of an instance of E8 Acquisition. The property will typically be used to describe a person donating or selling an object to a museum. In reality title is either transferred to or from someone, or both.
|
Examples:
- acquisition of the Amoudrouz collection by the Geneva Ethnography Museum (E8) transferred title from Heirs of Amoudrouz (E74)
|
Examples:
- The acquisition of the Amoudrouz collection by the Geneva Ethnography Museum (E8) transferred title from the Heirs of Amoudrouz (E74).
|
First order logic:
|
First order logic:
- P23(x,y) ⇒ E8(x)
- P23(x,y) ⇒ E39(y)
- P23(x,y) ⇒ P14(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E18 Physical Thing or things involved in an E8 Acquisition. In reality, an acquisition must refer to at least one transferred item.
|
Scope Note:
This property identifies the instance(s) of E18 Physical Thing involved in an instance of E8 Acquisition. In reality, an acquisition must refer to at least one transferred item.
|
Examples:
- acquisition of the Amoudrouz collection by the Geneva Ethnography Museum (E8) transferred title of Amoudrouz Collection (E78)
|
Examples:
- The acquisition of the Amoudrouz collection by the Geneva Ethnography Museum (E8) transferred title of the Amoudrouz Collection (E78).
|
First order logic:
|
First order logic:
- P24(x,y) ⇒ E8(x)
- P24(x,y) ⇒ E18(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E19 Physical Object that is moved during a move event. The property implies the object’s passive participation. For example, Monet’s painting “Impression sunrise” was moved for the first Impressionist exhibition in 1874. In reality, a move must concern at least one object.
|
Scope Note:
This property identifies an instance of E19 Physical Object that was moved by an instance of E9 Move. A move must concern at least one object. The property implies the object’s passive participation. For example, Monet’s painting “Impression sunrise” was moved for the first Impressionist exhibition in 1874.
|
Examples:
- Monet´s “Impression sunrise” (E22) moved by preparations for the First Impressionist Exhibition (E9)
|
Examples:
- Monet´s “Impression sunrise” (E22) moved by preparations for the First Impressionist Exhibition (E9).
|
First order logic:
|
First order logic:
- P25(x,y) ⇒ E9(x)
- P25(x,y) ⇒ E19(y)
- P25(x,y) ⇒ P12(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E4 Period. P7 took place at (witnessed): E53 Place
|
Subproperty of:
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the destination of a E9 Move. A move will be linked to a destination, such as the move of an artefact from storage to display. A move may be linked to many terminal instances of E53 Places. In this case the move describes a distribution of a set of objects. The area of the move includes the origin, route and destination.
|
Scope Note:
This property identifies a destination, an instance of E53 place, of an instance of E9 Move. A move will be linked to a destination, such as the move of an artifact from storage to display. A move may be linked to many terminal instances of E53 Place by multiple instances of this property. In this case the move describes a distribution of a set of objects. The area of the move includes the origin(s), route and destination(s). Therefore, the described destination is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at.
|
Examples:
- the movement of the Tut-Ankh-Amun Exhibition (E9) moved to The British Museum (E53)
|
Examples:
- The movement of the exhibition "Tutankhamun: Treasures of the Golden Pharaoh" between 15th of September and 2nd of November 2019 (E9) moved to the Saatchi Gallery London (E53).
|
First order logic:
|
First order logic:
- P26(x,y) ⇒ E9(x)
- P26(x,y) ⇒ E53(y)
- P26(x,y) ⇒ (∃z)[ E53(z) ∧ P7(x,z) ∧ P89(y,z)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E4 Period. P7 took place at (witnessed): E53 Place
|
Subproperty of:
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the starting E53 Place of an E9 Move. A move will be linked to an origin, such as the move of an artefact from storage to display. A move may be linked to many origins. In this case the move describes the picking up of a set of objects. The area of the move includes the origin, route and destination.
|
Scope Note:
This property identifies an origin, an instance of E53 Place, of an instance of E9 Move. A move will be linked to an origin, such as the move of an artifact from storage to display. A move may be linked to many starting instances of E53 Place by multiple instances of this property. In this case the move describes the picking up of a set of objects. The area of the move includes the origin(s), route and destination(s). Therefore, the described origin is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at.
|
Examples:
- the movement of the Tut-Ankh-Amun Exhibition (E9) moved from The Egyptian Museum in Cairo (E53)
|
Examples:
- The movement of the exhibition "Tutankhamun: Treasures of the Golden Pharaoh" between 15th of September and 2nd of November 2019 (E9) moved from Paris, Grande Halle de la Villette (E53).
|
First order logic:
|
First order logic:
- P27(x,y) ⇒ E9(x)
- P27(x,y) ⇒ E53(y)
- P27(x,y) ⇒ (∃z)[ E53(z) ∧ P7(x,z) ∧ P89(y,z)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor or Actors who surrender custody of an instance of E18 Physical Thing in an E10 Transfer of Custody activity. The property will typically describe an Actor surrendering custody of an object when it is handed over to someone else’s care. On occasion, physical custody may be surrendered involuntarily – through accident, loss or theft. In reality, custody is either transferred to someone or from someone, or both.
|
Scope Note:
This property identifies the instance(s) of E39 Actor who surrender custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe an Actor surrendering custody of an object when it is handed over to someone else’s care. On occasion, physical custody may be surrendered involuntarily – through accident, loss or theft. In reality, custody is either transferred to someone or from someone, or both.
|
Examples:
- the Secure Deliveries Inc. crew (E40) surrendered custody through The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10).
|
Examples:
- The Secure Deliveries Inc. crew (E74) surrendered custody through The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10).
|
First order logic:
|
First order logic:
- P28(x,y) ⇒ E10(x)
- P28(x,y) ⇒ E39(y)
- P28(x,y) ⇒ P14(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Subproperty of:
E7 Activity. P14 carried out by (performed): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor or Actors who receive custody of an instance of E18 Physical Thing in an E10 Transfer of Custody activity. The property will typically describe Actors receiving custody of an object when it is handed over from another Actor’s care. On occasion, physical custody may be received involuntarily or illegally – through accident, unsolicited donation, or theft. In reality, custody is either transferred to someone or from someone, or both.
|
Scope Note:
This property identifies the instance(s) E39 Actor who receive custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe Actors receiving custody of an object when it is handed over from another Actor’s care. On occasion, physical custody may be received involuntarily or illegally – through accident, unsolicited donation, or theft. In reality, custody is either transferred to someone or from someone, or both.
|
Examples:
- representatives of The National Gallery (E40) received custody through. The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10)
|
Examples:
- Representatives of The National Gallery (E74) received custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10).
|
First order logic:
|
First order logic:
- P29(x,y) ⇒ E10(x)
- P29(x,y) ⇒ E39(y)
- P29(x,y) ⇒ P14(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies an item or items of E18 Physical Thing concerned in an E10 Transfer of Custody activity. The property will typically describe the object that is handed over by an E39 Actor to another Actor’s custody. On occasion, physical custody may be transferred involuntarily or illegally – through accident, unsolicited donation, or theft.
|
Scope Note:
This property identifies the instance(s) of E18 Physical Thing concerned in an instance of E10 Transfer of Custody. The property will typically describe the object that is handed over by an instance of E39 Actor to to the custody of another instance of E39 Actor. On occasion, physical custody may be transferred involuntarily or illegally – through accident, unsolicited donation, or theft.
|
Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10) transferred custody of paintings from The Iveagh Bequest (E19)
|
Examples:
- The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10) transferred custody of paintings from The Iveagh Bequest (E19).
|
First order logic:
|
First order logic:
- P30(x,y) ⇒ E10(x)
- P30(x,y) ⇒ E18(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
E24 Physical Man-Made Thing
|
Range:
|
Superproperty of:
E12 Production. P108 has produced (was produced by): E24 Physical Man-Made ThingE79 Part Addition. P110 augmented (was augmented by): E24 Physical Man-Made ThingE80 Part Removal. P112 diminished (was diminished by): E24 Physical Man-Made Thing
|
Superproperty of:
E12 Production. P108 has produced (was produced by): E24 Physical Human-Made ThingE79 Part Addition. P110 augmented (was augmented by): E24 Physical Human-Made ThingE80 Part Removal. P112 diminished (was diminished by): E24 Physical Human-Made Thing
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E24 Physical Man-Made Thing modified in an E11 Modification. If a modification is applied to a non-man-made object, it is regarded as an E22 Man-Made Object from that time onwards.
|
Scope Note:
This property identifies the instance of E18 Physical Thing modified in an instance of E11 Modification.
|
Examples:
- rebuilding of the Reichstag (E11) has modified the Reichstag in Berlin (E24)
|
Examples:
- The rebuilding of the German Reichstag in Berlin (E11) has modified the Reichstag in Berlin (E24). (Foster, 2000)
|
First order logic:
|
First order logic:
- P31(x,y) ⇒ E11(x)
- P31(x,y) ⇒ E18(y)
- P31(x,y) ⇒ P12(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P125 used object of type (was type of object used in): E55 Type
|
Subproperty of:
E7 Activity. P125 used object of type (was type of object used in): E55 Type
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the technique that was employed in an act of modification. These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques such as embroidery, oil-painting, etc. Specific techniques may be further described as instances of E29 Design or Procedure.
|
Scope Note:
This property identifies the technique or method, modelled as an instance of E55 Type, that was employed in an instance of E7 Activity. These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques or methods such as embroidery, oil-painting, carbon dating, etc. Specific documented techniques should be described as instances of E29 Design or Procedure.
|
Examples:
- ornamentation of silver cup 113 (E11) used general technique gold-plating (E55) (Design or Procedure Type)
|
Examples:
- The ornamentation of silver cup 113 (E11) used general technique gold-plating (E55). [A Design or Procedure type] (fictitious)
|
First order logic:
|
First order logic:
- P32(x,y) ⇒ E7(x)
- P32(x,y) ⇒ E55(y)
- P32(x,y) ⇒ P125(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P16 used specific object (was used for): E70 Thing
|
Subproperty of:
E7 Activity. P16 used specific object (was used for): E70 Thing
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. Typical examples would include intervention plans for conservation or the construction plans of a building
|
Scope Note:
This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. Typical examples would include intervention plans for conservation or the construction plans of a building.
|
Examples:
- Ornamentation of silver cup 232 (E11) used specific technique ‘Instructions for golden chase work by A N Other’ (E29)
- Rebuilding of Reichstag (E11) used specific technique Architectural plans by Foster and Partners (E29)
|
Examples:
- The ornamentation of silver cup 232 (E11) used specific technique ‘Instructions for golden chase work by A N Other’ (E29). (fictitious)
- The rebuilding of the German Reichstag in Berlin (E11) used specific technique Architectural plans by Foster and Partners (E29). (Foster, 2000)
|
First order logic:
|
First order logic:
- P33(x,y) ⇒ E7(x)
- P33(x,y) ⇒ E29(y)
- P33(x,y) ⇒ P16(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E18 Physical Thing that was assessed during an E14 Condition Assessment activity. Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the E18 Physical Thing does not need to be present or extant.
|
Scope Note:
This property identifies the instance of E18 Physical Thing that was assessed during an instance of E14 Condition Assessment activity. Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the instance of E18 Physical Thing does not need to be present or extant at the time of assessment.
|
Examples:
- 1997 condition assessment of the silver collection (E14) concerned silver cup 232 (E22)
|
Examples:
- The condition assessment of the silver collection in 1997 (E14) concerned silver cup 232 (E22). (fictitious)
- The condition assessment of the cover of MS Sinai Greek 418 (E14) concerned the cover of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) concerned the endband cores of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)
|
First order logic:
|
First order logic:
- P34(x,y) ⇒ E14(x)
- P34(x,y) ⇒ E18(y)
- P34(x,y) ⇒ P140(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E3 Condition State that was observed in an E14 Condition Assessment activity.
|
Scope Note:
This property identifies the instance of E3 Condition State that was observed in an instance of E14 Condition Assessment activity.
|
Examples:
- 1997 condition assessment of silver cup 232 (E14) has identified oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
|
Examples:
- The condition assessment of silver cup 232 in 1997 (E14) has identified oxidation traces were present in 1997 (E3). [which has type (P2) with oxidation traces (E55)] (fictitious)
- The condition assessment of the cover of MS Sinai Greek 418 (E13) has identified the condition state in November 2003 (E3). [which has type fine (E55)] (Honey and Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) has identified the condition state in November 2003 (E3). [which has type broken (E55)] (Honey and Pickwoad, 2010)
|
First order logic:
|
First order logic:
- P35(x,y) ⇒E14(x)
- P35(x,y) ⇒ E3(y)
- P35(x,y) ⇒ P141(x,y)
|
|
|
|
Domain:
E15 Identifier Assignment
|
Domain:
E15 Identifier Assignment
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property records the identifier that was assigned to an item in an Identifier Assignment activity. The same identifier may be assigned on more than one occasion. An Identifier might be created prior to an assignment.
|
Scope Note:
This property records the identifier that was assigned to an item in an instance of P37 Identifier Assignment. The same identifier may be assigned on more than one occasion. An Identifier might be created prior to an assignment.
|
Examples:
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned “232” (E42)
|
Examples:
- The identifier assignment on 1st of June 1997 of the silver cup donated by Martin Doerr (E15) assigned “232” (E42) (fictitious)
|
First order logic:
|
First order logic:
- P37(x,y) ⇒ E15(x)
- P37(x,y) ⇒ E42(y)
- P37(x,y) ⇒ P141(x,y)
|
|
|
|
Domain:
E15 Identifier Assignment
|
Domain:
E15 Identifier Assignment
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property records the identifier that was deassigned from an instance of E1 CRM Entity. Deassignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. The same identifier may be deassigned on more than one occasion.
|
Scope Note:
This property records the identifier that was deassigned from an instance of E1 CRM Entity. De-assignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. The same identifier may be deassigned on more than one occasion.
|
Examples:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
|
Examples:
- The identifier assignment on 31st July 2001 of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42). (fictitious)
|
First order logic:
|
First order logic:
- P38(x,y) ⇒ E15(x)
- P38(x,y) ⇒ E42(y)
- P38(x,y) ⇒ P141(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity
|
Quantification:
many to one, necessary (1,1:0,n)
|
Quantification:
many to one, necessary (1,1:0,n)
|
Scope Note:
This property associates an instance of E16 Measurement with the instance of E1 CRM Entity to which it applied. An instance of E1 CRM Entity may be measured more than once. Material and immaterial things and processes may be measured, e.g. the number of words in a text, or the duration of an event.
|
Scope Note:
This property associates an instance of E16 Measurement with the instance of E18 Physical Thing upon which it acted. The instance of E16 Measurement is specific to the measured object. An instance of E18 Physical Thing may be measured more than once with different results, constituting different instances of E16 Measurement.
|
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
|
Examples:
- The measurement of the height of silver cup 232 on 31st of August 1997 (E16) measured silver cup 232 (E22). (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) measured the “Schoeninger Speer II” (E22). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995. See also, E16 Measurement.] (Kouwenhoven, 1997)
|
First order logic:
|
First order logic:
- P39(x,y) ⇒ E16(x)
- P39(x,y) ⇒ E18(y)
- P39(x,y) ⇒ P140(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property records the dimension that was observed in an E16 Measurement Event. E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object. Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant. Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
|
Scope Note:
This property records the dimension that was observed in an E16 Measurement Event. E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object. Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant. Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
|
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
|
Examples:
- The measurement of the height of silver cup 232 on 31st of August 1997 (E16) observed dimension silver cup 232 height (E54). [which has unit mm (E58), has value 224 (E60) ] (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) observed dimension the carbon 14 based temporal distance from 1996 to the growth of the wood of the “Schoeninger Speer II” (E60). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niederachsen, Germany, in 1995. See also: E16 Measurement.] (Kouwenhoven, 1997)
|
First order logic:
|
First order logic:
- P40(x,y) ⇒ E16(x)
- P40(x,y)⇒ E54(y)
- P40(x,y) ⇒ P141(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity
|
Quantification:
many to one, necessary (1,1:0,n)
|
Quantification:
many to one, necessary (1,1:0,n)
|
Scope Note:
This property records the item to which a type was assigned in an E17 Type Assignment activity. Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
|
Scope Note:
This property records the item to which a type was assigned in an E17 Type Assignment activity. Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
|
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
|
Examples:
- The classification of silver cup 232 on 31st of August 1997 (E17) classified silver cup 232 (E22). (fictitious)
|
First order logic:
|
First order logic:
- P41(x,y) ⇒ E17(x)
- P41(x,y) ⇒ E1(y)
- P41(x,y) ⇒ P140(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Subproperty of:
E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of). For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B. A Type may be intellectually constructed independent from assigning an instance of it.
|
Scope Note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of). For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B. A Type may be intellectually constructed independent from assigning an instance of it.
|
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
|
Examples:
- The classification of silver cup 232 on 31st August 1997 (E17) assigned goblet (E55). (fictitious)
|
First order logic:
|
First order logic:
- P42(x,y) ⇒ E17(x)
- P42(x,y)⇒ E55(y)
- P42(x,y) ⇒ P141(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
one to many, dependent (0,n:1.1)
|
Quantification:
one to many, dependent (0,n:1,1)
|
Scope Note:
This property records a E54 Dimension of some E70 Thing. It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. An instance of E54 Dimension is specific to an instance of E70 Thing.
|
Scope Note:
This property records a E54 Dimension of some E70 Thing. In the case that the recorded property is a result of a measurement of an instance of E18 Physical Thing, this property is a shortcut of the more fully developed path from E18 Physical Thing through P39i was measured by, E16 Measurement, P40 observed dimension to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. Knowledge about an instance of E54 Dimension need not be the result of a measurement; it may be the result of evaluating data or other information, which should be documented as an instance of E13 Attribute Assignment. An instance of E54 Dimension is specific to an instance of E70 Thing.
|
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
|
Examples:
- Silver cup 232 (E22) has dimension height of silver cup 232 (E54). [which has unit (P91) mm (E58), has value (P90) 224 (E60) ] (fictitious)
|
First order logic:
|
First order logic:
- P43(x,y) ⇒ E70(x)
- P43(x,y) ⇒ E54(y)
- P43(x,y) ⇐ (∃z) [E16(z) ˄ P39i(x,z) ˄ P40(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
one to many, dependent (0,n:1,1)
|
Quantification:
one to many, dependent (0,n:1,1)
|
Scope Note:
This property records an E3 Condition State for some E18 Physical Thing. It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom. An instance of Condition State is specific to an instance of Physical Thing.
|
Scope Note:
This property records an E3 Condition State for some E18 Physical Thing. This property is a shortcut of the more fully developed path from E18 Physical Thing through P34i was assessed by, E14 Condition Assessment, P35 has identified to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom. An instance of Condition State is specific to an instance of E18 Physical Thing.
|
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
|
Examples:
- Silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3). [which has type (P2) oxidation traces (E55)] (fictitious)
|
First order logic:
|
First order logic:
- P44(x,y) ⇒ E18(x)
- P44(x,y) ⇒ E3(y)
- P44(x,y) ⇐ (∃z) [E14(z) ˄ P34i(x,z) ˄ P35(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material. A Material, such as a theoretical alloy, may not have any physical instances.
|
Scope Note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different materials to be recorded. P45 consists of (is incorporated in) refers here to observed material as opposed to the consumed raw material. A material, such as a theoretical alloy, may not have any physical instances.
|
Examples:
- silver cup 232 (E22) consists of silver (E57)
|
Examples:
- Silver cup 232 (E22) consists of silver (E57). (fictitious)
|
First order logic:
|
First order logic:
- P45(x,y) ⇒ E18(x)
- P45(x,y) ⇒ E57(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E19 Physical Object. P56 bears feature (is found on): E26 Physical Feature
|
Superproperty of:
E19 Physical Object. P56 bears feature (is found on): E26 Physical Feature
|
Quantification:
|
Quantification:
|
Scope Note:
This property allows instances of E18 Physical Thing to be analysed into component elements. Component elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall. This property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property. The instances of E57 Materials of which an item of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in).
|
Scope Note:
This property associates an instance of E18 Physical Thing with another instance of Physical Thing that forms part of it. The spatial extent of the composing part is included in the spatial extent of the whole. Component elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall. This property does not specify when and for how long a component element resided in the respective whole. If a component is not part of a whole from the beginning of existence or until the end of existence of the whole, the classes E79 Part Addition and E90 Part Removal can be used to document when a component became part of a particular whole and/or when it stopped being a part of it. For the time-span of being part of the respective whole, the component is completely contained in the place the whole occupies. This property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property. The instances of E57 Material of which an instance of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in). This property is transitive and non-reflexive
|
Examples:
- the Royal carriage (E22) forms part of the Royal train (E22)
- the “Hog’s Back” (E24) forms part of the “Fosseway” (E24)
|
Examples:
- The Royal carriage (E22) forms part of the Royal train (E22).
- The “Hog’s Back” (E24) forms part of the “Fosseway” (E24).
|
First order logic:
|
First order logic:
- P46(x,y) ⇒ E18(x)
- P46(x,y) ⇒ E18(y)
- P46(x,y) ⇒ P132(x,y)
- [P46(x,y) ∧ P46(y,z)] ⇒ P46(x,z)
- P46(x,y) ⇒ (∃uzw)[E93(u) ∧ P195i (x,u) ∧ E52(z) ∧ P164(u,z) ∧ E93(w) ∧ P195i (w,y) ∧ P164(w,z) ∧ P10(w,u)]
- ¬P46(x,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Quantification:
|
Quantification:
|
Scope Note:
This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property.
|
Scope Note:
This property records the preferred instance of E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CIDOC CRM instance. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable instance of E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property.
|
Examples:
- the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier “OXCMS:2001.1.32” (E42)
|
Examples:
- The pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier “OXCMS:2001.1.32” (E42). (fictitious)
|
First order logic:
|
First order logic:
- P48(x,y) ⇒ E1(x)
- P48(x,y) ⇒ E42(y)
- P48(x,y) ⇒ P1(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E18 Physical Thing. P50 has current keeper (is current keeper of): E39 ActorE78 Collection. P109 has current or former curator (is current or former curator of): E39 Actor
|
Superproperty of:
E18 Physical Thing. P50 has current keeper (is current keeper of): E39 ActorE78 Curated Holding. P109 has current or former curator (is current or former curator of): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at some time. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody received by (received custody through) to E39 Actor.
|
Scope Note:
This property identifies the instance of E39 Actor who has or has had custody of an instance of E18 Physical Thing at some time. This property leaves open the question if parts of this physical thing have been added or removed during the time-spans it has been under the custody of this actor, but it is required that at least a part which can unambiguously be identified as representing the whole has been under this custody for its whole time. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P30i custody transferred through, E10 Transfer of Custody, P28 custody surrendered by or P29 custody received by to E39 Actor.
|
Examples:
- paintings from The Iveagh Bequest (E18) has former or current keeper Secure Deliveries Inc. (E40)
|
Examples:
- The paintings from The Iveagh Bequest (E78) has former or current keeper Secure Deliveries Inc. (E74).
|
First order logic:
|
First order logic:
- P49(x,y) ⇒ E18(x)
- P49(x,y) ⇒ E39(y)
- P49(x,y) ⇐ (∃z) [E10(z) ˄ P30i(x,z) ˄ [P28(z,y) ˅ P29(z,y) ]]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E18 Physical Thing. P49 has former or current keeper (is former or current keeper of): E39 Actor
|
Subproperty of:
E18 Physical Thing. P49 has former or current keeper (is former or current keeper of): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor or Actors who had custody of an instance of E18 Physical Thing at the time this property was recorded. P50 has current keeper (is current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P29 custody received by (received custody through) to E39 Actor.
|
Scope Note:
This property identifies the instance of E39 Actor that had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. This property is a shortcut for the more detailed path from E18 Physical Thing through, P30i custody transferred through, E10 Transfer of Custody, P29 custody received by to E39 Actor, if and only if the custody has not been surrendered by the receiving actor at any later time
|
Examples:
- paintings from The Iveagh Bequest (E18) has current keeper The National Gallery (E40)
|
Examples:
- The paintings from The Iveagh Bequest (E78) has current keeper The National Gallery (E74) (Iveagh Bequest, 1975)
|
First order logic:
|
First order logic:
- P50(x,y) ⇒ E18(x)
- P50(x,y) ⇒ E39(y)
- P50(x,y) ⇒ P49(x,y)
- P50(x,y) ⇐ (∃z) [[E10(z) ˄ P30i(x,z) ˄ P29(z,y) ]
- ˄ ¬ (∃w) [E10(w) ˄ P30i(x,w) ˄ P28(w,y)˄ P182(z,w)]]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E18 Physical Thing. P52 has current owner (is current owner of): E39 Actor
|
Superproperty of:
E18 Physical Thing. P52 has current owner (is current owner of): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor.
|
Scope Note:
This property identifies an instance of E39 Actor that is or had been the legal owner (i.e., title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P24i changed ownership through, E8 Acquisition, P23 transferred title from, or P22 transferred title to to E39 Actor.
|
Examples:
- paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21)
|
Examples:
- The paintings from the Iveagh Bequest (E78) has former or current owner Lord Iveagh (E21). (Bryant, 1990)
|
First order logic:
|
First order logic:
- P51(x,y) ⇒ E18(x)
- P51(x,y) ⇒ E39(y)
- P51(x,y) ⇐ (∃z) [E8(z) ˄ P24i(x,z) ˄ [P23(z,y) ˅ P22(z,y) ]]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E18 Physical Thing. P51 has former or current owner (is former or current owner of): E39 ActorE72 Legal Object. P105 right held by (has right on): E39 Actor
|
Subproperty of:
E18 Physical Thing. P51 has former or current owner (is former or current owner of): E39 ActorE72 Legal Object. P105 right held by (has right on): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E21 Person, E74 Group or E40 Legal Body that was the owner of an instance of E18 Physical Thing at the time this property was recorded. P52 has current owner (is current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P22 transferred title to (acquired title through) to E39 Actor, if and only if this acquisition event is the most recent.
|
Scope Note:
This property identifies the instance of E21 Person or E74 Group that was the owner of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. This property is a shortcut for the more detailed path from E18 Physical Thing through, P24i changed ownership through, E8 Acquisition, P22 transferred title to to E39 Actor, if and only if this acquisition event is the most recent.
|
Examples:
- paintings from the Iveagh Bequest (E18) has current owner «English Heritage» (E40)
|
Examples:
- The paintings from the Iveagh Bequest (E78) has current owner Historic England (E74). [This is still valid 2021 CE. The important collection of Old Master and British portraits was bequeathed to Kenwood by Edward Cecil Guinness, 1st Earl of Iveagh, in 1927.] (Iveagh Bequest, 1975; Bryant, 1990)
|
First order logic:
|
First order logic:
- P52(x,y) ⇒ E18(x)
- P52(x,y) ⇒ E39(y)
- P52(x,y) ⇒ P51(x,y)
- P52(x,y) ⇒ P105(x,y)
- P52(x,y) ⇐ (∃z) [[E8(z) ˄ P24i(x,z) ˄ P22(z,y) ]
- ˄ ¬ (∃w) [E8(w) ˄ P24i(x,w) ˄ P23(w,y)˄ P182(z,w)]]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E19 Physical Object. P55 has current location (currently holds): E53 Place
|
Superproperty of:
E19 Physical Object. P55 has current location (currently holds): E53 PlaceE18 Physical Thing. P156 occupies (is occupied by): E53 Place
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property allows an instance of E53 Place to be associated as the former or current location of an instance of E18 Physical Thing. In the case of E19 Physical Objects, the property does not allow any indication of the Time-Span during which the Physical Object was located at this Place, nor if this is the current location. In the case of immobile objects, the Place would normally correspond to the Place of creation. P53 has former or current location (is former or current location of) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P25 moved (moved by), E9 Move, P26 moved to (was destination of) or P27 moved from (was origin of) to E53 Place.
|
Scope Note:
This property identifies an instance of E53 Place as the former or current location of an instance of E18 Physical Thing. In the case of instances of E19 Physical Object, the property does not allow any indication of the Time-Span during which the instance of E19 Physical Object was located at this instance of E53 Place, nor if this is the current location. In the case of immobile objects, the Place would normally correspond to the Place of creation. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, though, P25i moved by, E9 Move, P26 moved to or P27 moved from to E53 Place.
|
Examples:
- silver cup 232 (E22) has former or current location Display Case 4, Room 23, Museum of Oxford (E53)
|
Examples:
- Silver cup 232 (E22) has former or current location Display Case 4, Room 23, Museum of Oxford (E53) (fictitious)
|
First order logic:
|
First order logic:
- P53(x,y) ⇒ E18(x)
- P53(x,y) ⇒ E53(y)
- P53(x,y) ⇐ (∃z) [E9(z) ˄ P25i(x,z) ˄ [P26(z,y) ˅ P27(z,y)]]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property records the foreseen permanent location of an instance of E19 Physical Object at the time this property was recorded. P54 has current permanent location (is current permanent location of) is similar to P55 has current location (currently holds). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location.
|
Scope Note:
This property records the foreseen permanent location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. P54 has current permanent location (is current permanent location of) is similar to P55 has current location (currently holds). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location.
|
Examples:
- silver cup 232 (E22) has current permanent location Shelf 3.1, Store 2, Museum of Oxford (E53)
|
Examples:
- Silver cup 232 (E22) has current permanent location Shelf 3.1, Store 2, Museum of Oxford (E53). (fictitious)
|
First order logic:
|
First order logic:
- P54(x,y) ⇒ E19(x)
- P54(x,y) ⇒ E53(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E18 Physical Thing. P53 has former or current location (is former or current location of): E53 Place
|
Subproperty of:
E18 Physical Thing. P53 has former or current location (is former or current location of): E53 Place
|
Quantification:
|
Quantification:
|
Scope Note:
This property records the location of an E19 Physical Object at the time the property was recorded. This property is a specialisation of P53 has former or current location (is former or current location of). It indicates that the E53 Place associated with the E19 Physical Object is the current location of the object. The property does not allow any indication of how long the Object has been at the current location. P55 has current location (currently holds) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P25 moved (moved by), E9 Move P26 moved to (was destination of) to E53 Place if and only if this Move is the most recent.
|
Scope Note:
This property records the location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. This property is a specialisation of P53 has former or current location (is former or current location of). It indicates that the instance of E53 Place associated with the instance of E19 Physical Object is the current location of the object. The property does not allow any indication of how long the object has been at the current location. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, through, P25i moved by, E9 Move, P26 moved to to E53 Place if and only if this Move is the most recent.
|
Examples:
- silver cup 232 (E22) has current location Display cabinet 23, Room 4, British Museum (E53)
|
Examples:
- Silver cup 232 (E22) has current location Display Cabinet 23, Room 4, British Museum (E53). (fictitious)
|
First order logic:
|
First order logic:
- P55(x,y) ⇒ E19(x)
- P55(x,y) ⇒ E53(y)
- P55(x,y) ⇒ P53(x,y)
- P55(x,y) ⇐ (∃z) [ [E9(z) ˄ P25i(x,z) ˄ P26(z,y)]
- ˄ ¬ (∃w) [E9(w) ˄ P25i(x,w) ˄ P27(w,y)˄ P182(z,w)]]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E18 Physical Thing. P46 is composed of (forms part of): E18 Physical Thing
|
Subproperty of:
E18 Physical Thing. P46 is composed of (forms part of): E18 Physical Thing
|
Quantification:
one to many, dependent (0,n:1,1)
|
Quantification:
one to many, dependent (0,n:1,1)
|
Scope Note:
This property describes a E26 Physical Feature found on a E19 Physical Object It does not specify the location of the feature on the object. P56 bears feature (is found on) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P59 has section (is located on or within), E53 Place, P53 has former or current location (is former or current location of) to E26 Physical Feature. A Physical Feature can only exist on one object. One object may bear more than one Physical Feature. An E27 Site should be considered as an E26 Physical Feature on the surface of the Earth.
|
Scope Note:
This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears. An instance of E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An instance of E27 Site should be considered as an instance of E26 Physical Feature on the surface of the Earth. An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i is found on the same E19 Physical Object as A. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path E19 Physical Object, through, P59 has section, E53 Place, P53i is former or current location of to E26 Physical Feature.
|
Examples:
- silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26)
|
Examples:
- Silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26) (fictitious)
|
First order logic:
|
First order logic:
- P56(x,y) ⇒E19(x)
- P56(x,y) ⇒ E26(y)
- P56(x,y) ⇒ P46(x,y)
- P56(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property documents the E60 Number of parts of which an instance of E19 Physical Object is composed. This may be used as a method of checking inventory counts with regard to aggregate or collective objects. What constitutes a part or component depends on the context and requirements of the documentation. Normally, the parts documented in this way would not be considered as worthy of individual attention. For a more complete description, objects may be decomposed into their components and constituents using P46 is composed of (forms parts of) and P45 consists of (is incorporated in). This allows each element to be described individually.
|
Scope Note:
This property documents the number of parts, an instance of E60 Number, of which an instance of E19 Physical Object is composed. This may be used as a method of checking inventory counts with regard to aggregate or collective objects. What constitutes a part or component depends on the context and requirements of the documentation. Normally, the parts documented in this way would not be considered as worthy of individual attention. For a more complete description, objects may be decomposed into their components and constituents using P46 is composed of (forms parts of) and P45 consists of (is incorporated in). This allows each element to be described individually.
|
Examples:
- chess set 233 (E22) has number of parts 33 (E60)
|
Examples:
- Chess set 233 (E22) has number of parts 33 (E60). (fictitious)
|
First order logic:
|
First order logic:
- P57(x,y) ⇒ E19(x)
- P57(x,y) ⇒ E60(y)
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
one to many, dependent, (0,n:1,1)
|
Quantification:
|
Scope Note:
This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing.
|
Scope Note:
|
Examples:
- HMS Victory (E22) has section definition “poop deck of HMS Victory” (E46)
|
Examples:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
|
Subproperty of:
E18 Physical Thing. P157i provides reference space for (is at rest relative to): E53 Place
|
Quantification:
|
Quantification:
|
Scope Note:
This property links an area to the instance of E18 Physical Thing upon which it is found. It is typically used when a named E46 Section Definition is not appropriate. E18 Physical Thing may be subdivided into arbitrary regions. P59 has section (is located on or within) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed (i.e. indirect) path from E18 Physical Thing through P58 has section definition (defines section), E46 Section Definition, P87 is identified by (identifies) to E53 Place. A Place can only be located on or within one Physical Object.
|
Scope Note:
This property links an area, i.e., an instance of E53 Place to the instance of E18 Physical Thing upon which it is found. This area may either be identified by a name, or by a geometry in terms of a coordinate system adapted to the shape of the respective instance of E18 Physical Thing. Typically, names identifying sections of physical objects are composed of the name of a kind of part and the name of the object itself, such as "The poop deck of H.M.S. Victory", which is composed of "poop deck" and "H.M.S. Victory".
|
Examples:
- HMS Victory (E22) has section HMS Victory section B347.6 (E53)
|
Examples:
- HMS Victory (E22) has section HMS Victory section B347.6 (E53). (Goodwin, 2015)
|
First order logic:
|
First order logic:
- P59(x,y) ⇒ E18(x)
- P59(x,y) ⇒ E53(y)
|
|
|
|
Domain:
E24 Physical Man-Made Thing
|
Domain:
E24 Physical Human-Made Thing
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies something that is depicted by an instance of E24 Physical Man-Made Thing. This property is a shortcut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined.
|
Scope Note:
This property identifies something that is depicted by an instance of E24 Physical Human-Made Thing. Depicting is meant in the sense that an instance of E24 Physical Human-Made Thing intentionally shows, through its optical qualities or form, a representation of the entity depicted. Photographs are by default regarded as being intentional in this sense. Anything that is designed to change the properties of the depiction, such as an e-book reader, is specifically excluded. The property does not pertain to inscriptions or any other information encoding. This property is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity. P138.1 mode of depiction allows the nature of the depiction to be refined.
|
Examples:
- The painting “La Liberté guidant le peuple” by Eugène Delacroix (E84) depicts the French “July Revolution” of 1830 (E7)
- the 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E24) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55)
|
Examples:
- The painting “La Liberté guidant le peuple” by Eugène Delacroix (E22) depicts the French “July Revolution” of 1830 (E7). (Delacroix, 1982)
- The 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E22) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55).
|
First order logic:
|
First order logic:
- P62(x,y) ⇒ E24(x)
- P62(x,y) ⇒ E1(y)
- P62(x,y,z) ⇒ [P62(x,y) ∧ E55(z)]
- P62(x,y) ⇐ (∃z) [E36(z) ˄ P65(x,z) ˄ P138(z,y)]
|
Properties:
P62.1 mode of depiction: E55 Type
|
Properties:
P62.1 mode of depiction: E55 Type
|
|
|
|
Domain:
E24 Physical Man-Made Thing
|
Domain:
E24 Physical Human-Made Thing
|
Range:
|
Range:
|
Subproperty of:
E24 Physical Man-Made Thing. P128 carries (is carried by): E90 Symbolic Object
|
Subproperty of:
E18 Physical Thing. P128 carries (is carried by): E90 Symbolic Object
|
Quantification:
|
Quantification:
|
Scope Note:
This property documents an E36 Visual Item shown by an instance of E24 Physical Man-Made Thing. This property is similar to P62 depicts (is depicted by) in that it associates an item of E24 Physical Man-Made Thing with a visual representation. However, P65 shows visual item (is shown by) differs from the P62 depicts (is depicted by) property in that it makes no claims about what the E36 Visual Item is deemed to represent. E36 Visual Item identifies a recognisable image or visual symbol, regardless of what this image may or may not represent. For example, all recent British coins bear a portrait of Queen Elizabeth II, a fact that is correctly documented using P62 depicts (is depicted by). Different portraits have been used at different periods, however. P65 shows visual item (is shown by) can be used to refer to a particular portrait. P65 shows visual item (is shown by) may also be used for Visual Items such as signs, marks and symbols, for example the 'Maltese Cross' or the 'copyright symbol’ that have no particular representational content. This property is part of the fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity which is shortcut by, P62 depicts (is depicted by).
|
Scope Note:
This property documents an instance of E36 Visual Item shown by an instance of E24 Physical Human-Made Thing. This property is similar to P62 depicts (is depicted by) in that it associates an instance of E24 Physical Human-Made Thing with a visual representation. However, P65 shows visual item (is shown by) differs from the P62 depicts (is depicted by) property in that it makes no claims about what the instance of E36 Visual Item is deemed to represent. An instance of E36 Visual Item identifies a recognisable image or visual symbol, regardless of what this image may or may not represent. For example, all recent British coins bear a portrait of Queen Elizabeth II, a fact that is correctly documented using P62 depicts (is depicted by). Different portraits have been used at different periods, however. P65 shows visual item (is shown by) can be used to refer to a particular portrait. P65 shows visual item (is shown by) may also be used for Visual Items such as signs, marks and symbols, for example the 'Maltese Cross' or the 'copyright symbol’ that have no particular representational content. This property is part of the fully developed path E24 Physical Human-Made Thing, P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity which is shortcut by, P62 depicts (is depicted by).
|
Examples:
- My T-Shirt (E22) shows visual item Mona Lisa (E38)
|
Examples:
- My T-Shirt (E22) shows visual item Mona Lisa (E36). (fictitious)
|
First order logic:
|
First order logic:
- P65(x,y) ⇒ E24(x)
- P65(x,y) ⇒ E36(y)
- P65(x,y) ⇒ P128(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E29 Design or Procedure. P68 foresees use of (use foreseen by): E57 MaterialE31 Document. P70 documents (is documented in): E1 CRM EntityE32 Authority Document. P71 lists (is listed in): E1 CRM EntityE89 Propositional Object. P129 is about (is subject of): E1 CRM EntityE36 Visual Item. P138 represents (has representation): E1 CRM Entity
|
Superproperty of:
E29 Design or Procedure. P68 foresees use of (use foreseen by): E57 MaterialE31 Document. P70 documents (is documented in): E1 CRM EntityE32 Authority Document. P71 lists (is listed in): E1 CRM EntityE89 Propositional Object. P129 is about (is subject of): E1 CRM EntityE36 Visual Item. P138 represents (has representation): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property documents that an E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the E89 Propositional Object.
|
Scope Note:
This property documents that an instance of E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the instance of E89 Propositional Object.
|
Examples:
- the eBay auction listing of 4 July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55)
|
Examples:
- The eBay auction listing of 4th July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55). (fictitious)
|
First order logic:
|
First order logic:
- P67(x,y) ⇒ E89(x)
- P67(x,y) ⇒ E1(y)
- P67(x,y,z) ⇒ [P67(x,y) ∧ E55(z)]
|
Properties:
|
Properties:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an E57 Material foreseeen to be used by an E29 Design or Procedure. E29 Designs and procedures commonly foresee the use of particular E57 Materials. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented. This property is not intended for the documentation of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed.
|
Scope Note:
This property identifies an instance of E57 Material foreseen to be used by an instance of E29 Design or Procedure. E29 Designs and procedures commonly foresee the use of particular instances of E57 Material. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented. This property is not intended for the documentation of instances of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed.
|
Examples:
- procedure for soda glass manufacture (E29) foresees use of soda (E57)
|
Examples:
- The procedure for soda glass manufacture (E29) foresees use of soda (E57). (Brooks, 1973)
|
First order logic:
|
First order logic:
- P68(x,y) ⇒ E29(x)
- P68(x,y) ⇒ E57(y)
- P68(x,y) ⇒ P67(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This symmetric property describes the association of an E29 Design or Procedure with other Designs or Procedures. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The P69.1 has type property of P69 is associated with allows the nature of the association to be specified; examples of types of association between instances of E29 Design or Procedure include: whole-part, sequence, prerequisite, etc
|
Scope Note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type. The property is not transitive The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc. The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
|
Examples:
- procedure for glass blowing (E29) is associated with procedure for glass heating (E29)
|
Examples:
- The procedure for glass blowing (E29) has association with the procedure for glass heating (E29). (Brooks, 1973)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55).
- The preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type has part (E55).
- Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type follows (E55). (Poole and Reed, 1962)
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type follows (E55). (Loubiere, 1995)
|
First order logic:
|
First order logic:
- P69(x,y) ⇒ E29(x)
- P69(x,y) ⇒ E29(y)
- P69(x,y,z) ⇒ [P69(x,y) ∧ E55(z)]
|
Properties:
|
Properties:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property describes the CRM Entities documented by instances of E31 Document. Documents may describe any conceivable entity, hence the link to the highest-level entity in the CRM hierarchy. This property is intended for cases where a reference is regarded as being of a documentary character, in the scholarly or scientific sense.
|
Scope Note:
This property describes the CRM Entities documented as instances of E31 Document. Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement.
|
Examples:
- the British Museum catalogue (E31) documents the British Museum’s Collection (E78)
|
Examples:
- The ‘Catalogue of the Greek coins of Arabia, Mesopotamia and Persia’ (E31) documents parts of the British Museum’s Collection (E78). (British Museum & Hill, 1922)
|
First order logic:
|
First order logic:
- P70(x,y) ⇒ E31(x)
- P70(x,y) ⇒ E1(y)
- P70(x,y) ⇒ P67(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
|
Scope Note:
This property associates an instance of E32 Authority Document, with an instance of E1 CRM Entity which it lists for reference purposes.
|
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
|
Examples:
- The Art & Architecture Thesaurus (E32) lists alcazars (E55). (http://vocab.getty.edu/page/aat/300006897)
|
First order logic:
|
First order logic:
- P71(x,y) ⇒ E32(x)
- P71(x,y) ⇒ E1(y)
- P71(x,y) ⇒ P67(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to many, necessary (0,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property describes the E56 Language of an E33 Linguistic Object. Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
|
Scope Note:
This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed. Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
|
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
|
Examples:
- The American Declaration of Independence (E33) has language 18th Century English (E56). (Perley, 2017)
|
First order logic:
|
First order logic:
- P72(x,y) ⇒ E33(x)
- P72(x,y) ⇒ E56(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E70 Thing. P130 shows features of (features are also found on): E70 Thing
|
Subproperty of:
E70 Thing. P130i features are also found on (shows features of): E70 Thing
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation. When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
|
Scope Note:
This property links an instance of E33 Linguistic Object (A), to another instance of E33 Linguistic Object (B) which is the translation of A. When an instance of E33 Linguistic Object is translated into a new language a new instance of E33 Linguistic Object is created, despite the translation being conceptually similar to the source. This property is non-symmetric.
|
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
|
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33). (Spiers & Surenne, 1854)
|
First order logic:
|
First order logic:
- P73(x,y) ⇒ E33(x)
- P73(x,y) ⇒ E33(y)
- P73(x,y) ⇒ P130i(x,y)
- P73(x,y) ⇒ ¬P73(y,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the current or former E53 Place of residence of an E39 Actor. The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
|
Scope Note:
This property describes the current or former place of residence (an instance of E53 Place) of an instance of E39 Actor. The residence may be either the place where the actor resides, or a legally registered address of any kind.
|
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
|
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53). (Robinson, 2000)
|
First order logic:
|
First order logic:
- P74(x,y) ⇒ E39(x)
- P74(x,y) ⇒ E53(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
|
Scope Note:
This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim.
|
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
|
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30). (Raga, 2016)
|
First order logic:
|
First order logic:
- P75(x,y) ⇒ E39(x)
- P75(x,y) ⇒ E30(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
|
Scope Note:
This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address.
|
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
|
Examples:
- The Research Libraries Group, Inc. (RLG) (E74) has contact point “bl.ric@rlg.org” (E41)
|
First order logic:
|
First order logic:
- P76(x,y) ⇒ E39(x)
- P76(x,y) ⇒ E41(y)
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Subproperty of:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an E52 Time-Span using an E49Time Appellation.
|
Scope Note:
|
Examples:
- the time span 1926 to 1988 (E52) is identified by “Showa” (Japanese time appellation) (E49)
|
Examples:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P3 has note: E62 String
|
Subproperty of:
E1 CRM Entity. P3 has note: E62 String
|
Quantification:
|
Quantification:
|
Scope Note:
This property qualifies the beginning of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc.
|
Scope Note:
This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the certainty, precision, sources etc. of its beginning. Such notes may also be used to elaborate arguments about constraints or to give explanations of alternatives.
|
Examples:
- the time-span of the Holocene (E52) beginning is qualified by approximately (E62)
|
Examples:
- The time-span of the Holocene (E52) beginning is qualified by “The formal definition and dating of the GSSP (GlobalStratotype Section and Point) for the base of the Holocene using the Greenland NGRIP ice core, and selected auxiliary records” (E62). (Walker et al., 2009)
|
First order logic:
|
First order logic:
- P79(x,y) ⇒ E52 (x)
- P79(x,y) ⇒ E62(y)
- P79(x,y) ⇒ P3(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P3 has note: E62 String
|
Subproperty of:
E1 CRM Entity. P3 has note: E62 String
|
Quantification:
|
Quantification:
|
Scope Note:
This property qualifies the end of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc.
|
Scope Note:
This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the end of this time-span concerning certainty, precision, sources etc. This property may also be used to describe arguments constraining possible dates and to distinguish reasons for alternative dates.
|
Examples:
- the time-span of the Holocene (E52) end is qualified by approximately (E62)
|
Examples:
- The time-span of the Holocene (E52) end is qualified by “still ongoing” (E62). (Walker et al., 2009)
|
First order logic:
|
First order logic:
- P80(x,y) ⇒ E52(x)
- P80(x,y) ⇒ E62(y)
- P80(x,y) ⇒ P3(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to one, necessary (1,1:0,n)
|
Quantification:
many to one, necessary (1,n:0,n)
|
Scope Note:
This property describes the minimum period of time covered by an E52 Time-Span. Since Time-Spans may not have precisely known temporal extents, the CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s minimum temporal extent (i.e. its inner boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CRM as application or system specific date intervals, and are not further analysed.
|
Scope Note:
This property associates an instance of E52 Time-Span with an instance of E61 Time Primitive specifying a minimum period of time covered by it. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s minimum temporal extent (i.e., its inner boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different minimum extents without contradicting each other, the smallest interval including all these extents will be the best estimate. This should be taken into account for information integration.
|
Examples:
- the time-span of the development of the CIDOC CRM (E52) ongoing throughout 1996-2002 (E61)
|
Examples:
- The time-span of the development of the CIDOC CRM (E52) ongoing throughout “1996-2003” (E61). (Doerr, 2003)
- The Time-Span of the Thirty Years War (E52) ongoing throughout “23rd May 1618 AD until 24th October 1648 AD” (E61). (Bonney, 2014)
- The time-span of the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) (E52) ongoing throughout “2181 BC – 2160 BC” (E61). (Reid, 1993)
[This is the minimal common agreement of two conflicting dates: James Henry Breasted dates the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) from 2475BC to 2160BC in his Ancient Records (first published in 1906), volume 1, sections 58–75 (Breasted, 1906). Ian Shaw dates it from 2181BC to 2125BC in his Oxford History of Ancient Egypt (published in 2000), pp. 479–483 (Shaw, 2000).]
|
First order logic:
|
First order logic:
- P81(x,y) ⇒ E52(x)
- P81(x,y) ⇒ E61(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to one, necessary (1,1:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property describes the maximum period of time within which an E52 Time-Span falls. Since Time-Spans may not have precisely known temporal extents, the CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s maximum temporal extent (i.e. its outer boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CRM as application or system specific date intervals, and are not further analysed.
|
Scope Note:
This property describes the maximum period of time within which an E52 Time-Span falls. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s maximum temporal extent (i.e., its outer boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different maximum extents without contradicting each other, the resulting intersection of all these extents will be the best estimate. This should be taken into account for information integration.
|
Examples:
- the time-span of the development of the CIDOC CRM (E52) at some time within 1992-infinity (E61)
|
Examples:
- The time-span of the development of the CIDOC CRM (E52) at some time within “1992-infinity” (E61). (Doerr, 2003)
- The Time-Span of the Battle in the Teutoburg Forest (E52) at some time within “September 9 CE” (E61). (Andrews & Kesteven, 1977)
- The time-Span of the death of Tut Ankh Amun (E52) at some time within “December 1324 BC to February 1323 BC” (E61). (Murdoch, 2003)
- The time-span of the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) (E52) at some time within “2475BC - 2125BC” (E61). (Reid, 1993)
|
First order logic:
|
First order logic:
- P82(x,y) ⇒ E52(x)
- P82(x,y) ⇒ E61(y)
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the minimum length of time covered by an E52 Time-Span. It allows an E52 Time-Span to be associated with an E54 Dimension representing it’s minimum duration (i.e. it’s inner boundary) independent from the actual beginning and end.
|
Scope Note:
|
Examples:
- the time span of the Battle of Issos 333 B.C.E. (E52) had at least duration Battle of Issos minimum duration (E54) has unit (P91) day (E58) has value (P90) 1 (E60)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the maximum length of time covered by an E52 Time-Span. It allows an E52 Time-Span to be associated with an E54 Dimension representing it’s maximum duration (i.e. it’s outer boundary) independent from the actual beginning and end.
|
Scope Note:
|
Examples:
- the time span of the Battle of Issos 333 B.C.E. (E52) had at most duration Battle of Issos maximum duration (E54) has unit (P91) day (E58) has value (P90) 2 (E60)
|
Examples:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the inclusion relationship between two instances of E52 Time-Span. This property supports the notion that a Time-Span’s temporal extent falls within the temporal extent of another Time-Span. It addresses temporal containment only, and no contextual link between the two instances of Time-Span is implied.
|
Scope Note:
This property describes the inclusion relationship between two instances of E52 Time-Span. This property supports the notion that the temporal extent of an instance of E52 Time-Span falls within the temporal extent of another instance of E52 Time-Span. It addresses temporal containment only, and no contextual link between the two instances of E52 Time-Span is implied. This property is transitive.
|
Examples:
- the time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52)
|
Examples:
- The time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52). (Riley, 2009) (Robinson, 2000)
|
First order logic:
|
First order logic:
- P86(x,y) ⇒ E52(x)
- P86(x,y) ⇒ E52(y)
- [P86(x,y) ∧ P86(y,z)] ⇒ P86(x,z)
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Subproperty of:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an E53 Place using an E44 Place Appellation.
|
Scope Note:
|
Examples:
- of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an E53 Place that forms part of another Place. It supports the notion that a Place can be subdivided into one or more constituent parts. It implies both spatial and contextual containment relationships between the two Places.
|
Scope Note:
|
Examples:
- the area covered by the London Borough of Islington in 1976 (E53) forms part of the area covered by Greater London in 1976 (E53)
|
Examples:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
many to many, necessary, dependent (1,n:0,n)
|
Scope Note:
This property identifies the instances of E53 Places that fall within the area covered by another Place. It addresses spatial containment only, and no ‘whole-part’ relationship between the two places is implied.
|
Scope Note:
This property identifies an instance of E53 Place that falls wholly within the extent of another instance of E53 Place. It addresses spatial containment only and does not imply any relationship between things or phenomena occupying these places. This property is transitive and reflexive.
|
Examples:
- the area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53)
|
Examples:
- The area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53). (Pryor, 2016)
|
First order logic:
|
First order logic:
- P89(x,y) ⇒ E53(x)
- P89(x,y) ⇒ E53(y)
- [P89(x,y) ∧ P89(y,z)] ⇒ P89(x,z)
- P89(x,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to one, necessary (1,1:0,n)
|
Quantification:
many to one, necessary (1,1:0,n)
|
Scope Note:
This property allows an E54 Dimension to be approximated by an E60 Number primitive.
|
Scope Note:
This property allows an instance of E54 Dimension to be approximated by an instance of E60 Number primitive.
|
Examples:
- height of silver cup 232 (E54) has value 226 (E60)
|
Examples:
- The height of silver cup 232 (E54) has value 226 (E60). (fictitious)
- Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30th March 1987 (E97) has value 24,750,000 (E60).
|
First order logic:
|
First order logic:
- P90(x,y) ⇒ E54(x)
- P90(x,y) ⇒ E60(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
|
Superproperty of:
E97 Monetary Amount. P180 has currency (was currency of): E98 Currency
|
Quantification:
many to one, necessary (1,1:0,n)
|
Quantification:
many to one, necessary (1,1:0,n)
|
Scope Note:
This property shows the type of unit an E54 Dimension was expressed in.
|
Scope Note:
This property shows the type of unit an instance of E54 Dimension was expressed in.
|
Examples:
- height of silver cup 232 (E54) has unit mm (E58)
|
Examples:
- The height of silver cup 232 (E54) has unit mm (E58). (fictitious)
|
First order logic:
|
First order logic:
- P91(x,y) ⇒ E54(x)
- P91(x,y) ⇒ E58(y)
|
|
|
|
Domain:
E63 Beginning of Existence
|
Domain:
E63 Beginning of Existence
|
Range:
|
Range:
|
Superproperty of:
E65 Creation. P94 has created (was created by): E28 Conceptual ObjectE66 Formation. P95 has formed (was formed by): E74 GroupE67 Birth. P98 brought into life (was born): E21 PersonE12 Production. P108 has produced (was produced by): E24 Physical Man-Made ThingE81 Transformation. P123 resulted in (resulted from): E77 Persistent Item
|
Superproperty of:
E65 Creation. P94 has created (was created by): E28 Conceptual ObjectE66 Formation. P95 has formed (was formed by): E74 GroupE67 Birth. P98 brought into life (was born): E21 PersonE12 Production. P108 has produced (was produced by): E24 Physical Human-Made ThingE81 Transformation. P123 resulted in (resulted from): E18 Physical Thing
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Scope Note:
This property allows an E63 Beginning of Existence event to be linked to the E77 Persistent Item brought into existence by it. It allows a “start” to be attached to any Persistent Item being documented i.e. E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, E51 Contact Point and E55 Type.
|
Scope Note:
This property links an instance of E63 Beginning of Existence to the instance of E77 Persistent Item brought into existence by it. It allows a “start” to be attached to any instance of E77 Persistent Item being documented, i.e., as instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation and E55 Type.
|
Examples:
- the birth of Mozart (E67) brought into existence Mozart (E21)
|
Examples:
- The birth of Mozart (E67) brought into existence Mozart (E21). (Deutsch, 1965)
|
First order logic:
|
First order logic:
- P92(x,y) ⇒ E63(x)
- P92(x,y) ⇒ E77(y)
- P92(x,y) ⇒ P12(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E6 Destruction. P13 destroyed (was destroyed by): E18 Physical ThingE68 Dissolution. P99 dissolved (was dissolved by): E74 GroupE69 Death. P100 was death of (died in): E21 PersonE81 Transformation. P124 transformed (was transformed by): E77 Persistent Item
|
Superproperty of:
E6 Destruction. P13 destroyed (was destroyed by): E18 Physical ThingE68 Dissolution. P99 dissolved (was dissolved by): E74 GroupE69 Death. P100 was death of (died in): E21 PersonE81 Transformation. P124 transformed (was transformed by): E18 Physical Thing
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Quantification:
one to many, necessary (1,n:0,1)
|
Quantification:
one to many, necessary (1,n:0,1)
|
Scope Note:
This property allows an E64 End of Existence event to be linked to the E77 Persistent Item taken out of existence by it. In the case of immaterial things, the E64 End of Existence is considered to take place with the destruction of the last physical carrier. This allows an “end” to be attached to any Persistent Item being documented i.e. E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, E51 Contact Point and E55 Type. For many Persistent Items we know the maximum life-span and can infer, that they must have ended to exist. We assume in that case an End of Existence, which may be as unnoticeable as forgetting the secret knowledge by the last representative of some indigenous nation.
|
Scope Note:
This property links an instance of E64 End of Existence to the instance of E77 Persistent Item taken out of existence by it. In the case of immaterial things, the instance of E64 End of Existence is considered to take place with the destruction of the last physical carrier. This allows an “end” to be attached to any instance of E77 Persistent Item being documented i.e., instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation and E55 Type. For many instances of E77 Persistent Item we know the maximum life-span and can infer, that they must have ended to exist. We assume in that case an instance of E64 End of Existence, which may be as unnoticeable as forgetting the secret knowledge by the last representative of some indigenous nation.
|
Examples:
- the death of Mozart (E69) took out of existence Mozart (E21)
|
Examples:
- The death of Mozart (E69) took out of existence Mozart (E21). (Deutsch, 1965)
|
First order logic:
|
First order logic:
- P93(x,y) ⇒ E64(x)
- P93(x,y) ⇒ E77(y)
- P93(x,y) ⇒ P12(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E83 Type Creation. P135 created type (was created by): E55 Type
|
Superproperty of:
E83 Type Creation. P135 created type (was created by): E55 Type
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Scope Note:
This property allows a conceptual E65 Creation to be linked to the E28 Conceptual Object created by it. It represents the act of conceiving the intellectual content of the E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.
|
Scope Note:
This property links an instance of E65 Creation to the instance of E28 Conceptual Object created by it. It represents the act of conceiving the intellectual content of the instance of E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the instance of E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.
|
Examples:
- the composition of “The Four Friends” by A. A. Milne (E65) has created “The Four Friends” by A. A. Milne (E28)
|
Examples:
- The composition of “The Four Friends” by A. A. Milne (E65) has created “The Four Friends” by A. A. Milne (E33). (Milne, 2012)
|
First order logic:
|
First order logic:
- P94(x,y) ⇒ E65(x)
- P94(x,y) ⇒ E28(y)
- P94(x,y) ⇒ P92(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Scope Note:
This property links the founding or E66 Formation for an E74 Group with the Group itself.
|
Scope Note:
This property associates the instance of E66 Formation with the instance of E74 Group that it founded.
|
Examples:
- the formation of the CIDOC CRM SIG at the August 2000 CIDOC Board meeting (E66) has formed the CIDOC CRM Special Interest Group (E74)
|
Examples:
- The formation of the CIDOC CRM SIG at the August 2000 CIDOC Board meeting (E66) has formed the CIDOC CRM Special Interest Group (E74).
|
First order logic:
|
First order logic:
- P95(x,y) ⇒ E66(x)
- P95(x,y) ⇒ E74(y)
- P95(x,y) ⇒ P92(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Quantification:
many to one, necessary (1,1:0,1)
|
Quantification:
many to one, necessary (1,1:0,n)
|
Scope Note:
This property links an E67 Birth event to an E21 Person as a participant in the role of birth-giving mother. Note that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The Person being born is linked to the Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. This is a sub-property of P11 had participant (participated in).
|
Scope Note:
This property links an instance of E67 Birth to an instance of E21 Person in the role of birth-giving mother. Note that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The instance of P21 Person being born is linked to the instance of E67 Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions.
|
Examples:
- the birth of Queen Elizabeth II (E67) by mother Queen Mother (E21)
|
Examples:
- The birth of Queen Elizabeth II (E67) by mother Her Majesty Queen Elizabeth The Queen Mother (E21). (Parker, 2002)
|
First order logic:
|
First order logic:
- P96(x,y) ⇒ E67(x)
- P96(x,y) ⇒ E21(y)
- P96(x,y) ⇒ P11(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to one, necessary (1,1:0,n)
|
Scope Note:
This property links an E67 Birth event to an E21 Person in the role of biological father. Note that biological fathers are not seen as necessary participants in the Birth, whereas birth-giving mothers are (see P96 by mother (gave birth)). The Person being born is linked to the Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. A Birth event is normally (but not always) associated with one biological father.
|
Scope Note:
This property links an instance of E67 Birth to an instance of E21 Person in the role of biological father. Note that biological fathers are not seen as necessary participants in the birth, whereas birth-giving mothers are (see P96 by mother (gave birth)). The Person being born is linked to the Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. An instance of E67 Birth is normally (but not always) associated with one biological father.
|
Examples:
- King George VI (E21) was father for the birth of Queen Elizabeth II (E67)
|
Examples:
- King George VI (E21) was father for the birth of Queen Elizabeth II (E67). (Parker, 2002)
|
First order logic:
|
First order logic:
- P97(x,y) ⇒ E67(x)
- P97(x,y) ⇒ E21(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Quantification:
one to many, dependent (0,n:1,1)
|
Quantification:
one to many, dependent (0,n:1,1)
|
Scope Note:
This property links an E67Birth event to an E21 Person in the role of offspring. Twins, triplets etc. are brought into life by the same Birth event. This is not intended for use with general Natural History material, only people. There is no explicit method for modelling conception and gestation except by using extensions.
|
Scope Note:
This property links an instance of E67 Birth event to an instance of E21 Person in the role of offspring. Twins, triplets etc. are brought into life by the same instance of E67 Birth. This is not intended for use with general Natural History material, only people. There is no explicit method for modelling conception and gestation except by using extensions.
|
Examples:
- the Birth of Queen Elizabeth II (E67) brought into life Queen Elizabeth II (E21)
|
Examples:
- The Birth of Queen Elizabeth II (E67) brought into life Queen Elizabeth II (E21). (Parker, 2002)
|
First order logic:
|
First order logic:
- P98(x,y) ⇒ E67(x)
- P98(x,y) ⇒ E21(y)
- P98(x,y) ⇒ P92(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 ActorE64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 ActorE64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Quantification:
one to many, necessary (1,n:0,n)
|
Quantification:
one to many, necessary (1,n:0,n)
|
Scope Note:
This property links the disbanding or E68 Dissolution of an E74 Group to the Group itself.
|
Scope Note:
This property associates the instance of E68 Dissolution with the instance of E74 Group that it disbanded.
|
Examples:
- the end of The Hole in the Wall Gang (E68) dissolved The Hole in the Wall Gang (E74)
|
Examples:
- The end of The Hole in the Wall Gang (E68) dissolved The Hole in the Wall Gang (E74). (Patterson, 1998)
|
First order logic:
|
First order logic:
- P99(x,y) ⇒ E68(x)
- P99(x,y) ⇒ E74(y)
- P99(x,y) ⇒ P11(x,y)
- P99(x,y) ⇒ P93(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Subproperty of:
E64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Quantification:
one to many, necessary (1,n:0,n)
|
Quantification:
one to many, necessary (1,n:0,1)
|
Scope Note:
This property links an E69 Death event to the E21 Person that died. A Death event may involve multiple people, for example in the case of a battle or disaster. This is not intended for use with general Natural History material, only people.
|
Scope Note:
This property links an instance of E69 Death to the instance of E21 Person that died. An instance of E69 Death may involve multiple people, for example in the case of a battle or disaster. This is not intended for use with general natural history material, only people.
|
Examples:
- Mozart’s death (E69) was death of Mozart (E21)
|
Examples:
- Mozart’s death (E69) was death of Mozart (E21). (Sitwell, 2017)
|
First order logic:
|
First order logic:
- P100(x,y) ⇒ E69(x)
- P100(x,y) ⇒ E21(y)
- P100(x,y) ⇒ P93(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property links an instance of E70 Thing to an E55 Type of usage. It allows the relationship between particular things, both physical and immaterial, and general methods and techniques of use to be documented. Thus it can be asserted that a baseball bat had a general use for sport and a specific use for threatening people during the Great Train Robbery.
|
Scope Note:
This property associates an instance of E70 Thing with an instance of E55 Type that describes the type of use that it was actually employed for. It allows the relationship between particular things, both physical and immaterial, and the general methods and techniques of real use to be documented. This may well be different from the intended functional purpose of the instance of E70 Thing (which can be documented with P103 was intended for (was intention of)). For example, it could be recorded that a particular wooden crate had a general use as a shelf support on a market stall even though it had been originally intended for carrying vegetables. The use of this property is intended to allow the documentation of usage patterns attested in historical records or through scientific investigation (for instance ceramic residue analysis). It should not be used to document the intended, and thus assumed, use of an object.
|
Examples:
- Tony Gill’s Ford Mustang (E22) had as general use transportation (E55)
|
Examples:
- Tony Gill’s Ford Mustang (E22) had as general use transportation (E55).
- The Egyptian unglazed vessel used in the 2003 study reported by Barnard et al. (E22) had as general use camel milk preparation (E55). (Barnard et al., 2007)
|
First order logic:
|
First order logic:
- P101(x,y) ⇒ E70(x)
- P101(x,y) ⇒ E55(y)
- P101(x,y) ⇒ (∃z)[E7(z) ∧ P16i(,x,z) ∧ P2(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Quantification:
|
Quantification:
|
Scope Note:
This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind.
|
Scope Note:
This property associates an instance of E35 Title has been applied to an instance of E71 Human-Made Thing. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the title and the thing to be further clarified, for example, if the title was a given title, a supplied title etc. It allows any human-made material or immaterial thing to be given a title. It is possible to imagine a title being created without a specific object in mind.
|
Examples:
- the first book of the Old Testament (E33) has title “Genesis” (E35)
- has type translated (E55)
|
Examples:
- The first book of the Old Testament (E33) has title “Genesis” (E35) has type translated title (E55) (E55). (Brueggemann, 1982)
- Monet’s painting from 1868-1869 held by Musée d'Orsay, Paris, under inventory number RF 1984 164 (E22) has title “La Pie” (E35) has type creator’s title (E55). (Musée d'Orsay, 2020)
- Monet’s painting from 1868-1869 held by Musée d'Orsay, Paris, under inventory number RF 1984 164 (E22) has title “The Magpie” (E35) has type translated title (E55). (Musée d'Orsay, 2020)
|
First order logic:
|
First order logic:
- P102(x,y) ⇒ E71(x)
- P102(x,y) ⇒ E35(y)
- P102(x,y,z) ⇒ [P102(x,y) ∧ E55(z)]
- P102(x,y) ⇒ P1(x,y)
|
Properties:
P102.1 has type: E55 Type
|
Properties:
P102.1 has type: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property links an instance of E71 Man-Made Thing to an E55 Type of usage. It creates a property between specific man-made things, both physical and immaterial, to Types of intended methods and techniques of use. Note: A link between specific man-made things and a specific use activity should be expressed using P19 was intended use of (was made for).
|
Scope Note:
This property links an instance of E71 Human-Made Thing to an instance of E55 Type describing its intended usage. It creates a relation between specific human-made things, both physical and immaterial, to types of intended methods and techniques of use. Note: A link between specific human-made things and a specific use activity should be expressed using P19 was intended use of (was made for).
|
Examples:
- this plate (E22) was intended for being destroyed at wedding reception (E55)
|
Examples:
- This plate (E22) was intended for being destroyed at wedding reception (E55). (fictitious)
|
First order logic:
|
First order logic:
- P103(x,y) ⇒ E71(x)
- P103(x,y) ⇒ E55(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property links a particular E72 Legal Object to the instances of E30 Right to which it is subject. The Right is held by an E39 Actor as described by P75 possesses (is possessed by).
|
Scope Note:
This property links a particular instance of E72 Legal Object to the instances of E30 Right to which it is subject. The Right is held by an E39 Actor as described by P75 possesses (is possessed by).
|
Examples:
- Beatles back catalogue (E72) is subject to reproduction right on Beatles back catalogue (E30)
|
Examples:
- The Beatles back catalogue (E89) is subject to reproduction right on the Beatles back catalogue (E30). (Raga, 2016)
|
First order logic:
|
First order logic:
- P104(x,y) ⇒ E72(x)
- P104(x,y) ⇒ E30(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E18 Physical Thing. P52 has current owner (is current owner of): E39 Actor
|
Superproperty of:
E18 Physical Thing. P52 has current owner (is current owner of): E39 Actor
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the E39 Actor who holds the instances of E30 Right to an E72 Legal Object. It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object. P105 right held by (has right on) is a shortcut of the fully developed path from E72 Legal Object through P104 is subject to (applies to), E30 Right, P75 possesses (is possessed by) to E39 Actor.
|
Scope Note:
This property identifies the instance of E39 Actor who holds the instances of E30 Right to an instance of E72 Legal Object. It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object. This property is a shortcut of the fully developed path from E72 Legal Object, P104 is subject to, E30 Right, P75i is possessed by to E39 Actor.
|
Examples:
- Beatles back catalogue (E73) right held by Michael Jackson (E21)
|
Examples:
- The Beatles back catalogue (E73) right held by Michael Jackson (E21). (Raga, 2016)
|
First order logic:
|
First order logic:
- P105(x,y) ⇒ E72(x)
- P105(x,y) ⇒ E39(y)
- P105(x,y) ⇐ (∃z) [E30(z) ˄ P104(x,z) ˄ P75i(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
|
Superproperty of:
E73 Information Object. P165 incorporates (is incorporated in): E90 Symbolic Object
|
Quantification:
|
Quantification:
|
Scope Note:
This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image.
|
Scope Note:
This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. This property is transitive and non-reflexive.
|
Examples:
- This Scope note P106 (E33) is composed of fragments of texts (E33)
- ‘recognizable’ P106 (E90) is composed of ‘ecognizabl’ (E90)
|
Examples:
- This Scope note of property P106 (E33) is composed of ‘fragments of texts’ (E33).
- ‘recognizable’ (E90) is composed of ‘ecognizabl’ (E90).
|
First order logic:
|
First order logic:
- P106(x,y) ⇒ E90(x)
- P106(x,y) ⇒ E90(y)
- [P106(x,y) ∧ P106(y,z)] ⇒ P106(x,z)
- ¬P106(x,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property relates an E39 Actor to the E74 Group of which that E39 Actor is a member. Groups, Legal Bodies and Persons, may all be members of Groups. A Group necessarily consists of more than one member. This property is a shortcut of the more fully developed path from E74 Group through P144 joined with (gained member by), E85 Joining, P143 joined (was joined by) to E39 Actor The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group.
|
Scope Note:
This property associates an instance of E74 Group with an instance of E39 Actor that is or has been a member thereof. Instances of E74 Group and E21 Person, may all be members of instances of E74 Group.An instance of E74 Group may be founded initially without any member. This property is a shortcut of the more fully developed path from E74 Group, P144i gained member by, E85 Joining, P143 joined to E39 Actor. The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group.
|
Examples:
- Moholy Nagy (E21) is current or former member of Bauhaus (E74)
- National Museum of Science and Industry (E40) has current or former member The National Railway Museum (E40)
- The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) with P107.1 kind of member husband (E55 Type)
|
Examples:
- Moholy-Nagy (E21) is current or former member of Bauhaus (E74). (Moholy-Nagy, 2012)
- National Museum of Science and Industry (E74) has current or former member The National Railway Museum (E74). (Rolt, 1971)
- The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) kind of member husband (E55). (Brandreth, 2004)
|
First order logic:
|
First order logic:
- P107(x,y) ⇒ E74(x)
- P107(x,y) ⇒ E39(y)
- P107(x,y,z) ⇒ [P107(x,y) ∧ E55(z)]
- P107(x,y) ⇐ (∃z) [E85(z) ˄ P144i(x,z) ˄ P143(z,y)]
|
Properties:
P107.1 kind of member: E55 Type
|
Properties:
P107.1 kind of member: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
E24 Physical Man-Made Thing
|
Range:
E24 Physical Human-Made Thing
|
Subproperty of:
E11 Modification. P31 has modified (was modified by): E24 Physical Man-Made ThingE63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Subproperty of:
E11 Modification. P31 has modified (was modified by): E18 Physical ThingE63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Quantification:
one to many, necessary, dependent (1,n:1,1)
|
Scope Note:
This property identifies the E24 Physical Man-Made Thing that came into existence as a result of an E12 Production. The identity of an instance of E24 Physical Man-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Man-Made Thing.
|
Scope Note:
This property identifies the instance of E24 Physical Human-Made Thing that came into existence as a result of the instance of E12 Production. The identity of an instance of E24 Physical Human-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Human-Made Thing.
|
Examples:
- The building of Rome (E12) has produced Τhe Colosseum (E22)
|
Examples:
- The building of Rome (E12) has produced Τhe Colosseum (E24). (Hopkins & Beard, 2011)
|
First order logic:
|
First order logic:
- P108(x,y) ⇒ E12(x)
- P108(x,y) ⇒ E24(y)
- P108(x,y) ⇒ P31(x,y)
- P108(x,y) ⇒ P92(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E18 Physical Thing. P49 has former or current keeper (is former or current keeper of): E39 Actor
|
Subproperty of:
E18 Physical Thing. P49 has former or current keeper (is former or current keeper of): E39 Actor
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E39 Actor or Actors who assume or have assumed overall curatorial responsibility for an E78 Collection. This property is effectively a short-cut. It does not allow a history of curation to be recorded. This would require use of an Event assigning responsibility for a Collection to a curator.
|
Scope Note:
This property identifies the instance of E39 Actor who assumed or have assumed overall curatorial responsibility for an instance of E78 Curated Holding. It does not allow a history of curation to be recorded. This would require use of an event initiating a curator being responsible for a collection.
|
Examples:
- the Robert Opie Collection (E78) has current or former curator Robert Opie (E39)
- the Mikael Heggelund Foslie’s coralline red algae Herbarium (E78) has current or former curator Mikael Heggelund Foslie
|
Examples:
- The Robert Opie Collection (E78) has current or former curator Robert Opie (E21). ( https://www.robertopiecollection.com/)
- The Mikael Heggelund Foslie’s coralline red algae Herbarium (E78) has current or former curator Mikael Heggelund Foslie (E21). (Woelkerling et al., 2005)
|
First order logic:
|
First order logic:
- P109(x,y) ⇒ E78(x)
- P109(x,y) ⇒ E39(y)
- P109(x,y) ⇒ P49(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
E24 Physical Man-Made Thing
|
Range:
E24 Physical Human-Made Thing
|
Subproperty of:
E11 Modification. P31 has modified (was modified by): E24 Physical Man-Made Thing
|
Subproperty of:
E11 Modification. P31 has modified (was modified by): E18 Physical Thing
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E24 Physical Man-Made Thing that is added to (augmented) in an E79 Part Addition. Although a Part Addition event normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.
|
Scope Note:
This property identifies the instance of E24 Physical Human-Made Thing that is added to (augmented) in an instance of E79 Part Addition. Although an instance of E79 Part Addition event normally concerns only one instance of E24 Physical Human-Made Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.
|
Examples:
- the final nail-insertion Event (E79) augmented Coffin of George VI (E24)
|
Examples:
- The final nail-insertion Event (E79) augmented Coffin of George VI (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state)
|
First order logic:
|
First order logic:
- P110(x,y) ⇒ E79(x)
- P110(x,y) ⇒ E24(y)
- P110(x,y) ⇒ P31(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent ItemE7 Activity. P16 used specific object (was used for): E70 Thing
|
Subproperty of:
E7 Activity. P16 used specific object (was used for): E70 Thing
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E18 Physical Thing that is added during an E79 Part Addition activity
|
Scope Note:
This property identifies the instance of E18 Physical Thing that is added during an instance of E79 Part Addition activity
|
Examples:
- the insertion of the final nail (E79) added the last nail in George VI’s coffin (E18)
|
Examples:
- The insertion of the final nail (E79) added the last nail in George VI’s coffin (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state)
|
First order logic:
|
First order logic:
- P111(x,y) ⇒ E79(x)
- P111(x,y) ⇒ E18(y)
- P111(x,y) ⇒ P16(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
E24 Physical Man-Made Thing
|
Range:
E24 Physical Human-Made Thing
|
Subproperty of:
E11 Modification. P31 has modified (was modified by): E24 Physical Man-Made Thing
|
Subproperty of:
E11 Modification. P31 has modified (was modified by): E18 Physical Thing
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E24 Physical Man-Made Thing that was diminished by E80 Part Removal. Although a Part removal activity normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single Part Removal activity.
|
Scope Note:
This property identifies the instance E24 Physical Human-Made Thing that was diminished by an instance of E80 Part Removal. Although an instance of E80 Part removal activity normally concerns only one instance of E24 Physical Human-Made Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single instance of E80 Part Removal activity.
|
Examples:
- the coffin of Tut-Ankh-Amun (E22) was diminished by The opening of the coffin of Tut-Ankh-Amun (E80)
|
Examples:
- The coffin of Tut-Ankh-Amun (E22) was diminished by The opening of the coffin of Tut-Ankh-Amun (E80). (Carter, 2014)
|
First order logic:
|
First order logic:
- P112(x,y) ⇒ E80(x)
- P112(x,y) ⇒ E24(y)
- P112(x,y) ⇒ P31(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Subproperty of:
E5 Event. P12 occurred in the presence of (was present at): E77 Persistent Item
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E18 Physical Thing that is removed during an E80 Part Removal activity.
|
Scope Note:
This property identifies the instance of E18 Physical Thing that is removed during an instance of E80 Part Removal activity.
|
Examples:
- the opening of the coffin of Tut-Ankh-Amun (E80) removed The mummy of Tut-Ankh-Amun (E20,E22)
|
Examples:
- The opening of the coffin of Tut-Ankh-Amun (E80) removed The mummy of Tut-Ankh-Amun (E20, E22). (Carter, 2014)
|
First order logic:
|
First order logic:
- P113(x,y) ⇒ E80(x)
- P113(x,y) ⇒ E18(y)
- P113(x,y) ⇒ P12(x,y)
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This symmetric property allows the instances of E2 Temporal Entity with the same E52 Time-Span to be equated. This property is only necessary if the time span is unknown (otherwise the equivalence can be calculated). This property is the same as the "equal" relationship of Allen’s temporal logic (Allen, 1983, pp. 832-843).
|
Scope Note:
|
Examples:
- the destruction of the Villa Justinian Tempus (E6) is equal in time to the death of Maximus Venderus (E69)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property allows the ending point for a E2 Temporal Entity to be situated by reference to the ending point of another temporal entity of longer duration. This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "finishes / finished-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843).
|
Scope Note:
|
Examples:
- Late Bronze Age (E4) finishes Bronze Age (E4)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property allows the starting point for a E2 Temporal Entity to be situated by reference to the starting point of another temporal entity of longer duration. This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "starts / started-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843).
|
Scope Note:
|
Examples:
- Early Bronze Age (E4) starts Bronze Age (E4)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property allows the entire E52 Time-Span of an E2 Temporal Entity to be situated within the Time-Span of another temporal entity that starts before and ends after the included temporal entity. This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "during / includes" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843).
|
Scope Note:
|
Examples:
- Middle Saxon period (E4) occurs during Saxon period (E4)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an overlap between the instances of E52 Time-Span of two instances of E2 Temporal Entity. It implies a temporal order between the two entities: if A overlaps in time B, then A must start before B, and B must end after A. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated). This property is the same as the "overlaps / overlapped-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843).
|
Scope Note:
|
Examples:
- the Iron Age (E4) overlaps in time with the Roman period (E4)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property indicates that one E2 Temporal Entity immediately follows another. It implies a particular order between the two entities: if A meets in time with B, then A must precede B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated). This property is the same as the "meets / met-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843).
|
Scope Note:
|
Examples:
- Early Saxon Period (E4) meets in time with Middle Saxon Period (E4)
|
Examples:
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies the relative chronological sequence of two temporal entities. It implies that a temporal gap exists between the end of A and the start of B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated). This property is the same as the "before / after" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843).
|
Scope Note:
|
Examples:
- Early Bronze Age (E4) occurs before Late Bronze age (E4)
|
Examples:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This symmetric property allows the instances of E53 Place with overlapping geometric extents to be associated with each other. It does not specify anything about the shared area. This property is purely spatial, in contrast to Allen operators, which are purely temporal.
|
Scope Note:
This symmetric property associates an instance of E53 Place with another instance of E53 Place geometrically overlapping it. It does not specify anything about the shared area. This property is purely spatial. It does not imply that phenomena that define, by their extent, places related by P121 overlaps with have ever covered a common area at the same time or even coexisted. In contrast, spatiotemporal overlaps described by P132 spatiotemporally overlaps are the total of areas simultaneously covered by the related spacetime volumes. This property is symmetric.
|
Examples:
- the territory of the United States (E53) overlaps with the Arctic (E53)
|
Examples:
- The territory of the United States as in 2020 (E53) overlaps with the Arctic (E53). (Gannett et al., 1904)
- The maximal extent of the Kingdom of Greece (1832-1973) (E53) overlaps with the maximal extent of the Republic of Turkey (29th October 1923 to now) (E53).
|
First order logic:
|
First order logic:
- P121(x,y) ⇒ E53(x)
- P121(x,y) ⇒ E53(y)
- P121(x,y) ⇒ P121(y,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This symmetric property allows the instances of E53 Place which share common borders to be related as such. This property is purely spatial, in contrast to Allen operators, which are purely temporal.
|
Scope Note:
This symmetric property associates an instance of E53 Place with another instance of E53 Place which shares a part of its border. This property is purely spatial. It does not imply that the phenomena that define, by their extent, places related by P122 borders with have ever shared a respective border at the same time or even coexisted. In particular, this may be the case when the respective common border is formed by a natural feature. This property is not transitive. This property is symmetric.
|
Examples:
- Scotland (E53) borders with England (E53)
|
Examples:
- Scotland in its 1603 borders (E53) borders with England in its 1603 borders (E53). (Crofton, 2015)
|
First order logic:
|
First order logic:
- P122(x,y) ⇒ E53(x)
- P122(x,y) ⇒ E53(y)
- P122(x,y) ⇒ P122(y,x)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Subproperty of:
E63 Beginning of Existence. P92 brought into existence (was brought into existence by): E77 Persistent Item
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the E77 Persistent Item or items that are the result of an E81 Transformation. New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the link to the common Transformation.
|
Scope Note:
This property identifies the instance or instances of E18 Physical Thing that are the result of an instance of E81 Transformation. New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the links to the common instance of E81 Transformation.
|
Examples:
- the transformation of the Venetian Loggia in Heraklion into a city hall (E81) resulted in the City Hall of Heraklion (E22)
- the death and mummification of Tut-Ankh-Amun (E81) resulted in the Mummy of Tut Tut-Ankh-Amun (E22 and E20)
|
Examples:
- The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) resulted in the City Hall of Heraklion (E24). [AND: has produced (P108) the City Hall of Heraklion (E22)] (Municipality of Heraklion, 2021)
- The mummification of Tut-Ankh-Amun (E81, E12) resulted in the Mummy of Tut-Ankh-Amun (E22,E20). [also: has produced (P108) the Mummy of Tut-Ankh-Amun (E22,E20).] (Carter & Mace 1977)
- The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the Eruption of Mount Vesuvius (E69, E81) resulted in petrified bodies (E20). [Some of these bodies could later be preserved in plaster.]
|
First order logic:
|
First order logic:
- P123(x,y) ⇒ E81(x)
- P123(x,y) ⇒ E18(y)
- P123(x,y) ⇒ P92(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Subproperty of:
E64 End of Existence. P93 took out of existence (was taken out of existence by): E77 Persistent Item
|
Quantification:
one to many, necessary (1,n:0,1)
|
Quantification:
one to many, necessary (1,n:0,1)
|
Scope Note:
This property identifies the E77 Persistent Item or items that cease to exist due to a E81 Transformation. It is replaced by the result of the Transformation, which becomes a new unit of documentation. The continuity between both items, the new and the old, is expressed by the link to the common Transformation.
|
Scope Note:
This property identifies the instance or instances E18 Physical Thing that have ceased to exist due to an instance of E81 Transformation. The item that has ceased to exist and was replaced by the result of the Transformation. The continuity between both items, the new and the old, is expressed by the links to the common instance of E81 Transformation.
|
Examples:
- the transformation of the Venetian Loggia in Heraklion into a city hall (E81) transformed the Venetian Loggia in Heraklion (E22)
- the death and mummification of Tut-Ankh-Amun (E81) transformed the ruling Pharao Tut-Ankh-Amun (E21)
|
Examples:
- The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) transformed the Venetian Loggia in Heraklion (E24). (Municipality of Heraklion, 2021)
- The mummification of Tut-Ankh-Amun (E81, E12) transformed the deceased Pharao Tut-Ankh-Amun (E21). (Carter & Mace, 1977)
- The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the Eruption of Mount Vesuvius (E69, E81) transformed some people of Pompeii (E21). [AND: was death of (P108) some people of Pompeii (E21).]
|
First order logic:
|
First order logic:
- P124(x,y) ⇒ E81(x)
- P124(x,y) ⇒ E18(y)
- P124(x,y) ⇒ P93(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E7 Activity. P32 used general technique (was technique of): E55 Type
|
Superproperty of:
E7 Activity. P32 used general technique (was technique of): E55 Type
|
Quantification:
|
Quantification:
|
Scope Note:
This property defines the kind of objects used in an E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer".
|
Scope Note:
This property associates an instance of E7 Activity to an instance of E55 Type, which classifies an instance of E70 Thing used in an instance of E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer". This property is a shortcut of the more fully developed path from E7 Activity through P16 used specific object, E70 Thing, P2 has type, to E55 Type
|
Examples:
- at the Battle of Agincourt (E7), the English archers used object of type long bow (E55)
|
Examples:
- The English archers’ activity in the Battle of Agincourt (E7) used object of type long bow (E55). (Curry, 2015)
|
First order logic:
|
First order logic:
- P125(x,y) ⇒ E7(x)
- P125(x,y) ⇒ E55(y)
- P125(x,y) ⇔ (∃z) [E70(z) ∧ P16(x,z) ∧ P2(z,y)]
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies E57 Material employed in an E11 Modification. The E57 Material used during the E11 Modification does not necessarily become incorporated into the E24 Physical Man-Made Thing that forms the subject of the E11 Modification.
|
Scope Note:
This property identifies the instance of E57 Material employed in an instance of E11 Modification. The instance of E57 Material used during the instance of E11 Modification does not necessarily become incorporated into the instance of E24 Physical Human-Made Thing that forms the subject of the instance of E11 Modification.
|
Examples:
- the repairing of the Queen Mary (E11) employed Steel (E57)
- distilled water (E57) was employed in the restoration of the Sistine Chapel (E11)
|
Examples:
- The repairing of the Queen Mary (E11) employed Steel (E57). [Beginning October 1942] (Britton, 2012)
- Distilled water (E57) was employed in the restoration of the Sistine Chapel (E11). (Pietrangeli, C., 1986)
|
First order logic:
|
First order logic:
- P126(x,y) ⇒ E11(x)
- P126(x,y) ⇒ E57(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies a super-Type to which an E55 Type is related. It allows Types to be organised into hierarchies. This is the sense of "broader term generic (BTG)" as defined in ISO 2788
|
Scope Note:
This property associates an instance of E55 Type with another instance of E55 Type that has a broader meaning. It allows instances of E55 Types to be organised into hierarchies. This is the sense of "broader term generic (BTG)" as defined in ISO 25964-2:2013 (International Organization for Standardization 2013). This property is transitive.
|
Examples:
- dime (E55) has broader term coin (E55)
|
Examples:
- dime (E55) has broader term coin (E55). (Yerkes, 1989)
|
First order logic:
|
First order logic:
- P127(x,y) ⇒ E55(x)
- P127(x,y) ⇒ E55(y)
- [P127(x,y) ∧ P127(y,z)] ⇒ P127(x,z)
|
|
|
|
Domain:
E24 Physical Man-Made Thing
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E24 Physical Man-Made Thing. P65 shows visual item (is shown by): E36 Visual Item
|
Superproperty of:
E24 Physical Human-Made Thing. P65 shows visual item (is shown by): E36 Visual Item
|
Subproperty of:
E70 Thing. P130 shows features of (features are also found on): E70 Thing
|
Subproperty of:
E70 Thing. P130 shows features of (features are also found on): E70 Thing
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an E73 Information Object carried by an instance of E24 Physical Man-Made Thing. In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items.
|
Scope Note:
This property identifies an instance E90 Symbolic Object carried by an instance of E18 Physical Thing. Since an instance of E90 Symbolic Object is defined as an immaterial idealization over potentially multiple carriers, any individual realization on a particular physical carrier may be defective, due to deterioration or shortcomings in the process of creating the realization compared to the intended ideal. As long as such defects do not substantially affect the complete recognition of the respective symbolic object, it is still regarded as carrying an instance of this E90 Symbolic Object. If these defects are of scholarly interest, the particular realization can be modelled as an instance of E25 Human-Made Feature. Note, that any instance of E90 Symbolic Object incorporated (P165) in the carried symbolic object is also carried by the same instance of E18 Physical Thing.
|
Examples:
- Matthew’s paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73)
|
Examples:
- Matthew’s paperback copy of Reach for the Sky (E18) carries the text of Reach for the Sky (E73). [see also: (Brickhill, 2001)] (fictitious)
|
First order logic:
|
First order logic:
- P128(x,y) ⇒ E18(x)
- P128(x,y) ⇒ E90(y)
- P128(x,y) ⇒ P130(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an E1 CRM Entity, in that it describes the primary subject or subjects of an E89 Propositional Object.
|
Scope Note:
This property documents that an instance of E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an instance of E1 CRM Entity, in that it describes the primary subject or subjects of an instance of E89 Propositional Object.
|
Examples:
- The text entitled ‘Reach for the sky’ (E33) is about Douglas Bader (E21)
|
Examples:
- The text entitled ‘Reach for the sky’ (E33) is about Douglas Bader (E21). (Brickhill, 2001)
|
First order logic:
|
First order logic:
- P129(x,y) ⇒ E89(x)
- P129(x,y) ⇒ E1(y)
- P129(x,y) ⇒ P67(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E33 Linguistic Object. P73 has translation (is translation of): E33 Linguistic ObjectE24 Physical Man-Made Thing. P128 carries (is carried by): E90 Symbolic Object
|
Superproperty of:
E18 Physical Thing. P128 carries (is carried by): E90 Symbolic Object
|
Quantification:
|
Quantification:
|
Scope Note:
This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons.
|
Scope Note:
This property generalises the notions of "copy of" and "similar to" into a directed relationship, where the domain expresses the derivative or influenced item and the range the source or influencing item, if such a direction can be established. The property can also be used to express similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. The property expresses a symmetric relationship in case no direction of influence can be established either from evidence on the item itself or from historical knowledge. This holds in particular for siblings of a derivation process from a common source or non-causal cultural parallels, such as some weaving patterns. The P130.1 kind of similarity property of the P130 shows features of (features are also found on) property enables the relationship between the domain and the range to be further clarified, in the sense from domain to range, if applicable. For example, it may be expressed if both items are product “of the same mould”, or if two texts “contain identical paragraphs”. If the reason for similarity is a sort of derivation process, i.e., that the creator has used or had in mind the form of a particular thing during the creation or production, this process should be explicitly modelled. In these cases, P130 shows features of can be regarded as a shortcut of such a process. However, the current model does not contain any path specific enough to infer this property. Specializations of the CIDOC CRM may however be more explicit, for instance describing the use of moulds etc. This property is not transitive.
|
Examples:
- the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55)
|
Examples:
- Mary Lamb’s Cymbeline from Charles and Mary Lamb’s Tales from Shakespeare (E89) shows features of William Shakespeare’s Cymbeline (E89). (Carrington, 1954)
- The audio recording of Dante Alighieri's La divina commedia read by Enrico de Negri (E73) shows features of the text of Dante Alighieri's La divina commedia (E89). (Alighieri, 1956)
|
First order logic:
|
First order logic:
- P130(x,y) ⇒ E70(x)
- P130(x,y) ⇒ E70(y)
- P130(x,y,z) ⇒ [P130(x,y) ∧ E55(z)]
|
Properties:
P130.1 kind of similarity: E55 Type
|
Properties:
P130.1 kind of similarity: E55 Type
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Subproperty of:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies a name used specifically to identify an E39 Actor. This property is a specialisation of P1 is identified by (identifies) is identified by.
|
Scope Note:
|
Examples:
- Tyler Withersopp IV (E39) is identified by “US social security number 619-17-4204” (E82)
|
Examples:
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
|
Superproperty of:
E92 Spacetime Volume. P10 falls within (contains): E92 Spacetime Volume
|
Quantification:
|
Quantification:
|
Scope Note:
This symmetric property allows instances of E4 Period that overlap both temporally and spatially to be related, i,e. they share some spatio-temporal extent. This property does not imply any ordering or sequence between the two periods, either spatial or temporal.
|
Scope Note:
This symmetric property associates two instances of E92 Spacetime Volume that have some of their extents in common. If only the fuzzy boundaries of the instances of E92 Spacetime Volume overlap, this property cannot be determined from observation alone and therefore should not be applied. However, there may be other forms of justification that the two instances of E92 Spacetime Volume must have some of their extents in common regardless of where and when precisely. If this property holds for two instances of E92 Spacetime Volume then it cannot be the case that P133 is spatiotemporally separated from also holds for the same two instances. Furthermore, there are cases where neither P132 spatiotemporally overlaps with nor P133 is spatiotemporally separated from holds between two instances of E92 Spacetime Volume. This would occur where only an overlap of the fuzzy boundaries of the two instances of E92 Spacetime Volume occurs and no other evidence is available. This property is symmetric
|
Examples:
- the “Urnfield” period (E4) overlaps with the “Hallstatt” period (E4)
|
Examples:
- The “Urnfield” period (E4) spatiotemporally overlaps with the “Hallstatt” period (E4. (Gimbutas, 1965)
|
First order logic:
|
First order logic:
- P132(x,y) ⇒ E92(x)
- P132(x,y) ⇒ E92(y)
- P132(x,y) ⇒ P132(y,x)
- P132(x,y) ⇒ ¬P133(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This symmetric property allows instances of E4 Period that do not overlap both temporally and spatially, to be related i,e. they do not share any spatio-temporal extent. This property does not imply any ordering or sequence between the two periods either spatial or temporal.
|
Scope Note:
This symmetric property associates two instances of E92 Spacetime Volume that have no extents in common. If only the fuzzy boundaries of the instances of E92 Spacetime Volume overlap, this property cannot be determined from observation alone and therefore should not be applied. However, there may be other forms of justification that the two instances of E92 Spacetime Volume must not have any of their extents in common regardless of where and when precisely. If this property holds for two instances of E92 Spacetime Volume then it cannot be the case that P132 spatiotemporally overlaps with also holds for the same two instances. Furthermore, there are cases where neither P132 spatiotemporally overlaps with nor P133 is spatiotemporally separated from holds between two instances of E92 Spacetime Volume. This would occur where only an overlap of the fuzzy boundaries of the two instances of E92 Spacetime Volume occurs and no other evidence is available. This property is not transitive. This property is symmetric.
|
Examples:
- the “Hallstatt” period (E4) is separated from the “La Tène” era (E4)
|
Examples:
- The “Hallstatt” period (E4) is spatiotemporally separated from the “La Tène” era (E4). (Marion, 2004)
- Kingdom of Greece (1831-1924) (E92) is spatiotemporally separated from Ottoman Empire (1299-1922) (E92).
- The path of the army of Alexander the Great (335-323 B.C.) (E7) is spatiotemporally separated from the Mauryan Empire (E4). (Lane Fox, 2004)
|
First order logic:
|
First order logic:
- P133(x,y) ⇒ E92(x)
- P133(x,y) ⇒ E92(y)
- P133(x,y) ⇒ P133(y,x)
- P133(x,y) ⇒ ¬P132(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P15 was influenced by (influenced): E1 CRM Entity
|
Subproperty of:
E7 Activity. P15 was influenced by (influenced): E1 CRM EntityE2 Temporal Entity. P176i starts after the start of (starts before the start of): E2 Temporal Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property allows two activities to be related where the domain is considered as an intentional continuation of the range. Used multiple times, this allows a chain of related activities to be created which follow each other in sequence.
|
Scope Note:
This property associates two instances of E7 Activity, where the domain is considered as an intentional continuation of the range. A continuation of an activity may happen when the continued activity is still ongoing or after the continued activity has completely ended. The continuing activity may have started already before it decided to continue the other one. Continuation implies a coherence of intentions and outcomes of the involved activities. This property is not transitive.
|
Examples:
- the construction of the Kölner Dom (Cologne Cathedral) (E7), abandoned in the 15th century, was continued by construction in the 19th century adapting the initial plans so as to preserve the intended appearance (E7)
|
Examples:
- The construction of the Kölner Dom (Cologne Cathedral) , abandoned in the 15th century (E7), was continued by construction in the 19th century (E7). [The construction in the 19th century adapted the initial plans so as to preserve the intended appearance.] (Wolff, 1999)
|
First order logic:
|
First order logic:
- P134(x,y) ⇒ E7(x)
- P134(x,y)⇒ E7(y)
- P134(x,y) ⇒ P15(x,y)
- P134(x,y) ⇒ P176i(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E65 Creation. P94 has created (was created by): E28 Conceptual Object
|
Subproperty of:
E65 Creation. P94 has created (was created by): E28 Conceptual Object
|
Quantification:
one to many, necessary (1,n:0,1)
|
Quantification:
one to many, necessary (1,n:0,1)
|
Scope Note:
This property identifies the E55 Type, which is created in an E83Type Creation activity.
|
Scope Note:
This property identifies the instance of E55 Type, which is created in an instance of E83 Type Creation activity.
|
Examples:
- The description of a new ribbon worm species by Bürger (E83) created type ‘Lineus coxinus (Bürger, 1892)’ (E55)
|
Examples:
- The description of a new ribbon worm species by Bürger (E83) created type ‘Lineus kennelii’ (E55). (Bürger, 1892)
|
First order logic:
|
First order logic:
- P135(x,y) ⇒ E83(x)
- P135(x,y) ⇒ E55(y)
- P135(x,y) ⇒ P94(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P15 was influenced by (influenced): E1 CRM Entity
|
Subproperty of:
E7 Activity. P15 was influenced by (influenced): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies one or more items that were used as evidence to declare a new E55 Type. The examination of these items is often the only objective way to understand the precise characteristics of a new Type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the Type, such as "holotype" or "original element".
|
Scope Note:
This property identifies one or more instances of E1 CRM Entity that were used as evidence to declare a new instance of E55 Type. The examination of these items is often the only objective way to understand the precise characteristics of a new type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the type, such as "holotype" or "original element".
|
Examples:
- the taxon creation of the plant species ‘Serratula glauca Linné, 1753.’ (E83) was based on Object BM000576251 of the Clayton Herbarium (E20) in the taxonomic role original element (E55)
|
Examples:
- The taxon creation of the plant species ‘Serratula glauca Linné, 1753.’ (E83) was based on Object BM000576251 of the Clayton Herbarium (E20) in the taxonomic role original element (E55). (Blake, 1918)
|
First order logic:
|
First order logic:
- P136(x,y) ⇒ E83(x)
- P136(x,y) ⇒ E1(y)
- P136(x,y,z) ⇒ [P136(x,y) ∧ E55(z)]
- P136(x,y) ⇒ P15(x,y)
|
Properties:
P136.1 in the taxonomic role: E55 Type
|
Properties:
P136.1 in the taxonomic role: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E1 CRM Entity. P2 has type (is type of): E55 Type
|
Subproperty of:
E1 CRM Entity. P2 has type (is type of): E55 Type
|
Quantification:
|
Quantification:
|
Scope Note:
This property allows an item to be declared as a particular example of an E55 Type or taxon The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the Type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic role "lectotype" is not associated with the Type Creation (E83) itself, but selected in a later phase.
|
Scope Note:
This property associates an instance of E1 CRM Entity with an instance of E55 Type for which it has been declared to be a particularly characteristic example. The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic role "lectotype" is not associated with the instance of E83 Type Creation itself but is selected in a later phase.
|
Examples:
- Object BM000098044 of the Clayton Herbarium (E20) exemplifies Spigelia marilandica (L.) L. (E55) in the taxonomic role lectotype
|
Examples:
- Object BM000098044 of the Clayton Herbarium (E20) exemplifies ‘Spigelia marilandica’ (L.) L. (E55) in the taxonomic role lectotype (E55). (Natural History Museum, 2021)
|
First order logic:
|
First order logic:
- P137(x,y) ⇒ E1(x)
- P137(x,y) ⇒ E55(y)
- P137(x,y,z) ⇒ [P137(x,y) ∧ E55(z)]
- P137(x,y) ⇒ P2(x,y)
|
Properties:
P137.1 in the taxonomic role: E55 Type
|
Properties:
P137.1 in the taxonomic role: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
|
Superproperty of:
E36 Visual Item. P199 represents instance of type: E55 Type
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Subproperty of:
E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property establishes the relationship between an E36 Visual Item and the entity that it visually represents. Any entity may be represented visually. This property is part of the fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity, which is shortcut by P62depicts (is depicted by). P138.1 mode of representation allows the nature of the representation to be refined.
|
Scope Note:
This property establishes the relationship between an instance of E36 Visual Item and the instance of E1 CRM Entity that it visually represents. Any entity may be represented visually. This property is part of the fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity, which is shortcut by P62 depicts (is depicted by). P138.1 mode of representation allows the nature of the representation to be refined. This property is also used for the relationship between an original and a digitisation of the original by the use of techniques such as digital photography, flatbed or infrared scanning. Digitisation is here seen as a process with a mechanical, causal component rendering the spatial distribution of structural and optical properties of the original and does not necessarily include any visual similarity identifiable by human observation.
|
Examples:
- the design on the reverse of a Swiss coin (E36) represents Helvetia (E28) mode of representation Profile (E55)
|
Examples:
- The digital file found at http://www.emunch.no/N/full/No-MM_N0001-01.jpg (E36) represents page 1 of Edward Munch's manuscript MM N 1, Munch-museet (E22) mode of representation Digitisation (E55).
- The 3D model VAM_A.200-1946_trace_1M.ply (E73) represents Victoria & Albert Museum’s Madonna and child sculpture (visual work) A.200-1946 (E22) mode of representation 3D surface (E55).
|
First order logic:
|
First order logic:
- P138(x,y) ⇒ E36(x)
- P138(x,y) ⇒ E1(y)
- P138(x,y,z) ⇒ [P138(x,y) ∧ E55(z)]
- P138(x,y) ⇒ P67(x,y)
|
Properties:
P138.1 mode of representation: E55 Type
|
Properties:
P138.1 mode of representation: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property establishes a relationship of equivalence between two instances of E41 Appellation independent from any item identified by them. It is a dynamic asymmetric relationship, where the range expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. The relationship is not transitive. The equivalence applies to all cases of use of an instance of E41 Appellation. Multiple names assigned to an object, which are not equivalent for all things identified with a specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies). P139.1 has type allows the type of derivation, such as “transliteration from Latin 1 to ASCII” be refined..
|
Scope Note:
This property associates an instance of E41 Appellation with another instance of E41 Appellation that constitutes a derivative or variant of the former and that may also be used for identifying items identified by the former, in suitable contexts, independent from the particular item to be identified. This property should not be confused with additional variants of names used characteristically for a single, particular item, such as individual nicknames. It is an asymmetric relationship, where the range expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. The relationship is not transitive. Multiple names assigned to an object, which do not apply to all things identified with the specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies) of this object. P139.1 has type allows the type of derivation to be refined, for instance “transliteration from Latin 1 to ASCII”.
|
Examples:
- "Martin Doerr" (E41) has alternative form "Martin Dörr" (E41) has type Alternate spelling (E55)
- "Гончарова, Наталья Сергеевна" (E41) has alternative form "Gončarova, Natal´â Sergeevna" (E41) has type ISO 9:1995 transliteration (E55)
- “Αθήνα” has alternative form “Athina” has type transcription.
|
Examples:
- "Martin Doerr" (E41) has alternative form "Martin Dörr" (E41) has type Alternate spelling (E55).
- "Гончарова, Наталья Сергеевна" (E41) has alternative form "Gončarova, Natal´â Sergeevna" (E41) has type ISO 9:1995 transliteration (E55).
- “Αθήνα” (E41) has alternative form “Athina” (E41) has type transcription (E55).
|
First order logic:
|
First order logic:
- P139(x,y) ⇒ E41(x)
- P139(x,y) ⇒ E41(y)
- P139(x,y,z) ⇒ [P139(x,y) ∧ E55(z)]
- P139(x,y) ⇒ P139(y,x)
- ¬P139(x,x)
|
Properties:
P139.1 has type: E55 Type
|
Properties:
P139.1 has type: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E14 Condition Assessment. P34 concerned (was assessed by): E18 Physical ThingE16 Measurement. P39 measured (was measured by): E1 CRM EntityE17 Type Assignment. P41 classified (was classified by): E1 CRM Entity
|
Superproperty of:
E14 Condition Assessment. P34 concerned (was assessed by): E18 Physical ThingE16 Measurement. P39 measured (was measured by): E18 Physical ThingE17 Type Assignment. P41 classified (was classified by): E1 CRM Entity
|
Quantification:
|
Quantification:
|
Scope Note:
This property indicates the item to which an attribute or relation is assigned.
|
Scope Note:
This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity about which it made an attribution. The instance of E1 CRM Entity plays the role of the domain of the attribution. The kind of attribution made should be documented using P177 assigned property type.
|
Examples:
- February 1997 Current Ownership Assessment of Martin Doerr’s silver cup (E13) assigned attribute to Martin Doerr’s silver cup (E19)
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E19)
|
Examples:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned attribute to Martin Doerr’s silver cup (E22). (fictitious)
- The Identifier Assignment on 1st June 1997 of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E22). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned attribute to MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)
|
First order logic:
|
First order logic:
- P140(x,y) ⇒ E13(x)
- P140(x,y) ⇒ E1(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Superproperty of:
E14 Condition Assessment. P35 has identified (was identified by): E3 Condition StateE15 Identifier Assignment. P37 assigned (was assigned by): E42 IdentifierE15 Identifier Assignment. P38 deassigned (was deassigned by): E42 IdentifierE16 Measurement. P40 observed dimension (was observed in): E54 DimensionE17 Type Assignment. P42 assigned (was assigned by): E55 Type
|
Superproperty of:
E14 Condition Assessment. P35 has identified (was identified by): E3 Condition StateE15 Identifier Assignment. P37 assigned (was assigned by): E42 IdentifierE15 Identifier Assignment. P38 deassigned (was deassigned by): E42 IdentifierE16 Measurement. P40 observed dimension (was observed in): E54 DimensionE17 Type Assignment. P42 assigned (was assigned by): E55 Type
|
Quantification:
|
Quantification:
|
Scope Note:
This property indicates the attribute that was assigned or the item that was related to the item denoted by a property P140 assigned attribute to in an Attribute assignment action.
|
Scope Note:
This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity used in the attribution. The instance of E1 CRM Entity here plays the role of the range of the attribution. The kind of attribution made should be documented using P177 assigned property type.
|
Examples:
- February 1997 Current Ownership Assessment of Martin Doerr’s silver cup (E13) assigned Martin Doerr (E21)
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned object identifier 232
|
Examples:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned Martin Doerr (E21). (fictitious)
- The Identifier Assignment on 1st June 1997 of the silver cup donated by Martin Doerr (E15) assigned 232 (E42). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned unsupported (E55.) (Honey & Pickwoad, 2010)
|
First order logic:
|
First order logic:
- P141(x,y) ⇒ E13(x)
- P141(x,y) ⇒ E1(y)
|
|
|
|
Domain:
E15 Identifier Assignment
|
Domain:
E15 Identifier Assignment
|
Range:
|
Range:
|
Subproperty of:
E7 Activity. P16 used specific object (was used for): E70 Thing
|
Subproperty of:
E7 Activity. P16 used specific object (was used for): E70 Thing
|
Quantification:
|
Quantification:
|
Scope Note:
This property associates the event of assigning an instance of E42 Identifier to an entity, with the instances of E41 Appellation that were used as elements of the identifier.
|
Scope Note:
This property associates an instance of E15 Identifier Assignment with the instance of E90 Symbolic Object used as constituent of an instance of E42 Identifier in this act of assignment.
|
Examples:
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E15) used constituent “Guillaume, de Machaut” (E82)
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E15) used constituent “ca. 1300-1377” (E49)
|
Examples:
- Assigning the personal name identifier “Guillaume, de Machaut, ca. 1300-1377” on 1st June, 2001 (E15) used constituent “ca. 1300-1377” (E41). (Kelly, 2014)
- Assigning a uniform title to the anonymous textual work known as ‘The Adoration of the Shepherds’(E15) used constituent “Coventry” (E41). (Encyclopedia Britannica, 1998)
- Assigning a uniform title to Pina Bausch’s choreographic work entitled ‘Rite of spring’ (E15) used constituent “(Choreographic Work: Bausch)” (E90). (Brandstetter and Klein, 2015)
- Assigning a uniform title to the motion picture directed in 1933 by Merian C. Cooper and Ernest B. Schoedsack and entitled ‘King Kong’ (E15) used constituent “1933” (E61). (Goldner and Turner, 1976)
- Assigning the corporate name identifier ‘Univerza v Ljubljani. Oddelek za bibliotekarstvo’ to The Department for library science of the University of Ljubljana in 2018 (E15) used constituent “Univerza v Ljubljani” (E42). [Done by the Department of Library and Information Science and Book Studies Library, University of Ljubljana in 2018]
|
First order logic:
|
First order logic:
- P142(x,y) ⇒ E15(x)
- P142(x,y) ⇒ E90(y)
- P142(x,y) ⇒ P16(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the instance of E39 Actor that becomes member of a E74 Group in an E85 Joining. Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through P144 joined with (gained member by), E85 Joining, P143 joined (was joined by) to E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).
|
Scope Note:
This property identifies the instance of E39 Actor that becomes member of an instance of E74 Group in an instance of E85 Joining. Joining events allow for describing people becoming members of a group with the more detailed path E74 Group, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).
|
Examples:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined Sir Isaac Newton (E21)
- The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined Mikhail Sergeyevich Gorbachev (E21)
- The implementation of the membership treaty January 1. 1973 between EU and Denmark (E85) joined Denmark (E40)
|
Examples:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined Sir Isaac Newton (E21). (Iliffe, 2013)
- The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined Mikhail Sergeyevich Gorbachev (E21). (Galeotti, 1997)
- The implementation of the membership treaty 1st January 1973 between EU and Denmark (E85) joined Denmark (E74).
|
First order logic:
|
First order logic:
- P143(x,y) ⇒ E85(x)
- P143(x,y) ⇒ E39(y)
- P143(x,y) ⇒ P11(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining. Although a Joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through P144 joined with (gained member by), E85 Joining, P143 joined (was joined by) to E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of). The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group.
|
Scope Note:
This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining. Although a joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of). The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group.
|
Examples:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined with the Convention Parliament (E40)
- The inauguration of Mikhail Sergeyevich Gorbachev as Leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined with the office of Leader of the Union of Soviet Socialist Republics (USSR) (E40) with P144.1 kind of member President (E55)
- The implementation of the membership treaty January 1. 1973 between EU and Denmark (E85) joined with EU (E40)
|
Examples:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined with the Convention Parliament (E74). (Iliffe, 2013)
- The inauguration of Mikhail Sergeyevich Gorbachev as Leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined with the office of Leader of the Union of Soviet Socialist Republics (USSR) (E74) kind of member President (E55). (Galeotti, 1997)
- The implementation of the membership treaty 1st January 1973 between EU and Denmark (E85) joined with EU (E74).
|
First order logic:
|
First order logic:
- P144(x,y) ⇒ E85(x)
- P144(x,y)⇒ E74(y)
- P144(x,y,z) ⇒ [P144(x,y) ∧ E55(z)]
- P144(x,y) ⇒ P11(x,y)
|
Properties:
P144.1 kind of member: E55 Type
|
Properties:
P144.1 kind of member: E55 Type
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving.
|
Scope Note:
This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving.
|
Examples:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 separated Sir Isaac Newton
- George Washington’s leaving office in 1797 separated George Washington
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland February 1. 1985 (E86) separated Greenland (E40)
|
Examples:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated Sir Isaac Newton (E21). (Iliffe, 2013)
- George Washington’s leaving office in 1797 (E86) separated George Washington (E21). (Unger, 2015)
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1st February 1985 (E86) separated Greenland (E74).
|
First order logic:
|
First order logic:
- P145(x,y) ⇒ E86(x)
- P145(x,y) ⇒ E39(y)
- P145(x,y) ⇒ P11(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Subproperty of:
E5 Event. P11 had participant (participated in): E39 Actor
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving. Although a Leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well.
|
Scope Note:
This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving. Although a leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well.
|
Examples:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 separated from the Convention Parliament
- George Washington’s leaving office in 1797 separated from the office of President of the United States
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland February 1. 1985 separated from EU (E40)
|
Examples:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated from the Convention Parliament (E74). (Iliffe, 2013)
- George Washington’s leaving office in 1797 (E86) separated from the office of President of the United States (E74). (Unger, 2015)
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1st February 1985 (E86) separated from EU (E74).
|
First order logic:
|
First order logic:
- P146(x,y) ⇒ E86(x)
- P146(x,y) ⇒ E74(y)
- P146(x,y) ⇒ P11(x,y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
many to many, necessary (1,n:0,n)
|
Quantification:
many to many, necessary (1,n:0,n)
|
Scope Note:
This property associates an instance of E78 Collection or collections with subject of a curation activity following some implicit or explicit curation plan.
|
Scope Note:
This property associates an instance of E87 Curation Activity with the instance of E78 Curated Holding with that is subject of that curation activity following some implicit or explicit curation plan.
|
Examples:
- The activities (E87) by the Benaki Museum curated the acquisition of dolls and games of urban and folk manufacture dating from the 17th to the 20th century, from England, France and Germany for the “Toys, Games and Childhood Collection (E78) of the Museum
- The activities (E87) of the Historical Museum of Crete, Heraklion, Crete, curated the development of the permanent Numismatic Collection (E78)
- The activities (E87) by Mikael Heggelund Foslie curated the Mikael Heggelund Foslie’s coralline red algae Herbarium
|
Examples:
- The curation activity of the Benaki Museum for the Toys, Games and Childhood Collection (E87) curated The Toys, Games and Childhood Collection of the Benaki Museum (E78). [The curation activity included the acquisition of dolls and games of urban and folk manufacture dating from the 17th to the 20th century, from England, France and Germany for the Toys, Games and Childhood Collection of the museum.] (Benaki Museum, 2016)
- The curation activity for the permanent Numismatic Collection of the Historical Museum of Crete, Heraklion, Crete from 2005 up to the present (E87) curated the Numismatic Collection (E78). (Historical Museum of Crete, 2005)
- The curation activity of Mikael Heggelund Foslie (E87) curated the Mikael Heggelund Foslie’s coralline red algae Herbarium (E78) (Woelkerling et al., 2005)
|
First order logic:
|
First order logic:
- P147(x,y) ⇒ E87(x)
- P147(x,y) ⇒ E78(y)
|
|
|
|
Domain:
|
Domain:
|
Range:
|
Range:
|
Quantification:
|
Quantification:
|
Scope Note:
This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object.
|
Scope Note:
This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. This property is transitive.
|
Examples:
- Dante’s “Divine Comedy” (E89) has component Dante’s “Hell” (E89)
|
Examples:
- Dante’s “Divine Comedy” (E89) has component Dante’s “Hell” (E89). (Alighieri, 1956)
|
First order logic:
|
First order logic:
- P148(x,y) ⇒ E89(x)
- P148(x,y) ⇒ E89(y)
- [P148(x,y) ∧ P148(y,z)] ⇒ P148(x,z)
|
|
|
NOT MATCHED
|
Domain:
|
Domain:
|
Range:
E75 Conceptual Object Appellation
|
Range:
|
Subproperty of:
E1 CRM Entity. P1 is identified by (identifies): E41 Appellation
|
Subproperty of:
|
Quantification:
|
Quantification:
|
Scope Note:
This property identifies an instance of E28 Conceptual Object using an instance of E75 Conceptual Object Appellation.
|
Scope Note:
|
Examples:
- The German edition of the CIDOC CRM (E73) is identified by ISBN 978-3-00-030907-6 (E75)
|
Examples:
|
|
11 References:
Allen, J.. (1983) Maintaining knowledge about temporal intervals. Communications of the ACM, 26, pp. 832-843.
Gangemi, A., Guarino, N., Masolo, C., Oltramari, A., & Schneider, L. (2002) Sweetening ontologies with DOLCE. In A. Gómez-Pérez & V. R. Benjamins (eds), Knowledge Engineering and Knowledge Management. Ontologies and the Semantic Web, 13th International Conference, EKAW 2002, October 1-4, 2002, Siguenza, Spain, Proceedings. Lecture Notes in Computer Science 2473 Springer 2002, ISBN 3-540-44268-5: pp.166-181.
Smith, B. & Varzi, A.. (2000) Fiat and Bona Fide Boundaries. Philosophy and Phenomenological Research, 60: 2, pp. 401–420.
International Organization for Standardization (ISO). “ISO 639. Code for the Representation of Names of Languages”. Reference number: ISO 639:1988 (E/F). Geneva: International Organization for Standardization, 1988. iii + 17 pages.
International Organization for Standardization (ISO). “ISO 1000. SI units and recommendations for the use of their multiples and of certain other units.” Reference number: ISO 1000:1992. Geneva: International Organization for Standardization.
|
NOT MATCHED
|
|
12 APPENDIX
|
8 Appendix
Automatically generated text about Classes & Properties declarations |
|
13 Editorial notes
Editors: | Nick Crofts City of Geneva, Geneva, Switzerland | Martin Doerr, ICS-FORTH, Heraklion-Crete, Greece | Tony Gill RLG, Mountain View, CA, USA | Stephen Stead, Paveprime Ltd, London UK | Matthew Stiff English Heritage Swindon, UK |
Creation Date: 11-07-1998 Last Modified: 24-10-2003 The present version of the CIDOC CRM incorporates a series of amendments to version 3.2.1, submitted to ISO and accepted as Committee Draft ISO/CD 21127. These amendments were the result of a systematic exploration of the requirements for the intended scope of the CIDOC CRM as decided in summer 2001. This includes in particular documentation in Natural History, archaeology and the ability to communicate with traditional and Digital Libraries. These amendments have been developed and approved by the CIDOC CRM Special Interest Group, ISO/TC46/SC4/WG9 in a series of meetings together with various invited experts in the period from July 2001 to October 2003. With this version, the cycle of amendments to extend the functionality of the CIDOC CRM ends. The development team felt that the task to cover the intended scope as outlined in July 2001 and the general functionality required by members of the team up to now has been successfully fulfilled. Further amendments should only concern editorial changes to improve the clarity of the text. Therefore, the modelling constructs of the CIDOC CRM are expected to undergo no changes from this version until the final International Standard. With version 3.3.2, we have changed the format of the Definition of the CIDOC CRM. We present: - A general introduction to the model (as before)
- The hierarchy of entities as an indented list (as before)
- The hierarchy of properties as an indented list
- The definition of each entity
- The definition of each property.
We took out all cross-reference information, i.e. inherited properties, direct and inherited inverse references of properties at the range entity, as well as the indices to properties, alphabetically, by range and by domain. So this document remains the pure definition, whereas the full cross-referenced text will appear as an additional hypertext document, which will be semi-automatically generated. The reason for this change are: (1) the size of the cross-referenced document exceeds what one would normally print in one document. (2) the cross-referencing does not contribute to the definition. (3) Translators of the document are forced to manually trace the consistency of the cross-referencing, a nearly impossible task. The cross-referenced document is of course the only one, that allows for fully understanding the model by reading and for using it in conceptual modelling. We further removed the references to the metamodel under which the CIDOC CRM was initially developed. Even though the use of this metamodel has contributed a lot to the rigidity of developing the CIDOC CRM, it seems to be of minor importance for the use of the Model itself. Moreover it needs reworking, and metamodelling is still not a standard procedure in conceptual modelling. Therefore the development team decided not to make it a part of the standard to become. We present in the Annex the amendment history from version 3.2.1 on. This, together with the meeting minutes and the “issues list” on the CIDOC CRM home page, allows for tracing the correctness of this document with respect to the decisions of the development team. Automatically generated text about document contents |
NOT MATCHED
|
|