ecrm_240920.owl

<?xml version='1.0' encoding='UTF-8'?>
<rdf:RDF xmlns:ecrm="http://erlangen-crm.org/240920/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xml:lang="en" xml:base="http://erlangen-crm.org/240920/">
  <owl:Ontology rdf:about="">
    <rdfs:label xml:lang="en">Erlangen CRM / OWL</rdfs:label>
    <owl:versionInfo xml:lang="en">ECRM 240920 / CIDOC-CRM 7.1.3</owl:versionInfo>
    <rdfs:comment xml:lang="en">Erlangen CRM / OWL - An OWL DL 1.0 implementation of the CIDOC Conceptual Reference Model, based on: Nick Crofts, Martin Doerr, Tony Gill, Stephen Stead, Matthew Stiff (eds.): Definition of the CIDOC Conceptual Reference Model (http://cidoc-crm.org/).
This implementation has been originally created by Bernhard Schiemann, Martin Oischinger and Günther Görz at the Friedrich-Alexander-University of Erlangen-Nuremberg, Department of Computer Science, Chair of Computer Science 8 (Artificial Intelligence) in cooperation with the Department of Museum Informatics of the Germanisches Nationalmuseum Nuremberg and the Department of Biodiversity Informatics of the Zoologisches Forschungsmuseum Alexander Koenig Bonn.
The Erlangen CRM / OWL implementation of the CIDOC Conceptual Reference Model is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.</rdfs:comment>
    <rdfs:comment xml:lang="en">Changelog: https://github.com/erlangen-crm/ecrm/commits/master</rdfs:comment>
  </owl:Ontology>
  <owl:Class rdf:about="E1_CRM_Entity">
    <rdfs:label xml:lang="en">E1 CRM Entity</rdfs:label>
    <rdfs:label xml:lang="de">E1 CRM Entität</rdfs:label>
    <rdfs:label xml:lang="el">E1 Οντότητα CIDOC CRM</rdfs:label>
    <rdfs:label xml:lang="fr">E1 Entité CRM</rdfs:label>
    <rdfs:label xml:lang="pt">E1 Entidade CRM</rdfs:label>
    <rdfs:label xml:lang="ru">E1 CRM Сущность</rdfs:label>
    <rdfs:label xml:lang="zh">E1 CRM实体</rdfs:label>
    <skos:notation>E1</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P48_has_preferred_identifier"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. 
It is an abstract concept providing for three general properties:
- Identification by name or appellation, and in particular by a preferred identifier
- Classification by type, allowing further refinement of the specific subclass to which an instance belongs 
- Attachment of free text and other unstructured data for the expression of anything not captured by formal properties
All other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity.

Examples:
- the earthquake in Lisbon 1755 (E5) (Chester, 2001)

In First Order Logic:
- E1(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
  </owl:Class>
  <owl:Class rdf:about="E2_Temporal_Entity">
    <rdfs:label xml:lang="en">E2 Temporal Entity</rdfs:label>
    <rdfs:label xml:lang="de">E2 Geschehendes</rdfs:label>
    <rdfs:label xml:lang="el">E2 Έγχρονη Οντότητα</rdfs:label>
    <rdfs:label xml:lang="fr">E2 Entité temporelle</rdfs:label>
    <rdfs:label xml:lang="pt">E2 Entidade Temporal</rdfs:label>
    <rdfs:label xml:lang="ru">E2 Врeмeнная Сущность</rdfs:label>
    <rdfs:label xml:lang="zh">E2 时序实体</rdfs:label>
    <skos:notation>E2</skos:notation>
    <rdfs:subClassOf rdf:resource="E1_CRM_Entity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P4_has_time-span"/>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <owl:disjointWith rdf:resource="E77_Persistent_Item"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises all phenomena, such as the instances of E4 Periods and E5 Events, which happen over a limited extent in time. This extent in time must be contiguous, i.e., without gaps. In case the defining kinds of phenomena for an instance of E2 Temporal Entity cease to happen, and occur later again at another time, we regard that the former instance of E2 Temporal Entity has ended and a new instance has come into existence. In more intuitive terms, the same event cannot happen twice.
In some contexts, such phenomena are also called perdurants. This class is disjoint from E77 Persistent Item and is an abstract class that typically has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing.

Examples:
- Bronze Age (E4) (Childe, 1963)
- the earthquake in Lisbon 1755 (E5) (Chester, 2001)
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 to 1946 (E3) (Maddox, 2015)

In First Order Logic:
- E2(x) ⇒ E1(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity"/>
  </owl:Class>
  <owl:Class rdf:about="E3_Condition_State">
    <rdfs:label xml:lang="en">E3 Condition State</rdfs:label>
    <rdfs:label xml:lang="de">E3 Zustandsphase</rdfs:label>
    <rdfs:label xml:lang="el">E3 Κατάσταση</rdfs:label>
    <rdfs:label xml:lang="fr">E3 État matériel</rdfs:label>
    <rdfs:label xml:lang="pt">E3 Estado Material</rdfs:label>
    <rdfs:label xml:lang="ru">E3 Состояниe</rdfs:label>
    <rdfs:label xml:lang="zh">E3 条件状态</rdfs:label>
    <skos:notation>E3</skos:notation>
    <rdfs:subClassOf rdf:resource="E2_Temporal_Entity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P44i_is_condition_of"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the states of objects characterised by a certain condition over a time-span. 
An instance of this class describes the prevailing physical condition of any material object or feature during a specific instance of E52 Time-Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held.
The nature of that condition can be described using P2 has type. For example, the instance of E3 Condition State “condition of the SS Great Britain between 22(nd) September 1846 and 27(th) August 1847” can be characterized as an instance “wrecked” of E55 Type.

Examples:
- the "reconstructed" state of the “Amber Room” in Tsarskoje Selo from summer 2003 until now (Owen, 2009)
- the "ruined" state of Peterhof Palace near Saint Petersburg from 1944 to 1946 (Maddox, 2015)
- the state of my turkey in the oven at 14:30 on 25(th) December 2002 [P2 has type: E55 Type “still not cooked”] (fictitious)
- the topography of the leaves of Sinai Printed Book 3234.2361 on the 10(th) July 2007 [described as: of type "cockled"] (fictitious)

In First Order Logic:
- E3(x) ⇒ E2(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E3_Condition_State"/>
  </owl:Class>
  <owl:Class rdf:about="E4_Period">
    <rdfs:label xml:lang="en">E4 Period</rdfs:label>
    <rdfs:label xml:lang="de">E4 Phase</rdfs:label>
    <rdfs:label xml:lang="el">E4 Περίοδος</rdfs:label>
    <rdfs:label xml:lang="fr">E4 Période</rdfs:label>
    <rdfs:label xml:lang="pt">E4 Período</rdfs:label>
    <rdfs:label xml:lang="ru">E4 Пeриод</rdfs:label>
    <rdfs:label xml:lang="zh">E4 时期</rdfs:label>
    <skos:notation>E4</skos:notation>
    <rdfs:subClassOf rdf:resource="E2_Temporal_Entity"/>
    <rdfs:subClassOf rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P7_took_place_at"/>
        <owl:someValuesFrom rdf:resource="E53_Place"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises sets of coherent phenomena or cultural manifestations occurring in time and space.
It is the social or physical coherence of these phenomena that identify an instance of E4 Period and not the associated spatiotemporal extent. This extent is only the “ground” or space in an abstract physical sense that the actual process of growth, spread and retreat has covered. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area and time as a sedentary culture. This also means that overlapping land use rights, common among first nations, amounts to overlapping periods.
Often, this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the “Ming Dynasty” or the “McCarthy Era”, but also geopolitical units and activities of settlements are regarded as special cases of E4 Period. However, there are no assumptions about the scale of the associated phenomena. In particular all events are seen as synthetic processes consisting of coherent phenomena. Therefore, E4 Period is a superclass of E5 Event. For example, a modern clinical birth, an instance of E67 Birth, can be seen as both a single event, i.e. an instance of E5 Event, and as an extended period, i.e. an instance of E4 Period, that consists of multiple physical processes and complementary activities performed by multiple instances of E39 Actor.
E4 Period is a subclass of E2 Temporal Entity and of E92 Spacetime Volume. The latter is intended as a phenomenal spacetime volume as defined in CIDOC CRMgeo (Doerr &amp; Hiebel, 2013). By virtue of this multiple inheritance, it is possible to discuss the physical extent of an instance of E4 Period without representing each instance of it together with an instance of its associated spacetime volume. This model combines two quite different kinds of substance: an instance of E4 Period is a phenomenon while an instance of E92 Spacetime Volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance of E4 Period is regarded to be unique to it due to all its details and fuzziness; its identity and existence depends uniquely on the identity of the instance of E4 Period. Therefore, this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language.
Typical use of this class in cultural heritage documentation is for documenting cultural and artistic periods. There are two different conceptualisations of ‘artistic style’, defined either by physical features or by historical context. For example, “Impressionism” can be viewed as a period in the European sphere of influence lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an instance of E4 Period, and the second defines morphological object types that fall under E55 Type.
A geopolitical unit as a specific case of an instance of E4 Period is the set of activities and phenomena related to the claim of power, the consequences of belonging to a jurisdictional area and an administrative system that establishes a geopolitical unit. Examples from the modern period are countries or administrative areas of countries such as districts whose actions and structures define activities and phenomena in the area that they intend to govern. The borders of geopolitical units are often defined in contracts or treaties although they may deviate from the actual practice. The spatiotemporal properties of Geopolitical units can be modelled through the properties inherited from E92 Spacetime Volume.
Another specific case of an instance of E4 Period is the actual extent of the set of activities and phenomena as evidenced by their physical traces that define a settlement, such as the populated period of Nineveh.

Examples:
- Jurassic (Hallam, 1975)
- Populated Period of Nineveh
- Imperial Rome under Marcus Aurelius
- European Bronze Age (Harrison, 2004) 
- Italian Renaissance (Macdonald, 1992)
- Thirty Years War (Lee, 1991)
- Sturm und Drang (Berkoff, 2013)
- Cubism (Cox, 2000)
- The Capital of Russia (E4) [the capital of Russia in the sense of an administrative unit moved in historical times from Moscow to St Petersburg and then back to Moscow. This exemplifies an administrative unit changing place over time without temporal discontinuity]
- The settling activity of the community of Helsinki (a.k.a. Helsingfors) (E7) [the original settlement called Helsinki was located in the area of the modern airport. The community moved later to settle on the coast. This exemplifies a continued activity changing place over time without temporal discontinuity]
- Bronze Age (E4) [Bronze Age, in the sense of technological adoption, spread over disjoint areas including islands such as the British Isles without temporal discontinuity]
- Japan, the state (E4) [In 2021, the Japanese state as a political unit comprised in 6852 islands extending along the Pacific coast of Asia]

In First Order Logic:
- E4(x) ⇒ E2(x)
- E4(x) ⇒ E92(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E4_Period"/>
  </owl:Class>
  <owl:Class rdf:about="E5_Event">
    <rdfs:label xml:lang="en">E5 Event</rdfs:label>
    <rdfs:label xml:lang="de">E5 Ereignis</rdfs:label>
    <rdfs:label xml:lang="el">E5 Συμβάν</rdfs:label>
    <rdfs:label xml:lang="fr">E5 Évènement</rdfs:label>
    <rdfs:label xml:lang="pt">E5 Evento</rdfs:label>
    <rdfs:label xml:lang="ru">E5 Событиe</rdfs:label>
    <rdfs:label xml:lang="zh">E5 事件</rdfs:label>
    <skos:notation>E5</skos:notation>
    <rdfs:subClassOf rdf:resource="E4_Period"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P12_occurred_in_the_presence_of"/>
        <owl:someValuesFrom rdf:resource="E77_Persistent_Item"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises distinct, delimited and coherent processes and interactions of a material nature, in cultural, social or physical systems, involving and affecting instances of E77 Persistent Item in a way characteristic of the kind of process. Typical examples are meetings, births, deaths, actions of decision taking, making or inventing things, but also more complex and extended ones such as conferences, elections, building of a castle, or battles.
While the continuous growth of a tree lacks the limits characteristic of an event, its germination from a seed does qualify as an event. Similarly, the blowing of the wind lacks the distinctness and limits of an event, but a hurricane, flood or earthquake would qualify as an event. Mental processes are considered as events, in cases where they are connected with the material externalization of their results; for example, the creation of a poem, a performance or a change of intention that becomes obvious from subsequent actions or declarations.
The effects of an instance of E5 Event may not lead to relevant permanent changes of properties or relations of the items involved in it, for example an unrecorded performance. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event.
While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example, the statements made during a meeting and the listening of the audience.
Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analysed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the size of the phenomena. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy overall effect and are thus not instances of E5 Event.

Examples:
- the birth of Cleopatra (E67) (Pomeroy, 1984)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6) (Camardo, 2013)
- World War II (E7) (Barber, 1994)
- the Battle of Stalingrad (E7) (Hoyt, 1993)
- the Yalta Conference (E7) (Harbutt, 2010)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday (fictitious)
- the CIDOC conference 2003 (E7)

In First Order Logic:
- E5(x) ⇒ E4(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
  </owl:Class>
  <owl:Class rdf:about="E6_Destruction">
    <rdfs:label xml:lang="en">E6 Destruction</rdfs:label>
    <rdfs:label xml:lang="de">E6 Zerstörung</rdfs:label>
    <rdfs:label xml:lang="el">E6 Καταστροφή</rdfs:label>
    <rdfs:label xml:lang="fr">E6 Destruction</rdfs:label>
    <rdfs:label xml:lang="pt">E6 Destruição</rdfs:label>
    <rdfs:label xml:lang="ru">E6 Разрушeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E6 破坏</rdfs:label>
    <skos:notation>E6</skos:notation>
    <rdfs:subClassOf rdf:resource="E64_End_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P13_destroyed"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing, such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction can 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: 
1. If the matter remaining from the destruction is not documented, the event is modelled solely as an instance of E6 Destruction. 
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as an instance of E11 Modification.

Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD (Camardo, 2013)
- the destruction of Nineveh (E6, E7) (River, 2016) 
- the breaking of a champagne glass yesterday by my dog (fictitious)

In First Order Logic:
- E6(x) ⇒ E64(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E6_Destruction"/>
  </owl:Class>
  <owl:Class rdf:about="E7_Activity">
    <rdfs:label xml:lang="en">E7 Activity</rdfs:label>
    <rdfs:label xml:lang="de">E7 Handlung</rdfs:label>
    <rdfs:label xml:lang="el">E7 Δράση</rdfs:label>
    <rdfs:label xml:lang="fr">E7 Activité</rdfs:label>
    <rdfs:label xml:lang="pt">E7 Atividade</rdfs:label>
    <rdfs:label xml:lang="ru">E7 Дeятeльность</rdfs:label>
    <rdfs:label xml:lang="zh">E7 活动</rdfs:label>
    <skos:notation>E7</skos:notation>
    <rdfs:subClassOf rdf:resource="E5_Event"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P14_carried_out_by"/>
        <owl:someValuesFrom rdf:resource="E39_Actor"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. 
This notion includes complex, composite, and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door.

Examples:
- the Battle of Stalingrad (Hoyt, 1993)
- the Yalta Conference (Harbutt, 2010)
- my birthday celebration 28-6-1995
- the writing of “Faust” by Goethe (E65) (Williams, 2020)
- the formation of the Bauhaus 1919 (E66) (Droste, 2006)
- the people of Iraq giving the name ‘Quyunjig’ to the place identified by the TGN as ‘7017998’
- Kira Weber working in glass art from 1984 to 1993
- Kira Weber working in oil and pastel painting from 1993

In First Order Logic:
- E7(x) ⇒ E5(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
  </owl:Class>
  <owl:Class rdf:about="E8_Acquisition">
    <rdfs:label xml:lang="en">E8 Acquisition</rdfs:label>
    <rdfs:label xml:lang="de">E8 Erwerb</rdfs:label>
    <rdfs:label xml:lang="el">E8 Απόκτηση</rdfs:label>
    <rdfs:label xml:lang="fr">E8 Acquisition</rdfs:label>
    <rdfs:label xml:lang="pt">E8 Aquisição</rdfs:label>
    <rdfs:label xml:lang="ru">E8 Поступлeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E8 采访</rdfs:label>
    <skos:notation>E8</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P24_transferred_title_of"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more other instances of E39 Actor. 
The class also applies to the establishment or loss of ownership of instances of E18 Physical Thing. It does not, however, imply changes of any other kinds of rights. 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:
1. the beginning of ownership
2. the end of ownership
3. the transfer of ownership
4. the acquisition from an unknown source
5. the loss of title due to destruction of the item
It may also describe events where a collector appropriates legal title, for example, by annexation or field collection. The interpretation of the museum notion of “accession” differs between institutions. The CIDOC CRM therefore models legal ownership (E8 Acquisition) and physical custody (E10 Transfer of Custody) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.

Examples:
- the collection of a hammerhead shark, genus Sphyrna (Carchariniformes), by John Steinbeck and Edward Ricketts at Puerto Escondido in the Gulf of Mexico on 25(th) March 1940. (Steinbeck, 2000)
- the acquisition of El Greco’s “The Apostles Peter and Paul” by the State Hermitage in Saint Petersburg. (https://hermitagemuseum.org/wps/portal/hermitage/digital-collection/01.+Paintings/32730)
- the loss of my stuffed Fringilla coelebs due to insect damage last year (fictitious)

In First Order Logic:
- E8(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E8_Acquisition"/>
  </owl:Class>
  <owl:Class rdf:about="E9_Move">
    <rdfs:label xml:lang="en">E9 Move</rdfs:label>
    <rdfs:label xml:lang="de">E9 Objektbewegung</rdfs:label>
    <rdfs:label xml:lang="el">E9 Μετακίνηση</rdfs:label>
    <rdfs:label xml:lang="fr">E9 Déplacement</rdfs:label>
    <rdfs:label xml:lang="pt">E9 Locomoção</rdfs:label>
    <rdfs:label xml:lang="ru">E9 Пeрeмeщeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E9 移动</rdfs:label>
    <skos:notation>E9</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P27_moved_from"/>
        <owl:someValuesFrom rdf:resource="E53_Place"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P26_moved_to"/>
        <owl:someValuesFrom rdf:resource="E53_Place"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P25_moved"/>
        <owl:someValuesFrom rdf:resource="E19_Physical_Object"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object. 
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.

Examples:
- the relocation of London Bridge from the UK to the USA (Wildfang, 2005)
- the movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019

In First Order Logic:
- E9(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E9_Move"/>
  </owl:Class>
  <owl:Class rdf:about="E10_Transfer_of_Custody">
    <rdfs:label xml:lang="en">E10 Transfer of Custody</rdfs:label>
    <rdfs:label xml:lang="de">E10 Übertragung des Gewahrsams</rdfs:label>
    <rdfs:label xml:lang="el">E10 Μεταβίβαση Κατοχής</rdfs:label>
    <rdfs:label xml:lang="fr">E10 Transfert de la garde</rdfs:label>
    <rdfs:label xml:lang="pt">E10 Transferência de Custódia</rdfs:label>
    <rdfs:label xml:lang="ru">E10 Пeрeдача Хранeния</rdfs:label>
    <rdfs:label xml:lang="zh">E10 转移监护权</rdfs:label>
    <skos:notation>E10</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P30_transferred_custody_of"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises transfers of the physical custody or the legal responsibility for the physical custody of objects. The recording of the donor or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. 
Depending on the circumstances, it may describe: 
1. the beginning of custody (there is no previous custodian)
2. the end of custody (there is no subsequent custodian)
3. the transfer of custody (transfer from one custodian to the next)
4. the receipt of custody from an unknown source (the previous custodian is unknown)
5. the declared loss of an object (the current or subsequent custodian is unknown)
In the event that only a single kind of transfer of custody occurs, either the legal responsibility for the custody or the actual physical possession of the object but not both, this difference should be expressed using the property 
P2 has type (is type of).
The sense of physical possession requires that the object of custody be in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing.
The interpretation of the museum notion of "accession" differs between institutions. The CIDOC CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these. 
Theft is a specific case of illegal transfer of custody.

Examples:
- the delivery of the paintings by Secure Deliveries Inc. to the National Gallery
- the return of Picasso’s “Guernica” to Madrid’s Prado in 1981 (Chipp, 1988)
- the transfer of custody of the work described as “Von der Velden ein Ufer an der See” from Johann Matthäus von Merian to the Auction House Heldevier (Jacob) for the purpose of sale, ca. 1716
- the transfer of custody of the painting ‘Mrs. Fitzherbert’ to the art dealer Knoedler from Parke-Bernet Galleries (New York, NY, USA) ca. March 1941

In First Order Logic:
- E10(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E10_Transfer_of_Custody"/>
  </owl:Class>
  <owl:Class rdf:about="E11_Modification">
    <rdfs:label xml:lang="en">E11 Modification</rdfs:label>
    <rdfs:label xml:lang="de">E11 Bearbeitung</rdfs:label>
    <rdfs:label xml:lang="el">E11 Τροποποίηση</rdfs:label>
    <rdfs:label xml:lang="fr">E11 Modification</rdfs:label>
    <rdfs:label xml:lang="pt">E11 Modificação</rdfs:label>
    <rdfs:label xml:lang="ru">E11 Измeнeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E11 修改</rdfs:label>
    <skos:notation>E11</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P31_has_modified"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises instances of E7 Activity that are undertaken to create, alter or change instances of E24 Physical Human-Made Thing.
This class includes the production of an item from raw materials and other so far undocumented objects. It also includes the conservation treatment of an object.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in an instance of E11 Modification, and that others may be produced as a result of it. An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
An activity undertaken on an object which was designed to alter it, but which, in fact, it did not in any seemingly significant way (such as the application of a solvent during conservation which failed to dissolve any part of the object), is still considered as an instance of E11 Modification. Typically, any such activity will leave at least forensic traces of evidence on the object.
If the instance of E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.

Examples:
- the construction of the SS Great Britain (E12) (Gregor, 1971)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956 (Håfors, 2010)
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81) (Yakel, 2000)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan (Cali and Dougil, 2012)

In First Order Logic:
- E11(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E11_Modification"/>
  </owl:Class>
  <owl:Class rdf:about="E12_Production">
    <rdfs:label xml:lang="en">E12 Production</rdfs:label>
    <rdfs:label xml:lang="de">E12 Herstellung</rdfs:label>
    <rdfs:label xml:lang="el">E12 Παραγωγή</rdfs:label>
    <rdfs:label xml:lang="fr">E12 Production</rdfs:label>
    <rdfs:label xml:lang="pt">E12 Produção</rdfs:label>
    <rdfs:label xml:lang="ru">E12 Изготовлeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E12 生产</rdfs:label>
    <skos:notation>E12</skos:notation>
    <rdfs:subClassOf rdf:resource="E11_Modification"/>
    <rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P108_has_produced"/>
        <owl:someValuesFrom rdf:resource="E24_Physical_Human-Made_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items. 
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one. 
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event. 
An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.

Examples:
- the construction of the SS Great Britain (Gregor, 1971)
- the first casting of the Little Mermaid from the harbour of Copenhagen (Dewey, 2003)
- Rembrandt’s creating of the seventh state of his etching “Woman sitting half dressed beside a stove”, 1658, identified by Bartsch Number 197 (E12, E65, E81) (Hind, 1923)

In First Order Logic:
- E12(x) ⇒ E11(x)
- E12(x) ⇒ E63(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E12_Production"/>
  </owl:Class>
  <owl:Class rdf:about="E13_Attribute_Assignment">
    <rdfs:label xml:lang="en">E13 Attribute Assignment</rdfs:label>
    <rdfs:label xml:lang="de">E13 Merkmalszuweisung</rdfs:label>
    <rdfs:label xml:lang="el">E13 Απόδοση Ιδιοτήτων</rdfs:label>
    <rdfs:label xml:lang="fr">E13 Assignation d’attribut</rdfs:label>
    <rdfs:label xml:lang="pt">E13 Atribuição de Característica</rdfs:label>
    <rdfs:label xml:lang="ru">E13 Назначeниe Атрибута</rdfs:label>
    <rdfs:label xml:lang="zh">E13 属性赋值</rdfs:label>
    <skos:notation>E13</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P140_assigned_attribute_to"/>
        <owl:someValuesFrom rdf:resource="E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the actions of making assertions about one property of an object or any single relation between two items or concepts. The type of the property asserted to hold between two items or concepts can be described by the property P177 assigned property 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.

Examples:
- the examination of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey &amp; Pickwoad, 2010)
- the assessment of the current ownership of Martin Doerr’s silver cup in February 1997 (fictitious)

In First Order Logic:
- E13(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E13_Attribute_Assignment"/>
  </owl:Class>
  <owl:Class rdf:about="E14_Condition_Assessment">
    <rdfs:label xml:lang="en">E14 Condition Assessment</rdfs:label>
    <rdfs:label xml:lang="de">E14 Zustandsfeststellung</rdfs:label>
    <rdfs:label xml:lang="el">E14 Εκτίμηση Κατάστασης</rdfs:label>
    <rdfs:label xml:lang="fr">E14 Évaluation d’état matériel</rdfs:label>
    <rdfs:label xml:lang="pt">E14 Avaliação do Estado Material</rdfs:label>
    <rdfs:label xml:lang="ru">E14 Оцeнка Состояния</rdfs:label>
    <rdfs:label xml:lang="zh">E14 状态评估</rdfs:label>
    <skos:notation>E14</skos:notation>
    <rdfs:subClassOf rdf:resource="E13_Attribute_Assignment"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P35_has_identified"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P34_concerned"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period. 
The condition assessment may be carried out by inspection, measurement, or through historical research. This class is used to document circumstances of the respective assessment that is relevant to interpret its quality at a later stage, or to continue research on related documents.

Examples:
- last year’s inspection of humidity damage to the frescos in the St. George chapel in our village (fictitious)
- the condition assessment of the endband cores of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey &amp; Pickwoad, 2010)
- the condition assessment of the cover of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey &amp; Pickwoad, 2010)

In First Order Logic:
- E14(x) ⇒ E13(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E14_Condition_Assessment"/>
  </owl:Class>
  <owl:Class rdf:about="E15_Identifier_Assignment">
    <rdfs:label xml:lang="en">E15 Identifier Assignment</rdfs:label>
    <rdfs:label xml:lang="de">E15 Kennzeichenzuweisung</rdfs:label>
    <rdfs:label xml:lang="el">E15 Απόδοση Αναγνωριστικού</rdfs:label>
    <rdfs:label xml:lang="fr">E15 Assignation d’identifiant</rdfs:label>
    <rdfs:label xml:lang="pt">E15 Atribuição de Identificador</rdfs:label>
    <rdfs:label xml:lang="ru">E15 Назначeниe Идeнтификатора</rdfs:label>
    <rdfs:label xml:lang="zh">E15 标识符赋值</rdfs:label>
    <skos:notation>E15</skos:notation>
    <rdfs:subClassOf rdf:resource="E13_Attribute_Assignment"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P37_assigned"/>
        <owl:someValuesFrom rdf:resource="E42_Identifier"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An instance 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 through the P2 has type (is type of) property.

Examples:
- replacement of the inventory number TA959a by GE34604 for a 17(th) century lamentation cloth at the Museum Benaki, Athens
- assigning the author and uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” to a work 
- on 1(st) June 2001, assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” to Guillaume de Machaut (Kelly, 2014)

In First Order Logic:
- E15(x) ⇒ E13(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E15_Identifier_Assignment"/>
  </owl:Class>
  <owl:Class rdf:about="E16_Measurement">
    <rdfs:label xml:lang="en">E16 Measurement</rdfs:label>
    <rdfs:label xml:lang="de">E16 Messung</rdfs:label>
    <rdfs:label xml:lang="el">E16 Μέτρηση</rdfs:label>
    <rdfs:label xml:lang="fr">E16 Mesurage</rdfs:label>
    <rdfs:label xml:lang="pt">E16 Medição</rdfs:label>
    <rdfs:label xml:lang="ru">E16 Измeрeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E16 测量</rdfs:label>
    <skos:notation>E16</skos:notation>
    <rdfs:subClassOf rdf:resource="E13_Attribute_Assignment"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P40_observed_dimension"/>
        <owl:someValuesFrom rdf:resource="E54_Dimension"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P39_measured"/>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises actions measuring 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 instance(s) of E18 Physical Thing that was used as the empirical basis for the attribute assignment. For instance, inferring properties of depicted items using image material, such as satellite images, is not regarded as an instance of E16 Measurement, but as a subsequent instance of E13 Attribute Assignment. Rather, only the production of the images, understood as arrays of radiation intensities, is regarded as an instance of E16 Measurement. The same reasoning holds for other sensor data.

Examples:
- measurement of the height of silver cup 232 on 31(st) August 1997 (fictitious)
- the carbon 14 dating of the “Schoeninger Speer II” in 1996 [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995.] (Kouwenhoven, 1997)

In First Order Logic:
- E16(x) ⇒ E13(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E16_Measurement"/>
  </owl:Class>
  <owl:Class rdf:about="E17_Type_Assignment">
    <rdfs:label xml:lang="en">E17 Type Assignment</rdfs:label>
    <rdfs:label xml:lang="de">E17 Typuszuweisung</rdfs:label>
    <rdfs:label xml:lang="el">E17 Απόδοση Τύπου</rdfs:label>
    <rdfs:label xml:lang="fr">E17 Assignation de type</rdfs:label>
    <rdfs:label xml:lang="pt">E17 Atribuição de Tipo</rdfs:label>
    <rdfs:label xml:lang="ru">E17 Назначeниe Типа</rdfs:label>
    <rdfs:label xml:lang="zh">E17 类型赋值</rdfs:label>
    <skos:notation>E17</skos:notation>
    <rdfs:subClassOf rdf:resource="E13_Attribute_Assignment"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P41_classified"/>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P42_assigned"/>
        <owl:someValuesFrom rdf:resource="E55_Type"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions, and concepts. 
This class allows for the documentation of the context of classification acts in cases where the value of the classification depends on the personal opinion of the classifier, and the date that the classification was made. This class also encompasses the notion of “determination,” i.e. the systematic and molecular identification of a specimen in biology.

Examples:
- the first classification of object GE34604 as Lamentation cloth at the Museum Benaki, Athens
- the determination of a cactus in Martin Doerr’s garden as Cereus hildmannianus K.Schum., July 2003

In First Order Logic:
- E17(x) ⇒ E13(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E17_Type_Assignment"/>
  </owl:Class>
  <owl:Class rdf:about="E18_Physical_Thing">
    <rdfs:label xml:lang="en">E18 Physical Thing</rdfs:label>
    <rdfs:label xml:lang="de">E18 Materielles</rdfs:label>
    <rdfs:label xml:lang="el">E18 Υλικό Πράγμα</rdfs:label>
    <rdfs:label xml:lang="fr">E18 Chose matérielle</rdfs:label>
    <rdfs:label xml:lang="pt">E18 Coisa Material</rdfs:label>
    <rdfs:label xml:lang="ru">E18 Матeриальный Прeдмeт</rdfs:label>
    <rdfs:label xml:lang="zh">E18 实物</rdfs:label>
    <skos:notation>E18</skos:notation>
    <rdfs:subClassOf rdf:resource="E72_Legal_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P13i_was_destroyed_by"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P45_consists_of"/>
        <owl:someValuesFrom rdf:resource="E57_Material"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P53_has_former_or_current_location"/>
        <owl:someValuesFrom rdf:resource="E53_Place"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <owl:disjointWith rdf:resource="E28_Conceptual_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises all persistent physical items with a relatively stable form, human-made or natural.
Depending on the existence of natural boundaries of such things, the CIDOC CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land, etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter.
An instance of E18 Physical Thing occupies not only a particular geometric space at any instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces, such as the interior of a box. For the purpose of more detailed descriptions of the presence of an instance of E18 Physical Thing in space and time it can be associated with its specific instance of E92 Spacetime Volume by the property P196 defines (is defined by). 
The CIDOC CRM is generally not concerned with amounts of matter in fluid or gaseous states, as long as they are not confined in an identifiable way for an identifiable minimal time-span.

Examples:
- the Cullinan Diamond (E19) (Scarratt and Shor, 2006)
- the cave “Ideon Andron” in Crete (E26) (Smith, 1844-49)
- the Mona Lisa (E22) (Mohen, 2006)

In First Order Logic:
- E18(x) ⇒ E72(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
  </owl:Class>
  <owl:Class rdf:about="E19_Physical_Object">
    <rdfs:label xml:lang="en">E19 Physical Object</rdfs:label>
    <rdfs:label xml:lang="de">E19 Materieller Gegenstand</rdfs:label>
    <rdfs:label xml:lang="el">E19 Υλικό Αντικείμενο</rdfs:label>
    <rdfs:label xml:lang="fr">E19 Objet matériel</rdfs:label>
    <rdfs:label xml:lang="pt">E19 Objeto Material</rdfs:label>
    <rdfs:label xml:lang="ru">E19 Матeриальный Объeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E19 物质对象</rdfs:label>
    <skos:notation>E19</skos:notation>
    <rdfs:subClassOf rdf:resource="E18_Physical_Thing"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P55_has_current_location"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P54_has_current_permanent_location"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises items of a material nature that are units for documentation and have physical boundaries that separate them completely in an objective way from other objects. 
The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen. Typically, instances of E19 Physical Object can be moved (if not too heavy).
In some contexts, such objects, except for aggregates, are also called “bona fide objects”, i.e. naturally defined objects (Smith &amp; Varzi, 2000). 
The decision as to what is documented as a complete item, rather than by its parts or components, may be purely administrative or may be a result of the order in which the item was acquired.

Examples:
- Aphrodite of Milos (E22) (Kousser, 2005)
- the Cullinan Diamond (Scarratt and Shor, 2006)
- Apollo 13 at the time of launch (E22) (Lovell and Kluger, 1994)

In First Order Logic:
- E19(x) ⇒ E18(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E19_Physical_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E20_Biological_Object">
    <rdfs:label xml:lang="en">E20 Biological Object</rdfs:label>
    <rdfs:label xml:lang="de">E20 Biologischer Gegenstand</rdfs:label>
    <rdfs:label xml:lang="el">E20 Βιολογικό Ακτικείμενο</rdfs:label>
    <rdfs:label xml:lang="fr">E20 Objet biologique</rdfs:label>
    <rdfs:label xml:lang="pt">E20 Objeto Biológico</rdfs:label>
    <rdfs:label xml:lang="ru">E20 Биологичeский Объeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E20 生物对象</rdfs:label>
    <skos:notation>E20</skos:notation>
    <rdfs:subClassOf rdf:resource="E19_Physical_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises individual items of a material nature, which live, have lived, or are natural products of or from living organisms. 
Artificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Human-Made Object.

Examples:
- me (fictitious)
- Tut-Ankh-Amun (Edwards and Boltin, 1979)
- Boukephalus [Horse of Alexander the Great] (Lamb, 2005)
- petrified dinosaur excrement PA1906-344

In First Order Logic:
- E20(x) ⇒ E19(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E20_Biological_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E21_Person">
    <rdfs:label xml:lang="en">E21 Person</rdfs:label>
    <rdfs:label xml:lang="de">E21 Person</rdfs:label>
    <rdfs:label xml:lang="el">E21 Πρόσωπο</rdfs:label>
    <rdfs:label xml:lang="fr">E21 Personne</rdfs:label>
    <rdfs:label xml:lang="pt">E21 Pessoa</rdfs:label>
    <rdfs:label xml:lang="ru">E21 Личность</rdfs:label>
    <rdfs:label xml:lang="zh">E21 人物</rdfs:label>
    <skos:notation>E21</skos:notation>
    <rdfs:subClassOf rdf:resource="E20_Biological_Object"/>
    <rdfs:subClassOf rdf:resource="E39_Actor"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P98i_was_born"/>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P152_has_parent"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">2</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises real persons who live or are assumed to have lived. 
Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CIDOC CRM does not propose a specific form to support reasoning about possible identity.
In a bibliographic context, a name presented following the conventions usually employed for personal names will be assumed to correspond to an actual real person (an instance of E21 Person), unless evidence is available to indicate that this is not the case. The fact that a persona may erroneously be classified as an instance of E21 Person does not imply that the concept comprises personae.

Examples:
- Tut-Ankh-Amun (Edwards and Boltin, 1979)
- Nelson Mandela (Brown and Hort, 2006)

In First Order Logic:
- E21(x) ⇒ E20(x)
- E21(x) ⇒ E39(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E21_Person"/>
  </owl:Class>
  <owl:Class rdf:about="E22_Human-Made_Object">
    <rdfs:label xml:lang="en">E22 Human-Made Object</rdfs:label>
    <rdfs:label xml:lang="fr">E22 Objet élaboré par l’humain</rdfs:label>
    <rdfs:label xml:lang="ru">E22 Рукотворный Объeкт</rdfs:label>
    <skos:notation>E22</skos:notation>
    <rdfs:subClassOf rdf:resource="E19_Physical_Object"/>
    <rdfs:subClassOf rdf:resource="E24_Physical_Human-Made_Thing"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises all persistent physical objects of any size that are purposely created by human activity and have physical boundaries that separate them completely in an objective way from other objects. 
The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen.

Examples:
- the Rosetta Stone (E22)
- LNER Class A4 4468 Mallard [the World’s fastest steam locomotive, preserved at the National Railway Museum of York, UK] (Solomon, 2003)
- the Portland Vase (Walker, 2004)

In First Order Logic:
- E22(x) ⇒ E19(x)
- E22(x) ⇒ E24(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E22_Human-Made_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E24_Physical_Human-Made_Thing">
    <rdfs:label xml:lang="en">E24 Physical Human-Made Thing</rdfs:label>
    <rdfs:label xml:lang="fr">E24 Chose matérielle élaborée par l’humain</rdfs:label>
    <rdfs:label xml:lang="ru">E24 Матeриальный Рукотворный Объeкт</rdfs:label>
    <skos:notation>E24</skos:notation>
    <rdfs:subClassOf rdf:resource="E18_Physical_Thing"/>
    <rdfs:subClassOf rdf:resource="E71_Human-Made_Thing"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P108i_was_produced_by"/>
        <owl:someValuesFrom rdf:resource="E12_Production"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises all persistent physical items of any size that are purposely created by human activity. This class comprises, besides others, human-made objects, such as a sword, and human-made features, such as rock art. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Human-Made Thing.
Instances of E24 Physical 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 instance of E24 Physical Human-Made Thing, the results of preparation of natural history specimens that substantially change their natural or original state should be regarded as instances of E24 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 an instance of E24 Physical Human-Made Thing may continue to be non-human-made and preserved during the production process, for example natural pearls used as a part of an eardrop.

Examples:
- the Forth Railway Bridge (Shipway, Bouch, Baker and Fowler, 1990).
- the Channel Tunnel (E25) (Holliday, Marcou and Vickerman, 1991)
- the Palace of Knossos (Evans, 1921)
- the Colosseum in Rome, Italy (Hopkins and Beard, 2011)
- the Historical Collection of the Museum Benaki in Athens (E78) (Georgoula, 2005)
- the Rosetta Stone (E22)
- my paperback copy of Crime &amp; Punishment (E22) (fictitious)
- the computer disk at ICS-FORTH that stores the canonical Definition of the CIDOC CRM v.3.2 (E22)
- my empty DVD disk (E22) (fictitious)

In First Order Logic:
- E24(x) ⇒ E18(x)
- E24(x) ⇒ E71(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E24_Physical_Human-Made_Thing"/>
  </owl:Class>
  <owl:Class rdf:about="E25_Human-Made_Feature">
    <rdfs:label xml:lang="en">E25 Human-Made Feature</rdfs:label>
    <rdfs:label xml:lang="fr">E25 Caractéristique élaborée par l'humain</rdfs:label>
    <rdfs:label xml:lang="ru">E25 Искусствeнный Признак</rdfs:label>
    <skos:notation>E25</skos:notation>
    <rdfs:subClassOf rdf:resource="E24_Physical_Human-Made_Thing"/>
    <rdfs:subClassOf rdf:resource="E26_Physical_Feature"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc. In particular, it includes the information encoding features on mechanical or digital carriers.

Examples:
- the Manchester Ship Canal (Farnie, 1980)
- Michael Jackson’s nose following plastic surgery
- the laser-readable “pits” engraved June 2014 on Martin Doerr’s CD-R, copying songs of Edith Piaf
- the carved letters on the Rosetta Stone

In First Order Logic:
- E25(x) ⇒ E24(x)
- E25(x) ⇒ E26(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E25_Human-Made_Feature"/>
  </owl:Class>
  <owl:Class rdf:about="E26_Physical_Feature">
    <rdfs:label xml:lang="en">E26 Physical Feature</rdfs:label>
    <rdfs:label xml:lang="de">E26 Materielles Merkmal</rdfs:label>
    <rdfs:label xml:lang="el">E26 Υλικό Μόρφωμα</rdfs:label>
    <rdfs:label xml:lang="fr">E26 Caractéristique physique</rdfs:label>
    <rdfs:label xml:lang="pt">E26 Característica Material</rdfs:label>
    <rdfs:label xml:lang="ru">E26 Физичeский Признак</rdfs:label>
    <rdfs:label xml:lang="zh">E26 物理特征</rdfs:label>
    <skos:notation>E26</skos:notation>
    <rdfs:subClassOf rdf:resource="E18_Physical_Thing"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P56i_is_found_on"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable features that are physically attached in an integral way to particular physical objects. 
Instances of E26 Physical Feature share many of the attributes of instances of E19 Physical Object. They may have a one-dimensional, two-dimensional, 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”, with the exception of aggregates of “bona fide objects” (Smith &amp; Varzi, 2000).

Examples:
- the cave of Dirou, Mani, Greece (Psimenos. 2005)
- the temple in Abu Simbel before its removal, which was carved out of solid rock (E25) (Hawass, 2000)
- Albrecht Duerer's signature on his painting of Charles the Great (E25) (Strauss, 1974)
- the damage to the nose of the Great Sphinx in Giza (Temple, 2009)
- Michael Jackson’s nose prior to plastic surgery

In First Order Logic:
- E26(x) ⇒ E18(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E26_Physical_Feature"/>
  </owl:Class>
  <owl:Class rdf:about="E27_Site">
    <rdfs:label xml:lang="en">E27 Site</rdfs:label>
    <rdfs:label xml:lang="de">E27 Gelände</rdfs:label>
    <rdfs:label xml:lang="el">E27 Φυσικός Χώρος</rdfs:label>
    <rdfs:label xml:lang="fr">E27 Site</rdfs:label>
    <rdfs:label xml:lang="pt">E27 Lugar</rdfs:label>
    <rdfs:label xml:lang="ru">E27 Мeстоположeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E27 场地</rdfs:label>
    <skos:notation>E27</skos:notation>
    <rdfs:subClassOf rdf:resource="E26_Physical_Feature"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises pieces of land or sea floor. 
In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings, and maps.
Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location.

Examples:
- the Amazon river basin (Hegen, 1966)
- Knossos (Evans, 1921)
- the Apollo 11 landing site (Siegler and Smrekar, 2014)
- Heathrow Airport (Wicks, 2014)
- the submerged harbour of the Minoan settlement of Gournia, Crete (Watrous, 2012)
- the island of Crete

In First Order Logic:
- E27(x) ⇒ E26(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E27_Site"/>
  </owl:Class>
  <owl:Class rdf:about="E28_Conceptual_Object">
    <rdfs:label xml:lang="en">E28 Conceptual Object</rdfs:label>
    <rdfs:label xml:lang="de">E28 Begrifflicher Gegenstand</rdfs:label>
    <rdfs:label xml:lang="el">E28 Νοητικό Αντικείμενο</rdfs:label>
    <rdfs:label xml:lang="fr">E28 Objet conceptuel</rdfs:label>
    <rdfs:label xml:lang="pt">E28 Objeto Conceitual</rdfs:label>
    <rdfs:label xml:lang="ru">E28 Концeптуальный Объeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E28 概念对象</rdfs:label>
    <skos:notation>E28</skos:notation>
    <rdfs:subClassOf rdf:resource="E71_Human-Made_Thing"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P94i_was_created_by"/>
        <owl:someValuesFrom rdf:resource="E65_Creation"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation, or historical implication. The production of such information might have been supported by the use of technical devices such as cameras or computers.
Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc.
They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost.

Examples:
- Beethoven’s “Ode an die Freude” (Ode to Joy) (E73) (Kershaw, 1999)
- the definition of “ontology” in the Oxford English Dictionary (E73) (Oxford University Press, 1989)
- the knowledge about the victory at Marathon carried by the famous runner (E89) (Lagos &amp; Karyanos, 2020)
- [Explanation note: The following examples illustrate the distinction between a propositional object, its names and its encoded forms. The Maxwell equations (Ball, 1962) are a good example, because they belong to the fundamental laws of physics and their mathematical content yields identical, unambiguous results regardless formulation and encoding.] 
- “Maxwell equations” (E41) [preferred subject access point from LCSH, http://lccn.loc.gov/sh85082387, accessed 18(th) April 2021. This is only the name for the Maxwell equations as standardized by the Library of Congress and not the equations themselves.]
- “Equations, Maxwell” (E41) [variant subject access point from LCSH, http://lccn.loc.gov/sh85082387, accessed 18(th) April 2021. This is another name for the equation standardized by the Library of Congress and not the equations themselves.]
- Maxwell's equations (E89) [This is the propositional content of the equations proper, independent of any particular notation or mathematical formalism.] (Ball, 1962)
- The encoding of Maxwells equations as in https://upload.wikimedia.org/wikipedia/commons/c/c4/Maxwell%27sEquations.svg (E73) [accessed 18(th) April 2021. This is one possible symbolic encoding of the propositional content of the equations.]

In First Order Logic:
- E28(x) ⇒ E71(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E28_Conceptual_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E29_Design_or_Procedure">
    <rdfs:label xml:lang="en">E29 Design or Procedure</rdfs:label>
    <rdfs:label xml:lang="de">E29 Entwurf oder Verfahren</rdfs:label>
    <rdfs:label xml:lang="el">E29 Σχέδιο</rdfs:label>
    <rdfs:label xml:lang="fr">E29 Conceptualisation ou procédure</rdfs:label>
    <rdfs:label xml:lang="pt">E29 Projeto ou Procedimento</rdfs:label>
    <rdfs:label xml:lang="ru">E29 Проeкт или Процeдура</rdfs:label>
    <rdfs:label xml:lang="zh">E29 设计或程序</rdfs:label>
    <skos:notation>E29</skos:notation>
    <rdfs:subClassOf rdf:resource="E73_Information_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form, or contents. In particular, it comprises plans for deliberate human activities that may result in new instances of E71 Human-Made Thing or for shaping or guiding the execution of an instance of E7 Activity.
Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others.
This is modelled using P69 has association with (is associated with): E29 Design or Procedure.
Designs or procedures can be seen as one of the following:
1. A schema for the activities it describes
2. A schema of the products that result from their application
3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci’s famous plans for flying machines
Because designs or procedures may never be applied or only partially executed, the CIDOC CRM models a loose relationship between the plan and the respective product.

Examples:
- the ISO standardisation procedure
- the musical notation for Beethoven’s “Ode to Joy” (Kershaw, 1999)
- the architectural drawings for the Kölner Dom (Cologne Cathedral) in Cologne, Germany (Wolff, 1999)
- the drawing found on Folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486 to 1490, kept in the Biblioteca Ambrosiana in Milan

In First Order Logic:
- E29(x) ⇒ E73(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
  </owl:Class>
  <owl:Class rdf:about="E30_Right">
    <rdfs:label xml:lang="en">E30 Right</rdfs:label>
    <rdfs:label xml:lang="de">E30 Recht</rdfs:label>
    <rdfs:label xml:lang="el">E30 Δικαίωμα</rdfs:label>
    <rdfs:label xml:lang="fr">E30 Droit</rdfs:label>
    <rdfs:label xml:lang="pt">E30 Direitos</rdfs:label>
    <rdfs:label xml:lang="ru">E30 Право</rdfs:label>
    <rdfs:label xml:lang="zh">E30 权限</rdfs:label>
    <skos:notation>E30</skos:notation>
    <rdfs:subClassOf rdf:resource="E89_Propositional_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P104i_applies_to"/>
        <owl:someValuesFrom rdf:resource="E72_Legal_Object"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises legal privileges concerning material and immaterial things or their derivatives. 
These include reproduction and property rights.

Examples:
- copyright held by ISO on ISO/CD 21127
- ownership of the “Mona Lisa” by the museum of the Louvre, Paris, France

In First Order Logic:
- E30(x) ⇒ E89(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E30_Right"/>
  </owl:Class>
  <owl:Class rdf:about="E31_Document">
    <rdfs:label xml:lang="en">E31 Document</rdfs:label>
    <rdfs:label xml:lang="de">E31 Dokument</rdfs:label>
    <rdfs:label xml:lang="el">E31 Τεκμήριο</rdfs:label>
    <rdfs:label xml:lang="fr">E31 Document</rdfs:label>
    <rdfs:label xml:lang="pt">E31 Documento</rdfs:label>
    <rdfs:label xml:lang="ru">E31 Докумeнт</rdfs:label>
    <rdfs:label xml:lang="zh">E31 文献</rdfs:label>
    <skos:notation>E31</skos:notation>
    <rdfs:subClassOf rdf:resource="E73_Information_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P70_documents"/>
        <owl:someValuesFrom rdf:resource="E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable immaterial items that make propositions about reality.
These propositions may be expressed in text, graphics, images, audiograms, videograms, or by other similar means. Documentation databases are regarded as instances of E31 Document. This class should not be confused with the concept “document” in Information Technology, which is compatible with E73 Information Object.

Examples:
- the Encyclopaedia Britannica (E32) (Kogan, 1958)
- the image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E36)
- Domesday Book [a manuscript record of the "Great Survey" of much of England and parts of Wales completed in 1086 by order of King William the Conqueror] (Hallam 1986)

In First Order Logic:
- E31(x) ⇒ E73(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E31_Document"/>
  </owl:Class>
  <owl:Class rdf:about="E32_Authority_Document">
    <rdfs:label xml:lang="en">E32 Authority Document</rdfs:label>
    <rdfs:label xml:lang="de">E32 Referenzdokument</rdfs:label>
    <rdfs:label xml:lang="el">E32 Πηγή Καθιερωμένων Όρων</rdfs:label>
    <rdfs:label xml:lang="fr">E32 Document de référence</rdfs:label>
    <rdfs:label xml:lang="pt">E32 Documento de Referência</rdfs:label>
    <rdfs:label xml:lang="ru">E32 Официальный Докумeнт</rdfs:label>
    <rdfs:label xml:lang="zh">E32 规范文档</rdfs:label>
    <skos:notation>E32</skos:notation>
    <rdfs:subClassOf rdf:resource="E31_Document"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P71_lists"/>
        <owl:someValuesFrom rdf:resource="E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.

Examples:
- Webster's Dictionary (Herbert, 1994)
- Getty Art and Architecture Thesaurus (Getty Trust, 1990)
- the CIDOC Conceptual Reference Model (Gergatsoulis et al., 2010)

In First Order Logic:
- E32(x) ⇒ E31(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E32_Authority_Document"/>
  </owl:Class>
  <owl:Class rdf:about="E33_Linguistic_Object">
    <rdfs:label xml:lang="en">E33 Linguistic Object</rdfs:label>
    <rdfs:label xml:lang="de">E33 Sprachlicher Gegenstand</rdfs:label>
    <rdfs:label xml:lang="el">E33 Γλωσσικό Αντικείμενο</rdfs:label>
    <rdfs:label xml:lang="fr">E33 Objet linguistique</rdfs:label>
    <rdfs:label xml:lang="pt">E33 Objeto Lingüístico</rdfs:label>
    <rdfs:label xml:lang="ru">E33 Лингвистичeский Объeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E33 语言对象</rdfs:label>
    <skos:notation>E33</skos:notation>
    <rdfs:subClassOf rdf:resource="E73_Information_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P73i_is_translation_of"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P72_has_language"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable expressions in natural language or languages. 
Instances of E33 Linguistic Object can be expressed in many ways: e.g. as written texts, recorded speech, or sign language. However, the CIDOC CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CIDOC CRM. These should be modelled as instances of E73 Information Object.
In general, an instance of E33 Linguistic Object may also contain non-linguistic information, often of artistic or aesthetic value. Only in cases in which the content of an instance of E33 Linguistic Object can completely be expressed by a series of binary-encoded symbols, its content may be documented within a respective knowledge base by the property P190 has symbolic content: E62 String. Otherwise, it should be understood as an identifiable digital resource only available independently from the respective knowledge base. 
In other cases, such as pages of an illuminated manuscript or recordings containing speech in a language supported by a writing system, the linguistic part of the content of an instance of E33 Linguistic Object may be documented within a respective knowledge base in a note by P3 has note: E62 String. Otherwise, it may be described using the property P165 incorporates (is incorporated in): E73 Information Object as a different object with its own identity.

Examples:
- the text of the Ellesmere Chaucer manuscript (Hilmo, 2019)
- the lyrics of the song “Blue Suede Shoes” (Cooper, 2008)
- the text of the “Jabberwocky” by Lewis Carroll (Carroll, 1981)
- the text of “Doktoro Jekyll kaj Sinjoro Hyde” [an Esperanto translation of Dr. Jekyll and Mr. Hyde]. (Stevenson, Morrison and Mann, 1909)
- the free dialog in the local dialect recorded in 1958, Telemark, Norway stored on tape or.7-89.s1 (00.15:46-00:34), The Language Collection at the University Library in Bergen, Norway (verified on 2020)

In First Order Logic:
- E33(x) ⇒ E73(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E33_Linguistic_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E33_E41_Linguistic_Appellation">
    <rdfs:label xml:lang="en">E33_E41 Linguistic Appellation</rdfs:label>
    <skos:notation>E33_E41</skos:notation>
    <rdfs:subClassOf rdf:resource="E33_Linguistic_Object"/>
    <rdfs:subClassOf rdf:resource="E41_Appellation"/>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E33_E41_Linguistic_Appellation"/>
  </owl:Class>
  <owl:Class rdf:about="E34_Inscription">
    <rdfs:label xml:lang="en">E34 Inscription</rdfs:label>
    <rdfs:label xml:lang="de">E34 Inschrift</rdfs:label>
    <rdfs:label xml:lang="el">E34 Επιγραφή</rdfs:label>
    <rdfs:label xml:lang="fr">E34 Inscription</rdfs:label>
    <rdfs:label xml:lang="pt">E34 Inscrição</rdfs:label>
    <rdfs:label xml:lang="ru">E34 Надпись</rdfs:label>
    <rdfs:label xml:lang="zh">E34 题识</rdfs:label>
    <skos:notation>E34</skos:notation>
    <rdfs:subClassOf rdf:resource="E33_Linguistic_Object"/>
    <rdfs:subClassOf rdf:resource="E37_Mark"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises recognisable texts that can be attached to instances of E24 Physical Human-Made Thing. 
The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class is not intended to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CIDOC CRM as instances of E24 Physical Human-Made Thing.
The relationship of a physical copy of a book to the text it contains is modelled using E18 Physical Thing. P128 carries (is carried by): E33 Linguistic Object.

Examples:
- “keep off the grass” [on a sign stuck in the lawn of the quad of Balliol College, Oxford, UK]
- the text published in Corpus Inscriptionum Latinarum V 895 (Mommsen, 1872)
- “Kilroy was here”

In First Order Logic:
- E34(x) ⇒ E33(x)
- E34(x) ⇒ E37(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E34_Inscription"/>
  </owl:Class>
  <owl:Class rdf:about="E35_Title">
    <rdfs:label xml:lang="en">E35 Title</rdfs:label>
    <rdfs:label xml:lang="de">E35 Titel</rdfs:label>
    <rdfs:label xml:lang="el">E35 Τίτλος</rdfs:label>
    <rdfs:label xml:lang="fr">E35 Titre</rdfs:label>
    <rdfs:label xml:lang="pt">E35 Título</rdfs:label>
    <rdfs:label xml:lang="ru">E35 Названиe</rdfs:label>
    <rdfs:label xml:lang="zh">E35 题名</rdfs:label>
    <skos:notation>E35</skos:notation>
    <rdfs:subClassOf rdf:resource="E33_Linguistic_Object"/>
    <rdfs:subClassOf rdf:resource="E41_Appellation"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the textual strings that within a cultural context can be clearly identified as titles due to their form. Being a subclass of E41 Appellation, E35 Title can only be used when such a string is actually used as a title of a work, such as a text, an artwork, or a piece of music.
Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting”, or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group.
This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.

Examples:
- “The Merchant of Venice” (McCullough, 2005)
- “Mona Lisa” (Mohen, Menu and Mottin, 2006)
- “La Pie” (Bortolatto, 1981)
- “Lucy in the Sky with Diamonds” (Lennon, 1967)

In First Order Logic:
- E35(x) ⇒ E33(x)
- E35(x) ⇒ E41(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E35_Title"/>
  </owl:Class>
  <owl:Class rdf:about="E36_Visual_Item">
    <rdfs:label xml:lang="en">E36 Visual Item</rdfs:label>
    <rdfs:label xml:lang="de">E36 Bildliches</rdfs:label>
    <rdfs:label xml:lang="el">E36 Οπτικό Στοιχείο</rdfs:label>
    <rdfs:label xml:lang="fr">E36 Entité visuelle</rdfs:label>
    <rdfs:label xml:lang="pt">E36 Item Visual</rdfs:label>
    <rdfs:label xml:lang="ru">E36 Визуальный Прeдмeт</rdfs:label>
    <rdfs:label xml:lang="zh">E36 可视项</rdfs:label>
    <skos:notation>E36</skos:notation>
    <rdfs:subClassOf rdf:resource="E73_Information_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the intellectual or conceptual aspects of recognisable marks and images.
This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation, and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support.
The E36 Visual Item class provides a means of identifying and linking together instances of E24 Physical Human-Made Thing that carry the same visual symbols, marks, or images, etc. The property P62 depicts (is depicted by) between E24 Physical Human-Made Thing and the depicted subjects (E1 CRM Entity) can be regarded as 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 E1 CRM Entity, which in addition captures the optical features of the depiction.

Examples:
- the visual appearance of Monet’s “La Pie” (Bortolatto, 1981)
- the Coca-Cola logo (E34)
- the Chi-Rho (E37)
- the communist red star (E37)
- the surface shape of Auguste Rodin's statue "Le Penseur" [There exist more than 20 copies, even of different size. Therefore, this is a good example that it is only the common surface shape, an immaterial visual item, which justifies displaying these copies as works of Auguste Rodin. As usual practice, Rodin himself did not produce the bronze statue, but only the prototype model.]

In First Order Logic:
- E36(x) ⇒ E73(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E36_Visual_Item"/>
  </owl:Class>
  <owl:Class rdf:about="E37_Mark">
    <rdfs:label xml:lang="en">E37 Mark</rdfs:label>
    <rdfs:label xml:lang="de">E37 Marke</rdfs:label>
    <rdfs:label xml:lang="el">E37 Σήμανση</rdfs:label>
    <rdfs:label xml:lang="fr">E37 Marque</rdfs:label>
    <rdfs:label xml:lang="pt">E37 Marca</rdfs:label>
    <rdfs:label xml:lang="ru">E37 Знак</rdfs:label>
    <rdfs:label xml:lang="zh">E37 标记</rdfs:label>
    <skos:notation>E37</skos:notation>
    <rdfs:subClassOf rdf:resource="E36_Visual_Item"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises symbols, signs, signatures, or short texts applied to instances of E24 Physical Human-Made Thing by arbitrary techniques, often in order to indicate such things as creator, owner, dedications, purpose, or to communicate information generally. Instances of E37 Mark do not represent the actual image of a mark, but the abstract ideal (or archetype) as used for codification in reference documents forming cultural documentation. 
This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Human-Made Feature.

Examples:
- Minoan double axe mark (Lowe Fri, 2011)
- ©
- ☺

In First Order Logic:
- E37(x) ⇒ E36(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E37_Mark"/>
  </owl:Class>
  <owl:Class rdf:about="E39_Actor">
    <rdfs:label xml:lang="en">E39 Actor</rdfs:label>
    <rdfs:label xml:lang="de">E39 Akteur</rdfs:label>
    <rdfs:label xml:lang="el">E39 Δράστης</rdfs:label>
    <rdfs:label xml:lang="fr">E39 Actant</rdfs:label>
    <rdfs:label xml:lang="pt">E39 Agente</rdfs:label>
    <rdfs:label xml:lang="ru">E39 Дeйствующий Субъeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E39 参与者</rdfs:label>
    <skos:notation>E39</skos:notation>
    <rdfs:subClassOf rdf:resource="E77_Persistent_Item"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises people, either individually or in groups, who have the potential to perform intentional actions of kinds for which they can be held responsible.

Examples:
- London and Continental Railways (E74)
- the Governor of the Bank of England in 1975 (E21)
- Sir Ian McKellen (E21) (Gibson, 1986)

In First Order Logic:
- E39(x) ⇒ E77(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E39_Actor"/>
  </owl:Class>
  <owl:Class rdf:about="E41_Appellation">
    <rdfs:label xml:lang="en">E41 Appellation</rdfs:label>
    <rdfs:label xml:lang="de">E41 Benennung</rdfs:label>
    <rdfs:label xml:lang="el">E41 Ονομασία</rdfs:label>
    <rdfs:label xml:lang="fr">E41 Appellation</rdfs:label>
    <rdfs:label xml:lang="pt">E41 Designação</rdfs:label>
    <rdfs:label xml:lang="ru">E41 Обозначeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E41 称谓</rdfs:label>
    <skos:notation>E41</skos:notation>
    <rdfs:subClassOf rdf:resource="E90_Symbolic_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises all 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 within a certain context.
Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e. other instances of E41 Appellation that are regarded as equivalent, regardless of 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 of E1 CRM Entity, such as for instances of E52 Time-Span (for instance “dates”), E39 Actor, E53 Place or E28 Conceptual Object. Postal addresses and E-mail addresses are characteristic examples of identifiers used by services transporting things between clients.
Even numerically expressed identifiers for extents in space or time are also regarded as instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though they allow for determining some time or location by a known procedure starting from a reference point and by virtue of that fact play a double role as instances of E59 Primitive Value.
E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment.

Examples:
- “Martin”
- “Aquae Sulis Minerva”
- “the Merchant of Venice” (E35) (McCullough, 2005)
- “Spigelia marilandica (L.) L.” [not the species, just the name] (Hershberger, Robacker and Jenkins, 2015)
- “information science” [not the science itself, but the name used to refer to the subject matter in an English-speaking context]
- “安” [Chinese “an”, meaning “peace”]
- “6°5’29”N 45°12’13”W” [example of a spatial coordinate]
- “Black queen’s bishop 4” [chess coordinate, example of an identifier in a conceptual space (E89)]
- “19-MAR-1922” [example of date]
- “+41 22 418 5571” [example of contact point]
- “weasel@paveprime.com” [example of contact point]
- “CH-1211, Genève” [example of place appellation]
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan” [example of a postal address]
- “the poop deck of H.M.S Victory” [example of a section definition on a human-made object (E22)]
- “the Venus de Milo’s left buttock” [example of a section definition on a human-made object (E22)]

In First Order Logic:
- E41(x) ⇒ E90(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E41_Appellation"/>
  </owl:Class>
  <owl:Class rdf:about="E42_Identifier">
    <rdfs:label xml:lang="en">E42 Identifier</rdfs:label>
    <rdfs:label xml:lang="de">E42 Kennung</rdfs:label>
    <rdfs:label xml:lang="el">E42 Κωδικός Αναγνώρισης</rdfs:label>
    <rdfs:label xml:lang="fr">E42 Identifiant</rdfs:label>
    <rdfs:label xml:lang="pt">E42 Identificador de Objeto</rdfs:label>
    <rdfs:label xml:lang="ru">E42 Идeнтификатор</rdfs:label>
    <rdfs:label xml:lang="zh">E42 标识符</rdfs:label>
    <skos:notation>E42</skos:notation>
    <rdfs:subClassOf rdf:resource="E41_Appellation"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. Postal addresses, telephone numbers, URLs and e-mail addresses are characteristic examples of identifiers used by services transporting things between clients.
The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.

Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1” (fictitious)
- “ISSN 0041-5278” [Identifier for “The UNESCO Courier (Print)”]
- ISRC “FIFIN8900186” [Identifier for : Kraft (29 min 14 s) / Magnus Lindberg, comp. ; Toimii Ensemble ; Swedish Radio symphony orchestra ; Esa-Pekka Salonen, dir.]
- Shelf mark “Res 8 P 10” 
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules] (Reaney, 1974)
- “+41 22 418 5571”
- “ weasel@paveprime.com”
- “Rue David Dufour 5, CH-1211, Genève”
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”

In First Order Logic:
- E42(x) ⇒ E41(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E42_Identifier"/>
  </owl:Class>
  <owl:Class rdf:about="E52_Time-Span">
    <rdfs:label xml:lang="en">E52 Time-Span</rdfs:label>
    <rdfs:label xml:lang="de">E52 Zeitspanne</rdfs:label>
    <rdfs:label xml:lang="el">E52 Χρονικό Διάστημα</rdfs:label>
    <rdfs:label xml:lang="fr">E52 Intervalle temporel</rdfs:label>
    <rdfs:label xml:lang="pt">E52 Período de Tempo</rdfs:label>
    <rdfs:label xml:lang="ru">E52 Интeрвал Врeмeни</rdfs:label>
    <rdfs:label xml:lang="zh">E52 时段</rdfs:label>
    <skos:notation>E52</skos:notation>
    <rdfs:subClassOf rdf:resource="E1_CRM_Entity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P4i_is_time-span_of"/>
        <owl:someValuesFrom rdf:resource="E2_Temporal_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end, and a duration. 
Instances of E52 Time-Span have no semantic connotations about phenomena happening within the temporal extent they represent. They do not convey any meaning other than a positioning on the “time-line” of chronology. The actual extent of an instance of E52 Time-Span can be approximated by properties of E52 Time-Span giving inner and outer bounds in the form of dates (instances of E61 Time Primitive). Comparing knowledge about time-spans is fundamental for chronological reasoning.
Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr &amp; 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 people 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 &amp; Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span. 
When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known.

Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 to 16h22 4(th) July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- the time-span of the Ming Dynasty (Chan, 2011)

In First Order Logic:
- E52(x) ⇒ E1(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span"/>
  </owl:Class>
  <owl:Class rdf:about="E53_Place">
    <rdfs:label xml:lang="en">E53 Place</rdfs:label>
    <rdfs:label xml:lang="de">E53 Ort</rdfs:label>
    <rdfs:label xml:lang="el">E53 Τόπος</rdfs:label>
    <rdfs:label xml:lang="fr">E53 Lieu</rdfs:label>
    <rdfs:label xml:lang="pt">E53 Local</rdfs:label>
    <rdfs:label xml:lang="ru">E53 Мeсто</rdfs:label>
    <rdfs:label xml:lang="zh">E53 地点</rdfs:label>
    <skos:notation>E53</skos:notation>
    <rdfs:subClassOf rdf:resource="E1_CRM_Entity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P59i_is_located_on_or_within"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises extents in the natural space where people live, 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, people 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, i.e. H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for).

Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring (fictitious)
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -&gt; &lt;- [the place between these two arrows in one of the reader's paper copy of this document. Each copy constitutes a different place of this spot.]

In First Order Logic:
- E53(x) ⇒ E1(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
  </owl:Class>
  <owl:Class rdf:about="E54_Dimension">
    <rdfs:label xml:lang="en">E54 Dimension</rdfs:label>
    <rdfs:label xml:lang="de">E54 Maß</rdfs:label>
    <rdfs:label xml:lang="el">E54 Μέγεθος</rdfs:label>
    <rdfs:label xml:lang="fr">E54 Dimension</rdfs:label>
    <rdfs:label xml:lang="pt">E54 Dimensão</rdfs:label>
    <rdfs:label xml:lang="ru">E54 Размeр</rdfs:label>
    <rdfs:label xml:lang="zh">E54 度量规格</rdfs:label>
    <skos:notation>E54</skos:notation>
    <rdfs:subClassOf rdf:resource="E1_CRM_Entity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P91_has_unit"/>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values, etc.
An instance of E54 Dimension represents the 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. Thermoluminescence dating and Rehydroxylation [RHX] dating are different dimensions of temporal distance from now, even if they aim at dating the same object. The method of determination should be expressed using the property P2 has type (is type of). Note that simple terms such as “diameter” or “length” are normally insufficient to unambiguously describe a respective dimension. In contrast, “maximum linear extent” may be sufficient.
The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension adequate to the precision of the applied method of determination. If the respective quantity belongs to a non-discrete space according to the laws of physics, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that comparability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension, as appropriate.

Examples:
- the weight of the Luxor Obelisk [250 metric tons]
- the vertical height of the statue of David by Michelangelo [5.17 metres]
- the weight of the Great Star of Africa diamond [530.2 carats]
- the calibrated C14 date for the Shroud of Turin [AD1262-1312, 1303-1384]
- the horizontal diameter of the Stonehenge Sarsen Circle [33 metres] (Pryor, 2016)
- the length of the sides of the Great Pyramid at Giza [230.34 metres] (Lehner and Hawass, 2017)
- the duration of the time-span of the Battle of Issos/Issus on 15(th) November 333 B.C.E. [less than 12 hours] (Howard, 2012)
- Christie’s hammer price, in British Pounds, for Vincent van Gogh's "Still Life: Vase with Fifteen Sunflowers" in London on 30(th) March 1987 (E97) [24.75 million GBP (British Pounds)]

In First Order Logic:
- E54(x) ⇒ E1(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
  </owl:Class>
  <owl:Class rdf:about="E55_Type">
    <rdfs:label xml:lang="en">E55 Type</rdfs:label>
    <rdfs:label xml:lang="de">E55 Typus</rdfs:label>
    <rdfs:label xml:lang="el">E55 Τύπος</rdfs:label>
    <rdfs:label xml:lang="fr">E55 Type</rdfs:label>
    <rdfs:label xml:lang="pt">E55 Tipo</rdfs:label>
    <rdfs:label xml:lang="ru">E55 Tип</rdfs:label>
    <rdfs:label xml:lang="zh">E55 类型</rdfs:label>
    <skos:notation>E55</skos:notation>
    <rdfs:subClassOf rdf:resource="E28_Conceptual_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P135i_was_created_by"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts, in contrast to instances of E41 Appellation which are used to name instances of CIDOC CRM classes. 
E55 Type provides an interface to domain specific ontologies and thesauri. These can be represented in the CIDOC CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term): E55 Type. Such hierarchies may be extended with additional properties.

Examples:
- weight, length, depth [types for instances of E54 Dimension]
- portrait, sketch, animation [types for instances of E36 Visual Item]
- French, English, German [types for instances of E56 Language]
- excellent, good, poor [types for instances of E3 Condition State]
- Ford Model T, chop stick [types for instances of E22 Human-Made Object]
- cave, doline, scratch [types for instances of E26 Physical Feature]
- poem, short story [types for instances of E33 Linguistic Object]
- wedding, earthquake, skirmish [types for instances of E5 Event]

In First Order Logic:
- E55(x) ⇒ E28(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
  </owl:Class>
  <owl:Class rdf:about="E56_Language">
    <rdfs:label xml:lang="en">E56 Language</rdfs:label>
    <rdfs:label xml:lang="de">E56 Sprache</rdfs:label>
    <rdfs:label xml:lang="el">E56 Γλώσσα</rdfs:label>
    <rdfs:label xml:lang="fr">E56 Langue</rdfs:label>
    <rdfs:label xml:lang="pt">E56 Língua</rdfs:label>
    <rdfs:label xml:lang="ru">E56 Язык</rdfs:label>
    <rdfs:label xml:lang="zh">E56 语种</rdfs:label>
    <skos:notation>E56</skos:notation>
    <rdfs:subClassOf rdf:resource="E55_Type"/>
    <rdfs:comment xml:lang="en">Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g. “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology should be used to denote instances of E56 Language, such as those defined in ISO 639-3:2007 and later versions.

Examples:
- ell [Greek] 
- eng [English] 
- epo [Esperanto] 
- spa [Spanish] 
- fra [French]

In First Order Logic:
- E56(x) ⇒ E55(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E56_Language"/>
  </owl:Class>
  <owl:Class rdf:about="E57_Material">
    <rdfs:label xml:lang="en">E57 Material</rdfs:label>
    <rdfs:label xml:lang="de">E57 Material</rdfs:label>
    <rdfs:label xml:lang="el">E57 Υλικό</rdfs:label>
    <rdfs:label xml:lang="fr">E57 Matériau</rdfs:label>
    <rdfs:label xml:lang="pt">E57 Material</rdfs:label>
    <rdfs:label xml:lang="ru">E57 Матeриал</rdfs:label>
    <rdfs:label xml:lang="zh">E57 材质</rdfs:label>
    <skos:notation>E57</skos:notation>
    <rdfs:subClassOf rdf:resource="E55_Type"/>
    <rdfs:comment xml:lang="en">Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials. 
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of (forms part of): E18 Physical Thing).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g. “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology should be used.

Examples:
- brick (Gurcke, 1987)
- gold (Watson, 1990)
- aluminium (Norman, 1986)
- polycarbonate (Mhaske, 2011)
- resin (Barton, 1992)

In First Order Logic:
- E57(x) ⇒ E55(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E57_Material"/>
  </owl:Class>
  <owl:Class rdf:about="E58_Measurement_Unit">
    <rdfs:label xml:lang="en">E58 Measurement Unit</rdfs:label>
    <rdfs:label xml:lang="de">E58 Maßeinheit</rdfs:label>
    <rdfs:label xml:lang="el">E58 Μονάδα Μέτρησης</rdfs:label>
    <rdfs:label xml:lang="fr">E58 Unité de mesure</rdfs:label>
    <rdfs:label xml:lang="pt">E58 Unidade de Medida</rdfs:label>
    <rdfs:label xml:lang="ru">E58 Eдиница Измeрeния</rdfs:label>
    <rdfs:label xml:lang="zh">E58 测量单位</rdfs:label>
    <skos:notation>E58</skos:notation>
    <rdfs:subClassOf rdf:resource="E55_Type"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P91i_is_unit_of"/>
        <owl:someValuesFrom rdf:resource="E54_Dimension"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc. 
This type is used categorically in the model without reference to instances of it, i.e. the model does not foresee the description of instances of instances of E58 Measurement Unit, e.g. “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible, such as those defined by ISO80000:2009. Archaic Measurement Units used in historical records should be preserved.

Examples:
- cm [centimetre]
- km [kilometre]
- m [metre]
- m/s [metres per second] (Hau et al., 1999)
- A [ampere]
- GRD [Greek Drachma] (E98) (Daniel, 2014)
- C [degrees centigrade] (Beckman, 1998)

In First Order Logic:
- E58(x) ⇒ E55(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E58_Measurement_Unit"/>
  </owl:Class>
  <owl:Class rdf:about="E63_Beginning_of_Existence">
    <rdfs:label xml:lang="en">E63 Beginning of Existence</rdfs:label>
    <rdfs:label xml:lang="de">E63 Daseinsbeginn</rdfs:label>
    <rdfs:label xml:lang="el">E63 Αρχή Ύπαρξης</rdfs:label>
    <rdfs:label xml:lang="fr">E63 Début d’existence</rdfs:label>
    <rdfs:label xml:lang="pt">E63 Início da Existência</rdfs:label>
    <rdfs:label xml:lang="ru">E63 Начало Сущeствования</rdfs:label>
    <rdfs:label xml:lang="zh">E63 初始</rdfs:label>
    <skos:notation>E63</skos:notation>
    <rdfs:subClassOf rdf:resource="E5_Event"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P92_brought_into_existence"/>
        <owl:someValuesFrom rdf:resource="E77_Persistent_Item"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises events that bring into existence any instance of E77 Persistent Item. 
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for both a terminus post quem and a terminus ante quem.

Examples:
- the birth of my child (E67) (fictitious)
- the birth of Snoopy, my dog (fictitious)
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower (E12) (Tissandier, 1889)

In First Order Logic:
- E63(x) ⇒ E5(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E63_Beginning_of_Existence"/>
  </owl:Class>
  <owl:Class rdf:about="E64_End_of_Existence">
    <rdfs:label xml:lang="en">E64 End of Existence</rdfs:label>
    <rdfs:label xml:lang="de">E64 Daseinsende</rdfs:label>
    <rdfs:label xml:lang="el">E64 Τέλος Ύπαρξης</rdfs:label>
    <rdfs:label xml:lang="fr">E64 Fin d’existence</rdfs:label>
    <rdfs:label xml:lang="pt">E64 Fim da Existência</rdfs:label>
    <rdfs:label xml:lang="ru">E64 Конeц Сущeствования</rdfs:label>
    <rdfs:label xml:lang="zh">E64 结束</rdfs:label>
    <skos:notation>E64</skos:notation>
    <rdfs:subClassOf rdf:resource="E5_Event"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P93_took_out_of_existence"/>
        <owl:someValuesFrom rdf:resource="E77_Persistent_Item"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises events that end the existence of any instance of E77 Persistent Item. 
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook both a terminus post quem and a 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.

Examples:
- the death of Snoopy, my dog (fictitious)
- the melting of the snowman (E6)
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356 BC (E7, E6) (Trell, 1945)

In First Order Logic:
- E64(x) ⇒ E5(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E64_End_of_Existence"/>
  </owl:Class>
  <owl:Class rdf:about="E65_Creation">
    <rdfs:label xml:lang="en">E65 Creation</rdfs:label>
    <rdfs:label xml:lang="de">E65 Begriffliche Schöpfung</rdfs:label>
    <rdfs:label xml:lang="el">E65 Δημιουργία</rdfs:label>
    <rdfs:label xml:lang="fr">E65 Création</rdfs:label>
    <rdfs:label xml:lang="pt">E65 Criação</rdfs:label>
    <rdfs:label xml:lang="ru">E65 Созданиe</rdfs:label>
    <rdfs:label xml:lang="zh">E65 创建</rdfs:label>
    <skos:notation>E65</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P94_has_created"/>
        <owl:someValuesFrom rdf:resource="E28_Conceptual_Object"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types, etc.

Examples:
- the framing of the U.S. Constitution (Farrand, 1913)
- the drafting of U.N. Resolution 1441 (United Nations Security Council, 2002)

In First Order Logic:
- E65(x) ⇒ E7(x)
- E65(x) ⇒ E63(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E65_Creation"/>
  </owl:Class>
  <owl:Class rdf:about="E66_Formation">
    <rdfs:label xml:lang="en">E66 Formation</rdfs:label>
    <rdfs:label xml:lang="de">E66 Gruppenbildung</rdfs:label>
    <rdfs:label xml:lang="el">E66 Συγκρότηση Ομάδας</rdfs:label>
    <rdfs:label xml:lang="fr">E66 Formation</rdfs:label>
    <rdfs:label xml:lang="pt">E66 Formação</rdfs:label>
    <rdfs:label xml:lang="ru">E66 Формированиe</rdfs:label>
    <rdfs:label xml:lang="zh">E66 组成</rdfs:label>
    <skos:notation>E66</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P95_has_formed"/>
        <owl:someValuesFrom rdf:resource="E74_Group"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation, or nation. 
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.

Examples:
- the formation of the CIDOC CRM Special Interest Group in 2000
- the formation of the Soviet Union (Pipes, 1964)
- the conspiring of the murderers of Caesar (Irwin, 1935)

In First Order Logic:
- E66(x) ⇒ E7(x)
- E66(x) ⇒ E63(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E66_Formation"/>
  </owl:Class>
  <owl:Class rdf:about="E67_Birth">
    <rdfs:label xml:lang="en">E67 Birth</rdfs:label>
    <rdfs:label xml:lang="de">E67 Geburt</rdfs:label>
    <rdfs:label xml:lang="el">E67 Γέννηση</rdfs:label>
    <rdfs:label xml:lang="fr">E67 Naissance</rdfs:label>
    <rdfs:label xml:lang="pt">E67 Nascimento</rdfs:label>
    <rdfs:label xml:lang="ru">E67 Рождeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E67 出生</rdfs:label>
    <skos:notation>E67</skos:notation>
    <rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P98_brought_into_life"/>
        <owl:someValuesFrom rdf:resource="E21_Person"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P97_from_father"/>
        <owl:someValuesFrom rdf:resource="E21_Person"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P96_by_mother"/>
        <owl:someValuesFrom rdf:resource="E21_Person"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living being.) 
Twins, triplets, etc. are brought into life by the same instance of E67 Birth. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood since the advent of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth.

Examples:
- the birth of Alexander the Great (Stoneman, 2004)

In First Order Logic:
- E67(x) ⇒ E63(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E67_Birth"/>
  </owl:Class>
  <owl:Class rdf:about="E68_Dissolution">
    <rdfs:label xml:lang="en">E68 Dissolution</rdfs:label>
    <rdfs:label xml:lang="de">E68 Gruppenauflösung</rdfs:label>
    <rdfs:label xml:lang="el">E68 Διάλυση Ομάδας</rdfs:label>
    <rdfs:label xml:lang="fr">E68 Dissolution</rdfs:label>
    <rdfs:label xml:lang="pt">E68 Dissolução</rdfs:label>
    <rdfs:label xml:lang="ru">E68 Роспуск</rdfs:label>
    <rdfs:label xml:lang="zh">E68 解散</rdfs:label>
    <skos:notation>E68</skos:notation>
    <rdfs:subClassOf rdf:resource="E64_End_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P99_dissolved"/>
        <owl:someValuesFrom rdf:resource="E74_Group"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the events that result in the formal or informal termination of an instance of E74 Group. 
If the dissolution was deliberate, the Dissolution event should also be instantiated as an instance of E7 Activity.

Examples:
- the fall of the Roman Empire (Whittington, 1964)
- the liquidation of Enron Corporation (Atlas, 2001)

In First Order Logic:
- E68(x) ⇒ E64(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E68_Dissolution"/>
  </owl:Class>
  <owl:Class rdf:about="E69_Death">
    <rdfs:label xml:lang="en">E69 Death</rdfs:label>
    <rdfs:label xml:lang="de">E69 Tod</rdfs:label>
    <rdfs:label xml:lang="el">E69 Θάνατος</rdfs:label>
    <rdfs:label xml:lang="fr">E69 Mort</rdfs:label>
    <rdfs:label xml:lang="pt">E69 Morte</rdfs:label>
    <rdfs:label xml:lang="ru">E69 Смeрть</rdfs:label>
    <rdfs:label xml:lang="zh">E69 死亡</rdfs:label>
    <skos:notation>E69</skos:notation>
    <rdfs:subClassOf rdf:resource="E64_End_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P100_was_death_of"/>
        <owl:someValuesFrom rdf:resource="E21_Person"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the deaths of human beings. 
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented as instances of E64 End of Existence.

Examples:
- the murder of Julius Caesar (E69, E7) (Irwin, 1935)
- the death of Senator Paul Wellstone (Monast and Tao, 2002)

In First Order Logic:
- E69(x) ⇒ E64(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E69_Death"/>
  </owl:Class>
  <owl:Class rdf:about="E70_Thing">
    <rdfs:label xml:lang="en">E70 Thing</rdfs:label>
    <rdfs:label xml:lang="de">E70 Sache</rdfs:label>
    <rdfs:label xml:lang="el">E70 Πράγμα</rdfs:label>
    <rdfs:label xml:lang="fr">E70 Chose</rdfs:label>
    <rdfs:label xml:lang="pt">E70 Coisa</rdfs:label>
    <rdfs:label xml:lang="ru">E70 Вeщь</rdfs:label>
    <rdfs:label xml:lang="zh">E70 事物</rdfs:label>
    <skos:notation>E70</skos:notation>
    <rdfs:subClassOf rdf:resource="E77_Persistent_Item"/>
    <rdfs:comment xml:lang="en">Scope note:
This general class comprises discrete, identifiable, instances of E77 Persistent Item that are documented as single units, that either consist of matter or depend on being carried by matter and are characterized by relative stability. 
They may be intellectual products or physical things. They may, for instance, have a solid physical form, an electronic encoding, or they may be a logical concept or structure.

Examples:
- my photograph collection (E78) (fictitious)
- the bottle of milk in my refrigerator (E22) (fictitious)
- the Riss A1 plan of the Straßburger Münster (French: Cathédrale Notre-Dame de Strasbourg) (E29) (Liess, R., 1985)
- the thing on the top of Otto Hahn’s desk (E19)
- the form of the no-smoking sign (E36)
- the cave of Dirou, Mani, Greece (E26) (Psimenos, 2005)

In First Order Logic:
- E70(x) ⇒ E77(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E70_Thing"/>
  </owl:Class>
  <owl:Class rdf:about="E71_Human-Made_Thing">
    <rdfs:label xml:lang="en">E71 Human-Made Thing</rdfs:label>
    <rdfs:label xml:lang="fr">E71 Chose élaborée par l’humain</rdfs:label>
    <rdfs:label xml:lang="ru">E71 Рукотворный Прeдмeт</rdfs:label>
    <skos:notation>E71</skos:notation>
    <rdfs:subClassOf rdf:resource="E70_Thing"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises discrete, identifiable human-made items that are documented as single units. 
These items are either intellectual products or human-made physical things, and are characterized by relative stability. They may, for instance, have a solid physical form, an electronic encoding, or they may be logical concepts or structures.

Examples:
- Beethoven’s 5(th) Symphony (E73) (Lockwood, 2015)
- Michelangelo’s David (E22) (Paoletti and Bagemihl, 2015)
- Einstein’s Theory of General Relativity (E89) (Hartle, 2003)
- the taxon ‘Fringilla coelebs Linnaeus,1758’ (E55) (Sinkevicius and Narusevicius, 2002)

In First Order Logic:
- E71(x) ⇒ E70(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E71_Human-Made_Thing"/>
  </owl:Class>
  <owl:Class rdf:about="E72_Legal_Object">
    <rdfs:label xml:lang="en">E72 Legal Object</rdfs:label>
    <rdfs:label xml:lang="de">E72 Rechtsobjekt</rdfs:label>
    <rdfs:label xml:lang="el">E72 Νομικό Αντικείμενο</rdfs:label>
    <rdfs:label xml:lang="fr">E72 Objet juridique</rdfs:label>
    <rdfs:label xml:lang="pt">E72 Objeto Jurídico</rdfs:label>
    <rdfs:label xml:lang="ru">E72 Объeкт Права</rdfs:label>
    <rdfs:label xml:lang="zh">E72 法律对象</rdfs:label>
    <skos:notation>E72</skos:notation>
    <rdfs:subClassOf rdf:resource="E70_Thing"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P104_is_subject_to"/>
        <owl:someValuesFrom rdf:resource="E30_Right"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P105_right_held_by"/>
        <owl:someValuesFrom rdf:resource="E39_Actor"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied. 
This is generally true for all instances of E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of an instance of E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CIDOC CRM.

Examples:
- the Cullinan diamond (E19) (Scarratt and Shor, 2006)
- definition of the CIDOC Conceptual Reference Model Version 5.0.4 (E73) (ISO 21127: 2014)

In First Order Logic:
- E72(x) ⇒ E70(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E72_Legal_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E73_Information_Object">
    <rdfs:label xml:lang="en">E73 Information Object</rdfs:label>
    <rdfs:label xml:lang="de">E73 Informationsgegenstand</rdfs:label>
    <rdfs:label xml:lang="el">E73 Πληροφοριακό Αντικείμενο</rdfs:label>
    <rdfs:label xml:lang="fr">E73 Objet informationnel</rdfs:label>
    <rdfs:label xml:lang="pt">E73 Objeto de Informação</rdfs:label>
    <rdfs:label xml:lang="ru">E73 Информационный Объeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E73 信息对象</rdfs:label>
    <skos:notation>E73</skos:notation>
    <rdfs:subClassOf rdf:resource="E89_Propositional_Object"/>
    <rdfs:subClassOf rdf:resource="E90_Symbolic_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable immaterial items, such as poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. The encoding structure known as a “named graph” also falls under this class, so that each “named graph” is an instance of E73 Information Object.
An instance of E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously.
Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression.

Examples:
- image BM000038850.JPG from the Clayton Herbarium in London (E31) (Natural History Museum, 2021)
- E. A. Poe's “The Raven” (Poe, 1869)
- the movie “The Seven Samurai” by Akira Kurosawa (Mellen, 2002)
- the text of Huray describing the Maxwell Equations (Huray, 2010)
- the Getty AAT as published as Linked Open Data, accessed 1/10/2014

In First Order Logic:
- E73(x) ⇒ E89(x)
- E73(x) ⇒ E90(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E74_Group">
    <rdfs:label xml:lang="en">E74 Group</rdfs:label>
    <rdfs:label xml:lang="de">E74 Menschliche Gruppe</rdfs:label>
    <rdfs:label xml:lang="el">E74 Ομάδα</rdfs:label>
    <rdfs:label xml:lang="fr">E74 Groupe</rdfs:label>
    <rdfs:label xml:lang="pt">E74 Grupo</rdfs:label>
    <rdfs:label xml:lang="ru">E74 Группа</rdfs:label>
    <rdfs:label xml:lang="zh">E74 团体</rdfs:label>
    <skos:notation>E74</skos:notation>
    <rdfs:subClassOf rdf:resource="E39_Actor"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P144i_gained_member_by"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">2</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P95i_was_formed_by"/>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P146i_lost_member_by"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">0</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P107_has_current_or_former_member"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">2</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises any gatherings or organizations of human individuals or groups that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. In such cases, it may happen that the group never had more than one member. A joint pseudonym (i.e. a name that seems indicative of an individual but that is actually used as a persona by two or more people) is a particular case of E74 Group.
A gathering of people becomes an instance of E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modelled as membership in an instance of E74 Group. Married couples and other concepts of family are regarded as particular examples of E74 Group.

Examples:
- the Impressionists (Wilson, 1994)
- the Navajo (Correll, 1972)
- the Greeks (Williams, 1993)
- the peace protestors in New York City on 15(th) February 2003
- Exxon-Mobil (Raymond, 2006)
- King Solomon and his wives (Thieberger, 1947)
- the President of the Swiss Confederation
- Nicolas Bourbaki [the collective pseudonym of a group of mathematicians, predominantly French alumni of the École normale supérieure] (Aczel, 2007)
- Betty Crocker (Crocker, 2012)
- Ellery Queen [Ellery Queen is a pseudonym created in 1929 by American crime fiction writers Frederic Dannay and Manfred Bennington Lee.] (Wheat, 2005)
- Greenpeace
- Paveprime Ltd
- the National Museum of Denmark

In First Order Logic:
- E74(x) ⇒ E39(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E74_Group"/>
  </owl:Class>
  <owl:Class rdf:about="E77_Persistent_Item">
    <rdfs:label xml:lang="en">E77 Persistent Item</rdfs:label>
    <rdfs:label xml:lang="de">E77 Seiendes</rdfs:label>
    <rdfs:label xml:lang="el">E77 Ον</rdfs:label>
    <rdfs:label xml:lang="fr">E77 Entité persistante</rdfs:label>
    <rdfs:label xml:lang="pt">E77 Entidade Persistente</rdfs:label>
    <rdfs:label xml:lang="ru">E77 Постоянная Сущность</rdfs:label>
    <rdfs:label xml:lang="zh">E77 持久项</rdfs:label>
    <skos:notation>E77</skos:notation>
    <rdfs:subClassOf rdf:resource="E1_CRM_Entity"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises items that have persistent characteristics of structural nature substantially related to their identity and their integrity, sometimes known as “endurants” in philosophy. Persistent Items may be physical entities, such as people, animals or things, conceptual entities such as ideas, concepts, products of the imagination or even names. 
Instances of E77 Persistent Item may be present or be part of interactions in different periods or events. They can repeatedly be recognized at disparate occasions during their existence by characteristics of structural nature. The respective characteristics need not be exactly the same during all the existence of an instance of E77 Persistent Item. Often, they undergo gradual change, still bearing some similarities with that of previous times, or disappear completely and new emerge. For instance, a person, from the time of being born on, will gradually change all its features and acquire new ones, such as a scar. Even the DNA in different body cells will develop defects and mutations. Nevertheless, relevant characteristics 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 exchange of parts and matter. On the opposite, the identity of a (version of a) text of a scientific publication is given by the exact arrangement of its relevant symbols. 
The main classes of objects that fall outside the scope of the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties. 
An instance of E77 Persistent Item does not require actual knowledge of the identifying features of the instance being currently known. There may be cases, where the actual identifying features of an instance of E77 Persistent Item are not decidable at a particular state of knowledge.

Examples:
- Leonardo da Vinci (E21) (Strano, 1953)
- Stonehenge (E24) (Pryor, 2016)
- the hole in the ozone layer (E4) (Hufford and Horwitz, 2005)
- the First Law of Thermodynamics (E89) (Craig and Gislason, 2002)
- the Bermuda Triangle (E53) (Dolan, 2005)

In First Order Logic:
- E77(x) ⇒ E1(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E77_Persistent_Item"/>
  </owl:Class>
  <owl:Class rdf:about="E78_Curated_Holding">
    <rdfs:label xml:lang="en">E78 Curated Holding</rdfs:label>
    <rdfs:label xml:lang="fr">E78 Collection</rdfs:label>
    <rdfs:label xml:lang="ru">E78 Отвeтствeнноe Хранeниe</rdfs:label>
    <skos:notation>E78</skos:notation>
    <rdfs:subClassOf rdf:resource="E24_Physical_Human-Made_Thing"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P109_has_current_or_former_curator"/>
        <owl:someValuesFrom rdf:resource="E39_Actor"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. Typical instances of curated holdings are museum collections, archives, library holdings and digital libraries. A digital library is regarded as an instance of E18 Physical Thing because it requires keeping physical carriers of the electronic content.
Items may be added or removed from an E78 Curated Holding in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Curated Holding who is often referred to using the name of the E78 Curated Holding (e.g. “The Wallace Collection decided…”). 
Collective objects in the general sense, like a tomb full of gifts, a folder with stamps, or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Curated Holding. This is because they form wholes, either because they are physically bound together or because they are kept together for their functionality.

Examples:
- the John Clayton Herbarium (Blake, 1918), (Natural History Museum, 2021)
- the Wallace Collection (Ingamells, 1990)
- Mikael Heggelund Foslie’s coralline red algae Herbarium at the Museum of Natural History and Archaeology, Trondheim, Norway (Woelkerling et al., 2005)
- the Digital Collections of the Munich DigitiZation Center (MDZ) accessible via https://www.digitale-sammlungen.de/ at least in January 2018.

In First Order Logic:
- E78(x) ⇒ E24(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E78_Curated_Holding"/>
  </owl:Class>
  <owl:Class rdf:about="E79_Part_Addition">
    <rdfs:label xml:lang="en">E79 Part Addition</rdfs:label>
    <rdfs:label xml:lang="de">E79 Teilhinzufügung</rdfs:label>
    <rdfs:label xml:lang="el">E79 Προσθήκη Μερών</rdfs:label>
    <rdfs:label xml:lang="fr">E79 Ajout d'élément</rdfs:label>
    <rdfs:label xml:lang="pt">E79 Adição de Parte</rdfs:label>
    <rdfs:label xml:lang="ru">E79 Добавлeниe Части</rdfs:label>
    <rdfs:label xml:lang="zh">E79 部分增加</rdfs:label>
    <skos:notation>E79</skos:notation>
    <rdfs:subClassOf rdf:resource="E11_Modification"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P110_augmented"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P111_added"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
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.

Examples:
- the setting of the Koh-I-Noor diamond into the crown of Queen Elizabeth the Queen Mother (Dalrymple, 2017)
- the addition of the painting “Room in Brooklyn” by Edward Hopper to the collection of the Museum of Fine Arts, Boston
- the attachment of the bronze hand on the tree forming the Alpi Marittime [ https://giuseppepenone.com/en/words/maritime-alps] (Mangini, 2010)

In First Order Logic:
- E79(x) ⇒ E11(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E79_Part_Addition"/>
  </owl:Class>
  <owl:Class rdf:about="E80_Part_Removal">
    <rdfs:label xml:lang="en">E80 Part Removal</rdfs:label>
    <rdfs:label xml:lang="de">E80 Teilentfernung</rdfs:label>
    <rdfs:label xml:lang="el">E80 Αφαίρεση Μερών</rdfs:label>
    <rdfs:label xml:lang="fr">E80 Retrait d'élément</rdfs:label>
    <rdfs:label xml:lang="pt">E80 Remoção de Parte</rdfs:label>
    <rdfs:label xml:lang="ru">E80 Удалeниe Части</rdfs:label>
    <rdfs:label xml:lang="zh">E80 部分去除</rdfs:label>
    <skos:notation>E80</skos:notation>
    <rdfs:subClassOf rdf:resource="E11_Modification"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P112_diminished"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P113_removed"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the activities that result in an instance of E18 Physical Thing being decreased by the removal of a part.
Typical scenarios include the detachment of an accessory, the removal of a component or part of a composite object, or the deaccessioning of an object from a curated collection, an instance of E78 Curated Holding. If the instance of E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an instance of E81 Transformation, i.e. a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be modelled as both an instance of E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewellery, or cultural artifacts being deaccessioned from different museum collections over their lifespan.

Examples:
- the removal of the Porite coral specimen from the Cocos Islands by Charles Darwin in April 1836 (Natural History Museum, 2021, b)
- the removal of the engine from my car (fictitious)
- the disposal of object number 1976:234 from the collection (fictitious)

In First Order Logic:
- E80(x) ⇒ E11(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E80_Part_Removal"/>
  </owl:Class>
  <owl:Class rdf:about="E81_Transformation">
    <rdfs:label xml:lang="en">E81 Transformation</rdfs:label>
    <rdfs:label xml:lang="de">E81 Umwandlung</rdfs:label>
    <rdfs:label xml:lang="el">E81 Μετατροπή</rdfs:label>
    <rdfs:label xml:lang="fr">E81 Transformation</rdfs:label>
    <rdfs:label xml:lang="pt">E81 Transformação</rdfs:label>
    <rdfs:label xml:lang="ru">E81 Трансформация</rdfs:label>
    <rdfs:label xml:lang="zh">E81 转变</rdfs:label>
    <skos:notation>E81</skos:notation>
    <rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence"/>
    <rdfs:subClassOf rdf:resource="E64_End_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P124_transformed"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P123_resulted_in"/>
        <owl:someValuesFrom rdf:resource="E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the events that result in the simultaneous destruction of one or more than one E18 Physical Thing and the creation of one or more than one E18 Physical Thing that preserves recognizable substance and structure from the first one(s) but has fundamentally different nature or identity.
Although the old and the new instances of E18 Physical Thing are treated as discrete entities having separate, unique identities, they are causally connected through the E81 Transformation; the destruction of the old E18 Physical Thing(s) directly causes the creation of the new one(s) using or preserving some relevant substance and structure. Instances of E81 Transformation are therefore distinct from re-classifications (documented using E17 Type Assignment) or modifications (documented using E11 Modification) of objects that do not fundamentally change their nature or identity. Characteristic cases are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimen in natural history.
Even though such instances of E81 Transformation are often motivated by a change of intended use, substantial material changes should justify the documentation of the result as a new instance of E18 Physical Thing and not just the change of function. The latter may be documented as an extended activity (instance of E7 Activity) of using it.

Examples:
- the mummification of Tut-Ankh-Amun (E81, E12) [the mummification of the body of the deceased is a human production process and simultaneously preserves structures of the body at and before death] (Carter and Mace 1977)
- the death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the Eruption of Mount Vesuvius (E69, E81)
- the transformation of the Hephaisteion temple in Athens, better known as “Theseion”, into a Christian church, dedicated to Saint George &lt;https://en.wikipedia.org/wiki/Saint_George&gt; around AD 700 (E81,E12) [which actually helped preserving part of the antique temple structure from 449BC]

In First Order Logic:
- E81(x) ⇒ E63(x)
- E81(x) ⇒ E64(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E81_Transformation"/>
  </owl:Class>
  <owl:Class rdf:about="E83_Type_Creation">
    <rdfs:label xml:lang="en">E83 Type Creation</rdfs:label>
    <rdfs:label xml:lang="de">E83 Typuserfindung</rdfs:label>
    <rdfs:label xml:lang="el">E83 Δημιουργία Τύπου</rdfs:label>
    <rdfs:label xml:lang="fr">E83 Création de type</rdfs:label>
    <rdfs:label xml:lang="pt">E83 Criação de Tipo</rdfs:label>
    <rdfs:label xml:lang="ru">E83 Созданиe Типа</rdfs:label>
    <rdfs:label xml:lang="zh">E83 类型创建</rdfs:label>
    <skos:notation>E83</skos:notation>
    <rdfs:subClassOf rdf:resource="E65_Creation"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P135_created_type"/>
        <owl:someValuesFrom rdf:resource="E55_Type"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises activities formally defining new types of items. 
It is typically a rigorous scholarly or scientific process that ensures a type is exhaustively described and appropriately named. In some cases, particularly in archaeology and the life sciences, E83 Type Creation requires the identification of an exemplary specimen and the publication of the type definition in an appropriate scholarly forum. The activity modelled as an instance of E83 Type Creation is central to research in the life sciences, where a type would be referred to as a “taxon,” the type description as a “protologue,” and the exemplary specimens as “original element” or “holotype”.

Examples:
- creation of the taxon Penicillium brefeldianum (Dodge, 1933)
- addition of class E85 Joining to the CIDOC CRM

In First Order Logic:
- E83(x) ⇒ E65(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E83_Type_Creation"/>
  </owl:Class>
  <owl:Class rdf:about="E85_Joining">
    <rdfs:label xml:lang="en">E85 Joining</rdfs:label>
    <rdfs:label xml:lang="de">E85 Beitritt</rdfs:label>
    <rdfs:label xml:lang="fr">E85 Adhésion</rdfs:label>
    <rdfs:label xml:lang="ru">E85 Вступлeниe</rdfs:label>
    <rdfs:label xml:lang="zh">E85 加入</rdfs:label>
    <skos:notation>E85</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P143_joined"/>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P144_joined_with"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the activities that result in an instance of E39 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party.
Typical scenarios include becoming a member of a social organisation, becoming an employee of a company, marriage, the adoption of a child by a family, and the inauguration of somebody into an official position.

Examples:
- the election of Sir Isaac Newton as Member of Parliament for the University of Cambridge to the Convention Parliament of 1689 (Gleick, 2003)
- the inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (Butson, 1986)
- the implementation of the membership treaty between EU and Denmark, 1(st) January 1993

In First Order Logic:
- E85(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E85_Joining"/>
  </owl:Class>
  <owl:Class rdf:about="E86_Leaving">
    <rdfs:label xml:lang="en">E86 Leaving</rdfs:label>
    <rdfs:label xml:lang="de">E86 Austritt</rdfs:label>
    <rdfs:label xml:lang="fr">E86 Départ</rdfs:label>
    <rdfs:label xml:lang="ru">E86 Выход</rdfs:label>
    <rdfs:label xml:lang="zh">E86 离开</rdfs:label>
    <skos:notation>E86</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P145_separated"/>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P146_separated_from"/>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party.
Typical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position.

Examples:
- the end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (Gleick, 2003)
- George Washington’s leaving office in 1797 (Jones, 1979)
- the implementation of the treaty regulating the termination of Greenland’s membership in EU between EU, Denmark and Greenland 1(st) February 1985

In First Order Logic:
- E86(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E86_Leaving"/>
  </owl:Class>
  <owl:Class rdf:about="E87_Curation_Activity">
    <rdfs:label xml:lang="en">E87 Curation Activity</rdfs:label>
    <rdfs:label xml:lang="de">E87 Kuratorische Tätigkeit</rdfs:label>
    <rdfs:label xml:lang="fr">E87 Activité curatoriale</rdfs:label>
    <rdfs:label xml:lang="ru">E87 Кураторство</rdfs:label>
    <rdfs:label xml:lang="zh">E87 管理</rdfs:label>
    <skos:notation>E87</skos:notation>
    <rdfs:subClassOf rdf:resource="E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P147_curated"/>
        <owl:someValuesFrom rdf:resource="E78_Curated_Holding"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the activities that contribute to the 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 such as 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 to form a collection is regarded as an instance of E12 Production Event, while the activities of evolving, preserving, and promoting a collection are regarded as instances of E87 Curation Activity.

Examples:
- the curation of Mikael Heggelund Foslie’s coralline red algae Herbarium 1876 to 1909 (when Foslie died), now at the Museum of Natural History and Archaeology, Norway (Woelkerling et al., 2005)

In First Order Logic:
- E87(x) ⇒ E7(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E87_Curation_Activity"/>
  </owl:Class>
  <owl:Class rdf:about="E89_Propositional_Object">
    <rdfs:label xml:lang="en">E89 Propositional Object</rdfs:label>
    <rdfs:label xml:lang="de">E89 Aussagenobjekt</rdfs:label>
    <rdfs:label xml:lang="fr">E89 Objet propositionnel</rdfs:label>
    <rdfs:label xml:lang="ru">E89 Пропозициональный Объeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E89 命题对象</rdfs:label>
    <skos:notation>E89</skos:notation>
    <rdfs:subClassOf rdf:resource="E28_Conceptual_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P148_has_component"/>
        <owl:someValuesFrom rdf:resource="E89_Propositional_Object"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P129i_is_subject_of"/>
        <owl:someValuesFrom rdf:resource="E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P67i_is_referred_to_by"/>
        <owl:someValuesFrom rdf:resource="E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse. 
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.

Examples:
- Maxwell’s Equations (Ball, 1962)
- the ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in Oxford edition
- the underlying prototype of any “no-smoking” sign (E36)
- the common ideas of the plots of the movie “The Seven Samurai” by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges (Mellen, 2002)
- the image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E36)
- the character “Little Red Riding Hood”, variants of which appear amongst others in Grimm brothers’ “Rotkäppchen”, other oral fairy tales and the film “Hoodwinked”
- the place “Havnor” as invented by Ursula K. Le Guin for her “Earthsea” book series, the related maps and appearing in derivative works based on these novels

In First Order Logic:
- E89(x) ⇒ E28(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E90_Symbolic_Object">
    <rdfs:label xml:lang="en">E90 Symbolic Object</rdfs:label>
    <rdfs:label xml:lang="de">E90 Symbolisches Objekt</rdfs:label>
    <rdfs:label xml:lang="fr">E90 Objet symbolique</rdfs:label>
    <rdfs:label xml:lang="ru">E90 Символичeский Объeкт</rdfs:label>
    <rdfs:label xml:lang="zh">E90 符号对象</rdfs:label>
    <skos:notation>E90</skos:notation>
    <rdfs:subClassOf rdf:resource="E28_Conceptual_Object"/>
    <rdfs:subClassOf rdf:resource="E72_Legal_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty rdf:resource="P106_is_composed_of"/>
        <owl:someValuesFrom rdf:resource="E90_Symbolic_Object"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code, or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note and its subproperty P190 has symbolic content allow for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. “bit”, “Latin character”, RGB pixel).

Examples:
- ‘ecognizabl’
- the “no-smoking” sign (E36)
- “BM000038850.JPG” (E41) [identifies a digital image] (Natural History Museum, 2021)
- image BM000038850.JPG from the Clayton Herbarium in London (E36) [depicts specimen of Verbesina virginica] (Natural History Museum, 2021)
- the distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E36)
- the Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition “La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi” (E33) (Petrocchi, 1967)

In First Order Logic:
- E90(x) ⇒ E28(x)
- E90(x) ⇒ E72(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E90_Symbolic_Object"/>
  </owl:Class>
  <owl:Class rdf:about="E92_Spacetime_Volume">
    <rdfs:label xml:lang="en">E92 Spacetime Volume</rdfs:label>
    <rdfs:label xml:lang="fr">E92 Volume spatio-temporel</rdfs:label>
    <rdfs:label xml:lang="ru">E92 Область Пространства-Врeмeни</rdfs:label>
    <skos:notation>E92</skos:notation>
    <rdfs:subClassOf rdf:resource="E1_CRM_Entity"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises 4-dimensional point sets (volumes) in physical spacetime (in contrast to mathematical models of it) regardless of 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.

Examples:
- the extent in space and time of the Event of Caesar’s murder (Irwin, 1935)
- where and when the carbon 14 dating of the “Schoeninger Speer II” in 1996 took place (Kouwenhoven, 1997)
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location (Goodwin, 2015)
- the extent in space and time defined by a polygon approximating the Danube river flood in Austria between 6(th) and 9(th) August 2002

In First Order Logic:
- E92(x) ⇒ E1(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume"/>
  </owl:Class>
  <owl:Class rdf:about="E93_Presence">
    <rdfs:label xml:lang="en">E93 Presence</rdfs:label>
    <rdfs:label xml:lang="fr">E93 Présence</rdfs:label>
    <rdfs:label xml:lang="ru">E93 Присутствиe</rdfs:label>
    <skos:notation>E93</skos:notation>
    <rdfs:subClassOf rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:comment xml:lang="en">Scope note:
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.

Examples:
- the Roman Empire on 19(th) August AD 14 (Clare and Edwards, 1992)
- Johann Joachim Winckelmann’s whereabouts in December 1775 (Leppmann, 1970)
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (Leppmann, 1970)

In First Order Logic:
- E93(x) ⇒ E92(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E93_Presence"/>
  </owl:Class>
  <owl:Class rdf:about="E96_Purchase">
    <rdfs:label xml:lang="en">E96 Purchase</rdfs:label>
    <rdfs:label xml:lang="fr">E96 Achat</rdfs:label>
    <rdfs:label xml:lang="ru">E96 Покупка</rdfs:label>
    <skos:notation>E96</skos:notation>
    <rdfs:subClassOf rdf:resource="E8_Acquisition"/>
    <rdfs:comment xml:lang="en">Scope note:
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.

Examples:
- the purchase of 10 okka of nails by the captain A. Syrmas on 18(th) September 1895 in Thessaloniki (Syrmas, 1896)

In First Order Logic:
- E96(x) ⇒ E8(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E96_Purchase"/>
  </owl:Class>
  <owl:Class rdf:about="E97_Monetary_Amount">
    <rdfs:label xml:lang="en">E97 Monetary Amount</rdfs:label>
    <rdfs:label xml:lang="fr">E97 Valeur monétaire</rdfs:label>
    <rdfs:label xml:lang="ru">E97 Дeнeжный Эквивалeнт</rdfs:label>
    <skos:notation>E97</skos:notation>
    <rdfs:subClassOf rdf:resource="E54_Dimension"/>
    <rdfs:comment xml:lang="en">Scope note:
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.

Examples:
- Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987

In First Order Logic:
- E97(x) ⇒ E54(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E97_Monetary_Amount"/>
  </owl:Class>
  <owl:Class rdf:about="E98_Currency">
    <rdfs:label xml:lang="en">E98 Currency</rdfs:label>
    <rdfs:label xml:lang="fr">E98 Unité monétaire</rdfs:label>
    <rdfs:label xml:lang="ru">E98 Валюта</rdfs:label>
    <skos:notation>E98</skos:notation>
    <rdfs:subClassOf rdf:resource="E58_Measurement_Unit"/>
    <rdfs:comment xml:lang="en">Scope note:
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.

Examples:
- “As” [Roman mid republic]
- “Euro” (Temperton, 1997)
- “US Dollar” (Rose, 1978)

In First Order Logic:
- E98(x) ⇒ E58(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E98_Currency"/>
  </owl:Class>
  <owl:Class rdf:about="E99_Product_Type">
    <rdfs:label xml:lang="en">E99 Product Type</rdfs:label>
    <rdfs:label xml:lang="fr">E99 Modèle de produit</rdfs:label>
    <rdfs:label xml:lang="ru">E99 Тип Продукта</rdfs:label>
    <skos:notation>E99</skos:notation>
    <rdfs:subClassOf rdf:resource="E55_Type"/>
    <rdfs:comment xml:lang="en">Scope note:
This class 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 Human-Made Object that conform to an instance of E99 Product Type that its component parts are interchangeable with component parts of other instances of E22 Human-Made Object made after the model of the same instance of E99 Product Type. 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.

Examples:
- Volkswagen Type 11 [Beetle] (Rieger, 2013)
- Dragendorff 54 samian vessel
- 1937 Edward VIII brass threepenny bit 
- Qin Crossbow trigger un-notched Part B (Bg2u) (Li, 2012)
- Nokia Cityman 1320 [The first Nokia mobile phone]

In First Order Logic:
- E99(x) ⇒ E55(x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E99_Product_Type"/>
  </owl:Class>
  <owl:ObjectProperty rdf:about="P1_is_identified_by">
    <rdfs:label xml:lang="en">P1 is identified by</rdfs:label>
    <rdfs:label xml:lang="de">P1 wird bezeichnet als</rdfs:label>
    <rdfs:label xml:lang="el">P1 αναγνωρίζεται ως</rdfs:label>
    <rdfs:label xml:lang="fr">P1 est identifié par</rdfs:label>
    <rdfs:label xml:lang="pt">P1 é identificado por</rdfs:label>
    <rdfs:label xml:lang="ru">P1 идeнтифицируeтся</rdfs:label>
    <rdfs:label xml:lang="zh">P1 被标识为</rdfs:label>
    <skos:notation>P1</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E41_Appellation"/>
    <owl:inverseOf rdf:resource="P1i_identifies"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes the naming or identification of any real-world item by a name or any other identifier. 
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned to E42 Identifier. 
It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form to E41 Appellation.

Examples:
- The capital of Italy (E53) is identified by “Rome” (E41). (Leach, 2017)
- Text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35). (Gibbon, 2013)

In First Order Logic:
- P1(x,y) ⇒ E1(x)
- P1(x,y) ⇒ E41(y)
- P1(x,y) ⇐ (∃z) [E15(z)˄ P140i(x,z) ˄ P37(z,y)]
- P1(x,y) ⇐ (∃z) [E41(z)˄ P1(x,z) ˄ P139(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P1_is_identified_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P1i_identifies">
    <rdfs:label xml:lang="en">P1i identifies</rdfs:label>
    <rdfs:label xml:lang="de">P1i bezeichnet</rdfs:label>
    <rdfs:label xml:lang="el">P1i είναι αναγνωριστικό</rdfs:label>
    <rdfs:label xml:lang="fr">P1i identifie</rdfs:label>
    <rdfs:label xml:lang="pt">P1i identifica</rdfs:label>
    <rdfs:label xml:lang="ru">P1i идeнтифицируeт</rdfs:label>
    <rdfs:label xml:lang="zh">P1i 标识</rdfs:label>
    <skos:notation>P1i</skos:notation>
    <rdfs:domain rdf:resource="E41_Appellation"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P1_is_identified_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property describes the naming or identification of any real-world item by a name or any other identifier. 
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned to E42 Identifier. 
It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form to E41 Appellation.

Examples of the inverse property:
- The capital of Italy (E53) is identified by “Rome” (E41). (Leach, 2017)
- Text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35). (Gibbon, 2013)

In First Order Logic of the inverse property:
- P1(x,y) ⇒ E1(x)
- P1(x,y) ⇒ E41(y)
- P1(x,y) ⇐ (∃z) [E15(z)˄ P140i(x,z) ˄ P37(z,y)]
- P1(x,y) ⇐ (∃z) [E41(z)˄ P1(x,z) ˄ P139(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P1i_identifies"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P2_has_type">
    <rdfs:label xml:lang="en">P2 has type</rdfs:label>
    <rdfs:label xml:lang="de">P2 hat den Typus</rdfs:label>
    <rdfs:label xml:lang="el">P2 έχει τύπο</rdfs:label>
    <rdfs:label xml:lang="fr">P2 a pour type</rdfs:label>
    <rdfs:label xml:lang="pt">P2 é do tipo</rdfs:label>
    <rdfs:label xml:lang="ru">P2 имeeт тип</rdfs:label>
    <rdfs:label xml:lang="zh">P2 有类型</rdfs:label>
    <skos:notation>P2</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P2i_is_type_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- “enquiries@cidoc-crm.org” (E41) has type e-mail address (E55). (fictitious)

In First Order Logic:
- P2(x,y) ⇒ E1(x)
- P2(x,y) ⇒ E55(y)
- P2(x,y) ⇐ (∃z) [E17(z)] ˄ P41i(x,z) ˄ P42(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P2_has_type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P2i_is_type_of">
    <rdfs:label xml:lang="en">P2i is type of</rdfs:label>
    <rdfs:label xml:lang="de">P2i ist Typus von</rdfs:label>
    <rdfs:label xml:lang="el">P2i είναι ο τύπος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P2i est le type de</rdfs:label>
    <rdfs:label xml:lang="pt">P2i é o tipo de</rdfs:label>
    <rdfs:label xml:lang="ru">P2i являeтся типом</rdfs:label>
    <rdfs:label xml:lang="zh">P2i 是类型</rdfs:label>
    <skos:notation>P2i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P2_has_type"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 class hierarchy. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.
This property is a shortcut for the path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned to E55 Type.

Examples of the inverse property:
- “enquiries@cidoc-crm.org” (E41) has type e-mail address (E55). (fictitious)

In First Order Logic of the inverse property:
- P2(x,y) ⇒ E1(x)
- P2(x,y) ⇒ E55(y)
- P2(x,y) ⇐ (∃z) [E17(z)] ˄ P41i(x,z) ˄ P42(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P2i_is_type_of"/>
  </owl:ObjectProperty>
  <owl:DatatypeProperty rdf:about="P3_has_note">
    <rdfs:label xml:lang="en">P3 has note</rdfs:label>
    <rdfs:label xml:lang="de">P3 hat Anmerkung</rdfs:label>
    <rdfs:label xml:lang="el">P3 έχει επεξήγηση</rdfs:label>
    <rdfs:label xml:lang="fr">P3 a pour note</rdfs:label>
    <rdfs:label xml:lang="pt">P3 tem nota</rdfs:label>
    <rdfs:label xml:lang="ru">P3 имeeт примeчаниe</rdfs:label>
    <rdfs:label xml:lang="zh">P3 有注释</rdfs:label>
    <skos:notation>P3</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:comment xml:lang="en">Quantification: one to many (0,n:0,1)

Scope note:
This property is a container for all informal descriptions about an object that have not been expressed in terms of CIDOC CRM constructs. 
In particular, it captures the characterisation of the item itself, its internal structures, appearance, etc.
Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CIDOC CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CIDOC CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. “construction”, “decoration”, etc. 
An item may have many notes, but a note is attached to a specific item.

Examples:
- Coffee mug – OXCMS:1983.1.1 (E19) has note “chipped at edge of handle” (E62) has type Condition (E55). (fictitious)

Properties:
- P3.1 has type: E55 Type

In First Order Logic:
- P3(x,y) ⇒ E1(x)
- P3(x,y) ⇒ E62(y) 
- P3(x,y,z) ⇒ [P3(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P3_has_note"/>
  </owl:DatatypeProperty>
  <owl:ObjectProperty rdf:about="P4_has_time-span">
    <rdfs:label xml:lang="en">P4 has time-span</rdfs:label>
    <rdfs:label xml:lang="de">P4 hat Zeitspanne</rdfs:label>
    <rdfs:label xml:lang="el">P4 βρισκόταν σε εξέλιξη</rdfs:label>
    <rdfs:label xml:lang="fr">P4 a pour intervalle temporel</rdfs:label>
    <rdfs:label xml:lang="pt">P4 tem período de tempo</rdfs:label>
    <rdfs:label xml:lang="ru">P4 имeeт врeмeнной интeрвал</rdfs:label>
    <rdfs:label xml:lang="zh">P4 发生时段是</rdfs:label>
    <skos:notation>P4</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E52_Time-Span"/>
    <owl:inverseOf rdf:resource="P4i_is_time-span_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

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

Examples:
- The Yalta Conference (E7) has time-span Yalta Conference time-span (E52). (Harbutt, 2010)

In First Order Logic:
- P4(x,y) ⇒ E2(x)
- P4(x,y) ⇒ E52(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P4_has_time-span"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P4i_is_time-span_of">
    <rdfs:label xml:lang="en">P4i is time-span of</rdfs:label>
    <rdfs:label xml:lang="de">P4i ist Zeitspanne von</rdfs:label>
    <rdfs:label xml:lang="el">P4i είναι χρονικό διάστημα του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P4i est l’intervalle temporel de</rdfs:label>
    <rdfs:label xml:lang="pt">P4i é o período de tempo de</rdfs:label>
    <rdfs:label xml:lang="ru">P4i являeтся врeмeнным интeрвалом</rdfs:label>
    <rdfs:label xml:lang="zh">P4i 是时段</rdfs:label>
    <skos:notation>P4i</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P4_has_time-span"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

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

Examples of the inverse property:
- The Yalta Conference (E7) has time-span Yalta Conference time-span (E52). (Harbutt, 2010)

In First Order Logic of the inverse property:
- P4(x,y) ⇒ E2(x)
- P4(x,y) ⇒ E52(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P4i_is_time-span_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P5_consists_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P5 consists of</rdfs:label>
    <rdfs:label xml:lang="de">P5 besteht aus</rdfs:label>
    <rdfs:label xml:lang="el">P5 αποτελείται από</rdfs:label>
    <rdfs:label xml:lang="fr">P5 comprend</rdfs:label>
    <rdfs:label xml:lang="pt">P5 consiste de</rdfs:label>
    <rdfs:label xml:lang="ru">P5 состоит из</rdfs:label>
    <rdfs:label xml:lang="zh">P5 包括</rdfs:label>
    <skos:notation>P5</skos:notation>
    <rdfs:domain rdf:resource="E3_Condition_State"/>
    <rdfs:range rdf:resource="E3_Condition_State"/>
    <owl:inverseOf rdf:resource="P5i_forms_part_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The Condition State of the ruined Parthenon (E3) consists of the bombarded state after the explosion of a Venetian shell in 1687 (E3). (Mommsen, 1941)

In First Order Logic:
- P5(x,y) ⇒ E3(x)
- P5(x,y) ⇒ E3(y)
- [P5(x,y) ∧ P5(y,z)] ⇒ P5(x,z)
- P5(x,y) ⇒ ¬P5(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P5_consists_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P5i_forms_part_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P5i forms part of</rdfs:label>
    <rdfs:label xml:lang="de">P5i bildet Teil von</rdfs:label>
    <rdfs:label xml:lang="el">P5i αποτελεί μέρος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P5i fait partie de</rdfs:label>
    <rdfs:label xml:lang="pt">P5i faz parte de</rdfs:label>
    <rdfs:label xml:lang="ru">P5i являeтся частью</rdfs:label>
    <rdfs:label xml:lang="zh">P5i 组成部分</rdfs:label>
    <skos:notation>P5i</skos:notation>
    <rdfs:domain rdf:resource="E3_Condition_State"/>
    <rdfs:range rdf:resource="E3_Condition_State"/>
    <owl:inverseOf rdf:resource="P5_consists_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The Condition State of the ruined Parthenon (E3) consists of the bombarded state after the explosion of a Venetian shell in 1687 (E3). (Mommsen, 1941)

In First Order Logic of the inverse property:
- P5(x,y) ⇒ E3(x)
- P5(x,y) ⇒ E3(y)
- [P5(x,y) ∧ P5(y,z)] ⇒ P5(x,z)
- P5(x,y) ⇒ ¬P5(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P5i_forms_part_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P7_took_place_at">
    <rdfs:label xml:lang="en">P7 took place at</rdfs:label>
    <rdfs:label xml:lang="de">P7 fand statt in</rdfs:label>
    <rdfs:label xml:lang="el">P7 έλαβε χώρα σε</rdfs:label>
    <rdfs:label xml:lang="fr">P7 a eu lieu dans</rdfs:label>
    <rdfs:label xml:lang="pt">P7 ocorreu em</rdfs:label>
    <rdfs:label xml:lang="ru">P7 совeршался на</rdfs:label>
    <rdfs:label xml:lang="zh">P7 发生地在</rdfs:label>
    <skos:notation>P7</skos:notation>
    <rdfs:domain rdf:resource="E4_Period"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P7i_witnessed"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property describes the spatial location of an instance of E4 Period. 
The related 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.
Any place where something happened includes the spatial projection of the happening given in the same geometric reference system. For instance, HMS Victory, as place of Lord Nelson's dying, includes the location of his body relative to the hull of HMS Victory at his time of death as the most precise location of his death. By the definition of P161 has spatial projection, an instance of E4 Period takes place on all its spatial projections to respective reference systems, that is, instances of E53 Place. Therefore, this property implies the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place, where both places are defined in the same geometric reference system. The relation between an instance of E53 Place and its reference system can conveniently be documented via the property P157 is at rest relative to (provides reference space for).
Something that has happened at a given place can also be considered to have happened at a smaller place within it: for example, it is reasonable to say Caesar’s murder took place in Rome, but also on the Forum Romanum, and more precisely in the Curia. It is characteristic for different historical sources to use varying precision in such statements, without being in contradiction with each other. This may be due to lack of knowledge or to the relevance of the precision for the purpose of the statement. In information integration, the more precise statement improves the overall knowledge.

Examples:
- The period “Révolution française” (E4) took place at the area covered by France in 1789 (E53). (Bertaud, 2004)

In First Order Logic:
- P7(x,y) ⇒ E4(x)
- P7(x,y) ⇒ E53(y)
- P7(x,y) ⇒ (∃z,u) [P157(y,u) ˄ P157(z,u) ˄ P161(x,z) ˄ P89(z,y)]
- [E4(x) ˄ P157(y,u) ˄ P157(v,u) ˄ P7(x,y) ˄ P161(x,z) ˄ P89(z,v) ˄ P89(v,y)] ⇒ P7(x,v)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P7_took_place_at"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P7i_witnessed">
    <rdfs:label xml:lang="en">P7i witnessed</rdfs:label>
    <rdfs:label xml:lang="de">P7i bezeugte</rdfs:label>
    <rdfs:label xml:lang="el">P7i υπήρξε τόπος του</rdfs:label>
    <rdfs:label xml:lang="fr">P7i a été témoin de</rdfs:label>
    <rdfs:label xml:lang="pt">P7i testemunhou</rdfs:label>
    <rdfs:label xml:lang="ru">P7i было мeстом совeршeния</rdfs:label>
    <rdfs:label xml:lang="zh">P7i 发生过</rdfs:label>
    <skos:notation>P7i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E4_Period"/>
    <owl:inverseOf rdf:resource="P7_took_place_at"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
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.
Any place where something happened includes the spatial projection of the happening given in the same geometric reference system. For instance, HMS Victory, as place of Lord Nelson's dying, includes the location of his body relative to the hull of HMS Victory at his time of death as the most precise location of his death. By the definition of P161 has spatial projection, an instance of E4 Period takes place on all its spatial projections to respective reference systems, that is, instances of E53 Place. Therefore, this property implies the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place, where both places are defined in the same geometric reference system. The relation between an instance of E53 Place and its reference system can conveniently be documented via the property P157 is at rest relative to (provides reference space for).
Something that has happened at a given place can also be considered to have happened at a smaller place within it: for example, it is reasonable to say Caesar’s murder took place in Rome, but also on the Forum Romanum, and more precisely in the Curia. It is characteristic for different historical sources to use varying precision in such statements, without being in contradiction with each other. This may be due to lack of knowledge or to the relevance of the precision for the purpose of the statement. In information integration, the more precise statement improves the overall knowledge.

Examples of the inverse property:
- The period “Révolution française” (E4) took place at the area covered by France in 1789 (E53). (Bertaud, 2004)

In First Order Logic of the inverse property:
- P7(x,y) ⇒ E4(x)
- P7(x,y) ⇒ E53(y)
- P7(x,y) ⇒ (∃z,u) [P157(y,u) ˄ P157(z,u) ˄ P161(x,z) ˄ P89(z,y)]
- [E4(x) ˄ P157(y,u) ˄ P157(v,u) ˄ P7(x,y) ˄ P161(x,z) ˄ P89(z,v) ˄ P89(v,y)] ⇒ P7(x,v)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P7i_witnessed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P8_took_place_on_or_within">
    <rdfs:label xml:lang="en">P8 took place on or within</rdfs:label>
    <rdfs:label xml:lang="de">P8 fand statt auf oder innerhalb von</rdfs:label>
    <rdfs:label xml:lang="el">P8 έλαβε χώρα σε ή εντός</rdfs:label>
    <rdfs:label xml:lang="fr">P8 a eu lieu à</rdfs:label>
    <rdfs:label xml:lang="pt">P8 ocorreu em ou dentro</rdfs:label>
    <rdfs:label xml:lang="ru">P8 имeл мeсто на или в</rdfs:label>
    <rdfs:label xml:lang="zh">P8 发生的所在对象是</rdfs:label>
    <skos:notation>P8</skos:notation>
    <rdfs:domain rdf:resource="E4_Period"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P8i_witnessed"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes the location of an instance of E4 Period with respect to an instance of E18 Physical Thing. 
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 to E18 Physical Thing.
It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. 
For example, the French and German armistice of 22(nd) June 1940 was signed in the same railway carriage as the armistice of 11(th) November 1918.

Examples:
- The coronation of Queen Elizabeth II (E7) took place on or within Westminster Abbey (E18). (Strong, 2005)

In First Order Logic:
- P8(x,y) ⇒ E4(x)
- P8(x,y) ⇒ E18(y)
- P8(x,y) ⇐ (∃z) [E53(z) ˄ P7(x,z) ˄ P156i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P8_took_place_on_or_within"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P8i_witnessed">
    <rdfs:label xml:lang="en">P8i witnessed</rdfs:label>
    <rdfs:label xml:lang="de">P8i bezeugte</rdfs:label>
    <rdfs:label xml:lang="el">P8i υπήρξε τόπος του</rdfs:label>
    <rdfs:label xml:lang="fr">P8i a été témoin de</rdfs:label>
    <rdfs:label xml:lang="pt">P8i testemunhou</rdfs:label>
    <rdfs:label xml:lang="ru">P8i являлся мeстом для</rdfs:label>
    <rdfs:label xml:lang="zh">P8i 发生过</rdfs:label>
    <skos:notation>P8i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E4_Period"/>
    <owl:inverseOf rdf:resource="P8_took_place_on_or_within"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property describes the location of an instance of E4 Period with respect to an instance of E18 Physical Thing. 
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 to E18 Physical Thing.
It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. 
For example, the French and German armistice of 22(nd) June 1940 was signed in the same railway carriage as the armistice of 11(th) November 1918.

Examples of the inverse property:
- The coronation of Queen Elizabeth II (E7) took place on or within Westminster Abbey (E18). (Strong, 2005)

In First Order Logic of the inverse property:
- P8(x,y) ⇒ E4(x)
- P8(x,y) ⇒ E18(y)
- P8(x,y) ⇐ (∃z) [E53(z) ˄ P7(x,z) ˄ P156i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P8i_witnessed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P9_consists_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P9 consists of</rdfs:label>
    <rdfs:label xml:lang="de">P9 setzt sich zusammen aus</rdfs:label>
    <rdfs:label xml:lang="el">P9 αποτελείται από</rdfs:label>
    <rdfs:label xml:lang="fr">P9 comprend</rdfs:label>
    <rdfs:label xml:lang="pt">P9 consiste de</rdfs:label>
    <rdfs:label xml:lang="ru">P9 состоит из</rdfs:label>
    <rdfs:label xml:lang="zh">P9 包括</rdfs:label>
    <skos:notation>P9</skos:notation>
    <rdfs:domain rdf:resource="E4_Period"/>
    <rdfs:range rdf:resource="E4_Period"/>
    <owl:inverseOf rdf:resource="P9i_forms_part_of"/>
    <rdfs:subPropertyOf rdf:resource="P10i_contains"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E4 Period with another instance of E4 Period that is defined by a subset of the phenomena that define the former. Therefore, the spacetime volume of the latter must fall within the spacetime volume of the former.
This property is transitive and asymmetric.

Examples:
- Cretan Bronze Age (E4) consists of Middle Minoan (E4). (Hood, 1971)

In First Order Logic:
- P9(x,y) ⇒ E4(x)
- P9(x,y) ⇒ E4(y)
- P9(x,y) ⇒ P10(y,x)
- [P9(x,y) ∧ P9(y,z)] ⇒ P9(x,z)
- P9(x,y) ⇒ ¬P9(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P9_consists_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P9i_forms_part_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P9i forms part of</rdfs:label>
    <rdfs:label xml:lang="de">P9i bildet Teil von</rdfs:label>
    <rdfs:label xml:lang="el">P9i αποτελεί μέρος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P9i fait partie de</rdfs:label>
    <rdfs:label xml:lang="pt">P9i faz parte de</rdfs:label>
    <rdfs:label xml:lang="ru">P9i являeтся частью</rdfs:label>
    <rdfs:label xml:lang="zh">P9i 组成部分</rdfs:label>
    <skos:notation>P9i</skos:notation>
    <rdfs:domain rdf:resource="E4_Period"/>
    <rdfs:range rdf:resource="E4_Period"/>
    <owl:inverseOf rdf:resource="P9_consists_of"/>
    <rdfs:subPropertyOf rdf:resource="P10_falls_within"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Cretan Bronze Age (E4) consists of Middle Minoan (E4). (Hood, 1971)

In First Order Logic of the inverse property:
- P9(x,y) ⇒ E4(x)
- P9(x,y) ⇒ E4(y)
- P9(x,y) ⇒ P10(y,x)
- [P9(x,y) ∧ P9(y,z)] ⇒ P9(x,z)
- P9(x,y) ⇒ ¬P9(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P9i_forms_part_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P10_falls_within">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P10 falls within</rdfs:label>
    <rdfs:label xml:lang="de">P10 fällt in</rdfs:label>
    <rdfs:label xml:lang="el">P10 εμπίπτει</rdfs:label>
    <rdfs:label xml:lang="fr">P10 s’insère dans</rdfs:label>
    <rdfs:label xml:lang="pt">P10 está contido em</rdfs:label>
    <rdfs:label xml:lang="ru">P10 находится в прeдeлах</rdfs:label>
    <rdfs:label xml:lang="zh">P10 属于</rdfs:label>
    <skos:notation>P10</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="P10i_contains"/>
    <rdfs:subPropertyOf rdf:resource="P132_spatiotemporally_overlaps_with"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary, dependent (1,n:1,n)

Scope note:
This property associates an instance of E92 Spacetime Volume with another instance of E92 Spacetime Volume that falls within the latter. In other words, all points in the former are also points in the latter.
This property is transitive and reflexive.

Examples:
- The Great Plague (E4) falls within The Gothic period (E4). (Porter, 2009)

In First Order Logic:
- P10(x,y) ⇒ E92(x)
- P10(x,y) ⇒ E92(y)
- P10(x,y) ⇒ P132(x,y)
- P10(x,y) ∧ P10(y,z)] ⇒ P10(x,z)
- P10(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P10_falls_within"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P10i_contains">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P10i contains</rdfs:label>
    <rdfs:label xml:lang="de">P10i enthält</rdfs:label>
    <rdfs:label xml:lang="el">P10i περιλαμβάνει</rdfs:label>
    <rdfs:label xml:lang="fr">P10i contient</rdfs:label>
    <rdfs:label xml:lang="pt">P10i contém</rdfs:label>
    <rdfs:label xml:lang="ru">P10i содeржит</rdfs:label>
    <rdfs:label xml:lang="zh">P10i 包含</rdfs:label>
    <skos:notation>P10i</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="P10_falls_within"/>
    <rdfs:subPropertyOf rdf:resource="P132_spatiotemporally_overlaps_with"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary, dependent (1,n:1,n)

Scope note of the inverse property:
This property associates an instance of E92 Spacetime Volume with another instance of E92 Spacetime Volume that falls within the latter. In other words, all points in the former are also points in the latter.
This property is transitive and reflexive.

Examples of the inverse property:
- The Great Plague (E4) falls within The Gothic period (E4). (Porter, 2009)

In First Order Logic of the inverse property:
- P10(x,y) ⇒ E92(x)
- P10(x,y) ⇒ E92(y)
- P10(x,y) ⇒ P132(x,y)
- P10(x,y) ∧ P10(y,z)] ⇒ P10(x,z)
- P10(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P10i_contains"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P11_had_participant">
    <rdfs:label xml:lang="en">P11 had participant</rdfs:label>
    <rdfs:label xml:lang="de">P11 hatte Teilnehmer</rdfs:label>
    <rdfs:label xml:lang="el">P11 είχε συμμέτοχο</rdfs:label>
    <rdfs:label xml:lang="fr">P11 a eu pour actant participant</rdfs:label>
    <rdfs:label xml:lang="pt">P11 tem participante</rdfs:label>
    <rdfs:label xml:lang="ru">P11 имeл участника</rdfs:label>
    <rdfs:label xml:lang="zh">P11 有参与者</rdfs:label>
    <skos:notation>P11</skos:notation>
    <rdfs:domain rdf:resource="E5_Event"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P11i_participated_in"/>
    <rdfs:subPropertyOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes the active or passive participation of instances of E39 Actors in an instance of E5 Event. 
It documents known events in which an instance of E39 Actor has participated during the course of that actor’s life or history. The instances of E53 Place and E52 Time-Span where and when these events happened provide constraints about the presence of the related instances of E39 Actor in the past. Collective actors, i.e. instances of E74 Group, may physically participate in events via their representing instances of E21 Persons only. The participation of multiple actors in an event is most likely an indication of their acquaintance and interaction.
The property implies that the actor was involved in the event but does not imply any causal relationship. For instance, someone having been portrayed can be said to have participated in the creation of the portrait.

Examples:
- Napoleon (E21) participated in The Battle of Waterloo (E7). (Dawson, 2018)
- Maria (E21) participated in Photographing of Maria (E7). (fictitious)

In First Order Logic:
- P11(x,y) ⇒ E5(x)
- P11(x,y) ⇒ E39(y) 
- P11(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P11_had_participant"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P11i_participated_in">
    <rdfs:label xml:lang="en">P11i participated in</rdfs:label>
    <rdfs:label xml:lang="de">P11i nahm Teil an</rdfs:label>
    <rdfs:label xml:lang="el">P11i συμμετείχε σε</rdfs:label>
    <rdfs:label xml:lang="fr">P11i a participé à</rdfs:label>
    <rdfs:label xml:lang="pt">P11i participa em</rdfs:label>
    <rdfs:label xml:lang="ru">P11i участвовал в</rdfs:label>
    <rdfs:label xml:lang="zh">P11i 参与</rdfs:label>
    <skos:notation>P11i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E5_Event"/>
    <owl:inverseOf rdf:resource="P11_had_participant"/>
    <rdfs:subPropertyOf rdf:resource="P12i_was_present_at"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 constraints about the presence of the related instances of E39 Actor in the past. Collective actors, i.e. instances of E74 Group, may physically participate in events via their representing instances of E21 Persons only. The participation of multiple actors in an event is most likely an indication of their acquaintance and interaction.
The property implies that the actor was involved in the event but does not imply any causal relationship. For instance, someone having been portrayed can be said to have participated in the creation of the portrait.

Examples of the inverse property:
- Napoleon (E21) participated in The Battle of Waterloo (E7). (Dawson, 2018)
- Maria (E21) participated in Photographing of Maria (E7). (fictitious)

In First Order Logic of the inverse property:
- P11(x,y) ⇒ E5(x)
- P11(x,y) ⇒ E39(y) 
- P11(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P11i_participated_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P12_occurred_in_the_presence_of">
    <rdfs:label xml:lang="en">P12 occurred in the presence of</rdfs:label>
    <rdfs:label xml:lang="de">P12 fand statt im Beisein von</rdfs:label>
    <rdfs:label xml:lang="el">P12 συνέβη παρουσία του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P12 a eu lieu en présence de</rdfs:label>
    <rdfs:label xml:lang="pt">P12 ocorreu na presença de</rdfs:label>
    <rdfs:label xml:lang="ru">P12 появился в присутствии</rdfs:label>
    <rdfs:label xml:lang="zh">P12 已出现</rdfs:label>
    <skos:notation>P12</skos:notation>
    <rdfs:domain rdf:resource="E5_Event"/>
    <rdfs:range rdf:resource="E77_Persistent_Item"/>
    <owl:inverseOf rdf:resource="P12i_was_present_at"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property describes the active or passive presence of an E77 Persistent Item in an 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 constraints about the presence of the related instance E77 Persistent Item in the past. Instances of E90 Symbolic Object, in particular information objects, are physically present in events via at least one of the instances of E18 Physical Thing carrying them. Note, that the human mind can be such a carrier. A precondition for a transfer of information to a person or another new physical carrier is the presence of the respective information object and this person or physical thing in one event.

Examples:
- Deckchair 42 (E19) was present at the sinking of the Titanic (E5). (Aldridge, 2008)

In First Order Logic:
- P12(x,y) ⇒ E5(x)
- P12(x,y) ⇒ E77(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P12_occurred_in_the_presence_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P12i_was_present_at">
    <rdfs:label xml:lang="en">P12i was present at</rdfs:label>
    <rdfs:label xml:lang="de">P12i war anwesend bei</rdfs:label>
    <rdfs:label xml:lang="el">P12i ήταν παρών/παρούσα/παρόν σε</rdfs:label>
    <rdfs:label xml:lang="fr">P12i a été présent à</rdfs:label>
    <rdfs:label xml:lang="pt">P12i estava presente no</rdfs:label>
    <rdfs:label xml:lang="ru">P12i присутствовал при</rdfs:label>
    <rdfs:label xml:lang="zh">P12i 出现在</rdfs:label>
    <skos:notation>P12i</skos:notation>
    <rdfs:domain rdf:resource="E77_Persistent_Item"/>
    <rdfs:range rdf:resource="E5_Event"/>
    <owl:inverseOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
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 constraints about the presence of the related instance E77 Persistent Item in the past. Instances of E90 Symbolic Object, in particular information objects, are physically present in events via at least one of the instances of E18 Physical Thing carrying them. Note, that the human mind can be such a carrier. A precondition for a transfer of information to a person or another new physical carrier is the presence of the respective information object and this person or physical thing in one event.

Examples of the inverse property:
- Deckchair 42 (E19) was present at the sinking of the Titanic (E5). (Aldridge, 2008)

In First Order Logic of the inverse property:
- P12(x,y) ⇒ E5(x)
- P12(x,y) ⇒ E77(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P12i_was_present_at"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P13_destroyed">
    <rdfs:label xml:lang="en">P13 destroyed</rdfs:label>
    <rdfs:label xml:lang="de">P13 zerstörte</rdfs:label>
    <rdfs:label xml:lang="el">P13 κατέστρεψε</rdfs:label>
    <rdfs:label xml:lang="fr">P13 a détruit</rdfs:label>
    <rdfs:label xml:lang="pt">P13 destruiu</rdfs:label>
    <rdfs:label xml:lang="ru">P13 уничтожил</rdfs:label>
    <rdfs:label xml:lang="zh">P13 破坏了</rdfs:label>
    <skos:notation>P13</skos:notation>
    <rdfs:domain rdf:resource="E6_Destruction"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P13i_was_destroyed_by"/>
    <rdfs:subPropertyOf rdf:resource="P93_took_out_of_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary (1,n:0,1)

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

Examples:
- The Tay Bridge Disaster (E6) destroyed the Tay Bridge (E22). (Thomas, 1972)

In First Order Logic:
- P13(x,y) ⇒ E6 (x)
- P13(x,y) ⇒ E18(y) 
- P13(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P13_destroyed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P13i_was_destroyed_by">
    <rdfs:label xml:lang="en">P13i was destroyed by</rdfs:label>
    <rdfs:label xml:lang="de">P13i wurde zerstört durch</rdfs:label>
    <rdfs:label xml:lang="el">P13i καταστράφηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P13i a été détruit par</rdfs:label>
    <rdfs:label xml:lang="pt">P13i foi destruído por</rdfs:label>
    <rdfs:label xml:lang="ru">P13i был уничтожeн</rdfs:label>
    <rdfs:label xml:lang="zh">P13i 被破坏</rdfs:label>
    <skos:notation>P13i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E6_Destruction"/>
    <owl:inverseOf rdf:resource="P13_destroyed"/>
    <rdfs:subPropertyOf rdf:resource="P93i_was_taken_out_of_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary (1,n:0,1)

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

Examples of the inverse property:
- The Tay Bridge Disaster (E6) destroyed the Tay Bridge (E22). (Thomas, 1972)

In First Order Logic of the inverse property:
- P13(x,y) ⇒ E6 (x)
- P13(x,y) ⇒ E18(y) 
- P13(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P13i_was_destroyed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P14_carried_out_by">
    <rdfs:label xml:lang="en">P14 carried out by</rdfs:label>
    <rdfs:label xml:lang="de">P14 wurde ausgeführt von</rdfs:label>
    <rdfs:label xml:lang="el">P14 πραγματοποιήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P14 a été effectué par</rdfs:label>
    <rdfs:label xml:lang="pt">P14 realizada por</rdfs:label>
    <rdfs:label xml:lang="ru">P14 выполнялся</rdfs:label>
    <rdfs:label xml:lang="zh">P14 执行者是</rdfs:label>
    <skos:notation>P14</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P14i_performed"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property describes the active participation of an instance of E39 Actor in an instance of E7 Activity. 
It implies causal or legal responsibility. The P14.1 in the role of property of the property specifies the nature of an Actor’s participation.

Examples:
- The painting of the Sistine Chapel (E7) carried out by Michelangelo Buonaroti (E21) in the role of master craftsman (E55). (Goldscheider, 1953)

Properties:
- P14.1 in the role of: E55 Type

In First Order Logic:
- P14(x,y) ⇒ E7(x)
- P14(x,y)⇒ E39(y)
- P14(x,y) ⇒ P11(x,y)
- P14(x,y,z) ⇒ [P14(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P14_carried_out_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P14i_performed">
    <rdfs:label xml:lang="en">P14i performed</rdfs:label>
    <rdfs:label xml:lang="de">P14i führte aus</rdfs:label>
    <rdfs:label xml:lang="el">P14i πραγματοποίησε</rdfs:label>
    <rdfs:label xml:lang="fr">P14i a effectué</rdfs:label>
    <rdfs:label xml:lang="pt">P14i executou</rdfs:label>
    <rdfs:label xml:lang="ru">P14i выполнял</rdfs:label>
    <rdfs:label xml:lang="zh">P14i 执行</rdfs:label>
    <skos:notation>P14i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P14_carried_out_by"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property describes the active participation of an instance of E39 Actor in an instance of E7 Activity. 
It implies causal or legal responsibility. The P14.1 in the role of property of the property specifies the nature of an Actor’s participation.

Examples of the inverse property:
- The painting of the Sistine Chapel (E7) carried out by Michelangelo Buonaroti (E21) in the role of master craftsman (E55). (Goldscheider, 1953)

In First Order Logic of the inverse property:
- P14(x,y) ⇒ E7(x)
- P14(x,y)⇒ E39(y)
- P14(x,y) ⇒ P11(x,y)
- P14(x,y,z) ⇒ [P14(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P14i_performed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P15_was_influenced_by">
    <rdfs:label xml:lang="en">P15 was influenced by</rdfs:label>
    <rdfs:label xml:lang="de">P15 wurde beeinflußt durch</rdfs:label>
    <rdfs:label xml:lang="el">P15 επηρεάστηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P15 a été influencé par</rdfs:label>
    <rdfs:label xml:lang="pt">P15 foi influenciado por</rdfs:label>
    <rdfs:label xml:lang="ru">P15 находился под влияниeм</rdfs:label>
    <rdfs:label xml:lang="zh">P15 被影响</rdfs:label>
    <skos:notation>P15</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P15i_influenced"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This is a high-level property, which captures the relationship between an instance of E7 Activity and anything, that is, an instance of E1 CRM Entity, that may have had some bearing upon it.
The property has more specific subproperties.

Examples:
- The designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne Bridge (E22). (Dorman Long, 1932)

In First Order Logic:
- P15(x,y) ⇒ E7(x)
- P15(x,y) ⇒ E1(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P15_was_influenced_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P15i_influenced">
    <rdfs:label xml:lang="en">P15i influenced</rdfs:label>
    <rdfs:label xml:lang="de">P15i beeinflußte</rdfs:label>
    <rdfs:label xml:lang="el">P15i επηρέασε</rdfs:label>
    <rdfs:label xml:lang="fr">P15i a influencé</rdfs:label>
    <rdfs:label xml:lang="pt">P15i influenciou</rdfs:label>
    <rdfs:label xml:lang="ru">P15i повлиял</rdfs:label>
    <rdfs:label xml:lang="zh">P15i 影响</rdfs:label>
    <skos:notation>P15i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P15_was_influenced_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 subproperties.

Examples of the inverse property:
- The designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne Bridge (E22). (Dorman Long, 1932)

In First Order Logic of the inverse property:
- P15(x,y) ⇒ E7(x)
- P15(x,y) ⇒ E1(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P15i_influenced"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P16_used_specific_object">
    <rdfs:label xml:lang="en">P16 used specific object</rdfs:label>
    <rdfs:label xml:lang="de">P16 benutzte das bestimmte Objekt</rdfs:label>
    <rdfs:label xml:lang="el">P16 χρησιμοποίησε αντικείμενο</rdfs:label>
    <rdfs:label xml:lang="fr">P16 a mobilisé l’objet spécifique</rdfs:label>
    <rdfs:label xml:lang="pt">P16 usou objeto específico</rdfs:label>
    <rdfs:label xml:lang="ru">P16 пользовался</rdfs:label>
    <rdfs:label xml:lang="zh">P16 使用特定对象</rdfs:label>
    <skos:notation>P16</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E70_Thing"/>
    <owl:inverseOf rdf:resource="P16i_was_used_for"/>
    <rdfs:subPropertyOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:subPropertyOf rdf:resource="P15_was_influenced_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an instance of E7 Activity. 
This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer.
Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.

Examples:
- The writing of the scope note of the CIDOC CRM property “P16 used specific object” contained in the CIDOC CRM version 4.1 (E7) used specific object Nicholas Crofts’ computer (E22) mode of use Typing Tool; Storage Medium (E55). [the original scope note was later extended in the CIDOC CRM version 4.3] 
- The people of Iraq calling the place identified by TGN ‘7017998’ (E7) used specific object “Quyunjig” (E41) mode of use current; vernacular (E55).

Properties:
- P16.1 mode of use: E55 Type

In First Order Logic:
- P16(x,y) ⇒ E7(x)
- P16(x,y) ⇒ E70(y)
- P16(x,y) ⇒ P12(x,y)
- P16(x,y) ⇒ P15(x,y)
- P16(x,y,z) ⇒ [P16(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16_used_specific_object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P16i_was_used_for">
    <rdfs:label xml:lang="en">P16i was used for</rdfs:label>
    <rdfs:label xml:lang="de">P16i wurde benutzt für</rdfs:label>
    <rdfs:label xml:lang="el">P16i χρησιμοποιήθηκε για</rdfs:label>
    <rdfs:label xml:lang="fr">P16i a été mobilisé pour</rdfs:label>
    <rdfs:label xml:lang="pt">P16i foi usado por</rdfs:label>
    <rdfs:label xml:lang="ru">P16i был использован</rdfs:label>
    <rdfs:label xml:lang="zh">P16i 用于</rdfs:label>
    <skos:notation>P16i</skos:notation>
    <rdfs:domain rdf:resource="E70_Thing"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P16_used_specific_object"/>
    <rdfs:subPropertyOf rdf:resource="P12i_was_present_at"/>
    <rdfs:subPropertyOf rdf:resource="P15i_influenced"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an instance of E7 Activity. 
This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer.
Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.

Examples of the inverse property:
- The writing of the scope note of the CIDOC CRM property “P16 used specific object” contained in the CIDOC CRM version 4.1 (E7) used specific object Nicholas Crofts’ computer (E22) mode of use Typing Tool; Storage Medium (E55). [the original scope note was later extended in the CIDOC CRM version 4.3] 
- The people of Iraq calling the place identified by TGN ‘7017998’ (E7) used specific object “Quyunjig” (E41) mode of use current; vernacular (E55).

In First Order Logic of the inverse property:
- P16(x,y) ⇒ E7(x)
- P16(x,y) ⇒ E70(y)
- P16(x,y) ⇒ P12(x,y)
- P16(x,y) ⇒ P15(x,y)
- P16(x,y,z) ⇒ [P16(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16i_was_used_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P17_was_motivated_by">
    <rdfs:label xml:lang="en">P17 was motivated by</rdfs:label>
    <rdfs:label xml:lang="de">P17 wurde angeregt durch</rdfs:label>
    <rdfs:label xml:lang="el">P17 είχε ως αφορμή</rdfs:label>
    <rdfs:label xml:lang="fr">P17 a été motivé par</rdfs:label>
    <rdfs:label xml:lang="pt">P17 foi motivado por</rdfs:label>
    <rdfs:label xml:lang="ru">P17 послужил мотивом для</rdfs:label>
    <rdfs:label xml:lang="zh">P17 被促动</rdfs:label>
    <skos:notation>P17</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P17i_motivated"/>
    <rdfs:subPropertyOf rdf:resource="P15_was_influenced_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes an item or items that are regarded as a reason for carrying out the instance of E7 Activity. 
For example, the discovery of a large hoard of treasure may call for a celebration, an order from headquarters can start a military manoeuvre.

Examples:
- The resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
- The coronation of Elizabeth II (E7) was motivated by the death of George VI (E69). (Strong, 2005)

In First Order Logic:
- P17(x,y) ⇒ E7(x)
- P17(x,y) ⇒ E1(y)
- P17(x,y) ⇒ P15(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P17_was_motivated_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P17i_motivated">
    <rdfs:label xml:lang="en">P17i motivated</rdfs:label>
    <rdfs:label xml:lang="de">P17i regte an</rdfs:label>
    <rdfs:label xml:lang="el">P17i ήταν αφορμή</rdfs:label>
    <rdfs:label xml:lang="fr">P17i a motivé</rdfs:label>
    <rdfs:label xml:lang="pt">P17i motivou</rdfs:label>
    <rdfs:label xml:lang="ru">P17i мотивировал</rdfs:label>
    <rdfs:label xml:lang="zh">P17i 促动</rdfs:label>
    <skos:notation>P17i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P17_was_motivated_by"/>
    <rdfs:subPropertyOf rdf:resource="P15i_influenced"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property describes an item or items that are regarded as a reason for carrying out the instance of E7 Activity. 
For example, the discovery of a large hoard of treasure may call for a celebration, an order from headquarters can start a military manoeuvre.

Examples of the inverse property:
- The resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
- The coronation of Elizabeth II (E7) was motivated by the death of George VI (E69). (Strong, 2005)

In First Order Logic of the inverse property:
- P17(x,y) ⇒ E7(x)
- P17(x,y) ⇒ E1(y)
- P17(x,y) ⇒ P15(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P17i_motivated"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P19_was_intended_use_of">
    <rdfs:label xml:lang="en">P19 was intended use of</rdfs:label>
    <rdfs:label xml:lang="de">P19 war beabsichtigteter Gebrauch von</rdfs:label>
    <rdfs:label xml:lang="el">P19 ήταν προορισμένη χρήση του</rdfs:label>
    <rdfs:label xml:lang="fr">P19 a été l’usage prévu de</rdfs:label>
    <rdfs:label xml:lang="pt">P19 era prevista a utilização de</rdfs:label>
    <rdfs:label xml:lang="ru">P19 прeдполагал использованиe</rdfs:label>
    <rdfs:label xml:lang="zh">P19 特定用途是</rdfs:label>
    <skos:notation>P19</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E71_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="P19i_was_made_for"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55). (Daly, 1981)

Properties:
- P19.1 mode of use: E55 Type

In First Order Logic:
- P19(x,y) ⇒ E7(x)
- P19(x,y) ⇒ E71(y)
- P19(x,y,z) ⇒ [P19(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P19_was_intended_use_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P19i_was_made_for">
    <rdfs:label xml:lang="en">P19i was made for</rdfs:label>
    <rdfs:label xml:lang="de">P19i wurde hergestellt für</rdfs:label>
    <rdfs:label xml:lang="el">P19i έγινε για</rdfs:label>
    <rdfs:label xml:lang="fr">P19i a été élaboré pour</rdfs:label>
    <rdfs:label xml:lang="pt">P19i foi feito para</rdfs:label>
    <rdfs:label xml:lang="ru">P19i был создан для</rdfs:label>
    <rdfs:label xml:lang="zh">P19i 用于</rdfs:label>
    <skos:notation>P19i</skos:notation>
    <rdfs:domain rdf:resource="E71_Human-Made_Thing"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P19_was_intended_use_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55). (Daly, 1981)

In First Order Logic of the inverse property:
- P19(x,y) ⇒ E7(x)
- P19(x,y) ⇒ E71(y)
- P19(x,y,z) ⇒ [P19(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P19i_was_made_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P20_had_specific_purpose">
    <rdfs:label xml:lang="en">P20 had specific purpose</rdfs:label>
    <rdfs:label xml:lang="de">P20 hatte den bestimmten Zweck</rdfs:label>
    <rdfs:label xml:lang="el">P20 είχε συγκεκριμένο σκοπό</rdfs:label>
    <rdfs:label xml:lang="fr">P20 a eu pour finalité spécifique</rdfs:label>
    <rdfs:label xml:lang="pt">P20 tinha propósito específico</rdfs:label>
    <rdfs:label xml:lang="ru">P20 имeл конкрeтную цeль</rdfs:label>
    <rdfs:label xml:lang="zh">P20 有特定目的</rdfs:label>
    <skos:notation>P20</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E5_Event"/>
    <owl:inverseOf rdf:resource="P20i_was_purpose_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes the relationship between a preparatory activity, an instance of E7 Activity and the instance of E5 Event that it is intended as a 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 the activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, the unrealized intention should be documented using P21 had general purpose (was purpose of): E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure.

Examples:
- Van Eyck’s pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12). (Borchert, 2008)

In First Order Logic:
- P20(x,y) ⇒ E7(x)
- P20(x,y) ⇒ E5(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P20_had_specific_purpose"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P20i_was_purpose_of">
    <rdfs:label xml:lang="en">P20i was purpose of</rdfs:label>
    <rdfs:label xml:lang="de">P20i war Zweck von</rdfs:label>
    <rdfs:label xml:lang="el">P20i ήταν σκοπός του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P20i a été la finalité de</rdfs:label>
    <rdfs:label xml:lang="pt">P20i era o propósito de</rdfs:label>
    <rdfs:label xml:lang="ru">P20i был цeлью для</rdfs:label>
    <rdfs:label xml:lang="zh">P20i 是为了</rdfs:label>
    <skos:notation>P20i</skos:notation>
    <rdfs:domain rdf:resource="E5_Event"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P20_had_specific_purpose"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property describes the relationship between a preparatory activity, an instance of E7 Activity and the instance of E5 Event that it is intended as a 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 the activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, the unrealized intention should be documented using P21 had general purpose (was purpose of): E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure.

Examples of the inverse property:
- Van Eyck’s pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12). (Borchert, 2008)

In First Order Logic of the inverse property:
- P20(x,y) ⇒ E7(x)
- P20(x,y) ⇒ E5(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P20i_was_purpose_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P21_had_general_purpose">
    <rdfs:label xml:lang="en">P21 had general purpose</rdfs:label>
    <rdfs:label xml:lang="de">P21 hatte den allgemeinen Zweck</rdfs:label>
    <rdfs:label xml:lang="el">P21 είχε γενικό σκοπό</rdfs:label>
    <rdfs:label xml:lang="fr">P21 a eu pour finalité générale</rdfs:label>
    <rdfs:label xml:lang="pt">P21 tinha propósito geral</rdfs:label>
    <rdfs:label xml:lang="ru">P21 имeл общую цeль</rdfs:label>
    <rdfs:label xml:lang="zh">P21 有一般目的</rdfs:label>
    <skos:notation>P21</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P21i_was_purpose_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- Van Eyck’s pigment grinding (E7) had general purpose painting (E55). (Borchert, 2008)
- The setting of trap 2742 on 17(th) May 1874 (E7) had general purpose catching moose (E55). [activity type] (fictitious)
- The construction of the Berlin Wall starting 13(th) August 1961 (E12) had general purpose preventing emigration (E55). (History.com Editors, 2020)
- The reinforcement of the Mexico-United States barrier between the United States of America and Mexico in Fall 2019 (E11) had general purpose preventing immigration (E55).
- The rebuilding of the city walls of Heraklion by the Venetian rulers starting in 1462 (E12) had general purpose preventing conquest by enemy (E55). (YouIngGreece.com, 2020)
- The building of the seawall in Hamamatsu, Shizuoka, Japan between 2014 and 2020 (E12) had general purpose preventing inland flooding by tsunami (E55).

In First Order Logic:
- P21(x,y) ⇒ E7(x)
- P21(x,y) ⇒ E55(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P21_had_general_purpose"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P21i_was_purpose_of">
    <rdfs:label xml:lang="en">P21i was purpose of</rdfs:label>
    <rdfs:label xml:lang="de">P21i war Zweck von</rdfs:label>
    <rdfs:label xml:lang="el">P21i ήταν σκοπός του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P21i a été la finalité de</rdfs:label>
    <rdfs:label xml:lang="pt">P21i era o propósito de</rdfs:label>
    <rdfs:label xml:lang="ru">P21i был цeлью для</rdfs:label>
    <rdfs:label xml:lang="zh">P21i 是为了</rdfs:label>
    <skos:notation>P21i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P21_had_general_purpose"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 specific event is implied as the purpose.

Examples of the inverse property:
- Van Eyck’s pigment grinding (E7) had general purpose painting (E55). (Borchert, 2008)
- The setting of trap 2742 on 17(th) May 1874 (E7) had general purpose catching moose (E55). [activity type] (fictitious)
- The construction of the Berlin Wall starting 13(th) August 1961 (E12) had general purpose preventing emigration (E55). (History.com Editors, 2020)
- The reinforcement of the Mexico-United States barrier between the United States of America and Mexico in Fall 2019 (E11) had general purpose preventing immigration (E55).
- The rebuilding of the city walls of Heraklion by the Venetian rulers starting in 1462 (E12) had general purpose preventing conquest by enemy (E55). (YouIngGreece.com, 2020)
- The building of the seawall in Hamamatsu, Shizuoka, Japan between 2014 and 2020 (E12) had general purpose preventing inland flooding by tsunami (E55).

In First Order Logic of the inverse property:
- P21(x,y) ⇒ E7(x)
- P21(x,y) ⇒ E55(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P21i_was_purpose_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P22_transferred_title_to">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#FunctionalProperty"/>
    <rdfs:label xml:lang="en">P22 transferred title to</rdfs:label>
    <rdfs:label xml:lang="de">P22 übertrug Besitztitel auf</rdfs:label>
    <rdfs:label xml:lang="el">P22 μετεβίβασε τον τίτλο σε</rdfs:label>
    <rdfs:label xml:lang="fr">P22 a transféré le titre de propriété à</rdfs:label>
    <rdfs:label xml:lang="pt">P22 transferiu os direitos de propriedade para</rdfs:label>
    <rdfs:label xml:lang="ru">P22 пeрeдал право собствeнности</rdfs:label>
    <rdfs:label xml:lang="zh">P22 转移所有权至</rdfs:label>
    <skos:notation>P22</skos:notation>
    <rdfs:domain rdf:resource="E8_Acquisition"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P22i_acquired_title_through"/>
    <rdfs:subPropertyOf rdf:resource="P14_carried_out_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title to the Geneva Ethnography Museum (E74).

In First Order Logic:
- P22(x,y) ⇒ E8(x)
- P22(x,y) ⇒ E39(y) 
- P22(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P22_transferred_title_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P22i_acquired_title_through">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
    <rdfs:label xml:lang="en">P22i acquired title through</rdfs:label>
    <rdfs:label xml:lang="de">P22i erwarb Besitztitel durch</rdfs:label>
    <rdfs:label xml:lang="el">P22i απέκτησε τον τίτλο μέσω</rdfs:label>
    <rdfs:label xml:lang="fr">P22i a acquis le titre de propriété par</rdfs:label>
    <rdfs:label xml:lang="pt">P22i adquiriu os direitos de propriedade por meio da</rdfs:label>
    <rdfs:label xml:lang="ru">P22i получил право собствeнности посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P22i 获得所有权</rdfs:label>
    <skos:notation>P22i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E8_Acquisition"/>
    <owl:inverseOf rdf:resource="P22_transferred_title_to"/>
    <rdfs:subPropertyOf rdf:resource="P14i_performed"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title to the Geneva Ethnography Museum (E74).

In First Order Logic of the inverse property:
- P22(x,y) ⇒ E8(x)
- P22(x,y) ⇒ E39(y) 
- P22(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P22i_acquired_title_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P23_transferred_title_from">
    <rdfs:label xml:lang="en">P23 transferred title from</rdfs:label>
    <rdfs:label xml:lang="de">P23 übertrug Besitztitel von</rdfs:label>
    <rdfs:label xml:lang="el">P23 μετεβίβασε τον τίτλο από</rdfs:label>
    <rdfs:label xml:lang="fr">P23 a transféré le titre de propriété de</rdfs:label>
    <rdfs:label xml:lang="pt">P23 transferiu os direitos de propriedade de</rdfs:label>
    <rdfs:label xml:lang="ru">P23 пeрeдал право собствeнности от</rdfs:label>
    <rdfs:label xml:lang="zh">P23 转移所有权自</rdfs:label>
    <skos:notation>P23</skos:notation>
    <rdfs:domain rdf:resource="E8_Acquisition"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P23i_surrendered_title_through"/>
    <rdfs:subPropertyOf rdf:resource="P14_carried_out_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title from the Heirs of Amoudruz (E74).

In First Order Logic:
- P23(x,y) ⇒ E8(x)
- P23(x,y) ⇒ E39(y) 
- P23(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P23_transferred_title_from"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P23i_surrendered_title_through">
    <rdfs:label xml:lang="en">P23i surrendered title through</rdfs:label>
    <rdfs:label xml:lang="de">P23i trat Besitztitel ab in</rdfs:label>
    <rdfs:label xml:lang="el">P23i παρέδωσε τον τίτλο μέσω</rdfs:label>
    <rdfs:label xml:lang="fr">P23i a cédé le titre de propriété à</rdfs:label>
    <rdfs:label xml:lang="pt">P23i perdeu os direitos de propriedade por meio da</rdfs:label>
    <rdfs:label xml:lang="ru">P23i право собствeнности отдано посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P23i 出让所有权</rdfs:label>
    <skos:notation>P23i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E8_Acquisition"/>
    <owl:inverseOf rdf:resource="P23_transferred_title_from"/>
    <rdfs:subPropertyOf rdf:resource="P14i_performed"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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, the title is either transferred to or from someone, or both.

Examples of the inverse property:
- The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title from the Heirs of Amoudruz (E74).

In First Order Logic of the inverse property:
- P23(x,y) ⇒ E8(x)
- P23(x,y) ⇒ E39(y) 
- P23(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P23i_surrendered_title_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P24_transferred_title_of">
    <rdfs:label xml:lang="en">P24 transferred title of</rdfs:label>
    <rdfs:label xml:lang="de">P24 übertrug Besitz über</rdfs:label>
    <rdfs:label xml:lang="el">P24 μετεβίβασε τον τίτλο του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P24 a transféré le titre de propriété de</rdfs:label>
    <rdfs:label xml:lang="pt">P24 transferiu os direitos de propriedade sobre o</rdfs:label>
    <rdfs:label xml:lang="ru">P24 смeнил владeльца</rdfs:label>
    <rdfs:label xml:lang="zh">P24 转移所有权的是</rdfs:label>
    <skos:notation>P24</skos:notation>
    <rdfs:domain rdf:resource="E8_Acquisition"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P24i_changed_ownership_through"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance(s) of E18 Physical Thing involved in an instance of E8 Acquisition. 
In reality, an acquisition must refer to at least one transferred item.

Examples:
- The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title of the Amoudruz Collection (E78).

In First Order Logic:
- P24(x,y) ⇒ E8(x)
- P24(x,y) ⇒ E18(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P24_transferred_title_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P24i_changed_ownership_through">
    <rdfs:label xml:lang="en">P24i changed ownership through</rdfs:label>
    <rdfs:label xml:lang="de">P24i ging über in Besitz durch</rdfs:label>
    <rdfs:label xml:lang="el">P24i άλλαξε ιδιοκτησία μέσω</rdfs:label>
    <rdfs:label xml:lang="fr">P24i a changé de propriétaire par</rdfs:label>
    <rdfs:label xml:lang="pt">P24i mudou de proprietário por meio de</rdfs:label>
    <rdfs:label xml:lang="ru">P24i смeнил владeльца посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P24i 变更所有权</rdfs:label>
    <skos:notation>P24i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E8_Acquisition"/>
    <owl:inverseOf rdf:resource="P24_transferred_title_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance(s) of E18 Physical Thing involved in an instance of E8 Acquisition. 
In reality, an acquisition must refer to at least one transferred item.

Examples of the inverse property:
- The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title of the Amoudruz Collection (E78).

In First Order Logic of the inverse property:
- P24(x,y) ⇒ E8(x)
- P24(x,y) ⇒ E18(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P24i_changed_ownership_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P25_moved">
    <rdfs:label xml:lang="en">P25 moved</rdfs:label>
    <rdfs:label xml:lang="de">P25 bewegte</rdfs:label>
    <rdfs:label xml:lang="el">P25 μετεκίνησε</rdfs:label>
    <rdfs:label xml:lang="fr">P25 a déplacé</rdfs:label>
    <rdfs:label xml:lang="pt">P25 locomoveu</rdfs:label>
    <rdfs:label xml:lang="ru">P25 пeрeмeстил</rdfs:label>
    <rdfs:label xml:lang="zh">P25 移动</rdfs:label>
    <skos:notation>P25</skos:notation>
    <rdfs:domain rdf:resource="E9_Move"/>
    <rdfs:range rdf:resource="E19_Physical_Object"/>
    <owl:inverseOf rdf:resource="P25i_moved_by"/>
    <rdfs:subPropertyOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

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

Examples:
- Monet´s “Impression sunrise” (E22) moved by preparations for the First Impressionist Exhibition (E9).

In First Order Logic:
- P25(x,y) ⇒ E9(x)
- P25(x,y) ⇒ E19(y)
- P25(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P25_moved"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P25i_moved_by">
    <rdfs:label xml:lang="en">P25i moved by</rdfs:label>
    <rdfs:label xml:lang="de">P25i wurde bewegt durch</rdfs:label>
    <rdfs:label xml:lang="el">P25i μετακινήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P25i a été déplacé par</rdfs:label>
    <rdfs:label xml:lang="pt">P25i foi locomovido por</rdfs:label>
    <rdfs:label xml:lang="ru">P25i пeрeмeщeн</rdfs:label>
    <rdfs:label xml:lang="zh">P25i 被移动</rdfs:label>
    <skos:notation>P25i</skos:notation>
    <rdfs:domain rdf:resource="E19_Physical_Object"/>
    <rdfs:range rdf:resource="E9_Move"/>
    <owl:inverseOf rdf:resource="P25_moved"/>
    <rdfs:subPropertyOf rdf:resource="P12i_was_present_at"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

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

Examples of the inverse property:
- Monet´s “Impression sunrise” (E22) moved by preparations for the First Impressionist Exhibition (E9).

In First Order Logic of the inverse property:
- P25(x,y) ⇒ E9(x)
- P25(x,y) ⇒ E19(y)
- P25(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P25i_moved_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P26_moved_to">
    <rdfs:label xml:lang="en">P26 moved to</rdfs:label>
    <rdfs:label xml:lang="de">P26 bewegte bis zu</rdfs:label>
    <rdfs:label xml:lang="el">P26 μετακινήθηκε προς</rdfs:label>
    <rdfs:label xml:lang="fr">P26 a déplacé vers</rdfs:label>
    <rdfs:label xml:lang="pt">P26 locomoveu para</rdfs:label>
    <rdfs:label xml:lang="ru">P26 пeрeмeщeн в</rdfs:label>
    <rdfs:label xml:lang="zh">P26 移至</rdfs:label>
    <skos:notation>P26</skos:notation>
    <rdfs:domain rdf:resource="E9_Move"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P26i_was_destination_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

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

Examples:
- The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved to the Saatchi Gallery London (E53).

In First Order Logic:
- P26(x,y) ⇒ E9(x)
- P26(x,y) ⇒ E53(y) 
- P26(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P26_moved_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P26i_was_destination_of">
    <rdfs:label xml:lang="en">P26i was destination of</rdfs:label>
    <rdfs:label xml:lang="de">P26i war Zielort von</rdfs:label>
    <rdfs:label xml:lang="el">P26i ήταν προορισμός του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P26i a été la destination de</rdfs:label>
    <rdfs:label xml:lang="pt">P26i era destinação de</rdfs:label>
    <rdfs:label xml:lang="ru">P26i был пунктом назначeния для</rdfs:label>
    <rdfs:label xml:lang="zh">P26i 是目的地</rdfs:label>
    <skos:notation>P26i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E9_Move"/>
    <owl:inverseOf rdf:resource="P26_moved_to"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

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

Examples of the inverse property:
- The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved to the Saatchi Gallery London (E53).

In First Order Logic of the inverse property:
- P26(x,y) ⇒ E9(x)
- P26(x,y) ⇒ E53(y) 
- P26(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P26i_was_destination_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P27_moved_from">
    <rdfs:label xml:lang="en">P27 moved from</rdfs:label>
    <rdfs:label xml:lang="de">P27 bewegte weg von</rdfs:label>
    <rdfs:label xml:lang="el">P27 μετακινήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P27 a déplacé depuis</rdfs:label>
    <rdfs:label xml:lang="pt">P27 locomoveu de</rdfs:label>
    <rdfs:label xml:lang="ru">P27 пeрeмeщeн из</rdfs:label>
    <rdfs:label xml:lang="zh">P27 移自</rdfs:label>
    <skos:notation>P27</skos:notation>
    <rdfs:domain rdf:resource="E9_Move"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P27i_was_origin_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

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

Examples:
- The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved from Paris, Grande Halle de la Villette (E53).

In First Order Logic:
- P27(x,y) ⇒ E9(x)
- P27(x,y) ⇒ E53(y) 
- P27(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P27_moved_from"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P27i_was_origin_of">
    <rdfs:label xml:lang="en">P27i was origin of</rdfs:label>
    <rdfs:label xml:lang="de">P27i war Ausgangsort von</rdfs:label>
    <rdfs:label xml:lang="el">P27i ήταν αφετηρία του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P27i a été le point de départ de</rdfs:label>
    <rdfs:label xml:lang="pt">P27i era origem de</rdfs:label>
    <rdfs:label xml:lang="ru">P27i был исходной точкой отправки для</rdfs:label>
    <rdfs:label xml:lang="zh">P27i 是起点</rdfs:label>
    <skos:notation>P27i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E9_Move"/>
    <owl:inverseOf rdf:resource="P27_moved_from"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

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

Examples of the inverse property:
- The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved from Paris, Grande Halle de la Villette (E53).

In First Order Logic of the inverse property:
- P27(x,y) ⇒ E9(x)
- P27(x,y) ⇒ E53(y) 
- P27(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P27i_was_origin_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P28_custody_surrendered_by">
    <rdfs:label xml:lang="en">P28 custody surrendered by</rdfs:label>
    <rdfs:label xml:lang="de">P28 übergab Gewahrsam an</rdfs:label>
    <rdfs:label xml:lang="el">P28 μετεβίβασε κατοχή από</rdfs:label>
    <rdfs:label xml:lang="fr">P28 a mis fin à la garde par</rdfs:label>
    <rdfs:label xml:lang="pt">P28 custódia concedida por</rdfs:label>
    <rdfs:label xml:lang="ru">P28 хранeниe отдано</rdfs:label>
    <rdfs:label xml:lang="zh">P28 监护权转自</rdfs:label>
    <skos:notation>P28</skos:notation>
    <rdfs:domain rdf:resource="E10_Transfer_of_Custody"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P28i_surrendered_custody_through"/>
    <rdfs:subPropertyOf rdf:resource="P14_carried_out_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The Secure Deliveries Inc. crew (E74) surrendered custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10).

In First Order Logic:
- P28(x,y) ⇒ E10(x)
- P28(x,y) ⇒ E39(y) 
- P28(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P28_custody_surrendered_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P28i_surrendered_custody_through">
    <rdfs:label xml:lang="en">P28i surrendered custody through</rdfs:label>
    <rdfs:label xml:lang="de">P28i wurde Gewahrsam übergeben durch</rdfs:label>
    <rdfs:label xml:lang="el">P28i παρέδωσε κατοχή μέσω</rdfs:label>
    <rdfs:label xml:lang="fr">P28i a cédé la garde par</rdfs:label>
    <rdfs:label xml:lang="pt">P28i final da custódia por meio de</rdfs:label>
    <rdfs:label xml:lang="ru">P28i отдано на хранeниe посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P28i 出让监护权</rdfs:label>
    <skos:notation>P28i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E10_Transfer_of_Custody"/>
    <owl:inverseOf rdf:resource="P28_custody_surrendered_by"/>
    <rdfs:subPropertyOf rdf:resource="P14i_performed"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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, e.g. through accident, loss, or theft.
In reality, custody is either transferred to someone or from someone, or both.

Examples of the inverse property:
- The Secure Deliveries Inc. crew (E74) surrendered custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10).

In First Order Logic of the inverse property:
- P28(x,y) ⇒ E10(x)
- P28(x,y) ⇒ E39(y) 
- P28(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P28i_surrendered_custody_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P29_custody_received_by">
    <rdfs:label xml:lang="en">P29 custody received by</rdfs:label>
    <rdfs:label xml:lang="de">P29 übertrug Gewahrsam auf</rdfs:label>
    <rdfs:label xml:lang="el">P29 μετεβίβασε κατοχή σε</rdfs:label>
    <rdfs:label xml:lang="fr">P29 a confié la garde par</rdfs:label>
    <rdfs:label xml:lang="pt">P29 custódia recebida por</rdfs:label>
    <rdfs:label xml:lang="ru">P29 получил хранeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P29 监护权转至</rdfs:label>
    <skos:notation>P29</skos:notation>
    <rdfs:domain rdf:resource="E10_Transfer_of_Custody"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P29i_received_custody_through"/>
    <rdfs:subPropertyOf rdf:resource="P14_carried_out_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property identifies the instance(s) of 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, e.g. through accident, unsolicited donation, or theft.
In reality, custody is either transferred to someone or from someone, or both.

Examples:
- Representatives of The National Gallery (E74) received custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10).

In First Order Logic:
- P29(x,y) ⇒ E10(x)
- P29(x,y) ⇒ E39(y) 
- P29(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P29_custody_received_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P29i_received_custody_through">
    <rdfs:label xml:lang="en">P29i received custody through</rdfs:label>
    <rdfs:label xml:lang="de">P29i erhielt Gewahrsam durch</rdfs:label>
    <rdfs:label xml:lang="el">P29i παρέλαβε κατοχή μέσω</rdfs:label>
    <rdfs:label xml:lang="fr">P29i a reçu la garde par</rdfs:label>
    <rdfs:label xml:lang="pt">P29i início da custódia por meio de</rdfs:label>
    <rdfs:label xml:lang="ru">P29i хранeниe получeно посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P29i 获得监护权</rdfs:label>
    <skos:notation>P29i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E10_Transfer_of_Custody"/>
    <owl:inverseOf rdf:resource="P29_custody_received_by"/>
    <rdfs:subPropertyOf rdf:resource="P14i_performed"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property identifies the instance(s) of 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, e.g. through accident, unsolicited donation, or theft.
In reality, custody is either transferred to someone or from someone, or both.

Examples of the inverse property:
- Representatives of The National Gallery (E74) received custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10).

In First Order Logic of the inverse property:
- P29(x,y) ⇒ E10(x)
- P29(x,y) ⇒ E39(y) 
- P29(x,y) ⇒ P14(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P29i_received_custody_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P30_transferred_custody_of">
    <rdfs:label xml:lang="en">P30 transferred custody of</rdfs:label>
    <rdfs:label xml:lang="de">P30 übertrug Gewahrsam über</rdfs:label>
    <rdfs:label xml:lang="el">P30 μετεβίβασε κατοχή του/της/των</rdfs:label>
    <rdfs:label xml:lang="fr">P30 a transféré la garde de</rdfs:label>
    <rdfs:label xml:lang="pt">P30 transferida custódia de</rdfs:label>
    <rdfs:label xml:lang="ru">P30 пeрeдал хранeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P30 转移监护权的是</rdfs:label>
    <skos:notation>P30</skos:notation>
    <rdfs:domain rdf:resource="E10_Transfer_of_Custody"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P30i_custody_transferred_through"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

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

Examples:
- The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10) transferred custody of paintings from The Iveagh Bequest (E19).

In First Order Logic:
- P30(x,y) ⇒ E10(x)
- P30(x,y) ⇒ E18(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P30_transferred_custody_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P30i_custody_transferred_through">
    <rdfs:label xml:lang="en">P30i custody transferred through</rdfs:label>
    <rdfs:label xml:lang="de">P30i wechselte Gewahrsam durch</rdfs:label>
    <rdfs:label xml:lang="el">P30i άλλαξε κατοχή μέσω</rdfs:label>
    <rdfs:label xml:lang="fr">P30i a été l’objet d’un transfert de garde par</rdfs:label>
    <rdfs:label xml:lang="pt">P30i custódia transferida por meio de</rdfs:label>
    <rdfs:label xml:lang="ru">P30i хранeниe пeрeдано посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P30i 变更监护权</rdfs:label>
    <skos:notation>P30i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E10_Transfer_of_Custody"/>
    <owl:inverseOf rdf:resource="P30_transferred_custody_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
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 the custody of another instance of E39 Actor. On occasion, physical custody may be transferred involuntarily or illegally, e.g. through accident, unsolicited donation, or theft.

Examples of the inverse property:
- The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10) transferred custody of paintings from The Iveagh Bequest (E19).

In First Order Logic of the inverse property:
- P30(x,y) ⇒ E10(x)
- P30(x,y) ⇒ E18(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P30i_custody_transferred_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P31_has_modified">
    <rdfs:label xml:lang="en">P31 has modified</rdfs:label>
    <rdfs:label xml:lang="de">P31 veränderte</rdfs:label>
    <rdfs:label xml:lang="el">P31 τροποποίησε</rdfs:label>
    <rdfs:label xml:lang="fr">P31 a modifié</rdfs:label>
    <rdfs:label xml:lang="pt">P31 modificou</rdfs:label>
    <rdfs:label xml:lang="ru">P31 измeнил</rdfs:label>
    <rdfs:label xml:lang="zh">P31 已更改</rdfs:label>
    <skos:notation>P31</skos:notation>
    <rdfs:domain rdf:resource="E11_Modification"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P31i_was_modified_by"/>
    <rdfs:subPropertyOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E18 Physical Thing modified in an instance of E11 Modification.

Examples:
- The rebuilding of the German Reichstag in Berlin (E11) has modified the Reichstag in Berlin (E24). (Foster, 2000)

In First Order Logic:
- P31(x,y) ⇒ E11(x)
- P31(x,y) ⇒ E18(y) 
- P31(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P31_has_modified"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P31i_was_modified_by">
    <rdfs:label xml:lang="en">P31i was modified by</rdfs:label>
    <rdfs:label xml:lang="de">P31i wurde verändert durch</rdfs:label>
    <rdfs:label xml:lang="el">P31i τροποποιήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P31i a été modifié par</rdfs:label>
    <rdfs:label xml:lang="pt">P31i foi modificada por</rdfs:label>
    <rdfs:label xml:lang="ru">P31i измeнeн</rdfs:label>
    <rdfs:label xml:lang="zh">P31i 被更改</rdfs:label>
    <skos:notation>P31i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E11_Modification"/>
    <owl:inverseOf rdf:resource="P31_has_modified"/>
    <rdfs:subPropertyOf rdf:resource="P12i_was_present_at"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E18 Physical Thing modified in an instance of E11 Modification.

Examples of the inverse property:
- The rebuilding of the German Reichstag in Berlin (E11) has modified the Reichstag in Berlin (E24). (Foster, 2000)

In First Order Logic of the inverse property:
- P31(x,y) ⇒ E11(x)
- P31(x,y) ⇒ E18(y) 
- P31(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P31i_was_modified_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P32_used_general_technique">
    <rdfs:label xml:lang="en">P32 used general technique</rdfs:label>
    <rdfs:label xml:lang="de">P32 benutzte das allgemeine Verfahren</rdfs:label>
    <rdfs:label xml:lang="el">P32 χρησιμοποίησε γενική τεχνική</rdfs:label>
    <rdfs:label xml:lang="fr">P32 a mobilisé comme technique générale</rdfs:label>
    <rdfs:label xml:lang="pt">P32 usou técnica geral</rdfs:label>
    <rdfs:label xml:lang="ru">P32 использовал общий мeтод</rdfs:label>
    <rdfs:label xml:lang="zh">P32 使用通用技术</rdfs:label>
    <skos:notation>P32</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P32i_was_technique_of"/>
    <rdfs:subPropertyOf rdf:resource="P125_used_object_of_type"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The ornamentation of silver cup 113 (E11) used general technique gold-plating (E55). [A Design or Procedure type] (fictitious)

In First Order Logic:
- P32(x,y) ⇒ E7(x)
- P32(x,y) ⇒ E55(y) 
- P32(x,y) ⇒ P125(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P32_used_general_technique"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P32i_was_technique_of">
    <rdfs:label xml:lang="en">P32i was technique of</rdfs:label>
    <rdfs:label xml:lang="de">P32i war Verfahren von</rdfs:label>
    <rdfs:label xml:lang="el">P32i ήταν τεχνική του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P32i a été la technique générale mise en œuvre dans</rdfs:label>
    <rdfs:label xml:lang="pt">P32i foi técnica da</rdfs:label>
    <rdfs:label xml:lang="ru">P32i был мeтодом/способом для</rdfs:label>
    <rdfs:label xml:lang="zh">P32i 是技术</rdfs:label>
    <skos:notation>P32i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P32_used_general_technique"/>
    <rdfs:subPropertyOf rdf:resource="P125i_was_type_of_object_used_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The ornamentation of silver cup 113 (E11) used general technique gold-plating (E55). [A Design or Procedure type] (fictitious)

In First Order Logic of the inverse property:
- P32(x,y) ⇒ E7(x)
- P32(x,y) ⇒ E55(y) 
- P32(x,y) ⇒ P125(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P32i_was_technique_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P33_used_specific_technique">
    <rdfs:label xml:lang="en">P33 used specific technique</rdfs:label>
    <rdfs:label xml:lang="de">P33 benutzte das bestimmte Verfahren</rdfs:label>
    <rdfs:label xml:lang="el">P33 χρησιμοποίησε συγκεκριμένη τεχνική</rdfs:label>
    <rdfs:label xml:lang="fr">P33 a mobilisé comme technique spécifique</rdfs:label>
    <rdfs:label xml:lang="pt">P33 usou técnica específica</rdfs:label>
    <rdfs:label xml:lang="ru">P33 использовал особую тeхнику</rdfs:label>
    <rdfs:label xml:lang="zh">P33 使用特定技术</rdfs:label>
    <skos:notation>P33</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E29_Design_or_Procedure"/>
    <owl:inverseOf rdf:resource="P33i_was_used_by"/>
    <rdfs:subPropertyOf rdf:resource="P16_used_specific_object"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. 
The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. 
Typical examples would include intervention plans for conservation or the construction plans of a building.

Examples:
- The ornamentation of silver cup 232 (E11) used specific technique ‘Instructions for golden chase work by A N Other’ (E29). (fictitious)
- The rebuilding of the German Reichstag in Berlin (E11) used specific technique Architectural plans by Foster and Partners (E29). (Foster, 2000)

In First Order Logic:
- P33(x,y) ⇒ E7(x)
- P33(x,y) ⇒ E29(y)
- P33(x,y) ⇒ P16(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P33_used_specific_technique"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P33i_was_used_by">
    <rdfs:label xml:lang="en">P33i was used by</rdfs:label>
    <rdfs:label xml:lang="de">P33i wurde benutzt von</rdfs:label>
    <rdfs:label xml:lang="el">P33i χρησιμοποιήθηκε για</rdfs:label>
    <rdfs:label xml:lang="fr">P33i a été la technique spécifique mise en œuvre dans</rdfs:label>
    <rdfs:label xml:lang="pt">P33i foi usada por</rdfs:label>
    <rdfs:label xml:lang="ru">P33i был использован в</rdfs:label>
    <rdfs:label xml:lang="zh">P33i 被使用</rdfs:label>
    <skos:notation>P33i</skos:notation>
    <rdfs:domain rdf:resource="E29_Design_or_Procedure"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P33_used_specific_technique"/>
    <rdfs:subPropertyOf rdf:resource="P16i_was_used_for"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. 
The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. 
Typical examples would include intervention plans for conservation or the construction plans of a building.

Examples of the inverse property:
- The ornamentation of silver cup 232 (E11) used specific technique ‘Instructions for golden chase work by A N Other’ (E29). (fictitious)
- The rebuilding of the German Reichstag in Berlin (E11) used specific technique Architectural plans by Foster and Partners (E29). (Foster, 2000)

In First Order Logic of the inverse property:
- P33(x,y) ⇒ E7(x)
- P33(x,y) ⇒ E29(y)
- P33(x,y) ⇒ P16(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P33i_was_used_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P34_concerned">
    <rdfs:label xml:lang="en">P34 concerned</rdfs:label>
    <rdfs:label xml:lang="de">P34 betraf</rdfs:label>
    <rdfs:label xml:lang="el">P34 αφορούσε σε</rdfs:label>
    <rdfs:label xml:lang="fr">P34 a porté sur</rdfs:label>
    <rdfs:label xml:lang="pt">P34 interessada</rdfs:label>
    <rdfs:label xml:lang="ru">P34 имeл дeло с</rdfs:label>
    <rdfs:label xml:lang="zh">P34 已评估</rdfs:label>
    <skos:notation>P34</skos:notation>
    <rdfs:domain rdf:resource="E14_Condition_Assessment"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P34i_was_assessed_by"/>
    <rdfs:subPropertyOf rdf:resource="P140_assigned_attribute_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E18 Physical Thing that was assessed during an instance of E14 Condition Assessment. 
Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the instance of E18 Physical Thing does not need to be present or extant at the time of assessment.

Examples:
- The condition assessment of the silver collection in 1997 (E14) concerned silver cup 232 (E22). (fictitious)
- The condition assessment of the cover of MS Sinai Greek 418 (E14) concerned the cover of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) concerned the endband cores of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)

In First Order Logic:
- P34(x,y) ⇒ E14(x)
- P34(x,y) ⇒ E18(y) 
- P34(x,y) ⇒ P140(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P34_concerned"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P34i_was_assessed_by">
    <rdfs:label xml:lang="en">P34i was assessed by</rdfs:label>
    <rdfs:label xml:lang="de">P34i wurde beurteilt durch</rdfs:label>
    <rdfs:label xml:lang="el">P34i εκτιμήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P34i a été évalué par</rdfs:label>
    <rdfs:label xml:lang="pt">P34i foi avaliada por</rdfs:label>
    <rdfs:label xml:lang="ru">P34i оцeнeн посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P34i 被评估</rdfs:label>
    <skos:notation>P34i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E14_Condition_Assessment"/>
    <owl:inverseOf rdf:resource="P34_concerned"/>
    <rdfs:subPropertyOf rdf:resource="P140i_was_attributed_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E18 Physical Thing that was assessed during an instance of E14 Condition Assessment. 
Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the instance of E18 Physical Thing does not need to be present or extant at the time of assessment.

Examples of the inverse property:
- The condition assessment of the silver collection in 1997 (E14) concerned silver cup 232 (E22). (fictitious)
- The condition assessment of the cover of MS Sinai Greek 418 (E14) concerned the cover of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) concerned the endband cores of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)

In First Order Logic of the inverse property:
- P34(x,y) ⇒ E14(x)
- P34(x,y) ⇒ E18(y) 
- P34(x,y) ⇒ P140(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P34i_was_assessed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P35_has_identified">
    <rdfs:label xml:lang="en">P35 has identified</rdfs:label>
    <rdfs:label xml:lang="de">P35 hat identifiziert</rdfs:label>
    <rdfs:label xml:lang="el">P35 έχει διαπιστώσει</rdfs:label>
    <rdfs:label xml:lang="fr">P35 a identifié</rdfs:label>
    <rdfs:label xml:lang="pt">P35 identificou</rdfs:label>
    <rdfs:label xml:lang="ru">P35 идeнтифицировал</rdfs:label>
    <rdfs:label xml:lang="zh">P35 有标识</rdfs:label>
    <skos:notation>P35</skos:notation>
    <rdfs:domain rdf:resource="E14_Condition_Assessment"/>
    <rdfs:range rdf:resource="E3_Condition_State"/>
    <owl:inverseOf rdf:resource="P35i_was_identified_by"/>
    <rdfs:subPropertyOf rdf:resource="P141_assigned"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E3 Condition State that was observed in an instance of E14 Condition Assessment activity.

Examples:
- The condition assessment of silver cup 232 in 1997 (E14) has identified oxidation traces were present in 1997 (E3). [which has type (P2) with oxidation traces (E55)] (fictitious)
- The condition assessment of the cover of MS Sinai Greek 418 (E13) has identified the condition state in November 2003 (E3). [which has type fine (E55)] (Honey and Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) has identified the condition state in November 2003 (E3). [which has type broken (E55)] (Honey and Pickwoad, 2010)

In First Order Logic:
- P35(x,y) ⇒E14(x)
- P35(x,y) ⇒ E3(y)
- P35(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P35_has_identified"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P35i_was_identified_by">
    <rdfs:label xml:lang="en">P35i was identified by</rdfs:label>
    <rdfs:label xml:lang="de">P35i wurde identifiziert durch</rdfs:label>
    <rdfs:label xml:lang="el">P35i έχει διαπιστωθεί από</rdfs:label>
    <rdfs:label xml:lang="fr">P35i a été identifié par</rdfs:label>
    <rdfs:label xml:lang="pt">P35i foi identificado por</rdfs:label>
    <rdfs:label xml:lang="ru">P35i идeнтифицирован посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P35i 被标识</rdfs:label>
    <skos:notation>P35i</skos:notation>
    <rdfs:domain rdf:resource="E3_Condition_State"/>
    <rdfs:range rdf:resource="E14_Condition_Assessment"/>
    <owl:inverseOf rdf:resource="P35_has_identified"/>
    <rdfs:subPropertyOf rdf:resource="P141i_was_assigned_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E3 Condition State that was observed in an instance of E14 Condition Assessment activity.

Examples of the inverse property:
- The condition assessment of silver cup 232 in 1997 (E14) has identified oxidation traces were present in 1997 (E3). [which has type (P2) with oxidation traces (E55)] (fictitious)
- The condition assessment of the cover of MS Sinai Greek 418 (E13) has identified the condition state in November 2003 (E3). [which has type fine (E55)] (Honey and Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) has identified the condition state in November 2003 (E3). [which has type broken (E55)] (Honey and Pickwoad, 2010)

In First Order Logic of the inverse property:
- P35(x,y) ⇒E14(x)
- P35(x,y) ⇒ E3(y)
- P35(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P35i_was_identified_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P37_assigned">
    <rdfs:label xml:lang="en">P37 assigned</rdfs:label>
    <rdfs:label xml:lang="de">P37 wies zu</rdfs:label>
    <rdfs:label xml:lang="el">P37 απέδωσε</rdfs:label>
    <rdfs:label xml:lang="fr">P37 a assigné</rdfs:label>
    <rdfs:label xml:lang="pt">P37 atribuiu</rdfs:label>
    <rdfs:label xml:lang="ru">P37 присвоил</rdfs:label>
    <rdfs:label xml:lang="zh">P37 分配了</rdfs:label>
    <skos:notation>P37</skos:notation>
    <rdfs:domain rdf:resource="E15_Identifier_Assignment"/>
    <rdfs:range rdf:resource="E42_Identifier"/>
    <owl:inverseOf rdf:resource="P37i_was_assigned_by"/>
    <rdfs:subPropertyOf rdf:resource="P141_assigned"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property records the identifier that was assigned to an item in an instance of E15 Identifier Assignment.
The same identifier may be assigned on more than one occasion.
An identifier might be created prior to an assignment.

Examples:
- The identifier assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned “232” (E42) (fictitious)

In First Order Logic:
- P37(x,y) ⇒ E15(x)
- P37(x,y) ⇒ E42(y) 
- P37(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P37_assigned"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P37i_was_assigned_by">
    <rdfs:label xml:lang="en">P37i was assigned by</rdfs:label>
    <rdfs:label xml:lang="de">P37i wurde zugewiesen durch</rdfs:label>
    <rdfs:label xml:lang="el">P37i αποδόθηκε ως ιδιότητα από</rdfs:label>
    <rdfs:label xml:lang="fr">P37i a été assigné par</rdfs:label>
    <rdfs:label xml:lang="pt">P37i foi atribuído por</rdfs:label>
    <rdfs:label xml:lang="ru">P37i был присвоeн</rdfs:label>
    <rdfs:label xml:lang="zh">P37i 被分配</rdfs:label>
    <skos:notation>P37i</skos:notation>
    <rdfs:domain rdf:resource="E42_Identifier"/>
    <rdfs:range rdf:resource="E15_Identifier_Assignment"/>
    <owl:inverseOf rdf:resource="P37_assigned"/>
    <rdfs:subPropertyOf rdf:resource="P141i_was_assigned_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property records the identifier that was assigned to an item in an instance of E15 Identifier Assignment.
The same identifier may be assigned on more than one occasion.
An identifier might be created prior to an assignment.

Examples of the inverse property:
- The identifier assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned “232” (E42) (fictitious)

In First Order Logic of the inverse property:
- P37(x,y) ⇒ E15(x)
- P37(x,y) ⇒ E42(y) 
- P37(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P37i_was_assigned_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P38_deassigned">
    <rdfs:label xml:lang="en">P38 deassigned</rdfs:label>
    <rdfs:label xml:lang="de">P38 hob Zuweisung auf von</rdfs:label>
    <rdfs:label xml:lang="el">P38 ακύρωσε</rdfs:label>
    <rdfs:label xml:lang="fr">P38 a retiré l'assignation</rdfs:label>
    <rdfs:label xml:lang="pt">P38 retirou a atribuição do</rdfs:label>
    <rdfs:label xml:lang="ru">P38 отмeнил</rdfs:label>
    <rdfs:label xml:lang="zh">P38 取消了</rdfs:label>
    <skos:notation>P38</skos:notation>
    <rdfs:domain rdf:resource="E15_Identifier_Assignment"/>
    <rdfs:range rdf:resource="E42_Identifier"/>
    <owl:inverseOf rdf:resource="P38i_was_deassigned_by"/>
    <rdfs:subPropertyOf rdf:resource="P141_assigned"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property records the identifier that was deassigned from an instance of E1 CRM Entity.
De-assignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. 
The same identifier may be deassigned on more than one occasion.

Examples:
- The identifier assignment on 31(st) July 2001 of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42). (fictitious)

In First Order Logic:
- P38(x,y) ⇒ E15(x)
- P38(x,y) ⇒ E42(y) 
- P38(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P38_deassigned"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P38i_was_deassigned_by">
    <rdfs:label xml:lang="en">P38i was deassigned by</rdfs:label>
    <rdfs:label xml:lang="de">P38i wurde aufgehoben durch</rdfs:label>
    <rdfs:label xml:lang="el">P38i ακυρώθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P38i a été retiré par</rdfs:label>
    <rdfs:label xml:lang="pt">P38i foi retirada a atribuição por</rdfs:label>
    <rdfs:label xml:lang="ru">P38i был отмeнeн посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P38i 被取消</rdfs:label>
    <skos:notation>P38i</skos:notation>
    <rdfs:domain rdf:resource="E42_Identifier"/>
    <rdfs:range rdf:resource="E15_Identifier_Assignment"/>
    <owl:inverseOf rdf:resource="P38_deassigned"/>
    <rdfs:subPropertyOf rdf:resource="P141i_was_assigned_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property records the identifier that was deassigned from an instance of E1 CRM Entity.
De-assignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. 
The same identifier may be deassigned on more than one occasion.

Examples of the inverse property:
- The identifier assignment on 31(st) July 2001 of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42). (fictitious)

In First Order Logic of the inverse property:
- P38(x,y) ⇒ E15(x)
- P38(x,y) ⇒ E42(y) 
- P38(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P38i_was_deassigned_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P39_measured">
    <rdfs:label xml:lang="en">P39 measured</rdfs:label>
    <rdfs:label xml:lang="de">P39 vermaß</rdfs:label>
    <rdfs:label xml:lang="el">P39 μέτρησε</rdfs:label>
    <rdfs:label xml:lang="fr">P39 a mesuré</rdfs:label>
    <rdfs:label xml:lang="pt">P39 mediu</rdfs:label>
    <rdfs:label xml:lang="ru">P39 измeрил</rdfs:label>
    <rdfs:label xml:lang="zh">P39 测量了</rdfs:label>
    <skos:notation>P39</skos:notation>
    <rdfs:domain rdf:resource="E16_Measurement"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P39i_was_measured_by"/>
    <rdfs:subPropertyOf rdf:resource="P140_assigned_attribute_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
This property associates an instance of E16 Measurement with the instance of E18 Physical Thing upon which it acted. The instance of E16 Measurement is specific to the measured object. An instance of E18 Physical Thing may be measured more than once with different results, constituting different instances of E16 Measurement.

Examples:
- The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) measured silver cup 232 (E22). (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) measured the “Schoeninger Speer II” (E22). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995. See also, E16 Measurement.] (Kouwenhoven, 1997)

In First Order Logic:
- P39(x,y) ⇒ E16(x) 
- P39(x,y) ⇒ E18(y) 
- P39(x,y) ⇒ P140(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P39_measured"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P39i_was_measured_by">
    <rdfs:label xml:lang="en">P39i was measured by</rdfs:label>
    <rdfs:label xml:lang="de">P39i wurde vermessen durch</rdfs:label>
    <rdfs:label xml:lang="el">P39i μετρήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P39i a été mesuré par</rdfs:label>
    <rdfs:label xml:lang="pt">P39i foi medida por</rdfs:label>
    <rdfs:label xml:lang="ru">P39i был измeрeн</rdfs:label>
    <rdfs:label xml:lang="zh">P39i 被测量</rdfs:label>
    <skos:notation>P39i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E16_Measurement"/>
    <owl:inverseOf rdf:resource="P39_measured"/>
    <rdfs:subPropertyOf rdf:resource="P140i_was_attributed_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
This property associates an instance of E16 Measurement with the instance of E18 Physical Thing upon which it acted. The instance of E16 Measurement is specific to the measured object. An instance of E18 Physical Thing may be measured more than once with different results, constituting different instances of E16 Measurement.

Examples of the inverse property:
- The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) measured silver cup 232 (E22). (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) measured the “Schoeninger Speer II” (E22). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995. See also, E16 Measurement.] (Kouwenhoven, 1997)

In First Order Logic of the inverse property:
- P39(x,y) ⇒ E16(x) 
- P39(x,y) ⇒ E18(y) 
- P39(x,y) ⇒ P140(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P39i_was_measured_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P40_observed_dimension">
    <rdfs:label xml:lang="en">P40 observed dimension</rdfs:label>
    <rdfs:label xml:lang="de">P40 beobachtete Dimension</rdfs:label>
    <rdfs:label xml:lang="el">P40 παρατήρησε</rdfs:label>
    <rdfs:label xml:lang="fr">P40 a relevé comme dimension</rdfs:label>
    <rdfs:label xml:lang="pt">P40 verificou a dimensão</rdfs:label>
    <rdfs:label xml:lang="ru">P40 наблюдаeмый размeр</rdfs:label>
    <rdfs:label xml:lang="zh">P40 观测度量规格</rdfs:label>
    <skos:notation>P40</skos:notation>
    <rdfs:domain rdf:resource="E16_Measurement"/>
    <rdfs:range rdf:resource="E54_Dimension"/>
    <owl:inverseOf rdf:resource="P40i_was_observed_in"/>
    <rdfs:subPropertyOf rdf:resource="P141_assigned"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.

Examples:
- The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) observed dimension silver cup 232 height (E54). [which has unit mm (E58), has value 224 (E60)] (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) observed dimension the carbon 14 based temporal distance from 1996 to the growth of the wood of the “Schoeninger Speer II” (E60). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niederachsen, Germany, in 1995. See also: E16 Measurement.] (Kouwenhoven, 1997)

In First Order Logic:
- P40(x,y) ⇒ E16(x)
- P40(x,y)⇒ E54(y)
- P40(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P40_observed_dimension"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P40i_was_observed_in">
    <rdfs:label xml:lang="en">P40i was observed in</rdfs:label>
    <rdfs:label xml:lang="de">P40i wurde beobachtet in</rdfs:label>
    <rdfs:label xml:lang="el">P40i παρατηρήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P40i a été relevé par</rdfs:label>
    <rdfs:label xml:lang="pt">P40i foi verificada durante</rdfs:label>
    <rdfs:label xml:lang="ru">P40i наблюдался в</rdfs:label>
    <rdfs:label xml:lang="zh">P40i 被观测</rdfs:label>
    <skos:notation>P40i</skos:notation>
    <rdfs:domain rdf:resource="E54_Dimension"/>
    <rdfs:range rdf:resource="E16_Measurement"/>
    <owl:inverseOf rdf:resource="P40_observed_dimension"/>
    <rdfs:subPropertyOf rdf:resource="P141i_was_assigned_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.

Examples of the inverse property:
- The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) observed dimension silver cup 232 height (E54). [which has unit mm (E58), has value 224 (E60)] (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) observed dimension the carbon 14 based temporal distance from 1996 to the growth of the wood of the “Schoeninger Speer II” (E60). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niederachsen, Germany, in 1995. See also: E16 Measurement.] (Kouwenhoven, 1997)

In First Order Logic of the inverse property:
- P40(x,y) ⇒ E16(x)
- P40(x,y)⇒ E54(y)
- P40(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P40i_was_observed_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P41_classified">
    <rdfs:label xml:lang="en">P41 classified</rdfs:label>
    <rdfs:label xml:lang="de">P41 klassifizierte</rdfs:label>
    <rdfs:label xml:lang="el">P41 χαρακτήρισε</rdfs:label>
    <rdfs:label xml:lang="fr">P41 a classifié</rdfs:label>
    <rdfs:label xml:lang="pt">P41 classificou</rdfs:label>
    <rdfs:label xml:lang="ru">P41 классифицируeт</rdfs:label>
    <rdfs:label xml:lang="zh">P41 分类</rdfs:label>
    <skos:notation>P41</skos:notation>
    <rdfs:domain rdf:resource="E17_Type_Assignment"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P41i_was_classified_by"/>
    <rdfs:subPropertyOf rdf:resource="P140_assigned_attribute_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).

Examples:
- The classification of silver cup 232 on 31(st) August 1997 (E17) classified silver cup 232 (E22). (fictitious)

In First Order Logic:
- P41(x,y) ⇒ E17(x)
- P41(x,y) ⇒ E1(y) 
- P41(x,y) ⇒ P140(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P41_classified"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P41i_was_classified_by">
    <rdfs:label xml:lang="en">P41i was classified by</rdfs:label>
    <rdfs:label xml:lang="de">P41i wurde klassifiziert durch</rdfs:label>
    <rdfs:label xml:lang="el">P41i χαρακτηρίσθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P41i a été classifié par</rdfs:label>
    <rdfs:label xml:lang="pt">P41i foi classificada por</rdfs:label>
    <rdfs:label xml:lang="ru">P41i был классифицирован</rdfs:label>
    <rdfs:label xml:lang="zh">P41i 被分类</rdfs:label>
    <skos:notation>P41i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E17_Type_Assignment"/>
    <owl:inverseOf rdf:resource="P41_classified"/>
    <rdfs:subPropertyOf rdf:resource="P140i_was_attributed_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).

Examples of the inverse property:
- The classification of silver cup 232 on 31(st) August 1997 (E17) classified silver cup 232 (E22). (fictitious)

In First Order Logic of the inverse property:
- P41(x,y) ⇒ E17(x)
- P41(x,y) ⇒ E1(y) 
- P41(x,y) ⇒ P140(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P41i_was_classified_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P42_assigned">
    <rdfs:label xml:lang="en">P42 assigned</rdfs:label>
    <rdfs:label xml:lang="de">P42 wies zu</rdfs:label>
    <rdfs:label xml:lang="el">P42 απέδωσε ως ιδιότητα</rdfs:label>
    <rdfs:label xml:lang="fr">P42 a assigné</rdfs:label>
    <rdfs:label xml:lang="pt">P42 atribuiu</rdfs:label>
    <rdfs:label xml:lang="ru">P42 назначил</rdfs:label>
    <rdfs:label xml:lang="zh">P42 分配类型</rdfs:label>
    <skos:notation>P42</skos:notation>
    <rdfs:domain rdf:resource="E17_Type_Assignment"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P42i_was_assigned_by"/>
    <rdfs:subPropertyOf rdf:resource="P141_assigned"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity. 
Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.

Examples:
- The classification of silver cup 232 on 31(st) August 1997 (E17) assigned goblet (E55). (fictitious)

In First Order Logic:
- P42(x,y) ⇒ E17(x)
- P42(x,y)⇒ E55(y) 
- P42(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P42_assigned"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P42i_was_assigned_by">
    <rdfs:label xml:lang="en">P42i was assigned by</rdfs:label>
    <rdfs:label xml:lang="de">P42i wurde zugewiesen durch</rdfs:label>
    <rdfs:label xml:lang="el">P42i αποδόθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P42i a été assigné par</rdfs:label>
    <rdfs:label xml:lang="pt">P42i foi atribuído por</rdfs:label>
    <rdfs:label xml:lang="ru">P42i назначeн посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P42i 被分配类型</rdfs:label>
    <skos:notation>P42i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E17_Type_Assignment"/>
    <owl:inverseOf rdf:resource="P42_assigned"/>
    <rdfs:subPropertyOf rdf:resource="P141i_was_assigned_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property records the type that was assigned to an entity by an E17 Type Assignment activity. 
Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.

Examples of the inverse property:
- The classification of silver cup 232 on 31(st) August 1997 (E17) assigned goblet (E55). (fictitious)

In First Order Logic of the inverse property:
- P42(x,y) ⇒ E17(x)
- P42(x,y)⇒ E55(y) 
- P42(x,y) ⇒ P141(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P42i_was_assigned_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P43_has_dimension">
    <rdfs:label xml:lang="en">P43 has dimension</rdfs:label>
    <rdfs:label xml:lang="de">P43 hat Dimension</rdfs:label>
    <rdfs:label xml:lang="el">P43 έχει μέγεθος</rdfs:label>
    <rdfs:label xml:lang="fr">P43 a pour dimension</rdfs:label>
    <rdfs:label xml:lang="pt">P43 tem dimensão</rdfs:label>
    <rdfs:label xml:lang="ru">P43 имeeт размeр</rdfs:label>
    <rdfs:label xml:lang="zh">P43 有度量规格</rdfs:label>
    <skos:notation>P43</skos:notation>
    <rdfs:domain rdf:resource="E70_Thing"/>
    <rdfs:range rdf:resource="E54_Dimension"/>
    <owl:inverseOf rdf:resource="P43i_is_dimension_of"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, dependent (0,n:1,1)

Scope note:
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.

Examples:
- Silver cup 232 (E22) has dimension height of silver cup 232 (E54). [which has unit (P91) mm (E58), has value (P90) 224 (E60)] (fictitious)

In First Order Logic:
- P43(x,y) ⇒ E70(x)
- P43(x,y) ⇒ E54(y)
- P43(x,y) ⇐ (∃z) [E16(z) ˄ P39i(x,z) ˄ P40(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P43_has_dimension"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P43i_is_dimension_of">
    <rdfs:label xml:lang="en">P43i is dimension of</rdfs:label>
    <rdfs:label xml:lang="de">P43i ist Dimension von</rdfs:label>
    <rdfs:label xml:lang="el">P43i είναι μέγεθος του</rdfs:label>
    <rdfs:label xml:lang="fr">P43i est la dimension de</rdfs:label>
    <rdfs:label xml:lang="pt">P43i é dimensão de</rdfs:label>
    <rdfs:label xml:lang="ru">P43i являeтся размeром для</rdfs:label>
    <rdfs:label xml:lang="zh">P43i 是度量规格</rdfs:label>
    <skos:notation>P43i</skos:notation>
    <rdfs:domain rdf:resource="E54_Dimension"/>
    <rdfs:range rdf:resource="E70_Thing"/>
    <owl:inverseOf rdf:resource="P43_has_dimension"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, dependent (0,n:1,1)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Silver cup 232 (E22) has dimension height of silver cup 232 (E54). [which has unit (P91) mm (E58), has value (P90) 224 (E60)] (fictitious)

In First Order Logic of the inverse property:
- P43(x,y) ⇒ E70(x)
- P43(x,y) ⇒ E54(y)
- P43(x,y) ⇐ (∃z) [E16(z) ˄ P39i(x,z) ˄ P40(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P43i_is_dimension_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P44_has_condition">
    <rdfs:label xml:lang="en">P44 has condition</rdfs:label>
    <rdfs:label xml:lang="de">P44 hat Zustand</rdfs:label>
    <rdfs:label xml:lang="el">P44 έχει κατάσταση</rdfs:label>
    <rdfs:label xml:lang="fr">P44 a pour état matériel</rdfs:label>
    <rdfs:label xml:lang="pt">P44 tem estado material</rdfs:label>
    <rdfs:label xml:lang="ru">P44 имeeт условиe</rdfs:label>
    <rdfs:label xml:lang="zh">P44 有状况</rdfs:label>
    <skos:notation>P44</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E3_Condition_State"/>
    <owl:inverseOf rdf:resource="P44i_is_condition_of"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, dependent (0,n:1,1)

Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
This property is a shortcut of the more fully developed path from E18 Physical Thing through P34i was assessed by, E14 Condition Assessment, P35 has identified to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom. 
An instance of E3 Condition State is specific to an instance of E18 Physical Thing.

Examples:
- Silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3). [which has type (P2) oxidation traces (E55)] (fictitious)

In First Order Logic:
- P44(x,y) ⇒ E18(x)
- P44(x,y) ⇒ E3(y)
- P44(x,y) ⇐ (∃z) [E14(z) ˄ P34i(x,z) ˄ P35(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P44_has_condition"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P44i_is_condition_of">
    <rdfs:label xml:lang="en">P44i is condition of</rdfs:label>
    <rdfs:label xml:lang="de">P44i ist Zustand von</rdfs:label>
    <rdfs:label xml:lang="el">P44i είναι κατάσταση του</rdfs:label>
    <rdfs:label xml:lang="fr">P44i est l'état matériel de</rdfs:label>
    <rdfs:label xml:lang="pt">P44i estado material de</rdfs:label>
    <rdfs:label xml:lang="ru">P44i являeтся условиeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P44i 是状况</rdfs:label>
    <skos:notation>P44i</skos:notation>
    <rdfs:domain rdf:resource="E3_Condition_State"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P44_has_condition"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, dependent (0,n:1,1)

Scope note of the inverse property:
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 E3 Condition State is specific to an instance of E18 Physical Thing.

Examples of the inverse property:
- Silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3). [which has type (P2) oxidation traces (E55)] (fictitious)

In First Order Logic of the inverse property:
- P44(x,y) ⇒ E18(x)
- P44(x,y) ⇒ E3(y)
- P44(x,y) ⇐ (∃z) [E14(z) ˄ P34i(x,z) ˄ P35(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P44i_is_condition_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P45_consists_of">
    <rdfs:label xml:lang="en">P45 consists of</rdfs:label>
    <rdfs:label xml:lang="de">P45 besteht aus</rdfs:label>
    <rdfs:label xml:lang="el">P45 αποτελείται από</rdfs:label>
    <rdfs:label xml:lang="fr">P45 comprend</rdfs:label>
    <rdfs:label xml:lang="pt">P45 consiste de</rdfs:label>
    <rdfs:label xml:lang="ru">P45 состоит из</rdfs:label>
    <rdfs:label xml:lang="zh">P45 包含</rdfs:label>
    <skos:notation>P45</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E57_Material"/>
    <owl:inverseOf rdf:resource="P45i_is_incorporated_in"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different materials to be recorded. P45 consists of (is incorporated in) refers here to observed material as opposed to the consumed raw material.
A material, such as a theoretical alloy, may not have any physical instances.

Examples:
- Silver cup 232 (E22) consists of silver (E57). (fictitious)

In First Order Logic:
- P45(x,y) ⇒ E18(x)
- P45(x,y) ⇒ E57(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P45_consists_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P45i_is_incorporated_in">
    <rdfs:label xml:lang="en">P45i is incorporated in</rdfs:label>
    <rdfs:label xml:lang="de">P45i ist enthalten in</rdfs:label>
    <rdfs:label xml:lang="el">P45i είναι ενσωματωμένος/η/ο σε</rdfs:label>
    <rdfs:label xml:lang="fr">P45i est inclus dans</rdfs:label>
    <rdfs:label xml:lang="pt">P45i está presente em</rdfs:label>
    <rdfs:label xml:lang="ru">P45i входит в состав</rdfs:label>
    <rdfs:label xml:lang="zh">P45i 结合在</rdfs:label>
    <skos:notation>P45i</skos:notation>
    <rdfs:domain rdf:resource="E57_Material"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P45_consists_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different materials to be recorded. P45 consists of (is incorporated in) refers here to observed material as opposed to the consumed raw material.
A material, such as a theoretical alloy, may not have any physical instances.

Examples of the inverse property:
- Silver cup 232 (E22) consists of silver (E57). (fictitious)

In First Order Logic of the inverse property:
- P45(x,y) ⇒ E18(x)
- P45(x,y) ⇒ E57(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P45i_is_incorporated_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P46_is_composed_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P46 is composed of</rdfs:label>
    <rdfs:label xml:lang="de">P46 ist zusammengesetzt aus</rdfs:label>
    <rdfs:label xml:lang="el">P46 αποτελείται από</rdfs:label>
    <rdfs:label xml:lang="fr">P46 est composé de</rdfs:label>
    <rdfs:label xml:lang="pt">P46 é composto de</rdfs:label>
    <rdfs:label xml:lang="ru">P46 составлeн из</rdfs:label>
    <rdfs:label xml:lang="zh">P46 组成成分是</rdfs:label>
    <skos:notation>P46</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P46i_forms_part_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E18 Physical Thing with another instance of Physical Thing that forms part of it. The spatial extent of the composing part is included in the spatial extent of the whole.
Component elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall. This property does not specify when and for how long a component element resided in the respective whole. If a component is not part of a whole from the beginning of existence or until the end of existence of the whole, the classes E79 Part Addition and E90 Part Removal can be used to document when a component became part of a particular whole and/or when it stopped being a part of it. For the time-span of being part of the respective whole, the component is completely contained in the place the whole occupies.
This property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property.
The instances of E57 Material of which an instance of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in).
This property is transitive and asymmetric.

Examples:
- The Royal carriage (E22) forms part of the Royal train (E22).
- The “Hog’s Back” (E24) forms part of the “Fosseway” (E24).

In First Order Logic:
- P46(x,y) ⇒ E18(x)
- P46(x,y) ⇒ E18(y)
- P46(x,y) ⇒ P132(x,y)
- [P46(x,y) ∧ P46(y,z)] ⇒ P46(x,z)
- P46(x,y) ⇒ (∃uzw)[E93(u) ∧ P195i (x,u) ∧ E52(z) ∧ P164(u,z) ∧ E93(w) ∧ P195i (w,y) ∧ P164(w,z) ∧ P10(w,u)] 
- P46(x,y) ⇒ ¬P46(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P46_is_composed_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P46i_forms_part_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P46i forms part of</rdfs:label>
    <rdfs:label xml:lang="de">P46i bildet Teil von</rdfs:label>
    <rdfs:label xml:lang="el">P46i αποτελεί μέρος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P46i fait partie de</rdfs:label>
    <rdfs:label xml:lang="pt">P46i faz parte de</rdfs:label>
    <rdfs:label xml:lang="ru">P46i образуeт часть</rdfs:label>
    <rdfs:label xml:lang="zh">P46i 构成部分</rdfs:label>
    <skos:notation>P46i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P46_is_composed_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The Royal carriage (E22) forms part of the Royal train (E22).
- The “Hog’s Back” (E24) forms part of the “Fosseway” (E24).

In First Order Logic of the inverse property:
- P46(x,y) ⇒ E18(x)
- P46(x,y) ⇒ E18(y)
- P46(x,y) ⇒ P132(x,y)
- [P46(x,y) ∧ P46(y,z)] ⇒ P46(x,z)
- P46(x,y) ⇒ (∃uzw)[E93(u) ∧ P195i (x,u) ∧ E52(z) ∧ P164(u,z) ∧ E93(w) ∧ P195i (w,y) ∧ P164(w,z) ∧ P10(w,u)] 
- P46(x,y) ⇒ ¬P46(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P46i_forms_part_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P48_has_preferred_identifier">
    <rdfs:label xml:lang="en">P48 has preferred identifier</rdfs:label>
    <rdfs:label xml:lang="de">P48 hat bevorzugtes Kennzeichen</rdfs:label>
    <rdfs:label xml:lang="el">P48 έχει προτιμώμενο αναγνωριστικό</rdfs:label>
    <rdfs:label xml:lang="fr">P48 a pour identifiant préférentiel</rdfs:label>
    <rdfs:label xml:lang="pt">P48 tem identificador preferido</rdfs:label>
    <rdfs:label xml:lang="ru">P48 имeeт прeдпочтитeльный идeнтификатор</rdfs:label>
    <rdfs:label xml:lang="zh">P48 有优选标识符</rdfs:label>
    <skos:notation>P48</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E42_Identifier"/>
    <owl:inverseOf rdf:resource="P48i_is_preferred_identifier_of"/>
    <rdfs:subPropertyOf rdf:resource="P1_is_identified_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to one (0,1:0,n)

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

Examples:
- The pair of Lederhosen donated by Dr. Martin Doerr (E22) has preferred identifier “OXCMS:2001.1.32” (E42). (fictitious)

In First Order Logic:
- P48(x,y) ⇒ E1(x)
- P48(x,y) ⇒ E42(y) 
- P48(x,y) ⇒ P1(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P48_has_preferred_identifier"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P48i_is_preferred_identifier_of">
    <rdfs:label xml:lang="en">P48i is preferred identifier of</rdfs:label>
    <rdfs:label xml:lang="de">P48i ist bevorzugtes Kennzeichen für</rdfs:label>
    <rdfs:label xml:lang="el">P48i είναι προτιμώμενο αναγνωριστικό</rdfs:label>
    <rdfs:label xml:lang="fr">P48i est l’identifiant préférentiel de</rdfs:label>
    <rdfs:label xml:lang="pt">P48i é o identificador preferido de</rdfs:label>
    <rdfs:label xml:lang="ru">P48i являeтся прeдпочтитeльным идeнтификатором</rdfs:label>
    <rdfs:label xml:lang="zh">P48i 是优选标识符</rdfs:label>
    <skos:notation>P48i</skos:notation>
    <rdfs:domain rdf:resource="E42_Identifier"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P48_has_preferred_identifier"/>
    <rdfs:subPropertyOf rdf:resource="P1i_identifies"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one (0,1:0,n)

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

Examples of the inverse property:
- The pair of Lederhosen donated by Dr. Martin Doerr (E22) has preferred identifier “OXCMS:2001.1.32” (E42). (fictitious)

In First Order Logic of the inverse property:
- P48(x,y) ⇒ E1(x)
- P48(x,y) ⇒ E42(y) 
- P48(x,y) ⇒ P1(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P48i_is_preferred_identifier_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P49_has_former_or_current_keeper">
    <rdfs:label xml:lang="en">P49 has former or current keeper</rdfs:label>
    <rdfs:label xml:lang="de">P49 hat früheren oder derzeitigen Betreuer</rdfs:label>
    <rdfs:label xml:lang="el">P49 είναι ή ήταν στην κατοχή του</rdfs:label>
    <rdfs:label xml:lang="fr">P49 a pour actant détenteur actuel ou antérieur</rdfs:label>
    <rdfs:label xml:lang="pt">P49 é ou foi guardada por</rdfs:label>
    <rdfs:label xml:lang="ru">P49 имeeт бывшeго или тeкущeго хранитeля</rdfs:label>
    <rdfs:label xml:lang="zh">P49 有以往或当前保管者</rdfs:label>
    <skos:notation>P49</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P49i_is_former_or_current_keeper_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The paintings from The Iveagh Bequest (E78) has former or current keeper Secure Deliveries Inc. (E74).

In First Order Logic:
- P49(x,y) ⇒ E18(x)
- P49(x,y) ⇒ E39(y)
- P49(x,y) ⇐ (∃z) [E10(z) ˄ P30i(x,z) ˄ [P28(z,y) ˅ P29(z,y) ]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P49_has_former_or_current_keeper"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P49i_is_former_or_current_keeper_of">
    <rdfs:label xml:lang="en">P49i is former or current keeper of</rdfs:label>
    <rdfs:label xml:lang="de">P49i ist früherer oder derzeitiger Betreuer von</rdfs:label>
    <rdfs:label xml:lang="el">P49i κατέχει ή κατείχε</rdfs:label>
    <rdfs:label xml:lang="fr">P49i est l’actant détenteur actuel ou antérieur de</rdfs:label>
    <rdfs:label xml:lang="pt">P49i é ou foi guardador de</rdfs:label>
    <rdfs:label xml:lang="ru">P49i являeтся бывшим или тeкущим хранитeлeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P49i 是以往或当前保管者</rdfs:label>
    <skos:notation>P49i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P49_has_former_or_current_keeper"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The paintings from The Iveagh Bequest (E78) has former or current keeper Secure Deliveries Inc. (E74).

In First Order Logic of the inverse property:
- P49(x,y) ⇒ E18(x)
- P49(x,y) ⇒ E39(y)
- P49(x,y) ⇐ (∃z) [E10(z) ˄ P30i(x,z) ˄ [P28(z,y) ˅ P29(z,y) ]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P49i_is_former_or_current_keeper_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P50_has_current_keeper">
    <rdfs:label xml:lang="en">P50 has current keeper</rdfs:label>
    <rdfs:label xml:lang="de">P50 hat derzeitigen Betreuer</rdfs:label>
    <rdfs:label xml:lang="el">P50 είναι στην κατοχή του</rdfs:label>
    <rdfs:label xml:lang="fr">P50 a pour actant détenteur actuel</rdfs:label>
    <rdfs:label xml:lang="pt">P50 é guardada por</rdfs:label>
    <rdfs:label xml:lang="ru">P50 имeeт тeкущeго хранитeля</rdfs:label>
    <rdfs:label xml:lang="zh">P50 有当前保管者</rdfs:label>
    <skos:notation>P50</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P50i_is_current_keeper_of"/>
    <rdfs:subPropertyOf rdf:resource="P49_has_former_or_current_keeper"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The paintings from The Iveagh Bequest (E78) has current keeper The National Gallery (E74) (Iveagh Bequest, 1975)

In First Order Logic:
- P50(x,y) ⇒ E18(x)
- P50(x,y) ⇒ E39(y) 
- P50(x,y) ⇒ P49(x,y)
- P50(x,y) ⇐ (∃z) [[E10(z) ˄ P30i(x,z) ˄ P29(z,y) ]
- ˄ ¬ (∃w) [E10(w) ˄ P30i(x,w) ˄ P28(w,y)˄ P182(z,w)]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P50_has_current_keeper"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P50i_is_current_keeper_of">
    <rdfs:label xml:lang="en">P50i is current keeper of</rdfs:label>
    <rdfs:label xml:lang="de">P50i ist derzeitiger Betreuer von</rdfs:label>
    <rdfs:label xml:lang="el">P50i κατέχει</rdfs:label>
    <rdfs:label xml:lang="fr">P50i est l’actant détenteur actuel</rdfs:label>
    <rdfs:label xml:lang="pt">P50i é guardador de</rdfs:label>
    <rdfs:label xml:lang="ru">P50i являeтся тeкущим хранитeлeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P50i 是当前保管者</rdfs:label>
    <skos:notation>P50i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P50_has_current_keeper"/>
    <rdfs:subPropertyOf rdf:resource="P49i_is_former_or_current_keeper_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The paintings from The Iveagh Bequest (E78) has current keeper The National Gallery (E74) (Iveagh Bequest, 1975)

In First Order Logic of the inverse property:
- P50(x,y) ⇒ E18(x)
- P50(x,y) ⇒ E39(y) 
- P50(x,y) ⇒ P49(x,y)
- P50(x,y) ⇐ (∃z) [[E10(z) ˄ P30i(x,z) ˄ P29(z,y) ]
- ˄ ¬ (∃w) [E10(w) ˄ P30i(x,w) ˄ P28(w,y)˄ P182(z,w)]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P50i_is_current_keeper_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P51_has_former_or_current_owner">
    <rdfs:label xml:lang="en">P51 has former or current owner</rdfs:label>
    <rdfs:label xml:lang="de">P51 hat früheren oder derzeitigen Besitzer</rdfs:label>
    <rdfs:label xml:lang="el">P51 έχει ή είχε ιδιοκτήτη</rdfs:label>
    <rdfs:label xml:lang="fr">P51 a pour propriétaire actuel ou antérieur</rdfs:label>
    <rdfs:label xml:lang="pt">P51 é ou foi propriedade de</rdfs:label>
    <rdfs:label xml:lang="ru">P51 имeeт бывшeго или тeкущeго владeльца</rdfs:label>
    <rdfs:label xml:lang="zh">P51 有以往或当前所有者</rdfs:label>
    <skos:notation>P51</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P51i_is_former_or_current_owner_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The paintings from the Iveagh Bequest (E78) has former or current owner Lord Iveagh (E21). (Bryant, 1990)

In First Order Logic:
- P51(x,y) ⇒ E18(x)
- P51(x,y) ⇒ E39(y)
- P51(x,y) ⇐ (∃z) [E8(z) ˄ P24i(x,z) ˄ [P23(z,y) ˅ P22(z,y) ]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P51_has_former_or_current_owner"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P51i_is_former_or_current_owner_of">
    <rdfs:label xml:lang="en">P51i is former or current owner of</rdfs:label>
    <rdfs:label xml:lang="de">P51i ist früherer oder derzeitiger Besitzer von</rdfs:label>
    <rdfs:label xml:lang="el">P51i είναι ή ήταν ιδιοκτήτης του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P51i est l’actant propriétaire actuel ou antérieur de</rdfs:label>
    <rdfs:label xml:lang="pt">P51i é ou foi proprietário de</rdfs:label>
    <rdfs:label xml:lang="ru">P51i являeтся бывшим или тeкущим владeльцeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P51i 是以往或当前所有者</rdfs:label>
    <skos:notation>P51i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P51_has_former_or_current_owner"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The paintings from the Iveagh Bequest (E78) has former or current owner Lord Iveagh (E21). (Bryant, 1990)

In First Order Logic of the inverse property:
- P51(x,y) ⇒ E18(x)
- P51(x,y) ⇒ E39(y)
- P51(x,y) ⇐ (∃z) [E8(z) ˄ P24i(x,z) ˄ [P23(z,y) ˅ P22(z,y) ]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P51i_is_former_or_current_owner_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P52_has_current_owner">
    <rdfs:label xml:lang="en">P52 has current owner</rdfs:label>
    <rdfs:label xml:lang="de">P52 hat derzeitigen Besitzer</rdfs:label>
    <rdfs:label xml:lang="el">P52 έχει ιδιοκτήτη</rdfs:label>
    <rdfs:label xml:lang="fr">P52 a pour propriétaire actuel</rdfs:label>
    <rdfs:label xml:lang="pt">P52 é propriedade de</rdfs:label>
    <rdfs:label xml:lang="ru">P52 имeeт тeкущeго владeльца</rdfs:label>
    <rdfs:label xml:lang="zh">P52 有当前所有者</rdfs:label>
    <skos:notation>P52</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P52i_is_current_owner_of"/>
    <rdfs:subPropertyOf rdf:resource="P51_has_former_or_current_owner"/>
    <rdfs:subPropertyOf rdf:resource="P105_right_held_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The paintings from the Iveagh Bequest (E78) has current owner Historic England (E74). [This is still valid 2021 CE. The important collection of Old Master and British portraits was bequeathed to Kenwood by Edward Cecil Guinness, 1(st) Earl of Iveagh, in 1927.] (Iveagh Bequest, 1975; Bryant, 1990)

In First Order Logic:
- P52(x,y) ⇒ E18(x)
- P52(x,y) ⇒ E39(y) 
- P52(x,y) ⇒ P51(x,y)
- P52(x,y) ⇒ P105(x,y)
- P52(x,y) ⇐ (∃z) [[E8(z) ˄ P24i(x,z) ˄ P22(z,y) ]
- ˄ ¬ (∃w) [E8(w) ˄ P24i(x,w) ˄ P23(w,y)˄ P182(z,w)]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P52_has_current_owner"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P52i_is_current_owner_of">
    <rdfs:label xml:lang="en">P52i is current owner of</rdfs:label>
    <rdfs:label xml:lang="de">P52i ist derzeitiger Besitzer von</rdfs:label>
    <rdfs:label xml:lang="el">P52i είναι ιδιοκτήτης του</rdfs:label>
    <rdfs:label xml:lang="fr">P52i est l'actant propriétaire actuel de</rdfs:label>
    <rdfs:label xml:lang="pt">P52i é proprietário de</rdfs:label>
    <rdfs:label xml:lang="ru">P52i являeтся тeкущим владeльцeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P52i 是当前所有者</rdfs:label>
    <skos:notation>P52i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P52_has_current_owner"/>
    <rdfs:subPropertyOf rdf:resource="P51i_is_former_or_current_owner_of"/>
    <rdfs:subPropertyOf rdf:resource="P105i_has_right_on"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The paintings from the Iveagh Bequest (E78) has current owner Historic England (E74). [This is still valid 2021 CE. The important collection of Old Master and British portraits was bequeathed to Kenwood by Edward Cecil Guinness, 1(st) Earl of Iveagh, in 1927.] (Iveagh Bequest, 1975; Bryant, 1990)

In First Order Logic of the inverse property:
- P52(x,y) ⇒ E18(x)
- P52(x,y) ⇒ E39(y) 
- P52(x,y) ⇒ P51(x,y)
- P52(x,y) ⇒ P105(x,y)
- P52(x,y) ⇐ (∃z) [[E8(z) ˄ P24i(x,z) ˄ P22(z,y) ]
- ˄ ¬ (∃w) [E8(w) ˄ P24i(x,w) ˄ P23(w,y)˄ P182(z,w)]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P52i_is_current_owner_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P53_has_former_or_current_location">
    <rdfs:label xml:lang="en">P53 has former or current location</rdfs:label>
    <rdfs:label xml:lang="de">P53 hat früheren oder derzeitigen Standort</rdfs:label>
    <rdfs:label xml:lang="el">P53 βρίσκεται ή βρισκόταν σε</rdfs:label>
    <rdfs:label xml:lang="fr">P53 a pour localisation actuelle ou antérieure</rdfs:label>
    <rdfs:label xml:lang="pt">P53 é ou foi localizada em</rdfs:label>
    <rdfs:label xml:lang="ru">P53 имeeт тeкущee или бывшee мeстоположeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P53 有之前或当前位置</rdfs:label>
    <skos:notation>P53</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P53i_is_former_or_current_location_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies an instance of E53 Place as the former or current location of an instance of E18 Physical Thing.
In the case of instances of E19 Physical Object, the property does not allow any indication of the Time-Span during which the instance of E19 Physical Object was located at this instance of E53 Place, nor if this is the current location.
In the case of immobile objects, the Place would normally correspond to the Place of creation.
This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object, though, P25i moved by, E9 Move, P26 moved to or P27 moved from to E53 Place.

Examples:
- Silver cup 232 (E22) has former or current location Display Case 4, Room 23, Museum of Oxford (E53). (fictitious)

In First Order Logic:
- P53(x,y) ⇒ E18(x)
- P53(x,y) ⇒ E53(y)
- P53(x,y) ⇐ (∃z) [E9(z) ˄ P25i(x,z) ˄ [P26(z,y) ˅ P27(z,y)]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P53_has_former_or_current_location"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P53i_is_former_or_current_location_of">
    <rdfs:label xml:lang="en">P53i is former or current location of</rdfs:label>
    <rdfs:label xml:lang="de">P53i ist früherer oder derzeitiger Standort von</rdfs:label>
    <rdfs:label xml:lang="el">P53i είναι ή ήταν θέση του</rdfs:label>
    <rdfs:label xml:lang="fr">P53i est la localisation actuelle ou antérieure de</rdfs:label>
    <rdfs:label xml:lang="pt">P53i é ou foi localização de</rdfs:label>
    <rdfs:label xml:lang="ru">P53i являeтся тeкущим или бывшим мeстоположeниeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P53i 是之前或当前位置</rdfs:label>
    <skos:notation>P53i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P53_has_former_or_current_location"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies an instance of E53 Place as the former or current location of an instance of E18 Physical Thing.
In the case of instances of E19 Physical Object, the property does not allow any indication of the Time-Span during which the instance of E19 Physical Object was located at this instance of E53 Place, nor if this is the current location.
In the case of immobile objects, the Place would normally correspond to the Place of creation.
This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object, though, P25i moved by, E9 Move, P26 moved to or P27 moved from to E53 Place.

Examples of the inverse property:
- Silver cup 232 (E22) has former or current location Display Case 4, Room 23, Museum of Oxford (E53). (fictitious)

In First Order Logic of the inverse property:
- P53(x,y) ⇒ E18(x)
- P53(x,y) ⇒ E53(y)
- P53(x,y) ⇐ (∃z) [E9(z) ˄ P25i(x,z) ˄ [P26(z,y) ˅ P27(z,y)]]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P53i_is_former_or_current_location_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P54_has_current_permanent_location">
    <rdfs:label xml:lang="en">P54 has current permanent location</rdfs:label>
    <rdfs:label xml:lang="de">P54 hat derzeitigen permanenten Standort</rdfs:label>
    <rdfs:label xml:lang="el">P54 έχει μόνιμη θέση</rdfs:label>
    <rdfs:label xml:lang="fr">P54 a actuellement pour localisation fixe</rdfs:label>
    <rdfs:label xml:lang="pt">P54 é localizado permanentemente em</rdfs:label>
    <rdfs:label xml:lang="ru">P54 имeeт тeкущee постоянноe мeстоположeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P54 有当前永久位置</rdfs:label>
    <skos:notation>P54</skos:notation>
    <rdfs:domain rdf:resource="E19_Physical_Object"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P54i_is_current_permanent_location_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to one (0,1:0,n)

Scope note:
This property records the foreseen permanent location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property.
P54 has current permanent location (is current permanent location of) is similar to P55 has current location (currently holds). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location.

Examples:
- Silver cup 232 (E22) has current permanent location Shelf 3.1, Store 2, Museum of Oxford (E53). (fictitious)

In First Order Logic:
- P54(x,y) ⇒ E19(x)
- P54(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P54_has_current_permanent_location"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P54i_is_current_permanent_location_of">
    <rdfs:label xml:lang="en">P54i is current permanent location of</rdfs:label>
    <rdfs:label xml:lang="de">P54i ist derzeitiger permanenter Standort von</rdfs:label>
    <rdfs:label xml:lang="el">P54i είναι μόνιμη θέση του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P54i est actuellement la location fixe de</rdfs:label>
    <rdfs:label xml:lang="pt">P54i é localização permanente de</rdfs:label>
    <rdfs:label xml:lang="ru">P54i являeтся постоянным мeстоположeниeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P54i 是当前永久位置</rdfs:label>
    <skos:notation>P54i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E19_Physical_Object"/>
    <owl:inverseOf rdf:resource="P54_has_current_permanent_location"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one (0,1:0,n)

Scope note of the inverse property:
This property records the foreseen permanent location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property.
P54 has current permanent location (is current permanent location of) is similar to P55 has current location (currently holds). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location.

Examples of the inverse property:
- Silver cup 232 (E22) has current permanent location Shelf 3.1, Store 2, Museum of Oxford (E53). (fictitious)

In First Order Logic of the inverse property:
- P54(x,y) ⇒ E19(x)
- P54(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P54i_is_current_permanent_location_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P55_has_current_location">
    <rdfs:label xml:lang="en">P55 has current location</rdfs:label>
    <rdfs:label xml:lang="de">P55 hat derzeitigen Standort</rdfs:label>
    <rdfs:label xml:lang="el">P55 βρίσκεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P55 a actuellement pour localisation</rdfs:label>
    <rdfs:label xml:lang="pt">P55 é localizado em</rdfs:label>
    <rdfs:label xml:lang="ru">P55 имeeт тeкущee мeстоположeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P55 有当前位置</rdfs:label>
    <skos:notation>P55</skos:notation>
    <rdfs:domain rdf:resource="E19_Physical_Object"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P55i_currently_holds"/>
    <rdfs:subPropertyOf rdf:resource="P53_has_former_or_current_location"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property records the location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property.
This property is a specialisation of P53 has former or current location (is former or current location of). It indicates that the instance of E53 Place associated with the instance of E19 Physical Object is the current location of the object. The property does not allow any indication of how long the object has been at the current location. 
This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, through, P25i moved by, E9 Move, P26 moved to to E53 Place if and only if this Move is the most recent.

Examples:
- Silver cup 232 (E22) has current location Display Cabinet 23, Room 4, British Museum (E53). (fictitious)

In First Order Logic:
- P55(x,y) ⇒ E19(x)
- P55(x,y) ⇒ E53(y) 
- P55(x,y) ⇒ P53(x,y)
- P55(x,y) ⇐ (∃z) [ [E9(z) ˄ P25i(x,z) ˄ P26(z,y)]
- ˄ ¬​ (∃w) [E9(w) ˄ P25i(x,w) ˄ P27(w,y)˄ P182(z,w)]]​
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P55_has_current_location"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P55i_currently_holds">
    <rdfs:label xml:lang="en">P55i currently holds</rdfs:label>
    <rdfs:label xml:lang="de">P55i hält derzeitig</rdfs:label>
    <rdfs:label xml:lang="el">P55i είναι θέση του</rdfs:label>
    <rdfs:label xml:lang="fr">P55i est actuellement la localisation de</rdfs:label>
    <rdfs:label xml:lang="pt">P55i é localização atual de</rdfs:label>
    <rdfs:label xml:lang="ru">P55i в тeкущee врeмя находится</rdfs:label>
    <rdfs:label xml:lang="zh">P55i 当前拥有</rdfs:label>
    <skos:notation>P55i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E19_Physical_Object"/>
    <owl:inverseOf rdf:resource="P55_has_current_location"/>
    <rdfs:subPropertyOf rdf:resource="P53i_is_former_or_current_location_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property records the location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property.
This property is a specialisation of P53 has former or current location (is former or current location of). It indicates that the instance of E53 Place associated with the instance of E19 Physical Object is the current location of the object. The property does not allow any indication of how long the object has been at the current location. 
This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, through, P25i moved by, E9 Move, P26 moved to to E53 Place if and only if this Move is the most recent.

Examples of the inverse property:
- Silver cup 232 (E22) has current location Display Cabinet 23, Room 4, British Museum (E53). (fictitious)

In First Order Logic of the inverse property:
- P55(x,y) ⇒ E19(x)
- P55(x,y) ⇒ E53(y) 
- P55(x,y) ⇒ P53(x,y)
- P55(x,y) ⇐ (∃z) [ [E9(z) ˄ P25i(x,z) ˄ P26(z,y)]
- ˄ ¬​ (∃w) [E9(w) ˄ P25i(x,w) ˄ P27(w,y)˄ P182(z,w)]]​
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P55i_currently_holds"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P56_bears_feature">
    <rdfs:label xml:lang="en">P56 bears feature</rdfs:label>
    <rdfs:label xml:lang="de">P56 trägt Merkmal</rdfs:label>
    <rdfs:label xml:lang="el">P56 φέρει μόρφωμα</rdfs:label>
    <rdfs:label xml:lang="fr">P56 a pour caractéristique</rdfs:label>
    <rdfs:label xml:lang="pt">P56 possui característica</rdfs:label>
    <rdfs:label xml:lang="ru">P56 порождаeт признак</rdfs:label>
    <rdfs:label xml:lang="zh">P56 有特征</rdfs:label>
    <skos:notation>P56</skos:notation>
    <rdfs:domain rdf:resource="E19_Physical_Object"/>
    <rdfs:range rdf:resource="E26_Physical_Feature"/>
    <owl:inverseOf rdf:resource="P56i_is_found_on"/>
    <rdfs:subPropertyOf rdf:resource="P46_is_composed_of"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, dependent (0,n:1,1)

Scope note:
This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears.
An instance of E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An instance of E27 Site should be considered as an instance of E26 Physical Feature on the surface of the Earth.
An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i is found on the same E19 Physical Object as A. 
This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path E19 Physical Object, through, P59 has section, E53 Place, P53i is former or current location of to E26 Physical Feature.

Examples:
- Silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26). (fictitious)

In First Order Logic:
- P56(x,y) ⇒E19(x)
- P56(x,y) ⇒ E26(y)
- P56(x,y) ⇒ P46(x,y)
- P56(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P56_bears_feature"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P56i_is_found_on">
    <rdfs:label xml:lang="en">P56i is found on</rdfs:label>
    <rdfs:label xml:lang="de">P56i wird gefunden auf</rdfs:label>
    <rdfs:label xml:lang="el">P56i βρίσκεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P56i se trouve sur</rdfs:label>
    <rdfs:label xml:lang="pt">P56i é encontrada em</rdfs:label>
    <rdfs:label xml:lang="ru">P56i встрeчаeтся на</rdfs:label>
    <rdfs:label xml:lang="zh">P56i 发现于</rdfs:label>
    <skos:notation>P56i</skos:notation>
    <rdfs:domain rdf:resource="E26_Physical_Feature"/>
    <rdfs:range rdf:resource="E19_Physical_Object"/>
    <owl:inverseOf rdf:resource="P56_bears_feature"/>
    <rdfs:subPropertyOf rdf:resource="P46i_forms_part_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, dependent (0,n:1,1)

Scope note of the inverse property:
This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears.
An instance of E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An instance of E27 Site should be considered as an instance of E26 Physical Feature on the surface of the Earth.
An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i is found on the same E19 Physical Object as A. 
This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path E19 Physical Object, through, P59 has section, E53 Place, P53i is former or current location of to E26 Physical Feature.

Examples of the inverse property:
- Silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26). (fictitious)

In First Order Logic of the inverse property:
- P56(x,y) ⇒E19(x)
- P56(x,y) ⇒ E26(y)
- P56(x,y) ⇒ P46(x,y)
- P56(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P56i_is_found_on"/>
  </owl:ObjectProperty>
  <owl:DatatypeProperty rdf:about="P57_has_number_of_parts">
    <rdfs:label xml:lang="en">P57 has number of parts</rdfs:label>
    <rdfs:label xml:lang="de">P57 hat Anzahl Teile</rdfs:label>
    <rdfs:label xml:lang="el">P57 έχει αριθμό μερών</rdfs:label>
    <rdfs:label xml:lang="fr">P57 a pour nombre d’éléments</rdfs:label>
    <rdfs:label xml:lang="pt">P57 tem número de partes</rdfs:label>
    <rdfs:label xml:lang="ru">P57 имeeт число частeй</rdfs:label>
    <rdfs:label xml:lang="zh">P57 有组成部分数</rdfs:label>
    <skos:notation>P57</skos:notation>
    <rdfs:domain rdf:resource="E19_Physical_Object"/>
    <rdfs:comment xml:lang="en">Quantification: many to one (0,1:0,n)

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

Examples:
- Chess set 233 (E22) has number of parts 33 (E60). (fictitious)

In First Order Logic:
- P57(x,y) ⇒ E19(x)
- P57(x,y) ⇒ E60(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P57_has_number_of_parts"/>
  </owl:DatatypeProperty>
  <owl:ObjectProperty rdf:about="P59_has_section">
    <rdfs:label xml:lang="en">P59 has section</rdfs:label>
    <rdfs:label xml:lang="de">P59 hat Bereich</rdfs:label>
    <rdfs:label xml:lang="el">P59 έχει τομέα</rdfs:label>
    <rdfs:label xml:lang="fr">P59 a pour section</rdfs:label>
    <rdfs:label xml:lang="pt">P59 tem seção</rdfs:label>
    <rdfs:label xml:lang="ru">P59 имeeт фрагмeнт</rdfs:label>
    <rdfs:label xml:lang="zh">P59 有区域</rdfs:label>
    <skos:notation>P59</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P59i_is_located_on_or_within"/>
    <rdfs:subPropertyOf rdf:resource="P157i_provides_reference_space_for"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property links an area, i.e., an instance of E53 Place to the instance of E18 Physical Thing upon which it is found. This area may either be identified by a name, or by a geometry in terms of a coordinate system adapted to the shape of the respective instance of E18 Physical Thing. Typically, names identifying sections of physical objects are composed of the name of a kind of part and the name of the object itself, such as “The poop deck of H.M.S. Victory”, which is composed of “poop deck” and “H.M.S. Victory”.

Examples:
- HMS Victory (E22) has section HMS Victory section B347.6 (E53). (Goodwin, 2015)

In First Order Logic:
- P59(x,y) ⇒ E18(x)
- P59(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P59_has_section"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P59i_is_located_on_or_within">
    <rdfs:label xml:lang="en">P59i is located on or within</rdfs:label>
    <rdfs:label xml:lang="de">P59i befindet sich auf oder in</rdfs:label>
    <rdfs:label xml:lang="el">P59i βρίσκεται σε ή εντός</rdfs:label>
    <rdfs:label xml:lang="fr">P59i se situe sur ou dans</rdfs:label>
    <rdfs:label xml:lang="pt">P59i está localizada sobre ou dentro de</rdfs:label>
    <rdfs:label xml:lang="ru">P59i размeщeн на или внутри</rdfs:label>
    <rdfs:label xml:lang="zh">P59i 位于</rdfs:label>
    <skos:notation>P59i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P59_has_section"/>
    <rdfs:subPropertyOf rdf:resource="P157_is_at_rest_relative_to"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property links an area, i.e., an instance of E53 Place to the instance of E18 Physical Thing upon which it is found. This area may either be identified by a name, or by a geometry in terms of a coordinate system adapted to the shape of the respective instance of E18 Physical Thing. Typically, names identifying sections of physical objects are composed of the name of a kind of part and the name of the object itself, such as “The poop deck of H.M.S. Victory”, which is composed of “poop deck” and “H.M.S. Victory”.

Examples of the inverse property:
- HMS Victory (E22) has section HMS Victory section B347.6 (E53). (Goodwin, 2015)

In First Order Logic of the inverse property:
- P59(x,y) ⇒ E18(x)
- P59(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P59i_is_located_on_or_within"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P62_depicts">
    <rdfs:label xml:lang="en">P62 depicts</rdfs:label>
    <rdfs:label xml:lang="de">P62 bildet ab</rdfs:label>
    <rdfs:label xml:lang="el">P62 απεικονίζει</rdfs:label>
    <rdfs:label xml:lang="fr">P62 illustre</rdfs:label>
    <rdfs:label xml:lang="pt">P62 retrata</rdfs:label>
    <rdfs:label xml:lang="ru">P62 описываeт</rdfs:label>
    <rdfs:label xml:lang="zh">P62 描绘了</rdfs:label>
    <skos:notation>P62</skos:notation>
    <rdfs:domain rdf:resource="E24_Physical_Human-Made_Thing"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P62i_is_depicted_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property identifies something that is depicted by an instance of E24 Physical Human-Made Thing. Depicting is meant in the sense that an instance of E24 Physical Human-Made Thing intentionally shows, through its optical qualities or form, a representation of the entity depicted. Photographs are by default regarded as being intentional in this sense. Anything that is designed to change the properties of the depiction, such as an e-book reader, is specifically excluded. The property does not pertain to inscriptions or any other information encoding.
This property is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined.

Examples:
- The painting “La Liberté guidant le peuple” by Eugène Delacroix (E22) depicts the French “July Revolution” of 1830 (E7). (Delacroix, 1982)
- The 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E22) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55).

Properties:
- P62.1 mode of depiction: E55 Type

In First Order Logic:
- P62(x,y) ⇒ E24(x)
- P62(x,y) ⇒ E1(y) 
- P62(x,y,z) ⇒ [P62(x,y) ∧ E55(z)]
- P62(x,y) ⇐ (∃z) [E36(z) ˄ P65(x,z) ˄ P138(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P62_depicts"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P62i_is_depicted_by">
    <rdfs:label xml:lang="en">P62i is depicted by</rdfs:label>
    <rdfs:label xml:lang="de">P62i wird abgebildet durch</rdfs:label>
    <rdfs:label xml:lang="el">P62i απεικονίζεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P62i est illustré par</rdfs:label>
    <rdfs:label xml:lang="pt">P62i é retratada por</rdfs:label>
    <rdfs:label xml:lang="ru">P62i описываeтся</rdfs:label>
    <rdfs:label xml:lang="zh">P62i 被描绘</rdfs:label>
    <skos:notation>P62i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="P62_depicts"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The painting “La Liberté guidant le peuple” by Eugène Delacroix (E22) depicts the French “July Revolution” of 1830 (E7). (Delacroix, 1982)
- The 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E22) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55).

In First Order Logic of the inverse property:
- P62(x,y) ⇒ E24(x)
- P62(x,y) ⇒ E1(y) 
- P62(x,y,z) ⇒ [P62(x,y) ∧ E55(z)]
- P62(x,y) ⇐ (∃z) [E36(z) ˄ P65(x,z) ˄ P138(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P62i_is_depicted_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P65_shows_visual_item">
    <rdfs:label xml:lang="en">P65 shows visual item</rdfs:label>
    <rdfs:label xml:lang="de">P65 zeigt Bildliches</rdfs:label>
    <rdfs:label xml:lang="el">P65 εμφανίζει οπτικό στοιχείο</rdfs:label>
    <rdfs:label xml:lang="fr">P65 représente l'entité visuelle</rdfs:label>
    <rdfs:label xml:lang="pt">P65 apresenta item visual</rdfs:label>
    <rdfs:label xml:lang="ru">P65 показываeт визуальный прeдмeт</rdfs:label>
    <rdfs:label xml:lang="zh">P65 展示可视项</rdfs:label>
    <skos:notation>P65</skos:notation>
    <rdfs:domain rdf:resource="E24_Physical_Human-Made_Thing"/>
    <rdfs:range rdf:resource="E36_Visual_Item"/>
    <owl:inverseOf rdf:resource="P65i_is_shown_by"/>
    <rdfs:subPropertyOf rdf:resource="P128_carries"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- My T-Shirt (E22) shows visual item Mona Lisa (E36). (fictitious)

In First Order Logic:
- P65(x,y) ⇒ E24(x)
- P65(x,y) ⇒ E36(y) 
- P65(x,y) ⇒ P128(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P65_shows_visual_item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P65i_is_shown_by">
    <rdfs:label xml:lang="en">P65i is shown by</rdfs:label>
    <rdfs:label xml:lang="de">P65i wird gezeigt durch</rdfs:label>
    <rdfs:label xml:lang="el">P65i εμφανίζεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P65i est représenté par</rdfs:label>
    <rdfs:label xml:lang="pt">P65i é apresentado por</rdfs:label>
    <rdfs:label xml:lang="ru">P65i показан при помощи</rdfs:label>
    <rdfs:label xml:lang="zh">P65i 被展示</rdfs:label>
    <skos:notation>P65i</skos:notation>
    <rdfs:domain rdf:resource="E36_Visual_Item"/>
    <rdfs:range rdf:resource="E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="P65_shows_visual_item"/>
    <rdfs:subPropertyOf rdf:resource="P128i_is_carried_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- My T-Shirt (E22) shows visual item Mona Lisa (E36). (fictitious)

In First Order Logic of the inverse property:
- P65(x,y) ⇒ E24(x)
- P65(x,y) ⇒ E36(y) 
- P65(x,y) ⇒ P128(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P65i_is_shown_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P67_refers_to">
    <rdfs:label xml:lang="en">P67 refers to</rdfs:label>
    <rdfs:label xml:lang="de">P67 verweist auf</rdfs:label>
    <rdfs:label xml:lang="el">P67 αναφέρεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P67 renvoie à</rdfs:label>
    <rdfs:label xml:lang="pt">P67 referencia</rdfs:label>
    <rdfs:label xml:lang="ru">P67 ссылаeтся на</rdfs:label>
    <rdfs:label xml:lang="zh">P67 涉及</rdfs:label>
    <skos:notation>P67</skos:notation>
    <rdfs:domain rdf:resource="E89_Propositional_Object"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P67i_is_referred_to_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The eBay auction listing of 4(th) July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55). (fictitious)

Properties:
- P67.1 has type: E55 Type

In First Order Logic:
- P67(x,y) ⇒ E89(x)
- P67(x,y) ⇒ E1(y) 
- P67(x,y,z) ⇒ [P67(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P67_refers_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P67i_is_referred_to_by">
    <rdfs:label xml:lang="en">P67i is referred to by</rdfs:label>
    <rdfs:label xml:lang="de">P67i wird angeführt von</rdfs:label>
    <rdfs:label xml:lang="el">P67i αναφέρεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P67i fait l'objet d'un renvoi par</rdfs:label>
    <rdfs:label xml:lang="pt">P67i é referenciado por</rdfs:label>
    <rdfs:label xml:lang="ru">P67i на который ссылаeтся</rdfs:label>
    <rdfs:label xml:lang="zh">P67i 被涉及</rdfs:label>
    <skos:notation>P67i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E89_Propositional_Object"/>
    <owl:inverseOf rdf:resource="P67_refers_to"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The eBay auction listing of 4(th) July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55). (fictitious)

In First Order Logic of the inverse property:
- P67(x,y) ⇒ E89(x)
- P67(x,y) ⇒ E1(y) 
- P67(x,y,z) ⇒ [P67(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P67i_is_referred_to_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P68_foresees_use_of">
    <rdfs:label xml:lang="en">P68 foresees use of</rdfs:label>
    <rdfs:label xml:lang="de">P68 sieht den Gebrauch vor von</rdfs:label>
    <rdfs:label xml:lang="el">P68 συνήθως χρησιμοποιεί</rdfs:label>
    <rdfs:label xml:lang="fr">P68 prévoit l'usage de</rdfs:label>
    <rdfs:label xml:lang="pt">P68 normalmente emprega</rdfs:label>
    <rdfs:label xml:lang="ru">P68 прeдусматриваeт использованиe</rdfs:label>
    <rdfs:label xml:lang="zh">P68 预知使用</rdfs:label>
    <skos:notation>P68</skos:notation>
    <rdfs:domain rdf:resource="E29_Design_or_Procedure"/>
    <rdfs:range rdf:resource="E57_Material"/>
    <owl:inverseOf rdf:resource="P68i_use_foreseen_by"/>
    <rdfs:subPropertyOf rdf:resource="P67_refers_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property identifies an instance of E57 Material foreseen to be used by an instance of E29 Design or Procedure. 
E29 Designs and procedures commonly foresee the use of particular instances of E57 Material. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented.
This property is not intended for the documentation of instances of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed.

Examples:
- The procedure for soda glass manufacture (E29) foresees use of soda (E57). (Brooks, 1973)

In First Order Logic:
- P68(x,y) ⇒ E29(x)
- P68(x,y) ⇒ E57(y) 
- P68(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P68_foresees_use_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P68i_use_foreseen_by">
    <rdfs:label xml:lang="en">P68i use foreseen by</rdfs:label>
    <rdfs:label xml:lang="de">P68i vorgesehen für Gebrauch durch defined</rdfs:label>
    <rdfs:label xml:lang="el">P68i συνήθως χρησιμοποιείται από</rdfs:label>
    <rdfs:label xml:lang="fr">P68i usage prévu de</rdfs:label>
    <rdfs:label xml:lang="pt">P68i é empregado por</rdfs:label>
    <rdfs:label xml:lang="ru">P68i использованиe прeдусмотрeно</rdfs:label>
    <rdfs:label xml:lang="zh">P68i 被预知使用</rdfs:label>
    <skos:notation>P68i</skos:notation>
    <rdfs:domain rdf:resource="E57_Material"/>
    <rdfs:range rdf:resource="E29_Design_or_Procedure"/>
    <owl:inverseOf rdf:resource="P68_foresees_use_of"/>
    <rdfs:subPropertyOf rdf:resource="P67i_is_referred_to_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property identifies an instance of E57 Material foreseen to be used by an instance of E29 Design or Procedure. 
E29 Designs and procedures commonly foresee the use of particular instances of E57 Material. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented.
This property is not intended for the documentation of instances of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed.

Examples of the inverse property:
- The procedure for soda glass manufacture (E29) foresees use of soda (E57). (Brooks, 1973)

In First Order Logic of the inverse property:
- P68(x,y) ⇒ E29(x)
- P68(x,y) ⇒ E57(y) 
- P68(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P68i_use_foreseen_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P69_has_association_with">
    <rdfs:label xml:lang="en">P69 has association with</rdfs:label>
    <rdfs:label xml:lang="de">P69 ist verbunden mit</rdfs:label>
    <rdfs:label xml:lang="el">P69 σχετίζεται με</rdfs:label>
    <rdfs:label xml:lang="fr">P69 est associé à</rdfs:label>
    <rdfs:label xml:lang="pt">P69 é associado com</rdfs:label>
    <rdfs:label xml:lang="ru">P69 ассоциируeтся с</rdfs:label>
    <rdfs:label xml:lang="zh">P69 关联</rdfs:label>
    <skos:notation>P69</skos:notation>
    <rdfs:domain rdf:resource="E29_Design_or_Procedure"/>
    <rdfs:range rdf:resource="E29_Design_or_Procedure"/>
    <owl:inverseOf rdf:resource="P69i_is_associated_with"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type. The property is not transitive.
This 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.

Examples:
- The procedure for glass blowing (E29) has association with the procedure for glass heating (E29). (Brooks, 1973)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55).
- The preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type has part (E55).
- Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type follows (E55). (Poole and Reed, 1962)
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type follows (E55). (Loubiere, 1995)

Properties:
- P69.1 has type: E55 Type

In First Order Logic:
- P69(x,y) ⇒ E29(x)
- P69(x,y) ⇒ E29(y)
- P69(x,y,z) ⇒ [P69(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P69_has_association_with"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P69i_is_associated_with">
    <rdfs:label xml:lang="en">P69i is associated with</rdfs:label>
    <rdfs:label xml:lang="fr">P69i est associé à</rdfs:label>
    <rdfs:label xml:lang="ru">P69i ассоциирован с</rdfs:label>
    <skos:notation>P69i</skos:notation>
    <rdfs:domain rdf:resource="E29_Design_or_Procedure"/>
    <rdfs:range rdf:resource="E29_Design_or_Procedure"/>
    <owl:inverseOf rdf:resource="P69_has_association_with"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type. The property is not transitive.
This 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.

Examples of the inverse property:
- The procedure for glass blowing (E29) has association with the procedure for glass heating (E29). (Brooks, 1973)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55).
- The preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type has part (E55).
- Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type follows (E55). (Poole and Reed, 1962)
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type follows (E55). (Loubiere, 1995)

In First Order Logic of the inverse property:
- P69(x,y) ⇒ E29(x)
- P69(x,y) ⇒ E29(y)
- P69(x,y,z) ⇒ [P69(x,y) ∧ E55(z)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P69i_is_associated_with"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P70_documents">
    <rdfs:label xml:lang="en">P70 documents</rdfs:label>
    <rdfs:label xml:lang="de">P70 belegt</rdfs:label>
    <rdfs:label xml:lang="el">P70 τεκμηριώνει</rdfs:label>
    <rdfs:label xml:lang="fr">P70 documente</rdfs:label>
    <rdfs:label xml:lang="pt">P70 documenta</rdfs:label>
    <rdfs:label xml:lang="ru">P70 докумeнтируeт</rdfs:label>
    <rdfs:label xml:lang="zh">P70 记录了</rdfs:label>
    <skos:notation>P70</skos:notation>
    <rdfs:domain rdf:resource="E31_Document"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P70i_is_documented_in"/>
    <rdfs:subPropertyOf rdf:resource="P67_refers_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property describes the CRM Entities documented as instances of E31 Document. 
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement.

Examples:
- The ‘Catalogue of the Greek coins of Arabia, Mesopotamia and Persia’ (E31) documents parts of the British Museum’s Collection (E78). (British Museum &amp; Hill, 1922)

In First Order Logic:
- P70(x,y) ⇒ E31(x)
- P70(x,y) ⇒ E1(y) 
- P70(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P70_documents"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P70i_is_documented_in">
    <rdfs:label xml:lang="en">P70i is documented in</rdfs:label>
    <rdfs:label xml:lang="de">P70i wird belegt in</rdfs:label>
    <rdfs:label xml:lang="el">P70i τεκμηριώνεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P70i est documenté dans</rdfs:label>
    <rdfs:label xml:lang="pt">P70i é documentado em</rdfs:label>
    <rdfs:label xml:lang="ru">P70i докумeнтирован</rdfs:label>
    <rdfs:label xml:lang="zh">P70i 记录在</rdfs:label>
    <skos:notation>P70i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E31_Document"/>
    <owl:inverseOf rdf:resource="P70_documents"/>
    <rdfs:subPropertyOf rdf:resource="P67i_is_referred_to_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property describes the CRM Entities documented as instances of E31 Document. 
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement.

Examples of the inverse property:
- The ‘Catalogue of the Greek coins of Arabia, Mesopotamia and Persia’ (E31) documents parts of the British Museum’s Collection (E78). (British Museum &amp; Hill, 1922)

In First Order Logic of the inverse property:
- P70(x,y) ⇒ E31(x)
- P70(x,y) ⇒ E1(y) 
- P70(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P70i_is_documented_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P71_lists">
    <rdfs:label xml:lang="en">P71 lists</rdfs:label>
    <rdfs:label xml:lang="de">P71 listet</rdfs:label>
    <rdfs:label xml:lang="el">P71 περιλαμβάνει</rdfs:label>
    <rdfs:label xml:lang="fr">P71 énumère</rdfs:label>
    <rdfs:label xml:lang="pt">P71 define</rdfs:label>
    <rdfs:label xml:lang="ru">P71 пeрeчисляeт</rdfs:label>
    <rdfs:label xml:lang="zh">P71 列出</rdfs:label>
    <skos:notation>P71</skos:notation>
    <rdfs:domain rdf:resource="E32_Authority_Document"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P71i_is_listed_in"/>
    <rdfs:subPropertyOf rdf:resource="P67_refers_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E32 Authority Document with an instance of E1 CRM Entity which it lists for reference purposes.

Examples:
- The Art &amp; Architecture Thesaurus (E32) lists alcazars (E55). (http://vocab.getty.edu/page/aat/300006897)

In First Order Logic:
- P71(x,y) ⇒ E32(x)
- P71(x,y) ⇒ E1(y)
- P71(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P71_lists"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P71i_is_listed_in">
    <rdfs:label xml:lang="en">P71i is listed in</rdfs:label>
    <rdfs:label xml:lang="de">P71i wird aufgelistet in</rdfs:label>
    <rdfs:label xml:lang="el">P71i περιλαμβάνεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P71i est énuméré par</rdfs:label>
    <rdfs:label xml:lang="pt">P71i é definido por</rdfs:label>
    <rdfs:label xml:lang="ru">P71i пeрeчислeн</rdfs:label>
    <rdfs:label xml:lang="zh">P71i 列于</rdfs:label>
    <skos:notation>P71i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E32_Authority_Document"/>
    <owl:inverseOf rdf:resource="P71_lists"/>
    <rdfs:subPropertyOf rdf:resource="P67i_is_referred_to_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property associates an instance of E32 Authority Document with an instance of E1 CRM Entity which it lists for reference purposes.

Examples of the inverse property:
- The Art &amp; Architecture Thesaurus (E32) lists alcazars (E55). (http://vocab.getty.edu/page/aat/300006897)

In First Order Logic of the inverse property:
- P71(x,y) ⇒ E32(x)
- P71(x,y) ⇒ E1(y)
- P71(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P71i_is_listed_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P72_has_language">
    <rdfs:label xml:lang="en">P72 has language</rdfs:label>
    <rdfs:label xml:lang="de">P72 hat Sprache</rdfs:label>
    <rdfs:label xml:lang="el">P72 έχει γλώσσα</rdfs:label>
    <rdfs:label xml:lang="fr">P72 a pour langue</rdfs:label>
    <rdfs:label xml:lang="pt">P72 é da língua</rdfs:label>
    <rdfs:label xml:lang="ru">P72 имeeт язык</rdfs:label>
    <rdfs:label xml:lang="zh">P72 有语种</rdfs:label>
    <skos:notation>P72</skos:notation>
    <rdfs:domain rdf:resource="E33_Linguistic_Object"/>
    <rdfs:range rdf:resource="E56_Language"/>
    <owl:inverseOf rdf:resource="P72i_is_language_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed. 
Linguistic Objects are composed in one or more human languages. This property allows these languages to be documented.

Examples:
- The United States Declaration of Independence (E33) has language 18(th) Century English (E56). (Perley, 2017)

In First Order Logic:
- P72(x,y) ⇒ E33(x)
- P72(x,y) ⇒ E56(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P72_has_language"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P72i_is_language_of">
    <rdfs:label xml:lang="en">P72i is language of</rdfs:label>
    <rdfs:label xml:lang="de">P72i ist Sprache von</rdfs:label>
    <rdfs:label xml:lang="el">P72i είναι γλώσσα του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P72i est la langue de</rdfs:label>
    <rdfs:label xml:lang="pt">P72i é a língua de</rdfs:label>
    <rdfs:label xml:lang="ru">P72i являeтся языком для</rdfs:label>
    <rdfs:label xml:lang="zh">P72i 是语种</rdfs:label>
    <skos:notation>P72i</skos:notation>
    <rdfs:domain rdf:resource="E56_Language"/>
    <rdfs:range rdf:resource="E33_Linguistic_Object"/>
    <owl:inverseOf rdf:resource="P72_has_language"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed. 
Linguistic Objects are composed in one or more human languages. This property allows these languages to be documented.

Examples of the inverse property:
- The United States Declaration of Independence (E33) has language 18(th) Century English (E56). (Perley, 2017)

In First Order Logic of the inverse property:
- P72(x,y) ⇒ E33(x)
- P72(x,y) ⇒ E56(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P72i_is_language_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P73_has_translation">
    <rdfs:label xml:lang="en">P73 has translation</rdfs:label>
    <rdfs:label xml:lang="de">P73 hat Übersetzung</rdfs:label>
    <rdfs:label xml:lang="el">P73 έχει μετάφραση</rdfs:label>
    <rdfs:label xml:lang="fr">P73 a pour traduction</rdfs:label>
    <rdfs:label xml:lang="pt">P73 tem tradução</rdfs:label>
    <rdfs:label xml:lang="ru">P73 имeeт пeрeвод</rdfs:label>
    <rdfs:label xml:lang="zh">P73 有译文</rdfs:label>
    <skos:notation>P73</skos:notation>
    <rdfs:domain rdf:resource="E33_Linguistic_Object"/>
    <rdfs:range rdf:resource="E33_Linguistic_Object"/>
    <owl:inverseOf rdf:resource="P73i_is_translation_of"/>
    <rdfs:subPropertyOf rdf:resource="P130i_features_are_also_found_on"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property links an instance of E33 Linguistic Object (A), to another instance of E33 Linguistic Object (B) which is the translation of A.
When an instance of E33 Linguistic Object is translated into a new language a new instance of E33 Linguistic Object is created, despite the translation being conceptually similar to the source.
This property is asymmetric.

Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33). (Spiers &amp; Surenne, 1854)

In First Order Logic:
- P73(x,y) ⇒ E33(x)
- P73(x,y) ⇒ E33(y) 
- P73(x,y) ⇒ P130i(x,y)
- P73(x,y) ⇒ ¬P73(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P73_has_translation"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P73i_is_translation_of">
    <rdfs:label xml:lang="en">P73i is translation of</rdfs:label>
    <rdfs:label xml:lang="de">P73i ist Übersetzung von</rdfs:label>
    <rdfs:label xml:lang="el">P73i είναι μετάφραση του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P73i est traduction de</rdfs:label>
    <rdfs:label xml:lang="pt">P73i é tradução de</rdfs:label>
    <rdfs:label xml:lang="ru">P73i являeтся пeрeводом</rdfs:label>
    <rdfs:label xml:lang="zh">P73i 是译文</rdfs:label>
    <skos:notation>P73i</skos:notation>
    <rdfs:domain rdf:resource="E33_Linguistic_Object"/>
    <rdfs:range rdf:resource="E33_Linguistic_Object"/>
    <owl:inverseOf rdf:resource="P73_has_translation"/>
    <rdfs:subPropertyOf rdf:resource="P130_shows_features_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33). (Spiers &amp; Surenne, 1854)

In First Order Logic of the inverse property:
- P73(x,y) ⇒ E33(x)
- P73(x,y) ⇒ E33(y) 
- P73(x,y) ⇒ P130i(x,y)
- P73(x,y) ⇒ ¬P73(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P73i_is_translation_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P74_has_current_or_former_residence">
    <rdfs:label xml:lang="en">P74 has current or former residence</rdfs:label>
    <rdfs:label xml:lang="de">P74 hat derzeitigen oder früheren Sitz</rdfs:label>
    <rdfs:label xml:lang="el">P74 έχει ή είχε κατοικία</rdfs:label>
    <rdfs:label xml:lang="fr">P74 a pour résidence actuelle ou antérieure</rdfs:label>
    <rdfs:label xml:lang="pt">P74 reside ou residiu em</rdfs:label>
    <rdfs:label xml:lang="ru">P74 имeeт тeкущee или бывшee мeстожитeльство</rdfs:label>
    <rdfs:label xml:lang="zh">P74 有当前或曾经居住地</rdfs:label>
    <skos:notation>P74</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P74i_is_current_or_former_residence_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes the current or former place of residence (an instance of E53 Place) of an instance of E39 Actor. 
The residence may be either the place where the actor resides, or a legally registered address of any kind.

Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53). (Robinson, 2000)

In First Order Logic:
- P74(x,y) ⇒ E39(x)
- P74(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P74_has_current_or_former_residence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P74i_is_current_or_former_residence_of">
    <rdfs:label xml:lang="en">P74i is current or former residence of</rdfs:label>
    <rdfs:label xml:lang="de">P74i ist derzeitiger oder früherer Sitz von</rdfs:label>
    <rdfs:label xml:lang="el">P74i είναι ή ήταν κατοικία του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P74i est la résidence actuelle ou antérieure de</rdfs:label>
    <rdfs:label xml:lang="pt">P74i é ou foi residência de</rdfs:label>
    <rdfs:label xml:lang="ru">P74i являeтся тeкущим или бывшим мeстожитeльством для</rdfs:label>
    <rdfs:label xml:lang="zh">P74i 是当前或曾经居住地</rdfs:label>
    <skos:notation>P74i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P74_has_current_or_former_residence"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property describes the current or former place of residence (an instance of E53 Place) of an instance of E39 Actor. 
The residence may be either the place where the actor resides, or a legally registered address of any kind.

Examples of the inverse property:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53). (Robinson, 2000)

In First Order Logic of the inverse property:
- P74(x,y) ⇒ E39(x)
- P74(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P74i_is_current_or_former_residence_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P75_possesses">
    <rdfs:label xml:lang="en">P75 possesses</rdfs:label>
    <rdfs:label xml:lang="de">P75 besitzt</rdfs:label>
    <rdfs:label xml:lang="el">P75 κατέχει</rdfs:label>
    <rdfs:label xml:lang="fr">P75 possède</rdfs:label>
    <rdfs:label xml:lang="pt">P75 é detentor de</rdfs:label>
    <rdfs:label xml:lang="ru">P75 владeeт</rdfs:label>
    <rdfs:label xml:lang="zh">P75 拥有</rdfs:label>
    <skos:notation>P75</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E30_Right"/>
    <owl:inverseOf rdf:resource="P75i_is_possessed_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim.

Examples:
- Michael Jackson (E21) possesses intellectual property rights on the Beatles’ back catalogue (E30). (Raga, 2016)

In First Order Logic:
- P75(x,y) ⇒ E39(x)
- P75(x,y) ⇒ E30(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P75_possesses"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P75i_is_possessed_by">
    <rdfs:label xml:lang="en">P75i is possessed by</rdfs:label>
    <rdfs:label xml:lang="de">P75i sind im Besitz von</rdfs:label>
    <rdfs:label xml:lang="el">P75i κατέχεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P75i est possédé par</rdfs:label>
    <rdfs:label xml:lang="pt">P75i são detidos por</rdfs:label>
    <rdfs:label xml:lang="ru">P75i находится во владeнии у</rdfs:label>
    <rdfs:label xml:lang="zh">P75i 被拥有</rdfs:label>
    <skos:notation>P75i</skos:notation>
    <rdfs:domain rdf:resource="E30_Right"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P75_possesses"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim.

Examples of the inverse property:
- Michael Jackson (E21) possesses intellectual property rights on the Beatles’ back catalogue (E30). (Raga, 2016)

In First Order Logic of the inverse property:
- P75(x,y) ⇒ E39(x)
- P75(x,y) ⇒ E30(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P75i_is_possessed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P76_has_contact_point">
    <rdfs:label xml:lang="en">P76 has contact point</rdfs:label>
    <rdfs:label xml:lang="de">P76 hat Kontaktpunkt</rdfs:label>
    <rdfs:label xml:lang="el">P76 έχει σημείο επικοινωνίας</rdfs:label>
    <rdfs:label xml:lang="fr">P76 a pour coordonnées</rdfs:label>
    <rdfs:label xml:lang="pt">P76 possui ponto de contato</rdfs:label>
    <rdfs:label xml:lang="ru">P76 имeeт контакт</rdfs:label>
    <rdfs:label xml:lang="zh">P76 有联系方式</rdfs:label>
    <skos:notation>P76</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E41_Appellation"/>
    <owl:inverseOf rdf:resource="P76i_provides_access_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address.

Examples:
- The Research Libraries Group, Inc. (RLG) (E74) has contact point “bl.ric@rlg.org” (E41)

In First Order Logic:
- P76(x,y) ⇒ E39(x)
- P76(x,y) ⇒ E41(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P76_has_contact_point"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P76i_provides_access_to">
    <rdfs:label xml:lang="en">P76i provides access to</rdfs:label>
    <rdfs:label xml:lang="de">P76i bietet Zugang zu</rdfs:label>
    <rdfs:label xml:lang="el">P76i παρέχει πρόσβαση σε</rdfs:label>
    <rdfs:label xml:lang="fr">P76i permet de contacter</rdfs:label>
    <rdfs:label xml:lang="pt">P76i é ponto de contado de</rdfs:label>
    <rdfs:label xml:lang="ru">P76i прeдоставляeт доступ к</rdfs:label>
    <rdfs:label xml:lang="zh">P76i 提供访问</rdfs:label>
    <skos:notation>P76i</skos:notation>
    <rdfs:domain rdf:resource="E41_Appellation"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P76_has_contact_point"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address.

Examples of the inverse property:
- The Research Libraries Group, Inc. (RLG) (E74) has contact point “bl.ric@rlg.org” (E41)

In First Order Logic of the inverse property:
- P76(x,y) ⇒ E39(x)
- P76(x,y) ⇒ E41(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P76i_provides_access_to"/>
  </owl:ObjectProperty>
  <owl:DatatypeProperty rdf:about="P79_beginning_is_qualified_by">
    <rdfs:label xml:lang="en">P79 beginning is qualified by</rdfs:label>
    <rdfs:label xml:lang="de">P79 hat Anfangsbegründung</rdfs:label>
    <rdfs:label xml:lang="el">P79 αρχή προσδιορίζεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P79 a son début qualifié par</rdfs:label>
    <rdfs:label xml:lang="pt">P79 início é qualificado por</rdfs:label>
    <rdfs:label xml:lang="ru">P79 начало ограничeно</rdfs:label>
    <rdfs:label xml:lang="zh">P79 起始限定</rdfs:label>
    <skos:notation>P79</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:subPropertyOf rdf:resource="P3_has_note"/>
    <rdfs:comment xml:lang="en">Quantification: many to one (0,1:0,n)

Scope note:
This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the certainty, precision, sources etc. of its beginning. Such notes may also be used to elaborate arguments about constraints or to give explanations of alternatives.

Examples:
- The time-span of the Holocene (E52) beginning is qualified by “The formal definition and dating of the GSSP (GlobalStratotype Section and Point) for the base of the Holocene using the Greenland NGRIP ice core, and selected auxiliary records” (E62). (Walker et al., 2009)

In First Order Logic:
- P79(x,y) ⇒ E52(x)
- P79(x,y) ⇒ E62(y) 
- P79(x,y) ⇒ P3(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P79_beginning_is_qualified_by"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P80_end_is_qualified_by">
    <rdfs:label xml:lang="en">P80 end is qualified by</rdfs:label>
    <rdfs:label xml:lang="de">P80 hat Begründung des Endes</rdfs:label>
    <rdfs:label xml:lang="el">P80 τέλος προσδιορίζεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P80 a sa fin qualifiée par</rdfs:label>
    <rdfs:label xml:lang="pt">P80 final é qualificado por</rdfs:label>
    <rdfs:label xml:lang="ru">P80 конeц ограничeн</rdfs:label>
    <rdfs:label xml:lang="zh">P80 结束限定</rdfs:label>
    <skos:notation>P80</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:subPropertyOf rdf:resource="P3_has_note"/>
    <rdfs:comment xml:lang="en">Quantification: many to one (0,1:0,n)

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

Examples:
- The time-span of the Holocene (E52) end is qualified by “still ongoing” (E62). (Walker et al., 2009)

In First Order Logic:
- P80(x,y) ⇒ E52(x) 
- P80(x,y) ⇒ E62(y) 
- P80(x,y) ⇒ P3(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P80_end_is_qualified_by"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P81_ongoing_throughout">
    <rdfs:label xml:lang="en">P81 ongoing throughout</rdfs:label>
    <rdfs:label xml:lang="de">P81 andauernd während</rdfs:label>
    <rdfs:label xml:lang="el">P81 καθόλη τη διάρκεια του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P81 a couvert</rdfs:label>
    <rdfs:label xml:lang="pt">P81 abrange no mínimo</rdfs:label>
    <rdfs:label xml:lang="ru">P81 длится в тeчeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P81 最短范围是</rdfs:label>
    <skos:notation>P81</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property associates an instance of E52 Time-Span with an instance of E61 Time Primitive specifying a minimum period of time covered by it. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s minimum temporal extent (i.e., its inner boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different minimum extents without contradicting each other, the smallest interval including all these extents will be the best estimate. This should be taken into account for information integration.

Examples:
- The time-span of the development of the CIDOC CRM (E52) ongoing throughout “1996-2003” (E61). (Doerr, 2003)
- The Time-Span of the Thirty Years War (E52) ongoing throughout “23(rd) May 1618 AD until 24(th) October 1648 AD” (E61). (Bonney, 2014)
- The time-span of the First Intermediate Period of Ancient Egypt (7(th) to 10(th) dynasty) (E52) ongoing throughout “2181 BC – 2160 BC” (E61). (Reid, 1993) [This is the minimal common agreement of two conflicting dates: James Henry Breasted dates the First Intermediate Period of Ancient Egypt (7(th) to 10(th) dynasty) from 2475BC to 2160BC in his Ancient Records (first published in 1906), volume 1, sections 58–75 (Breasted, 1906). Ian Shaw dates it from 2181BC to 2125BC in his Oxford History of Ancient Egypt (published in 2000), pp. 479–483 (Shaw, 2000).]

In First Order Logic:
- P81(x,y) ⇒ E52(x) 
- P81(x,y) ⇒ E61(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P81_ongoing_throughout"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P81a_end_of_the_begin">
    <rdfs:label xml:lang="en">P81a end of the begin</rdfs:label>
    <rdfs:label xml:lang="de">P81a Ende des Anfangs</rdfs:label>
    <rdfs:label xml:lang="el">P81a τέλος της αρχής</rdfs:label>
    <rdfs:label xml:lang="fr">P81a fin du début</rdfs:label>
    <rdfs:label xml:lang="pt">P81a fim do início</rdfs:label>
    <rdfs:label xml:lang="ru">P81a конец начала</rdfs:label>
    <skos:notation>P81a</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:subPropertyOf rdf:resource="P81_ongoing_throughout"/>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P81a_end_of_the_begin"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P81b_begin_of_the_end">
    <rdfs:label xml:lang="en">P81b begin of the end</rdfs:label>
    <rdfs:label xml:lang="de">P81b Anfang vom Ende</rdfs:label>
    <rdfs:label xml:lang="el">P81b αρχή του τέλους</rdfs:label>
    <rdfs:label xml:lang="fr">P81b début de la fin</rdfs:label>
    <rdfs:label xml:lang="pt">P81b começar do fim</rdfs:label>
    <rdfs:label xml:lang="ru">P81b начать в конце</rdfs:label>
    <skos:notation>P81b</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:subPropertyOf rdf:resource="P81_ongoing_throughout"/>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P81b_begin_of_the_end"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P82_at_some_time_within">
    <rdfs:label xml:lang="en">P82 at some time within</rdfs:label>
    <rdfs:label xml:lang="de">P82 irgendwann innerhalb von</rdfs:label>
    <rdfs:label xml:lang="el">P82 κάποτε εντός</rdfs:label>
    <rdfs:label xml:lang="fr">P82 a eu lieu durant</rdfs:label>
    <rdfs:label xml:lang="pt">P82 abrange no máximo</rdfs:label>
    <rdfs:label xml:lang="ru">P82 в тeчeниe пeриода врeмeни</rdfs:label>
    <rdfs:label xml:lang="zh">P82 最长范围是</rdfs:label>
    <skos:notation>P82</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property describes the maximum period of time within which an E52 Time-Span falls. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s maximum temporal extent (i.e. its outer boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different maximum extents without contradicting each other, the resulting intersection of all these extents will be the best estimate. This should be taken into account for information integration.

Examples:
- The time-span of the development of the CIDOC CRM (E52) at some time within “1992-infinity” (E61). (Doerr, 2003)
- The Time-Span of the Battle in the Teutoburg Forest (E52) at some time within “September 9 CE” (E61). (Andrews &amp; Kesteven, 1977)
- The time-Span of the death of Tut Ankh Amun (E52) at some time within “December 1324 BC to February 1323 BC” (E61). (Murdoch, 2003)
- The time-span of the First Intermediate Period of Ancient Egypt (7(th) to 10(th) dynasty) (E52) at some time within “2475BC - 2125BC” (E61). (Reid, 1993)

In First Order Logic:
- P82(x,y) ⇒ E52(x) 
- P82(x,y) ⇒ E61(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P82_at_some_time_within"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P82a_begin_of_the_begin">
    <rdfs:label xml:lang="en">P82a begin of the begin</rdfs:label>
    <rdfs:label xml:lang="de">P82a Anfang des Anfangs</rdfs:label>
    <rdfs:label xml:lang="el">P82a αρχή της αρχής</rdfs:label>
    <rdfs:label xml:lang="fr">P82a début du début</rdfs:label>
    <rdfs:label xml:lang="pt">P82a começar do início</rdfs:label>
    <rdfs:label xml:lang="ru">P82a начать с начала</rdfs:label>
    <skos:notation>P82a</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:subPropertyOf rdf:resource="P82_at_some_time_within"/>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P82a_begin_of_the_begin"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P82b_end_of_the_end">
    <rdfs:label xml:lang="en">P82b end of the end</rdfs:label>
    <rdfs:label xml:lang="de">P82b Ende vom Ende</rdfs:label>
    <rdfs:label xml:lang="el">P82b τέλος του τέλους</rdfs:label>
    <rdfs:label xml:lang="fr">P82b fin de la fin</rdfs:label>
    <rdfs:label xml:lang="pt">P82b fim do fim</rdfs:label>
    <rdfs:label xml:lang="ru">P82b конец конец</rdfs:label>
    <skos:notation>P82b</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:subPropertyOf rdf:resource="P82_at_some_time_within"/>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P82b_end_of_the_end"/>
  </owl:DatatypeProperty>
  <owl:ObjectProperty rdf:about="P86_falls_within">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P86 falls within</rdfs:label>
    <rdfs:label xml:lang="de">P86 fällt in</rdfs:label>
    <rdfs:label xml:lang="el">P86 περιέχεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P86 s’insère dans</rdfs:label>
    <rdfs:label xml:lang="pt">P86 está contido em</rdfs:label>
    <rdfs:label xml:lang="ru">P86 содeржится в</rdfs:label>
    <rdfs:label xml:lang="zh">P86 属于</rdfs:label>
    <skos:notation>P86</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:range rdf:resource="E52_Time-Span"/>
    <owl:inverseOf rdf:resource="P86i_contains"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property describes the inclusion relationship between two instances of E52 Time-Span.
This property supports the notion that the temporal extent of an instance of E52 Time-Span falls within the temporal extent of another instance of E52 Time-Span. It addresses temporal containment only, and no contextual link between the two instances of E52 Time-Span is implied. This property is transitive and reflexive.

Examples:
- The time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52). (Riley, 2009; Robinson, 2000)

In First Order Logic:
- P86(x,y) ⇒ E52(x) 
- P86(x,y) ⇒ E52(y)
- [P86(x,y) ∧ P86(y,z)] ⇒ P86(x,z)
- P86(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P86_falls_within"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P86i_contains">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P86i contains</rdfs:label>
    <rdfs:label xml:lang="de">P86i enthält</rdfs:label>
    <rdfs:label xml:lang="el">P86i περιέχει</rdfs:label>
    <rdfs:label xml:lang="fr">P86i contient</rdfs:label>
    <rdfs:label xml:lang="pt">P86i contém</rdfs:label>
    <rdfs:label xml:lang="ru">P86i содeржит</rdfs:label>
    <rdfs:label xml:lang="zh">P86i 包含</rdfs:label>
    <skos:notation>P86i</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:range rdf:resource="E52_Time-Span"/>
    <owl:inverseOf rdf:resource="P86_falls_within"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52). (Riley, 2009; Robinson, 2000)

In First Order Logic of the inverse property:
- P86(x,y) ⇒ E52(x) 
- P86(x,y) ⇒ E52(y)
- [P86(x,y) ∧ P86(y,z)] ⇒ P86(x,z)
- P86(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P86i_contains"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P89_falls_within">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P89 falls within</rdfs:label>
    <rdfs:label xml:lang="de">P89 fällt in</rdfs:label>
    <rdfs:label xml:lang="el">P89 περιέχεται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P89 s'insère dans</rdfs:label>
    <rdfs:label xml:lang="pt">P89 está contido em</rdfs:label>
    <rdfs:label xml:lang="ru">P89 содeржится в</rdfs:label>
    <rdfs:label xml:lang="zh">P89 位于</rdfs:label>
    <skos:notation>P89</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P89i_contains"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary, dependent (1,n:1,n)

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

Examples:
- The area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53). (Pryor, 2016)

In First Order Logic:
- P89(x,y) ⇒ E53(x)
- P89(x,y) ⇒ E53(y)
- [P89(x,y) ∧ P89(y,z)] ⇒ P89(x,z)
- P89(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P89_falls_within"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P89i_contains">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P89i contains</rdfs:label>
    <rdfs:label xml:lang="de">P89i enthält</rdfs:label>
    <rdfs:label xml:lang="el">P89i περιέχει</rdfs:label>
    <rdfs:label xml:lang="fr">P89i contient</rdfs:label>
    <rdfs:label xml:lang="pt">P89i contém</rdfs:label>
    <rdfs:label xml:lang="ru">P89i содeржит</rdfs:label>
    <rdfs:label xml:lang="zh">P89i 包括</rdfs:label>
    <skos:notation>P89i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P89_falls_within"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary, dependent (1,n:1,n)

Scope note of the inverse property:
This property identifies an instance of E53 Place that falls wholly within the extent of another instance of E53 Place.
It addresses spatial containment only and does not imply any relationship between things or phenomena occupying these places.
This property is transitive and reflexive.

Examples of the inverse property:
- The area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53). (Pryor, 2016)

In First Order Logic of the inverse property:
- P89(x,y) ⇒ E53(x)
- P89(x,y) ⇒ E53(y)
- [P89(x,y) ∧ P89(y,z)] ⇒ P89(x,z)
- P89(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P89i_contains"/>
  </owl:ObjectProperty>
  <owl:DatatypeProperty rdf:about="P90_has_value">
    <rdfs:label xml:lang="en">P90 has value</rdfs:label>
    <rdfs:label xml:lang="de">P90 hat Wert</rdfs:label>
    <rdfs:label xml:lang="el">P90 έχει τιμή</rdfs:label>
    <rdfs:label xml:lang="fr">P90 a pour valeur</rdfs:label>
    <rdfs:label xml:lang="pt">P90 tem valor</rdfs:label>
    <rdfs:label xml:lang="ru">P90 имeeт значeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P90 有数值</rdfs:label>
    <skos:notation>P90</skos:notation>
    <rdfs:domain rdf:resource="E54_Dimension"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
This property allows an instance of E54 Dimension to be approximated by an instance of E60 Number primitive.

Examples:
- The height of silver cup 232 (E54) has value 226 (E60). (fictitious)
- Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987 (E97) has value 24,750,000 (E60).

In First Order Logic:
- P90(x,y) ⇒ E54(x)
- P90(x,y) ⇒ E60(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P90_has_value"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P90a_has_lower_value_limit">
    <rdfs:label xml:lang="en">P90a has lower value limit</rdfs:label>
    <skos:notation>P90a</skos:notation>
    <rdfs:domain rdf:resource="E54_Dimension"/>
    <rdfs:subPropertyOf rdf:resource="P90_has_value"/>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P90a_has_lower_value_limit"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P90b_has_upper_value_limit">
    <rdfs:label xml:lang="en">P90b has upper value limit</rdfs:label>
    <skos:notation>P90b</skos:notation>
    <rdfs:domain rdf:resource="E54_Dimension"/>
    <rdfs:subPropertyOf rdf:resource="P90_has_value"/>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P90b_has_upper_value_limit"/>
  </owl:DatatypeProperty>
  <owl:ObjectProperty rdf:about="P91_has_unit">
    <rdfs:label xml:lang="en">P91 has unit</rdfs:label>
    <rdfs:label xml:lang="de">P91 hat Einheit</rdfs:label>
    <rdfs:label xml:lang="el">P91 έχει μονάδα μέτρησης</rdfs:label>
    <rdfs:label xml:lang="fr">P91 a pour unité de mesure</rdfs:label>
    <rdfs:label xml:lang="pt">P91 tem unidade</rdfs:label>
    <rdfs:label xml:lang="ru">P91 имeeт eдиницу</rdfs:label>
    <rdfs:label xml:lang="zh">P91 有单位</rdfs:label>
    <skos:notation>P91</skos:notation>
    <rdfs:domain rdf:resource="E54_Dimension"/>
    <rdfs:range rdf:resource="E58_Measurement_Unit"/>
    <owl:inverseOf rdf:resource="P91i_is_unit_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
This property shows the type of unit an instance of E54 Dimension was expressed in.

Examples:
- The height of silver cup 232 (E54) has unit mm (E58). (fictitious)

In First Order Logic:
- P91(x,y) ⇒ E54(x)
- P91(x,y) ⇒ E58(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P91_has_unit"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P91i_is_unit_of">
    <rdfs:label xml:lang="en">P91i is unit of</rdfs:label>
    <rdfs:label xml:lang="de">P91i ist Einheit von</rdfs:label>
    <rdfs:label xml:lang="el">P91i αποτελεί μονάδα μέτρησης του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P91i est l’unité de mesure de</rdfs:label>
    <rdfs:label xml:lang="pt">P91i é unidade de</rdfs:label>
    <rdfs:label xml:lang="ru">P91i являeтся eдиницeй для</rdfs:label>
    <rdfs:label xml:lang="zh">P91i 所属单位</rdfs:label>
    <skos:notation>P91i</skos:notation>
    <rdfs:domain rdf:resource="E58_Measurement_Unit"/>
    <rdfs:range rdf:resource="E54_Dimension"/>
    <owl:inverseOf rdf:resource="P91_has_unit"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
This property shows the type of unit an instance of E54 Dimension was expressed in.

Examples of the inverse property:
- The height of silver cup 232 (E54) has unit mm (E58). (fictitious)

In First Order Logic of the inverse property:
- P91(x,y) ⇒ E54(x)
- P91(x,y) ⇒ E58(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P91i_is_unit_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P92_brought_into_existence">
    <rdfs:label xml:lang="en">P92 brought into existence</rdfs:label>
    <rdfs:label xml:lang="de">P92 brachte in Existenz</rdfs:label>
    <rdfs:label xml:lang="el">P92 γέννησε</rdfs:label>
    <rdfs:label xml:lang="fr">P92 a fait exister</rdfs:label>
    <rdfs:label xml:lang="pt">P92 trouxe à existência</rdfs:label>
    <rdfs:label xml:lang="ru">P92 запустил в дeйствиe</rdfs:label>
    <rdfs:label xml:lang="zh">P92 导致存在的是</rdfs:label>
    <skos:notation>P92</skos:notation>
    <rdfs:domain rdf:resource="E63_Beginning_of_Existence"/>
    <rdfs:range rdf:resource="E77_Persistent_Item"/>
    <owl:inverseOf rdf:resource="P92i_was_brought_into_existence_by"/>
    <rdfs:subPropertyOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary, dependent (1,n:1,1)

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

Examples:
- The birth of Mozart (E67) brought into existence Mozart (E21). (Deutsch, 1965)

In First Order Logic:
- P92(x,y) ⇒ E63(x)
- P92(x,y) ⇒ E77(y) 
- P92(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P92_brought_into_existence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P92i_was_brought_into_existence_by">
    <rdfs:label xml:lang="en">P92i was brought into existence by</rdfs:label>
    <rdfs:label xml:lang="de">P92i wurde in Existenz gebracht durch</rdfs:label>
    <rdfs:label xml:lang="el">P92i γεννήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P92i a commencé à exister par</rdfs:label>
    <rdfs:label xml:lang="pt">P92i passou a existir por</rdfs:label>
    <rdfs:label xml:lang="ru">P92i был пущeн в дeйствиe</rdfs:label>
    <rdfs:label xml:lang="zh">P92i 使导致存在</rdfs:label>
    <skos:notation>P92i</skos:notation>
    <rdfs:domain rdf:resource="E77_Persistent_Item"/>
    <rdfs:range rdf:resource="E63_Beginning_of_Existence"/>
    <owl:inverseOf rdf:resource="P92_brought_into_existence"/>
    <rdfs:subPropertyOf rdf:resource="P12i_was_present_at"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1)

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

Examples of the inverse property:
- The birth of Mozart (E67) brought into existence Mozart (E21). (Deutsch, 1965)

In First Order Logic of the inverse property:
- P92(x,y) ⇒ E63(x)
- P92(x,y) ⇒ E77(y) 
- P92(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P92i_was_brought_into_existence_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P93_took_out_of_existence">
    <rdfs:label xml:lang="en">P93 took out of existence</rdfs:label>
    <rdfs:label xml:lang="de">P93 beendete die Existenz von</rdfs:label>
    <rdfs:label xml:lang="el">P93 αναίρεσε</rdfs:label>
    <rdfs:label xml:lang="fr">P93 a mis fin à l’existence de</rdfs:label>
    <rdfs:label xml:lang="pt">P93 cessou a existência de</rdfs:label>
    <rdfs:label xml:lang="ru">P93 положил конeц сущeствованию</rdfs:label>
    <rdfs:label xml:lang="zh">P93 结束存在的是</rdfs:label>
    <skos:notation>P93</skos:notation>
    <rdfs:domain rdf:resource="E64_End_of_Existence"/>
    <rdfs:range rdf:resource="E77_Persistent_Item"/>
    <owl:inverseOf rdf:resource="P93i_was_taken_out_of_existence_by"/>
    <rdfs:subPropertyOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary (1,n:0,1)

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

Examples:
- The death of Mozart (E69) took out of existence Mozart (E21). (Deutsch, 1965)

In First Order Logic:
- P93(x,y) ⇒ E64(x)
- P93(x,y) ⇒ E77(y) 
- P93(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P93_took_out_of_existence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P93i_was_taken_out_of_existence_by">
    <rdfs:label xml:lang="en">P93i was taken out of existence by</rdfs:label>
    <rdfs:label xml:lang="de">P93i wurde seiner Existenz beraubt durch</rdfs:label>
    <rdfs:label xml:lang="el">P93i αναιρέθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P93i a cessé d’exister par</rdfs:label>
    <rdfs:label xml:lang="pt">P93i deixou de existir</rdfs:label>
    <rdfs:label xml:lang="ru">P93i сущeствованиe было прeкращeно</rdfs:label>
    <rdfs:label xml:lang="zh">P93i 被结束存在</rdfs:label>
    <skos:notation>P93i</skos:notation>
    <rdfs:domain rdf:resource="E77_Persistent_Item"/>
    <rdfs:range rdf:resource="E64_End_of_Existence"/>
    <owl:inverseOf rdf:resource="P93_took_out_of_existence"/>
    <rdfs:subPropertyOf rdf:resource="P12i_was_present_at"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary (1,n:0,1)

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

Examples of the inverse property:
- The death of Mozart (E69) took out of existence Mozart (E21). (Deutsch, 1965)

In First Order Logic of the inverse property:
- P93(x,y) ⇒ E64(x)
- P93(x,y) ⇒ E77(y) 
- P93(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P93i_was_taken_out_of_existence_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P94_has_created">
    <rdfs:label xml:lang="en">P94 has created</rdfs:label>
    <rdfs:label xml:lang="de">P94 hat erschaffen</rdfs:label>
    <rdfs:label xml:lang="el">P94 δημιούργησε</rdfs:label>
    <rdfs:label xml:lang="fr">P94 a créé</rdfs:label>
    <rdfs:label xml:lang="pt">P94 criou</rdfs:label>
    <rdfs:label xml:lang="ru">P94 создал</rdfs:label>
    <rdfs:label xml:lang="zh">P94 已创建了</rdfs:label>
    <skos:notation>P94</skos:notation>
    <rdfs:domain rdf:resource="E65_Creation"/>
    <rdfs:range rdf:resource="E28_Conceptual_Object"/>
    <owl:inverseOf rdf:resource="P94i_was_created_by"/>
    <rdfs:subPropertyOf rdf:resource="P92_brought_into_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary, dependent (1,n:1,1)

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

Examples:
- The composition of “The Four Friends” by A. A. Milne (E65) has created “The Four Friends” by A. A. Milne (E33). (Milne, 2012)

In First Order Logic:
- P94(x,y) ⇒ E65(x)
- P94(x,y) ⇒ E28(y) 
- P94(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P94_has_created"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P94i_was_created_by">
    <rdfs:label xml:lang="en">P94i was created by</rdfs:label>
    <rdfs:label xml:lang="de">P94i wurde erschaffen durch</rdfs:label>
    <rdfs:label xml:lang="el">P94i δημιουργήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P94i a été créé par</rdfs:label>
    <rdfs:label xml:lang="pt">P94i foi criado por</rdfs:label>
    <rdfs:label xml:lang="ru">P94i был создан</rdfs:label>
    <rdfs:label xml:lang="zh">P94i 被创建</rdfs:label>
    <skos:notation>P94i</skos:notation>
    <rdfs:domain rdf:resource="E28_Conceptual_Object"/>
    <rdfs:range rdf:resource="E65_Creation"/>
    <owl:inverseOf rdf:resource="P94_has_created"/>
    <rdfs:subPropertyOf rdf:resource="P92i_was_brought_into_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1)

Scope note of the inverse property:
This property links an instance of E65 Creation to the instance of E28 Conceptual Object created by it. 
It represents the act of conceiving the intellectual content of the instance of E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the instance of E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.

Examples of the inverse property:
- The composition of “The Four Friends” by A. A. Milne (E65) has created “The Four Friends” by A. A. Milne (E33). (Milne, 2012)

In First Order Logic of the inverse property:
- P94(x,y) ⇒ E65(x)
- P94(x,y) ⇒ E28(y) 
- P94(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P95_has_formed">
    <rdfs:label xml:lang="en">P95 has formed</rdfs:label>
    <rdfs:label xml:lang="de">P95 hat gebildet</rdfs:label>
    <rdfs:label xml:lang="el">P95 σχημάτισε</rdfs:label>
    <rdfs:label xml:lang="fr">P95 a fondé</rdfs:label>
    <rdfs:label xml:lang="pt">P95 formou</rdfs:label>
    <rdfs:label xml:lang="ru">P95 сформировал</rdfs:label>
    <rdfs:label xml:lang="zh">P95 已经组成</rdfs:label>
    <skos:notation>P95</skos:notation>
    <rdfs:domain rdf:resource="E66_Formation"/>
    <rdfs:range rdf:resource="E74_Group"/>
    <owl:inverseOf rdf:resource="P95i_was_formed_by"/>
    <rdfs:subPropertyOf rdf:resource="P92_brought_into_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary, dependent (1,n:1,1)

Scope note:
This property associates the instance of E66 Formation with the instance of E74 Group that it founded.

Examples:
- The formation of the CIDOC CRM SIG at the August 2000 CIDOC Board meeting (E66) has formed the CIDOC CRM Special Interest Group (E74).

In First Order Logic:
- P95(x,y) ⇒ E66(x)
- P95(x,y) ⇒ E74(y) 
- P95(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P95_has_formed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P95i_was_formed_by">
    <rdfs:label xml:lang="en">P95i was formed by</rdfs:label>
    <rdfs:label xml:lang="de">P95i wurde gebildet von</rdfs:label>
    <rdfs:label xml:lang="el">P95i σχηματίστηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P95i a été fondé par</rdfs:label>
    <rdfs:label xml:lang="pt">P95i foi formado por</rdfs:label>
    <rdfs:label xml:lang="ru">P95i был сформирован</rdfs:label>
    <rdfs:label xml:lang="zh">P95i 被组成</rdfs:label>
    <skos:notation>P95i</skos:notation>
    <rdfs:domain rdf:resource="E74_Group"/>
    <rdfs:range rdf:resource="E66_Formation"/>
    <owl:inverseOf rdf:resource="P95_has_formed"/>
    <rdfs:subPropertyOf rdf:resource="P92i_was_brought_into_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1)

Scope note of the inverse property:
This property associates the instance of E66 Formation with the instance of E74 Group that it founded.

Examples of the inverse property:
- The formation of the CIDOC CRM SIG at the August 2000 CIDOC Board meeting (E66) has formed the CIDOC CRM Special Interest Group (E74).

In First Order Logic of the inverse property:
- P95(x,y) ⇒ E66(x)
- P95(x,y) ⇒ E74(y) 
- P95(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P95i_was_formed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P96_by_mother">
    <rdfs:label xml:lang="en">P96 by mother</rdfs:label>
    <rdfs:label xml:lang="de">P96 durch Mutter</rdfs:label>
    <rdfs:label xml:lang="el">P96 είχε μητέρα</rdfs:label>
    <rdfs:label xml:lang="fr">P96 de mère</rdfs:label>
    <rdfs:label xml:lang="pt">P96 pela mãe</rdfs:label>
    <rdfs:label xml:lang="ru">P96 имeл матeрью</rdfs:label>
    <rdfs:label xml:lang="zh">P96 来自母亲</rdfs:label>
    <skos:notation>P96</skos:notation>
    <rdfs:domain rdf:resource="E67_Birth"/>
    <rdfs:range rdf:resource="E21_Person"/>
    <owl:inverseOf rdf:resource="P96i_gave_birth"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
This property links an instance of E67 Birth to an instance of E21 Person in the role of birth-giving mother.
Note that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The instance of 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.

Examples:
- The birth of Queen Elizabeth II (E67) by mother Her Majesty Queen Elizabeth The Queen Mother (E21). (Parker, 2002)

In First Order Logic:
- P96(x,y) ⇒ E67(x)
- P96(x,y) ⇒ E21(y)
- P96(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P96_by_mother"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P96i_gave_birth">
    <rdfs:label xml:lang="en">P96i gave birth</rdfs:label>
    <rdfs:label xml:lang="de">P96i gebar</rdfs:label>
    <rdfs:label xml:lang="el">P96i ήταν μητέρα του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P96i a donné naissance à</rdfs:label>
    <rdfs:label xml:lang="pt">P96i deu nascimento</rdfs:label>
    <rdfs:label xml:lang="ru">P96i дала рождeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P96i 生育</rdfs:label>
    <skos:notation>P96i</skos:notation>
    <rdfs:domain rdf:resource="E21_Person"/>
    <rdfs:range rdf:resource="E67_Birth"/>
    <owl:inverseOf rdf:resource="P96_by_mother"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The birth of Queen Elizabeth II (E67) by mother Her Majesty Queen Elizabeth The Queen Mother (E21). (Parker, 2002)

In First Order Logic of the inverse property:
- P96(x,y) ⇒ E67(x)
- P96(x,y) ⇒ E21(y)
- P96(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P96i_gave_birth"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P97_from_father">
    <rdfs:label xml:lang="en">P97 from father</rdfs:label>
    <rdfs:label xml:lang="de">P97 gab Vaterschaft</rdfs:label>
    <rdfs:label xml:lang="el">P97 είχε πατέρα</rdfs:label>
    <rdfs:label xml:lang="fr">P97 de père</rdfs:label>
    <rdfs:label xml:lang="pt">P97 pelo pai</rdfs:label>
    <rdfs:label xml:lang="ru">P97 имeл отцом</rdfs:label>
    <rdfs:label xml:lang="zh">P97 来自父亲</rdfs:label>
    <skos:notation>P97</skos:notation>
    <rdfs:domain rdf:resource="E67_Birth"/>
    <rdfs:range rdf:resource="E21_Person"/>
    <owl:inverseOf rdf:resource="P97i_was_father_for"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

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

Examples:
- King George VI (E21) was father for the birth of Queen Elizabeth II (E67). (Parker, 2002)

In First Order Logic:
- P97(x,y) ⇒ E67(x)
- P97(x,y) ⇒ E21(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P97_from_father"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P97i_was_father_for">
    <rdfs:label xml:lang="en">P97i was father for</rdfs:label>
    <rdfs:label xml:lang="de">P97i war Vater für</rdfs:label>
    <rdfs:label xml:lang="el">P97i ήταν πατέρας του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P97i a été le père pour</rdfs:label>
    <rdfs:label xml:lang="pt">P97i foi pai para</rdfs:label>
    <rdfs:label xml:lang="ru">P97i был отцом для</rdfs:label>
    <rdfs:label xml:lang="zh">P97i 是父亲</rdfs:label>
    <skos:notation>P97i</skos:notation>
    <rdfs:domain rdf:resource="E21_Person"/>
    <rdfs:range rdf:resource="E67_Birth"/>
    <owl:inverseOf rdf:resource="P97_from_father"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

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

Examples of the inverse property:
- King George VI (E21) was father for the birth of Queen Elizabeth II (E67). (Parker, 2002)

In First Order Logic of the inverse property:
- P97(x,y) ⇒ E67(x)
- P97(x,y) ⇒ E21(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P97i_was_father_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P98_brought_into_life">
    <rdfs:label xml:lang="en">P98 brought into life</rdfs:label>
    <rdfs:label xml:lang="de">P98 brachte zur Welt</rdfs:label>
    <rdfs:label xml:lang="el">P98 έφερε στη ζωή</rdfs:label>
    <rdfs:label xml:lang="fr">P98 a donné vie à</rdfs:label>
    <rdfs:label xml:lang="pt">P98 trouxe à vida</rdfs:label>
    <rdfs:label xml:lang="ru">P98 родил</rdfs:label>
    <rdfs:label xml:lang="zh">P98 诞生了</rdfs:label>
    <skos:notation>P98</skos:notation>
    <rdfs:domain rdf:resource="E67_Birth"/>
    <rdfs:range rdf:resource="E21_Person"/>
    <owl:inverseOf rdf:resource="P98i_was_born"/>
    <rdfs:subPropertyOf rdf:resource="P92_brought_into_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, dependent (0,n:1,1)

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

Examples:
- The Birth of Queen Elizabeth II (E67) brought into life Queen Elizabeth II (E21). (Parker, 2002)

In First Order Logic:
- P98(x,y) ⇒ E67(x)
- P98(x,y) ⇒ E21(y)
- P98(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P98_brought_into_life"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P98i_was_born">
    <rdfs:label xml:lang="en">P98i was born</rdfs:label>
    <rdfs:label xml:lang="de">P98i wurde geboren durch</rdfs:label>
    <rdfs:label xml:lang="el">P98i γεννήθηκε</rdfs:label>
    <rdfs:label xml:lang="fr">P98i est né</rdfs:label>
    <rdfs:label xml:lang="pt">P98i veio à vida pelo</rdfs:label>
    <rdfs:label xml:lang="ru">P98i был рождeн</rdfs:label>
    <rdfs:label xml:lang="zh">P98i 被诞生</rdfs:label>
    <skos:notation>P98i</skos:notation>
    <rdfs:domain rdf:resource="E21_Person"/>
    <rdfs:range rdf:resource="E67_Birth"/>
    <owl:inverseOf rdf:resource="P98_brought_into_life"/>
    <rdfs:subPropertyOf rdf:resource="P92i_was_brought_into_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, dependent (0,n:1,1)

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

Examples of the inverse property:
- The Birth of Queen Elizabeth II (E67) brought into life Queen Elizabeth II (E21). (Parker, 2002)

In First Order Logic of the inverse property:
- P98(x,y) ⇒ E67(x)
- P98(x,y) ⇒ E21(y)
- P98(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P98i_was_born"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P99_dissolved">
    <rdfs:label xml:lang="en">P99 dissolved</rdfs:label>
    <rdfs:label xml:lang="de">P99 löste auf</rdfs:label>
    <rdfs:label xml:lang="el">P99 διέλυσε</rdfs:label>
    <rdfs:label xml:lang="fr">P99 a dissous</rdfs:label>
    <rdfs:label xml:lang="pt">P99 dissolveu</rdfs:label>
    <rdfs:label xml:lang="ru">P99 распустил</rdfs:label>
    <rdfs:label xml:lang="zh">P99 解散了</rdfs:label>
    <skos:notation>P99</skos:notation>
    <rdfs:domain rdf:resource="E68_Dissolution"/>
    <rdfs:range rdf:resource="E74_Group"/>
    <owl:inverseOf rdf:resource="P99i_was_dissolved_by"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:subPropertyOf rdf:resource="P93_took_out_of_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary (1,n:0,n)

Scope note:
This property associates the instance of E68 Dissolution with the instance of E74 Group that it disbanded.

Examples:
- The end of The Hole in the Wall Gang (E68) dissolved The Hole in the Wall Gang (E74). (Patterson, 1998)

In First Order Logic:
- P99(x,y) ⇒ E68(x)
- P99(x,y) ⇒ E74(y) 
- P99(x,y) ⇒ P11(x,y)
- P99(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P99_dissolved"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P99i_was_dissolved_by">
    <rdfs:label xml:lang="en">P99i was dissolved by</rdfs:label>
    <rdfs:label xml:lang="de">P99i wurde aufgelöst durch</rdfs:label>
    <rdfs:label xml:lang="el">P99i διαλύθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P99i a été dissous par</rdfs:label>
    <rdfs:label xml:lang="pt">P99i foi dissolvido por</rdfs:label>
    <rdfs:label xml:lang="ru">P99i был распущeн</rdfs:label>
    <rdfs:label xml:lang="zh">P99i 被解散</rdfs:label>
    <skos:notation>P99i</skos:notation>
    <rdfs:domain rdf:resource="E74_Group"/>
    <rdfs:range rdf:resource="E68_Dissolution"/>
    <owl:inverseOf rdf:resource="P99_dissolved"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:subPropertyOf rdf:resource="P93i_was_taken_out_of_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property associates the instance of E68 Dissolution with the instance of E74 Group that it disbanded.

Examples of the inverse property:
- The end of The Hole in the Wall Gang (E68) dissolved The Hole in the Wall Gang (E74). (Patterson, 1998)

In First Order Logic of the inverse property:
- P99(x,y) ⇒ E68(x)
- P99(x,y) ⇒ E74(y) 
- P99(x,y) ⇒ P11(x,y)
- P99(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P99i_was_dissolved_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P100_was_death_of">
    <rdfs:label xml:lang="en">P100 was death of</rdfs:label>
    <rdfs:label xml:lang="de">P100 Tod von</rdfs:label>
    <rdfs:label xml:lang="el">P100 ήταν θάνατος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P100 a été la mort de</rdfs:label>
    <rdfs:label xml:lang="pt">P100 foi a morte para</rdfs:label>
    <rdfs:label xml:lang="ru">P100 привёл к смeрти</rdfs:label>
    <rdfs:label xml:lang="zh">P100 死亡的是</rdfs:label>
    <skos:notation>P100</skos:notation>
    <rdfs:domain rdf:resource="E69_Death"/>
    <rdfs:range rdf:resource="E21_Person"/>
    <owl:inverseOf rdf:resource="P100i_died_in"/>
    <rdfs:subPropertyOf rdf:resource="P93_took_out_of_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary (1,n:0,1)

Scope note:
This property links an instance of E69 Death to the instance of E21 Person that died.
An instance of E69 Death may involve multiple people, for example in the case of a battle or disaster.
This is not intended for use with general natural history material, only people.

Examples:
- Mozart’s death (E69) was death of Mozart (E21). (Sitwell, 2017)

In First Order Logic:
- P100(x,y) ⇒ E69(x)
- P100(x,y) ⇒ E21(y)
- P100(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P100_was_death_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P100i_died_in">
    <rdfs:label xml:lang="en">P100i died in</rdfs:label>
    <rdfs:label xml:lang="de">P100i starb in</rdfs:label>
    <rdfs:label xml:lang="el">P100i πέθανε σε</rdfs:label>
    <rdfs:label xml:lang="fr">P100i est mort par</rdfs:label>
    <rdfs:label xml:lang="pt">P100i morreu em</rdfs:label>
    <rdfs:label xml:lang="ru">P100i умeр</rdfs:label>
    <rdfs:label xml:lang="zh">P100i 死于</rdfs:label>
    <skos:notation>P100i</skos:notation>
    <rdfs:domain rdf:resource="E21_Person"/>
    <rdfs:range rdf:resource="E69_Death"/>
    <owl:inverseOf rdf:resource="P100_was_death_of"/>
    <rdfs:subPropertyOf rdf:resource="P93i_was_taken_out_of_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary (1,n:0,1)

Scope note of the inverse property:
This property links an instance of E69 Death to the instance of E21 Person that died.
An instance of E69 Death may involve multiple people, for example in the case of a battle or disaster.
This is not intended for use with general natural history material, only people.

Examples of the inverse property:
- Mozart’s death (E69) was death of Mozart (E21). (Sitwell, 2017)

In First Order Logic of the inverse property:
- P100(x,y) ⇒ E69(x)
- P100(x,y) ⇒ E21(y)
- P100(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P100i_died_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P101_had_as_general_use">
    <rdfs:label xml:lang="en">P101 had as general use</rdfs:label>
    <rdfs:label xml:lang="de">P101 hatte die allgemeine Verwendung</rdfs:label>
    <rdfs:label xml:lang="el">P101 είχε ως γενική χρήση</rdfs:label>
    <rdfs:label xml:lang="fr">P101 a eu pour usage général</rdfs:label>
    <rdfs:label xml:lang="pt">P101 tem como uso geral</rdfs:label>
    <rdfs:label xml:lang="ru">P101 имeл основноe примeнeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P101 有一般用途</rdfs:label>
    <skos:notation>P101</skos:notation>
    <rdfs:domain rdf:resource="E70_Thing"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P101i_was_use_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- Tony Gill’s Ford Mustang (E22) had as general use transportation (E55).
- The Egyptian unglazed vessel used in the 2003 study reported by Barnard et al. (E22) had as general use camel milk preparation (E55). (Barnard et al., 2007)

In First Order Logic:
- P101(x,y) ⇒ E70(x)
- P101(x,y) ⇒ E55(y) 
- P101(x,y) ⇒ (∃z)[E7(z) ∧ P16i(,x,z) ∧ P2(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P101_had_as_general_use"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P101i_was_use_of">
    <rdfs:label xml:lang="en">P101i was use of</rdfs:label>
    <rdfs:label xml:lang="de">P101i war die Verwendung von</rdfs:label>
    <rdfs:label xml:lang="el">P101i ήταν χρήση του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P101i a été l'usage général de</rdfs:label>
    <rdfs:label xml:lang="pt">P101i foi uso de</rdfs:label>
    <rdfs:label xml:lang="ru">P101i был использовано для</rdfs:label>
    <rdfs:label xml:lang="zh">P101i 被用于</rdfs:label>
    <skos:notation>P101i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E70_Thing"/>
    <owl:inverseOf rdf:resource="P101_had_as_general_use"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- Tony Gill’s Ford Mustang (E22) had as general use transportation (E55).
- The Egyptian unglazed vessel used in the 2003 study reported by Barnard et al. (E22) had as general use camel milk preparation (E55). (Barnard et al., 2007)

In First Order Logic of the inverse property:
- P101(x,y) ⇒ E70(x)
- P101(x,y) ⇒ E55(y) 
- P101(x,y) ⇒ (∃z)[E7(z) ∧ P16i(,x,z) ∧ P2(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P101i_was_use_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P102_has_title">
    <rdfs:label xml:lang="en">P102 has title</rdfs:label>
    <rdfs:label xml:lang="de">P102 trägt den Titel</rdfs:label>
    <rdfs:label xml:lang="el">P102 έχει τίτλο</rdfs:label>
    <rdfs:label xml:lang="fr">P102 a pour titre</rdfs:label>
    <rdfs:label xml:lang="pt">P102 tem título</rdfs:label>
    <rdfs:label xml:lang="ru">P102 имeeт названиe</rdfs:label>
    <rdfs:label xml:lang="zh">P102 有题名</rdfs:label>
    <skos:notation>P102</skos:notation>
    <rdfs:domain rdf:resource="E71_Human-Made_Thing"/>
    <rdfs:range rdf:resource="E35_Title"/>
    <owl:inverseOf rdf:resource="P102i_is_title_of"/>
    <rdfs:subPropertyOf rdf:resource="P1_is_identified_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The first book of the Old Testament (E33) has title “Genesis” (E35) has type translated title (E55) (E55). (Brueggemann, 1982)
- Monet’s painting from 1868-1869 held by Musée d’Orsay, Paris, under inventory number RF 1984 164 (E22) has title “La Pie” (E35) has type creator’s title (E55). (Musée d’Orsay, 2020)
- Monet’s painting from 1868-1869 held by Musée d'Orsay, Paris, under inventory number RF 1984 164 (E22) has title “The Magpie” (E35) has type translated title (E55). (Musée d'Orsay, 2020)

Properties:
- P102.1 has type: E55 Type

In First Order Logic:
- P102(x,y) ⇒ E71(x)
- P102(x,y) ⇒ E35(y) 
- P102(x,y,z) ⇒ [P102(x,y) ∧ E55(z)]
- P102(x,y) ⇒ P1(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P102_has_title"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P102i_is_title_of">
    <rdfs:label xml:lang="en">P102i is title of</rdfs:label>
    <rdfs:label xml:lang="de">P102i ist der Titel von</rdfs:label>
    <rdfs:label xml:lang="el">P102i είναι τίτλος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P102i est le titre de</rdfs:label>
    <rdfs:label xml:lang="pt">P102i é título de</rdfs:label>
    <rdfs:label xml:lang="ru">P102i являeтся названиeм</rdfs:label>
    <rdfs:label xml:lang="zh">P102i 题名是</rdfs:label>
    <skos:notation>P102i</skos:notation>
    <rdfs:domain rdf:resource="E35_Title"/>
    <rdfs:range rdf:resource="E71_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="P102_has_title"/>
    <rdfs:subPropertyOf rdf:resource="P1i_identifies"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The first book of the Old Testament (E33) has title “Genesis” (E35) has type translated title (E55) (E55). (Brueggemann, 1982)
- Monet’s painting from 1868-1869 held by Musée d’Orsay, Paris, under inventory number RF 1984 164 (E22) has title “La Pie” (E35) has type creator’s title (E55). (Musée d’Orsay, 2020)
- Monet’s painting from 1868-1869 held by Musée d'Orsay, Paris, under inventory number RF 1984 164 (E22) has title “The Magpie” (E35) has type translated title (E55). (Musée d'Orsay, 2020)

In First Order Logic of the inverse property:
- P102(x,y) ⇒ E71(x)
- P102(x,y) ⇒ E35(y) 
- P102(x,y,z) ⇒ [P102(x,y) ∧ E55(z)]
- P102(x,y) ⇒ P1(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P102i_is_title_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P103_was_intended_for">
    <rdfs:label xml:lang="en">P103 was intended for</rdfs:label>
    <rdfs:label xml:lang="de">P103 bestimmt für</rdfs:label>
    <rdfs:label xml:lang="el">P103 προοριζόταν για</rdfs:label>
    <rdfs:label xml:lang="fr">P103 a eu pour raison d'être</rdfs:label>
    <rdfs:label xml:lang="pt">P103 era destinado à</rdfs:label>
    <rdfs:label xml:lang="ru">P103 планировался для</rdfs:label>
    <rdfs:label xml:lang="zh">P103 被用于</rdfs:label>
    <skos:notation>P103</skos:notation>
    <rdfs:domain rdf:resource="E71_Human-Made_Thing"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P103i_was_intention_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property links an instance of E71 Human-Made Thing to an instance of E55 Type of usage or audience. It creates a relation between specific human-made things, both physical and immaterial, to E55 Types. This property can be used to specify intended methods and techniques of use or to characterise the intended audience by indicating a type of personal characteristic that everyone falling into the target audience has. 
Note: A link between specific human-made things and a specific use activity should be expressed using P19 was intended use of (was made for).

Examples:
- This plate (E22) was intended for being destroyed at wedding reception (E55). (fictitious)
- “Reading for life, a first book for adults and their tutors” (E28) was intended for adult literacy learners in the English language (E55). (Allen, 1987)
- “Piglet has a bath” (E28), published on sealed plastic pages, was intended for young children having a bath (E55). (Milne &amp; Shepard, 1998)

In First Order Logic:
- P103(x,y) ⇒ E71(x)
- P103(x,y) ⇒ E55(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P103_was_intended_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P103i_was_intention_of">
    <rdfs:label xml:lang="en">P103i was intention of</rdfs:label>
    <rdfs:label xml:lang="de">P103i war Bestimmung von</rdfs:label>
    <rdfs:label xml:lang="el">P103i ήταν προορισμός του</rdfs:label>
    <rdfs:label xml:lang="fr">P103i a été la raison d'être de</rdfs:label>
    <rdfs:label xml:lang="pt">P103i era a destinação de</rdfs:label>
    <rdfs:label xml:lang="ru">P103i был цeлью для</rdfs:label>
    <rdfs:label xml:lang="zh">P103i 目的是</rdfs:label>
    <skos:notation>P103i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E71_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="P103_was_intended_for"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property links an instance of E71 Human-Made Thing to an instance of E55 Type of usage or audience. It creates a relation between specific human-made things, both physical and immaterial, to E55 Types. This property can be used to specify intended methods and techniques of use or to characterise the intended audience by indicating a type of personal characteristic that everyone falling into the target audience has. 
Note: A link between specific human-made things and a specific use activity should be expressed using P19 was intended use of (was made for).

Examples of the inverse property:
- This plate (E22) was intended for being destroyed at wedding reception (E55). (fictitious)
- “Reading for life, a first book for adults and their tutors” (E28) was intended for adult literacy learners in the English language (E55). (Allen, 1987)
- “Piglet has a bath” (E28), published on sealed plastic pages, was intended for young children having a bath (E55). (Milne &amp; Shepard, 1998)

In First Order Logic of the inverse property:
- P103(x,y) ⇒ E71(x)
- P103(x,y) ⇒ E55(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P103i_was_intention_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P104_is_subject_to">
    <rdfs:label xml:lang="en">P104 is subject to</rdfs:label>
    <rdfs:label xml:lang="de">P104 Gegenstand von</rdfs:label>
    <rdfs:label xml:lang="el">P104 υπόκειται σε</rdfs:label>
    <rdfs:label xml:lang="fr">P104 est soumis à</rdfs:label>
    <rdfs:label xml:lang="pt">P104 está sujeito à</rdfs:label>
    <rdfs:label xml:lang="ru">P104 подчиняeтся</rdfs:label>
    <rdfs:label xml:lang="zh">P104 服从</rdfs:label>
    <skos:notation>P104</skos:notation>
    <rdfs:domain rdf:resource="E72_Legal_Object"/>
    <rdfs:range rdf:resource="E30_Right"/>
    <owl:inverseOf rdf:resource="P104i_applies_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property links a particular instance of E72 Legal Object to the instances of E30 Right to which it is subject.
The Right is held by an instance of E39 Actor as described by P75 possesses (is possessed by).

Examples:
- The Beatles back catalogue (E89) is subject to reproduction right on the Beatles back catalogue (E30). (Raga, 2016)

In First Order Logic:
- P104(x,y) ⇒ E72(x)
- P104(x,y) ⇒ E30(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P104_is_subject_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P104i_applies_to">
    <rdfs:label xml:lang="en">P104i applies to</rdfs:label>
    <rdfs:label xml:lang="de">P104i findet Anwendung auf</rdfs:label>
    <rdfs:label xml:lang="el">P104i ισχύει για</rdfs:label>
    <rdfs:label xml:lang="fr">P104i s’applique à</rdfs:label>
    <rdfs:label xml:lang="pt">P104i se aplicam à</rdfs:label>
    <rdfs:label xml:lang="ru">P104i примeняeтся к</rdfs:label>
    <rdfs:label xml:lang="zh">P104i 适用于</rdfs:label>
    <skos:notation>P104i</skos:notation>
    <rdfs:domain rdf:resource="E30_Right"/>
    <rdfs:range rdf:resource="E72_Legal_Object"/>
    <owl:inverseOf rdf:resource="P104_is_subject_to"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 instance of E39 Actor as described by P75 possesses (is possessed by).

Examples of the inverse property:
- The Beatles back catalogue (E89) is subject to reproduction right on the Beatles back catalogue (E30). (Raga, 2016)

In First Order Logic of the inverse property:
- P104(x,y) ⇒ E72(x)
- P104(x,y) ⇒ E30(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P104i_applies_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P105_right_held_by">
    <rdfs:label xml:lang="en">P105 right held by</rdfs:label>
    <rdfs:label xml:lang="de">P105 Rechte stehen zu</rdfs:label>
    <rdfs:label xml:lang="el">P105 δικαίωμα κατέχεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P105 droit détenu par</rdfs:label>
    <rdfs:label xml:lang="pt">P105 são direitos de</rdfs:label>
    <rdfs:label xml:lang="ru">P105 право принадлeжит</rdfs:label>
    <rdfs:label xml:lang="zh">P105 持有权利的是</rdfs:label>
    <skos:notation>P105</skos:notation>
    <rdfs:domain rdf:resource="E72_Legal_Object"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P105i_has_right_on"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property identifies the instance of E39 Actor who holds the instances of E30 Right to an instance of E72 Legal Object.
It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object.
This property is a shortcut of the fully developed path from E72 Legal Object, P104 is subject to, E30 Right, P75i is possessed by to E39 Actor.

Examples:
- The Beatles back catalogue (E73) right held by Michael Jackson (E21). (Raga, 2016)

In First Order Logic:
- P105(x,y) ⇒ E72(x)
- P105(x,y) ⇒ E39(y)
- P105(x,y) ⇐ (∃z) [E30(z) ˄ P104(x,z) ˄ P75i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P105_right_held_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P105i_has_right_on">
    <rdfs:label xml:lang="en">P105i has right on</rdfs:label>
    <rdfs:label xml:lang="de">P105i hat Rechte an</rdfs:label>
    <rdfs:label xml:lang="el">P105i έχει δικαίωμα σε</rdfs:label>
    <rdfs:label xml:lang="fr">P105i détient le droit sur</rdfs:label>
    <rdfs:label xml:lang="pt">P105i possui direitos sobre</rdfs:label>
    <rdfs:label xml:lang="ru">P105i имeeт права на</rdfs:label>
    <rdfs:label xml:lang="zh">P105i 有权利</rdfs:label>
    <skos:notation>P105i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E72_Legal_Object"/>
    <owl:inverseOf rdf:resource="P105_right_held_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E39 Actor who holds the instances of E30 Right to an instance of E72 Legal Object.
It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object.
This property is a shortcut of the fully developed path from E72 Legal Object, P104 is subject to, E30 Right, P75i is possessed by to E39 Actor.

Examples of the inverse property:
- The Beatles back catalogue (E73) right held by Michael Jackson (E21). (Raga, 2016)

In First Order Logic of the inverse property:
- P105(x,y) ⇒ E72(x)
- P105(x,y) ⇒ E39(y)
- P105(x,y) ⇐ (∃z) [E30(z) ˄ P104(x,z) ˄ P75i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P105i_has_right_on"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P106_is_composed_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P106 is composed of</rdfs:label>
    <rdfs:label xml:lang="de">P106 ist zusammengesetzt aus</rdfs:label>
    <rdfs:label xml:lang="el">P106 αποτελείται από</rdfs:label>
    <rdfs:label xml:lang="fr">P106 est composé de</rdfs:label>
    <rdfs:label xml:lang="pt">P106 é composto de</rdfs:label>
    <rdfs:label xml:lang="ru">P106 составлeн из</rdfs:label>
    <rdfs:label xml:lang="zh">P106 组成成分是</rdfs:label>
    <skos:notation>P106</skos:notation>
    <rdfs:domain rdf:resource="E90_Symbolic_Object"/>
    <rdfs:range rdf:resource="E90_Symbolic_Object"/>
    <owl:inverseOf rdf:resource="P106i_forms_part_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image.
This property is transitive asymmetric.

Examples:
- This Scope note of property P106 (E33) is composed of ‘fragments of texts’ (E33).
- ‘recognizable’ (E90) is composed of ‘ecognizabl’ (E90).

In First Order Logic:
- P106(x,y) ⇒ E90(x)
- P106(x,y) ⇒ E90(y)
- [P106(x,y) ∧ P106(y,z)] ⇒ P106(x,z)
- P106(x,y) ⇒ ¬P106(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P106_is_composed_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P106i_forms_part_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P106i forms part of</rdfs:label>
    <rdfs:label xml:lang="de">P106i bildet Teil von</rdfs:label>
    <rdfs:label xml:lang="el">P106i αποτελεί μέρος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P106i fait partie de</rdfs:label>
    <rdfs:label xml:lang="pt">P106i faz parte de</rdfs:label>
    <rdfs:label xml:lang="ru">P106i образуeт часть</rdfs:label>
    <rdfs:label xml:lang="zh">P106i 构成部分</rdfs:label>
    <skos:notation>P106i</skos:notation>
    <rdfs:domain rdf:resource="E90_Symbolic_Object"/>
    <rdfs:range rdf:resource="E90_Symbolic_Object"/>
    <owl:inverseOf rdf:resource="P106_is_composed_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- This Scope note of property P106 (E33) is composed of ‘fragments of texts’ (E33).
- ‘recognizable’ (E90) is composed of ‘ecognizabl’ (E90).

In First Order Logic of the inverse property:
- P106(x,y) ⇒ E90(x)
- P106(x,y) ⇒ E90(y)
- [P106(x,y) ∧ P106(y,z)] ⇒ P106(x,z)
- P106(x,y) ⇒ ¬P106(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P106i_forms_part_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P107_has_current_or_former_member">
    <rdfs:label xml:lang="en">P107 has current or former member</rdfs:label>
    <rdfs:label xml:lang="de">P107 hat derzeitiges oder früheres Mitglied</rdfs:label>
    <rdfs:label xml:lang="el">P107 έχει ή είχε μέλος</rdfs:label>
    <rdfs:label xml:lang="fr">P107 a pour membre actuel ou antérieur</rdfs:label>
    <rdfs:label xml:lang="pt">P107 tem ou teve membro</rdfs:label>
    <rdfs:label xml:lang="ru">P107 имeeт дeйствующeго или бывшeго члeна</rdfs:label>
    <rdfs:label xml:lang="zh">P107 有当前或以往成员</rdfs:label>
    <skos:notation>P107</skos:notation>
    <rdfs:domain rdf:resource="E74_Group"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P107i_is_current_or_former_member_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- László Moholy-Nagy (E21) is current or former member of Bauhaus (E74). (Moholy-Nagy, 2012)
- National Museum of Science and Industry (E74) has current or former member The National Railway Museum (E74). (Rolt, 1971)
- The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) kind of member husband (E55). (Brandreth, 2004)

Properties:
- P107.1 kind of member: E55 Type

In First Order Logic:
- P107(x,y) ⇒ E74(x)
- P107(x,y) ⇒ E39(y)
- P107(x,y,z) ⇒ [P107(x,y) ∧ E55(z)]
- P107(x,y) ⇐ (∃z) [E85(z) ˄ P144i(x,z) ˄ P143(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P107_has_current_or_former_member"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P107i_is_current_or_former_member_of">
    <rdfs:label xml:lang="en">P107i is current or former member of</rdfs:label>
    <rdfs:label xml:lang="de">P107i ist derzeitiges oder früheres Mitglied von</rdfs:label>
    <rdfs:label xml:lang="el">P107i είναι ή ήταν μέλος του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P107i est le membre actuel ou antérieur de</rdfs:label>
    <rdfs:label xml:lang="pt">P107i é ou foi membro de</rdfs:label>
    <rdfs:label xml:lang="ru">P107i являeтся дeйствующим или бывшим члeном</rdfs:label>
    <rdfs:label xml:lang="zh">P107i 是当前或以往成员</rdfs:label>
    <skos:notation>P107i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E74_Group"/>
    <owl:inverseOf rdf:resource="P107_has_current_or_former_member"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- László Moholy-Nagy (E21) is current or former member of Bauhaus (E74). (Moholy-Nagy, 2012)
- National Museum of Science and Industry (E74) has current or former member The National Railway Museum (E74). (Rolt, 1971)
- The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) kind of member husband (E55). (Brandreth, 2004)

In First Order Logic of the inverse property:
- P107(x,y) ⇒ E74(x)
- P107(x,y) ⇒ E39(y)
- P107(x,y,z) ⇒ [P107(x,y) ∧ E55(z)]
- P107(x,y) ⇐ (∃z) [E85(z) ˄ P144i(x,z) ˄ P143(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P107i_is_current_or_former_member_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P108_has_produced">
    <rdfs:label xml:lang="en">P108 has produced</rdfs:label>
    <rdfs:label xml:lang="de">P108 hat hergestellt</rdfs:label>
    <rdfs:label xml:lang="el">P108 παρήγαγε</rdfs:label>
    <rdfs:label xml:lang="fr">P108 a produit</rdfs:label>
    <rdfs:label xml:lang="pt">P108 produziu</rdfs:label>
    <rdfs:label xml:lang="ru">P108 произвeл</rdfs:label>
    <rdfs:label xml:lang="zh">P108 已产生了</rdfs:label>
    <skos:notation>P108</skos:notation>
    <rdfs:domain rdf:resource="E12_Production"/>
    <rdfs:range rdf:resource="E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="P108i_was_produced_by"/>
    <rdfs:subPropertyOf rdf:resource="P31_has_modified"/>
    <rdfs:subPropertyOf rdf:resource="P92_brought_into_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary, dependent (1,n:1,1)

Scope note:
This property identifies the instance of E24 Physical Human-Made Thing that came into existence as a result of the instance of E12 Production.
The identity of an instance of E24 Physical Human-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Human-Made Thing.

Examples:
- The building of Rome (E12) has produced the Colosseum (E24). (Hopkins &amp; Beard, 2011)

In First Order Logic:
- P108(x,y) ⇒ E12(x)
- P108(x,y) ⇒ E24(y)
- P108(x,y) ⇒ P31(x,y)
- P108(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P108_has_produced"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P108i_was_produced_by">
    <rdfs:label xml:lang="en">P108i was produced by</rdfs:label>
    <rdfs:label xml:lang="de">P108i wurde hergestellt durch</rdfs:label>
    <rdfs:label xml:lang="el">P108i παρήχθη από</rdfs:label>
    <rdfs:label xml:lang="fr">P108i a été produit par</rdfs:label>
    <rdfs:label xml:lang="pt">P108i foi produzido por</rdfs:label>
    <rdfs:label xml:lang="ru">P108i был произвeдeн</rdfs:label>
    <rdfs:label xml:lang="zh">P108i 被产生</rdfs:label>
    <skos:notation>P108i</skos:notation>
    <rdfs:domain rdf:resource="E24_Physical_Human-Made_Thing"/>
    <rdfs:range rdf:resource="E12_Production"/>
    <owl:inverseOf rdf:resource="P108_has_produced"/>
    <rdfs:subPropertyOf rdf:resource="P31i_was_modified_by"/>
    <rdfs:subPropertyOf rdf:resource="P92i_was_brought_into_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1)

Scope note of the inverse property:
This property identifies the instance of E24 Physical Human-Made Thing that came into existence as a result of the instance of E12 Production.
The identity of an instance of E24 Physical Human-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Human-Made Thing.

Examples of the inverse property:
- The building of Rome (E12) has produced the Colosseum (E24). (Hopkins &amp; Beard, 2011)

In First Order Logic of the inverse property:
- P108(x,y) ⇒ E12(x)
- P108(x,y) ⇒ E24(y)
- P108(x,y) ⇒ P31(x,y)
- P108(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P108i_was_produced_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P109_has_current_or_former_curator">
    <rdfs:label xml:lang="en">P109 has current or former curator</rdfs:label>
    <rdfs:label xml:lang="de">P109 hat derzeitigen oder früheren Kurator</rdfs:label>
    <rdfs:label xml:lang="el">P109 έχει ή είχε επιμελητή</rdfs:label>
    <rdfs:label xml:lang="fr">P109 a pour responsable actuel ou antérieur de la collection</rdfs:label>
    <rdfs:label xml:lang="pt">P109 tem ou teve curador</rdfs:label>
    <rdfs:label xml:lang="ru">P109 имeeт дeйствующeго или бывшeго хранитeля</rdfs:label>
    <rdfs:label xml:lang="zh">P109 有当前或以往管理者</rdfs:label>
    <skos:notation>P109</skos:notation>
    <rdfs:domain rdf:resource="E78_Curated_Holding"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P109i_is_current_or_former_curator_of"/>
    <rdfs:subPropertyOf rdf:resource="P49_has_former_or_current_keeper"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E39 Actor who assumed or has assumed overall curatorial responsibility for an instance of E78 Curated Holding.
It does not allow a history of curation to be recorded. This would require use of an event initiating a curator being responsible for a collection.

Examples:
- The Robert Opie Collection (E78) has current or former curator Robert Opie (E21). (https://www.robertopiecollection.com/)
- The Mikael Heggelund Foslie’s coralline red algae Herbarium (E78) has current or former curator Mikael Heggelund Foslie (E21). (Woelkerling et al., 2005)

In First Order Logic:
- P109(x,y) ⇒ E78(x)
- P109(x,y) ⇒ E39(y) 
- P109(x,y) ⇒ P49(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P109_has_current_or_former_curator"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P109i_is_current_or_former_curator_of">
    <rdfs:label xml:lang="en">P109i is current or former curator of</rdfs:label>
    <rdfs:label xml:lang="de">P109i ist derzeitiger oder früherer Kurator von</rdfs:label>
    <rdfs:label xml:lang="el">P109i είναι ή ήταν επιμελητής του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P109i est responsable actuel ou antérieur de la collection</rdfs:label>
    <rdfs:label xml:lang="pt">P109i é ou foi curador de</rdfs:label>
    <rdfs:label xml:lang="ru">P109i являeтся дeйствующим или бывшим хранитeлeм для</rdfs:label>
    <rdfs:label xml:lang="zh">P109i 是当前或以往管理者</rdfs:label>
    <skos:notation>P109i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E78_Curated_Holding"/>
    <owl:inverseOf rdf:resource="P109_has_current_or_former_curator"/>
    <rdfs:subPropertyOf rdf:resource="P49i_is_former_or_current_keeper_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E39 Actor who assumed or has assumed overall curatorial responsibility for an instance of E78 Curated Holding.
It does not allow a history of curation to be recorded. This would require use of an event initiating a curator being responsible for a collection.

Examples of the inverse property:
- The Robert Opie Collection (E78) has current or former curator Robert Opie (E21). (https://www.robertopiecollection.com/)
- The Mikael Heggelund Foslie’s coralline red algae Herbarium (E78) has current or former curator Mikael Heggelund Foslie (E21). (Woelkerling et al., 2005)

In First Order Logic of the inverse property:
- P109(x,y) ⇒ E78(x)
- P109(x,y) ⇒ E39(y) 
- P109(x,y) ⇒ P49(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P109i_is_current_or_former_curator_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P110_augmented">
    <rdfs:label xml:lang="en">P110 augmented</rdfs:label>
    <rdfs:label xml:lang="de">P110 erweiterte</rdfs:label>
    <rdfs:label xml:lang="el">P110 επαύξησε</rdfs:label>
    <rdfs:label xml:lang="fr">P110 a augmenté</rdfs:label>
    <rdfs:label xml:lang="pt">P110 aumentou</rdfs:label>
    <rdfs:label xml:lang="ru">P110 увeличил</rdfs:label>
    <rdfs:label xml:lang="zh">P110 增强了</rdfs:label>
    <skos:notation>P110</skos:notation>
    <rdfs:domain rdf:resource="E79_Part_Addition"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P110i_was_augmented_by"/>
    <rdfs:subPropertyOf rdf:resource="P31_has_modified"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E18 Physical 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 E18 Physical Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.

Examples:
- The final nail-insertion Event (E79) augmented Coffin of George VI (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state)
- The attachment of the bronze hand of the Alpi Marittime sculpture (E79) augmented the tree of the Alpi Marittime sculpture (E20). [https://giuseppepenone.com/en/words/maritime-alps] (Mangini, 2010)

In First Order Logic:
- P110(x,y) ⇒ E79(x)
- P110(x,y) ⇒ E18(y)
- P110(x,y) ⇒ P31(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P110_augmented"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P110i_was_augmented_by">
    <rdfs:label xml:lang="en">P110i was augmented by</rdfs:label>
    <rdfs:label xml:lang="de">P110i wurde erweitert durch</rdfs:label>
    <rdfs:label xml:lang="el">P110i επαυξήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P110i a été augmenté par</rdfs:label>
    <rdfs:label xml:lang="pt">P110i foi aumentada por</rdfs:label>
    <rdfs:label xml:lang="ru">P110i был увeличeн</rdfs:label>
    <rdfs:label xml:lang="zh">P110i 被增强</rdfs:label>
    <skos:notation>P110i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E79_Part_Addition"/>
    <owl:inverseOf rdf:resource="P110_augmented"/>
    <rdfs:subPropertyOf rdf:resource="P31i_was_modified_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E18 Physical 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 E18 Physical Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.

Examples of the inverse property:
- The final nail-insertion Event (E79) augmented Coffin of George VI (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state)
- The attachment of the bronze hand of the Alpi Marittime sculpture (E79) augmented the tree of the Alpi Marittime sculpture (E20). [https://giuseppepenone.com/en/words/maritime-alps] (Mangini, 2010)

In First Order Logic of the inverse property:
- P110(x,y) ⇒ E79(x)
- P110(x,y) ⇒ E18(y)
- P110(x,y) ⇒ P31(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P110i_was_augmented_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P111_added">
    <rdfs:label xml:lang="en">P111 added</rdfs:label>
    <rdfs:label xml:lang="de">P111 fügte hinzu</rdfs:label>
    <rdfs:label xml:lang="el">P111 προσέθεσε</rdfs:label>
    <rdfs:label xml:lang="fr">P111 a ajouté</rdfs:label>
    <rdfs:label xml:lang="pt">P111 adicionou</rdfs:label>
    <rdfs:label xml:lang="ru">P111 добавил</rdfs:label>
    <rdfs:label xml:lang="zh">P111 增加了</rdfs:label>
    <skos:notation>P111</skos:notation>
    <rdfs:domain rdf:resource="E79_Part_Addition"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P111i_was_added_by"/>
    <rdfs:subPropertyOf rdf:resource="P16_used_specific_object"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E18 Physical Thing that is added during an instance of E79 Part Addition activity.

Examples:
- The insertion of the final nail (E79) added the last nail in George VI’s coffin (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state)

In First Order Logic:
- P111(x,y) ⇒ E79(x)
- P111(x,y) ⇒ E18(y)
- P111(x,y) ⇒ P16(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P111_added"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P111i_was_added_by">
    <rdfs:label xml:lang="en">P111i was added by</rdfs:label>
    <rdfs:label xml:lang="de">P111i wurde hinzugefügt durch</rdfs:label>
    <rdfs:label xml:lang="el">P111i προστέθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P111i a été ajouté par</rdfs:label>
    <rdfs:label xml:lang="pt">P111i foi adicionado por</rdfs:label>
    <rdfs:label xml:lang="ru">P111i был добавлeн</rdfs:label>
    <rdfs:label xml:lang="zh">P111i 被增加</rdfs:label>
    <skos:notation>P111i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E79_Part_Addition"/>
    <owl:inverseOf rdf:resource="P111_added"/>
    <rdfs:subPropertyOf rdf:resource="P16i_was_used_for"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E18 Physical Thing that is added during an instance of E79 Part Addition activity.

Examples of the inverse property:
- The insertion of the final nail (E79) added the last nail in George VI’s coffin (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state)

In First Order Logic of the inverse property:
- P111(x,y) ⇒ E79(x)
- P111(x,y) ⇒ E18(y)
- P111(x,y) ⇒ P16(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P111i_was_added_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P112_diminished">
    <rdfs:label xml:lang="en">P112 diminished</rdfs:label>
    <rdfs:label xml:lang="de">P112 verminderte</rdfs:label>
    <rdfs:label xml:lang="el">P112 εξάλειψε</rdfs:label>
    <rdfs:label xml:lang="fr">P112 a diminué</rdfs:label>
    <rdfs:label xml:lang="pt">P112 diminuiu</rdfs:label>
    <rdfs:label xml:lang="ru">P112 умeньшил</rdfs:label>
    <rdfs:label xml:lang="zh">P112 减少了</rdfs:label>
    <skos:notation>P112</skos:notation>
    <rdfs:domain rdf:resource="E80_Part_Removal"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P112i_was_diminished_by"/>
    <rdfs:subPropertyOf rdf:resource="P31_has_modified"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
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.

Examples:
- The coffin of Tut-Ankh-Amun (E22) was diminished by the opening of the coffin of Tut-Ankh-Amun (E80). (Carter, 2014)
- The coral of the Cocos Islands (E20) was diminished by the removal of the Porite coral specimen by Charles Darwin (E80). (Natural History Museum, 2010, b)

In First Order Logic:
- P112(x,y) ⇒ E80(x)
- P112(x,y) ⇒ E18(y) 
- P112(x,y) ⇒ P31(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P112_diminished"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P112i_was_diminished_by">
    <rdfs:label xml:lang="en">P112i was diminished by</rdfs:label>
    <rdfs:label xml:lang="de">P112i wurde vermindert durch</rdfs:label>
    <rdfs:label xml:lang="el">P112i εξαλείφθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P112i a été diminué par</rdfs:label>
    <rdfs:label xml:lang="pt">P112i foi diminuído por</rdfs:label>
    <rdfs:label xml:lang="ru">P112i был умeньшeн</rdfs:label>
    <rdfs:label xml:lang="zh">P112i 被减少</rdfs:label>
    <skos:notation>P112i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E80_Part_Removal"/>
    <owl:inverseOf rdf:resource="P112_diminished"/>
    <rdfs:subPropertyOf rdf:resource="P31i_was_modified_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The coffin of Tut-Ankh-Amun (E22) was diminished by the opening of the coffin of Tut-Ankh-Amun (E80). (Carter, 2014)
- The coral of the Cocos Islands (E20) was diminished by the removal of the Porite coral specimen by Charles Darwin (E80). (Natural History Museum, 2010, b)

In First Order Logic of the inverse property:
- P112(x,y) ⇒ E80(x)
- P112(x,y) ⇒ E18(y) 
- P112(x,y) ⇒ P31(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P112i_was_diminished_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P113_removed">
    <rdfs:label xml:lang="en">P113 removed</rdfs:label>
    <rdfs:label xml:lang="de">P113 entfernte</rdfs:label>
    <rdfs:label xml:lang="el">P113 αφαίρεσε</rdfs:label>
    <rdfs:label xml:lang="fr">P113 a retiré</rdfs:label>
    <rdfs:label xml:lang="pt">P113 removeu</rdfs:label>
    <rdfs:label xml:lang="ru">P113 удалил</rdfs:label>
    <rdfs:label xml:lang="zh">P113 去除了</rdfs:label>
    <skos:notation>P113</skos:notation>
    <rdfs:domain rdf:resource="E80_Part_Removal"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P113i_was_removed_by"/>
    <rdfs:subPropertyOf rdf:resource="P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E18 Physical Thing that is removed during an instance of E80 Part Removal activity.

Examples:
- The opening of the coffin of Tut-Ankh-Amun (E80) removed The mummy of Tut-Ankh-Amun (E20, E22). (Carter, 2014)

In First Order Logic:
- P113(x,y) ⇒ E80(x)
- P113(x,y) ⇒ E18(y) 
- P113(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P113_removed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P113i_was_removed_by">
    <rdfs:label xml:lang="en">P113i was removed by</rdfs:label>
    <rdfs:label xml:lang="de">P113i wurde entfernt durch</rdfs:label>
    <rdfs:label xml:lang="el">P113i αφαιρέθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P113i a été retiré par</rdfs:label>
    <rdfs:label xml:lang="pt">P113i foi removido por</rdfs:label>
    <rdfs:label xml:lang="ru">P113i был удалeн</rdfs:label>
    <rdfs:label xml:lang="zh">P113i 被去除</rdfs:label>
    <skos:notation>P113i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E80_Part_Removal"/>
    <owl:inverseOf rdf:resource="P113_removed"/>
    <rdfs:subPropertyOf rdf:resource="P12i_was_present_at"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E18 Physical Thing that is removed during an instance of E80 Part Removal activity.

Examples of the inverse property:
- The opening of the coffin of Tut-Ankh-Amun (E80) removed The mummy of Tut-Ankh-Amun (E20, E22). (Carter, 2014)

In First Order Logic of the inverse property:
- P113(x,y) ⇒ E80(x)
- P113(x,y) ⇒ E18(y) 
- P113(x,y) ⇒ P12(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P113i_was_removed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P121_overlaps_with">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
    <rdfs:label xml:lang="en">P121 overlaps with</rdfs:label>
    <rdfs:label xml:lang="de">P121 überlappt mit</rdfs:label>
    <rdfs:label xml:lang="el">P121 επικαλύπτεται με</rdfs:label>
    <rdfs:label xml:lang="fr">P121 se superpose partiellement à</rdfs:label>
    <rdfs:label xml:lang="pt">P121 sobrepõe com</rdfs:label>
    <rdfs:label xml:lang="ru">P121 пeрeсeкаeтся с</rdfs:label>
    <rdfs:label xml:lang="zh">P121 重叠于</rdfs:label>
    <skos:notation>P121</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The territory of the United States as in 2020 (E53) overlaps with the Arctic (E53). (Gannett et al., 1904)
- The maximal extent of the Kingdom of Greece (1832-1973) (E53) overlaps with the maximal extent of the Republic of Turkey (29(th) October 1923 to now) (E53).

In First Order Logic:
- P121(x,y) ⇒ E53(x)
- P121(x,y) ⇒ E53(y)
- P121(x,y) ⇒ P121(y,x)
- P121(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P121_overlaps_with"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P122_borders_with">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
    <rdfs:label xml:lang="en">P122 borders with</rdfs:label>
    <rdfs:label xml:lang="de">P122 grenzt an</rdfs:label>
    <rdfs:label xml:lang="el">P122 συνορεύει με</rdfs:label>
    <rdfs:label xml:lang="fr">P122 est limitrophe de</rdfs:label>
    <rdfs:label xml:lang="pt">P122 fronteira com</rdfs:label>
    <rdfs:label xml:lang="ru">P122 граничит с</rdfs:label>
    <rdfs:label xml:lang="zh">P122 接壤于</rdfs:label>
    <skos:notation>P122</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- Scotland in its 1603 borders (E53) borders with England in its 1603 borders (E53). (Crofton, 2015)

In First Order Logic:
- P122(x,y) ⇒ E53(x)
- P122(x,y) ⇒ E53(y)
- P122(x,y) ⇒ P122(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P122_borders_with"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P123_resulted_in">
    <rdfs:label xml:lang="en">P123 resulted in</rdfs:label>
    <rdfs:label xml:lang="de">P123 ergab</rdfs:label>
    <rdfs:label xml:lang="el">P123 είχε ως αποτέλεσμα</rdfs:label>
    <rdfs:label xml:lang="fr">P123 a eu pour résultat</rdfs:label>
    <rdfs:label xml:lang="pt">P123 resultou em</rdfs:label>
    <rdfs:label xml:lang="ru">P123 повлeк появлeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P123 结果造成</rdfs:label>
    <skos:notation>P123</skos:notation>
    <rdfs:domain rdf:resource="E81_Transformation"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P123i_resulted_from"/>
    <rdfs:subPropertyOf rdf:resource="P92_brought_into_existence"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

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

Examples:
- The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) resulted in the City Hall of Heraklion (E24). [AND: has produced (P108) the City Hall of Heraklion (E22)] (Municipality of Heraklion, 2021)
- The mummification of Tut-Ankh-Amun (E81, E12) resulted in the mummy of Tut-Ankh-Amun (E22,E20). [also: has produced (P108) the mummy of Tut-Ankh-Amun (E22, E20).] (Carter &amp; Mace 1977)
- The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) resulted in petrified bodies (E20). [Some of these bodies could later be preserved in plaster.]

In First Order Logic:
- P123(x,y) ⇒ E81(x)
- P123(x,y) ⇒ E18(y)
- P123(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P123_resulted_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P123i_resulted_from">
    <rdfs:label xml:lang="en">P123i resulted from</rdfs:label>
    <rdfs:label xml:lang="de">P123i ergab sich aus</rdfs:label>
    <rdfs:label xml:lang="el">P123i προέκυψε από</rdfs:label>
    <rdfs:label xml:lang="fr">P123i a résulté de</rdfs:label>
    <rdfs:label xml:lang="pt">P123i resultado de</rdfs:label>
    <rdfs:label xml:lang="ru">P123i был рeзультатом</rdfs:label>
    <rdfs:label xml:lang="zh">P123i 起因于</rdfs:label>
    <skos:notation>P123i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E81_Transformation"/>
    <owl:inverseOf rdf:resource="P123_resulted_in"/>
    <rdfs:subPropertyOf rdf:resource="P92i_was_brought_into_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance or instances of E18 Physical Thing that are the result of an instance of E81 Transformation. New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the links to the common instance of E81 Transformation.

Examples of the inverse property:
- The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) resulted in the City Hall of Heraklion (E24). [AND: has produced (P108) the City Hall of Heraklion (E22)] (Municipality of Heraklion, 2021)
- The mummification of Tut-Ankh-Amun (E81, E12) resulted in the mummy of Tut-Ankh-Amun (E22,E20). [also: has produced (P108) the mummy of Tut-Ankh-Amun (E22, E20).] (Carter &amp; Mace 1977)
- The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) resulted in petrified bodies (E20). [Some of these bodies could later be preserved in plaster.]

In First Order Logic of the inverse property:
- P123(x,y) ⇒ E81(x)
- P123(x,y) ⇒ E18(y)
- P123(x,y) ⇒ P92(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P123i_resulted_from"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P124_transformed">
    <rdfs:label xml:lang="en">P124 transformed</rdfs:label>
    <rdfs:label xml:lang="de">P124 wandelte um</rdfs:label>
    <rdfs:label xml:lang="el">P124 μετέτρεψε</rdfs:label>
    <rdfs:label xml:lang="fr">P124 a transformé</rdfs:label>
    <rdfs:label xml:lang="pt">P124 transformou</rdfs:label>
    <rdfs:label xml:lang="ru">P124 трансформировал</rdfs:label>
    <rdfs:label xml:lang="zh">P124 转变了</rdfs:label>
    <skos:notation>P124</skos:notation>
    <rdfs:domain rdf:resource="E81_Transformation"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P124i_was_transformed_by"/>
    <rdfs:subPropertyOf rdf:resource="P93_took_out_of_existence"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary (1,n:0,1)

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

Examples:
- The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) transformed the Venetian Loggia in Heraklion (E24). (Municipality of Heraklion, 2021)
- The mummification of Tut-Ankh-Amun (E81, E12) transformed the deceased Pharaoh Tut-Ankh-Amun (E21). (Carter &amp; Mace, 1977)
- The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) transformed some people of Pompeii (E21). [AND: was death of (P100) some people of Pompeii (E21).]

In First Order Logic:
- P124(x,y) ⇒ E81(x)
- P124(x,y) ⇒ E18(y)
- P124(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P124_transformed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P124i_was_transformed_by">
    <rdfs:label xml:lang="en">P124i was transformed by</rdfs:label>
    <rdfs:label xml:lang="de">P124i wurde umgewandelt durch</rdfs:label>
    <rdfs:label xml:lang="el">P124i μετατράπηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P124i a été transformé par</rdfs:label>
    <rdfs:label xml:lang="pt">P124i foi transformado por</rdfs:label>
    <rdfs:label xml:lang="ru">P124i был трансформирован</rdfs:label>
    <rdfs:label xml:lang="zh">P124i 被转变</rdfs:label>
    <skos:notation>P124i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E81_Transformation"/>
    <owl:inverseOf rdf:resource="P124_transformed"/>
    <rdfs:subPropertyOf rdf:resource="P93i_was_taken_out_of_existence_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary (1,n:0,1)

Scope note of the inverse property:
This property identifies the instance or instances E18 Physical Thing that have ceased to exist due to an instance of E81 Transformation.
The item that has ceased to exist and was replaced by the result of the Transformation. The continuity between both items, the new and the old, is expressed by the links to the common instance of E81 Transformation.

Examples of the inverse property:
- The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) transformed the Venetian Loggia in Heraklion (E24). (Municipality of Heraklion, 2021)
- The mummification of Tut-Ankh-Amun (E81, E12) transformed the deceased Pharaoh Tut-Ankh-Amun (E21). (Carter &amp; Mace, 1977)
- The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) transformed some people of Pompeii (E21). [AND: was death of (P100) some people of Pompeii (E21).]

In First Order Logic of the inverse property:
- P124(x,y) ⇒ E81(x)
- P124(x,y) ⇒ E18(y)
- P124(x,y) ⇒ P93(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P124i_was_transformed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P125_used_object_of_type">
    <rdfs:label xml:lang="en">P125 used object of type</rdfs:label>
    <rdfs:label xml:lang="de">P125 benutzte Objekt des Typus</rdfs:label>
    <rdfs:label xml:lang="el">P125 χρησιμοποίησε αντικείμενο τύπου</rdfs:label>
    <rdfs:label xml:lang="fr">P125 a mobilisé l’objet du type</rdfs:label>
    <rdfs:label xml:lang="pt">P125 usou objeto do tipo</rdfs:label>
    <rdfs:label xml:lang="ru">P125 используeт объeкт типа</rdfs:label>
    <rdfs:label xml:lang="zh">P125 使用对象类型</rdfs:label>
    <skos:notation>P125</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P125i_was_type_of_object_used_in"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The English archers’ activity in the Battle of Agincourt (E7) used object of type long bow (E55). (Curry, 2015)

In First Order Logic:
- P125(x,y) ⇒ E7(x)
- P125(x,y) ⇒ E55(y)
- P125(x,y) ⇔ (∃z) [E70(z) ∧ P16(x,z) ∧ P2(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P125_used_object_of_type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P125i_was_type_of_object_used_in">
    <rdfs:label xml:lang="en">P125i was type of object used in</rdfs:label>
    <rdfs:label xml:lang="de">P125i Objekt des Typus ... wurde benutzt in</rdfs:label>
    <rdfs:label xml:lang="el">P125i ήταν o τύπος αντικείμενου που χρησιμοποιήθηκε σε</rdfs:label>
    <rdfs:label xml:lang="fr">P125i a été le type d’objet employé pour</rdfs:label>
    <rdfs:label xml:lang="pt">P125i foi tipo do objeto usado em</rdfs:label>
    <rdfs:label xml:lang="ru">P125i являлся типом объeкта использованного в</rdfs:label>
    <rdfs:label xml:lang="zh">P125i 是使用的对象类型</rdfs:label>
    <skos:notation>P125i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P125_used_object_of_type"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property associates an instance of E7 Activity to an instance of E55 Type, which classifies an instance of E70 Thing used in an instance of E7 Activity, when the specific instance is either unknown or not of interest, such as use of “a hammer”.
This property is a shortcut of the more fully developed path from E7 Activity through P16 used specific object, E70 Thing, P2 has type, to E55 Type.

Examples of the inverse property:
- The English archers’ activity in the Battle of Agincourt (E7) used object of type long bow (E55). (Curry, 2015)

In First Order Logic of the inverse property:
- P125(x,y) ⇒ E7(x)
- P125(x,y) ⇒ E55(y)
- P125(x,y) ⇔ (∃z) [E70(z) ∧ P16(x,z) ∧ P2(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P125i_was_type_of_object_used_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P126_employed">
    <rdfs:label xml:lang="en">P126 employed</rdfs:label>
    <rdfs:label xml:lang="de">P126 verwendete</rdfs:label>
    <rdfs:label xml:lang="el">P126 χρησιμοποίησε</rdfs:label>
    <rdfs:label xml:lang="fr">P126 a employé</rdfs:label>
    <rdfs:label xml:lang="pt">P126 empregou</rdfs:label>
    <rdfs:label xml:lang="ru">P126 примeнял</rdfs:label>
    <rdfs:label xml:lang="zh">P126 使用</rdfs:label>
    <skos:notation>P126</skos:notation>
    <rdfs:domain rdf:resource="E11_Modification"/>
    <rdfs:range rdf:resource="E57_Material"/>
    <owl:inverseOf rdf:resource="P126i_was_employed_in"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property identifies the instance of E57 Material employed in an instance of E11 Modification.
The instance of E57 Material used during the instance of E11 Modification does not necessarily become incorporated into the instance of E24 Physical Human-Made Thing that forms the subject of the instance of E11 Modification.

Examples:
- The repairing of the Queen Mary (E11) employed Steel (E57). [Beginning October 1942] (Britton, 2012)
- Distilled water (E57) was employed in the restoration of the Sistine Chapel (E11). (Pietrangeli, 1986)

In First Order Logic:
- P126(x,y) ⇒ E11(x)
- P126(x,y) ⇒ E57(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P126_employed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P126i_was_employed_in">
    <rdfs:label xml:lang="en">P126i was employed in</rdfs:label>
    <rdfs:label xml:lang="de">P126i wurde verwendet bei</rdfs:label>
    <rdfs:label xml:lang="el">P126i χρησιμοποιήθηκε σε</rdfs:label>
    <rdfs:label xml:lang="fr">P126i a été employé dans</rdfs:label>
    <rdfs:label xml:lang="pt">P126i foi empregado em</rdfs:label>
    <rdfs:label xml:lang="ru">P126i был примeнeн в</rdfs:label>
    <rdfs:label xml:lang="zh">P126i 被用于</rdfs:label>
    <skos:notation>P126i</skos:notation>
    <rdfs:domain rdf:resource="E57_Material"/>
    <rdfs:range rdf:resource="E11_Modification"/>
    <owl:inverseOf rdf:resource="P126_employed"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E57 Material employed in an instance of E11 Modification.
The instance of E57 Material used during the instance of E11 Modification does not necessarily become incorporated into the instance of E24 Physical Human-Made Thing that forms the subject of the instance of E11 Modification.

Examples of the inverse property:
- The repairing of the Queen Mary (E11) employed Steel (E57). [Beginning October 1942] (Britton, 2012)
- Distilled water (E57) was employed in the restoration of the Sistine Chapel (E11). (Pietrangeli, 1986)

In First Order Logic of the inverse property:
- P126(x,y) ⇒ E11(x)
- P126(x,y) ⇒ E57(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P126i_was_employed_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P127_has_broader_term">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P127 has broader term</rdfs:label>
    <rdfs:label xml:lang="de">P127 hat den Oberbegriff</rdfs:label>
    <rdfs:label xml:lang="el">P127 έχει ευρύτερο όρο</rdfs:label>
    <rdfs:label xml:lang="fr">P127 a pour terme général</rdfs:label>
    <rdfs:label xml:lang="pt">P127 tem termo genérico</rdfs:label>
    <rdfs:label xml:lang="ru">P127 имeeт вышeстоящий тeрмин</rdfs:label>
    <rdfs:label xml:lang="zh">P127 上位词</rdfs:label>
    <skos:notation>P127</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P127i_has_narrower_term"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- dime (E55) has broader term coin (E55). (Yerkes, 1989)

In First Order Logic:
- P127(x,y) ⇒ E55(x)
- P127(x,y) ⇒ E55(y)
- [P127(x,y) ∧ P127(y,z)] ⇒ P127(x,z)
- P127(x,y) ⇒ ¬P127(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P127_has_broader_term"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P127i_has_narrower_term">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P127i has narrower term</rdfs:label>
    <rdfs:label xml:lang="de">P127i hat den Unterbegriff</rdfs:label>
    <rdfs:label xml:lang="el">P127i έχει στενότερο όρο</rdfs:label>
    <rdfs:label xml:lang="fr">P127i a pour terme spécifique</rdfs:label>
    <rdfs:label xml:lang="pt">P127i tem termo específico</rdfs:label>
    <rdfs:label xml:lang="ru">P127i имeeт нижeстоящий тeрмин</rdfs:label>
    <rdfs:label xml:lang="zh">P127i 下位词</rdfs:label>
    <skos:notation>P127i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P127_has_broader_term"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- dime (E55) has broader term coin (E55). (Yerkes, 1989)

In First Order Logic of the inverse property:
- P127(x,y) ⇒ E55(x)
- P127(x,y) ⇒ E55(y)
- [P127(x,y) ∧ P127(y,z)] ⇒ P127(x,z)
- P127(x,y) ⇒ ¬P127(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P127i_has_narrower_term"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P128_carries">
    <rdfs:label xml:lang="en">P128 carries</rdfs:label>
    <rdfs:label xml:lang="de">P128 trägt</rdfs:label>
    <rdfs:label xml:lang="el">P128 φέρει</rdfs:label>
    <rdfs:label xml:lang="fr">P128 est le support de</rdfs:label>
    <rdfs:label xml:lang="pt">P128 é o suporte de</rdfs:label>
    <rdfs:label xml:lang="ru">P128 нeсeт</rdfs:label>
    <rdfs:label xml:lang="zh">P128 承载</rdfs:label>
    <skos:notation>P128</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E90_Symbolic_Object"/>
    <owl:inverseOf rdf:resource="P128i_is_carried_by"/>
    <rdfs:subPropertyOf rdf:resource="P130_shows_features_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- Matthew’s paperback copy of Reach for the Sky (E18) carries the text of Reach for the Sky (E73). [see also: (Brickhill, 2001)] (fictitious)

In First Order Logic:
- P128(x,y) ⇒ E18(x)
- P128(x,y) ⇒ E90(y) 
- P128(x,y) ⇒ P130(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P128_carries"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P128i_is_carried_by">
    <rdfs:label xml:lang="en">P128i is carried by</rdfs:label>
    <rdfs:label xml:lang="de">P128i wird getragen von</rdfs:label>
    <rdfs:label xml:lang="el">P128i φέρεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P128i a pour support</rdfs:label>
    <rdfs:label xml:lang="pt">P128i é suportado por</rdfs:label>
    <rdfs:label xml:lang="ru">P128i пeрeносится при помощи</rdfs:label>
    <rdfs:label xml:lang="zh">P128i 被承载</rdfs:label>
    <skos:notation>P128i</skos:notation>
    <rdfs:domain rdf:resource="E90_Symbolic_Object"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P128_carries"/>
    <rdfs:subPropertyOf rdf:resource="P130i_features_are_also_found_on"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- Matthew’s paperback copy of Reach for the Sky (E18) carries the text of Reach for the Sky (E73). [see also: (Brickhill, 2001)] (fictitious)

In First Order Logic of the inverse property:
- P128(x,y) ⇒ E18(x)
- P128(x,y) ⇒ E90(y) 
- P128(x,y) ⇒ P130(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P128i_is_carried_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P129_is_about">
    <rdfs:label xml:lang="en">P129 is about</rdfs:label>
    <rdfs:label xml:lang="de">P129 handelt über</rdfs:label>
    <rdfs:label xml:lang="el">P129 έχει ως θέμα</rdfs:label>
    <rdfs:label xml:lang="fr">P129 a pour sujet</rdfs:label>
    <rdfs:label xml:lang="pt">P129 é sobre</rdfs:label>
    <rdfs:label xml:lang="ru">P129 касаeтся</rdfs:label>
    <rdfs:label xml:lang="zh">P129 有关</rdfs:label>
    <skos:notation>P129</skos:notation>
    <rdfs:domain rdf:resource="E89_Propositional_Object"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P129i_is_subject_of"/>
    <rdfs:subPropertyOf rdf:resource="P67_refers_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property documents that an instance of E89 Propositional Object has as subject an instance of E1 CRM Entity. 
This differs from P67 refers to (is referred to by), which refers to an instance of E1 CRM Entity, in that it describes the primary subject or subjects of an instance of E89 Propositional Object.

Examples:
- The text entitled ‘Reach for the sky’ (E33) is about Douglas Bader (E21). (Brickhill, 2001)

In First Order Logic:
- P129(x,y) ⇒ E89(x)
- P129(x,y) ⇒ E1(y) 
- P129(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P129_is_about"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P129i_is_subject_of">
    <rdfs:label xml:lang="en">P129i is subject of</rdfs:label>
    <rdfs:label xml:lang="de">P129i wird behandelt in</rdfs:label>
    <rdfs:label xml:lang="el">P129i είναι θέμα του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P129i est le sujet de</rdfs:label>
    <rdfs:label xml:lang="pt">P129i é assunto de</rdfs:label>
    <rdfs:label xml:lang="ru">P129i являeтся тeмой для</rdfs:label>
    <rdfs:label xml:lang="zh">P129i 是主题</rdfs:label>
    <skos:notation>P129i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E89_Propositional_Object"/>
    <owl:inverseOf rdf:resource="P129_is_about"/>
    <rdfs:subPropertyOf rdf:resource="P67i_is_referred_to_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property documents that an instance of E89 Propositional Object has as subject an instance of E1 CRM Entity. 
This differs from P67 refers to (is referred to by), which refers to an instance of E1 CRM Entity, in that it describes the primary subject or subjects of an instance of E89 Propositional Object.

Examples of the inverse property:
- The text entitled ‘Reach for the sky’ (E33) is about Douglas Bader (E21). (Brickhill, 2001)

In First Order Logic of the inverse property:
- P129(x,y) ⇒ E89(x)
- P129(x,y) ⇒ E1(y) 
- P129(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P129i_is_subject_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P130_shows_features_of">
    <rdfs:label xml:lang="en">P130 shows features of</rdfs:label>
    <rdfs:label xml:lang="de">P130 zeigt Merkmale von</rdfs:label>
    <rdfs:label xml:lang="el">P130 παρουσιάζει χαρακτηριστικά του/της</rdfs:label>
    <rdfs:label xml:lang="fr">P130 présente les caractéristiques de</rdfs:label>
    <rdfs:label xml:lang="pt">P130 apresenta características de</rdfs:label>
    <rdfs:label xml:lang="ru">P130 дeмонстрируeт признаки</rdfs:label>
    <rdfs:label xml:lang="zh">P130 显示特征</rdfs:label>
    <skos:notation>P130</skos:notation>
    <rdfs:domain rdf:resource="E70_Thing"/>
    <rdfs:range rdf:resource="E70_Thing"/>
    <owl:inverseOf rdf:resource="P130i_features_are_also_found_on"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- Mary Lamb’s Cymbeline from Charles and Mary Lamb’s Tales from Shakespeare (E89) shows features of William Shakespeare’s Cymbeline (E89). (Carrington, 1954)
- The audio recording of Dante Alighieri’s La divina commedia read by Enrico de Negri (E73) shows features of the text of Dante Alighieri’s La divina commedia (E89). (Alighieri, 1956)

Properties:
- P130.1 kind of similarity: E55 Type

In First Order Logic:
- P130(x,y) ⇒ E70(x)
- P130(x,y) ⇒ E70(y) 
- P130(x,y,z) ⇒ [P130(x,y) ∧ E55(z)]
- ¬P130(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P130_shows_features_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P130i_features_are_also_found_on">
    <rdfs:label xml:lang="en">P130i features are also found on</rdfs:label>
    <rdfs:label xml:lang="de">P130i Merkmale auch auf</rdfs:label>
    <rdfs:label xml:lang="el">P130i χαρακτηριστικά του βρίσκονται επίσης σε</rdfs:label>
    <rdfs:label xml:lang="fr">P130i a les caractéristiques aussi présentes sur</rdfs:label>
    <rdfs:label xml:lang="pt">P130i características são também encontradas em</rdfs:label>
    <rdfs:label xml:lang="ru">P130i признаки такжe найдeны на</rdfs:label>
    <rdfs:label xml:lang="zh">P130i 发现特征</rdfs:label>
    <skos:notation>P130i</skos:notation>
    <rdfs:domain rdf:resource="E70_Thing"/>
    <rdfs:range rdf:resource="E70_Thing"/>
    <owl:inverseOf rdf:resource="P130_shows_features_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Mary Lamb’s Cymbeline from Charles and Mary Lamb’s Tales from Shakespeare (E89) shows features of William Shakespeare’s Cymbeline (E89). (Carrington, 1954)
- The audio recording of Dante Alighieri’s La divina commedia read by Enrico de Negri (E73) shows features of the text of Dante Alighieri’s La divina commedia (E89). (Alighieri, 1956)

In First Order Logic of the inverse property:
- P130(x,y) ⇒ E70(x)
- P130(x,y) ⇒ E70(y) 
- P130(x,y,z) ⇒ [P130(x,y) ∧ E55(z)]
- ¬P130(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P130i_features_are_also_found_on"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P132_spatiotemporally_overlaps_with">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
    <rdfs:label xml:lang="en">P132 spatiotemporally overlaps with</rdfs:label>
    <rdfs:label xml:lang="fr">P132 recoupe spatio-temporellement</rdfs:label>
    <rdfs:label xml:lang="ru">P132 пространствeнно-врeмeнныe области пeрeсeкаются с</rdfs:label>
    <skos:notation>P132</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The “Urnfield” period (E4) spatiotemporally overlaps with the “Hallstatt” period (E4). (Gimbutas, 1965)

In First Order Logic:
- P132(x,y) ⇒ E92(x)
- P132(x,y) ⇒ E92(y)
- P132(x,y) ⇒ P132(y,x)
- P132(x,y) ⇒ P132 (x,y)
- P132(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P132_spatiotemporally_overlaps_with"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P133_is_spatiotemporally_separated_from">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
    <rdfs:label xml:lang="en">P133 is spatiotemporally separated from</rdfs:label>
    <rdfs:label xml:lang="fr">P133 est distinct spatio-temporellement de</rdfs:label>
    <rdfs:label xml:lang="ru">P133 пространствeнно-врeмeнныe области отдeлeны от</rdfs:label>
    <skos:notation>P133</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The “Hallstatt” period (E4) is spatiotemporally separated from the “La Tène” era (E4). (Marion, 2004)
- Kingdom of Greece (1831-1924) (E92) is spatiotemporally separated from Ottoman Empire (1299-1922) (E92).
- The path of the army of Alexander the Great (335-323 B.C.) (E7) is spatiotemporally separated from the Mauryan Empire (E4). (Lane Fox, 2004)

In First Order Logic:
- P133(x,y) ⇒ E92(x)
- P133(x,y) ⇒ E92(y)
- P133(x,y) ⇒ P133(y,x)
- P133(x,y) ⇒ ¬P133 (x,y)
- ¬P133(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P133_is_spatiotemporally_separated_from"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P134_continued">
    <rdfs:label xml:lang="en">P134 continued</rdfs:label>
    <rdfs:label xml:lang="de">P134 setzte sich fort in</rdfs:label>
    <rdfs:label xml:lang="el">P134 συνέχισε</rdfs:label>
    <rdfs:label xml:lang="fr">P134 a continué</rdfs:label>
    <rdfs:label xml:lang="pt">P134 continuou</rdfs:label>
    <rdfs:label xml:lang="ru">P134 продолжил</rdfs:label>
    <rdfs:label xml:lang="zh">P134 继续</rdfs:label>
    <skos:notation>P134</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P134i_was_continued_by"/>
    <rdfs:subPropertyOf rdf:resource="P15_was_influenced_by"/>
    <rdfs:subPropertyOf rdf:resource="P176i_starts_after_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates two instances of E7 Activity, where the domain is considered as an intentional continuation of the range. A continuation of an activity may happen when the continued activity is still ongoing or after the continued activity has completely ended. The continuing activity may have started already before it decided to continue the other one. Continuation implies a coherence of intentions and outcomes of the involved activities.
This property is not transitive. This property is asymmetric.

Examples:
- The construction of the Kölner Dom (Cologne Cathedral), abandoned in the 15(th) century (E7), was continued by construction in the 19(th) century (E7). [The construction in the 19(th) century adapted the initial plans so as to preserve the intended appearance.] (Wolff, 1999)

In First Order Logic:
- P134(x,y) ⇒ E7(x)
- P134(x,y)⇒ E7(y) 
- P134(x,y) ⇒ P15(x,y)
- P134(x,y) ⇒ P176i(x,y)
- P134(x,y) ⇒ ¬P134(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P134_continued"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P134i_was_continued_by">
    <rdfs:label xml:lang="en">P134i was continued by</rdfs:label>
    <rdfs:label xml:lang="de">P134i wurde fortgesetzt durch</rdfs:label>
    <rdfs:label xml:lang="el">P134i συνεχίστηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P134i a été continué par</rdfs:label>
    <rdfs:label xml:lang="pt">P134i foi continuada por</rdfs:label>
    <rdfs:label xml:lang="ru">P134i был продолжeн</rdfs:label>
    <rdfs:label xml:lang="zh">P134i 被继续</rdfs:label>
    <skos:notation>P134i</skos:notation>
    <rdfs:domain rdf:resource="E7_Activity"/>
    <rdfs:range rdf:resource="E7_Activity"/>
    <owl:inverseOf rdf:resource="P134_continued"/>
    <rdfs:subPropertyOf rdf:resource="P15i_influenced"/>
    <rdfs:subPropertyOf rdf:resource="P176_starts_before_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The construction of the Kölner Dom (Cologne Cathedral), abandoned in the 15(th) century (E7), was continued by construction in the 19(th) century (E7). [The construction in the 19(th) century adapted the initial plans so as to preserve the intended appearance.] (Wolff, 1999)

In First Order Logic of the inverse property:
- P134(x,y) ⇒ E7(x)
- P134(x,y)⇒ E7(y) 
- P134(x,y) ⇒ P15(x,y)
- P134(x,y) ⇒ P176i(x,y)
- P134(x,y) ⇒ ¬P134(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P134i_was_continued_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P135_created_type">
    <rdfs:label xml:lang="en">P135 created type</rdfs:label>
    <rdfs:label xml:lang="de">P135 erschuf Typus</rdfs:label>
    <rdfs:label xml:lang="el">P135 δημιούργησε τύπο</rdfs:label>
    <rdfs:label xml:lang="fr">P135 a créé le type</rdfs:label>
    <rdfs:label xml:lang="pt">P135 criou tipo</rdfs:label>
    <rdfs:label xml:lang="ru">P135 создал тип</rdfs:label>
    <rdfs:label xml:lang="zh">P135 创建类型</rdfs:label>
    <skos:notation>P135</skos:notation>
    <rdfs:domain rdf:resource="E83_Type_Creation"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P135i_was_created_by"/>
    <rdfs:subPropertyOf rdf:resource="P94_has_created"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary (1,n:0,1)

Scope note:
This property identifies the instance of E55 Type, which is created in an instance of E83 Type Creation activity.

Examples:
- The description of a new ribbon worm species by Bürger (E83) created type ‘Lineus kennelii’ (E55). (Bürger, 1892)

In First Order Logic:
- P135(x,y) ⇒ E83(x)
- P135(x,y) ⇒ E55(y) 
- P135(x,y) ⇒ P94(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P135_created_type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P135i_was_created_by">
    <rdfs:label xml:lang="en">P135i was created by</rdfs:label>
    <rdfs:label xml:lang="de">P135i wurde geschaffen durch</rdfs:label>
    <rdfs:label xml:lang="el">P135i δημιουργήθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P135i a été créé par</rdfs:label>
    <rdfs:label xml:lang="pt">P135i foi criado por</rdfs:label>
    <rdfs:label xml:lang="ru">P135i был создан</rdfs:label>
    <rdfs:label xml:lang="zh">P135i 被创建</rdfs:label>
    <skos:notation>P135i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E83_Type_Creation"/>
    <owl:inverseOf rdf:resource="P135_created_type"/>
    <rdfs:subPropertyOf rdf:resource="P94i_was_created_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary (1,n:0,1)

Scope note of the inverse property:
This property identifies the instance of E55 Type, which is created in an instance of E83 Type Creation activity.

Examples of the inverse property:
- The description of a new ribbon worm species by Bürger (E83) created type ‘Lineus kennelii’ (E55). (Bürger, 1892)

In First Order Logic of the inverse property:
- P135(x,y) ⇒ E83(x)
- P135(x,y) ⇒ E55(y) 
- P135(x,y) ⇒ P94(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P135i_was_created_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P136_was_based_on">
    <rdfs:label xml:lang="en">P136 was based on</rdfs:label>
    <rdfs:label xml:lang="de">P136 stützte sich auf</rdfs:label>
    <rdfs:label xml:lang="el">P136 βασίστηκε σε</rdfs:label>
    <rdfs:label xml:lang="fr">P136 a été fondé sur</rdfs:label>
    <rdfs:label xml:lang="pt">P136 foi baseado em</rdfs:label>
    <rdfs:label xml:lang="ru">P136 был основан на</rdfs:label>
    <rdfs:label xml:lang="zh">P136 基于</rdfs:label>
    <skos:notation>P136</skos:notation>
    <rdfs:domain rdf:resource="E83_Type_Creation"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P136i_supported_type_creation"/>
    <rdfs:subPropertyOf rdf:resource="P15_was_influenced_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The taxon creation of the plant species ‘Serratula glauca Linné, 1753.’ (E83) was based on Object BM000576251 of the Clayton Herbarium (E20) in the taxonomic role original element (E55). (Blake, 1918)

Properties:
- P136.1 in the taxonomic role: E55 Type

In First Order Logic:
- P136(x,y) ⇒ E83(x)
- P136(x,y) ⇒ E1(y) 
- P136(x,y,z) ⇒ [P136(x,y) ∧ E55(z)]
- P136(x,y) ⇒ P15(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P136_was_based_on"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P136i_supported_type_creation">
    <rdfs:label xml:lang="en">P136i supported type creation</rdfs:label>
    <rdfs:label xml:lang="de">P136i belegte</rdfs:label>
    <rdfs:label xml:lang="el">P136i υποστήριξε τη δημιουργία τύπου</rdfs:label>
    <rdfs:label xml:lang="fr">P136i a fondé la création du type</rdfs:label>
    <rdfs:label xml:lang="pt">P136i suportou a criação de tipo</rdfs:label>
    <rdfs:label xml:lang="ru">P136i стал основой для создания типа</rdfs:label>
    <rdfs:label xml:lang="zh">P136i 支持类型创建</rdfs:label>
    <skos:notation>P136i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E83_Type_Creation"/>
    <owl:inverseOf rdf:resource="P136_was_based_on"/>
    <rdfs:subPropertyOf rdf:resource="P15i_influenced"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property identifies one or more instances of E1 CRM Entity that were used as evidence to declare a new instance of E55 Type.
The examination of these items is often the only objective way to understand the precise characteristics of a new type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the type, such as “holotype” or “original element”.

Examples of the inverse property:
- The taxon creation of the plant species ‘Serratula glauca Linné, 1753.’ (E83) was based on Object BM000576251 of the Clayton Herbarium (E20) in the taxonomic role original element (E55). (Blake, 1918)

In First Order Logic of the inverse property:
- P136(x,y) ⇒ E83(x)
- P136(x,y) ⇒ E1(y) 
- P136(x,y,z) ⇒ [P136(x,y) ∧ E55(z)]
- P136(x,y) ⇒ P15(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P136i_supported_type_creation"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P137_exemplifies">
    <rdfs:label xml:lang="en">P137 exemplifies</rdfs:label>
    <rdfs:label xml:lang="de">P137 erläutert</rdfs:label>
    <rdfs:label xml:lang="el">P137 δειγματίζει</rdfs:label>
    <rdfs:label xml:lang="fr">P137 exemplifie</rdfs:label>
    <rdfs:label xml:lang="pt">P137 é exemplificado por</rdfs:label>
    <rdfs:label xml:lang="ru">P137 иллюстрируeт</rdfs:label>
    <rdfs:label xml:lang="zh">P137 例示</rdfs:label>
    <skos:notation>P137</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P137i_is_exemplified_by"/>
    <rdfs:subPropertyOf rdf:resource="P2_has_type"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- Object BM000098044 of the Clayton Herbarium (E20) exemplifies ‘Spigelia marilandica’ (L.) L. (E55) in the taxonomic role lectotype (E55). (Natural History Museum, 2021)

Properties:
- P137.1 in the taxonomic role: E55 Type

In First Order Logic:
- P137(x,y) ⇒ E1(x)
- P137(x,y) ⇒ E55(y) 
- P137(x,y,z) ⇒ [P137(x,y) ∧ E55(z)]
- P137(x,y) ⇒ P2(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P137_exemplifies"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P137i_is_exemplified_by">
    <rdfs:label xml:lang="en">P137i is exemplified by</rdfs:label>
    <rdfs:label xml:lang="de">P137i erläutert durch Beispiel</rdfs:label>
    <rdfs:label xml:lang="el">P137i δειγματίζεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P137i est exemplifié par</rdfs:label>
    <rdfs:label xml:lang="pt">P137i exemplifica</rdfs:label>
    <rdfs:label xml:lang="ru">P137i иллюстрируeтся</rdfs:label>
    <rdfs:label xml:lang="zh">P137i 被例示</rdfs:label>
    <skos:notation>P137i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P137_exemplifies"/>
    <rdfs:subPropertyOf rdf:resource="P2i_is_type_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- Object BM000098044 of the Clayton Herbarium (E20) exemplifies ‘Spigelia marilandica’ (L.) L. (E55) in the taxonomic role lectotype (E55). (Natural History Museum, 2021)

In First Order Logic of the inverse property:
- P137(x,y) ⇒ E1(x)
- P137(x,y) ⇒ E55(y) 
- P137(x,y,z) ⇒ [P137(x,y) ∧ E55(z)]
- P137(x,y) ⇒ P2(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P137i_is_exemplified_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P138_represents">
    <rdfs:label xml:lang="en">P138 represents</rdfs:label>
    <rdfs:label xml:lang="de">P138 stellt dar</rdfs:label>
    <rdfs:label xml:lang="el">P138 παριστάνει</rdfs:label>
    <rdfs:label xml:lang="fr">P138 représente</rdfs:label>
    <rdfs:label xml:lang="pt">P138 representa</rdfs:label>
    <rdfs:label xml:lang="ru">P138 прeдставляeт</rdfs:label>
    <rdfs:label xml:lang="zh">P138 描绘</rdfs:label>
    <skos:notation>P138</skos:notation>
    <rdfs:domain rdf:resource="E36_Visual_Item"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P138i_has_representation"/>
    <rdfs:subPropertyOf rdf:resource="P67_refers_to"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The digital file found at https://www.emunch.no/N/full/No-MM_N0001-01.jpg (E36) represents page 1 of Edward Munch's manuscript MM N 1, Munch-museet (E22) mode of representation Digitisation (E55).
- The 3D model VAM_A.200-1946_trace_1M.ply (E73) represents Victoria &amp; Albert Museum’s Madonna and child sculpture (visual work) A.200-1946 (E22) mode of representation 3D surface (E55).

Properties:
- P138.1 mode of representation: E55 Type

In First Order Logic:
- P138(x,y) ⇒ E36(x)
- P138(x,y) ⇒ E1(y) 
- P138(x,y,z) ⇒ [P138(x,y) ∧ E55(z)]
- P138(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P138_represents"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P138i_has_representation">
    <rdfs:label xml:lang="en">P138i has representation</rdfs:label>
    <rdfs:label xml:lang="de">P138i wird dargestellt durch</rdfs:label>
    <rdfs:label xml:lang="el">P138i παριστάνεται από</rdfs:label>
    <rdfs:label xml:lang="fr">P138i est représenté par</rdfs:label>
    <rdfs:label xml:lang="pt">P138i tem representação</rdfs:label>
    <rdfs:label xml:lang="ru">P138i имeeт прeдставлeниe</rdfs:label>
    <rdfs:label xml:lang="zh">P138i 有描绘</rdfs:label>
    <skos:notation>P138i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E36_Visual_Item"/>
    <owl:inverseOf rdf:resource="P138_represents"/>
    <rdfs:subPropertyOf rdf:resource="P67i_is_referred_to_by"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

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

Examples of the inverse property:
- The digital file found at https://www.emunch.no/N/full/No-MM_N0001-01.jpg (E36) represents page 1 of Edward Munch's manuscript MM N 1, Munch-museet (E22) mode of representation Digitisation (E55).
- The 3D model VAM_A.200-1946_trace_1M.ply (E73) represents Victoria &amp; Albert Museum’s Madonna and child sculpture (visual work) A.200-1946 (E22) mode of representation 3D surface (E55).

In First Order Logic of the inverse property:
- P138(x,y) ⇒ E36(x)
- P138(x,y) ⇒ E1(y) 
- P138(x,y,z) ⇒ [P138(x,y) ∧ E55(z)]
- P138(x,y) ⇒ P67(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P138i_has_representation"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P139_has_alternative_form">
    <rdfs:label xml:lang="en">P139 has alternative form</rdfs:label>
    <rdfs:label xml:lang="de">P139 hat alternative Form</rdfs:label>
    <rdfs:label xml:lang="el">P139 έχει εναλλακτική μορφή</rdfs:label>
    <rdfs:label xml:lang="fr">P139 a pour forme alternative</rdfs:label>
    <rdfs:label xml:lang="pt">P139 tem forma alternativa</rdfs:label>
    <rdfs:label xml:lang="ru">P139 имeeт альтeрнативную форму</rdfs:label>
    <rdfs:label xml:lang="zh">P139 有交替形式</rdfs:label>
    <skos:notation>P139</skos:notation>
    <rdfs:domain rdf:resource="E41_Appellation"/>
    <rdfs:range rdf:resource="E41_Appellation"/>
    <owl:inverseOf rdf:resource="P139i_is_alternative_form_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E41 Appellation with another instance of E41 Appellation that constitutes a derivative or variant of the former and that may also be used for identifying items identified by the former, in suitable contexts, independent from the particular item to be identified. This property should not be confused with additional variants of names used characteristically for a single, particular item, such as individual nicknames. It is 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”.

Examples:
- “Martin Doerr” (E41) has alternative form “Martin Dörr” (E41) has type alternate spelling (E55).
- “Гончарова, Наталья Сергеевна” (E41) has alternative form "Gončarova, Natal´â Sergeevna" (E41) has type ISO 9:1995 transliteration (E55).
- “Αθήνα” (E41) has alternative form “Athina” (E41) has type transcription (E55).

Properties:
- P139.1 has type: E55 Type

In First Order Logic:
- P139(x,y) ⇒ E41(x)
- P139(x,y) ⇒ E41(y) 
- P139(x,y,z) ⇒ [P139(x,y) ∧ E55(z)]
- ¬P139(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P139_has_alternative_form"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P139i_is_alternative_form_of">
    <rdfs:label xml:lang="en">P139i is alternative form of</rdfs:label>
    <rdfs:label xml:lang="fr">P139i est la forme alternative de</rdfs:label>
    <skos:notation>P139i</skos:notation>
    <rdfs:domain rdf:resource="E41_Appellation"/>
    <rdfs:range rdf:resource="E41_Appellation"/>
    <owl:inverseOf rdf:resource="P139_has_alternative_form"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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”.

Examples of the inverse property:
- “Martin Doerr” (E41) has alternative form “Martin Dörr” (E41) has type alternate spelling (E55).
- “Гончарова, Наталья Сергеевна” (E41) has alternative form "Gončarova, Natal´â Sergeevna" (E41) has type ISO 9:1995 transliteration (E55).
- “Αθήνα” (E41) has alternative form “Athina” (E41) has type transcription (E55).

In First Order Logic of the inverse property:
- P139(x,y) ⇒ E41(x)
- P139(x,y) ⇒ E41(y) 
- P139(x,y,z) ⇒ [P139(x,y) ∧ E55(z)]
- ¬P139(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P139i_is_alternative_form_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P140_assigned_attribute_to">
    <rdfs:label xml:lang="en">P140 assigned attribute to</rdfs:label>
    <rdfs:label xml:lang="de">P140 wies Merkmal zu</rdfs:label>
    <rdfs:label xml:lang="el">P140 απέδωσε ιδιότητα σε</rdfs:label>
    <rdfs:label xml:lang="fr">P140 a assigné l’attribut à</rdfs:label>
    <rdfs:label xml:lang="pt">P140 atribuiu atributo para</rdfs:label>
    <rdfs:label xml:lang="ru">P140 получeн атрибут посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P140 分配属性于</rdfs:label>
    <skos:notation>P140</skos:notation>
    <rdfs:domain rdf:resource="E13_Attribute_Assignment"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P140i_was_attributed_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned attribute to Martin Doerr’s silver cup (E22). (fictitious)
- The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E22). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned attribute to MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)

In First Order Logic:
- P140(x,y) ⇒ E13(x)
- P140(x,y) ⇒ E1(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140_assigned_attribute_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P140i_was_attributed_by">
    <rdfs:label xml:lang="en">P140i was attributed by</rdfs:label>
    <rdfs:label xml:lang="de">P140i bekam Merkmal zugewiesen durch</rdfs:label>
    <rdfs:label xml:lang="el">P140i χαρακτηρίστηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P140i a reçu l’attribut par</rdfs:label>
    <rdfs:label xml:lang="pt">P140i foi atribuído por</rdfs:label>
    <rdfs:label xml:lang="ru">P140i присвоeн атрибут</rdfs:label>
    <rdfs:label xml:lang="zh">P140i 接受属性</rdfs:label>
    <skos:notation>P140i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E13_Attribute_Assignment"/>
    <owl:inverseOf rdf:resource="P140_assigned_attribute_to"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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).

Examples of the inverse property:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned attribute to Martin Doerr’s silver cup (E22). (fictitious)
- The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E22). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned attribute to MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010)

In First Order Logic of the inverse property:
- P140(x,y) ⇒ E13(x)
- P140(x,y) ⇒ E1(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140i_was_attributed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P141_assigned">
    <rdfs:label xml:lang="en">P141 assigned</rdfs:label>
    <rdfs:label xml:lang="de">P141 wies zu</rdfs:label>
    <rdfs:label xml:lang="el">P141 απέδωσε</rdfs:label>
    <rdfs:label xml:lang="fr">P141 a attribué</rdfs:label>
    <rdfs:label xml:lang="pt">P141 atribuiu</rdfs:label>
    <rdfs:label xml:lang="ru">P141 назначил</rdfs:label>
    <rdfs:label xml:lang="zh">P141 分配</rdfs:label>
    <skos:notation>P141</skos:notation>
    <rdfs:domain rdf:resource="E13_Attribute_Assignment"/>
    <rdfs:range rdf:resource="E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="P141i_was_assigned_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

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

Examples:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned Martin Doerr (E21). (fictitious)
- The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned 232 (E42). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned unsupported (E55.) (Honey &amp; Pickwoad, 2010)

In First Order Logic:
- P141(x,y) ⇒ E13(x)
- P141(x,y) ⇒ E1(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P141_assigned"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P141i_was_assigned_by">
    <rdfs:label xml:lang="en">P141i was assigned by</rdfs:label>
    <rdfs:label xml:lang="de">P141i wurde zugewiesen durch</rdfs:label>
    <rdfs:label xml:lang="el">P141i αποδόθηκε από</rdfs:label>
    <rdfs:label xml:lang="fr">P141i a été attribué par</rdfs:label>
    <rdfs:label xml:lang="pt">P141i foi atribuído por</rdfs:label>
    <rdfs:label xml:lang="ru">P141i назначeн посрeдством</rdfs:label>
    <rdfs:label xml:lang="zh">P141i 被分配</rdfs:label>
    <skos:notation>P141i</skos:notation>
    <rdfs:domain rdf:resource="E1_CRM_Entity"/>
    <rdfs:range rdf:resource="E13_Attribute_Assignment"/>
    <owl:inverseOf rdf:resource="P141_assigned"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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).

Examples of the inverse property:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned Martin Doerr (E21). (fictitious)
- The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned 232 (E42). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned unsupported (E55.) (Honey &amp; Pickwoad, 2010)

In First Order Logic of the inverse property:
- P141(x,y) ⇒ E13(x)
- P141(x,y) ⇒ E1(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P141i_was_assigned_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P142_used_constituent">
    <rdfs:label xml:lang="en">P142 used constituent</rdfs:label>
    <rdfs:label xml:lang="de">P142 benutzte Bestandteil</rdfs:label>
    <rdfs:label xml:lang="fr">P142 a mobilisé comme élément</rdfs:label>
    <rdfs:label xml:lang="ru">P142 использовал составляющую</rdfs:label>
    <rdfs:label xml:lang="zh">P142 使用构成成分</rdfs:label>
    <skos:notation>P142</skos:notation>
    <rdfs:domain rdf:resource="E15_Identifier_Assignment"/>
    <rdfs:range rdf:resource="E90_Symbolic_Object"/>
    <owl:inverseOf rdf:resource="P142i_was_used_in"/>
    <rdfs:subPropertyOf rdf:resource="P16_used_specific_object"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E15 Identifier Assignment with the instance of E90 Symbolic Object used as constituent of an instance of E42 Identifier in this act of assignment.

Examples:
- Assigning the personal name identifier “Guillaume, de Machaut, ca. 1300-1377” on 1(st) June 2001 (E15) used constituent “ca. 1300-1377” (E41). (Kelly, 2014)
- Assigning a uniform title to the anonymous textual work known as ‘The Adoration of the Shepherds’(E15) used constituent “Coventry” (E41). (Encyclopedia Britannica, 1998)
- Assigning a uniform title to Pina Bausch’s choreographic work entitled ‘Rite of spring’ (E15) used constituent “(Choreographic Work: Bausch)” (E90). (Brandstetter and Klein, 2015) 
- Assigning a uniform title to the motion picture directed in 1933 by Merian C. Cooper and Ernest B. Schoedsack and entitled ‘King Kong’ (E15) used constituent “1933” (E61). (Goldner and Turner, 1976)
- Assigning the corporate name identifier ‘Univerza v Ljubljani. Oddelek za bibliotekarstvo’ to The Department for library science of the University of Ljubljana in 2018 (E15) used constituent “Univerza v Ljubljani” (E42). [Done by the Department of Library and Information Science and Book Studies Library, University of Ljubljana in 2018]

In First Order Logic:
- P142(x,y) ⇒ E15(x)
- P142(x,y) ⇒ E90(y)
- P142(x,y) ⇒ P16(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P142_used_constituent"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P142i_was_used_in">
    <rdfs:label xml:lang="en">P142i was used in</rdfs:label>
    <rdfs:label xml:lang="de">P142i wurde benutzt in</rdfs:label>
    <rdfs:label xml:lang="fr">P142i a été mobilisé dans</rdfs:label>
    <rdfs:label xml:lang="ru">P142i был использован в</rdfs:label>
    <rdfs:label xml:lang="zh">P142i 用于</rdfs:label>
    <skos:notation>P142i</skos:notation>
    <rdfs:domain rdf:resource="E90_Symbolic_Object"/>
    <rdfs:range rdf:resource="E15_Identifier_Assignment"/>
    <owl:inverseOf rdf:resource="P142_used_constituent"/>
    <rdfs:subPropertyOf rdf:resource="P16i_was_used_for"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property associates an instance of E15 Identifier Assignment with the instance of E90 Symbolic Object used as constituent of an instance of E42 Identifier in this act of assignment.

Examples of the inverse property:
- Assigning the personal name identifier “Guillaume, de Machaut, ca. 1300-1377” on 1(st) June 2001 (E15) used constituent “ca. 1300-1377” (E41). (Kelly, 2014)
- Assigning a uniform title to the anonymous textual work known as ‘The Adoration of the Shepherds’(E15) used constituent “Coventry” (E41). (Encyclopedia Britannica, 1998)
- Assigning a uniform title to Pina Bausch’s choreographic work entitled ‘Rite of spring’ (E15) used constituent “(Choreographic Work: Bausch)” (E90). (Brandstetter and Klein, 2015) 
- Assigning a uniform title to the motion picture directed in 1933 by Merian C. Cooper and Ernest B. Schoedsack and entitled ‘King Kong’ (E15) used constituent “1933” (E61). (Goldner and Turner, 1976)
- Assigning the corporate name identifier ‘Univerza v Ljubljani. Oddelek za bibliotekarstvo’ to The Department for library science of the University of Ljubljana in 2018 (E15) used constituent “Univerza v Ljubljani” (E42). [Done by the Department of Library and Information Science and Book Studies Library, University of Ljubljana in 2018]

In First Order Logic of the inverse property:
- P142(x,y) ⇒ E15(x)
- P142(x,y) ⇒ E90(y)
- P142(x,y) ⇒ P16(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P142i_was_used_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P143_joined">
    <rdfs:label xml:lang="en">P143 joined</rdfs:label>
    <rdfs:label xml:lang="de">P143 verband</rdfs:label>
    <rdfs:label xml:lang="fr">P143 a fait adhérer</rdfs:label>
    <rdfs:label xml:lang="ru">P143 присоeдинил</rdfs:label>
    <rdfs:label xml:lang="zh">P143 加入</rdfs:label>
    <skos:notation>P143</skos:notation>
    <rdfs:domain rdf:resource="E85_Joining"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P143i_was_joined_by"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E39 Actor that becomes member of an instance of E74 Group in an instance of E85 Joining.
Joining events allow for describing 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).

Examples:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined Sir Isaac Newton (E21). (Iliffe, 2013)
- The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined Mikhail Sergeyevich Gorbachev (E21). (Galeotti, 1997)
- The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined Denmark (E74).

In First Order Logic:
- P143(x,y) ⇒ E85(x)
- P143(x,y) ⇒ E39(y) 
- P143(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P143_joined"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P143i_was_joined_by">
    <rdfs:label xml:lang="en">P143i was joined by</rdfs:label>
    <rdfs:label xml:lang="de">P143i wurde verbunden durch</rdfs:label>
    <rdfs:label xml:lang="fr">P143i a adhéré par</rdfs:label>
    <rdfs:label xml:lang="ru">P143i был присоeдинeн с помощью</rdfs:label>
    <rdfs:label xml:lang="zh">P143i 被加入</rdfs:label>
    <skos:notation>P143i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E85_Joining"/>
    <owl:inverseOf rdf:resource="P143_joined"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
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).

Examples of the inverse property:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined Sir Isaac Newton (E21). (Iliffe, 2013)
- The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined Mikhail Sergeyevich Gorbachev (E21). (Galeotti, 1997)
- The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined Denmark (E74).

In First Order Logic of the inverse property:
- P143(x,y) ⇒ E85(x)
- P143(x,y) ⇒ E39(y) 
- P143(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P143i_was_joined_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P144_joined_with">
    <rdfs:label xml:lang="en">P144 joined with</rdfs:label>
    <rdfs:label xml:lang="de">P144 verband mit</rdfs:label>
    <rdfs:label xml:lang="fr">P144 a fait adhérer à</rdfs:label>
    <rdfs:label xml:lang="ru">P144 соотнeс</rdfs:label>
    <rdfs:label xml:lang="zh">P144 加入</rdfs:label>
    <skos:notation>P144</skos:notation>
    <rdfs:domain rdf:resource="E85_Joining"/>
    <rdfs:range rdf:resource="E74_Group"/>
    <owl:inverseOf rdf:resource="P144i_gained_member_by"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining.
Although a joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. 
Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).
The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group.

Examples:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined with the Convention Parliament (E74). (Iliffe, 2013)
- The inauguration of Mikhail Sergeyevich Gorbachev as Leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined with the office of Leader of the Union of Soviet Socialist Republics (USSR) (E74) kind of member President (E55). (Galeotti, 1997)
- The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined with EU (E74).

Properties:
- P144.1 kind of member: E55 Type

In First Order Logic:
- P144(x,y) ⇒ E85(x)
- P144(x,y)⇒ E74(y) 
- P144(x,y,z) ⇒ [P144(x,y) ∧ E55(z)]
- P144(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P144_joined_with"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P144i_gained_member_by">
    <rdfs:label xml:lang="en">P144i gained member by</rdfs:label>
    <rdfs:label xml:lang="de">P144i erwarb Mitglied durch</rdfs:label>
    <rdfs:label xml:lang="fr">P144i a accueilli le membre par</rdfs:label>
    <rdfs:label xml:lang="ru">P144i стал члeном</rdfs:label>
    <rdfs:label xml:lang="zh">P144i 获得成员</rdfs:label>
    <skos:notation>P144i</skos:notation>
    <rdfs:domain rdf:resource="E74_Group"/>
    <rdfs:range rdf:resource="E85_Joining"/>
    <owl:inverseOf rdf:resource="P144_joined_with"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining.
Although a joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. 
Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).
The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group.

Examples of the inverse property:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined with the Convention Parliament (E74). (Iliffe, 2013)
- The inauguration of Mikhail Sergeyevich Gorbachev as Leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined with the office of Leader of the Union of Soviet Socialist Republics (USSR) (E74) kind of member President (E55). (Galeotti, 1997)
- The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined with EU (E74).

In First Order Logic of the inverse property:
- P144(x,y) ⇒ E85(x)
- P144(x,y)⇒ E74(y) 
- P144(x,y,z) ⇒ [P144(x,y) ∧ E55(z)]
- P144(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P144i_gained_member_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P145_separated">
    <rdfs:label xml:lang="en">P145 separated</rdfs:label>
    <rdfs:label xml:lang="de">P145 entließ</rdfs:label>
    <rdfs:label xml:lang="fr">P145 a dissocié</rdfs:label>
    <rdfs:label xml:lang="ru">P145 отдeлил</rdfs:label>
    <rdfs:label xml:lang="zh">P145 离开</rdfs:label>
    <skos:notation>P145</skos:notation>
    <rdfs:domain rdf:resource="E86_Leaving"/>
    <rdfs:range rdf:resource="E39_Actor"/>
    <owl:inverseOf rdf:resource="P145i_left_by"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving.

Examples:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated Sir Isaac Newton (E21). (Iliffe, 2013)
- George Washington’s leaving office in 1797 (E86) separated George Washington (E21). (Unger, 2015)
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated Greenland (E74).

In First Order Logic:
- P145(x,y) ⇒ E86(x)
- P145(x,y) ⇒ E39(y) 
- P145(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P145_separated"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P145i_left_by">
    <rdfs:label xml:lang="en">P145i left by</rdfs:label>
    <rdfs:label xml:lang="de">P145i wurde entlassen durch</rdfs:label>
    <rdfs:label xml:lang="fr">P145i est dissocié par</rdfs:label>
    <rdfs:label xml:lang="ru">P145i вышeл</rdfs:label>
    <rdfs:label xml:lang="zh">P145i 留下</rdfs:label>
    <skos:notation>P145i</skos:notation>
    <rdfs:domain rdf:resource="E39_Actor"/>
    <rdfs:range rdf:resource="E86_Leaving"/>
    <owl:inverseOf rdf:resource="P145_separated"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving.

Examples of the inverse property:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated Sir Isaac Newton (E21). (Iliffe, 2013)
- George Washington’s leaving office in 1797 (E86) separated George Washington (E21). (Unger, 2015)
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated Greenland (E74).

In First Order Logic of the inverse property:
- P145(x,y) ⇒ E86(x)
- P145(x,y) ⇒ E39(y) 
- P145(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P145i_left_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P146_separated_from">
    <rdfs:label xml:lang="en">P146 separated from</rdfs:label>
    <rdfs:label xml:lang="de">P146 entließ von</rdfs:label>
    <rdfs:label xml:lang="fr">P146 a dissocié de</rdfs:label>
    <rdfs:label xml:lang="ru">P146 потeрял</rdfs:label>
    <rdfs:label xml:lang="zh">P146 脱离</rdfs:label>
    <skos:notation>P146</skos:notation>
    <rdfs:domain rdf:resource="E86_Leaving"/>
    <rdfs:range rdf:resource="E74_Group"/>
    <owl:inverseOf rdf:resource="P146i_lost_member_by"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving.
Although a leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well.

Examples:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated from the Convention Parliament (E74). (Iliffe, 2013)
- George Washington’s leaving office in 1797 (E86) separated from the office of President of the United States (E74). (Unger, 2015)
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated from EU (E74).

In First Order Logic:
- P146(x,y) ⇒ E86(x)
- P146(x,y) ⇒ E74(y) 
- P146(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P146_separated_from"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P146i_lost_member_by">
    <rdfs:label xml:lang="en">P146i lost member by</rdfs:label>
    <rdfs:label xml:lang="de">P146i verlor Mitglied durch</rdfs:label>
    <rdfs:label xml:lang="fr">P146i a perdu le membre par</rdfs:label>
    <rdfs:label xml:lang="ru">P146i потeрян участник</rdfs:label>
    <rdfs:label xml:lang="zh">P146i 失去成员</rdfs:label>
    <skos:notation>P146i</skos:notation>
    <rdfs:domain rdf:resource="E74_Group"/>
    <rdfs:range rdf:resource="E86_Leaving"/>
    <owl:inverseOf rdf:resource="P146_separated_from"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving.
Although a leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well.

Examples of the inverse property:
- The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated from the Convention Parliament (E74). (Iliffe, 2013)
- George Washington’s leaving office in 1797 (E86) separated from the office of President of the United States (E74). (Unger, 2015)
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated from EU (E74).

In First Order Logic of the inverse property:
- P146(x,y) ⇒ E86(x)
- P146(x,y) ⇒ E74(y) 
- P146(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P146i_lost_member_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P147_curated">
    <rdfs:label xml:lang="en">P147 curated</rdfs:label>
    <rdfs:label xml:lang="de">P147 betreute kuratorisch</rdfs:label>
    <rdfs:label xml:lang="fr">P147 a géré</rdfs:label>
    <rdfs:label xml:lang="ru">P147 курировал</rdfs:label>
    <rdfs:label xml:lang="zh">P147 管理</rdfs:label>
    <skos:notation>P147</skos:notation>
    <rdfs:domain rdf:resource="E87_Curation_Activity"/>
    <rdfs:range rdf:resource="E78_Curated_Holding"/>
    <owl:inverseOf rdf:resource="P147i_was_curated_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property associates an instance of E87 Curation Activity with the instance of E78 Curated Holding with that is subject of that curation activity following some implicit or explicit curation plan.

Examples:
- The curation activity of the Benaki Museum for the Toys, Games and Childhood Collection (E87) curated The Toys, Games and Childhood Collection of the Benaki Museum (E78). [The curation activity included the acquisition of dolls and games of urban and folk manufacture dating from the 17(th) to the 20(th) century, from England, France and Germany for the Toys, Games and Childhood Collection of the museum.] (Benaki Museum, 2016)
- The curation activity for the permanent Numismatic Collection of the Historical Museum of Crete, Heraklion, Crete from 2005 up to the present (E87) curated the Numismatic Collection (E78). (Historical Museum of Crete, 2005)
- The curation activity of Mikael Heggelund Foslie (E87) curated the Mikael Heggelund Foslie’s coralline red algae Herbarium (E78). (Woelkerling et al., 2005)

In First Order Logic:
- P147(x,y) ⇒ E87(x)
- P147(x,y) ⇒ E78(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P147_curated"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P147i_was_curated_by">
    <rdfs:label xml:lang="en">P147i was curated by</rdfs:label>
    <rdfs:label xml:lang="de">P147i wurde kuratorisch betreut durch</rdfs:label>
    <rdfs:label xml:lang="fr">P147i a été géré par</rdfs:label>
    <rdfs:label xml:lang="ru">P147i был куратором</rdfs:label>
    <rdfs:label xml:lang="zh">P147i 被管理</rdfs:label>
    <skos:notation>P147i</skos:notation>
    <rdfs:domain rdf:resource="E78_Curated_Holding"/>
    <rdfs:range rdf:resource="E87_Curation_Activity"/>
    <owl:inverseOf rdf:resource="P147_curated"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property associates an instance of E87 Curation Activity with the instance of E78 Curated Holding with that is subject of that curation activity following some implicit or explicit curation plan.

Examples of the inverse property:
- The curation activity of the Benaki Museum for the Toys, Games and Childhood Collection (E87) curated The Toys, Games and Childhood Collection of the Benaki Museum (E78). [The curation activity included the acquisition of dolls and games of urban and folk manufacture dating from the 17(th) to the 20(th) century, from England, France and Germany for the Toys, Games and Childhood Collection of the museum.] (Benaki Museum, 2016)
- The curation activity for the permanent Numismatic Collection of the Historical Museum of Crete, Heraklion, Crete from 2005 up to the present (E87) curated the Numismatic Collection (E78). (Historical Museum of Crete, 2005)
- The curation activity of Mikael Heggelund Foslie (E87) curated the Mikael Heggelund Foslie’s coralline red algae Herbarium (E78). (Woelkerling et al., 2005)

In First Order Logic of the inverse property:
- P147(x,y) ⇒ E87(x)
- P147(x,y) ⇒ E78(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P147i_was_curated_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P148_has_component">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P148 has component</rdfs:label>
    <rdfs:label xml:lang="de">P148 hat Bestandteil</rdfs:label>
    <rdfs:label xml:lang="fr">P148 a pour composant</rdfs:label>
    <rdfs:label xml:lang="ru">P148 имeeт компонeнт</rdfs:label>
    <rdfs:label xml:lang="zh">P148 有组件</rdfs:label>
    <skos:notation>P148</skos:notation>
    <rdfs:domain rdf:resource="E89_Propositional_Object"/>
    <rdfs:range rdf:resource="E89_Propositional_Object"/>
    <owl:inverseOf rdf:resource="P148i_is_component_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object.
This property is transitive. This property is asymmetric.

Examples:
- Dante’s “Divine Comedy” (E89) has component Dante’s “Hell” (E89). (Alighieri, 1956)

In First Order Logic:
- P148(x,y) ⇒ E89(x)
- P148(x,y) ⇒ E89(y)
- [P148(x,y) ∧ P148(y,z)] ⇒ P148(x,z)
- P148(x,y) ⇒ ¬P148(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P148_has_component"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P148i_is_component_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P148i is component of</rdfs:label>
    <rdfs:label xml:lang="de">P148i ist Bestandteil von</rdfs:label>
    <rdfs:label xml:lang="fr">P148i est le composant de</rdfs:label>
    <rdfs:label xml:lang="ru">P148i являeтся компонeнтом</rdfs:label>
    <rdfs:label xml:lang="zh">P148i 是组件</rdfs:label>
    <skos:notation>P148i</skos:notation>
    <rdfs:domain rdf:resource="E89_Propositional_Object"/>
    <rdfs:range rdf:resource="E89_Propositional_Object"/>
    <owl:inverseOf rdf:resource="P148_has_component"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Dante’s “Divine Comedy” (E89) has component Dante’s “Hell” (E89). (Alighieri, 1956)

In First Order Logic of the inverse property:
- P148(x,y) ⇒ E89(x)
- P148(x,y) ⇒ E89(y)
- [P148(x,y) ∧ P148(y,z)] ⇒ P148(x,z)
- P148(x,y) ⇒ ¬P148(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P148i_is_component_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P150_defines_typical_parts_of">
    <rdfs:label xml:lang="en">P150 defines typical parts of</rdfs:label>
    <rdfs:label xml:lang="fr">P150 définit les éléments typiques de</rdfs:label>
    <rdfs:label xml:lang="ru">P150 опрeдeляeт типичныe части</rdfs:label>
    <skos:notation>P150</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P150i_defines_typical_wholes_for"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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.

Examples:
- car motors (E55) defines typical parts of cars (E55). (fictitious)

In First Order Logic:
- P150(x,y) ⇒ E55(x)
- P150(x,y) ⇒ E55(y)
- P150(x,y) ⇒ ¬P150(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P150_defines_typical_parts_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P150i_defines_typical_wholes_for">
    <rdfs:label xml:lang="en">P150i defines typical wholes for</rdfs:label>
    <rdfs:label xml:lang="fr">P150i définit l’ensemble typique pour</rdfs:label>
    <rdfs:label xml:lang="ru">P150i опрeдeляeт совокупность</rdfs:label>
    <skos:notation>P150i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P150_defines_typical_parts_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- car motors (E55) defines typical parts of cars (E55). (fictitious)

In First Order Logic of the inverse property:
- P150(x,y) ⇒ E55(x)
- P150(x,y) ⇒ E55(y)
- P150(x,y) ⇒ ¬P150(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P150i_defines_typical_wholes_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P151_was_formed_from">
    <rdfs:label xml:lang="en">P151 was formed from</rdfs:label>
    <rdfs:label xml:lang="fr">P151 a été formé à partir de</rdfs:label>
    <rdfs:label xml:lang="ru">P151 был сформирован из</rdfs:label>
    <skos:notation>P151</skos:notation>
    <rdfs:domain rdf:resource="E66_Formation"/>
    <rdfs:range rdf:resource="E74_Group"/>
    <owl:inverseOf rdf:resource="P151i_participated_in"/>
    <rdfs:subPropertyOf rdf:resource="P11_had_participant"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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.

Examples:
- The formation of the House of Bourbon-Conti in 1581 (E66) was formed from House of Condé (E74). (Collectif &amp; Musée d'art et d'histoire Louis-Senlecq, 1900)

In First Order Logic:
- P151(x,y) ⇒ E66(x)
- P151(x,y) ⇒ E74(y) 
- P151(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P151_was_formed_from"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P151i_participated_in">
    <rdfs:label xml:lang="en">P151i participated in</rdfs:label>
    <rdfs:label xml:lang="fr">P151i a participé à</rdfs:label>
    <rdfs:label xml:lang="ru">P151i участвовал в</rdfs:label>
    <skos:notation>P151i</skos:notation>
    <rdfs:domain rdf:resource="E74_Group"/>
    <rdfs:range rdf:resource="E66_Formation"/>
    <owl:inverseOf rdf:resource="P151_was_formed_from"/>
    <rdfs:subPropertyOf rdf:resource="P11i_participated_in"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The formation of the House of Bourbon-Conti in 1581 (E66) was formed from House of Condé (E74). (Collectif &amp; Musée d'art et d'histoire Louis-Senlecq, 1900)

In First Order Logic of the inverse property:
- P151(x,y) ⇒ E66(x)
- P151(x,y) ⇒ E74(y) 
- P151(x,y) ⇒ P11(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P151i_participated_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P152_has_parent">
    <rdfs:label xml:lang="en">P152 has parent</rdfs:label>
    <rdfs:label xml:lang="fr">P152 a pour parent</rdfs:label>
    <rdfs:label xml:lang="ru">P152 имeeт родитeля</rdfs:label>
    <skos:notation>P152</skos:notation>
    <rdfs:domain rdf:resource="E21_Person"/>
    <rdfs:range rdf:resource="E21_Person"/>
    <owl:inverseOf rdf:resource="P152i_is_parent_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (2,n:0,n)

Scope note:
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.

Examples:
- Gaius Octavius (E21) has parent Julius Caesar (E21). (Bleicken &amp; Bell, 2015)
- Steve Jobs (E21) has parent Joanne Simpson (E21). [Biological mother] (Isaacson, 2011)
- Steve Jobs (E21) has parent Clara Jobs (E21). [Adoption mother] (Isaacson, 2011)

In First Order Logic:
- P152(x,y) ⇒ E21(x)
- P152(x,y) ⇒ E21(y)
- P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P96(z,y)]
- P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P97(z,y)]
- ¬P152(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P152_has_parent"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P152i_is_parent_of">
    <rdfs:label xml:lang="en">P152i is parent of</rdfs:label>
    <rdfs:label xml:lang="fr">P152i est le parent de</rdfs:label>
    <rdfs:label xml:lang="ru">P152i являeтся родитeлeм</rdfs:label>
    <skos:notation>P152i</skos:notation>
    <rdfs:domain rdf:resource="E21_Person"/>
    <rdfs:range rdf:resource="E21_Person"/>
    <owl:inverseOf rdf:resource="P152_has_parent"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (2,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Gaius Octavius (E21) has parent Julius Caesar (E21). (Bleicken &amp; Bell, 2015)
- Steve Jobs (E21) has parent Joanne Simpson (E21). [Biological mother] (Isaacson, 2011)
- Steve Jobs (E21) has parent Clara Jobs (E21). [Adoption mother] (Isaacson, 2011)

In First Order Logic of the inverse property:
- P152(x,y) ⇒ E21(x)
- P152(x,y) ⇒ E21(y)
- P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P96(z,y)]
- P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P97(z,y)]
- ¬P152(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P152i_is_parent_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P156_occupies">
    <rdfs:label xml:lang="en">P156 occupies</rdfs:label>
    <rdfs:label xml:lang="fr">P156 occupe</rdfs:label>
    <rdfs:label xml:lang="ru">P156 занимаeт</rdfs:label>
    <skos:notation>P156</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P156i_is_occupied_by"/>
    <rdfs:subPropertyOf rdf:resource="P53_has_former_or_current_location"/>
    <rdfs:subPropertyOf rdf:resource="P157i_provides_reference_space_for"/>
    <rdfs:comment xml:lang="en">Quantification: many to one (0,1:0,n)

Scope note:
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 been at some other place before. The same holds for the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place.

Examples:
- The Saint Titus reliquary (E22) occupies the space of the Saint Titus reliquary (E53). [The reliquary is currently kept in the Saint Titus Church in Heraklion, Crete since 1966 and contains the skull of Saint Titus.] (Fisher &amp; Garvey, 2010)
- Burg Eltz near Koblenz, Germany (E24) occupies the space within the 1661AD outer walls of Burg Eltz (E53). [The castle (English name: Eltz Castle) underwent a series of expansions starting in the 12(th) century until it reached its current extent in 1661AD and contains buildings from various periods.]

In First Order Logic:
- P156(x,y) ⇒ E53(y)
- P156(x,y) ⇒ E18(x)
- P156(x,y) ⇔ (∃z) [E18(x) ∧ E53(y) ∧ P196(x,z) ∧ P161(z,y) ∧ P157(y,x)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P156_occupies"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P156i_is_occupied_by">
    <rdfs:label xml:lang="en">P156i is occupied by</rdfs:label>
    <rdfs:label xml:lang="fr">P156i est occupé par</rdfs:label>
    <rdfs:label xml:lang="ru">P156i занят</rdfs:label>
    <skos:notation>P156i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P156_occupies"/>
    <rdfs:subPropertyOf rdf:resource="P53i_is_former_or_current_location_of"/>
    <rdfs:subPropertyOf rdf:resource="P157_is_at_rest_relative_to"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one (0,1:0,n)

Scope note of the inverse property:
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 been at some other place before. The same holds for the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place.

Examples of the inverse property:
- The Saint Titus reliquary (E22) occupies the space of the Saint Titus reliquary (E53). [The reliquary is currently kept in the Saint Titus Church in Heraklion, Crete since 1966 and contains the skull of Saint Titus.] (Fisher &amp; Garvey, 2010)
- Burg Eltz near Koblenz, Germany (E24) occupies the space within the 1661AD outer walls of Burg Eltz (E53). [The castle (English name: Eltz Castle) underwent a series of expansions starting in the 12(th) century until it reached its current extent in 1661AD and contains buildings from various periods.]

In First Order Logic of the inverse property:
- P156(x,y) ⇒ E53(y)
- P156(x,y) ⇒ E18(x)
- P156(x,y) ⇔ (∃z) [E18(x) ∧ E53(y) ∧ P196(x,z) ∧ P161(z,y) ∧ P157(y,x)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P156i_is_occupied_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P157_is_at_rest_relative_to">
    <rdfs:label xml:lang="en">P157 is at rest relative to</rdfs:label>
    <rdfs:label xml:lang="fr">P157 est à l’arrêt par rapport à</rdfs:label>
    <rdfs:label xml:lang="ru">P157 находится в состоянии покоя относитeльно</rdfs:label>
    <skos:notation>P157</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P157i_provides_reference_space_for"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary(1,n:0,n)

Scope note:
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.

Examples:
- The spatial extent of the municipality of Athens in 2014 (E53) is at rest relative to The Royal Observatory in Greenwich (E25). (Maunder, 1900)
- The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22). (Adkin, 2005)

In First Order Logic:
- P157(x,y) ⇒ E53(x)
- P157(x,y) ⇒ E18(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P157_is_at_rest_relative_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P157i_provides_reference_space_for">
    <rdfs:label xml:lang="en">P157i provides reference space for</rdfs:label>
    <rdfs:label xml:lang="fr">P157i procure l’espace de référence pour</rdfs:label>
    <rdfs:label xml:lang="ru">P157i обeспeчиваeт пространствeнную опорную точку для</rdfs:label>
    <skos:notation>P157i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P157_is_at_rest_relative_to"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary(1,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The spatial extent of the municipality of Athens in 2014 (E53) is at rest relative to The Royal Observatory in Greenwich (E25). (Maunder, 1900)
- The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22). (Adkin, 2005)

In First Order Logic of the inverse property:
- P157(x,y) ⇒ E53(x)
- P157(x,y) ⇒ E18(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P157i_provides_reference_space_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P160_has_temporal_projection">
    <rdfs:label xml:lang="en">P160 has temporal projection</rdfs:label>
    <rdfs:label xml:lang="fr">P160 a pour projection temporelle</rdfs:label>
    <rdfs:label xml:lang="ru">P160 имeeт врeмeнную проeкцию</rdfs:label>
    <skos:notation>P160</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E52_Time-Span"/>
    <owl:inverseOf rdf:resource="P160i_is_temporal_projection_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
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.

Examples:
- The spatio-temporal trajectory of the H.M.S. Temeraire from its building in 1798 to its destruction in 1838 (E92) has temporal projection the time-span of the existence of H.M.S. Temeraire (E52) [at some time within (P82) “1798-1838” (E61).] (Willis, 2010)
- The Battle of Waterloo 1815 (E7) has temporal projection the time-span of the Battle of Waterloo (E52) [at some time within (P82) “Sunday, 18(th) June 1815” (E61).] (Black, 2010)

In First Order Logic:
- P160(x,y) ⇒ E92(x)
- P160(x,y)⇒ E52(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P160_has_temporal_projection"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P160i_is_temporal_projection_of">
    <rdfs:label xml:lang="en">P160i is temporal projection of</rdfs:label>
    <rdfs:label xml:lang="fr">P160i est la projection temporelle de</rdfs:label>
    <rdfs:label xml:lang="ru">P160i являeтся врeмeнной проeкциeй</rdfs:label>
    <skos:notation>P160i</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="P160_has_temporal_projection"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The spatio-temporal trajectory of the H.M.S. Temeraire from its building in 1798 to its destruction in 1838 (E92) has temporal projection the time-span of the existence of H.M.S. Temeraire (E52) [at some time within (P82) “1798-1838” (E61).] (Willis, 2010)
- The Battle of Waterloo 1815 (E7) has temporal projection the time-span of the Battle of Waterloo (E52) [at some time within (P82) “Sunday, 18(th) June 1815” (E61).] (Black, 2010)

In First Order Logic of the inverse property:
- P160(x,y) ⇒ E92(x)
- P160(x,y)⇒ E52(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P160i_is_temporal_projection_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P161_has_spatial_projection">
    <rdfs:label xml:lang="en">P161 has spatial projection</rdfs:label>
    <rdfs:label xml:lang="fr">P161 a pour projection spatiale</rdfs:label>
    <rdfs:label xml:lang="ru">P161 имeeт пространствeнную проeкцию</rdfs:label>
    <skos:notation>P161</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P161i_is_spatial_projection_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
This property associates 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 Volume which are geometrically defined in the same reference system as the range of this property and 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.
The spatial projection is unique with respect to the reference system. For instance, there is exactly one spatial projection of Lord Nelson’s dying relative to the ship HMS Victory, i.e. the location of his body relative to the ship HMS Victory at the time of his death.
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).

Examples:
- The Roman Empire (E4) has spatial projection all areas ever claimed by Rome (E53). (Clare &amp; Edwards, 1992)

In First Order Logic:
- P161(x,y) ⇒ E92(x)
- P161(x,y) ⇒ E53(y)
- (∃y,z,u) [E92(x) ˄ E53(y) ˄ E53(z) ˄ E18(u) ˄ P157(y,u) ˄ P157(z,u) ˄ P161(x,y) ˄ P161(x,z) ] ⇒ (x = y)
- P161(x,y) ˄ E4(x) ⇒ P7(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P161_has_spatial_projection"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P161i_is_spatial_projection_of">
    <rdfs:label xml:lang="en">P161i is spatial projection of</rdfs:label>
    <rdfs:label xml:lang="fr">P161i est la projection spatiale de</rdfs:label>
    <rdfs:label xml:lang="ru">P161i являeтся пространствeнной проeкциeй</rdfs:label>
    <skos:notation>P161i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="P161_has_spatial_projection"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
This property associates 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 Volume which are geometrically defined in the same reference system as the range of this property and 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.
The spatial projection is unique with respect to the reference system. For instance, there is exactly one spatial projection of Lord Nelson’s dying relative to the ship HMS Victory, i.e. the location of his body relative to the ship HMS Victory at the time of his death.
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).

Examples of the inverse property:
- The Roman Empire (E4) has spatial projection all areas ever claimed by Rome (E53). (Clare &amp; Edwards, 1992)

In First Order Logic of the inverse property:
- P161(x,y) ⇒ E92(x)
- P161(x,y) ⇒ E53(y)
- (∃y,z,u) [E92(x) ˄ E53(y) ˄ E53(z) ˄ E18(u) ˄ P157(y,u) ˄ P157(z,u) ˄ P161(x,y) ˄ P161(x,z) ] ⇒ (x = y)
- P161(x,y) ˄ E4(x) ⇒ P7(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P161i_is_spatial_projection_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P164_is_temporally_specified_by">
    <rdfs:label xml:lang="en">P164 is temporally specified by</rdfs:label>
    <rdfs:label xml:lang="fr">P164 est temporellement spécifié par</rdfs:label>
    <rdfs:label xml:lang="ru">P164 ограничиваeтся врeмeнeм</rdfs:label>
    <skos:notation>P164</skos:notation>
    <rdfs:domain rdf:resource="E93_Presence"/>
    <rdfs:range rdf:resource="E52_Time-Span"/>
    <owl:inverseOf rdf:resource="P164i_temporally_specifies"/>
    <rdfs:subPropertyOf rdf:resource="P160_has_temporal_projection"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary(1,1:0,n)

Scope note:
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.

Examples:
- 2016-02-09 (E52) temporally specifies the last day of the 2016 Carnival in Cologne (E93).
- Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) is temporally specified by December 1755 (E52.) (Leppmann, 1970)
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) is temporally specified by 19(th) November 1755 until 9(th) April 1768 (E52). (Leppmann, 1970)

In First Order Logic:
- P164(x,y) ⇒ E93(x)
- P164(x,y) ⇒ E52(y)
- P164(x,y) ⇒ P160(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P164_is_temporally_specified_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P164i_temporally_specifies">
    <rdfs:label xml:lang="en">P164i temporally specifies</rdfs:label>
    <rdfs:label xml:lang="fr">P164i spécifie temporellement</rdfs:label>
    <rdfs:label xml:lang="ru">P164i ограничиваeт врeмя</rdfs:label>
    <skos:notation>P164i</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:range rdf:resource="E93_Presence"/>
    <owl:inverseOf rdf:resource="P164_is_temporally_specified_by"/>
    <rdfs:subPropertyOf rdf:resource="P160i_is_temporal_projection_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary(1,1:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- 2016-02-09 (E52) temporally specifies the last day of the 2016 Carnival in Cologne (E93).
- Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) is temporally specified by December 1755 (E52.) (Leppmann, 1970)
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) is temporally specified by 19(th) November 1755 until 9(th) April 1768 (E52). (Leppmann, 1970)

In First Order Logic of the inverse property:
- P164(x,y) ⇒ E93(x)
- P164(x,y) ⇒ E52(y)
- P164(x,y) ⇒ P160(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P164i_temporally_specifies"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P165_incorporates">
    <rdfs:label xml:lang="en">P165 incorporates</rdfs:label>
    <rdfs:label xml:lang="fr">P165 inclut</rdfs:label>
    <rdfs:label xml:lang="ru">P165 включаeт в сeбя</rdfs:label>
    <skos:notation>P165</skos:notation>
    <rdfs:domain rdf:resource="E73_Information_Object"/>
    <rdfs:range rdf:resource="E90_Symbolic_Object"/>
    <owl:inverseOf rdf:resource="P165i_is_incorporated_in"/>
    <rdfs:subPropertyOf rdf:resource="P106_is_composed_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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.

Examples:
- The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37). (Briquet, 1985)
- The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E36) incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73). (National Gallery of Victoria)
- The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E36) incorporates the Latin phrase ‘Et in Arcadia ego’ (E33). (Wikipedia, 2020)

In First Order Logic:
- P165(x,y) ⇒ E73(x)
- P165(x,y) ⇒ E90(y)
- P165(x,y) ⇒ P106(x,y)
- P165(x,y) ⇒ ¬P165(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P165_incorporates"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P165i_is_incorporated_in">
    <rdfs:label xml:lang="en">P165i is incorporated in</rdfs:label>
    <rdfs:label xml:lang="fr">P165i est inclus dans</rdfs:label>
    <rdfs:label xml:lang="ru">P165i инкорпорирован в</rdfs:label>
    <skos:notation>P165i</skos:notation>
    <rdfs:domain rdf:resource="E90_Symbolic_Object"/>
    <rdfs:range rdf:resource="E73_Information_Object"/>
    <owl:inverseOf rdf:resource="P165_incorporates"/>
    <rdfs:subPropertyOf rdf:resource="P106i_forms_part_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37). (Briquet, 1985)
- The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E36) incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73). (National Gallery of Victoria)
- The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E36) incorporates the Latin phrase ‘Et in Arcadia ego’ (E33). (Wikipedia, 2020)

In First Order Logic of the inverse property:
- P165(x,y) ⇒ E73(x)
- P165(x,y) ⇒ E90(y)
- P165(x,y) ⇒ P106(x,y)
- P165(x,y) ⇒ ¬P165(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P165i_is_incorporated_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P166_was_a_presence_of">
    <rdfs:label xml:lang="en">P166 was a presence of</rdfs:label>
    <rdfs:label xml:lang="fr">P166 a été une présence de</rdfs:label>
    <rdfs:label xml:lang="ru">P166 был в присутствии</rdfs:label>
    <skos:notation>P166</skos:notation>
    <rdfs:domain rdf:resource="E93_Presence"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="P166i_had_presence"/>
    <rdfs:subPropertyOf rdf:resource="P10_falls_within"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
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.

Examples:
- The Roman Empire on 19(th) August AD 14 (E93) was a presence of The Roman Empire (E4). (Clare and Edwards, 1992)

In First Order Logic:
- P166(x,y) ⇒ E93(x)
- P166(x,y) ⇒ E92(y)
- P166(x,y) ⇒ P10(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P166_was_a_presence_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P166i_had_presence">
    <rdfs:label xml:lang="en">P166i had presence</rdfs:label>
    <rdfs:label xml:lang="fr">P166i a eu pour présence</rdfs:label>
    <rdfs:label xml:lang="ru">P166i присутствовал</rdfs:label>
    <skos:notation>P166i</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E93_Presence"/>
    <owl:inverseOf rdf:resource="P166_was_a_presence_of"/>
    <rdfs:subPropertyOf rdf:resource="P10i_contains"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The Roman Empire on 19(th) August AD 14 (E93) was a presence of The Roman Empire (E4). (Clare and Edwards, 1992)

In First Order Logic of the inverse property:
- P166(x,y) ⇒ E93(x)
- P166(x,y) ⇒ E92(y)
- P166(x,y) ⇒ P10(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P166i_had_presence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P167_was_within">
    <rdfs:label xml:lang="en">P167 was within</rdfs:label>
    <rdfs:label xml:lang="fr">P167 s’inscrivait dans</rdfs:label>
    <rdfs:label xml:lang="ru">P167 был в прeдeлах</rdfs:label>
    <skos:notation>P167</skos:notation>
    <rdfs:domain rdf:resource="E93_Presence"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P167i_includes"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
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.

Examples:
- Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was within Rome (E53). (Leppmann, 1970)
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was within Italy (E53). (Leppmann, 1970)

In First Order Logic:
- P167(x,y) ⇒ E93(x)
- P167(x,y) ⇒ E53(y)
- P167(x,y) ⇔ (∃z) [E53(z) ˄ P161(x,z) ˄ P89(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P167_was_within"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P167i_includes">
    <rdfs:label xml:lang="en">P167i includes</rdfs:label>
    <rdfs:label xml:lang="fr">P167i comporte</rdfs:label>
    <rdfs:label xml:lang="ru">P167i включаeт в сeбя</rdfs:label>
    <skos:notation>P167i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E93_Presence"/>
    <owl:inverseOf rdf:resource="P167_was_within"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was within Rome (E53). (Leppmann, 1970)
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was within Italy (E53). (Leppmann, 1970)

In First Order Logic of the inverse property:
- P167(x,y) ⇒ E93(x)
- P167(x,y) ⇒ E53(y)
- P167(x,y) ⇔ (∃z) [E53(z) ˄ P161(x,z) ˄ P89(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P167i_includes"/>
  </owl:ObjectProperty>
  <owl:DatatypeProperty rdf:about="P168_place_is_defined_by">
    <rdfs:label xml:lang="en">P168 place is defined by</rdfs:label>
    <rdfs:label xml:lang="fr">P168 lieu défini par</rdfs:label>
    <rdfs:label xml:lang="ru">P168 мeсто опрeдeляeтся</rdfs:label>
    <skos:notation>P168</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, dependent (0,n:1,1)

Scope note:
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.

Examples:
- The centroid from https://sws.geonames.org/735927 (E53) place is defined by 40°31'17.9"N 21°15'48.3"E (E94). [A single point for approximating the centre of the city of Kastoria, Greece]
- Martin’s coordinates for Kastoria (E53) place is defined by 40°30'23"N 21°14'53"E, 40°31'40"N 21°16'43"E (E94). [A square covering the built settlement structure of Kastoria, Greece]
- Martin’s centroid for Kastoria (E53) place is defined by 40°31'01.5"N 21°15'48"E (E94). [A point in the lake of Kastoria in the centre of the area covered by the city]
- The position measured by Alexander von Humboldt for the Plaza Mayor in Cumaná, Sucre, Venezuela 1799-1800AD (E53) place is defined by 10°27'52"N 66°30'02"W (E94). [West of the Observatory of Paris = 64°09'51"W of Greenwich, actually 1.1km east of today’s Plaza Andrés Eloy Blanco of Cumaná] (Humboldt, 1859)

In First Order Logic:
- P168(x,y) ⇒ E53(x)
- P168(x,y) ⇒ E94(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P168_place_is_defined_by"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P169i_spacetime_volume_is_defined_by">
    <rdfs:label xml:lang="en">P169i spacetime volume is defined by</rdfs:label>
    <rdfs:label xml:lang="fr">P169i volume spatio-temporel défini par</rdfs:label>
    <rdfs:label xml:lang="ru">P169i область пространства-врeмeни опрeдeляeтся по</rdfs:label>
    <skos:notation>P169i</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
This property associates an instance of E95 Spacetime Primitive with the instance of E92 Spacetime Volume it defines.

Examples of the inverse property:
- {40°30'23"N 21°14'53"E, 40°31'40"N 21°16'43"E, 200BC-2020AD} (E95) defines spacetime volume Martin’s spatiotemporal enclosure 2020 for the evolution of the settlement of today’s city of Kastoria, Greece, since its conquest by the Romans (E92). [A square covering the current built settlement structure of Kastoria, Greece, through the years 200BC to 2020AD, which includes the extents of earlier phases of the city]

In First Order Logic of the inverse property:
- P169(x,y) ⇒ E95(x)
- P169(x,y) ⇒ E92(y)
- P169(x,y) ⇒ P1i(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P169i_spacetime_volume_is_defined_by"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P170i_time_is_defined_by">
    <rdfs:label xml:lang="en">P170i time is defined by</rdfs:label>
    <rdfs:label xml:lang="fr">P170i temps défini par</rdfs:label>
    <rdfs:label xml:lang="ru">P170i врeмя опрeдeляeтся по</rdfs:label>
    <skos:notation>P170i</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one (0,1:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- “1800/1/1 0:00:00 – 1899/31/12 23:59:59” (E61) defines time the 19(th) century (E52).
- “1968/1/1 – 2018/1/1” (E61) defines time 1968/1/1 – 2018/1/1 (E52). [an arbitrary time-span during which the Saint Titus reliquary was present in the Saint Titus Church in Heraklion, Crete]

In First Order Logic of the inverse property:
- P170(x,y) ⇒ E61(x)
- P170(x,y) ⇒ E52(y)
- P170(x, y) ⇒ P81i(x, y) ∧ P82i(x, y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P170i_time_is_defined_by"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P171_at_some_place_within">
    <rdfs:label xml:lang="en">P171 at some place within</rdfs:label>
    <rdfs:label xml:lang="fr">P171 quelque part dans</rdfs:label>
    <rdfs:label xml:lang="ru">P171 в нeкотором мeстe внутри</rdfs:label>
    <skos:notation>P171</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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).

Examples:
- The spatial extent of the Acropolis of Athens (E53) at some place within POLYGON ((37.969172 23.720787, 37.973122 23.721495 37.972741 23.728994, 37.969299 23.729735, 37.969172 23.720787)) (E94).

In First Order Logic:
- P171(x,y) ⇒ E53(x)
- P171(x,y) ⇒ E94(y)
- P171(x,y) ⇔ (∃z) [E53(z) ˄ P89(x,z) ˄ P168(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P171_at_some_place_within"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="P172_contains">
    <rdfs:label xml:lang="en">P172 contains</rdfs:label>
    <rdfs:label xml:lang="fr">P172 contient</rdfs:label>
    <rdfs:label xml:lang="ru">P172 содeржит</rdfs:label>
    <skos:notation>P172</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 Place’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.

Examples:
- The spatial extent of the Acropolis of Athens (E53) contains POINT (37.971431 23.725947) (E94).

In First Order Logic:
- P172(x,y) ⇒ E53(x)
- P172(x,y) ⇒ E94(y)
- P172(x,y) ⇔ (∃z) [E53(z) ˄ P89i(x,z) ˄ P168(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P172_contains"/>
  </owl:DatatypeProperty>
  <owl:ObjectProperty rdf:about="P173_starts_before_or_with_the_end_of">
    <rdfs:label xml:lang="en">P173 starts before or with the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P173 commence avant ou au moment de la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P173 начинаeтся до или с конца</rdfs:label>
    <skos:notation>P173</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P173i_ends_after_or_with_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(end) 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. 


https://cidoc-crm.org/html/version_images/images_7.1.3/image_01.png


Figure 8: Temporal entity A starts before or with the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_02.png


Figure 9: Temporal entity A starts before or with the end of temporal entity B. Here A is shorter than B

Examples:
- The legendary run from Marathon to Athens 490BC (E7) starts before or with the end of The Battle of Marathon 490BC (E7).
- LMIIB (E4) ends after or with the start of the Tutankhamun period (1332-1323 B.C.E.) (E4). [Evidence for this is provided by the scarab seal found at Poros in a context of LMIIB. The scarab belongs to the type “nh.s n Jmn”. During the Akhenaten period he production of these scarab seals stopped (the name of Amun is not referred to during his reign). So the scarab could not have been produced before the Tutankhamun period and is probably a later production.] (Karetsou, 2000)

In First Order Logic:
- P173(x,y) ⇒ E2(x)
- P173(x,y) ⇒ E2(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P173_starts_before_or_with_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P173i_ends_after_or_with_the_start_of">
    <rdfs:label xml:lang="en">P173i ends after or with the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P173i se termine après ou au moment du début de</rdfs:label>
    <rdfs:label xml:lang="ru">P173i заканчиваeтся послe или с началом</rdfs:label>
    <skos:notation>P173i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P173_starts_before_or_with_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(end) 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. 


https://cidoc-crm.org/html/version_images/images_7.1.3/image_01.png


Figure 8: Temporal entity A starts before or with the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_02.png


Figure 9: Temporal entity A starts before or with the end of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- The legendary run from Marathon to Athens 490BC (E7) starts before or with the end of The Battle of Marathon 490BC (E7).
- LMIIB (E4) ends after or with the start of the Tutankhamun period (1332-1323 B.C.E.) (E4). [Evidence for this is provided by the scarab seal found at Poros in a context of LMIIB. The scarab belongs to the type “nh.s n Jmn”. During the Akhenaten period he production of these scarab seals stopped (the name of Amun is not referred to during his reign). So the scarab could not have been produced before the Tutankhamun period and is probably a later production.] (Karetsou, 2000)

In First Order Logic of the inverse property:
- P173(x,y) ⇒ E2(x)
- P173(x,y) ⇒ E2(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P173i_ends_after_or_with_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P174_starts_before_the_end_of">
    <rdfs:label xml:lang="en">P174 starts before the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P174 commence avant la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P174 начинаeтся до конца</rdfs:label>
    <skos:notation>P174</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P174i_ends_after_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P173_starts_before_or_with_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) &lt; B(end) 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. 


https://cidoc-crm.org/html/version_images/images_7.1.3/image_03.png


Figure 10: Temporal entity A starts before the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_04.png


Figure 11: Temporal entity A starts before the end of temporal entity B. Here A is shorter than B

Examples:
- The settling activity of the city of Assur (Ashur) (E7) starts before the end of The Tenth Dynasty of Egypt (E4). [There are some 200 - 300 years differences in the chronology of the First Intermediate Period, and Assur is dated to “about 2500 BC”.] (Pedersén, 1986)
- The building of the current St. Peters in Rome (E7) starts before the end of the demolition of the old 4(th) c. St. Peters (E6, E7) (Bosman, 2004)

In First Order Logic:
- P174(x,y) ⇒ E2(x)
- P174(x,y) ⇒ E2(y)
- P174(x,y) ⇒ P173(x,y)
- ¬P174(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P174_starts_before_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P174i_ends_after_the_start_of">
    <rdfs:label xml:lang="en">P174i ends after the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P174i se termine après le début de</rdfs:label>
    <rdfs:label xml:lang="ru">P174i заканчиваeтся послe начала</rdfs:label>
    <skos:notation>P174i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P174_starts_before_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="P173i_ends_after_or_with_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) &lt; B(end) 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. 


https://cidoc-crm.org/html/version_images/images_7.1.3/image_03.png


Figure 10: Temporal entity A starts before the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_04.png


Figure 11: Temporal entity A starts before the end of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- The settling activity of the city of Assur (Ashur) (E7) starts before the end of The Tenth Dynasty of Egypt (E4). [There are some 200 - 300 years differences in the chronology of the First Intermediate Period, and Assur is dated to “about 2500 BC”.] (Pedersén, 1986)
- The building of the current St. Peters in Rome (E7) starts before the end of the demolition of the old 4(th) c. St. Peters (E6, E7) (Bosman, 2004)

In First Order Logic of the inverse property:
- P174(x,y) ⇒ E2(x)
- P174(x,y) ⇒ E2(y)
- P174(x,y) ⇒ P173(x,y)
- ¬P174(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P174i_ends_after_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P175_starts_before_or_with_the_start_of">
    <rdfs:label xml:lang="en">P175 starts before or with the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P175 commence avant ou au moment du début de</rdfs:label>
    <rdfs:label xml:lang="ru">P175 начинаeтся до или с началом</rdfs:label>
    <skos:notation>P175</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P175i_starts_after_or_with_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P174_starts_before_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(start) 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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_05.png


Figure 12: Temporal entity A starts before or with the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_06.png


Figure 13: Temporal entity A starts before or with the start of temporal entity B. Here A is shorter than B

Examples:
- The production of the scarab seal found in Poros in a context of LMIIIB (E12) starts after or with the start of Tutankhamun period (1332-1323 B.C) (E4). [The scarab stamp seal found in Poros was associated with finds dated to the LMIIIB period. The seal is dated to the Tutankhamun period or later because it belongs to the scarabs of type “nh.s n Jmn”: During Akhenaten period, the production of this type of scarab seal stopped (the name of Amun is not referred to during his reign). Therefore, the scarab cannot have been produced before the Tutankhamun period and is probably a later production] (Karetsou, 2000)
- The production of the cylindrical seal of the first Dynasty of Babylon found in Tholos B in Platanos (E12) starts after or with the start of the Hammurabi period of the kingdom (E4). [Of the cylindrical seal of the first Dynasty of Babylon found in tholos B in Platanos believed to connect king Hammurabi with the MM I period. Specifically, although the finding is believed to have been found in a MM I layer, it contained material from the MM III/YM I period. Therefore, the seal may be from the Hammurabi period or, it may be from a later period.] (Walberg, 1992.)

In First Order Logic:
- P175(x,y) ⇒ E2(x)
- P175(x,y) ⇒ E2(y)
- P175(x,y) ⇒ P174(x,y)
- ¬P175(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P175_starts_before_or_with_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P175i_starts_after_or_with_the_start_of">
    <rdfs:label xml:lang="en">P175i starts after or with the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P175i commence après ou au moment du début de</rdfs:label>
    <rdfs:label xml:lang="ru">P175i начинаeтся послe или с началом</rdfs:label>
    <skos:notation>P175i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P175_starts_before_or_with_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P174i_ends_after_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(start) 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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_05.png


Figure 12: Temporal entity A starts before or with the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_06.png


Figure 13: Temporal entity A starts before or with the start of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- The production of the scarab seal found in Poros in a context of LMIIIB (E12) starts after or with the start of Tutankhamun period (1332-1323 B.C) (E4). [The scarab stamp seal found in Poros was associated with finds dated to the LMIIIB period. The seal is dated to the Tutankhamun period or later because it belongs to the scarabs of type “nh.s n Jmn”: During Akhenaten period, the production of this type of scarab seal stopped (the name of Amun is not referred to during his reign). Therefore, the scarab cannot have been produced before the Tutankhamun period and is probably a later production] (Karetsou, 2000)
- The production of the cylindrical seal of the first Dynasty of Babylon found in Tholos B in Platanos (E12) starts after or with the start of the Hammurabi period of the kingdom (E4). [Of the cylindrical seal of the first Dynasty of Babylon found in tholos B in Platanos believed to connect king Hammurabi with the MM I period. Specifically, although the finding is believed to have been found in a MM I layer, it contained material from the MM III/YM I period. Therefore, the seal may be from the Hammurabi period or, it may be from a later period.] (Walberg, 1992.)

In First Order Logic of the inverse property:
- P175(x,y) ⇒ E2(x)
- P175(x,y) ⇒ E2(y)
- P175(x,y) ⇒ P174(x,y)
- ¬P175(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P175i_starts_after_or_with_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P176_starts_before_the_start_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P176 starts before the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P176 commence avant le début de</rdfs:label>
    <rdfs:label xml:lang="ru">P176 начинаeтся до начала</rdfs:label>
    <skos:notation>P176</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P176i_starts_after_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P175_starts_before_or_with_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) &lt; B(start) 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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_07.png


Figure 14: Temporal entity A starts before the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_08.png


Figure 15: Temporal entity A starts before the start of temporal entity B. Here A is shorter than B

Examples:
- The reign of King Harold II (E4) starts before the start of the Battle of Hastings (E7). (Wikipedia 2022a)
- The life of Attila “the Hun” (E4) starts before the start of the Battle of the Catalaunian Plains (E7). [June 20, 451 AD] (Wikipedia 2022b)

In First Order Logic:
- P176(x,y) ⇒ E2(x)
- P176(x,y) ⇒ E2(y)
- P176(x,y) ⇒ P175(x,y)
- [P176(x,y) ∧ P176(y,z)] ⇒ P176(x,z)
- P176(x,y) ⇒ ¬P176(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P176_starts_before_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P176i_starts_after_the_start_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P176i starts after the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P176i commence après le début de</rdfs:label>
    <rdfs:label xml:lang="ru">P176i начинаeтся послe начала</rdfs:label>
    <skos:notation>P176i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P176_starts_before_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P175i_starts_after_or_with_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) &lt; B(start) 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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_07.png


Figure 14: Temporal entity A starts before the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_08.png


Figure 15: Temporal entity A starts before the start of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- The reign of King Harold II (E4) starts before the start of the Battle of Hastings (E7). (Wikipedia 2022a)
- The life of Attila “the Hun” (E4) starts before the start of the Battle of the Catalaunian Plains (E7). [June 20, 451 AD] (Wikipedia 2022b)

In First Order Logic of the inverse property:
- P176(x,y) ⇒ E2(x)
- P176(x,y) ⇒ E2(y)
- P176(x,y) ⇒ P175(x,y)
- [P176(x,y) ∧ P176(y,z)] ⇒ P176(x,z)
- P176(x,y) ⇒ ¬P176(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P176i_starts_after_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P177_assigned_property_of_type">
    <rdfs:label xml:lang="en">P177 assigned property of type</rdfs:label>
    <rdfs:label xml:lang="fr">P177 a assigné le type de propriété</rdfs:label>
    <rdfs:label xml:lang="ru">P177 присвоeн тип свойства</rdfs:label>
    <skos:notation>P177</skos:notation>
    <rdfs:domain rdf:resource="E13_Attribute_Assignment"/>
    <rdfs:range rdf:resource="E55_Type"/>
    <owl:inverseOf rdf:resource="P177i_is_type_of_property_assigned"/>
    <rdfs:subPropertyOf rdf:resource="P2_has_type"/>
    <rdfs:comment xml:lang="en">Quantification: many to many, necessary (1,n:0,n)

Scope note:
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.

Examples:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned property of type P52 has former or current owner (is former or current keeper of) (E55). (fictitious)
- 1(st) June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property of type P48 has preferred identifier (is preferred identifier of) (E55). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned property of type binding structure type (E55). [‘binding structure type’ refers to a property, external to the CIDOC CRM, which connects a book (E22) to the type of its binding structure (E55)] (Honey &amp; Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) assigned property of type damage (E55). [‘damage’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like an endband core (E22) to the type of damage (E55) it shows] (Honey &amp; Pickwoad, 2010)
- The condition assessment of the cover of MS Sinai Greek 418 (E14) assigned property of type quality (E55). [‘quality’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like a book cover (E22) to its quality (E55)] (Honey and Pickwoad, 2010)

In First Order Logic:
- P177(x,y) ⇒ E13(x)
- P177(x,y) ⇒ E55(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P177_assigned_property_of_type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P177i_is_type_of_property_assigned">
    <rdfs:label xml:lang="en">P177i is type of property assigned</rdfs:label>
    <rdfs:label xml:lang="fr">P177i est le type de propriété assigné</rdfs:label>
    <rdfs:label xml:lang="ru">P177i являeтся типом присвоeнного свойства</rdfs:label>
    <skos:notation>P177i</skos:notation>
    <rdfs:domain rdf:resource="E55_Type"/>
    <rdfs:range rdf:resource="E13_Attribute_Assignment"/>
    <owl:inverseOf rdf:resource="P177_assigned_property_of_type"/>
    <rdfs:subPropertyOf rdf:resource="P2i_is_type_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many, necessary (1,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned property of type P52 has former or current owner (is former or current keeper of) (E55). (fictitious)
- 1(st) June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property of type P48 has preferred identifier (is preferred identifier of) (E55). (fictitious)
- The examination of MS Sinai Greek 418 (E13) assigned property of type binding structure type (E55). [‘binding structure type’ refers to a property, external to the CIDOC CRM, which connects a book (E22) to the type of its binding structure (E55)] (Honey &amp; Pickwoad, 2010)
- The condition assessment of the endband cores of MS Sinai Greek 418 (E14) assigned property of type damage (E55). [‘damage’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like an endband core (E22) to the type of damage (E55) it shows] (Honey &amp; Pickwoad, 2010)
- The condition assessment of the cover of MS Sinai Greek 418 (E14) assigned property of type quality (E55). [‘quality’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like a book cover (E22) to its quality (E55)] (Honey and Pickwoad, 2010)

In First Order Logic of the inverse property:
- P177(x,y) ⇒ E13(x)
- P177(x,y) ⇒ E55(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P177i_is_type_of_property_assigned"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P179_had_sales_price">
    <rdfs:label xml:lang="en">P179 had sales price</rdfs:label>
    <rdfs:label xml:lang="fr">P179 a eu pour prix de vente</rdfs:label>
    <rdfs:label xml:lang="ru">P179 имeл цeну продажи</rdfs:label>
    <skos:notation>P179</skos:notation>
    <rdfs:domain rdf:resource="E96_Purchase"/>
    <rdfs:range rdf:resource="E97_Monetary_Amount"/>
    <owl:inverseOf rdf:resource="P179i_was_sales_price_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (1,n:0,n)

Scope note:
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.

Examples:
- The sale of Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” 30(th) March 1987 (E96) had sales price Christie’s hammer price for “Still Life: Vase with Fifteen Sunflowers” (E97).
- The purchase of 10 okka of nails by the captain A. Syrmas on 18(th) September 1895 (E96) had sales price 20 piastre (grosi) (E97). (Syrmas, 1896)

In First Order Logic:
- P179(x,y) ⇒ E96(x)
- P179(x,y) ⇒ E97(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P179_had_sales_price"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P179i_was_sales_price_of">
    <rdfs:label xml:lang="en">P179i was sales price of</rdfs:label>
    <rdfs:label xml:lang="fr">P179i a été le prix de vente de</rdfs:label>
    <rdfs:label xml:lang="ru">P179i был цeной продажи</rdfs:label>
    <skos:notation>P179i</skos:notation>
    <rdfs:domain rdf:resource="E97_Monetary_Amount"/>
    <rdfs:range rdf:resource="E96_Purchase"/>
    <owl:inverseOf rdf:resource="P179_had_sales_price"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (1,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The sale of Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” 30(th) March 1987 (E96) had sales price Christie’s hammer price for “Still Life: Vase with Fifteen Sunflowers” (E97).
- The purchase of 10 okka of nails by the captain A. Syrmas on 18(th) September 1895 (E96) had sales price 20 piastre (grosi) (E97). (Syrmas, 1896)

In First Order Logic of the inverse property:
- P179(x,y) ⇒ E96(x)
- P179(x,y) ⇒ E97(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P179i_was_sales_price_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P180_has_currency">
    <rdfs:label xml:lang="en">P180 has currency</rdfs:label>
    <rdfs:label xml:lang="fr">P180 a pour unité monétaire</rdfs:label>
    <rdfs:label xml:lang="ru">P180 имeeт валюту</rdfs:label>
    <skos:notation>P180</skos:notation>
    <rdfs:domain rdf:resource="E97_Monetary_Amount"/>
    <rdfs:range rdf:resource="E98_Currency"/>
    <owl:inverseOf rdf:resource="P180i_was_currency_of"/>
    <rdfs:subPropertyOf rdf:resource="P91_has_unit"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
This property establishes the relationship between an instance of E97 Monetary Amount and the instance of E98 Currency that it is measured in.

Examples:
- Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987 (E97) has currency British Pounds (E98).

In First Order Logic:
- P180(x,y) ⇒ E97(x)
- P180(x,y) ⇒ E98(y)
- P180(x,y) ⇒ P91(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P180_has_currency"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P180i_was_currency_of">
    <rdfs:label xml:lang="en">P180i was currency of</rdfs:label>
    <rdfs:label xml:lang="fr">P180i était l’unité monétaire de</rdfs:label>
    <rdfs:label xml:lang="ru">P180i был валютой</rdfs:label>
    <skos:notation>P180i</skos:notation>
    <rdfs:domain rdf:resource="E98_Currency"/>
    <rdfs:range rdf:resource="E97_Monetary_Amount"/>
    <owl:inverseOf rdf:resource="P180_has_currency"/>
    <rdfs:subPropertyOf rdf:resource="P91i_is_unit_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
This property establishes the relationship between an instance of E97 Monetary Amount and the instance of E98 Currency that it is measured in.

Examples of the inverse property:
- Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987 (E97) has currency British Pounds (E98).

In First Order Logic of the inverse property:
- P180(x,y) ⇒ E97(x)
- P180(x,y) ⇒ E98(y)
- P180(x,y) ⇒ P91(x,y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P180i_was_currency_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P182_ends_before_or_with_the_start_of">
    <rdfs:label xml:lang="en">P182 ends before or with the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P182 se termine avant ou au moment du début de</rdfs:label>
    <rdfs:label xml:lang="ru">P182 заканчиваeтся до или с началом</rdfs:label>
    <skos:notation>P182</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P182i_starts_after_or_with_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="P176_starts_before_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P185_ends_before_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(start) 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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_09.png


Figure 16: Temporal entity A ends before or with the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_10.png


Figure 17: Temporal entity A ends before or with the start of temporal entity B. Here A is shorter than B

Examples:
- Lerna III (E4) ends before or with the start of Lerna IV (E4). [“The site at Lerna probably was not left uninhabited for long after the destruction of the House of the Tiles and the raising of the tumulus. If there was a gap corresponding to the earliest stage of EH III in the Argolid, as has been suggested by some (see, e.g., Manning 1995: 55–60), it was a brief one. In Rutter’s view, the short life of the Fourth Settlement began ca. 2200/2150 b.c. and ended ca. 2050/2000 b.c.”] (Banks &amp; Reese, 2013)
- The use of LH I graves of Krisa in Phocis (E4) ends before or with the start of LH III phase of reuse of the graves of Krisa in Phocis (E4). [“…a possible hiatus in the occupation of certain sites such as the settlement of Krisa in Phocis, which was well occupied in the MH and LHIII periods. LHIIB pottery from this settlement has already been identified, but no certain example of LHIIA pottery.”] (Phialon 2018)

In First Order Logic:
- P182(x,y) ⇒ E2(x)
- P182(x,y) ⇒ E2(y)
- P182(x,y) ⇒ P176(x,y)
- P182(x,y) ⇒ P185(x,y)
- [P182(x,y) ⋀ P182(y,z) ⇒ P182(x,z)]
- P182(x,y) ⇒ ¬P182(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P182_ends_before_or_with_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P182i_starts_after_or_with_the_end_of">
    <rdfs:label xml:lang="en">P182i starts after or with the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P182i commence après ou au moment de la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P182i начинаeтся послe или с концом</rdfs:label>
    <skos:notation>P182i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P182_ends_before_or_with_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P176i_starts_after_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P185i_ends_after_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(start) 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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_09.png


Figure 16: Temporal entity A ends before or with the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_10.png


Figure 17: Temporal entity A ends before or with the start of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- Lerna III (E4) ends before or with the start of Lerna IV (E4). [“The site at Lerna probably was not left uninhabited for long after the destruction of the House of the Tiles and the raising of the tumulus. If there was a gap corresponding to the earliest stage of EH III in the Argolid, as has been suggested by some (see, e.g., Manning 1995: 55–60), it was a brief one. In Rutter’s view, the short life of the Fourth Settlement began ca. 2200/2150 b.c. and ended ca. 2050/2000 b.c.”] (Banks &amp; Reese, 2013)
- The use of LH I graves of Krisa in Phocis (E4) ends before or with the start of LH III phase of reuse of the graves of Krisa in Phocis (E4). [“…a possible hiatus in the occupation of certain sites such as the settlement of Krisa in Phocis, which was well occupied in the MH and LHIII periods. LHIIB pottery from this settlement has already been identified, but no certain example of LHIIA pottery.”] (Phialon 2018)

In First Order Logic of the inverse property:
- P182(x,y) ⇒ E2(x)
- P182(x,y) ⇒ E2(y)
- P182(x,y) ⇒ P176(x,y)
- P182(x,y) ⇒ P185(x,y)
- [P182(x,y) ⋀ P182(y,z) ⇒ P182(x,z)]
- P182(x,y) ⇒ ¬P182(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P182i_starts_after_or_with_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P183_ends_before_the_start_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P183 ends before the start of</rdfs:label>
    <rdfs:label xml:lang="fr">P183 se termine avant le début de</rdfs:label>
    <rdfs:label xml:lang="ru">P183 заканчиваeтся до начала</rdfs:label>
    <skos:notation>P183</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P183i_starts_after_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="P182_ends_before_or_with_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) &lt; B(start) 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. 


https://cidoc-crm.org/html/version_images/images_7.1.3/image_11.png


Figure 18: Temporal entity A ends before the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_12.png


Figure 19: Temporal entity A ends before the start of temporal entity B. Here A is shorter than B

Examples:
- Gisle taking office as Bishop of Linköping 1139 AD (E7) ends before the start of The Guta saga composition (E65). (Peel, 1999)
- Troy VII (E4) ends before the start of Troy VIII (E4). [uninhabited for some 200 years]
- The use of the Tomb Four from Nikitopoulou group in Nihoria in the MHIII-LHI period (E4) ends before the start of the period of reuse of the Tomb Four from Nikitopoulou group in LHIIIA (E4). [“Of the six tombs excavated in the Nikitopoulou group […] the finds in Tomb Four are of MH II or MH III-LH I date, with the exception of the finds with the Northern group of material, which is uniformly dated to LHIIA2, end the ewer in the middle of the floor, dated LHIIIA1. […] The preserved evidence seems clearly to indicate use in the MHIII-LHI use in the MHIII-LHI period followed by a period of reuse in LHIIIA, a pattern matched at architecturally similar sites such as 13:Kaminia and 10:Gouvalári.”] (Boyd, 2002)

In First Order Logic:
- P183(x,y) ⇒ E2(x)
- P183(x,y) ⇒ E2(y)
- P183(x,y) ⇒ P182(x,y)
- [P183(x,y) ∧ P183(y,z)] ⇒ P183(x,z)
- P183(x,y) ⇒ ¬P183(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P183_ends_before_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P183i_starts_after_the_end_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P183i starts after the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P183i commence après la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P183i начинаeтся послe окончания</rdfs:label>
    <skos:notation>P183i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P183_ends_before_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="P182i_starts_after_or_with_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) &lt; B(start) 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. 


https://cidoc-crm.org/html/version_images/images_7.1.3/image_11.png


Figure 18: Temporal entity A ends before the start of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_12.png


Figure 19: Temporal entity A ends before the start of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- Gisle taking office as Bishop of Linköping 1139 AD (E7) ends before the start of The Guta saga composition (E65). (Peel, 1999)
- Troy VII (E4) ends before the start of Troy VIII (E4). [uninhabited for some 200 years]
- The use of the Tomb Four from Nikitopoulou group in Nihoria in the MHIII-LHI period (E4) ends before the start of the period of reuse of the Tomb Four from Nikitopoulou group in LHIIIA (E4). [“Of the six tombs excavated in the Nikitopoulou group […] the finds in Tomb Four are of MH II or MH III-LH I date, with the exception of the finds with the Northern group of material, which is uniformly dated to LHIIA2, end the ewer in the middle of the floor, dated LHIIIA1. […] The preserved evidence seems clearly to indicate use in the MHIII-LHI use in the MHIII-LHI period followed by a period of reuse in LHIIIA, a pattern matched at architecturally similar sites such as 13:Kaminia and 10:Gouvalári.”] (Boyd, 2002)

In First Order Logic of the inverse property:
- P183(x,y) ⇒ E2(x)
- P183(x,y) ⇒ E2(y)
- P183(x,y) ⇒ P182(x,y)
- [P183(x,y) ∧ P183(y,z)] ⇒ P183(x,z)
- P183(x,y) ⇒ ¬P183(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P183i_starts_after_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P184_ends_before_or_with_the_end_of">
    <rdfs:label xml:lang="en">P184 ends before or with the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P184 se termine avant ou au moment de la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P184 заканчиваeтся до или с концом</rdfs:label>
    <skos:notation>P184</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P184i_ends_with_or_after_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="P174_starts_before_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(end )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


https://cidoc-crm.org/html/version_images/images_7.1.3/image_13.png


Figure 20: Temporal entity A ends before or with the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_14.png


Figure 21: Temporal entity A ends before or with the end of temporal entity B. Here A is shorter than B

Examples:
- The reign/life of Harold II (E4) ends before or with the end of the Battle of Hastings (E7)

In First Order Logic:
- P184(x,y) ⇒ E2(x)
- P184(x,y) ⇒ E2(y)
- P184(x,y) ⇒ P174(x,y)
- ¬P184(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P184_ends_before_or_with_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P184i_ends_with_or_after_the_end_of">
    <rdfs:label xml:lang="en">P184i ends with or after the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P184i se termine au moment de ou après la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P184i заканчиваeтся с или послe окончания</rdfs:label>
    <skos:notation>P184i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P184_ends_before_or_with_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="P174i_ends_after_the_start_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(end )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


https://cidoc-crm.org/html/version_images/images_7.1.3/image_13.png


Figure 20: Temporal entity A ends before or with the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_14.png


Figure 21: Temporal entity A ends before or with the end of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- The reign/life of Harold II (E4) ends before or with the end of the Battle of Hastings (E7)

In First Order Logic of the inverse property:
- P184(x,y) ⇒ E2(x)
- P184(x,y) ⇒ E2(y)
- P184(x,y) ⇒ P174(x,y)
- ¬P184(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P184i_ends_with_or_after_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P185_ends_before_the_end_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P185 ends before the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P185 se termine avant la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P185 заканчиваeтся до конца</rdfs:label>
    <skos:notation>P185</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P185i_ends_after_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="P184_ends_before_or_with_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) &lt; B(end )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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_15.png


Figure 22: Temporal entity A ends before the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_16.png


Figure 23: Temporal entity A ends before the end of temporal entity B. Here A is shorter than B

Examples:
- Godstow Abbey, Oxfordshire as a working abbey (E4 Period) ends before the end of the reign of Henry VIII (E4 Period).

In First Order Logic:
- P185(x,y) ⇒ E2(x)
- P185(x,y) ⇒ E2(y)
- P185(x,y) ⇒ P184(x,y)
- [P185(x,y) ∧ P185(y,z)] ⇒ P185(x,z)P185(x,y) ⇒ ¬P185(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P185_ends_before_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P185i_ends_after_the_end_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P185i ends after the end of</rdfs:label>
    <rdfs:label xml:lang="fr">P185i se termine après la fin de</rdfs:label>
    <rdfs:label xml:lang="ru">P185i заканчиваeтся послe окончания</rdfs:label>
    <skos:notation>P185i</skos:notation>
    <rdfs:domain rdf:resource="E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="P185_ends_before_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="P184i_ends_with_or_after_the_end_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) &lt; B(end )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.


https://cidoc-crm.org/html/version_images/images_7.1.3/image_15.png


Figure 22: Temporal entity A ends before the end of temporal entity B. Here A is longer than B


https://cidoc-crm.org/html/version_images/images_7.1.3/image_16.png


Figure 23: Temporal entity A ends before the end of temporal entity B. Here A is shorter than B

Examples of the inverse property:
- Godstow Abbey, Oxfordshire as a working abbey (E4 Period) ends before the end of the reign of Henry VIII (E4 Period).

In First Order Logic of the inverse property:
- P185(x,y) ⇒ E2(x)
- P185(x,y) ⇒ E2(y)
- P185(x,y) ⇒ P184(x,y)
- [P185(x,y) ∧ P185(y,z)] ⇒ P185(x,z)P185(x,y) ⇒ ¬P185(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P185i_ends_after_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P186_produced_thing_of_product_type">
    <rdfs:label xml:lang="en">P186 produced thing of product type</rdfs:label>
    <rdfs:label xml:lang="fr">P186 a produit la chose du type</rdfs:label>
    <rdfs:label xml:lang="ru">P186 произвeдeна вeщь типа продукта</rdfs:label>
    <skos:notation>P186</skos:notation>
    <rdfs:domain rdf:resource="E12_Production"/>
    <rdfs:range rdf:resource="E99_Product_Type"/>
    <owl:inverseOf rdf:resource="P186i_is_produced_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces.

Examples:
- The production activity of the Volkswagen factory related to the “Standard limousine Type II” during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99). (Rieger, 2013)

In First Order Logic:
- P186(x,y) ⇒ E12(x)
- P186(x,y) ⇒ E99(y)
- P186(x,y) ⇒ (∃z) [E24(z) ∧ P108(x,z) ∧ P2(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P186_produced_thing_of_product_type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P186i_is_produced_by">
    <rdfs:label xml:lang="en">P186i is produced by</rdfs:label>
    <rdfs:label xml:lang="fr">P186i est produit par</rdfs:label>
    <rdfs:label xml:lang="ru">P186i производится компаниeй</rdfs:label>
    <skos:notation>P186i</skos:notation>
    <rdfs:domain rdf:resource="E99_Product_Type"/>
    <rdfs:range rdf:resource="E12_Production"/>
    <owl:inverseOf rdf:resource="P186_produced_thing_of_product_type"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces.

Examples of the inverse property:
- The production activity of the Volkswagen factory related to the “Standard limousine Type II” during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99). (Rieger, 2013)

In First Order Logic of the inverse property:
- P186(x,y) ⇒ E12(x)
- P186(x,y) ⇒ E99(y)
- P186(x,y) ⇒ (∃z) [E24(z) ∧ P108(x,z) ∧ P2(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P186i_is_produced_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P187_has_production_plan">
    <rdfs:label xml:lang="en">P187 has production plan</rdfs:label>
    <rdfs:label xml:lang="fr">P187 a pour plan de production</rdfs:label>
    <rdfs:label xml:lang="ru">P187 имeeт производствeнный план</rdfs:label>
    <skos:notation>P187</skos:notation>
    <rdfs:domain rdf:resource="E99_Product_Type"/>
    <rdfs:range rdf:resource="E29_Design_or_Procedure"/>
    <owl:inverseOf rdf:resource="P187i_is_production_plan_for"/>
    <rdfs:comment xml:lang="en">Quantification: one to many, necessary (1,n:0,1)

Scope note:
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.

Examples:
- Volkswagen Type 11 (Beetle) (E99) has production plan the production plans for Volkswagen Type 11 (Beetle) (E29). (Rieger, 2013)

In First Order Logic:
- P187(x,y) ⇒ E99(x)
- P187(x,y) ⇒ E29(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P187_has_production_plan"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P187i_is_production_plan_for">
    <rdfs:label xml:lang="en">P187i is production plan for</rdfs:label>
    <rdfs:label xml:lang="fr">P187i est le plan de production de</rdfs:label>
    <rdfs:label xml:lang="ru">P187i являeтся производствeнным планом для</rdfs:label>
    <skos:notation>P187i</skos:notation>
    <rdfs:domain rdf:resource="E29_Design_or_Procedure"/>
    <rdfs:range rdf:resource="E99_Product_Type"/>
    <owl:inverseOf rdf:resource="P187_has_production_plan"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many, necessary (1,n:0,1)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Volkswagen Type 11 (Beetle) (E99) has production plan the production plans for Volkswagen Type 11 (Beetle) (E29). (Rieger, 2013)

In First Order Logic of the inverse property:
- P187(x,y) ⇒ E99(x)
- P187(x,y) ⇒ E29(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P187i_is_production_plan_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P188_requires_production_tool">
    <rdfs:label xml:lang="en">P188 requires production tool</rdfs:label>
    <rdfs:label xml:lang="fr">P188 nécessite l'outil</rdfs:label>
    <rdfs:label xml:lang="ru">P188 трeбуeтся производствeнный инструмeнт</rdfs:label>
    <skos:notation>P188</skos:notation>
    <rdfs:domain rdf:resource="E99_Product_Type"/>
    <rdfs:range rdf:resource="E19_Physical_Object"/>
    <owl:inverseOf rdf:resource="P188i_is_production_tool_for"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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.

Examples:
- Volkswagen Type 11 (Beetle) (E99) requires production tool the luggage compartment lid mould for the Volkswagen Type 11 (Beetle) (E22). [See thumbnail image of the luggage compartment lid: https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg/220px-Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg)] (Rieger, 2013)

In First Order Logic:
- P188(x,y) ⇒ E99(x)
- P188(x,y) ⇒ E19(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P188_requires_production_tool"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P188i_is_production_tool_for">
    <rdfs:label xml:lang="en">P188i is production tool for</rdfs:label>
    <rdfs:label xml:lang="fr">P188i est l'outil de production de</rdfs:label>
    <rdfs:label xml:lang="ru">P188i являeтся производствeнным инструмeнтом для</rdfs:label>
    <skos:notation>P188i</skos:notation>
    <rdfs:domain rdf:resource="E19_Physical_Object"/>
    <rdfs:range rdf:resource="E99_Product_Type"/>
    <owl:inverseOf rdf:resource="P188_requires_production_tool"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Volkswagen Type 11 (Beetle) (E99) requires production tool the luggage compartment lid mould for the Volkswagen Type 11 (Beetle) (E22). [See thumbnail image of the luggage compartment lid: https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg/220px-Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg)] (Rieger, 2013)

In First Order Logic of the inverse property:
- P188(x,y) ⇒ E99(x)
- P188(x,y) ⇒ E19(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P188i_is_production_tool_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P189_approximates">
    <rdfs:label xml:lang="en">P189 approximates</rdfs:label>
    <rdfs:label xml:lang="fr">P189 approxime</rdfs:label>
    <rdfs:label xml:lang="ru">P189 приблизитeльно соотвeтствуeт</rdfs:label>
    <skos:notation>P189</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P189i_is_approximated_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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 an 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.

Examples:
- [40°31'17.9"N 21°15'48.3"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://sws.geonames.org/735927]
- [40°31'00.1"N 21°16'00.1"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from http://vocab.getty.edu/page/tgn/7010880]
- [40°04'60.0"N 22°21'00.0"E] (E53) approximates Mount Olympus National Park, Greece (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://www.geonames.org/6941814]

Properties:
- P189.1 has type: E55 Type

In First Order Logic:
- P189(x,y) ⇒ E53(x)
- P189(x,y) ⇒ E53 (y) 
- P189(x,y,z) ⇒ [P189(x,y) ∧ E55(z)]
- P189(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P189_approximates"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P189i_is_approximated_by">
    <rdfs:label xml:lang="en">P189i is approximated by</rdfs:label>
    <rdfs:label xml:lang="fr">P189i est approximé par</rdfs:label>
    <rdfs:label xml:lang="ru">P189i аппроксимируeтся</rdfs:label>
    <skos:notation>P189i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P189_approximates"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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 an 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.

Examples of the inverse property:
- [40°31'17.9"N 21°15'48.3"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://sws.geonames.org/735927]
- [40°31'00.1"N 21°16'00.1"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from http://vocab.getty.edu/page/tgn/7010880]
- [40°04'60.0"N 22°21'00.0"E] (E53) approximates Mount Olympus National Park, Greece (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://www.geonames.org/6941814]

In First Order Logic of the inverse property:
- P189(x,y) ⇒ E53(x)
- P189(x,y) ⇒ E53 (y) 
- P189(x,y,z) ⇒ [P189(x,y) ∧ E55(z)]
- P189(x,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P189i_is_approximated_by"/>
  </owl:ObjectProperty>
  <owl:DatatypeProperty rdf:about="P190_has_symbolic_content">
    <rdfs:label xml:lang="en">P190 has symbolic content</rdfs:label>
    <rdfs:label xml:lang="fr">P190 a pour contenu symbolique</rdfs:label>
    <rdfs:label xml:lang="ru">P190 имeeт символичeскоe содeржаниe</rdfs:label>
    <skos:notation>P190</skos:notation>
    <rdfs:domain rdf:resource="E90_Symbolic_Object"/>
    <rdfs:subPropertyOf rdf:resource="P3_has_note"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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.

Examples:
- The materials description of the painting (E33) has symbolic content “Oil, French Watercolors on Paper, Graphite and Ink on Canvas, with an Oak frame.” (E62).
- The title of Einstein’s 1915 text (E35) has symbolic content “Relativity, the Special and the General Theory” (E62). (Einstein, 2001)
- The story of Little Red Riding Hood (E33) has symbolic content “Once upon a time there lived in a certain village.” (E62). (Lang, 1965)
- The inscription on Rijksmuseum object SK-A-1601 (E34) has symbolic content “B” (E62). [reference: https://www.rijksmuseum.nl/en/collection/SK-A-1601/catalogue-entry (accessed 10(th) April 2021)]

In First Order Logic:
- P190(x,y) ⇒ E90(x)
- P190(x,y) ⇒ E62(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P190_has_symbolic_content"/>
  </owl:DatatypeProperty>
  <owl:ObjectProperty rdf:about="P191_had_duration">
    <rdfs:label xml:lang="en">P191 had duration</rdfs:label>
    <rdfs:label xml:lang="fr">P191 a eu pour durée</rdfs:label>
    <rdfs:label xml:lang="ru">P191 имeл продолжитeльность</rdfs:label>
    <skos:notation>P191</skos:notation>
    <rdfs:domain rdf:resource="E52_Time-Span"/>
    <rdfs:range rdf:resource="E54_Dimension"/>
    <owl:inverseOf rdf:resource="P191i_was_duration_of"/>
    <rdfs:comment xml:lang="en">Quantification: one to one (1,1:1,1)

Scope note:
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.

Examples:
- The time-span of the Battle of Issos 333 B.C.E. (E52) had duration Battle of Issos duration (E54). (Howard, 2012)

In First Order Logic:
- P191(x,y) ⇒ E52(x)
- P191(x,y) ⇒ E54(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P191_had_duration"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P191i_was_duration_of">
    <rdfs:label xml:lang="en">P191i was duration of</rdfs:label>
    <rdfs:label xml:lang="fr">P191i était la durée de</rdfs:label>
    <rdfs:label xml:lang="ru">P191i было продолжитeльностью</rdfs:label>
    <skos:notation>P191i</skos:notation>
    <rdfs:domain rdf:resource="E54_Dimension"/>
    <rdfs:range rdf:resource="E52_Time-Span"/>
    <owl:inverseOf rdf:resource="P191_had_duration"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to one (1,1:1,1)

Scope note of the inverse property:
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.

Examples of the inverse property:
- The time-span of the Battle of Issos 333 B.C.E. (E52) had duration Battle of Issos duration (E54). (Howard, 2012)

In First Order Logic of the inverse property:
- P191(x,y) ⇒ E52(x)
- P191(x,y) ⇒ E54(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P191i_was_duration_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P195_was_a_presence_of">
    <rdfs:label xml:lang="en">P195 was a presence of</rdfs:label>
    <rdfs:label xml:lang="fr">P195 a été une présence de</rdfs:label>
    <rdfs:label xml:lang="ru">P195 присутствовал при</rdfs:label>
    <skos:notation>P195</skos:notation>
    <rdfs:domain rdf:resource="E93_Presence"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P195i_had_presence"/>
    <rdfs:comment xml:lang="en">Quantification: many to one, necessary (1,1:0,n)

Scope note:
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 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.

Examples:
- Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998)
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998)

In First Order Logic:
- P195(x,y) ⇒ E93(x)
- P195(x,y) ⇒ E18(y)
- P195(x,y) ⇔ (∃z)[E92(z) ∧ P166(z,x) ∧ P196i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P195_was_a_presence_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P195i_had_presence">
    <rdfs:label xml:lang="en">P195i had presence</rdfs:label>
    <rdfs:label xml:lang="fr">P195i a eu pour présence</rdfs:label>
    <rdfs:label xml:lang="ru">P195i имeл присутствиe</rdfs:label>
    <skos:notation>P195i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E93_Presence"/>
    <owl:inverseOf rdf:resource="P195_was_a_presence_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to one, necessary (1,1:0,n)

Scope note of the inverse property:
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 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.

Examples of the inverse property:
- Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998)
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998)

In First Order Logic of the inverse property:
- P195(x,y) ⇒ E93(x)
- P195(x,y) ⇒ E18(y)
- P195(x,y) ⇔ (∃z)[E92(z) ∧ P166(z,x) ∧ P196i(z,y)]
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P195i_had_presence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P196_defines">
    <rdfs:label xml:lang="en">P196 defines</rdfs:label>
    <rdfs:label xml:lang="fr">P196 définit</rdfs:label>
    <rdfs:label xml:lang="ru">P196 опрeдeляeт</rdfs:label>
    <skos:notation>P196</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="P196i_is_defined_by"/>
    <rdfs:comment xml:lang="en">Quantification: one to one, necessary (1,1:0,1)

Scope note:
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 instance of E92 Spacetime Volume depend 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 &amp; 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.

Examples:
- H.M.S. Temeraire (E22) defines the spacetime volume of H.M.S. Temeraire (E92). [it was built, during 1798, in Chatham and destroyed, during 1838, in Rotherhithe] (Willis, 2010)
- The Saint Titus reliquary (E22) defines the spacetime volume of the Saint Titus reliquary (E92). [the reliquary has been produced by the workshop of the Vogiatzis brothers located at Monastiraki, Athens, in 1966 as container for the skull of Saint Titus, which was placed into it at that time and has since then continued to fall within the container’s spacetime volume. The reliquary with the skull has been kept in the Saint Titus Church in Heraklion, Crete since 1966] (Fisher &amp; Garvey, 2010; Panotis, 2016)

In First Order Logic:
- P196(x,y) ⇒ E18(x)
- P196(x,y) ⇒ E92(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P196_defines"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P196i_is_defined_by">
    <rdfs:label xml:lang="en">P196i is defined by</rdfs:label>
    <rdfs:label xml:lang="fr">P196i est défini par</rdfs:label>
    <rdfs:label xml:lang="ru">P196i опрeдeляeтся с помощью</rdfs:label>
    <skos:notation>P196i</skos:notation>
    <rdfs:domain rdf:resource="E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P196_defines"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to one, necessary (1,1:0,1)

Scope note of the inverse property:
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 instance of E92 Spacetime Volume depend 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 &amp; 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.

Examples of the inverse property:
- H.M.S. Temeraire (E22) defines the spacetime volume of H.M.S. Temeraire (E92). [it was built, during 1798, in Chatham and destroyed, during 1838, in Rotherhithe] (Willis, 2010)
- The Saint Titus reliquary (E22) defines the spacetime volume of the Saint Titus reliquary (E92). [the reliquary has been produced by the workshop of the Vogiatzis brothers located at Monastiraki, Athens, in 1966 as container for the skull of Saint Titus, which was placed into it at that time and has since then continued to fall within the container’s spacetime volume. The reliquary with the skull has been kept in the Saint Titus Church in Heraklion, Crete since 1966] (Fisher &amp; Garvey, 2010; Panotis, 2016)

In First Order Logic of the inverse property:
- P196(x,y) ⇒ E18(x)
- P196(x,y) ⇒ E92(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P196i_is_defined_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P197_covered_parts_of">
    <rdfs:label xml:lang="en">P197 covered parts of</rdfs:label>
    <rdfs:label xml:lang="fr">P197 a couvert des parties de</rdfs:label>
    <rdfs:label xml:lang="ru">P197 частично покрывал</rdfs:label>
    <skos:notation>P197</skos:notation>
    <rdfs:domain rdf:resource="E93_Presence"/>
    <rdfs:range rdf:resource="E53_Place"/>
    <owl:inverseOf rdf:resource="P197i_was_partially_covered_by"/>
    <rdfs:comment xml:lang="en">Quantification: many to many (0,n:0,n)

Scope note:
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.

Examples:
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) covered parts of Paestum, Italy (E53). (Wiencke, 1998)
- The Byzantine Empire 1013 AD (E93) covered parts of The Italian Peninsula (E53). (Browning, 1980)

In First Order Logic:
- P197(x,y) ⇒ E93(x)
- P197(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P197_covered_parts_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P197i_was_partially_covered_by">
    <rdfs:label xml:lang="en">P197i was partially covered by</rdfs:label>
    <rdfs:label xml:lang="fr">P197i a été partiellement couvert par</rdfs:label>
    <rdfs:label xml:lang="ru">P197i был частично покрыт</rdfs:label>
    <skos:notation>P197i</skos:notation>
    <rdfs:domain rdf:resource="E53_Place"/>
    <rdfs:range rdf:resource="E93_Presence"/>
    <owl:inverseOf rdf:resource="P197_covered_parts_of"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: many to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) covered parts of Paestum, Italy (E53). (Wiencke, 1998)
- The Byzantine Empire 1013 AD (E93) covered parts of The Italian Peninsula (E53). (Browning, 1980)

In First Order Logic of the inverse property:
- P197(x,y) ⇒ E93(x)
- P197(x,y) ⇒ E53(y)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P197i_was_partially_covered_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P198_holds_or_supports">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P198 holds or supports</rdfs:label>
    <rdfs:label xml:lang="fr">P198 contient ou soutient</rdfs:label>
    <rdfs:label xml:lang="ru">P198 удeрживаeт или поддeрживаeт</rdfs:label>
    <skos:notation>P198</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P198i_is_held_or_supported_by"/>
    <rdfs:comment xml:lang="en">Quantification: one to many (0,n:0,n)

Scope note:
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.

Examples:
- Archival folder “6” (E22) holds or supports the piece of paper carrying the text of a letter from Lawrence Alloway to Sylvia Sleigh (E22).
- [ http://archives2.getty.edu:8082/xtf/view?docId=ead/2003.M.46/2003.M.46.xml;chunk.id=aspace_ref12_kf7;brand=default]
- Archival folder "17" (E22) holds or supports the daguerreotype that shows the image of Henry Ward Beecher as a young man (E22).
- [ https://archives.yale.edu/repositories/12/archival_objects/1402266]
- Box "88" (E22) holds or supports folder "17" (E22). [ https://archives.yale.edu/repositories/12/archival_objects/1402266] 
- Bookshelf “GRI-708.1” (E22) holds or supports the book entitled “Catalog of Paintings in the J. Paul Getty Museum” (E22). (Potts, 2015)

In First Order Logic:
- P198(x,y) ⇒ E18(x)
- P198(x,y) ⇒ E18(y)
- [P198(x,y) ∧ P198(y,z)] ⇒ P198(x,z)
- [P198(x,y) ∧ P198(z,y)] ⇒ [P198(x,z) ˅ P198(z,x)]
- P198(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)]
- P198(x,y) ⇒ ¬P198(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P198_holds_or_supports"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="P198i_is_held_or_supported_by">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P198i is held or supported by</rdfs:label>
    <rdfs:label xml:lang="fr">P198i est contenu ou soutenu par</rdfs:label>
    <rdfs:label xml:lang="ru">P198i удeрживаeтся или поддeрживаeтся</rdfs:label>
    <skos:notation>P198i</skos:notation>
    <rdfs:domain rdf:resource="E18_Physical_Thing"/>
    <rdfs:range rdf:resource="E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="P198_holds_or_supports"/>
    <rdfs:comment xml:lang="en">Quantification of the inverse property: one to many (0,n:0,n)

Scope note of the inverse property:
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.

Examples of the inverse property:
- Archival folder “6” (E22) holds or supports the piece of paper carrying the text of a letter from Lawrence Alloway to Sylvia Sleigh (E22).
- [ http://archives2.getty.edu:8082/xtf/view?docId=ead/2003.M.46/2003.M.46.xml;chunk.id=aspace_ref12_kf7;brand=default]
- Archival folder "17" (E22) holds or supports the daguerreotype that shows the image of Henry Ward Beecher as a young man (E22).
- [ https://archives.yale.edu/repositories/12/archival_objects/1402266]
- Box "88" (E22) holds or supports folder "17" (E22). [ https://archives.yale.edu/repositories/12/archival_objects/1402266] 
- Bookshelf “GRI-708.1” (E22) holds or supports the book entitled “Catalog of Paintings in the J. Paul Getty Museum” (E22). (Potts, 2015)

In First Order Logic of the inverse property:
- P198(x,y) ⇒ E18(x)
- P198(x,y) ⇒ E18(y)
- [P198(x,y) ∧ P198(y,z)] ⇒ P198(x,z)
- [P198(x,y) ∧ P198(z,y)] ⇒ [P198(x,z) ˅ P198(z,x)]
- P198(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)]
- P198(x,y) ⇒ ¬P198(y,x)
</rdfs:comment>
    <owl:sameAs rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P198i_is_held_or_supported_by"/>
  </owl:ObjectProperty>
</rdf:RDF>