Model
type: Class
notation: CC1
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects created during the creative design phase in order to represent aesthetic concepts. The propositional content contained in a model provides information regarding an overall CC13 Design Concept and can be used to understand some aspect of the creator’s intent. Instances of this class are information objects produced as a result of design processes (instances of F28 Expression Creation) undertaken in relation to the goals of an instance of an overall CC15 Design Conception activity which, in turn, typically intends to comply with the specifications of an instance of CC6 Programme. As a subclass of F22 Self-Contained Expression, an instance of CC1 Model realizes, in whole or in part, the propositional content of the instance of CC13 Design Concept. As a subclass of CC5 Formulation, an instance of CC1 Model may function to project representations of the relations of space and materiality of the CC13 Design Concept, via CC12 Event Trigger Template, such that these representations can be used as guides for their eventual realization in some manufactured object.
subclass of: Formulation

Realization
type: Class
notation: CC2
comment: This class comprises the event of the instantiated realization of a planned artistic concept (CC20 Oeuvre), into an objective, concretized form (material and / or informational). This activity follows plans and projections delivered from one of more creative processes, such as CC14 Programme Conception, CC15 Design Conception and CC16 Realization Planning. Each of these is capable of delivering one or more outputs in the form of instances of CC5 Formulations which can be used by an instance of CC2 Realization to attempt to bring into existence the aimed for artistic object (E22 Human-made Object and/or E73 Information Object).

Realization Concept
type: Class
notation: CC3
comment: This class comprises combinations of concepts such as are found in planning documents, including BIM, details, drawings, sketches, diagrams, blueprints, descriptions, 3D representations etc. which altogether aim to describe an approach for realizing an artistic concept. The instance of CC3 Realization Concept is a complex set of ideas that is proposed as the intellectual response to a certain projected CC13 Design Concept, which has itself typically been expressed in a number of instances of CC1 Model. An instance of CC3 Realization Concept is the overall approach for how to interpret the latter into a plan for the design’s physical realization or materialization (CC2 Realization). An instance of CC3 Realization Concept is typically elaborated by an actor acting as the “Maitrise d’Oeuvre” through different planning documents (instances of CC4 Realization Plan) that represent particular aspects of the overall plan. In the normal case, one of these proposals will be selected (CC19 Assessment) as satisfying the CC13 Design Concept expressed in some particular set of instances of CC1 Model and will serve as the instance of CC4 Realization Plan that expresses the proposed CC3 Realization Concept. The substance of CC3 Realization Concept is ideas; with regards to realizing objects into reality, the ideas proposed typically deal with the planning of the execution of a CC1 Model into a physical object, while taking into account various real-world constraints regarding the organization of the events necessary to bring this end about (CC12 Event Trigger Template). An instance of CC3 Realization Concept is complex by nature as it interacts with the set of constraints expressed in one or more instances of CC1 Model that detail the conceptual and physical aspects of the spatial projection selected as expressing the CC13 Design Concept. The specific functionality of this class is to indicate the sets of concepts generated in order to plan the execution of an act of artistic reali…

Realization Plan
type: Class
notation: CC4
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects created during CC16 Realization Planning activities, in order to express and represent aspects of a projected CC2 Realization to be undertaken and its outcome. The propositional content contained in an instance of CC4 Realization Plan provides information regarding some aspect of an overall concept for a CC3 Realization Concept and can be used to understand the intent of the one who drafted the plan. Instances of this class are information objects produced as the result of realization planning processes (instances of F28 Expression Creation) undertaken in relation to the goals of an instance of an overall CC16 Realization Planning activity which, in turn, aims to comply with the specifications of an instance of CC1 Model. An instance of CC4 Realization Plan represents, in whole or in part, the propositional content of the instance of CC3 Realization Concept.
subclass of: Formulation

Formulation
type: Class
notation: CC5
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects generated during creative conception activities which project certain potential events and objects into the world. The propositional content contained in a formulation provides information which represents particular creative concepts proposed for a certain project and which may provide information pertaining to a projected generated object and the manner of its CC2 Realization. Instances of this class are information objects arising through an activity of F28 Expression Creation, undertaken in relation to the goals of an instance of CC9 Oeuvre Conception, aiming towards realizing a creative idea. An instance of CC5 Formulation represents, in whole or in part, the propositional content of the instance of CC20 Oeuvre.
subclass of: Plan

Programme
type: Class
notation: CC6
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects created during the creative programmation phase in order to express and represent CC17 Projective Requirements for a particular overall artistic project. This class comprises instances of information objects expressing projective requirements, wishes and needs for some CC20 Oeuvre in a formalized manner. A finalized, accepted CC6 Programme provides an expression of the requirements that will be employed to guide and constrain an eventual CC13 Design Concept. An instance of CC6 Programme comes into existence from an activity of expression creation (instance of F28 Expression Creation) and aims to represent, in whole or in part, the propositional content of the instance of CC17 Projective Requirements.
subclass of: Formulation

Oeuvre Conception
type: Class
notation: CC9
comment: This class comprises the evolution of a set of activities that aim towards the common intent of realizing a creative work in a broad sense. The coming into existence of an instance of CC9 Oeuvre Conception marks the initiation of an instance of CC20 Oeuvre. The latter intellectually gathers together the ideas and formulations contained in the various subworks (CC17 Projective Requirements, CC13 Design Concept, CC3 Realization Concept) and their formal expressions (CC6 Programme, CC1 Model, CC4 Realization Plan) that serve the common goal of the work’s final realization (CC2 Realization). In a commercial sphere, this is frequently undertaken with the participation of a client team acting as a client or patron and an executing team acting as a designer or service provider. An instance of this class often comes into being alongside the assignment of two groups as holding the roles of client and realizer who are formally attributed statuses as such. An associated ‘witness’ of such a will motivates the documentation of an instance of this event. Where possible, then, instances of CC9 Oeuvre Conception should be associated to instances of ZE6 Social Status through the property ZP75i is context for which document the actors causally implicated in willing the existence of the oeuvre and the roles that they play respectively, especially via their playing the role of client or patron / design or service provider. The instance of CC9 Oeuvre Conception is considered to be on-going and to encompass the sub-activities undertaken towards the realization of the main goal as long as the two parties continue to pursue this aim.

Object Trigger Template
type: Class
notation: CC11
comment: This class comprises specifications of projected artistic and architectural objects that detail constraints, specified as desired or necessary, that the projected object should comply with, according to a documented instance of CC5 Formulation. The function of CC11 Object Trigger Template is to allow the specification of qualities which the realized object should have such as dimension, material, function etc. The qualities specified here should be considered to stand as valid constraints to downstream and potentially upstream creative activities (CC14 Programme Conception, CC15 Design Conception, CC16 Realization Planning) within the context of an ongoing CC9 Oeuvre Conception, which can be used as to check conformity between desired and delivered outcomes ranging across realized plans (CC6 Programme, CC1 Model and CC4 Realization Plan) as well as the artistic object (E22 Human-made Object and/or E73 Information Object) finally generated through an act of CC2 Realization. For the documentation of the details of the constraints on the projected creation activity of a physical object (E22 Human-made Object), an associated instance of CC12 Event Trigger Template should be instantiated and connected through the property cp14i is stipulated object outcome.
subclass of: Propositional Object

Event Trigger Template
type: Class
notation: CC12
comment: This class comprises specifications of projected creative activities towards the CC2 Realization of a creative work. It details guidelines and constraints that downstream and upstream creative activities should comply with, according to a documented instance of CC5 Formulation. The specified constraints can be instantiated on the level of kinds of processes, items or qualities and quantities involved in the action. The qualities specified here should be considered to stand as valid constraints on downstream and potentially upstream creative activities (CC14 Programme Conception, CC15 Design Conception, CC16 Realization Planning) within the context of an ongoing CC9 Oeuvre, which can be used as a check of conformity between desired and delivered outcomes ranging across instances of CC5 Formulation subtypes (i.e., CC6 Programme, CC1 Model and CC4 Realization Plan) as well as the act of CC2 Realization itself, unless a newer instance of CC5 Formulation is created to supersede. An instance of an expected kind of outcome in terms of object, e.g. design or building, is typically implied in most instances of CC12 Event Trigger Template and should be documented via an instance of CC11 Object Trigger Template.
subclass of: Propositional Object

Design Concept
type: Class
notation: CC13
comment: This class comprises combinations of concepts found in creative expressions, such as drawings, sketches, diagrams, plans, descriptions, 3D representations etc, which together form an overall concept for a design. An instance of CC13 Design Concept is a complex set of ideas that is proposed as the intellectual response to a certain, projected creative aim, that may be documented as an instance of CC6 Programme, expressing the latter as particular creative design proposals. The CC13 Design Concept is typically elaborated by an actor in the role of ‘Maitrise d’Oeuvre’ through different design documents (instances of CC1 Model) that represent various aspects of the overall idea. The substance of CC13 Design Concept is ideas. An instance of CC13 Design Concept is complex by nature as it interacts with the set of requirements typically expressed in an instance of CC6 Programme, which concretizes the requirements set out by an instance of CC17 Projective Requirements. It is articulated through various documents expressing different collective proposals that will go through processes of selection and filtering. In the normal case, one of these proposals will be selected as satisfying the CC17 Projective Requirements expressed in a CC6 Programme and serve as the accepted instance(s) of CC1 Model that expresses the final CC13 Design Concept.

Programme Conception
type: Class
notation: CC14
comment: This class comprises the beginning of the evolution of a set of activities that aim towards the formulation of user or client’s (e.g.: a designated “Maîtrise d'Ouvrage”) needs, wishes and requirements for a projected CC20 Oeuvre. The substance of programming is intentional activity towards generated CC17 Projective Requirements that will typically be formally specified and approved in a requirements document, an instance of CC6 Programme. The instance of CC14 Programme Conception begins when the client starts to formulate their needs, with or without external party participation of the eventually designated realizing party (e.g., a designated ‘Maîtrise d'Oeuvre’).

Design Conception
type: Class
notation: CC15
comment: This class comprises the beginning of the evolution of a set of activities that aim towards the formulation of a creative design concept (CC13), realized in one or more instances of CC1 Model, that usually respond to an instance of CC17 Projective Requirements formulated for a projected creative work (CC20). The substance of design conception is intentional activity towards the formalization of a proposal detailing a (series of) model(s) (CC1) aiming to satisfy the initiating client’s requirements expressed in a formal programme (CC6). The instance of design conception begins when the actor charged with realizing the creative work (e.g.: the designated ‘Maîtrise d'Oeuvre’) starts the activities to formulate a design proposal, with or without an external party participating, which may or may not include the designated ‘Maîtrise d'Ouvrage’.

Realization Planning
type: Class
notation: CC16
comment: This class comprises the beginning of the evolution of a set of activities that aim towards the articulation of a CC3 Realization Concept, concretized in one or more CC4 Realization Plans, which aim to accurately incorporate a specific set of design documents (instances of CC1 Model) into a plan to realize a creative idea, typically as a physical work (E22 Human-made Object). The instance of this event begins when an actor, such as that designated ‘Maîtrise d'Oeuvre’, starts the activities of formulating the plan towards realization, with or without an external party participating, which may or may not include the ‘Maîtrise d'Ouvrage’.

Projective Requirements
type: Class
notation: CC17
comment: This class comprises distinct concepts or combinations of concepts embodying the aim, will and/or desire of an actor with regards to a particular projected CC20 Oeuvre. The instance of CC17 Projective Requirements is elicited from an actor either by him/herself or, more usually, with others, in order to express it in some concrete, documented form which will be used to guide the activities of a CC15 Design Conception. The substance of an instance of CC17 Projective Requirements is ideas in the sense of an articulated will, aim and desire with regards to a projected outcome, which is usually elaborated and reformulated over time in different iterations and derivations of the initial will, and finally realized in one or more CC6 Programmes, to be adopted as a guide in the design phase.

Assessment
type: Class
notation: CC19
comment: This class comprises acts of evaluation of an instance of E73 Information Object against an implicit or explicit standard by some actor. An instance of CC19 Assessment is undertaken in order to provide some form of feedback and evaluation on the assessed instance of E73 Information Object in the form of a categorical assessment, a reviewed information object or both. An act of assessment may result in the assignment of an evaluative categorical rank to the assessed conceptual pattern. An act of assessment may also result in a revised version of the assessed instance of E73 Information Object being produced by the assessor. The newly resultant assessed instance of E73 Information Object may include additions, deletions, modifications and commentaries relative to the original target of assessment. The resultant instance information object is, then, considered to incorporate elements of the original E73 Information Object. The edge cases of an act of assessment are the rejection or acceptance of the assessed E73 Information Object. In the case of rejection, the assessed information object has been categorized as a failure by the assessing actor, potentially terminating a direction of creation. In the case of approval, the assessed information object is considered to have been categorized as accepted in toto qua information object by the assessor, relative to the standard of evaluation. Acts of assessment are considered to generate and be generated by instances of F28 Expression Creation in a cycle that typically aims towards achieving an acceptance evaluation. Within the context of a cycle of creative processes, an act of assessment resulting in an assignment of approval typically indicates that the assessor considers the main idea and all relevant additional parameters of judgement with regards to the formulation of the object to be satisfactory and to express the instance of F15 Complex Work which it was formulated to materialize.

Oeuvre
type: Class
notation: CC20
comment: This class comprises combinations of concepts that together represent a recognizable novel intellectual content that is intended to be realized into a particular physical or conceptual form. The substance of an instance of this class is its unique set of ideas. An instance of this class is complex in that it is typically composed of a set of other ideas which together form its content. An instance of CC20 Oeuvre is typically formed of member works consisting of a CC17 Project Requirement, CC13 Design Concept and a CC4 Realization Plan. Together these works are progressively realized in order to be able to bring into existence a particular creation, physical or intellectual, through a CC2 Realization act. An instance of this class comes to be through its initiation by an activity of creation (CC9 Oeuvre Conception) which, in turn, entails the willing of the realization of this idea by one or more parties acting as patrons and service providers in turn. The substance of CC20 Oeuvre is ideas. An instance of CC20 Oeuvre represents the most abstract level of a creative intellectual project, and gathers together all the particular ideas created towards its expression into a larger whole. CC20 Oeuvre stands apart from any individual physical or intellectual creation undertaken in the elaboration of a creative idea and stands for the idea itself. The documentation of an instance of CC20 Oeuvre thus allows both for the richer elaboration of the elements that lead to an eventual physical or intellectual instantiation of the idea through tracing the individual processes and components leading to a final as well as supporting the possibility to document partially realized or mostly unrealized creative projects.

CRM Entity
type: Class
notation: E1
comment: 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 identifierClassification 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 propertiesAll other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity.
subclass of: Thing

Physical Thing
type: Class
notation: E18
comment: 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.
subclass of: Legal Object
subclass of: Material Substantial

Physical Feature
type: Class
notation: E26
comment: 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”.
subclass of: Physical Thing

Site
type: Class
notation: E27
comment: 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.
subclass of: Physical Feature
subclass of: Rigid Physical Feature

Conceptual Object
type: Class
notation: E28
comment: 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.
subclass of: Human-Made Thing

Design or Procedure
type: Class
notation: E29
comment: 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 followingA schema for the activities it describesA 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.
subclass of: Information Object

Actor
type: Class
notation: E39
comment: 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.
subclass of: Persistent Item

Time-Span
type: Class
notation: E52
comment: 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.
subclass of: CRM Entity

Place
type: Class
notation: E53
comment: This class comprises extents in the natural space we live in, in particular on the surface of the Earth, 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).
subclass of: CRM Entity

Dimension
type: Class
notation: E54
comment: 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 …
subclass of: CRM Entity

Type
type: Class
notation: E55
comment: 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.
subclass of: Conceptual Object

Material
type: Class
notation: E57
comment: 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.
subclass of: Type

Thing
type: Class
notation: E70
comment: 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.
subclass of: Persistent Item

Human-Made Thing
type: Class
notation: E71
comment: 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.
subclass of: Thing

Legal Object
type: Class
notation: E72
comment: 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.
subclass of: Thing

Information Object
type: Class
notation: E73
comment: 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.
subclass of: Propositional Object
subclass of: Symbolic Object

Persistent Item
type: Class
notation: E77
comment: 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 used should 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 or 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 ex…
subclass of: CRM Entity

Propositional Object
type: Class
notation: E89
comment: 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.
subclass of: Conceptual Object

Symbolic Object
type: Class
notation: E90
comment: 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).
subclass of: Conceptual Object
subclass of: Legal Object

Expression
type: Class
notation: F2
comment: This class comprises the intellectual or artistic realisations of Works in the form of identifiable immaterial objects, such as texts, poems, jokes, musical or choreographic notations, movement pattern, sound pattern, images, multimedia objects, or any combination of such forms. The substance of F2 Expression is signs.An Expression is the outcome of the intellectual or creative process of realizing a Work. Subsequent expressions conveying the same work may be created over time.Expressions do not depend on a specific physical carrier and can exist on one or more carriers simultaneously. As far as bibliographic practice is concerned, only instances of F2 Expression that are externalised on physical carriers other than both the creator’s brain and an auditor’s brain are taken into account.The form of F2 Expression is an inherent characteristic of the F2 Expression. Differences in form imply different Expressions (e.g., from text to spoken word, a transcript of a recording). Similarly, differences in language or means of performance imply different Expressions (e.g., translations or arrangements for different instruments). Thus, if a text is revised or modified, the result is considered to be a new F2 Expression. While theoretically any change in signs will result in a new Expression, conventionally the context and use will determine the rules for distinguishing among expressions.An instance of F2 Expression which includes spoken or written text may be multiply instantiated as an instance of E33 Linguistic Object. This allows for the association of the E56 Language of the text with the instance of F2 Expression by using the property P72 has language (is language of).
subclass of: Information Object

Material Substantial
type: Class
notation: S10
comment: This class comprises constellations of matter with a relative stability of any form sufficient to associate them with a persistent identity, such as being confined to certain extent, having a relative stability of form or structure, or containing a fixed amount of matter. In particular, it comprises physical things in the narrower sense and fluid bodies. It is an abstraction of physical substance for solid and non-solid things of matter.
subclass of: Thing
subclass of: Observable Entity

Observable Entity
type: Class
notation: S15
comment: This class comprises instances of E5 Event or S10 Material Substantial (i.e. items or phenomena, such as physical things, their behaviour, states and interactions or events), that can be observed by measurement or detection devices or by human sensory impression including when enhanced by tools. In order to be observable, instances of E5 Event must consist of some interaction or action of material substance. In some cases, the spatiotemporal confinement of the event itself, such as a flash, a car stopping etc. marks the limits of a documented observation of an event. In other cases, such as the situation of a car passing by a certain object, the spatiotemporal limits of the event of observing itself, as well as the direction of attention or the orientation of used instruments, may constrain the observed detail of a larger process, e.g., noticing the sight of a car passing by; a light emission, etc. Conceptual objects manifest through their carriers such as books, digital media, or even human memory. Attributes of conceptual objects, such as number of words, can be observed on their carriers. If the respective properties between carriers differ, either they carry different instances of conceptual objects or the difference can be attributed to accidental deficiencies in one of the carriers. In that sense even immaterial objects are observable. By this model we address the fact that frequently, the actually observed carriers of conceptual objects are not explicitly identified in documentation, i.e., they are assumed to have existed but they are unknown as individuals.
subclass of: CRM Entity

Rigid Physical Feature
type: Class
notation: S20
comment: Any instance of this class is a physical feature with sufficient stability of form in itself and with respect to the physical object bearing it in order to associate a permanent reference space within which its form is invariant and at rest. The maximum volume in space that an instance of S20 Rigid Physical Feature occupies defines uniquely a place for the feature with respect to its surrounding matter. Therefore we model S20 Rigid Physical Feature as a subclass of E26 Physical Feature and of E53 Place. The latter is intended as a phenomenal place as defined in CRMgeo (Doerr and Hiebel 2013). By virtue of this multiple inheritance we can discuss positions relative to the extent of an instance of S20 Rigid Physical Feature without representing each instance of it together with an instance of its associated place. However, since the identity and existence of this place depends uniquely on the identity of the instance of S20 Rigid Physical Feature as matter, this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language. It shortcuts an implicit self-referential path from E26 Physical Feature through P156 occupies, E53 Place, P157 is at rest relative to E26 Physical Feature. In cases of instances of S20 Rigid Physical Feature on or in the surface of earth, the default reference is typically fixed to the closer environment of the tectonic plate or sea floor. In cases of features on mobile objects, the reference space is typically fixed to the geometry of the bearing object. Note that the reference space associated with the instance of S20 Rigid Physical Feature may quite well be deformed over time, as long the continuity of its topology does not become unclear, such as the compression of dinosaur bones in geological layers, or the distortions of the hull of a ship by the waves of the sea. Defined in this way, the reference space can be used as a means to infer from current topological relationships past topologic…
subclass of: Physical Feature
subclass of: Place

Thing
type: Class
notation: Thing
comment: The class of OWL individuals.

Plan
type: Class
notation: ZE59
comment: Instances of this class comprise symbolically expressed (whether in writing, orally or in some other recognized symbolic system within a socio-cultural group) projections of futural events and objectivities. An instance of this class is an intellectual object which describes a not yet extant futural world and describes how it is projected to be. A plan foresees what is foreseen to be brought about or to take place given certain eventualities. The content of a plan expressed as a machine-readable string can be documented in relation to an instance of this object via the property P190 has symbolic content. The content of a plan can further be expressed in more analytic format by connecting it to a projected instance of Event Trigger Template which describes the particular set of parameters which are envisioned to take place when the plan would be executed. An instance of plan comes into existence when it is symbolically formulated in some real instantiation and ceases to exist when no further carriers or memory of it remain.
subclass of: Design or Procedure
subclass of: Expression

projects
type: Property
range:
  ressource: Event Trigger Template
comment: This property describes the relation between a CC5 Formulation and a projected event it plans for. Instances of CC5 Formulation may contain detailed, analytic information regarding how the plan formulates an intended event, or set of events, to occur, documenting also how and under what conditions a specific event can be said to have taken place and achieved according to a set of agreed terms. By instantiating this property, an activity plan can be connected to the analytic information it details for the projected manner of execution of the event that it foresees.
domain:
  ressource: Plan

stipulates type of object outcome
type: Property
range:
  ressource: Type
comment: This property describes what type of object has been stipulated in a CC12 Event Trigger Template, as expected to be brought into existence through the event it projects. The form of stipulation is categorical, specifying a kind of object to be produced but not its particular features.
domain:
  ressource: Event Trigger Template

stipulates event type
type: Property
range:
  ressource: Type
comment: This property describes what form of activity the projected event is expected to consist in, stipulating its basic nature such as: production, communication, design.
domain:
  ressource: Event Trigger Template

stipulates actor type
type: Property
range:
  ressource: Type
comment: This property describes the kind(s) of actor that a projected activity is foreseen to involve. It thus allows the description of kinds of participants in the foreseen event at the categorical level. A plan may, thus, call for a certain type of professional to be involved, a certain category of individual etc.
domain:
  ressource: Event Trigger Template

stipulates place
type: Property
range:
  ressource: Place
comment: This property describes the expected, real-world place where the projected event is supposed to occur.
domain:
  ressource: Event Trigger Template

stipulates time-span
type: Property
range:
  ressource: Time-Span
comment: This property describes the expected time-span within which the projected event is supposed to occur.
domain:
  ressource: Event Trigger Template

stipulates actor
type: Property
range:
  ressource: Actor
comment: This property describes instances of particular individuals persons or groups that are expected to participate within the projected event.
domain:
  ressource: Event Trigger Template

stipulates equipment
type: Property
range:
  ressource: Physical Thing
comment: This property describes instances of equipment (E18) that are stipulated as expected to be used in the carrying out of the projected event.
domain:
  ressource: Event Trigger Template

stipulates particular method
type: Property
range:
  ressource: Design or Procedure
comment: This property describes instances of design or procedures that are stipulated to be followed in the carrying out of the projected event.
domain:
  ressource: Event Trigger Template

stipulates specific budget
type: Property
range:
  ressource: Dimension
comment: This property describes the budget that is stipulated as a constraint to the carrying out of the projected event.
domain:
  ressource: Event Trigger Template

stipulates object outcome
type: Property
range:
  ressource: Object Trigger Template
comment: This property relates an instance of Event Trigger Template to an instance of Objecter Trigger Template that is specified to be an outcome of the projected event.
domain:
  ressource: Event Trigger Template

stipulates sub-event
type: Property
range:
  ressource: Event Trigger Template
comment: This property enables the documentation of planned sub-events stipulated as part of an overall projected event. It is used to link an instance of Event Trigger Template to another instance of this class which would be an element of its own execution. The intention of this property is to enable the modelling of the projection of a complex event with sub-elements.
domain:
  ressource: Event Trigger Template

stipulates material
type: Property
range:
  ressource: Material
comment: This property describes the material of which the projected object is expected to be comprised.
domain:
  ressource: Object Trigger Template

stipulates site
type: Property
range:
  ressource: Site
comment: This property describes a particular real world site at which the projected object is expected to be installed or placed.
domain:
  ressource: Object Trigger Template

stipulates dimension
type: Property
range:
  ressource: Dimension
comment: This property describes the expected dimensions of the projected object.
domain:
  ressource: Object Trigger Template

stipulates function
type: Property
range:
  ressource: Type
comment: This property describes the expected function of the projected object.
domain:
  ressource: Object Trigger Template

stipulates reference
type: Property
range:
  ressource: Information Object
comment: This property associates an instance of Object Trigger Template with an Information Object which is to be used as a reference in the making of the projected object. The end result should show similarity to the referenced object
domain:
  ressource: Object Trigger Template

stipulates part
type: Property
range:
  ressource: Object Trigger Template
comment: This property enables the documentation of expected parts of a planned object and the particular features of those parts.
domain:
  ressource: Object Trigger Template

assessed
type: Property
range:
  ressource: Information Object
comment: This property indicates that an assessment activity was carried out on an instance of information object.
domain:
  ressource: Assessment

produced revision
type: Property
range:
  ressource: Information Object
comment: This property indicates that a new information object was created out of an assessment activity. The generated instance of information object will incorporate the assessed information object but may have added, removed, or modified its content as part of the assessment activity.
domain:
  ressource: Assessment

concerns extant object
type: Property
range:
  ressource: Physical Thing
comment: This property describes instances of things that are the main object concerned in the realization of the projected new configuration of an extant object. The execution of the object template may result in modification or transformation of the object indicated by this property.
domain:
  ressource: Object Trigger Template

was projected by
type: Property
range:
  ressource: Plan
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the relation between a CC5 Formulation and a projected event it plans for. Instances of CC5 Formulation may contain detailed, analytic information regarding how the plan formulates an intended event, or set of events, to occur, documenting also how and under what conditions a specific event can be said to have taken place and achieved according to a set of agreed terms. By instantiating this property, an activity plan can be connected to the analytic information it details for the projected manner of execution of the event that it foresees.
domain:
  ressource: Event Trigger Template

is type of object outcome stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes what type of object has been stipulated in a CC12 Event Trigger Template, as expected to be brought into existence through the event it projects. The form of stipulation is categorical, specifying a kind of object to be produced but not its particular features.
domain:
  ressource: Type

is event type stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes what form of activity the projected event is expected to consist in, stipulating its basic nature such as: production, communication, design.
domain:
  ressource: Type

is actor type stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the kind(s) of actor that a projected activity is foreseen to involve. It thus allows the description of kinds of participants in the foreseen event at the categorical level. A plan may, thus, call for a certain type of professional to be involved, a certain category of individual etc.
domain:
  ressource: Type

is place stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the expected, real-world place where the projected event is supposed to occur.
domain:
  ressource: Place

is time-span stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the expected time-span within which the projected event is supposed to occur.
domain:
  ressource: Time-Span

is actor stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes instances of particular individuals persons or groups that are expected to participate within the projected event.
domain:
  ressource: Actor

is equipment stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes instances of equipment (E18) that are stipulated as expected to be used in the carrying out of the projected event.
domain:
  ressource: Physical Thing

is particular method stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes instances of design or procedures that are stipulated to be followed in the carrying out of the projected event.
domain:
  ressource: Design or Procedure

is budget stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the budget that is stipulated as a constraint to the carrying out of the projected event.
domain:
  ressource: Dimension

is object outcome stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property relates an instance of Event Trigger Template to an instance of Objecter Trigger Template that is specified to be an outcome of the projected event.
domain:
  ressource: Object Trigger Template

is sub-event stipulated by
type: Property
range:
  ressource: Event Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property enables the documentation of planned sub-events stipulated as part of an overall projected event. It is used to link an instance of Event Trigger Template to another instance of this class which would be an element of its own execution. The intention of this property is to enable the modelling of the projection of a complex event with sub-elements.
domain:
  ressource: Event Trigger Template

is material stipulated by
type: Property
range:
  ressource: Object Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the material of which the projected object is expected to be comprised.
domain:
  ressource: Material

is site stipulated by
type: Property
range:
  ressource: Object Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes a particular real world site at which the projected object is expected to be installed or placed.
domain:
  ressource: Site

is dimension stipulated by
type: Property
range:
  ressource: Object Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the expected dimensions of the projected object.
domain:
  ressource: Dimension

is function stipulated by
type: Property
range:
  ressource: Object Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the expected function of the projected object.
domain:
  ressource: Type

is reference stipulated by
type: Property
range:
  ressource: Object Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Object Trigger Template with an Information Object which is to be used as a reference in the making of the projected object. The end result should show similarity to the referenced object
domain:
  ressource: Information Object

is part stipulated by
type: Property
range:
  ressource: Object Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property enables the documentation of expected parts of a planned object and the particular features of those parts.
domain:
  ressource: Object Trigger Template

was assessed by
type: Property
range:
  ressource: Assessment
comment: This property is the inverse of the forward property described in the scope note that follows. This property indicates that an assessment activity was carried out on an instance of information object.
domain:
  ressource: Information Object

was revision produced by
type: Property
range:
  ressource: Assessment
comment: This property is the inverse of the forward property described in the scope note that follows. This property indicates that a new information object was created out of an assessment activity. The generated instance of information object will incorporate the assessed information object but may have added, removed, or modified its content as part of the assessment activity.
domain:
  ressource: Information Object

is object of concern of
type: Property
range:
  ressource: Object Trigger Template
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes instances of things that are the main object concerned in the realization of the projected new configuration of an extant object. The execution of the object template may result in modification or transformation of the object indicated by this property.
domain:
  ressource: Physical Thing