SDHSS CIDOC CRM supplement (v1.0)
type: Ontology
version info: Exported from OntoME: SDHSS CIDOC CRM supplement (v1.0)
comment: Classes and properties in this namespace explain the use of CIDOC CRM class types, from the perspective of connecting class types to controlled vocabularies.

Duration
type: Class
notation: C1
comment: A time length. A duration is a specialisation of E54 Dimension providing a measure of time.
subclass of: Dimension

Time unit
type: Class
notation: C2
comment: A measurement unit of durations and periods of time like second, hour, day, year or century
subclass of: Type
subclass of: Measurement Unit

Activity Type
type: Class
notation: C3
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E7 Activity class.
subclass of: Type

Physical Human-Made Thing Type
type: Class
notation: C4
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E23 Physical Human-Made Thing class.
subclass of: Type

Item Type
type: Class
notation: C5
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of F5 Item.
subclass of: Type

Expression Type
type: Class
notation: C6
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the Expression – F2 class.
subclass of: Type

Digital Object Type
type: Class
notation: C7
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the Expression – F2 class.
subclass of: Type

Type of manifestation product type
type: Class
notation: C8
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the Manifestation Product Type – F3 class.
subclass of: Type

Group Type
type: Class
notation: C9
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the 'crm:E74 Group'.
subclass of: Type

Manifestation Singleton Type
type: Class
notation: C10
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of F4 Manifestation Singleton.
subclass of: Type

Numeric dimension
type: Class
notation: C11
comment: A numeric dimension is a specialisation of the crm:E54 Dimension class modeling measured quantities like the number (of items) or a percentage, that have, strictly speaking, no measurement unit but need to be specified by a type in order to capture the meaning of the measured value. E.g. 10 has not the same meaning as number (of items) or percentage. A specific vocabulary will allow to distinguish between the different scenarios.
subclass of: Dimension

Numeric dimension type
type: Class
notation: C12
comment: This class model the type of a numeric dimension without measurement unit. Its instances, like number (of items), percentage, permille (per thousand), etc. allow to understand the meaning of the measured quantity.
subclass of: Measurement Unit

Length
type: Class
notation: C13
comment: A measure of length. A lenght is a specialisation of E54 Dimension providing a measure of distance, height, etc.
subclass of: Dimension

Length measurement unit
type: Class
notation: C14
comment: A measurement unit of length like mile, inch, meter, micron, etc.
subclass of: Measurement Unit

Weight
type: Class
notation: C15
comment: Amount a thing weighs
subclass of: Dimension

Weight measurement unit
type: Class
notation: C16
comment: The measurement unit of weight, like pound, kilogram, etc.
subclass of: Measurement Unit

Area
type: Class
notation: C17
comment: Measurable amount of space of a flat surface
subclass of: Dimension

Area measurement unit
type: Class
notation: C18
comment: The measurement unit of an area, e.g. a square yard, acre, square meter, hectare, etc.
subclass of: Measurement Unit

Volume measurement unit
type: Class
notation: C19
comment: A measurement unit of volume, like pint, liter, gallon, etc.
subclass of: Measurement Unit

Volume
type: Class
notation: C20
comment: Amount of space that an object fills or a container has
subclass of: Dimension

Monetary amount
type: Class
notation: C21
comment: This class models any measurable monetary value. It is equivalent to the crm:E97 Monetary amount class, defined as "This class comprises quantities of monetary possessions or obligations in terms of their nominal value with respect to a particular currency. [...]" in CIDOC CRM version 6.2.9.
subclass of: Dimension

Currency
type: Class
notation: C22
comment: This class models a social object allowing to standardize the money used in a community or country. It is equivalent to crm:E98 currency defined as "This class comprises the units in which a monetary system, supported by an administrative authority or other community, quantifies and arithmetically compares all monetary amounts declared in the unit. [...]" in CIDOC CRM version 6.2.9.
subclass of: Measurement Unit

Identifier Type
type: Class
notation: C24
comment: A type of identifier(social security number, database identifier, etc.). For URIs in the sense of the Semantic Web, cf. the subclass of identifier crm-sup:C30 Uniform Resource Identifier (URI) which should be preferred.
subclass of: Type

Collection Type
type: Class
notation: C26
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E78 Collection class.
subclass of: Type

Dimension Type
type: Class
notation: C27
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E54 Dimension class.
subclass of: Type

Information Object Type
type: Class
notation: C28
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E54 Information Object Type class.
subclass of: Type

Performance Type
type: Class
notation: C29
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the frbroo:F31 Performance class.
subclass of: Type

Uniform Resource Identifier (URI)
type: Class
notation: C30
comment: A Uniform Resource Identifier (URI) is a unique sequence of characters that identifies a logical or physical resource used by Semantic Web technologies.
subclass of: Identifier

Move Type
type: Class
notation: C31
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E9 Move class.
subclass of: Type

Observed Entity Type
type: Class
notation: C32
comment: This class comprises types of observed entities.
subclass of: Type

Serial Work Type
type: Class
notation: C33
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the frbroo:F18 Serial Work class.
subclass of: Type

Purpose
type: Class
notation: C34
comment: This class comprises types of purposes for activities or mentioned in texts, etc. The purposed themselves, as individuals, should be expressed as propositional objects and the present concepts classify several purposes belonging to the same type.
subclass of: Type
notation: C37
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E5 Event class. This kind of types are useful for providing the identity of generic instances of the Event class. If specific properties related to a specific Event type are needed, then a subclass of Event should be produced.
label: Event Type

Propositional Object Type
type: Class
notation: C35
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E89 Propositional Object class.
subclass of: Type

Person Type
type: Class
notation: C36
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of the crm:E21 Person. This class should not be used to express activities, social roles or institutional functions of persons (for these there are specific classes), but only to provide a generally acceptable classification of sets of persons in the perspective of a research question.
subclass of: Type

Digital Object
type: Class
notation: D1
comment: This class comprises identifiable immaterial items that can be represented as sets of bit sequences, such as data sets, e-texts, images, audio or video items, software, etc., and are documented as single units. Any aggregation of instances of D1 Digital Object into a whole treated as single unit is also regarded as an instance of D1 Digital Object. This means that for instance, the content of a DVD, an XML file on it, and an element of this file, are regarded as distinct instances of D1 Digital Object, mutually related by the P106 is composed of (forms part of) property. A D1 Digital Object does not depend on a specific physical carrier, and it can exist on one or more carriers simultaneously.

Digitization Process
type: Class
notation: D2
comment: This class comprises events that result in the creation of instances of D9 Data Object that represent the appearance and/or form of an instance of E18 Physical Thing such as paper documents, statues, buildings, paintings, etc. A particular case is the analogue-to-digital conversion of audiovisual material. This class represents the transition from a material thing to an immaterial representation of it. The characteristic subsequent processing steps on digital objects are regarded as instances of D3 Formal Derivation.

Formal Derivation
type: Class
notation: D3
comment: This class comprises events that result in the creation of a D1 Digital Object from another one following a deterministic algorithm, such that the resulting instance of digital object shares representative properties with the original object. In other words, this class describes the transition from an immaterial object referred to by property L21 used as derivation source (was derivation source for) to another immaterial object referred to by property L22 created derivative (was derivative created by) preserving the representation of some things but in a different form. Characteristic examples are colour corrections, contrast changes and resizing of images.

Digital Machine Event
type: Class
notation: D7
comment: This class comprises events that happen on physical digital devices following a human activity that intentionally caused its immediate or delayed initiation and results in the creation of a new instance of D1 Digital Object on behalf of the human actor. The input of a D7 Digital Machine Event may be parameter settings and/or data to be processed. Some D7 Digital Machine Events may form part of a wider E65 Creation event. In this case, all machine output of the partial events is regarded as creation of the overall activity.

Digital Device
type: Class
notation: D8
comment: This class comprises identifiable material items such as computers, scanners, cameras, etc. that have the capability to process or produce instances of D1 Digital Object.

Data Object
type: Class
notation: D9
comment: This class comprises instances of D1 Digital Object that are the direct result of a digital measurement or a formal derivative of it, containing quantitative properties of some physical things or other constellations of matter.

Software Execution
type: Class
notation: D10
comment: This class comprises events by which a digital device runs a software program or a series of computing operations on a digital object as a single task, which is completely determined by its digital input, the software and the generic properties of the device.

Digital Measurement Event
type: Class
notation: D11
comment: This class comprises actions measuring physical properties using a digital device, that are determined by a systematic procedure and creates an instance of D9 Data Object, which is stored on an instance of D13 Digital Information Carrier. In contrast to instances of D10 Software Execution, environmental factors have an intended influence on the outcome of an instance of D11 Digital Measurement Event. Measurement devices may include running distinct software, such as the RAW to JPEG conversion in digital cameras. In this case, the event is regarded as instance of both classes, D10 Software Execution and D11 Digital Measurement Event.

Data Transfer Event
type: Class
notation: D12
comment: This class comprises events that transfer a digital object from one digital carrier to another. Normally, the digital object remains the same. If in general or by observation the transfer implies or has implied some data corruption, the change of the digital objects may be documented distinguishing input and output rather than instantiating the property L14 transferred (was transferred by).

Digital Information Carrier
type: Class
notation: D13
comment: This class comprises all instances of E84 Information Carrier that are explicitly designed to be used as persistent digital physical carriers of instances of D1 Digital Object. A D13 Digital Information Carrier may or may not contain information, e.g., an empty diskette.

Software
type: Class
notation: D14
comment: This class comprises software codes, computer programs, procedures and functions that are used to operate a system of digital objects.

Person Name
type: Class
notation: D21
comment: This class comprises the proper noun name that identifies a person that acts as an entity.

Annotation Object
type: Class
notation: D29
comment: This class comprises objects that make propositions about other artefacts.Instances of this class are not the attributes themselves, by which things are annotated, but represent the connection between the concepts related in a proposition, and the activities of creation, modification and deletion.This class is specialized by appropriate subclasses to express more specific relationships between annotated things, such as knowledge object, same as etc.

Annotation Event
type: Class
notation: D30
comment: This class comprises events that describe the creation of associations (“Annotation Objects”) between objects or areas of objects of the Repository, with other objects or regions or persons, places, events. It is the event that creates the Annotation Object.

Area
type: Class
notation: D35
comment: This class describes a part (of any shape or size) of interest in basically any media object stored in the Object Repository, i.e., a text, an image, a video or a 3D model. It points to content consisting of just a portion or area of a file. In some contexts, however, the area can also point to content represented by an integral (i.e., proper) file. It is equal to the METS AREA element.

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 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.

Temporal Entity
type: Class
notation: E2
comment: This class comprises all phenomena, such as the instances of E4 Periods, E5 Events and states, 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 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, 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.

Condition State
type: Class
notation: E3
comment: 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”.

Period
type: Class
notation: E4
comment: 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 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 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. As the actual extent of an 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 disconnec…

Event
type: Class
notation: E5
comment: 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.

Destruction
type: Class
notation: E6
comment: 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.

Activity
type: Class
notation: E7
comment: 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.

Acquisition
type: Class
notation: E8
comment: 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.

Move
type: Class
notation: E9
comment: 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.

Transfer of Custody
type: Class
notation: E10
comment: 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.

Modification
type: Class
notation: E11
comment: 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.

Production
type: Class
notation: E12
comment: 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.

Attribute Assignment
type: Class
notation: E13
comment: 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.

Condition Assessment
type: Class
notation: E14
comment: 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.

Identifier Assignment
type: Class
notation: E15
comment: 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. 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.

Measurement
type: Class
notation: E16
comment: This class comprises actions measuring physical properties and other values that can be determined by a systematic procedure. 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.

Type Assignment
type: Class
notation: E17
comment: 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.

Physical Thing
type: Class
notation: E18
comment: 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. An instance of E18 Physical Thing occupies not only a particular geometric space, 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. Physical things consisting of aggregations of physically unconnected objects, such as a set of chessmen, occupy a number of individually contiguous spacetime volumes equal to the number of unconnected objects that constitute the set. We model E18 Physical Thing to be a subclass of E72 Legal Object and of E92 Spacetime volume. The latter is intended as a phenomenal spacetime volume as defined in CRMgeo (Doerr and Hiebel 2013). By virtue of this multiple inheritance we can discuss the physical extent of an E18 Physical Thing 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 E18 Physical Thing is matter while a spacetime volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance of E18 Physical Thing 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 E18 Physical Thing. Therefore this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language. The CIDOC C…

Physical Object
type: Class
notation: E19
comment: 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.

Person
type: Class
notation: E21
comment: 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.

Man-Made Object
type: Class
notation: E22
comment: 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.

Physical Man-Made Thing
type: Class
notation: E24
comment: 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.

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”.

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.

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 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 has association with (is associated with). Designs or procedures can be seen as one of the following: 1. A schema for the activities it describes2. A schema of the products that result from their application.3. 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.

Right
type: Class
notation: E30
comment: This class comprises legal privileges concerning material and immaterial things or their derivatives. These include reproduction and property rights

Document
type: Class
notation: E31
comment: 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.

Authority Document
type: Class
notation: E32
comment: This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.

Linguistic Object
type: Class
notation: E33
comment: 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

Title
type: Class
notation: E35
comment: 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.

Visual Item
type: Class
notation: E36
comment: 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.

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. 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.

Legal Body
type: Class
notation: E40
comment: 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.

Appellation
type: Class
notation: E41
comment: 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. 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

Identifier
type: Class
notation: E42
comment: 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.

Place Appellation
type: Class
notation: E44
comment: 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.

Section Definition
type: Class
notation: E46
comment: 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 ).

Time Appellation
type: Class
notation: E49
comment: 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’.

Contact Point
type: Class
notation: E51
comment: 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.

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. 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.

Place
type: Class
notation: E53
comment: 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.

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. 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.

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 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.

Language
type: Class
notation: E56
comment: 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.

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). 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.

Measurement Unit
type: Class
notation: E58
comment: 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.

Number
type: Class
notation: E60
comment: 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

Time Primitive
type: Class
notation: E61
comment: 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.

String
type: Class
notation: E62
comment: 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

Beginning of Existence
type: Class
notation: E63
comment: 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.

End of Existence
type: Class
notation: E64
comment: 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.

Creation
type: Class
notation: E65
comment: 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.

Formation
type: Class
notation: E66
comment: 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.

Birth
type: Class
notation: E67
comment: 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.

Dissolution
type: Class
notation: E68
comment: 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.

Death
type: Class
notation: E69
comment: 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.

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.

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

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 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.

Information Object
type: Class
notation: E73
comment: 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. The encoding structure known as a "named graph" also falls under this class, so that each "named graph" is an instance of an E73 Information Object.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.

Group
type: Class
notation: E74
comment: This class comprises any gatherings or organizations of E39 Actors 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 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.

Conceptual Object Appellation
type: Class
notation: E75
comment: This class comprises appellations that are by their form or syntax specific to identifying instances of E28 Conceptual Object, such as intellectual products, standardized patterns etc.

Persistent Item
type: Class
notation: E77
comment: 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.

Collection
type: Class
notation: E78
comment: 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.

Part Addition
type: Class
notation: E79
comment: 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.

Part Removal
type: Class
notation: E80
comment: 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.

Transformation
type: Class
notation: E81
comment: 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.

Actor Appellation
type: Class
notation: E82
comment: 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.

Type Creation
type: Class
notation: E83
comment: 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”.

Information Carrier
type: Class
notation: E84
comment: 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. 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.

Joining
type: Class
notation: E85
comment: 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.

Leaving
type: Class
notation: E86
comment: 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.

Curation Activity
type: Class
notation: E87
comment: 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.

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 topics 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.

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 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. 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 allows 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).

Spacetime Volume
type: Class
notation: E92
comment: This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.

Presence
type: Class
notation: E93
comment: This class comprises instances of E92 Spacetime Volume that result from intersection of instances of E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituing spacetime volume and the time-span. This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD.

Space Primitive
type: Class
notation: E94
comment: This class comprises instances of E59 Primitive Value for space that should be implemented with appropriate validation, precision and references to spatial coordinate systems to express geometries on or relative to earth, or any other stable constellations of matter, relevant to cultural and scientific documentation.An E94 Space Primitive defines an E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr and Hiebel 2013), which means that the identity of the place is derived from its geometric definition. This declarative place allows for the application of all place properties to relate phenomenal places to their approximations expressed with geometries.Instances of E94 Space Primitive provide the ability to link CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualisation of the instances of E53 Place they define, in their geographic context and for computing topological relations between places based on these geometries.E94 Space Primitive is not further elaborated upon within this model. Statement of compatibility with OPENGIS

Work
type: Class
notation: F1
comment: This class comprises distinct concepts or combinations of concepts identified in artistic and intellectual expressions, such as poems, stories or musical compositions. Such concepts may appear in the course of the coherent evolution of an original idea into one or more expressions that are dominated by the original idea. A Work may be elaborated by one or more Actors simultaneously or over time. The substance of Work is ideas. A Work may have members that are works in their own right. A Work can be either individual or complex. If it is individual its concept is completely realised in a single F22 Self-Contained Expression. If it is complex its concept is embedded in an F15 Complex Work. An F15 Complex Work consists of alternative members that are either F15 Complex Works themselves or F14 Individual Works. A Work is the product of an intellectual process of one or more persons, yet only indirect evidence about it is at our hands. This can be contextual information such as the existence of an order for a work, reflections of the creators themselves that are documented somewhere, and finally the expressions of the work created. As ideas normally take shape during discussion, elaboration and implementation, it is not reasonable to assume that a work starts with a complete concept. In some cases, it can be very difficult or impossible to define the whole of the concept of a work at a particular time. The objective evidence for such a notion can only be based on a stage of expressions at a given time. In this sense, the sets of ideas that constitute particular self-contained expressions may be regarded as a kind of “snap-shot” of a work. A Work may include the concept of aggregating expressions of other works into a new expression. For instance, an anthology of poems is regarded as a work in its own right that makes use of expressions of the individual poems that have been selected and ordered as part of an intellectual process. This does not make the contents of the ag…

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 that have objectively recognisable structures. The substance of F2 Expression is signs. Expressions cannot exist without a physical carrier, but do not depend on a specific physical carrier and can exist on one or more carriers simultaneously. Carriers may include human memory. Inasmuch as the form of F2 Expression is an inherent characteristic of the F2 Expression, any change in form (e.g., from alpha-numeric notation to spoken word, a poem created in capitals and rendered in lower case) is a new F2 Expression. Similarly, changes in the intellectual conventions or instruments that are employed to express a work (e.g., translation from one language to another) result in the creation of a new F2 Expression. Thus, if a text is revised or modified, the resulting F2 Expression is considered to be a new F2 Expression. Minor changes, such as corrections of spelling and punctuation, etc., are normally considered variations within the same F2 Expression. On a practical level, the degree to which distinctions are made between variant expressions of a work will depend to some extent on the nature of the F1 Work itself, and on the anticipated needs of users. The genre of the work may provide an indication of which features are essential to the expression. In some cases, aspects of physical form, such as typeface and page layout, are not integral to the intellectual or artistic realisation of the work as such, and therefore are not distinctive criteria for the respective expressions. For another work, features such as layout may be essential. For instance, the author or a graphic designer may wrap a poem around an image. An expression of a work may include expressions of other works within it. For instan…

Manifestation Product Type
type: Class
notation: F3
comment: This class comprises the definitions of publication products. An instance of F3 Manifestation Product Type is the “species”, and all copies of a given object are “specimens” of it. An instance of F3 Manifestation Product Type defines all of the features or traits that instances of F5 Item normally display in order that they may be recognised as copies of a particular publication. However, due to production problems or subsequent events, one or more instances of F5 Item may not exhibit all these features or traits; yet such instances still retain their relationship to the same instance of F3 Manifestation Product Type. The features that characterise a given instance of F3 Manifestation Product Type include: one instance of F24 Publication Expression, containing one or more than one instance of F2 Expression, reflecting the authors’ content of the manifestation and all additional input by the publisher; and the appropriate types of physical features for that form of the object. For example, hardcover and paperback are two distinct publications (i.e. two distinct instances of F3 Manifestation Product Type) even though authorial and editorial content are otherwise identical in both publications. The activity of cataloguing aims at the most accurate listing of features or traits of an instance of F3 Manifestation Product Type that are sufficient to distinguish it from another instance of F3 Manifestation Product Type.

Manifestation Singleton
type: Class
notation: F4
comment: This class comprises physical objects that each carry an instance of F2 Expression, and that were produced as unique objects, with no siblings intended in the course of their production. It should be noted that if all but one copy of a given publication are destroyed, then that copy does not become an instance of F4 Manifestation Singleton, because it was produced together with sibling copies, even though it now happens to be unique. Examples of instances of F4 Manifestation Singleton include manuscripts, preparatory sketches and the final clean draft sent by an author or a composer to a publisher.

Item
type: Class
notation: F5
comment: This class comprises physical objects (printed books, scores, CDs, DVDs, CD-ROMS, etc.) that carry a F24 Publication Expression and were produced by an industrial process involving an F3 Manifestation Product Type.

Nomen
type: Class
notation: F12
comment: This class comprises any sign or arrangements of signs following a specific syntax (sequences of alphanumeric characters, chemical structure symbols, sound symbols, ideograms etc.) that are used or can be used to refer to and identify a specific instance of some class or category within a certain context. The scripts or type sets for the types of symbols used to compose an instance of F12 Nomen have to be explicitly specified. The identity of an instance of F12 Nomen is given by the order of its symbols and their individual role with respect to their scripts, regardless of the semantics of the larger structural components it may be built from. Structural tags occurring in the nomen string are regarded as symbols constituting the nomen. Spelling variants are regarded as different nomina, whereas the use of different fonts (visual representation variants) or different digital encodings do not change the identity.

Identifier
type: Class
notation: F13
comment: 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. [Adapted from the Scope Note of CIDOC CRM E42 Identifier ver. 5.0.1]

Individual Work
type: Class
notation: F14
comment: This class comprises works that are realised by one and only one self-contained expression, i.e., works representing the concept as expressed by precisely this expression. Inherent to the notion of work is the completion of recognisable outcomes of the work. These outcomes, i.e. the Self-Contained Expressions, are regarded as the symbolic equivalents of Individual Works, which form the atoms of a complex work. Normally creators would characterise an outcome of a work as finished. In other cases, one could recognise an outcome of a work as complete from the elaboration or logical coherence of its content, or if there is any historical knowledge about the creator deliberately or accidentally never finishing (completing) that particular expression. In all those cases, one would regard the corresponding expression as equivalent to one Individual Work.

Complex Work
type: Class
notation: F15
comment: This class comprises works that have other works as members. The members of a Complex Work may constitute alternatives to, derivatives of, or self-contained components of other members of the same Complex Work. In practice, no clear line can be drawn between parallel and subsequent processes in the evolution of a work. One part may not be finished when another is already revised. An initially monolithic work may be taken up and evolve in pieces. The member relationship of Work is based on the conceptual relationship, and should not be confused with the internal structural parts of an individual expression. The fact that an expression may contain parts from other work(s) does not make the expressed work complex. For instance, an anthology for which only one version exists is not a complex work. The boundaries of a Complex Work have nothing to do with the value of the intellectual achievement but only with the dominance of a concept. Thus, derivations such as translations are regarded as belonging to the same Complex Work, even though in addition they constitute an Individual Work themselves. In contrast, a Work that significantly takes up and merges concepts of other works so that it is no longer dominated by the initial concept is regarded as a new work. In cataloguing practice, detailed rules are established prescribing which kinds of derivation should be regarded as crossing the boundaries of a complex work. Adaptation and derivation graphs allow the recognition of distinct sub-units, i.e. a complex work contained in a larger complex work. As a Complex Work can be taken up by any creator who acquires the spirit of its concept, it is never finished in an absolute sense.

Serial Work
type: Class
notation: F18
comment: This class comprises works that are, or have been, planned to result in sequences of Expressions or Manifestations with common features. Whereas a work can acquire new members during the time it evolves, Expressions and Manifestations are identified with a certain state achieved at a particular point in time. Therefore there is in general no single Expression or Manifestation representing a complete serial work, unless the serial work has ended. Serial Works may or may not have a plan for an overall expression. The retrospective reprinting of all issues of a Serial Work at once, in the form of a monograph, is regarded to be another member of a Complex Work, which contains the Serial Work and the Individual Work realised in the monograph. This does not make the monograph part of the Serial Work.

Publication Work
type: Class
notation: F19
comment: This class comprises works that have been planned to result in a manifestation product type or an electronic publishing service and that pertain to the rendering of expressions from other works

Performance Work
type: Class
notation: F20
comment: This class comprises the sets of concepts for rendering a particular or a series of like performances. F20 Performance Work is declared as a subclass of F16 Container Work. This implies that the incorporated expressions (such as the text of the staged play, the text of the argument for the ballet, the recorded music to be used for the ballet, or the content of the musical score to be used for a concert, etc.) are not by themselves a part of the expression of this F1 Work. Rather, an expression (F25 Performance Plan) of the instructions the stage production, choreography or musical performance consists of incorporates (P165) that textual or musical content. In other words, the text of ‘Hamlet’ is not a component of the concepts that underlie a given mise-en-scène of ‘Hamlet’, but any staging directions (F25 Performance Plan) that convey a given director’s vision of ‘Hamlet’ must necessarily incorporate the text of ‘Hamlet’.

Recording Work
type: Class
notation: F21
comment: This class comprises works that conceptualise the capturing of features of perdurants. The characteristics of the manifestation of a recording work are those of the product of the capture process. The characteristics of any other works recorded are distinct from those of the recording work itself. In the case where the recorded perdurant expresses some Work, the respective instance of F21 is also an F16 Container Work. The concept of recording is not necessarily linked to the use of modern devices that allow for mechanical recording, such as tape recorders or cameras. However, in practice, library catalogues tend to regard as recordings only the products of such mechanical devices. But the concept of recording is very much linked to the notion that there is something that is recorded. In general, photographs or animated images are not to be regarded as instances of F21 Recording Work just because of the use of the medium, but simply as instances of F1 Work (or F15 Complex Work). Only such photographs and animated images that can be used as documentation are to be regarded as recordings.

Self-Contained Expression
type: Class
notation: F22
comment: This class comprises the immaterial realisations of individual works at a particular time that are regarded as a complete whole. The quality of wholeness reflects the intention of its creator that this expression should convey the concept of the work. Such a whole can in turn be part of a larger whole. Inherent to the notion of work is the completion of recognisable outcomes of the work. These outcomes, i.e. the Self-Contained Expressions, are regarded as the symbolic equivalents of Individual Works, which form the atoms of a complex work. A Self-Contained Expression may contain expressions or parts of expressions from other work, such as citations or items collected in anthologies. Even though they are incorporated in the Self-Contained Expression, they are not regarded as becoming members of the expressed container work by their inclusion in the expression, but are rather regarded as foreign or referred to elements. F22 Self-Contained Expression can be distinguished from F23 Expression Fragment in that an F23 Expression Fragment was not intended by its creator to make sense by itself. Normally creators would characterise an outcome of a work as finished. In other cases, one could recognise an outcome of a work as complete from the elaboration or logical coherence of its content, or if there is any historical knowledge about the creator deliberately or accidentally never finishing (completing) that particular expression. In all those cases, one would regard an expression as self-contained.

Expression Fragment
type: Class
notation: F23
comment: This class comprises parts of Expressions and these parts are not Self-Contained Expressions themselves. The existence of an instance of F23 Expression Fragment can be due to accident, such as loss of material over time, e.g. the only remaining manuscript of an antique text being partially eaten by worms, or due to deliberate isolation, such as excerpts taken from a text by the compiler of a collection of excerpts. An F23 Expression Fragment is only identified with respect to its occurrence in a known or assumed whole. The size of an instance of F23 Expression Fragment ranges from more than 99% of an instance of F22 Self-Contained Expression to tiny bits (a few words from a text, one bar from a musical composition, one detail from a still image, a two-second clip from a movie, etc.).

Publication Expression
type: Class
notation: F24
comment: This class comprises complete sets of signs present in publications, reflecting publishers’ final decisions as to both selection of content and layout of the publications. Frequently the creation of a Publication Expression includes both adding graphical form and fonts to Expressions consisting of words alone and selecting illustrations and other content. As such, an instance of Publication Expression incorporates all Expressions combined for the resulting final form of rendering, whether visual, audio or tactile. An instance of Publication Expression is one entity regardless of the number of independent Expressions published within it, as long as it represents one unit of release. The published third party content can be associated via the property P165 incorporates (is incorporated in).

Performance Plan
type: Class
notation: F25
comment: This class comprises sets of directions to which individual performances of theatrical, choreographic, or musical works and their combinations should conform. In the case of theatrical performances, such directions incorporate, but are not limited nor reducible to, the text of a given version of the play performed (e.g., a translated text, some passages of which are deliberately omitted, with some rephrased lines, etc.). In the case of choreographic performances, such directions may incorporate, but are neither limited nor reducible to, the notation of choreographic movements in systems such as labanotation. In the case of musical performances, such directions may incorporate, but are neither limited nor reducible to, the musical score. In case of electronic music, they may incorporate software instructions. These directions may or may not completely determine the form of the intended performance. Depending on the nature of the directions, the form of the intended performance, such as the sets of movements or the sound characteristics, may or may not be predictable from the directions. Note that a performance plan may be more or less elaborate, and may even foresee just improvisation.

Recording
type: Class
notation: F26
comment: This class comprises expressions which are created in instances of F29 Recording Event. A recording is intended to convey (and preserve) the features of one or more perdurants.

Work Conception
type: Class
notation: F27
comment: This class comprises beginnings of evolutions of works. An instance of F27 Work Conception marks the initiation of the creation of a work. The work, as an intellectual construction, evolves from this point on, until the last known expression of it. The instance of E39 Actor with which a work is associated through the chain of properties F1 Work R16i was initiated by F27 Work Conception P14 carried out by E39 Actor corresponds to the notion of the “creator” of the work. In the case of commissioned works, it is not the commissioning that is regarded as the work conception, but the acceptance of the commission. This event does not always correlate with the date assigned in common library practice to the work, which is usually a later event (such as the date of completion of the first clean draft). In addition, F27 Work Conception can serve to document the circumstances that surrounded the appearance of the original idea for a work, when these are known.

Expression Creation
type: Class
notation: F28
comment: This class comprises activities that result in instances of F2 Expression coming into existence. This class characterises the externalisation of an Individual Work. Although F2 Expression is an abstract entity, a conceptual object, the creation of an expression inevitably also affects the physical world: when you scribble the first draft of a poem on a sheet of paper, you produce an instance of F4 Manifestation Singleton; F28 Expression Creation is a subclass of E12 Production because the recording of the expression causes a physical modification of the carrying E18 Physical Thing. The work becomes manifest by being expressed on a physical carrier different from the creator’s brain. The spatio-temporal circumstances under which the expression is created are necessarily the same spatio-temporal circumstances under which the first instance of F4 Manifestation Singleton is produced. The mechanisms through which oral tradition (of myths, tales, music, etc.) operates are not further investigated in this model. As far as bibliographic practice is concerned, only those instances of F2 Expression that are externalised on physical carriers other than both the creator’s brain and the auditor’s brain are taken into account (for a discussion of the modelling of oral traditions, see: Nicolas, Yann. ‘Folklore Requirements for Bibliographic Records: oral traditions and FRBR.’ In: Cataloging Classification Quarterly (2005). Vol. 39, No. 3-4. P. 179-195). It is possible to use the P2 has type (is type of) property in order to specify that the creation of a given expression of a given work played a particular role with regard to the overall bibliographic history of that work (e.g., that it was the creation of the progenitor expression on which all other expressions of the same work are based; or that it was the creation of the critical edition that served as the basis for canonical references to the work).

Recording Event
type: Class
notation: F29
comment: This class comprises activities that intend to convey (and preserve) the features of perdurants in a recording, such as a live recording of a performance, a documentary, or other capture of a perdurant. Such activities may follow the directions of a recording plan. They may include postproduction.

Publication Event
type: Class
notation: F30
comment: This class comprises the activities of publishing. Such an event includes the creation of an F24 Publication Expression and setting up the means of production. The end of this event is regarded as the date of publication, regardless of whether the carrier production is started. Publishing can be either physical or electronic. Electronic publishing is regarded as making an instance of F24 Publication Expression available in electronic form on a public network. Electronic Publishing does not mean producing a physical instance of F5 Item by partially electronic means. Making an electronic file available on a physical carrier can be regarded as equivalent to setting up the means of production; downloading the file is regarded as the electronic equivalent of F32 Carrier Production Event.

Performance
type: Class
notation: F31
comment: This class comprises activities that follow the directions of a performance plan, such as a theatrical play, an expression of a choreographic work or a musical work; i.e., they are intended to communicate directly or indirectly to an audience. Such activities can be identified at various levels of granularity, and can be contiguous or not. Any individual performance (with or without intermissions) is a single instance of F31 Performance. In addition, a complete run of performances can also be seen as an instance of F31 Performance, with individual performances as parts. A complete run of performances may comprise an original run plus any of its extensions and tours. Note that a performance plan may be more or less elaborate, and may even foresee just improvisation.

Carrier Production Event
type: Class
notation: F32
comment: This class comprises activities that result in instances of F54 Utilised Information Carrier coming into existence. Both the production of a series of physical objects (printed books, scores, CDs, DVDs, CD-ROMS, etc.) and the creation of a new copy of a file on an electronic carrier are regarded as instances of F32 Carrier Production Event. Typically, the production of copies of a publication (no matter whether it is a book, a sound recording, a DVD, a cartographic resource, etc.) strives to produce items all as similar as possible to a prototype that displays all the features that all the copies of the publication should also display, which is reflected in property R27 used as source material F24 Publication Expression.

Reproduction Event
type: Class
notation: F33
comment: This class comprises activities that consist in making copies, more or less mechanically, of an instance of E84 Information Carrier (such as an F5 Item or an F4 Manifestation Singleton which is also instance of E84 Information Carrier), preserving the expression carried by it. A Reproduction Event results in new instances of E84 Information Carrier coming into existence. In general, the copy will have different attributes from the original and they are therefore not regarded as siblings. This class makes it possible to account for the legal distinction between private copying for the purpose of “fair use,” and mass production for the purpose of dissemination. It can prove difficult to determine where to draw the line between F33 Reproduction Event and F32 Carrier Production Event in cases where multiple copies are produced. In this case, the copies, but not the original, may be regarded as instances of F5 Item. It is the existence of an explicit production plan that makes the difference. As a consequence, F33 Reproduction Event and F32 Carrier Production Event are not declared as disjoint, which makes it possible to account for such situations that could be regarded as instances of both Production Event and Reproduction Event.

KOS
type: Class
notation: F34
comment: This class comprises documents that establish controlled terminology (nomina) for consistent use. They may also describe relationships between entities and controlled terminology and relationships between entities. Note that any meaningful change in a Knowledge Organisation System (KOS) that affects the validity status of its elements defines a new release (Expression) of the KOS. Note that identifiers created following a rule in a KOS are to be regarded as being taken from this KOS, even though not explicitly spelled out. This definition of KOS reflects current library practice and not the use of the term in general.

Nomen Use Statement
type: Class
notation: F35
comment: This class comprises statements relating a Thema with a particular Nomen and its usage in the context of a common Complex Work realized by one or more KOS.

Script Conversion
type: Class
notation: F36
comment: This class comprises rule sets for converting signs or arrangements of signs from one script or type set to another.

Character
type: Class
notation: F38
comment: This class comprises fictional or iconographic individuals or groups of individuals (including families) appearing in works in a way relevant as subjects. Characters may be purely fictitious or based on real persons or groups, but as characters they may exhibit properties that would be inconsistent with a real person or group. Rather than merging characters with real persons, they should be described as disjoint, but related entities.

Identifier Assignment
type: Class
notation: F40
comment: This class comprises activities that result in the allocation of an identifier to an instance of any subclass of E1 CRM Entity. An F40 Identifier Assignment may include the creation of the identifier from multiple constituents. Explicit reference to the used constituents can be made using the property P142 used constituent (was used in). The syntax of the identifier and the kinds of constituents to be used in constructing it may be declared in a rule. The construction of controlled access points for the names of persons, families and corporate bodies following specific cataloguing rules is a typical library application of identifier assignment. F40 Identifier Assignment also includes the assignment of controlled access points for works or expressions.

Representative Manifestation Assignment
type: Class
notation: F41
comment: This class comprises activities through which an Agency declares (implicitly or explicitly) that a given instance of F3 Manifestation Product Type or F4 Manifestation Singleton is representative for a given F2 Expression, i.e., that some features found on that instance of F3 Manifestation Product Type or F4 Manifestation Singleton (most prominently, information about the title) can be inferred to also apply to that instance of F2 Expression, no matter within which manifestation it is embodied. The reasoning behind is that the Work title is known through the title of an Expression that is deemed representative of the Work, and the title of the representative Expression is known through the title proper of a Manifestation that is deemed representative of the Expression representative of the Work.

Representative Expression Assignment
type: Class
notation: F42
comment: This class comprises activities through which an Agency declares (implicitly or explicitly) that a given instance of F2 Expression is representative for a given F15 Complex Work, i.e., that some attributes of that instance of F2 Expression (most prominently, information about the title) can be inferred to also apply to that instance of F15 Complex Work, no matter in which particular expression it is realised. The reasoning behind this is that the Work title is known through the title of an Expression that is deemed representative of the Work, and the title of the representative Expression is known through the title of a Manifestation that is deemed representative of the Expression that is representative of the Work. For instance, by using the qualified controlled access point ‘Poe, Edgar Allan, 1809-1849. Murders in the rue Morgue (French)’ for the French rendition of Poe’s ‘Murders in the rue Morgue’ by Baudelaire, an Agency implicitly states that the French text does not constitute a representative F2 Expression for Poe’s F1 Work, however the original English text does constitute a representative F2 Expression for Poe’s F1 Work.

Identifier Rule
type: Class
notation: F43
comment: This class comprises sets of instructions relating to the formulation of a unique identifier.

Bibliographic Agency
type: Class
notation: F44
comment: This class comprises agents who create the bibliographic description of publications and perform the authority control associated with such descriptions, for the description of copies of such publications actually held by libraries, and for the description of unique documents (manuscripts, objects…) held by libraries. The activity of creating such descriptions implies that one has to make decisions (as to the controlled access point for a work, as to whether an arrangement still belongs to the same work or is definitely a new work, etc.). Since such decisions always are debatable and different agencies can make different decisions about the same real-world entities, it is important to document which agency made which decision.

Pursuit
type: Class
notation: F51
comment: This class comprises periods of continuous activity of an Actor in a specific professional or creative domain or field.

Name Use Activity
type: Class
notation: F52
comment: This class comprises periods of continuous use of a specific instance of E41 Appellation for a particular instance of E1 CRM Entity by an E39 Actor. It includes in particular the use of the name by its carrier. Characteristically, actors performing an activity may choose a particular appellation for themselves in the context of this activity. Such cases should be modelled by additionally classifying these activities as instances of F52 Name Use Activity. It is possible to specify the type of name use, through the P2 has type property, e.g.: use of a pseudonym, use of a married name, use of a birth name, use of a blended name, use of a religious name, etc.

Utilized Information Carrier
type: Class
notation: F54
comment: This class comprises physical objects that carry one or more instances of F24 Publication Expression.

Matter Removal
type: Class
notation: S1
comment: This class comprises the activities that result in an instance of S10 Material Substantial being decreased by the removal of an amount of matter. Typical scenarios include the removal of a component or piece of a physical object, removal of an archaeological or geological layer, taking a tissue sample from a body or a sample of fluid from a body of water. The removed matter may acquire a persistent identity of different nature beyond the act of its removal, such as becoming a physical object in the narrower sense. Such cases should be modeled by using multiple instantiation with adequate concepts of creating the respective items.

Sample Taking
type: Class
notation: S2
comment: This class comprises the activity that results in taking an amount of matter as sample for further analysis from a material substantial such as a body of water, a geological formation or an archaeological object. The removed matter may acquire a persistent identity of different nature beyond the act of its removal, such as becoming a physical object in the narrower sense. The sample is typically removed from a physical feature which is used as a frame of reference, the place of sampling. In case of non-rigid Material Substantials, the source of sampling may regarded not to be modified by the activity of sample taking.

Observation
type: Class
notation: S4
comment: This class comprises the activity of gaining scientific knowledge about particular states of physical reality gained by empirical evidence, experiments and by measurements. We define observation in the sense of natural sciences, as a kind of human activity: at some Place and within some Time-Span, certain Physical Things and their behavior and interactions are observed, either directly by human sensory impression, or enhanced with tools and measurement devices. The output of the internal processes of measurement devices that do not require additional human interaction are in general regarded as part of the observation and not as additional inference. Manual recordings may serve as additional evidence. Measurements and witnessing of events are special cases of observations. Observations result in a belief about certain propositions. In this model, the degree of confidence in the observed properties is regarded to be “true” per default, but could be described differently by adding a property P3 has note to an instance of S4 Observation, or by reification of the property O16 observed value. Primary data from measurement devices are regarded in this model to be results of observation and can be interpreted as propositions believed to be true within the (known) tolerances and degree of reliability of the device. Observations represent the transition between reality and propositions in the form of instances of a formal ontology, and can be subject to data evaluation from this point on.

Data Evaluation
type: Class
notation: S6
comment: This class comprises the action of concluding propositions on a respective reality from observational data by making evaluations based on mathematical inference rules and calculations using established hypotheses, such as the calculation of an earthquake epicenter. S6 Data Evaluation is not defined as S21/E16 Measurement; Secondary derivations of dimensions of an object from data measured by different processes are regarded as S6 Data Evaluation and not determining instances of Measurement in its own right. For instance, the volume of a statue concluded from a 3D model is an instance of S6 Data Evaluation and not of Measurement.

Property Type
type: Class
notation: S9
comment: This class comprises types of properties. Typically, instances of S9 Property Type would be taken from an ontology or terminological system. In particular, instances of this class can be used to describe in a parametric way what kind of properties the values in scientific data sets are about. By virtue of such descriptions, numeric data can be interpreted as sets of propositions in terms of a formal ontology, such as “concentration of nitrate”, observed in the ground water from a certain borehole.

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.

Amount of Matter
type: Class
notation: S11
comment: This class comprises fixed amounts of matter specified as some air, some water, some soil, etc., defined by the total and integrity of their material content.

Amount of Fluid
type: Class
notation: S12
comment: This class comprises fixed amounts of fluid defined by the total of its material content, typically molecules. They frequently acquire identity in laboratory practice by the fact of being kept or handled together within some adequate containers.

Sample
type: Class
notation: S13
comment: This class comprises instances of S11 Amount of Matter taken from some instance of S10 Material Substantial with the intention to be representative for some material qualities of the instance of S10 Material Substantial or part of it was taken from for further analysis. We typically regard a sample as ceasing to exist when the respective representative qualities become corrupted, such as the purity of a water sample or the layering of a bore core.

Fluid Body
type: Class
notation: S14
comment: This class comprises a mass of matter in fluid form environmentally constraint in some persistent form allowing for identifying it for the management or research of material phenomena, such as a part of the sea, a river, the atmosphere or the milk in a bottle. Fluids are generally defined by the continuity criterion which is characteristic of their substance: their amorphous matter is continuous and tends to flow. Therefore, contiguous amounts of matter within a fluid body may stay contiguous or at least be locally spatially confined for a sufficiently long time in order to be temporarily identified and traced. This is a much weaker concept of stability of form than the one we would apply to what one would call a physical object. In general, an instance of Fluid Body may gain or lose matter over time through so-called sources or sinks in its surface, in contrast to physical things, which may lose or gain matter by exchange of pieces such as spare parts or corrosion.

Observable Entity
type: Class
notation: S15
comment: This class comprises instances of E2 Temporal Entity or E77 Persistent Item, i.e. items or phenomena that can be observed, either directly by human sensory impression, or enhanced with tools and measurement devices, such as physical things, their behavior, states and interactions or events. Conceptual objects can be present in events by their carriers such as books, digital media, or even human memory. By virtue of this presence, properties 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 give credit to the fact that frequently, the actually observed carriers of conceptual objects are not explicitly identified in documentation, i.e., the actual carrier is assumed having existed but is unknown as an individual.

State
type: Class
notation: S16
comment: This class comprises the persistence of a particular value range of the properties of a particular thing or things over a time-span.

Physical Genesis
type: Class
notation: S17
comment: This class comprises events or processes that result in (generate) physical things, man-made or natural, coming into being in the form by which they are later identified. The creation of a new physical item, at the same time, can be a result of an alteration (modification) – it can become a new thing due to an alteration activity.

Alteration
type: Class
notation: S18
comment: This class comprises natural events or man-made processes that create, alter or change physical things, by affecting permanently their form or consistency without changing their identity. Examples include alterations on depositional features-layers by natural factors or disturbance by roots or insects, organic alterations, petrification, etc.

Encounter Event
type: Class
notation: S19
comment: This class comprises activities of S4 Observation (substance) where an E39 Actor encounters an instance of E18 Physical Thing of a kind relevant for the mission of the observation or regarded as potentially relevant for some community (identity). This observation produces knowledge about the existence of the respective thing at a particular place in or on surrounding matter. This knowledge may be new to the group of people the actor belongs to. In that case we would talk about a discovery. The observer may recognize or assign an individual identity of the thing encountered or regard only the type as noteworthy in the associated documentation or report. In archaeology there is a particular interest if an object is found “in situ”, i.e. if its embedding in the surrounding matter supports the assumption that the object was not moved since the archaeologically relevant deposition event. The surrounding matter with the relative position of the object in it as well as the absolute position and time of the observation may be recorded in order to enable inferences about the history of the E18 Physical Thing. In Biology, additional parameters may be recorded like the kind of ecosystem, if the biological individual survives the observation, what detection or catching devices have been used or if the encounter event supported the detection of a new biological kind (“taxon”).

Physical Feature
type: Class
notation: S20
comment: This class comprises identifiable features that are physically attached in an integral way to particular physical objects. An instance of S20 Physical Feature also represents the place it occupies with respect to the surrounding matter. More precisely, it is the maximal real volume in space that an instance of S20 Physical Feature is occupying during its lifetime with respect to the default reference space relative to which the feature is at rest. In cases of features 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. 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 colors, 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 and Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”.

Measurement
type: Class
notation: S21
comment: This class comprises actions measuring instances of E2 Temporal Entity or E77 Persistent Items, properties of physical things, or phenomena, states and interactions or events, that can be determined by a systematic procedure. Primary data from measurement devices are regarded to be results of an observation process.

Segment of Matter
type: Class
notation: S22
comment: This class comprises physical material in a relative stability of form (substance) within a specific spacetime volume (unity, extend). The spatial extend of a S22 Segment of Matter is defined by humans usually because the constellation is subject to a specific interest for and investigations of the geometric arrangement of physical features or parts of them on or within the specified S22 Segment of Matter. It comes into existence as being an object of discourse through S4 Observation or declaration and is restricted to the time span starting after the last change through an S18 Alteration before the S4 Observation or declaration and ending with the next S18 Alteration Event (identity). A S22 Segment of Matter exists as long as there is no modification of the geometric arrangement of its particles. Therefore the temporal boundaries of the defining Spacetime Volume are given by two S18 Alteration events. The history of a S22 Segment of Matter started with the first S17 Physical Genesis event that deposited still existing matter within the defined spatial extend. The collection of all S18 Alteration events represent its history. Some of the events will not leave any physical material within the S22 Segment of Matter. (to be elaborated further)

should have type
type: ObjectProperty
range: Type
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E55 Type, which all exemplars of that publication should belong to, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E55 Type. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
notation: CLP2
domain: Manifestation Product Type

should have dimension
type: ObjectProperty
range: Dimension
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E54 Dimension, which all exemplars of that publication should have, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P39i was measured by E16 Measurement P40 observed dimension E54 Dimension. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
notation: CLP43
domain: Manifestation Product Type

should consist of
type: ObjectProperty
range: Material
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E57 Material, which all exemplars of that publication should consist of, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E57 Material. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
notation: CLP45
domain: Manifestation Product Type

should be composed of
type: ObjectProperty
range: Manifestation Product Type
comment: This property associates an instance of F3 Manifestation Product Type which prescribes that all its Items will contain as parts an Item of another instance of F3 Manifestation Product Type with that instance of F3 Manifestation Product Type.
notation: CLP46
domain: Manifestation Product Type

should have number of parts
type: ObjectProperty
range: Number
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E60 Number, which denotes the number of physical units all exemplars of that publication should consist of, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P57 has number of parts E60 Number. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
notation: CLP57
domain: Manifestation Product Type

subject to
type: ObjectProperty
range: Right
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E30 Right, which applies to all exemplars of that publication, as long as they are recognised as exemplars of that publication. The rights covered by this property may include: acquisition or access authorisation; terms of availability; access restrictions on the Manifestation Product Type; etc.
notation: CLP104
domain: Manifestation Product Type

right held by
type: ObjectProperty
range: Actor
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E39 Actor, who holds an instance of E30 Right on all exemplars of that publication, as long as they are recognised as exemplars of that publication.
notation: CLP105
domain: Manifestation Product Type

should carry
type: ObjectProperty
range: Publication Expression
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F24 Publication Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item R6 carries F24 Publication Expression. It can happen that a given exemplar, or a subset of exemplars, originally produced, or intended to be produced with that characteristic, accidentally lacks part of the publication expression. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
notation: CLR6
domain: Manifestation Product Type

digitized
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of D2 Digitization Process with an instance of E18 Physical Thing which is a material thing.
notation: L1
domain: Digitization Process

used as source
type: ObjectProperty
range: Digital Object
comment: This property associates an instance of D10 Software Execution with an instance of D1 Digital Object which is used as a source, software essential for the performance.
notation: L2
domain: Software Execution

has preferred label
type: ObjectProperty
range: String
comment: This property associates an instance of E1 Entity with an instance of resource used as a preferred lexical label. This property is a specialisation of rdf schema label.
notation: L4
domain: CRM Entity

had input
type: ObjectProperty
range: Digital Object
comment: This property associates an instance of D7 Digital Machine Event with an instance of D1 Digital Object which is the input used to specify the machine action.
notation: L10
domain: Digital Machine Event

had output
type: ObjectProperty
range: Digital Object
comment: This property associates an instance of D7 Digital Machine Event with an instance of D1 Digital Object which is the output of the activity.
notation: L11
domain: Digital Machine Event

happened on device
type: ObjectProperty
range: Digital Device
comment: This property associates an instance of D7 Digital Machine Event with an object, the D8 Digital Device, which happened with, e.g a capturing event that happened on/with a digital camera, etc.
notation: L12
domain: Digital Machine Event

used parameters
type: ObjectProperty
range: Digital Object
comment: This property associates an instance of D10 Software Execution with a digital object used as a parameter during the process.
notation: L13
domain: Software Execution

transferred
type: ObjectProperty
range: Digital Object
comment: This property identifies a digital object transferred by a D12 Data Transfer Event.
notation: L14
domain: Data Transfer Event

has sender
type: ObjectProperty
range: Digital Device
comment: This property identifies a digital device used as a medium on which data are transferred through a D12 Data Transfer Event.
notation: L15
domain: Data Transfer Event

has receiver
type: ObjectProperty
range: Digital Device
comment: This property identifies a digital device used as a medium to receive data through a D12 Data Transfer Event.
notation: L16
domain: Data Transfer Event

measured thing of type
type: ObjectProperty
range: Type
comment: This property associates an instance of D11 Digital Measurement Event with the instance of E55Type of object to which it applied.
notation: L17
domain: Digital Measurement Event

has modified
type: ObjectProperty
range: Digital Information Carrier
comment: This property identifies a Digital Information Carrier modified in a Digital Machine Event.
notation: L18
domain: Digital Machine Event

stores
type: ObjectProperty
range: Digital Object
comment: This property associates an instance of a D13 Digital Information Carrier with the instance of Digital Object that is stored on it.
notation: L19
domain: Digital Information Carrier

has created
type: ObjectProperty
range: Data Object
comment: This property identifies a Data Object that came into existence as a result of a D11 Digital Measurement Event.
notation: L20
domain: Digital Measurement Event

used as derivation source
type: ObjectProperty
range: Digital Object
comment: This property associates an instance of a D3 Formal Derivation with the instance of D1 Digital Object that is used as a derivation source.
notation: L21
domain: Formal Derivation

created derivative
type: ObjectProperty
range: Digital Object
comment: This property associates an instance of D3 Formal Derivation with the Digital Object it used to create a version of.
notation: L22
domain: Formal Derivation

used software or firmware
type: ObjectProperty
range: Software
comment: This property associates an instance of D7 Digital Machine Event with the instance of D14 Software that had used.
notation: L23
domain: Digital Machine Event

created logfile
type: ObjectProperty
range: Digital Object
comment: This property identifies the logfile that was created by a D10 Software Execution in order to record all the activities in the system.
notation: L24
domain: Software Execution

has responsible organization
type: ObjectProperty
range: Legal Body
comment: This property describes the participation of a Legal Body in being responsible for the outcome of a specific activity.
notation: L29
domain: Activity

has operator
type: ObjectProperty
range: Person
comment: This property describes the activity that is being operated by a person.
notation: L30
domain: Activity

has starting date-time
type: ObjectProperty
range: Time Primitive
comment: This property allows the starting point for a D7 Digital Machine Event to be situated. This property expresses the approximation of the starting date of a time span.
notation: L31
domain: Digital Machine Event

has ending date-time
type: ObjectProperty
range: Time Primitive
comment: This property allows the ending point for a D7 Digital Machine Event to be situated. This property expresses the approximation of the ending date of a time span.
notation: L32
domain: Digital Machine Event

has maker
type: ObjectProperty
range: Actor
comment: This property identifies the maker, the actor who is responsible for the production of a device, a computer, a digital camera, any kind of a machine that has been produced. This property is a shortcut of a more fully developed path from CRM E12 Production: P108 has produced: E24 Physical Man-Made Thing. In this case, there is no need to describe the more detailed property through a production event, so L33F has maker is recommended to be used instead.
notation: L33
domain: Physical Man-Made Thing

has contractor
type: ObjectProperty
range: Legal Body
comment: This property describes the participation of a Legal Body in being contractor for the outcome of a specific activity.This property is a specialisation of L29_has_responsible_organization.
notation: L34
domain: Activity

has commissioner
type: ObjectProperty
range: Legal Body
comment: This property describes the participation of a Legal Body in being commissioner for the outcome of a specific activity.This property is a specialisation of L29_has_responsible_organization.
notation: L35
domain: Activity

annotates
type: ObjectProperty
range: CRM Entity
comment: This property describes the associations between objects or areas of objects of the RI, with other objects or regions or persons, places, events.
notation: L43
domain: Annotation Object

has comment
type: ObjectProperty
range: String
comment: This property associates an instance of a textual note with an instance of an object of RI it makes a comment about.
notation: L47
domain: CRM Entity

created annotation
type: ObjectProperty
range: Annotation Object
comment: This property identifies the D29 Annotation Object (associations) that came into existence as a result of a D30 Annotation Event.
notation: L48
domain: Annotation Event

is primary area of
type: ObjectProperty
range: Digital Object
comment: This property describes the association between a particular area declared in an original digital object.
notation: L49
domain: Area

is propagated area of
type: ObjectProperty
range: Digital Object
comment: This property describes the association between an area and the digital object to which it is propagated.
notation: L50
domain: Area

has first name
type: ObjectProperty
range: String
comment: This property defines a personal name used to identify a person.
notation: L51
domain: Person Name

has last name
type: ObjectProperty
range: String
comment: This property defines the last name used to identify a person.
notation: L52
domain: Person Name

is not uniquely identified by
type: ObjectProperty
range: String
comment: This property describes a non unique identification applied to E1 CRM Entity.
notation: L53
domain: CRM Entity

is same-as
type: ObjectProperty
range: CRM Entity
comment: This property describes a non unique identification applied to E1 CRM Entity.
notation: L54
domain: CRM Entity

has inventory no
type: ObjectProperty
range: String
comment: This property records the inventory number that was used to identify an instance of E1 CRM Entity at the time this property was record.
notation: L55
domain: CRM Entity

has pixel width
type: ObjectProperty
range: Number
comment: This property records the pixel width of the data object; it approximates a dimension that is part of the image data analysis.
notation: L56
domain: Data Object

has pixel height
type: ObjectProperty
range: Number
comment: This property records the pixel height of the data object; it approximates a dimension that is part of the image data analysis.
notation: L57
domain: Data Object

has serial number
type: ObjectProperty
range: String
comment: This property records the serial number that was assigned to identify an instance of E22 Man Made Object.
notation: L59
domain: Man-Made Object

documents
type: ObjectProperty
range: CRM Entity
comment: This property describes the CRM Entities documented by instances of Digitization Processes.
notation: L60
domain: Digitization Process

was ongoing at
type: ObjectProperty
range: Time Primitive
comment: This property describes the minimum period of time covered by a digital machine event. It identifies the minimum extent of the event.
notation: L61
domain: Digital Machine Event

diminished
type: ObjectProperty
range: Material Substantial
comment: This property associates an instance of S1 Matter Removal with the instance of S10 Material Substantial that this activity diminished.
notation: O1
domain: Matter Removal

removed
type: ObjectProperty
range: Amount of Matter
comment: This property associates an instance of S1 Matter Removal with the instance of S11 Amount of Matter that it has removed.
notation: O2
domain: Matter Removal

sampled from
type: ObjectProperty
range: Material Substantial
comment: This property associates an instance of S2 Sample Taking with the instance S10 Material Substantial from which a sample was taken This may be a feature or a fluid body from which a sample was removed.
notation: O3
domain: Sample Taking

sampled at
type: ObjectProperty
range: Place
comment: This property associates an instance of S2 Sample Taking with the instance of E53 Place at which this activity sampled. It identifies the narrower spatial location from which an instance of a sample was taken. This maybe known or given in absolute terms or relative to an instance of a material substantial from which it was taken. It describes a position within the area in which the instance of the sampling activity occurred. The latter comprises the space within which operators and instruments were contained during the activity.
notation: O4
domain: Sample Taking

removed
type: ObjectProperty
range: Sample
comment: This property associates an instance of S2 Sample Taking with the instance of S13 Sample that was removed during this activity. The sample is identified by a unique identifier.
notation: O5
domain: Sample Taking

forms former or current part of
type: ObjectProperty
range: Fluid Body
comment: This property associates an instance of S12 Amount of Fluid with an instance of S14 Fluid Body which forms part of it. It allows instances of S14 Fluid Body to be analyzed into elements of S12 Amount of Fluid.
notation: O6
domain: Amount of Fluid

contains or confines
type: ObjectProperty
range: Place
comment: This property associates an instance of E53 Place contained or confined in an instance of E53 Place with the latter. It describes a spatial containment between places or features. It declares a type of a feature which has a kind of spatial containment. Features such as layers defined as a Place that are contained or confined by a Physical Feature behaving as a place. A place-feature that is defined by its environmental area, by another place; it conforms to the outline of its container.
notation: O7
domain: Place

observed
type: ObjectProperty
range: Observable Entity
comment: This property associates an instance of S4 Observation with an instance of S15 Observable Entity that was observed. Specifically it describes that a thing, a feature, a phenomenon or its reaction is observed by an activity of Observation.
notation: O8
domain: Observation

observed property type
type: ObjectProperty
range: Property Type
comment: This property associates an instance of S4 Observation with the instance of S9 Property Type for which the observation provides a value or evidence, such as “concentration of nitrate” observed the water from a particular borehole. Encoding the observed property by type, observed entity and value (properties O9, O10, O16) is a method to circumscribe the reification of the observed property by the respective instance of S4 Observation. In an RDFS encoding, this circumscription can be transformed into an explicit representation of the observed property in terms of a formal ontology either by use of a reification construct or by the use of a Named Graph containing the observed property. The latter representation allows for more formal reasoning with the model, the former is more flexible about the kinds of observations.
notation: O9
domain: Observation

assigned dimension
type: ObjectProperty
range: Dimension
comment: This property associates an instance of S6 Data Evaluation with an instance of E54 Dimension that a data evaluation activity has assigned. In that case, dimensions may be determined by making evaluations on observational data based on mathematical inference rules and calculations.
notation: O10
domain: Data Evaluation

described
type: ObjectProperty
range: Observable Entity
comment: This property associates an instance of S6 Data Evaluation with an instance of S15 Observable Entity for which a data evaluation activity provides a description. This description of any Observable Entity is based on data evaluations.
notation: O11
domain: Data Evaluation

has dimension
type: ObjectProperty
range: Dimension
comment: This property associates an instance of S15 Observable Entity with an instance of E54 Dimension that the observable entity has.It offers no information about how and when an E54 Dimension was established.
notation: O12
domain: Observable Entity

triggers
type: ObjectProperty
range: Event
comment: This property associates an instance of E5 Event that triggers another instance of E5 Event with the latter. It identifies the interaction between events: an event can activate (trigger) other event/s; in that sense it is interpreted as the cause, the triggering factor of a situation in tension (a system); a reaction between events.
notation: O13
domain: Event

initializes
type: ObjectProperty
range: State
comment: This property associates an instance of E5 Event with instance/s of S16 State/s that an event initializes. These states are described as the results, consequences of an E5 Event.
notation: O14
domain: Event

occupied
type: ObjectProperty
range: Place
comment: This property associates an instance of S10 Material Substantial with the instance of E53 Place that this substance occupied. It describes the space filled (occupied) by a physical matter. This property is the development of the shortcut expressed in the proposition of classification: “S20 Physical Feature” isA “E53 Place”
notation: O15
domain: Material Substantial

observed value
type: ObjectProperty
range: CRM Entity
comment: This property associates a value assigned to an entity observed by S4 Observation.
notation: O16
domain: Observation

generated
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of S17 Physical Genesis event with an instance of E18 Physical Thing that the event generated.
notation: O17
domain: Physical Genesis

altered
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of S18 Alteration process with an instance of E18 Physical Thing which was altered by this activity.
notation: O18
domain: Alteration

has found object
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of S19 Encounter Event with an instance of E18 Physical Thing that has been found.
notation: O19
domain: Encounter Event

sampled from type of part
type: ObjectProperty
range: Type
comment: This property associates the activity of a Sample Taking with the type of the location part from which a sample was taken. It is a shortcut of the property O4 sampled at, and it is used as an alternative property, identifying features and material substantial as types of parts of sampling positions.
notation: O20
domain: Sample Taking

has found at
type: ObjectProperty
range: Place
comment: This property associates an instance of S19 Encounter Event with an instance of E53 Place at which an encounter event found things. It identifies the narrower spatial location in which a thing was found at. This maybe known or given in absolute terms or relative to the thing found. It describes a position within the area in which the instance of the encounter event occurred and found something.
notation: O21
domain: Encounter Event

partly or completely contains
type: ObjectProperty
range: Physical Feature
comment: This property identifies an S20 Physical Feature as being part of a S22 Segment of Matter. One S22 Segment of Matter usually contains several S20 Physical Features.
notation: O22
domain: Segment of Matter

is defined by
type: ObjectProperty
range: Spacetime Volume
comment: This property identifies the E92 Spacetime Volume that defines a S22 Segment of Matter. The spatial boundaries of the E92 Spacetime Volume are defined through S4 Observation or declaration while the temporal boundaries are confined by S18 Alteration events.
notation: O23
domain: Segment of Matter

measured
type: ObjectProperty
range: Observable Entity
comment: This property associates an instance of S21 Measurement with the instance of S15 Observable Entity to which it applied. An instance of S15 Observable 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.
notation: O24
domain: Measurement

has type
type: ObjectProperty
range: Physical Human-Made Thing Type
comment: Associates a physical human-made thing with a type which expresses its essential classification.
notation: P1
domain: Physical Man-Made Thing
sub property of: has type

is identified by
type: ObjectProperty
range: Appellation
comment: 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.
notation: P1
domain: CRM Entity

has item type
type: ObjectProperty
range: Item Type
comment: Associates an Item (F5) with the type which defines its identity
notation: P2
domain: Item
sub property of: has type

has type
type: ObjectProperty
range: Type
comment: 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.
notation: P2
domain: CRM Entity

has digital object type
type: ObjectProperty
range: Digital Object Type
comment: Associates a digital object with the type which defines its identity
notation: P3
domain: Digital Object
sub property of: has type

has note
type: ObjectProperty
range: String
comment: 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.
notation: P3
domain: CRM Entity

has expression type
type: ObjectProperty
range: Expression Type
comment: Associates an expression with the type which defines its identity
notation: P4
domain: Expression
sub property of: has type

has time-span
type: ObjectProperty
range: Time-Span
comment: 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.
notation: P4
domain: Temporal Entity

has type of manifestation product type
type: ObjectProperty
range: Type of manifestation product type
comment: Associates a manifestation product type with the type which defines its identity
notation: P5
domain: Manifestation Product Type
sub property of: has type

consists of
type: ObjectProperty
range: Condition State
comment: 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
notation: P5
domain: Condition State

has manifestation singleton type
type: ObjectProperty
range: Manifestation Singleton Type
comment: Associates a manifestation singleton with the type which defines its identity
notation: P6
domain: Manifestation Singleton
sub property of: has type

took place at
type: ObjectProperty
range: Place
comment: 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.It is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place.
notation: P7
domain: Period

took place on or within
type: ObjectProperty
range: Physical Thing
comment: 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 shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156 occupies (is occupied by) to 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.
notation: P8
domain: Period

consists of
type: ObjectProperty
range: Period
comment: 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.
notation: P9
domain: Period

has activity type
type: ObjectProperty
range: Activity Type
comment: This property associates an activity with the type which defines its identity.
notation: P9
domain: Activity
sub property of: has type
range: Identifier Type
comment: Associates the string defining the identity of the identifier
label: has identifier type
notation: P19
domain: Identifier

has time unit
type: ObjectProperty
range: Time unit
comment: Associates a duration with its time unit
notation: P10
domain: Duration
sub property of: has unit

falls within
type: ObjectProperty
range: Spacetime Volume
comment: 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.
notation: P10
domain: Spacetime Volume

has numeric dimension type
type: ObjectProperty
range: Numeric dimension type
comment: Associates a numeric dimension with its type (by analogy with the unit of measurement for distinguishing quantities having none).
notation: P11
domain: Numeric dimension
sub property of: has unit

had participant
type: ObjectProperty
range: Actor
comment: 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.
notation: P11
domain: Event

occurred in the presence of
type: ObjectProperty
range: Persistent Item
comment: 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.
notation: P12
domain: Event

has measurement unit
type: ObjectProperty
range: Length measurement unit
comment: Associates a lenght with its measurement unit
notation: P12
domain: Length
sub property of: has unit

destroyed
type: ObjectProperty
range: Physical Thing
comment: 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.
notation: P13
domain: Destruction

has measurement unit
type: ObjectProperty
range: Weight measurement unit
comment: Associates a weight with its measurement unit
notation: P13
domain: Weight
sub property of: has unit

carried out by
type: ObjectProperty
range: Actor
comment: 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.
notation: P14
domain: Activity

has measurement unit
type: ObjectProperty
range: Area measurement unit
comment: Associates an area with its measurement unit
notation: P14
domain: Area
sub property of: has unit

has measurement unit
type: ObjectProperty
range: Volume measurement unit
comment: Associates a volume with its measurement unit
notation: P15
domain: Volume
sub property of: has unit

was influenced by
type: ObjectProperty
range: CRM Entity
comment: 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.
notation: P15
domain: Activity

used specific object
type: ObjectProperty
range: Thing
comment: 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.
notation: P16
domain: Activity

has currency
type: ObjectProperty
range: Currency
comment: This property associates a monetary amount with its currency and is equivalent to crm:P180 has currency as defined in CIDOC CRM version 6.2.9.
notation: P16
domain: Monetary amount
sub property of: has unit

was motivated by
type: ObjectProperty
range: CRM Entity
comment: 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.
notation: P17
domain: Activity

is composed of part of type
type: ObjectProperty
range: Type
comment: This property models components of physical objects that are not identified as individuals but just as types. It extends the crm:P46 is composed of property to more general situation where the identification of each part of a physical thing is not identified as such.
notation: P17
domain: Physical Thing

was intended use of
type: ObjectProperty
range: Man-Made Thing
comment: 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)).
notation: P19
domain: Activity

had specific purpose
type: ObjectProperty
range: Event
comment: 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.
notation: P20
domain: Activity

same as external identifier
type: ObjectProperty
range: Identifier
comment: This property associates an entity, identified in the domain information system, with a persistent identifier provided for the same resource (be this physical or conceptual) in an external namespace i.e. in a different information system in which the entity receives an identifier (range of the property). The nature of the external identifier (database primary key, authority file number, etc.) will be provided using specific types. In case of URIs, in the sense of the Semantic Web, the subproperty crm-sup:P28 same as URI [owl:sameAs] is to be preferred.
notation: P20
domain: CRM Entity
sub property of: is identified by

had general purpose
type: ObjectProperty
range: Type
comment: 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.
notation: P21
domain: Activity

transferred title to
type: ObjectProperty
range: Actor
comment: 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.
notation: P22
domain: Acquisition

transferred title from
type: ObjectProperty
range: Actor
comment: 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.
notation: P23
domain: Acquisition

transferred title of
type: ObjectProperty
range: Physical Thing
comment: 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.
notation: P24
domain: Acquisition

moved
type: ObjectProperty
range: Physical Object
comment: This property identifies an instance of E19 Physical Object that was moved by a move event. 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.
notation: P25
domain: Move

has dimension type
type: ObjectProperty
range: Dimension Type
comment: Associates a dimension with a type which expresses its essential classification.
notation: P25
domain: Dimension
sub property of: has type

moved to
type: ObjectProperty
range: Place
comment: This property identifies a 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 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.
notation: P26
domain: Move

moved from
type: ObjectProperty
range: Place
comment: This property identifies a 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 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.
notation: P27
domain: Move

has performance type
type: ObjectProperty
range: Performance Type
comment: This property associates a performance with the type which defines its identity
notation: P27
domain: Performance
sub property of: has type

same as URI [owl:sameAs]
type: ObjectProperty
range: Uniform Resource Identifier (URI)
comment: This property is equivalent to the owl:sameAs property: it associates an entity in an information system with the URI that the same entity or resource has in another namespace (e.g. VIAF, IdRef, DBPedia, Wikidata) , in the context of the Semantic Web.
notation: P28
domain: CRM Entity
sub property of: same as external identifier

custody surrendered by
type: ObjectProperty
range: Actor
comment: 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.
notation: P28
domain: Transfer of Custody

custody received by
type: ObjectProperty
range: Actor
comment: 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.
notation: P29
domain: Transfer of Custody

has move identifying type
type: ObjectProperty
range: Move Type
comment: Associates a move with the type which defines its identity
notation: P29
domain: Move
sub property of: has type

transferred custody of
type: ObjectProperty
range: Physical Thing
comment: 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.
notation: P30
domain: Transfer of Custody

observed entity type
type: ObjectProperty
range: Observed Entity Type
comment: This property associates an instance of S4 Observation with the instancean Observed Entity Type, i.e. a type classifying the value assigned to an entity observed by S4 Observation.
notation: P30
domain: Observation
sub property of: has type

has serial work type
type: ObjectProperty
range: Serial Work Type
comment: This property allows sub typing of frbroo:F18 Serial Work instances - a form of specialisation – through the use of a terminological hierarchy, or thesaurus.
notation: P31
domain: Serial Work
sub property of: has type

has modified
type: ObjectProperty
range: Physical Man-Made Thing
comment: 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.
notation: P31
domain: Modification

used general technique
type: ObjectProperty
range: Type
comment: This property identifies the technique or method that was employed in an 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. This property identifies the technique that was employed in an act of modification.
notation: P32
domain: Activity

has propositional object type
type: ObjectProperty
range: Propositional Object Type
comment: Associates a propositional object with a type which expresses its essential classification.
notation: P32
domain: Propositional Object
sub property of: has type

used specific technique
type: ObjectProperty
range: Design or Procedure
comment: 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.
notation: P33
domain: Activity

has person type
type: ObjectProperty
range: Person Type
comment: This property associates a person with the type which defines its identity.
notation: P33
domain: Person
sub property of: has type

has event type
type: ObjectProperty
range: Purpose
comment: Associates an event (crm:E5) with the type which defines its identity
notation: P34
domain: Event
sub property of: has type

concerned
type: ObjectProperty
range: Physical Thing
comment: 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.
notation: P34
domain: Condition Assessment

has identified
type: ObjectProperty
range: Condition State
comment: This property identifies the E3 Condition State that was observed in an E14 Condition Assessment activity.
notation: P35
domain: Condition Assessment

assigned
type: ObjectProperty
range: Identifier
comment: 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.
notation: P37
domain: Identifier Assignment

deassigned
type: ObjectProperty
range: Identifier
comment: 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.
notation: P38
domain: Identifier Assignment

measured
type: ObjectProperty
range: CRM Entity
comment: 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.
notation: P39
domain: Measurement

observed dimension
type: ObjectProperty
range: Dimension
comment: 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.
notation: P40
domain: Measurement

classified
type: ObjectProperty
range: CRM Entity
comment: 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).
notation: P41
domain: Type Assignment

assigned
type: ObjectProperty
range: Type
comment: 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.
notation: P42
domain: Type Assignment

has dimension
type: ObjectProperty
range: Dimension
comment: 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.
notation: P43
domain: Thing

has condition
type: ObjectProperty
range: Condition State
comment: 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.
notation: P44
domain: Physical Thing

consists of
type: ObjectProperty
range: Material
comment: 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
notation: P45
domain: Physical Thing

is composed of
type: ObjectProperty
range: Physical Thing
comment: 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 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 item of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in).
notation: P46
domain: Physical Thing

has preferred identifier
type: ObjectProperty
range: Identifier
comment: 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.
notation: P48
domain: CRM Entity

has former or current keeper
type: ObjectProperty
range: Actor
comment: 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.
notation: P49
domain: Physical Thing

has current keeper
type: ObjectProperty
range: Actor
comment: This property identifies the E39 Actor or Actors who 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. 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.
notation: P50
domain: Physical Thing

has former or current owner
type: ObjectProperty
range: Actor
comment: 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.
notation: P51
domain: Physical Thing

has current owner
type: ObjectProperty
range: Actor
comment: 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 of validity of the record or database containing the statement that uses this property. 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.
notation: P52
domain: Physical Thing

has former or current location
type: ObjectProperty
range: Place
comment: 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.
notation: P53
domain: Physical Thing

has current permanent location
type: ObjectProperty
range: Place
comment: 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.
notation: P54
domain: Physical Object

has current location
type: ObjectProperty
range: Place
comment: This property records the location of an 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 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.
notation: P55
domain: Physical Object

bears feature
type: ObjectProperty
range: Physical Feature
comment: This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears.An E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An E27 Site should be considered as an 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 found on the same E19 Physical Object as A.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 Definition of the CIDOC Conceptual Reference Model 149 within), E53 Place, P53 has former or current location (is former or current location of) to E26 Physical Feature.
notation: P56
domain: Physical Object

has number of parts
type: ObjectProperty
range: Number
comment: 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.
notation: P57
domain: Physical Object

has section definition
type: ObjectProperty
range: Section Definition
comment: 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.
notation: P58
domain: Physical Thing

has section
type: ObjectProperty
range: Place
comment: 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.
notation: P59
domain: Physical Thing

depicts
type: ObjectProperty
range: CRM Entity
comment: This property identifies something that is depicted by an instance of E24 Physical Man-Made Thing. Depicting is meant in the sense that the surface of the E24 Physical Man-Made Thing shows, through its passive optical qualities or form, a representation of the entity depicted. It does not pertain to inscriptions or any other information encoding. 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 E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined.
notation: P62
domain: Physical Man-Made Thing

shows visual item
type: ObjectProperty
range: Visual Item
comment: 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).
notation: P65
domain: Physical Man-Made Thing

refers to
type: ObjectProperty
range: CRM Entity
comment: 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.
notation: P67
domain: Propositional Object

foresees use of
type: ObjectProperty
range: Material
comment: 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.
notation: P68
domain: Design or Procedure

has association with
type: ObjectProperty
range: Design or Procedure
comment: 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 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.
notation: P69
domain: Design or Procedure

documents
type: ObjectProperty
range: CRM Entity
comment: 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.
notation: P70
domain: Document

lists
type: ObjectProperty
range: CRM Entity
comment: This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
notation: P71
domain: Authority Document

has language
type: ObjectProperty
range: Language
comment: 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.
notation: P72
domain: Linguistic Object

has translation
type: ObjectProperty
range: Linguistic Object
comment: 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.
notation: P73
domain: Linguistic Object

has current or former residence
type: ObjectProperty
range: Place
comment: 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.
notation: P74
domain: Actor

possesses
type: ObjectProperty
range: Right
comment: This property identifies former or current instances of E30 Rights held by an E39 Actor.
notation: P75
domain: Actor

has contact point
type: ObjectProperty
range: Contact Point
comment: 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.
notation: P76
domain: Actor

is identified by
type: ObjectProperty
range: Time Appellation
comment: This property identifies an E52 Time-Span using an E49Time Appellation.
notation: P78
domain: Time-Span

beginning is qualified by
type: ObjectProperty
range: String
comment: This property qualifies the beginning of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc.
notation: P79
domain: Time-Span

end is qualified by
type: ObjectProperty
range: String
comment: This property qualifies the end of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc.
notation: P80
domain: Time-Span

ongoing throughout
type: ObjectProperty
range: Time Primitive
comment: 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.
notation: P81
domain: Time-Span

at some time within
type: ObjectProperty
range: Time Primitive
comment: 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.
notation: P82
domain: Time-Span

had at least duration
type: ObjectProperty
range: Dimension
comment: 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.
notation: P83
domain: Time-Span

had at most duration
type: ObjectProperty
range: Dimension
comment: 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.
notation: P84
domain: Time-Span

falls within
type: ObjectProperty
range: Time-Span
comment: 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.
notation: P86
domain: Time-Span

is identified by
type: ObjectProperty
range: Place Appellation
comment: This property identifies an E53 Place using an E44 Place Appellation. Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
notation: P87
domain: Place

falls within
type: ObjectProperty
range: Place
comment: This property identifies an instance of E53 Place that falls wholly within the extent of another E53 Place. It addresses spatial containment only, and does not imply any relationship between things or phenomena occupying these places.
notation: P89
domain: Place

has value
type: ObjectProperty
range: Number
comment: This property allows an E54 Dimension to be approximated by an E60 Number primitive.
notation: P90
domain: Dimension

has unit
type: ObjectProperty
range: Measurement Unit
comment: This property shows the type of unit an E54 Dimension was expressed in.
notation: P91
domain: Dimension

brought into existence
type: ObjectProperty
range: Persistent Item
comment: 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
notation: P92
domain: Beginning of Existence

took out of existence
type: ObjectProperty
range: Persistent Item
comment: 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.
notation: P93
domain: End of Existence

has created
type: ObjectProperty
range: Conceptual Object
comment: 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.
notation: P94
domain: Creation

has formed
type: ObjectProperty
range: Group
comment: This property links the founding or E66 Formation for an E74 Group with the Group itself.
notation: P95
domain: Formation

by mother
type: ObjectProperty
range: Person
comment: 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).
notation: P96
domain: Birth

from father
type: ObjectProperty
range: Person
comment: 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.
notation: P97
domain: Birth

brought into life
type: ObjectProperty
range: Person
comment: 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.
notation: P98
domain: Birth

dissolved
type: ObjectProperty
range: Group
comment: This property links the disbanding or E68 Dissolution of an E74 Group to the Group itself.
notation: P99
domain: Dissolution

was death of
type: ObjectProperty
range: Person
comment: This property 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.
notation: P100
domain: Death

had as general use
type: ObjectProperty
range: Type
comment: 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.
notation: P101
domain: Thing

has title
type: ObjectProperty
range: Title
comment: 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.
notation: P102
domain: Man-Made Thing

was intended for
type: ObjectProperty
range: Type
comment: 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).
notation: P103
domain: Man-Made Thing

is subject to
type: ObjectProperty
range: Right
comment: 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).
notation: P104
domain: Legal Object

right held by
type: ObjectProperty
range: Actor
comment: 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.
notation: P105
domain: Legal Object

is composed of
type: ObjectProperty
range: Symbolic Object
comment: 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.
notation: P106
domain: Symbolic Object

has current or former member
type: ObjectProperty
range: Actor
comment: 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 ActorThe property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group.
notation: P107
domain: Group

has produced
type: ObjectProperty
range: Physical Man-Made Thing
comment: 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.
notation: P108
domain: Production

has current or former curator
type: ObjectProperty
range: Actor
comment: This property identifies the E39 Actor or Actors who assume or have assumed overall curatorial responsibility for an E78 Collection. 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.
notation: P109
domain: Collection

augmented
type: ObjectProperty
range: Physical Man-Made Thing
comment: 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.
notation: P110
domain: Part Addition

added
type: ObjectProperty
range: Physical Thing
comment: This property identifies the E18 Physical Thing that is added during an E79 Part Addition activity
notation: P111
domain: Part Addition

diminished
type: ObjectProperty
range: Physical Man-Made Thing
comment: 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.
notation: P112
domain: Part Removal

removed
type: ObjectProperty
range: Physical Thing
comment: This property identifies the E18 Physical Thing that is removed during an E80 Part Removal activity.
notation: P113
domain: Part Removal

is equal in time to
type: ObjectProperty
range: Temporal Entity
comment: 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).
notation: P114
domain: Temporal Entity

finishes
type: ObjectProperty
range: Temporal Entity
comment: 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).
notation: P115
domain: Temporal Entity

starts
type: ObjectProperty
range: Temporal Entity
comment: 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).
notation: P116
domain: Temporal Entity

occurs during
type: ObjectProperty
range: Temporal Entity
comment: 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).
notation: P117
domain: Temporal Entity

overlaps in time with
type: ObjectProperty
range: Temporal Entity
comment: 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).
notation: P118
domain: Temporal Entity

meets in time with
type: ObjectProperty
range: Temporal Entity
comment: 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).
notation: P119
domain: Temporal Entity

occurs before
type: ObjectProperty
range: Temporal Entity
comment: 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).
notation: P120
domain: Temporal Entity

overlaps with
type: ObjectProperty
range: Place
comment: 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.
notation: P121
domain: Place

borders with
type: ObjectProperty
range: Place
comment: 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.
notation: P122
domain: Place

resulted in
type: ObjectProperty
range: Persistent Item
comment: 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.
notation: P123
domain: Transformation

transformed
type: ObjectProperty
range: Persistent Item
comment: 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.
notation: P124
domain: Transformation

used object of type
type: ObjectProperty
range: Type
comment: 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".
notation: P125
domain: Activity

employed
type: ObjectProperty
range: Material
comment: 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.
notation: P126
domain: Modification

has broader term
type: ObjectProperty
range: Type
comment: 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
notation: P127
domain: Type

carries
type: ObjectProperty
range: Symbolic Object
comment: This property identifies an E90 Symbolic Object carried by an instance of E18 Physical Thing.
notation: P128
domain: Physical Thing

is about
type: ObjectProperty
range: CRM Entity
comment: 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.
notation: P129
domain: Propositional Object

shows features of
type: ObjectProperty
range: Thing
comment: 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.
notation: P130
domain: Thing

is identified by
type: ObjectProperty
range: Actor Appellation
comment: 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.
notation: P131
domain: Actor

overlaps with
type: ObjectProperty
range: Spacetime Volume
comment: 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.
notation: P132
domain: Spacetime Volume

is separated from
type: ObjectProperty
range: Spacetime Volume
comment: 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.
notation: P133
domain: Spacetime Volume

continued
type: ObjectProperty
range: Activity
comment: 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.
notation: P134
domain: Activity

created type
type: ObjectProperty
range: Type
comment: This property identifies the E55 Type, which is created in an E83Type Creation activity.
notation: P135
domain: Type Creation

was based on
type: ObjectProperty
range: CRM Entity
comment: 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".
notation: P136
domain: Type Creation

exemplifies
type: ObjectProperty
range: Type
comment: This property allows an item to be declared as a particular example of an E55 Type or taxonThe 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.
notation: P137
domain: CRM Entity

represents
type: ObjectProperty
range: CRM Entity
comment: 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. 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.
notation: P138
domain: Visual Item

has alternative form
type: ObjectProperty
range: Appellation
comment: 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..
notation: P139
domain: Appellation

assigned attribute to
type: ObjectProperty
range: CRM Entity
comment: This property indicates the item to which an attribute or relation is assigned.
notation: P140
domain: Attribute Assignment

assigned
type: ObjectProperty
range: CRM Entity
comment: 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.
notation: P141
domain: Attribute Assignment

used constituent
type: ObjectProperty
range: Symbolic Object
comment: 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.
notation: P142
domain: Identifier Assignment

joined
type: ObjectProperty
range: Actor
comment: 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).
notation: P143
domain: Joining

joined with
type: ObjectProperty
range: Group
comment: 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.
notation: P144
domain: Joining

separated
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving.
notation: P145
domain: Leaving

separated from
type: ObjectProperty
range: Group
comment: 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.
notation: P146
domain: Leaving

curated
type: ObjectProperty
range: Collection
comment: This property associates an instance of E87 Curation Activity with the instance of E78 Collection that is subject of that curation activity.
notation: P147
domain: Curation Activity

has component
type: ObjectProperty
range: Propositional Object
comment: 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.
notation: P148
domain: Propositional Object

is identified by
type: ObjectProperty
range: Conceptual Object Appellation
comment: This property identifies an instance of E28 Conceptual Object using an instance of E75 Conceptual Object Appellation.
notation: P149
domain: Conceptual Object

defines typical parts of
type: ObjectProperty
range: Type
comment: The property "broaderPartitive" associates an instance of E55 Type “A” with an instance of E55 Type “B”, when items of type “A” typically form part of items of type “B”, such as “car motors” and “cars”. It allows Types to be organised into hierarchies. This is the sense of "broader term partitive (BTP)" as defined in ISO 2788 and “broaderPartitive” in SKOS.
notation: P150
domain: Type

was formed from
type: ObjectProperty
range: Group
comment: This property associates an instance of E66 Formation with an instance of E74 Group from which the new group was formed preserving a sense of continuity such as in mission, membership or tradition.
notation: P151
domain: Formation

has parent
type: ObjectProperty
range: Person
comment: This property associates an instance of E21 Person with another instance of E21 Person who plays the role of the first instance’s parent, regardless of whether the relationship is biological parenthood, assumed or pretended biological parenthood or an equivalent legal status of rights and obligations obtained by a social or legal act. This property is, among others, a shortcut of the fully developed paths from ‘E21Person’ through ‘P98i was born’, ‘E67 Birth’, ‘P96 by mother’ to ‘E21 Person’, and from ‘E21Person’ through ‘P98i was born’, ‘E67 Birth’, ‘P97 from father’ to ‘E21 Person’.
notation: P152
domain: Person

occupies
type: ObjectProperty
range: Place
comment: This property describes the largest volume in space that an instance of E18 Physical Thing has occupied at any time during its existence, with respect to the reference space relative to itself. This allows you to describe the thing itself as a place that may contain other things, such as a box that may contain coins. In other words, it is the volume that contains all the points which the thing has covered at some time during its existence. In the case of an E26 Physical Feature the default reference space is the one in which the object that bears the feature or at least the surrounding matter of the feature is at rest. In this case there is a 1:1 relation of E26 Feature and E53 Place. For simplicity of implementation multiple inheritance (E26 Feature IsA E53 Place) may be a practical approach. For instances of E19 Physical Objects the default reference space is the one which is at rest to the object itself, i.e. which moves together with the object. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces. This property is a subproperty of P161 has spatial projection because it refers to its own domain as reference space for its range, whereas P161 has spatial projection may refer to a place in terms of any reference space. For some instances of E18 Physical Object the relative stability of form may not be sufficient to define a useful local reference space, for instance for an amoeba. In such cases the fully developed path to an external reference space and using a temporal validity component may be adequate to determine the place they have occupied. In contrast to P156 occupies, the property P53 has former or current location identifies an instance of E53 Place at which a thing is or has been for some unspecified time span. Further it does not constrain the reference space of the referred instance of P53 Place.
notation: P156
domain: Physical Thing

is at rest relative to
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of P53 Place with the instance of E18 Physical Thing that determines a reference space for this instance of P53 Place by being at rest with respect to this reference space. The relative stability of form of an E18 Physical Thing defines its default reference space. The reference space is not spatially limited to the referred thing. For example, a ship determines a reference space in terms of which other ships in its neighbourhood may be described. Larger constellations of matter, such as continental plates, may comprise many physical features that are at rest with them and define the same reference space.
notation: P157
domain: Place

has temporal projection
type: ObjectProperty
range: Time-Span
comment: This property describes the temporal projection of an instance of an E92 Spacetime Volume. The property P4 has time-span is the same as P160 has temporal projection if it is used to document an instance of E4 Period or any subclass of it.
notation: P160
domain: Spacetime Volume

has spatial projection
type: ObjectProperty
range: Place
comment: This property associates an instance of a E92 Spacetime Volume with an instance of E53 Place that is the result of the spatial projection of the instance of a E92 Spacetime Volume on a reference space. In general there can be more than one useful reference space to describe the spatial projection of a spacetime volume, such as that of a battle ship versus that of the seafloor. Therefore the projection is not unique.This is part of the fully developed path that is shortcut by P7took place at (witnessed).The more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place.
notation: P161
domain: Spacetime Volume

during
type: ObjectProperty
range: Time-Span
comment: This property relates an E93 Presence with an arbitrary E52 Time-Span that defines the section of the spacetime volume that this instance of E93 Presence is related to by P166 was a presence of (had presence) that is concerned by this instance of E93 Presence.
notation: P164
domain: Presence

incorporates
type: ObjectProperty
range: Symbolic Object
comment: This property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page.
notation: P165
domain: Information Object

was a presence of
type: ObjectProperty
range: Spacetime Volume
comment: This property relates an E93 Presence with the STV it is part of…
notation: P166
domain: Presence

was at
type: ObjectProperty
range: Place
comment: This property points to a wider area in which my thing /event was…
notation: P167
domain: Presence

place is defined by
type: ObjectProperty
range: Space Primitive
comment: This property associates an instance of E53 Place with an instance of E94 Space Primitive that defines it. Syntactic variants or use of different scripts may result in multiple instances of E94 Space Primitive defining exactly the same place. Transformations between different reference systems in general result in new definitions of places approximating each other and not in alternative definitions. Note that it is possible for a place to be defined by phenomena causal to it or other forms of identification rather than by an instance of E94 Space Primitive. In this case, this property must not be used for approximating the respective instance of E53 Place with an instance of E94 Space Primitive.
notation: P168
domain: Place

end of the begin
type: ObjectProperty
range: Time Primitive
comment: This is defined as the first boundary of the property P81
notation: P81a
domain: Time-Span

begin of the begin
type: ObjectProperty
range: Time Primitive
comment: This is defined as the first boundary of the property P82
notation: P82a
domain: Time-Span

begin of the end
type: ObjectProperty
range: Time Primitive
comment: This is defined as the second boundary of the property P81
notation: P81b
domain: Time-Span

end of the end
type: ObjectProperty
range: Time Primitive
comment: This is defined as the second boundary of the property P82
notation: P82b
domain: Time-Span

is logical successor of
type: ObjectProperty
range: Work
comment: This property associates an instance of F1 Work which logically continues the content of another instance of F1 Work with the latter.
notation: R1
domain: Work

is derivative of
type: ObjectProperty
range: Work
comment: This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter. The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation etc.
notation: R2
domain: Work

is realised in
type: ObjectProperty
range: Self-Contained Expression
comment: This property associates an instance of F22 Self-Contained Expression with an instance of F1 Work. This property expresses the association that exists between an expression (F22) and the work that this expression conveys. The semantics of the association will be different depending on what specific subtype of F1 Work the work is an instance of. If the work is an instance of F14 Individual Work, the F22 Self-Contained Expression completely conveys the individual work. If the work is an instance of F15 Complex Work, the F22 Self-Contained Expression conveys an alternative member of the complex work. Our factual knowledge of how a given work is realised into an expression is often limited and this property makes it possible to express the association between instances of F22 Self-Contained Expression and the work it conveys without using the more developed paths. The property R3.1 has type: E55 Type allows for specifying the role played by the referred to expression in the overall bibliographic history of the work (e.g., ‘progenitor expression’, on which all other expressions of the same work are based; ‘reference for canonical citations’, in the sense of the HuCit ontology developed by Matteo Romanello and Michele Pasin; ‘earliest draft’, ‘intermediate draft’, ‘final clean draft’, ‘princeps edition’, etc.).
notation: R3
domain: Work

carriers provided by
type: ObjectProperty
range: Manifestation Product Type
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F2 Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This property is a shortcut of: F2 Expression P165i is incorporated in F24 Publication Expression CLR6i should be carried by F3 Manifestation Product Type.
notation: R4
domain: Expression

has component
type: ObjectProperty
range: Self-Contained Expression
comment: This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X. It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by P165 incorporates.
notation: R5
domain: Expression

carries
type: ObjectProperty
range: Publication Expression
comment: This property associates an instance of F54 Utilised Information Carrier with the unique instance of F24 Publication Expression it carries.
notation: R6
domain: Utilized Information Carrier

is example of
type: ObjectProperty
range: Manifestation Product Type
comment: This property associates a publication with one of its exemplars. It is a shortcut of the more developed path: F5 Item R28i was produced by F32 Carrier Production R26 produced things of type (was produced by): F3 Manifestation Product Type.
notation: R7
domain: Item

consists of
type: ObjectProperty
range: Symbolic Object
comment: This property associates an instance of F13 Identifier with one of the non-syntactic instances of E90 Symbolic Object which form part of it.
notation: R8
domain: Identifier

is realised in
type: ObjectProperty
range: Self-Contained Expression
comment: This property associates an F14 Individual Work with the unique F22 Self-Contained Expression that completely conveys it. It is a shortcut for the more developed path: F14 Individual Work R19i was realised through F28 Expression Creation R17 created F22 Self-Contained Expression.
notation: R9
domain: Individual Work

has member
type: ObjectProperty
range: Work
comment: This property associates an instance of F15 Complex Work with an instance of F1 Work that forms part of it.
notation: R10
domain: Complex Work

has issuing rule
type: ObjectProperty
range: Design or Procedure
comment: This property associates an instance of F18 Serial Work with the instance of E29 Design or Procedure that specifies the issuing policy planned by this Work, such as sequencing pattern, expected frequency and expected regularity. This property is a shortcut of the full path: F18 Serial Work R23i was realised through F30 Publication Event P16 used specific object E29 Design or Procedure.
notation: R11
domain: Serial Work

is realised in
type: ObjectProperty
range: Performance Plan
comment: This property associates an instance of F20 Performance Work with an instance of F25 Performance Plan that consists of signs (words, figures, etc.) which express the directions the instance of F20 Performance Work consists of.
notation: R12
domain: Performance Work

is realised in
type: ObjectProperty
range: Recording
comment: This property associates an instance of F21 Recording Work with an instance of F26 Recording realising the instance of F21 Recording Work. This is a shortcut of the more elaborated path through R22 was realised through, F29 Recording Event and R21 created, which should be used when information about the recording event is available.
notation: R13
domain: Recording Work

has fragment
type: ObjectProperty
range: Expression Fragment
comment: This property associates the fragment of an expression and the expression of which it is a fragment.
notation: R15
domain: Expression

initiated
type: ObjectProperty
range: Work
comment: This property associates the first conception of a work and the work itself that ensued from a given initial idea. It marks the origin of the causality chain that results in a work’s coming into existence.
notation: R16
domain: Work Conception

created
type: ObjectProperty
range: Expression
comment: This property associates the expression that was first externalised during a particular creation event with that particular creation event.
notation: R17
domain: Expression Creation

created
type: ObjectProperty
range: Manifestation Singleton
comment: This property associates an instance of F28 Expression Creation with the first physical objects in which the resulting instance of F2 Expression was embodied.
notation: R18
domain: Expression Creation

created a realisation of
type: ObjectProperty
range: Work
comment: This property associates an instance of F28 Expression Creation with the corresponding instance of F14 Individual Work or an instance of F15 Complex Work of which the corresponding instance of F14 Individual Work is a member.
notation: R19
domain: Expression Creation

recorded
type: ObjectProperty
range: Temporal Entity
comment: This property associates an instance of F29 Recording Event with the instance of E2 Temporal Entity which was captured.
notation: R20
domain: Recording Event

created
type: ObjectProperty
range: Recording
comment: This property associates an instance of F29 Recording Event with the instance of F26 Recording that was created.
notation: R21
domain: Recording Event

created a realisation of
type: ObjectProperty
range: Recording Work
comment: This property associates an instance of F29 Recording Event with the instance of F21 Recording Work it realised.
notation: R22
domain: Recording Event

created a realisation of
type: ObjectProperty
range: Publication Work
comment: This property associates an instance of F30 Publication Event with the instance of F19 Publication Work it realised.
notation: R23
domain: Publication Event

created
type: ObjectProperty
range: Publication Expression
comment: This property associates the instance of F24 Publication Expression that was created during a particular F30 Publication Event with that F30 Publication Event.
notation: R24
domain: Publication Event

performed
type: ObjectProperty
range: Performance Plan
comment: This property associates an instance of F31 Performance with the instance of F25 Performance Plan to which all those participating in the performance were supposed to conform.
notation: R25
domain: Performance

produced things of type
type: ObjectProperty
range: Manifestation Product Type
comment: This property associates an instance of F32 Carrier Production Event with the instance of F3 Manifestation Product Type it produced items of.
notation: R26
domain: Carrier Production Event

used as source material
type: ObjectProperty
range: Publication Expression
comment: This property associates an instance of F32 Carrier Production Event with the set of signs provided by the publisher to be carried by all of the produced items.
notation: R27
domain: Carrier Production Event

produced
type: ObjectProperty
range: Utilized Information Carrier
comment: This property associates an instance of F32 Carrier Production Event with any one of the produced items (i.e., the instances of F5 Item or F53 Material Copy).
notation: R28
domain: Carrier Production Event

reproduced
type: ObjectProperty
range: Information Carrier
comment: This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it reproduces.
notation: R29
domain: Reproduction Event

produced
type: ObjectProperty
range: Information Carrier
comment: This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it produces.
notation: R30
domain: Reproduction Event

is reproduction of
type: ObjectProperty
range: Information Carrier
comment: This property associates an instance of E84 Information Carrier which is a reproduction of another instance of E84 Information Carrier with the latter. It is considered that a reproduction of multiple originals resulting in a single product requires a merging of those objects prior to the reproduction. Therefore an Information Carrier is regarded to be a reproduction of one and only one original. This property is a shortcut of the more fully developed path from E84 Information Carrier through R30 produced (was produced by), F33 Reproduction Event R29 reproduced (was reproduced by) to E84 Information Carrier.
notation: R31
domain: Information Carrier

is warranted by
type: ObjectProperty
range: Name Use Activity
comment: This property associates an instance of F35 Nomen Use Statement with an instance of F52 Name Use Activity which provides evidence for the use of the particular nomen in the stated sense. The association between this name use activity and a source for it may be described by the property P70 documents (is documented in).
notation: R32
domain: Nomen Use Statement

has content
type: ObjectProperty
range: String
comment: This property associates an instance of F12 Nomen with one or more equivalent serialized content models for it. In digital form the symbol arrangement constituting an instance of F12 Nomen can only be represented through a particular encoding, for example ASCII or Latin1 for the Latin script. We call such a representation a content model. The property R33.1 has encoding: E55 Type allows for specifying the encoding of a particular associated content model. Together with this specification, a content model allows for unambiguously defining a nomen independently from the encoding used for representing the content.
notation: R33
domain: Nomen

has validity period
type: ObjectProperty
range: Time-Span
comment: This property associates an instance of F34 KOS with the instance of E52 Time-Span describing the period for which the particular KOS Expression was regarded as valid by its maintainers. Each change of validity status of a nomen use statement within a KOS should be associated with a release change of the KOS. The individual time-span of a validity state of a nomen would be the union of the time-spans of the KOS in which the Nomen was declared to have the particular validity status (provisional, accepted, obsolete etc...).
notation: R34
domain: KOS

specified by
type: ObjectProperty
range: KOS
comment: This property associates an instance of F35 Nomen Use Statement with an instance of F34 KOS in which the Nomen Use Statement has a given status. The property R35.1 allows for specifying the particular status of the nomen use statement within the KOS. An instance of R35 is specified by should have only one status.
notation: R35
domain: Nomen Use Statement

uses script conversion
type: ObjectProperty
range: Script Conversion
comment: This property associates an instance of F35 Nomen Use Statement with the instance of F36 Script Conversion that was used to create the Nomen referred to in the Nomen Use Statement. The source of this conversion may or may not be explicitly mentioned. Is shortcut of: F35 Nomen Use Statement R17 was created by (created) F28 Expression Creation P33 used specific technique (was used by) E29 Design or Procedure.
notation: R36
domain: Nomen Use Statement

states as nomen
type: ObjectProperty
range: Nomen
comment: NO TEXT PROPERTY FOUND
notation: R37
domain: Nomen Use Statement

refers to thema
type: ObjectProperty
range: CRM Entity
comment: This property associates an instance of F35 Nomen Use Statement with the instance of E1 CRM Entity for which it declares the usage of a nomen.
notation: R38
domain: Nomen Use Statement

is intended for
type: ObjectProperty
range: Group
comment: This property associates an instance of F35 Nomen Use Statement with an instance of E74 Group which is the target audience for which the associated nomen use is intended. To indicate that the associated nomen is declared as preferred in all contexts, the instance of E74 Group is ‘mankind’.
notation: R39
domain: Nomen Use Statement

has representative expression
type: ObjectProperty
range: Self-Contained Expression
comment: This property identifies an instance of F22 Self-Contained Expression that has been chosen as the most characteristic expression of the instance of F1 Work of which it is an expression. There is no other semantic implication to this notion of being characteristic than to be an adequate candidate to uniquely identify the Work realized by it. Prototypically, this is the instance of F22 Self-Contained Expression that is deemed characteristic of an instance of F15 Complex Work. Typically, any expression that is not regarded as “representative” for the work it expresses, would require a controlled access point, with qualifiers specifying the differences between that expression and a representative expression, although this may not always be done in practice. The title of a Work may not be one taken from a representative expression. A given work can have more than one representative expression, provided the differences between these expressions are not deemed “substantial.” If the anticipated needs of users are not considered to call for bibliographic distinctions between variant expressions of a work, then even expressions that differ significantly from each other can be regarded as equally representative for the work. (See FRBR: Final Report, p. 19-20). A given expression can be deemed representative for a work with regard to some of its aspects (e.g., the text contained in an edition the title proper of which reads ‘The tragicall historie of HAMLET Prince of Denmarke’, and the language of that text), and not representative for it with regard to some other aspects (e.g., the title proper ‘The tragicall historie of HAMLET Prince of Denmarke’ itself, which, being different from the title that is regarded as “representative” for Shakespeare’s work, will require the use of a controlled access point). R40 has representative expression is a shortcut of the more developed path F1 Work R50i was assigned by F42 Representative Expression Assignment R51 assigned F2 Expression.
notation: R40
domain: Work

has representative manifestation product type
type: ObjectProperty
range: Manifestation Product Type
comment: This property identifies an instance of F3 Manifestation Product Type that has been chosen as the most characteristic Manifestation Product Type of the instance of F2 Expression of which it is a manifestation. Identifying an instance of F3 Manifestation Product Type that is representative for an instance of F2 Expression makes it possible in turn to identify an instance of F2 Expression that is representative for an instance of F1 Work, and to decide what should be regarded as the title of the work. The title of an Expression may not be one taken from a representative Manifestation Product Type or Manifestation Singleton. A given expression can have more than one Representative Manifestation Product Type. R41 has representative manifestation product type is a shortcut of the more developed path F2 Expression R48i was assigned by F41 Representative Manifestation Assignment R49 assigned F3 Manifestation Product Type.
notation: R41
domain: Expression

is representative manifestation singleton for
type: ObjectProperty
range: Expression
comment: This property identifies an instance of Manifestation Singleton that has been declared as the unique representative for an instance of F2 Expression by some bibliographic agency. This property identifies an instance of F4 Manifestation Singleton that has been chosen as the most characteristic Manifestation Singleton of the instance of F2 Expression of which it is a manifestation. Identifying an instance of F4 Manifestation Singleton that is representative for an instance of F2 Expression makes it possible in turn to identify an instance of F2 Expression that is representative for an instance of F1 Work, and to decide what should be regarded as the title of the work. The title of an Expression may not be one taken from a representative Manifestation Product Type or Manifestation Singleton. A given expression can have more than one representative Manifestation Singleton. It is a shortcut for the more developed path: F2 Expression R48i was assigned by F41 Representative Manifestation Assignment R53 assigned F4 Manifestation Singleton.
notation: R42
domain: Manifestation Singleton

carried out by
type: ObjectProperty
range: Bibliographic Agency
comment: This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which Manifestation (i.e., which instance of F3 Manifestation Product Type or F4 Manifestation Singleton) is representative for a given expression. In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.
notation: R43
domain: Representative Manifestation Assignment

carried out by
type: ObjectProperty
range: Bibliographic Agency
comment: This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which expression is representative for a given Work. In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.
notation: R44
domain: Representative Expression Assignment

assigned to
type: ObjectProperty
range: CRM Entity
comment: This property identifies the entity to which an actor, such as a bibliographic agency, assigned an instance of F13 Identifier.
notation: R45
domain: Identifier Assignment

assigned to
type: ObjectProperty
range: Identifier
comment: This property associates the instance of F13 Identifier assigned to an instance of E1 CRM Entity and the event of assigning it.
notation: R46
domain: Identifier Assignment

assigned to
type: ObjectProperty
range: Expression
comment: This property associates the event of assigning a representative instance of F3 Manifestation Product Type or F4 Manifestation Singleton with the expression to which it was assigned.
notation: R48
domain: Representative Manifestation Assignment

assigned
type: ObjectProperty
range: Manifestation Product Type
comment: This property associates the event of assigning a representative instance of F3 Manifestation Product Type with the F3 Manifestation Product Type which has been assigned.
notation: R49
domain: Representative Manifestation Assignment

assigned to
type: ObjectProperty
range: Complex Work
comment: This property associates the event of assigning a representative instance of F2 Expression with the instance of F15 Complex Work to which it was assigned.
notation: R50
domain: Representative Expression Assignment

assigned
type: ObjectProperty
range: Expression
comment: This property associates the event of assigning a representative instance of F2 Expression with the F2 Expression which has been assigned.
notation: R51
domain: Representative Expression Assignment

used rule
type: ObjectProperty
range: Identifier Rule
comment: This property associates the event of assigning an instance of F13 Identifier with the instructions followed by an actor, such as a Bibliographic Agency, in creating that identifier.
notation: R52
domain: Identifier Assignment

assigned
type: ObjectProperty
range: Manifestation Singleton
comment: This property associates the event of assigning a representative instance of F4 Manifestation Singleton with the F4 Manifestation Singleton which has been assigned.
notation: R53
domain: Representative Manifestation Assignment

has nomen language
type: ObjectProperty
range: Language
comment: This property associates an instance of F35 Nomen Use Statement with an instance of E56 Language which is a target language for the associated nomen use.
notation: R54
domain: Nomen Use Statement

has nomen form
type: ObjectProperty
range: Type
comment: This property associates an instance of F35 Nomen Use Statement with the instance of E55 Type that characterizes the Nomen referred to in the Nomen Use Statement, such as abbreviation, full name etc. In the case of abbreviations, the source of this form may or may not be explicitly mentioned.
notation: R55
domain: Nomen Use Statement

has related use
type: ObjectProperty
range: Nomen Use Statement
comment: This property associates an instance of F35 Nomen Use Statement with another instance of F35 Nomen Use Statement which has a related use in some context, such as alternative, lexical variant, replacing former use etc. The property R56.1 allows for specifying the particular kind of the nomen use statement relationship.
notation: R56
domain: Nomen Use Statement

is based on
type: ObjectProperty
range: Actor
comment: This property associates an instance of F38 Character with an instance of E39 Actor that the character is motivated by or is intended to represent. An instance of F38 Character may be based on a combination of features taken from several actors. This property is a shortcut of the more fully developed path from E28 Conceptual Object, restricted to F38 Character, through the inverse of P94 has created (was created by), E65 Creation P17 was motivated by (motivated) to E1 CRM Entity restricted to E39 Actor.
notation: R57
domain: Character

has fictional member
type: ObjectProperty
range: Character
comment: This property associates an instance of F38 Character representing a group with another instance of F38 Character that is presented in relevant fiction as a member of the fictional group.
notation: R58
domain: Character

had typical subject
type: ObjectProperty
range: CRM Entity
comment: This property associates an instance of F51 Pursuit with the instance of E1 CRM Entity that is the typical subject of the associated activity, such as an area of expertise in which the actor is engaged or was engaged.
notation: R59
domain: Pursuit

used to use language
type: ObjectProperty
range: Language
comment: This property associates an instance of F51 Pursuit with the instance of E56 Language that was characteristically used for the products of the associated activity. The property R60.1 has type of use allows for specifying a particular form of use.
notation: R60
domain: Pursuit

occured in kind of context
type: ObjectProperty
range: Type
comment: This property associates an instance of F52 Name Use Activity with the instance of E55 Type that characterises the kind of role or context within which the associated name was used.
notation: R61
domain: Name Use Activity

was used for membership in
type: ObjectProperty
range: Group
comment: This property associates an instance of F52 Name Use Activity with the instance of E74 Group that characterises the context within which the associated name was used for membership in that group.
notation: R62
domain: Name Use Activity

named
type: ObjectProperty
range: CRM Entity
comment: This property associates an instance of F52 Name Use Activity with the instance of E1 CRM Entity that the associated name was used for.
notation: R63
domain: Name Use Activity

used name
type: ObjectProperty
range: Appellation
comment: This property associates an instance of F52 Name Use Activity with the instance of E41 Appellation that was used for the associated entity.
notation: R64
domain: Name Use Activity

recorded aspects of
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of F29 Recording Event with an instance of E18 Physical Thing some of whose features, at the time of recording, were recorded in that process.
notation: R65
domain: Recording Event

included performed version of
type: ObjectProperty
range: Propositional Object
comment: This property associates an instance of F31 Performance with a product of the mind that was performed in the course of that instance of F31 Performance. According to the level of knowledge available about the performance, the range of this property can actually be specialised as either an instance of F1 Work (if nothing is known as to which specific expression of the work was performed), or of F2 Expression (if there is a reasonable amount of certainty as to which specific expression—e.g., a well identified translation of a play—of the work was performed). In addition to being a subproperty of P16 used specific object (was used for), this property also is a shortcut of the fully developed path that goes from F31 Performance to F1 Work through: R25 performed F25 Performance Plan P165 incorporates F22 Self-Contained Expression R3i realises. In this fully developed path, the specific instance of F22 Self-Contained Expression can be precisely identified and described for its own sake, or it can just be known to have necessarily existed.
notation: R66
domain: Performance