cidoc-crm.rdf

<?xml version="1.0"?>
<rdf:RDF
    xmlns:ecrm="http://erlangen-crm.org/current/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:skos="http://www.w3.org/2004/02/skos/core#"
    xmlns:protege="http://protege.stanford.edu/plugins/owl/protege#"
    xmlns:xsp="http://www.owl-ontologies.com/2005/08/07/xsp.owl#"
    xmlns:owl="http://www.w3.org/2002/07/owl#"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
    xmlns:swrl="http://www.w3.org/2003/11/swrl#"
    xmlns:swrlb="http://www.w3.org/2003/11/swrlb#"
    xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  xml:base="http://erlangen-crm.org/current/">
  <owl:Ontology rdf:about="">
    <rdfs:label xml:lang="en">Erlangen CRM / OWL</rdfs:label>
    <rdfs:comment xml:lang="en">Changelog: https://github.com/erlangen-crm/ecrm/commits/master</rdfs:comment>
    <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>
    <owl:versionInfo rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >ECRM 200717 / CIDOC-CRM 6.2.9</owl:versionInfo>
  </owl:Ontology>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E1_CRM_Entity">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E1</skos:notation>
    <rdfs:label xml:lang="en">E1 CRM Entity</rdfs:label>
    <rdfs:comment xml:lang="en">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:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. 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>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P48_has_preferred_identifier"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E29_Design_or_Procedure">
    <rdfs:label xml:lang="en">E29 Design or Procedure</rdfs:label>
    <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 of Beethoven's "Ode to Joy"
- the architectural drawings for the Kölner Dom in Cologne, Germany
- The drawing on the folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486-1490, kept in the Biblioteca Ambrosiana in Milan


In First Order Logic:
E29(x) ⊃ E73(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E73_Information_Object"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E29</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E63_Beginning_of_Existence">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E63</skos:notation>
    <rdfs:label xml:lang="en">E63 Beginning of Existence</rdfs:label>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E77_Persistent_Item"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92_brought_into_existence"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E5_Event"/>
    </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 determination of a “terminus post quem” or “terminus ante quem”. 


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


In First Order Logic:
E63(x) ⊃ E5(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E6_Destruction">
    <rdfs:label xml:lang="en">E6 Destruction</rdfs:label>
    <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 may be documented by classifying the event as both an instance of E6 Destruction and of E7 Activity.

The decision to document an object as destroyed, transformed or modified is context sensitive:
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 as an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
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) (George, 2000)
- the breaking of a champagne glass yesterday by my dog


In First Order Logic:
E6(x) ⊃ E64(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E18_Physical_Thing"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P13_destroyed"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E64_End_of_Existence"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E6</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E18_Physical_Thing">
    <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) (Mohem, 2006)


In First Order Logic:
E18(x) ⊃ E72(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E18</skos:notation>
    <owl:disjointWith>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E28_Conceptual_Object"/>
    </owl:disjointWith>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E53_Place"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P53_has_former_or_current_location"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E57_Material"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P45_consists_of"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E72_Legal_Object"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P13i_was_destroyed_by"/>
        </owl:onProperty>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:label xml:lang="en">E18 Physical Thing</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E5_Event">
    <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 performances. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event. While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example the statements made during a meeting and the listening of the audience.

Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analyzed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the size of the phenomena. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy overall effect and are thus not instances of E5 Event.


Examples:
- the birth of Cleopatra (E67) (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
- the CIDOC Conference 2003 (E7)


In First Order Logic:
E5(x) ⊃ E4(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E77_Persistent_Item"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E4_Period"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E5</skos:notation>
    <rdfs:label xml:lang="en">E5 Event</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E67_Birth">
    <rdfs:label xml:lang="en">E67 Birth</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E67</skos:notation>
    <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 typically brought into life by the same instance of E67 Birth. The introduction of E67 Birth as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the birth.


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


In First Order Logic:
E67(x) ⊃ E63(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E21_Person"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P96_by_mother"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P97_from_father"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E21_Person"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E63_Beginning_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E21_Person"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P98_brought_into_life"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E14_Condition_Assessment">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E14</skos:notation>
    <rdfs:label xml:lang="en">E14 Condition Assessment</rdfs:label>
    <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 may be relevant to interpret its quality at a later stage, or to continue research on related documents.


Examples:
- last year's inspection of humidity damage to the frescos in the St. George chapel in our village


In First Order Logic:
E14(x) ⊃ E13(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P34_concerned"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:minCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P35_has_identified"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E32_Authority_Document">
    <rdfs:label xml:lang="en">E32 Authority Document</rdfs:label>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E31_Document"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P71_lists"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/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
- Getty Art and Architecture Thesaurus (Getty Trust, 1990)
- the CIDOC Conceptual Reference Model (Gergatsoulis, M. et al., 2010) 


In First Order Logic:
E32(x) ⊃ E31(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E32</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E30_Right">
    <rdfs:label xml:lang="en">E30 Right</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E30</skos:notation>
    <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 Louvre


In First Order Logic:
E30(x) ⊃ E89(x</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E89_Propositional_Object"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E72_Legal_Object"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P104i_applies_to"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E90_Symbolic_Object">
    <rdfs:label xml:lang="en">E90 Symbolic Object</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E90</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
        <owl:onProperty>
          <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P106_is_composed_of"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E72_Legal_Object"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E28_Conceptual_Object"/>
    </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)
- image BM000038850.JPG from the Clayton Herbarium in London (E36)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E36)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)


In First Order Logic:
E90(x) ⊃ E28(x)
E90(x) ⊃ E72(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E16_Measurement">
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:cardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P39_measured"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P40_observed_dimension"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E54_Dimension"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E16</skos:notation>
    <rdfs:label xml:lang="en">E16 Measurement</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises actions measuring quantitative physical properties and other values that can be determined by a systematic, objective procedure of direct observation of particular states of physical reality. Properties of instances of E90 Symbolic Object may be measured by observing some of their representative carriers which may or may not be named explicitly. 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 measurement activity.

Examples include measuring the nominal monetary value of a collection of coins or the running time of a movie on a specific video cassette. The E16 Measurement may use simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. 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, 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 height of silver cup 232 on the 31st  August 1997
- the carbon 14 dating of the “Schoeninger Speer II” in 1996 [an about 400.000 years old
- Palaeolithic complete wooden spear found in Schoeningen, Niedersachsen, Germany in 1995] (Kouwenhoven, 1997)
- The pixel size of the jpeg version of Titian’s painting Bacchus and Ariadne from 1520–3, as freely downloadable from the National Gallery in London’s web page &lt;https://www.nationalgallery.org.uk/paintings/titian-bacchus-and-ariadne&gt; is 581600 pixels.
- The scope note of E21 Person in the Definition of the CIDOC Conceptual Reference Model Version 5.0.4 as downloaded from &lt;http://www.cidoccrm.org/sites/default/files/cidoc_crm_version_5.0.4.pdf&gt; consists of 77 words.


In First Order Logic:
E16(x) ⊃ E13(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E26_Physical_Feature">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E26</skos:notation>
    <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-, two- or three-dimensional geometric extent, but there are no natural borders that separate them completely in an objective way from the carrier objects. For example, a doorway is a feature but the door itself, being attached by hinges, is not. 

Instances of E26 Physical Feature can be features in a narrower sense, such as scratches, holes, reliefs, surface colours, reflection zones in an opal crystal or a density change in a piece of wood. In the wider sense, they are portions of particular objects with partially imaginary borders, such as the core of the Earth, an area of property on the surface of the Earth, a landscape or the head of a contiguous marble statue. They can be measured and dated, and it is sometimes possible to state who or what is or was responsible for them. They cannot be separated from the carrier object, but a segment of the carrier object may be identified (or sometimes removed) carrying the complete feature.

This definition coincides with the definition of "fiat objects" (Smith &amp; Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”. 


Examples:
- the temple in Abu Simbel before its removal, which was carved out of solid rock (Hawass, 2000)
- Albrecht Duerer's signature on his painting of Charles the Great (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>
    <rdfs:label xml:lang="en">E26 Physical Feature</rdfs:label>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P56i_is_found_on"/>
        </owl:onProperty>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E3_Condition_State">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E3</skos:notation>
    <rdfs:label xml:lang="en">E3 Condition State</rdfs:label>
    <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 E52 Time Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held. The nature of that condition can be described using  P2 has type. For example, the E3 Condition State "condition of the SS Great Britain between 22 September 1846 and 27 August 1847" can be characterized as E55 Type "wrecked".


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


In First Order Logic:
E3(x) ⊃ E2(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P44i_is_condition_of"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E78_Curated_Holding">
    <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 often referred to with the name of the E78 Curated Holding (e.g. “The Wallace Collection decided…”). 

Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, Definition of the CIDOC Conceptual Reference Model version 6.2.8 36
should be documented as instances of E19 Physical Object, and not as instances of E78 Curated Holding. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.


Examples:
the John Clayton Herbarium
 the Wallace Collection (Ingamells, 1990)
 Mikael Heggelund Foslie’s coralline red algae Herbarium at Museum of Natural History and Archaeology, Trondheim, Norway
 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>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P109_has_current_or_former_curator"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E39_Actor"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    </rdfs:subClassOf>
    <rdfs:label xml:lang="en">E78 Collection</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E78</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E21_Person">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E21</skos:notation>
    <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, 1979)
- Nelson Mandela (Brown, 2006)


In First Order Logic:
E21(x) ⊃ E20(x)
E21(x) ⊃ E39(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
        >2</owl:minCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P152_has_parent"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E39_Actor"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P98i_was_born"/>
        </owl:onProperty>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E20_Biological_Object"/>
    </rdfs:subClassOf>
    <rdfs:label xml:lang="en">E21 Person</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E68_Dissolution">
    <rdfs:label xml:lang="en">E68 Dissolution</rdfs:label>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E74_Group"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P99_dissolved"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E64_End_of_Existence"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E68</skos:notation>
    <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:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E19_Physical_Object">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E19</skos:notation>
    <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” (Smith &amp; Varzi, 2000, pp.401-420), i.e. naturally defined objects.

The decision as to what is documented as a complete item, rather than by its parts or components, may be a purely administrative decision or may be a result of the order in which the item was acquired.


Examples: 
- John SmithAphrodite of Milos (Kousser, 2005)
- the Palace of Knossos (Evans, 1921-36)
- the Cullinan Diamond (Scarratt and Shor, 2006)
- Apollo 13 at the time of launch (Lovell and Kluger, 1994)


In First Order Logic:
E19(x) ⊃ E18(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P54_has_current_permanent_location"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P55_has_current_location"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">E19 Physical Object</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E27_Site">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E27</skos:notation>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E26_Physical_Feature"/>
    <rdfs:label xml:lang="en">E27 Site</rdfs:label>
    <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
- Knossos
- the Apollo 11 landing site
- Heathrow Airport
- the submerged harbour of the Minoan settlement of Gournia, Crete

In First Order Logic:
E27(x)⊃ E26(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E81_Transformation">
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the events that result in the simultaneous destruction of one or more than one instance of E18 Physical Thing and the creation of one or more than one instance of 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 an instance of E81 Transformation. The creation of the new instances of E18 Physical Thing directly causes the destruction of the old instances of E18 Physical Thing using or preserving some relevant substance and structure. Instances of E81 Transformation are therefore distinct from re-classifications (documented as instances of E17 Type Assignment) or modifications (documented as instances of E11 Modification) of objects that do not fundamentally change their nature or identity. Characteristic cases of instances of E81 Transformation are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimens in natural history.


Examples:
- the death and mummification of Tut-Ankh-Amun (transformation of Tut-Ankh-Amun from a living person to a mummy) (E69,E81,E7)


In First Order Logic:
E81(x) ⊃ E63(x)
E81(x) ⊃ E64(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E81 Transformation</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E81</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P123_resulted_in"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E77_Persistent_Item"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E77_Persistent_Item"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P124_transformed"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E64_End_of_Existence"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E63_Beginning_of_Existence"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E74_Group">
    <rdfs:label xml:lang="en">E74 Group</rdfs:label>
    <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 (cf. HumanML markup). Married couples and other concepts of family are regarded as particular examples of E74 Group.


Examples:
- the impressionists (Wilson, 1983)
- the Navajo (Correll, 1972)
- the Greeks (Williams, 1993)
- the peace protestors in New York City on February 15 2003
- Exxon-Mobil (‘Exxon Mobil Corp’, Mergent's dividend achievers, vol. 3, no. 3, 2006, pp. 97-97)
- King Solomon and his wives (Thieberger, 1947)
- The President of the Swiss Confederation
- Nicolas Bourbaki (Aczel, 2007)
- Betty Crocker (Crocker, 2012)
- Ellery Queen (Wheat, 2005)
- Greenpeace
- Paveprime Ltd
- the National Museum of Denmark


In First Order Logic:
E74(x) ⊃ E39(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E74</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P107_has_current_or_former_member"/>
        </owl:onProperty>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >2</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P146i_lost_member_by"/>
        </owl:onProperty>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >0</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P95i_was_formed_by"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P144i_gained_member_by"/>
        </owl:onProperty>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >2</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E39_Actor"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E85_Joining">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E85</skos:notation>
    <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 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 January 1. 1993


In First Order Logic:
E85(x) ⊃ E7(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:minCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P144_joined_with"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:cardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P143_joined"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E7_Activity"/>
    </rdfs:subClassOf>
    <rdfs:label xml:lang="en">E85 Joining</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E12_Production">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E63_Beginning_of_Existence"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P108_has_produced"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E11_Modification"/>
    </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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E12</skos:notation>
    <rdfs:label xml:lang="en">E12 Production</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E52_Time-Span">
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P4i_is_time-span_of"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E52</skos:notation>
    <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 “timeline” 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 and Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which we can infer knowledge about it, such as in relative chronologies.

Some instances of E52 may be defined precisely as representing a declaration of a temporal extent, as, for instance, done in a business contract. They constitute declarative time-spans as defined in CRMgeo (Doerr and Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span.

When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known.


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


In First Order Logic:
E52(x) ⊃ E1(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E52 Time-Span</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E20_Biological_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
- Tut-Ankh-Amun (Edwards, 1979)
- Boukephalas [Horse of Alexander the Great](Lamb, 2005)
- petrified dinosaur excrement PA1906-344


In First Order Logic:
E20(x) ⊃ E19(x)</rdfs:comment>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <rdfs:label xml:lang="en">E20 Biological Object</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E20</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E73_Information_Object">
    <rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable immaterial items, such as a poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. 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 Definition of the CIDOC Conceptual Reference Model version 6.2.8 34 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)
- E. A. Poe's "The Raven" (Poe, 1869)
- the movie "The Seven Samurai" by Akira Kurosawa (Mellen, 2002)
- 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>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E89_Propositional_Object"/>
    </rdfs:subClassOf>
    <rdfs:label xml:lang="en">E73 Information Object</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E73</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E54_Dimension">
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P91_has_unit"/>
        </owl:onProperty>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <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 true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.

Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.


Examples:
- The 250 metric ton weight of the Luxor Obelisk
- The 5.17 m height of the statue of David by Michaelangelo
- The 530.2 carats of the Great Star of Africa diamond
- The AD1262-1312, 1303-1384 calibrated C14 date for the Shroud of Turin
- The 33 m diameter of the Stonehenge Sarcen Circle
- The 755.9 foot length of the sides of the Great Pyramid at Giza 
- Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97) has currency British Pounds (E98)
- The time span of the Battle of Issos 333 B.C.E. (E52) had duration Battle of Issos duration (E54)


In First Order Logic:
E54(x) ⊃ E1(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E54</skos:notation>
    <rdfs:label xml:lang="en">E54 Dimension</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E72_Legal_Object">
    <rdfs:label xml:lang="en">E72 Legal Object</rdfs:label>
    <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 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: 2004)


In First Order Logic:
E72(x) ⊃ E70(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P105_right_held_by"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E39_Actor"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P104_is_subject_to"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E30_Right"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E70_Thing"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E72</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E34_Inscription">
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E37_Mark"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
    </rdfs:subClassOf>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises recognisable, texts attached to instances of E24 Physical Human-Made Thing.

The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CIDOC CRM as instances of E24 Physical Human-Made Thing.

The relationship of a physical copy of a book to the text it contains is modelled using E18 Physical Thing. P128 carries (is carried by): E33 Linguistic Object.


Examples:
- "keep off the grass" on a sign stuck in the lawn of the quad of Balliol College
- The text published in Corpus Inscriptionum Latinarum V 895
- Kilroy was here


In First Order Logic:
E34(x) ⊃ E33(x)
E34(x) ⊃ E37(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E34</skos:notation>
    <rdfs:label xml:lang="en">E34 Inscription</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E70_Thing">
    <rdfs:label xml:lang="en">E70 Thing</rdfs:label>
    <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)
- the bottle of milk in my refrigerator (E22)
- 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 (E27) (Psimenos. 2005)


In First Order Logic:
E70(x) ⊃ E77(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E70</skos:notation>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E77_Persistent_Item"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E64_End_of_Existence">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E64</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E77_Persistent_Item"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P93_took_out_of_existence"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
    <rdfs:label xml:lang="en">E64 End of Existence</rdfs:label>
    <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 for determination of a “terminus post quem” or “terminus ante quem”. In cases where substance from an instance of E64 Persistent Item continues to exist in a new form, the process would be documented as instances of E81 Transformation.


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


In First Order Logic:
E64(x) ⊃ E5(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E89_Propositional_Object">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E89</skos:notation>
    <rdfs:label xml:lang="en">E89 Propositional Object</rdfs:label>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P129i_is_subject_of"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
        <owl:onProperty>
          <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P148_has_component"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E28_Conceptual_Object"/>
    </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 (Huray, 2010)
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 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:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E4_Period">
    <rdfs:label xml:lang="en">E4 Period</rdfs:label>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E53_Place"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P7_took_place_at"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E4</skos:notation>
    <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.

As the actual extent of an instance of E4 Period in spacetime we regard the trajectories of the participating physical things during their participation in an instance of E4 Period. This includes the open spaces via which these things have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event. Examples include the air in a meeting room transferring the voices of the participants. Since these phenomena are fuzzy, we assume the spatiotemporal extent to be contiguous, except for cases of phenomena spreading out over islands or other separated areas, including geopolitical units distributed over disconnected areas such as islands or colonies.

Whether the trajectories necessary for participants to travel between these areas are regarded as part of the spatiotemporal extent or not has to be decided in each case based on a concrete analysis, taking use of the sea for other purposes than travel, such as fishing, into consideration. One may also argue that the activities to govern disconnected areas imply travelling through spaces connecting them and that these areas hence are spatially connected in a way, but it appears counterintuitive to consider for instance travel routes in international waters as extensions of geopolitical units.


We model E4 Period as a subclass of E2 Temporal Entity and of E92 Spacetime Volume. The latter is intended as a phenomenal spacetime volume as defined in CIDOC CRMgeo (Doerr and Hiebel, 2013). By virtue of this multiple inheritance we can discuss the physical extent of an instance of E4 Period without representing each instance of it together with an instance of its associated spacetime volume. This model combines two quite different kinds of substance: an instance of E4 Period is a phenomena 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, c2004)
- Italian Renaissance (Macdonald, 1992)
- Thirty Years War (Lee, 1991)
- Sturm und Drang (Berkoff, 2013)
- Cubism (Cox, 2000)


In First Order Logic: 
E4(x) ⊃ E2(x)
E4(x) ⊃ E92(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E24</skos:notation>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P108i_was_produced_by"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E12_Production"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">E24 Physical Man-Made Thing</rdfs:label>
    <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 swords, and Human-Made features, such as rock art. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Human-Made Thing.

Instances of Human-Made thing may be the result of modifying pre-existing physical things, preserving larger parts or most of the original matter and structure, which poses the question if they are new or even Human-Made, the respective interventions of production made on such original material should be obvious and sufficient to regard that the product has a new, distinct identity and intended function and is human-made. Substantial continuity of the previous matter and structure in the new product can be documented by describing the production process also as instance of E81 Transformation.

Whereas interventions of conservation and repair are not regarded to produce a new Human-Made thing, the results of preparation of natural history specimen that substantially change their natural or original state should be regarded as physical Human-Made things, including the uncovering of petrified biological features from a solid piece of stone. On the other side, scribbling a museum number on a natural object should not be regarded to make it Human-Made. This notwithstanding, parts, sections, segments, or features of a physical Human-Made thing may continue to be non-Human-Made and preserved during the production process, for example natural pearls used as a part of an eardrop.


Examples:
- the Forth Railway Bridge (E22) (The Forth Railway Bridge centenary 1890-1990 ICE Proceedings, 1990, Vol.88(6), pp.1079-1107.
- the Channel Tunnel (E25) (Holliday, I., Marcou, G., and Vickerman, R. W., 1991)
- the Historical Collection of the Museum Benaki in Athens (E78) (Georgoula, E., 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:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E36_Visual_Item">
    <rdfs:label xml:lang="en">E36 Visual Item</rdfs:label>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E73_Information_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E36</skos:notation>
    <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 class E36 Visual Item 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 depicted subjects (E1 CRM Entity) is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity, which in addition captures the optical features of the depiction.


Examples:
- the visual appearance of Monet's "La Pie"
- the Coca-Cola logo (E34)
- the Chi-Rho (E37)
- the communist red star (E37)


In First Order Logic:
E36(x) ⊃ E73(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E33_Linguistic_Object">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E73_Information_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P72_has_language"/>
        </owl:onProperty>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P73i_is_translation_of"/>
        </owl:onProperty>
      </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 CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CRM. These should be modelled as instances of E73 Information Object.

The text of an instance of E33 Linguistic Object can be documented in a note by P3 has note: E62 String


Examples:
- the text of the Ellesmere Chaucer manuscript (Hilmo, 2004)
- 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, 1909)


In First Order Logic:
E33(x) ⊃ E73(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E33 Linguistic Object</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E33</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E92_Spacetime_Volume">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime (in contrast to mathematical models of it) regardless their true geometric forms. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, E53 Place and E52 Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of E92 Spacetime Volume is its projection on time.


Examples:
- the spacetime Volume of the Event of Ceasars murder 
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996  took place 
- the spatio‐temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002


In First Order Logic:
E92(x) ⊃ E1(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E92</skos:notation>
    <rdfs:label xml:lang="en">E92 Spacetime Volume</rdfs:label>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E83_Type_Creation">
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E55_Type"/>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P135_created_type"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E65_Creation"/>
    </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 B. O. Dodge' (1933)
- addition of class E85 Joining to the CIDOC CRM


In First Order Logic:
E83(x) ⊃ E65(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E83 Type Creation</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E83</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E65_Creation">
    <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>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E7_Activity"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P94_has_created"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E28_Conceptual_Object"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E63_Beginning_of_Existence"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E65</skos:notation>
    <rdfs:label xml:lang="en">E65 Creation</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E77_Persistent_Item">
    <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 dissappear completely and new emerge. For instance, a person, from the time of being born on, will gradually change all its features and acquire new ones, such as a scar. Even the DNA in different body cells will develop defects and mutations. Nevertheless, relevant characteristics use to be sufficiently similar to recognize the instance for some substantial period of time. 
The more specific criteria that determine the identity of instances of subclasses of E77 Persistent Item may vary considerably and are described of referred to in the respective scope notes. The decision about which exact criteria to use depends on whether the observable behaviour of the respective part of reality such confined conforms to the reasoning the user is interested in. For example, a building can be regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria, such as being bodily separated from other persons. Similarly, inanimate objects may be subject to exchange of parts and matter. On the opposite, the identity of a (version of a) text of a scientific publication is given by the exact arrangement of its relevant symbols.
The main classes of objects that fall outside the scope of the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties. An instance of E77 Persistent Item does not require actual knowledge of the identifying features of the instance being currently known. There may be cases, where the actual identifying features of an instance
of E77 Persistent Item are not decidable at a particular state of knowledge. 


Examples:
- Leonard da Vinci (Strano, 1953)
- Stonehenge (Richards, 2005)
- the hole in the ozone layer (Hufford and Horwitz, 2005)
- the First Law of Thermodynamics (Craig and Gislason, 2002)
- the Bermuda Triangle (Dolan, 2005)


In First Order Logic:
E77(x) ⊃ E1(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E77 Persistent Item</rdfs:label>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E77</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E7_Activity">
    <rdfs:label xml:lang="en">E7 Activity</rdfs:label>
    <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, 1987)
- the formation of the Bauhaus 1919 (E66) (Droste, 2006)
- calling the place identified by TGN ‘7017998’ ‘Quyunjig’ by the people of Iraq
- Kira Weber working in glass art from 1984 to 1993
- Kira Weber working in oil and pastel painting from 1993


In First Order Logic:
E7(x) ⊃ E5(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E7</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14_carried_out_by"/>
        </owl:onProperty>
        <owl:someValuesFrom>
          <owl:Class rdf:about="http://erlangen-crm.org/current/E39_Actor"/>
        </owl:someValuesFrom>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E96_Purchase">
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E8_Acquisition"/>
    </rdfs:subClassOf>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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.


In First Order Logic:
E96(x) ⊃ E8(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E56_Language">
    <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 are used to denote instances of E56 Language, such as those defined in ISO 639-1:2002 and later versions. 


Examples:
- el [Greek] (Palmer, 1980)
- en [English] (Wilson, 1983)
- eo [Esperanto] (Nuessel, 2000)
- es [Spanish] (Pineda, 1993)
- fr [French] (Rickard, 1974)


In First Order Logic:
E56(x) ⊃ E55(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E55_Type"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E56</skos:notation>
    <rdfs:label xml:lang="en">E56 Language</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E2_Temporal_Entity">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E2</skos:notation>
    <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 – 1946 (E3) (Maddox, 2015)


In First Order Logic:
E2(x) ⊃ E1(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E2 Temporal Entity</rdfs:label>
    <owl:disjointWith rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:cardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P4_has_time-span"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E79_Part_Addition">
    <rdfs:label xml:lang="en">E79 Part Addition</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises activities that result in an instance of E24 Physical Human-Made Thing being increased, enlarged or augmented by the addition of a part.

Typical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated instance of E78 Collection. Objects to which parts are added are, by definition, human-made, since the addition of a part implies a human activity. Following the addition of parts, the resulting human-made assemblages are treated objectively as single identifiable wholes, made up of constituent or component parts bound together either physically (for example the engine becoming a part of the car), or by sharing a common purpose (such as the 32 chess pieces that make up a chess set). This class of activities forms a basis for reasoning about the history and continuity of identity of objects that are integrated into other objects over time, such as precious gemstones being repeatedly incorporated into different items of jewellery, or cultural artifacts being added to different museum instances of E78 Collection 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


In First Order Logic:
E79(x) ⊃ E11(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E79</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P111_added"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P110_augmented"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E11_Modification"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E93_Presence">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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.


In First Order Logic:
E93(x) ⊃ E92(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E93 Spacetime Snapshot</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E93</skos:notation>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E99_Product_Type">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Scope note:
This classes comprises types that stand as the models for instances of E22 Human-Made Object that are produced as the result of production activities using plans exact enough to result in one or more series of uniform, functionally and aesthetically identical and interchangeable items. The product type is the intended ideal form of the manufacture process. It is typical of instances of E22 that conform to an instance of E99 Product Type that its component parts are interchangeable with component parts of other instances of E22 made after the model of the same instance of E99. Frequently, the uniform production according to a given instance of E99 Product Type is achieved by creating individual tools, such as moulds or print Definition of the CIDOC Conceptual Reference Model version 6.2.8 45 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)
- Dragendorff 54 samian vessel
- 1937 Edward VIII brass threepenny bit
- Qin Crossbow trigger un-notched Part B (Bg2u)
- Nokia Cityman 1320 (The first Nokia mobile phone)


In First Order Logic:
E99(x) ⊃ E55(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E55_Type"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E35_Title">
    <rdfs:label xml:lang="en">E35 Title</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E35</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises textual strings that within a cultural context can be clearly identified as titles due to their form. Being a subclass of E41 Appellation, E35 Title can only be used when such a string is actually used as a title of a work, such as a text, an artwork, or a piece of music.

Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group.

This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.


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


In First Order Logic:
E35(x) ⊃ E33(x)
E35(x) ⊃ E41(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E41_Appellation"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E42_Identifier">
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E41_Appellation"/>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E42</skos:notation>
    <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. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.


Examples:
- "MM.GE.195"
- "13.45.1976"
- "OXCMS: 1997.4.1"
- ISSN "0041-5278"
- ISRC "FIFIN8900116"
- Shelf mark "Res 8 P 10"
- "Guillaume de Machaut (1300?-1377)" [a controlled personal name heading that follows
the French rules] (Reaney, 1974)
- “+41 22 418 5571”
- weasel@paveprime.com
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”


In First Order Logic:
E42(x) ⊃ E41(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E42 Identifier</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E41_Appellation">
    <rdfs:comment xml:lang="en">Scope note:
This class comprises signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class or category within a certain context.

Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but instead by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes.

Different languages may use different appellations for the same thing, such as the names of major cities. Some appellations may be formulated using a valid noun phrase of a particular language. In these cases, the respective instances of E41 Appellation should also be declared as instances of E33 Linguistic Object. Then the language using the appellation can be declared with the property P72 has language: E56 Language.

Instances of E41 Appellation may be used to identify any instance of E1 CRM Entity and sometimes are characteristic for instances of more specific subclasses E1 CRM Entity, such as for instances of E52 Time-Span (for instance “dates”), E39 Actor, E53 Place or E28 Conceptual Object. Postal addresses and E-mail addresses are characteristic examples of identifiers used by services transporting things between clients.

Even numerically expressed identifiers for extents in space or time are also regarded as instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though they allow for determining some time or location by a known procedure starting from a reference point and by virtue of that fact play a double role as instances of E59 Primitive Value.

E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment


Examples:
- "Martin" 
- “Aquae Sulis Minerva”
- "the Merchant of Venice" (E35)
- "Spigelia marilandica (L.) L." [not the species, just the name] (Hershberger, Jenkins and Robacker, 2015)
- "information science" [not the science itself, but the name through which we refer to it in an English-speaking context] 
- “安” [Chinese "an", meaning "peace"]
- “6°5’29”N 45°12’13”W” (example of spatial coordinate)
- “Black queen’s bishop 4” [chess coordinate] (example of spatial coordinate)
- “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 address)
- “the poop deck of H.M.S Victory” (example of section definition)
- “the Venus de Milo’s left buttock” (example of section definition)


In First Order Logic:
E41(x) ⊃ E90(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E41 Appellation</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E41</skos:notation>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E22_Human-Made_Object">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises physical objects purposely created by human activity.

No assumptions are made as to the extent of modification required to justify regarding an object as human-made. For example, an inscribed piece of rock or a preserved butterfly are both regarded as instances of E22 Human-Made Object.


Examples:
- Mallard (the World’s fastest steam engine) (Solomon, 2003)
- the Portland Vase (Walker, 2004)
- the Coliseum (Hopkins, 2005)


In First Order Logic:
E22(x) ⊃ E19(x)
E22(x) ⊃ E24(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E22 Man-Made Object</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E22</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E66_Formation">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P95_has_formed"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E63_Beginning_of_Existence"/>
    <rdfs:label xml:lang="en">E66 Formation</rdfs:label>
    <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
- 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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E66</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E80_Part_Removal">
    <rdfs:label xml:lang="en">E80 Part Removal</rdfs:label>
    <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 Collection. 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 
Definition of the CIDOC Conceptual Reference Model version 6.2.8 37 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 jewelry, or cultural artifacts being deaccessioned from different museum collections over their lifespan.


Examples:
- the removal of the engine from my car
- the disposal of object number 1976:234 from the collection


In First Order Logic:
E80(x) ⊃ E11(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E80</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P113_removed"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P112_diminished"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E11_Modification"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E37_Mark">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E37</skos:notation>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E36_Visual_Item"/>
    <rdfs:label xml:lang="en">E37 Mark</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises symbols, signs, signatures or texts applied to instances of E24 Physical HumanMade Thing by arbitrary techniques in order to indicate the creator, owner, dedications, purpose, etc.

Instances of E37 Mark do not represent the actual image of a mark, but the abstract ideal, as they use to
be codified in reference documents that are used in cultural documentation.


Examples:
 Minoan double axe mark 
 ©
 


In First Order Logic:
E37(x) ⊃ E36(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E13_Attribute_Assignment">
    <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 type: E55 Type.

For example, the class describes the actions of people making propositions and statements during certain scientific/scholarly procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on whether this information should be accessible by structured queries.

This class allows for the documentation of how the respective assignment came about, and whose opinion it was. Note that all instances of properties described in a knowledge base are the opinion of someone. Per default, they are the opinion of the team maintaining the knowledge base. This fact must not individually be registered for all instances of properties provided by the maintaining team, because it would result in an endless recursion of whose opinion was the description of an opinion. Therefore, the use of instances of E13 Attribute Assignment marks the fact, that the maintaining team is in general neutral to the validity of the respective assertion, but registers someone else’s opinion and how it came about. 

All properties assigned in such an action can also be seen as directly relating the respective pair of items or concepts. Multiple use of instances of E13 Attribute Assignment may possibly lead to a collection of contradictory values.

All cases of properties in this model that are also described indirectly through a subclass of E13 Attribute Assignment are characterised as "short cuts" of a path via this subclass. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action of assertion or the short cut, and the relation between both alternatives can be captured by simple rules.


Examples:
- the assessment of the current ownership of Martin Doerr's silver cup in February 1997


In First Order Logic: 
E13(x) ⊃ E7(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E13 Attribute Assignment</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E13</skos:notation>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P140_assigned_attribute_to"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E10_Transfer_of_Custody">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P30_transferred_custody_of"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E10</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises transfers of physical custody of objects between instances of E39 Actor. 

The recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:
1. the beginning of custody
2. the end of custody
3. the transfer of custody
4. the receipt of custody from an unknown source
5. the declared loss of an object

The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft. The sense of physical possession requires that the object of custody is 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. For instance, in the case of a set of cutlery we may require the majority of pieces having been in the hands of the actor regardless which individual pieces are kept over time.

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.


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)


In First Order Logic:
E10(x) ⊃ E7(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E10 Transfer of Custody</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E28_Conceptual_Object">
    <rdfs:label xml:lang="en">E28 Conceptual Object</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E28</skos:notation>
    <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 may have been supported by the use of technical devices such as cameras or computers.

Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc.

They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost. 


Examples:
- Beethoven’s “Ode an die Freude” (Ode to Joy) (E73) (Kershaw, 1999)
- the definition of “ontology” in the Oxford English Dictionary (E73)
- the knowledge about the victory at Marathon carried by the famous runner (E89)
[explanation note: In the following examples we illustrate the distinction between a propositional object,
its names and its encoded forms. The Maxwell equations 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’ [preferred subject access point from LCSH] (E41)  http://lccn.loc.gov/sh85082387 [5], as of 19 November 2012]
**explanation: This is only the name for the Maxwell equations as standardized by the Library of Congress and NOT the equations themselves.
- ‘Equations, Maxwell’ [variant subject access point, from the same source] (E41)
**explanation: This is another name for the equation standardized by the Library of Congress and not the equations themselves
- Maxwell's equations (E89)
** explanation: This is the propositional content of the equations proper, independent of any particular notation or mathematical formalism.
- The encoding of Maxwells equations as in https://upload.wikimedia.org/wikipedia/commons/thumb/c/c4/Maxwell [6]'s Equations.svg/500pxMaxwell'sEquations.svg.png (E73)
** explanation: This is one possible symbolic encoding of the propositional content of the equations.


In First Order Logic:
E28(x) ⊃ E71(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P94i_was_created_by"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E65_Creation"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E8_Acquisition">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E8</skos:notation>
    <rdfs:label xml:lang="en">E8 Acquisition</rdfs:label>
    <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 right. The recording of the donor and/or recipient is optional. It is possible that in an instance of E8 Acquisition there is either no donor or no recipient. Depending on the circumstances, it may describe:
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 hammer-head shark of the genus Sphyrna (Carchariniformes) XXXtbc by John Steinbeck and Edward Ricketts at Puerto Escondido in the Gulf of Mexico on March 25th, 1940. (Steinbeck, 2000)
- the acquisition of El Greco’s painting entitled ‘The Apostles Peter and Paul’ by the State Hermitage in Saint Petersburg
- the loss of my stuffed chaffinch ‘Fringilla coelebs Linnaeus, 1758’ due to insect damage last year


In First Order Logic:
E8(x) ⊃ E7(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P24_transferred_title_of"/>
        </owl:onProperty>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E97_Monetary_Amount">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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  Definition of the CIDOC Conceptual Reference Model version 6.2.8 44 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. 


Example:
- Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97) has currency British Pounds (E98)


In First Order Logic:
E97(x) ⊃ E54(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E53_Place">
    <rdfs:label xml:lang="en">E53 Place</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E53</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.

The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks, but may also be determined by reference to mobile objetcts. A Place can be determined by combining a frame of reference and a location with respect to this frame.

It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance. 

Any instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for).


Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: "Fish collected at three miles north of the confluence of the Arve and the Rhone"
- here -&gt; &lt;-


In First Order Logic:
E53(x) ⊃ E1(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P59i_is_located_on_or_within"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E39_Actor">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E39</skos:notation>
    <rdfs:label xml:lang="en">E39 Actor</rdfs:label>
    <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 someone may be held responsible.


Examples:
- London and Continental Railways (E40)
- the Governor of the Bank of England in 1975 (E21)
- Sir Ian McKellan (E21)


In First Order Logic:
E39(x) ⊃ E77(x)</rdfs:comment>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E71_Human-Made_Thing">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <rdfs:label xml:lang="en">E71 Man-Made Thing</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E71</skos:notation>
    <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 5th Symphony (E73) (Lockwood, 2015)
- Michelangelo’s David (Paoletti, 2015)
- Einstein’s Theory of General Relativity (E73) (Hartle, 2003)
- the taxon ‘Fringilla coelebs Linnaeus,1758’ (E55) (Sinkevicius and Narusevicius, 2002)


In First Order Logic:
E71(x) ⊃ E70(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E11_Modification">
    <rdfs:comment xml:lang="en">Scope note:
This class comprises instances of E7 Activity that 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, and the preventive treatment or restoration of an object for conservation.

Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in 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.

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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E11</skos:notation>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P31_has_modified"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:label xml:lang="en">E11 Modification</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E57_Material">
    <rdfs:label xml:lang="en">E57 Material</rdfs:label>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E55_Type"/>
    </rdfs:subClassOf>
    <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 are 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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E57</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E98_Currency">
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E55_Type"/>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E58_Measurement_Unit"/>
    </rdfs:subClassOf>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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) ⊃ E55(x)
E98(x) ⊃ E58(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E86_Leaving">
    <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 February 1. 1985


In First Order Logic:
E86(x) ⊃ E7(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E86 Leaving</rdfs:label>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P146_separated_from"/>
        </owl:onProperty>
        <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:minCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:cardinality>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P145_separated"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E86</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E25_Human-Made_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.

No assumptions are made as to the extent of modification required to justify regarding a feature as human-made. For example, rock art or even “cup and ring” carvings on bedrock are regarded as types of E25 Human-Made Feature.


Examples:
- the Manchester Ship Canal (Famie, 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’s.
- The carved letters on the Rosetta Stone


In First Order Logic:
E25(x) ⊃ E26(x)
E25(x) ⊃ E24(x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E25</skos:notation>
    <rdfs:label xml:lang="en">E25 Man-Made Feature</rdfs:label>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E26_Physical_Feature"/>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E31_Document">
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E73_Information_Object"/>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P70_documents"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E31</skos:notation>
    <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 a special case of E31 Document. This class should not be confused with the term "document" in Information Technology, which is compatible with E73 Information Object.


Examples:
- the Encyclopaedia Britannica (E32) (Kogan, 1958)
- The image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E38)
- the Doomsday Book


In First Order Logic:
E31(x) ⊃ E73(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E31 Document</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E58_Measurement_Unit">
    <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 [meter]
- m/s [meters per second] (Hau, 1999)
- A [Ampere]
- GRD [Greek Drachme] (Daniel, 2014) (E98)
- °C [degrees centigrade] (Beckman, 1998)


In First Order Logic:
E58(x) ⊃ E55(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P91i_is_unit_of"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Class rdf:about="http://erlangen-crm.org/current/E55_Type"/>
    </rdfs:subClassOf>
    <rdfs:label xml:lang="en">E58 Measurement Unit</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E58</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E9_Move">
    <rdfs:label xml:lang="en">E9 Move</rdfs:label>
    <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. (Clarke, 1992)
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979 (Treasures of Tutankhamun, exhibition catalogue, 1972) .


In First Order Logic:
E9(x) ⊃ E7(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P25_moved"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P26_moved_to"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P27_moved_from"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E9</skos:notation>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E55_Type">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E55</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P135i_was_created_by"/>
        </owl:onProperty>
        <owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:maxCardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E28_Conceptual_Object"/>
    <rdfs:label xml:lang="en">E55 Type</rdfs:label>
    <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 is the CIDOC CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CIDOC CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term): E55Type. Such hierarchies may be extended with additional properties. 


Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]


In First Order Logic:
E55(x) ⊃ E28(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E15_Identifier_Assignment">
    <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. Instances of E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure. 

Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.

The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.


Examples:
- Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
- Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for the respective work
- On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” to Guillaume de Machaut


In First Order Logic:
E15(x) ⊃ E13(x)</rdfs:comment>
    <rdfs:label xml:lang="en">E15 Identifier Assignment</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E15</skos:notation>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P37_assigned"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E42_Identifier"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E87_Curation_Activity">
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P147_curated"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E78_Curated_Holding"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E87</skos:notation>
    <rdfs:label xml:lang="en">E87 Curation Activity</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the activities that result in the continuity of management and the preservation and evolution of instances of E78 Collection, following an implicit or explicit curation plan.

It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded.

Items are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an instance of E78 Collection for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity.


Examples:
- the curation of Mikael Heggelund Foslie's coralline red algae Herbarium 1876 – 1909 (when Foslie died), now at Museum of Natural History and Archaeology, Norway


In First Order Logic:
E87(x) ⊃ E7(x)</rdfs:comment>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E17_Type_Assignment">
    <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 Lament Cloth, October 2nd
- the determination of a cactus in Martin Doerr's garden as 'Cereus hildmannianus K.Schumann', July 2003

In First Order Logic:
E17(x) ⊃ E13(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P42_assigned"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P41_classified"/>
        </owl:onProperty>
        <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
        >1</owl:cardinality>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E17</skos:notation>
    <rdfs:label xml:lang="en">E17 Type Assignment</rdfs:label>
  </owl:Class>
  <owl:Class rdf:about="http://erlangen-crm.org/current/E69_Death">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >E69</skos:notation>
    <rdfs:label xml:lang="en">E69 Death</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This class comprises the deaths of human beings.
If a person is killed, the death should be documented as an instance of both E69 Death and E7 Activity. The death or perishing of other living beings should be documented asinstances of E64 End of Existence.


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


In First Order Logic:
E69(x) ⊃ E64(x)</rdfs:comment>
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P100_was_death_of"/>
        </owl:onProperty>
        <owl:someValuesFrom rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
      </owl:Restriction>
    </rdfs:subClassOf>
    <rdfs:subClassOf rdf:resource="http://erlangen-crm.org/current/E64_End_of_Existence"/>
  </owl:Class>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P71i_is_listed_in">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P71i</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by"/>
    </rdfs:subPropertyOf>
    <rdfs:label xml:lang="en">P71 is listed in</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E32_Authority_Document"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P71_lists"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P103i_was_intention_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P103_was_intended_for"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P103 was intention of</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P103i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P43i_is_dimension_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P43i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P43_has_dimension"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <rdfs:label xml:lang="en">P43 is dimension of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P11i_participated_in">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P11i</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P12i_was_present_at"/>
    </rdfs:subPropertyOf>
    <rdfs:label xml:lang="en">P11 participated in</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P11_had_participant"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P16i_was_used_for">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:label xml:lang="en">P16 was used for</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P16i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P16_used_specific_object"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P15i_influenced"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P12i_was_present_at"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P179_had_sales_price">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 maychange in the course of the purchase activity.


Examples:	
- The sale of Vincent van Gogh’s “Vase with Fifteen Sunflowers” on 1987/03/30 (E96) had sales price Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97)


In First Order Logic:
P179(x,y) ⊃ E96(x)
P179(x,y) ⊃ E97(y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P179i_was_sales_price_of"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E97_Monetary_Amount"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E96_Purchase"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P179 had sales price</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P73i_is_translation_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P73_has_translation"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P73 is translation of</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P73i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P130_shows_features_of"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P108_has_produced">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P108</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P108i_was_produced_by"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92_brought_into_existence"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P31_has_modified"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E12_Production"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E24 Physical Human-Made Thing that came into existence as a result of the instance of E12 Production.

The identity of an instance of E24 Physical Human-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Human-Made Thing.


Examples:
- The building of Rome (E12) has produced Τhe Colosseum (E22)


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>
    <rdfs:label xml:lang="en">P108 has produced</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P74i_is_current_or_former_residence_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P74_has_current_or_former_residence"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P74i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P74 is current or former residence of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67_refers_to">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P67</skos:notation>
    <rdfs:comment xml:lang="en">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 for 4 July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55)


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>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:label xml:lang="en">P67 refers to</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P141_assigned">
    <rdfs:label xml:lang="en">P141 assigned</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P141i_was_assigned_by"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P141</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity used in the attribution. The instance of E1 CRM Entity here plays the role of the range of the attribution.

The kind of attribution made should be documented using P177 assigned property type.


Examples:
- February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned Martin Doerr (E21)
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned object identifier 232


In First Order Logic:
P141(x,y) ⊃ E13(x)
P141(x,y) ⊃ E1(y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P76_has_contact_point">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E41_Appellation"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P76</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address.

Examples:
- RLG (E40) has contact point "bl.ric@rlg.org" (E41)

In First Order Logic:
P76(x,y) ⊃ E39(x)
P76(x,y) ⊃ E41(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P76 has contact point</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P76i_provides_access_to"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P111i_was_added_by">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P111 was added by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P111i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E79_Part_Addition"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P111_added"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P16i_was_used_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P109i_is_current_or_former_curator_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E78_Curated_Holding"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P109_has_current_or_former_curator"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P109i</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P49i_is_former_or_current_keeper_of"/>
    </rdfs:subPropertyOf>
    <rdfs:label xml:lang="en">P109 is current or former curator of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P30i_custody_transferred_through">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P30i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E10_Transfer_of_Custody"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P30_transferred_custody_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P30 custody transferred through</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P141i_was_assigned_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P141i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P141_assigned"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    <rdfs:label xml:lang="en">P141 was assigned by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P12i_was_present_at"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P12</skos:notation>
    <rdfs:label xml:lang="en">P12 occurred in the presence of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
    <rdfs:comment xml:lang="en">Scope note:
This property describes the active or passive presence of an E77 Persistent Item in an instance of E5 Event without implying any specific role.

It documents known events in which an instance of E77 Persistent Item was present during the course of its life or history. For example, an object may be the desk, now in a museum on which a treaty was signed. The instance of E53 Place and the instance of E52 Time-Span where and when these events happened provide us with constraints about the presence of the related instance E77 Persistent Item in the past. Instances of E90 Symbolic Object, in particular information objects, are physically present in events via at least one of the instances of E18 Physical Thing carrying them. Note, that the human mind can be such a carrier. A precondition for a transfer of information to a person or another new physical carrier is the presence of the respective information object and this person or physical thing in one event.


Examples:
- Deckchair 42 (E19) was present at The sinking of the Titanic (E5)


In First Order Logic:
P12(x,y) ⊃ E5(x)
P12(x,y) ⊃ E77(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P134i_was_continued_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P134i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P15i_influenced"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P174i_ends_after_the_start_of"/>
    </rdfs:subPropertyOf>
    <rdfs:label xml:lang="en">P134 was continued by</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P134_continued"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P105i_has_right_on">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P105_right_held_by"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:label xml:lang="en">P105 has right on</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P105i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E72_Legal_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P182i_starts_after_or_with_the_end_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P182_ends_before_or_at_the_start_of"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P185i_ends_after_the_end_of"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P176i_starts_after_the_start_of"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P182_ends_before_or_at_the_start_of">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets}


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)</rdfs:comment>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P185_ends_before_the_end_of"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P176_starts_before_the_start_of"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P182 ends befort or at the start of</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P182i_starts_after_or_with_the_end_of"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P186i_is_produced_by">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P186 produced thing of product type</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P186_produced_thing_of_product_type"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P33i_was_used_by">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:label xml:lang="en">P33 was used by</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P33_used_specific_technique"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P33i</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P16i_was_used_for"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P51i_is_former_or_current_owner_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P51_has_former_or_current_owner"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P51i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P51 is former or current owner of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P143i_was_joined_by">
    <rdfs:label xml:lang="en">P143 was joined by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E85_Joining"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P143_joined"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P143i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P187_has_production_plan">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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:
- the production plans (E29) for Volkswagen Type 11 (Beetle) (E99)


In First Order Logic:
P187(x,y) ⊃ E99(x)
P187(x,y) ⊃ E29(y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P187i_is_production_plan_for"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E99_Product_Type"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P187 has production plan</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P176_starts_before_the_start_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P176i_starts_after_the_start_of"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P175_starts_before_or_with_the_start_of"/>
    </rdfs:subPropertyOf>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Astart &lt; Bstart is true. 

This property is part of the set of temporal primitives P173 – P176, P182 – P185.


This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, contains, finished-by}


In First Order Logic:
P176(x,y) ⊃ E2(x)
P176(x,y) ⊃ E2(y)
P176(x,y) ⊃ P175(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P176 starts before the start of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P26i_was_destination_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E9_Move"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P26_moved_to"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P26 was destination of</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P7i_witnessed"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P26i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P102_has_title">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P102i_is_title_of"/>
    </owl:inverseOf>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E35 Title has been applied to an instance of E71 Human-Made Thing.

The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the title and the thing to be further clarified, for example, if the title was a given title, a supplied title etc. 
It allows any human-made material or immaterial thing to be given a title. It is possible to imagine a title being created without a specific object in mind.


Examples:
- the first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55)


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>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P102</skos:notation>
    <rdfs:label xml:lang="en">P102 has title</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E35_Title"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P1_is_identified_by"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P174i_ends_after_the_start_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P173i_ends_with_or_after_the_start_of"/>
    </rdfs:subPropertyOf>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P174 ends after the start of</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P174_starts_before_the_end_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P76i_provides_access_to">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P76i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:label xml:lang="en">P76 provides access to</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P76_has_contact_point"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P46i_forms_part_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P46_is_composed_of"/>
    </owl:inverseOf>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P46 forms part of</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P46i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P95_has_formed">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:comment xml:lang="en">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>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E66_Formation"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92_brought_into_existence"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P95i_was_formed_by"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P95 has formed</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P95</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P21_had_general_purpose">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P21</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:label xml:lang="en">P21 had general purpose</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property describes an intentional relationship between an E7 Activity and some general goal or purpose.

This may involve activities intended as preparation for some type of activity or event. P21 had general purpose (was purpose of) differs from P20 had specific purpose (was purpose of) in that no occurrence of an event is implied as the purpose.


Examples:
- Van Eyck's pigment grinding (E7) had general purpose painting (E55)
- the setting of trap 2742 on May 17th 1874 (E7) had general purpose Catching Moose (E55) (Activity type)


In First Order Logic:
P21(x,y) ⊃ E7(x)
P21(x,y) ⊃ E55(y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P21i_was_purpose_of"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P152i_is_parent_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P152i</skos:notation>
    <rdfs:label xml:lang="en">P152 is parent of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P152_has_parent"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P123_resulted_in">
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92_brought_into_existence"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P123i_resulted_from"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P123</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance or instances of E18 Physical Thing that are the result of an instance of E81 Transformation. New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the links to the common instance of E81 Transformation


Examples:
- the transformation of the Venetian Loggia in Heraklion into a city hall (E81)  resulted in the City Hall of Heraklion (E22)
- the death and mummification of Tut-Ankh-Amun (E81) resulted in the Mummy of Tut Tut-Ankh-Amun (E22 and E20)


In First Order Logic:
P123(x,y) ⊃ E81(x)
P123(x,y) ⊃ E77(y)
P123(x,y) ⊃ P92(x,y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E81_Transformation"/>
    <rdfs:label xml:lang="en">P123 resulted in</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P152_has_parent">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P152i_is_parent_of"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P152</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 ‘E21Person’ through ‘P98i was born’, ‘E67 Birth’, ‘P96 by mother’ to ‘E21 Person’, and from ‘E21Person’ through ‘P98i was born’, ‘E67 Birth’, ‘P97 from father’ to ‘E21 Person’.


Examples:
- Gaius Octavius (E21) has parent Julius Caesar (E21)
- Steve Jobs (E21) has parent Joanne Simpson (biological mother) (E21)
- Steve Jobs (E21) has parent Clara Jobs (adoption mother) (E21)


In First Order Logic:
P152(x,y) ⊃ E21(x)
P152(x,y) ⊃ E21(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P152 has parent</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P93_took_out_of_existence">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P93</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
    <rdfs:comment xml:lang="en">Scope note:
This property links an instance of E64 End of Existence to the instance 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)


In First Order Logic:
P93 (x,y) ⊃ E64(x)
P93 (x,y) ⊃ E77(y)
P93(x,y) ⊃ P12(x,y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P93i_was_taken_out_of_existence_by"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E64_End_of_Existence"/>
    <rdfs:label xml:lang="en">P93 took out of existence</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P15_was_influenced_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P15</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P15i_influenced"/>
    </owl:inverseOf>
    <rdfs:comment xml:lang="en">Scope note:
This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it.

The property has more specific sub properties.


Examples:
- the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22)


In First Order Logic: 
P15 (x,y) ⊃ E7(x)
P15 (x,y) ⊃ E1(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P15 was influenced by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P49i_is_former_or_current_keeper_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P49i</skos:notation>
    <rdfs:label xml:lang="en">P49 is former or current keeper of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P49_has_former_or_current_keeper"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P164i_was_time-span_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P164_during"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P160i_is_temporal_projection_of"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P145_separated">
    <rdfs:label xml:lang="en">P145 separated</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P145i_left_by"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P11_had_participant"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P145</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E86_Leaving"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving.


Examples:
- The end of Sir Isaac Newton's duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 separated Sir Isaac Newton
- George Washington's leaving office in 1797 separated George Washington
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland February 1. 1985 (E86) separated Greenland (E74)


In First Order Logic:
P145(x,y) ⊃ E86(x)
P145(x,y) ⊃ E39(y)
P145(x,y) ⊃ P11(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P143_joined">
    <rdfs:label xml:lang="en">P143 joined</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P143</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P11_had_participant"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E85_Joining"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P143i_was_joined_by"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E39 Actor that becomes member of an instance of E74 Group in an instance of E85 Joining.

Joining events allow for describing people becoming members of a group with the more detailed path E74 Group, P144i gained member by, E85 Joining, P143 joined , E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).


Examples:
- The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined Sir Isaac Newton (E21)
- The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined Mikhail Sergeyevich Gorbachev (E21)
- The implementation of the membership treaty January 1. 1973 between EU and Denmark (E85) joined Denmark (E74)


In First Order Logic:
P143(x,y) ⊃ E85(x)
P143(x,y) ⊃ E39(y)
P143(x,y) ⊃ P11(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P65i_is_shown_by">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P65_shows_visual_item"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P128i_is_carried_by"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P65i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <rdfs:label xml:lang="en">P65 is shown by</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E36_Visual_Item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P25_moved">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P25</skos:notation>
    <rdfs:label xml:lang="en">P25 moved</rdfs:label>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P25i_moved_by"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E9_Move"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P151_was_formed_from">
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P11_had_participant"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E66_Formation"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P151</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P151i_participated_in"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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)


In First Order Logic:
P151(x,y) ⊃ E66(x)
P151(x,y) ⊃ E74(y)
P151(x,y) ⊃ P11(x,y)</rdfs:comment>
    <rdfs:label xml:lang="en">P151 was formed from</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P31_has_modified">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P31i_was_modified_by"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P31</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E24 Physical Human-Made Thing modified in an instance of E11 Modification.


Examples:
- rebuilding of the Reichstag (E11) has modified the Reichstag in Berlin (E24)


In First Order Logic:
P31(x,y) ⊃ E11(x)
P31(x,y) ⊃ E24(y)
P31(x,y) ⊃ P12(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E11_Modification"/>
    <rdfs:label xml:lang="en">P31 has modified</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P53_has_former_or_current_location">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P53i_is_former_or_current_location_of"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P53 has former or current location</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P53</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:comment xml:lang="en">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 TimeSpan 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. 
P53 has former or current location (is former or current location of) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from ‘E19 Physical Object’, 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)


In First Order Logic:
P53(x,y) ⊃ E18(x)
P53(x,y) ⊃ E53(y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P177_assigned_property_type">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P177 assigned property type</rdfs:label>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 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:
- February 1997 Current Ownership Assessment of Martin Doerr’s silver cup (E13) assigned property type P52 has former or current owner (is former or current keeper of) (E55)
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property type P48 has preferred identifier (is preferred identifier of) (E55)


In First Order Logic:
 P177(x,y) ⊃ E13(x)
 P177(x,y) ⊃ E55(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P2_has_type"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P62i_is_depicted_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P62i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:label xml:lang="en">P62 is depicted by</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P62_depicts"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P101_had_as_general_use">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P101i_was_use_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <rdfs:label xml:lang="en">P101 had as general use</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E70 Thing with an instance of E55 Type describing its general usage.

It allows the relationship between particular things, both physical and immaterial, and general methods and techniques of use to be documented. Thus it can be asserted that a baseball bat had a general use for sport and a specific use for threatening people during the Great Train Robbery.


Examples:
- Tony Gill's Ford Mustang (E22) had as general use transportation (E55)


In First Order Logic:
P101(x,y) ⊃ E70(x)
P101(x,y) ⊃ E55(y)
P101(x,y) ⊃ (∃z)[E7(z) ∧ P16(z,x) ∧ P2(z,y)]</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P101</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P184i_ends_with_or_after_the_end_of">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P174i_ends_after_the_start_of"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P184_ends_before_or_with_the_end_of"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P184 ends before or with the end of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P38i_was_deassigned_by">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141i_was_assigned_by"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E42_Identifier"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P38_deassigned"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P38 was deassigned by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P38i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E15_Identifier_Assignment"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P188i_is_production_tool_for">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P188_requires_production_tool"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E99_Product_Type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P52_has_current_owner">
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P51_has_former_or_current_owner"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P105_right_held_by"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P52i_is_current_owner_of"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P52</skos:notation>
    <rdfs:comment xml:lang="en">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.

P52 has current owner (is current owner of) is a shortcut for the more detailed path from ‘E18 Physical Thing through’, ‘P24i changed ownership through, ‘E8 Acquisition’, ‘P22 transferred title to’, to ‘E39 Actor’, if and only if this acquisition event is the most recent.


Examples:
- paintings from the Iveagh Bequest (E18) has current owner «English Heritage» (E74)


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)</rdfs:comment>
    <rdfs:label xml:lang="en">P52 has current owner</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P13_destroyed">
    <rdfs:comment xml:lang="en">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 Desaster (E6) destroyed The Tay Bridge (E22)


In First Order Logic:
P13 (x,y) ⊃ E6 (x)
P13 (x,y) ⊃ E18(y)
P13 (x,y) ⊃ P93(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E6_Destruction"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P93_took_out_of_existence"/>
    <rdfs:label xml:lang="en">P13 destroyed</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P13</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P13i_was_destroyed_by"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P147i_was_curated_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E87_Curation_Activity"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E78_Curated_Holding"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P147i</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P147_curated"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P147 was curated by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P110i_was_augmented_by">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P110_augmented"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P110i</skos:notation>
    <rdfs:label xml:lang="en">P110 was augmented by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E79_Part_Addition"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P31i_was_modified_by"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P191i_was_duration_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P191_had_duration"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P156_occupies">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P156i_is_occupied_by"/>
    </owl:inverseOf>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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, 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, E53 Place. 


In First Order Logic:
P156(x,y) ⊃ E53(y)
P156(x,y) ⊃ E18(x)
P156 (x,y) = [E18(x) ∧ E53(y) ∧ P196(x,z) ∧ P161(z,y) ∧ P157(y,x)]</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P156</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P53_has_former_or_current_location"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P157i_provides_reference_space_for"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P156 occupies</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P45i_is_incorporated_in">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E57_Material"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P45 is incorporated in</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P45_consists_of"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P45i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P21i_was_purpose_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P21i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P21_had_general_purpose"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:label xml:lang="en">P21 was purpose of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P123i_resulted_from">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E81_Transformation"/>
    <rdfs:label xml:lang="en">P123 resulted from</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P123_resulted_in"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92i_was_brought_into_existence_by"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P123i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P54_has_current_permanent_location">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <rdfs:label xml:lang="en">P54 has current permanent location</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P54</skos:notation>
    <rdfs:comment xml:lang="en">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)

In First Order Logic:
P54(x,y) ⊃ E19(x)
P54(x,y) ⊃ E53(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P54i_is_current_permanent_location_of"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P1_is_identified_by">
    <rdfs:comment xml:lang="en">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.

P1 is identified by (identifies), is a shortcut for the path from ‘E1 CRM Entity’ through ‘P140i was attributed by’, ‘E15 Identifier Assignment’, ‘P37 assigned’,‘E42 Identifier’.


Examples:
- the capital of Italy (E53) is identified by "Rome" (E48)
- text 25014-32 (E33) is identified by "The Decline and Fall of the Roman Empire" (E35)


In First Order Logic:
P1(x,y) ⊃ E1(x)
P1(x,y) ⊃ E41(y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P1i_identifies"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E41_Appellation"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P1</skos:notation>
    <rdfs:label xml:lang="en">P1 is identified by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P72_has_language">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P72i_is_language_of"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P72</skos:notation>
    <rdfs:label xml:lang="en">P72 has language</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E56_Language"/>
    <rdfs:comment xml:lang="en">Scope note:
This property describes the E56 Language of an E33 Linguistic Object.

Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.

Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)

In First Order Logic:
P72(x,y) ⊃ E33(x)
P72(x,y) ⊃ E56(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P173i_ends_with_or_after_the_start_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P173_starts_before_or_at_the_end_of"/>
    </owl:inverseOf>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P173 starts before or at the end of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P100_was_death_of">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P93_took_out_of_existence"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P100i_died_in"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P100 was death of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P100</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property links an E69 instance of E69 Death event 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)

In First Order Logic:
P100(x,y) ⊃ E69(x)
P100(x,y) ⊃ E21(y)
P100(x,y) ⊃ P93(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E69_Death"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P166i_had_presence">
    <rdfs:subPropertyOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P10i_contains"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P166_was_a_presence_of"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P113i_was_removed_by">
    <rdfs:label xml:lang="en">P113 was removed by</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P12i_was_present_at"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P113i</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P113_removed"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E80_Part_Removal"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P142_used_constituent">
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E15 Identifier Assignment with the instance of E90 Symbolic Object used as constituent of an instance of E42 Identifier in this act of assignment.


Examples:
- On June 1, 2001 assigning the personal name identifier “Guillaume, de Machaut, ca. 1300-1377” (E15) used constituent “ca. 1300-1377” (E41) 
- Assigning a uniform title to the anonymous textual work known as ‘The Adoration of the Shepherds’(E15) used constituent ‘Coventry’ (E41) 
- Assigning a uniform title to Pina Bausch’s choreographic work entitled ‘Rite of spring’ (E15) used constituent ‘(Choreographic Work: Bausch)’(E90) 
- 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’ (E41) 
- Assigning the corporate name identifier ‘Univerza v Ljubljani. Oddelek za bibliotekarstvo’ to The Department for library science of the University of Ljubljana (E15) used constituent ‘Univerza v Ljubljani’ (E42)


In First Order Logic:
P142(x,y) ⊃ E15(x)
P142(x,y) ⊃ E90(y)
P142(x,y) ⊃ P16(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E15_Identifier_Assignment"/>
    <rdfs:label xml:lang="en">P142 used constituent</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P16_used_specific_object"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P142</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P142i_was_used_in"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P55_has_current_location">
    <rdfs:comment xml:lang="en">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.

P55 has current location (currently holds) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from ‘E19 Physical Object’,through, ‘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)


In First Order Logic:
P55(x,y) ⊃ E19(x)
P55(x,y) ⊃ E53(y)
P55(x,y) ⊃ P53(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P55</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P55i_currently_holds"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P55 has current location</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P53_has_former_or_current_location"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P174_starts_before_the_end_of">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P174 starts before the end of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P173_starts_before_or_at_the_end_of"/>
    </rdfs:subPropertyOf>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Astart &lt; Bend is true. 

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983] :{before, meets, overlaps, starts, started-by, contains, finishes, finished-by, equals, during,  overlapped by}

Typically, this property is a consequence of a known influence of some event on another event or activity, such as a novel written by someone being continued by someone else, or the knowledge of a defeat on a distant battlefield causing people to end their ongoing activities.


In First Order Logic:
P174(x,y) ⊃ E2(x)
P174(x,y) ⊃ E2(y)
P174(x,y) ⊃ P173(x,y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P174i_ends_after_the_start_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P20_had_specific_purpose">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P20</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the relationship between a preparatory activity, an instance of E7 Activity and the instance of E7 Event it is intended to be preparation for.

This includes activities, orders and other organisational actions, taken in preparation for other activities or events.

P20 had specific purpose (was purpose of) implies that an activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, one may document the unrealized intention using P21 had general purpose (was purpose of): E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure.


Examples:
- Van Eyck's pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12)


In First Order Logic:
P21(x,y) ⊃ E7(x)
P21(x,y) ⊃ E55(y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P20i_was_purpose_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:label xml:lang="en">P20 had specific purpose</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P164_during">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Scope note:
This property relates an instance of E93 Presence with the chosen instance of E52 Time-Span that defines the time-slice of the spacetime volume that this instance of E93 Presence is related to by the property P166 was a presence of (had presence).


Examples:
- 2016-02-09 (E52) was time-span of the last day of the 2016 Carnival in Cologne (E93).


In First Order Logic:
P164 (x,y) ⊃ E93(x)
P164 (x,y) ⊃ E52(y)
P164 (x,y) ⊃ P160(x,y)</rdfs:comment>
    <rdfs:label xml:lang="en">P164 is restricted by</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P160_has_temporal_projection"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P164</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P164i_was_time-span_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P96i_gave_birth">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P96i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P96_by_mother"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E67_Birth"/>
    <rdfs:label xml:lang="en">P96 gave birth</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P100i_died_in">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E69_Death"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P93i_was_taken_out_of_existence_by"/>
    </rdfs:subPropertyOf>
    <rdfs:label xml:lang="en">P100 died in</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P100i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P100_was_death_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P16_used_specific_object">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P15_was_influenced_by"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P16i_was_used_for"/>
    <rdfs:label xml:lang="en">P16 used specific object</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <rdfs:comment xml:lang="en">Scope note:
This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an instance of E7 Activity.

This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer.

Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.


Examples:
- the writing of this scope note (E7) used specific object Nicholas Crofts' computer (E22) mode of use Typing Tool; Storage Medium (E55)
- the people of Iraq calling the place identified by TGN '7017998' (E7) used specific object "Quyunjig" (E44) mode of use Current; Vernacular (E55)


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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P16</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P11_had_participant">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:label xml:lang="en">P11 had participant</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P11</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property describes the active or passive participation of instances of E39 Actors in an instance of E5 Event.

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


Examples:
- Napoleon (E21) participated in The Battle of Waterloo (E7)
- Maria (E21) participated in Photographing of Maria (E7)


In First Order Logic:
P11(x,y) ⊃ E5(x)
P11(x,y) ⊃ E39(y)
P11(x,y) ⊃ P12(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P176i_starts_after_the_start_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P176_starts_before_the_start_of"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P175i_starts_after_or_with_the_start_of"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P19i_was_made_for">
    <rdfs:label xml:lang="en">P19 was made for</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P19_was_intended_use_of"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P19i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P51_has_former_or_current_owner">
    <rdfs:label xml:lang="en">P51 has former or current owner</rdfs:label>
    <rdfs:comment xml:lang="en">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. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from ‘E18 Physical Thing’ through ‘P24i changed ownership through’, ‘E8 Acquisition’, ‘P23 transferred title from’, or ‘P22 transferred title to’,to ‘E39 Actor’.


Examples:
- paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21)


In First Order Logic:
P51(x,y) ⊃ E18(x)
P51(x,y) ⊃ E39(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P51</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P51i_is_former_or_current_owner_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P19_was_intended_use_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P19i_was_made_for"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:label xml:lang="en">P19 was intended use of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    <rdfs:comment xml:lang="en">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)


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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P19</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P40_observed_dimension">
    <rdfs:comment xml:lang="en">Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.


Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)


In First Order Logic:
P40(x,y) ⊃ E16(x)
P40(x,y)⊃ E54(y)
P40(x,y) ⊃ P141(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141_assigned"/>
    <rdfs:label xml:lang="en">P40 observed dimension</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P40</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P40i_was_observed_in"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E16_Measurement"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P69_has_association_with">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P69i_is_associated_with"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:label xml:lang="en">P69 has association with</rdfs:label>
    <rdfs:comment xml:lang="en">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 P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc. 
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
This property is transitive.


Examples:
- Procedure for glass blowing (E29) has association with procedure for glass heating (E29) 
- 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) 
- Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type 'has part' (E55). Preparation of parchment (E29) has association with stretching 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).
- 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)'.


In First Order Logic:
P69 (x,y) ⊃ E29(x)
P69 (x,y) ⊃ E29(y)
P69(x,y,z) ⊃ [P69(x,y) ∧ E55(z)]
P69(x,y) ⊃P69(y,x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P69</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P45_consists_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P45</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E57_Material"/>
    <rdfs:label xml:lang="en">P45 consists of</rdfs:label>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P45(x,y) ⊃ E18(x)
P45(x,y) ⊃ E57(y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P45i_is_incorporated_in"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P35_has_identified">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P35</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the E3 Condition State that was observed in an E14 Condition Assessment activity.


Examples:
- 1997 condition assessment of silver cup 232 (E14) has identified oxidation traces were present in 1997 (E3) has type oxidation traces (E55)


In First Order Logic:
P35(x,y) ⊃E14(x)
P35(x,y) ⊃ E3(y)
P35(x,y) ⊃ P141(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141_assigned"/>
    <rdfs:label xml:lang="en">P35 has identified</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P35i_was_identified_by"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E14_Condition_Assessment"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P53i_is_former_or_current_location_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P53_has_former_or_current_location"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P53i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P53 is former or current location of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P196_defines">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P196i_is_defined_by"/>
    </owl:inverseOf>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P196 defines</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 E92 Spacetime Volume depends uniquely on the identity of the instance of E18 Physical Thing, whose existence defines it. It constitutes a phenomenal spacetime volume as defined in CRMgeo (Doerr and 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.


In First Order Logic:
P196(x,y) ⊃ E18(x)
P196(x,y) ⊃ E92(y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P99_dissolved">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P99</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E68_Dissolution"/>
    <rdfs:label xml:lang="en">P99 dissolved</rdfs:label>
    <rdfs:comment xml:lang="en">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)


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>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P93_took_out_of_existence"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11_had_participant"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P99i_was_dissolved_by"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P130i_features_are_also_found_on">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P130i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <rdfs:label xml:lang="en">P130 features are also found on</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P130_shows_features_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P39_measured">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E16_Measurement"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P39</skos:notation>
    <rdfs:label xml:lang="en">P39 measured</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P140_assigned_attribute_to"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P39i_was_measured_by"/>
    </owl:inverseOf>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E16 Measurement with the instance of E1 CRM Entity to which it applied. An instance of E1 CRM Entity may be measured more than once. Material and immaterial things and processes may be measured, e.g. the number of words in a text, or the duration of an event.


Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)


In First Order Logic:
P39(x,y) ⊃ E16(x)
P39(x,y) ⊃ E1(y)
P39(x,y) ⊃ P140(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P157i_provides_reference_space_for">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P157i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P157 provides reference space for</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P157_is_at_rest_relative_to"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P112_diminished">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P31_has_modified"/>
    <rdfs:label xml:lang="en">P112 diminished</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P112</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance E24 Physical Human-Made Thing that was diminished by an instance of E80 Part Removal.

Although an instance of E80 Part removal activity normally concerns only one instance of E24 Physical Human-Made Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single instance of E80 Part Removal activity. 


Examples:
- the coffin of Tut-Ankh-Amun (E22) was diminished by The opening of the coffin of Tut-Ankh-Amun (E80)


In First Order Logic:
P112(x,y) ⊃ E80(x)
P112(x,y) ⊃ E24(y)
P112(x,y) ⊃ P31(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E80_Part_Removal"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P112i_was_diminished_by"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P62_depicts">
    <rdfs:label xml:lang="en">P62 depicts</rdfs:label>
    <rdfs:comment xml:lang="en">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, E1 CRM Entity. P138.1 mode of representation “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)
- the 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E24) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55)


In First Order Logic:
P62(x,y) ⊃ E24(x)
P62(x,y) ⊃ E1(y)
P62(x,y,z) ⊃ [P62(x,y) ∧ E55(z)]

Properties: P62.1 mode of depiction: E55 Type</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P62</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P62i_is_depicted_by"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P41i_was_classified_by">
    <rdfs:label xml:lang="en">P41 was classified by</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P140i_was_attributed_by"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P41_classified"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P41i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E17_Type_Assignment"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P23i_surrendered_title_through">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P23_transferred_title_from"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P23i</skos:notation>
    <rdfs:label xml:lang="en">P23 surrendered title through</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E8_Acquisition"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14i_performed"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P108i_was_produced_by">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P108_has_produced"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P108i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <rdfs:label xml:lang="en">P108 was produced by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E12_Production"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92i_was_brought_into_existence_by"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P31i_was_modified_by"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P97_from_father">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P97</skos:notation>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P97(x,y) ⊃ E67(x)
P97(x,y) ⊃ E21(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E67_Birth"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P97i_was_father_for"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P97 from father</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P2_has_type">
    <rdfs:comment xml:lang="en">Scope note:
This property allows sub typing of CIDOC CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus.

The CIDOC CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CIDOC CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E41 Appellation, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CIDOC CRM hierarchy. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.


Examples:
- "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55)


In First Order Logic:
P2(x,y) ⊃ E1(x)
P2(x,y) ⊃ E55(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P2</skos:notation>
    <rdfs:label xml:lang="en">P2 has type</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P2i_is_type_of"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P195_was_presence_of">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P195 was presence of</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P195i_had_presence"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 were 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), E93 Presence.


In First Order Logic:
P195(x,y) ⊃ E93(x)
P195(x,y) ⊃ E18(y)
P195(x,y) = (∃z)[E9(z) ∧ P196 (y,z) ∧ P166(z,x)]</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P70_documents">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P67_refers_to"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E31_Document"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P70i_is_documented_in"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P70 documents</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:comment xml:lang="en">Scope note:
This property describes the CRM Entities documented as instances of E31 Document.
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement


Examples:
- the British Museum catalogue (E31) documents the British Museum's Collection (E78)


In First Order Logic:
P70 (x,y) ⊃ E31(x)
P70 (x,y) ⊃ E1(y)
P70(x,y) ⊃ P67(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P70</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P102i_is_title_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P102i</skos:notation>
    <rdfs:label xml:lang="en">P102 is title of</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P1i_identifies"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P102_has_title"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E35_Title"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P105_right_held_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P105</skos:notation>
    <rdfs:comment xml:lang="en">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.
P105 right held by (has right on) is a shortcut of the fully developed path E72 Legal Object,P104 is subject to, E30 Right, P75i is possessed by, E39 Actor.


Examples:
- Beatles back catalogue (E73) right held by Michael Jackson (E21)


In First Order Logic:
P105(x,y) ⊃ E72(x)
P105(x,y) ⊃ E39(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P105i_has_right_on"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E72_Legal_Object"/>
    <rdfs:label xml:lang="en">P105 right held by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P12i_was_present_at">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P12i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
    <rdfs:label xml:lang="en">P12 was present at</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P146_separated_from">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P146i_lost_member_by"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11_had_participant"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E86_Leaving"/>
    <rdfs:label xml:lang="en">P146 separated from</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving.

Although a Leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well.


Examples:
- The end of Sir Isaac Newton's duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 separated from the Convention Parliament
- George Washington's leaving office in 1797 separated from the office of President of the United States
- The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland February 1. 1985 separated from EU (E74)


In First Order Logic:
P146(x,y) ⊃ E86(x)
P146(x,y) ⊃ E74(y)
P146(x,y) ⊃ P11(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P146</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P74_has_current_or_former_residence">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P74i_is_current_or_former_residence_of"/>
    <rdfs:label xml:lang="en">P74 has current or former residence</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P74(x,y) ⊃ E39(x)
P74(x,y) ⊃ E53(y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P74</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P140i_was_attributed_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P140i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    <rdfs:label xml:lang="en">P140 was attributed by</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P140_assigned_attribute_to"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P161_has_spatial_projection">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P161i_is_spatial_projection_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P161</skos:notation>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Scope note:
This property associates an instance of an instance of E92 Spacetime Volume with an instance of E53 Place that is the result of the spatial projection of the instance of the E92 Spacetime Volume on a reference space.

In general there can be more than one useful reference space (for reference space see P156 occupies and P157 is at rest relative to) to describe the spatial projection of a spacetime volume, for example, in describing a sea battle, the difference between the battle ship and the seafloor as reference spaces. Thus it can be seen that the projection is not unique.

The spatial projection is the actual spatial coverage of a spacetime volume, which normally has fuzzy boundaries except for instances of E92 Spacetime Volumes which are geometrically defined in the same reference system as the range of this property are an exception to this and do not have fuzzy boundaries. Modelling explicitly fuzzy spatial projections serves therefore as a common topological reference of different spatial approximations rather than absolute geometric determination, for instance for relating outer or inner spatial boundaries for the respective spacetime volumes.

In case the domain of an instance of P161 has spatial projection is an instance of E4 Period, the spatial projection describes all areas that period was ever present at, for instance, the Roman Empire. 

This property is part of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection, which in turn is implied by P156 occupies (is occupied by).

This property is part of the fully developed path from E4 Period through P161 has spatial projection,
E53 Place, P89 falls within (contains) to E53 Place, which in turn is shortcut by P7 took place at
(witnessed).


Example:
The Roman Empire P161 has spatial projection all areas ever claimed by Rome.


In First Order Logic:
P161(x,y) ⊃ E92(x)
P161(x,y) ⊃ E53(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P161 has spatial projection</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P34_concerned">
    <rdfs:label xml:lang="en">P34 concerned</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E14_Condition_Assessment"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E18 Physical Thing that was assessed during an instance of E14 Condition Assessment activity.
Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the instance of E18 Physical Thing does not need to be present or extant at the time of assessment.


Examples:
- 1997 condition assessment of the silver collection (E14) concerned silver cup 232 (E22)


In First Order Logic:
P34(x,y) ⊃ E14(x)
P34(x,y) ⊃ E18(y)
P34(x,y) ⊃ P140(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P34</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P140_assigned_attribute_to"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P34i_was_assessed_by"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P31i_was_modified_by">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P31_has_modified"/>
    <rdfs:label xml:lang="en">P31 was modified by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P31i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E11_Modification"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12i_was_present_at"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P128_carries">
    <rdfs:label xml:lang="en">P128 carries</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P128i_is_carried_by"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P130_shows_features_of"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P128</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P128(x,y) ⊃ E18(x)
P128(x,y) ⊃ E90(y)
P128(x,y) ⊃ P130(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P140_assigned_attribute_to">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity about which it made an attribution. The instance of E1 CRM Entity plays the role of the domain of the attribution.

The kind of attribution made should be documented using P177 assigned property type.


Examples:
- February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned attribute to Martin Doerr's silver cup (E19)
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E19)


In First Order Logic:
P140(x,y) ⊃ E13(x)
P140(x,y) ⊃ E1(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P140 assigned attribute to</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P140</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E13_Attribute_Assignment"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P140i_was_attributed_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P144_joined_with">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P144i_gained_member_by"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:label xml:lang="en">P144 joined with</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11_had_participant"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E85_Joining"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P144</skos:notation>
    <rdfs:comment xml:lang="en">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)
- 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) with P144.1 kind  of member President (E55)
- The implementation of the membership treaty January 1. 1973 between EU and Denmark (E85) joined with EU (E74)


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:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P135i_was_created_by">
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P94i_was_created_by"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P135_created_type"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P135i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:label xml:lang="en">P135 was created by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E83_Type_Creation"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P146i_lost_member_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E86_Leaving"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:label xml:lang="en">P146 lost member by</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P146_separated_from"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P146i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P32_used_general_technique">
    <rdfs:comment xml:lang="en">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. This property identifies the technique that was employed in an act of modification. 


Examples:
- ornamentation of silver cup 113 (E11) used general technique gold-plating (E55) (Design or Procedure Type)


In First Order Logic:
P32(x,y) ⊃ E7(x)
P32(x,y) ⊃ E55(y)
P32(x,y) ⊃ P125(x,y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P32i_was_technique_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P32</skos:notation>
    <rdfs:label xml:lang="en">P32 used general technique</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P125_used_object_of_type"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P4_has_time-span">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P4i_is_time-span_of"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P4 has time-span</rdfs:label>
    <rdfs:comment xml:lang="en">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 E52 Temporal Entity may share a common instance of E52 Time-Span only if they come into being and end being due to an identical declarations or events.


Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)


In First Order Logic:
P4(x,y) ⊃ E2(x)
P4(x,y) ⊃ E52(y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P4</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P72i_is_language_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P72_has_language"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E56_Language"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P72i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
    <rdfs:label xml:lang="en">P72 is language of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P37_assigned">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E42_Identifier"/>
    <rdfs:label xml:lang="en">P37 assigned</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141_assigned"/>
    <rdfs:comment xml:lang="en">Scope note:
This property records the identifier that was assigned to an item in an instance of P37 Identifier Assignment.
The same identifier may be assigned on more than one occasion.
An Identifier might be created prior to an assignment.


Examples:
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned "232" (E42)


In First Order Logic:
P37(x,y) ⊃ E15(x)
P37(x,y) ⊃ E42(y)
P37(x,y) ⊃ P141(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P37</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P37i_was_assigned_by"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E15_Identifier_Assignment"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P134_continued">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P174_starts_before_the_end_of"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P15_was_influenced_by"/>
    <rdfs:comment xml:lang="en">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.


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


In First Order Logic:
P134(x,y) ⊃ E7(x)
P134(x,y)⊃ E7(y)
P134(x,y) ⊃ P15(x,y)
P134(x,y) ⊃ P174(x,y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P134i_was_continued_by"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P134</skos:notation>
    <rdfs:label xml:lang="en">P134 continued</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P91i_is_unit_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E58_Measurement_Unit"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <rdfs:label xml:lang="en">P91 is unit of</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P91i</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P91_has_unit"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P65_shows_visual_item">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P65</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P65i_is_shown_by"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P128_carries"/>
    <rdfs:comment xml:lang="en">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,E1 CRM Entity which is shortcut by, P62 depicts (is depicted by).


Examples:
- My T-Shirt (E22) shows visual item Mona Lisa (E38)


In First Order Logic:
P65(x,y) ⊃ E24(x)
P65(x,y) ⊃ E36(y)
P65(x,y) ⊃ P128(x,y)</rdfs:comment>
    <rdfs:label xml:lang="en">P65 shows visual item</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E36_Visual_Item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P56i_is_found_on">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P46i_forms_part_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E26_Physical_Feature"/>
    <rdfs:label xml:lang="en">P56 is found on</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P56i</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P56_bears_feature"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P7i_witnessed">
    <rdfs:label xml:lang="en">P7 witnessed</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P7_took_place_at"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P7i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P151i_participated_in">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P151_was_formed_from"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P151i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E66_Formation"/>
    <rdfs:label xml:lang="en">P151 participated in</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P113_removed">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E80_Part_Removal"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P113i_was_removed_by"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P113</skos:notation>
    <rdfs:label xml:lang="en">P113 removed</rdfs:label>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P113(x,y) ⊃ E80(x)
P113(x,y) ⊃ E18(y)
P113(x,y) ⊃ P12(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P124_transformed">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P124 transformed</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P93_took_out_of_existence"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance or instances E18 Physical Thing that have ceased to exist due to an instance of E81 Transformation.
The item that has ceased to exist and was replaced by the result of the Transformation. The continuity between both items, the new and the old, is expressed by the links to the common instance of E81 Transformation.


Examples:
- the transformation of the Venetian Loggia in Heraklion into a city hall (E81) transformed the Venetian Loggia in Heraklion (E22)
- the death and mummification of Tut-Ankh-Amun (E81) transformed the ruling Pharao Tut-Ankh-Amun (E21)


In First Order Logic:
P124(x,y) ⊃ E81(x)
P124(x,y) ⊃ E77(y)
P124(x,y) ⊃ P93(x,y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P124i_was_transformed_by"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E81_Transformation"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P124</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P189_approximates">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P189 approximates</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P189i_is_approximated_by"/>
    </owl:inverseOf>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 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.


Examples:
 [40°31'17.9"N 21°15'48.3"E] approximates Kastoria, Greece, TGN ID: 7010880. (coordinates from https://sws.geonames.org/735927)
 [40°31'00.1"N 21°16'00.1"E] approximates Kastoria, Greece, TGN ID: 7010880. (coordinates from http://vocab.getty.edu/page/tgn/7010880)
 [40°04'60.0"N 22°21'00.0"E] approximates Mount Olympus National Park, Greece (coordinates from https://www.geonames.org/6941814)


In First Order Logic:
P189(x,y) ⊃ E53(x)
P189(x,y) ⊃ E53 (y)
P189 (x,y,z) ⊃ [P189 (x,y) ∧ E55(z)]</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P129i_is_subject_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P129_is_about"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by"/>
    </rdfs:subPropertyOf>
    <rdfs:label xml:lang="en">P129 is subject of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P129i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P23_transferred_title_from">
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the E39 Actor or Actors who relinquish legal ownership as the result of an E8 Acquisition.

The property will typically be used to describe a person donating or selling an object to a museum. In reality title is either transferred to or from someone, or both.


Examples:
- acquisition of the Amoudrouz collection by the Geneva Ethnographic Museum (E8) transferred title from Heirs of Amoudrouz (E74)


In First Order Logic:
P23(x,y) ⊃ E8(x)
P23(x,y) ⊃ E39(y)
P23 (x,y) ⊃ P14(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P23</skos:notation>
    <rdfs:label xml:lang="en">P23 transferred title from</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14_carried_out_by"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E8_Acquisition"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P23i_surrendered_title_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P46_is_composed_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P46i_forms_part_of"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P46</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:comment xml:lang="en">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 item of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in).


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) ⊃ (uzw)[E93(u) ∧ P166 (x,u) ∧ E52(z) ∧ P164(u,z) ∧ E93(w) ∧ P166 (y,w) ∧
P164(w,z) ∧ P10(w,u)]</rdfs:comment>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:label xml:lang="en">P46 is composed of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P147_curated">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E78_Curated_Holding"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P147</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P147i_was_curated_by"/>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E87 Curation Activity with the instance of E78 Curated Holdingwith that is subject of that curation activity following some implicit or explicit curation plan.


Examples:
- The activities (E87) by the Benaki Museum curated the acquisition of dolls and games of urban and folk manufacture dating from the 17th to the 20th century, from England, France and Germany for the "Toys, Games and Childhood Collection (E78) of the Museum
- The activities (E87) of the Historical Museum of Crete, Heraklion, Crete, curated the development of the permanent Numismatic Collection (E78)
- The activities (E87) by Mikael Heggelund Foslie curated the Mikael Heggelund Foslie's coralline red algae Herbarium


In First Order Logic:
P147(x,y) ⊃ E87(x)
P147(x,y) ⊃ E78(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E87_Curation_Activity"/>
    <rdfs:label xml:lang="en">P147 curated</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P32i_was_technique_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P125i_was_type_of_object_used_in"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:label xml:lang="en">P32 was technique of</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P32_used_general_technique"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P32i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P96_by_mother">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P96i_gave_birth"/>
    <rdfs:comment xml:lang="en">Scope note:
This property links an instance ofE67 Birth to an instance of E21 Person in the role of birth-giving mother. Note that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The instance of P21 Person being born is linked to the instance of E67 Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions.
This is a sub-property of P11 had participant (participated in).


Examples:
- the birth of Queen Elizabeth II (E67) by mother Queen Mother (E21)


In First Order Logic:
P96(x,y) ⊃ E67(x)
P96(x,y) ⊃ E21(y)
P96(x,y) ⊃ P11(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11_had_participant"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E67_Birth"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P96</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <rdfs:label xml:lang="en">P96 by mother</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P4i_is_time-span_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <rdfs:label xml:lang="en">P4 is time-span of</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P4i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P4_has_time-span"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P110_augmented">
    <rdfs:label xml:lang="en">P110 augmented</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E79_Part_Addition"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P110i_was_augmented_by"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P110</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E24 Physical Human-Made Thing that is added to (augmented) in an instance of E79 Part Addition.

Although an instance of E79 Part Addition event normally concerns only one instance of E24 Physical Human-Made Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.


Examples:
- the final nail-insertion Event (E79) augmented Coffin of George VI (E24)


In First Order Logic:
P110(x,y) ⊃ E79(x)
P110(x,y) ⊃ E24(y)
P110(x,y) ⊃ P31(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P31_has_modified"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P195i_had_presence">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P195_was_presence_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P41_classified">
    <rdfs:label xml:lang="en">P41 classified</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from ‘E1 CRM Entity’ through ‘P41i was classified by’, ‘E17 Type Assignment’, ‘P42 assigned’, to ‘E55 Type’ for assigning types to objects compared to the shortcut offered by P2 has type (is type of).


Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)


In First Order Logic:
P41(x,y) ⊃ E17(x)
P41(x,y) ⊃ E1(y)
P41(x,y) ⊃ P140(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E17_Type_Assignment"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P140_assigned_attribute_to"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P41i_was_classified_by"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P41</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P55i_currently_holds">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P53i_is_former_or_current_location_of"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P55_has_current_location"/>
    <rdfs:label xml:lang="en">P55 currently holds</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P55i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P186_produced_thing_of_product_type">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E12_Production"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99).


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>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E99_Product_Type"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P186 produced thing of product type</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P186i_is_produced_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P104i_applies_to">
    <rdfs:label xml:lang="en">P104 applies to</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E72_Legal_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P104i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E30_Right"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P104_is_subject_to"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P68_foresees_use_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P68</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies an instance of E57 Material foreseen to be used by an instance of E29 Design or Procedure.

E29 Designs and procedures commonly foresee the use of particular instances of E57 Material. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented.

This property is not intended for the documentation of instances of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed.


Examples:
- procedure for soda glass manufacture (E29) foresees use of soda (E57)


In First Order Logic:
P68(x,y) ⊃ E29(x)
P68(x,y) ⊃ E57(y)
P68(x,y) ⊃ P67(x,y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P68i_use_foreseen_by"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P68 foresees use of</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P67_refers_to"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E57_Material"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P137_exemplifies">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P137</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P2_has_type"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:label xml:lang="en">P137 exemplifies</rdfs:label>
    <rdfs:comment xml:lang="en">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 selected in a later phase.


Examples:
- Object BM000098044 of the Clayton Herbarium (E20) exemplifies Spigelia marilandica (L.) L. (E55) in the taxonomic role lectotype


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:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P137i_is_exemplified_by"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P136i_supported_type_creation">
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P15i_influenced"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P136_was_based_on"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P136i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E83_Type_Creation"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:label xml:lang="en">P136 supported type creation</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P1i_identifies">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P1i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P1_is_identified_by"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E41_Appellation"/>
    <rdfs:label xml:lang="en">P1 identifies</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P173_starts_before_or_at_the_end_of">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P173 starts before or at the end of</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P173i_ends_with_or_after_the_start_of"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bend is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to the disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, met-by, overlaps, starts, started-by, contains, finishes, finished-by, equals, during,  overlapped by}


In First Order Logic:
P173(x,y) ⊃ E2(x)
P173(x,y) ⊃ E2(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92_brought_into_existence">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92i_was_brought_into_existence_by"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P92 brought into existence</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P92</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E63_Beginning_of_Existence"/>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P92(x,y) ⊃ E63(x)
P92(x,y) ⊃ E77(y)
P92(x,y) ⊃ P12(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12_occurred_in_the_presence_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P54i_is_current_permanent_location_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P54_has_current_permanent_location"/>
    <rdfs:label xml:lang="en">P54 is current permanent location of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P54i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P167i_was_place_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P167_at"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P28i_surrendered_custody_through">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E10_Transfer_of_Custody"/>
    <rdfs:label xml:lang="en">P28 surrendered custody through</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P28_custody_surrendered_by"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14i_performed"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P28i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P43_has_dimension">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P43</skos:notation>
    <rdfs:label xml:lang="en">P43 has dimension</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P43i_is_dimension_of"/>
    <rdfs:comment xml:lang="en">Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from ‘E70 Thing’ through ‘P39 measured’, ‘E16 Measurement’, ‘P40 observed dimension’, to ‘E54 Dimension’. It offers no information about how and when an E54 Dimension was established, nor by whom.

An instance of E54 Dimension is specific to an instance of E70 Thing.


Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)


In First Order Logic:
P43(x,y) ⊃ E70(x)
P43(x,y) ⊃ E54(y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P189i_is_approximated_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P189_approximates"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P188_requires_production_tool">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P188i_is_production_tool_for"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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:
- the luggage compartment lid mould (E19) for the Volkswagen Type 11 (Beetle) (E99) (https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Type_1_(Auto_classique_St._Lazare_%2710).jpg/220pxVolkswagen_Type_1_(Auto_classique_St._Lazare_%2710).jpg)


In First Order Logic:
P188(x,y) ⊃ E99(x)
P188(x,y) ⊃ E19(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E99_Product_Type"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P188 requires production tool</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P145i_left_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P145i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E86_Leaving"/>
    <rdfs:label xml:lang="en">P145 left by</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P145_separated"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P167_at">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P167i_was_place_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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. It 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. 


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:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P111_added">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P111</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P16_used_specific_object"/>
    <rdfs:label xml:lang="en">P111 added</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P111i_was_added_by"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E79_Part_Addition"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E18 Physical Thing that is added during an instance of E79 Part Addition activity


Examples:
- the insertion of the final nail (E79) added the last nail in George VI's coffin (E18)


In First Order Logic:
P111(x,y) ⊃ E79(x)
P111(x,y) ⊃ E18(y)
P111(x,y) ⊃ P12(x,y)
P111(x,y) ⊃ P16(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P180_has_currency">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P180 has currency</rdfs:label>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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:	
- Christies’ hammer price for “Vase with Fifteen Sunflowers” (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>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P91_has_unit"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P180i_was_currency_of"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E97_Monetary_Amount"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E98_Currency"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P44_has_condition">
    <rdfs:comment xml:lang="en">Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from ‘E18 Physical Thing’ through ‘P34 concerned’, ‘E14 Condition Assessment’, ‘P35 has identified’, to ‘E3 Condition State’. It offers no information about how and when the E3 Condition State was established, nor by whom.

An instance of Condition State is specific to an instance of Physical Thing.


Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)


In First Order Logic:
P44(x,y) ⊃ E18(x)
P44(x,y) ⊃ E3(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P44 has condition</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P44</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P44i_is_condition_of"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P71_lists">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E32_Authority_Document"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:label xml:lang="en">P71 lists</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P71i_is_listed_in"/>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P71(x,y) ⊃ E32(x)
P71(x,y) ⊃ E1(y)
P71(x,y) ⊃ P67(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P71</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P67_refers_to"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P129_is_about">
    <rdfs:label xml:lang="en">P129 is about</rdfs:label>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P129(x,y) ⊃ E89(x)
P129(x,y) ⊃ E1(y)
P129(x,y) ⊃ P67(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P67_refers_to"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P129i_is_subject_of"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P129</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P75_possesses">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E30_Right"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:label xml:lang="en">P75 possesses</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P75i_is_possessed_by"/>
    </owl:inverseOf>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.

Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles' back catalogue (E30)

In First Order Logic:
P75(x,y) ⊃ E39(x)
P75(x,y) ⊃ E30(y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P75</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P126i_was_employed_in">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P126_employed"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P126 was employed in</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E57_Material"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P126i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E11_Modification"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P175_starts_before_or_with_the_start_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P175i_starts_after_or_with_the_start_of"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P174_starts_before_the_end_of"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P175 starts before or with the start of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, starts, started-by, contains, finished-by, equals}


In First Order Logic:
P175(x,y) ⊃ E2(x)
P175(x,y) ⊃ E2(y)
P175(x,y) ⊃ P174(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P59i_is_located_on_or_within">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P59i</skos:notation>
    <rdfs:label xml:lang="en">P59 is located on or within</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P59_has_section"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P157_is_at_rest_relative_to"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P101i_was_use_of">
    <rdfs:label xml:lang="en">P101 was use of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P101i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P101_had_as_general_use"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P24_transferred_title_of">
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance(s) of E18 Physical Thing involved in an instance of E8 Acquisition.

In reality, an acquisition must refer to at least one transferred item.


Examples:
- acquisition of the Amoudrouz collection by the Geneva Ethnographic Museum (E8) transferred title of Amoudrouz Collection (E78)


In First Order Logic:
P24(x,y) ⊃ E8(x)
P24(x,y) ⊃ E18(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P24 transferred title of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E8_Acquisition"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P24</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P24i_changed_ownership_through"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P49_has_former_or_current_keeper">
    <rdfs:comment xml:lang="en">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.

P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from ‘E18 Physical Thing’ through ‘P30 transferred custody of’, ‘E10 Transfer of Custody’, ‘P28 custody surrendered by’ or ‘P29 custody received by’ to ‘ E39 Actor’.


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


In First Order Logic:
P49(x,y) ⊃ E18(x)
P49(x,y) ⊃ E39(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P49</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P49 has former or current keeper</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P49i_is_former_or_current_keeper_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P187i_is_production_plan_for">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E99_Product_Type"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P187_has_production_plan"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P94i_was_created_by">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E28_Conceptual_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P94i</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92i_was_brought_into_existence_by"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P94_has_created"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E65_Creation"/>
    <rdfs:label xml:lang="en">P94 was created by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P99i_was_dissolved_by">
    <rdfs:label xml:lang="en">P99 was dissolved by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E68_Dissolution"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P99i</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P93i_was_taken_out_of_existence_by"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P99_dissolved"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P103_was_intended_for">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P103i_was_intention_of"/>
    <rdfs:comment xml:lang="en">Scope note:
This property links an instance of E71 Human-Made Thing to an instance of E55 Type describing its intended usage.

It creates a relation between specific human-made things, both physical and immaterial, to types of intended methods and techniques of use. Note: A link between specific human-made things and a specific use activity should be expressed using P19 was intended use of (was made for).


Examples:
- this plate (E22) was intended for being destroyed at wedding reception (E55)


In First Order Logic:
P103(x,y) ⊃ E71(x)
P103(x,y) ⊃ E55(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E71_Human-Made_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P103</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:label xml:lang="en">P103 was intended for</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P50i_is_current_keeper_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P50_has_current_keeper"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P49i_is_former_or_current_keeper_of"/>
    <rdfs:label xml:lang="en">P50 is current keeper of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P50i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P98i_was_born">
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92i_was_brought_into_existence_by"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P98i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E67_Birth"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <rdfs:label xml:lang="en">P98 was born</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P98_brought_into_life"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P184_ends_before_or_with_the_end_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P184i_ends_with_or_after_the_end_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P184 ens before or with the end of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bend   is true. 

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, finished by, start, equals, during, finishes}


In First Order Logic:
P184(x,y) ⊃ E2(x)
P184(x,y) ⊃ E2(y)
P184(x,y) ⊃ P174(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P174_starts_before_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P50_has_current_keeper">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P49_has_former_or_current_keeper"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P50</skos:notation>
    <rdfs:label xml:lang="en">P50 has current keeper</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the an 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.
P50 has current keeper (is current keeper of) 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’.


Examples:
- painting from The Iveagh Bequest (E18) has current keeper The National Gallery (E74)


In First Order Logic:
P50(x,y) ⊃ E18(x)
P50(x,y) ⊃ E39(y)
P50(x,y) ⊃ P49(x,y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P50i_is_current_keeper_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P35i_was_identified_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E14_Condition_Assessment"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141i_was_assigned_by"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P35_has_identified"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P35i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <rdfs:label xml:lang="en">P35 was identified by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P17i_motivated">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P17i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P17_was_motivated_by"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P17 motivated</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P15i_influenced"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P15i_influenced">
    <rdfs:label xml:lang="en">P15 influenced</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P15i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P15_was_influenced_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P125_used_object_of_type">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <rdfs:label xml:lang="en">P125 used object of type</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P125i_was_type_of_object_used_in"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P125</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E7 Activity to an instance of E55 Type,which defines used in an instance of E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer".


Examples:
- at the Battle of Agincourt (E7), the English archers used object of type long bow (E55)


In First Order Logic:
P125(x,y) ⊃ E7(x)
P125(x,y) ⊃ E55(y)
P125(x,y) iff (∃z)[E70(z) ∧ P16(x,z) ∧ P2(z,y)]</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P13i_was_destroyed_by">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P13i</skos:notation>
    <rdfs:label xml:lang="en">P13 was destroyed by</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P93i_was_taken_out_of_existence_by"/>
    </rdfs:subPropertyOf>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P13_destroyed"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E6_Destruction"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P160i_is_temporal_projection_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P160_has_temporal_projection"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P185_ends_before_the_end_of">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Aend &lt; Bend   is true. 

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, starts, during}


In First Order Logic:
P185(x,y) ⊃ E2(x)
P185(x,y) ⊃ E2(y)
P185(x,y) ⊃ P184(x,y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P185 ends before the end of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P185i_ends_after_the_end_of"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P184_ends_before_or_with_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P7_took_place_at">
    <rdfs:comment xml:lang="en">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.

It is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place. E4 Period is a subclass of E92 Spacetime Volume. By the definition of P161 has spatial projection an instance of E4 Period takes place on all its spatial projections, that is, instances of E53 Place. Something happening at a given place can also be considered to happen at a larger place containing the first. For example, the assault on the Bastille July 14th 1789 took place in the area covered by Paris in 1789 but also in the area covered by France in 1789. 


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


In First Order Logic:
P7(x,y) ⊃ E4(x)
P7(x,y) ⊃ E53(y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P7</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P7i_witnessed"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
    <rdfs:label xml:lang="en">P7 took place at</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P24i_changed_ownership_through">
    <rdfs:label xml:lang="en">P24 changed ownership through</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P24_transferred_title_of"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E8_Acquisition"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P24i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P94_has_created">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E65_Creation"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P94</skos:notation>
    <rdfs:comment xml:lang="en">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 instanced of E28 Conceptual Object.
As an example, this is the composition of a poem, not its commitment to paper.


Examples:
- the composition of "The Four Friends" by A. A. Milne (E65) has created "The Four Friends" by A. A. Milne (E28)


In First Order Logic:
P94(x,y) ⊃ E65(x)
P94(x,y) ⊃ E28(y)
P94(x,y) ⊃ P92(x,y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P94i_was_created_by"/>
    <rdfs:label xml:lang="en">P94 has created</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P92_brought_into_existence"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E28_Conceptual_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P20i_was_purpose_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E5_Event"/>
    <rdfs:label xml:lang="en">P20 was purpose of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P20i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P20_had_specific_purpose"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P128i_is_carried_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P128i</skos:notation>
    <rdfs:label xml:lang="en">P128 is carried by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P128_carries"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P130i_features_are_also_found_on"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P161i_is_spatial_projection_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P161_has_spatial_projection"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P191_had_duration">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P191i_was_duration_of"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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)


In First Order Logic:
 P191(x,y) ⊃ E52(x)
 P191(x,y) ⊃ E54(y)</rdfs:comment>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P191 had duration</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P180i_was_currency_of">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P91i_is_unit_of"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P180_has_currency"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E98_Currency"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P40i_was_observed_in">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P40_observed_dimension"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P40i</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141i_was_assigned_by"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E16_Measurement"/>
    <rdfs:label xml:lang="en">P40 was observed in</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P156i_is_occupied_by">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P161i_is_spatial_projection_of"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P156_occupies"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P9_consists_of">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P9i_forms_part_of"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P9 consists of</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P10i_contains"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:subPropertyOf>
      <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P132_spatiotemporally_overlaps_with"/>
    </rdfs:subPropertyOf>
    <rdfs:comment xml:lang="en">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.


Examples:
- Cretan Bronze Age (E4) consists of Middle Minoan (E4)


In First Order Logic:
P9(x,y) ⊃ E4(x)
P9(x,y) ⊃ E4(y)
P9(x,y) ⊃ P10(y,x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P9</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P179i_was_sales_price_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P179_had_sales_price"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P33_used_specific_technique">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P33</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P33i_was_used_by"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it.

The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition.

Typical examples would include intervention plans for conservation or the construction plans of a building


Examples:
- Ornamentation of silver cup 232 (E11) used specific technique 'Instructions for golden chase work by A N Other' (E29)
- Rebuilding of Reichstag (E11) used specific technique Architectural plans by Foster and Partners (E29)


In First Order Logic:
P33(x,y) ⊃ E7(x)
P33(x,y) ⊃ E29(y)
P33(x,y) ⊃ P16(x,y)</rdfs:comment>
    <rdfs:label xml:lang="en">P33 used specific technique</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P16_used_specific_object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P69i_is_associated_with">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P69i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P69_has_association_with"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
    <rdfs:label xml:lang="en">P69 is associated with</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P29i_received_custody_through">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P29_custody_received_by"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P29 received custody through</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P29i</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14i_performed"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E10_Transfer_of_Custody"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P25i_moved_by">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12i_was_present_at"/>
    <rdfs:label xml:lang="en">P25 moved by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P25i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E9_Move"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P25_moved"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P144i_gained_member_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E85_Joining"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P144_joined_with"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:label xml:lang="en">P144 gained member by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P144i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P112i_was_diminished_by">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E24_Physical_Human-Made_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P112i</skos:notation>
    <rdfs:label xml:lang="en">P112 was diminished by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E80_Part_Removal"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P112_diminished"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P31i_was_modified_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P59_has_section">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P59i_is_located_on_or_within"/>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P59(x,y) ⊃ E18(x)
P59(x,y) ⊃ E53(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P59 has section</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P59</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P157i_provides_reference_space_for"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P93i_was_taken_out_of_existence_by">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P93_took_out_of_existence"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P93i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E64_End_of_Existence"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12i_was_present_at"/>
    <rdfs:label xml:lang="en">P93 was taken out of existence by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P104_is_subject_to">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E72_Legal_Object"/>
    <rdfs:comment xml:lang="en">Scope note:
This property links a particular instance of E72 Legal Object to the instances of E30 Right to which it is subject.

The Right is held by an E39 Actor as described by P75 possesses (is possessed by).


Examples:
- Beatles back catalogue (E72) is subject to reproduction right on Beatles back catalogue (E30)


In First Order Logic:
P104(x,y) ⊃ E72(x)
P104(x,y) ⊃ E30(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P104 is subject to</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P104i_applies_to"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P104</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E30_Right"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P17_was_motivated_by">
    <rdfs:comment xml:lang="en">Scope note:
This property describes an item or items that are regarded as a reason for carrying out the E7 Activity.

For example, the discovery of a large hoard of treasure may call for a celebration, an order from head quarters can start a military manoeuvre.


Examples:
- the resignation of the chief executive (E7) was motivated by the collapse of Swiss Air (E68).
- the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)


In First Order Logic:
P17(x,y) ⊃ E7(x)
P17(x,y) ⊃ E1(y)
P17 (x,y) ⊃ P15(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P17</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P15_was_influenced_by"/>
    <rdfs:label xml:lang="en">P17 was motivated by</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P17i_motivated"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P34i_was_assessed_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P34i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P34_concerned"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P140i_was_attributed_by"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E14_Condition_Assessment"/>
    <rdfs:label xml:lang="en">P34 was assessed by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P75i_is_possessed_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P75_possesses"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E30_Right"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P75i</skos:notation>
    <rdfs:label xml:lang="en">P75 is possessed by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P136_was_based_on">
    <rdfs:comment xml:lang="en">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)


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>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:label xml:lang="en">P136 was based on</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E83_Type_Creation"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P15_was_influenced_by"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P136</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P136i_supported_type_creation"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14i_performed">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11i_participated_in"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14_carried_out_by"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P14i</skos:notation>
    <rdfs:label xml:lang="en">P14 performed</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P183_ends_before_the_start_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P182_ends_before_or_at_the_start_of"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 = [Astart, Aend] and B = [Bstart, Bend], we mean Aend &lt; Bstart  is true. 

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before}


In First Order Logic:
P183(x,y) ⊃ E2(x)
P183(x,y) ⊃ E2(y)
P183(x,y) ⊃ P182(x,y)</rdfs:comment>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P183i_starts_after_the_end_of"/>
    </owl:inverseOf>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P183 ends before the start of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P56_bears_feature">
    <rdfs:comment xml:lang="en">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 found on the same E19 Physical Object as A. 
P56 bears feature (is found on) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path ‘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)


In First Order Logic:
P56(x,y) ⊃E19(x)
P56(x,y) ⊃ E26(y)
P56(x,y) ⊃ P46(x,y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P56i_is_found_on"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E26_Physical_Feature"/>
    <rdfs:label xml:lang="en">P56 bears feature</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P56</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P46_is_composed_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P165_incorporates">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P165i_is_incorporated_in"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E73_Information_Object"/>
    <rdfs:subPropertyOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P106_is_composed_of"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities.

It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc.

In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters.

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.


Examples:	
- The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37)
- The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E36) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73)
- The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E36) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33)


In First Order Logic:
P165(x,y) ⊃ E73(x)
P165(x,y) ⊃ E90(y)
P165(x,y) ⊃ P106(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P183i_starts_after_the_end_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P183_ends_before_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P182i_starts_after_or_with_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P125i_was_type_of_object_used_in">
    <rdfs:label xml:lang="en">P125 was type of object used in</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P125i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P125_used_object_of_type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P8_took_place_on_or_within">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P8</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:comment xml:lang="en">Scope note:
This property describes the location of an instance of E4 Period with respect to an instance of E19 Physical Object.
P8 took place on or within (witnessed) is a shortcut of the more fully developed path from ‘E4 Period’ through ‘P7 took place at’, ‘E53 Place’, ‘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 June 1940 was signed in the same railway carriage as the armistice of 11 November 1918.


Examples:
- the coronation of Queen Elisabeth II (E7) took place on or within Westminster Abbey (E19)


In First Order Logic:
P8(x,y) ⊃ E4(x)
P8(x,y) ⊃ E18(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P8 took place on or within</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P8i_witnessed"/>
    </owl:inverseOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P42i_was_assigned_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E17_Type_Assignment"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P42_assigned"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141i_was_assigned_by"/>
    <rdfs:label xml:lang="en">P42 was assigned by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P42i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P52i_is_current_owner_of">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P51i_is_former_or_current_owner_of"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P105i_has_right_on"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P52_has_current_owner"/>
    <rdfs:label xml:lang="en">P52 is current owner of</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P52i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P92i_was_brought_into_existence_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E63_Beginning_of_Existence"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P92i</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P12i_was_present_at"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P92_brought_into_existence"/>
    <rdfs:label xml:lang="en">P92 was brought into existence by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P142i_was_used_in">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P142_used_constituent"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P16i_was_used_for"/>
    <rdfs:label xml:lang="en">P142 was used in</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E15_Identifier_Assignment"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P142i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P70i_is_documented_in">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E31_Document"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by"/>
    </rdfs:subPropertyOf>
    <rdfs:label xml:lang="en">P70 is documented in</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P70_documents"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P70i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P126_employed">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P126</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E57 Material employed in an instance of E11 Modification.

The instance of E57 Material used during the instance of E11 Modification does not necessarily become incorporated into the instance of E24 Physical Human-Made Thing that forms the subject of the instance of E11 Modification.


Examples:
- the repairing of the Queen Mary (E11) employed Steel (E57)
- distilled water (E57) was employed in the restoration of the Sistine Chapel (E11)


In First Order Logic:
P126(x,y) ⊃ E11(x)
P126(x,y) ⊃ E57(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E57_Material"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E11_Modification"/>
    <rdfs:label xml:lang="en">P126 employed</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P126i_was_employed_in"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P48i_is_preferred_identifier_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P48i</skos:notation>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P48_has_preferred_identifier"/>
    </owl:inverseOf>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P1i_identifies"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E42_Identifier"/>
    <rdfs:label xml:lang="en">P48 is preferred identifier of</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P68i_use_foreseen_by">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P68_foresees_use_of"/>
    <rdfs:label xml:lang="en">P68 use foreseen by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P68i</skos:notation>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E57_Material"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E29_Design_or_Procedure"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P9i_forms_part_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P9_consists_of"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P9i</skos:notation>
    <rdfs:label xml:lang="en">P9 forms part of</rdfs:label>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:subPropertyOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P10_falls_within"/>
    </rdfs:subPropertyOf>
    <rdfs:subPropertyOf>
      <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P132_spatiotemporally_overlaps_with"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P26_moved_to">
    <rdfs:label xml:lang="en">P26 moved to</rdfs:label>
    <rdfs:comment xml:lang="en">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 Tut-Ankh-Amun Exhibition (E9) moved to The British Museum (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>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E9_Move"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P26</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P26i_was_destination_of"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P135_created_type">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P94_has_created"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P135</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E83_Type_Creation"/>
    <rdfs:label xml:lang="en">P135 created type</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E55 Type, which is created in an instance of E83 Type Creation


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


In First Order Logic:
P135(x,y) ⊃ E83(x)
P135(x,y) ⊃ E55(y)
P135(x,y) ⊃ P94(x,y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P135i_was_created_by"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P124i_was_transformed_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P124i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P124_transformed"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E81_Transformation"/>
    <rdfs:label xml:lang="en">P124 was transformed by</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P93i_was_taken_out_of_existence_by"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E77_Persistent_Item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P130_shows_features_of">
    <rdfs:label xml:lang="en">P130 shows features of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P130</skos:notation>
    <rdfs:comment xml:lang="en">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.


In First Order Logic:
P130 (x,y) ⊃ E70(x)
P130 (x,y) ⊃ E70(y)
P130(x,y,z) ⊃ [P130(x,y) ∧ E55(z)]</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E70_Thing"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P130i_features_are_also_found_on"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P165i_is_incorporated_in">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P165_incorporates"/>
    <rdfs:subPropertyOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P106i_forms_part_of"/>
    </rdfs:subPropertyOf>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P107i_is_current_or_former_member_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:label xml:lang="en">P107 is current or former member of</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P107_has_current_or_former_member"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P107i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P14_carried_out_by">
    <rdfs:label xml:lang="en">P14 carried out by</rdfs:label>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P11_had_participant"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E7_Activity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P14i_performed"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P14</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property describes the active participation of an instance of E39 Actor in an instance of E7 Activity.

It implies causal or legal responsibility. The P14.1 in the role of property of the property specifies the nature of an Actor’s participation.


Examples:
- the painting of the Sistine Chapel (E7) carried out by Michaelangelo Buonaroti (E21) in the role of master craftsman (E55)


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:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P48_has_preferred_identifier">
    <rdfs:label xml:lang="en">P48 has preferred identifier</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P48i_is_preferred_identifier_of"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P1_is_identified_by"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P48</skos:notation>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P48(x,y) ⊃ E1(x)
P48(x,y) ⊃ E42(y)
P48(x,y) ⊃ P1(x,y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E42_Identifier"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P30_transferred_custody_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P30</skos:notation>
    <rdfs:label xml:lang="en">P30 transferred custody of</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P30i_custody_transferred_through"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance(s) of E18 Physical Thing concerned in an instance of E10 Transfer of Custody.

The property will typically describe the object that is handed over by an instance of E39 Actor to to the custody of another instance of E39 Actor. On occasion, physical custody may be transferred involuntarily or illegally – through accident, unsolicited donation, or theft.


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


In First Order Logic:
P30 (x,y) ⊃ E10(x)
P30 (x,y) ⊃ E18(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E10_Transfer_of_Custody"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P29_custody_received_by">
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance(s) E39 Actor who receive custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody.

The property will typically describe Actors receiving custody of an object when it is handed over from Definition of the CIDOC Conceptual Reference Model version 6.2.8 58 another Actor’s care. On occasion, physical custody may be received involuntarily or illegally – through accident, unsolicited donation, or theft.
In reality, custody is either transferred to someone or from someone, or both.


Examples:
- representatives of The National Gallery (E74) received custody through. The delivery of the paintings by Secure Delivieries 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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P29</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P14_carried_out_by"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E10_Transfer_of_Custody"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P29i_received_custody_through"/>
    <rdfs:label xml:lang="en">P29 custody received by</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P95i_was_formed_by">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E66_Formation"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P95i</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P92i_was_brought_into_existence_by"/>
    <rdfs:label xml:lang="en">P95 was formed by</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P95_has_formed"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P185i_ends_after_the_end_of">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    ></rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P184i_ends_with_or_after_the_end_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E2_Temporal_Entity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P185_ends_before_the_end_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P157_is_at_rest_relative_to">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P157i_provides_reference_space_for"/>
    <rdfs:label xml:lang="en">P157 is at rest relative to</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P157</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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)
- The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22)


In First Order Logic:
P157(x,y) ⊃ E53(x)
P157(x,y) ⊃ E18(y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P137i_is_exemplified_by">
    <rdfs:label xml:lang="en">P137 is exemplified by</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P2i_is_type_of"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P137i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P137_exemplifies"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P97i_was_father_for">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E67_Birth"/>
    <rdfs:label xml:lang="en">P97 was father for</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P97i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P97_from_father"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P44i_is_condition_of">
    <rdfs:label xml:lang="en">P44 is condition of</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P44_has_condition"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P44i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P107_has_current_or_former_member">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P107</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E74_Group"/>
    <rdfs:comment xml:lang="en">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 Grous 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 E74 Group , P144i gained member by, E85 Joining, P143 joined , E39 Actor
The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group. 


Examples:
- Moholy Nagy (E21) is current or former member of Bauhaus (E74)
- National Museum of Science and Industry (E74) has current or former member The National Railway Museum (E74)
- The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) with P107.1 kind of member husband (E55 Type)


In First Order Logic:
P107(x,y) ⊃ E74(x)
P107(x,y) ⊃ E39(y)
P107(x,y,z) ⊃ [P107(x,y) ∧ E55(z)]</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P107i_is_current_or_former_member_of"/>
    <rdfs:label xml:lang="en">P107 has current or former member</rdfs:label>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P42_assigned">
    <rdfs:comment xml:lang="en">Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from ‘E1 CRM Entity’ through ‘P41i was classified by’, ‘E17 Type Assignment’, ‘P42 assigned’, to ‘E55 Type’ for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.


Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)


In First Order Logic:
P42(x,y) ⊃ E17(x)
P42(x,y)⊃ E55(y)
P42(x,y) ⊃ P141(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E17_Type_Assignment"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141_assigned"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P42i_was_assigned_by"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P42</skos:notation>
    <rdfs:label xml:lang="en">P42 assigned</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P91_has_unit">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P91</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <rdfs:label xml:lang="en">P91 has unit</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property shows the type of unit an instance of E54 Dimension was expressed in.


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


In First Order Logic:
P91(x,y) ⊃ E54(x)
P91(x,y) ⊃ E58(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E58_Measurement_Unit"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P91i_is_unit_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P2i_is_type_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P2_has_type"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P2i</skos:notation>
    <rdfs:label xml:lang="en">P2 is type of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P138_represents">
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P138i_has_representation"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P138 represents</rdfs:label>
    <rdfs:comment xml:lang="en">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 P62depicts (is depicted by). P138.1 mode of representation allows the nature of the representation to be refined.

This property is also used for the relationship between an original and a digitisation of the original by the use of techniques such as digital photography, flatbed or infrared scanning. Digitisation is here seen as a process with a mechanical, causal component rendering the spatial distribution of structural and optical properties of the original and does not necessarily include any visual similarity identifiable by human observation."


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


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>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P138</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P67_refers_to"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E36_Visual_Item"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P39i_was_measured_by">
    <rdfs:label xml:lang="en">P39 was measured by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P39i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P140i_was_attributed_by"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E16_Measurement"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P39_measured"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P109_has_current_or_former_curator">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E78_Curated_Holding"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P109i_is_current_or_former_curator_of"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E39 Actor who assumed or have assumed overall curatorial responsibility for an instance of E78 Collection.

It does not allow a history of curation to be recorded. This would require use of an event initiating a curator being responsible for a collection.


Examples:
- the Robert Opie Collection (E78) has current or former curator Robert Opie (E39)
- the Mikael Heggelund Foslie's coralline red algae Herbarium (E78) has current or former curator Mikael Heggelund Foslie


In First Order Logic:
P109(x,y) ⊃ E78(x)
P109(x,y) ⊃ E39(y)
P109(x,y) ⊃ P49(x,y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E39_Actor"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P49_has_former_or_current_keeper"/>
    <rdfs:label xml:lang="en">P109 has current or former curator</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P109</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P5i_forms_part_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P5i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <rdfs:label xml:lang="en">P5 forms part of</rdfs:label>
    <owl:inverseOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P5_consists_of"/>
    </owl:inverseOf>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P196i_is_defined_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P196_defines"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P175i_starts_after_or_with_the_start_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P175_starts_before_or_with_the_start_of"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P174i_ends_after_the_start_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P73_has_translation">
    <rdfs:comment xml:lang="en">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 transitive.


Examples:
- "Les Baigneurs" (E33) has translation "The Bathers" (E33)


In First Order Logic:
P73(x,y) ⊃ E33(x)
P73(x,y) ⊃ E33(y)
P73(x,y) ⊃ P130(y,x)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P130i_features_are_also_found_on"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P73</skos:notation>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
    <rdfs:label xml:lang="en">P73 has translation</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E33_Linguistic_Object"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P73i_is_translation_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P160_has_temporal_projection">
    <rdfs:label xml:lang="en">P160 has temporal projection</rdfs:label>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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.


Example:


In First Order Logic:
P160(x,y) ⊃ E92(x)
P160(x,y)⊃ E52(y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P160i_is_temporal_projection_of"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P160</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P37i_was_assigned_by">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141i_was_assigned_by"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P37_assigned"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P37i</skos:notation>
    <rdfs:label xml:lang="en">P37 was assigned by</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E15_Identifier_Assignment"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E42_Identifier"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P166_was_a_presence_of">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P166i_had_presence"/>
    <rdfs:subPropertyOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P10_falls_within"/>
    </rdfs:subPropertyOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E93_Presence"/>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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. 


In First Order Logic:
P166(x,y) ⊃ E93(x)
P166(x,y) ⊃ E92(y)
P166(x,y) ⊃ P10(x,y)</rdfs:comment>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P8i_witnessed">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E18_Physical_Thing"/>
    <rdfs:label xml:lang="en">P8 witnessed</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P8_took_place_on_or_within"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E4_Period"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P8i</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P98_brought_into_life">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E21_Person"/>
    <rdfs:label xml:lang="en">P98 brought into life</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P98</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P98i_was_born"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P92_brought_into_existence"/>
    <rdfs:comment xml:lang="en">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)


In First Order Logic:
P98(x,y) ⊃ E67(x)
P98(x,y) ⊃ E21(y)
P98(x,y) ⊃ P92(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E67_Birth"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P28_custody_surrendered_by">
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance(s) of E39 Actor who surrender custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody.

The property will typically describe an Actor surrendering custody of an object when it is handed over to someone else’s care. On occasion, physical custody may be surrendered involuntarily – through accident, loss or theft.
In reality, custody is either transferred to someone or from someone, or both.

Examples:
- the Secure Deliveries Inc. crew (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>
    <rdfs:label xml:lang="en">P28 custody surrendered by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P28</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P14_carried_out_by"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E10_Transfer_of_Custody"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P28i_surrendered_custody_through"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P5_consists_of">
    <rdfs:comment xml:lang="en">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.


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


In First Order Logic:
P5(x,y) ⊃ E3(x)
P5(x,y) ⊃ E3(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P5</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E3_Condition_State"/>
    <rdfs:label xml:lang="en">P5 consists of</rdfs:label>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P5i_forms_part_of"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P138i_has_representation">
    <rdfs:label xml:lang="en">P138 has representation</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:subPropertyOf>
      <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by"/>
    </rdfs:subPropertyOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P138i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E36_Visual_Item"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P138_represents"/>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P38_deassigned">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P38i_was_deassigned_by"/>
    <rdfs:comment xml:lang="en">Scope note:
This property records the identifier that was deassigned from an instance of E1 CRM Entity.
Deassignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up.
The same identifier may be deassigned on more than one occasion


Examples:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned "232" (E42)


In First Order Logic:
P38(x,y) ⊃ E15(x)
P38(x,y) ⊃ E42(y)
P38(x,y) ⊃ P141(x,y)</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P141_assigned"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E15_Identifier_Assignment"/>
    <rdfs:label xml:lang="en">P38 deassigned</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E42_Identifier"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P38</skos:notation>
  </owl:ObjectProperty>
  <owl:ObjectProperty rdf:about="http://erlangen-crm.org/current/P67i_is_referred_to_by">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P67_refers_to"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P67i</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <rdfs:label xml:lang="en">P67 is referred to by</rdfs:label>
  </owl:ObjectProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P170i_time_is_defined_by">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P170i time is defined by</rdfs:label>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Scope note:
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.


In First Order Logic:
P170(x,y) ⊃ E61(x)
P170(x,y) ⊃ E52(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P79_beginning_is_qualified_by">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P79</skos:notation>
    <rdfs:subPropertyOf>
      <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P3_has_note"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <rdfs:comment xml:lang="en">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 theHolocene using the Greenland NGRIP ice core,and selected auxiliary records” (Walker et al 2009) (E62)


In First Order Logic:
P79 (x,y) ⊃ E52 (x)
P79 (x,y) ⊃ E62(y)
P79(x,y) ⊃ P3(x,y)</rdfs:comment>
    <rdfs:label xml:lang="en">P79 beginning is qualified by</rdfs:label>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P172_contains">
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P172 contains</rdfs:label>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 Places’s minimum spatial extent (i.e. its inner boundary or a point being within a Place) to be assigned an instance of E94 Space Primitive value.
This property is a shortcut of the fully developed path: E53 Place, P89i contains, E53 Place, P168 place is defined by, 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)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P82_at_some_time_within">
    <rdfs:comment xml:lang="en">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.


Examples:
- the time-span of the development of the CIDOC CRM (E52) at some time within 1992-infinity (E61)


In First Order Logic:
P82 (x,y) ⊃ E52(x)
P82 (x,y) ⊃ E61(y)</rdfs:comment>
    <rdfs:label xml:lang="en">P82 at some time within</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P82</skos:notation>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P171_at_some_place_within">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 an instance of E53 Places’s maximum spatial extent (i.e. its outer boundary) to be assigned an instance of E94 Space Primitive value.

P171 at some place within is a shortcut of the fully developed path E53 Place, P89 falls within, E53 Place, P168 place is defined by, 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) is 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)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P171 at some place within</rdfs:label>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P3_has_note">
    <rdfs:label xml:lang="en">P3 has note</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs.

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

Examples:
- coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" (E62) has type
Condition (E55)

In First Order Logic:
P3(x,y) ⊃ E1(x)
P3(x,y) ⊃ E62(y)
P3(x,y,z) ⊃ [P3(x,y) ∧ E55(z)]

Properties: P3.1 has type: E55 Type</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E1_CRM_Entity"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P3</skos:notation>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P81_ongoing_throughout">
    <rdfs:comment xml:lang="en">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, there may be multiple minimum periods of . Union of

Examples:
- the time-span of the development of the CIDOC CRM (E52) ongoing throughout 1996-2002 (E61)

In First Order Logic:
P81 (x,y) ⊃ E52(x)
P81 (x,y) ⊃ E61(y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P81</skos:notation>
    <rdfs:label xml:lang="en">P81 ongoing throughout</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P169i_spacetime_volume_is_defined_by">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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.


In First Order Logic:
P168(x,y) ⊃ E53(x)
P168(x,y) ⊃ E94(y)</rdfs:comment>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P169i spacetime volume is defined by</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P57_has_number_of_parts">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E19_Physical_Object"/>
    <rdfs:label xml:lang="en">P57 has number of parts</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property documents the E60 Number of parts of which an instance of E19 Physical Object is composed.

This may be used as a method of checking inventory counts with regard to aggregate or collective objects. What constitutes a part or component depends on the context and requirements of the documentation. Normally, the parts documented in this way would not be considered as worthy of individual attention.

For a more complete description, objects may be decomposed into their components and constituents using P46 is composed of (forms parts of) and P45 consists of (is incorporated in). This allows each element to be described individually.

Examples:
- chess set 233 (E22) has number of parts 33 (E60)

In First Order Logic:
P57(x,y) ⊃ E19(x)
P57(x,y) ⊃ E60(y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P57</skos:notation>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P80_end_is_qualified_by">
    <rdfs:comment xml:lang="en">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 end. 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) end is qualified by “still ongoing” (E62)

In First Order Logic:
P80(x,y) ⊃ E52(x)
P80(x,y) ⊃ E62(y)
P80(x,y) ⊃ P3(x,y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <rdfs:label xml:lang="en">P80 end is qualified by</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P80</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P3_has_note"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P181_has_amount">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Scope note:
This property establishes the relationship between an instance of E97 Monetary Amount and the amount of currency, an instance of E60 Number, that it consists of.


Examples:	
- Christies hammer price for “Vase with Fifteen Sunflowers” (E97) has amount 24,750,000 (E60)


In First Order Logic:
P181(x,y) ⊃ E97(x)
P181(x,y) ⊃ E60(y)
P181(x,y) ⊃ P90(x,y)</rdfs:comment>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P181 has amount</rdfs:label>
    <rdfs:subPropertyOf>
      <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P90_has_value"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E97_Monetary_Amount"/>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P190_has_symbolic_content">
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P3_has_note"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P190 has symbolic content</rdfs:label>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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 (E33) of the painting has symbolic content “Oil, French Watercolors on Paper, Graphite and Ink on Canvas, with an Oak frame.”
- The title (E35) of Einstein’s 1915 text has symbolic content “Relativity, the Special and the General Theory “
- The story of Little Red Riding Hood (E33) has symbolic content “Once upon a time there lived in a certain village …”
- The inscription (E34) on Rijksmuseum object SK-A-1601 has symbolic content “B”


In First Order Logic:
P190(x,y) ⊃ E90(x)
P190(x,y) ⊃ E62(y)</rdfs:comment>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P168_place_is_defined_by">
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Scope note:&#xD;
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.


In First Order Logic:
P168(x,y) ⊃ E53(x)
P168(x,y) ⊃ E94(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P168 place is defined by</rdfs:label>
  </owl:DatatypeProperty>
  <owl:DatatypeProperty rdf:about="http://erlangen-crm.org/current/P90_has_value">
    <rdfs:label xml:lang="en">P90 has value</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E54_Dimension"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P90</skos:notation>
    <rdfs:comment xml:lang="en">Scope note:
This property allows an instance of E54 Dimension to be approximated by an instance of E60 Number
primitive.


Examples:
- height of silver cup 232 (E54) has value 226 (E60)


In First Order Logic:
P90(x,y) ⊃ E54(x)
P90(x,y) ⊃ E60(y)</rdfs:comment>
  </owl:DatatypeProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P127i_has_narrower_term">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P127_has_broader_term"/>
    </owl:inverseOf>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P127i</skos:notation>
    <rdfs:label xml:lang="en">P127 has narrower term</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P27i_was_origin_of">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P27i</skos:notation>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P7i_witnessed"/>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P27_moved_from"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P27 was origin of</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E9_Move"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P148_has_component">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:comment xml:lang="en">Scope note:
This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object.
This property is transitive


Examples:
- Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89)


In First Order Logic:
P148(x,y) ⊃ E89(x)
P148(x,y) ⊃ E89(y)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P148</skos:notation>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P148i_is_component_of"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P148 has component</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P86i_contains">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P86i</skos:notation>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P86_falls_within"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P86 contains</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P86_falls_within">
    <rdfs:comment xml:lang="en">Scope note:
This property describes the inclusion relationship between two instances of E52 Time-Span.

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


Examples:
- the time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52)


In First Order Logic:
P86(x,y) ⊃ E52(x)
P86(x,y) ⊃ E52(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <rdfs:label xml:lang="en">P86 falls within</rdfs:label>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P86</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E52_Time-Span"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P86i_contains"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P148i_is_component_of">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P148_has_component"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:label xml:lang="en">P148 is component of</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P148i</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E89_Propositional_Object"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P106i_forms_part_of">
    <rdfs:label xml:lang="en">P106 forms part of</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P106i</skos:notation>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P106_is_composed_of"/>
    </owl:inverseOf>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P150_defines_typical_parts_of">
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P150</skos:notation>
    <rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >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”. The property is in general not transitive.

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.


Examples:
- Car motors (E55) defines typical parts of cars (E55)


In First Order Logic:
P150(x,y) ⊃ (E55 Type)
P150(x,y) ⊃ E55(y)</rdfs:comment>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P150i_defines_typical_wholes_for"/>
    </owl:inverseOf>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:label xml:lang="en">P150 defines typical parts of</rdfs:label>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P10_falls_within">
    <rdfs:label xml:lang="en">P10 falls within</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P10</skos:notation>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:comment xml:lang="en">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.


Examples:
- the Great Plague (E4) falls within The Gothic period (E4)


In First Order Logic:
P10(x,y) ⊃ E92(x)
P10(x,y) ⊃ E92(y)
P10(x,y) ⊃ P132(x,y)</rdfs:comment>
    <rdfs:subPropertyOf>
      <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P132_spatiotemporally_overlaps_with"/>
    </rdfs:subPropertyOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P10i_contains"/>
    </owl:inverseOf>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P89_falls_within">
    <rdfs:comment xml:lang="en">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.


Examples:
- the area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53)


In First Order Logic:
P89(x,y) ⊃ E53(x)
P89(x,y) ⊃ E53(y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P89</skos:notation>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P89 falls within</rdfs:label>
    <owl:inverseOf>
      <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P89i_contains"/>
    </owl:inverseOf>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P150i_defines_typical_wholes_for">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <rdfs:label xml:lang="en">P150 defines typical wholes for</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P150i</skos:notation>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P150_defines_typical_parts_of"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P127_has_broader_term">
    <rdfs:label xml:lang="en">P127 has broader term</rdfs:label>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:comment xml:lang="en">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.

This property is transitive.


Examples:
- dime (E55) has broader term coin (E55)


In First Order Logic:
P127(x,y) ⊃ E55(x)
P127(x,y) ⊃ E55(y)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P127</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E55_Type"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P127i_has_narrower_term"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P10i_contains">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P10i</skos:notation>
    <rdfs:label xml:lang="en">P10 contains</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P10_falls_within"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdfs:subPropertyOf>
      <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P132_spatiotemporally_overlaps_with"/>
    </rdfs:subPropertyOf>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P89i_contains">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P89i</skos:notation>
    <rdfs:label xml:lang="en">P89 contains</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P89_falls_within"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P106_is_composed_of">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:label xml:lang="en">P106 is composed of</rdfs:label>
    <rdfs:comment xml:lang="en">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.


Examples:
- This Scope note P106 (E33) is composed of fragments of texts (E33)
- 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90)


In First Order Logic:
P106(x,y) ⊃ E90(x)
P106(x,y) ⊃ E90(y)</rdfs:comment>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P106i_forms_part_of"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P106</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E90_Symbolic_Object"/>
  </owl:TransitiveProperty>
  <owl:TransitiveProperty rdf:about="http://erlangen-crm.org/current/P27_moved_from">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P27i_was_origin_of"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P27</skos:notation>
    <rdfs:comment xml:lang="en">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 Tut-Ankh-Amun Exhibition (E9) moved from The Egyptian Museum in Cairo (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>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E9_Move"/>
    <rdfs:label xml:lang="en">P27 moved from</rdfs:label>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
  </owl:TransitiveProperty>
  <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P122_borders_with">
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:comment xml:lang="en">Scope note:
This symmetric property associates an instance of E53 Place with another instance of E53 Place which shares a part of its borders.

This property is purely spatial, in contrast to time properties, which are purely temporal.


Examples:
- Scotland (E53) borders with England (E53)


In First Order Logic:
P122(x,y) ⊃ E53(x)
P122(x,y) ⊃ E53(y)
P122(x,y) ⊃ P122(y,x)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P122</skos:notation>
    <rdfs:label xml:lang="en">P122 borders with</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P122_borders_with"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
  </owl:SymmetricProperty>
  <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P139_has_alternative_form">
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P139_has_alternative_form"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P139</skos:notation>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E41_Appellation"/>
    <rdfs:label xml:lang="en">P139 has alternative form</rdfs:label>
    <rdfs:comment xml:lang="en">Scope note:
This property establishes a relationship of equivalence between two instances of E41 Appellation independent from any item identified by them. It is a dynamic asymmetric relationship, where the range expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric.
The relationship is not transitive.

The equivalence applies to all cases of use of an instance of E41 Appellation. Multiple names assigned to an object, which are not equivalent for all things identified with a specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies).

P139.1 has type allows the type of derivation, such as “transliteration from Latin 1 to ASCII” be refined..


Examples:
- "Martin Doerr" (E41) has alternative form "Martin Dörr" (E41) has type Alternate spelling (E55)
- "Гончарова, Наталья Сергеевна" (E41) has alternative form "Gončarova, Natal´â Sergeevna" (E41) has type ISO 9:1995 transliteration (E55)
- "Αθήνα" has alternative form "Athina" has type transcription.


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,y) ⊃ P139(y,x)</rdfs:comment>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E41_Appellation"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
  </owl:SymmetricProperty>
  <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P121_overlaps_with">
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P121</skos:notation>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P121_overlaps_with"/>
    <rdfs:comment xml:lang="en">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, in contrast to the temporal overlaps described by pxxx, pxxy or pxxz, and and, spatio temporal overlaps described by p132 spatiotemporally overlaps with.


Examples:
- the territory of the United States (E53) overlaps with the Arctic (E53)
- The maximal extent of the Greek Kingdom (E53) overlaps with the maximal extent of the Ottoman Empire(E53)


In First Order Logic:
P121(x,y) ⊃ E53(x)
P121(x,y) ⊃ E53(y)
P121(x,y) ⊃ P121(y,x)</rdfs:comment>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E53_Place"/>
    <rdfs:label xml:lang="en">P121 overlaps with</rdfs:label>
  </owl:SymmetricProperty>
  <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P132_spatiotemporally_overlaps_with">
    <rdfs:label xml:lang="en">P132 overlaps with</rdfs:label>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdfs:comment xml:lang="en">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 also holds for the same two instances. Furthermore, there are cases where neither P132 nor P133 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.


Examples:
- the “Urnfield” period (E4) spatiotemporally overlaps with the “Hallstatt” period (E4)


In First Order Logic: 
P132(x,y) ⊃ E92(x) 
P132(x,y) ⊃ E92(y) 
P132(x,y) ⊃ P132(y,x)
P132(x,y) ⊃ ¬P133(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P132</skos:notation>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P132_spatiotemporally_overlaps_with"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
  </owl:SymmetricProperty>
  <owl:SymmetricProperty rdf:about="http://erlangen-crm.org/current/P133_is_spatiotemporally_separated_from">
    <rdfs:label xml:lang="en">P133 is separated from</rdfs:label>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P133_is_spatiotemporally_separated_from"/>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E92_Spacetime_Volume"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P133</skos:notation>
    <rdfs:comment xml:lang="en">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 nor P133 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.


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


In First Order Logic:
P133(x,y) ⊃ E92(x) 
P133(x,y) ⊃ E92(y) 
P133(x,y) ⊃ P133(y,x)
P133(x,y) ⊃ ¬P132(x,y)</rdfs:comment>
  </owl:SymmetricProperty>
  <owl:FunctionalProperty rdf:about="http://erlangen-crm.org/current/P22_transferred_title_to">
    <owl:inverseOf>
      <owl:InverseFunctionalProperty rdf:about="http://erlangen-crm.org/current/P22i_acquired_title_through"/>
    </owl:inverseOf>
    <rdfs:label xml:lang="en">P22 transferred title to</rdfs:label>
    <rdfs:domain rdf:resource="http://erlangen-crm.org/current/E8_Acquisition"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <rdfs:comment xml:lang="en">Scope note:
This property identifies the instance of E39 Actor that acquires the legal ownership of an object as a result of an instance of E8 Acquisition.

The property will typically describe an Actor purchasing or otherwise acquiring an object from another Actor. However, title may also be acquired, without any corresponding loss of title by another Actor, through legal fieldwork such as hunting, shooting or fishing.

In reality the title is either transferred to or from someone, or both.


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


In First Order Logic:
P22(x,y) ⊃ E8(x)
P22(x,y) ⊃ E39(y)
P22 (x,y) ⊃ P14(x,y)</rdfs:comment>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P22</skos:notation>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P14_carried_out_by"/>
  </owl:FunctionalProperty>
  <owl:InverseFunctionalProperty rdf:about="http://erlangen-crm.org/current/P22i_acquired_title_through">
    <rdfs:label xml:lang="en">P22 acquired title through</rdfs:label>
    <skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >P22i</skos:notation>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
    <owl:inverseOf rdf:resource="http://erlangen-crm.org/current/P22_transferred_title_to"/>
    <rdfs:subPropertyOf rdf:resource="http://erlangen-crm.org/current/P14i_performed"/>
    <rdfs:range rdf:resource="http://erlangen-crm.org/current/E8_Acquisition"/>
  </owl:InverseFunctionalProperty>
</rdf:RDF>

<!-- Created with Protege (with OWL Plugin 3.5, Build 663)  http://protege.stanford.edu -->