Creative Processes Representation Ontology Version 2.3
type: Ontology
version info: Exported from OntoME: Creative Processes Representation Ontology Version 2.3
comment: Creative Processes Representation Ontology (CPRo) is an ontological model harmonizing to the CIDOC CRM family of models that aims to facilitate the representation and integration of information related to creative processes and the materialization of ideas into reality. It has a particular focus on creative processes. The presently proposed model and its related classes and properties have been modelled to cover architectural practice, artistic production, and design activities considered broadly. Examples Used In order to illustrate the ontology's use, the specification provides a related set of examples from architecture, the rebuild project on the site of the World Trade Centre, NY, and art the "Gates of Hell" by Rodin. Future editions aim to carry examples from additional fields. Compatibility and Nomenclature This unofficial extension of the CIDOC CRM is formulated in relation to: CIDOC CRM v.7.1.3 LRMoo v.1.0 AAAo v.2.0 The specification consists of a set of declarations for formalized classes and properties that extend the CIDOC CRM and the above official extensions. Adopting the conventions of the CIDOC CRM each class and property have been given an identifier in addition to their names. The naming convention adopted for this extension is: CC = classCP = property The choice of these names was arbitrary, making a conceptual connection with the official CRM representation while clearly distinguishing the new classes and properties from those of either CRM base or its official extensions. Namespace: https://ontology.swissartresearch.net/cpro Maintenance and Archiving CPRo is an actively maintained ontology. It is our aim to develop publicly and participatively, learning from and engaging with the scholarly community that adopts it. Towards this end we maintain the ontology with the following processes and relative tools. Ontology Development We adopt the OntoMe tool developed by LARHRA to manage the ontology and produce editions. This ensures a consistent manag…

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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 identifierClassification by type, allowing further refinement of the specific subclass an instance belongs to Attachment of free text and other unstructured data for the expression of anything not captured by formal propertiesAll other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity.

Temporal Entity
type: Class
notation: E2
comment: This class comprises all phenomena, such as the instances of E4 Periods and E5 Events, which happen over a limited extent in time. This extent in time must be contiguous, i.e., without gaps. In case the defining kinds of phenomena for an instance of E2 Temporal Entity cease to happen, and occur later again at another time, we regard that the former instance of E2 Temporal Entity has ended and a new instance has come into existence. In more intuitive terms, the same event cannot happen twice.In some contexts, such phenomena are also called perdurants. This class is disjoint from E77 Persistent Item and is an abstract class that typically has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing.

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 instance of E52 Time-Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held.The nature of that condition can be described using P2 has type. For example, the instance of E3 Condition State “condition of the SS Great Britain between 22nd September 1846 and 27th August 1847” can be characterized as an instance “wrecked” of E55 Type.

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 instance of E4 Period and not the associated spatiotemporal extent. This extent is only the “ground” or space in an abstract physical sense that the actual process of growth, spread and retreat has covered. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area and time as a sedentary culture. This also means that overlapping land use rights, common among first nations, amounts to overlapping periods.Often, this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the “Ming Dynasty” or the “McCarthy Era”, but also geopolitical units and activities of settlements are regarded as special cases of E4 Period. However, there are no assumptions about the scale of the associated phenomena. In particular all events are seen as synthetic processes consisting of coherent phenomena. Therefore, E4 Period is a superclass of E5 Event. For example, a modern clinical birth, an instance of E67 Birth, can be seen as both a single event, i.e., an instance of E5 Event, and as an extended period, i.e., an instance of E4 Period, that consists of multiple physical processes and complementary activities performed by multiple instances of E39 Actor.As the actual extent of an instance of E4 Period in spacetime we regard the trajectories of the participating physical things during their participation in an instance of E4 Period. This includes the open spaces via which these things have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event. Examples include the air in a meeting room transferring the voices of the participants. Since these phenomena are fuzzy, we assume the spatiotemporal extent to be c…

Event
type: Class
notation: E5
comment: This class comprises distinct, delimited and coherent processes and interactions of a material nature, in cultural, social or physical systems, involving and affecting instances of E77 Persistent Item in a way characteristic of the kind of process. Typical examples are meetings, births, deaths, actions of decision taking, making or inventing things, but also more complex and extended ones such as conferences, elections, building of a castle, or battles.While the continuous growth of a tree lacks the limits characteristic of an event, its germination from a seed does qualify as an event. Similarly, the blowing of the wind lacks the distinctness and limits of an event, but a hurricane, flood or earthquake would qualify as an event. Mental processes are considered as events, in cases where they are connected with the material externalization of their results; for example, the creation of a poem, a performance or a change of intention that becomes obvious from subsequent actions or declarations.The effects of an instance of E5 Event may not lead to relevant permanent changes of properties or relations of the items involved in it, for example an unrecorded performance. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event.While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example, the statements made during a meeting and the listening of the audience.Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analysed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the si…

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 instance of E6 Destruction and of E7 Activity. The decision to document an object as destroyed, transformed or modified is context sensitive: If the matter remaining from the destruction is not documented, the event is modelled solely as an instance of E6 Destruction. An event should also be documented as an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as an instance of E11 Modification.

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 ownershipthe end of ownershipthe transfer of ownershipthe acquisition from an unknown sourcethe loss of title due to destruction of the itemIt may also describe events where a collector appropriates legal title, for example by annexation or field collection. The interpretation of the museum notion of "accession" differs between institutions. The CIDOC CRM therefore models legal ownership (E8 Acquisition) and physical custody (E10 Transfer of Custody) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.

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 the physical custody or the legal responsibility for the physical custody of objects. The recording of the donor or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances, it may describe: the beginning of custody (there is no previous custodian)the end of custody (there is no subsequent custodian)the transfer of custody (transfer from one custodian to the next)the receipt of custody from an unknown source (the previous custodian is unknown)the declared loss of an object (the current or subsequent custodian is unknown)In the event that only a single kind of transfer of custody occurs, either the legal responsibility for the custody or the actual physical possession of the object but not both, this difference should be expressed using the property P2 has type (is type of). The sense of physical possession requires that the object of custody be in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. The interpretation of the museum notion of "accession" differs between institutions. The CIDOC CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these. Theft is a specific case of illegal transfer of custody.

Modification
type: Class
notation: E11
comment: This class comprises instances of E7 Activity that are undertaken to create, alter or change instances of E24 Physical Human-Made Thing.This class includes the production of an item from raw materials and other so far undocumented objects. It also includes the conservation treatment of an object.Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in an instance of E11 Modification, and that others may be produced as a result of it. An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.An activity undertaken on an object which was designed to alter it, but which, in fact, it did not in any seemingly significant way (such as the application of a solvent during conservation which failed to dissolve any part of the object), is still considered as an instance of E11 Modification. Typically, any such activity will leave at least forensic traces of evidence on the object.If the instance of E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.

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 an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.

Attribute Assignment
type: Class
notation: E13
comment: This class comprises the actions of making assertions about one property of an object or any single relation between two items or concepts. The type of the property asserted to hold between two items or concepts can be described by the property P177 assigned property of type (is type of property assigned): E55 Type. For example, the class describes the actions of people making propositions and statements during certain scientific/scholarly procedures, e.g., the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on whether this information should be accessible by structured queries.This class allows for the documentation of how the respective assignment came about, and whose opinion it was. Note that all instances of properties described in a knowledge base are the opinion of someone. Per default, they are the opinion of the team maintaining the knowledge base. This fact must not individually be registered for all instances of properties provided by the maintaining team, because it would result in an endless recursion of whose opinion was the description of an opinion. Therefore, the use of instances of E13 Attribute Assignment marks the fact, that the maintaining team is in general neutral to the validity of the respective assertion, but registers someone else’s opinion and how it came about.All properties assigned in such an action can also be seen as directly relating the respective pair of items or concepts. Multiple use of instances of E13 Attribute Assignment may possibly lead to a collection of contradictory values. All cases of properties in this model that are also described indirectly through a subclass of E13 Attribute Assignment are characterised as "short cuts" of a path via this subclass. This redundant modelling of two alternative views is preferred be…

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. Instances of E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.

Measurement
type: Class
notation: E16
comment: This class comprises actions measuring quantitative physical properties and other values that can be determined by a systematic, objective procedure of direct observation of particular states of physical reality. An instance of E16 Measurement may 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. Methods and devices employed should be associated with instances of E16 Measurement by properties such as P33 used specific technique: E29 Design or Procedure, P125 used object of type: E55 Type, P16 used specific object (was used for): E70 Thing, whereas basic techniques such as "carbon-14 dating" should be encoded using P2 has type (is type of): E55 Type. Details of methods and devices reused or reusable in other instances of E16 Measurement should be documented for these entities rather than the measurements themselves, whereas details of particular execution may be documented by free text or by instantiating adequate sub-activities, if the detail may be of interest for an overarching query.Regardless whether a measurement is made by an instrument or by human senses, it represents the initial transition from physical reality to information without any other documented information object in between within the reasoning chain that would represent the result of the interaction of the observer or device with reality. Therefore, determining properties of an instance of E90 Symbolic Object is regarded as an instance of E13 Attribute Assignment, which may be inferred from observing and measuring representative carriers. In the case that the carrier can be named, the property P16 used specific object (was used for): should be used to indicate the…

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, human-made or natural.Depending on the existence of natural boundaries of such things, the CIDOC CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter.An instance of E18 Physical Thing occupies not only a particular geometric space at any instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces, such as the interior of a box. For the purpose of more detailed descriptions of the presence of an instance of E18 Physical Thing in space and time it can be associated with its specific instance of E92 Spacetime Volume by the property P196 defines (is defined by). The CIDOC CRM is generally not concerned with amounts of matter in fluid or gaseous states, as long as they are not confined in an identifiable way for an identifiable minimal time-span.

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 CIDOC CRM does not propose a specific form to support reasoning about possible identity.In a bibliographic context, a name presented following the conventions usually employed for personal names will be assumed to correspond to an actual real person (an instance of E21 Person), unless evidence is available to indicate that this is not the case. The fact that a persona may erroneously be classified as an instance of E21 Person does not imply that the concept comprises personae.

Physical Human-Made Thing
type: Class
notation: E24
comment: This class comprises all persistent physical items of any size that are purposely created by human activity. This class comprises, besides others, Human-Made objects, such as a sword, and Human-Made features, such as rock art. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Human-Made Thing.Instances of Human-Made thing may be the result of modifying pre-existing physical things, preserving larger parts or most of the original matter and structure, which poses the question if they are new or even Human-Made, the respective interventions of production made on such original material should be obvious and sufficient to regard that the product has a new, distinct identity and intended function and is human-made. Substantial continuity of the previous matter and structure in the new product can be documented by describing the production process also as an instance of E81 Transformation.Whereas interventions of conservation and repair are not regarded to produce a new Human-Made thing, the results of preparation of natural history specimens that substantially change their natural or original state should be regarded as physical Human-Made things, including the uncovering of petrified biological features from a solid piece of stone. On the other side, scribbling a museum number on a natural object should not be regarded to make it Human-Made. This notwithstanding, parts, sections, segments, or features of a physical Human-Made thing may continue to be non-Human-Made and preserved during the production process, for example natural pearls used as a part of an eardrop.

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

Site
type: Class
notation: E27
comment: This class comprises pieces of land or sea floor. In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings and maps.Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location.

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 new instances of E71 Human-Made Thing or for shaping or guiding the execution of an instance of E7 Activity.Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others.This is modelled using P69 has association with (is associated with): E29 Design or Procedure.Designs or procedures can be seen as one of the followingA schema for the activities it describesA schema of the products that result from their application.An independent intellectual product that may have never been applied, such as Leonardo da Vinci’s famous plans for flying machines.Because designs or procedures may never be applied or only partially executed, the CIDOC CRM models a loose relationship between the plan and the respective product.

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 instances of E31 Document. This class should not be confused with the concept “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 CIDOC CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CIDOC CRM. These should be modelled as instances of E73 Information Object.In general, an instance of E33 Linguistic Object may also contain non-linguistic information, often of artistic or aesthetic value. Only in cases in which the content of an instance of E33 Linguistic Object can completely be expressed by a series of binary-encoded symbols, its content may be documented within a respective knowledge base by the property P190 has symbolic content: E62 String. Otherwise, it should be understood as an identifiable digital resource only available independently from the respective knowledge base. In other cases, such as pages of an illuminated manuscript or recordings containing speech in a language supported by a writing system, the linguistic part of the content of an instance of E33 Linguistic Object may be documented within a respective knowledge base in a note by P3 has note: E62 String. Otherwise, it may be described using the property P165 incorporates (is incorporated in): E73 Information Object as a different object with its own identity.

Title
type: Class
notation: E35
comment: This class comprises textual strings that within a cultural context can be clearly identified as titles due to their form. Being a subclass of E41 Appellation, E35 Title can only be used when such a string is actually used as a title of a work, such as a text, an artwork, or a piece of music.Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group.This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.

Visual Item
type: Class
notation: E36
comment: This class comprises the intellectual or conceptual aspects of recognisable marks, images and other visual works.This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support.The class E36 Visual Item provides a means of identifying and linking together instances of E24 Physical Human-Made Thing that carry the same visual qualities (symbols, marks or images etc.). The property P62 depicts (is depicted by) between E24 Physical Human-Made Thing and depicted subjects (E1 CRM Entity) is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity, which in addition captures the optical features of the depiction.

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.

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.Different languages may use different appellations for the same thing, such as the names of major cities. Some appellations may be formulated using a valid noun phrase of a particular language. In these cases, the respective instances of E41 Appellation should also be declared as instances of E33 Linguistic Object. Then the language using the appellation can be declared with the property P72 has language: E56 Language.Instances of E41 Appellation may be used to identify any instance of E1 CRM Entity and sometimes are characteristic for instances of more specific subclasses E1 CRM Entity, such as for instances of E52 Time-Span (for instance “dates”), E39 Actor, E53 Place or E28 Conceptual Object. Postal addresses and E-mail addresses are characteristic examples of identifiers used by services transporting things between clients.Even numerically expressed identifiers for extents in space or time are also regarded as instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though they allow for determining some time or location by a known procedure starting from a reference point and by virtue of that fact play a double role as instances of E59 Primitive Value.E41 Appellation should not be confused with the act of naming something. Cf. E15 …

Identifier
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. Postal addresses, telephone numbers, URLs and e-mail addresses are characteristic examples of identifiers used by services transporting things between clients.The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.

Time-Span
type: Class
notation: E52
comment: This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration. Instances of E52 Time-Span have no semantic connotations about phenomena happening within the temporal extent they represent. They do not convey any meaning other than a positioning on the “time-line” of chronology. The actual extent of an instance of E52 Time-Span can be approximated by properties of E52 Time-Span giving inner and outer bounds in the form of dates (instances of E61 Time Primitive). Comparing knowledge about time-spans is fundamental for chronological reasoning.Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which we can infer knowledge about it, such as in relative chronologies.Some instances of E52 may be defined precisely as representing a declaration of a temporal extent, as, for instance, done in a business contract. They constitute declarative time-spans as defined in CRMgeo (Doerr Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span. When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known.

Place
type: Class
notation: E53
comment: This class comprises extents in the natural space we live in, in particular on the surface of the Earth, in the pure sense of physics: independent from temporal phenomena and matter. They may serve describing the physical location of things or phenomena or other areas of interest. Geometrically, instances of E53 Place constitute single contiguous areas or a finite aggregation of disjoint areas in space which are each individually contiguous. They may have fuzzy boundaries. The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks, but may also be determined by reference to mobile objects. A Place can be determined by combining a frame of reference and a location with respect to this frame. It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.Any instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for).

Dimension
type: Class
notation: E54
comment: This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e., by points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.An instance of E54 Dimension represents the empirical or theoretically derived quantity, including the precision tolerances resulting from the particular method or calculation. The identity of an instance of E54 Dimension depends on the method of its determination because each method may produce different values even when determining comparable qualities. For instance, the wingspan of a bird alive or dead is a different dimension. Thermoluninescence dating and Rehydroxylation [RHX] dating are different dimensions of temporal distance from now, even if they aim at dating the same object. The method of determination should be expressed using the property P2 has type (is type of). Note that simple terms such as “diameter” or “length” are normally insufficient to unambiguously describe a respective dimension. In contrast, “maximum linear extent” may be sufficient.The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension adequate to the precision of the applied method of determination. If the respective quantity belongs to a non-discrete space according to the laws of physics, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that comparability of values described in different units depends critically on the representation as value regions.Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional …

Type
type: Class
notation: E55
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CIDOC CRM classes. E55 Type is the CIDOC CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CIDOC CRM as subclasses of E55 Type, forming hierarchies of terms, i.e., instances of E55 Type linked via P127 has broader term (has narrower term): E55 Type. Such hierarchies may be extended with additional properties.

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-2:1998 and later versions.

Material
type: Class
notation: E57
comment: This class is a specialization of E55 Type and comprises the concepts of materials. Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of (forms part of): E18 Physical Thing).This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.It is recommended that internationally or nationally agreed codes and terminology are used.

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, such as those defined by ISO80000:2009. 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 numerically expressed identifiers in continua, which are instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension.

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 references to temporal coordinate systems to express time in some context relevant to cultural and scientific documentation.Instantiating different instances of E61 Time Primitive relative to the same instance of E52 Time-Span allows for the expression of multiple opinions/approximations of the same phenomenon. When representing different opinions/approximations of the E52 Time-Span of some E2 Temporal Entity, multiple instances of E61 Time Primitive should be instantiated relative to one E52 Time-Span. Only one E52 Time-Span should be instantiated since there is only one real phenomenal time extent of any given temporal entity.The instances of E61 Time Primitive are not considered as elements of the universe of discourse that the CIDOC CRM aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.Therefore, they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class.

String
type: Class
notation: E62
comment: This class comprises coherent sequences of binary-encoded symbols. They correspond to the content of an instance of E90 Symbolic object. Instances of E62 String represent only the symbol sequence itself. They may or may not contain a language code. In contrast, instances of other subclasses of E59 Primitive value represent entities in mathematical spaces other than that of symbol sequences, by using binary-encoded symbols, such as date expressions or numbers in decimal encoding. For instance, different syntactic forms of a date expression may represent the same date but consist of different strings.

Beginning of Existence
type: Class
notation: E63
comment: This class comprises events that bring into existence any instance of E77 Persistent Item. It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”.

End of Existence
type: Class
notation: E64
comment: This class comprises events that end the existence of any instance of E77 Persistent Item. It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”. In cases where substance from an instance of E77 Persistent Item continues to exist in a new form, the process would be documented as instances of 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 being). Twins, triplets etc. are typically brought into life by the same instance of E67 Birth. The introduction of E67 Birth as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the birth.

Dissolution
type: Class
notation: E68
comment: This class comprises the events that result in the formal or informal termination of an instance of E74 Group. If the dissolution was deliberate, the Dissolution event should also be instantiated as an instance of E7 Activity.

Death
type: Class
notation: E69
comment: This class comprises the deaths of human beings. If a person is killed, the death should be documented as an instance of both E69 Death and E7 Activity. The death or perishing of other living beings should be documented as instances of E64 End of Existence.

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.

Human-Made Thing
type: Class
notation: E71
comment: This class comprises discrete, identifiable human-made items that are documented as single units. These items are either intellectual products or human-made physical things, and are characterized by relative stability. They may for instance have a solid physical form, an electronic encoding, or they may be logical concepts or structures.

Legal Object
type: Class
notation: E72
comment: This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied. This is true for all instances of E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of an instance of E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CIDOC CRM.

Information Object
type: Class
notation: E73
comment: This class comprises identifiable immaterial items, such as poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. The encoding structure known as a "named graph" also falls under this class, so that each "named graph" is an instance of E73 Information Object.An instance of E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously.Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression.

Group
type: Class
notation: E74
comment: This class comprises any gatherings or organizations of human individuals or groups that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. In such cases, it may happen that the group never had more than one member. A joint pseudonym (i.e., a name that seems indicative of an individual but that is actually used as a persona by two or more people) is a particular case of E74 Group.A gathering of people becomes an instance of E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modelled as membership in an instance of E74 Group. Married couples and other concepts of family are regarded as particular examples of E74 Group.

Persistent Item
type: Class
notation: E77
comment: This class comprises items that have persistent characteristics of structural nature substantially related to their identity and their integrity, sometimes known as “endurants” in philosophy. Persistent Items may be physical entities, such as people, animals or things, conceptual entities such as ideas, concepts, products of the imagination or even names. Instances of E77 Persistent Item may be present or be part of interactions in different periods or events. They can repeatedly be recognized at disparate occasions during their existence by characteristics of structural nature. The respective characteristics need not be exactly the same during all the existence of an instance of E77 Persistent Item. Often, they undergo gradual change, still bearing some similarities with that of previous times, or disappear completely and new emerge. For instance, a person, from the time of being born on, will gradually change all its features and acquire new ones, such as a scar. Even the DNA in different body cells will develop defects and mutations. Nevertheless, relevant characteristics used should be sufficiently similar to recognize the instance for some substantial period of time. The more specific criteria that determine the identity of instances of subclasses of E77 Persistent Item may vary considerably and are described or referred to in the respective scope notes. The decision about which exact criteria to use depends on whether the observable behaviour of the respective part of reality such confined conforms to the reasoning the user is interested in. For example, a building can be regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria, such as being bodily separated from other persons. Similarly, inanimate objects may be subject to ex…

Curated Holding
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. Typical instances of curated holdings are museum collections, archives, library holdings and digital libraries. A digital library is regarded as an instance of E18 Physical Thing because it requires keeping physical carriers of the electronic content.Items may be added or removed from an E78 Curated Holding in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Curated Holding often referred to with the name of the E78 Curated Holding (e.g., “The Wallace Collection decided…”). Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Curated Holding. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.

Part Addition
type: Class
notation: E79
comment: This class comprises activities that result in an instance of E18 Physical Thing being increased, enlarged or augmented by the addition of a part. Typical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated instance of E78 Curated Holding. Both the E18 Physical Thing being augmented and the E18 Physical Thing that is being added are treated as separate identifiable wholes prior to the instance of E79 Part Addition. Following the addition of parts, the resulting 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 artefacts being added to different museum instances of E78 Curated Holding 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 collection, an instance of E78 Curated Holding. If the instance of E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an instance of E81 Transformation, i.e., a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be modelled as both an instance of E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewellery, 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 E18 Physical Thing and the creation of one or more than one E18 Physical Thing that preserves recognizable substance and structure from the first one(s) but has fundamentally different nature or identity.Although the old and the new instances of E18 Physical Thing are treated as discrete entities having separate, unique identities, they are causally connected through the E81 Transformation; the destruction of the old E18 Physical Thing(s) directly causes the creation of the new one(s) using or preserving some relevant substance and structure. Instances of E81 Transformation are therefore distinct from re-classifications (documented using E17 Type Assignment) or modifications (documented using E11 Modification) of objects that do not fundamentally change their nature or identity. Characteristic cases are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimen in natural history.Even though such instances of E81 Transformation are often motivated by a change of intended use, substantial material changes should justify the documentation of the result as a new instance of E18 Physical Thing and not just the change of function. The latter may be documented as an extended activity (instance of E7 Activity) of using it.

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 modelled as an instance of E83 Type Creation is central to research in the life sciences, where a type would be referred to as a “taxon,” the type description as a “protologue,” and the exemplary specimens as “original element” or “holotype”.

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 Curated Holding, following an implicit or explicit curation plan. It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded.Items are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an instance of E78 Curated Holding for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity.

Propositional Object
type: Class
notation: E89
comment: This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse. This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.

Symbolic Object
type: Class
notation: E90
comment: This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note and its subproperty P190 has symbolic content allow for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g., "bit", "Latin character", RGB pixel).

Spacetime Volume
type: Class
notation: E92
comment: This class comprises 4-dimensional point sets (volumes) in physical spacetime (in contrast to mathematical models of it) regardless their true geometric forms. 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, E53 Place and E52 Time-Span 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 E92 Spacetime Volume is its projection on time.

Presence
type: Class
notation: E93
comment: This class comprises instances of E92 Spacetime Volume, whose temporal extent has been chosen in order to determine the spatial extent of a phenomenon over the chosen time-span. Respective phenomena may, for instance, be historical events or periods, but can also be the diachronic extent and existence of physical things. In other words, instances of this class fix a slice of another instance of E92 Spacetime Volume in time. The temporal extent of an instance of E93 Presence typically is predetermined by the researcher so as to focus the investigation particularly on finding the spatial extent of the phenomenon by testing for its characteristic features. There are at least two basic directions such investigations might take. The investigation may wish to determine where something was during some time or it may wish to reconstruct the total passage of a phenomenon’s spacetime volume through an examination of discrete presences. Observation and measurement of features indicating the presence or absence of a phenomenon in some space allows for the progressive approximation of spatial extents through argumentation typically based on inclusion, exclusion and various overlaps.

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 on any other stable constellations of matter, relevant to cultural and scientific documentation.An instance of E94 Space Primitive defines an instance of E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr Hiebel 2013), which means that the identity of the place is derived from its geometric definition. Such a declarative place may allow for the approximation of instances of E53 Place defined by the actual extent of some phenomenon, such as a settlement or a riverbed, or other forms of identification rather than by an instance of E94 Space Primitive. Note that using an instance of E94 Space Primitive for approximating the actual extent of some place always defines a (declarative) instance of E53 Place in its own right. Definitions of instances of E53 Place using different spatial reference systems are always definitions of different instances of E53 Place.Instances of E94 Space Primitive provide the ability to link CIDOC CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualization 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. It is considered good practice to maintain compatibility with OGC standards.

Spacetime Primitive
type: Class
notation: E95
comment: This class comprises instances of E59 Primitive Value for spacetime volumes that should be implemented with appropriate validation, precision and reference systems to express geometries being limited and varying over time on or relative to Earth, or any other stable constellations of matter, relevant to cultural and scientific documentation. An instance of E95 Spacetime Primitive may consist of one expression including temporal and spatial information such as in GML or a different form of expressing spacetime in an integrated way such as a formula containing all 4 dimensions.An instance of E95 Spacetime Primitive defines an instance of E92 Spacetime Volume in the sense of a declarative spacetime volume as defined in CRMgeo (Doerr Hiebel 2013), which means that the identity of the instance of E92 Spacetime Volume is derived from its geometric and temporal definition. This declarative spacetime volume allows for the application of all E92 Spacetime Volume properties to relate phenomenal spacetime volumes of periods and physical things to propositions about their spatial and temporal extents.Instances of E92 Spacetime Volume defined by P169 defines spacetime volume (spacetime volume is defined by) that use different spatiotemporal referring systems are always regarded as different instances of the E92 Spacetime Volume.It is possible for a spacetime volume to be defined by phenomena causal to it, such as an expanding and declining realm, a settlement structure or a battle, or other forms of identification rather than by an instance of E95 Spacetime Primitive. Any spatiotemporal approximation of such a phenomenon by an instance of E95 Spacetime Primitive constitutes an instance of E92 Spacetime Volume in its own right.E95 Spacetime Primitive is not further elaborated upon within this model. Compatibility with OGC standards is recommended.

Purchase
type: Class
notation: E96
comment: This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more different instances of E39 Actor, where the transferring party is completely compensated by the payment of a monetary amount. In more detail, a purchase agreement establishes a fixed monetary obligation at its initialization on the receiving party, to the giving party. An instance of E96 Purchase begins with the contract or equivalent agreement and ends with the fulfilment of all contractual obligations. In the case that the activity is abandoned before both parties have fulfilled these obligations, the activity is not regarded as an instance of E96 Purchase.This class is a very specific case of the much more complex social business practices of exchange of goods and the creation and satisfaction of related social obligations. Purchase activities which define individual sales prices per object can be modelled by instantiating E96 Purchase for each object individually and as part of an overall instance of E96 Purchase transaction.

Monetary Amount
type: Class
notation: E97
comment: This class comprises quantities of monetary possessions or obligations in terms of their nominal value with respect to a particular currency. These quantities may be abstract accounting units, the nominal value of a heap of coins or bank notes at the time of validity of the respective currency, the nominal value of a bill of exchange or other documents expressing monetary claims or obligations. It specifically excludes amounts expressed in terms of weights of valuable items, like gold and diamonds, and quantities of other non-currency items, like goats or stocks and bonds.

Currency
type: Class
notation: E98
comment: 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. The unit of a monetary system must describe a nominal value which is kept constant by its administrative authority and an associated banking system if it exists, and not by market value. For instance, one may pay with grams of gold, but the respective monetary amount would have been agreed as the gold price in US dollars on the day of the payment. Under this definition, British Pounds, U.S. Dollars, and European Euros are examples of currency, but “grams of gold” is not. One monetary system has one and only one currency. Instances of this class must not be confused with coin denominations, such as “Dime” or “Sestertius”. Non-monetary exchange of value in terms of quantities of a particular type of goods, such as cows, do not constitute a currency.

Product Type
type: Class
notation: E99
comment: This classes comprises types that stand as the models for instances of E22 Human-Made Object that are produced as the result of production activities using plans exact enough to result in one or more series of uniform, functionally and aesthetically identical and interchangeable items. The product type is the intended ideal form of the manufacture process. It is typical of instances of E22 that conform to an instance of E99 Product Type that its component parts are interchangeable with component parts of other instances of E22 made after the model of the same instance of E99. Frequently, the uniform production according to a given instance of E99 Product Type is achieved by creating individual tools, such as moulds or print plates that are themselves carriers of the design of the product type. Modern tools may use the flexibility of electronically controlled devices to achieve such uniformity. The product type itself, i.e., the potentially unlimited series of aesthetically equivalent items, may be the target of artistic design, rather than the individual object. In extreme cases, only one instance of a product type may have been produced, such as in a "print on demand" process which was only triggered once. However, this should not be confused with industrial prototypes, such as car prototypes, which are produced prior to the production line being set up, or test the production line itself.

Work
type: Class
notation: F1
comment: This class comprises distinct intellectual ideas conveyed in artistic and intellectual creations, such a poems, stories or musical compositions. A Work is the outcome of an intellectual process of one or more persons. Inherent to the notion of work is the existence of recognisable realizations of the work in the form of one or more expressions. Works are often regarded as finished and discrete e.g. when declared as such by the creator of the work or based on the elaboration or logical coherence of its content. However, works may be recognized as existing but unfinished e.g. if the creators deliberately or accidentally never explicitly finished a particular Expression but have left behind partial expressions. In the absence of explicit information about the initial conception, which is rarely available, the first expression created constitutes witness of the beginning of existence of a Work. A Work can evolve over time, such as through revised editions. A Work may be elaborated by one or more Actors simultaneously, in parallel, or over time. Additional expressions of a Work can continue to be created over time. The boundaries of a Work have nothing to do with the value of the intellectual achievement but only with the dominance of a concept. The main purpose of this class is to enable bringing together intellectually equivalent Expressions in order to display to a user all available alternatives of the same intellectual or artistic content.

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

Manifestation
type: Class
notation: F3
comment: This class comprises products rendering one or more Expressions. A Manifestation is defined by both the overall content and the form of its presentation. The substance of F3 Manifestation is not only signs, but also the manner in which they are presented to be consumed by users, including the kind of media adopted.An F3 Manifestation is the outcome of a publication process where one or more F2 Expressions are prepared for public dissemination, but it may also be a unique form created directly on some material carrier without the intent of being formally published.An instance of F3 Manifestation typically incorporates one or more instances of F2 Expression representing a distinct logical content and all additional input by a publisher such as text layout and cover design. Additionally an F3 Manifestation can be identified by the physical features for the medium of distribution, if applicable. For example, publications in the form of hard-cover and paperback editions would be two distinct instances of F3 Manifestation, even though authorial and editorial content are otherwise identical in both publications.In the case of industrial products such as printed books or music CDs, but also digital material, an instance of F3 Manifestation can be regarded as the prototype for all copies of it. In these cases, an instance of F3 Manifestation specifies all of the features or traits that instances of F5 Item display in order to be copies of a particular publication. In the case of industrial products, instances of F3 Manifestation are also instances of E99 Product Type, normally nowadays identified by characteristic identifiers such as ISBN numbers.

Item
type: Class
notation: F5
comment: This class comprises physical objects (printed books, scores, CDs, DVDs, CD-ROMS, etc.) that were produced by (P186i) an industrial process involving a given instance of F3 Manifestation. As a result, all the instances of F5 Item associated with a given instance of F3 Manifestation are expected to carry the content defined in that instance of F3 Manifestation, although some or even all of them may happen to carry a content that significantly differs from it, due to either an accident in the course of industrial production, or subsequent physical modification or degradation.An instance of F5 Item that consists of a physical object or set of objects with clear physical boundaries is also an instance of E22 Human-Made Object. An instance of F5 Item that is stored on a part of a larger physical support (such as an electronic file among others on a disc) can also be considered to be an instance of E25 Human-Made Feature.The notion of F5 Item is only relevant with regard to the production process, from a bibliographic point of view. The physical units managed by cultural heritage institutions in their holdings are a distinct notion: a unit of holdings certainly can be equal to an instance of F5 Item, but it also can be either “bigger” than one (e.g., when two instances of F5 Item are bound together (in the case of printed books)), or “smaller” than one (e.g., for incomplete holdings, such as when only one CD from a two-CD set is held). From an operational point of view, cultural heritage institutions typically do not manage instances of F5 Item, but physical holdings units, instances of E19 Physical Object, although for libraries in most cases this is not significant because each item corresponds with a single unit. When this is not the case, the linkage between items and the units relevant for collection management can be recorded through the P46 is composed of (forms part of) property between instances of F5 Item and instances of E19 Physical Object. If needed, an insta…

Nomen
type: Class
notation: F12
comment: This class comprises associations between an instance of any class, and signs or arrangements of signs that are used to refer to and identify that instance.Signs include alphanumeric characters, ideograms, notations such as chemical structure symbols, sound symbols, etc. The scripts or type sets for the symbols used to compose an instance of F12 Nomen have to be sufficiently specified. Spelling variants are regarded as different nomens, whereas the use of different fonts (visual representation variants) or different digital encodings do not change the identity.An arbitrary combination of signs or symbols cannot be regarded as an appellation or designation until it is associated with something in some context. In that sense, the F12 Nomen class can be understood as the reification of a relationship between an instance of E1 CRM Entity and an instance of E41 Appellation. Two instances of F12 Nomen can happen to be associated with equivalent strings and yet remain distinct, as long as they refer to distinct instances of E1 CRM Entity. Furthermore, two instances of F12 Nomen referring to the same instance of E1 CRM Entity may be associated with equivalent strings, and remain distinct as long as they are associated with distinct properties of the F12 Nomen class (for example, having the same spelling in different languages, or being defined in different controlled vocabularies).An instance of F12 Nomen associates a combination of signs with an instance of E1 CRM Entity on the basis of a cultural or linguistic convention: by associating a string with anything, the instance of F12 Nomen establishes a meaning that is not inherent in the instance of E62 String that is associated with it. Depending on context of use, nomens associated with equivalent strings can be associated with instances of different things in the real world even within the same language (polysemy and homonymy). Conversely, the same thing can be referred to through any number of nomens (synonymy). In the c…

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 the F1 Work, which contains the Serial Work and the Work realised in the monograph. This does not make the monograph part of the Serial Work.

Work Creation
type: Class
notation: F27
comment: This class comprises activities by which instances of F1 Work come into existence. An instance of F27 Work Creation can serve to document the period a work was coming into existence and the circumstances of it, when these are known.An instance of F27 Work Creation marks the initial creation of an instance of F1 Work through expressions or other externalisations that are sufficiently elaborated so that the characteristic conceptual identity of the work could be recognized as existing.In many cases this will coincide with the first known complete externalisation of an expression of the work. In other cases, the initial creation of an instance of F1 Work may be inferred from multiple, or later, expressions or other forms of evidence. For instance, commissioning of a work may explicitly be agreed on after the presentation of an already complete and detailed elaboration of the work that was not made public. Performances may be prior to written expressions, as in the case of Shakespeare’s works.The work, as an intellectual construction, may evolve from its initial creation onwards, until the last known expression of it.An instance of E39 Actor with which a work is associated through the chain of properties F1 Work. R16i was created by: F27 Work Creation. P14 carried out by (performed): E39 Actor corresponds to the notion of the “creator” of the work.In the situation where an expression of one instance of F1 Work serves as source material for the creation of the first expression of a new instance of F1 Work, the direct relationship between the works is indicated using the property R2 is derivative of (has derivative) between the two instances of F1 Work. The link to the specific source expression is indicated with the property P16 used specific object (was used for) using the path: F1 Work(1). R3 is realised in: F2 Expression(1). P16i was used for: F27 Work Creation. R16 created: F1 Work(2).

Expression Creation
type: Class
notation: F28
comment: This class comprises activities that result in instances of F2 Expression coming into existence. An instance of F2 Expression is considered to be created when it is captured on a carrier other than the creator’s brain.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 F3 Manifestation and an instance of F5 Item. F28 Expression Creation is a subclass of E12 Production because the recording of the expression causes a physical modification of the E18 Physical Thing that serves as the carrier. The creation of an instance of F2 Expression coincides with the creation of the first instance of F3 Manifestation that R4 embodies (is embodied in) this instance of F2 Expression.The P2 has type (is type of) property can be used to specify the type of the instance of F28 Expression Creation (i.e., activities such as translating, revising, or arranging music are types of creation process). The type of the process is distinct from the type of result even though the typology frequently used for instances of the resulting F2 Expressions may imply the category of the instance of the F28 Expression Creation.An instance of F28 Expression Creation may use as source material one or more specific instances of F2 Expression. When the source expression is documented this is also expressed by the property R76 is derivative of (has derivative).

Manifestation Creation
type: Class
notation: F30
comment: This class comprises the activities of selecting, arranging and presenting one or more instances of F2 Expression on a carrier or other persistent presentation means with the purpose of communicating it to some public. It includes the specification of the presentation as to sensory impression (such as visual appearance or audio rendition).

Performance
type: Class
notation: F31
comment: This class comprises activities where an instance of F1 Work is presented or communicated directly or indirectly to an audience, such as a theatrical play, a musical work or a choreographic work.Performances can be identified at various levels of granularity, but an instance of F31 Performance is always associated with a single identified instance of F1 Work. An instance of F31 Performance may consist of other instances of F31 Performance as parts, such as a piano concerto that has multiple movements. In addition, a complete run of equivalent performances of the same work can also be seen as an instance of F31 Performance, with the individual performances as parts.Activities that include performing multiple individual works, e.g., that are put together as a program for a show or concert, but where the activity as a whole is not associated with an instance of F1 Work, should be represented as instances of E7 Activity consisting of individual instances of F31 Performances as parts (the property P9 consists of (forms part of) expresses the relationship).Instances of F31 Performance may be created according to specific staging directions, be based on specific known instances of F2 Expression (such as translations), or be influenced by or include elements that relate to different works other than the single work the performance is dominated by. This can be documented using the properties P16 used specific object (was used for) or P15 was influenced by (influenced).

Item Production Event
type: Class
notation: F32
comment: This class comprises activities that result in one or more instances of F5 Item coming into existence. The production of a series of physical objects (printed books, scores, CDs, DVDs, CD-ROMs, etc.), producing a unique item (writing a manuscript on parchment, painting a watercolour, etc.), and the creation of a new copy of a file on an electronic carrier are all regarded as instances of F32 Item Production Event. For mass-produced items, the production process (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 the property R27 materialized: F3 Manifestation.

Reproduction Event
type: Class
notation: F33
comment: This class comprises activities that consist in producing items of a new instance of F3 Manifestation that preserve both the content and layout found on items of a pre-existing instance of F3 Manifestation. The individual instance or instances of F5 Item that was or were used as a source for this process may be precisely identified or not. Such activities result in products known as facsimiles, reproductions, reprints, reissues, or new releases.

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.

Argumentation
type: Class
notation: I1
comment: This class comprises the activity of making honest inferences or observations. An honest inference or observation is one in which the E39 Actor carrying out the I1 Argumentation justifies and believes that the I6 Belief Value associated with the resulting I2 Belief about the I4 Proposition Set is the correct value at the time that the activity was undertaken and that any I3 Inference Logic or methodology was correctly applied. One instance of E39 Actor may carry out an instance of I1 Argumentation, though the E39 Actor may, of course, be an instance of E74 Group.

Belief
type: Class
notation: I2
comment: This class comprises the notion that the associated I4 Proposition Set is held to have a particular I6 Belief Value by a particular E39 Actor. This can be understood as the period of time that an individual group holds a particular set of propositions to be true, false, or somewhere in between.

Inference Logic
type: Class
notation: I3
comment: This class comprises the rules used as inputs to I5 Inference Making. In this context, the term “logic” is used in the most general sense of the Greek term, and not in the mathematical sense only. Examples are the direct application of formal logic, mathematical theories and calculus, formal or informal default reasoning based on default values associated with categories, probabilistic reasoning-based mathematical models and assumed or observed frequencies for certain categories, application of theoretical social models and comparisons with “cultural parallels”, etc. An instance of Inference Logic could also be a reference to the exact software release of a Bayesian reasoner, a rule such as “later layers are on top of earlier layers”, or even a term like “social intuition”, if this is scholarly acceptable (after Doerr, Kritsotaki and Boutsika, 2011). Indeed, anything that is scientifically or academically acceptable as a method for drawing conclusions may be included, for instance, human pattern recognition. A particular instance of I3 Inference Logic would be the algorithm implemented in a particular revision of a software package. Instances of I3 Inference Logic not only comprise the method of reasoning, but also the set of categorical laws or axioms used in the argumentation. Often, both are inextricably interwoven, for instance in a software implementation.

Proposition Set
type: Class
notation: I4
comment: This class comprises the sets of formal, binary propositions that an I2 Belief is held about. It could be implemented as a named graph, a spreadsheet, or any other structured dataset. Regardless of the specific syntax employed, the effective propositions it contains should be made up of unambiguous identifiers, concepts of a formal ontology, and constructs of logic.

Inference Making
type: Class
notation: I5
comment: This class comprises the action of making honest propositions and statements about particular states of affairs in reality or possible realities, or categorical descriptions of reality by using inferences from other statements based on hypotheses and any form of formal or informal logic. It includes evaluations, calculations, and interpretations, based on mathematical formulations and propositions. It is characterized by the use of an existing I2 Belief as the premise that, taken together with a set of I3 Inference Logic, draws a further I2 Belief as a conclusion. Documenting instances of I5 Inference making primarily enables tracing the dependency of knowledge from conclusion to premise through subsequent inferences possibly back to primary evidence, so that the range of influence of knowledge revision at any intermediate stage of complex inference chains on current convictions can be narrowed down by query. The explicit reference to the applied inference logic further allows scholars and scientists to assess if they can or would follow the documented argument. The class is not intended to promote the use of computationally decidable systems of logic as replacements of scholarly justifications of arguments, even though it allows for documenting the use of decidable logic, if that was deemed adequate for the problem at hand. Principles of scholarly justifications of arguments are also regarded as kinds of inference logic.

Belief Value
type: Class
notation: I6
comment: This class comprises any encoding of the value of the truth of an I2 Belief. It may be expressed in terms of discrete logic, modal logic, probability, fuzziness, or any other adequaterepresentational system. A minimum requirement of flexibility is for three values: True; False; Unknown.

Belief Adoption
type: Class
notation: I7
comment: This class comprises the action of an E39 Actor adopting propositions taken from an interpretation of the intended meaning of an instance of E73 Information Object as being true, or in some way likely to be true. The adopted propositions constitute the conclusion of the action in the form of a new instance of I12 Adopted belief of the actor adopting it. The basis of I7 Belief Adoption is the justification of trust in the source of the adopted propositions, rather than the application of rules for inferring the respective propositions from logical remises. Typical examples are the citation of academic papers or the reuse of datasets. Where an instance of I7 Belief Adoption is based on personal communication (marked as pers.comm. in the studied text), this should be represented by using P2 has type: “Pers.Comm.”, directly from the instance of I7 Belief Adoption.

Provenance Statement
type: Class
notation: I10
comment: This class comprises statements about the provenance of instances of E70 Thing existing at the time of making the provenance statements. An instance of I10 Provenance Statement must contain propositions about the presence of the respective instances of E70 Thing in an event or spatiotemporal context of reference. Characteristically, it may pertain to the writing by a known author at a known or unknown date or place, or to the existence of the text known to some public, regardless of the truth of authorship. In case that only information objects exist describing the proper thing of interest, such as a photo, or photo of a photo, of a lost archaeological object, an instance of I10 ProvenanceStatement should contain the relevant chain of intermediate events transferring the information from the proper thing of interest up to the extant information objects taken into account, or refer to it. The property J20 is about the provenance of can be used to link the instance of I10 Provenance Statement as a whole, with the proper thing of interest. It constitutes a constraint to the provenance statement that it must contain the description of the relevant context of reference, and, if applicable, to the relevant chain of intermediate events transferring the information.

Adopted Belief
type: Class
notation: I12
comment: This class comprises the notion that an instance of E39 Actor adopted the meaning of an associated instance of I4 Proposition Set by arguments of trust from a source created by another instance of E39 Actor, and holds it as being true or in some way likely to be true. This source can be documented via the property J14 adopted interpretation of (has adopted interpretation). The used interpretation of the meaning of the source may be a belief of the adopting Actor or another one and can be documented as an instance of I13 Intended Meaning Belief, if this detail is relevant.

Intended Meaning Belief
type: Class
notation: I13
comment: This class comprises beliefs on the part of an instance of E39 Actor that a particular I4 Proposition Set formally represents (in part or in its entirety) the intended meaning that was created by another instance of E39 Actor, without considering an opinion yet about its truth or trustworthiness. The belief constitutes an interpretation of the source. The respective proposition set can be documented using the property J16 assumed meaning (is supposed meaning in), whereas the respective source can be documented via the property J17 about (has interpretation) and holds as being true or in some way likely to be true.

Provenance Belief
type: Class
notation: I14
comment: This class comprises beliefs of an Actor that a particular instance of E70 Thing, in general available to this Actor, is identical to one present in a relevant event or context of reference in the past, such as a text in a book being sufficiently identical to the one in the claimed author’s original manuscript or edition in order to be used by the Actor for citation. Other examples are the provenance of archaeological objects in collections, which may pertain to the claimed excavation spot or to the inferred context of their creation. The term “in general available” means that the thing is either physically in the hands of the actor or that the actor or an actor of their trust has the principled ability to get access to thething. In case that only information objects exist describing the proper thing of interest, such as a photo of a lost archaeological object, an instance of Ix5 Provenance Belief should be based on arguments including references to provenance beliefs about descriptions, representations and the described things. A formal description about the assumed provenance can be documented via the property Jxx8 that. Note that, depending on the intended argumentation about the respective instance of E70 Thing, different aspects of provenance may be described about the same instance of E70 Thing.

Provenance Assessment
type: Class
notation: I15
comment: This class comprises activities of making arguments and concluding about the likely provenance of instances of E70 Thing existing at the time of this assessment. These activities may further be about the provenance of things referred to or represented by existing information objects, and subsequent references.

Meaning Comprehension
type: Class
notation: I16
comment: This class comprises processes of interpreting the intended meaning of parts or the whole of the content of an instance of E73 Information Object as propositions. Such interpretations may include the disambiguation of the meaning of words and expressions, expanding abbreviations, resolving named entities, references and co-references, and complementing missing text parts, without however arguing about the actual truth of the information. In principle, any use of an information object pertaining to its meaning implies an instance of Ix1 Meaning Comprehension. However, in practical applications, texts in natural language are often clear enough so that no explicit explanation of the interpretation is needed for the user. In such cases, there is no need to create explicit instances of Ix1 Meaning Comprehension, but the adopted belief may directly be linked via Jxx2 adopted interpretation of (has adopted interpretation), or the instance of Ix1 Meaning Comprehension may be made implicit to an instance of I7 Belief Adoption by multiple instantiation. Explicit documentation of instances of Ix1 Meaning Comprehension are useful, if the interpretations are not obvious and if competing arguments about them exist.

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 through empirical evidence, experiments and 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 by human sensory impression, and often enhanced by tools and measurement devices. Observed situations or dimensions may pertain to properties confined to a single instance of S15 Observable Entity or pertain to constellations of multiple instances and relations between them, in particular distances between them. 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. 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. Measurements and witnessing of events are special cases of observations. Observations result in a belief that certain propositions held at a time within the time-span of the observation. In this model, the degree of confidence in the observed properties is regarded to be “true” by default, but could be described differently by adding a property P3 has note to an instance of S4 Observation

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. In order to be able to identify and recognize in practice one instance of S11 Amount of Matter, some sort of confinement is needed that serves as a constraint for the enclosed matter and the integrity of the content, such as a bottle. In contrast to instances of E18 Physical Thing, no stability of form is required. The content may be put into another bottle without losing its identity. Subclasses may define very different identity conditions for the integrity of the content, such as chemical composition, or the sequence of layers of a bore core. Whereas an instance of E18 Physical Thing may gradually change form and chemical composition while preserving its identity, such as living beings, an instance of S11 Amount of Matter may lose its identifying features by such processes. What matters for the identity of an instance of S1 Amount of Matter is the preservation of a relevant composition from the initial state of definition onwards.

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

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

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

Measurement
type: Class
notation: S21
comment: This class comprises actions measuring instances of S15 Observable Entity, 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 features with relative stability of form and structure within a declared spatial volume of interest. The spatial extent of an instance of S22 Segment of Matter may be declared or defined by a researcher or observer usually because the arrangement and composition of substance is characteristic for the surrounding matter or can be interpreted as traces of its genesis and subsequent internal and external processes it was exposed to. The defining spatial extent is typically declared on a continuous matter by means of geometric determination without observable boundaries on all sides or any side. It may however be extracted at some point in time along the declared boundaries. An instance of S22 Segment of Matter is regarded to be existing from the time on it completely solidified with a structure that is still preserved in a recognizable way at the time of its spatial definition. Its existence is regarded to end when its respective integrity is partially or completely corrupted. Uncorrupted subsections of an instance of S22 Segment of Matter may continue to exist as segments of matter in their own right beyond the existence of the containing instance, and may have solidified before it. Typical examples are segments of archaeological or geological layers. They are regarded as uncorrupted even if they have undergone conformal deformations, such as compressions or shifts, as long as the effects of these deformations do not destroy the relevant structures of interest. This means that the defining spatial volume may be only geometrically valid for an instant of time for which it was declared, and undergo before and after deformations. In some cases, it may be possible to calculate the initial volume at the time of solidification, for instance for petrified bones compressed in Jurassic layers.

Position Determination
type: Class
notation: S23
comment: This class comprises activities of determining positions in space and time. The determined position is intended to approximate a part or all of the extent of the presence (instance of E93 Presence) of an instance of E18 Physical Thing or E4 Period of interest, such as the outer walls of an excavated settlement, the position of a ship sailing or the start and end of athlete's run in a competition. Characteristically, a theodolite or GPS device may be positioned on some persistent feature. Determining the position of the device will yield an approximation of the position of the feature of interest. Alternatively, some material item may be observed moving through a determined position at a given time. This class does not inherit properties from class S21 Measurement. A position determination is an evaluation of a combination of measurement of multiple associated distances and/or angles (instances of E54 Dimension) from a particular spot to certain reference points of previously known position in the same reference space. A particular role is played by the Earth's magnetic field and rotational axis as reference for an angle or direction. Often, the observed constituting dimensions are not documented, or hidden in an electronic device software. The determined position is given as an E94 Space Primitive corresponding to a declarative place. Together with the measured time-span covering the time-critical observations it forms a spacetime volume, which should normally overlap with the spatiotemporal extent of the thing or phenomenon of interest.

Sample Splitting
type: Class
notation: S24
comment: This class comprises the activity of dividing an instance of S13 Sample into new instances of S13 Sample. This activity describes cases of sub-sampling where the resulting instance maintains the characteristic qualities of the original instance. Any observations of these qualities made on the new instance also apply to the original one. This class should be used to model cases of splitting a homogenous sample into multiple ones.

Written Text
type: Class
notation: TX1
comment: This class comprises visible or tactile marks (called glyphs or graphs), which relate in a systematic way to units of speech, intentionally traced (i.e., “written”) on some kind of physical support by using specific techniques and tools, with the purpose of conveying a message towards a given receiver or group of receivers.

Writing
type: Class
notation: TX2
comment: This class describes the activity of communicating information by means of permanent, visible marks in a non-mechanical way, using various techniques (painting, sculpture, etc.) and by means of specific tools, on a given support.

Writing System
type: Class
notation: TX3
comment: This class represents a conventional symbolic system designed to represent units of a natural language with the purpose of recording and transmitting information. A writing system consists of a set of symbols (graphemes, TX8), instantiated through physical signs of a visual or tactile nature (glyphs, TX9) representing linguistic units of any kind and the related syntactic (i.e., graphotactic) rules.It is used to produce a TX1 Written Text during a TX2 Writing event.

Writing Field
type: Class
notation: TX4
comment: This class describes the portion of the physical carrier arranged and usually reserved and delimited for the purpose of accommodating a written text, highlighting and isolating it from the other parts of the object to which it belongs, enhancing and guaranteeing its readability. This entity is paramount specially in epigraphy, in which a specific element called “epigraphic field” has been defined by the discipline itself. Its importance is also evident in papyrology and codicology, where a clear distinction between area(s) containing the written text and empty parts of the support (margins, intercolumnia, etc.) is significant for the definition of styles and periods of the document.

Text Recognition
type: Class
notation: TX5
comment: This class comprises activities of recognizing physical features on some surface, often an instance of TX4 Writing Field, as an arrangement of a series of identifiable glyphs of some known script, deciphered or not, in an order characteristic for a text.For study purposes, the text recognition procedure requires a scientific autoptic examination of the text. An autoptic examination consists of an accurate analysis of the surface and the signs, and prescribes the use of specific tools and procedures for establishing the exact value of each sign on the physical feature. Deterioration of the original medium or “sloppy” writing may render parts of the original text as undecipherable or ambiguous, which may be annotated in the transcript following epigraphic standards; a text recognition typically results in a record of an equivalent sequence of graphemes on another persistent medium in a scholarly established form of representation of the respective graphemes, often called a “transcript”.An instance of TX5 Text Recognition may in particular apply even to a single glyph, typically forming part of an instance of TX5 Text Recognition applying to a larger sequence of glyphs containing the former glyph.The recognition process may be assisted by mechanical means, imaging technology, or a traditional squeeze for incised glyphs. In case the recognition process is solely based on the latter, the observation concerns only the representations on the latter as present to the researcher in some physical form or projection and should unambiguously be documented as such.In case the recognized text has not been documented in a transcript, text recognition may constitute an implicit part of an overarching reading process, instance of TX14 Reading, which has resulted in other noteworthy propositions related to the content of the recognized text. On the other side, recognition of single glyphs or contracted parts of texts, as they are characteristic for the use of ligatured scripts, may q…

Transliteration
type: Class
notation: TX6
comment: This class comprises activities of exactly re-writing (i.e., re-encoding) an instance of TX12 Grapheme Sequence, i.e., the characters of a text, a contiguous part or a single character of it, by using a writing system (TX3) different from that of the original text, without changing the order of characters or words, by using standard correspondences.This operation may apply a 1:1 relation between the signs of the two writing systems, a “transliteration” in the narrower sense (e.g., the ALA-LC Romanization of Greek to Latin). It may also apply an approximation of the sounds of a language, as defined by the source writing system, by that of the target writing system, normally called a “transcription” (e.g., the “rōmaji” Romanization of Japanese), or a mixture of both (e.g. the ELOT 743 Type 2 – transcription of Greek to Latin letters). In a broader sense, the term “transcription” also applies to the activity of re-encoding a text using the same writing system (see example 1). The P16 used specific object (was used for) property can be used to specify the applied method of correspondence.

Written Text Segment
type: Class
notation: TX7
comment: This class describes portions of text considered to be of particular significance by scholars, as witnesses of a certain meaning or bearers of a particular phenomenon relevant to the investigation, study and understanding of a text. Examples of such text portions are columns, fragments, sections, paragraphs, as well as single words or signs, or other components of a written text. To each of these entities can be associated a single production event (TX2) or destruction event (E6), as in the case of letters or words damaged or worn by atmospheric agents or human interventions, as well as specific conditions (E3) for documenting its status during the text recognition process (TX5). The relationship between a written text (TX1) and its components is documented through the TXP4 has segment property.

Grapheme
type: Class
notation: TX8
comment: This class comprises symbols used as kinds of atomic units with distinctive value in a given writing system in order to represent linguistic units of some level to encode elements of a message. According to the typology of the writing system, the represented linguistic units can be phonemes (as in Latin), syllables (as in Mycenaean Linear B), up to complete words (as in Chinese and Sumerian scripts).A writing system also provides the conventions determining how the graphemes are to be used to write a language (orthographic rules).In some writing systems, graphemes may also be used as auxiliary signs, for instance, for disambiguating senses of homonyms, as in the Japanese writing system, or to mark the semantic categories of the words, as in the ancient Egyptian determinatives.

Glyph
type: Class
notation: TX9
comment: This class describes the physical, concrete features traced by a writer, representing the material manifestations of the graphemes needed to codify a linguistic expression. Glyphs are typically observed by the scholars during a text recognition activity (TX5) carried out to decode and recognise the graphemes (TX8) they represent.

Style
type: Class
notation: TX10
comment: This class describes stylistic variations of texts, including local script styles (as the Carolingian minuscule for the Latin script) and individual scribal hands. It includes: the general appearance of the script, in terms of general design, aspects related to a bilinear system (i.e., upper- and lowercase), measures (i.e., large, medium or small), shape and number of strokes forming a character, its order and direction. A style includes also information about ductus (the direction the text), ligatures and nexi (i.e., the connection between characters obtained by tracing them without detaching the writing instrument from the support and using one or more strokes in common), and the writing angle (i.e., the position the writing instrument is located with respect to the support). The style corresponds to fonts and their variations in the modern printing process.

Grapheme Sequence
type: Class
notation: TX12
comment: This class comprises particular sequences of Graphemes used for representing the abstract written form of a section of a given particular text.

Script
type: Class
notation: TX13
comment: This class comprises functionally complete sets of mutually different graphemes employed by one or more languages, regardless of the specific operating rules in a particular language. A writing system, on the other hand, also refers to the set of relations between symbols and linguistic units they represent. The same language may be written using different scripts.

Reading
type: Class
notation: TX14
comment: This class describes the complete intellectual activity, involving the interaction of visual-perceptual, linguistic, and conceptual systems, leading from text recognition (TX5) until its association with a complete linguistic meaning.

Institutional Fact
type: Class
notation: ZE1
comment: An instance of institutional fact is an ascription of a status function to an object by a community. The institutional fact is a concretization of a collective intentionality of the community in question towards a certain object over a certain period of time. An instance of institutional fact is recognizable to a competent speaker/member of a symbolic community (native or learner with sufficient competence). It may not be perceived through a single sense impression but through multiple experiences and implicit reasonings (e.g.: embedded participation, behavioural observation, linguistic evidence and interview), yet typically such intermediate observations and inferences are not necessarily recorded or accessible. The historical statement is typically the assertion of the institutional fact, that such and such a fact was the case, and was in force for a given community, at some time. The epistemic veridicality of the stated /reference instance of institutional fact is always open to contestation. The means of contestation involve analyzing the sources which support it. Instances of institutional fact come into existence based on conventions establishing the conditions under which they come into effect. Typically, an instance of institutional fact will come into existence either because of the performance of its stipulated, initiating speech act (e.g.: state of being married via marriage) or as a result of events fulfilling existing norm prescriptions in the community (e.g.: state of being uncle as result of birth of child of sister). An institutional fact comes to be through the agreed fiat of a community. It typically ceases to exist either because of a stipulated, nullifying speech act (e.g. divorce proceeding), because a community ceases to support the effective rule supporting its declaration (e.g.: ownership of people) or force majeure (e.g.: object ascribed function/status or community perceiving status is eliminated).

Appellative Status
type: Class
notation: ZE2
comment: An instance of appellative status is the collective ascription of an appellation to an object by a community. The substance of the appellative status is the communal commitment to the naming of the object in question with a designated appellation, under a designated modality. Instances of appellative status are recognizable through evidence of community members adopting the intentional stance of so-naming towards the object in question, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: ZE19 Naming] initiating this status. Examples of such evidence include, several individuals so naming a thing, a witness declaring that a thing is ‘so named, by us’ or through documents reporting this fact. Instances of appellative status may come to be through a formal process such as a declarative act of naming, or may have arisen through habit, fiat or be of unknown origin. Instances of appellative status may end either through a formal process, such as a new declarative act of naming, the formal stripping of a name, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Contact Point Status
type: Class
notation: ZE3
comment: An instance of contact status is the collective ascription of a contact point to an actor by a community. The substance of the contact status is the communal commitment to the addressing of messages to the actor in question according to a designated contact point appellation, using the implied message exchanging method. Instances of contact status are recognizable through evidence of community members adopting the intentional stance of so-addressing messages to the actor in question, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: E15 Identifier Assignment] initiating this status. Examples of such evidence include, several individuals so addressing messages to an actor via this contact point appellation, a witness declaring that an actor can so be reached, or through documents reporting this fact. Instances of contact status may come to be through a formal process such as a declarative act of identifier assignment, or may have arisen through habit, fiat or be of unknown origin. Instances of contact status may end either though a formal process, such as a new declarative act of identifier assignment, through formal assignment, or may simply fade out of use, be eliminated by fiat or for unknown reasons.

Classificatory Status
type: Class
notation: ZE4
comment: An instance of classificatory status is the collective ascription of a type to an object by a community. The substance of the classificatory status is the communal commitment to the classification of the object in question according to the designated type. Instances of classificatory status are recognizable through evidence of community members adopting the intentional stance of so-classifying the object in question, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: E17 Type Assignment] initiating this status. Instances of classificatory status may come to be through a formal process such as a declarative act of classification [E17 Type Assignment], or may have arisen through habit, fiat or be of unknown origin. Instances of classificatory status may end either though a formal process, such as a new declarative act of classification, be officially declassified, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Function Status
type: Class
notation: ZE5
comment: An instance of function status is the collective ascription of an operative functionality to an object by a community. The substance of the function status is the communal commitment to relating to and / or using the object in question according to a designated function. Instances of function status are recognizable through evidence of community members adopting the intentional stance of so using or relating to the object in question, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: E17 Type Assignment] initiating this status. Instances of function status may come to be through a formal process such as a declarative act of classification [E17 type Assignment], or may have arisen through habit, fiat or be of unknown origin. Instances of function status may end either though a formal process, such as a new declarative act of classification, or may simply fade out of use, be eliminated by fiat or by unknown reason.

Social Status
type: Class
notation: ZE6
comment: An instance of social status is the collective ascription of a social function to an actor by a community. The substance of the social status is the communal commitment to relating to and acting toward the actor in question according to the designated status. It is important to underline that an instance of social status relates to a classification of an individual as holding a particular role or function in the community in general. This is to be distinguished from a social relation status, a binary construct that binds two different actors in a certain relation. For example, an instance of social status could be the social status of "Coach". This social status, if ascribed to an individual, holds for that person within a general social context and for a particular group and/or population. This is distinct from a social relation status that is recognized particularly between the two individuals concerned, such as "coach of", that would particularly hold between the individual who is coach and the individual who is a team member. Instances of social status are recognizable through evidence of community members adopting the intentional stance of so relating or acting toward the actor in question, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: E17 Type Assignment] initiating this status. Instances of social status may be attributed to individuals or to groups of individuals. Instances of social status may also be held in relation to a third party, to whom the subject of the social status bears certain rights and/or responsibilities. Instances of social status may come to be through a formal process such as a declarative act of assignment [E17 Type Assignment], or may have arisen through habit, fiat or be of unknown origin. Instances of social status may end either though a formal process, such as a new declarative act of classification, or may simply fade out of use, be eliminated by fiat…

Custodial Status
type: Class
notation: ZE7
comment: An instance of custodial status is the collective ascription of a relationship of custodianship of some actor over an object by a community. The substance of the custodial status is the communal commitment to the recognition of the relationship of custodianship over the designated object by the actor in question. Instances of custodial status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: ZE21 Declarative Transfer of Custody] initiating this status. Instances of classificatory status may come to be through a formal process such as a declarative transfer of custody, or may have arisen through habit, fiat or be of unknown origin. Instances of custodial status may end either though a formal process, such as a new declarative act of legal transfer of custody, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Ownership Status
type: Class
notation: ZE8
comment: An instance of ownership status is the collective ascription of a relationship of legal possession of some actor over a legal object by a community. The substance of the ownership status is the communal commitment to the recognition of the relationship of possession over the designated legal object by the actor in question. Instances of ownership status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: ZE20 Declarative Acquisition] initiating this status. Instances of ownership status may come to be through a formal process such as a declarative act of taking ownership, or may have arisen through habit, fiat or be of unknown origin. Instances of ownership status may end either though a formal process, such as a new declarative act of acquisition, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Residential Status
type: Class
notation: ZE9
comment: An instance of residential status is the collective ascription to an actor of a formal place of residence by a community. The substance of the residential status is the communal commitment to the recognition and use of the designated place with regards to the residence of the designated actor. Instances of residential status are recognizable through evidence of community members adopting the intentional stance of so-recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of residence status may come to be through a formal process such as a declarative act of taking up residence, or may have arisen through habit, fiat or be of unknown origin. Instances of residence status may end either though a formal process, such as a new declarative act, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Family Status
type: Class
notation: ZE10
comment: An instance of family status is the collective ascription of a familial relationship between one person and another by a community. The substance of the family status is the communal recognition of the familial connection between the two actors in question. Instances of family status are recognizable through evidence of community members adopting the intentional stance and behaviour indicated as proper to this relation, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act (e.g.: adoption) initiating this status. Instances of family status may come to be simply through birth in a certain community or may require that a formal process such as a right of passage has been undertaken. Instances of family status may end either though a formal process such as a renunciation or through death.

Membership Status
type: Class
notation: ZE11
comment: An instance of membership status is the collective ascription of a membership relationship between an actor and some group by a community. The substance of the membership status is the communal recognition of the ascribed membership relation between the actor and the group in question. Instances of membership status are recognizable through evidence of community members adopting the intentional stance and behaviour indicated as proper to this relation, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: ZE22 Declarative Joining] initiating this status. Instances of membership status may come to be through a formal process such as a declarative act of declarative joining or may have arisen through habit, fiat or be of unknown origin. Instances of membership status may end either though a formal process [e.g.: ZE23 Declarative Leaving], or may simply fade out, be eliminated by fiat or for unknown reasons.

Referential Status
type: Class
notation: ZE12
comment: An instance of referential status is the collective ascription of a referential relationship between a propositional object and some entity by a community. The substance of the referential status is the communal recognition of the ascribed referential relation holding between the propositional object and the entity in question. Instances of referential status are recognizable through evidence of community members adopting the intentional stance and behaviour indicated as properly holding between the propositional object and the object it is taken to refer to in the manner it is meant to refer, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of referential status may come to be through a formal process such as a declarative act or may have arisen through habit, fiat or be of unknown origin. Instances of referential status may end either though a formal process, or may simply fade out, be eliminated by fiat or for unknown reasons.

Speech Act
type: Class
notation: ZE13
comment: An instance of speech act comprises an intentional activity engaged in by a set of actors to create a new institutional fact - or to nullify an existing one - that holds for a given community. In this sense, a speech act is transformative symbolic act. Speech acts are carried out by intentional actors through invoking a social rule and performing a prescribed set of actions often including the locution of set formulae of phrases by certain actors, fulfilling certain roles. Correct execution of the speech act as specified by the rule results in the existence of new institutional facts or their negation. The substance of speech act is ritual action performed by a group. An instance of speech act begins when the intended ritual proceeding as specified by the rule invoked is initiated. The instance of speech act ends when the required set of actions specified for the act in question are executed or it is abandoned.

Similarity Status
type: Class
notation: ZE14
comment: An instance of similarity status is the collective ascription of a similarity relationship between any two objects by a community. The substance of the similarity status is the communal recognition of the ascribed similarity relation between the two entities in question. Instances of similarity status are recognizable through evidence of community members adopting the intentional stance and behaviour indicated by the kind of similarity believed to hold between the two referenced entities, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of similarity status may come to be through a formal process such as a declarative act (e.g., scholarship) or may have arisen through habit, fiat or be of unknown origin. Instances of similarity status may end either though a formal process (e.g., disproof or refutation), or may simply fade out, be eliminated by fiat or for unknown reasons.

Set Status
type: Class
notation: ZE15
comment: An instance of set status is the collective ascription of some relationship of belonging between some entity and a notional set by a community. The substance of the set status is the communal recognition of the ascribed belonging between the subject entity and the set in question. Instances of set status are recognizable through evidence of community members adopting the intentional stance and behaviour indicated as proper to this set-belonging relation, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of set status may come to be through a formal process or may have arisen through habit, fiat or be of unknown origin. Instances of membership status may end either though a formal process, or may simply fade out, be eliminated by fiat or for unknown reasons.

Notional Set
type: Class
notation: ZE24
comment: Instances of this class comprise notional sets of objects which have been grouped together for one reason or another. The substance of notional set is ideational. A notional set comes to be when it is asserted or otherwise declared. It gains or loses members according to the particular rules guiding its maintenance. Typically instances of ZE24 Notional Set serve a functional purpose such as the grouping of some objects according to an ad hoc, context particular, or a context categorical criterion. See also Linked.Art:Set

Dating Status
type: Class
notation: ZE25
comment: An instance of dating status is the collective ascription of a relative dating to an event (such as the production or the use of an object or the despotional moment of an archaeological context) by its association to an established and named historical or archaeological period or event. The substance of the dating status is the communal recognition of the ascribed chronology as holding true for the dated event and potential, relative object(s) it involves. Instances of dating status are typically recorded in the archaeological / archival record. Instances of dating status are most typically initiated by a formal process such as a scholarly dating attribution (ZE26 Dating Declaration). Instances of dating status may be terminated either through a formal process (official disproof) or be replaced by another dating declaration holding an updated belief and supported by further evidence.

Declaration of Obligation
type: Class
notation: ZE27
comment: Instances of declaration of obligation are characterized by formal acts of recognition of a state of obligation between one party and another party for a certain measurable amount of goods. Instances of this class comprise official acts undertaken following formal procedures within a social grouping leading to formal recognition of an obligation status between two actors. The substance of declaration of obligation is an intentional, social act. Instances of ZE27 Declaration of Obligation come about when the specific social procedure required is intentionally and successfully enacted according to the prevalent rules. They end with the successful termination of the act or because of its premature termination. A successful act of ZE27 Declaration of Obligation leads to the generation of an instance of ZE28 Obligation Status, the institutional fact that thereafter holds between two actors until it has been abrogated.

Obligation Status
type: Class
notation: ZE28
comment: An instance of obligation status demarks a socially recognized state of obligation holding between two parties, wherein the first party is recognized to have the requirement to fulfil a debt to the second party for a certain measurable amount. The substance of the obligation status is the commitment from one party to another for compensation in a socially recognized form. Instances of obligation status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: ZE27 Declaration of Obligation) initiating this status. Instances of obligation status may come to be through a formal process such as an act of declaring obligation [ZE27 Declaration of Obligation), or may have arisen through habit, fiat or be of unknown origin. Instances of obligation may end either though a formal process, such as an act of renunciation, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Transfer of Property Right
type: Class
notation: ZE29
comment: Instances of declaration of transfer of property right consist of events in which an official transfer of a property right is undertaken between two individuals with the result that a new right is assigned to the receiver and the right of the giver may be forfeited. Instances of this class consist of events in which an official transfer of a property right is undertaken between two individuals with the result that a new right is assigned to the receiver and the right of the giver may be forfeited. The substance of transfer of property right is an intentional, social act. Instances of ZE29 Transfer of Property Right come about when the specific social procedure required is intentionally and successfully enacted according to the prevalent rules. They end with the successful termination of the act or because of its premature termination. A successful act of ZE29 Transfer of Property Right leads to the generation of an instance of ZE30 Property Right Status, the institutional fact that thereafter mediates the social relation to this object until it has been abrogated.

Property Right Status
type: Class
notation: ZE30
comment: Instances of property right status indicate the holding of a right over a legal object by some actor for some time. An instance of property right status is the collective ascription of a relationship of legal right of some actor over a legal object by a community. The substance of the property right status is the communal commitment to the recognition of the right of use, right to earn income from, and right of disposal (of some sort) over the designated legal object by the actor in question. Instances of property right status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: ZE29 Transfer of Property Right) initiating this status. Instances of property right status may come to be through a formal process such as a declarative act of taking possession of right [ZE29 Transfer of Property Right), or may have arisen through habit, fiat or be of unknown origin. Instances of property right status may end either though a formal process, such as a new transfer or right, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Locative Status
type: Class
notation: ZE35
comment: An instance of locative status is the collective ascription to an entity of a formal association to a geographic place. The substance of the locative status is the communal attribution of a defined association type between the designated entity and place. As opposed to connections created between entities and places through their passage through space and time, e.g.: the place of birth being a property of the birth event of an individual, locative statuses are created de jure rather than de facto and create a socially recognized connection between an entity and a location regardless the real or known spatiotemporal history of that object. For example, documentation may point to ambiguous evidence linking an object and a place such as the 'origin' of a person or the 'provenance' location of a physical object. In these cases, when we do not know the actual physical history of the object in question, but we do have a de jure attribution from which some knowledge may be derived, we can document and follow an instance of Locative Status for an object in relation to a geographic location. Instances of locative status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of locative status may come to be through a formal process such as a declarative act of such definition, or may have arisen through habit, fiat or be of unknown origin. Instances of locative status may end either though a formal process, such as a new declarative act, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Persons
type: Class
notation: ZE36
comment: Instances of this class comprise sentient beings endowed, to more or less extent, with intentionality, either as individuals or collectives. Instances of Persons are first causes and ends in themselves in a philosophical sense. The substance of Persons is personhood in this sense of being endowed with intentionality and the requisite respect qua sentient being.

Population
type: Class
notation: ZE37
comment: This class comprises a defined set of persons who are considered to together form a coherent, identifiable unit according to certain characteristics such as citizenry, religious affiliation or other uniting characteristics or properties. Instances of population may be emically or etically defined. The substance of population is a collectivity of people[.] Instances of population existence natural population come into and go out of existence through natural and social processes the particular details of which are often difficult to know or the subject of research and investigation. If a population is declaratively defined such as 'male voters between the age of 20 and 30 in Alabama in 2024 election cycle', then the existence condition is relative to the de jure declaration of their composition. An instance of population can be identified to be in existence when a suitable collective of individuals matching to its description can be identified to live and conform to those characteristics

Population Existence
type: Class
notation: ZE38
comment: This class comprises the proper existence event of a population. Population existence consists in the temporal continuance of a specified population over a time and space. Instances of population existence come into existence with the appearance or expression of the population and cease to exist with its dissolution. In the case of a de jure population, the duration of the population existence is a matter of declaration.

Physical Locative Status
type: Class
notation: ZE43
comment: An instance of physical locative status is the collective ascription to a physical object of a formal association to a geographic place. The substance of the locative status is the communal attribution of a defined association type between the designated object and place. As opposed to connections created between physical objects and places through their passage through space and time, e.g.: the place of production being a property of the production event of an individual, physical locative statuses are created de jure rather than de facto and create a socially recognized connection between an object and a location regardless the real or known spatiotemporal history of that object. For example, documentation may point to ambiguous evidence linking an object and a place such as the 'provenance' location of a physical object. In these cases, when we do not know the actual physical history of the object in question, but we do have a de jure attribution from which some knowledge may be derived, we can document and follow an instance of Physical Locative Status for an object in relation to a geographic location. Instances of physical locative status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of locative status may come to be through a formal process such as a declarative act of such definition, or may have arisen through habit, fiat or be of unknown origin. Instances of locative status may end either though a formal process, such as a new declarative act, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Topographical Status
type: Class
notation: ZE44
comment: An instance of topographical status is the collective ascription to a geographical place of a formal spatial association to another geographic place. The substance of the topographical status is the communal attribution of a defined spatial association between two geographic places. As opposed to connections created between geographic places as determine through a pure mathematic relation, e.g.: the falling within of a larger geometry by a smaller geometry, topographical statuses depend also on a de jure, socially recognized connection between two topographies. For example, when there are distinct political positions on the boundaries of a country, whether a geographic area 'falls within' another geographic area depends not only on the geometric calculation, but on the definition of extents of the geographic spaces in the first place. IInstances of topographical status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of topographical status may come to be through a formal process such as a declarative act of such definition, or may have arisen through habit, fiat or be of unknown origin. Instances of locative status may end either though a formal process, such as a new declarative act, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Promissory Status
type: Class
notation: ZE45
comment: An instance of promissory status is the collective ascription of a promissory obligation between two parties. The substance of the promissory status is the communal recognition of the promise in question, which may nonetheless only bind two individuals directly. The substance of promissory status includes the ascription of an outcome which may detail guidelines and constraints that downstream activities on the part of promissory parties should comply with. Put otherwise, the promise promises a futural event on the part of the promisor to the promisee. The specified promissory constraints of this event can be instantiated on the level of kinds of processes, items or qualities and quantities involved in the action. Instances of promissory status are recognizable through evidence of community members adopting an intentional stance towards the promise that exists between the two parties, as observable from direct witnesses, through the reports of competent observers or through documentary evidence of a declarative act (e.g.: ZE46 Promissory Agreement Event) initiating this status. Instances of promissory status may come to be through a formal process such as a declarative promisory agreement, or may have arisen through habit, fiat or be of unknown origin. Instances of promissory status may end either through a formal process, such as a new declarative promissory agreement, the formal stripping of an existing promissory status, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Promissory Agreement Event
type: Class
notation: ZE46
comment: Instances of promissory agreement event are characterized by formal acts of recognition of a promise between one party and another party for a certain outcome. Instances of this class comprise explicit acts undertaken following given procedures within a social grouping leading to explicit recognition of a promissory status between two actors. The substance of promissory agreement is an intentional, social act. Instances of ZE46 Promissory Agreement come about when the specific social procedure required is intentionally and successfully enacted according to the prevalent rules. They end with the successful termination of the act or because of its premature termination. A successful act of ZE46 Promissory Agreement leads to the generation of an instance of ZE45 Promissory Status, the institutional fact that thereafter holds between two actors until it has been abrogated.

Text Sequence Status
type: Class
notation: ZE49
comment: An instance of text sequence status is a collective ascription to a written text sequence of a formal association to another written text sequence, in relation to which it is conceived as occupying a determinate place (i.e., the order in which they are to be read, wherein one text sequence follows another). The substance of the text sequence status is the communal attribution of a recognizable sequencing order between the designated text fields As opposed to the connections created between a text field and the physical substrate upon which it is written, text sequence statuses are created de jure rather than de facto and create socially recognized connections between them. For example, an editorial annotation may indicate that a paragraph from a 'lower' position on the writing surface (such as a page) is to be inserted between two paragraphs at a 'higher' position (or on another page altogether). In such cases, the sequence in which the paragraphs are to be read does not coincide with the physical position of the text field in question, or the exact ordering of the paragraphs may be the subject of research or scholarly debate, but we do have de jure attribution from which some knowledge may be derived and documented with an instance of Text Sequence Status. Instances of text sequence status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of text sequence status may come to be through a formal process such as a declarative act of such definition, or may have arisen through habit, fiat or be of unknown origin. Instances of text sequence status may end either though a formal process, such as a new declarative act, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

Authority Status
type: Class
notation: ZE50
comment: An instance of authority status is the collective ascription of an authority function to an actor by a community, although not necessary by their will. The substance of the authority status is the communal commitment to relating to and acting toward the actor in question according to the designated authority. Instances of authority status may be attributed to individuals or to groups of individuals. Instances of authority status are recognizable through evidence of community members adopting the intentional stance of so relating or acting toward the actor in question, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act [e.g.: E17 Type Assignment] initiating this status. Instances of social status may come to be through a formal process such as a declarative act of assignment [E17 Type Assignment], or may have arisen through habit, fiat or be of unknown origin. Instances of social status may end either though a formal process, such as a new declarative act of classification, or simply fade out of existence.

Transformative Symbolic Act
type: Class
notation: ZE52
comment: This class comprises actions of a symbolic nature that are intentionally carried out by instances of E39 Actor and are transformative in consequence on a cultural and/or social level, initiating new instances of institutional fact or terminating the existence of previous institutional facts within that society / culture. An instance of transformative symbolic act is carried out within a social-cultural framework and makes use of the codes and symbols of that framework to communicate a message symbolically. As with any symbolic act, it may affirm or challenge one or more institutional facts recognized within such a system, but the specific difference of a transformative symbolic act is to be the cause of both new institutional facts and of the demise of existing institutional facts. Instances of transformative symbolic act begin when an E39 Actor intentionally engages in an action invoking an existing code or symbol with the intent to affirm or challenge an institutional fact and end when the invoking act / practice has been completed (or was interrupted). The end of a transformative symbolic act is necessarily accompanied by the change in composition of the overall set of institutional facts of the social cultural framework in which it was undertaken, with one or more instances thereof either coming into or going out of existence.

Symbolic Act
type: Class
notation: ZE53
comment: This class comprises actions of a symbolic nature that are intentionally carried out by instances of E39 Actor. In engaging in a symbolic act, an E39 Actor communicates to other actors. The specific content of a symbolic act's communicative outcome currently lies beyond the scope of this class. Instances of this class can be used to document events of affirmative or negatory relation towards an extant social fact as communicated by an actor. An instance of symbolic act is carried out within a social-cultural framework and makes use of the codes and symbols of that framework to communicate a message symbolically and typically affirms or challenges one or more institutional facts recognized therein. Instances of symbolic act begin when an E39 Actor intentionally engages in an action invoking an existing code or symbol with the intent to affirm or challenge an institutional fact and end when the invoking act / practice has been completed (or was interrupted).

Social Relation Status
type: Class
notation: ZE55
comment: An instance of social relation status is the collective ascription of a social relationship between one person and another by a community. The substance of the social relation status is the communal recognition of the binary social connection between the two actors in question. It is important to underline that an instance of social relation consists of is a binary construct that binds two different actors in a certain relation and is to be distinguished from social status. For example, an instance of social relation status could be the social relation status of "professor of" between a teacher and their student. This is a social relation status that is recognized particularly between the two individuals concerned, to be distinguished from a social status, recognized, for example, by the title 'Dr', which may or may not be held at the time in question and has no particular bearing on a relationship with any one individual. Instances of social relation status are recognizable through evidence of community members adopting the intentional stance and behaviour indicated as proper to this relation, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of social relation status may come to be simply through birth in a certain community or may require that a formal process such as a right of passage has been undertaken. Instances of social relation status may end either though a formal process such as a renunciation, or may simply fade out of use, be eliminated by fiat or be of unknown reason. or through death.

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

Evental Locative Status
type: Class
notation: ZE60
comment: An instance of evental locative status is the collective ascription to an event of a formal association to a geographic place. The substance of the locative status is the communal attribution of a defined association type between the designated event and place. As opposed to connections created between events and places through their passage through space and time, e.g.: the place of production being a property of the production event, evental locative statuses are created de jure rather than de facto and create a socially recognized connection between an event and a location regardless the real spatiotemporal history of that event, known or unknown. Instances of evental locative status are recognizable through evidence of community members adopting the intentional stance of so recognizing this status, as observable from direct witnesses, through the reports of competent observers or through evidence of a declarative act initiating this status. Instances of evental locative status may come to be through a formal process such as a declarative act of such definition, or may have arisen through habit, fiat or be of unknown origin. Instances of evental locative status may end either though a formal process, such as a new declarative act, or may simply fade out of use, be eliminated by fiat or be of unknown reason.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

stipulates prices
type: ObjectProperty
range: Dimension
comment: This property describes the expected, real-world price that the projected event is expected to cost.
notation: CP26
domain: Event Trigger Template

stipulates language
type: ObjectProperty
range: Language
comment: This property indicates the language in which the event is expected to take place .
notation: CP27
domain: Event Trigger Template

stipulates character
type: ObjectProperty
range: Type
comment: This property describes the expected character that would be performed in the projected event.
notation: CP28
domain: Event Trigger Template

stipulates audience
type: ObjectProperty
range: Type
comment: This property describes the expected type of audience for the projected event.
notation: CP29
domain: Event Trigger Template

had audience type
type: ObjectProperty
range: Type
comment: This property associates an instance of activity with the kind of audience it was performed for.
notation: CP30
domain: Activity

was intended pattern for
type: ObjectProperty
range: Activity
comment: This property links an instance of Event Trigger Template to an activity for which it was the intended pattern.
notation: CP31
domain: Event Trigger Template

used as premise
type: ObjectProperty
range: Belief
comment: This property associates an instance of I2 Belief with the instance of I5 Inference Making that used it as a premise.
notation: J1
domain: Inference Making

concluded that
type: ObjectProperty
range: Belief
comment: This property associates an instance of I2 Belief with the instance of I1 Argumentation that concluded it.
notation: J2
domain: Argumentation

applied
type: ObjectProperty
range: Inference Logic
comment: This property associates an instance of I3 Inference Logic with the instance of I5 Inference Making that used it to draw its conclusion.
notation: J3
domain: Inference Making

that
type: ObjectProperty
range: Proposition Set
comment: This property associates an instance of I4 Proposition Set with the instance of I2 Belief that holds an opinion about it.
notation: J4
domain: Belief

holds to be
type: ObjectProperty
range: Belief Value
comment: This property associates an instance of I2 Belief with the I6 Belief Value that reflects the opinion of the instance of I2 Belief about the I4 Proposition Set associated with it.
notation: J5
domain: Belief

is based on evidence from
type: ObjectProperty
range: Information Object
comment: This property associates an instance of I7 Belief Adoption with the instance of E73 Information Object hat a source of or evidence for the I4 Proposition Set that was adopted.
notation: J7
domain: Belief Adoption

adopted interpretation
type: ObjectProperty
range: Adopted Belief
comment: This property associates an instance of I7 Belief Adoption with the instance of I12 Adopted Belief that was established and possibly selected from the interpretation of the source or sources referred to by the property J14 adopted interpretation of. This property implies a relation of trust in the reliability of the sources. The actual believed content, i.e., propositions about some past reality that have been adopted from the source, should be documented using the property J4 that.
notation: J13
domain: Belief Adoption

adopted interpretation of
type: ObjectProperty
range: Information Object
comment: This property associates an instance of I12 Adopted Belief with a source or sources of interpretation from which the belief was established and possibly selected. In some cases of scholarly arguments, multiple source referring to a common topic may have been interpreted in order to form a particular belief about the topic referred to.
notation: J14
domain: Adopted Belief

assumed meaning
type: ObjectProperty
range: Intended Meaning Belief
comment: This property associates an instance of I7 Belief Adoption with an instance of I13 Intended meaning Belief about a meaning believed to be expressed in the source or sources referred to by the property J14 adopted interpretation of.
notation: J15
domain: Belief Adoption

assumed meaning
type: ObjectProperty
range: Proposition Set
comment: This property associates an instance of I13 Intended Meaning Belief with the instance of I4 Proposition Set that represents the meaning assumed by the holder of the belief to have been intended by the respective source. The latter source can be documented with the property J17 about (has interpretation).
notation: J16
domain: Intended Meaning Belief

about
type: ObjectProperty
range: Information Object
comment: This property associates an instance of I13 Intended Meaning Belief with the instance of E73 Information Object that was a source of or evidence for the interpretation of its intended meaning. If sources are fragmentary about or complementary to a specific topic, more than one source may have been used.
notation: J17
domain: Intended Meaning Belief

assumed provenance
type: ObjectProperty
range: Provenance Belief
comment: This property associates an instance of I7 Belief Adoption with an instance of I14 Provenance Belief about the source or sources referred to by the property J14 adopted interpretation of, which justifies the conviction that the trusted and adopted content of the source, or its copy at hand, is actually identical, or sufficiently close to the assumed original and its context of creation.
notation: J18
domain: Belief Adoption

that
type: ObjectProperty
range: Provenance Statement
comment: This property associates an instance of I14 Provenance Belief with the instance of I10 Provenance Statement that holds an opinion about it.
notation: J19
domain: Provenance Belief

is about the provenance of
type: ObjectProperty
range: Thing
comment: This property associates an instance of I10 Provenance Statement with an instance of E70 Thing, the provenance of which the statement describes.
notation: J20
domain: Provenance Statement

concluded provenance
type: ObjectProperty
range: Provenance Belief
comment: This property describes the naming or identification of any real-world item by a name or any other identifier. This property associates an instance of I15 Provenance Assessment with an instance of I14 Provenance Belief that constitutes the conclusion of the assessment. An instance of I15 Provenance Assessment may conclude more than one instances of I14 Provenance Belief, typically about different objects considered in the same assessment.
notation: J21
domain: Provenance Assessment

interpreted meaning of
type: ObjectProperty
range: Thing
comment: This property associates an instance of I16 Meaning Comprehension with the instance of E73 Information Object that was the source of or evidence for the interpretation of its intended meaning. If sources are fragmentary about or complementary to a specific topic, more than one source may have been used.
notation: J22
domain: Meaning Comprehension

interpreted meaning as
type: ObjectProperty
range: Intended Meaning Belief
comment: This property associates an instance of I16 Meaning Comprehension with the instance of I13 Intended Meaning Belief that was the result of the interpretation of the intended meaning of the analysed source(s).
notation: J23
domain: Meaning Comprehension

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

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

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

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

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

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

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. Although an instance of S1 Matter Removal activity normally concerns only one item of S10 Material Substantial, it is possible to imagine circumstances under which more than one item might be diminished by a single Matter Removal activity. An instance S1 Matter Removal activity requires to diminish at least one item of S10 Material Substantial. This may be realized by any of the subproperties of O1 diminished. Therefore the instantiation of a particular subproperty of O1 diminished is not necessary.
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. In particular, it 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 ("spot") at which this activity sampled. It identifies the narrowest relevant area on the material substantial from which the sample was taken. This may be known or given in absolute terms or relative to an instance of the material substantial from which it was taken. If samples are taken from more than one spot, the sample taking activity must be documented by separate instances for each spot. The property P7 took place at, inherited from E4 Period, describes the position of the area in which the sampling activity occurred; this latter comprises the space within which operators and instruments were contained during the activity, and the sample taking spot.
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 taken during the activity.
notation: O5
domain: Sample Taking

is 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 formed or 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

confines
type: ObjectProperty
range: Material Substantial
comment: This property associates an instance of S20 Rigid Physical Feature with an instance of S10 Material Substantial that it partially or completely confines. It describes cases in which rigid features such as stratigraphic layers, walls, dams, riverbeds, etc. form the boundaries of some item such as another stratigraphic layer or the waters of a river.
notation: O7
domain: Rigid Physical Feature

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 in 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. In case the instance of S15 Observable Entity is more specifically an instance of E18 Physical Thing, using the property O12 has dimension (is dimension of) is equivalent to using the property P43 has dimension (is dimension of). In other words, using the one implies the other.
notation: O12
domain: Observable Entity

triggered
type: ObjectProperty
range: Event
comment: This property associates an instance of E5 Event that triggered another instance of E5 Event with the latter. It identifies the interaction between events: an event can activate (trigger) other events in a target system that is in a situation of sustained tension, such as a trap or an unstable mountain slope giving way to a land slide after a rain or earthquake. In that sense the triggering event is interpreted as a cause. However, the association of the two events is based on their temporal proximity, with the triggering event ending when the triggered event starts.
notation: O13
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”. This property is equivalent to P156 occupies (is occupied by) with domain E18 Physical Thing and range 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

encountered object
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of S19 Encounter Event with an instance of E18 Physical Thing that was encountered or observed as present during the event.
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

encountered at
type: ObjectProperty
range: Place
comment: This property associates an instance of S19 Encounter Event with an instance of E53 Place at which the things, which were encountered, were observed to be present. This may be given in absolute terms or in terms relative to the observed thing. The associated place must be within the boundaries of the E53 Place at which the S19 Encounter Event took place, if that has been given. Note, that the encountered object may be larger and extend beyond the place of encounter, such as a corner of a building being excavated.
notation: O21
domain: Encounter Event

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

contains
type: ObjectProperty
range: Material Substantial
comment: This property describes that an instance of S10 Material Substantial was or is contained in another instance of S10 Material Substantial regardless of whether the identity of the involved instances is based on the persistence of the form of material or on material substance that may change form.
notation: O25
domain: Material Substantial

split
type: ObjectProperty
range: Sample
comment: This property associates an instance of S24 Sample Splitting with the instance of S13 Sample which is the original sample being split.
notation: O27
domain: Sample Splitting

is conceptually greater than
type: ObjectProperty
range: Type
comment: This property allows an instance of E55 Type from a particular concept scheme or vocabulary to be declared as having an order relative to other instances of E55 Type in the same or other concept schemes, without necessarily having a specific value associated with either instance. This allows, for example, for an E55 Type instance representing the concept of "good" in a conservation report vocabulary to be greater than the E55 Type instance representing the concept of "average" in the same vocabulary. This property is transitive, and thus if "average" is greater than "poor", then "good" is also greater than "poor". In the domain of statistics, types that participate in this kind of relationship are called "Ordinal Variables"; as opposed to those without order which are called "Nominal Variables". This property allows for queries that select based on the relative position of participating E55 Types.
notation: O28
domain: Type

removed sub-sample
type: ObjectProperty
range: Sample
comment: This property associates an instance of S24 Sample Splitting with the resulting instance of S13 Sample that has been removed from the original sample. The new sample (i.e. the sub-sample) maintains the characteristic qualities of the original.
notation: O29
domain: Sample Splitting

determined position
type: ObjectProperty
range: Space Primitive
comment: This property associates an instance of S23 Position Determination with the instance of E94 Space Primitive which is the result of that determination. The instance of E94 Space Primitive approximates the place occupied by the entity whose position is being determined.
notation: O30
domain: Position Determination

has validity time-span
type: ObjectProperty
range: Time-Span
comment: This property associates an instance of S23 Position Determination with the instance of E52 Time-Span for which the determination is valid according to the observer at the time of the observation. No inferences can be made in relation to the validity of the determination outside this time-span despite the fact that some entities are relatively stable and their positions may remain the same after the determination. The time-span of validity should fall within the overall time-span of the process of determination.
notation: O31
domain: Position Determination

determined position of
type: ObjectProperty
range: Observable Entity
comment: This property connects an instance of S23 Position Determination with the instance of S15 Observable Entity whose position is being determined.
notation: O32
domain: Position Determination

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.This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned to E42 Identifier. It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form to E41 Appellation.
notation: P1
domain: CRM Entity

has type
type: ObjectProperty
range: Type
comment: This property allows sub typing of CIDOC CRM entities –a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CIDOC CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CIDOC CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E41 Appellation, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CIDOC CRM hierarchy. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.This property is a shortcut for the path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned to E55 Type.
notation: P2
domain: CRM Entity

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 CIDOC CRM constructs. In particular, it captures the characterisation of the item itself, its internal structures, appearance etc.Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CIDOC CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CIDOC CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g., “construction”, “decoration” etc. An item may have many notes, but a note is attached to a specific item.
notation: P3
domain: CRM Entity

has time-span
type: ObjectProperty
range: Time-Span
comment: This property associates an instance of E2 Temporal Entity with the instance of E52 Time-Span during which it was on-going. The associated instance of E52 Time-Span is understood as the real time-span during which the phenomena making up the temporal entity instance were active. More than one instance of E2 Temporal Entity may share a common instance of E52 Time-Span only if they come into being and end being due to identical declarations or events.
notation: P4
domain: Temporal Entity

consists of
type: ObjectProperty
range: Condition State
comment: This property describes the decomposition of an instance of E3 Condition State into discrete, subsidiary states. It is assumed that the sub-states into which the condition state is analysed form a logical whole - although the entire story may not be completely known – and that the sub-states are in fact constitutive of the general condition state. For example, a general condition state of “in ruins” may be decomposed into the individual stages of decay. This property is transitive and asymmetric.
notation: P5
domain: Condition State

took place at
type: ObjectProperty
range: Place
comment: This property describes the spatial location of an instance of E4 Period. The related instance of E53 Place should be seen as a wider approximation of the geometric area within which the phenomena that characterise the period in question occurred, see below. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (frequently on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France in 1789”; the “Victorian” period may be said to have taken place in “Britain from 1837-1901” and its colonies, as well as other parts of Europe and North America. An instance of E4 Period can take place at multiple non-contiguous, non-overlapping locations.This property is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place. E4 Period is a subclass of E92 Spacetime Volume. By the definition of P161 has spatial projection an instance of E4 Period takes place on all its spatial projections, that is, instances of E53 Place. Something happening at a given place can also be considered to happen at a larger place containing the first. For example, the assault on the Bastille 14th July 1789 took place in the area covered by Paris in 1789 but also in the area covered by France in 1789.
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 instance of E19 Physical Object. This property is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156i is occupied by E18 Physical Thing.It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. For example, the French and German armistice of 22nd June 1940 was signed in the same railway carriage as the armistice of 11th 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.This property is transitive and asymmetric.
notation: P9
domain: Period

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.This property is transitive and reflexive.
notation: P10
domain: Spacetime Volume

had participant
type: ObjectProperty
range: Actor
comment: This property describes the active or passive participation of instances of E39 Actors in an instance of E5 Event. It documents known events in which an instance of E39 Actor has participated during the course of that actor’s life or history. The instances of E53 Place and E52 Time-Span where and when these events happened provide us with constraints about the presence of the related instances of E39 Actor in the past. Collective actors, i.e., instances of E74 Group, may physically participate in events via their representing instances of E21 Persons only. The participation of multiple actors in an event is most likely an indication of their acquaintance and interaction.The property implies that the actor was involved in the event but does not imply any causal relationship. For instance, someone having been portrayed can be said to have participated in the creation of the portrait.
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 instance of E5 Event without implying any specific role. It documents known events in which an instance of E77 Persistent Item was present during the course of its life or history. For example, an object may be the desk, now in a museum, on which a treaty was signed. The instance of E53 Place and the instance of E52 Time-Span where and when these events happened provide us with constraints about the presence of the related instance E77 Persistent Item in the past. Instances of E90 Symbolic Object, in particular information objects, are physically present in events via at least one of the instances of E18 Physical Thing carrying them. Note, that the human mind can be such a carrier. A precondition for a transfer of information to a person or another new physical carrier is the presence of the respective information object and this person or physical thing in one event.
notation: P12
domain: Event

destroyed
type: ObjectProperty
range: Physical Thing
comment: This property links an instance of E6 Destruction to an instance of E18 Physical Thing that has been destroyed by it. Destruction implies the end of an item’s life as a subject of cultural documentation – the physical matter of which the item was composed may in fact continue to exist. An instance of E6 Destruction may be contiguous with an instance of E12 Production that brings into existence a derived object composed partly of matter from the destroyed object.
notation: P13
domain: Destruction

carried out by
type: ObjectProperty
range: Actor
comment: This property describes the active participation of an instance of E39 Actor in an instance of E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property specifies the nature of an Actor’s participation.
notation: P14
domain: Activity

was influenced by
type: ObjectProperty
range: CRM Entity
comment: This is a high-level property, which captures the relationship between an instance of E7 Activity and anything, that is, an instance of E1 CRM Entity that may have had some bearing upon it.The property has more specific sub properties.
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 instance of E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer.Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.
notation: P16
domain: Activity

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 instance of E7 Activity. For example, the discovery of a large hoard of treasure may call for a celebration, an order from headquarters can start a military manoeuvre.
notation: P17
domain: Activity

was intended use of
type: ObjectProperty
range: Human-Made Thing
comment: This property relates an instance of E7 Activity with instances of E71 Human-Made Thing, created specifically for use in the activity. This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)).
notation: P19
domain: Activity

had specific purpose
type: ObjectProperty
range: Event
comment: This property identifies the relationship between a preparatory activity, an instance of E7 Activity and the instance of E5 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

had general purpose
type: ObjectProperty
range: Type
comment: This property describes an intentional relationship between an instance of E7 Activity and some general goal or purpose, described as an instance of E55 Type. This may involve activities intended as preparation for some type of activity or event. P21 had general purpose (was purpose of) differs from P20 had specific purpose (was purpose of) in that no occurrence of an event is implied as the purpose.
notation: P21
domain: Activity

transferred title to
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E39 Actor that acquires the legal ownership of an object as a result of an instance of E8 Acquisition. The property will typically describe an Actor purchasing or otherwise acquiring an object from another Actor. However, title may also be acquired, without any corresponding loss of title by another Actor, through legal fieldwork such as hunting, shooting or fishing.In reality the title is either transferred to or from someone, or both.
notation: P22
domain: Acquisition

transferred title from
type: ObjectProperty
range: Actor
comment: This property identifies the instance(s) of E39 Actor who relinquish legal ownership as the result of an instance of E8 Acquisition.The property will typically be used to describe a person donating or selling an object to a museum. In reality title is either transferred to or from someone, or both.
notation: P23
domain: Acquisition

transferred title of
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance(s) of E18 Physical Thing involved in an instance of E8 Acquisition. In reality, an acquisition must refer to at least one transferred item.
notation: P24
domain: Acquisition

moved
type: ObjectProperty
range: Physical Object
comment: This property identifies an instance of E19 Physical Object that was moved by an instance of E9 Move. A move must concern at least one object.The property implies the object’s passive participation. For example, Monet’s painting “Impression sunrise” was moved for the first Impressionist exhibition in 1874.
notation: P25
domain: Move

moved to
type: ObjectProperty
range: Place
comment: This property identifies a destination, an instance of E53 place, of an instance of E9 Move. A move will be linked to a destination, such as the move of an artifact from storage to display. A move may be linked to many terminal instances of E53 Place by multiple instances of this property. In this case the move describes a distribution of a set of objects. The area of the move includes the origin(s), route and destination(s).Therefore, the described destination is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at.
notation: P26
domain: Move

moved from
type: ObjectProperty
range: Place
comment: This property identifies an origin, an instance of E53 Place, of an instance of E9 Move.A move will be linked to an origin, such as the move of an artifact from storage to display. A move may be linked to many starting instances of E53 Place by multiple instances of this property. In this case the move describes the picking up of a set of objects. The area of the move includes the origin(s), route and destination(s).Therefore, the described origin is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at.
notation: P27
domain: Move

custody surrendered by
type: ObjectProperty
range: Actor
comment: This property identifies the instance(s) of E39 Actor who surrender custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe an Actor surrendering custody of an object when it is handed over to someone else’s care. On occasion, physical custody may be surrendered involuntarily – through accident, loss or theft.In reality, custody is either transferred to someone or from someone, or both.
notation: P28
domain: Transfer of Custody

custody received by
type: ObjectProperty
range: Actor
comment: This property identifies the instance(s) E39 Actor who receive custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe Actors receiving custody of an object when it is handed over from another Actor’s care. On occasion, physical custody may be received involuntarily or illegally – through accident, unsolicited donation, or theft.In reality, custody is either transferred to someone or from someone, or both.
notation: P29
domain: Transfer of Custody

transferred custody of
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance(s) of E18 Physical Thing concerned in an instance of E10 Transfer of Custody. The property will typically describe the object that is handed over by an instance of E39 Actor to to the custody of another instance of E39 Actor. On occasion, physical custody may be transferred involuntarily or illegally – through accident, unsolicited donation, or theft.
notation: P30
domain: Transfer of Custody

has modified
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance of E18 Physical Thing modified in an instance of E11 Modification.
notation: P31
domain: Modification

used general technique
type: ObjectProperty
range: Type
comment: This property identifies the technique or method, modelled as an instance of E55 Type, that was employed in an instance of E7 Activity. These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques or methods such as embroidery, oil-painting, carbon dating, etc. Specific documented techniques should be described as instances of E29 Design or Procedure.
notation: P32
domain: Activity

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

concerned
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance of E18 Physical Thing that was assessed during an instance of E14 Condition Assessment activity. Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the instance of E18 Physical Thing does not need to be present or extant at the time of assessment.
notation: P34
domain: Condition Assessment

has identified
type: ObjectProperty
range: Condition State
comment: This property identifies the instance of E3 Condition State that was observed in an instance of 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 instance of P37 Identifier Assignment.The same identifier may be assigned on more than one occasion.An Identifier might be created prior to an assignment.
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.De-assignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. The same identifier may be deassigned on more than one occasion.
notation: P38
domain: Identifier Assignment

measured
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of E16 Measurement with the instance of E18 Physical Thing upon which it acted. The instance of E16 Measurement is specific to the measured object. An instance of E18 Physical Thing may be measured more than once with different results, constituting different instances of E16 Measurement.
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 CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
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 P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.A Type may be intellectually constructed independent from assigning an instance of it.
notation: P42
domain: Type Assignment

has dimension
type: ObjectProperty
range: Dimension
comment: This property records an instance of E54 Dimension of some instance of E70 Thing.In the case that the recorded property is a result of a measurement of an instance of E18 Physical Thing, this property is a shortcut of the more fully developed path from E18 Physical Thing through P39i was measured by, E16 Measurement, P40 observed dimension to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. Knowledge about an instance of E54 Dimension need not be the result of a measurement; it may be the result of evaluating data or other information, which should be documented as an instance of E13 Attribute Assignment. An instance of E54 Dimension is specific to an instance of E70 Thing.
notation: P43
domain: Thing

has condition
type: ObjectProperty
range: Condition State
comment: This property records an E3 Condition State for some E18 Physical Thing.This property is a shortcut of the more fully developed path from E18 Physical Thing through P34i was assessed by, E14 Condition Assessment, P35 has identified to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom. An instance of Condition State is specific to an instance of E18 Physical Thing.
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 associates an instance of E18 Physical Thing with another instance of Physical Thing that forms part of it. The spatial extent of the composing part is included in the spatial extent of the whole.Component elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall. This property does not specify when and for how long a component element resided in the respective whole. If a component is not part of a whole from the beginning of existence or until the end of existence of the whole, the classes E79 Part Addition and E90 Part Removal can be used to document when a component became part of a particular whole and/or when it stopped being a part of it. For the time-span of being part of the respective whole, the component is completely contained in the place the whole occupies.This property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property.The instances of E57 Material of which an instance of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in).This property is transitive and asymmetric.
notation: P46
domain: Physical Thing

has preferred identifier
type: ObjectProperty
range: Identifier
comment: This property records the preferred instance of E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded.More than one preferred identifier may have been assigned to an item over time.Use of this property requires an external mechanism for assigning temporal validity to the respective CIDOC CRM instance.The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable instance of E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property.
notation: P48
domain: CRM Entity

has former or current keeper
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E39 Actor who has or has had custody of an instance of E18 Physical Thing at some time. This property leaves open the question if parts of this physical thing have been added or removed during the time-spans it has been under the custody of this actor, but it is required that at least a part which can unambiguously be identified as representing the whole has been under this custody for its whole time. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P30i custody transferred through, E10 Transfer of Custody, P28 custody surrendered by or P29 custody received by to E39 Actor.
notation: P49
domain: Physical Thing

has current keeper
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E39 Actor that had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property.This property is a shortcut for the more detailed path from E18 Physical Thing through, P30i custody transferred through, E10 Transfer of Custody, P29 custody received by to E39 Actor, if and only if the custody has not been surrendered by the receiving actor at any later time
notation: P50
domain: Physical Thing

has former or current owner
type: ObjectProperty
range: Actor
comment: This property identifies an instance of E39 Actor that is or had been the legal owner (i.e., title holder) of an instance of E18 Physical Thing at some time.The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P24i changed ownership through, E8 Acquisition, P23 transferred title from, or P22 transferred title to to E39 Actor.
notation: P51
domain: Physical Thing

has current owner
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E21 Person or E74 Group that was the owner of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property.This property is a shortcut for the more detailed path from E18 Physical Thing through, P24i changed ownership through, E8 Acquisition, P22 transferred title to to E39 Actor, if and only if this acquisition event is the most recent.
notation: P52
domain: Physical Thing

has former or current location
type: ObjectProperty
range: Place
comment: This property identifies an instance of E53 Place as the former or current location of an instance of E18 Physical Thing.In the case of instances of E19 Physical Object, the property does not allow any indication of the Time-Span during which the instance of E19 Physical Object was located at this instance of E53 Place, nor if this is the current location.In the case of immobile objects, the Place would normally correspond to the Place of creation.This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, though, P25i moved by, E9 Move, P26 moved to or P27 moved from to E53 Place.
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 instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property.This property is a specialisation of P53 has former or current location (is former or current location of). It indicates that the instance of E53 Place associated with the instance of E19 Physical Object is the current location of the object. The property does not allow any indication of how long the object has been at the current location. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, through, P25i moved by, E9 Move, P26 moved to to E53 Place if and only if this Move is the most recent.
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 instance of E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An instance of E27 Site should be considered as an instance of E26 Physical Feature on the surface of the Earth.An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i is found on the same E19 Physical Object as A. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path E19 Physical Object, through, P59 has section, E53 Place, P53i is former or current location of to E26 Physical Feature.
notation: P56
domain: Physical Object

has number of parts
type: ObjectProperty
range: Number
comment: This property documents the number of parts, an instance of E60 Number, of which an instance of E19 Physical Object is composed.This may be used as a method of checking inventory counts with regard to aggregate or collective objects. What constitutes a part or component depends on the context and requirements of the documentation. Normally, the parts documented in this way would not be considered as worthy of individual attention.For a more complete description, objects may be decomposed into their components and constituents using P46 is composed of (forms parts of) and P45 consists of (is incorporated in). This allows each element to be described individually.
notation: P57
domain: Physical Object

has section
type: ObjectProperty
range: Place
comment: This property links an area, i.e., an instance of E53 Place to the instance of E18 Physical Thing upon which it is found. This area may either be identified by a name, or by a geometry in terms of a coordinate system adapted to the shape of the respective instance of E18 Physical Thing. Typically, names identifying sections of physical objects are composed of the name of a kind of part and the name of the object itself, such as "The poop deck of H.M.S. Victory", which is composed of "poop deck" and "H.M.S. Victory".
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 Human-Made Thing. Depicting is meant in the sense that an instance of E24 Physical Human-Made Thing intentionally shows, through its optical qualities or form, a representation of the entity depicted. Photographs are by default regarded as being intentional in this sense. Anything that is designed to change the properties of the depiction, such as an e-book reader, is specifically excluded. The property does not pertain to inscriptions or any other information encoding.This property is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined.
notation: P62
domain: Physical Human-Made Thing

shows visual item
type: ObjectProperty
range: Visual Item
comment: This property documents an instance of E36 Visual Item shown by an instance of E24 Physical Human-Made Thing.This property is similar to P62 depicts (is depicted by) in that it associates an instance of E24 Physical Human-Made Thing with a visual representation. However, P65 shows visual item (is shown by) differs from the P62 depicts (is depicted by) property in that it makes no claims about what the instance of E36 Visual Item is deemed to represent. An instance of E36 Visual Item identifies a recognisable image or visual symbol, regardless of what this image may or may not represent.For example, all recent British coins bear a portrait of Queen Elizabeth II, a fact that is correctly documented using P62 depicts (is depicted by). Different portraits have been used at different periods, however. P65 shows visual item (is shown by) can be used to refer to a particular portrait.P65 shows visual item (is shown by) may also be used for Visual Items such as signs, marks and symbols, for example the ''Maltese Cross'' or the ''copyright symbol’ that have no particular representational content. This property is part of the fully developed path E24 Physical Human-Made Thing, P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity which is shortcut by, P62 depicts (is depicted by).
notation: P65
domain: Physical Human-Made Thing

refers to
type: ObjectProperty
range: CRM Entity
comment: This property documents that an instance of E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the instance of E89 Propositional Object.
notation: P67
domain: Propositional Object

foresees use of
type: ObjectProperty
range: Material
comment: This property identifies an instance of E57 Material foreseen to be used by an instance of E29 Design or Procedure. E29 Designs and procedures commonly foresee the use of particular instances of E57 Material. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented.This property is not intended for the documentation of instances of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed.
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 property is not transitiveThis property is a directed relationship. 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.Instances of this property are considered to be symmetric, in case no directed sense is provided for them by the property P69.1 has type.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 as instances of E31 Document. Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement.
notation: P70
domain: Document

lists
type: ObjectProperty
range: CRM Entity
comment: This property associates an instance of E32 Authority Document, with an instance of E1 CRM Entity which it lists for reference purposes.
notation: P71
domain: Authority Document

has language
type: ObjectProperty
range: Language
comment: This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed. Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
notation: P72
domain: Linguistic Object

has translation
type: ObjectProperty
range: Linguistic Object
comment: This property links an instance of E33 Linguistic Object (A), to another instance of E33 Linguistic Object (B) which is the translation of A.When an instance of E33 Linguistic Object is translated into a new language a new instance of E33 Linguistic Object is created, despite the translation being conceptually similar to the source.This property is asymmetric.
notation: P73
domain: Linguistic Object

has current or former residence
type: ObjectProperty
range: Place
comment: This property describes the current or former place of residence (an instance of E53 Place) of an instance of E39 Actor. The residence may be either the place where the actor resides, or a legally registered address of any kind.
notation: P74
domain: Actor

possesses
type: ObjectProperty
range: Right
comment: This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim.
notation: P75
domain: Actor

has contact point
type: ObjectProperty
range: Appellation
comment: This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address.
notation: P76
domain: Actor

beginning is qualified by
type: ObjectProperty
range: String
comment: This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the certainty, precision, sources etc. of its beginning. Such notes may also be used to elaborate arguments about constraints or to give explanations of alternatives.
notation: P79
domain: Time-Span

end is qualified by
type: ObjectProperty
range: String
comment: This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the end of this time-span concerning certainty, precision, sources etc. This property may also be used to describe arguments constraining possible dates and to distinguish reasons for alternative dates.
notation: P80
domain: Time-Span

ongoing throughout
type: ObjectProperty
range: Time Primitive
comment: This property associates an instance of E52 Time-Span with an instance of E61 Time Primitive specifying a minimum period of time covered by it. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s minimum temporal extent (i.e., its inner boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different minimum extents without contradicting each other, the smallest interval including all these extents will be the best estimate. This should be taken into account for information integration.
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 CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s maximum temporal extent (i.e., its outer boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different maximum extents without contradicting each other, the resulting intersection of all these extents will be the best estimate. This should be taken into account for information integration.
notation: P82
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 the temporal extent of an instance of E52 Time-Span falls within the temporal extent of another instance of E52 Time-Span. It addresses temporal containment only, and no contextual link between the two instances of E52 Time-Span is implied. This property is transitive and reflexive.
notation: P86
domain: Time-Span

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

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

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

brought into existence
type: ObjectProperty
range: Persistent Item
comment: This property links an instance of E63 Beginning of Existence to the instance of E77 Persistent Item brought into existence by it.It allows a “start” to be attached to any instance of E77 Persistent Item being documented, i.e., as instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation and E55 Type.
notation: P92
domain: Beginning of Existence

took out of existence
type: ObjectProperty
range: Persistent Item
comment: This property links an instance of E64 End of Existence to the instance of E77 Persistent Item taken out of existence by it.In the case of immaterial things, the instance of E64 End of Existence is considered to take place with the destruction of the last physical carrier.This allows an “end” to be attached to any instance of E77 Persistent Item being documented i.e., instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation and E55 Type. For many instances of E77 Persistent Item we know the maximum life-span and can infer that they must have ended to exist. We assume in that case an instance of E64 End of Existence, which may be as unnoticeable as forgetting the secret knowledge by the last representative of some indigenous nation.
notation: P93
domain: End of Existence

has created
type: ObjectProperty
range: Conceptual Object
comment: This property links an instance of E65 Creation to the instance of E28 Conceptual Object created by it. It represents the act of conceiving the intellectual content of the instance of E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the instance of E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.
notation: P94
domain: Creation

has formed
type: ObjectProperty
range: Group
comment: This property associates the instance of E66 Formation with the instance of E74 Group that it founded.
notation: P95
domain: Formation

by mother
type: ObjectProperty
range: Person
comment: This property links an instance of E67 Birth to an instance of E21 Person in the role of birth-giving mother.Note that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The instance of E21 Person being born is linked to the instance of E67 Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions.
notation: P96
domain: Birth

from father
type: ObjectProperty
range: Person
comment: This property links an instance of E67 Birth to an instance of E21 Person in the role of biological father.Note that biological fathers are not seen as necessary participants in the birth, whereas birth-giving mothers are (see P96 by mother (gave birth)). The Person being born is linked to the Birth with the property P98 brought into life (was born).This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. An instance of E67 Birth is normally (but not always) associated with one biological father.
notation: P97
domain: Birth

brought into life
type: ObjectProperty
range: Person
comment: This property links an instance of E67 Birth event to an instance of E21 Person in the role of offspring.Twins, triplets etc. are brought into life by the same instance of E67 Birth. This is not intended for use with general Natural History material, only people. There is no explicit method for modelling conception and gestation except by using extensions.
notation: P98
domain: Birth

dissolved
type: ObjectProperty
range: Group
comment: This property associates the instance of E68 Dissolution with the instance of E74 Group that it disbanded.
notation: P99
domain: Dissolution

was death of
type: ObjectProperty
range: Person
comment: This property links an instance of E69 Death to the instance of E21 Person that died.An instance of E69 Death may involve multiple people, for example in the case of a battle or disaster.This is not intended for use with general natural history material, only people.
notation: P100
domain: Death

had as general use
type: ObjectProperty
range: Type
comment: This property associates an instance of E70 Thing with an instance of E55 Type that describes the type of use that it was actually employed for.It allows the relationship between particular things, both physical and immaterial, and the general methods and techniques of real use to be documented. This may well be different from the intended functional purpose of the instance of E70 Thing (which can be documented with P103 was intended for (was intention of)). For example, it could be recorded that a particular wooden crate had a general use as a shelf support on a market stall even though it had been originally intended for carrying vegetables.The use of this property is intended to allow the documentation of usage patterns attested in historical records or through scientific investigation (for instance ceramic residue analysis). It should not be used to document the intended, and thus assumed, use of an object.
notation: P101
domain: Thing

has title
type: ObjectProperty
range: Title
comment: This property associates an instance of E35 Title has been applied to an instance of E71 Human-Made Thing. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the title and the thing to be further clarified, for example, if the title was a given title, a supplied title etc.It allows any human-made material or immaterial thing to be given a title. It is possible to imagine a title being created without a specific object in mind.
notation: P102
domain: Human-Made Thing

was intended for
type: ObjectProperty
range: Type
comment: This property links an instance of E71 Human-Made Thing to an instance of E55 Type describing its intended usage. It creates a relation between specific human-made things, both physical and immaterial, to types of intended methods and techniques of use. Note: A link between specific human-made things and a specific use activity should be expressed using P19 was intended use of (was made for).
notation: P103
domain: Human-Made Thing

is subject to
type: ObjectProperty
range: Right
comment: This property links a particular instance of E72 Legal Object to the instances of E30 Right to which it is subject.The Right is held by an E39 Actor as described by P75 possesses (is possessed by).
notation: P104
domain: Legal Object

right held by
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E39 Actor who holds the instances of E30 Right to an instance of E72 Legal Object.It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object.This property is a shortcut of the fully developed path from E72 Legal Object, P104 is subject to, E30 Right, P75i is possessed by to E39 Actor.
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.This property is transitive asymmetric.
notation: P106
domain: Symbolic Object

has current or former member
type: ObjectProperty
range: Actor
comment: This property associates an instance of E74 Group with an instance of E39 Actor that is or has been a member thereof.Instances of E74 Group and E21 Person may all be members of instances of E74 Group. An instance of E74 Group may be founded initially without any member. This property is a shortcut of the more fully developed path from E74 Group, P144i gained member by, E85 Joining, P143 joined to E39 Actor.The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group.
notation: P107
domain: Group

has produced
type: ObjectProperty
range: Physical Human-Made Thing
comment: This property identifies the instance of E24 Physical Human-Made Thing that came into existence as a result of the instance of E12 Production.The identity of an instance of E24 Physical Human-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Human-Made Thing.
notation: P108
domain: Production

has current or former curator
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E39 Actor who assumed or have assumed overall curatorial responsibility for an instance of E78 Curated Holding.It does not allow a history of curation to be recorded. This would require use of an event initiating a curator being responsible for a collection.
notation: P109
domain: Curated Holding

augmented
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance of E24 Physical Human-Made Thing that is added to (augmented) in an instance of E79 Part Addition.Although an instance of E79 Part Addition event normally concerns only one instance of E24 Physical Human-Made Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.
notation: P110
domain: Part Addition

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

diminished
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance of E18 Physical Thing that was diminished by an instance of E80 Part Removal.Although an instance of E80 Part removal activity normally concerns only one instance of E18 Physical Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single instance of E80 Part Removal activity.
notation: P112
domain: Part Removal

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

overlaps with
type: ObjectProperty
range: Place
comment: This symmetric property associates an instance of E53 Place with another instance of E53 Place geometrically overlapping it. It does not specify anything about the shared area. This property is purely spatial. It does not imply that phenomena that define, by their extent, places related by P121 overlaps with have ever covered a common area at the same time or even coexisted. In contrast, spatiotemporal overlaps described by P132 spatiotemporally overlaps are the total of areas simultaneously covered by the related spacetime volumes.This property is symmetric. This property is reflexive.
notation: P121
domain: Place

borders with
type: ObjectProperty
range: Place
comment: This symmetric property associates an instance of E53 Place with another instance of E53 Place which shares a part of its border. This property is purely spatial. It does not imply that the phenomena that define, by their extent, places related by P122 borders with have ever shared a respective border at the same time or even coexisted. In particular, this may be the case when the respective common border is formed by a natural feature. This property is not transitive. This property is symmetric.
notation: P122
domain: Place

resulted in
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance or instances of E18 Physical Thing that are the result of an instance of E81 Transformation. New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the links to the common instance of E81 Transformation.
notation: P123
domain: Transformation

transformed
type: ObjectProperty
range: Physical Thing
comment: This property identifies the instance or instances E18 Physical Thing that have ceased to exist due to an instance of E81 Transformation.The item that has ceased to exist and was replaced by the result of the Transformation. The continuity between both items, the new and the old, is expressed by the links to the common instance of E81 Transformation.
notation: P124
domain: Transformation

used object of type
type: ObjectProperty
range: Type
comment: This property associates an instance of E7 Activity to an instance of E55 Type, which classifies an instance of E70 Thing used in an instance of E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer".This property is a shortcut of the more fully developed path from E7 Activity through P16 used specific object, E70 Thing, P2 has type, to E55 Type
notation: P125
domain: Activity

employed
type: ObjectProperty
range: Material
comment: This property identifies the instance of E57 Material employed in an instance of E11 Modification.The instance of E57 Material used during the instance of E11 Modification does not necessarily become incorporated into the instance of E24 Physical Human-Made Thing that forms the subject of the instance of E11 Modification.
notation: P126
domain: Modification

has broader term
type: ObjectProperty
range: Type
comment: This property associates an instance of E55 Type with another instance of E55 Type that has a broader meaning. It allows instances of E55 Types to be organised into hierarchies. This is the sense of "broader term generic (BTG)" as defined in ISO 25964-2:2013 (International Organization for Standardization 2013).This property is transitive. This property is asymmetric.
notation: P127
domain: Type

carries
type: ObjectProperty
range: Symbolic Object
comment: This property identifies an instance E90 Symbolic Object carried by an instance of E18 Physical Thing. Since an instance of E90 Symbolic Object is defined as an immaterial idealization over potentially multiple carriers, any individual realization on a particular physical carrier may be defective, due to deterioration or shortcomings in the process of creating the realization compared to the intended ideal. As long as such defects do not substantially affect the complete recognition of the respective symbolic object, it is still regarded as carrying an instance of this E90 Symbolic Object. If these defects are of scholarly interest, the particular realization can be modelled as an instance of E25 Human-Made Feature. Note, that any instance of E90 Symbolic Object incorporated (P165) in the carried symbolic object is also carried by the same instance of E18 Physical Thing.
notation: P128
domain: Physical Thing

is about
type: ObjectProperty
range: CRM Entity
comment: This property documents that an instance of E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an instance of E1 CRM Entity, in that it describes the primary subject or subjects of an instance of E89 Propositional Object.
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 directed relationship, where the domain expresses the derivative or influenced item and the range the source or influencing item, if such a direction can be established. The property can also be used to express similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. The property expresses a symmetric relationship in case no direction of influence can be established either from evidence on the item itself or from historical knowledge. This holds in particular for siblings of a derivation process from a common source or non-causal cultural parallels, such as some weaving patterns.The P130.1 kind of similarity property of the P130 shows features of (features are also found on) property enables the relationship between the domain and the range to be further clarified, in the sense from domain to range, if applicable. For example, it may be expressed if both items are product “of the same mould”, or if two texts “contain identical paragraphs”. If the reason for similarity is a sort of derivation process, i.e., that the creator has used or had in mind the form of a particular thing during the creation or production, this process should be explicitly modelled. In these cases, P130 shows features of can be regarded as a shortcut of such a process. However, the current model does not contain any path specific enough to infer this property. Specializations of the CIDOC CRM may however be more explicit, for instance describing the use of moulds etc.This property is not transitive. This property is irreflexive.
notation: P130
domain: Thing

spatiotemporally overlaps with
type: ObjectProperty
range: Spacetime Volume
comment: This symmetric property associates two instances of E92 Spacetime Volume that have some of their extents in common. If only the fuzzy boundaries of the instances of E92 Spacetime Volume overlap, this property cannot be determined from observation alone and therefore should not be applied. However, there may be other forms of justification that the two instances of E92 Spacetime Volume must have some of their extents in common regardless of where and when precisely. If this property holds for two instances of E92 Spacetime Volume then it cannot be the case that P133 is spatiotemporally separated from also holds for the same two instances. Furthermore, there are cases where neither P132 spatiotemporally overlaps with nor P133 is spatiotemporally separated from holds between two instances of E92 Spacetime Volume. This would occur where only an overlap of the fuzzy boundaries of the two instances of E92 Spacetime Volume occurs and no other evidence is available. This property is not transitive. This property is symmetric. This property is reflexive.
notation: P132
domain: Spacetime Volume

is spatiotemporally separated from
type: ObjectProperty
range: Spacetime Volume
comment: This symmetric property associates two instances of E92 Spacetime Volume that have no extents in common. If only the fuzzy boundaries of the instances of E92 Spacetime Volume overlap, this property cannot be determined from observation alone and therefore should not be applied. However, there may be other forms of justification that the two instances of E92 Spacetime Volume must not have any of their extents in common regardless of where and when precisely. If this property holds for two instances of E92 Spacetime Volume then it cannot be the case that P132 spatiotemporally overlaps with also holds for the same two instances. Furthermore, there are cases where neither P132 spatiotemporally overlaps with nor P133 is spatiotemporally separated from holds between two instances of E92 Spacetime Volume. This would occur where only an overlap of the fuzzy boundaries of the two instances of E92 Spacetime Volume occurs and no other evidence is available.This property is not transitive. This property is symmetric. This property is irreflexive.
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.This property is not transitive. This property is asymmetric.
notation: P134
domain: Activity

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

was based on
type: ObjectProperty
range: CRM Entity
comment: This property identifies one or more instances of E1 CRM Entity that were used as evidence to declare a new instance of E55 Type.The examination of these items is often the only objective way to understand the precise characteristics of a new type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the type, such as "holotype" or "original element".
notation: P136
domain: Type Creation

exemplifies
type: ObjectProperty
range: Type
comment: This property associates an instance of E1 CRM Entity with an instance of E55 Type for which it has been declared to be a particularly characteristic example.The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic role "lectotype" is not associated with the instance of E83 Type Creation itself but is selected in a later phase.
notation: P137
domain: CRM Entity

represents
type: ObjectProperty
range: CRM Entity
comment: This property establishes the relationship between an instance of E36 Visual Item and the instance of E1 CRM Entity that it visually represents.Any entity may be represented visually. This property is part of the fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity, which is shortcut by P62 depicts (is depicted by). P138.1 mode of representation allows the nature of the representation to be refined.This property is also used for the relationship between an original and a digitisation of the original by the use of techniques such as digital photography, flatbed or infrared scanning. Digitisation is here seen as a process with a mechanical, causal component rendering the spatial distribution of structural and optical properties of the original and does not necessarily include any visual similarity identifiable by human observation.
notation: P138
domain: Visual Item

has alternative form
type: ObjectProperty
range: Appellation
comment: This property associates an instance of E41 Appellation with another instance of E41 Appellation that constitutes a derivative or variant of the former and that may also be used for identifying items identified by the former, in suitable contexts, independent from the particular item to be identified. This property should not be confused with additional variants of names used characteristically for a single, particular item, such as individual nicknames. It is a directed relationship, where the range expresses the derivative or variant and the domain the source of derivation or original form of variation, if such a direction can be established. Otherwise, the relationship is symmetric. Multiple names assigned to an object, which do not apply to all things identified with the specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies) of this object.P139.1 has type allows the type of derivation to be refined, for instance “transliteration from Latin 1 to ASCII”.
notation: P139
domain: Appellation

assigned attribute to
type: ObjectProperty
range: CRM Entity
comment: This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity about which it made an attribution. The instance of E1 CRM Entity plays the role of the domain of the attribution. The kind of attribution made should be documented using P177 assigned property of type (is type of property assigned).
notation: P140
domain: Attribute Assignment

assigned
type: ObjectProperty
range: CRM Entity
comment: This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity used in the attribution. The instance of E1 CRM Entity here plays the role of the range of the attribution.The kind of attribution made should be documented using P177 assigned property of type (is type of property assigned).
notation: P141
domain: Attribute Assignment

used constituent
type: ObjectProperty
range: Symbolic Object
comment: This property associates an instance of E15 Identifier Assignment with the instance of E90 Symbolic Object used as constituent of an instance of E42 Identifier in this act of assignment.
notation: P142
domain: Identifier Assignment

joined
type: ObjectProperty
range: Actor
comment: This property identifies the instance of E39 Actor that becomes member of an instance of E74 Group in an instance of E85 Joining.Joining events allow for describing actors becoming members of a group with the more detailed path E74 Group, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).
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, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group.
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: Curated Holding
comment: This property associates an instance of E87 Curation Activity with the instance of E78 Curated Holding with that is subject of that curation activity following some implicit or explicit curation plan.
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.This property is transitive. This property is asymmetric.
notation: P148
domain: Propositional Object

defines typical parts of
type: ObjectProperty
range: Type
comment: This property 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 based on one type describing a typical part of another. This property is equivalent to "broader term partitive (BTP)" as defined in ISO 2788 and “broaderPartitive” in SKOS.This property is not transitive. This property is asymmetric.
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 E21 Person through P98i was born, E67 Birth, P96 by mother to E21 Person, and from E21 Person through P98i was born, E67 Birth, P97 from father to E21 Person.This property is not transitive. This property is irreflexive.
notation: P152
domain: Person

occupies
type: ObjectProperty
range: Place
comment: This property describes the largest volume in space, an instance of E53 Place, that an instance of E18 Physical Thing has occupied at any time during its existence, with respect to the reference space relative to the physical thing itself. This allows for describing 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. The reference space for the associated place must be the one that is permanently at rest (P157 is at rest relative to) relative to the physical thing. For instances of E19 Physical Objects it is the one which is at rest relative to the object itself, i.e., which moves together with the object. For instances of E26 Physical Feature it is one which is at rest relative to the physical feature itself and the surrounding matter immediately connected to it. Therefore, there is a 1:1 relation between the instance E18 Physical Thing and the instance of E53 Place it occupies. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces. This property implies the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place. However, in contrast to P156 occupies, the property P161 has spatial projection does not constrain the reference space of the referred instance of E53 Place. In contrast to P156 occupies, for the property P53 has former or current location the following holds: It does not constrain the reference space of the referred instance of E53 Place. It identifies a possibly wider instance of E53 Place at which a thing is or has been for some unspecified time-span. If the reference space of the referred instance of E53 Place is not at rest with respect to the physical thing found there, the physical thing may move away after some time to another place and/or may have bee…
notation: P156
domain: Physical Thing

is at rest relative to
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of E53 Place with the instance of E18 Physical Thing that determines a reference space for this instance of E53 Place by being at rest with respect to this reference space. The relative stability of form of an instance of 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 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 an instance of E92 Spacetime Volume with an instance of E53 Place that is the result of the spatial projection of the instance of the E92 Spacetime Volume on a reference space.In general, there can be more than one useful reference space (for reference space see P156 occupies and P157 is at rest relative to) to describe the spatial projection of a spacetime volume, for example, in describing a sea battle, the difference between the battle ship and the seafloor as reference spaces. Thus, it can be seen that the projection is not unique.The spatial projection is the actual spatial coverage of a spacetime volume, which normally has fuzzy boundaries except for instances of E92 Spacetime Volumes which are geometrically defined in the same reference system as the range of this property are an exception to this and do not have fuzzy boundaries. Modelling explicitly fuzzy spatial projections serves therefore as a common topological reference of different spatial approximations rather than absolute geometric determination, for instance for relating outer or inner spatial boundaries for the respective spacetime volumes.In case the domain of an instance of P161 has spatial projection is an instance of E4 Period, the spatial projection describes all areas that period was ever present at, for instance, the Roman Empire. This property is part of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place, which in turn is implied by P156 occupies (is occupied by). This property is part of the fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place, which in turn is shortcut by P7 took place at (witnessed).
notation: P161
domain: Spacetime Volume

is temporally specified by
type: ObjectProperty
range: Time-Span
comment: This property relates an instance of E93 Presence with the instance of E52 Time-Span that defines the time-slice of the spacetime volume that this instance of E93 Presence is related to via the property P166 was a presence of (had presence).There are two typical cases for the determination of the related instance of E52 Time-Span. In the first, it is the temporal extent of an instance of E2 Temporal Entity (documented with P4 has time-span (is time-span of)): this then documents the simultaneity of the instance of E93 Presence and the instance of E2 Temporal Entity, even if the absolute time-span is not known, and can be regarded as a phenomenal time-span. In the second, the instance of E52 Time-Span is a date range declared in or derived from historical sources or provided by dating methods: this is a declarative time-span.
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 instances of E73 Information Object, 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.When restricted to information objects, that is, seen as a property with E73 Information Object as domain and range the property is transitive.A digital photograph of a manuscript page incorporates the text of a manuscript page, if the respective text is defined as a sequence of symbols of a particular type, such as Latin characters, and the resolution and quality of the digital image is sufficient to resolve these symbols so they are readable on the digital image.This property is asymmetric.
notation: P165
domain: Information Object

was a presence of
type: ObjectProperty
range: Spacetime Volume
comment: This property associates an instance of E93 Presence with the instance of E92 Spacetime Volume of which it represents a temporal restriction (i.e.: a time-slice). Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence.
notation: P166
domain: Presence

was within
type: ObjectProperty
range: Place
comment: This property associates an instance of E93 Presence with an instance of E53 Place that geometrically includes the spatial projection of the respective instance of E93 Presence. Besides others, this property may be used to state in which space an object has been for some known time, such as a room of a castle or in a drawer. It may also be used to describe a confinement of the spatial extent of some realm during a known time-span. This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place.
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 always result in new definitions of places approximating each other and not in alternative definitions.
notation: P168
domain: Place

defines spacetime volume
type: ObjectProperty
range: Spacetime Volume
comment: This property associates an instance of E95 Spacetime Primitive with the instance of E92 Spacetime Volume it defines.
notation: P169
domain: Spacetime Primitive

defines time
type: ObjectProperty
range: Time-Span
comment: This property associates an instance of E61 Time Primitive with the instance of E52 Time-Span that constitutes the interpretation of the terms of the time primitive as an extent in absolute, real time. The quantification allows several instances of E61 Time Primitive that are each expressed in different syntactic forms, to define the same instance of E52 Time-Span.
notation: P170
domain: Time Primitive

at some place within
type: ObjectProperty
range: Space Primitive
comment: This property describes the maximum spatial extent within which an instance of E53 Place falls. Since instances of E53 Places may not have precisely known spatial extents, the CIDOC CRM supports statements about maximum spatial extents of instances of E53 Place. This property allows an instance of E53 Place’s maximum spatial extent (i.e., its outer boundary) to be assigned an instance of E94 Space Primitive value. This property is a shortcut of the fully developed path from E53 Place, P89 falls within, E53 Place, P168 place is defined by to E94 Space Primitive through a declarative Place that is not explicitly documented, to a Space Primitive: declarative places are defined in CRMgeo (Doerr and Hiebel 2013).
notation: P171
domain: Place

contains
type: ObjectProperty
range: Space Primitive
comment: This property describes a minimum spatial extent which is contained within an instance of E53 Place. Since instances of E53 Place may not have precisely known spatial extents, the CIDOC CRM supports statements about minimum spatial extents of instances of E53 Place. This property allows an instance of E53 Places’s minimum spatial extent (i.e., its inner boundary or a point being within a Place) to be assigned an instance of E94 Space Primitive value. This property is a shortcut of the fully developed path from E53 Place, P89i contains, E53 Place, P168 place is defined by to E94 Space Primitive
notation: P172
domain: Place

starts before or with the end of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity.In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bend is true.This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to the disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, met-by, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by}.This property is not transitive. Figure 8: Temporal entity A starts before or with the end of temporal entity B. Here A is longer than B Figure 9: Temporal entity A starts before or with the end of temporal entity B. Here A is shorter than B
notation: P173
domain: Temporal Entity

starts before the end of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart < Bend is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by}Typically, this property is a consequence of a known influence of some event on another event or activity, such as a novel written by someone being continued by someone else, or the knowledge of a defeat on a distant battlefield causing people to end their ongoing activities. This property is not transitive. This property is irreflexive. Figure 10: Temporal entity A starts before the end of temporal entity B. Here A is longer than B Figure 11: Temporal entity A starts before the end of temporal entity B. Here A is shorter than B
notation: P174
domain: Temporal Entity

starts before or with the start of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bstart is true.This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finished-by, equals}In a model with fuzzy borders, this property will not be transitive.This property is irreflexive. Figure 12: Temporal entity A starts before or with the start of temporal entity B. Here A is longer than B Figure 13: Temporal entity A starts before or with the start of temporal entity B. Here A is shorter than B
notation: P175
domain: Temporal Entity

starts before the start of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart < Bstart is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, contains, finished-by}. This property is transitive. This property is asymmetric. Figure 14: Temporal entity A starts before the start of temporal entity B. Here A is longer than B Figure 15: Temporal entity A starts before the start of temporal entity B. Here A is shorter than B
notation: P176
domain: Temporal Entity

assigned property of type
type: ObjectProperty
range: Type
comment: This property associates an instance of E13 Attribute Assignment with the type of property or relation that this assignment maintains to hold between the item to which it assigns an attribute and the attribute itself. Note that the properties defined by the CIDOC CRM also constitute instances of E55 Type themselves. The direction of the assigned property of type is understood to be from the attributed item (the range of property P140 assigned attribute to) to the attribute item (the range of the property P141 assigned). More than one property type may be assigned to hold between two items.A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.
notation: P177
domain: Attribute Assignment

had sales price
type: ObjectProperty
range: Monetary Amount
comment: This property establishes the relationship between an instance of E96 Purchase and the instance of E97 Monetary Amount that forms the compensation for the transaction. The monetary amount agreed upon may change in the course of the purchase activity.
notation: P179
domain: Purchase

has currency
type: ObjectProperty
range: Currency
comment: This property establishes the relationship between an instance of E97 Monetary Amount and the instance of E98 Currency that it is measured in.
notation: P180
domain: Monetary Amount

ends before or with the start of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bstart is true.This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets}.This property is transitive. This property is asymmetric. Figure 16: Temporal entity A ends before or with the start of temporal entity B. Here A is longer than B Figure 17: Temporal entity A ends before or with the start of temporal entity B. Here A is shorter than B
notation: P182
domain: Temporal Entity

ends before the start of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend < Bstart is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to the following Allen temporal relation (Allen, 1983) : {before}.This property is transitive. This property is asymmetric. Figure 18: Temporal entity A ends before the start of temporal entity B. Here A is longer than B Figure 19: Temporal entity A ends before the start of temporal entity B. Here A is shorter than B
notation: P183
domain: Temporal Entity

ends before or with the end of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bend is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, finished by, start, equals, during, finishes}.This property is irreflexive Figure 20: Temporal entity A ends before or with the end of temporal entity B. Here A is longer than B Figure 21: Temporal entity A ends before or with the end of temporal entity B. Here A is shorter than B
notation: P184
domain: Temporal Entity

ends before the end of
type: ObjectProperty
range: Temporal Entity
comment: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend < Bend is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185.This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, during}.This property is transitive. This property is asymmetric. Figure 22: Temporal entity A ends before the end of temporal entity B. Here A is longer than B Figure 23: Temporal entity A ends before the end of temporal entity B. Here A is shorter than B
notation: P185
domain: Temporal Entity

produced thing of product type
type: ObjectProperty
range: Product Type
comment: This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces.
notation: P186
domain: Production

has production plan
type: ObjectProperty
range: Design or Procedure
comment: This property associates an instance of E99 Product Type with an instance of E29 Design or Procedure that completely determines the production of instances of E18 Physical Thing. The resulting instances of E18 Physical Thing are considered exemplars of this instance of E99 Product Type when the process specified is correctly executed. Note that the respective instance of E29 Design or Procedure may not necessarily be fixed in a written/graphical form, and may require the use of tools or models unique to the product type. The same instance of E99 Product Type may be associated with several variant plans.
notation: P187
domain: Product Type

requires production tool
type: ObjectProperty
range: Physical Object
comment: This property associates an instance of E99 Product Type with an instance of E19 Physical Object that is needed for the production of an instance of E18 Physical Thing. When the process of production is correctly executed in accordance with the plan and using the specified instance of E19 Physical Object, the resulting instance of E18 Physical Thing is considered an exemplar of this instance of E99 Product Type. The instance of E19 Physical Object may bear distinct features that are transformed into characteristic features of the resulting instance of E18 Physical Thing. Examples include models and moulds.
notation: P188
domain: Product Type

approximates
type: ObjectProperty
range: Place
comment: This property associates an instance of E53 Place with another instance of E53 Place, which is defined in the same reference space, and which is used to approximate the former. The property does not necessarily state the quality or accuracy of this approximation, but rather indicates the use of the first instance of place to approximate the second.In common documentation practice, find or encounter spots e.g., in archaeology, botany or zoology are often related to the closest village, river or other named place without detailing the relation, e.g., if it is located within the village or in a certain distance of the specified place. In this case the stated “phenomenal” place found in the documentation can be seen as approximation of the actual encounter spot without more specific knowledge. In more recent documentation often point coordinate information is provided that originates from GPS measurements or georeferencing from a map. This point coordinate information does not state the actual place of the encounter spot but tries to approximate it with a “declarative” place. The accuracy depends on the methodology used when creating the coordinates. It may be dependent on technical limitations like GPS accuracy but also on the method where the GPS location is taken in relation to the measured feature. If the methodology is known a maximum deviation from the measured point can be calculated and the encounter spot or feature may be related to the resulting circle using an instance of P171 at some place within.This property is not transitive. This property is reflexive.
notation: P189
domain: Place

has symbolic content
type: ObjectProperty
range: String
comment: This property associates an instance of E90 Symbolic Object with a complete, identifying representation of its content in the form of an instance of E62 String. This property only applies to instances of E90 Symbolic Object that can be represented completely in this form. The representation may be more specific than the symbolic level defining the identity condition of the represented. This depends on the type of the symbolic object represented. For instance, if a name has type "Modern Greek character sequence", it may be represented in a loss-free Latin transcription, meaning however the sequence of Greek letters. As another example, if the represented object has type "English words sequence", American English or British English spelling variants may be chosen to represent the English word "colour" without defining a different symbolic object. If a name has type "European traditional name", no particular string may define its content.
notation: P190
domain: Symbolic Object

had duration
type: ObjectProperty
range: Dimension
comment: This property describes the length of time covered by an instance of E52 Time-Span. It allows an instance of E52 Time-Span to be associated with an instance of E54 Dimension representing duration independent from the actual beginning and end. Indeterminacy of the duration value can be expressed by assigning a numerical interval to the property P90 has value of E54 Dimension.
notation: P191
domain: Time-Span

was a presence of
type: ObjectProperty
range: Physical Thing
comment: This property associates an instance of E93 Presence with the instance of E18 Physical Thing of which it represents a temporal restriction (i.e.: a time-slice) of the thing’s trajectory through spacetime. In other words, it describes where the instance of E18 Physical Thing was or moved around within a given time-span. Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence.This property is a strong shortcut of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P166 was a presence of (had presence) to E93 Presence.
notation: P195
domain: Presence

defines
type: ObjectProperty
range: Spacetime Volume
comment: This property associates an instance of E18 Physical Thing with the instance of E92 Spacetime Volume that constitutes the complete trajectory of its geometric extent through spacetime for the whole time of the existence of the instance of E18 Physical Thing.An instance of E18 Physical Thing not only occupies a particular geometric space at each instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime, i.e., the instance of E92 Spacetime Volume this property associates it with. This real spatiotemporal extent of the instance of E18 Physical Thing is regarded as being unique, in all its details and fuzziness; the identity and existence of the E92 Spacetime Volume depends uniquely on the identity of the instance of E18 Physical Thing, whose existence defines it. It constitutes a phenomenal spacetime volume as defined in CRMgeo (Doerr & Hiebel, 2013).Included in this spacetime volume are both the spaces filled by the matter of the physical thing and any inner space that may exist, for instance the interior of a box. Physical things consisting of aggregations of physically unconnected objects, such as a set of chessmen, occupy a finite number of individually contiguous subsets of this spacetime volume equal to the number of objects that constitute the set and that are never connected during its existence.
notation: P196
domain: Physical Thing

covered parts of
type: ObjectProperty
range: Place
comment: This property associates an instance of E93 Presence with an instance of E53 Place that geometrically overlaps with the spatial projection of the respective instance of E93 Presence. A use case of this property is to state through which places an object or an instance of E21 Person has or was moved within a given time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span. This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P121 overlaps with, to E53 Place.
notation: P197
domain: Presence

holds or supports
type: ObjectProperty
range: Physical Thing
comment: This property relates one instance of E18 Physical Thing which acts as a container or support to a supported or contained instance of E18 Physical Thing. Typical examples of E18 Physical Things which are intended to function as a container or support include shelves, folders or boxes. These containers or supports provide a stable surface which is intended for other physical objects to be placed upon for storage, display, transport or other similar functions.This property is a shortcut of the more fully developed path from E18 Physical Thing through P59 has section, E53 Place, P53i is former or current location of, to E18 Physical Thing. It is not a sub-property of P46 is composed of, as the held or supported object is not a component of the container or support.This property can be used to avoid explicitly instantiating the E53 Place which is defined by an instance of E18 Physical Thing, especially when the only intended use of that instance of E18 Physical Thing is to act as a container or surface for the storage of other instances of E18 Physical Thing. The place’s existence is defined by the existence of the container or surface, and will go out of existence at the same time as the destruction of the container or surface. This property is transitive. This property is asymmetric.
notation: P198
domain: Physical Thing

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. This property is not transitive. It is asymmetric and irreflexive.
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. This property is transitive, asymmetric and irreflexive. The inverse of this property is equivalent to the developed path: F1 Work(1). R3 is realised in: F2 Expression(1). P16i was used for: F28 Expression Creation. R17 created: F2 Expression(2). R3i realises: F1 Work(2). That is, F1 Work(1). R2i has derivative: F1 Work (2), without needing to specify the specific expressions involved in the derivation. 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: Expression
comment: This property associates an instance of F2 Expression with an instance of F1 Work. This property expresses the association that exists between an expression and the work that this expression conveys. Our factual knowledge of how a given work is historically realised into expressions is often limited. Therefore, this property makes it possible to express the association between an instance of F2 Expression and the instance of F1 Work it conveys without identifying the particular instances of F2 Expression that were part of a chain of derivation from the source.
notation: R3
domain: Work

embodies
type: ObjectProperty
range: Expression
comment: This property associates an instance of F3 Manifestation with one or more instances of F2 Expression which are rendered by this instance of F3 Manifestation. The manifestation formats the expression(s) in the way they are to be presented to some public, including specifying the intended sensory impression (such as visual appearance or audio rendition).
notation: R4
domain: Manifestation

has component
type: ObjectProperty
range: Expression
comment: This property associates an instance of an F2 Expression X with a structural component Y that conveys a part of the overall work realized by X, such as volumes, chapters, or sections. This property is transitive, asymmetric and irreflexive. Any part of an expression that conveys complete propositions, such as a single phrase, can be documented using the more general property P148 has component (is component of). Any part of an expression that does not completely follow meaningful boundaries, such as lines or pages of text or portions visible on images, can be documented using the property P106 is composed of (forms part of), and not with R5 has component (is component of). Fragments, in particular, can be documented with the more specific property R15 has fragment (is fragment of). This property does not cover the relationship that exists between expressions that are realisations of different works, where one is re-used in a new, larger expression. Such a relationship is modelled by R75 incorporates (is incorporated in).
notation: R5
domain: Expression

exemplifies
type: ObjectProperty
range: Manifestation
comment: This property associates an instance of F3 Manifestation with an instance of F5 Item that is one of its exemplars or its only exemplar. Instances of F5 Item correspond to the kinds of physical unit(s) specified in the manifestation, regardless of possible later changes. Even though an item may exhibit defects with respect to the intended manifestation, it is still regarded to carry the manifestation, as long as it is produced or made accessible as a functional item by its creators.
notation: R7
domain: Item

combines
type: ObjectProperty
range: Nomen
comment: This property associates an instance of F12 Nomen with another instance of F12 Nomen where the string of the domain instance of F12 Nomen includes the complete symbolic content of the string of the range instance of F12 Nomen. This property is not transitive. It is asymmetric and irreflexive. Shortcut of: F12 Nomen (1). R33 has string: E62 String (1). P190i is symbolic content of: E90 Symbolic Object (1): P106 is composed of: E90 Symbolic Object (2). P190 has symbolic content: E62 String (2). R33i is string of: F12 Nomen (2)
notation: R8
domain: Nomen

is member of
type: ObjectProperty
range: Conceptual Object
comment: This property associates an instance of F1 Work with an instance of E28 Conceptual Object that represents a generalization of the work. The property can be used to group variant, alternative or related works that are considered to share a common concept. Whereas instances of F1 Work are always realised in instances of F2 Expression, there is no particular expression that fully conveys the instance of Conceptual Object that a work may be a member of. Intended usage of the property includes what is discussed as “superwork” in the library community. Typical examples are novels that can be grouped by fictional universes or common characters, paintings or graphical works that exist as a family of alternatives, musical compositions that are referred to as the same although they exist as particular versions that are each identified as an individual work. The instance of E28 Conceptual Object that has works as members will often be constructed for a specific purpose, such as bibliographic organization or retrieval.
notation: R10
domain: 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 instance of F18 Serial Work, such as sequencing pattern, expected frequency and expected regularity. Shortcut of: F18 Serial Work. R19i was realised through: F30 Manifestation Creation. P16 used specific object (was used for): E29 Design or Procedure
notation: R11
domain: Serial Work

has fragment
type: ObjectProperty
range: Symbolic Object
comment: This property associates an instance of E90 Symbolic Object with an instance of F2 Expression of which it is a fragment. The fragment is not itself an instance of F2 Expression as it does not express any instance of F1 Work. When the fragment consists of intelligible words it is an instance of E33 Linguistic Object.An instance of E90 Symbolic Object is only considered a fragment of an instance of F2 Expression when related to its occurrence in a known or assumed whole by the R15 has fragment (is fragment of) property. The size of an instance of E90 Symbolic Object ranges from more than 99% of an instance of F2 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 video, etc.).An instance of E90 Symbolic Object can become a fragment of an instance of F2 Expression through the deterioration over time of a carrier of the expression, such as when only fragments of a manuscript of an ancient text survive. Typically instances of E90 Symbolic Object that are of interest as fragments of expressions are formed deliberately, such as when excerpts are taken from a text by the compiler of a collection of excerpts, or citations from one expression are used in another text.
notation: R15
domain: Expression

created
type: ObjectProperty
range: Work
comment: This property associates the initial creation of a work and the instance of F1 Work that was created.
notation: R16
domain: Work Creation

created
type: ObjectProperty
range: Expression
comment: This property associates an instance of F2 Expression that was externalised during a particular instance of F28 Expression Creation event with that particular creation event. An instance of expression creation creates an instance of expression and also creates any expressions that are parts of that expression.
notation: R17
domain: Expression Creation

created a realisation of
type: ObjectProperty
range: Work
comment: This property associates an instance of F28 Expression Creation with the instance of F1 Work which was externalised in an instance of F2 Expression created by this creation event.
notation: R19
domain: Expression Creation

created
type: ObjectProperty
range: Manifestation
comment: This property associates the instance of F3 Manifestation that was created during a particular instance of F30 Manifestation Creation with that instance of F30 Manifestation Creation event.
notation: R24
domain: Manifestation Creation

materialized
type: ObjectProperty
range: Manifestation
comment: This property associates an instance of F32 Item Production Event with the set of signs provided by the publisher to be carried by all of the produced items (i.e., the instances of F5 Item) and any other physical features foreseen as integral to the instance of F3 Manifestation that is materialised.
notation: R27
domain: Item Production Event

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

reproduced object
type: ObjectProperty
range: Item
comment: This property associates an instance of F33 Reproduction Event with an instance of F5 Item it reproduces.
notation: R29
domain: Reproduction Event

reproduced publication
type: ObjectProperty
range: Manifestation
comment: This property associates an instance of F33 Reproduction Event with an instance of F3 Manifestation it reproduces.
notation: R30
domain: Reproduction Event

has string
type: ObjectProperty
range: String
comment: This property associates an instance of F12 Nomen with a sign or arrangement of signs that is used to refer to something through that instance of F12 Nomen.
notation: R33
domain: Nomen

is specified by
type: ObjectProperty
range: Expression
comment: This property associates an instance of F12 Nomen with an instance of F2 Expression which documents, defines or provides evidence for the particular nomen in the stated sense.
notation: R35
domain: Nomen

uses script conversion
type: ObjectProperty
range: Script Conversion
comment: This property associates an instance of F12 Nomen with an instance of F36 Script Conversion that is used to create the E62 String used in that instance of F12 Nomen from the string used in another instance of F12 Nomen that co-refers with the first nomen (the instances of F12 Nomen are related via the R56 has related form (is related form of) property). The source of this conversion may or may not be explicitly mentioned. Shortcut of:F12 Nomen. R17i was created by (created): E65 Creation. P33 used specific technique (was used by): E29 Design or Procedure
notation: R36
domain: Nomen

has language
type: ObjectProperty
range: Language
comment: This property associates an instance of F12 Nomen with an instance of E56 Language which is the language used for or associated with the nomen.
notation: R54
domain: Nomen

has related form
type: ObjectProperty
range: Nomen
comment: This property associates an instance of F12 Nomen with another instance of F12 Nomen which co-refers to the same instance of E1 CRM Entity. This property is not transitive. It is symmetric and irreflexive. The property R56.1 has type allows for specifying the particular kind of relationship that holds between the domain nomen and the range nomen, such as by being a derivation, an alternative, a lexical variant, etc. Typing the association may cause loss of symmetry. Shortcut of:E89 Propositional Object (1). P67 refers to: E1 CRM Entity. P67i is referred to by: E89 Propositional Object (2)
notation: R56
domain: Nomen

has part
type: ObjectProperty
range: Work
comment: This property associates an instance of F1 Work with another instance of F1 Work that forms part of it in a complementary role to other sibling parts, conceived at some point in time to form together a logical whole, such as the parts of a trilogy. This property is transitive, asymmetric and irreflexive.
notation: R67
domain: Work

is inspired by
type: ObjectProperty
range: Work
comment: This property associates an instance of F1 Work with another instance of F1 Work whose content was inspired by that instance of F1 Work. The content of the range work instance served in some way as a source of ideas for the domain work instance. Neither instance of F1 Work may be a part of the other. This property is not transitive. It is irreflexive. Shortcut of: F1 Work (2). R16i was created by: F27 Work Creation. P15 was influenced by: F1 Work (1)
notation: R68
domain: Work

has physical form
type: ObjectProperty
range: Type
comment: This property associates an instance of F3 Manifestation with an instance of E55 Type describing the kind of physical form that characterizes instances of F5 Item carrying this F3 Manifestation.In the case of instances of manifestations intended to be rendered by mediation (such as with electronic devices), the form also indicates the kind of equipment and software tools necessary.
notation: R69
domain: Manifestation

has dimension
type: ObjectProperty
range: Dimension
comment: This property associates an instance of F3 Manifestation with an instance of E54 Dimension that describes aspects of its symbolic content, such as word counts, or describes the kind of physical form that characterizes instances of F5 Item carrying this F3 Manifestation, such as number of pages. This inference is an induction along the path that can be modelled as: F3 Manifestation. R7i is exemplified by: F5 Item. P43 has dimension (is dimension of): E54 Dimension. It can happen that a given item, or subset of items, originally produced, or intended to be produced, with a certain value for a particular kind of dimension, has a different value for this kind of dimension by accident. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation.
notation: R70
domain: Manifestation

has part
type: ObjectProperty
range: Manifestation
comment: This property associates an instance of F3 Manifestation with a structural part of it that is itself an instance of F3 Manifestation. This property is transitive, asymmetric and irreflexive.
notation: R71
domain: Manifestation

takes representative attribute from
type: ObjectProperty
range: Expression
comment: This property associates an instance of F1 Work with instances of F2 Expression that bear attributes which are used to characterize the work. The instance of F2 Expression in question must be one that realizes that instance of F1 Work. An instance of F2 Expression may or may not serve as source of representative expression attributes for its associated instance of F1 Work. If it does, it may provide one attribute or many. Only one or more than one of the instances of F2 Expression associated with an instance of F1 Work may provide attributes that characterize that instance of F1 Work. The representative expression attributes can all come from the same expression or from more than one expressions.
notation: R73
domain: Work

uses expression of
type: ObjectProperty
range: Work
comment: This property associates an instance of F1 Work with another instance of F1 Work where all expressions of the former will include some expression of the latter. This property is not transitive. It is irreflexive. This property represents the generalized relationship between works that is described at the expression level using R75 incorporates (is incorporated in).
notation: R74
domain: Work

incorporates
type: ObjectProperty
range: Expression
comment: This property associates an instance of F2 Expression with an instance of F2 Expression that is an integral part of the first, but where the latter realises a different instance of F1 Work from the first. This property is transitive, asymmetric and irreflexive.
notation: R75
domain: Expression

is derivative of
type: ObjectProperty
range: Expression
comment: This property associates an instance of F2 Expression with another instance of F2 Expression which was its source or one of its sources. This property is not transitive. It is asymmetric and irreflexive. This property is also a shortcut of the fully developed path: F2 Expression (1). P16i was used for: F28 Expression Creation. R17 created: F2 Expression (2). The property R76.1 has type of this property allows for specifying the kind of derivation, such as translation, revision, etc.
notation: R76
domain: Expression

accompanies or complements
type: ObjectProperty
range: Work
comment: This property associates one instance of F1 Work with another instance of F1 Work which is intended to accompany it or to function as a complement for it. This property is neither transitive nor intransitive. It is generally not symmetric and it is irreflexive. In many but not all cases, one of the instances of F1 Work is primary and can be used without the other work, while the other is secondary and depends on the first work (such as a work that is a concordance for another work). In some cases a work may have been created to accompany or complement a specific expression of another work. The link to the source expression can be indicated using the property P16 used specific object (was used for) using the path: F1 Work(1). R3 is realised in: F2 Expression(1). P16i was used for: F27 Work Creation. R16 created: F1 Work(2). Shortcut of: F1 Work. P19i was made for: E7 Activity. P19 was intended use of: F1 Work
notation: R77
domain: Work

has alternate
type: ObjectProperty
range: Manifestation
comment: This property associates one instance of F3 Manifestation with another instance of F3 Manifestation that exemplifies the same instance of F2 Expression, when the two instances of F3 Manifestation can be used as alternatives for each other in particular use cases. This property is transitive and symmetric. It is irreflexive.The alternative manifestations may be in the same physical form, for example, simultaneous publications in different markets. More frequently, the alternative relationship is established when the alternative manifestations are in different physical forms, designed to enable use of the same content with different playback equipment (such as a DVD and Blu-ray disc version of the same videorecording).
notation: R78
domain: Manifestation

has representative expression attribute
type: ObjectProperty
range: Type
comment: This property associates an instance of F1 Work with an instance of E55 Type that describes a category of attribute that is considered essential in characterizing instances of F1 Work. The types of interest will vary depending on the kind of work. The value of the attribute is considered representative of the instance of F1 Work. It is normally inferred from the values attributed to instances of F2 Expression that realize the work and that are considered canonical or best representative of the work. The values may also be assigned from characteristics abstracted from a more or less nebulous network of similar expressions. There is no requirement to precisely identify one or more expressions which serve as sources for the values of the types serving as representative expression attributes; however, if this is known, an instance of F2 Expression considered representative of an F1 Work may be related to the instance of F1 Work using the R73 takes representative attribute from (bears representative attribute for) property.
notation: R79
domain: Work

performed
type: ObjectProperty
range: Work
comment: This property associates an instance of F31 Performance with an instance of F1 Work. The property is used to express the association between an instance of F31 Performance and the instance of F1 Work it conveys.
notation: R80
domain: Performance

recorded
type: ObjectProperty
range: Performance
comment: This property associates an instance of F28 Expression Creation with an instance of F31 Performance that it records.This property allows for the documentation of the association that exists between the outcome of an instance of F28 Expression Creation such as a performance recording, and the instance of F31 Performance that it is a recording of. For documenting performances that are more integral and planned parts of an expression creation (such as the recording of a performance solely done for the purpose of audio or video productions), the use of the property P9 consist of (forms part of) is more specific (and appropriate).
notation: R81
domain: Expression Creation

used writing system
type: ObjectProperty
range: Writing System
comment: This property identifies the specific instance of TX3 Writing System employed during the writing event (TX2) that led to the creation of a written text (TX1).
notation: TXP1
domain: Writing

includes
type: ObjectProperty
range: Written Text
comment: This property describes the relation existing between a TX1 Written Text and the TX4 Writing Field, specifically created to accommodate the text, within which it is inscribed. This relation becomes quite relevant in the very frequent case where more than a single text is found on different areas of a specific support.
notation: TXP2
domain: Writing Field

has segment
type: ObjectProperty
range: Written Text Segment
comment: This property is intended to correlate a text and the different parts of it which a scholar can identify, such as: letters, words, lines, columns, pages, or any other scan that can be made by scholars because it is considered to have a particular relevance for the investigation of the text itself.
notation: TXP4
domain: Written Text

wrote
type: ObjectProperty
range: Written Text
comment: This property is used to describe in detail the close relationship between a text and the writing event that led to its production.
notation: TXP5
domain: Writing

encodes
type: ObjectProperty
range: Language
comment: This property is used to indicate the language encoded by the TX3 Writing System and used for writing, reading or rendering (i.e. transcribing) a TX1 Written Text.
notation: TXP6
domain: Writing System

has item
type: ObjectProperty
range: Grapheme
comment: This property associates an instance of TX13 Script with an instance of TX8 Grapheme employed by this script. Different instances of TX13 Script may have some graphemes in common.
notation: TXP7
domain: Script

has component
type: ObjectProperty
range: Glyph
comment: This property is used to state the (physical) belonging of a glyph to a given TX1 Written Text.
notation: TXP8
domain: Written Text

is encoded using
type: ObjectProperty
range: Writing System
comment: This property has the purpose of directly associating a TX1 Written Text with the TX3 Writing System used for encoding it. It is a shortcut of the more fully articulated path from TX1 Written Text through TXP5i was written by, TX2 Writing, TXP1 used writing system to TX3 Writing System.
notation: TXP9
domain: Written Text

deciphered text
type: ObjectProperty
range: Physical Human-Made Thing
comment: This property associates an instance of TX5 Text Recognition with an instance of E24 Physical Human-Made Thing carrying a glyph or a sequence of glyphs that was recognized in the respective activity of text recognition. Typically, the associated instance of E24 Physical Human-Made Thing is more specifically an instance of TX1 Written Text, however, a text may also be recognized from a mechanical copy, a photograph, squeeze or other form of material copy of a written original, which would not by itself constitute an instance of TX1 Written Text. In the latter case, the material copy should be associated with the original written text using the property ‘P130 shows features’.If the text was actually recognized only from a digital representation, this property should not be used, rather the property TXP13 deciphered via the representation should be used instead.
notation: TXP10
domain: Text Recognition

transcribed
type: ObjectProperty
range: Grapheme Sequence
comment: This property describes the relation between an activity of TX6 Transliteration and the identified sequence of graphemes (TX12) represented in an instance of TX1 Written Text.
notation: TXP11
domain: Transliteration

has style
type: ObjectProperty
range: Style
comment: This property describes information about the style used for the realization of the written text (TX1). The property TXP12.1 has type allows the nature of the style to be specified, for example to record the direction, orientation or the linear system of the text.
notation: TXP12
domain: Written Text

deciphered via the representation
type: ObjectProperty
range: Visual Item
comment: This property associates an instance of TX5 Text Recognition with an instance of E36 Visual Item, capturing the optical impression of an instance of TX1 Written Text by some mechanical method, that was used for recognizing the text without access to the original text and without an explicitly documented material copy or electronic display device that was used for the process.If the text was actually recognized from an autoptic recognition or from a material reproduction, this property may not be used but the property “TXP10 deciphered text (was deciphered by)” should be used instead.This property should also not be used, if the recognition of the text was actually carried out from the original text or a material copy of it together with an auxiliary instance of E36 Visual Item. In this case, the use of the auxiliary material should be documented with the more general property P16 used specific object.
notation: TXP13
domain: Text Recognition

used copy or representation of
type: ObjectProperty
range: Written Text
comment: This property associates an instance of TX5 Text Recognition, carried out only via copies or representations of a text, with the original instance of TX1 Written Text that was represented on the used copies or digital surrogates.This property is to be used only for non-autoptic recognition. If this particular recognition of the text was actually carried out from the original text, the property TXP10 deciphered text should be used for associating the instance of TX5 Text Recognition with the original instance of TX1 Written Text.If some form of material copy of the written text was used for the text recognition, then this material copy should be associated with the original written text using the property ‘P130 shows features of’.
notation: TXP14
domain: Text Recognition

recorded correspondence
type: ObjectProperty
range: Grapheme Sequence
comment: This property associates an instance of TX5 Text Recognition with an instance of TX12 Grapheme Sequence that was created by this activity of text recognition for recording and representing as faithfully as possible the exact value of each sign on the physical material of the recognized instance of TX1 Written Text.
notation: TXP15
domain: Text Recognition

employs script
type: ObjectProperty
range: Script
comment: This property associates an instance of TX3 Writing System with one of the instances of the script (TX13) it employs.
notation: TXP16
domain: Writing System

has part
type: ObjectProperty
range: Grapheme Sequence
comment: This property associates an instance of TX12 Grapheme Sequence with another instance of TX12 Grapheme Sequence appearing at a particular position of the sequence. The property can be also used by an instance of TX11 Grapheme Occurrence (subclass of TX12 Grapheme Sequence) for denoting that a grapheme occurrence has part another grapheme occurrence. Note that a grapheme occurrence may be a symbolic composite containing another grapheme occurrence, such as the minute character “e” on top of the character “u” in former German writing systems denoting the symbol for “ü”.
notation: TXP17
domain: Grapheme Sequence

read
type: ObjectProperty
range: Written Text
comment: This property associates an instance of TX14 Reading with an instance of TX1 Written Text whose linguistic meaning was interpreted/understood through the reading process. It is a shortcut of the fully developed path from TX14 Reading through P9 consists of, TX5 Text Recognition, TXP10 deciphered text, to TX1 Written Text.
notation: TXP18
domain: Reading

has intentional subject
type: ObjectProperty
range: CRM Entity
comment: This property is used to connect an instance of institutional fact to an entity with which it is concerned. The intentional subject indicated by this property is the object about which the institutional fact holds for the group committed to this institutional reality.
notation: ZP1
domain: Institutional Fact

ascribes intentional target
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate the entity which an instance of institutional fact ascribes to its subject. The intentional target indicated by this property is the object which the institutional fact establishes as holding of its subject for the group committed to this institutional reality. The manner of its holding is indicated by the intentional relation.
notation: ZP2
domain: Institutional Fact

ascribes intentional relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the relationship which an instance of institutional fact takes to hold between its subject and its object. The intentional relation indicated by this property is the kind of relationship which the institutional fact establishes as holding between them for the group committed to this institutional reality.
notation: ZP3
domain: Institutional Fact

holds for
type: ObjectProperty
range: Group
comment: This property is used to indicate the community or group for whom an instance of institutional fact holds. Institutional facts have identity only relative to some group for whom they have a significance as formulated through a chosen symbolic system.
notation: ZP4
domain: Institutional Fact

has appellative subject
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate the entity for which an appellation holds as institutional fact.
notation: ZP5
domain: Appellative Status

ascribes appellation
type: ObjectProperty
range: Appellation
comment: This property is used to indicate the appellation which is indicated as holding for the named subject of the appellative status.
notation: ZP6
domain: Appellative Status

ascribes appellative relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the appellation which is indicated as holding for the named subject of the appellative status pertains to this subject.
notation: ZP7
domain: Appellative Status

has contact point subject
type: ObjectProperty
range: Actor
comment: This property is used to indicate the entity for which a contact point has been specified as means of contact.
notation: ZP8
domain: Contact Point Status

ascribes contact point
type: ObjectProperty
range: Identifier
comment: This property is used to indicate the contact point which is indicated as holding for the named subject of the contact status.
notation: ZP9
domain: Contact Point Status

ascribes contact point relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the contact point which is indicated as holding for the named subject of the contact status pertains to this subject.
notation: ZP10
domain: Contact Point Status

has classificatory subject
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate the entity for which a certain classification is taken to hold by the instance of classificatory status.
notation: ZP11
domain: Classificatory Status

ascribes classification
type: ObjectProperty
range: Type
comment: This property is used to indicate the type which is indicated as holding for the subject of the classification status.
notation: ZP12
domain: Classificatory Status

ascribes classification relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the type which is indicated as holding for the subject of the classification status pertains to this subject.
notation: ZP13
domain: Classificatory Status

has functional subject
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate the entity for which a certain functional classification is taken to hold by the instance of functional status.
notation: ZP14
domain: Function Status

ascribes function
type: ObjectProperty
range: Type
comment: This property is used to indicate the type of function which is indicated as holding for the subject of the function status.
notation: ZP15
domain: Function Status

ascribes functional relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the function which is indicated as holding for the subject of the function status pertains to this subject.
notation: ZP16
domain: Function Status

has social status subject
type: ObjectProperty
range: Actor
comment: This property is used to indicate the actor for which a certain social status is taken to hold by the instance of social status.
notation: ZP17
domain: Social Status

ascribes social status
type: ObjectProperty
range: Type
comment: This property is used to indicate the type of social status which is indicated as holding for the subject of the social status ascription.
notation: ZP18
domain: Social Status

ascribes social status relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the type of social status which is indicated as holding for the subject pertains to this subject.
notation: ZP19
domain: Social Status

has custodial subject
type: ObjectProperty
range: Physical Thing
comment: This property is used to indicate the physical thing over which a certain custodial status is taken to hold.
notation: ZP20
domain: Custodial Status

ascribes custodian
type: ObjectProperty
range: Actor
comment: This property is used to indicate the custodian to whom the custody of the physical thing which is the subject of the custodial status redounds.
notation: ZP21
domain: Custodial Status

ascribes custodial relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the custodial status which is indicated as holding over the legal object by the custodian pertains to this subject.
notation: ZP22
domain: Custodial Status

has ownership subject
type: ObjectProperty
range: Physical Thing
comment: This property is used to indicate the legal object over which a certain ownership status is taken to hold.
notation: ZP23
domain: Ownership Status

ascribes owner
type: ObjectProperty
range: Actor
comment: This property is used to indicate the owner to whom the title of the legal object which is the subject of the ownership status redounds.
notation: ZP24
domain: Ownership Status

ascribes ownership relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the ownership status which is indicated as holding over the legal object by the owner pertains to this subject.
notation: ZP25
domain: Ownership Status

has residence subject
type: ObjectProperty
range: Actor
comment: This property is used to indicate the actor for whom the residence status is taken to hold.
notation: ZP26
domain: Residential Status

ascribes residence place
type: ObjectProperty
range: Place
comment: This property is used to indicate the place at which the subject of the residence status is taken to reside or dwell.
notation: ZP27
domain: Residential Status

ascribes residence relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the residence status which is indicated as holding over the actor pertains to this subject.
notation: ZP28
domain: Residential Status

has familial subject
type: ObjectProperty
range: Person
comment: This property is used to indicate the person for whom the family status is taken to hold.
notation: ZP29
domain: Family Status

ascribes relative
type: ObjectProperty
range: Person
comment: This property is used to indicate the person with whom the subject of the family relation status has the familial relation which they have.
notation: ZP30
domain: Family Status

ascribes familial relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of family status which is indicated as holding between the subject individual and his/her ascribed relative.
notation: ZP31
domain: Family Status

has membership subject
type: ObjectProperty
range: Actor
comment: This property is used to indicate the person or group for whom the membership status is taken to hold.
notation: ZP32
domain: Membership Status

ascribes group
type: ObjectProperty
range: Group
comment: This property is used to indicate the group ascribed to the subject person of the membership status as having a membership relation thereto.
notation: ZP33
domain: Membership Status

ascribes membership relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of membership status which is indicated as holding between the subject actor and the group to which it is ascribed as being a member.
notation: ZP34
domain: Membership Status

has referential subject
type: ObjectProperty
range: Propositional Object
comment: This property is used to indicate the propositional object for which the referential status is taken to hold.
notation: ZP35
domain: Referential Status

ascribes referent
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate the referent to which the subject propositional object is taken to refer.
notation: ZP36
domain: Referential Status

ascribes referential relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of referential status which is indicated as holding between the subject propositional object and its indicated intended referent.
notation: ZP37
domain: Referential Status

ascribes referential mode
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the referential status which is indicated as holding between the subject propositional object and its indicated intended referent holds.
notation: ZP38
domain: Referential Status

performed
type: ObjectProperty
range: Design or Procedure
comment: This property is used to indicate the performance plan sanctioned by normative rule appealed to by a symbolic act in order to bring out the specific intended communicative effect. At a general level, the performance plan is what is appealed to in order to carry out the symbolic act in the first place. For example, an act of defiance may call on a specific sequence of gestures to be instantiated. The case of speech act (ZE13) is a special case of symbolic act where the performance plan indicates the series of necessary procedures that must be followed in order for the speech act to have been successfully carried out and to have created a genuine instance of the institutional fact that it was designed to make possible.
notation: ZP40
domain: Symbolic Act

uttered
type: ObjectProperty
range: Information Object
comment: It is typical of performance plans for normative procedures to include a necessary invoking clause or set of clauses which must be uttered in the course of the performance of the speech act in order to for it to be successfully carried out. This property enables the documentation of the use of such a linguistic object.
notation: ZP41
domain: Speech Act

intentionally initiated
type: ObjectProperty
range: Institutional Fact
comment: This property is used to connect an instance of transformative symbolic act to the instance of institutional fact which it brought into existence through the successful performance of a specified norm type conformant symbolic act.
notation: ZP42
domain: Transformative Symbolic Act

has similarity subject
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate one of two entities for which the similarity status is taken to hold.
notation: ZP43
domain: Similarity Status

ascribes similarity target
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate the other entity for which the similarity status is taken to hold.
notation: ZP44
domain: Similarity Status

ascribes similarity relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of similarity which is indicated as holding between the two entities indicated in the similarity status.
notation: ZP45
domain: Similarity Status

ascribes similarity mode
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the similarity status, which is indicated as holding between the two entities indicated in the similarity status, is the case. It''s function corresponds with the .1 properties in CIDOC-CRM 7.1.1.
notation: ZP46
domain: Similarity Status

has set belonging subject
type: ObjectProperty
range: CRM Entity
comment: This property is used to indicate an entity which is taken as belonging to a particular set by the instance of set status.
notation: ZP47
domain: Set Status

ascribes set
type: ObjectProperty
range: Notional Set
comment: This property is used to indicate the set to which an entity is indicated as belonging .
notation: ZP48
domain: Set Status

ascribes set belonging relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of belonging to the set which is indicated as holding between the subject entity and the target set.
notation: ZP49
domain: Set Status

has former or current set member
type: ObjectProperty
range: CRM Entity
comment: This property is used to connect an instance of set to an entity considered to be one of its members.
notation: ZP51
domain: Notional Set

intentionally terminated
type: ObjectProperty
range: Institutional Fact
comment: This property is used to connect an instance of transformative symbolic act to the instance of institutional fact which it cancels through the successful performance of a specified norm type conformant symbolic act.
notation: ZP52
domain: Transformative Symbolic Act

ascribes relative date
type: ObjectProperty
range: Period
comment: This property is used to connect the instance of dating status to the instance of a period to which another instance of period is related for the purposes of datation.
notation: ZP54
domain: Dating Status

has dating subject
type: ObjectProperty
range: Period
comment: This property is used to connect the instance of dating status to an instance of a period typically associated with the existence or use of a physical thing or an object which is the ultimate object of inquiry.
notation: ZP55
domain: Dating Status

ascribes dating relation
type: ObjectProperty
range: Type
comment: This property is used to assign the type of relationship the dated period of the object under investigation bears towards the period assigned to it as its datation.
notation: ZP56
domain: Dating Status

has obligation subject
type: ObjectProperty
range: Dimension
comment: This property is used to indicate a dimension which represents an amount of debt owed from one party to another within an instance of formal obligation.
notation: ZP57
domain: Obligation Status

ascribes debtor
type: ObjectProperty
range: Actor
comment: This property is used to indicate an actor whom is bound by an obligation which it is their duty to repay.
notation: ZP58
domain: Obligation Status

ascribes obligation relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of obligation relation that holds between the debtor and the obligation.
notation: ZP59
domain: Obligation Status

ascribes debtee
type: ObjectProperty
range: Actor
comment: This property is used to indicate the actor to whom an obligation is owed in the context of an obligation.
notation: ZP60
domain: Obligation Status

transferred property right to
type: ObjectProperty
range: Actor
comment: This property is used to indicate the receiver of a property right from another party within the context of a transfer of property right.
notation: ZP61
domain: Transfer of Property Right

transferred property right from
type: ObjectProperty
range: Actor
comment: This property is used to indicate the party ceding property right to another party within the context of a transfer of property right.
notation: ZP62
domain: Transfer of Property Right

transferred property right over
type: ObjectProperty
range: Legal Object
comment: This property is used to indicate the legal object over which property right has been transfered from one party to another.
notation: ZP63
domain: Transfer of Property Right

has property right subject
type: ObjectProperty
range: Legal Object
comment: This property is used to indicate an object that is subject to a property right of some actor.
notation: ZP64
domain: Property Right Status

ascribes property right holder
type: ObjectProperty
range: Actor
comment: This property is used to indicate an actor who holds a right over a legal object within the context of a property right status.
notation: ZP65
domain: Property Right Status

ascribes property right relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of property right relation that is held over the legal object by the actor in the context of a property right status.
notation: ZP66
domain: Property Right Status

generated obligation upon
type: ObjectProperty
range: Actor
comment: This property is used to indicate the party who owes another party within the the context of a declaration of obligation.
notation: ZP67
domain: Declaration of Obligation

generated obligation to
type: ObjectProperty
range: Actor
comment: This property is used to indicate the party who is owed by another party within the the context of a declaration of obligation.
notation: ZP68
domain: Declaration of Obligation

generated obligation of
type: ObjectProperty
range: Dimension
comment: This property is used to indicate the specific amount owed by one party to another within the context of a declaration of obligation.
notation: ZP69
domain: Declaration of Obligation

ascribes social status in relation to
type: ObjectProperty
range: Actor
comment: This property is used to indicate a third party actor for whom another''s social status holds relevance (in the form of rights and/or responsibilities that are thus due to them) in the instance of social status.
notation: ZP70
domain: Social Status

applies for context
type: ObjectProperty
range: Event
comment: This property is used to indicate an event context which limits the temporal scope within which an instance of institutional fact is meant to hold. When indicated the event context stands as the frame in which the institutional fact is held to be valid by the associated group for whom it has significance.
notation: ZP75
domain: Institutional Fact

applies for context type
type: ObjectProperty
range: Type
comment: This property is used to indicate an event context type which limits the spatio-temporal scope within which an instance of institutional fact is meant to hold to certain kinds of event. When indicated the event context type stands as the frame or frames in which the institutional fact is held to be valid by the associated group for whom it has significance.
notation: ZP76
domain: Institutional Fact

ascribes place
type: ObjectProperty
range: Place
comment: This property is used to indicate the place in a locative association that is taken to hold for an entity.
notation: ZP77
domain: Locative Status

had constituent
type: ObjectProperty
range: Persons
comment: This property relates an instance of population to an instance of persons, individual or collective, to which it belongs qua constituent.
notation: ZP78
domain: Population

had population
type: ObjectProperty
range: Population
comment: This property relates an instance of population existence to the population whose existence it was.
notation: ZP79
domain: Population Existence

has physical locative subject
type: ObjectProperty
range: Physical Thing
comment: This property is used to designate the instance of physical object whose socially defined location the instance of physical locative status delineates.
notation: ZP83
domain: Physical Locative Status

ascribes location relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the physical locative status which is indicated as holding over the physical object pertains to this subject.
notation: ZP84
domain: Physical Locative Status

has topographical subject
type: ObjectProperty
range: Place
comment: This property is used to designate the instance of place whose socially defined location the instance of topographical status delineates.
notation: ZP85
domain: Topographical Status

ascribes promisee
type: ObjectProperty
range: Persons
comment: This property is used to indicate the actor to whom a promise has been offered in an intentional promise.
notation: ZP86
domain: Promissory Status

ascribes promisor
type: ObjectProperty
range: Actor
comment: This property is used to indicate an actor who is bound by a promise which it is their duty to fulfil.
notation: ZP87
domain: Promissory Status

ascribes topographical relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the topographical status which is indicated as holding between two places.
notation: ZP88
domain: Topographical Status

has promissory subject
type: ObjectProperty
range: Plan
comment: This property is used to indicate an instance of formulation which represents the promise given from one party to another within an instance of an intentional promise.
notation: ZP89
domain: Promissory Status

ascribes promissory relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of promise relation that holds between the promisor and the promisee.
notation: ZP90
domain: Promissory Status

generated promise of
type: ObjectProperty
range: Plan
comment: This property associates an instance of promissory agreement to the plan for a futural event (the realized promise) that it generates and which is promised through it.
notation: ZP91
domain: Promissory Agreement Event

has text sequence subject
type: ObjectProperty
range: Writing Field
comment: This property is used to indicate the text field which has been ascribed a sequential location in relation to another text field.
notation: ZP93
domain: Text Sequence Status

ascribes text sequence correlate
type: ObjectProperty
range: Writing Field
comment: This property is used to designate a text field to which another text field has been assigned in order to designate its relative place.
notation: ZP94
domain: Text Sequence Status

ascribes text sequence relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the text sequence status which is indicated as holding over the textual sequence pertains to this subject.
notation: ZP95
domain: Text Sequence Status

has authority status subject
type: ObjectProperty
range: Actor
comment: This property is used to indicate the actor which has been ascribed an authority status.
notation: ZP96
domain: Authority Status

ascribes authority status
type: ObjectProperty
range: Type
comment: This property is used to indicate the type of authority ascribed to the actor by the authority status.
notation: ZP97
domain: Authority Status

challenged
type: ObjectProperty
range: Institutional Fact
comment: This property links an instance of symbolic act with an instance of institutional fact which it challenges through its performance.
notation: ZP100
domain: Symbolic Act

affirmed
type: ObjectProperty
range: Institutional Fact
comment: This property links an instance of symbolic act with an instance of institutional fact which it affirms through its performance.
notation: ZP101
domain: Symbolic Act

ascribes social relation target
type: ObjectProperty
range: Actor
comment: This property is used to indicate the person with whom the subject of the social relation status has the social relation which they have.
notation: ZP103
domain: Social Relation Status

ascribes social relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of social relation status which is indicated as holding between the subject individual and their ascribed social relative.
notation: ZP104
domain: Social Relation Status

has social relation subject
type: ObjectProperty
range: Actor
comment: This property is used to indicate the person for whom the social relation status is taken to hold.
notation: ZP105
domain: Social Relation Status

initiated
type: ObjectProperty
range: Institutional Fact
comment: This property is used to connect the instance of event to the instance of institutional fact which it brought into existence by fiat thanks to its accordance to a socially defined norm. In this case the bringing about of a new institutional fact need not be intentional or following any particular rule intentionally. Rather, within a social context it is recognized that the very fact of a particular event occurring is causal to the initiation of the related social fact. For example, in certain property right laws, the very fact of writing down an idea (E65 Creation) initiates an instance of property right over the generated information object, regardless of the intention or not of the author to so create such a right.
notation: ZP111
domain: Event

terminated
type: ObjectProperty
range: Institutional Fact
comment: This property is used to connect the instance of event to the instance of institutional fact which it terminated the existence of by fiat thanks to its accordance to a socially defined norm. In this case the cancellation of an institutional fact need not be intentional or following any particular rule intentionally. Rather, within a social context it is recognized that the very fact of a particular event occurring is causal to the cancellation of the related social fact. For example, a certain social system may recognize that an ''act of god'' such as an earthquake may terminate the property right of an individual over some object (another social system may not, however).
notation: ZP112
domain: Event

has successor status
type: ObjectProperty
range: Institutional Fact
comment: This property links one instance of institutional fact with another where the latter succeeds the former as a formal continuation.
notation: ZP113
domain: Institutional Fact

has geographic scope
type: ObjectProperty
range: Place
comment: This property is used to connect an institutional fact to a place, which defines the scope of that facts spatial validity.
notation: ZP114
domain: Institutional Fact

holds over
type: ObjectProperty
range: Population
comment: This property associates and instance of institutional fact to an instance of population over which this fact holds. As opposed to the property of ZP4 holding for, the effect which this institutional fact holds in relation to the related population is not necessarily one which has been directly intended. The population undergoes the social fact instantiated, rather than causing it to occur directly through agency in a speech act or transformative act. The population is the patient of this operation, not its agent.
notation: ZP115
domain: Institutional Fact

ascribes authority status relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific manner in which the type of authority status which is indicated as holding for the subject pertains to this subject.
notation: ZP116
domain: Authority Status

generated promise to
type: ObjectProperty
range: Persons
comment: This property is used to indicate the persons to whom a promise is made, when two parties reach a promissory agreement.
notation: ZP117
domain: Promissory Agreement Event

generated promise upon
type: ObjectProperty
range: Actor
comment: This property is used to indicate the actor upon whom an obligation is generated when two parties reach a promissory agreement.
notation: ZP118
domain: Promissory Agreement Event

ascribes event location relation
type: ObjectProperty
range: Type
comment: This property is used to indicate the specific type of event locative status which is indicated as holding between the subject event and its ascribed place.
notation: ZP119
domain: Evental Locative Status

has event location subject
type: ObjectProperty
range: Event
comment: This property is used to indicate the event which has been ascribed a place.
notation: ZP120
domain: Evental Locative Status

involved
type: ObjectProperty
range: Persons
comment: This property describes the passive involvement of instances of ZE39 Persons in an instance of E5 Event.
notation: ZP121
domain: Event