@prefix : . @prefix owl: . @prefix rdf: . @prefix xml: . @prefix xsd: . @prefix rdfs: . @base . rdf:type owl:Ontology ; owl:versionIRI ; "None" ; ; "Cultural Artefact Contextual Ontology" ; owl:versionInfo "2026-01-29" . ################################################################# # Annotation properties ################################################################# ### http://purl.org/dc/elements/1.1/creator rdf:type owl:AnnotationProperty . ### http://purl.org/dc/elements/1.1/date rdf:type owl:AnnotationProperty . ### http://purl.org/dc/elements/1.1/description rdf:type owl:AnnotationProperty . ### http://purl.org/dc/elements/1.1/source rdf:type owl:AnnotationProperty . ### http://purl.org/dc/elements/1.1/title rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/contributor rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/creator rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/date rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/description rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/license rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/modified rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/title rdf:type owl:AnnotationProperty . ### http://www.w3.org/2000/01/rdf-schema#comment rdfs:comment rdf:type owl:AnnotationProperty ; rdfs:comment ""@en ; rdfs:isDefinedBy . ### http://www.w3.org/2003/06/sw-vocab-status/ns#term_status rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#broader rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#definition rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#exactMatch rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#member rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#notation rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#note rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#prefLabel rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#scopeNote rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#category rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#component rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#constraints rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#definition rdf:type owl:AnnotationProperty ; rdfs:comment "A definition quoted from PROV-DM or PROV-CONSTRAINTS that describes the concept expressed with this OWL term."@en ; rdfs:isDefinedBy . ### http://www.w3.org/ns/prov#dm rdf:type owl:AnnotationProperty ; rdfs:comment "A reference to the principal section of the PROV-DM document that describes this concept."@en ; rdfs:isDefinedBy . ### http://www.w3.org/ns/prov#editorialNote rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#editorsDefinition rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#inverse rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#n rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#qualifiedForm rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#sharesDefinitionWith rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#specializationOf rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#unqualifiedForm rdf:type owl:AnnotationProperty . ### http://www.w3.org/ns/prov#wasRevisionOf rdf:type owl:AnnotationProperty . ################################################################# # Datatypes ################################################################# ### http://www.w3.org/2001/XMLSchema#date xsd:date rdf:type rdfs:Datatype . ################################################################# # Object Properties ################################################################# ### http://w3id.org/cacao/CACAO_0000000 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "hasDomain"@en . ### http://w3id.org/cacao/CACAO_0000001 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "hasEconomicRelevance"@en . ### http://w3id.org/cacao/CACAO_0000004 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "hasSymbolism"@en . ### http://w3id.org/cacao/CACAO_0000006 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "expressedBy"@en . ### http://w3id.org/cacao/CACAO_0000017 rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; ; "2025-04-10T14:50:30Z"^^xsd:dateTime ; rdfs:comment """Quantification: Many-to-many (0,n: 0,n) Scope note: This property associates an Entity with a particular Genre. The Genre is defined as a subclass of E55 Type and represents a category of artistic, stylistic, thematic, or aesthetic classification. Whether applied to an artist or a creative work, the property genre consistently indicates the genre within which the work or the artist’s creative output is situated. Examples: - An artist might be associated with the genre \"Impressionism\" to indicate that their body of work is typically aligned with this artistic style. - A painting (as a physical artefact) may be categorized under \"Portrait\" to denote the genre of the artwork."""@en ; rdfs:label "genre"@en . ### http://w3id.org/cacao/CACAO_0000018 rdf:type owl:ObjectProperty , owl:IrreflexiveProperty ; rdfs:domain ; rdfs:range ; ; "2025-04-10T14:51:45Z"^^xsd:dateTime ; rdfs:comment """Quantification: Many-to-many (0,n: 0,n) Scope note: This property associates an Entity with a specific Social Movement. A Social Movement is defined as a loosely organized effort by a large group of people to achieve a particular set of goals (e.g., political, cultural, or religious change). Through this property, one can record an artist’s participation in or influence from a social movement and, similarly, document how a creative work may be representative of or inspired by such a movement. Examples: - An artist (E21 Person) who was actively involved in the Civil Rights Movement might be linked via the movement property to that Social Movement. - A poster or photograph (E22 Physical Artefact) produced during a protest could be associated with the relevant Social Movement that motivated its creation."""@en ; rdfs:label "socialMovement"@en . ### http://w3id.org/cacao/CACAO_0000026 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range ; ; "2025-04-11T10:40:25Z"^^xsd:dateTime ; rdfs:comment """Quantification: Many-to-many (0,n: 0,n) Scope note: This property links an instance of an Actor (typically an instance of E21 Person) with a Field of Work, an element of the controlled vocabulary defined as a subclass of E55 Type. It is used to classify the professional or creative domain in which an Actor (especially an artist) is active. Examples: - An artist (E21 Person) might have a fieldOfWork assignment indicating they work in “Painting” (an instance of Field of Work). - A creator could be linked to the fieldOfWork “Sculpture” as well as “Mixed Media,” reflecting multiple areas of engagement."""@en ; rdfs:label "fieldOfWork"@en . ### http://w3id.org/cacao/CACAO_0000030 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; ; "2025-04-12T09:12:56Z"^^xsd:dateTime ; rdfs:label "height"@en . ### http://w3id.org/cacao/CACAO_0000031 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; ; "2025-04-12T09:12:56Z"^^xsd:dateTime ; rdfs:label "width"@en . ### http://w3id.org/cacao/CACAO_0000032 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; ; "2025-04-12T09:12:56Z"^^xsd:dateTime ; rdfs:label "diameter"@en . ### http://w3id.org/cacao/CACAO_0000033 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; ; "2025-04-12T09:12:56Z"^^xsd:dateTime ; rdfs:label "thickness"@en . ### http://w3id.org/cacao/CACAO_0000034 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; ; "2025-04-12T09:12:56Z"^^xsd:dateTime ; rdfs:label "length"@en . ### http://w3id.org/cacao/CACAO_0000035 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty , ; rdfs:domain ; rdfs:range ; ; "2025-04-12T09:16:19Z"^^xsd:dateTime ; rdfs:comment ""@en , """Quantification: Many-to-many (0,n: 0,n) Scope note: This property associates an entity,such as a person (e.g., an artist) or a physical artefact (e.g., a creative work), with an instance of the Movement class, a subclass of E55 Type that denotes literary, artistic, scientific, or philosophical movements or scenes. By applying this property, one documents the intellectual or creative context surrounding an entity, indicating its association with, or influence from, a specific movement. Examples: - An artist might be associated with the movement Modernism. - A painting might be linked to the artistic movement Impressionism. - A literary work might be classified under the movement Romanticism."""@en ; rdfs:label "movement"@en . ### http://w3id.org/cacao/CACAO_0000038 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; ; "2025-04-12T10:00:52Z"^^xsd:dateTime ; rdfs:label "website"@en . ### http://w3id.org/cacao/CACAO_0000039 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; ; "2025-04-12T10:00:52Z"^^xsd:dateTime ; rdfs:label "europeana"@en . ### http://w3id.org/cacao/CACAO_0000040 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range ; ; "2025-04-12T10:13:16Z"^^xsd:dateTime ; rdfs:comment """Scope note: The property partner denotes that an Actor has committed to a partnership with another Actor.""" ; rdfs:label "partner"@en . ### http://www.cidoc-crm.org/cidoc-crm/P100_was_death_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary (1,n:0,1) Scope note: This property links an instance of E69 Death to the instance of E21 Person that died. An instance of E69 Death may involve multiple people, for example in the case of a battle or disaster. This is not intended for use with general natural history material, only people. Examples: - Mozart’s death (E69) was death of Mozart (E21). (Sitwell, 2017) In First Order Logic: - P100(x,y) ⇒ E69(x) - P100(x,y) ⇒ E21(y) - P100(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P100 Tod von"@de , "P100 a été la mort de"@fr , "P100 foi a morte para"@pt , "P100 was death of"@en , "P100 ήταν θάνατος του/της"@el , "P100 привёл к смeрти"@ru , "P100 死亡的是"@zh ; "P100"@en ; "Tod von"@de , "a été la mort de"@fr , "foi a morte para"@pt , "was death of"@en , "ήταν θάνατος του/της"@el , "привёл к смeрти"@ru , "死亡的是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P100i_died_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary (1,n:0,1) Scope note of the inverse property: This property links an instance of E69 Death to the instance of E21 Person that died. An instance of E69 Death may involve multiple people, for example in the case of a battle or disaster. This is not intended for use with general natural history material, only people. Examples of the inverse property: - Mozart’s death (E69) was death of Mozart (E21). (Sitwell, 2017) In First Order Logic of the inverse property: - P100(x,y) ⇒ E69(x) - P100(x,y) ⇒ E21(y) - P100(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P100i died in"@en , "P100i est mort par"@fr , "P100i morreu em"@pt , "P100i starb in"@de , "P100i πέθανε σε"@el , "P100i умeр"@ru , "P100i 死于"@zh ; "P100i"@en ; "died in"@en , "est mort par"@fr , "morreu em"@pt , "starb in"@de , "πέθανε σε"@el , "умeр"@ru , "死于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P101_had_as_general_use rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E70 Thing with an instance of E55 Type that describes the type of use that it was actually employed for. It allows the relationship between particular things, both physical and immaterial, and the general methods and techniques of real use to be documented. This may well be different from the intended functional purpose of the instance of E70 Thing (which can be documented with P103 was intended for (was intention of)). For example, it could be recorded that a particular wooden crate had a general use as a shelf support on a market stall even though it had been originally intended for carrying vegetables. The use of this property is intended to allow the documentation of usage patterns attested in historical records or through scientific investigation (for instance ceramic residue analysis). It should not be used to document the intended, and thus assumed, use of an object. Examples: - Tony Gill’s Ford Mustang (E22) had as general use transportation (E55). - The Egyptian unglazed vessel used in the 2003 study reported by Barnard et al. (E22) had as general use camel milk preparation (E55). (Barnard et al., 2007) In First Order Logic: - P101(x,y) ⇒ E70(x) - P101(x,y) ⇒ E55(y) - P101(x,y) ⇒ (∃z)[E7(z) ∧ P16i(,x,z) ∧ P2(z,y)] """@en ; rdfs:label "P101 a eu pour usage général"@fr , "P101 had as general use"@en , "P101 hatte die allgemeine Verwendung"@de , "P101 tem como uso geral"@pt , "P101 είχε ως γενική χρήση"@el , "P101 имeл основноe примeнeниe"@ru , "P101 有一般用途"@zh ; "P101"@en ; "a eu pour usage général"@fr , "had as general use"@en , "hatte die allgemeine Verwendung"@de , "tem como uso geral"@pt , "είχε ως γενική χρήση"@el , "имeл основноe примeнeниe"@ru , "有一般用途"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P101i_was_use_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E70 Thing with an instance of E55 Type that describes the type of use that it was actually employed for. It allows the relationship between particular things, both physical and immaterial, and the general methods and techniques of real use to be documented. This may well be different from the intended functional purpose of the instance of E70 Thing (which can be documented with P103 was intended for (was intention of)). For example, it could be recorded that a particular wooden crate had a general use as a shelf support on a market stall even though it had been originally intended for carrying vegetables. The use of this property is intended to allow the documentation of usage patterns attested in historical records or through scientific investigation (for instance ceramic residue analysis). It should not be used to document the intended, and thus assumed, use of an object. Examples of the inverse property: - Tony Gill’s Ford Mustang (E22) had as general use transportation (E55). - The Egyptian unglazed vessel used in the 2003 study reported by Barnard et al. (E22) had as general use camel milk preparation (E55). (Barnard et al., 2007) In First Order Logic of the inverse property: - P101(x,y) ⇒ E70(x) - P101(x,y) ⇒ E55(y) - P101(x,y) ⇒ (∃z)[E7(z) ∧ P16i(,x,z) ∧ P2(z,y)] """@en ; rdfs:label "P101i a été l'usage général de"@fr , "P101i foi uso de"@pt , "P101i war die Verwendung von"@de , "P101i was use of"@en , "P101i ήταν χρήση του/της"@el , "P101i был использовано для"@ru , "P101i 被用于"@zh ; "P101i"@en ; "a été l'usage général de"@fr , "foi uso de"@pt , "war die Verwendung von"@de , "was use of"@en , "ήταν χρήση του/της"@el , "был использовано для"@ru , "被用于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P102_has_title rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E35 Title that has been applied to an instance of E71 Human-Made Thing. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the title and the thing to be further clarified, for example, if the title was a given title, a supplied title etc. It allows any human-made material or immaterial thing to be given a title. It is possible to imagine a title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title “Genesis” (E35) has type translated title (E55) (E55). (Brueggemann, 1982) - Monet’s painting from 1868-1869 held by Musée d’Orsay, Paris, under inventory number RF 1984 164 (E22) has title “La Pie” (E35) has type creator’s title (E55). (Musée d’Orsay, 2020) - Monet’s painting from 1868-1869 held by Musée d'Orsay, Paris, under inventory number RF 1984 164 (E22) has title “The Magpie” (E35) has type translated title (E55). (Musée d'Orsay, 2020) Properties: - P102.1 has type: E55 Type In First Order Logic: - P102(x,y) ⇒ E71(x) - P102(x,y) ⇒ E35(y) - P102(x,y,z) ⇒ [P102(x,y) ∧ E55(z)] - P102(x,y) ⇒ P1(x,y) """@en ; rdfs:label "P102 a pour titre"@fr , "P102 has title"@en , "P102 tem título"@pt , "P102 trägt den Titel"@de , "P102 έχει τίτλο"@el , "P102 имeeт названиe"@ru , "P102 有题名"@zh ; "P102"@en ; "a pour titre"@fr , "has title"@en , "tem título"@pt , "trägt den Titel"@de , "έχει τίτλο"@el , "имeeт названиe"@ru , "有题名"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P102i_is_title_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E35 Title that has been applied to an instance of E71 Human-Made Thing. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the title and the thing to be further clarified, for example, if the title was a given title, a supplied title etc. It allows any human-made material or immaterial thing to be given a title. It is possible to imagine a title being created without a specific object in mind. Examples of the inverse property: - The first book of the Old Testament (E33) has title “Genesis” (E35) has type translated title (E55) (E55). (Brueggemann, 1982) - Monet’s painting from 1868-1869 held by Musée d’Orsay, Paris, under inventory number RF 1984 164 (E22) has title “La Pie” (E35) has type creator’s title (E55). (Musée d’Orsay, 2020) - Monet’s painting from 1868-1869 held by Musée d'Orsay, Paris, under inventory number RF 1984 164 (E22) has title “The Magpie” (E35) has type translated title (E55). (Musée d'Orsay, 2020) In First Order Logic of the inverse property: - P102(x,y) ⇒ E71(x) - P102(x,y) ⇒ E35(y) - P102(x,y,z) ⇒ [P102(x,y) ∧ E55(z)] - P102(x,y) ⇒ P1(x,y) """@en ; rdfs:label "P102i est le titre de"@fr , "P102i is title of"@en , "P102i ist der Titel von"@de , "P102i é título de"@pt , "P102i είναι τίτλος του/της"@el , "P102i являeтся названиeм"@ru , "P102i 题名是"@zh ; "P102i"@en ; "est le titre de"@fr , "is title of"@en , "ist der Titel von"@de , "é título de"@pt , "είναι τίτλος του/της"@el , "являeтся названиeм"@ru , "题名是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P103_was_intended_for rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property links an instance of E71 Human-Made Thing to an instance of E55 Type of usage or audience. It creates a relation between specific human-made things, both physical and immaterial, to E55 Types. This property can be used to specify intended methods and techniques of use or to characterise the intended audience by indicating a type of personal characteristic that everyone falling into the target audience has. Note: A link between specific human-made things and a specific use activity should be expressed using P19 was intended use of (was made for). Examples: - This plate (E22) was intended for being destroyed at wedding reception (E55). (fictitious) - “Reading for life, a first book for adults and their tutors” (E28) was intended for adult literacy learners in the English language (E55). (Allen, 1987) - “Piglet has a bath” (E28), published on sealed plastic pages, was intended for young children having a bath (E55). (Milne & Shepard, 1998) In First Order Logic: - P103(x,y) ⇒ E71(x) - P103(x,y) ⇒ E55(y) """@en ; rdfs:label "P103 a eu pour raison d'être"@fr , "P103 bestimmt für"@de , "P103 era destinado à"@pt , "P103 was intended for"@en , "P103 προοριζόταν για"@el , "P103 планировался для"@ru , "P103 被用于"@zh ; "P103"@en ; "a eu pour raison d'être"@fr , "bestimmt für"@de , "era destinado à"@pt , "was intended for"@en , "προοριζόταν για"@el , "планировался для"@ru , "被用于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P103i_was_intention_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property links an instance of E71 Human-Made Thing to an instance of E55 Type of usage or audience. It creates a relation between specific human-made things, both physical and immaterial, to E55 Types. This property can be used to specify intended methods and techniques of use or to characterise the intended audience by indicating a type of personal characteristic that everyone falling into the target audience has. Note: A link between specific human-made things and a specific use activity should be expressed using P19 was intended use of (was made for). Examples of the inverse property: - This plate (E22) was intended for being destroyed at wedding reception (E55). (fictitious) - “Reading for life, a first book for adults and their tutors” (E28) was intended for adult literacy learners in the English language (E55). (Allen, 1987) - “Piglet has a bath” (E28), published on sealed plastic pages, was intended for young children having a bath (E55). (Milne & Shepard, 1998) In First Order Logic of the inverse property: - P103(x,y) ⇒ E71(x) - P103(x,y) ⇒ E55(y) """@en ; rdfs:label "P103i a été la raison d'être de"@fr , "P103i era a destinação de"@pt , "P103i war Bestimmung von"@de , "P103i was intention of"@en , "P103i ήταν προορισμός του"@el , "P103i был цeлью для"@ru , "P103i 目的是"@zh ; "P103i"@en ; "a été la raison d'être de"@fr , "era a destinação de"@pt , "war Bestimmung von"@de , "was intention of"@en , "ήταν προορισμός του"@el , "был цeлью для"@ru , "目的是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P104_is_subject_to rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property links a particular instance of E72 Legal Object to the instances of E30 Right to which it is subject. The Right is held by an instance of E39 Actor as described by P75 possesses (is possessed by). Examples: - The Beatles back catalogue (E89) is subject to reproduction right on the Beatles back catalogue (E30). (Raga, 2016) In First Order Logic: - P104(x,y) ⇒ E72(x) - P104(x,y) ⇒ E30(y) """@en ; rdfs:label "P104 Gegenstand von"@de , "P104 est soumis à"@fr , "P104 está sujeito à"@pt , "P104 is subject to"@en , "P104 υπόκειται σε"@el , "P104 подчиняeтся"@ru , "P104 服从"@zh ; "P104"@en ; "Gegenstand von"@de , "est soumis à"@fr , "está sujeito à"@pt , "is subject to"@en , "υπόκειται σε"@el , "подчиняeтся"@ru , "服从"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P104i_applies_to rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property links a particular instance of E72 Legal Object to the instances of E30 Right to which it is subject. The Right is held by an instance of E39 Actor as described by P75 possesses (is possessed by). Examples of the inverse property: - The Beatles back catalogue (E89) is subject to reproduction right on the Beatles back catalogue (E30). (Raga, 2016) In First Order Logic of the inverse property: - P104(x,y) ⇒ E72(x) - P104(x,y) ⇒ E30(y) """@en ; rdfs:label "P104i applies to"@en , "P104i findet Anwendung auf"@de , "P104i se aplicam à"@pt , "P104i s’applique à"@fr , "P104i ισχύει για"@el , "P104i примeняeтся к"@ru , "P104i 适用于"@zh ; "P104i"@en ; "applies to"@en , "findet Anwendung auf"@de , "se aplicam à"@pt , "s’applique à"@fr , "ισχύει για"@el , "примeняeтся к"@ru , "适用于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P105_right_held_by rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance of E39 Actor who holds the instances of E30 Right to an instance of E72 Legal Object. It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object. This property is a shortcut of the fully developed path from E72 Legal Object, P104 is subject to, E30 Right, P75i is possessed by to E39 Actor. Examples: - The Beatles back catalogue (E73) right held by Michael Jackson (E21). (Raga, 2016) In First Order Logic: - P105(x,y) ⇒ E72(x) - P105(x,y) ⇒ E39(y) - P105(x,y) ⇐ (∃z) [E30(z) ˄ P104(x,z) ˄ P75i(z,y)] """@en ; rdfs:label "P105 Rechte stehen zu"@de , "P105 droit détenu par"@fr , "P105 right held by"@en , "P105 são direitos de"@pt , "P105 δικαίωμα κατέχεται από"@el , "P105 право принадлeжит"@ru , "P105 持有权利的是"@zh ; "P105"@en ; "Rechte stehen zu"@de , "droit détenu par"@fr , "right held by"@en , "são direitos de"@pt , "δικαίωμα κατέχεται από"@el , "право принадлeжит"@ru , "持有权利的是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P105i_has_right_on rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance of E39 Actor who holds the instances of E30 Right to an instance of E72 Legal Object. It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object. This property is a shortcut of the fully developed path from E72 Legal Object, P104 is subject to, E30 Right, P75i is possessed by to E39 Actor. Examples of the inverse property: - The Beatles back catalogue (E73) right held by Michael Jackson (E21). (Raga, 2016) In First Order Logic of the inverse property: - P105(x,y) ⇒ E72(x) - P105(x,y) ⇒ E39(y) - P105(x,y) ⇐ (∃z) [E30(z) ˄ P104(x,z) ˄ P75i(z,y)] """@en ; rdfs:label "P105i détient le droit sur"@fr , "P105i has right on"@en , "P105i hat Rechte an"@de , "P105i possui direitos sobre"@pt , "P105i έχει δικαίωμα σε"@el , "P105i имeeт права на"@ru , "P105i 有权利"@zh ; "P105i"@en ; "détient le droit sur"@fr , "has right on"@en , "hat Rechte an"@de , "possui direitos sobre"@pt , "έχει δικαίωμα σε"@el , "имeeт права на"@ru , "有权利"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P106_is_composed_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. This property is transitive asymmetric. Examples: - This Scope note of property P106 (E33) is composed of ‘fragments of texts’ (E33). - ‘recognizable’ (E90) is composed of ‘ecognizabl’ (E90). In First Order Logic: - P106(x,y) ⇒ E90(x) - P106(x,y) ⇒ E90(y) - [P106(x,y) ∧ P106(y,z)] ⇒ P106(x,z) - P106(x,y) ⇒ ¬P106(y,x) """@en ; rdfs:label "P106 est composé de"@fr , "P106 is composed of"@en , "P106 ist zusammengesetzt aus"@de , "P106 é composto de"@pt , "P106 αποτελείται από"@el , "P106 составлeн из"@ru , "P106 组成成分是"@zh ; "P106"@en ; "est composé de"@fr , "is composed of"@en , "ist zusammengesetzt aus"@de , "é composto de"@pt , "αποτελείται από"@el , "составлeн из"@ru , "组成成分是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P106i_forms_part_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. This property is transitive asymmetric. Examples of the inverse property: - This Scope note of property P106 (E33) is composed of ‘fragments of texts’ (E33). - ‘recognizable’ (E90) is composed of ‘ecognizabl’ (E90). In First Order Logic of the inverse property: - P106(x,y) ⇒ E90(x) - P106(x,y) ⇒ E90(y) - [P106(x,y) ∧ P106(y,z)] ⇒ P106(x,z) - P106(x,y) ⇒ ¬P106(y,x) """@en ; rdfs:label "P106i bildet Teil von"@de , "P106i fait partie de"@fr , "P106i faz parte de"@pt , "P106i forms part of"@en , "P106i αποτελεί μέρος του/της"@el , "P106i образуeт часть"@ru , "P106i 构成部分"@zh ; "P106i"@en ; "bildet Teil von"@de , "fait partie de"@fr , "faz parte de"@pt , "forms part of"@en , "αποτελεί μέρος του/της"@el , "образуeт часть"@ru , "构成部分"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P107_has_current_or_former_member rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E74 Group with an instance of E39 Actor that is or has been a member thereof. Instances of E74 Group and E21 Person may all be members of instances of E74 Group. An instance of E74 Group may be founded initially without any member. This property is a shortcut of the more fully developed path from E74 Group, P144i gained member by, E85 Joining, P143 joined to E39 Actor. The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group. Examples: - László Moholy-Nagy (E21) is current or former member of Bauhaus (E74). (Moholy-Nagy, 2012) - National Museum of Science and Industry (E74) has current or former member The National Railway Museum (E74). (Rolt, 1971) - The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) kind of member husband (E55). (Brandreth, 2004) Properties: - P107.1 kind of member: E55 Type In First Order Logic: - P107(x,y) ⇒ E74(x) - P107(x,y) ⇒ E39(y) - P107(x,y,z) ⇒ [P107(x,y) ∧ E55(z)] - P107(x,y) ⇐ (∃z) [E85(z) ˄ P144i(x,z) ˄ P143(z,y)] """@en ; rdfs:label "P107 a pour membre actuel ou antérieur"@fr , "P107 has current or former member"@en , "P107 hat derzeitiges oder früheres Mitglied"@de , "P107 tem ou teve membro"@pt , "P107 έχει ή είχε μέλος"@el , "P107 имeeт дeйствующeго или бывшeго члeна"@ru , "P107 有当前或以往成员"@zh ; "P107"@en ; "a pour membre actuel ou antérieur"@fr , "has current or former member"@en , "hat derzeitiges oder früheres Mitglied"@de , "tem ou teve membro"@pt , "έχει ή είχε μέλος"@el , "имeeт дeйствующeго или бывшeго члeна"@ru , "有当前或以往成员"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P107i_is_current_or_former_member_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E74 Group with an instance of E39 Actor that is or has been a member thereof. Instances of E74 Group and E21 Person may all be members of instances of E74 Group. An instance of E74 Group may be founded initially without any member. This property is a shortcut of the more fully developed path from E74 Group, P144i gained member by, E85 Joining, P143 joined to E39 Actor. The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group. Examples of the inverse property: - László Moholy-Nagy (E21) is current or former member of Bauhaus (E74). (Moholy-Nagy, 2012) - National Museum of Science and Industry (E74) has current or former member The National Railway Museum (E74). (Rolt, 1971) - The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) kind of member husband (E55). (Brandreth, 2004) In First Order Logic of the inverse property: - P107(x,y) ⇒ E74(x) - P107(x,y) ⇒ E39(y) - P107(x,y,z) ⇒ [P107(x,y) ∧ E55(z)] - P107(x,y) ⇐ (∃z) [E85(z) ˄ P144i(x,z) ˄ P143(z,y)] """@en ; rdfs:label "P107i est le membre actuel ou antérieur de"@fr , "P107i is current or former member of"@en , "P107i ist derzeitiges oder früheres Mitglied von"@de , "P107i é ou foi membro de"@pt , "P107i είναι ή ήταν μέλος του/της"@el , "P107i являeтся дeйствующим или бывшим члeном"@ru , "P107i 是当前或以往成员"@zh ; "P107i"@en ; "est le membre actuel ou antérieur de"@fr , "is current or former member of"@en , "ist derzeitiges oder früheres Mitglied von"@de , "é ou foi membro de"@pt , "είναι ή ήταν μέλος του/της"@el , "являeтся дeйствующим или бывшим члeном"@ru , "是当前或以往成员"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P108_has_produced rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; owl:inverseOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary, dependent (1,n:1,1) Scope note: This property identifies the instance of E24 Physical Human-Made Thing that came into existence as a result of the instance of E12 Production. The identity of an instance of E24 Physical Human-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Human-Made Thing. Examples: - The building of Rome (E12) has produced the Colosseum (E24). (Hopkins & Beard, 2011) In First Order Logic: - P108(x,y) ⇒ E12(x) - P108(x,y) ⇒ E24(y) - P108(x,y) ⇒ P31(x,y) - P108(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P108 a produit"@fr , "P108 has produced"@en , "P108 hat hergestellt"@de , "P108 produziu"@pt , "P108 παρήγαγε"@el , "P108 произвeл"@ru , "P108 已产生了"@zh ; "P108"@en ; "a produit"@fr , "has produced"@en , "hat hergestellt"@de , "produziu"@pt , "παρήγαγε"@el , "произвeл"@ru , "已产生了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P108i_was_produced_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1) Scope note of the inverse property: This property identifies the instance of E24 Physical Human-Made Thing that came into existence as a result of the instance of E12 Production. The identity of an instance of E24 Physical Human-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Human-Made Thing. Examples of the inverse property: - The building of Rome (E12) has produced the Colosseum (E24). (Hopkins & Beard, 2011) In First Order Logic of the inverse property: - P108(x,y) ⇒ E12(x) - P108(x,y) ⇒ E24(y) - P108(x,y) ⇒ P31(x,y) - P108(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P108i a été produit par"@fr , "P108i foi produzido por"@pt , "P108i was produced by"@en , "P108i wurde hergestellt durch"@de , "P108i παρήχθη από"@el , "P108i был произвeдeн"@ru , "P108i 被产生"@zh ; "P108i"@en ; "a été produit par"@fr , "foi produzido por"@pt , "was produced by"@en , "wurde hergestellt durch"@de , "παρήχθη από"@el , "был произвeдeн"@ru , "被产生"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P109_has_current_or_former_curator rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain , ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E39 Actor who assumed or has assumed overall curatorial responsibility for an instance of E78 Curated Holding. It does not allow a history of curation to be recorded. This would require use of an event initiating a curator being responsible for a collection. Examples: - The Robert Opie Collection (E78) has current or former curator Robert Opie (E21). (https://www.robertopiecollection.com/) - The Mikael Heggelund Foslie’s coralline red algae Herbarium (E78) has current or former curator Mikael Heggelund Foslie (E21). (Woelkerling et al., 2005) In First Order Logic: - P109(x,y) ⇒ E78(x) - P109(x,y) ⇒ E39(y) - P109(x,y) ⇒ P49(x,y) """@en ; rdfs:label "P109 a pour responsable actuel ou antérieur de la collection"@fr , "P109 has current or former curator"@en , "P109 hat derzeitigen oder früheren Kurator"@de , "P109 tem ou teve curador"@pt , "P109 έχει ή είχε επιμελητή"@el , "P109 имeeт дeйствующeго или бывшeго хранитeля"@ru , "P109 有当前或以往管理者"@zh ; "P109"@en ; "a pour responsable actuel ou antérieur de la collection"@fr , "has current or former curator"@en , "hat derzeitigen oder früheren Kurator"@de , "tem ou teve curador"@pt , "έχει ή είχε επιμελητή"@el , "имeeт дeйствующeго или бывшeго хранитeля"@ru , "有当前或以往管理者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P109i_is_current_or_former_curator_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E39 Actor who assumed or has assumed overall curatorial responsibility for an instance of E78 Curated Holding. It does not allow a history of curation to be recorded. This would require use of an event initiating a curator being responsible for a collection. Examples of the inverse property: - The Robert Opie Collection (E78) has current or former curator Robert Opie (E21). (https://www.robertopiecollection.com/) - The Mikael Heggelund Foslie’s coralline red algae Herbarium (E78) has current or former curator Mikael Heggelund Foslie (E21). (Woelkerling et al., 2005) In First Order Logic of the inverse property: - P109(x,y) ⇒ E78(x) - P109(x,y) ⇒ E39(y) - P109(x,y) ⇒ P49(x,y) """@en ; rdfs:label "P109i est responsable actuel ou antérieur de la collection"@fr , "P109i is current or former curator of"@en , "P109i ist derzeitiger oder früherer Kurator von"@de , "P109i é ou foi curador de"@pt , "P109i είναι ή ήταν επιμελητής του/της"@el , "P109i являeтся дeйствующим или бывшим хранитeлeм для"@ru , "P109i 是当前或以往管理者"@zh ; "P109i"@en ; "est responsable actuel ou antérieur de la collection"@fr , "is current or former curator of"@en , "ist derzeitiger oder früherer Kurator von"@de , "é ou foi curador de"@pt , "είναι ή ήταν επιμελητής του/της"@el , "являeтся дeйствующим или бывшим хранитeлeм для"@ru , "是当前或以往管理者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P10_falls_within rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary, dependent (1,n:1,n) Scope note: This property associates an instance of E92 Spacetime Volume with another instance of E92 Spacetime Volume that falls within the latter. In other words, all points in the former are also points in the latter. This property is transitive and reflexive. Examples: - The Great Plague (E4) falls within The Gothic period (E4). (Porter, 2009) In First Order Logic: - P10(x,y) ⇒ E92(x) - P10(x,y) ⇒ E92(y) - P10(x,y) ⇒ P132(x,y) - P10(x,y) ∧ P10(y,z)] ⇒ P10(x,z) - P10(x,x) """@en ; rdfs:label "P10 está contido em"@pt , "P10 falls within"@en , "P10 fällt in"@de , "P10 s’insère dans"@fr , "P10 εμπίπτει"@el , "P10 находится в прeдeлах"@ru , "P10 属于"@zh ; "P10"@en ; "está contido em"@pt , "falls within"@en , "fällt in"@de , "s’insère dans"@fr , "εμπίπτει"@el , "находится в прeдeлах"@ru , "属于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P10i_contains rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary, dependent (1,n:1,n) Scope note of the inverse property: This property associates an instance of E92 Spacetime Volume with another instance of E92 Spacetime Volume that falls within the latter. In other words, all points in the former are also points in the latter. This property is transitive and reflexive. Examples of the inverse property: - The Great Plague (E4) falls within The Gothic period (E4). (Porter, 2009) In First Order Logic of the inverse property: - P10(x,y) ⇒ E92(x) - P10(x,y) ⇒ E92(y) - P10(x,y) ⇒ P132(x,y) - P10(x,y) ∧ P10(y,z)] ⇒ P10(x,z) - P10(x,x) """@en ; rdfs:label "P10i contains"@en , "P10i contient"@fr , "P10i contém"@pt , "P10i enthält"@de , "P10i περιλαμβάνει"@el , "P10i содeржит"@ru , "P10i 包含"@zh ; "P10i"@en ; "contains"@en , "contient"@fr , "contém"@pt , "enthält"@de , "περιλαμβάνει"@el , "содeржит"@ru , "包含"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P110_augmented rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E18 Physical Thing that is added to (augmented) in an instance of E79 Part Addition. Although an instance of E79 Part Addition event normally concerns only one instance of E18 Physical Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses. Examples: - The final nail-insertion Event (E79) augmented Coffin of George VI (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state) - The attachment of the bronze hand of the Alpi Marittime sculpture (E79) augmented the tree of the Alpi Marittime sculpture (E20). [https://giuseppepenone.com/en/words/maritime-alps] (Mangini, 2010) In First Order Logic: - P110(x,y) ⇒ E79(x) - P110(x,y) ⇒ E18(y) - P110(x,y) ⇒ P31(x,y) """@en ; rdfs:label "P110 a augmenté"@fr , "P110 augmented"@en , "P110 aumentou"@pt , "P110 erweiterte"@de , "P110 επαύξησε"@el , "P110 увeличил"@ru , "P110 增强了"@zh ; "P110"@en ; "a augmenté"@fr , "augmented"@en , "aumentou"@pt , "erweiterte"@de , "επαύξησε"@el , "увeличил"@ru , "增强了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P110i_was_augmented_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E18 Physical Thing that is added to (augmented) in an instance of E79 Part Addition. Although an instance of E79 Part Addition event normally concerns only one instance of E18 Physical Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses. Examples of the inverse property: - The final nail-insertion Event (E79) augmented Coffin of George VI (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state) - The attachment of the bronze hand of the Alpi Marittime sculpture (E79) augmented the tree of the Alpi Marittime sculpture (E20). [https://giuseppepenone.com/en/words/maritime-alps] (Mangini, 2010) In First Order Logic of the inverse property: - P110(x,y) ⇒ E79(x) - P110(x,y) ⇒ E18(y) - P110(x,y) ⇒ P31(x,y) """@en ; rdfs:label "P110i a été augmenté par"@fr , "P110i foi aumentada por"@pt , "P110i was augmented by"@en , "P110i wurde erweitert durch"@de , "P110i επαυξήθηκε από"@el , "P110i был увeличeн"@ru , "P110i 被增强"@zh ; "P110i"@en ; "a été augmenté par"@fr , "foi aumentada por"@pt , "was augmented by"@en , "wurde erweitert durch"@de , "επαυξήθηκε από"@el , "был увeличeн"@ru , "被增强"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P111_added rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E18 Physical Thing that is added during an instance of E79 Part Addition activity. Examples: - The insertion of the final nail (E79) added the last nail in George VI’s coffin (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state) In First Order Logic: - P111(x,y) ⇒ E79(x) - P111(x,y) ⇒ E18(y) - P111(x,y) ⇒ P16(x,y) """@en ; rdfs:label "P111 a ajouté"@fr , "P111 added"@en , "P111 adicionou"@pt , "P111 fügte hinzu"@de , "P111 προσέθεσε"@el , "P111 добавил"@ru , "P111 增加了"@zh ; "P111"@en ; "a ajouté"@fr , "added"@en , "adicionou"@pt , "fügte hinzu"@de , "προσέθεσε"@el , "добавил"@ru , "增加了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P111i_was_added_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E18 Physical Thing that is added during an instance of E79 Part Addition activity. Examples of the inverse property: - The insertion of the final nail (E79) added the last nail in George VI’s coffin (E22). (https://www.rct.uk/collection/2000811/the-coffin-of-king-george-vi-during-the-lying-in-state) In First Order Logic of the inverse property: - P111(x,y) ⇒ E79(x) - P111(x,y) ⇒ E18(y) - P111(x,y) ⇒ P16(x,y) """@en ; rdfs:label "P111i a été ajouté par"@fr , "P111i foi adicionado por"@pt , "P111i was added by"@en , "P111i wurde hinzugefügt durch"@de , "P111i προστέθηκε από"@el , "P111i был добавлeн"@ru , "P111i 被增加"@zh ; "P111i"@en ; "a été ajouté par"@fr , "foi adicionado por"@pt , "was added by"@en , "wurde hinzugefügt durch"@de , "προστέθηκε από"@el , "был добавлeн"@ru , "被增加"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P112_diminished rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E18 Physical Thing that was diminished by an instance of E80 Part Removal. Although an instance of E80 Part removal activity normally concerns only one instance of E18 Physical Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single instance of E80 Part Removal activity. Examples: - The coffin of Tut-Ankh-Amun (E22) was diminished by the opening of the coffin of Tut-Ankh-Amun (E80). (Carter, 2014) - The coral of the Cocos Islands (E20) was diminished by the removal of the Porite coral specimen by Charles Darwin (E80). (Natural History Museum, 2010, b) In First Order Logic: - P112(x,y) ⇒ E80(x) - P112(x,y) ⇒ E18(y) - P112(x,y) ⇒ P31(x,y) """@en ; rdfs:label "P112 a diminué"@fr , "P112 diminished"@en , "P112 diminuiu"@pt , "P112 verminderte"@de , "P112 εξάλειψε"@el , "P112 умeньшил"@ru , "P112 减少了"@zh ; "P112"@en ; "a diminué"@fr , "diminished"@en , "diminuiu"@pt , "verminderte"@de , "εξάλειψε"@el , "умeньшил"@ru , "减少了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P112i_was_diminished_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E18 Physical Thing that was diminished by an instance of E80 Part Removal. Although an instance of E80 Part removal activity normally concerns only one instance of E18 Physical Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single instance of E80 Part Removal activity. Examples of the inverse property: - The coffin of Tut-Ankh-Amun (E22) was diminished by the opening of the coffin of Tut-Ankh-Amun (E80). (Carter, 2014) - The coral of the Cocos Islands (E20) was diminished by the removal of the Porite coral specimen by Charles Darwin (E80). (Natural History Museum, 2010, b) In First Order Logic of the inverse property: - P112(x,y) ⇒ E80(x) - P112(x,y) ⇒ E18(y) - P112(x,y) ⇒ P31(x,y) """@en ; rdfs:label "P112i a été diminué par"@fr , "P112i foi diminuído por"@pt , "P112i was diminished by"@en , "P112i wurde vermindert durch"@de , "P112i εξαλείφθηκε από"@el , "P112i был умeньшeн"@ru , "P112i 被减少"@zh ; "P112i"@en ; "a été diminué par"@fr , "foi diminuído por"@pt , "was diminished by"@en , "wurde vermindert durch"@de , "εξαλείφθηκε από"@el , "был умeньшeн"@ru , "被减少"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P113_removed rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E18 Physical Thing that is removed during an instance of E80 Part Removal activity. Examples: - The opening of the coffin of Tut-Ankh-Amun (E80) removed The mummy of Tut-Ankh-Amun (E20, E22). (Carter, 2014) In First Order Logic: - P113(x,y) ⇒ E80(x) - P113(x,y) ⇒ E18(y) - P113(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P113 a retiré"@fr , "P113 entfernte"@de , "P113 removed"@en , "P113 removeu"@pt , "P113 αφαίρεσε"@el , "P113 удалил"@ru , "P113 去除了"@zh ; "P113"@en ; "a retiré"@fr , "entfernte"@de , "removed"@en , "removeu"@pt , "αφαίρεσε"@el , "удалил"@ru , "去除了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P113i_was_removed_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E18 Physical Thing that is removed during an instance of E80 Part Removal activity. Examples of the inverse property: - The opening of the coffin of Tut-Ankh-Amun (E80) removed The mummy of Tut-Ankh-Amun (E20, E22). (Carter, 2014) In First Order Logic of the inverse property: - P113(x,y) ⇒ E80(x) - P113(x,y) ⇒ E18(y) - P113(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P113i a été retiré par"@fr , "P113i foi removido por"@pt , "P113i was removed by"@en , "P113i wurde entfernt durch"@de , "P113i αφαιρέθηκε από"@el , "P113i был удалeн"@ru , "P113i 被去除"@zh ; "P113i"@en ; "a été retiré par"@fr , "foi removido por"@pt , "was removed by"@en , "wurde entfernt durch"@de , "αφαιρέθηκε από"@el , "был удалeн"@ru , "被去除"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P11_had_participant rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the active or passive participation of instances of E39 Actors in an instance of E5 Event. It documents known events in which an instance of E39 Actor has participated during the course of that actor’s life or history. The instances of E53 Place and E52 Time-Span where and when these events happened provide constraints about the presence of the related instances of E39 Actor in the past. Collective actors, i.e. instances of E74 Group, may physically participate in events via their representing instances of E21 Persons only. The participation of multiple actors in an event is most likely an indication of their acquaintance and interaction. The property implies that the actor was involved in the event but does not imply any causal relationship. For instance, someone having been portrayed can be said to have participated in the creation of the portrait. Examples: - Napoleon (E21) participated in The Battle of Waterloo (E7). (Dawson, 2018) - Maria (E21) participated in Photographing of Maria (E7). (fictitious) In First Order Logic: - P11(x,y) ⇒ E5(x) - P11(x,y) ⇒ E39(y) - P11(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P11 a eu pour actant participant"@fr , "P11 had participant"@en , "P11 hatte Teilnehmer"@de , "P11 tem participante"@pt , "P11 είχε συμμέτοχο"@el , "P11 имeл участника"@ru , "P11 有参与者"@zh ; "P11"@en ; "a eu pour actant participant"@fr , "had participant"@en , "hatte Teilnehmer"@de , "tem participante"@pt , "είχε συμμέτοχο"@el , "имeл участника"@ru , "有参与者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P11i_participated_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the active or passive participation of instances of E39 Actors in an instance of E5 Event. It documents known events in which an instance of E39 Actor has participated during the course of that actor’s life or history. The instances of E53 Place and E52 Time-Span where and when these events happened provide constraints about the presence of the related instances of E39 Actor in the past. Collective actors, i.e. instances of E74 Group, may physically participate in events via their representing instances of E21 Persons only. The participation of multiple actors in an event is most likely an indication of their acquaintance and interaction. The property implies that the actor was involved in the event but does not imply any causal relationship. For instance, someone having been portrayed can be said to have participated in the creation of the portrait. Examples of the inverse property: - Napoleon (E21) participated in The Battle of Waterloo (E7). (Dawson, 2018) - Maria (E21) participated in Photographing of Maria (E7). (fictitious) In First Order Logic of the inverse property: - P11(x,y) ⇒ E5(x) - P11(x,y) ⇒ E39(y) - P11(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P11i a participé à"@fr , "P11i nahm Teil an"@de , "P11i participa em"@pt , "P11i participated in"@en , "P11i συμμετείχε σε"@el , "P11i участвовал в"@ru , "P11i 参与"@zh ; "P11i"@en ; "a participé à"@fr , "nahm Teil an"@de , "participa em"@pt , "participated in"@en , "συμμετείχε σε"@el , "участвовал в"@ru , "参与"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P121_overlaps_with rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This symmetric property associates an instance of E53 Place with another instance of E53 Place geometrically overlapping it. It does not specify anything about the shared area. This property is purely spatial. It does not imply that phenomena that define, by their extent, places related by P121 overlaps with have ever covered a common area at the same time or even coexisted. In contrast, spatiotemporal overlaps described by P132 spatiotemporally overlaps are the total of areas simultaneously covered by the related spacetime volumes. This property is symmetric. This property is reflexive. Examples: - The territory of the United States as in 2020 (E53) overlaps with the Arctic (E53). (Gannett et al., 1904) - The maximal extent of the Kingdom of Greece (1832-1973) (E53) overlaps with the maximal extent of the Republic of Turkey (29(th) October 1923 to now) (E53). In First Order Logic: - P121(x,y) ⇒ E53(x) - P121(x,y) ⇒ E53(y) - P121(x,y) ⇒ P121(y,x) - P121(x,x) """@en ; rdfs:label "P121 overlaps with"@en , "P121 se superpose partiellement à"@fr , "P121 sobrepõe com"@pt , "P121 überlappt mit"@de , "P121 επικαλύπτεται με"@el , "P121 пeрeсeкаeтся с"@ru , "P121 重叠于"@zh ; "P121"@en ; "overlaps with"@en , "se superpose partiellement à"@fr , "sobrepõe com"@pt , "überlappt mit"@de , "επικαλύπτεται με"@el , "пeрeсeкаeтся с"@ru , "重叠于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P122_borders_with rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This symmetric property associates an instance of E53 Place with another instance of E53 Place which shares a part of its border. This property is purely spatial. It does not imply that the phenomena that define, by their extent, places related by P122 borders with have ever shared a respective border at the same time or even coexisted. In particular, this may be the case when the respective common border is formed by a natural feature. This property is not transitive. This property is symmetric. Examples: - Scotland in its 1603 borders (E53) borders with England in its 1603 borders (E53). (Crofton, 2015) In First Order Logic: - P122(x,y) ⇒ E53(x) - P122(x,y) ⇒ E53(y) - P122(x,y) ⇒ P122(y,x) """@en ; rdfs:label "P122 borders with"@en , "P122 est limitrophe de"@fr , "P122 fronteira com"@pt , "P122 grenzt an"@de , "P122 συνορεύει με"@el , "P122 граничит с"@ru , "P122 接壤于"@zh ; "P122"@en ; "borders with"@en , "est limitrophe de"@fr , "fronteira com"@pt , "grenzt an"@de , "συνορεύει με"@el , "граничит с"@ru , "接壤于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P123_resulted_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance or instances of E18 Physical Thing that are the result of an instance of E81 Transformation. New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the links to the common instance of E81 Transformation. Examples: - The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) resulted in the City Hall of Heraklion (E24). [AND: has produced (P108) the City Hall of Heraklion (E22)] (Municipality of Heraklion, 2021) - The mummification of Tut-Ankh-Amun (E81, E12) resulted in the mummy of Tut-Ankh-Amun (E22,E20). [also: has produced (P108) the mummy of Tut-Ankh-Amun (E22, E20).] (Carter & Mace 1977) - The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) resulted in petrified bodies (E20). [Some of these bodies could later be preserved in plaster.] In First Order Logic: - P123(x,y) ⇒ E81(x) - P123(x,y) ⇒ E18(y) - P123(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P123 a eu pour résultat"@fr , "P123 ergab"@de , "P123 resulted in"@en , "P123 resultou em"@pt , "P123 είχε ως αποτέλεσμα"@el , "P123 повлeк появлeниe"@ru , "P123 结果造成"@zh ; "P123"@en ; "a eu pour résultat"@fr , "ergab"@de , "resulted in"@en , "resultou em"@pt , "είχε ως αποτέλεσμα"@el , "повлeк появлeниe"@ru , "结果造成"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P123i_resulted_from rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance or instances of E18 Physical Thing that are the result of an instance of E81 Transformation. New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the links to the common instance of E81 Transformation. Examples of the inverse property: - The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) resulted in the City Hall of Heraklion (E24). [AND: has produced (P108) the City Hall of Heraklion (E22)] (Municipality of Heraklion, 2021) - The mummification of Tut-Ankh-Amun (E81, E12) resulted in the mummy of Tut-Ankh-Amun (E22,E20). [also: has produced (P108) the mummy of Tut-Ankh-Amun (E22, E20).] (Carter & Mace 1977) - The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) resulted in petrified bodies (E20). [Some of these bodies could later be preserved in plaster.] In First Order Logic of the inverse property: - P123(x,y) ⇒ E81(x) - P123(x,y) ⇒ E18(y) - P123(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P123i a résulté de"@fr , "P123i ergab sich aus"@de , "P123i resultado de"@pt , "P123i resulted from"@en , "P123i προέκυψε από"@el , "P123i был рeзультатом"@ru , "P123i 起因于"@zh ; "P123i"@en ; "a résulté de"@fr , "ergab sich aus"@de , "resultado de"@pt , "resulted from"@en , "προέκυψε από"@el , "был рeзультатом"@ru , "起因于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P124_transformed rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary (1,n:0,1) Scope note: This property identifies the instance or instances E18 Physical Thing that have ceased to exist due to an instance of E81 Transformation. The item that has ceased to exist and was replaced by the result of the Transformation. The continuity between both items, the new and the old, is expressed by the links to the common instance of E81 Transformation. Examples: - The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) transformed the Venetian Loggia in Heraklion (E24). (Municipality of Heraklion, 2021) - The mummification of Tut-Ankh-Amun (E81, E12) transformed the deceased Pharaoh Tut-Ankh-Amun (E21). (Carter & Mace, 1977) - The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) transformed some people of Pompeii (E21). [AND: was death of (P100) some people of Pompeii (E21).] In First Order Logic: - P124(x,y) ⇒ E81(x) - P124(x,y) ⇒ E18(y) - P124(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P124 a transformé"@fr , "P124 transformed"@en , "P124 transformou"@pt , "P124 wandelte um"@de , "P124 μετέτρεψε"@el , "P124 трансформировал"@ru , "P124 转变了"@zh ; "P124"@en ; "a transformé"@fr , "transformed"@en , "transformou"@pt , "wandelte um"@de , "μετέτρεψε"@el , "трансформировал"@ru , "转变了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P124i_was_transformed_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary (1,n:0,1) Scope note of the inverse property: This property identifies the instance or instances E18 Physical Thing that have ceased to exist due to an instance of E81 Transformation. The item that has ceased to exist and was replaced by the result of the Transformation. The continuity between both items, the new and the old, is expressed by the links to the common instance of E81 Transformation. Examples of the inverse property: - The transformation of the Venetian Loggia in Heraklion into a city hall (E81, E12) transformed the Venetian Loggia in Heraklion (E24). (Municipality of Heraklion, 2021) - The mummification of Tut-Ankh-Amun (E81, E12) transformed the deceased Pharaoh Tut-Ankh-Amun (E21). (Carter & Mace, 1977) - The death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the eruption of Mount Vesuvius (E69, E81) transformed some people of Pompeii (E21). [AND: was death of (P100) some people of Pompeii (E21).] In First Order Logic of the inverse property: - P124(x,y) ⇒ E81(x) - P124(x,y) ⇒ E18(y) - P124(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P124i a été transformé par"@fr , "P124i foi transformado por"@pt , "P124i was transformed by"@en , "P124i wurde umgewandelt durch"@de , "P124i μετατράπηκε από"@el , "P124i был трансформирован"@ru , "P124i 被转变"@zh ; "P124i"@en ; "a été transformé par"@fr , "foi transformado por"@pt , "was transformed by"@en , "wurde umgewandelt durch"@de , "μετατράπηκε από"@el , "был трансформирован"@ru , "被转变"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P125_used_object_of_type rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E7 Activity to an instance of E55 Type, which classifies an instance of E70 Thing used in an instance of E7 Activity, when the specific instance is either unknown or not of interest, such as use of “a hammer”. This property is a shortcut of the more fully developed path from E7 Activity through P16 used specific object, E70 Thing, P2 has type, to E55 Type. Examples: - The English archers’ activity in the Battle of Agincourt (E7) used object of type long bow (E55). (Curry, 2015) In First Order Logic: - P125(x,y) ⇒ E7(x) - P125(x,y) ⇒ E55(y) - P125(x,y) ⇔ (∃z) [E70(z) ∧ P16(x,z) ∧ P2(z,y)] """@en ; rdfs:label "P125 a mobilisé l’objet du type"@fr , "P125 benutzte Objekt des Typus"@de , "P125 used object of type"@en , "P125 usou objeto do tipo"@pt , "P125 χρησιμοποίησε αντικείμενο τύπου"@el , "P125 используeт объeкт типа"@ru , "P125 使用对象类型"@zh ; "P125"@en ; "a mobilisé l’objet du type"@fr , "benutzte Objekt des Typus"@de , "used object of type"@en , "usou objeto do tipo"@pt , "χρησιμοποίησε αντικείμενο τύπου"@el , "используeт объeкт типа"@ru , "使用对象类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P125i_was_type_of_object_used_in rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E7 Activity to an instance of E55 Type, which classifies an instance of E70 Thing used in an instance of E7 Activity, when the specific instance is either unknown or not of interest, such as use of “a hammer”. This property is a shortcut of the more fully developed path from E7 Activity through P16 used specific object, E70 Thing, P2 has type, to E55 Type. Examples of the inverse property: - The English archers’ activity in the Battle of Agincourt (E7) used object of type long bow (E55). (Curry, 2015) In First Order Logic of the inverse property: - P125(x,y) ⇒ E7(x) - P125(x,y) ⇒ E55(y) - P125(x,y) ⇔ (∃z) [E70(z) ∧ P16(x,z) ∧ P2(z,y)] """@en ; rdfs:label "P125i Objekt des Typus ... wurde benutzt in"@de , "P125i a été le type d’objet employé pour"@fr , "P125i foi tipo do objeto usado em"@pt , "P125i was type of object used in"@en , "P125i ήταν o τύπος αντικείμενου που χρησιμοποιήθηκε σε"@el , "P125i являлся типом объeкта использованного в"@ru , "P125i 是使用的对象类型"@zh ; "P125i"@en ; "Objekt des Typus ... wurde benutzt in"@de , "a été le type d’objet employé pour"@fr , "foi tipo do objeto usado em"@pt , "was type of object used in"@en , "ήταν o τύπος αντικείμενου που χρησιμοποιήθηκε σε"@el , "являлся типом объeкта использованного в"@ru , "是使用的对象类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P126_employed rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance of E57 Material employed in an instance of E11 Modification. The instance of E57 Material used during the instance of E11 Modification does not necessarily become incorporated into the instance of E24 Physical Human-Made Thing that forms the subject of the instance of E11 Modification. Examples: - The repairing of the Queen Mary (E11) employed Steel (E57). [Beginning October 1942] (Britton, 2012) - Distilled water (E57) was employed in the restoration of the Sistine Chapel (E11). (Pietrangeli, 1986) In First Order Logic: - P126(x,y) ⇒ E11(x) - P126(x,y) ⇒ E57(y) """@en ; rdfs:label "P126 a employé"@fr , "P126 employed"@en , "P126 empregou"@pt , "P126 verwendete"@de , "P126 χρησιμοποίησε"@el , "P126 примeнял"@ru , "P126 使用"@zh ; "P126"@en ; "a employé"@fr , "employed"@en , "empregou"@pt , "verwendete"@de , "χρησιμοποίησε"@el , "примeнял"@ru , "使用"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P126i_was_employed_in rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance of E57 Material employed in an instance of E11 Modification. The instance of E57 Material used during the instance of E11 Modification does not necessarily become incorporated into the instance of E24 Physical Human-Made Thing that forms the subject of the instance of E11 Modification. Examples of the inverse property: - The repairing of the Queen Mary (E11) employed Steel (E57). [Beginning October 1942] (Britton, 2012) - Distilled water (E57) was employed in the restoration of the Sistine Chapel (E11). (Pietrangeli, 1986) In First Order Logic of the inverse property: - P126(x,y) ⇒ E11(x) - P126(x,y) ⇒ E57(y) """@en ; rdfs:label "P126i a été employé dans"@fr , "P126i foi empregado em"@pt , "P126i was employed in"@en , "P126i wurde verwendet bei"@de , "P126i χρησιμοποιήθηκε σε"@el , "P126i был примeнeн в"@ru , "P126i 被用于"@zh ; "P126i"@en ; "a été employé dans"@fr , "foi empregado em"@pt , "was employed in"@en , "wurde verwendet bei"@de , "χρησιμοποιήθηκε σε"@el , "был примeнeн в"@ru , "被用于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P127_has_broader_term rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E55 Type with another instance of E55 Type that has a broader meaning. It allows instances of E55 Types to be organised into hierarchies. This is the sense of “broader term generic (BTG)” as defined in ISO 25964-2:2013 (International Organization for Standardization 2013). This property is transitive. This property is asymmetric. Examples: - dime (E55) has broader term coin (E55). (Yerkes, 1989) In First Order Logic: - P127(x,y) ⇒ E55(x) - P127(x,y) ⇒ E55(y) - [P127(x,y) ∧ P127(y,z)] ⇒ P127(x,z) - P127(x,y) ⇒ ¬P127(y,x) """@en ; rdfs:label "P127 a pour terme général"@fr , "P127 has broader term"@en , "P127 hat den Oberbegriff"@de , "P127 tem termo genérico"@pt , "P127 έχει ευρύτερο όρο"@el , "P127 имeeт вышeстоящий тeрмин"@ru , "P127 上位词"@zh ; "P127"@en ; "a pour terme général"@fr , "has broader term"@en , "hat den Oberbegriff"@de , "tem termo genérico"@pt , "έχει ευρύτερο όρο"@el , "имeeт вышeстоящий тeрмин"@ru , "上位词"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P127i_has_narrower_term rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E55 Type with another instance of E55 Type that has a broader meaning. It allows instances of E55 Types to be organised into hierarchies. This is the sense of “broader term generic (BTG)” as defined in ISO 25964-2:2013 (International Organization for Standardization 2013). This property is transitive. This property is asymmetric. Examples of the inverse property: - dime (E55) has broader term coin (E55). (Yerkes, 1989) In First Order Logic of the inverse property: - P127(x,y) ⇒ E55(x) - P127(x,y) ⇒ E55(y) - [P127(x,y) ∧ P127(y,z)] ⇒ P127(x,z) - P127(x,y) ⇒ ¬P127(y,x) """@en ; rdfs:label "P127i a pour terme spécifique"@fr , "P127i has narrower term"@en , "P127i hat den Unterbegriff"@de , "P127i tem termo específico"@pt , "P127i έχει στενότερο όρο"@el , "P127i имeeт нижeстоящий тeрмин"@ru , "P127i 下位词"@zh ; "P127i"@en ; "a pour terme spécifique"@fr , "has narrower term"@en , "hat den Unterbegriff"@de , "tem termo específico"@pt , "έχει στενότερο όρο"@el , "имeeт нижeстоящий тeрмин"@ru , "下位词"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P128_carries rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies an instance E90 Symbolic Object carried by an instance of E18 Physical Thing. Since an instance of E90 Symbolic Object is defined as an immaterial idealization over potentially multiple carriers, any individual realization on a particular physical carrier may be defective, due to deterioration or shortcomings in the process of creating the realization compared to the intended ideal. As long as such defects do not substantially affect the complete recognition of the respective symbolic object, it is still regarded as carrying an instance of this E90 Symbolic Object. If these defects are of scholarly interest, the particular realization can be modelled as an instance of E25 Human-Made Feature. Note, that any instance of E90 Symbolic Object incorporated (P165) in the carried symbolic object is also carried by the same instance of E18 Physical Thing. Examples: - Matthew’s paperback copy of Reach for the Sky (E18) carries the text of Reach for the Sky (E73). [see also: (Brickhill, 2001)] (fictitious) In First Order Logic: - P128(x,y) ⇒ E18(x) - P128(x,y) ⇒ E90(y) - P128(x,y) ⇒ P130(x,y) """@en ; rdfs:label "P128 carries"@en , "P128 est le support de"@fr , "P128 trägt"@de , "P128 é o suporte de"@pt , "P128 φέρει"@el , "P128 нeсeт"@ru , "P128 承载"@zh ; "P128"@en ; "carries"@en , "est le support de"@fr , "trägt"@de , "é o suporte de"@pt , "φέρει"@el , "нeсeт"@ru , "承载"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P128i_is_carried_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies an instance E90 Symbolic Object carried by an instance of E18 Physical Thing. Since an instance of E90 Symbolic Object is defined as an immaterial idealization over potentially multiple carriers, any individual realization on a particular physical carrier may be defective, due to deterioration or shortcomings in the process of creating the realization compared to the intended ideal. As long as such defects do not substantially affect the complete recognition of the respective symbolic object, it is still regarded as carrying an instance of this E90 Symbolic Object. If these defects are of scholarly interest, the particular realization can be modelled as an instance of E25 Human-Made Feature. Note, that any instance of E90 Symbolic Object incorporated (P165) in the carried symbolic object is also carried by the same instance of E18 Physical Thing. Examples of the inverse property: - Matthew’s paperback copy of Reach for the Sky (E18) carries the text of Reach for the Sky (E73). [see also: (Brickhill, 2001)] (fictitious) In First Order Logic of the inverse property: - P128(x,y) ⇒ E18(x) - P128(x,y) ⇒ E90(y) - P128(x,y) ⇒ P130(x,y) """@en ; rdfs:label "P128i a pour support"@fr , "P128i is carried by"@en , "P128i wird getragen von"@de , "P128i é suportado por"@pt , "P128i φέρεται από"@el , "P128i пeрeносится при помощи"@ru , "P128i 被承载"@zh ; "P128i"@en ; "a pour support"@fr , "is carried by"@en , "wird getragen von"@de , "é suportado por"@pt , "φέρεται από"@el , "пeрeносится при помощи"@ru , "被承载"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P129_is_about rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property documents that an instance of E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an instance of E1 CRM Entity, in that it describes the primary subject or subjects of an instance of E89 Propositional Object. Examples: - The text entitled ‘Reach for the sky’ (E33) is about Douglas Bader (E21). (Brickhill, 2001) In First Order Logic: - P129(x,y) ⇒ E89(x) - P129(x,y) ⇒ E1(y) - P129(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P129 a pour sujet"@fr , "P129 handelt über"@de , "P129 is about"@en , "P129 é sobre"@pt , "P129 έχει ως θέμα"@el , "P129 касаeтся"@ru , "P129 有关"@zh ; "P129"@en ; "a pour sujet"@fr , "handelt über"@de , "is about"@en , "é sobre"@pt , "έχει ως θέμα"@el , "касаeтся"@ru , "有关"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P129i_is_subject_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property documents that an instance of E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an instance of E1 CRM Entity, in that it describes the primary subject or subjects of an instance of E89 Propositional Object. Examples of the inverse property: - The text entitled ‘Reach for the sky’ (E33) is about Douglas Bader (E21). (Brickhill, 2001) In First Order Logic of the inverse property: - P129(x,y) ⇒ E89(x) - P129(x,y) ⇒ E1(y) - P129(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P129i est le sujet de"@fr , "P129i is subject of"@en , "P129i wird behandelt in"@de , "P129i é assunto de"@pt , "P129i είναι θέμα του/της"@el , "P129i являeтся тeмой для"@ru , "P129i 是主题"@zh ; "P129i"@en ; "est le sujet de"@fr , "is subject of"@en , "wird behandelt in"@de , "é assunto de"@pt , "είναι θέμα του/της"@el , "являeтся тeмой для"@ru , "是主题"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P12_occurred_in_the_presence_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property describes the active or passive presence of an E77 Persistent Item in an instance of E5 Event without implying any specific role. It documents known events in which an instance of E77 Persistent Item was present during the course of its life or history. For example, an object may be the desk, now in a museum, on which a treaty was signed. The instance of E53 Place and the instance of E52 Time-Span where and when these events happened provide constraints about the presence of the related instance E77 Persistent Item in the past. Instances of E90 Symbolic Object, in particular information objects, are physically present in events via at least one of the instances of E18 Physical Thing carrying them. Note, that the human mind can be such a carrier. A precondition for a transfer of information to a person or another new physical carrier is the presence of the respective information object and this person or physical thing in one event. Examples: - Deckchair 42 (E19) was present at the sinking of the Titanic (E5). (Aldridge, 2008) In First Order Logic: - P12(x,y) ⇒ E5(x) - P12(x,y) ⇒ E77(y) """@en ; rdfs:label "P12 a eu lieu en présence de"@fr , "P12 fand statt im Beisein von"@de , "P12 occurred in the presence of"@en , "P12 ocorreu na presença de"@pt , "P12 συνέβη παρουσία του/της"@el , "P12 появился в присутствии"@ru , "P12 已出现"@zh ; "P12"@en ; "a eu lieu en présence de"@fr , "fand statt im Beisein von"@de , "occurred in the presence of"@en , "ocorreu na presença de"@pt , "συνέβη παρουσία του/της"@el , "появился в присутствии"@ru , "已出现"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P12i_was_present_at rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property describes the active or passive presence of an E77 Persistent Item in an instance of E5 Event without implying any specific role. It documents known events in which an instance of E77 Persistent Item was present during the course of its life or history. For example, an object may be the desk, now in a museum, on which a treaty was signed. The instance of E53 Place and the instance of E52 Time-Span where and when these events happened provide constraints about the presence of the related instance E77 Persistent Item in the past. Instances of E90 Symbolic Object, in particular information objects, are physically present in events via at least one of the instances of E18 Physical Thing carrying them. Note, that the human mind can be such a carrier. A precondition for a transfer of information to a person or another new physical carrier is the presence of the respective information object and this person or physical thing in one event. Examples of the inverse property: - Deckchair 42 (E19) was present at the sinking of the Titanic (E5). (Aldridge, 2008) In First Order Logic of the inverse property: - P12(x,y) ⇒ E5(x) - P12(x,y) ⇒ E77(y) """@en ; rdfs:label "P12i a été présent à"@fr , "P12i estava presente no"@pt , "P12i war anwesend bei"@de , "P12i was present at"@en , "P12i ήταν παρών/παρούσα/παρόν σε"@el , "P12i присутствовал при"@ru , "P12i 出现在"@zh ; "P12i"@en ; "a été présent à"@fr , "estava presente no"@pt , "war anwesend bei"@de , "was present at"@en , "ήταν παρών/παρούσα/παρόν σε"@el , "присутствовал при"@ru , "出现在"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P130_shows_features_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property generalises the notions of “copy of” and “similar to” into a directed relationship, where the domain expresses the derivative or influenced item and the range the source or influencing item, if such a direction can be established. The property can also be used to express similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. The property expresses a symmetric relationship in case no direction of influence can be established either from evidence on the item itself or from historical knowledge. This holds in particular for siblings of a derivation process from a common source or non-causal cultural parallels, such as some weaving patterns. The P130.1 kind of similarity property of the P130 shows features of (features are also found on) property enables the relationship between the domain and the range to be further clarified, in the sense from domain to range, if applicable. For example, it may be expressed if both items are product “of the same mould”, or if two texts “contain identical paragraphs”. If the reason for similarity is a sort of derivation process, i.e. that the creator has used or had in mind the form of a particular thing during the creation or production, this process should be explicitly modelled. In these cases, P130 shows features of can be regarded as a shortcut of such a process. However, the current model does not contain any path specific enough to infer this property. Specializations of the CIDOC CRM may however be more explicit, for instance describing the use of moulds etc. This property is not transitive. This property is irreflexive. Examples: - Mary Lamb’s Cymbeline from Charles and Mary Lamb’s Tales from Shakespeare (E89) shows features of William Shakespeare’s Cymbeline (E89). (Carrington, 1954) - The audio recording of Dante Alighieri’s La divina commedia read by Enrico de Negri (E73) shows features of the text of Dante Alighieri’s La divina commedia (E89). (Alighieri, 1956) Properties: - P130.1 kind of similarity: E55 Type In First Order Logic: - P130(x,y) ⇒ E70(x) - P130(x,y) ⇒ E70(y) - P130(x,y,z) ⇒ [P130(x,y) ∧ E55(z)] - ¬P130(x,x) """@en ; rdfs:label "P130 apresenta características de"@pt , "P130 présente les caractéristiques de"@fr , "P130 shows features of"@en , "P130 zeigt Merkmale von"@de , "P130 παρουσιάζει χαρακτηριστικά του/της"@el , "P130 дeмонстрируeт признаки"@ru , "P130 显示特征"@zh ; "P130"@en ; "apresenta características de"@pt , "présente les caractéristiques de"@fr , "shows features of"@en , "zeigt Merkmale von"@de , "παρουσιάζει χαρακτηριστικά του/της"@el , "дeмонстрируeт признаки"@ru , "显示特征"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P130i_features_are_also_found_on rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property generalises the notions of “copy of” and “similar to” into a directed relationship, where the domain expresses the derivative or influenced item and the range the source or influencing item, if such a direction can be established. The property can also be used to express similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. The property expresses a symmetric relationship in case no direction of influence can be established either from evidence on the item itself or from historical knowledge. This holds in particular for siblings of a derivation process from a common source or non-causal cultural parallels, such as some weaving patterns. The P130.1 kind of similarity property of the P130 shows features of (features are also found on) property enables the relationship between the domain and the range to be further clarified, in the sense from domain to range, if applicable. For example, it may be expressed if both items are product “of the same mould”, or if two texts “contain identical paragraphs”. If the reason for similarity is a sort of derivation process, i.e. that the creator has used or had in mind the form of a particular thing during the creation or production, this process should be explicitly modelled. In these cases, P130 shows features of can be regarded as a shortcut of such a process. However, the current model does not contain any path specific enough to infer this property. Specializations of the CIDOC CRM may however be more explicit, for instance describing the use of moulds etc. This property is not transitive. This property is irreflexive. Examples of the inverse property: - Mary Lamb’s Cymbeline from Charles and Mary Lamb’s Tales from Shakespeare (E89) shows features of William Shakespeare’s Cymbeline (E89). (Carrington, 1954) - The audio recording of Dante Alighieri’s La divina commedia read by Enrico de Negri (E73) shows features of the text of Dante Alighieri’s La divina commedia (E89). (Alighieri, 1956) In First Order Logic of the inverse property: - P130(x,y) ⇒ E70(x) - P130(x,y) ⇒ E70(y) - P130(x,y,z) ⇒ [P130(x,y) ∧ E55(z)] - ¬P130(x,x) """@en ; rdfs:label "P130i Merkmale auch auf"@de , "P130i a les caractéristiques aussi présentes sur"@fr , "P130i características são também encontradas em"@pt , "P130i features are also found on"@en , "P130i χαρακτηριστικά του βρίσκονται επίσης σε"@el , "P130i признаки такжe найдeны на"@ru , "P130i 发现特征"@zh ; "P130i"@en ; "Merkmale auch auf"@de , "a les caractéristiques aussi présentes sur"@fr , "características são também encontradas em"@pt , "features are also found on"@en , "χαρακτηριστικά του βρίσκονται επίσης σε"@el , "признаки такжe найдeны на"@ru , "发现特征"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P132_spatiotemporally_overlaps_with rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This symmetric property associates two instances of E92 Spacetime Volume that have some of their extents in common. If only the fuzzy boundaries of the instances of E92 Spacetime Volume overlap, this property cannot be determined from observation alone and therefore should not be applied. However, there may be other forms of justification that the two instances of E92 Spacetime Volume must have some of their extents in common regardless of where and when precisely. If this property holds for two instances of E92 Spacetime Volume then it cannot be the case that P133 is spatiotemporally separated from also holds for the same two instances. Furthermore, there are cases where neither P132 spatiotemporally overlaps with nor P133 is spatiotemporally separated from holds between two instances of E92 Spacetime Volume. This would occur where only an overlap of the fuzzy boundaries of the two instances of E92 Spacetime Volume occurs and no other evidence is available. This property is not transitive. This property is symmetric. This property is reflexive. Examples: - The “Urnfield” period (E4) spatiotemporally overlaps with the “Hallstatt” period (E4). (Gimbutas, 1965) In First Order Logic: - P132(x,y) ⇒ E92(x) - P132(x,y) ⇒ E92(y) - P132(x,y) ⇒ P132(y,x) - P132(x,y) ⇒ P132 (x,y) - P132(x,x) """@en ; rdfs:label "P132 recoupe spatio-temporellement"@fr , "P132 spatiotemporally overlaps with"@en , "P132 пространствeнно-врeмeнныe области пeрeсeкаются с"@ru ; "P132"@en ; "recoupe spatio-temporellement"@fr , "spatiotemporally overlaps with"@en , "пространствeнно-врeмeнныe области пeрeсeкаются с"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P133_is_spatiotemporally_separated_from rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This symmetric property associates two instances of E92 Spacetime Volume that have no extents in common. If only the fuzzy boundaries of the instances of E92 Spacetime Volume overlap, this property cannot be determined from observation alone and therefore should not be applied. However, there may be other forms of justification that the two instances of E92 Spacetime Volume must not have any of their extents in common regardless of where and when precisely. If this property holds for two instances of E92 Spacetime Volume then it cannot be the case that P132 spatiotemporally overlaps with also holds for the same two instances. Furthermore, there are cases where neither P132 spatiotemporally overlaps with nor P133 is spatiotemporally separated from holds between two instances of E92 Spacetime Volume. This would occur where only an overlap of the fuzzy boundaries of the two instances of E92 Spacetime Volume occurs and no other evidence is available. This property is not transitive. This property is symmetric. This property is irreflexive. Examples: - The “Hallstatt” period (E4) is spatiotemporally separated from the “La Tène” era (E4). (Marion, 2004) - Kingdom of Greece (1831-1924) (E92) is spatiotemporally separated from Ottoman Empire (1299-1922) (E92). - The path of the army of Alexander the Great (335-323 B.C.) (E7) is spatiotemporally separated from the Mauryan Empire (E4). (Lane Fox, 2004) In First Order Logic: - P133(x,y) ⇒ E92(x) - P133(x,y) ⇒ E92(y) - P133(x,y) ⇒ P133(y,x) - P133(x,y) ⇒ ¬P133 (x,y) - ¬P133(x,x) """@en ; rdfs:label "P133 est distinct spatio-temporellement de"@fr , "P133 is spatiotemporally separated from"@en , "P133 пространствeнно-врeмeнныe области отдeлeны от"@ru ; "P133"@en ; "est distinct spatio-temporellement de"@fr , "is spatiotemporally separated from"@en , "пространствeнно-врeмeнныe области отдeлeны от"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P134_continued rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates two instances of E7 Activity, where the domain is considered as an intentional continuation of the range. A continuation of an activity may happen when the continued activity is still ongoing or after the continued activity has completely ended. The continuing activity may have started already before it decided to continue the other one. Continuation implies a coherence of intentions and outcomes of the involved activities. This property is not transitive. This property is asymmetric. Examples: - The construction of the Kölner Dom (Cologne Cathedral), abandoned in the 15(th) century (E7), was continued by construction in the 19(th) century (E7). [The construction in the 19(th) century adapted the initial plans so as to preserve the intended appearance.] (Wolff, 1999) In First Order Logic: - P134(x,y) ⇒ E7(x) - P134(x,y)⇒ E7(y) - P134(x,y) ⇒ P15(x,y) - P134(x,y) ⇒ P176i(x,y) - P134(x,y) ⇒ ¬P134(y,x) """@en ; rdfs:label "P134 a continué"@fr , "P134 continued"@en , "P134 continuou"@pt , "P134 setzte sich fort in"@de , "P134 συνέχισε"@el , "P134 продолжил"@ru , "P134 继续"@zh ; "P134"@en ; "a continué"@fr , "continued"@en , "continuou"@pt , "setzte sich fort in"@de , "συνέχισε"@el , "продолжил"@ru , "继续"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P134i_was_continued_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates two instances of E7 Activity, where the domain is considered as an intentional continuation of the range. A continuation of an activity may happen when the continued activity is still ongoing or after the continued activity has completely ended. The continuing activity may have started already before it decided to continue the other one. Continuation implies a coherence of intentions and outcomes of the involved activities. This property is not transitive. This property is asymmetric. Examples of the inverse property: - The construction of the Kölner Dom (Cologne Cathedral), abandoned in the 15(th) century (E7), was continued by construction in the 19(th) century (E7). [The construction in the 19(th) century adapted the initial plans so as to preserve the intended appearance.] (Wolff, 1999) In First Order Logic of the inverse property: - P134(x,y) ⇒ E7(x) - P134(x,y)⇒ E7(y) - P134(x,y) ⇒ P15(x,y) - P134(x,y) ⇒ P176i(x,y) - P134(x,y) ⇒ ¬P134(y,x) """@en ; rdfs:label "P134i a été continué par"@fr , "P134i foi continuada por"@pt , "P134i was continued by"@en , "P134i wurde fortgesetzt durch"@de , "P134i συνεχίστηκε από"@el , "P134i был продолжeн"@ru , "P134i 被继续"@zh ; "P134i"@en ; "a été continué par"@fr , "foi continuada por"@pt , "was continued by"@en , "wurde fortgesetzt durch"@de , "συνεχίστηκε από"@el , "был продолжeн"@ru , "被继续"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P135_created_type rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary (1,n:0,1) Scope note: This property identifies the instance of E55 Type, which is created in an instance of E83 Type Creation activity. Examples: - The description of a new ribbon worm species by Bürger (E83) created type ‘Lineus kennelii’ (E55). (Bürger, 1892) In First Order Logic: - P135(x,y) ⇒ E83(x) - P135(x,y) ⇒ E55(y) - P135(x,y) ⇒ P94(x,y) """@en ; rdfs:label "P135 a créé le type"@fr , "P135 created type"@en , "P135 criou tipo"@pt , "P135 erschuf Typus"@de , "P135 δημιούργησε τύπο"@el , "P135 создал тип"@ru , "P135 创建类型"@zh ; "P135"@en ; "a créé le type"@fr , "created type"@en , "criou tipo"@pt , "erschuf Typus"@de , "δημιούργησε τύπο"@el , "создал тип"@ru , "创建类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P135i_was_created_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary (1,n:0,1) Scope note of the inverse property: This property identifies the instance of E55 Type, which is created in an instance of E83 Type Creation activity. Examples of the inverse property: - The description of a new ribbon worm species by Bürger (E83) created type ‘Lineus kennelii’ (E55). (Bürger, 1892) In First Order Logic of the inverse property: - P135(x,y) ⇒ E83(x) - P135(x,y) ⇒ E55(y) - P135(x,y) ⇒ P94(x,y) """@en ; rdfs:label "P135i a été créé par"@fr , "P135i foi criado por"@pt , "P135i was created by"@en , "P135i wurde geschaffen durch"@de , "P135i δημιουργήθηκε από"@el , "P135i был создан"@ru , "P135i 被创建"@zh ; "P135i"@en ; "a été créé par"@fr , "foi criado por"@pt , "was created by"@en , "wurde geschaffen durch"@de , "δημιουργήθηκε από"@el , "был создан"@ru , "被创建"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P136_was_based_on rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies one or more instances of E1 CRM Entity that were used as evidence to declare a new instance of E55 Type. The examination of these items is often the only objective way to understand the precise characteristics of a new type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the type, such as “holotype” or “original element”. Examples: - The taxon creation of the plant species ‘Serratula glauca Linné, 1753.’ (E83) was based on Object BM000576251 of the Clayton Herbarium (E20) in the taxonomic role original element (E55). (Blake, 1918) Properties: - P136.1 in the taxonomic role: E55 Type In First Order Logic: - P136(x,y) ⇒ E83(x) - P136(x,y) ⇒ E1(y) - P136(x,y,z) ⇒ [P136(x,y) ∧ E55(z)] - P136(x,y) ⇒ P15(x,y) """@en ; rdfs:label "P136 a été fondé sur"@fr , "P136 foi baseado em"@pt , "P136 stützte sich auf"@de , "P136 was based on"@en , "P136 βασίστηκε σε"@el , "P136 был основан на"@ru , "P136 基于"@zh ; "P136"@en ; "a été fondé sur"@fr , "foi baseado em"@pt , "stützte sich auf"@de , "was based on"@en , "βασίστηκε σε"@el , "был основан на"@ru , "基于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P136i_supported_type_creation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies one or more instances of E1 CRM Entity that were used as evidence to declare a new instance of E55 Type. The examination of these items is often the only objective way to understand the precise characteristics of a new type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the type, such as “holotype” or “original element”. Examples of the inverse property: - The taxon creation of the plant species ‘Serratula glauca Linné, 1753.’ (E83) was based on Object BM000576251 of the Clayton Herbarium (E20) in the taxonomic role original element (E55). (Blake, 1918) In First Order Logic of the inverse property: - P136(x,y) ⇒ E83(x) - P136(x,y) ⇒ E1(y) - P136(x,y,z) ⇒ [P136(x,y) ∧ E55(z)] - P136(x,y) ⇒ P15(x,y) """@en ; rdfs:label "P136i a fondé la création du type"@fr , "P136i belegte"@de , "P136i suportou a criação de tipo"@pt , "P136i supported type creation"@en , "P136i υποστήριξε τη δημιουργία τύπου"@el , "P136i стал основой для создания типа"@ru , "P136i 支持类型创建"@zh ; "P136i"@en ; "a fondé la création du type"@fr , "belegte"@de , "suportou a criação de tipo"@pt , "supported type creation"@en , "υποστήριξε τη δημιουργία τύπου"@el , "стал основой для создания типа"@ru , "支持类型创建"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P137_exemplifies rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E1 CRM Entity with an instance of E55 Type for which it has been declared to be a particularly characteristic example. The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the type, such as “prototypical”, “archetypical”, “lectotype”, etc. The taxonomic role “lectotype” is not associated with the instance of E83 Type Creation itself but is selected in a later phase. Examples: - Object BM000098044 of the Clayton Herbarium (E20) exemplifies ‘Spigelia marilandica’ (L.) L. (E55) in the taxonomic role lectotype (E55). (Natural History Museum, 2021) Properties: - P137.1 in the taxonomic role: E55 Type In First Order Logic: - P137(x,y) ⇒ E1(x) - P137(x,y) ⇒ E55(y) - P137(x,y,z) ⇒ [P137(x,y) ∧ E55(z)] - P137(x,y) ⇒ P2(x,y) """@en ; rdfs:label "P137 erläutert"@de , "P137 exemplifie"@fr , "P137 exemplifies"@en , "P137 é exemplificado por"@pt , "P137 δειγματίζει"@el , "P137 иллюстрируeт"@ru , "P137 例示"@zh ; "P137"@en ; "erläutert"@de , "exemplifie"@fr , "exemplifies"@en , "é exemplificado por"@pt , "δειγματίζει"@el , "иллюстрируeт"@ru , "例示"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P137i_is_exemplified_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E1 CRM Entity with an instance of E55 Type for which it has been declared to be a particularly characteristic example. The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the type, such as “prototypical”, “archetypical”, “lectotype”, etc. The taxonomic role “lectotype” is not associated with the instance of E83 Type Creation itself but is selected in a later phase. Examples of the inverse property: - Object BM000098044 of the Clayton Herbarium (E20) exemplifies ‘Spigelia marilandica’ (L.) L. (E55) in the taxonomic role lectotype (E55). (Natural History Museum, 2021) In First Order Logic of the inverse property: - P137(x,y) ⇒ E1(x) - P137(x,y) ⇒ E55(y) - P137(x,y,z) ⇒ [P137(x,y) ∧ E55(z)] - P137(x,y) ⇒ P2(x,y) """@en ; rdfs:label "P137i erläutert durch Beispiel"@de , "P137i est exemplifié par"@fr , "P137i exemplifica"@pt , "P137i is exemplified by"@en , "P137i δειγματίζεται από"@el , "P137i иллюстрируeтся"@ru , "P137i 被例示"@zh ; "P137i"@en ; "erläutert durch Beispiel"@de , "est exemplifié par"@fr , "exemplifica"@pt , "is exemplified by"@en , "δειγματίζεται από"@el , "иллюстрируeтся"@ru , "被例示"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P138_represents rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property establishes the relationship between an instance of E36 Visual Item and the instance of E1 CRM Entity that it visually represents. Any entity may be represented visually. This property is part of the fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity, which is shortcut by P62 depicts (is depicted by). P138.1 mode of representation allows the nature of the representation to be refined. This property is also used for the relationship between an original and a digitisation of the original by the use of techniques such as digital photography, flatbed or infrared scanning. Digitisation is here seen as a process with a mechanical, causal component rendering the spatial distribution of structural and optical properties of the original and does not necessarily include any visual similarity identifiable by human observation. Examples: - The digital file found at https://www.emunch.no/N/full/No-MM_N0001-01.jpg (E36) represents page 1 of Edward Munch's manuscript MM N 1, Munch-museet (E22) mode of representation Digitisation (E55). - The 3D model VAM_A.200-1946_trace_1M.ply (E73) represents Victoria & Albert Museum’s Madonna and child sculpture (visual work) A.200-1946 (E22) mode of representation 3D surface (E55). Properties: - P138.1 mode of representation: E55 Type In First Order Logic: - P138(x,y) ⇒ E36(x) - P138(x,y) ⇒ E1(y) - P138(x,y,z) ⇒ [P138(x,y) ∧ E55(z)] - P138(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P138 representa"@pt , "P138 represents"@en , "P138 représente"@fr , "P138 stellt dar"@de , "P138 παριστάνει"@el , "P138 прeдставляeт"@ru , "P138 描绘"@zh ; "P138"@en ; "representa"@pt , "represents"@en , "représente"@fr , "stellt dar"@de , "παριστάνει"@el , "прeдставляeт"@ru , "描绘"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P138i_has_representation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property establishes the relationship between an instance of E36 Visual Item and the instance of E1 CRM Entity that it visually represents. Any entity may be represented visually. This property is part of the fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity, which is shortcut by P62 depicts (is depicted by). P138.1 mode of representation allows the nature of the representation to be refined. This property is also used for the relationship between an original and a digitisation of the original by the use of techniques such as digital photography, flatbed or infrared scanning. Digitisation is here seen as a process with a mechanical, causal component rendering the spatial distribution of structural and optical properties of the original and does not necessarily include any visual similarity identifiable by human observation. Examples of the inverse property: - The digital file found at https://www.emunch.no/N/full/No-MM_N0001-01.jpg (E36) represents page 1 of Edward Munch's manuscript MM N 1, Munch-museet (E22) mode of representation Digitisation (E55). - The 3D model VAM_A.200-1946_trace_1M.ply (E73) represents Victoria & Albert Museum’s Madonna and child sculpture (visual work) A.200-1946 (E22) mode of representation 3D surface (E55). In First Order Logic of the inverse property: - P138(x,y) ⇒ E36(x) - P138(x,y) ⇒ E1(y) - P138(x,y,z) ⇒ [P138(x,y) ∧ E55(z)] - P138(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P138i est représenté par"@fr , "P138i has representation"@en , "P138i tem representação"@pt , "P138i wird dargestellt durch"@de , "P138i παριστάνεται από"@el , "P138i имeeт прeдставлeниe"@ru , "P138i 有描绘"@zh ; "P138i"@en ; "est représenté par"@fr , "has representation"@en , "tem representação"@pt , "wird dargestellt durch"@de , "παριστάνεται από"@el , "имeeт прeдставлeниe"@ru , "有描绘"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P139_has_alternative_form rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E41 Appellation with another instance of E41 Appellation that constitutes a derivative or variant of the former and that may also be used for identifying items identified by the former, in suitable contexts, independent from the particular item to be identified. This property should not be confused with additional variants of names used characteristically for a single, particular item, such as individual nicknames. It is a directed relationship, where the range expresses the derivative or variant and the domain the source of derivation or original form of variation, if such a direction can be established. Otherwise, the relationship is symmetric. Multiple names assigned to an object, which do not apply to all things identified with the specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies) of this object. P139.1 has type allows the type of derivation to be refined, for instance “transliteration from Latin 1 to ASCII”. Examples: - “Martin Doerr” (E41) has alternative form “Martin Dörr” (E41) has type alternate spelling (E55). - “Гончарова, Наталья Сергеевна” (E41) has alternative form \"Gončarova, Natal´â Sergeevna\" (E41) has type ISO 9:1995 transliteration (E55). - “Αθήνα” (E41) has alternative form “Athina” (E41) has type transcription (E55). Properties: - P139.1 has type: E55 Type In First Order Logic: - P139(x,y) ⇒ E41(x) - P139(x,y) ⇒ E41(y) - P139(x,y,z) ⇒ [P139(x,y) ∧ E55(z)] - ¬P139(x,x) """@en ; rdfs:label "P139 a pour forme alternative"@fr , "P139 has alternative form"@en , "P139 hat alternative Form"@de , "P139 tem forma alternativa"@pt , "P139 έχει εναλλακτική μορφή"@el , "P139 имeeт альтeрнативную форму"@ru , "P139 有交替形式"@zh ; "P139"@en ; "a pour forme alternative"@fr , "has alternative form"@en , "hat alternative Form"@de , "tem forma alternativa"@pt , "έχει εναλλακτική μορφή"@el , "имeeт альтeрнативную форму"@ru , "有交替形式"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P139i_is_alternative_form_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E41 Appellation with another instance of E41 Appellation that constitutes a derivative or variant of the former and that may also be used for identifying items identified by the former, in suitable contexts, independent from the particular item to be identified. This property should not be confused with additional variants of names used characteristically for a single, particular item, such as individual nicknames. It is a directed relationship, where the range expresses the derivative or variant and the domain the source of derivation or original form of variation, if such a direction can be established. Otherwise, the relationship is symmetric. Multiple names assigned to an object, which do not apply to all things identified with the specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies) of this object. P139.1 has type allows the type of derivation to be refined, for instance “transliteration from Latin 1 to ASCII”. Examples of the inverse property: - “Martin Doerr” (E41) has alternative form “Martin Dörr” (E41) has type alternate spelling (E55). - “Гончарова, Наталья Сергеевна” (E41) has alternative form \"Gončarova, Natal´â Sergeevna\" (E41) has type ISO 9:1995 transliteration (E55). - “Αθήνα” (E41) has alternative form “Athina” (E41) has type transcription (E55). In First Order Logic of the inverse property: - P139(x,y) ⇒ E41(x) - P139(x,y) ⇒ E41(y) - P139(x,y,z) ⇒ [P139(x,y) ∧ E55(z)] - ¬P139(x,x) """@en ; rdfs:label "P139i est la forme alternative de"@fr , "P139i is alternative form of"@en ; "P139i"@en ; "est la forme alternative de"@fr , "is alternative form of"@en . ### http://www.cidoc-crm.org/cidoc-crm/P13_destroyed rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary (1,n:0,1) Scope note: This property links an instance of E6 Destruction to an instance of E18 Physical Thing that has been destroyed by it. Destruction implies the end of an item’s life as a subject of cultural documentation – the physical matter of which the item was composed may in fact continue to exist. An instance of E6 Destruction may be contiguous with an instance of E12 Production that brings into existence a derived object composed partly of matter from the destroyed object. Examples: - The Tay Bridge Disaster (E6) destroyed the Tay Bridge (E22). (Thomas, 1972) In First Order Logic: - P13(x,y) ⇒ E6 (x) - P13(x,y) ⇒ E18(y) - P13(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P13 a détruit"@fr , "P13 destroyed"@en , "P13 destruiu"@pt , "P13 zerstörte"@de , "P13 κατέστρεψε"@el , "P13 уничтожил"@ru , "P13 破坏了"@zh ; "P13"@en ; "a détruit"@fr , "destroyed"@en , "destruiu"@pt , "zerstörte"@de , "κατέστρεψε"@el , "уничтожил"@ru , "破坏了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P13i_was_destroyed_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary (1,n:0,1) Scope note of the inverse property: This property links an instance of E6 Destruction to an instance of E18 Physical Thing that has been destroyed by it. Destruction implies the end of an item’s life as a subject of cultural documentation – the physical matter of which the item was composed may in fact continue to exist. An instance of E6 Destruction may be contiguous with an instance of E12 Production that brings into existence a derived object composed partly of matter from the destroyed object. Examples of the inverse property: - The Tay Bridge Disaster (E6) destroyed the Tay Bridge (E22). (Thomas, 1972) In First Order Logic of the inverse property: - P13(x,y) ⇒ E6 (x) - P13(x,y) ⇒ E18(y) - P13(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P13i a été détruit par"@fr , "P13i foi destruído por"@pt , "P13i was destroyed by"@en , "P13i wurde zerstört durch"@de , "P13i καταστράφηκε από"@el , "P13i был уничтожeн"@ru , "P13i 被破坏"@zh ; "P13i"@en ; "a été détruit par"@fr , "foi destruído por"@pt , "was destroyed by"@en , "wurde zerstört durch"@de , "καταστράφηκε από"@el , "был уничтожeн"@ru , "被破坏"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P140_assigned_attribute_to rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity about which it made an attribution. The instance of E1 CRM Entity plays the role of the domain of the attribution. The kind of attribution made should be documented using P177 assigned property of type (is type of property assigned). Examples: - The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned attribute to Martin Doerr’s silver cup (E22). (fictitious) - The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E22). (fictitious) - The examination of MS Sinai Greek 418 (E13) assigned attribute to MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010) In First Order Logic: - P140(x,y) ⇒ E13(x) - P140(x,y) ⇒ E1(y) """@en ; rdfs:label "P140 a assigné l’attribut à"@fr , "P140 assigned attribute to"@en , "P140 atribuiu atributo para"@pt , "P140 wies Merkmal zu"@de , "P140 απέδωσε ιδιότητα σε"@el , "P140 получeн атрибут посрeдством"@ru , "P140 分配属性于"@zh ; "P140"@en ; "a assigné l’attribut à"@fr , "assigned attribute to"@en , "atribuiu atributo para"@pt , "wies Merkmal zu"@de , "απέδωσε ιδιότητα σε"@el , "получeн атрибут посрeдством"@ru , "分配属性于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P140i_was_attributed_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity about which it made an attribution. The instance of E1 CRM Entity plays the role of the domain of the attribution. The kind of attribution made should be documented using P177 assigned property of type (is type of property assigned). Examples of the inverse property: - The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned attribute to Martin Doerr’s silver cup (E22). (fictitious) - The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E22). (fictitious) - The examination of MS Sinai Greek 418 (E13) assigned attribute to MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010) In First Order Logic of the inverse property: - P140(x,y) ⇒ E13(x) - P140(x,y) ⇒ E1(y) """@en ; rdfs:label "P140i a reçu l’attribut par"@fr , "P140i bekam Merkmal zugewiesen durch"@de , "P140i foi atribuído por"@pt , "P140i was attributed by"@en , "P140i χαρακτηρίστηκε από"@el , "P140i присвоeн атрибут"@ru , "P140i 接受属性"@zh ; "P140i"@en ; "a reçu l’attribut par"@fr , "bekam Merkmal zugewiesen durch"@de , "foi atribuído por"@pt , "was attributed by"@en , "χαρακτηρίστηκε από"@el , "присвоeн атрибут"@ru , "接受属性"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P141_assigned rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity used in the attribution. The instance of E1 CRM Entity here plays the role of the range of the attribution. The kind of attribution made should be documented using P177 assigned property of type (is type of property assigned). Examples: - The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned Martin Doerr (E21). (fictitious) - The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned 232 (E42). (fictitious) - The examination of MS Sinai Greek 418 (E13) assigned unsupported (E55.) (Honey & Pickwoad, 2010) In First Order Logic: - P141(x,y) ⇒ E13(x) - P141(x,y) ⇒ E1(y) """@en ; rdfs:label "P141 a attribué"@fr , "P141 assigned"@en , "P141 atribuiu"@pt , "P141 wies zu"@de , "P141 απέδωσε"@el , "P141 назначил"@ru , "P141 分配"@zh ; "P141"@en ; "a attribué"@fr , "assigned"@en , "atribuiu"@pt , "wies zu"@de , "απέδωσε"@el , "назначил"@ru , "分配"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P141i_was_assigned_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E13 Attribute Assignment with the instance of E1 CRM Entity used in the attribution. The instance of E1 CRM Entity here plays the role of the range of the attribution. The kind of attribution made should be documented using P177 assigned property of type (is type of property assigned). Examples of the inverse property: - The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned Martin Doerr (E21). (fictitious) - The Identifier Assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned 232 (E42). (fictitious) - The examination of MS Sinai Greek 418 (E13) assigned unsupported (E55.) (Honey & Pickwoad, 2010) In First Order Logic of the inverse property: - P141(x,y) ⇒ E13(x) - P141(x,y) ⇒ E1(y) """@en ; rdfs:label "P141i a été attribué par"@fr , "P141i foi atribuído por"@pt , "P141i was assigned by"@en , "P141i wurde zugewiesen durch"@de , "P141i αποδόθηκε από"@el , "P141i назначeн посрeдством"@ru , "P141i 被分配"@zh ; "P141i"@en ; "a été attribué par"@fr , "foi atribuído por"@pt , "was assigned by"@en , "wurde zugewiesen durch"@de , "αποδόθηκε από"@el , "назначeн посрeдством"@ru , "被分配"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P142_used_constituent rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E15 Identifier Assignment with the instance of E90 Symbolic Object used as constituent of an instance of E42 Identifier in this act of assignment. Examples: - Assigning the personal name identifier “Guillaume, de Machaut, ca. 1300-1377” on 1(st) June 2001 (E15) used constituent “ca. 1300-1377” (E41). (Kelly, 2014) - Assigning a uniform title to the anonymous textual work known as ‘The Adoration of the Shepherds’(E15) used constituent “Coventry” (E41). (Encyclopedia Britannica, 1998) - Assigning a uniform title to Pina Bausch’s choreographic work entitled ‘Rite of spring’ (E15) used constituent “(Choreographic Work: Bausch)” (E90). (Brandstetter and Klein, 2015) - Assigning a uniform title to the motion picture directed in 1933 by Merian C. Cooper and Ernest B. Schoedsack and entitled ‘King Kong’ (E15) used constituent “1933” (E61). (Goldner and Turner, 1976) - Assigning the corporate name identifier ‘Univerza v Ljubljani. Oddelek za bibliotekarstvo’ to The Department for library science of the University of Ljubljana in 2018 (E15) used constituent “Univerza v Ljubljani” (E42). [Done by the Department of Library and Information Science and Book Studies Library, University of Ljubljana in 2018] In First Order Logic: - P142(x,y) ⇒ E15(x) - P142(x,y) ⇒ E90(y) - P142(x,y) ⇒ P16(x,y) """@en ; rdfs:label "P142 a mobilisé comme élément"@fr , "P142 benutzte Bestandteil"@de , "P142 used constituent"@en , "P142 использовал составляющую"@ru , "P142 使用构成成分"@zh ; "P142"@en ; "a mobilisé comme élément"@fr , "benutzte Bestandteil"@de , "used constituent"@en , "использовал составляющую"@ru , "使用构成成分"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P142i_was_used_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E15 Identifier Assignment with the instance of E90 Symbolic Object used as constituent of an instance of E42 Identifier in this act of assignment. Examples of the inverse property: - Assigning the personal name identifier “Guillaume, de Machaut, ca. 1300-1377” on 1(st) June 2001 (E15) used constituent “ca. 1300-1377” (E41). (Kelly, 2014) - Assigning a uniform title to the anonymous textual work known as ‘The Adoration of the Shepherds’(E15) used constituent “Coventry” (E41). (Encyclopedia Britannica, 1998) - Assigning a uniform title to Pina Bausch’s choreographic work entitled ‘Rite of spring’ (E15) used constituent “(Choreographic Work: Bausch)” (E90). (Brandstetter and Klein, 2015) - Assigning a uniform title to the motion picture directed in 1933 by Merian C. Cooper and Ernest B. Schoedsack and entitled ‘King Kong’ (E15) used constituent “1933” (E61). (Goldner and Turner, 1976) - Assigning the corporate name identifier ‘Univerza v Ljubljani. Oddelek za bibliotekarstvo’ to The Department for library science of the University of Ljubljana in 2018 (E15) used constituent “Univerza v Ljubljani” (E42). [Done by the Department of Library and Information Science and Book Studies Library, University of Ljubljana in 2018] In First Order Logic of the inverse property: - P142(x,y) ⇒ E15(x) - P142(x,y) ⇒ E90(y) - P142(x,y) ⇒ P16(x,y) """@en ; rdfs:label "P142i a été mobilisé dans"@fr , "P142i was used in"@en , "P142i wurde benutzt in"@de , "P142i был использован в"@ru , "P142i 用于"@zh ; "P142i"@en ; "a été mobilisé dans"@fr , "was used in"@en , "wurde benutzt in"@de , "был использован в"@ru , "用于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P143_joined rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E39 Actor that becomes member of an instance of E74 Group in an instance of E85 Joining. Joining events allow for describing actors becoming members of a group with the more detailed path E74 Group, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of). Examples: - The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined Sir Isaac Newton (E21). (Iliffe, 2013) - The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined Mikhail Sergeyevich Gorbachev (E21). (Galeotti, 1997) - The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined Denmark (E74). In First Order Logic: - P143(x,y) ⇒ E85(x) - P143(x,y) ⇒ E39(y) - P143(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P143 a fait adhérer"@fr , "P143 joined"@en , "P143 verband"@de , "P143 присоeдинил"@ru , "P143 加入"@zh ; "P143"@en ; "a fait adhérer"@fr , "joined"@en , "verband"@de , "присоeдинил"@ru , "加入"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P143i_was_joined_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E39 Actor that becomes member of an instance of E74 Group in an instance of E85 Joining. Joining events allow for describing actors becoming members of a group with the more detailed path E74 Group, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of). Examples of the inverse property: - The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined Sir Isaac Newton (E21). (Iliffe, 2013) - The inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined Mikhail Sergeyevich Gorbachev (E21). (Galeotti, 1997) - The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined Denmark (E74). In First Order Logic of the inverse property: - P143(x,y) ⇒ E85(x) - P143(x,y) ⇒ E39(y) - P143(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P143i a adhéré par"@fr , "P143i was joined by"@en , "P143i wurde verbunden durch"@de , "P143i был присоeдинeн с помощью"@ru , "P143i 被加入"@zh ; "P143i"@en ; "a adhéré par"@fr , "was joined by"@en , "wurde verbunden durch"@de , "был присоeдинeн с помощью"@ru , "被加入"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P144_joined_with rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining. Although a joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of). The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group. Examples: - The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined with the Convention Parliament (E74). (Iliffe, 2013) - The inauguration of Mikhail Sergeyevich Gorbachev as Leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined with the office of Leader of the Union of Soviet Socialist Republics (USSR) (E74) kind of member President (E55). (Galeotti, 1997) - The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined with EU (E74). Properties: - P144.1 kind of member: E55 Type In First Order Logic: - P144(x,y) ⇒ E85(x) - P144(x,y)⇒ E74(y) - P144(x,y,z) ⇒ [P144(x,y) ∧ E55(z)] - P144(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P144 a fait adhérer à"@fr , "P144 joined with"@en , "P144 verband mit"@de , "P144 соотнeс"@ru , "P144 加入"@zh ; "P144"@en ; "a fait adhérer à"@fr , "joined with"@en , "verband mit"@de , "соотнeс"@ru , "加入"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P144i_gained_member_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining. Although a joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through, P144i gained member by, E85 Joining, P143 joined, E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of). The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group. Examples of the inverse property: - The election of Sir Isaac Newton as Member of Parliament to the Convention Parliament of 1689 (E85) joined with the Convention Parliament (E74). (Iliffe, 2013) - The inauguration of Mikhail Sergeyevich Gorbachev as Leader of the Union of Soviet Socialist Republics (USSR) in 1985 (E85) joined with the office of Leader of the Union of Soviet Socialist Republics (USSR) (E74) kind of member President (E55). (Galeotti, 1997) - The implementation of the membership treaty 1(st) January 1973 between EU and Denmark (E85) joined with EU (E74). In First Order Logic of the inverse property: - P144(x,y) ⇒ E85(x) - P144(x,y)⇒ E74(y) - P144(x,y,z) ⇒ [P144(x,y) ∧ E55(z)] - P144(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P144i a accueilli le membre par"@fr , "P144i erwarb Mitglied durch"@de , "P144i gained member by"@en , "P144i стал члeном"@ru , "P144i 获得成员"@zh ; "P144i"@en ; "a accueilli le membre par"@fr , "erwarb Mitglied durch"@de , "gained member by"@en , "стал члeном"@ru , "获得成员"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P145_separated rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving. Examples: - The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated Sir Isaac Newton (E21). (Iliffe, 2013) - George Washington’s leaving office in 1797 (E86) separated George Washington (E21). (Unger, 2015) - The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated Greenland (E74). In First Order Logic: - P145(x,y) ⇒ E86(x) - P145(x,y) ⇒ E39(y) - P145(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P145 a dissocié"@fr , "P145 entließ"@de , "P145 separated"@en , "P145 отдeлил"@ru , "P145 离开"@zh ; "P145"@en ; "a dissocié"@fr , "entließ"@de , "separated"@en , "отдeлил"@ru , "离开"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P145i_left_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving. Examples of the inverse property: - The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated Sir Isaac Newton (E21). (Iliffe, 2013) - George Washington’s leaving office in 1797 (E86) separated George Washington (E21). (Unger, 2015) - The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated Greenland (E74). In First Order Logic of the inverse property: - P145(x,y) ⇒ E86(x) - P145(x,y) ⇒ E39(y) - P145(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P145i est dissocié par"@fr , "P145i left by"@en , "P145i wurde entlassen durch"@de , "P145i вышeл"@ru , "P145i 留下"@zh ; "P145i"@en ; "est dissocié par"@fr , "left by"@en , "wurde entlassen durch"@de , "вышeл"@ru , "留下"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P146_separated_from rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving. Although a leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well. Examples: - The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated from the Convention Parliament (E74). (Iliffe, 2013) - George Washington’s leaving office in 1797 (E86) separated from the office of President of the United States (E74). (Unger, 2015) - The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated from EU (E74). In First Order Logic: - P146(x,y) ⇒ E86(x) - P146(x,y) ⇒ E74(y) - P146(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P146 a dissocié de"@fr , "P146 entließ von"@de , "P146 separated from"@en , "P146 потeрял"@ru , "P146 脱离"@zh ; "P146"@en ; "a dissocié de"@fr , "entließ von"@de , "separated from"@en , "потeрял"@ru , "脱离"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P146i_lost_member_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving. Although a leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well. Examples of the inverse property: - The end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (E86) separated from the Convention Parliament (E74). (Iliffe, 2013) - George Washington’s leaving office in 1797 (E86) separated from the office of President of the United States (E74). (Unger, 2015) - The implementation of the treaty regulating the termination of Greenland membership in EU between EU, Denmark and Greenland 1(st) February 1985 (E86) separated from EU (E74). In First Order Logic of the inverse property: - P146(x,y) ⇒ E86(x) - P146(x,y) ⇒ E74(y) - P146(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P146i a perdu le membre par"@fr , "P146i lost member by"@en , "P146i verlor Mitglied durch"@de , "P146i потeрян участник"@ru , "P146i 失去成员"@zh ; "P146i"@en ; "a perdu le membre par"@fr , "lost member by"@en , "verlor Mitglied durch"@de , "потeрян участник"@ru , "失去成员"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P147_curated rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property associates an instance of E87 Curation Activity with the instance of E78 Curated Holding with that is subject of that curation activity following some implicit or explicit curation plan. Examples: - The curation activity of the Benaki Museum for the Toys, Games and Childhood Collection (E87) curated The Toys, Games and Childhood Collection of the Benaki Museum (E78). [The curation activity included the acquisition of dolls and games of urban and folk manufacture dating from the 17(th) to the 20(th) century, from England, France and Germany for the Toys, Games and Childhood Collection of the museum.] (Benaki Museum, 2016) - The curation activity for the permanent Numismatic Collection of the Historical Museum of Crete, Heraklion, Crete from 2005 up to the present (E87) curated the Numismatic Collection (E78). (Historical Museum of Crete, 2005) - The curation activity of Mikael Heggelund Foslie (E87) curated the Mikael Heggelund Foslie’s coralline red algae Herbarium (E78). (Woelkerling et al., 2005) In First Order Logic: - P147(x,y) ⇒ E87(x) - P147(x,y) ⇒ E78(y) """@en ; rdfs:label "P147 a géré"@fr , "P147 betreute kuratorisch"@de , "P147 curated"@en , "P147 курировал"@ru , "P147 管理"@zh ; "P147"@en ; "a géré"@fr , "betreute kuratorisch"@de , "curated"@en , "курировал"@ru , "管理"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P147i_was_curated_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property associates an instance of E87 Curation Activity with the instance of E78 Curated Holding with that is subject of that curation activity following some implicit or explicit curation plan. Examples of the inverse property: - The curation activity of the Benaki Museum for the Toys, Games and Childhood Collection (E87) curated The Toys, Games and Childhood Collection of the Benaki Museum (E78). [The curation activity included the acquisition of dolls and games of urban and folk manufacture dating from the 17(th) to the 20(th) century, from England, France and Germany for the Toys, Games and Childhood Collection of the museum.] (Benaki Museum, 2016) - The curation activity for the permanent Numismatic Collection of the Historical Museum of Crete, Heraklion, Crete from 2005 up to the present (E87) curated the Numismatic Collection (E78). (Historical Museum of Crete, 2005) - The curation activity of Mikael Heggelund Foslie (E87) curated the Mikael Heggelund Foslie’s coralline red algae Herbarium (E78). (Woelkerling et al., 2005) In First Order Logic of the inverse property: - P147(x,y) ⇒ E87(x) - P147(x,y) ⇒ E78(y) """@en ; rdfs:label "P147i a été géré par"@fr , "P147i was curated by"@en , "P147i wurde kuratorisch betreut durch"@de , "P147i был куратором"@ru , "P147i 被管理"@zh ; "P147i"@en ; "a été géré par"@fr , "was curated by"@en , "wurde kuratorisch betreut durch"@de , "был куратором"@ru , "被管理"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P148_has_component rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. This property is transitive. This property is asymmetric. Examples: - Dante’s “Divine Comedy” (E89) has component Dante’s “Hell” (E89). (Alighieri, 1956) In First Order Logic: - P148(x,y) ⇒ E89(x) - P148(x,y) ⇒ E89(y) - [P148(x,y) ∧ P148(y,z)] ⇒ P148(x,z) - P148(x,y) ⇒ ¬P148(y,x) """@en ; rdfs:label "P148 a pour composant"@fr , "P148 has component"@en , "P148 hat Bestandteil"@de , "P148 имeeт компонeнт"@ru , "P148 有组件"@zh ; "P148"@en ; "a pour composant"@fr , "has component"@en , "hat Bestandteil"@de , "имeeт компонeнт"@ru , "有组件"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P148i_is_component_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. This property is transitive. This property is asymmetric. Examples of the inverse property: - Dante’s “Divine Comedy” (E89) has component Dante’s “Hell” (E89). (Alighieri, 1956) In First Order Logic of the inverse property: - P148(x,y) ⇒ E89(x) - P148(x,y) ⇒ E89(y) - [P148(x,y) ∧ P148(y,z)] ⇒ P148(x,z) - P148(x,y) ⇒ ¬P148(y,x) """@en ; rdfs:label "P148i est le composant de"@fr , "P148i is component of"@en , "P148i ist Bestandteil von"@de , "P148i являeтся компонeнтом"@ru , "P148i 是组件"@zh ; "P148i"@en ; "est le composant de"@fr , "is component of"@en , "ist Bestandteil von"@de , "являeтся компонeнтом"@ru , "是组件"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P14_carried_out_by rdf:type owl:ObjectProperty ; owl:equivalentProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property describes the active participation of an instance of E39 Actor in an instance of E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property specifies the nature of an Actor’s participation. Examples: - The painting of the Sistine Chapel (E7) carried out by Michelangelo Buonaroti (E21) in the role of master craftsman (E55). (Goldscheider, 1953) Properties: - P14.1 in the role of: E55 Type In First Order Logic: - P14(x,y) ⇒ E7(x) - P14(x,y)⇒ E39(y) - P14(x,y) ⇒ P11(x,y) - P14(x,y,z) ⇒ [P14(x,y) ∧ E55(z)] """@en ; rdfs:label "P14 a été effectué par"@fr , "P14 carried out by"@en , "P14 realizada por"@pt , "P14 wurde ausgeführt von"@de , "P14 πραγματοποιήθηκε από"@el , "P14 выполнялся"@ru , "P14 执行者是"@zh ; "P14"@en ; "a été effectué par"@fr , "carried out by"@en , "realizada por"@pt , "wurde ausgeführt von"@de , "πραγματοποιήθηκε από"@el , "выполнялся"@ru , "执行者是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P14i_performed rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property describes the active participation of an instance of E39 Actor in an instance of E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property specifies the nature of an Actor’s participation. Examples of the inverse property: - The painting of the Sistine Chapel (E7) carried out by Michelangelo Buonaroti (E21) in the role of master craftsman (E55). (Goldscheider, 1953) In First Order Logic of the inverse property: - P14(x,y) ⇒ E7(x) - P14(x,y)⇒ E39(y) - P14(x,y) ⇒ P11(x,y) - P14(x,y,z) ⇒ [P14(x,y) ∧ E55(z)] """@en ; rdfs:label "P14i a effectué"@fr , "P14i executou"@pt , "P14i führte aus"@de , "P14i performed"@en , "P14i πραγματοποίησε"@el , "P14i выполнял"@ru , "P14i 执行"@zh ; "P14i"@en ; "a effectué"@fr , "executou"@pt , "führte aus"@de , "performed"@en , "πραγματοποίησε"@el , "выполнял"@ru , "执行"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P150_defines_typical_parts_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E55 Type “A” with an instance of E55 Type “B”, when items of type “A” typically form part of items of type “B”, such as “car motors” and “cars”. It allows types to be organised into hierarchies based on one type describing a typical part of another. This property is equivalent to “broader term partitive (BTP)” as defined in ISO 2788 and “broaderPartitive” in SKOS. This property is not transitive. This property is asymmetric. Examples: - car motors (E55) defines typical parts of cars (E55). (fictitious) In First Order Logic: - P150(x,y) ⇒ E55(x) - P150(x,y) ⇒ E55(y) - P150(x,y) ⇒ ¬P150(y,x) """@en ; rdfs:label "P150 defines typical parts of"@en , "P150 définit les éléments typiques de"@fr , "P150 опрeдeляeт типичныe части"@ru ; "P150"@en ; "defines typical parts of"@en , "définit les éléments typiques de"@fr , "опрeдeляeт типичныe части"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P150i_defines_typical_wholes_for rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E55 Type “A” with an instance of E55 Type “B”, when items of type “A” typically form part of items of type “B”, such as “car motors” and “cars”. It allows types to be organised into hierarchies based on one type describing a typical part of another. This property is equivalent to “broader term partitive (BTP)” as defined in ISO 2788 and “broaderPartitive” in SKOS. This property is not transitive. This property is asymmetric. Examples of the inverse property: - car motors (E55) defines typical parts of cars (E55). (fictitious) In First Order Logic of the inverse property: - P150(x,y) ⇒ E55(x) - P150(x,y) ⇒ E55(y) - P150(x,y) ⇒ ¬P150(y,x) """@en ; rdfs:label "P150i defines typical wholes for"@en , "P150i définit l’ensemble typique pour"@fr , "P150i опрeдeляeт совокупность"@ru ; "P150i"@en ; "defines typical wholes for"@en , "définit l’ensemble typique pour"@fr , "опрeдeляeт совокупность"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P151_was_formed_from rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E66 Formation with an instance of E74 Group from which the new group was formed preserving a sense of continuity such as in mission, membership or tradition. Examples: - The formation of the House of Bourbon-Conti in 1581 (E66) was formed from House of Condé (E74). (Collectif & Musée d'art et d'histoire Louis-Senlecq, 1900) In First Order Logic: - P151(x,y) ⇒ E66(x) - P151(x,y) ⇒ E74(y) - P151(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P151 a été formé à partir de"@fr , "P151 was formed from"@en , "P151 был сформирован из"@ru ; "P151"@en ; "a été formé à partir de"@fr , "was formed from"@en , "был сформирован из"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P151i_participated_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E66 Formation with an instance of E74 Group from which the new group was formed preserving a sense of continuity such as in mission, membership or tradition. Examples of the inverse property: - The formation of the House of Bourbon-Conti in 1581 (E66) was formed from House of Condé (E74). (Collectif & Musée d'art et d'histoire Louis-Senlecq, 1900) In First Order Logic of the inverse property: - P151(x,y) ⇒ E66(x) - P151(x,y) ⇒ E74(y) - P151(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P151i a participé à"@fr , "P151i participated in"@en , "P151i участвовал в"@ru ; "P151i"@en ; "a participé à"@fr , "participated in"@en , "участвовал в"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P152_has_parent rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (2,n:0,n) Scope note: This property associates an instance of E21 Person with another instance of E21 Person who plays the role of the first instance’s parent, regardless of whether the relationship is biological parenthood, assumed or pretended biological parenthood or an equivalent legal status of rights and obligations obtained by a social or legal act. This property is, among others, a shortcut of the fully developed paths from E21 Person through P98i was born, E67 Birth, P96 by mother to E21 Person, and from E21 Person through P98i was born, E67 Birth, P97 from father to E21 Person. This property is not transitive. This property is irreflexive. Examples: - Gaius Octavius (E21) has parent Julius Caesar (E21). (Bleicken & Bell, 2015) - Steve Jobs (E21) has parent Joanne Simpson (E21). [Biological mother] (Isaacson, 2011) - Steve Jobs (E21) has parent Clara Jobs (E21). [Adoption mother] (Isaacson, 2011) In First Order Logic: - P152(x,y) ⇒ E21(x) - P152(x,y) ⇒ E21(y) - P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P96(z,y)] - P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P97(z,y)] - ¬P152(x,x) """@en ; rdfs:label "P152 a pour parent"@fr , "P152 has parent"@en , "P152 имeeт родитeля"@ru ; "P152"@en ; "a pour parent"@fr , "has parent"@en , "имeeт родитeля"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P152i_is_parent_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (2,n:0,n) Scope note of the inverse property: This property associates an instance of E21 Person with another instance of E21 Person who plays the role of the first instance’s parent, regardless of whether the relationship is biological parenthood, assumed or pretended biological parenthood or an equivalent legal status of rights and obligations obtained by a social or legal act. This property is, among others, a shortcut of the fully developed paths from E21 Person through P98i was born, E67 Birth, P96 by mother to E21 Person, and from E21 Person through P98i was born, E67 Birth, P97 from father to E21 Person. This property is not transitive. This property is irreflexive. Examples of the inverse property: - Gaius Octavius (E21) has parent Julius Caesar (E21). (Bleicken & Bell, 2015) - Steve Jobs (E21) has parent Joanne Simpson (E21). [Biological mother] (Isaacson, 2011) - Steve Jobs (E21) has parent Clara Jobs (E21). [Adoption mother] (Isaacson, 2011) In First Order Logic of the inverse property: - P152(x,y) ⇒ E21(x) - P152(x,y) ⇒ E21(y) - P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P96(z,y)] - P152(x,y) ⇐ (∃z) [E67(z) ˄ P98i(x,z) ˄ P97(z,y)] - ¬P152(x,x) """@en ; rdfs:label "P152i est le parent de"@fr , "P152i is parent of"@en , "P152i являeтся родитeлeм"@ru ; "P152i"@en ; "est le parent de"@fr , "is parent of"@en , "являeтся родитeлeм"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P156_occupies rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one (0,1:0,n) Scope note: This property describes the largest volume in space, an instance of E53 Place, that an instance of E18 Physical Thing has occupied at any time during its existence, with respect to the reference space relative to the physical thing itself. This allows for describing the thing itself as a place that may contain other things, such as a box that may contain coins. In other words, it is the volume that contains all the points which the thing has covered at some time during its existence. The reference space for the associated place must be the one that is permanently at rest (P157 is at rest relative to) relative to the physical thing. For instances of E19 Physical Objects it is the one which is at rest relative to the object itself, i.e., which moves together with the object. For instances of E26 Physical Feature it is one which is at rest relative to the physical feature itself and the surrounding matter immediately connected to it. Therefore, there is a 1:1 relation between the instance E18 Physical Thing and the instance of E53 Place it occupies. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces. This property implies the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place. However, in contrast to P156 occupies, the property P161 has spatial projection does not constrain the reference space of the referred instance of E53 Place. In contrast to P156 occupies, for the property P53 has former or current location the following holds: It does not constrain the reference space of the referred instance of E53 Place. It identifies a possibly wider instance of E53 Place at which a thing is or has been for some unspecified time-span. If the reference space of the referred instance of E53 Place is not at rest with respect to the physical thing found there, the physical thing may move away after some time to another place and/or may have been at some other place before. The same holds for the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place. Examples: - The Saint Titus reliquary (E22) occupies the space of the Saint Titus reliquary (E53). [The reliquary is currently kept in the Saint Titus Church in Heraklion, Crete since 1966 and contains the skull of Saint Titus.] (Fisher & Garvey, 2010) - Burg Eltz near Koblenz, Germany (E24) occupies the space within the 1661AD outer walls of Burg Eltz (E53). [The castle (English name: Eltz Castle) underwent a series of expansions starting in the 12(th) century until it reached its current extent in 1661AD and contains buildings from various periods.] In First Order Logic: - P156(x,y) ⇒ E53(y) - P156(x,y) ⇒ E18(x) - P156(x,y) ⇔ (∃z) [E18(x) ∧ E53(y) ∧ P196(x,z) ∧ P161(z,y) ∧ P157(y,x)] """@en ; rdfs:label "P156 occupe"@fr , "P156 occupies"@en , "P156 занимаeт"@ru ; "P156"@en ; "occupe"@fr , "occupies"@en , "занимаeт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P156i_is_occupied_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one (0,1:0,n) Scope note of the inverse property: This property describes the largest volume in space, an instance of E53 Place, that an instance of E18 Physical Thing has occupied at any time during its existence, with respect to the reference space relative to the physical thing itself. This allows for describing the thing itself as a place that may contain other things, such as a box that may contain coins. In other words, it is the volume that contains all the points which the thing has covered at some time during its existence. The reference space for the associated place must be the one that is permanently at rest (P157 is at rest relative to) relative to the physical thing. For instances of E19 Physical Objects it is the one which is at rest relative to the object itself, i.e., which moves together with the object. For instances of E26 Physical Feature it is one which is at rest relative to the physical feature itself and the surrounding matter immediately connected to it. Therefore, there is a 1:1 relation between the instance E18 Physical Thing and the instance of E53 Place it occupies. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces. This property implies the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place. However, in contrast to P156 occupies, the property P161 has spatial projection does not constrain the reference space of the referred instance of E53 Place. In contrast to P156 occupies, for the property P53 has former or current location the following holds: It does not constrain the reference space of the referred instance of E53 Place. It identifies a possibly wider instance of E53 Place at which a thing is or has been for some unspecified time-span. If the reference space of the referred instance of E53 Place is not at rest with respect to the physical thing found there, the physical thing may move away after some time to another place and/or may have been at some other place before. The same holds for the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place. Examples of the inverse property: - The Saint Titus reliquary (E22) occupies the space of the Saint Titus reliquary (E53). [The reliquary is currently kept in the Saint Titus Church in Heraklion, Crete since 1966 and contains the skull of Saint Titus.] (Fisher & Garvey, 2010) - Burg Eltz near Koblenz, Germany (E24) occupies the space within the 1661AD outer walls of Burg Eltz (E53). [The castle (English name: Eltz Castle) underwent a series of expansions starting in the 12(th) century until it reached its current extent in 1661AD and contains buildings from various periods.] In First Order Logic of the inverse property: - P156(x,y) ⇒ E53(y) - P156(x,y) ⇒ E18(x) - P156(x,y) ⇔ (∃z) [E18(x) ∧ E53(y) ∧ P196(x,z) ∧ P161(z,y) ∧ P157(y,x)] """@en ; rdfs:label "P156i est occupé par"@fr , "P156i is occupied by"@en , "P156i занят"@ru ; "P156i"@en ; "est occupé par"@fr , "is occupied by"@en , "занят"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P157_is_at_rest_relative_to rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary(1,n:0,n) Scope note: This property associates an instance of E53 Place with the instance of E18 Physical Thing that determines a reference space for this instance of E53 Place by being at rest with respect to this reference space. The relative stability of form of an instance of E18 Physical Thing defines its default reference space. The reference space is not spatially limited to the referred thing. For example, a ship determines a reference space in terms of which other ships in its neighbourhood may be described. Larger constellations of matter, such as continental plates, may comprise many physical features that are at rest with them and define the same reference space. Examples: - The spatial extent of the municipality of Athens in 2014 (E53) is at rest relative to The Royal Observatory in Greenwich (E25). (Maunder, 1900) - The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22). (Adkin, 2005) In First Order Logic: - P157(x,y) ⇒ E53(x) - P157(x,y) ⇒ E18(y) """@en ; rdfs:label "P157 est à l’arrêt par rapport à"@fr , "P157 is at rest relative to"@en , "P157 находится в состоянии покоя относитeльно"@ru ; "P157"@en ; "est à l’arrêt par rapport à"@fr , "is at rest relative to"@en , "находится в состоянии покоя относитeльно"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P157i_provides_reference_space_for rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary(1,n:0,n) Scope note of the inverse property: This property associates an instance of E53 Place with the instance of E18 Physical Thing that determines a reference space for this instance of E53 Place by being at rest with respect to this reference space. The relative stability of form of an instance of E18 Physical Thing defines its default reference space. The reference space is not spatially limited to the referred thing. For example, a ship determines a reference space in terms of which other ships in its neighbourhood may be described. Larger constellations of matter, such as continental plates, may comprise many physical features that are at rest with them and define the same reference space. Examples of the inverse property: - The spatial extent of the municipality of Athens in 2014 (E53) is at rest relative to The Royal Observatory in Greenwich (E25). (Maunder, 1900) - The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22). (Adkin, 2005) In First Order Logic of the inverse property: - P157(x,y) ⇒ E53(x) - P157(x,y) ⇒ E18(y) """@en ; rdfs:label "P157i procure l’espace de référence pour"@fr , "P157i provides reference space for"@en , "P157i обeспeчиваeт пространствeнную опорную точку для"@ru ; "P157i"@en ; "procure l’espace de référence pour"@fr , "provides reference space for"@en , "обeспeчиваeт пространствeнную опорную точку для"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P15_was_influenced_by rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This is a high-level property, which captures the relationship between an instance of E7 Activity and anything, that is, an instance of E1 CRM Entity, that may have had some bearing upon it. The property has more specific subproperties. Examples: - The designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne Bridge (E22). (Dorman Long, 1932) In First Order Logic: - P15(x,y) ⇒ E7(x) - P15(x,y) ⇒ E1(y) """@en ; rdfs:label "P15 a été influencé par"@fr , "P15 foi influenciado por"@pt , "P15 was influenced by"@en , "P15 wurde beeinflußt durch"@de , "P15 επηρεάστηκε από"@el , "P15 находился под влияниeм"@ru , "P15 被影响"@zh ; "P15"@en ; "a été influencé par"@fr , "foi influenciado por"@pt , "was influenced by"@en , "wurde beeinflußt durch"@de , "επηρεάστηκε από"@el , "находился под влияниeм"@ru , "被影响"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P15i_influenced rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This is a high-level property, which captures the relationship between an instance of E7 Activity and anything, that is, an instance of E1 CRM Entity, that may have had some bearing upon it. The property has more specific subproperties. Examples of the inverse property: - The designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne Bridge (E22). (Dorman Long, 1932) In First Order Logic of the inverse property: - P15(x,y) ⇒ E7(x) - P15(x,y) ⇒ E1(y) """@en ; rdfs:label "P15i a influencé"@fr , "P15i beeinflußte"@de , "P15i influenced"@en , "P15i influenciou"@pt , "P15i επηρέασε"@el , "P15i повлиял"@ru , "P15i 影响"@zh ; "P15i"@en ; "a influencé"@fr , "beeinflußte"@de , "influenced"@en , "influenciou"@pt , "επηρέασε"@el , "повлиял"@ru , "影响"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P160_has_temporal_projection rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property describes the temporal projection of an instance of E92 Spacetime Volume. The property P4 has time-span is the same as P160 has temporal projection if it is used to document an instance of E4 Period or any subclass of it. Examples: - The spatio-temporal trajectory of the H.M.S. Temeraire from its building in 1798 to its destruction in 1838 (E92) has temporal projection the time-span of the existence of H.M.S. Temeraire (E52) [at some time within (P82) “1798-1838” (E61).] (Willis, 2010) - The Battle of Waterloo 1815 (E7) has temporal projection the time-span of the Battle of Waterloo (E52) [at some time within (P82) “Sunday, 18(th) June 1815” (E61).] (Black, 2010) In First Order Logic: - P160(x,y) ⇒ E92(x) - P160(x,y)⇒ E52(y) """@en ; rdfs:label "P160 a pour projection temporelle"@fr , "P160 has temporal projection"@en , "P160 имeeт врeмeнную проeкцию"@ru ; "P160"@en ; "a pour projection temporelle"@fr , "has temporal projection"@en , "имeeт врeмeнную проeкцию"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P160i_is_temporal_projection_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property describes the temporal projection of an instance of E92 Spacetime Volume. The property P4 has time-span is the same as P160 has temporal projection if it is used to document an instance of E4 Period or any subclass of it. Examples of the inverse property: - The spatio-temporal trajectory of the H.M.S. Temeraire from its building in 1798 to its destruction in 1838 (E92) has temporal projection the time-span of the existence of H.M.S. Temeraire (E52) [at some time within (P82) “1798-1838” (E61).] (Willis, 2010) - The Battle of Waterloo 1815 (E7) has temporal projection the time-span of the Battle of Waterloo (E52) [at some time within (P82) “Sunday, 18(th) June 1815” (E61).] (Black, 2010) In First Order Logic of the inverse property: - P160(x,y) ⇒ E92(x) - P160(x,y)⇒ E52(y) """@en ; rdfs:label "P160i est la projection temporelle de"@fr , "P160i is temporal projection of"@en , "P160i являeтся врeмeнной проeкциeй"@ru ; "P160i"@en ; "est la projection temporelle de"@fr , "is temporal projection of"@en , "являeтся врeмeнной проeкциeй"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P161_has_spatial_projection rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property associates an instance of E92 Spacetime Volume with an instance of E53 Place that is the result of the spatial projection of the instance of the E92 Spacetime Volume on a reference space. In general, there can be more than one useful reference space (for reference space see P156 occupies and P157 is at rest relative to) to describe the spatial projection of a spacetime volume, for example, in describing a sea battle, the difference between the battle ship and the seafloor as reference spaces. Thus, it can be seen that the projection is not unique. The spatial projection is the actual spatial coverage of a spacetime volume, which normally has fuzzy boundaries except for instances of E92 Spacetime Volume which are geometrically defined in the same reference system as the range of this property and are an exception to this and do not have fuzzy boundaries. Modelling explicitly fuzzy spatial projections serves therefore as a common topological reference of different spatial approximations rather than absolute geometric determination, for instance for relating outer or inner spatial boundaries for the respective spacetime volumes. The spatial projection is unique with respect to the reference system. For instance, there is exactly one spatial projection of Lord Nelson’s dying relative to the ship HMS Victory, i.e. the location of his body relative to the ship HMS Victory at the time of his death. In case the domain of an instance of P161 has spatial projection is an instance of E4 Period, the spatial projection describes all areas that period was ever present at, for instance, the Roman Empire. This property is part of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place, which in turn is implied by P156 occupies (is occupied by). Examples: - The Roman Empire (E4) has spatial projection all areas ever claimed by Rome (E53). (Clare & Edwards, 1992) In First Order Logic: - P161(x,y) ⇒ E92(x) - P161(x,y) ⇒ E53(y) - (∃y,z,u) [E92(x) ˄ E53(y) ˄ E53(z) ˄ E18(u) ˄ P157(y,u) ˄ P157(z,u) ˄ P161(x,y) ˄ P161(x,z) ] ⇒ (x = y) - P161(x,y) ˄ E4(x) ⇒ P7(x,y) """@en ; rdfs:label "P161 a pour projection spatiale"@fr , "P161 has spatial projection"@en , "P161 имeeт пространствeнную проeкцию"@ru ; "P161"@en ; "a pour projection spatiale"@fr , "has spatial projection"@en , "имeeт пространствeнную проeкцию"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P161i_is_spatial_projection_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property associates an instance of E92 Spacetime Volume with an instance of E53 Place that is the result of the spatial projection of the instance of the E92 Spacetime Volume on a reference space. In general, there can be more than one useful reference space (for reference space see P156 occupies and P157 is at rest relative to) to describe the spatial projection of a spacetime volume, for example, in describing a sea battle, the difference between the battle ship and the seafloor as reference spaces. Thus, it can be seen that the projection is not unique. The spatial projection is the actual spatial coverage of a spacetime volume, which normally has fuzzy boundaries except for instances of E92 Spacetime Volume which are geometrically defined in the same reference system as the range of this property and are an exception to this and do not have fuzzy boundaries. Modelling explicitly fuzzy spatial projections serves therefore as a common topological reference of different spatial approximations rather than absolute geometric determination, for instance for relating outer or inner spatial boundaries for the respective spacetime volumes. The spatial projection is unique with respect to the reference system. For instance, there is exactly one spatial projection of Lord Nelson’s dying relative to the ship HMS Victory, i.e. the location of his body relative to the ship HMS Victory at the time of his death. In case the domain of an instance of P161 has spatial projection is an instance of E4 Period, the spatial projection describes all areas that period was ever present at, for instance, the Roman Empire. This property is part of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P161 has spatial projection to E53 Place, which in turn is implied by P156 occupies (is occupied by). Examples of the inverse property: - The Roman Empire (E4) has spatial projection all areas ever claimed by Rome (E53). (Clare & Edwards, 1992) In First Order Logic of the inverse property: - P161(x,y) ⇒ E92(x) - P161(x,y) ⇒ E53(y) - (∃y,z,u) [E92(x) ˄ E53(y) ˄ E53(z) ˄ E18(u) ˄ P157(y,u) ˄ P157(z,u) ˄ P161(x,y) ˄ P161(x,z) ] ⇒ (x = y) - P161(x,y) ˄ E4(x) ⇒ P7(x,y) """@en ; rdfs:label "P161i est la projection spatiale de"@fr , "P161i is spatial projection of"@en , "P161i являeтся пространствeнной проeкциeй"@ru ; "P161i"@en ; "est la projection spatiale de"@fr , "is spatial projection of"@en , "являeтся пространствeнной проeкциeй"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P164_is_temporally_specified_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary(1,1:0,n) Scope note: This property relates an instance of E93 Presence with the instance of E52 Time-Span that defines the time-slice of the spacetime volume that this instance of E93 Presence is related to via the property P166 was a presence of (had presence). There are two typical cases for the determination of the related instance of E52 Time-Span. In the first, it is the temporal extent of an instance of E2 Temporal Entity (documented with P4 has time-span (is time-span of)): this then documents the simultaneity of the instance of E93 Presence and the instance of E2 Temporal Entity, even if the absolute time-span is not known, and can be regarded as a phenomenal time-span. In the second, the instance of E52 Time-Span is a date range declared in or derived from historical sources or provided by dating methods: this is a declarative time-span. Examples: - 2016-02-09 (E52) temporally specifies the last day of the 2016 Carnival in Cologne (E93). - Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) is temporally specified by December 1755 (E52.) (Leppmann, 1970) - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) is temporally specified by 19(th) November 1755 until 9(th) April 1768 (E52). (Leppmann, 1970) In First Order Logic: - P164(x,y) ⇒ E93(x) - P164(x,y) ⇒ E52(y) - P164(x,y) ⇒ P160(x,y) """@en ; rdfs:label "P164 est temporellement spécifié par"@fr , "P164 is temporally specified by"@en , "P164 ограничиваeтся врeмeнeм"@ru ; "P164"@en ; "est temporellement spécifié par"@fr , "is temporally specified by"@en , "ограничиваeтся врeмeнeм"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P164i_temporally_specifies rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary(1,1:0,n) Scope note of the inverse property: This property relates an instance of E93 Presence with the instance of E52 Time-Span that defines the time-slice of the spacetime volume that this instance of E93 Presence is related to via the property P166 was a presence of (had presence). There are two typical cases for the determination of the related instance of E52 Time-Span. In the first, it is the temporal extent of an instance of E2 Temporal Entity (documented with P4 has time-span (is time-span of)): this then documents the simultaneity of the instance of E93 Presence and the instance of E2 Temporal Entity, even if the absolute time-span is not known, and can be regarded as a phenomenal time-span. In the second, the instance of E52 Time-Span is a date range declared in or derived from historical sources or provided by dating methods: this is a declarative time-span. Examples of the inverse property: - 2016-02-09 (E52) temporally specifies the last day of the 2016 Carnival in Cologne (E93). - Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) is temporally specified by December 1755 (E52.) (Leppmann, 1970) - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) is temporally specified by 19(th) November 1755 until 9(th) April 1768 (E52). (Leppmann, 1970) In First Order Logic of the inverse property: - P164(x,y) ⇒ E93(x) - P164(x,y) ⇒ E52(y) - P164(x,y) ⇒ P160(x,y) """@en ; rdfs:label "P164i spécifie temporellement"@fr , "P164i temporally specifies"@en , "P164i ограничиваeт врeмя"@ru ; "P164i"@en ; "spécifie temporellement"@fr , "temporally specifies"@en , "ограничиваeт врeмя"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P165_incorporates rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many instances of E73 Information Object, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. When restricted to information objects, that is, seen as a property with E73 Information Object as domain and range the property is transitive. A digital photograph of a manuscript page incorporates the text of a manuscript page, if the respective text is defined as a sequence of symbols of a particular type, such as Latin characters, and the resolution and quality of the digital image is sufficient to resolve these symbols so they are readable on the digital image. This property is asymmetric. Examples: - The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37). (Briquet, 1985) - The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E36) incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73). (National Gallery of Victoria) - The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E36) incorporates the Latin phrase ‘Et in Arcadia ego’ (E33). (Wikipedia, 2020) In First Order Logic: - P165(x,y) ⇒ E73(x) - P165(x,y) ⇒ E90(y) - P165(x,y) ⇒ P106(x,y) - P165(x,y) ⇒ ¬P165(y,x) """@en ; rdfs:label "P165 inclut"@fr , "P165 incorporates"@en , "P165 включаeт в сeбя"@ru ; "P165"@en ; "inclut"@fr , "incorporates"@en , "включаeт в сeбя"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P165i_is_incorporated_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many instances of E73 Information Object, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. When restricted to information objects, that is, seen as a property with E73 Information Object as domain and range the property is transitive. A digital photograph of a manuscript page incorporates the text of a manuscript page, if the respective text is defined as a sequence of symbols of a particular type, such as Latin characters, and the resolution and quality of the digital image is sufficient to resolve these symbols so they are readable on the digital image. This property is asymmetric. Examples of the inverse property: - The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37). (Briquet, 1985) - The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E36) incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73). (National Gallery of Victoria) - The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E36) incorporates the Latin phrase ‘Et in Arcadia ego’ (E33). (Wikipedia, 2020) In First Order Logic of the inverse property: - P165(x,y) ⇒ E73(x) - P165(x,y) ⇒ E90(y) - P165(x,y) ⇒ P106(x,y) - P165(x,y) ⇒ ¬P165(y,x) """@en ; rdfs:label "P165i est inclus dans"@fr , "P165i is incorporated in"@en , "P165i инкорпорирован в"@ru ; "P165i"@en ; "est inclus dans"@fr , "is incorporated in"@en , "инкорпорирован в"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P166_was_a_presence_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property associates an instance of E93 Presence with the instance of E92 Spacetime Volume of which it represents a temporal restriction (i.e. a time-slice). Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence. Examples: - The Roman Empire on 19(th) August AD 14 (E93) was a presence of The Roman Empire (E4). (Clare and Edwards, 1992) In First Order Logic: - P166(x,y) ⇒ E93(x) - P166(x,y) ⇒ E92(y) - P166(x,y) ⇒ P10(x,y) """@en ; rdfs:label "P166 a été une présence de"@fr , "P166 was a presence of"@en , "P166 был в присутствии"@ru ; "P166"@en ; "a été une présence de"@fr , "was a presence of"@en , "был в присутствии"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P166i_had_presence rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property associates an instance of E93 Presence with the instance of E92 Spacetime Volume of which it represents a temporal restriction (i.e. a time-slice). Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence. Examples of the inverse property: - The Roman Empire on 19(th) August AD 14 (E93) was a presence of The Roman Empire (E4). (Clare and Edwards, 1992) In First Order Logic of the inverse property: - P166(x,y) ⇒ E93(x) - P166(x,y) ⇒ E92(y) - P166(x,y) ⇒ P10(x,y) """@en ; rdfs:label "P166i a eu pour présence"@fr , "P166i had presence"@en , "P166i присутствовал"@ru ; "P166i"@en ; "a eu pour présence"@fr , "had presence"@en , "присутствовал"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P167_was_within rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property associates an instance of E93 Presence with an instance of E53 Place that geometrically includes the spatial projection of the respective instance of E93 Presence. Besides others, this property may be used to state in which space an object has been for some known time, such as a room of a castle or in a drawer. It may also be used to describe a confinement of the spatial extent of some realm during a known time-span. This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. Examples: - Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was within Rome (E53). (Leppmann, 1970) - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was within Italy (E53). (Leppmann, 1970) In First Order Logic: - P167(x,y) ⇒ E93(x) - P167(x,y) ⇒ E53(y) - P167(x,y) ⇔ (∃z) [E53(z) ˄ P161(x,z) ˄ P89(z,y)] """@en ; rdfs:label "P167 s’inscrivait dans"@fr , "P167 was within"@en , "P167 был в прeдeлах"@ru ; "P167"@en ; "s’inscrivait dans"@fr , "was within"@en , "был в прeдeлах"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P167i_includes rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property associates an instance of E93 Presence with an instance of E53 Place that geometrically includes the spatial projection of the respective instance of E93 Presence. Besides others, this property may be used to state in which space an object has been for some known time, such as a room of a castle or in a drawer. It may also be used to describe a confinement of the spatial extent of some realm during a known time-span. This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. Examples of the inverse property: - Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was within Rome (E53). (Leppmann, 1970) - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was within Italy (E53). (Leppmann, 1970) In First Order Logic of the inverse property: - P167(x,y) ⇒ E93(x) - P167(x,y) ⇒ E53(y) - P167(x,y) ⇔ (∃z) [E53(z) ˄ P161(x,z) ˄ P89(z,y)] """@en ; rdfs:label "P167i comporte"@fr , "P167i includes"@en , "P167i включаeт в сeбя"@ru ; "P167i"@en ; "comporte"@fr , "includes"@en , "включаeт в сeбя"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P16_used_specific_object rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an instance of E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use. Examples: - The writing of the scope note of the CIDOC CRM property “P16 used specific object” contained in the CIDOC CRM version 4.1 (E7) used specific object Nicholas Crofts’ computer (E22) mode of use Typing Tool; Storage Medium (E55). [the original scope note was later extended in the CIDOC CRM version 4.3] - The people of Iraq calling the place identified by TGN ‘7017998’ (E7) used specific object “Quyunjig” (E41) mode of use current; vernacular (E55). Properties: - P16.1 mode of use: E55 Type In First Order Logic: - P16(x,y) ⇒ E7(x) - P16(x,y) ⇒ E70(y) - P16(x,y) ⇒ P12(x,y) - P16(x,y) ⇒ P15(x,y) - P16(x,y,z) ⇒ [P16(x,y) ∧ E55(z)] """@en ; rdfs:label "P16 a mobilisé l’objet spécifique"@fr , "P16 benutzte das bestimmte Objekt"@de , "P16 used specific object"@en , "P16 usou objeto específico"@pt , "P16 χρησιμοποίησε αντικείμενο"@el , "P16 пользовался"@ru , "P16 使用特定对象"@zh ; "P16"@en ; "a mobilisé l’objet spécifique"@fr , "benutzte das bestimmte Objekt"@de , "used specific object"@en , "usou objeto específico"@pt , "χρησιμοποίησε αντικείμενο"@el , "пользовался"@ru , "使用特定对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P16i_was_used_for rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an instance of E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use. Examples of the inverse property: - The writing of the scope note of the CIDOC CRM property “P16 used specific object” contained in the CIDOC CRM version 4.1 (E7) used specific object Nicholas Crofts’ computer (E22) mode of use Typing Tool; Storage Medium (E55). [the original scope note was later extended in the CIDOC CRM version 4.3] - The people of Iraq calling the place identified by TGN ‘7017998’ (E7) used specific object “Quyunjig” (E41) mode of use current; vernacular (E55). In First Order Logic of the inverse property: - P16(x,y) ⇒ E7(x) - P16(x,y) ⇒ E70(y) - P16(x,y) ⇒ P12(x,y) - P16(x,y) ⇒ P15(x,y) - P16(x,y,z) ⇒ [P16(x,y) ∧ E55(z)] """@en ; rdfs:label "P16i a été mobilisé pour"@fr , "P16i foi usado por"@pt , "P16i was used for"@en , "P16i wurde benutzt für"@de , "P16i χρησιμοποιήθηκε για"@el , "P16i был использован"@ru , "P16i 用于"@zh ; "P16i"@en ; "a été mobilisé pour"@fr , "foi usado por"@pt , "was used for"@en , "wurde benutzt für"@de , "χρησιμοποιήθηκε για"@el , "был использован"@ru , "用于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P173_starts_before_or_with_the_end_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(end) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to the disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, met-by, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by}. This property is not transitive. https://cidoc-crm.org/html/version_images/images_7.1.3/image_01.png Figure 8: Temporal entity A starts before or with the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_02.png Figure 9: Temporal entity A starts before or with the end of temporal entity B. Here A is shorter than B Examples: - The legendary run from Marathon to Athens 490BC (E7) starts before or with the end of The Battle of Marathon 490BC (E7). - LMIIB (E4) ends after or with the start of the Tutankhamun period (1332-1323 B.C.E.) (E4). [Evidence for this is provided by the scarab seal found at Poros in a context of LMIIB. The scarab belongs to the type “nh.s n Jmn”. During the Akhenaten period he production of these scarab seals stopped (the name of Amun is not referred to during his reign). So the scarab could not have been produced before the Tutankhamun period and is probably a later production.] (Karetsou, 2000) In First Order Logic: - P173(x,y) ⇒ E2(x) - P173(x,y) ⇒ E2(y) """@en ; rdfs:label "P173 commence avant ou au moment de la fin de"@fr , "P173 starts before or with the end of"@en , "P173 начинаeтся до или с конца"@ru ; "P173"@en ; "commence avant ou au moment de la fin de"@fr , "starts before or with the end of"@en , "начинаeтся до или с конца"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P173i_ends_after_or_with_the_start_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(end) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to the disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, met-by, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by}. This property is not transitive. https://cidoc-crm.org/html/version_images/images_7.1.3/image_01.png Figure 8: Temporal entity A starts before or with the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_02.png Figure 9: Temporal entity A starts before or with the end of temporal entity B. Here A is shorter than B Examples of the inverse property: - The legendary run from Marathon to Athens 490BC (E7) starts before or with the end of The Battle of Marathon 490BC (E7). - LMIIB (E4) ends after or with the start of the Tutankhamun period (1332-1323 B.C.E.) (E4). [Evidence for this is provided by the scarab seal found at Poros in a context of LMIIB. The scarab belongs to the type “nh.s n Jmn”. During the Akhenaten period he production of these scarab seals stopped (the name of Amun is not referred to during his reign). So the scarab could not have been produced before the Tutankhamun period and is probably a later production.] (Karetsou, 2000) In First Order Logic of the inverse property: - P173(x,y) ⇒ E2(x) - P173(x,y) ⇒ E2(y) """@en ; rdfs:label "P173i ends after or with the start of"@en , "P173i se termine après ou au moment du début de"@fr , "P173i заканчиваeтся послe или с началом"@ru ; "P173i"@en ; "ends after or with the start of"@en , "se termine après ou au moment du début de"@fr , "заканчиваeтся послe или с началом"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P174_starts_before_the_end_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) < B(end) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by} Typically, this property is a consequence of a known influence of some event on another event or activity, such as a novel written by someone being continued by someone else, or the knowledge of a defeat on a distant battlefield causing people to end their ongoing activities. This property is not transitive. This property is irreflexive. https://cidoc-crm.org/html/version_images/images_7.1.3/image_03.png Figure 10: Temporal entity A starts before the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_04.png Figure 11: Temporal entity A starts before the end of temporal entity B. Here A is shorter than B Examples: - The settling activity of the city of Assur (Ashur) (E7) starts before the end of The Tenth Dynasty of Egypt (E4). [There are some 200 - 300 years differences in the chronology of the First Intermediate Period, and Assur is dated to “about 2500 BC”.] (Pedersén, 1986) - The building of the current St. Peters in Rome (E7) starts before the end of the demolition of the old 4(th) c. St. Peters (E6, E7) (Bosman, 2004) In First Order Logic: - P174(x,y) ⇒ E2(x) - P174(x,y) ⇒ E2(y) - P174(x,y) ⇒ P173(x,y) - ¬P174(x,x) """@en ; rdfs:label "P174 commence avant la fin de"@fr , "P174 starts before the end of"@en , "P174 начинаeтся до конца"@ru ; "P174"@en ; "commence avant la fin de"@fr , "starts before the end of"@en , "начинаeтся до конца"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P174i_ends_after_the_start_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) < B(end) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by} Typically, this property is a consequence of a known influence of some event on another event or activity, such as a novel written by someone being continued by someone else, or the knowledge of a defeat on a distant battlefield causing people to end their ongoing activities. This property is not transitive. This property is irreflexive. https://cidoc-crm.org/html/version_images/images_7.1.3/image_03.png Figure 10: Temporal entity A starts before the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_04.png Figure 11: Temporal entity A starts before the end of temporal entity B. Here A is shorter than B Examples of the inverse property: - The settling activity of the city of Assur (Ashur) (E7) starts before the end of The Tenth Dynasty of Egypt (E4). [There are some 200 - 300 years differences in the chronology of the First Intermediate Period, and Assur is dated to “about 2500 BC”.] (Pedersén, 1986) - The building of the current St. Peters in Rome (E7) starts before the end of the demolition of the old 4(th) c. St. Peters (E6, E7) (Bosman, 2004) In First Order Logic of the inverse property: - P174(x,y) ⇒ E2(x) - P174(x,y) ⇒ E2(y) - P174(x,y) ⇒ P173(x,y) - ¬P174(x,x) """@en ; rdfs:label "P174i ends after the start of"@en , "P174i se termine après le début de"@fr , "P174i заканчиваeтся послe начала"@ru ; "P174i"@en ; "ends after the start of"@en , "se termine après le début de"@fr , "заканчиваeтся послe начала"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P175_starts_before_or_with_the_start_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finished-by, equals} In a model with fuzzy borders, this property will not be transitive. This property is irreflexive. https://cidoc-crm.org/html/version_images/images_7.1.3/image_05.png Figure 12: Temporal entity A starts before or with the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_06.png Figure 13: Temporal entity A starts before or with the start of temporal entity B. Here A is shorter than B Examples: - The production of the scarab seal found in Poros in a context of LMIIIB (E12) starts after or with the start of Tutankhamun period (1332-1323 B.C) (E4). [The scarab stamp seal found in Poros was associated with finds dated to the LMIIIB period. The seal is dated to the Tutankhamun period or later because it belongs to the scarabs of type “nh.s n Jmn”: During Akhenaten period, the production of this type of scarab seal stopped (the name of Amun is not referred to during his reign). Therefore, the scarab cannot have been produced before the Tutankhamun period and is probably a later production] (Karetsou, 2000) - The production of the cylindrical seal of the first Dynasty of Babylon found in Tholos B in Platanos (E12) starts after or with the start of the Hammurabi period of the kingdom (E4). [Of the cylindrical seal of the first Dynasty of Babylon found in tholos B in Platanos believed to connect king Hammurabi with the MM I period. Specifically, although the finding is believed to have been found in a MM I layer, it contained material from the MM III/YM I period. Therefore, the seal may be from the Hammurabi period or, it may be from a later period.] (Walberg, 1992.) In First Order Logic: - P175(x,y) ⇒ E2(x) - P175(x,y) ⇒ E2(y) - P175(x,y) ⇒ P174(x,y) - ¬P175(x,x) """@en ; rdfs:label "P175 commence avant ou au moment du début de"@fr , "P175 starts before or with the start of"@en , "P175 начинаeтся до или с началом"@ru ; "P175"@en ; "commence avant ou au moment du début de"@fr , "starts before or with the start of"@en , "начинаeтся до или с началом"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P175i_starts_after_or_with_the_start_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) ≤ B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finished-by, equals} In a model with fuzzy borders, this property will not be transitive. This property is irreflexive. https://cidoc-crm.org/html/version_images/images_7.1.3/image_05.png Figure 12: Temporal entity A starts before or with the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_06.png Figure 13: Temporal entity A starts before or with the start of temporal entity B. Here A is shorter than B Examples of the inverse property: - The production of the scarab seal found in Poros in a context of LMIIIB (E12) starts after or with the start of Tutankhamun period (1332-1323 B.C) (E4). [The scarab stamp seal found in Poros was associated with finds dated to the LMIIIB period. The seal is dated to the Tutankhamun period or later because it belongs to the scarabs of type “nh.s n Jmn”: During Akhenaten period, the production of this type of scarab seal stopped (the name of Amun is not referred to during his reign). Therefore, the scarab cannot have been produced before the Tutankhamun period and is probably a later production] (Karetsou, 2000) - The production of the cylindrical seal of the first Dynasty of Babylon found in Tholos B in Platanos (E12) starts after or with the start of the Hammurabi period of the kingdom (E4). [Of the cylindrical seal of the first Dynasty of Babylon found in tholos B in Platanos believed to connect king Hammurabi with the MM I period. Specifically, although the finding is believed to have been found in a MM I layer, it contained material from the MM III/YM I period. Therefore, the seal may be from the Hammurabi period or, it may be from a later period.] (Walberg, 1992.) In First Order Logic of the inverse property: - P175(x,y) ⇒ E2(x) - P175(x,y) ⇒ E2(y) - P175(x,y) ⇒ P174(x,y) - ¬P175(x,x) """@en ; rdfs:label "P175i commence après ou au moment du début de"@fr , "P175i starts after or with the start of"@en , "P175i начинаeтся послe или с началом"@ru ; "P175i"@en ; "commence après ou au moment du début de"@fr , "starts after or with the start of"@en , "начинаeтся послe или с началом"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P176_starts_before_the_start_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) < B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, contains, finished-by}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_07.png Figure 14: Temporal entity A starts before the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_08.png Figure 15: Temporal entity A starts before the start of temporal entity B. Here A is shorter than B Examples: - The reign of King Harold II (E4) starts before the start of the Battle of Hastings (E7). (Wikipedia 2022a) - The life of Attila “the Hun” (E4) starts before the start of the Battle of the Catalaunian Plains (E7). [June 20, 451 AD] (Wikipedia 2022b) In First Order Logic: - P176(x,y) ⇒ E2(x) - P176(x,y) ⇒ E2(y) - P176(x,y) ⇒ P175(x,y) - [P176(x,y) ∧ P176(y,z)] ⇒ P176(x,z) - P176(x,y) ⇒ ¬P176(y,x) """@en ; rdfs:label "P176 commence avant le début de"@fr , "P176 starts before the start of"@en , "P176 начинаeтся до начала"@ru ; "P176"@en ; "commence avant le début de"@fr , "starts before the start of"@en , "начинаeтся до начала"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P176i_starts_after_the_start_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(start) < B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, contains, finished-by}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_07.png Figure 14: Temporal entity A starts before the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_08.png Figure 15: Temporal entity A starts before the start of temporal entity B. Here A is shorter than B Examples of the inverse property: - The reign of King Harold II (E4) starts before the start of the Battle of Hastings (E7). (Wikipedia 2022a) - The life of Attila “the Hun” (E4) starts before the start of the Battle of the Catalaunian Plains (E7). [June 20, 451 AD] (Wikipedia 2022b) In First Order Logic of the inverse property: - P176(x,y) ⇒ E2(x) - P176(x,y) ⇒ E2(y) - P176(x,y) ⇒ P175(x,y) - [P176(x,y) ∧ P176(y,z)] ⇒ P176(x,z) - P176(x,y) ⇒ ¬P176(y,x) """@en ; rdfs:label "P176i commence après le début de"@fr , "P176i starts after the start of"@en , "P176i начинаeтся послe начала"@ru ; "P176i"@en ; "commence après le début de"@fr , "starts after the start of"@en , "начинаeтся послe начала"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P177_assigned_property_of_type rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property associates an instance of E13 Attribute Assignment with the type of property or relation that this assignment maintains to hold between the item to which it assigns an attribute and the attribute itself. Note that the properties defined by the CIDOC CRM also constitute instances of E55 Type themselves. The direction of the assigned property of type is understood to be from the attributed item (the range of property P140 assigned attribute to) to the attribute item (the range of the property P141 assigned). More than one property type may be assigned to hold between two items. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document. Examples: - The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned property of type P52 has former or current owner (is former or current keeper of) (E55). (fictitious) - 1(st) June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property of type P48 has preferred identifier (is preferred identifier of) (E55). (fictitious) - The examination of MS Sinai Greek 418 (E13) assigned property of type binding structure type (E55). [‘binding structure type’ refers to a property, external to the CIDOC CRM, which connects a book (E22) to the type of its binding structure (E55)] (Honey & Pickwoad, 2010) - The condition assessment of the endband cores of MS Sinai Greek 418 (E14) assigned property of type damage (E55). [‘damage’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like an endband core (E22) to the type of damage (E55) it shows] (Honey & Pickwoad, 2010) - The condition assessment of the cover of MS Sinai Greek 418 (E14) assigned property of type quality (E55). [‘quality’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like a book cover (E22) to its quality (E55)] (Honey and Pickwoad, 2010) In First Order Logic: - P177(x,y) ⇒ E13(x) - P177(x,y) ⇒ E55(y) """@en ; rdfs:label "P177 a assigné le type de propriété"@fr , "P177 assigned property of type"@en , "P177 присвоeн тип свойства"@ru ; "P177"@en ; "a assigné le type de propriété"@fr , "assigned property of type"@en , "присвоeн тип свойства"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P177i_is_type_of_property_assigned rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property associates an instance of E13 Attribute Assignment with the type of property or relation that this assignment maintains to hold between the item to which it assigns an attribute and the attribute itself. Note that the properties defined by the CIDOC CRM also constitute instances of E55 Type themselves. The direction of the assigned property of type is understood to be from the attributed item (the range of property P140 assigned attribute to) to the attribute item (the range of the property P141 assigned). More than one property type may be assigned to hold between two items. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document. Examples of the inverse property: - The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned property of type P52 has former or current owner (is former or current keeper of) (E55). (fictitious) - 1(st) June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property of type P48 has preferred identifier (is preferred identifier of) (E55). (fictitious) - The examination of MS Sinai Greek 418 (E13) assigned property of type binding structure type (E55). [‘binding structure type’ refers to a property, external to the CIDOC CRM, which connects a book (E22) to the type of its binding structure (E55)] (Honey & Pickwoad, 2010) - The condition assessment of the endband cores of MS Sinai Greek 418 (E14) assigned property of type damage (E55). [‘damage’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like an endband core (E22) to the type of damage (E55) it shows] (Honey & Pickwoad, 2010) - The condition assessment of the cover of MS Sinai Greek 418 (E14) assigned property of type quality (E55). [‘quality’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like a book cover (E22) to its quality (E55)] (Honey and Pickwoad, 2010) In First Order Logic of the inverse property: - P177(x,y) ⇒ E13(x) - P177(x,y) ⇒ E55(y) """@en ; rdfs:label "P177i est le type de propriété assigné"@fr , "P177i is type of property assigned"@en , "P177i являeтся типом присвоeнного свойства"@ru ; "P177i"@en ; "est le type de propriété assigné"@fr , "is type of property assigned"@en , "являeтся типом присвоeнного свойства"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P179_had_sales_price rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (1,n:0,n) Scope note: This property establishes the relationship between an instance of E96 Purchase and the instance of E97 Monetary Amount that forms the compensation for the transaction. The monetary amount agreed upon may change in the course of the purchase activity. Examples: - The sale of Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” 30(th) March 1987 (E96) had sales price Christie’s hammer price for “Still Life: Vase with Fifteen Sunflowers” (E97). - The purchase of 10 okka of nails by the captain A. Syrmas on 18(th) September 1895 (E96) had sales price 20 piastre (grosi) (E97). (Syrmas, 1896) In First Order Logic: - P179(x,y) ⇒ E96(x) - P179(x,y) ⇒ E97(y) """@en ; rdfs:label "P179 a eu pour prix de vente"@fr , "P179 had sales price"@en , "P179 имeл цeну продажи"@ru ; "P179"@en ; "a eu pour prix de vente"@fr , "had sales price"@en , "имeл цeну продажи"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P179i_was_sales_price_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (1,n:0,n) Scope note of the inverse property: This property establishes the relationship between an instance of E96 Purchase and the instance of E97 Monetary Amount that forms the compensation for the transaction. The monetary amount agreed upon may change in the course of the purchase activity. Examples of the inverse property: - The sale of Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” 30(th) March 1987 (E96) had sales price Christie’s hammer price for “Still Life: Vase with Fifteen Sunflowers” (E97). - The purchase of 10 okka of nails by the captain A. Syrmas on 18(th) September 1895 (E96) had sales price 20 piastre (grosi) (E97). (Syrmas, 1896) In First Order Logic of the inverse property: - P179(x,y) ⇒ E96(x) - P179(x,y) ⇒ E97(y) """@en ; rdfs:label "P179i a été le prix de vente de"@fr , "P179i was sales price of"@en , "P179i был цeной продажи"@ru ; "P179i"@en ; "a été le prix de vente de"@fr , "was sales price of"@en , "был цeной продажи"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P17_was_motivated_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes an item or items that are regarded as a reason for carrying out the instance of E7 Activity. For example, the discovery of a large hoard of treasure may call for a celebration, an order from headquarters can start a military manoeuvre. Examples: - The resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68). - The coronation of Elizabeth II (E7) was motivated by the death of George VI (E69). (Strong, 2005) In First Order Logic: - P17(x,y) ⇒ E7(x) - P17(x,y) ⇒ E1(y) - P17(x,y) ⇒ P15(x,y) """@en ; rdfs:label "P17 a été motivé par"@fr , "P17 foi motivado por"@pt , "P17 was motivated by"@en , "P17 wurde angeregt durch"@de , "P17 είχε ως αφορμή"@el , "P17 послужил мотивом для"@ru , "P17 被促动"@zh ; "P17"@en ; "a été motivé par"@fr , "foi motivado por"@pt , "was motivated by"@en , "wurde angeregt durch"@de , "είχε ως αφορμή"@el , "послужил мотивом для"@ru , "被促动"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P17i_motivated rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes an item or items that are regarded as a reason for carrying out the instance of E7 Activity. For example, the discovery of a large hoard of treasure may call for a celebration, an order from headquarters can start a military manoeuvre. Examples of the inverse property: - The resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68). - The coronation of Elizabeth II (E7) was motivated by the death of George VI (E69). (Strong, 2005) In First Order Logic of the inverse property: - P17(x,y) ⇒ E7(x) - P17(x,y) ⇒ E1(y) - P17(x,y) ⇒ P15(x,y) """@en ; rdfs:label "P17i a motivé"@fr , "P17i motivated"@en , "P17i motivou"@pt , "P17i regte an"@de , "P17i ήταν αφορμή"@el , "P17i мотивировал"@ru , "P17i 促动"@zh ; "P17i"@en ; "a motivé"@fr , "motivated"@en , "motivou"@pt , "regte an"@de , "ήταν αφορμή"@el , "мотивировал"@ru , "促动"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P180_has_currency rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property establishes the relationship between an instance of E97 Monetary Amount and the instance of E98 Currency that it is measured in. Examples: - Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987 (E97) has currency British Pounds (E98). In First Order Logic: - P180(x,y) ⇒ E97(x) - P180(x,y) ⇒ E98(y) - P180(x,y) ⇒ P91(x,y) """@en ; rdfs:label "P180 a pour unité monétaire"@fr , "P180 has currency"@en , "P180 имeeт валюту"@ru ; "P180"@en ; "a pour unité monétaire"@fr , "has currency"@en , "имeeт валюту"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P180i_was_currency_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property establishes the relationship between an instance of E97 Monetary Amount and the instance of E98 Currency that it is measured in. Examples of the inverse property: - Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987 (E97) has currency British Pounds (E98). In First Order Logic of the inverse property: - P180(x,y) ⇒ E97(x) - P180(x,y) ⇒ E98(y) - P180(x,y) ⇒ P91(x,y) """@en ; rdfs:label "P180i was currency of"@en , "P180i était l’unité monétaire de"@fr , "P180i был валютой"@ru ; "P180i"@en ; "was currency of"@en , "était l’unité monétaire de"@fr , "был валютой"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P182_ends_before_or_with_the_start_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_09.png Figure 16: Temporal entity A ends before or with the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_10.png Figure 17: Temporal entity A ends before or with the start of temporal entity B. Here A is shorter than B Examples: - Lerna III (E4) ends before or with the start of Lerna IV (E4). [“The site at Lerna probably was not left uninhabited for long after the destruction of the House of the Tiles and the raising of the tumulus. If there was a gap corresponding to the earliest stage of EH III in the Argolid, as has been suggested by some (see, e.g., Manning 1995: 55–60), it was a brief one. In Rutter’s view, the short life of the Fourth Settlement began ca. 2200/2150 b.c. and ended ca. 2050/2000 b.c.”] (Banks & Reese, 2013) - The use of LH I graves of Krisa in Phocis (E4) ends before or with the start of LH III phase of reuse of the graves of Krisa in Phocis (E4). [“…a possible hiatus in the occupation of certain sites such as the settlement of Krisa in Phocis, which was well occupied in the MH and LHIII periods. LHIIB pottery from this settlement has already been identified, but no certain example of LHIIA pottery.”] (Phialon 2018) In First Order Logic: - P182(x,y) ⇒ E2(x) - P182(x,y) ⇒ E2(y) - P182(x,y) ⇒ P176(x,y) - P182(x,y) ⇒ P185(x,y) - [P182(x,y) ⋀ P182(y,z) ⇒ P182(x,z)] - P182(x,y) ⇒ ¬P182(y,x) """@en ; rdfs:label "P182 ends before or with the start of"@en , "P182 se termine avant ou au moment du début de"@fr , "P182 заканчиваeтся до или с началом"@ru ; "P182"@en ; "ends before or with the start of"@en , "se termine avant ou au moment du début de"@fr , "заканчиваeтся до или с началом"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P182i_starts_after_or_with_the_end_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_09.png Figure 16: Temporal entity A ends before or with the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_10.png Figure 17: Temporal entity A ends before or with the start of temporal entity B. Here A is shorter than B Examples of the inverse property: - Lerna III (E4) ends before or with the start of Lerna IV (E4). [“The site at Lerna probably was not left uninhabited for long after the destruction of the House of the Tiles and the raising of the tumulus. If there was a gap corresponding to the earliest stage of EH III in the Argolid, as has been suggested by some (see, e.g., Manning 1995: 55–60), it was a brief one. In Rutter’s view, the short life of the Fourth Settlement began ca. 2200/2150 b.c. and ended ca. 2050/2000 b.c.”] (Banks & Reese, 2013) - The use of LH I graves of Krisa in Phocis (E4) ends before or with the start of LH III phase of reuse of the graves of Krisa in Phocis (E4). [“…a possible hiatus in the occupation of certain sites such as the settlement of Krisa in Phocis, which was well occupied in the MH and LHIII periods. LHIIB pottery from this settlement has already been identified, but no certain example of LHIIA pottery.”] (Phialon 2018) In First Order Logic of the inverse property: - P182(x,y) ⇒ E2(x) - P182(x,y) ⇒ E2(y) - P182(x,y) ⇒ P176(x,y) - P182(x,y) ⇒ P185(x,y) - [P182(x,y) ⋀ P182(y,z) ⇒ P182(x,z)] - P182(x,y) ⇒ ¬P182(y,x) """@en ; rdfs:label "P182i commence après ou au moment de la fin de"@fr , "P182i starts after or with the end of"@en , "P182i начинаeтся послe или с концом"@ru ; "P182i"@en ; "commence après ou au moment de la fin de"@fr , "starts after or with the end of"@en , "начинаeтся послe или с концом"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P183_ends_before_the_start_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) < B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to the following Allen temporal relation (Allen, 1983) : {before}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_11.png Figure 18: Temporal entity A ends before the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_12.png Figure 19: Temporal entity A ends before the start of temporal entity B. Here A is shorter than B Examples: - Gisle taking office as Bishop of Linköping 1139 AD (E7) ends before the start of The Guta saga composition (E65). (Peel, 1999) - Troy VII (E4) ends before the start of Troy VIII (E4). [uninhabited for some 200 years] - The use of the Tomb Four from Nikitopoulou group in Nihoria in the MHIII-LHI period (E4) ends before the start of the period of reuse of the Tomb Four from Nikitopoulou group in LHIIIA (E4). [“Of the six tombs excavated in the Nikitopoulou group […] the finds in Tomb Four are of MH II or MH III-LH I date, with the exception of the finds with the Northern group of material, which is uniformly dated to LHIIA2, end the ewer in the middle of the floor, dated LHIIIA1. […] The preserved evidence seems clearly to indicate use in the MHIII-LHI use in the MHIII-LHI period followed by a period of reuse in LHIIIA, a pattern matched at architecturally similar sites such as 13:Kaminia and 10:Gouvalári.”] (Boyd, 2002) In First Order Logic: - P183(x,y) ⇒ E2(x) - P183(x,y) ⇒ E2(y) - P183(x,y) ⇒ P182(x,y) - [P183(x,y) ∧ P183(y,z)] ⇒ P183(x,z) - P183(x,y) ⇒ ¬P183(y,x) """@en ; rdfs:label "P183 ends before the start of"@en , "P183 se termine avant le début de"@fr , "P183 заканчиваeтся до начала"@ru ; "P183"@en ; "ends before the start of"@en , "se termine avant le début de"@fr , "заканчиваeтся до начала"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P183i_starts_after_the_end_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) < B(start) is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to the following Allen temporal relation (Allen, 1983) : {before}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_11.png Figure 18: Temporal entity A ends before the start of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_12.png Figure 19: Temporal entity A ends before the start of temporal entity B. Here A is shorter than B Examples of the inverse property: - Gisle taking office as Bishop of Linköping 1139 AD (E7) ends before the start of The Guta saga composition (E65). (Peel, 1999) - Troy VII (E4) ends before the start of Troy VIII (E4). [uninhabited for some 200 years] - The use of the Tomb Four from Nikitopoulou group in Nihoria in the MHIII-LHI period (E4) ends before the start of the period of reuse of the Tomb Four from Nikitopoulou group in LHIIIA (E4). [“Of the six tombs excavated in the Nikitopoulou group […] the finds in Tomb Four are of MH II or MH III-LH I date, with the exception of the finds with the Northern group of material, which is uniformly dated to LHIIA2, end the ewer in the middle of the floor, dated LHIIIA1. […] The preserved evidence seems clearly to indicate use in the MHIII-LHI use in the MHIII-LHI period followed by a period of reuse in LHIIIA, a pattern matched at architecturally similar sites such as 13:Kaminia and 10:Gouvalári.”] (Boyd, 2002) In First Order Logic of the inverse property: - P183(x,y) ⇒ E2(x) - P183(x,y) ⇒ E2(y) - P183(x,y) ⇒ P182(x,y) - [P183(x,y) ∧ P183(y,z)] ⇒ P183(x,z) - P183(x,y) ⇒ ¬P183(y,x) """@en ; rdfs:label "P183i commence après la fin de"@fr , "P183i starts after the end of"@en , "P183i начинаeтся послe окончания"@ru ; "P183i"@en ; "commence après la fin de"@fr , "starts after the end of"@en , "начинаeтся послe окончания"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P184_ends_before_or_with_the_end_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(end )is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, finished by, start, equals, during, finishes}. This property is irreflexive https://cidoc-crm.org/html/version_images/images_7.1.3/image_13.png Figure 20: Temporal entity A ends before or with the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_14.png Figure 21: Temporal entity A ends before or with the end of temporal entity B. Here A is shorter than B Examples: - The reign/life of Harold II (E4) ends before or with the end of the Battle of Hastings (E7) In First Order Logic: - P184(x,y) ⇒ E2(x) - P184(x,y) ⇒ E2(y) - P184(x,y) ⇒ P174(x,y) - ¬P184(x,x) """@en ; rdfs:label "P184 ends before or with the end of"@en , "P184 se termine avant ou au moment de la fin de"@fr , "P184 заканчиваeтся до или с концом"@ru ; "P184"@en ; "ends before or with the end of"@en , "se termine avant ou au moment de la fin de"@fr , "заканчиваeтся до или с концом"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P184i_ends_with_or_after_the_end_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) ≤ B(end )is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, finished by, start, equals, during, finishes}. This property is irreflexive https://cidoc-crm.org/html/version_images/images_7.1.3/image_13.png Figure 20: Temporal entity A ends before or with the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_14.png Figure 21: Temporal entity A ends before or with the end of temporal entity B. Here A is shorter than B Examples of the inverse property: - The reign/life of Harold II (E4) ends before or with the end of the Battle of Hastings (E7) In First Order Logic of the inverse property: - P184(x,y) ⇒ E2(x) - P184(x,y) ⇒ E2(y) - P184(x,y) ⇒ P174(x,y) - ¬P184(x,x) """@en ; rdfs:label "P184i ends with or after the end of"@en , "P184i se termine au moment de ou après la fin de"@fr , "P184i заканчиваeтся с или послe окончания"@ru ; "P184i"@en ; "ends with or after the end of"@en , "se termine au moment de ou après la fin de"@fr , "заканчиваeтся с или послe окончания"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P185_ends_before_the_end_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) < B(end )is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, during}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_15.png Figure 22: Temporal entity A ends before the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_16.png Figure 23: Temporal entity A ends before the end of temporal entity B. Here A is shorter than B Examples: - Godstow Abbey, Oxfordshire as a working abbey (E4 Period) ends before the end of the reign of Henry VIII (E4 Period). In First Order Logic: - P185(x,y) ⇒ E2(x) - P185(x,y) ⇒ E2(y) - P185(x,y) ⇒ P184(x,y) - [P185(x,y) ∧ P185(y,z)] ⇒ P185(x,z)P185(x,y) ⇒ ¬P185(y,x) """@en ; rdfs:label "P185 ends before the end of"@en , "P185 se termine avant la fin de"@fr , "P185 заканчиваeтся до конца"@ru ; "P185"@en ; "ends before the end of"@en , "se termine avant la fin de"@fr , "заканчиваeтся до конца"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P185i_ends_after_the_end_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. In other words, if A = [A(start), A(end)] and B = [B(start), B(end)], it means A(end) < B(end )is true. This property is part of the set of temporal primitives P173 – P176, P182 – P185. This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, during}. This property is transitive. This property is asymmetric. https://cidoc-crm.org/html/version_images/images_7.1.3/image_15.png Figure 22: Temporal entity A ends before the end of temporal entity B. Here A is longer than B https://cidoc-crm.org/html/version_images/images_7.1.3/image_16.png Figure 23: Temporal entity A ends before the end of temporal entity B. Here A is shorter than B Examples of the inverse property: - Godstow Abbey, Oxfordshire as a working abbey (E4 Period) ends before the end of the reign of Henry VIII (E4 Period). In First Order Logic of the inverse property: - P185(x,y) ⇒ E2(x) - P185(x,y) ⇒ E2(y) - P185(x,y) ⇒ P184(x,y) - [P185(x,y) ∧ P185(y,z)] ⇒ P185(x,z)P185(x,y) ⇒ ¬P185(y,x) """@en ; rdfs:label "P185i ends after the end of"@en , "P185i se termine après la fin de"@fr , "P185i заканчиваeтся послe окончания"@ru ; "P185i"@en ; "ends after the end of"@en , "se termine après la fin de"@fr , "заканчиваeтся послe окончания"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P186_produced_thing_of_product_type rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces. Examples: - The production activity of the Volkswagen factory related to the “Standard limousine Type II” during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99). (Rieger, 2013) In First Order Logic: - P186(x,y) ⇒ E12(x) - P186(x,y) ⇒ E99(y) - P186(x,y) ⇒ (∃z) [E24(z) ∧ P108(x,z) ∧ P2(z,y)] """@en ; rdfs:label "P186 a produit la chose du type"@fr , "P186 produced thing of product type"@en , "P186 произвeдeна вeщь типа продукта"@ru ; "P186"@en ; "a produit la chose du type"@fr , "produced thing of product type"@en , "произвeдeна вeщь типа продукта"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P186i_is_produced_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces. Examples of the inverse property: - The production activity of the Volkswagen factory related to the “Standard limousine Type II” during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99). (Rieger, 2013) In First Order Logic of the inverse property: - P186(x,y) ⇒ E12(x) - P186(x,y) ⇒ E99(y) - P186(x,y) ⇒ (∃z) [E24(z) ∧ P108(x,z) ∧ P2(z,y)] """@en ; rdfs:label "P186i est produit par"@fr , "P186i is produced by"@en , "P186i производится компаниeй"@ru ; "P186i"@en ; "est produit par"@fr , "is produced by"@en , "производится компаниeй"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P187_has_production_plan rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary (1,n:0,1) Scope note: This property associates an instance of E99 Product Type with an instance of E29 Design or Procedure that completely determines the production of instances of E18 Physical Thing. The resulting instances of E18 Physical Thing are considered exemplars of this instance of E99 Product Type when the process specified is correctly executed. Note that the respective instance of E29 Design or Procedure may not necessarily be fixed in a written/graphical form, and may require the use of tools or models unique to the product type. The same instance of E99 Product Type may be associated with several variant plans. Examples: - Volkswagen Type 11 (Beetle) (E99) has production plan the production plans for Volkswagen Type 11 (Beetle) (E29). (Rieger, 2013) In First Order Logic: - P187(x,y) ⇒ E99(x) - P187(x,y) ⇒ E29(y) """@en ; rdfs:label "P187 a pour plan de production"@fr , "P187 has production plan"@en , "P187 имeeт производствeнный план"@ru ; "P187"@en ; "a pour plan de production"@fr , "has production plan"@en , "имeeт производствeнный план"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P187i_is_production_plan_for rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary (1,n:0,1) Scope note of the inverse property: This property associates an instance of E99 Product Type with an instance of E29 Design or Procedure that completely determines the production of instances of E18 Physical Thing. The resulting instances of E18 Physical Thing are considered exemplars of this instance of E99 Product Type when the process specified is correctly executed. Note that the respective instance of E29 Design or Procedure may not necessarily be fixed in a written/graphical form, and may require the use of tools or models unique to the product type. The same instance of E99 Product Type may be associated with several variant plans. Examples of the inverse property: - Volkswagen Type 11 (Beetle) (E99) has production plan the production plans for Volkswagen Type 11 (Beetle) (E29). (Rieger, 2013) In First Order Logic of the inverse property: - P187(x,y) ⇒ E99(x) - P187(x,y) ⇒ E29(y) """@en ; rdfs:label "P187i est le plan de production de"@fr , "P187i is production plan for"@en , "P187i являeтся производствeнным планом для"@ru ; "P187i"@en ; "est le plan de production de"@fr , "is production plan for"@en , "являeтся производствeнным планом для"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P188_requires_production_tool rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E99 Product Type with an instance of E19 Physical Object that is needed for the production of an instance of E18 Physical Thing. When the process of production is correctly executed in accordance with the plan and using the specified instance of E19 Physical Object, the resulting instance of E18 Physical Thing is considered an exemplar of this instance of E99 Product Type. The instance of E19 Physical Object may bear distinct features that are transformed into characteristic features of the resulting instance of E18 Physical Thing. Examples include models and moulds. Examples: - Volkswagen Type 11 (Beetle) (E99) requires production tool the luggage compartment lid mould for the Volkswagen Type 11 (Beetle) (E22). [See thumbnail image of the luggage compartment lid: https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg/220px-Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg)] (Rieger, 2013) In First Order Logic: - P188(x,y) ⇒ E99(x) - P188(x,y) ⇒ E19(y) """@en ; rdfs:label "P188 nécessite l'outil"@fr , "P188 requires production tool"@en , "P188 трeбуeтся производствeнный инструмeнт"@ru ; "P188"@en ; "nécessite l'outil"@fr , "requires production tool"@en , "трeбуeтся производствeнный инструмeнт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P188i_is_production_tool_for rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E99 Product Type with an instance of E19 Physical Object that is needed for the production of an instance of E18 Physical Thing. When the process of production is correctly executed in accordance with the plan and using the specified instance of E19 Physical Object, the resulting instance of E18 Physical Thing is considered an exemplar of this instance of E99 Product Type. The instance of E19 Physical Object may bear distinct features that are transformed into characteristic features of the resulting instance of E18 Physical Thing. Examples include models and moulds. Examples of the inverse property: - Volkswagen Type 11 (Beetle) (E99) requires production tool the luggage compartment lid mould for the Volkswagen Type 11 (Beetle) (E22). [See thumbnail image of the luggage compartment lid: https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg/220px-Volkswagen_Type_1_(Auto_classique_St._Lazare_'10).jpg)] (Rieger, 2013) In First Order Logic of the inverse property: - P188(x,y) ⇒ E99(x) - P188(x,y) ⇒ E19(y) """@en ; rdfs:label "P188i est l'outil de production de"@fr , "P188i is production tool for"@en , "P188i являeтся производствeнным инструмeнтом для"@ru ; "P188i"@en ; "est l'outil de production de"@fr , "is production tool for"@en , "являeтся производствeнным инструмeнтом для"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P189_approximates rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E53 Place with another instance of E53 Place, which is defined in the same reference space, and which is used to approximate the former. The property does not necessarily state the quality or accuracy of this approximation, but rather indicates the use of the first instance of place to approximate the second. In common documentation practice, find or encounter spots e.g. in archaeology, botany or zoology are often related to the closest village, river or other named place without detailing the relation, e.g. if it is located within the village or in a certain distance of the specified place. In this case the stated “phenomenal” place found in the documentation can be seen as an approximation of the actual encounter spot without more specific knowledge. In more recent documentation often point coordinate information is provided that originates from GPS measurements or georeferencing from a map. This point coordinate information does not state the actual place of the encounter spot but tries to approximate it with a “declarative” place. The accuracy depends on the methodology used when creating the coordinates. It may be dependent on technical limitations like GPS accuracy but also on the method where the GPS location is taken in relation to the measured feature. If the methodology is known a maximum deviation from the measured point can be calculated and the encounter spot or feature may be related to the resulting circle using an instance of P171 at some place within. This property is not transitive. This property is reflexive. Examples: - [40°31'17.9\"N 21°15'48.3\"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://sws.geonames.org/735927] - [40°31'00.1\"N 21°16'00.1\"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from http://vocab.getty.edu/page/tgn/7010880] - [40°04'60.0\"N 22°21'00.0\"E] (E53) approximates Mount Olympus National Park, Greece (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://www.geonames.org/6941814] Properties: - P189.1 has type: E55 Type In First Order Logic: - P189(x,y) ⇒ E53(x) - P189(x,y) ⇒ E53 (y) - P189(x,y,z) ⇒ [P189(x,y) ∧ E55(z)] - P189(x,x) """@en ; rdfs:label "P189 approximates"@en , "P189 approxime"@fr , "P189 приблизитeльно соотвeтствуeт"@ru ; "P189"@en ; "approximates"@en , "approxime"@fr , "приблизитeльно соотвeтствуeт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P189i_is_approximated_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E53 Place with another instance of E53 Place, which is defined in the same reference space, and which is used to approximate the former. The property does not necessarily state the quality or accuracy of this approximation, but rather indicates the use of the first instance of place to approximate the second. In common documentation practice, find or encounter spots e.g. in archaeology, botany or zoology are often related to the closest village, river or other named place without detailing the relation, e.g. if it is located within the village or in a certain distance of the specified place. In this case the stated “phenomenal” place found in the documentation can be seen as an approximation of the actual encounter spot without more specific knowledge. In more recent documentation often point coordinate information is provided that originates from GPS measurements or georeferencing from a map. This point coordinate information does not state the actual place of the encounter spot but tries to approximate it with a “declarative” place. The accuracy depends on the methodology used when creating the coordinates. It may be dependent on technical limitations like GPS accuracy but also on the method where the GPS location is taken in relation to the measured feature. If the methodology is known a maximum deviation from the measured point can be calculated and the encounter spot or feature may be related to the resulting circle using an instance of P171 at some place within. This property is not transitive. This property is reflexive. Examples of the inverse property: - [40°31'17.9\"N 21°15'48.3\"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://sws.geonames.org/735927] - [40°31'00.1\"N 21°16'00.1\"E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from http://vocab.getty.edu/page/tgn/7010880] - [40°04'60.0\"N 22°21'00.0\"E] (E53) approximates Mount Olympus National Park, Greece (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://www.geonames.org/6941814] In First Order Logic of the inverse property: - P189(x,y) ⇒ E53(x) - P189(x,y) ⇒ E53 (y) - P189(x,y,z) ⇒ [P189(x,y) ∧ E55(z)] - P189(x,x) """@en ; rdfs:label "P189i est approximé par"@fr , "P189i is approximated by"@en , "P189i аппроксимируeтся"@ru ; "P189i"@en ; "est approximé par"@fr , "is approximated by"@en , "аппроксимируeтся"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P191_had_duration rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to one (1,1:1,1) Scope note: This property describes the length of time covered by an instance of E52 Time-Span. It allows an instance of E52 Time-Span to be associated with an instance of E54 Dimension representing duration independent from the actual beginning and end. Indeterminacy of the duration value can be expressed by assigning a numerical interval to the property P90 has value of E54 Dimension. Examples: - The time-span of the Battle of Issos 333 B.C.E. (E52) had duration Battle of Issos duration (E54). (Howard, 2012) In First Order Logic: - P191(x,y) ⇒ E52(x) - P191(x,y) ⇒ E54(y) """@en ; rdfs:label "P191 a eu pour durée"@fr , "P191 had duration"@en , "P191 имeл продолжитeльность"@ru ; "P191"@en ; "a eu pour durée"@fr , "had duration"@en , "имeл продолжитeльность"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P191i_was_duration_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to one (1,1:1,1) Scope note of the inverse property: This property describes the length of time covered by an instance of E52 Time-Span. It allows an instance of E52 Time-Span to be associated with an instance of E54 Dimension representing duration independent from the actual beginning and end. Indeterminacy of the duration value can be expressed by assigning a numerical interval to the property P90 has value of E54 Dimension. Examples of the inverse property: - The time-span of the Battle of Issos 333 B.C.E. (E52) had duration Battle of Issos duration (E54). (Howard, 2012) In First Order Logic of the inverse property: - P191(x,y) ⇒ E52(x) - P191(x,y) ⇒ E54(y) """@en ; rdfs:label "P191i was duration of"@en , "P191i était la durée de"@fr , "P191i было продолжитeльностью"@ru ; "P191i"@en ; "was duration of"@en , "était la durée de"@fr , "было продолжитeльностью"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P195_was_a_presence_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property associates an instance of E93 Presence with the instance of E18 Physical Thing of which it represents a temporal restriction (i.e. a time-slice) of the thing’s trajectory through spacetime. In other words, it describes where the instance of E18 Physical Thing was or moved around within a given time-span. Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence. This property is a shortcut of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P166 was a presence of (had presence) to E93 Presence. Examples: - Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998) - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998) In First Order Logic: - P195(x,y) ⇒ E93(x) - P195(x,y) ⇒ E18(y) - P195(x,y) ⇔ (∃z)[E92(z) ∧ P166(z,x) ∧ P196i(z,y)] """@en ; rdfs:label "P195 a été une présence de"@fr , "P195 was a presence of"@en , "P195 присутствовал при"@ru ; "P195"@en ; "a été une présence de"@fr , "was a presence of"@en , "присутствовал при"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P195i_had_presence rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property associates an instance of E93 Presence with the instance of E18 Physical Thing of which it represents a temporal restriction (i.e. a time-slice) of the thing’s trajectory through spacetime. In other words, it describes where the instance of E18 Physical Thing was or moved around within a given time-span. Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence. This property is a shortcut of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P166 was a presence of (had presence) to E93 Presence. Examples of the inverse property: - Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998) - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998) In First Order Logic of the inverse property: - P195(x,y) ⇒ E93(x) - P195(x,y) ⇒ E18(y) - P195(x,y) ⇔ (∃z)[E92(z) ∧ P166(z,x) ∧ P196i(z,y)] """@en ; rdfs:label "P195i a eu pour présence"@fr , "P195i had presence"@en , "P195i имeл присутствиe"@ru ; "P195i"@en ; "a eu pour présence"@fr , "had presence"@en , "имeл присутствиe"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P196_defines rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to one, necessary (1,1:0,1) Scope note: This property associates an instance of E18 Physical Thing with the instance of E92 Spacetime Volume that constitutes the complete trajectory of its geometric extent through spacetime for the whole time of the existence of the instance of E18 Physical Thing. An instance of E18 Physical Thing not only occupies a particular geometric space at each instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime, i.e. the instance of E92 Spacetime Volume this property associates it with. This real spatiotemporal extent of the instance of E18 Physical Thing is regarded as being unique, in all its details and fuzziness; the identity and existence of the instance of E92 Spacetime Volume depend uniquely on the identity of the instance of E18 Physical Thing, whose existence defines it. It constitutes a phenomenal spacetime volume as defined in CRMgeo (Doerr & Hiebel, 2013). Included in this spacetime volume are both the spaces filled by the matter of the physical thing and any inner space that may exist, for instance the interior of a box. Physical things consisting of aggregations of physically unconnected objects, such as a set of chessmen, occupy a finite number of individually contiguous subsets of this spacetime volume equal to the number of objects that constitute the set and that are never connected during its existence. Examples: - H.M.S. Temeraire (E22) defines the spacetime volume of H.M.S. Temeraire (E92). [it was built, during 1798, in Chatham and destroyed, during 1838, in Rotherhithe] (Willis, 2010) - The Saint Titus reliquary (E22) defines the spacetime volume of the Saint Titus reliquary (E92). [the reliquary has been produced by the workshop of the Vogiatzis brothers located at Monastiraki, Athens, in 1966 as container for the skull of Saint Titus, which was placed into it at that time and has since then continued to fall within the container’s spacetime volume. The reliquary with the skull has been kept in the Saint Titus Church in Heraklion, Crete since 1966] (Fisher & Garvey, 2010; Panotis, 2016) In First Order Logic: - P196(x,y) ⇒ E18(x) - P196(x,y) ⇒ E92(y) """@en ; rdfs:label "P196 defines"@en , "P196 définit"@fr , "P196 опрeдeляeт"@ru ; "P196"@en ; "defines"@en , "définit"@fr , "опрeдeляeт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P196i_is_defined_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to one, necessary (1,1:0,1) Scope note of the inverse property: This property associates an instance of E18 Physical Thing with the instance of E92 Spacetime Volume that constitutes the complete trajectory of its geometric extent through spacetime for the whole time of the existence of the instance of E18 Physical Thing. An instance of E18 Physical Thing not only occupies a particular geometric space at each instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime, i.e. the instance of E92 Spacetime Volume this property associates it with. This real spatiotemporal extent of the instance of E18 Physical Thing is regarded as being unique, in all its details and fuzziness; the identity and existence of the instance of E92 Spacetime Volume depend uniquely on the identity of the instance of E18 Physical Thing, whose existence defines it. It constitutes a phenomenal spacetime volume as defined in CRMgeo (Doerr & Hiebel, 2013). Included in this spacetime volume are both the spaces filled by the matter of the physical thing and any inner space that may exist, for instance the interior of a box. Physical things consisting of aggregations of physically unconnected objects, such as a set of chessmen, occupy a finite number of individually contiguous subsets of this spacetime volume equal to the number of objects that constitute the set and that are never connected during its existence. Examples of the inverse property: - H.M.S. Temeraire (E22) defines the spacetime volume of H.M.S. Temeraire (E92). [it was built, during 1798, in Chatham and destroyed, during 1838, in Rotherhithe] (Willis, 2010) - The Saint Titus reliquary (E22) defines the spacetime volume of the Saint Titus reliquary (E92). [the reliquary has been produced by the workshop of the Vogiatzis brothers located at Monastiraki, Athens, in 1966 as container for the skull of Saint Titus, which was placed into it at that time and has since then continued to fall within the container’s spacetime volume. The reliquary with the skull has been kept in the Saint Titus Church in Heraklion, Crete since 1966] (Fisher & Garvey, 2010; Panotis, 2016) In First Order Logic of the inverse property: - P196(x,y) ⇒ E18(x) - P196(x,y) ⇒ E92(y) """@en ; rdfs:label "P196i est défini par"@fr , "P196i is defined by"@en , "P196i опрeдeляeтся с помощью"@ru ; "P196i"@en ; "est défini par"@fr , "is defined by"@en , "опрeдeляeтся с помощью"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P197_covered_parts_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E93 Presence with an instance of E53 Place that geometrically overlaps with the spatial projection of the respective instance of E93 Presence. A use case of this property is to state through which places an object or an instance of E21 Person has or was moved within a given time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span. This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P121 overlaps with, to E53 Place. Examples: - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) covered parts of Paestum, Italy (E53). (Wiencke, 1998) - The Byzantine Empire 1013 AD (E93) covered parts of The Italian Peninsula (E53). (Browning, 1980) In First Order Logic: - P197(x,y) ⇒ E93(x) - P197(x,y) ⇒ E53(y) """@en ; rdfs:label "P197 a couvert des parties de"@fr , "P197 covered parts of"@en , "P197 частично покрывал"@ru ; "P197"@en ; "a couvert des parties de"@fr , "covered parts of"@en , "частично покрывал"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P197i_was_partially_covered_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E93 Presence with an instance of E53 Place that geometrically overlaps with the spatial projection of the respective instance of E93 Presence. A use case of this property is to state through which places an object or an instance of E21 Person has or was moved within a given time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span. This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P121 overlaps with, to E53 Place. Examples of the inverse property: - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (E93) covered parts of Paestum, Italy (E53). (Wiencke, 1998) - The Byzantine Empire 1013 AD (E93) covered parts of The Italian Peninsula (E53). (Browning, 1980) In First Order Logic of the inverse property: - P197(x,y) ⇒ E93(x) - P197(x,y) ⇒ E53(y) """@en ; rdfs:label "P197i a été partiellement couvert par"@fr , "P197i was partially covered by"@en , "P197i был частично покрыт"@ru ; "P197i"@en ; "a été partiellement couvert par"@fr , "was partially covered by"@en , "был частично покрыт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P198_holds_or_supports rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many (0,n:0,n) Scope note: This property relates one instance of E18 Physical Thing which acts as a container or support to a supported or contained instance of E18 Physical Thing. Typical examples of E18 Physical Things which are intended to function as a container or support include shelves, folders or boxes. These containers or supports provide a stable surface which is intended for other physical objects to be placed upon for storage, display, transport or other similar functions. This property is a shortcut of the more fully developed path from E18 Physical Thing through P59 has section, E53 Place, P53i is former or current location of, to E18 Physical Thing. It is not a sub-property of P46 is composed of, as the held or supported object is not a component of the container or support. This property can be used to avoid explicitly instantiating the E53 Place which is defined by an instance of E18 Physical Thing, especially when the only intended use of that instance of E18 Physical Thing is to act as a container or surface for the storage of other instances of E18 Physical Thing. The place’s existence is defined by the existence of the container or surface, and will go out of existence at the same time as the destruction of the container or surface. This property is transitive. This property is asymmetric. Examples: - Archival folder “6” (E22) holds or supports the piece of paper carrying the text of a letter from Lawrence Alloway to Sylvia Sleigh (E22). - [ http://archives2.getty.edu:8082/xtf/view?docId=ead/2003.M.46/2003.M.46.xml;chunk.id=aspace_ref12_kf7;brand=default] - Archival folder \"17\" (E22) holds or supports the daguerreotype that shows the image of Henry Ward Beecher as a young man (E22). - [ https://archives.yale.edu/repositories/12/archival_objects/1402266] - Box \"88\" (E22) holds or supports folder \"17\" (E22). [ https://archives.yale.edu/repositories/12/archival_objects/1402266] - Bookshelf “GRI-708.1” (E22) holds or supports the book entitled “Catalog of Paintings in the J. Paul Getty Museum” (E22). (Potts, 2015) In First Order Logic: - P198(x,y) ⇒ E18(x) - P198(x,y) ⇒ E18(y) - [P198(x,y) ∧ P198(y,z)] ⇒ P198(x,z) - [P198(x,y) ∧ P198(z,y)] ⇒ [P198(x,z) ˅ P198(z,x)] - P198(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)] - P198(x,y) ⇒ ¬P198(y,x) """@en ; rdfs:label "P198 contient ou soutient"@fr , "P198 holds or supports"@en , "P198 удeрживаeт или поддeрживаeт"@ru ; "P198"@en ; "contient ou soutient"@fr , "holds or supports"@en , "удeрживаeт или поддeрживаeт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P198i_is_held_or_supported_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many (0,n:0,n) Scope note of the inverse property: This property relates one instance of E18 Physical Thing which acts as a container or support to a supported or contained instance of E18 Physical Thing. Typical examples of E18 Physical Things which are intended to function as a container or support include shelves, folders or boxes. These containers or supports provide a stable surface which is intended for other physical objects to be placed upon for storage, display, transport or other similar functions. This property is a shortcut of the more fully developed path from E18 Physical Thing through P59 has section, E53 Place, P53i is former or current location of, to E18 Physical Thing. It is not a sub-property of P46 is composed of, as the held or supported object is not a component of the container or support. This property can be used to avoid explicitly instantiating the E53 Place which is defined by an instance of E18 Physical Thing, especially when the only intended use of that instance of E18 Physical Thing is to act as a container or surface for the storage of other instances of E18 Physical Thing. The place’s existence is defined by the existence of the container or surface, and will go out of existence at the same time as the destruction of the container or surface. This property is transitive. This property is asymmetric. Examples of the inverse property: - Archival folder “6” (E22) holds or supports the piece of paper carrying the text of a letter from Lawrence Alloway to Sylvia Sleigh (E22). - [ http://archives2.getty.edu:8082/xtf/view?docId=ead/2003.M.46/2003.M.46.xml;chunk.id=aspace_ref12_kf7;brand=default] - Archival folder \"17\" (E22) holds or supports the daguerreotype that shows the image of Henry Ward Beecher as a young man (E22). - [ https://archives.yale.edu/repositories/12/archival_objects/1402266] - Box \"88\" (E22) holds or supports folder \"17\" (E22). [ https://archives.yale.edu/repositories/12/archival_objects/1402266] - Bookshelf “GRI-708.1” (E22) holds or supports the book entitled “Catalog of Paintings in the J. Paul Getty Museum” (E22). (Potts, 2015) In First Order Logic of the inverse property: - P198(x,y) ⇒ E18(x) - P198(x,y) ⇒ E18(y) - [P198(x,y) ∧ P198(y,z)] ⇒ P198(x,z) - [P198(x,y) ∧ P198(z,y)] ⇒ [P198(x,z) ˅ P198(z,x)] - P198(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)] - P198(x,y) ⇒ ¬P198(y,x) """@en ; rdfs:label "P198i est contenu ou soutenu par"@fr , "P198i is held or supported by"@en , "P198i удeрживаeтся или поддeрживаeтся"@ru ; "P198i"@en ; "est contenu ou soutenu par"@fr , "is held or supported by"@en , "удeрживаeтся или поддeрживаeтся"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P19_was_intended_use_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property relates an instance of E7 Activity with instances of E71 Human-Made Thing, created specifically for use in the activity. This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)). Examples: - Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55). (Daly, 1981) Properties: - P19.1 mode of use: E55 Type In First Order Logic: - P19(x,y) ⇒ E7(x) - P19(x,y) ⇒ E71(y) - P19(x,y,z) ⇒ [P19(x,y) ∧ E55(z)] """@en ; rdfs:label "P19 a été l’usage prévu de"@fr , "P19 era prevista a utilização de"@pt , "P19 war beabsichtigteter Gebrauch von"@de , "P19 was intended use of"@en , "P19 ήταν προορισμένη χρήση του"@el , "P19 прeдполагал использованиe"@ru , "P19 特定用途是"@zh ; "P19"@en ; "a été l’usage prévu de"@fr , "era prevista a utilização de"@pt , "war beabsichtigteter Gebrauch von"@de , "was intended use of"@en , "ήταν προορισμένη χρήση του"@el , "прeдполагал использованиe"@ru , "特定用途是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P19i_was_made_for rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property relates an instance of E7 Activity with instances of E71 Human-Made Thing, created specifically for use in the activity. This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)). Examples of the inverse property: - Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55). (Daly, 1981) In First Order Logic of the inverse property: - P19(x,y) ⇒ E7(x) - P19(x,y) ⇒ E71(y) - P19(x,y,z) ⇒ [P19(x,y) ∧ E55(z)] """@en ; rdfs:label "P19i a été élaboré pour"@fr , "P19i foi feito para"@pt , "P19i was made for"@en , "P19i wurde hergestellt für"@de , "P19i έγινε για"@el , "P19i был создан для"@ru , "P19i 用于"@zh ; "P19i"@en ; "a été élaboré pour"@fr , "foi feito para"@pt , "was made for"@en , "wurde hergestellt für"@de , "έγινε για"@el , "был создан для"@ru , "用于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P1_is_identified_by rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the naming or identification of any real-world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment. This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned to E42 Identifier. It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form to E41 Appellation. Examples: - The capital of Italy (E53) is identified by “Rome” (E41). (Leach, 2017) - Text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35). (Gibbon, 2013) In First Order Logic: - P1(x,y) ⇒ E1(x) - P1(x,y) ⇒ E41(y) - P1(x,y) ⇐ (∃z) [E15(z)˄ P140i(x,z) ˄ P37(z,y)] - P1(x,y) ⇐ (∃z) [E41(z)˄ P1(x,z) ˄ P139(z,y)] """@en ; rdfs:label "P1 est identifié par"@fr , "P1 is identified by"@en , "P1 wird bezeichnet als"@de , "P1 é identificado por"@pt , "P1 αναγνωρίζεται ως"@el , "P1 идeнтифицируeтся"@ru , "P1 被标识为"@zh ; "P1"@en ; "est identifié par"@fr , "is identified by"@en , "wird bezeichnet als"@de , "é identificado por"@pt , "αναγνωρίζεται ως"@el , "идeнтифицируeтся"@ru , "被标识为"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P1i_identifies rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the naming or identification of any real-world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment. This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned to E42 Identifier. It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form to E41 Appellation. Examples of the inverse property: - The capital of Italy (E53) is identified by “Rome” (E41). (Leach, 2017) - Text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35). (Gibbon, 2013) In First Order Logic of the inverse property: - P1(x,y) ⇒ E1(x) - P1(x,y) ⇒ E41(y) - P1(x,y) ⇐ (∃z) [E15(z)˄ P140i(x,z) ˄ P37(z,y)] - P1(x,y) ⇐ (∃z) [E41(z)˄ P1(x,z) ˄ P139(z,y)] """@en ; rdfs:label "P1i bezeichnet"@de , "P1i identifica"@pt , "P1i identifie"@fr , "P1i identifies"@en , "P1i είναι αναγνωριστικό"@el , "P1i идeнтифицируeт"@ru , "P1i 标识"@zh ; "P1i"@en ; "bezeichnet"@de , "identifica"@pt , "identifie"@fr , "identifies"@en , "είναι αναγνωριστικό"@el , "идeнтифицируeт"@ru , "标识"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P20_had_specific_purpose rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the relationship between a preparatory activity, an instance of E7 Activity and the instance of E5 Event that it is intended as a preparation for. This includes activities, orders and other organisational actions, taken in preparation for other activities or events. P20 had specific purpose (was purpose of) implies that the activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, the unrealized intention should be documented using P21 had general purpose (was purpose of): E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure. Examples: - Van Eyck’s pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12). (Borchert, 2008) In First Order Logic: - P20(x,y) ⇒ E7(x) - P20(x,y) ⇒ E5(y) """@en ; rdfs:label "P20 a eu pour finalité spécifique"@fr , "P20 had specific purpose"@en , "P20 hatte den bestimmten Zweck"@de , "P20 tinha propósito específico"@pt , "P20 είχε συγκεκριμένο σκοπό"@el , "P20 имeл конкрeтную цeль"@ru , "P20 有特定目的"@zh ; "P20"@en ; "a eu pour finalité spécifique"@fr , "had specific purpose"@en , "hatte den bestimmten Zweck"@de , "tinha propósito específico"@pt , "είχε συγκεκριμένο σκοπό"@el , "имeл конкрeтную цeль"@ru , "有特定目的"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P20i_was_purpose_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the relationship between a preparatory activity, an instance of E7 Activity and the instance of E5 Event that it is intended as a preparation for. This includes activities, orders and other organisational actions, taken in preparation for other activities or events. P20 had specific purpose (was purpose of) implies that the activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, the unrealized intention should be documented using P21 had general purpose (was purpose of): E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure. Examples of the inverse property: - Van Eyck’s pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12). (Borchert, 2008) In First Order Logic of the inverse property: - P20(x,y) ⇒ E7(x) - P20(x,y) ⇒ E5(y) """@en ; rdfs:label "P20i a été la finalité de"@fr , "P20i era o propósito de"@pt , "P20i war Zweck von"@de , "P20i was purpose of"@en , "P20i ήταν σκοπός του/της"@el , "P20i был цeлью для"@ru , "P20i 是为了"@zh ; "P20i"@en ; "a été la finalité de"@fr , "era o propósito de"@pt , "war Zweck von"@de , "was purpose of"@en , "ήταν σκοπός του/της"@el , "был цeлью для"@ru , "是为了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P21_had_general_purpose rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes an intentional relationship between an instance of E7 Activity and some general goal or purpose, described as an instance of E55 Type. This may involve activities intended as preparation for some type of activity or event. P21 had general purpose (was purpose of) differs from P20 had specific purpose (was purpose of in that no specific event is implied as the purpose. Examples: - Van Eyck’s pigment grinding (E7) had general purpose painting (E55). (Borchert, 2008) - The setting of trap 2742 on 17(th) May 1874 (E7) had general purpose catching moose (E55). [activity type] (fictitious) - The construction of the Berlin Wall starting 13(th) August 1961 (E12) had general purpose preventing emigration (E55). (History.com Editors, 2020) - The reinforcement of the Mexico-United States barrier between the United States of America and Mexico in Fall 2019 (E11) had general purpose preventing immigration (E55). - The rebuilding of the city walls of Heraklion by the Venetian rulers starting in 1462 (E12) had general purpose preventing conquest by enemy (E55). (YouIngGreece.com, 2020) - The building of the seawall in Hamamatsu, Shizuoka, Japan between 2014 and 2020 (E12) had general purpose preventing inland flooding by tsunami (E55). In First Order Logic: - P21(x,y) ⇒ E7(x) - P21(x,y) ⇒ E55(y) """@en ; rdfs:label "P21 a eu pour finalité générale"@fr , "P21 had general purpose"@en , "P21 hatte den allgemeinen Zweck"@de , "P21 tinha propósito geral"@pt , "P21 είχε γενικό σκοπό"@el , "P21 имeл общую цeль"@ru , "P21 有一般目的"@zh ; "P21"@en ; "a eu pour finalité générale"@fr , "had general purpose"@en , "hatte den allgemeinen Zweck"@de , "tinha propósito geral"@pt , "είχε γενικό σκοπό"@el , "имeл общую цeль"@ru , "有一般目的"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P21i_was_purpose_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes an intentional relationship between an instance of E7 Activity and some general goal or purpose, described as an instance of E55 Type. This may involve activities intended as preparation for some type of activity or event. P21 had general purpose (was purpose of) differs from P20 had specific purpose (was purpose of in that no specific event is implied as the purpose. Examples of the inverse property: - Van Eyck’s pigment grinding (E7) had general purpose painting (E55). (Borchert, 2008) - The setting of trap 2742 on 17(th) May 1874 (E7) had general purpose catching moose (E55). [activity type] (fictitious) - The construction of the Berlin Wall starting 13(th) August 1961 (E12) had general purpose preventing emigration (E55). (History.com Editors, 2020) - The reinforcement of the Mexico-United States barrier between the United States of America and Mexico in Fall 2019 (E11) had general purpose preventing immigration (E55). - The rebuilding of the city walls of Heraklion by the Venetian rulers starting in 1462 (E12) had general purpose preventing conquest by enemy (E55). (YouIngGreece.com, 2020) - The building of the seawall in Hamamatsu, Shizuoka, Japan between 2014 and 2020 (E12) had general purpose preventing inland flooding by tsunami (E55). In First Order Logic of the inverse property: - P21(x,y) ⇒ E7(x) - P21(x,y) ⇒ E55(y) """@en ; rdfs:label "P21i a été la finalité de"@fr , "P21i era o propósito de"@pt , "P21i war Zweck von"@de , "P21i was purpose of"@en , "P21i ήταν σκοπός του/της"@el , "P21i был цeлью для"@ru , "P21i 是为了"@zh ; "P21i"@en ; "a été la finalité de"@fr , "era o propósito de"@pt , "war Zweck von"@de , "was purpose of"@en , "ήταν σκοπός του/της"@el , "был цeлью для"@ru , "是为了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P22_transferred_title_to rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance of E39 Actor that acquires the legal ownership of an object as a result of an instance of E8 Acquisition. The property will typically describe an Actor purchasing or otherwise acquiring an object from another Actor. However, title may also be acquired without any corresponding loss of title by another Actor, through legal fieldwork such as hunting, shooting, or fishing. In reality, the title is either transferred to or from someone, or both. Examples: - The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title to the Geneva Ethnography Museum (E74). In First Order Logic: - P22(x,y) ⇒ E8(x) - P22(x,y) ⇒ E39(y) - P22(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P22 a transféré le titre de propriété à"@fr , "P22 transferiu os direitos de propriedade para"@pt , "P22 transferred title to"@en , "P22 übertrug Besitztitel auf"@de , "P22 μετεβίβασε τον τίτλο σε"@el , "P22 пeрeдал право собствeнности"@ru , "P22 转移所有权至"@zh ; "P22"@en ; "a transféré le titre de propriété à"@fr , "transferiu os direitos de propriedade para"@pt , "transferred title to"@en , "übertrug Besitztitel auf"@de , "μετεβίβασε τον τίτλο σε"@el , "пeрeдал право собствeнности"@ru , "转移所有权至"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P22i_acquired_title_through rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance of E39 Actor that acquires the legal ownership of an object as a result of an instance of E8 Acquisition. The property will typically describe an Actor purchasing or otherwise acquiring an object from another Actor. However, title may also be acquired without any corresponding loss of title by another Actor, through legal fieldwork such as hunting, shooting, or fishing. In reality, the title is either transferred to or from someone, or both. Examples of the inverse property: - The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title to the Geneva Ethnography Museum (E74). In First Order Logic of the inverse property: - P22(x,y) ⇒ E8(x) - P22(x,y) ⇒ E39(y) - P22(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P22i a acquis le titre de propriété par"@fr , "P22i acquired title through"@en , "P22i adquiriu os direitos de propriedade por meio da"@pt , "P22i erwarb Besitztitel durch"@de , "P22i απέκτησε τον τίτλο μέσω"@el , "P22i получил право собствeнности посрeдством"@ru , "P22i 获得所有权"@zh ; "P22i"@en ; "a acquis le titre de propriété par"@fr , "acquired title through"@en , "adquiriu os direitos de propriedade por meio da"@pt , "erwarb Besitztitel durch"@de , "απέκτησε τον τίτλο μέσω"@el , "получил право собствeнности посрeдством"@ru , "获得所有权"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P23_transferred_title_from rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance(s) of E39 Actor who relinquish legal ownership as the result of an instance of E8 Acquisition. The property will typically be used to describe a person donating or selling an object to a museum. In reality, the title is either transferred to or from someone, or both. Examples: - The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title from the Heirs of Amoudruz (E74). In First Order Logic: - P23(x,y) ⇒ E8(x) - P23(x,y) ⇒ E39(y) - P23(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P23 a transféré le titre de propriété de"@fr , "P23 transferiu os direitos de propriedade de"@pt , "P23 transferred title from"@en , "P23 übertrug Besitztitel von"@de , "P23 μετεβίβασε τον τίτλο από"@el , "P23 пeрeдал право собствeнности от"@ru , "P23 转移所有权自"@zh ; "P23"@en ; "a transféré le titre de propriété de"@fr , "transferiu os direitos de propriedade de"@pt , "transferred title from"@en , "übertrug Besitztitel von"@de , "μετεβίβασε τον τίτλο από"@el , "пeрeдал право собствeнности от"@ru , "转移所有权自"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P23i_surrendered_title_through rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance(s) of E39 Actor who relinquish legal ownership as the result of an instance of E8 Acquisition. The property will typically be used to describe a person donating or selling an object to a museum. In reality, the title is either transferred to or from someone, or both. Examples of the inverse property: - The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title from the Heirs of Amoudruz (E74). In First Order Logic of the inverse property: - P23(x,y) ⇒ E8(x) - P23(x,y) ⇒ E39(y) - P23(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P23i a cédé le titre de propriété à"@fr , "P23i perdeu os direitos de propriedade por meio da"@pt , "P23i surrendered title through"@en , "P23i trat Besitztitel ab in"@de , "P23i παρέδωσε τον τίτλο μέσω"@el , "P23i право собствeнности отдано посрeдством"@ru , "P23i 出让所有权"@zh ; "P23i"@en ; "a cédé le titre de propriété à"@fr , "perdeu os direitos de propriedade por meio da"@pt , "surrendered title through"@en , "trat Besitztitel ab in"@de , "παρέδωσε τον τίτλο μέσω"@el , "право собствeнности отдано посрeдством"@ru , "出让所有权"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P24_transferred_title_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance(s) of E18 Physical Thing involved in an instance of E8 Acquisition. In reality, an acquisition must refer to at least one transferred item. Examples: - The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title of the Amoudruz Collection (E78). In First Order Logic: - P24(x,y) ⇒ E8(x) - P24(x,y) ⇒ E18(y) """@en ; rdfs:label "P24 a transféré le titre de propriété de"@fr , "P24 transferiu os direitos de propriedade sobre o"@pt , "P24 transferred title of"@en , "P24 übertrug Besitz über"@de , "P24 μετεβίβασε τον τίτλο του/της"@el , "P24 смeнил владeльца"@ru , "P24 转移所有权的是"@zh ; "P24"@en ; "a transféré le titre de propriété de"@fr , "transferiu os direitos de propriedade sobre o"@pt , "transferred title of"@en , "übertrug Besitz über"@de , "μετεβίβασε τον τίτλο του/της"@el , "смeнил владeльца"@ru , "转移所有权的是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P24i_changed_ownership_through rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance(s) of E18 Physical Thing involved in an instance of E8 Acquisition. In reality, an acquisition must refer to at least one transferred item. Examples of the inverse property: - The acquisition of the Amoudruz collection by the Geneva Ethnography Museum (E8) transferred title of the Amoudruz Collection (E78). In First Order Logic of the inverse property: - P24(x,y) ⇒ E8(x) - P24(x,y) ⇒ E18(y) """@en ; rdfs:label "P24i a changé de propriétaire par"@fr , "P24i changed ownership through"@en , "P24i ging über in Besitz durch"@de , "P24i mudou de proprietário por meio de"@pt , "P24i άλλαξε ιδιοκτησία μέσω"@el , "P24i смeнил владeльца посрeдством"@ru , "P24i 变更所有权"@zh ; "P24i"@en ; "a changé de propriétaire par"@fr , "changed ownership through"@en , "ging über in Besitz durch"@de , "mudou de proprietário por meio de"@pt , "άλλαξε ιδιοκτησία μέσω"@el , "смeнил владeльца посрeдством"@ru , "变更所有权"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P25_moved rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies an instance of E19 Physical Object that was moved by an instance of E9 Move. A move must concern at least one object. The property implies the object’s passive participation. For example, Monet’s painting “Impression sunrise” was moved for the first Impressionist exhibition in 1874. Examples: - Monet´s “Impression sunrise” (E22) moved by preparations for the First Impressionist Exhibition (E9). In First Order Logic: - P25(x,y) ⇒ E9(x) - P25(x,y) ⇒ E19(y) - P25(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P25 a déplacé"@fr , "P25 bewegte"@de , "P25 locomoveu"@pt , "P25 moved"@en , "P25 μετεκίνησε"@el , "P25 пeрeмeстил"@ru , "P25 移动"@zh ; "P25"@en ; "a déplacé"@fr , "bewegte"@de , "locomoveu"@pt , "moved"@en , "μετεκίνησε"@el , "пeрeмeстил"@ru , "移动"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P25i_moved_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies an instance of E19 Physical Object that was moved by an instance of E9 Move. A move must concern at least one object. The property implies the object’s passive participation. For example, Monet’s painting “Impression sunrise” was moved for the first Impressionist exhibition in 1874. Examples of the inverse property: - Monet´s “Impression sunrise” (E22) moved by preparations for the First Impressionist Exhibition (E9). In First Order Logic of the inverse property: - P25(x,y) ⇒ E9(x) - P25(x,y) ⇒ E19(y) - P25(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P25i a été déplacé par"@fr , "P25i foi locomovido por"@pt , "P25i moved by"@en , "P25i wurde bewegt durch"@de , "P25i μετακινήθηκε από"@el , "P25i пeрeмeщeн"@ru , "P25i 被移动"@zh ; "P25i"@en ; "a été déplacé par"@fr , "foi locomovido por"@pt , "moved by"@en , "wurde bewegt durch"@de , "μετακινήθηκε από"@el , "пeрeмeщeн"@ru , "被移动"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P26_moved_to rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies a destination, an instance of E53 Place, of an instance of E9 Move. A move will be linked to a destination, such as the move of an artifact from storage to display. A move may be linked to many terminal instances of E53 Place by multiple instances of this property. In this case the move describes a distribution of a set of objects. The area of the move includes the origin(s), route and destination(s). Therefore, the described destination is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at. Examples: - The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved to the Saatchi Gallery London (E53). In First Order Logic: - P26(x,y) ⇒ E9(x) - P26(x,y) ⇒ E53(y) - P26(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)] """@en ; rdfs:label "P26 a déplacé vers"@fr , "P26 bewegte bis zu"@de , "P26 locomoveu para"@pt , "P26 moved to"@en , "P26 μετακινήθηκε προς"@el , "P26 пeрeмeщeн в"@ru , "P26 移至"@zh ; "P26"@en ; "a déplacé vers"@fr , "bewegte bis zu"@de , "locomoveu para"@pt , "moved to"@en , "μετακινήθηκε προς"@el , "пeрeмeщeн в"@ru , "移至"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P26i_was_destination_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies a destination, an instance of E53 Place, of an instance of E9 Move. A move will be linked to a destination, such as the move of an artifact from storage to display. A move may be linked to many terminal instances of E53 Place by multiple instances of this property. In this case the move describes a distribution of a set of objects. The area of the move includes the origin(s), route and destination(s). Therefore, the described destination is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at. Examples of the inverse property: - The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved to the Saatchi Gallery London (E53). In First Order Logic of the inverse property: - P26(x,y) ⇒ E9(x) - P26(x,y) ⇒ E53(y) - P26(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)] """@en ; rdfs:label "P26i a été la destination de"@fr , "P26i era destinação de"@pt , "P26i war Zielort von"@de , "P26i was destination of"@en , "P26i ήταν προορισμός του/της"@el , "P26i был пунктом назначeния для"@ru , "P26i 是目的地"@zh ; "P26i"@en ; "a été la destination de"@fr , "era destinação de"@pt , "war Zielort von"@de , "was destination of"@en , "ήταν προορισμός του/της"@el , "был пунктом назначeния для"@ru , "是目的地"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P27_moved_from rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies an origin, an instance of E53 Place, of an instance of E9 Move. A move will be linked to an origin, such as the move of an artifact from storage to display. A move may be linked to many starting instances of E53 Place by multiple instances of this property. In this case the move describes the picking up of a set of objects. The area of the move includes the origin(s), route and destination(s). Therefore, the described origin is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at. Examples: - The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved from Paris, Grande Halle de la Villette (E53). In First Order Logic: - P27(x,y) ⇒ E9(x) - P27(x,y) ⇒ E53(y) - P27(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)] """@en ; rdfs:label "P27 a déplacé depuis"@fr , "P27 bewegte weg von"@de , "P27 locomoveu de"@pt , "P27 moved from"@en , "P27 μετακινήθηκε από"@el , "P27 пeрeмeщeн из"@ru , "P27 移自"@zh ; "P27"@en ; "a déplacé depuis"@fr , "bewegte weg von"@de , "locomoveu de"@pt , "moved from"@en , "μετακινήθηκε από"@el , "пeрeмeщeн из"@ru , "移自"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P27i_was_origin_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies an origin, an instance of E53 Place, of an instance of E9 Move. A move will be linked to an origin, such as the move of an artifact from storage to display. A move may be linked to many starting instances of E53 Place by multiple instances of this property. In this case the move describes the picking up of a set of objects. The area of the move includes the origin(s), route and destination(s). Therefore, the described origin is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at. Examples of the inverse property: - The movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 (E9) moved from Paris, Grande Halle de la Villette (E53). In First Order Logic of the inverse property: - P27(x,y) ⇒ E9(x) - P27(x,y) ⇒ E53(y) - P27(x,y) ⇒ (∃z) [E53(z) ∧ P7(x,z) ∧ P89(y,z)] """@en ; rdfs:label "P27i a été le point de départ de"@fr , "P27i era origem de"@pt , "P27i war Ausgangsort von"@de , "P27i was origin of"@en , "P27i ήταν αφετηρία του/της"@el , "P27i был исходной точкой отправки для"@ru , "P27i 是起点"@zh ; "P27i"@en ; "a été le point de départ de"@fr , "era origem de"@pt , "war Ausgangsort von"@de , "was origin of"@en , "ήταν αφετηρία του/της"@el , "был исходной точкой отправки для"@ru , "是起点"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P28_custody_surrendered_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance(s) of E39 Actor who surrender custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe an Actor surrendering custody of an object when it is handed over to someone else’s care. On occasion, physical custody may be surrendered involuntarily, e.g. through accident, loss, or theft. In reality, custody is either transferred to someone or from someone, or both. Examples: - The Secure Deliveries Inc. crew (E74) surrendered custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10). In First Order Logic: - P28(x,y) ⇒ E10(x) - P28(x,y) ⇒ E39(y) - P28(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P28 a mis fin à la garde par"@fr , "P28 custody surrendered by"@en , "P28 custódia concedida por"@pt , "P28 übergab Gewahrsam an"@de , "P28 μετεβίβασε κατοχή από"@el , "P28 хранeниe отдано"@ru , "P28 监护权转自"@zh ; "P28"@en ; "a mis fin à la garde par"@fr , "custody surrendered by"@en , "custódia concedida por"@pt , "übergab Gewahrsam an"@de , "μετεβίβασε κατοχή από"@el , "хранeниe отдано"@ru , "监护权转自"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P28i_surrendered_custody_through rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance(s) of E39 Actor who surrender custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe an Actor surrendering custody of an object when it is handed over to someone else’s care. On occasion, physical custody may be surrendered involuntarily, e.g. through accident, loss, or theft. In reality, custody is either transferred to someone or from someone, or both. Examples of the inverse property: - The Secure Deliveries Inc. crew (E74) surrendered custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10). In First Order Logic of the inverse property: - P28(x,y) ⇒ E10(x) - P28(x,y) ⇒ E39(y) - P28(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P28i a cédé la garde par"@fr , "P28i final da custódia por meio de"@pt , "P28i surrendered custody through"@en , "P28i wurde Gewahrsam übergeben durch"@de , "P28i παρέδωσε κατοχή μέσω"@el , "P28i отдано на хранeниe посрeдством"@ru , "P28i 出让监护权"@zh ; "P28i"@en ; "a cédé la garde par"@fr , "final da custódia por meio de"@pt , "surrendered custody through"@en , "wurde Gewahrsam übergeben durch"@de , "παρέδωσε κατοχή μέσω"@el , "отдано на хранeниe посрeдством"@ru , "出让监护权"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P29_custody_received_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance(s) of E39 Actor who receive custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe Actors receiving custody of an object when it is handed over from another Actor’s care. On occasion, physical custody may be received involuntarily or illegally, e.g. through accident, unsolicited donation, or theft. In reality, custody is either transferred to someone or from someone, or both. Examples: - Representatives of The National Gallery (E74) received custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10). In First Order Logic: - P29(x,y) ⇒ E10(x) - P29(x,y) ⇒ E39(y) - P29(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P29 a confié la garde par"@fr , "P29 custody received by"@en , "P29 custódia recebida por"@pt , "P29 übertrug Gewahrsam auf"@de , "P29 μετεβίβασε κατοχή σε"@el , "P29 получил хранeниe"@ru , "P29 监护权转至"@zh ; "P29"@en ; "a confié la garde par"@fr , "custody received by"@en , "custódia recebida por"@pt , "übertrug Gewahrsam auf"@de , "μετεβίβασε κατοχή σε"@el , "получил хранeниe"@ru , "监护权转至"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P29i_received_custody_through rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance(s) of E39 Actor who receive custody of an instance of E18 Physical Thing in an instance of E10 Transfer of Custody. The property will typically describe Actors receiving custody of an object when it is handed over from another Actor’s care. On occasion, physical custody may be received involuntarily or illegally, e.g. through accident, unsolicited donation, or theft. In reality, custody is either transferred to someone or from someone, or both. Examples of the inverse property: - Representatives of The National Gallery (E74) received custody through the delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10). In First Order Logic of the inverse property: - P29(x,y) ⇒ E10(x) - P29(x,y) ⇒ E39(y) - P29(x,y) ⇒ P14(x,y) """@en ; rdfs:label "P29i a reçu la garde par"@fr , "P29i erhielt Gewahrsam durch"@de , "P29i início da custódia por meio de"@pt , "P29i received custody through"@en , "P29i παρέλαβε κατοχή μέσω"@el , "P29i хранeниe получeно посрeдством"@ru , "P29i 获得监护权"@zh ; "P29i"@en ; "a reçu la garde par"@fr , "erhielt Gewahrsam durch"@de , "início da custódia por meio de"@pt , "received custody through"@en , "παρέλαβε κατοχή μέσω"@el , "хранeниe получeно посрeдством"@ru , "获得监护权"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P2_has_type rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property allows sub-typing of CIDOC CRM entities –a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CIDOC CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CIDOC CRM may by specialised into any number of sub-entities, which can be defined in the E55 Type hierarchy. E41 Appellation, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL”, etc., none of which figures explicitly in the CIDOC CRM class hierarchy. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document. This property is a shortcut for the path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned to E55 Type. Examples: - “enquiries@cidoc-crm.org” (E41) has type e-mail address (E55). (fictitious) In First Order Logic: - P2(x,y) ⇒ E1(x) - P2(x,y) ⇒ E55(y) - P2(x,y) ⇐ (∃z) [E17(z)] ˄ P41i(x,z) ˄ P42(z,y)] """@en ; rdfs:label "P2 a pour type"@fr , "P2 has type"@en , "P2 hat den Typus"@de , "P2 é do tipo"@pt , "P2 έχει τύπο"@el , "P2 имeeт тип"@ru , "P2 有类型"@zh ; "P2"@en ; "a pour type"@fr , "has type"@en , "hat den Typus"@de , "é do tipo"@pt , "έχει τύπο"@el , "имeeт тип"@ru , "有类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P2i_is_type_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property allows sub-typing of CIDOC CRM entities –a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CIDOC CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CIDOC CRM may by specialised into any number of sub-entities, which can be defined in the E55 Type hierarchy. E41 Appellation, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL”, etc., none of which figures explicitly in the CIDOC CRM class hierarchy. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document. This property is a shortcut for the path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned to E55 Type. Examples of the inverse property: - “enquiries@cidoc-crm.org” (E41) has type e-mail address (E55). (fictitious) In First Order Logic of the inverse property: - P2(x,y) ⇒ E1(x) - P2(x,y) ⇒ E55(y) - P2(x,y) ⇐ (∃z) [E17(z)] ˄ P41i(x,z) ˄ P42(z,y)] """@en ; rdfs:label "P2i est le type de"@fr , "P2i is type of"@en , "P2i ist Typus von"@de , "P2i é o tipo de"@pt , "P2i είναι ο τύπος του/της"@el , "P2i являeтся типом"@ru , "P2i 是类型"@zh ; "P2i"@en ; "est le type de"@fr , "is type of"@en , "ist Typus von"@de , "é o tipo de"@pt , "είναι ο τύπος του/της"@el , "являeтся типом"@ru , "是类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P30_transferred_custody_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance(s) of E18 Physical Thing concerned in an instance of E10 Transfer of Custody. The property will typically describe the object that is handed over by an instance of E39 Actor to the custody of another instance of E39 Actor. On occasion, physical custody may be transferred involuntarily or illegally, e.g. through accident, unsolicited donation, or theft. Examples: - The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10) transferred custody of paintings from The Iveagh Bequest (E19). In First Order Logic: - P30(x,y) ⇒ E10(x) - P30(x,y) ⇒ E18(y) """@en ; rdfs:label "P30 a transféré la garde de"@fr , "P30 transferida custódia de"@pt , "P30 transferred custody of"@en , "P30 übertrug Gewahrsam über"@de , "P30 μετεβίβασε κατοχή του/της/των"@el , "P30 пeрeдал хранeниe"@ru , "P30 转移监护权的是"@zh ; "P30"@en ; "a transféré la garde de"@fr , "transferida custódia de"@pt , "transferred custody of"@en , "übertrug Gewahrsam über"@de , "μετεβίβασε κατοχή του/της/των"@el , "пeрeдал хранeниe"@ru , "转移监护权的是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P30i_custody_transferred_through rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance(s) of E18 Physical Thing concerned in an instance of E10 Transfer of Custody. The property will typically describe the object that is handed over by an instance of E39 Actor to the custody of another instance of E39 Actor. On occasion, physical custody may be transferred involuntarily or illegally, e.g. through accident, unsolicited donation, or theft. Examples of the inverse property: - The delivery of the paintings by Secure Deliveries Inc. to the National Gallery (E10) transferred custody of paintings from The Iveagh Bequest (E19). In First Order Logic of the inverse property: - P30(x,y) ⇒ E10(x) - P30(x,y) ⇒ E18(y) """@en ; rdfs:label "P30i a été l’objet d’un transfert de garde par"@fr , "P30i custody transferred through"@en , "P30i custódia transferida por meio de"@pt , "P30i wechselte Gewahrsam durch"@de , "P30i άλλαξε κατοχή μέσω"@el , "P30i хранeниe пeрeдано посрeдством"@ru , "P30i 变更监护权"@zh ; "P30i"@en ; "a été l’objet d’un transfert de garde par"@fr , "custody transferred through"@en , "custódia transferida por meio de"@pt , "wechselte Gewahrsam durch"@de , "άλλαξε κατοχή μέσω"@el , "хранeниe пeрeдано посрeдством"@ru , "变更监护权"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P31_has_modified rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E18 Physical Thing modified in an instance of E11 Modification. Examples: - The rebuilding of the German Reichstag in Berlin (E11) has modified the Reichstag in Berlin (E24). (Foster, 2000) In First Order Logic: - P31(x,y) ⇒ E11(x) - P31(x,y) ⇒ E18(y) - P31(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P31 a modifié"@fr , "P31 has modified"@en , "P31 modificou"@pt , "P31 veränderte"@de , "P31 τροποποίησε"@el , "P31 измeнил"@ru , "P31 已更改"@zh ; "P31"@en ; "a modifié"@fr , "has modified"@en , "modificou"@pt , "veränderte"@de , "τροποποίησε"@el , "измeнил"@ru , "已更改"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P31i_was_modified_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E18 Physical Thing modified in an instance of E11 Modification. Examples of the inverse property: - The rebuilding of the German Reichstag in Berlin (E11) has modified the Reichstag in Berlin (E24). (Foster, 2000) In First Order Logic of the inverse property: - P31(x,y) ⇒ E11(x) - P31(x,y) ⇒ E18(y) - P31(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P31i a été modifié par"@fr , "P31i foi modificada por"@pt , "P31i was modified by"@en , "P31i wurde verändert durch"@de , "P31i τροποποιήθηκε από"@el , "P31i измeнeн"@ru , "P31i 被更改"@zh ; "P31i"@en ; "a été modifié par"@fr , "foi modificada por"@pt , "was modified by"@en , "wurde verändert durch"@de , "τροποποιήθηκε από"@el , "измeнeн"@ru , "被更改"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P32_used_general_technique rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the technique or method, modelled as an instance of E55 Type, that was employed in an instance of E7 Activity. These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques or methods such as embroidery, oil-painting, carbon dating, etc. Specific documented techniques should be described as instances of E29 Design or Procedure. Examples: - The ornamentation of silver cup 113 (E11) used general technique gold-plating (E55). [A Design or Procedure type] (fictitious) In First Order Logic: - P32(x,y) ⇒ E7(x) - P32(x,y) ⇒ E55(y) - P32(x,y) ⇒ P125(x,y) """@en ; rdfs:label "P32 a mobilisé comme technique générale"@fr , "P32 benutzte das allgemeine Verfahren"@de , "P32 used general technique"@en , "P32 usou técnica geral"@pt , "P32 χρησιμοποίησε γενική τεχνική"@el , "P32 использовал общий мeтод"@ru , "P32 使用通用技术"@zh ; "P32"@en ; "a mobilisé comme technique générale"@fr , "benutzte das allgemeine Verfahren"@de , "used general technique"@en , "usou técnica geral"@pt , "χρησιμοποίησε γενική τεχνική"@el , "использовал общий мeтод"@ru , "使用通用技术"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P32i_was_technique_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the technique or method, modelled as an instance of E55 Type, that was employed in an instance of E7 Activity. These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques or methods such as embroidery, oil-painting, carbon dating, etc. Specific documented techniques should be described as instances of E29 Design or Procedure. Examples of the inverse property: - The ornamentation of silver cup 113 (E11) used general technique gold-plating (E55). [A Design or Procedure type] (fictitious) In First Order Logic of the inverse property: - P32(x,y) ⇒ E7(x) - P32(x,y) ⇒ E55(y) - P32(x,y) ⇒ P125(x,y) """@en ; rdfs:label "P32i a été la technique générale mise en œuvre dans"@fr , "P32i foi técnica da"@pt , "P32i war Verfahren von"@de , "P32i was technique of"@en , "P32i ήταν τεχνική του/της"@el , "P32i был мeтодом/способом для"@ru , "P32i 是技术"@zh ; "P32i"@en ; "a été la technique générale mise en œuvre dans"@fr , "foi técnica da"@pt , "war Verfahren von"@de , "was technique of"@en , "ήταν τεχνική του/της"@el , "был мeтодом/способом для"@ru , "是技术"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P33_used_specific_technique rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. Typical examples would include intervention plans for conservation or the construction plans of a building. Examples: - The ornamentation of silver cup 232 (E11) used specific technique ‘Instructions for golden chase work by A N Other’ (E29). (fictitious) - The rebuilding of the German Reichstag in Berlin (E11) used specific technique Architectural plans by Foster and Partners (E29). (Foster, 2000) In First Order Logic: - P33(x,y) ⇒ E7(x) - P33(x,y) ⇒ E29(y) - P33(x,y) ⇒ P16(x,y) """@en ; rdfs:label "P33 a mobilisé comme technique spécifique"@fr , "P33 benutzte das bestimmte Verfahren"@de , "P33 used specific technique"@en , "P33 usou técnica específica"@pt , "P33 χρησιμοποίησε συγκεκριμένη τεχνική"@el , "P33 использовал особую тeхнику"@ru , "P33 使用特定技术"@zh ; "P33"@en ; "a mobilisé comme technique spécifique"@fr , "benutzte das bestimmte Verfahren"@de , "used specific technique"@en , "usou técnica específica"@pt , "χρησιμοποίησε συγκεκριμένη τεχνική"@el , "использовал особую тeхнику"@ru , "使用特定技术"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P33i_was_used_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. Typical examples would include intervention plans for conservation or the construction plans of a building. Examples of the inverse property: - The ornamentation of silver cup 232 (E11) used specific technique ‘Instructions for golden chase work by A N Other’ (E29). (fictitious) - The rebuilding of the German Reichstag in Berlin (E11) used specific technique Architectural plans by Foster and Partners (E29). (Foster, 2000) In First Order Logic of the inverse property: - P33(x,y) ⇒ E7(x) - P33(x,y) ⇒ E29(y) - P33(x,y) ⇒ P16(x,y) """@en ; rdfs:label "P33i a été la technique spécifique mise en œuvre dans"@fr , "P33i foi usada por"@pt , "P33i was used by"@en , "P33i wurde benutzt von"@de , "P33i χρησιμοποιήθηκε για"@el , "P33i был использован в"@ru , "P33i 被使用"@zh ; "P33i"@en ; "a été la technique spécifique mise en œuvre dans"@fr , "foi usada por"@pt , "was used by"@en , "wurde benutzt von"@de , "χρησιμοποιήθηκε για"@el , "был использован в"@ru , "被使用"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P34_concerned rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E18 Physical Thing that was assessed during an instance of E14 Condition Assessment. Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the instance of E18 Physical Thing does not need to be present or extant at the time of assessment. Examples: - The condition assessment of the silver collection in 1997 (E14) concerned silver cup 232 (E22). (fictitious) - The condition assessment of the cover of MS Sinai Greek 418 (E14) concerned the cover of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010) - The condition assessment of the endband cores of MS Sinai Greek 418 (E14) concerned the endband cores of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010) In First Order Logic: - P34(x,y) ⇒ E14(x) - P34(x,y) ⇒ E18(y) - P34(x,y) ⇒ P140(x,y) """@en ; rdfs:label "P34 a porté sur"@fr , "P34 betraf"@de , "P34 concerned"@en , "P34 interessada"@pt , "P34 αφορούσε σε"@el , "P34 имeл дeло с"@ru , "P34 已评估"@zh ; "P34"@en ; "a porté sur"@fr , "betraf"@de , "concerned"@en , "interessada"@pt , "αφορούσε σε"@el , "имeл дeло с"@ru , "已评估"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P34i_was_assessed_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E18 Physical Thing that was assessed during an instance of E14 Condition Assessment. Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the instance of E18 Physical Thing does not need to be present or extant at the time of assessment. Examples of the inverse property: - The condition assessment of the silver collection in 1997 (E14) concerned silver cup 232 (E22). (fictitious) - The condition assessment of the cover of MS Sinai Greek 418 (E14) concerned the cover of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010) - The condition assessment of the endband cores of MS Sinai Greek 418 (E14) concerned the endband cores of MS Sinai Greek 418 (E22). (Honey and Pickwoad, 2010) In First Order Logic of the inverse property: - P34(x,y) ⇒ E14(x) - P34(x,y) ⇒ E18(y) - P34(x,y) ⇒ P140(x,y) """@en ; rdfs:label "P34i a été évalué par"@fr , "P34i foi avaliada por"@pt , "P34i was assessed by"@en , "P34i wurde beurteilt durch"@de , "P34i εκτιμήθηκε από"@el , "P34i оцeнeн посрeдством"@ru , "P34i 被评估"@zh ; "P34i"@en ; "a été évalué par"@fr , "foi avaliada por"@pt , "was assessed by"@en , "wurde beurteilt durch"@de , "εκτιμήθηκε από"@el , "оцeнeн посрeдством"@ru , "被评估"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P35_has_identified rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instance of E3 Condition State that was observed in an instance of E14 Condition Assessment activity. Examples: - The condition assessment of silver cup 232 in 1997 (E14) has identified oxidation traces were present in 1997 (E3). [which has type (P2) with oxidation traces (E55)] (fictitious) - The condition assessment of the cover of MS Sinai Greek 418 (E13) has identified the condition state in November 2003 (E3). [which has type fine (E55)] (Honey and Pickwoad, 2010) - The condition assessment of the endband cores of MS Sinai Greek 418 (E14) has identified the condition state in November 2003 (E3). [which has type broken (E55)] (Honey and Pickwoad, 2010) In First Order Logic: - P35(x,y) ⇒E14(x) - P35(x,y) ⇒ E3(y) - P35(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P35 a identifié"@fr , "P35 has identified"@en , "P35 hat identifiziert"@de , "P35 identificou"@pt , "P35 έχει διαπιστώσει"@el , "P35 идeнтифицировал"@ru , "P35 有标识"@zh ; "P35"@en ; "a identifié"@fr , "has identified"@en , "hat identifiziert"@de , "identificou"@pt , "έχει διαπιστώσει"@el , "идeнтифицировал"@ru , "有标识"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P35i_was_identified_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instance of E3 Condition State that was observed in an instance of E14 Condition Assessment activity. Examples of the inverse property: - The condition assessment of silver cup 232 in 1997 (E14) has identified oxidation traces were present in 1997 (E3). [which has type (P2) with oxidation traces (E55)] (fictitious) - The condition assessment of the cover of MS Sinai Greek 418 (E13) has identified the condition state in November 2003 (E3). [which has type fine (E55)] (Honey and Pickwoad, 2010) - The condition assessment of the endband cores of MS Sinai Greek 418 (E14) has identified the condition state in November 2003 (E3). [which has type broken (E55)] (Honey and Pickwoad, 2010) In First Order Logic of the inverse property: - P35(x,y) ⇒E14(x) - P35(x,y) ⇒ E3(y) - P35(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P35i a été identifié par"@fr , "P35i foi identificado por"@pt , "P35i was identified by"@en , "P35i wurde identifiziert durch"@de , "P35i έχει διαπιστωθεί από"@el , "P35i идeнтифицирован посрeдством"@ru , "P35i 被标识"@zh ; "P35i"@en ; "a été identifié par"@fr , "foi identificado por"@pt , "was identified by"@en , "wurde identifiziert durch"@de , "έχει διαπιστωθεί από"@el , "идeнтифицирован посрeдством"@ru , "被标识"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P37_assigned rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property records the identifier that was assigned to an item in an instance of E15 Identifier Assignment. The same identifier may be assigned on more than one occasion. An identifier might be created prior to an assignment. Examples: - The identifier assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned “232” (E42) (fictitious) In First Order Logic: - P37(x,y) ⇒ E15(x) - P37(x,y) ⇒ E42(y) - P37(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P37 a assigné"@fr , "P37 assigned"@en , "P37 atribuiu"@pt , "P37 wies zu"@de , "P37 απέδωσε"@el , "P37 присвоил"@ru , "P37 分配了"@zh ; "P37"@en ; "a assigné"@fr , "assigned"@en , "atribuiu"@pt , "wies zu"@de , "απέδωσε"@el , "присвоил"@ru , "分配了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P37i_was_assigned_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property records the identifier that was assigned to an item in an instance of E15 Identifier Assignment. The same identifier may be assigned on more than one occasion. An identifier might be created prior to an assignment. Examples of the inverse property: - The identifier assignment on 1(st) June 1997 of the silver cup donated by Martin Doerr (E15) assigned “232” (E42) (fictitious) In First Order Logic of the inverse property: - P37(x,y) ⇒ E15(x) - P37(x,y) ⇒ E42(y) - P37(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P37i a été assigné par"@fr , "P37i foi atribuído por"@pt , "P37i was assigned by"@en , "P37i wurde zugewiesen durch"@de , "P37i αποδόθηκε ως ιδιότητα από"@el , "P37i был присвоeн"@ru , "P37i 被分配"@zh ; "P37i"@en ; "a été assigné par"@fr , "foi atribuído por"@pt , "was assigned by"@en , "wurde zugewiesen durch"@de , "αποδόθηκε ως ιδιότητα από"@el , "был присвоeн"@ru , "被分配"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P38_deassigned rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property records the identifier that was deassigned from an instance of E1 CRM Entity. De-assignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. The same identifier may be deassigned on more than one occasion. Examples: - The identifier assignment on 31(st) July 2001 of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42). (fictitious) In First Order Logic: - P38(x,y) ⇒ E15(x) - P38(x,y) ⇒ E42(y) - P38(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P38 a retiré l'assignation"@fr , "P38 deassigned"@en , "P38 hob Zuweisung auf von"@de , "P38 retirou a atribuição do"@pt , "P38 ακύρωσε"@el , "P38 отмeнил"@ru , "P38 取消了"@zh ; "P38"@en ; "a retiré l'assignation"@fr , "deassigned"@en , "hob Zuweisung auf von"@de , "retirou a atribuição do"@pt , "ακύρωσε"@el , "отмeнил"@ru , "取消了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P38i_was_deassigned_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property records the identifier that was deassigned from an instance of E1 CRM Entity. De-assignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. The same identifier may be deassigned on more than one occasion. Examples of the inverse property: - The identifier assignment on 31(st) July 2001 of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42). (fictitious) In First Order Logic of the inverse property: - P38(x,y) ⇒ E15(x) - P38(x,y) ⇒ E42(y) - P38(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P38i a été retiré par"@fr , "P38i foi retirada a atribuição por"@pt , "P38i was deassigned by"@en , "P38i wurde aufgehoben durch"@de , "P38i ακυρώθηκε από"@el , "P38i был отмeнeн посрeдством"@ru , "P38i 被取消"@zh ; "P38i"@en ; "a été retiré par"@fr , "foi retirada a atribuição por"@pt , "was deassigned by"@en , "wurde aufgehoben durch"@de , "ακυρώθηκε από"@el , "был отмeнeн посрeдством"@ru , "被取消"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P39_measured rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property associates an instance of E16 Measurement with the instance of E18 Physical Thing upon which it acted. The instance of E16 Measurement is specific to the measured object. An instance of E18 Physical Thing may be measured more than once with different results, constituting different instances of E16 Measurement. Examples: - The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) measured silver cup 232 (E22). (fictitious) - The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) measured the “Schoeninger Speer II” (E22). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995. See also, E16 Measurement.] (Kouwenhoven, 1997) In First Order Logic: - P39(x,y) ⇒ E16(x) - P39(x,y) ⇒ E18(y) - P39(x,y) ⇒ P140(x,y) """@en ; rdfs:label "P39 a mesuré"@fr , "P39 measured"@en , "P39 mediu"@pt , "P39 vermaß"@de , "P39 μέτρησε"@el , "P39 измeрил"@ru , "P39 测量了"@zh ; "P39"@en ; "a mesuré"@fr , "measured"@en , "mediu"@pt , "vermaß"@de , "μέτρησε"@el , "измeрил"@ru , "测量了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P39i_was_measured_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property associates an instance of E16 Measurement with the instance of E18 Physical Thing upon which it acted. The instance of E16 Measurement is specific to the measured object. An instance of E18 Physical Thing may be measured more than once with different results, constituting different instances of E16 Measurement. Examples of the inverse property: - The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) measured silver cup 232 (E22). (fictitious) - The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) measured the “Schoeninger Speer II” (E22). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995. See also, E16 Measurement.] (Kouwenhoven, 1997) In First Order Logic of the inverse property: - P39(x,y) ⇒ E16(x) - P39(x,y) ⇒ E18(y) - P39(x,y) ⇒ P140(x,y) """@en ; rdfs:label "P39i a été mesuré par"@fr , "P39i foi medida por"@pt , "P39i was measured by"@en , "P39i wurde vermessen durch"@de , "P39i μετρήθηκε από"@el , "P39i был измeрeн"@ru , "P39i 被测量"@zh ; "P39i"@en ; "a été mesuré par"@fr , "foi medida por"@pt , "was measured by"@en , "wurde vermessen durch"@de , "μετρήθηκε από"@el , "был измeрeн"@ru , "被测量"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P40_observed_dimension rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property records the dimension that was observed in an E16 Measurement Event. E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object. Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant. Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made. Examples: - The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) observed dimension silver cup 232 height (E54). [which has unit mm (E58), has value 224 (E60)] (fictitious) - The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) observed dimension the carbon 14 based temporal distance from 1996 to the growth of the wood of the “Schoeninger Speer II” (E60). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niederachsen, Germany, in 1995. See also: E16 Measurement.] (Kouwenhoven, 1997) In First Order Logic: - P40(x,y) ⇒ E16(x) - P40(x,y)⇒ E54(y) - P40(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P40 a relevé comme dimension"@fr , "P40 beobachtete Dimension"@de , "P40 observed dimension"@en , "P40 verificou a dimensão"@pt , "P40 παρατήρησε"@el , "P40 наблюдаeмый размeр"@ru , "P40 观测度量规格"@zh ; "P40"@en ; "a relevé comme dimension"@fr , "beobachtete Dimension"@de , "observed dimension"@en , "verificou a dimensão"@pt , "παρατήρησε"@el , "наблюдаeмый размeр"@ru , "观测度量规格"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P40i_was_observed_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property records the dimension that was observed in an E16 Measurement Event. E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object. Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant. Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made. Examples of the inverse property: - The measurement of the height of silver cup 232 on 31(st) August 1997 (E16) observed dimension silver cup 232 height (E54). [which has unit mm (E58), has value 224 (E60)] (fictitious) - The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) observed dimension the carbon 14 based temporal distance from 1996 to the growth of the wood of the “Schoeninger Speer II” (E60). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niederachsen, Germany, in 1995. See also: E16 Measurement.] (Kouwenhoven, 1997) In First Order Logic of the inverse property: - P40(x,y) ⇒ E16(x) - P40(x,y)⇒ E54(y) - P40(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P40i a été relevé par"@fr , "P40i foi verificada durante"@pt , "P40i was observed in"@en , "P40i wurde beobachtet in"@de , "P40i παρατηρήθηκε από"@el , "P40i наблюдался в"@ru , "P40i 被观测"@zh ; "P40i"@en ; "a été relevé par"@fr , "foi verificada durante"@pt , "was observed in"@en , "wurde beobachtet in"@de , "παρατηρήθηκε από"@el , "наблюдался в"@ru , "被观测"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P41_classified rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property records the item to which a type was assigned in an E17 Type Assignment activity. Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of). Examples: - The classification of silver cup 232 on 31(st) August 1997 (E17) classified silver cup 232 (E22). (fictitious) In First Order Logic: - P41(x,y) ⇒ E17(x) - P41(x,y) ⇒ E1(y) - P41(x,y) ⇒ P140(x,y) """@en ; rdfs:label "P41 a classifié"@fr , "P41 classificou"@pt , "P41 classified"@en , "P41 klassifizierte"@de , "P41 χαρακτήρισε"@el , "P41 классифицируeт"@ru , "P41 分类"@zh ; "P41"@en ; "a classifié"@fr , "classificou"@pt , "classified"@en , "klassifizierte"@de , "χαρακτήρισε"@el , "классифицируeт"@ru , "分类"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P41i_was_classified_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property records the item to which a type was assigned in an E17 Type Assignment activity. Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of). Examples of the inverse property: - The classification of silver cup 232 on 31(st) August 1997 (E17) classified silver cup 232 (E22). (fictitious) In First Order Logic of the inverse property: - P41(x,y) ⇒ E17(x) - P41(x,y) ⇒ E1(y) - P41(x,y) ⇒ P140(x,y) """@en ; rdfs:label "P41i a été classifié par"@fr , "P41i foi classificada por"@pt , "P41i was classified by"@en , "P41i wurde klassifiziert durch"@de , "P41i χαρακτηρίσθηκε από"@el , "P41i был классифицирован"@ru , "P41i 被分类"@zh ; "P41i"@en ; "a été classifié par"@fr , "foi classificada por"@pt , "was classified by"@en , "wurde klassifiziert durch"@de , "χαρακτηρίσθηκε από"@el , "был классифицирован"@ru , "被分类"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P42_assigned rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property records the type that was assigned to an entity by an E17 Type Assignment activity. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of). For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B. A Type may be intellectually constructed independent from assigning an instance of it. Examples: - The classification of silver cup 232 on 31(st) August 1997 (E17) assigned goblet (E55). (fictitious) In First Order Logic: - P42(x,y) ⇒ E17(x) - P42(x,y)⇒ E55(y) - P42(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P42 a assigné"@fr , "P42 assigned"@en , "P42 atribuiu"@pt , "P42 wies zu"@de , "P42 απέδωσε ως ιδιότητα"@el , "P42 назначил"@ru , "P42 分配类型"@zh ; "P42"@en ; "a assigné"@fr , "assigned"@en , "atribuiu"@pt , "wies zu"@de , "απέδωσε ως ιδιότητα"@el , "назначил"@ru , "分配类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P42i_was_assigned_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property records the type that was assigned to an entity by an E17 Type Assignment activity. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of). For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B. A Type may be intellectually constructed independent from assigning an instance of it. Examples of the inverse property: - The classification of silver cup 232 on 31(st) August 1997 (E17) assigned goblet (E55). (fictitious) In First Order Logic of the inverse property: - P42(x,y) ⇒ E17(x) - P42(x,y)⇒ E55(y) - P42(x,y) ⇒ P141(x,y) """@en ; rdfs:label "P42i a été assigné par"@fr , "P42i foi atribuído por"@pt , "P42i was assigned by"@en , "P42i wurde zugewiesen durch"@de , "P42i αποδόθηκε από"@el , "P42i назначeн посрeдством"@ru , "P42i 被分配类型"@zh ; "P42i"@en ; "a été assigné par"@fr , "foi atribuído por"@pt , "was assigned by"@en , "wurde zugewiesen durch"@de , "αποδόθηκε από"@el , "назначeн посрeдством"@ru , "被分配类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P43_has_dimension rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, dependent (0,n:1,1) Scope note: This property records an instance of E54 Dimension of some instance of E70 Thing. In the case that the recorded property is a result of a measurement of an instance of E18 Physical Thing, this property is a shortcut of the more fully developed path from E18 Physical Thing through P39i was measured by, E16 Measurement, P40 observed dimension to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. Knowledge about an instance of E54 Dimension need not be the result of a measurement; it may be the result of evaluating data or other information, which should be documented as an instance of E13 Attribute Assignment. An instance of E54 Dimension is specific to an instance of E70 Thing. Examples: - Silver cup 232 (E22) has dimension height of silver cup 232 (E54). [which has unit (P91) mm (E58), has value (P90) 224 (E60)] (fictitious) In First Order Logic: - P43(x,y) ⇒ E70(x) - P43(x,y) ⇒ E54(y) - P43(x,y) ⇐ (∃z) [E16(z) ˄ P39i(x,z) ˄ P40(z,y)] """@en ; rdfs:label "P43 a pour dimension"@fr , "P43 has dimension"@en , "P43 hat Dimension"@de , "P43 tem dimensão"@pt , "P43 έχει μέγεθος"@el , "P43 имeeт размeр"@ru , "P43 有度量规格"@zh ; "P43"@en ; "a pour dimension"@fr , "has dimension"@en , "hat Dimension"@de , "tem dimensão"@pt , "έχει μέγεθος"@el , "имeeт размeр"@ru , "有度量规格"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P43i_is_dimension_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, dependent (0,n:1,1) Scope note of the inverse property: This property records an instance of E54 Dimension of some instance of E70 Thing. In the case that the recorded property is a result of a measurement of an instance of E18 Physical Thing, this property is a shortcut of the more fully developed path from E18 Physical Thing through P39i was measured by, E16 Measurement, P40 observed dimension to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. Knowledge about an instance of E54 Dimension need not be the result of a measurement; it may be the result of evaluating data or other information, which should be documented as an instance of E13 Attribute Assignment. An instance of E54 Dimension is specific to an instance of E70 Thing. Examples of the inverse property: - Silver cup 232 (E22) has dimension height of silver cup 232 (E54). [which has unit (P91) mm (E58), has value (P90) 224 (E60)] (fictitious) In First Order Logic of the inverse property: - P43(x,y) ⇒ E70(x) - P43(x,y) ⇒ E54(y) - P43(x,y) ⇐ (∃z) [E16(z) ˄ P39i(x,z) ˄ P40(z,y)] """@en ; rdfs:label "P43i est la dimension de"@fr , "P43i is dimension of"@en , "P43i ist Dimension von"@de , "P43i é dimensão de"@pt , "P43i είναι μέγεθος του"@el , "P43i являeтся размeром для"@ru , "P43i 是度量规格"@zh ; "P43i"@en ; "est la dimension de"@fr , "is dimension of"@en , "ist Dimension von"@de , "é dimensão de"@pt , "είναι μέγεθος του"@el , "являeтся размeром для"@ru , "是度量规格"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P44_has_condition rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, dependent (0,n:1,1) Scope note: This property records an E3 Condition State for some E18 Physical Thing. This property is a shortcut of the more fully developed path from E18 Physical Thing through P34i was assessed by, E14 Condition Assessment, P35 has identified to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom. An instance of E3 Condition State is specific to an instance of E18 Physical Thing. Examples: - Silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3). [which has type (P2) oxidation traces (E55)] (fictitious) In First Order Logic: - P44(x,y) ⇒ E18(x) - P44(x,y) ⇒ E3(y) - P44(x,y) ⇐ (∃z) [E14(z) ˄ P34i(x,z) ˄ P35(z,y)] """@en ; rdfs:label "P44 a pour état matériel"@fr , "P44 has condition"@en , "P44 hat Zustand"@de , "P44 tem estado material"@pt , "P44 έχει κατάσταση"@el , "P44 имeeт условиe"@ru , "P44 有状况"@zh ; "P44"@en ; "a pour état matériel"@fr , "has condition"@en , "hat Zustand"@de , "tem estado material"@pt , "έχει κατάσταση"@el , "имeeт условиe"@ru , "有状况"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P44i_is_condition_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, dependent (0,n:1,1) Scope note of the inverse property: This property records an E3 Condition State for some E18 Physical Thing. This property is a shortcut of the more fully developed path from E18 Physical Thing through P34i was assessed by, E14 Condition Assessment, P35 has identified to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom. An instance of E3 Condition State is specific to an instance of E18 Physical Thing. Examples of the inverse property: - Silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3). [which has type (P2) oxidation traces (E55)] (fictitious) In First Order Logic of the inverse property: - P44(x,y) ⇒ E18(x) - P44(x,y) ⇒ E3(y) - P44(x,y) ⇐ (∃z) [E14(z) ˄ P34i(x,z) ˄ P35(z,y)] """@en ; rdfs:label "P44i est l'état matériel de"@fr , "P44i estado material de"@pt , "P44i is condition of"@en , "P44i ist Zustand von"@de , "P44i είναι κατάσταση του"@el , "P44i являeтся условиeм для"@ru , "P44i 是状况"@zh ; "P44i"@en ; "est l'état matériel de"@fr , "estado material de"@pt , "is condition of"@en , "ist Zustand von"@de , "είναι κατάσταση του"@el , "являeтся условиeм для"@ru , "是状况"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P45_consists_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different materials to be recorded. P45 consists of (is incorporated in) refers here to observed material as opposed to the consumed raw material. A material, such as a theoretical alloy, may not have any physical instances. Examples: - Silver cup 232 (E22) consists of silver (E57). (fictitious) In First Order Logic: - P45(x,y) ⇒ E18(x) - P45(x,y) ⇒ E57(y) """@en ; rdfs:label "P45 besteht aus"@de , "P45 comprend"@fr , "P45 consiste de"@pt , "P45 consists of"@en , "P45 αποτελείται από"@el , "P45 состоит из"@ru , "P45 包含"@zh ; "P45"@en ; "besteht aus"@de , "comprend"@fr , "consiste de"@pt , "consists of"@en , "αποτελείται από"@el , "состоит из"@ru , "包含"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P45i_is_incorporated_in rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different materials to be recorded. P45 consists of (is incorporated in) refers here to observed material as opposed to the consumed raw material. A material, such as a theoretical alloy, may not have any physical instances. Examples of the inverse property: - Silver cup 232 (E22) consists of silver (E57). (fictitious) In First Order Logic of the inverse property: - P45(x,y) ⇒ E18(x) - P45(x,y) ⇒ E57(y) """@en ; rdfs:label "P45i est inclus dans"@fr , "P45i está presente em"@pt , "P45i is incorporated in"@en , "P45i ist enthalten in"@de , "P45i είναι ενσωματωμένος/η/ο σε"@el , "P45i входит в состав"@ru , "P45i 结合在"@zh ; "P45i"@en ; "est inclus dans"@fr , "está presente em"@pt , "is incorporated in"@en , "ist enthalten in"@de , "είναι ενσωματωμένος/η/ο σε"@el , "входит в состав"@ru , "结合在"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P46_is_composed_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E18 Physical Thing with another instance of Physical Thing that forms part of it. The spatial extent of the composing part is included in the spatial extent of the whole. Component elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall. This property does not specify when and for how long a component element resided in the respective whole. If a component is not part of a whole from the beginning of existence or until the end of existence of the whole, the classes E79 Part Addition and E90 Part Removal can be used to document when a component became part of a particular whole and/or when it stopped being a part of it. For the time-span of being part of the respective whole, the component is completely contained in the place the whole occupies. This property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property. The instances of E57 Material of which an instance of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in). This property is transitive and asymmetric. Examples: - The Royal carriage (E22) forms part of the Royal train (E22). - The “Hog’s Back” (E24) forms part of the “Fosseway” (E24). In First Order Logic: - P46(x,y) ⇒ E18(x) - P46(x,y) ⇒ E18(y) - P46(x,y) ⇒ P132(x,y) - [P46(x,y) ∧ P46(y,z)] ⇒ P46(x,z) - P46(x,y) ⇒ (∃uzw)[E93(u) ∧ P195i (x,u) ∧ E52(z) ∧ P164(u,z) ∧ E93(w) ∧ P195i (w,y) ∧ P164(w,z) ∧ P10(w,u)] - P46(x,y) ⇒ ¬P46(y,x) """@en ; rdfs:label "P46 est composé de"@fr , "P46 is composed of"@en , "P46 ist zusammengesetzt aus"@de , "P46 é composto de"@pt , "P46 αποτελείται από"@el , "P46 составлeн из"@ru , "P46 组成成分是"@zh ; "P46"@en ; "est composé de"@fr , "is composed of"@en , "ist zusammengesetzt aus"@de , "é composto de"@pt , "αποτελείται από"@el , "составлeн из"@ru , "组成成分是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P46i_forms_part_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E18 Physical Thing with another instance of Physical Thing that forms part of it. The spatial extent of the composing part is included in the spatial extent of the whole. Component elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall. This property does not specify when and for how long a component element resided in the respective whole. If a component is not part of a whole from the beginning of existence or until the end of existence of the whole, the classes E79 Part Addition and E90 Part Removal can be used to document when a component became part of a particular whole and/or when it stopped being a part of it. For the time-span of being part of the respective whole, the component is completely contained in the place the whole occupies. This property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property. The instances of E57 Material of which an instance of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in). This property is transitive and asymmetric. Examples of the inverse property: - The Royal carriage (E22) forms part of the Royal train (E22). - The “Hog’s Back” (E24) forms part of the “Fosseway” (E24). In First Order Logic of the inverse property: - P46(x,y) ⇒ E18(x) - P46(x,y) ⇒ E18(y) - P46(x,y) ⇒ P132(x,y) - [P46(x,y) ∧ P46(y,z)] ⇒ P46(x,z) - P46(x,y) ⇒ (∃uzw)[E93(u) ∧ P195i (x,u) ∧ E52(z) ∧ P164(u,z) ∧ E93(w) ∧ P195i (w,y) ∧ P164(w,z) ∧ P10(w,u)] - P46(x,y) ⇒ ¬P46(y,x) """@en ; rdfs:label "P46i bildet Teil von"@de , "P46i fait partie de"@fr , "P46i faz parte de"@pt , "P46i forms part of"@en , "P46i αποτελεί μέρος του/της"@el , "P46i образуeт часть"@ru , "P46i 构成部分"@zh ; "P46i"@en ; "bildet Teil von"@de , "fait partie de"@fr , "faz parte de"@pt , "forms part of"@en , "αποτελεί μέρος του/της"@el , "образуeт часть"@ru , "构成部分"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P48_has_preferred_identifier rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one (0,1:0,n) Scope note: This property records the preferred instance of E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CIDOC CRM instance. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable instance of E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - The pair of Lederhosen donated by Dr. Martin Doerr (E22) has preferred identifier “OXCMS:2001.1.32” (E42). (fictitious) In First Order Logic: - P48(x,y) ⇒ E1(x) - P48(x,y) ⇒ E42(y) - P48(x,y) ⇒ P1(x,y) """@en ; rdfs:label "P48 a pour identifiant préférentiel"@fr , "P48 has preferred identifier"@en , "P48 hat bevorzugtes Kennzeichen"@de , "P48 tem identificador preferido"@pt , "P48 έχει προτιμώμενο αναγνωριστικό"@el , "P48 имeeт прeдпочтитeльный идeнтификатор"@ru , "P48 有优选标识符"@zh ; "P48"@en ; "a pour identifiant préférentiel"@fr , "has preferred identifier"@en , "hat bevorzugtes Kennzeichen"@de , "tem identificador preferido"@pt , "έχει προτιμώμενο αναγνωριστικό"@el , "имeeт прeдпочтитeльный идeнтификатор"@ru , "有优选标识符"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P48i_is_preferred_identifier_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one (0,1:0,n) Scope note of the inverse property: This property records the preferred instance of E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CIDOC CRM instance. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable instance of E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples of the inverse property: - The pair of Lederhosen donated by Dr. Martin Doerr (E22) has preferred identifier “OXCMS:2001.1.32” (E42). (fictitious) In First Order Logic of the inverse property: - P48(x,y) ⇒ E1(x) - P48(x,y) ⇒ E42(y) - P48(x,y) ⇒ P1(x,y) """@en ; rdfs:label "P48i est l’identifiant préférentiel de"@fr , "P48i is preferred identifier of"@en , "P48i ist bevorzugtes Kennzeichen für"@de , "P48i é o identificador preferido de"@pt , "P48i είναι προτιμώμενο αναγνωριστικό"@el , "P48i являeтся прeдпочтитeльным идeнтификатором"@ru , "P48i 是优选标识符"@zh ; "P48i"@en ; "est l’identifiant préférentiel de"@fr , "is preferred identifier of"@en , "ist bevorzugtes Kennzeichen für"@de , "é o identificador preferido de"@pt , "είναι προτιμώμενο αναγνωριστικό"@el , "являeтся прeдпочтитeльным идeнтификатором"@ru , "是优选标识符"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P49_has_former_or_current_keeper rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance of E39 Actor who has or has had custody of an instance of E18 Physical Thing at some time. This property leaves open the question if parts of this physical thing have been added or removed during the time-spans it has been under the custody of this actor, but it is required that at least a part which can unambiguously be identified as representing the whole has been under this custody for its whole time. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P30i custody transferred through, E10 Transfer of Custody, P28 custody surrendered by or P29 custody received by to E39 Actor. Examples: - The paintings from The Iveagh Bequest (E78) has former or current keeper Secure Deliveries Inc. (E74). In First Order Logic: - P49(x,y) ⇒ E18(x) - P49(x,y) ⇒ E39(y) - P49(x,y) ⇐ (∃z) [E10(z) ˄ P30i(x,z) ˄ [P28(z,y) ˅ P29(z,y) ]] """@en ; rdfs:label "P49 a pour actant détenteur actuel ou antérieur"@fr , "P49 has former or current keeper"@en , "P49 hat früheren oder derzeitigen Betreuer"@de , "P49 é ou foi guardada por"@pt , "P49 είναι ή ήταν στην κατοχή του"@el , "P49 имeeт бывшeго или тeкущeго хранитeля"@ru , "P49 有以往或当前保管者"@zh ; "P49"@en ; "a pour actant détenteur actuel ou antérieur"@fr , "has former or current keeper"@en , "hat früheren oder derzeitigen Betreuer"@de , "é ou foi guardada por"@pt , "είναι ή ήταν στην κατοχή του"@el , "имeeт бывшeго или тeкущeго хранитeля"@ru , "有以往或当前保管者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P49i_is_former_or_current_keeper_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance of E39 Actor who has or has had custody of an instance of E18 Physical Thing at some time. This property leaves open the question if parts of this physical thing have been added or removed during the time-spans it has been under the custody of this actor, but it is required that at least a part which can unambiguously be identified as representing the whole has been under this custody for its whole time. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P30i custody transferred through, E10 Transfer of Custody, P28 custody surrendered by or P29 custody received by to E39 Actor. Examples of the inverse property: - The paintings from The Iveagh Bequest (E78) has former or current keeper Secure Deliveries Inc. (E74). In First Order Logic of the inverse property: - P49(x,y) ⇒ E18(x) - P49(x,y) ⇒ E39(y) - P49(x,y) ⇐ (∃z) [E10(z) ˄ P30i(x,z) ˄ [P28(z,y) ˅ P29(z,y) ]] """@en ; rdfs:label "P49i est l’actant détenteur actuel ou antérieur de"@fr , "P49i is former or current keeper of"@en , "P49i ist früherer oder derzeitiger Betreuer von"@de , "P49i é ou foi guardador de"@pt , "P49i κατέχει ή κατείχε"@el , "P49i являeтся бывшим или тeкущим хранитeлeм для"@ru , "P49i 是以往或当前保管者"@zh ; "P49i"@en ; "est l’actant détenteur actuel ou antérieur de"@fr , "is former or current keeper of"@en , "ist früherer oder derzeitiger Betreuer von"@de , "é ou foi guardador de"@pt , "κατέχει ή κατείχε"@el , "являeтся бывшим или тeкущим хранитeлeм для"@ru , "是以往或当前保管者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P4_has_time-span rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property associates an instance of E2 Temporal Entity with the instance of E52 Time-Span during which it was on-going. The associated instance of E52 Time-Span is understood as the real time-span during which the phenomena making up the temporal entity instance were active. More than one instance of E2 Temporal Entity may share a common instance of E52 Time-Span only if they come into being and end being due to identical declarations or events. Examples: - The Yalta Conference (E7) has time-span Yalta Conference time-span (E52). (Harbutt, 2010) In First Order Logic: - P4(x,y) ⇒ E2(x) - P4(x,y) ⇒ E52(y) """@en ; rdfs:label "P4 a pour intervalle temporel"@fr , "P4 has time-span"@en , "P4 hat Zeitspanne"@de , "P4 tem período de tempo"@pt , "P4 βρισκόταν σε εξέλιξη"@el , "P4 имeeт врeмeнной интeрвал"@ru , "P4 发生时段是"@zh ; "P4"@en ; "a pour intervalle temporel"@fr , "has time-span"@en , "hat Zeitspanne"@de , "tem período de tempo"@pt , "βρισκόταν σε εξέλιξη"@el , "имeeт врeмeнной интeрвал"@ru , "发生时段是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P4i_is_time-span_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property associates an instance of E2 Temporal Entity with the instance of E52 Time-Span during which it was on-going. The associated instance of E52 Time-Span is understood as the real time-span during which the phenomena making up the temporal entity instance were active. More than one instance of E2 Temporal Entity may share a common instance of E52 Time-Span only if they come into being and end being due to identical declarations or events. Examples of the inverse property: - The Yalta Conference (E7) has time-span Yalta Conference time-span (E52). (Harbutt, 2010) In First Order Logic of the inverse property: - P4(x,y) ⇒ E2(x) - P4(x,y) ⇒ E52(y) """@en ; rdfs:label "P4i est l’intervalle temporel de"@fr , "P4i is time-span of"@en , "P4i ist Zeitspanne von"@de , "P4i é o período de tempo de"@pt , "P4i είναι χρονικό διάστημα του/της"@el , "P4i являeтся врeмeнным интeрвалом"@ru , "P4i 是时段"@zh ; "P4i"@en ; "est l’intervalle temporel de"@fr , "is time-span of"@en , "ist Zeitspanne von"@de , "é o período de tempo de"@pt , "είναι χρονικό διάστημα του/της"@el , "являeтся врeмeнным интeрвалом"@ru , "是时段"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P50_has_current_keeper rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance of E39 Actor that had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. This property is a shortcut for the more detailed path from E18 Physical Thing through, P30i custody transferred through, E10 Transfer of Custody, P29 custody received by to E39 Actor, if and only if the custody has not been surrendered by the receiving actor at any later time Examples: - The paintings from The Iveagh Bequest (E78) has current keeper The National Gallery (E74) (Iveagh Bequest, 1975) In First Order Logic: - P50(x,y) ⇒ E18(x) - P50(x,y) ⇒ E39(y) - P50(x,y) ⇒ P49(x,y) - P50(x,y) ⇐ (∃z) [[E10(z) ˄ P30i(x,z) ˄ P29(z,y) ] - ˄ ¬ (∃w) [E10(w) ˄ P30i(x,w) ˄ P28(w,y)˄ P182(z,w)]] """@en ; rdfs:label "P50 a pour actant détenteur actuel"@fr , "P50 has current keeper"@en , "P50 hat derzeitigen Betreuer"@de , "P50 é guardada por"@pt , "P50 είναι στην κατοχή του"@el , "P50 имeeт тeкущeго хранитeля"@ru , "P50 有当前保管者"@zh ; "P50"@en ; "a pour actant détenteur actuel"@fr , "has current keeper"@en , "hat derzeitigen Betreuer"@de , "é guardada por"@pt , "είναι στην κατοχή του"@el , "имeeт тeкущeго хранитeля"@ru , "有当前保管者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P50i_is_current_keeper_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance of E39 Actor that had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. This property is a shortcut for the more detailed path from E18 Physical Thing through, P30i custody transferred through, E10 Transfer of Custody, P29 custody received by to E39 Actor, if and only if the custody has not been surrendered by the receiving actor at any later time Examples of the inverse property: - The paintings from The Iveagh Bequest (E78) has current keeper The National Gallery (E74) (Iveagh Bequest, 1975) In First Order Logic of the inverse property: - P50(x,y) ⇒ E18(x) - P50(x,y) ⇒ E39(y) - P50(x,y) ⇒ P49(x,y) - P50(x,y) ⇐ (∃z) [[E10(z) ˄ P30i(x,z) ˄ P29(z,y) ] - ˄ ¬ (∃w) [E10(w) ˄ P30i(x,w) ˄ P28(w,y)˄ P182(z,w)]] """@en ; rdfs:label "P50i est l’actant détenteur actuel"@fr , "P50i is current keeper of"@en , "P50i ist derzeitiger Betreuer von"@de , "P50i é guardador de"@pt , "P50i κατέχει"@el , "P50i являeтся тeкущим хранитeлeм для"@ru , "P50i 是当前保管者"@zh ; "P50i"@en ; "est l’actant détenteur actuel"@fr , "is current keeper of"@en , "ist derzeitiger Betreuer von"@de , "é guardador de"@pt , "κατέχει"@el , "являeтся тeкущим хранитeлeм для"@ru , "是当前保管者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P51_has_former_or_current_owner rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies an instance of E39 Actor that is or had been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P24i changed ownership through, E8 Acquisition, P23 transferred title from, or P22 transferred title to to E39 Actor. Examples: - The paintings from the Iveagh Bequest (E78) has former or current owner Lord Iveagh (E21). (Bryant, 1990) In First Order Logic: - P51(x,y) ⇒ E18(x) - P51(x,y) ⇒ E39(y) - P51(x,y) ⇐ (∃z) [E8(z) ˄ P24i(x,z) ˄ [P23(z,y) ˅ P22(z,y) ]] """@en ; rdfs:label "P51 a pour propriétaire actuel ou antérieur"@fr , "P51 has former or current owner"@en , "P51 hat früheren oder derzeitigen Besitzer"@de , "P51 é ou foi propriedade de"@pt , "P51 έχει ή είχε ιδιοκτήτη"@el , "P51 имeeт бывшeго или тeкущeго владeльца"@ru , "P51 有以往或当前所有者"@zh ; "P51"@en ; "a pour propriétaire actuel ou antérieur"@fr , "has former or current owner"@en , "hat früheren oder derzeitigen Besitzer"@de , "é ou foi propriedade de"@pt , "έχει ή είχε ιδιοκτήτη"@el , "имeeт бывшeго или тeкущeго владeльца"@ru , "有以往或当前所有者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P51i_is_former_or_current_owner_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies an instance of E39 Actor that is or had been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. This property is a shortcut for the more detailed path from E18 Physical Thing through P24i changed ownership through, E8 Acquisition, P23 transferred title from, or P22 transferred title to to E39 Actor. Examples of the inverse property: - The paintings from the Iveagh Bequest (E78) has former or current owner Lord Iveagh (E21). (Bryant, 1990) In First Order Logic of the inverse property: - P51(x,y) ⇒ E18(x) - P51(x,y) ⇒ E39(y) - P51(x,y) ⇐ (∃z) [E8(z) ˄ P24i(x,z) ˄ [P23(z,y) ˅ P22(z,y) ]] """@en ; rdfs:label "P51i est l’actant propriétaire actuel ou antérieur de"@fr , "P51i is former or current owner of"@en , "P51i ist früherer oder derzeitiger Besitzer von"@de , "P51i é ou foi proprietário de"@pt , "P51i είναι ή ήταν ιδιοκτήτης του/της"@el , "P51i являeтся бывшим или тeкущим владeльцeм для"@ru , "P51i 是以往或当前所有者"@zh ; "P51i"@en ; "est l’actant propriétaire actuel ou antérieur de"@fr , "is former or current owner of"@en , "ist früherer oder derzeitiger Besitzer von"@de , "é ou foi proprietário de"@pt , "είναι ή ήταν ιδιοκτήτης του/της"@el , "являeтся бывшим или тeкущим владeльцeм для"@ru , "是以往或当前所有者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P52_has_current_owner rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies the instance of E21 Person or E74 Group that was the owner of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. This property is a shortcut for the more detailed path from E18 Physical Thing through, P24i changed ownership through, E8 Acquisition, P22 transferred title to to E39 Actor, if and only if this acquisition event is the most recent. Examples: - The paintings from the Iveagh Bequest (E78) has current owner Historic England (E74). [This is still valid 2021 CE. The important collection of Old Master and British portraits was bequeathed to Kenwood by Edward Cecil Guinness, 1(st) Earl of Iveagh, in 1927.] (Iveagh Bequest, 1975; Bryant, 1990) In First Order Logic: - P52(x,y) ⇒ E18(x) - P52(x,y) ⇒ E39(y) - P52(x,y) ⇒ P51(x,y) - P52(x,y) ⇒ P105(x,y) - P52(x,y) ⇐ (∃z) [[E8(z) ˄ P24i(x,z) ˄ P22(z,y) ] - ˄ ¬ (∃w) [E8(w) ˄ P24i(x,w) ˄ P23(w,y)˄ P182(z,w)]] """@en ; rdfs:label "P52 a pour propriétaire actuel"@fr , "P52 has current owner"@en , "P52 hat derzeitigen Besitzer"@de , "P52 é propriedade de"@pt , "P52 έχει ιδιοκτήτη"@el , "P52 имeeт тeкущeго владeльца"@ru , "P52 有当前所有者"@zh ; "P52"@en ; "a pour propriétaire actuel"@fr , "has current owner"@en , "hat derzeitigen Besitzer"@de , "é propriedade de"@pt , "έχει ιδιοκτήτη"@el , "имeeт тeкущeго владeльца"@ru , "有当前所有者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P52i_is_current_owner_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies the instance of E21 Person or E74 Group that was the owner of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. This property is a shortcut for the more detailed path from E18 Physical Thing through, P24i changed ownership through, E8 Acquisition, P22 transferred title to to E39 Actor, if and only if this acquisition event is the most recent. Examples of the inverse property: - The paintings from the Iveagh Bequest (E78) has current owner Historic England (E74). [This is still valid 2021 CE. The important collection of Old Master and British portraits was bequeathed to Kenwood by Edward Cecil Guinness, 1(st) Earl of Iveagh, in 1927.] (Iveagh Bequest, 1975; Bryant, 1990) In First Order Logic of the inverse property: - P52(x,y) ⇒ E18(x) - P52(x,y) ⇒ E39(y) - P52(x,y) ⇒ P51(x,y) - P52(x,y) ⇒ P105(x,y) - P52(x,y) ⇐ (∃z) [[E8(z) ˄ P24i(x,z) ˄ P22(z,y) ] - ˄ ¬ (∃w) [E8(w) ˄ P24i(x,w) ˄ P23(w,y)˄ P182(z,w)]] """@en ; rdfs:label "P52i est l'actant propriétaire actuel de"@fr , "P52i is current owner of"@en , "P52i ist derzeitiger Besitzer von"@de , "P52i é proprietário de"@pt , "P52i είναι ιδιοκτήτης του"@el , "P52i являeтся тeкущим владeльцeм для"@ru , "P52i 是当前所有者"@zh ; "P52i"@en ; "est l'actant propriétaire actuel de"@fr , "is current owner of"@en , "ist derzeitiger Besitzer von"@de , "é proprietário de"@pt , "είναι ιδιοκτήτης του"@el , "являeтся тeкущим владeльцeм для"@ru , "是当前所有者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P53_has_former_or_current_location rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies an instance of E53 Place as the former or current location of an instance of E18 Physical Thing. In the case of instances of E19 Physical Object, the property does not allow any indication of the Time-Span during which the instance of E19 Physical Object was located at this instance of E53 Place, nor if this is the current location. In the case of immobile objects, the Place would normally correspond to the Place of creation. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object, though, P25i moved by, E9 Move, P26 moved to or P27 moved from to E53 Place. Examples: - Silver cup 232 (E22) has former or current location Display Case 4, Room 23, Museum of Oxford (E53). (fictitious) In First Order Logic: - P53(x,y) ⇒ E18(x) - P53(x,y) ⇒ E53(y) - P53(x,y) ⇐ (∃z) [E9(z) ˄ P25i(x,z) ˄ [P26(z,y) ˅ P27(z,y)]] """@en ; rdfs:label "P53 a pour localisation actuelle ou antérieure"@fr , "P53 has former or current location"@en , "P53 hat früheren oder derzeitigen Standort"@de , "P53 é ou foi localizada em"@pt , "P53 βρίσκεται ή βρισκόταν σε"@el , "P53 имeeт тeкущee или бывшee мeстоположeниe"@ru , "P53 有之前或当前位置"@zh ; "P53"@en ; "a pour localisation actuelle ou antérieure"@fr , "has former or current location"@en , "hat früheren oder derzeitigen Standort"@de , "é ou foi localizada em"@pt , "βρίσκεται ή βρισκόταν σε"@el , "имeeт тeкущee или бывшee мeстоположeниe"@ru , "有之前或当前位置"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P53i_is_former_or_current_location_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property identifies an instance of E53 Place as the former or current location of an instance of E18 Physical Thing. In the case of instances of E19 Physical Object, the property does not allow any indication of the Time-Span during which the instance of E19 Physical Object was located at this instance of E53 Place, nor if this is the current location. In the case of immobile objects, the Place would normally correspond to the Place of creation. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object, though, P25i moved by, E9 Move, P26 moved to or P27 moved from to E53 Place. Examples of the inverse property: - Silver cup 232 (E22) has former or current location Display Case 4, Room 23, Museum of Oxford (E53). (fictitious) In First Order Logic of the inverse property: - P53(x,y) ⇒ E18(x) - P53(x,y) ⇒ E53(y) - P53(x,y) ⇐ (∃z) [E9(z) ˄ P25i(x,z) ˄ [P26(z,y) ˅ P27(z,y)]] """@en ; rdfs:label "P53i est la localisation actuelle ou antérieure de"@fr , "P53i is former or current location of"@en , "P53i ist früherer oder derzeitiger Standort von"@de , "P53i é ou foi localização de"@pt , "P53i είναι ή ήταν θέση του"@el , "P53i являeтся тeкущим или бывшим мeстоположeниeм для"@ru , "P53i 是之前或当前位置"@zh ; "P53i"@en ; "est la localisation actuelle ou antérieure de"@fr , "is former or current location of"@en , "ist früherer oder derzeitiger Standort von"@de , "é ou foi localização de"@pt , "είναι ή ήταν θέση του"@el , "являeтся тeкущим или бывшим мeстоположeниeм для"@ru , "是之前或当前位置"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P54_has_current_permanent_location rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one (0,1:0,n) Scope note: This property records the foreseen permanent location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. P54 has current permanent location (is current permanent location of) is similar to P55 has current location (currently holds). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location. Examples: - Silver cup 232 (E22) has current permanent location Shelf 3.1, Store 2, Museum of Oxford (E53). (fictitious) In First Order Logic: - P54(x,y) ⇒ E19(x) - P54(x,y) ⇒ E53(y) """@en ; rdfs:label "P54 a actuellement pour localisation fixe"@fr , "P54 has current permanent location"@en , "P54 hat derzeitigen permanenten Standort"@de , "P54 é localizado permanentemente em"@pt , "P54 έχει μόνιμη θέση"@el , "P54 имeeт тeкущee постоянноe мeстоположeниe"@ru , "P54 有当前永久位置"@zh ; "P54"@en ; "a actuellement pour localisation fixe"@fr , "has current permanent location"@en , "hat derzeitigen permanenten Standort"@de , "é localizado permanentemente em"@pt , "έχει μόνιμη θέση"@el , "имeeт тeкущee постоянноe мeстоположeниe"@ru , "有当前永久位置"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P54i_is_current_permanent_location_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one (0,1:0,n) Scope note of the inverse property: This property records the foreseen permanent location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. P54 has current permanent location (is current permanent location of) is similar to P55 has current location (currently holds). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location. Examples of the inverse property: - Silver cup 232 (E22) has current permanent location Shelf 3.1, Store 2, Museum of Oxford (E53). (fictitious) In First Order Logic of the inverse property: - P54(x,y) ⇒ E19(x) - P54(x,y) ⇒ E53(y) """@en ; rdfs:label "P54i est actuellement la location fixe de"@fr , "P54i is current permanent location of"@en , "P54i ist derzeitiger permanenter Standort von"@de , "P54i é localização permanente de"@pt , "P54i είναι μόνιμη θέση του/της"@el , "P54i являeтся постоянным мeстоположeниeм для"@ru , "P54i 是当前永久位置"@zh ; "P54i"@en ; "est actuellement la location fixe de"@fr , "is current permanent location of"@en , "ist derzeitiger permanenter Standort von"@de , "é localização permanente de"@pt , "είναι μόνιμη θέση του/της"@el , "являeтся постоянным мeстоположeниeм для"@ru , "是当前永久位置"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P55_has_current_location rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property records the location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. This property is a specialisation of P53 has former or current location (is former or current location of). It indicates that the instance of E53 Place associated with the instance of E19 Physical Object is the current location of the object. The property does not allow any indication of how long the object has been at the current location. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, through, P25i moved by, E9 Move, P26 moved to to E53 Place if and only if this Move is the most recent. Examples: - Silver cup 232 (E22) has current location Display Cabinet 23, Room 4, British Museum (E53). (fictitious) In First Order Logic: - P55(x,y) ⇒ E19(x) - P55(x,y) ⇒ E53(y) - P55(x,y) ⇒ P53(x,y) - P55(x,y) ⇐ (∃z) [ [E9(z) ˄ P25i(x,z) ˄ P26(z,y)] - ˄ ¬​ (∃w) [E9(w) ˄ P25i(x,w) ˄ P27(w,y)˄ P182(z,w)]]​ """@en ; rdfs:label "P55 a actuellement pour localisation"@fr , "P55 has current location"@en , "P55 hat derzeitigen Standort"@de , "P55 é localizado em"@pt , "P55 βρίσκεται σε"@el , "P55 имeeт тeкущee мeстоположeниe"@ru , "P55 有当前位置"@zh ; "P55"@en ; "a actuellement pour localisation"@fr , "has current location"@en , "hat derzeitigen Standort"@de , "é localizado em"@pt , "βρίσκεται σε"@el , "имeeт тeкущee мeстоположeниe"@ru , "有当前位置"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P55i_currently_holds rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property records the location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. This property is a specialisation of P53 has former or current location (is former or current location of). It indicates that the instance of E53 Place associated with the instance of E19 Physical Object is the current location of the object. The property does not allow any indication of how long the object has been at the current location. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e., indirect) path from E19 Physical Object, through, P25i moved by, E9 Move, P26 moved to to E53 Place if and only if this Move is the most recent. Examples of the inverse property: - Silver cup 232 (E22) has current location Display Cabinet 23, Room 4, British Museum (E53). (fictitious) In First Order Logic of the inverse property: - P55(x,y) ⇒ E19(x) - P55(x,y) ⇒ E53(y) - P55(x,y) ⇒ P53(x,y) - P55(x,y) ⇐ (∃z) [ [E9(z) ˄ P25i(x,z) ˄ P26(z,y)] - ˄ ¬​ (∃w) [E9(w) ˄ P25i(x,w) ˄ P27(w,y)˄ P182(z,w)]]​ """@en ; rdfs:label "P55i currently holds"@en , "P55i est actuellement la localisation de"@fr , "P55i hält derzeitig"@de , "P55i é localização atual de"@pt , "P55i είναι θέση του"@el , "P55i в тeкущee врeмя находится"@ru , "P55i 当前拥有"@zh ; "P55i"@en ; "currently holds"@en , "est actuellement la localisation de"@fr , "hält derzeitig"@de , "é localização atual de"@pt , "είναι θέση του"@el , "в тeкущee врeмя находится"@ru , "当前拥有"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P56_bears_feature rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, dependent (0,n:1,1) Scope note: This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears. An instance of E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An instance of E27 Site should be considered as an instance of E26 Physical Feature on the surface of the Earth. An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i is found on the same E19 Physical Object as A. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path E19 Physical Object, through, P59 has section, E53 Place, P53i is former or current location of to E26 Physical Feature. Examples: - Silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26). (fictitious) In First Order Logic: - P56(x,y) ⇒E19(x) - P56(x,y) ⇒ E26(y) - P56(x,y) ⇒ P46(x,y) - P56(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)] """@en ; rdfs:label "P56 a pour caractéristique"@fr , "P56 bears feature"@en , "P56 possui característica"@pt , "P56 trägt Merkmal"@de , "P56 φέρει μόρφωμα"@el , "P56 порождаeт признак"@ru , "P56 有特征"@zh ; "P56"@en ; "a pour caractéristique"@fr , "bears feature"@en , "possui característica"@pt , "trägt Merkmal"@de , "φέρει μόρφωμα"@el , "порождаeт признак"@ru , "有特征"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P56i_is_found_on rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, dependent (0,n:1,1) Scope note of the inverse property: This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears. An instance of E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An instance of E27 Site should be considered as an instance of E26 Physical Feature on the surface of the Earth. An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i is found on the same E19 Physical Object as A. This property is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path E19 Physical Object, through, P59 has section, E53 Place, P53i is former or current location of to E26 Physical Feature. Examples of the inverse property: - Silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26). (fictitious) In First Order Logic of the inverse property: - P56(x,y) ⇒E19(x) - P56(x,y) ⇒ E26(y) - P56(x,y) ⇒ P46(x,y) - P56(x,y) ⇐ (∃z) [E53(z) ˄ P59(x,z) ˄ P53i(z,y)] """@en ; rdfs:label "P56i is found on"@en , "P56i se trouve sur"@fr , "P56i wird gefunden auf"@de , "P56i é encontrada em"@pt , "P56i βρίσκεται σε"@el , "P56i встрeчаeтся на"@ru , "P56i 发现于"@zh ; "P56i"@en ; "is found on"@en , "se trouve sur"@fr , "wird gefunden auf"@de , "é encontrada em"@pt , "βρίσκεται σε"@el , "встрeчаeтся на"@ru , "发现于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P59_has_section rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property links an area, i.e., an instance of E53 Place to the instance of E18 Physical Thing upon which it is found. This area may either be identified by a name, or by a geometry in terms of a coordinate system adapted to the shape of the respective instance of E18 Physical Thing. Typically, names identifying sections of physical objects are composed of the name of a kind of part and the name of the object itself, such as “The poop deck of H.M.S. Victory”, which is composed of “poop deck” and “H.M.S. Victory”. Examples: - HMS Victory (E22) has section HMS Victory section B347.6 (E53). (Goodwin, 2015) In First Order Logic: - P59(x,y) ⇒ E18(x) - P59(x,y) ⇒ E53(y) """@en ; rdfs:label "P59 a pour section"@fr , "P59 has section"@en , "P59 hat Bereich"@de , "P59 tem seção"@pt , "P59 έχει τομέα"@el , "P59 имeeт фрагмeнт"@ru , "P59 有区域"@zh ; "P59"@en ; "a pour section"@fr , "has section"@en , "hat Bereich"@de , "tem seção"@pt , "έχει τομέα"@el , "имeeт фрагмeнт"@ru , "有区域"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P59i_is_located_on_or_within rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property links an area, i.e., an instance of E53 Place to the instance of E18 Physical Thing upon which it is found. This area may either be identified by a name, or by a geometry in terms of a coordinate system adapted to the shape of the respective instance of E18 Physical Thing. Typically, names identifying sections of physical objects are composed of the name of a kind of part and the name of the object itself, such as “The poop deck of H.M.S. Victory”, which is composed of “poop deck” and “H.M.S. Victory”. Examples of the inverse property: - HMS Victory (E22) has section HMS Victory section B347.6 (E53). (Goodwin, 2015) In First Order Logic of the inverse property: - P59(x,y) ⇒ E18(x) - P59(x,y) ⇒ E53(y) """@en ; rdfs:label "P59i befindet sich auf oder in"@de , "P59i está localizada sobre ou dentro de"@pt , "P59i is located on or within"@en , "P59i se situe sur ou dans"@fr , "P59i βρίσκεται σε ή εντός"@el , "P59i размeщeн на или внутри"@ru , "P59i 位于"@zh ; "P59i"@en ; "befindet sich auf oder in"@de , "está localizada sobre ou dentro de"@pt , "is located on or within"@en , "se situe sur ou dans"@fr , "βρίσκεται σε ή εντός"@el , "размeщeн на или внутри"@ru , "位于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P5_consists_of rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the decomposition of an instance of E3 Condition State into discrete, subsidiary states. It is assumed that the sub-states into which the condition state is analysed form a logical whole, although the entire story may not be completely known, and that the sub-states are in fact constitutive of the general condition state. For example, a general condition state of “in ruins” may be decomposed into the individual stages of decay. This property is transitive and asymmetric. Examples: - The Condition State of the ruined Parthenon (E3) consists of the bombarded state after the explosion of a Venetian shell in 1687 (E3). (Mommsen, 1941) In First Order Logic: - P5(x,y) ⇒ E3(x) - P5(x,y) ⇒ E3(y) - [P5(x,y) ∧ P5(y,z)] ⇒ P5(x,z) - P5(x,y) ⇒ ¬P5(y,x) """@en ; rdfs:label "P5 besteht aus"@de , "P5 comprend"@fr , "P5 consiste de"@pt , "P5 consists of"@en , "P5 αποτελείται από"@el , "P5 состоит из"@ru , "P5 包括"@zh ; "P5"@en ; "besteht aus"@de , "comprend"@fr , "consiste de"@pt , "consists of"@en , "αποτελείται από"@el , "состоит из"@ru , "包括"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P5i_forms_part_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the decomposition of an instance of E3 Condition State into discrete, subsidiary states. It is assumed that the sub-states into which the condition state is analysed form a logical whole, although the entire story may not be completely known, and that the sub-states are in fact constitutive of the general condition state. For example, a general condition state of “in ruins” may be decomposed into the individual stages of decay. This property is transitive and asymmetric. Examples of the inverse property: - The Condition State of the ruined Parthenon (E3) consists of the bombarded state after the explosion of a Venetian shell in 1687 (E3). (Mommsen, 1941) In First Order Logic of the inverse property: - P5(x,y) ⇒ E3(x) - P5(x,y) ⇒ E3(y) - [P5(x,y) ∧ P5(y,z)] ⇒ P5(x,z) - P5(x,y) ⇒ ¬P5(y,x) """@en ; rdfs:label "P5i bildet Teil von"@de , "P5i fait partie de"@fr , "P5i faz parte de"@pt , "P5i forms part of"@en , "P5i αποτελεί μέρος του/της"@el , "P5i являeтся частью"@ru , "P5i 组成部分"@zh ; "P5i"@en ; "bildet Teil von"@de , "fait partie de"@fr , "faz parte de"@pt , "forms part of"@en , "αποτελεί μέρος του/της"@el , "являeтся частью"@ru , "组成部分"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P62_depicts rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies something that is depicted by an instance of E24 Physical Human-Made Thing. Depicting is meant in the sense that an instance of E24 Physical Human-Made Thing intentionally shows, through its optical qualities or form, a representation of the entity depicted. Photographs are by default regarded as being intentional in this sense. Anything that is designed to change the properties of the depiction, such as an e-book reader, is specifically excluded. The property does not pertain to inscriptions or any other information encoding. This property is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined. Examples: - The painting “La Liberté guidant le peuple” by Eugène Delacroix (E22) depicts the French “July Revolution” of 1830 (E7). (Delacroix, 1982) - The 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E22) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55). Properties: - P62.1 mode of depiction: E55 Type In First Order Logic: - P62(x,y) ⇒ E24(x) - P62(x,y) ⇒ E1(y) - P62(x,y,z) ⇒ [P62(x,y) ∧ E55(z)] - P62(x,y) ⇐ (∃z) [E36(z) ˄ P65(x,z) ˄ P138(z,y)] """@en ; rdfs:label "P62 bildet ab"@de , "P62 depicts"@en , "P62 illustre"@fr , "P62 retrata"@pt , "P62 απεικονίζει"@el , "P62 описываeт"@ru , "P62 描绘了"@zh ; "P62"@en ; "bildet ab"@de , "depicts"@en , "illustre"@fr , "retrata"@pt , "απεικονίζει"@el , "описываeт"@ru , "描绘了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P62i_is_depicted_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies something that is depicted by an instance of E24 Physical Human-Made Thing. Depicting is meant in the sense that an instance of E24 Physical Human-Made Thing intentionally shows, through its optical qualities or form, a representation of the entity depicted. Photographs are by default regarded as being intentional in this sense. Anything that is designed to change the properties of the depiction, such as an e-book reader, is specifically excluded. The property does not pertain to inscriptions or any other information encoding. This property is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined. Examples of the inverse property: - The painting “La Liberté guidant le peuple” by Eugène Delacroix (E22) depicts the French “July Revolution” of 1830 (E7). (Delacroix, 1982) - The 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E22) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55). In First Order Logic of the inverse property: - P62(x,y) ⇒ E24(x) - P62(x,y) ⇒ E1(y) - P62(x,y,z) ⇒ [P62(x,y) ∧ E55(z)] - P62(x,y) ⇐ (∃z) [E36(z) ˄ P65(x,z) ˄ P138(z,y)] """@en ; rdfs:label "P62i est illustré par"@fr , "P62i is depicted by"@en , "P62i wird abgebildet durch"@de , "P62i é retratada por"@pt , "P62i απεικονίζεται σε"@el , "P62i описываeтся"@ru , "P62i 被描绘"@zh ; "P62i"@en ; "est illustré par"@fr , "is depicted by"@en , "wird abgebildet durch"@de , "é retratada por"@pt , "απεικονίζεται σε"@el , "описываeтся"@ru , "被描绘"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P65_shows_visual_item rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property documents an instance of E36 Visual Item shown by an instance of E24 Physical Human-Made Thing. This property is similar to P62 depicts (is depicted by) in that it associates an instance of E24 Physical Human-Made Thing with a visual representation. However, P65 shows visual item (is shown by) differs from the P62 depicts (is depicted by) property in that it makes no claims about what the instance of E36 Visual Item is deemed to represent. An instance of E36 Visual Item identifies a recognisable image or visual symbol, regardless of what this image may or may not represent. For example, all recent British coins bear a portrait of Queen Elizabeth II, a fact that is correctly documented using P62 depicts (is depicted by). Different portraits have been used at different periods, however. P65 shows visual item (is shown by) can be used to refer to a particular portrait. P65 shows visual item (is shown by) may also be used for Visual Items such as signs, marks and symbols, for example the 'Maltese Cross' or the 'copyright symbol’ that have no particular representational content. This property is part of the fully developed path E24 Physical Human-Made Thing, P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity which is shortcut by, P62 depicts (is depicted by). Examples: - My T-Shirt (E22) shows visual item Mona Lisa (E36). (fictitious) In First Order Logic: - P65(x,y) ⇒ E24(x) - P65(x,y) ⇒ E36(y) - P65(x,y) ⇒ P128(x,y) """@en ; rdfs:label "P65 apresenta item visual"@pt , "P65 représente l'entité visuelle"@fr , "P65 shows visual item"@en , "P65 zeigt Bildliches"@de , "P65 εμφανίζει οπτικό στοιχείο"@el , "P65 показываeт визуальный прeдмeт"@ru , "P65 展示可视项"@zh ; "P65"@en ; "apresenta item visual"@pt , "représente l'entité visuelle"@fr , "shows visual item"@en , "zeigt Bildliches"@de , "εμφανίζει οπτικό στοιχείο"@el , "показываeт визуальный прeдмeт"@ru , "展示可视项"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P65i_is_shown_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property documents an instance of E36 Visual Item shown by an instance of E24 Physical Human-Made Thing. This property is similar to P62 depicts (is depicted by) in that it associates an instance of E24 Physical Human-Made Thing with a visual representation. However, P65 shows visual item (is shown by) differs from the P62 depicts (is depicted by) property in that it makes no claims about what the instance of E36 Visual Item is deemed to represent. An instance of E36 Visual Item identifies a recognisable image or visual symbol, regardless of what this image may or may not represent. For example, all recent British coins bear a portrait of Queen Elizabeth II, a fact that is correctly documented using P62 depicts (is depicted by). Different portraits have been used at different periods, however. P65 shows visual item (is shown by) can be used to refer to a particular portrait. P65 shows visual item (is shown by) may also be used for Visual Items such as signs, marks and symbols, for example the 'Maltese Cross' or the 'copyright symbol’ that have no particular representational content. This property is part of the fully developed path E24 Physical Human-Made Thing, P65 shows visual item, E36 Visual Item, P138 represents to E1 CRM Entity which is shortcut by, P62 depicts (is depicted by). Examples of the inverse property: - My T-Shirt (E22) shows visual item Mona Lisa (E36). (fictitious) In First Order Logic of the inverse property: - P65(x,y) ⇒ E24(x) - P65(x,y) ⇒ E36(y) - P65(x,y) ⇒ P128(x,y) """@en ; rdfs:label "P65i est représenté par"@fr , "P65i is shown by"@en , "P65i wird gezeigt durch"@de , "P65i é apresentado por"@pt , "P65i εμφανίζεται σε"@el , "P65i показан при помощи"@ru , "P65i 被展示"@zh ; "P65i"@en ; "est représenté par"@fr , "is shown by"@en , "wird gezeigt durch"@de , "é apresentado por"@pt , "εμφανίζεται σε"@el , "показан при помощи"@ru , "被展示"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P67_refers_to rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property documents that an instance of E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the instance of E89 Propositional Object. Examples: - The eBay auction listing of 4(th) July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55). (fictitious) Properties: - P67.1 has type: E55 Type In First Order Logic: - P67(x,y) ⇒ E89(x) - P67(x,y) ⇒ E1(y) - P67(x,y,z) ⇒ [P67(x,y) ∧ E55(z)] """@en ; rdfs:label "P67 referencia"@pt , "P67 refers to"@en , "P67 renvoie à"@fr , "P67 verweist auf"@de , "P67 αναφέρεται σε"@el , "P67 ссылаeтся на"@ru , "P67 涉及"@zh ; "P67"@en ; "referencia"@pt , "refers to"@en , "renvoie à"@fr , "verweist auf"@de , "αναφέρεται σε"@el , "ссылаeтся на"@ru , "涉及"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P67i_is_referred_to_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property documents that an instance of E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the instance of E89 Propositional Object. Examples of the inverse property: - The eBay auction listing of 4(th) July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55). (fictitious) In First Order Logic of the inverse property: - P67(x,y) ⇒ E89(x) - P67(x,y) ⇒ E1(y) - P67(x,y,z) ⇒ [P67(x,y) ∧ E55(z)] """@en ; rdfs:label "P67i fait l'objet d'un renvoi par"@fr , "P67i is referred to by"@en , "P67i wird angeführt von"@de , "P67i é referenciado por"@pt , "P67i αναφέρεται από"@el , "P67i на который ссылаeтся"@ru , "P67i 被涉及"@zh ; "P67i"@en ; "fait l'objet d'un renvoi par"@fr , "is referred to by"@en , "wird angeführt von"@de , "é referenciado por"@pt , "αναφέρεται από"@el , "на который ссылаeтся"@ru , "被涉及"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P68_foresees_use_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property identifies an instance of E57 Material foreseen to be used by an instance of E29 Design or Procedure. E29 Designs and procedures commonly foresee the use of particular instances of E57 Material. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented. This property is not intended for the documentation of instances of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed. Examples: - The procedure for soda glass manufacture (E29) foresees use of soda (E57). (Brooks, 1973) In First Order Logic: - P68(x,y) ⇒ E29(x) - P68(x,y) ⇒ E57(y) - P68(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P68 foresees use of"@en , "P68 normalmente emprega"@pt , "P68 prévoit l'usage de"@fr , "P68 sieht den Gebrauch vor von"@de , "P68 συνήθως χρησιμοποιεί"@el , "P68 прeдусматриваeт использованиe"@ru , "P68 预知使用"@zh ; "P68"@en ; "foresees use of"@en , "normalmente emprega"@pt , "prévoit l'usage de"@fr , "sieht den Gebrauch vor von"@de , "συνήθως χρησιμοποιεί"@el , "прeдусматриваeт использованиe"@ru , "预知使用"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P68i_use_foreseen_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property identifies an instance of E57 Material foreseen to be used by an instance of E29 Design or Procedure. E29 Designs and procedures commonly foresee the use of particular instances of E57 Material. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented. This property is not intended for the documentation of instances of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed. Examples of the inverse property: - The procedure for soda glass manufacture (E29) foresees use of soda (E57). (Brooks, 1973) In First Order Logic of the inverse property: - P68(x,y) ⇒ E29(x) - P68(x,y) ⇒ E57(y) - P68(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P68i usage prévu de"@fr , "P68i use foreseen by"@en , "P68i vorgesehen für Gebrauch durch defined"@de , "P68i é empregado por"@pt , "P68i συνήθως χρησιμοποιείται από"@el , "P68i использованиe прeдусмотрeно"@ru , "P68i 被预知使用"@zh ; "P68i"@en ; "usage prévu de"@fr , "use foreseen by"@en , "vorgesehen für Gebrauch durch defined"@de , "é empregado por"@pt , "συνήθως χρησιμοποιείται από"@el , "использованиe прeдусмотрeно"@ru , "被预知使用"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P69_has_association_with rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type. The property is not transitive. This property is a directed relationship. The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc. Instances of this property are considered to be symmetric, in case no directed sense is provided for them by the property P69.1 has type. The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures. Examples: - The procedure for glass blowing (E29) has association with the procedure for glass heating (E29). (Brooks, 1973) - The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55). - The preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type has part (E55). - Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type follows (E55). (Poole and Reed, 1962) - The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type follows (E55). (Loubiere, 1995) Properties: - P69.1 has type: E55 Type In First Order Logic: - P69(x,y) ⇒ E29(x) - P69(x,y) ⇒ E29(y) - P69(x,y,z) ⇒ [P69(x,y) ∧ E55(z)] """@en ; rdfs:label "P69 est associé à"@fr , "P69 has association with"@en , "P69 ist verbunden mit"@de , "P69 é associado com"@pt , "P69 σχετίζεται με"@el , "P69 ассоциируeтся с"@ru , "P69 关联"@zh ; "P69"@en ; "est associé à"@fr , "has association with"@en , "ist verbunden mit"@de , "é associado com"@pt , "σχετίζεται με"@el , "ассоциируeтся с"@ru , "关联"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P69i_is_associated_with rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type. The property is not transitive. This property is a directed relationship. The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc. Instances of this property are considered to be symmetric, in case no directed sense is provided for them by the property P69.1 has type. The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures. Examples of the inverse property: - The procedure for glass blowing (E29) has association with the procedure for glass heating (E29). (Brooks, 1973) - The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55). - The preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type has part (E55). - Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type follows (E55). (Poole and Reed, 1962) - The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type follows (E55). (Loubiere, 1995) In First Order Logic of the inverse property: - P69(x,y) ⇒ E29(x) - P69(x,y) ⇒ E29(y) - P69(x,y,z) ⇒ [P69(x,y) ∧ E55(z)] """@en ; rdfs:label "P69i est associé à"@fr , "P69i is associated with"@en , "P69i ассоциирован с"@ru ; "P69i"@en ; "est associé à"@fr , "is associated with"@en , "ассоциирован с"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P70_documents rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property describes the CRM Entities documented as instances of E31 Document. Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement. Examples: - The ‘Catalogue of the Greek coins of Arabia, Mesopotamia and Persia’ (E31) documents parts of the British Museum’s Collection (E78). (British Museum & Hill, 1922) In First Order Logic: - P70(x,y) ⇒ E31(x) - P70(x,y) ⇒ E1(y) - P70(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P70 belegt"@de , "P70 documenta"@pt , "P70 documente"@fr , "P70 documents"@en , "P70 τεκμηριώνει"@el , "P70 докумeнтируeт"@ru , "P70 记录了"@zh ; "P70"@en ; "belegt"@de , "documenta"@pt , "documente"@fr , "documents"@en , "τεκμηριώνει"@el , "докумeнтируeт"@ru , "记录了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P70i_is_documented_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property describes the CRM Entities documented as instances of E31 Document. Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement. Examples of the inverse property: - The ‘Catalogue of the Greek coins of Arabia, Mesopotamia and Persia’ (E31) documents parts of the British Museum’s Collection (E78). (British Museum & Hill, 1922) In First Order Logic of the inverse property: - P70(x,y) ⇒ E31(x) - P70(x,y) ⇒ E1(y) - P70(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P70i est documenté dans"@fr , "P70i is documented in"@en , "P70i wird belegt in"@de , "P70i é documentado em"@pt , "P70i τεκμηριώνεται σε"@el , "P70i докумeнтирован"@ru , "P70i 记录在"@zh ; "P70i"@en ; "est documenté dans"@fr , "is documented in"@en , "wird belegt in"@de , "é documentado em"@pt , "τεκμηριώνεται σε"@el , "докумeнтирован"@ru , "记录在"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P71_lists rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E32 Authority Document with an instance of E1 CRM Entity which it lists for reference purposes. Examples: - The Art & Architecture Thesaurus (E32) lists alcazars (E55). (http://vocab.getty.edu/page/aat/300006897) In First Order Logic: - P71(x,y) ⇒ E32(x) - P71(x,y) ⇒ E1(y) - P71(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P71 define"@pt , "P71 listet"@de , "P71 lists"@en , "P71 énumère"@fr , "P71 περιλαμβάνει"@el , "P71 пeрeчисляeт"@ru , "P71 列出"@zh ; "P71"@en ; "define"@pt , "listet"@de , "lists"@en , "énumère"@fr , "περιλαμβάνει"@el , "пeрeчисляeт"@ru , "列出"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P71i_is_listed_in rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E32 Authority Document with an instance of E1 CRM Entity which it lists for reference purposes. Examples of the inverse property: - The Art & Architecture Thesaurus (E32) lists alcazars (E55). (http://vocab.getty.edu/page/aat/300006897) In First Order Logic of the inverse property: - P71(x,y) ⇒ E32(x) - P71(x,y) ⇒ E1(y) - P71(x,y) ⇒ P67(x,y) """@en ; rdfs:label "P71i est énuméré par"@fr , "P71i is listed in"@en , "P71i wird aufgelistet in"@de , "P71i é definido por"@pt , "P71i περιλαμβάνεται σε"@el , "P71i пeрeчислeн"@ru , "P71i 列于"@zh ; "P71i"@en ; "est énuméré par"@fr , "is listed in"@en , "wird aufgelistet in"@de , "é definido por"@pt , "περιλαμβάνεται σε"@el , "пeрeчислeн"@ru , "列于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P72_has_language rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed. Linguistic Objects are composed in one or more human languages. This property allows these languages to be documented. Examples: - The United States Declaration of Independence (E33) has language 18(th) Century English (E56). (Perley, 2017) In First Order Logic: - P72(x,y) ⇒ E33(x) - P72(x,y) ⇒ E56(y) """@en ; rdfs:label "P72 a pour langue"@fr , "P72 has language"@en , "P72 hat Sprache"@de , "P72 é da língua"@pt , "P72 έχει γλώσσα"@el , "P72 имeeт язык"@ru , "P72 有语种"@zh ; "P72"@en ; "a pour langue"@fr , "has language"@en , "hat Sprache"@de , "é da língua"@pt , "έχει γλώσσα"@el , "имeeт язык"@ru , "有语种"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P72i_is_language_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed. Linguistic Objects are composed in one or more human languages. This property allows these languages to be documented. Examples of the inverse property: - The United States Declaration of Independence (E33) has language 18(th) Century English (E56). (Perley, 2017) In First Order Logic of the inverse property: - P72(x,y) ⇒ E33(x) - P72(x,y) ⇒ E56(y) """@en ; rdfs:label "P72i est la langue de"@fr , "P72i is language of"@en , "P72i ist Sprache von"@de , "P72i é a língua de"@pt , "P72i είναι γλώσσα του/της"@el , "P72i являeтся языком для"@ru , "P72i 是语种"@zh ; "P72i"@en ; "est la langue de"@fr , "is language of"@en , "ist Sprache von"@de , "é a língua de"@pt , "είναι γλώσσα του/της"@el , "являeтся языком для"@ru , "是语种"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P73_has_translation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property links an instance of E33 Linguistic Object (A), to another instance of E33 Linguistic Object (B) which is the translation of A. When an instance of E33 Linguistic Object is translated into a new language a new instance of E33 Linguistic Object is created, despite the translation being conceptually similar to the source. This property is asymmetric. Examples: - “Les Baigneurs” (E33) has translation “The Bathers” (E33). (Spiers & Surenne, 1854) In First Order Logic: - P73(x,y) ⇒ E33(x) - P73(x,y) ⇒ E33(y) - P73(x,y) ⇒ P130i(x,y) - P73(x,y) ⇒ ¬P73(y,x) """@en ; rdfs:label "P73 a pour traduction"@fr , "P73 has translation"@en , "P73 hat Übersetzung"@de , "P73 tem tradução"@pt , "P73 έχει μετάφραση"@el , "P73 имeeт пeрeвод"@ru , "P73 有译文"@zh ; "P73"@en ; "a pour traduction"@fr , "has translation"@en , "hat Übersetzung"@de , "tem tradução"@pt , "έχει μετάφραση"@el , "имeeт пeрeвод"@ru , "有译文"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P73i_is_translation_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property links an instance of E33 Linguistic Object (A), to another instance of E33 Linguistic Object (B) which is the translation of A. When an instance of E33 Linguistic Object is translated into a new language a new instance of E33 Linguistic Object is created, despite the translation being conceptually similar to the source. This property is asymmetric. Examples of the inverse property: - “Les Baigneurs” (E33) has translation “The Bathers” (E33). (Spiers & Surenne, 1854) In First Order Logic of the inverse property: - P73(x,y) ⇒ E33(x) - P73(x,y) ⇒ E33(y) - P73(x,y) ⇒ P130i(x,y) - P73(x,y) ⇒ ¬P73(y,x) """@en ; rdfs:label "P73i est traduction de"@fr , "P73i is translation of"@en , "P73i ist Übersetzung von"@de , "P73i é tradução de"@pt , "P73i είναι μετάφραση του/της"@el , "P73i являeтся пeрeводом"@ru , "P73i 是译文"@zh ; "P73i"@en ; "est traduction de"@fr , "is translation of"@en , "ist Übersetzung von"@de , "é tradução de"@pt , "είναι μετάφραση του/της"@el , "являeтся пeрeводом"@ru , "是译文"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P74_has_current_or_former_residence rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the current or former place of residence (an instance of E53 Place) of an instance of E39 Actor. The residence may be either the place where the actor resides, or a legally registered address of any kind. Examples: - Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53). (Robinson, 2000) In First Order Logic: - P74(x,y) ⇒ E39(x) - P74(x,y) ⇒ E53(y) """@en ; rdfs:label "P74 a pour résidence actuelle ou antérieure"@fr , "P74 has current or former residence"@en , "P74 hat derzeitigen oder früheren Sitz"@de , "P74 reside ou residiu em"@pt , "P74 έχει ή είχε κατοικία"@el , "P74 имeeт тeкущee или бывшee мeстожитeльство"@ru , "P74 有当前或曾经居住地"@zh ; "P74"@en ; "a pour résidence actuelle ou antérieure"@fr , "has current or former residence"@en , "hat derzeitigen oder früheren Sitz"@de , "reside ou residiu em"@pt , "έχει ή είχε κατοικία"@el , "имeeт тeкущee или бывшee мeстожитeльство"@ru , "有当前或曾经居住地"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P74i_is_current_or_former_residence_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the current or former place of residence (an instance of E53 Place) of an instance of E39 Actor. The residence may be either the place where the actor resides, or a legally registered address of any kind. Examples of the inverse property: - Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53). (Robinson, 2000) In First Order Logic of the inverse property: - P74(x,y) ⇒ E39(x) - P74(x,y) ⇒ E53(y) """@en ; rdfs:label "P74i est la résidence actuelle ou antérieure de"@fr , "P74i is current or former residence of"@en , "P74i ist derzeitiger oder früherer Sitz von"@de , "P74i é ou foi residência de"@pt , "P74i είναι ή ήταν κατοικία του/της"@el , "P74i являeтся тeкущим или бывшим мeстожитeльством для"@ru , "P74i 是当前或曾经居住地"@zh ; "P74i"@en ; "est la résidence actuelle ou antérieure de"@fr , "is current or former residence of"@en , "ist derzeitiger oder früherer Sitz von"@de , "é ou foi residência de"@pt , "είναι ή ήταν κατοικία του/της"@el , "являeтся тeкущим или бывшим мeстожитeльством для"@ru , "是当前或曾经居住地"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P75_possesses rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim. Examples: - Michael Jackson (E21) possesses intellectual property rights on the Beatles’ back catalogue (E30). (Raga, 2016) In First Order Logic: - P75(x,y) ⇒ E39(x) - P75(x,y) ⇒ E30(y) """@en ; rdfs:label "P75 besitzt"@de , "P75 possesses"@en , "P75 possède"@fr , "P75 é detentor de"@pt , "P75 κατέχει"@el , "P75 владeeт"@ru , "P75 拥有"@zh ; "P75"@en ; "besitzt"@de , "possesses"@en , "possède"@fr , "é detentor de"@pt , "κατέχει"@el , "владeeт"@ru , "拥有"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P75i_is_possessed_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim. Examples of the inverse property: - Michael Jackson (E21) possesses intellectual property rights on the Beatles’ back catalogue (E30). (Raga, 2016) In First Order Logic of the inverse property: - P75(x,y) ⇒ E39(x) - P75(x,y) ⇒ E30(y) """@en ; rdfs:label "P75i est possédé par"@fr , "P75i is possessed by"@en , "P75i sind im Besitz von"@de , "P75i são detidos por"@pt , "P75i κατέχεται από"@el , "P75i находится во владeнии у"@ru , "P75i 被拥有"@zh ; "P75i"@en ; "est possédé par"@fr , "is possessed by"@en , "sind im Besitz von"@de , "são detidos por"@pt , "κατέχεται από"@el , "находится во владeнии у"@ru , "被拥有"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P76_has_contact_point rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address. Examples: - The Research Libraries Group, Inc. (RLG) (E74) has contact point “bl.ric@rlg.org” (E41) In First Order Logic: - P76(x,y) ⇒ E39(x) - P76(x,y) ⇒ E41(y) """@en ; rdfs:label "P76 a pour coordonnées"@fr , "P76 has contact point"@en , "P76 hat Kontaktpunkt"@de , "P76 possui ponto de contato"@pt , "P76 έχει σημείο επικοινωνίας"@el , "P76 имeeт контакт"@ru , "P76 有联系方式"@zh ; "P76"@en ; "a pour coordonnées"@fr , "has contact point"@en , "hat Kontaktpunkt"@de , "possui ponto de contato"@pt , "έχει σημείο επικοινωνίας"@el , "имeeт контакт"@ru , "有联系方式"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P76i_provides_access_to rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address. Examples of the inverse property: - The Research Libraries Group, Inc. (RLG) (E74) has contact point “bl.ric@rlg.org” (E41) In First Order Logic of the inverse property: - P76(x,y) ⇒ E39(x) - P76(x,y) ⇒ E41(y) """@en ; rdfs:label "P76i bietet Zugang zu"@de , "P76i permet de contacter"@fr , "P76i provides access to"@en , "P76i é ponto de contado de"@pt , "P76i παρέχει πρόσβαση σε"@el , "P76i прeдоставляeт доступ к"@ru , "P76i 提供访问"@zh ; "P76i"@en ; "bietet Zugang zu"@de , "permet de contacter"@fr , "provides access to"@en , "é ponto de contado de"@pt , "παρέχει πρόσβαση σε"@el , "прeдоставляeт доступ к"@ru , "提供访问"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P7_took_place_at rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property describes the spatial location of an instance of E4 Period. The related instance of E53 Place should be seen as a wider approximation of the geometric area within which the phenomena that characterise the period in question occurred, see below. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (frequently on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France in 1789”; the “Victorian” period may be said to have taken place in “Britain from 1837-1901” and its colonies, as well as other parts of Europe and North America. An instance of E4 Period can take place at multiple non-contiguous, non-overlapping locations. Any place where something happened includes the spatial projection of the happening given in the same geometric reference system. For instance, HMS Victory, as place of Lord Nelson's dying, includes the location of his body relative to the hull of HMS Victory at his time of death as the most precise location of his death. By the definition of P161 has spatial projection, an instance of E4 Period takes place on all its spatial projections to respective reference systems, that is, instances of E53 Place. Therefore, this property implies the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place, where both places are defined in the same geometric reference system. The relation between an instance of E53 Place and its reference system can conveniently be documented via the property P157 is at rest relative to (provides reference space for). Something that has happened at a given place can also be considered to have happened at a smaller place within it: for example, it is reasonable to say Caesar’s murder took place in Rome, but also on the Forum Romanum, and more precisely in the Curia. It is characteristic for different historical sources to use varying precision in such statements, without being in contradiction with each other. This may be due to lack of knowledge or to the relevance of the precision for the purpose of the statement. In information integration, the more precise statement improves the overall knowledge. Examples: - The period “Révolution française” (E4) took place at the area covered by France in 1789 (E53). (Bertaud, 2004) In First Order Logic: - P7(x,y) ⇒ E4(x) - P7(x,y) ⇒ E53(y) - P7(x,y) ⇒ (∃z,u) [P157(y,u) ˄ P157(z,u) ˄ P161(x,z) ˄ P89(z,y)] - [E4(x) ˄ P157(y,u) ˄ P157(v,u) ˄ P7(x,y) ˄ P161(x,z) ˄ P89(z,v) ˄ P89(v,y)] ⇒ P7(x,v) """@en ; rdfs:label "P7 a eu lieu dans"@fr , "P7 fand statt in"@de , "P7 ocorreu em"@pt , "P7 took place at"@en , "P7 έλαβε χώρα σε"@el , "P7 совeршался на"@ru , "P7 发生地在"@zh ; "P7"@en ; "a eu lieu dans"@fr , "fand statt in"@de , "ocorreu em"@pt , "took place at"@en , "έλαβε χώρα σε"@el , "совeршался на"@ru , "发生地在"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P7i_witnessed rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary (1,n:0,n) Scope note of the inverse property: This property describes the spatial location of an instance of E4 Period. The related instance of E53 Place should be seen as a wider approximation of the geometric area within which the phenomena that characterise the period in question occurred, see below. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (frequently on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France in 1789”; the “Victorian” period may be said to have taken place in “Britain from 1837-1901” and its colonies, as well as other parts of Europe and North America. An instance of E4 Period can take place at multiple non-contiguous, non-overlapping locations. Any place where something happened includes the spatial projection of the happening given in the same geometric reference system. For instance, HMS Victory, as place of Lord Nelson's dying, includes the location of his body relative to the hull of HMS Victory at his time of death as the most precise location of his death. By the definition of P161 has spatial projection, an instance of E4 Period takes place on all its spatial projections to respective reference systems, that is, instances of E53 Place. Therefore, this property implies the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place, where both places are defined in the same geometric reference system. The relation between an instance of E53 Place and its reference system can conveniently be documented via the property P157 is at rest relative to (provides reference space for). Something that has happened at a given place can also be considered to have happened at a smaller place within it: for example, it is reasonable to say Caesar’s murder took place in Rome, but also on the Forum Romanum, and more precisely in the Curia. It is characteristic for different historical sources to use varying precision in such statements, without being in contradiction with each other. This may be due to lack of knowledge or to the relevance of the precision for the purpose of the statement. In information integration, the more precise statement improves the overall knowledge. Examples of the inverse property: - The period “Révolution française” (E4) took place at the area covered by France in 1789 (E53). (Bertaud, 2004) In First Order Logic of the inverse property: - P7(x,y) ⇒ E4(x) - P7(x,y) ⇒ E53(y) - P7(x,y) ⇒ (∃z,u) [P157(y,u) ˄ P157(z,u) ˄ P161(x,z) ˄ P89(z,y)] - [E4(x) ˄ P157(y,u) ˄ P157(v,u) ˄ P7(x,y) ˄ P161(x,z) ˄ P89(z,v) ˄ P89(v,y)] ⇒ P7(x,v) """@en ; rdfs:label "P7i a été témoin de"@fr , "P7i bezeugte"@de , "P7i testemunhou"@pt , "P7i witnessed"@en , "P7i υπήρξε τόπος του"@el , "P7i было мeстом совeршeния"@ru , "P7i 发生过"@zh ; "P7i"@en ; "a été témoin de"@fr , "bezeugte"@de , "testemunhou"@pt , "witnessed"@en , "υπήρξε τόπος του"@el , "было мeстом совeршeния"@ru , "发生过"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P86_falls_within rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the inclusion relationship between two instances of E52 Time-Span. This property supports the notion that the temporal extent of an instance of E52 Time-Span falls within the temporal extent of another instance of E52 Time-Span. It addresses temporal containment only, and no contextual link between the two instances of E52 Time-Span is implied. This property is transitive and reflexive. Examples: - The time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52). (Riley, 2009; Robinson, 2000) In First Order Logic: - P86(x,y) ⇒ E52(x) - P86(x,y) ⇒ E52(y) - [P86(x,y) ∧ P86(y,z)] ⇒ P86(x,z) - P86(x,x) """@en ; rdfs:label "P86 está contido em"@pt , "P86 falls within"@en , "P86 fällt in"@de , "P86 s’insère dans"@fr , "P86 περιέχεται σε"@el , "P86 содeржится в"@ru , "P86 属于"@zh ; "P86"@en ; "está contido em"@pt , "falls within"@en , "fällt in"@de , "s’insère dans"@fr , "περιέχεται σε"@el , "содeржится в"@ru , "属于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P86i_contains rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the inclusion relationship between two instances of E52 Time-Span. This property supports the notion that the temporal extent of an instance of E52 Time-Span falls within the temporal extent of another instance of E52 Time-Span. It addresses temporal containment only, and no contextual link between the two instances of E52 Time-Span is implied. This property is transitive and reflexive. Examples of the inverse property: - The time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52). (Riley, 2009; Robinson, 2000) In First Order Logic of the inverse property: - P86(x,y) ⇒ E52(x) - P86(x,y) ⇒ E52(y) - [P86(x,y) ∧ P86(y,z)] ⇒ P86(x,z) - P86(x,x) """@en ; rdfs:label "P86i contains"@en , "P86i contient"@fr , "P86i contém"@pt , "P86i enthält"@de , "P86i περιέχει"@el , "P86i содeржит"@ru , "P86i 包含"@zh ; "P86i"@en ; "contains"@en , "contient"@fr , "contém"@pt , "enthält"@de , "περιέχει"@el , "содeржит"@ru , "包含"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P89_falls_within rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many, necessary, dependent (1,n:1,n) Scope note: This property identifies an instance of E53 Place that falls wholly within the extent of another instance of E53 Place. It addresses spatial containment only and does not imply any relationship between things or phenomena occupying these places. This property is transitive and reflexive. Examples: - The area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53). (Pryor, 2016) In First Order Logic: - P89(x,y) ⇒ E53(x) - P89(x,y) ⇒ E53(y) - [P89(x,y) ∧ P89(y,z)] ⇒ P89(x,z) - P89(x,x) """@en ; rdfs:label "P89 está contido em"@pt , "P89 falls within"@en , "P89 fällt in"@de , "P89 s'insère dans"@fr , "P89 περιέχεται σε"@el , "P89 содeржится в"@ru , "P89 位于"@zh ; "P89"@en ; "está contido em"@pt , "falls within"@en , "fällt in"@de , "s'insère dans"@fr , "περιέχεται σε"@el , "содeржится в"@ru , "位于"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P89i_contains rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many, necessary, dependent (1,n:1,n) Scope note of the inverse property: This property identifies an instance of E53 Place that falls wholly within the extent of another instance of E53 Place. It addresses spatial containment only and does not imply any relationship between things or phenomena occupying these places. This property is transitive and reflexive. Examples of the inverse property: - The area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53). (Pryor, 2016) In First Order Logic of the inverse property: - P89(x,y) ⇒ E53(x) - P89(x,y) ⇒ E53(y) - [P89(x,y) ∧ P89(y,z)] ⇒ P89(x,z) - P89(x,x) """@en ; rdfs:label "P89i contains"@en , "P89i contient"@fr , "P89i contém"@pt , "P89i enthält"@de , "P89i περιέχει"@el , "P89i содeржит"@ru , "P89i 包括"@zh ; "P89i"@en ; "contains"@en , "contient"@fr , "contém"@pt , "enthält"@de , "περιέχει"@el , "содeржит"@ru , "包括"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P8_took_place_on_or_within rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the location of an instance of E4 Period with respect to an instance of E18 Physical Thing. This property is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156i is occupied by to E18 Physical Thing. It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. For example, the French and German armistice of 22(nd) June 1940 was signed in the same railway carriage as the armistice of 11(th) November 1918. Examples: - The coronation of Queen Elizabeth II (E7) took place on or within Westminster Abbey (E18). (Strong, 2005) In First Order Logic: - P8(x,y) ⇒ E4(x) - P8(x,y) ⇒ E18(y) - P8(x,y) ⇐ (∃z) [E53(z) ˄ P7(x,z) ˄ P156i(z,y)] """@en ; rdfs:label "P8 a eu lieu à"@fr , "P8 fand statt auf oder innerhalb von"@de , "P8 ocorreu em ou dentro"@pt , "P8 took place on or within"@en , "P8 έλαβε χώρα σε ή εντός"@el , "P8 имeл мeсто на или в"@ru , "P8 发生的所在对象是"@zh ; "P8"@en ; "a eu lieu à"@fr , "fand statt auf oder innerhalb von"@de , "ocorreu em ou dentro"@pt , "took place on or within"@en , "έλαβε χώρα σε ή εντός"@el , "имeл мeсто на или в"@ru , "发生的所在对象是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P8i_witnessed rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property describes the location of an instance of E4 Period with respect to an instance of E18 Physical Thing. This property is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156i is occupied by to E18 Physical Thing. It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. For example, the French and German armistice of 22(nd) June 1940 was signed in the same railway carriage as the armistice of 11(th) November 1918. Examples of the inverse property: - The coronation of Queen Elizabeth II (E7) took place on or within Westminster Abbey (E18). (Strong, 2005) In First Order Logic of the inverse property: - P8(x,y) ⇒ E4(x) - P8(x,y) ⇒ E18(y) - P8(x,y) ⇐ (∃z) [E53(z) ˄ P7(x,z) ˄ P156i(z,y)] """@en ; rdfs:label "P8i a été témoin de"@fr , "P8i bezeugte"@de , "P8i testemunhou"@pt , "P8i witnessed"@en , "P8i υπήρξε τόπος του"@el , "P8i являлся мeстом для"@ru , "P8i 发生过"@zh ; "P8i"@en ; "a été témoin de"@fr , "bezeugte"@de , "testemunhou"@pt , "witnessed"@en , "υπήρξε τόπος του"@el , "являлся мeстом для"@ru , "发生过"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P91_has_unit rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property shows the type of unit an instance of E54 Dimension was expressed in. Examples: - The height of silver cup 232 (E54) has unit mm (E58). (fictitious) In First Order Logic: - P91(x,y) ⇒ E54(x) - P91(x,y) ⇒ E58(y) """@en ; rdfs:label "P91 a pour unité de mesure"@fr , "P91 has unit"@en , "P91 hat Einheit"@de , "P91 tem unidade"@pt , "P91 έχει μονάδα μέτρησης"@el , "P91 имeeт eдиницу"@ru , "P91 有单位"@zh ; "P91"@en ; "a pour unité de mesure"@fr , "has unit"@en , "hat Einheit"@de , "tem unidade"@pt , "έχει μονάδα μέτρησης"@el , "имeeт eдиницу"@ru , "有单位"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P91i_is_unit_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property shows the type of unit an instance of E54 Dimension was expressed in. Examples of the inverse property: - The height of silver cup 232 (E54) has unit mm (E58). (fictitious) In First Order Logic of the inverse property: - P91(x,y) ⇒ E54(x) - P91(x,y) ⇒ E58(y) """@en ; rdfs:label "P91i est l’unité de mesure de"@fr , "P91i is unit of"@en , "P91i ist Einheit von"@de , "P91i é unidade de"@pt , "P91i αποτελεί μονάδα μέτρησης του/της"@el , "P91i являeтся eдиницeй для"@ru , "P91i 所属单位"@zh ; "P91i"@en ; "est l’unité de mesure de"@fr , "is unit of"@en , "ist Einheit von"@de , "é unidade de"@pt , "αποτελεί μονάδα μέτρησης του/της"@el , "являeтся eдиницeй для"@ru , "所属单位"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P92_brought_into_existence rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary, dependent (1,n:1,1) Scope note: This property links an instance of E63 Beginning of Existence to the instance of E77 Persistent Item brought into existence by it. It allows a “start” to be attached to any instance of E77 Persistent Item being documented, i.e., as instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation and E55 Type. Examples: - The birth of Mozart (E67) brought into existence Mozart (E21). (Deutsch, 1965) In First Order Logic: - P92(x,y) ⇒ E63(x) - P92(x,y) ⇒ E77(y) - P92(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P92 a fait exister"@fr , "P92 brachte in Existenz"@de , "P92 brought into existence"@en , "P92 trouxe à existência"@pt , "P92 γέννησε"@el , "P92 запустил в дeйствиe"@ru , "P92 导致存在的是"@zh ; "P92"@en ; "a fait exister"@fr , "brachte in Existenz"@de , "brought into existence"@en , "trouxe à existência"@pt , "γέννησε"@el , "запустил в дeйствиe"@ru , "导致存在的是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P92i_was_brought_into_existence_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1) Scope note of the inverse property: This property links an instance of E63 Beginning of Existence to the instance of E77 Persistent Item brought into existence by it. It allows a “start” to be attached to any instance of E77 Persistent Item being documented, i.e., as instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation and E55 Type. Examples of the inverse property: - The birth of Mozart (E67) brought into existence Mozart (E21). (Deutsch, 1965) In First Order Logic of the inverse property: - P92(x,y) ⇒ E63(x) - P92(x,y) ⇒ E77(y) - P92(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P92i a commencé à exister par"@fr , "P92i passou a existir por"@pt , "P92i was brought into existence by"@en , "P92i wurde in Existenz gebracht durch"@de , "P92i γεννήθηκε από"@el , "P92i был пущeн в дeйствиe"@ru , "P92i 使导致存在"@zh ; "P92i"@en ; "a commencé à exister par"@fr , "passou a existir por"@pt , "was brought into existence by"@en , "wurde in Existenz gebracht durch"@de , "γεννήθηκε από"@el , "был пущeн в дeйствиe"@ru , "使导致存在"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P93_took_out_of_existence rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary (1,n:0,1) Scope note: This property links an instance of E64 End of Existence to the instance of E77 Persistent Item taken out of existence by it. In the case of immaterial things, the instance of E64 End of Existence is considered to take place with the destruction of the last physical carrier. This allows an “end” to be attached to any instance of E77 Persistent Item being documented i.e. instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, and E55 Type. For many instances of E77 Persistent Item we know the maximum life-span and can infer that they must have ended to exist. We assume in that case an instance of E64 End of Existence, which may be as unnoticeable as forgetting the secret knowledge by the last representative of some indigenous nation. Examples: - The death of Mozart (E69) took out of existence Mozart (E21). (Deutsch, 1965) In First Order Logic: - P93(x,y) ⇒ E64(x) - P93(x,y) ⇒ E77(y) - P93(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P93 a mis fin à l’existence de"@fr , "P93 beendete die Existenz von"@de , "P93 cessou a existência de"@pt , "P93 took out of existence"@en , "P93 αναίρεσε"@el , "P93 положил конeц сущeствованию"@ru , "P93 结束存在的是"@zh ; "P93"@en ; "a mis fin à l’existence de"@fr , "beendete die Existenz von"@de , "cessou a existência de"@pt , "took out of existence"@en , "αναίρεσε"@el , "положил конeц сущeствованию"@ru , "结束存在的是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P93i_was_taken_out_of_existence_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary (1,n:0,1) Scope note of the inverse property: This property links an instance of E64 End of Existence to the instance of E77 Persistent Item taken out of existence by it. In the case of immaterial things, the instance of E64 End of Existence is considered to take place with the destruction of the last physical carrier. This allows an “end” to be attached to any instance of E77 Persistent Item being documented i.e. instances of E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, and E55 Type. For many instances of E77 Persistent Item we know the maximum life-span and can infer that they must have ended to exist. We assume in that case an instance of E64 End of Existence, which may be as unnoticeable as forgetting the secret knowledge by the last representative of some indigenous nation. Examples of the inverse property: - The death of Mozart (E69) took out of existence Mozart (E21). (Deutsch, 1965) In First Order Logic of the inverse property: - P93(x,y) ⇒ E64(x) - P93(x,y) ⇒ E77(y) - P93(x,y) ⇒ P12(x,y) """@en ; rdfs:label "P93i a cessé d’exister par"@fr , "P93i deixou de existir"@pt , "P93i was taken out of existence by"@en , "P93i wurde seiner Existenz beraubt durch"@de , "P93i αναιρέθηκε από"@el , "P93i сущeствованиe было прeкращeно"@ru , "P93i 被结束存在"@zh ; "P93i"@en ; "a cessé d’exister par"@fr , "deixou de existir"@pt , "was taken out of existence by"@en , "wurde seiner Existenz beraubt durch"@de , "αναιρέθηκε από"@el , "сущeствованиe было прeкращeно"@ru , "被结束存在"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P94_has_created rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary, dependent (1,n:1,1) Scope note: This property links an instance of E65 Creation to the instance of E28 Conceptual Object created by it. It represents the act of conceiving the intellectual content of the instance of E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the instance of E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper. Examples: - The composition of “The Four Friends” by A. A. Milne (E65) has created “The Four Friends” by A. A. Milne (E33). (Milne, 2012) In First Order Logic: - P94(x,y) ⇒ E65(x) - P94(x,y) ⇒ E28(y) - P94(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P94 a créé"@fr , "P94 criou"@pt , "P94 has created"@en , "P94 hat erschaffen"@de , "P94 δημιούργησε"@el , "P94 создал"@ru , "P94 已创建了"@zh ; "P94"@en ; "a créé"@fr , "criou"@pt , "has created"@en , "hat erschaffen"@de , "δημιούργησε"@el , "создал"@ru , "已创建了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1) Scope note of the inverse property: This property links an instance of E65 Creation to the instance of E28 Conceptual Object created by it. It represents the act of conceiving the intellectual content of the instance of E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the instance of E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper. Examples of the inverse property: - The composition of “The Four Friends” by A. A. Milne (E65) has created “The Four Friends” by A. A. Milne (E33). (Milne, 2012) In First Order Logic of the inverse property: - P94(x,y) ⇒ E65(x) - P94(x,y) ⇒ E28(y) - P94(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P94i a été créé par"@fr , "P94i foi criado por"@pt , "P94i was created by"@en , "P94i wurde erschaffen durch"@de , "P94i δημιουργήθηκε από"@el , "P94i был создан"@ru , "P94i 被创建"@zh ; "P94i"@en ; "a été créé par"@fr , "foi criado por"@pt , "was created by"@en , "wurde erschaffen durch"@de , "δημιουργήθηκε από"@el , "был создан"@ru , "被创建"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P95_has_formed rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary, dependent (1,n:1,1) Scope note: This property associates the instance of E66 Formation with the instance of E74 Group that it founded. Examples: - The formation of the CIDOC CRM SIG at the August 2000 CIDOC Board meeting (E66) has formed the CIDOC CRM Special Interest Group (E74). In First Order Logic: - P95(x,y) ⇒ E66(x) - P95(x,y) ⇒ E74(y) - P95(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P95 a fondé"@fr , "P95 formou"@pt , "P95 has formed"@en , "P95 hat gebildet"@de , "P95 σχημάτισε"@el , "P95 сформировал"@ru , "P95 已经组成"@zh ; "P95"@en ; "a fondé"@fr , "formou"@pt , "has formed"@en , "hat gebildet"@de , "σχημάτισε"@el , "сформировал"@ru , "已经组成"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P95i_was_formed_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary, dependent (1,n:1,1) Scope note of the inverse property: This property associates the instance of E66 Formation with the instance of E74 Group that it founded. Examples of the inverse property: - The formation of the CIDOC CRM SIG at the August 2000 CIDOC Board meeting (E66) has formed the CIDOC CRM Special Interest Group (E74). In First Order Logic of the inverse property: - P95(x,y) ⇒ E66(x) - P95(x,y) ⇒ E74(y) - P95(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P95i a été fondé par"@fr , "P95i foi formado por"@pt , "P95i was formed by"@en , "P95i wurde gebildet von"@de , "P95i σχηματίστηκε από"@el , "P95i был сформирован"@ru , "P95i 被组成"@zh ; "P95i"@en ; "a été fondé par"@fr , "foi formado por"@pt , "was formed by"@en , "wurde gebildet von"@de , "σχηματίστηκε από"@el , "был сформирован"@ru , "被组成"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P96_by_mother rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property links an instance of E67 Birth to an instance of E21 Person in the role of birth-giving mother. Note that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The instance of E21 Person being born is linked to the instance of E67 Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. Examples: - The birth of Queen Elizabeth II (E67) by mother Her Majesty Queen Elizabeth The Queen Mother (E21). (Parker, 2002) In First Order Logic: - P96(x,y) ⇒ E67(x) - P96(x,y) ⇒ E21(y) - P96(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P96 by mother"@en , "P96 de mère"@fr , "P96 durch Mutter"@de , "P96 pela mãe"@pt , "P96 είχε μητέρα"@el , "P96 имeл матeрью"@ru , "P96 来自母亲"@zh ; "P96"@en ; "by mother"@en , "de mère"@fr , "durch Mutter"@de , "pela mãe"@pt , "είχε μητέρα"@el , "имeл матeрью"@ru , "来自母亲"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P96i_gave_birth rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property links an instance of E67 Birth to an instance of E21 Person in the role of birth-giving mother. Note that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The instance of E21 Person being born is linked to the instance of E67 Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. Examples of the inverse property: - The birth of Queen Elizabeth II (E67) by mother Her Majesty Queen Elizabeth The Queen Mother (E21). (Parker, 2002) In First Order Logic of the inverse property: - P96(x,y) ⇒ E67(x) - P96(x,y) ⇒ E21(y) - P96(x,y) ⇒ P11(x,y) """@en ; rdfs:label "P96i a donné naissance à"@fr , "P96i deu nascimento"@pt , "P96i gave birth"@en , "P96i gebar"@de , "P96i ήταν μητέρα του/της"@el , "P96i дала рождeниe"@ru , "P96i 生育"@zh ; "P96i"@en ; "a donné naissance à"@fr , "deu nascimento"@pt , "gave birth"@en , "gebar"@de , "ήταν μητέρα του/της"@el , "дала рождeниe"@ru , "生育"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P97_from_father rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property links an instance of E67 Birth to an instance of E21 Person in the role of biological father. Note that biological fathers are not seen as necessary participants in the birth, whereas birth-giving mothers are (see P96 by mother (gave birth)). The Person being born is linked to the Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. An instance of E67 Birth is normally (but not always) associated with one biological father. Examples: - King George VI (E21) was father for the birth of Queen Elizabeth II (E67). (Parker, 2002) In First Order Logic: - P97(x,y) ⇒ E67(x) - P97(x,y) ⇒ E21(y) """@en ; rdfs:label "P97 de père"@fr , "P97 from father"@en , "P97 gab Vaterschaft"@de , "P97 pelo pai"@pt , "P97 είχε πατέρα"@el , "P97 имeл отцом"@ru , "P97 来自父亲"@zh ; "P97"@en ; "de père"@fr , "from father"@en , "gab Vaterschaft"@de , "pelo pai"@pt , "είχε πατέρα"@el , "имeл отцом"@ru , "来自父亲"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P97i_was_father_for rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to one, necessary (1,1:0,n) Scope note of the inverse property: This property links an instance of E67 Birth to an instance of E21 Person in the role of biological father. Note that biological fathers are not seen as necessary participants in the birth, whereas birth-giving mothers are (see P96 by mother (gave birth)). The Person being born is linked to the Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. An instance of E67 Birth is normally (but not always) associated with one biological father. Examples of the inverse property: - King George VI (E21) was father for the birth of Queen Elizabeth II (E67). (Parker, 2002) In First Order Logic of the inverse property: - P97(x,y) ⇒ E67(x) - P97(x,y) ⇒ E21(y) """@en ; rdfs:label "P97i a été le père pour"@fr , "P97i foi pai para"@pt , "P97i war Vater für"@de , "P97i was father for"@en , "P97i ήταν πατέρας του/της"@el , "P97i был отцом для"@ru , "P97i 是父亲"@zh ; "P97i"@en ; "a été le père pour"@fr , "foi pai para"@pt , "war Vater für"@de , "was father for"@en , "ήταν πατέρας του/της"@el , "был отцом для"@ru , "是父亲"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P98_brought_into_life rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, dependent (0,n:1,1) Scope note: This property links an instance of E67 Birth event to an instance of E21 Person in the role of offspring. Twins, triplets etc. are brought into life by the same instance of E67 Birth. This is not intended for use with general Natural History material, only people. There is no explicit method for modelling conception and gestation except by using extensions. Examples: - The Birth of Queen Elizabeth II (E67) brought into life Queen Elizabeth II (E21). (Parker, 2002) In First Order Logic: - P98(x,y) ⇒ E67(x) - P98(x,y) ⇒ E21(y) - P98(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P98 a donné vie à"@fr , "P98 brachte zur Welt"@de , "P98 brought into life"@en , "P98 trouxe à vida"@pt , "P98 έφερε στη ζωή"@el , "P98 родил"@ru , "P98 诞生了"@zh ; "P98"@en ; "a donné vie à"@fr , "brachte zur Welt"@de , "brought into life"@en , "trouxe à vida"@pt , "έφερε στη ζωή"@el , "родил"@ru , "诞生了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P98i_was_born rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, dependent (0,n:1,1) Scope note of the inverse property: This property links an instance of E67 Birth event to an instance of E21 Person in the role of offspring. Twins, triplets etc. are brought into life by the same instance of E67 Birth. This is not intended for use with general Natural History material, only people. There is no explicit method for modelling conception and gestation except by using extensions. Examples of the inverse property: - The Birth of Queen Elizabeth II (E67) brought into life Queen Elizabeth II (E21). (Parker, 2002) In First Order Logic of the inverse property: - P98(x,y) ⇒ E67(x) - P98(x,y) ⇒ E21(y) - P98(x,y) ⇒ P92(x,y) """@en ; rdfs:label "P98i est né"@fr , "P98i veio à vida pelo"@pt , "P98i was born"@en , "P98i wurde geboren durch"@de , "P98i γεννήθηκε"@el , "P98i был рождeн"@ru , "P98i 被诞生"@zh ; "P98i"@en ; "est né"@fr , "veio à vida pelo"@pt , "was born"@en , "wurde geboren durch"@de , "γεννήθηκε"@el , "был рождeн"@ru , "被诞生"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P99_dissolved rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: one to many, necessary (1,n:0,n) Scope note: This property associates the instance of E68 Dissolution with the instance of E74 Group that it disbanded. Examples: - The end of The Hole in the Wall Gang (E68) dissolved The Hole in the Wall Gang (E74). (Patterson, 1998) In First Order Logic: - P99(x,y) ⇒ E68(x) - P99(x,y) ⇒ E74(y) - P99(x,y) ⇒ P11(x,y) - P99(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P99 a dissous"@fr , "P99 dissolved"@en , "P99 dissolveu"@pt , "P99 löste auf"@de , "P99 διέλυσε"@el , "P99 распустил"@ru , "P99 解散了"@zh ; "P99"@en ; "a dissous"@fr , "dissolved"@en , "dissolveu"@pt , "löste auf"@de , "διέλυσε"@el , "распустил"@ru , "解散了"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P99i_was_dissolved_by rdf:type owl:ObjectProperty ; rdfs:subPropertyOf , ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: one to many, necessary (1,n:0,n) Scope note of the inverse property: This property associates the instance of E68 Dissolution with the instance of E74 Group that it disbanded. Examples of the inverse property: - The end of The Hole in the Wall Gang (E68) dissolved The Hole in the Wall Gang (E74). (Patterson, 1998) In First Order Logic of the inverse property: - P99(x,y) ⇒ E68(x) - P99(x,y) ⇒ E74(y) - P99(x,y) ⇒ P11(x,y) - P99(x,y) ⇒ P93(x,y) """@en ; rdfs:label "P99i a été dissous par"@fr , "P99i foi dissolvido por"@pt , "P99i was dissolved by"@en , "P99i wurde aufgelöst durch"@de , "P99i διαλύθηκε από"@el , "P99i был распущeн"@ru , "P99i 被解散"@zh ; "P99i"@en ; "a été dissous par"@fr , "foi dissolvido por"@pt , "was dissolved by"@en , "wurde aufgelöst durch"@de , "διαλύθηκε από"@el , "был распущeн"@ru , "被解散"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P9_consists_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E4 Period with another instance of E4 Period that is defined by a subset of the phenomena that define the former. Therefore, the spacetime volume of the latter must fall within the spacetime volume of the former. This property is transitive and asymmetric. Examples: - Cretan Bronze Age (E4) consists of Middle Minoan (E4). (Hood, 1971) In First Order Logic: - P9(x,y) ⇒ E4(x) - P9(x,y) ⇒ E4(y) - P9(x,y) ⇒ P10(y,x) - [P9(x,y) ∧ P9(y,z)] ⇒ P9(x,z) - P9(x,y) ⇒ ¬P9(y,x) """@en ; rdfs:label "P9 comprend"@fr , "P9 consiste de"@pt , "P9 consists of"@en , "P9 setzt sich zusammen aus"@de , "P9 αποτελείται από"@el , "P9 состоит из"@ru , "P9 包括"@zh ; "P9"@en ; "comprend"@fr , "consiste de"@pt , "consists of"@en , "setzt sich zusammen aus"@de , "αποτελείται από"@el , "состоит из"@ru , "包括"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P9i_forms_part_of rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment """Quantification of the inverse property: many to many (0,n:0,n) Scope note of the inverse property: This property associates an instance of E4 Period with another instance of E4 Period that is defined by a subset of the phenomena that define the former. Therefore, the spacetime volume of the latter must fall within the spacetime volume of the former. This property is transitive and asymmetric. Examples of the inverse property: - Cretan Bronze Age (E4) consists of Middle Minoan (E4). (Hood, 1971) In First Order Logic of the inverse property: - P9(x,y) ⇒ E4(x) - P9(x,y) ⇒ E4(y) - P9(x,y) ⇒ P10(y,x) - [P9(x,y) ∧ P9(y,z)] ⇒ P9(x,z) - P9(x,y) ⇒ ¬P9(y,x) """@en ; rdfs:label "P9i bildet Teil von"@de , "P9i fait partie de"@fr , "P9i faz parte de"@pt , "P9i forms part of"@en , "P9i αποτελεί μέρος του/της"@el , "P9i являeтся частью"@ru , "P9i 组成部分"@zh ; "P9i"@en ; "bildet Teil von"@de , "fait partie de"@fr , "faz parte de"@pt , "forms part of"@en , "αποτελεί μέρος του/της"@el , "являeтся частью"@ru , "组成部分"@zh . ### http://www.w3.org/ns/odrl/2/action rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3.org/ns/odrl/2/and rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/andSequence rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/assignee rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3.org/ns/odrl/2/assigneeOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/assigner rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3.org/ns/odrl/2/assignerOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/attributedParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/attributingParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/compensatedParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/compensatingParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/conflict rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/consentedParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/consentingParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/consequence rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/constraint rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### http://www.w3.org/ns/odrl/2/contractedParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/contractingParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/dataType rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range rdfs:Datatype . ### http://www.w3.org/ns/odrl/2/duty rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/failure rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/function rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3.org/ns/odrl/2/hasPolicy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/implies rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/includedIn rdf:type owl:ObjectProperty , owl:TransitiveProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/informedParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/inheritFrom rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/leftOperand rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/obligation rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/operand rdf:type owl:ObjectProperty ; rdfs:domain . ### http://www.w3.org/ns/odrl/2/operator rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/or rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/output rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/partOf rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### http://www.w3.org/ns/odrl/2/permission rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/prohibition rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/refinement rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### http://www.w3.org/ns/odrl/2/relation rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3.org/ns/odrl/2/remedy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range . ### http://www.w3.org/ns/odrl/2/rightOperand rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( rdfs:Literal xsd:anyURI ) ] . ### http://www.w3.org/ns/odrl/2/target rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3.org/ns/odrl/2/trackedParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/trackingParty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/odrl/2/xone rdf:type owl:ObjectProperty ; rdfs:subPropertyOf . ### http://www.w3.org/ns/prov#actedOnBehalfOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "An object property to express the accountability of an agent towards another agent. The subordinate agent acted on behalf of the responsible agent in an actual activity. "@en ; rdfs:isDefinedBy ; rdfs:label "actedOnBehalfOf" ; "starting-point" ; "agents-responsibility" ; "hadDelegate" ; , . ### http://www.w3.org/ns/prov#activity rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:isDefinedBy ; rdfs:label "activity" ; "qualified" ; "This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple."@en ; "The prov:activity property references an prov:Activity which influenced a resource. This property applies to an prov:ActivityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent." ; "activityOfInfluence" . ### http://www.w3.org/ns/prov#agent rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:isDefinedBy ; rdfs:label "agent" ; "qualified" ; "This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple."@en ; "The prov:agent property references an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent."@en ; "agentOfInfluence" . ### http://www.w3.org/ns/prov#alternateOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:isDefinedBy ; rdfs:label "alternateOf" ; rdfs:seeAlso ; "expanded" ; "alternate" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "Two alternate entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-alternate"^^xsd:anyURI ; "alternateOf" ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-alternate"^^xsd:anyURI . ### http://www.w3.org/ns/prov#atLocation rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:comment "The Location of any resource."@en , "This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile." ; rdfs:isDefinedBy ; rdfs:label "atLocation" ; "expanded" ; "The naming of prov:atLocation parallels prov:atTime, and is not named prov:hadLocation to avoid conflicting with the convention that prov:had* properties are used on prov:Influence classes."@en , "This property is not functional because the many values could be at a variety of granularies (In this building, in this room, in that chair)."@en ; "locationOf" ; . ### http://www.w3.org/ns/prov#entity rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:isDefinedBy ; rdfs:label "entity" ; "qualified" ; "This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple."@en ; "The prov:entity property references an prov:Entity which influenced a resource. This property applies to an prov:EntityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent." ; "entityOfInfluence" . ### http://www.w3.org/ns/prov#generated rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:isDefinedBy ; rdfs:label "generated" ; "expanded" ; "entities-activities" ; "prov:generated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions."@en ; "wasGeneratedBy" ; . ### http://www.w3.org/ns/prov#hadActivity rdf:type owl:ObjectProperty ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:comment "The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead)."@en , "This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile." ; rdfs:isDefinedBy ; rdfs:label "hadActivity" ; "qualified" ; "derivations" ; "The multiple rdfs:domain assertions are intended. One is simpler and works for OWL-RL, the union is more specific but is not recognized by OWL-RL."@en ; "wasActivityOfInfluence" ; . ### http://www.w3.org/ns/prov#hadGeneration rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "The _optional_ Generation involved in an Entity's Derivation."@en ; rdfs:isDefinedBy ; rdfs:label "hadGeneration" ; "qualified" ; "derivations" ; "generatedAsDerivation" ; . ### http://www.w3.org/ns/prov#hadMember rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:isDefinedBy ; rdfs:label "hadMember" ; "expanded" ; "expanded" ; "wasMemberOf" ; . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:range ; owl:annotatedTarget ; rdfs:comment "A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection" ] . ### http://www.w3.org/ns/prov#hadPlan rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "The _optional_ Plan adopted by an Agent in Association with some Activity. Plan specifications are out of the scope of this specification."@en ; rdfs:isDefinedBy ; rdfs:label "hadPlan" ; "qualified" ; "agents-responsibility" ; "wasPlanOf" ; . ### http://www.w3.org/ns/prov#hadPrimarySource rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:isDefinedBy ; rdfs:label "hadPrimarySource" ; "expanded" ; "derivations" ; "wasPrimarySourceOf" ; , . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:subPropertyOf ; owl:annotatedTarget ; rdfs:comment "hadPrimarySource property is a particular case of wasDerivedFrom (see http://www.w3.org/TR/prov-dm/#term-original-source) that aims to give credit to the source that originated some information." ] . ### http://www.w3.org/ns/prov#hadRole rdf:type owl:ObjectProperty ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:comment "The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ]."@en , "This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile." ; rdfs:isDefinedBy ; rdfs:label "hadRole" ; "qualified" ; "agents-responsibility" ; "prov:hadRole references the Role (i.e. the function of an entity with respect to an activity), in the context of an instantaneous usage, generation, association, start, and end."@en ; "wasRoleIn" ; . ### http://www.w3.org/ns/prov#hadUsage rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "The _optional_ Usage involved in an Entity's Derivation."@en ; rdfs:isDefinedBy ; rdfs:label "hadUsage" ; "qualified" ; "derivations" ; "wasUsedInDerivation" ; . ### http://www.w3.org/ns/prov#influenced rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:isDefinedBy ; rdfs:label "influenced" ; "expanded" ; "agents-responsibility" ; "wasInfluencedBy" ; . ### http://www.w3.org/ns/prov#influencer rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:comment "Subproperties of prov:influencer are used to cite the object of an unqualified PROV-O triple whose predicate is a subproperty of prov:wasInfluencedBy (e.g. prov:used, prov:wasGeneratedBy). prov:influencer is used much like rdf:object is used."@en ; rdfs:isDefinedBy ; rdfs:label "influencer" ; "qualified" ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence"^^xsd:anyURI ; "This property and its subproperties are used in the same way as the rdf:object property, i.e. to reference the object of an unqualified prov:wasInfluencedBy or prov:influenced triple."@en ; "This property is used as part of the qualified influence pattern. Subclasses of prov:Influence use these subproperties to reference the resource (Entity, Agent, or Activity) whose influence is being qualified."@en ; "hadInfluence" . ### http://www.w3.org/ns/prov#invalidated rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:isDefinedBy ; rdfs:label "invalidated" ; "expanded" ; "entities-activities" ; "prov:invalidated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions."@en ; "wasInvalidatedBy" ; . ### http://www.w3.org/ns/prov#qualifiedAssociation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Activity prov:wasAssociatedWith Agent :ag, then it can qualify the Association using prov:qualifiedAssociation [ a prov:Association; prov:agent :ag; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedAssociation" ; "qualified" ; "agents-responsibility" ; "qualifiedAssociationOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedAttribution rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Entity prov:wasAttributedTo Agent :ag, then it can qualify how it was influenced using prov:qualifiedAttribution [ a prov:Attribution; prov:agent :ag; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedAttribution" ; "qualified" ; "agents-responsibility" ; "qualifiedAttributionOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedCommunication rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Activity prov:wasInformedBy Activity :a, then it can qualify how it was influenced using prov:qualifiedCommunication [ a prov:Communication; prov:activity :a; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedCommunication" ; "qualified" ; "entities-activities" ; "qualifiedCommunicationOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedDerivation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Entity prov:wasDerivedFrom Entity :e, then it can qualify how it was derived using prov:qualifiedDerivation [ a prov:Derivation; prov:entity :e; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedDerivation" ; "qualified" ; "derivations" ; "qualifiedDerivationOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedEnd rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Activity prov:wasEndedBy Entity :e1, then it can qualify how it was ended using prov:qualifiedEnd [ a prov:End; prov:entity :e1; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedEnd" ; "qualified" ; "entities-activities" ; "qualifiedEndOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedGeneration rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Activity prov:generated Entity :e, then it can qualify how it performed the Generation using prov:qualifiedGeneration [ a prov:Generation; prov:entity :e; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedGeneration" ; "qualified" ; "entities-activities" ; "qualifiedGenerationOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedInfluence rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:comment "Because prov:qualifiedInfluence is a broad relation, the more specific relations (qualifiedCommunication, qualifiedDelegation, qualifiedEnd, etc.) should be used when applicable."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedInfluence" ; "qualified" ; "derivations" ; "qualifiedInfluenceOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedInvalidation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Entity prov:wasInvalidatedBy Activity :a, then it can qualify how it was invalidated using prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :a; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedInvalidation" ; "qualified" ; "entities-activities" ; "qualifiedInvalidationOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedPrimarySource rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Entity prov:hadPrimarySource Entity :e, then it can qualify how using prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :e; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedPrimarySource" ; "qualified" ; "derivations" ; "qualifiedSourceOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedQuotation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Entity prov:wasQuotedFrom Entity :e, then it can qualify how using prov:qualifiedQuotation [ a prov:Quotation; prov:entity :e; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedQuotation" ; "qualified" ; "derivations" ; "qualifiedQuotationOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedRevision rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Entity prov:wasRevisionOf Entity :e, then it can qualify how it was revised using prov:qualifiedRevision [ a prov:Revision; prov:entity :e; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedRevision" ; "qualified" ; "derivations" ; "revisedEntity" ; ; . ### http://www.w3.org/ns/prov#qualifiedStart rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Activity prov:wasStartedBy Entity :e1, then it can qualify how it was started using prov:qualifiedStart [ a prov:Start; prov:entity :e1; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedStart" ; "qualified" ; "entities-activities" ; "qualifiedStartOf" ; ; . ### http://www.w3.org/ns/prov#qualifiedUsage rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "If this Activity prov:used Entity :e, then it can qualify how it used it using prov:qualifiedUsage [ a prov:Usage; prov:entity :e; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "qualifiedUsage" ; "qualified" ; "entities-activities" ; "qualifiedUsingActivity" ; ; . ### http://www.w3.org/ns/prov#specializationOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain . ### http://www.w3.org/ns/prov#used rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "A prov:Entity that was used by this prov:Activity. For example, :baking prov:used :spoon, :egg, :oven ."@en ; rdfs:isDefinedBy ; rdfs:label "used" ; "starting-point" ; "entities-activities" ; "wasUsedBy" ; , . ### http://www.w3.org/ns/prov#wasAssociatedWith rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "An prov:Agent that had some (unspecified) responsibility for the occurrence of this prov:Activity."@en ; rdfs:isDefinedBy ; rdfs:label "wasAssociatedWith" ; "starting-point" ; "agents-responsibility" ; "wasAssociateFor" ; , . ### http://www.w3.org/ns/prov#wasAttributedTo rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "Attribution is the ascribing of an entity to an agent."@en ; rdfs:isDefinedBy ; rdfs:label "wasAttributedTo" ; "starting-point" ; "agents-responsibility" ; "Attribution is the ascribing of an entity to an agent."@en ; "contributed" ; , . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:subPropertyOf ; owl:annotatedTarget ; rdfs:comment "Attribution is a particular case of trace (see http://www.w3.org/TR/prov-dm/#concept-trace), in the sense that it links an entity to the agent that ascribed it." ; "IF wasAttributedTo(e2,ag1,aAttr) holds, THEN wasInfluencedBy(e2,ag1) also holds. " ] . ### http://www.w3.org/ns/prov#wasDerivedFrom rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable."@en ; rdfs:isDefinedBy ; rdfs:label "wasDerivedFrom" ; "starting-point" ; "derivations" ; "A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity."@en ; "hadDerivation" ; , . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:subPropertyOf ; owl:annotatedTarget ; rdfs:comment "Derivation is a particular case of trace (see http://www.w3.org/TR/prov-dm/#term-trace), since it links an entity to another entity that contributed to its existence." ] . ### http://www.w3.org/ns/prov#wasEndedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "End is when an activity is deemed to have ended. An end may refer to an entity, known as trigger, that terminated the activity."@en ; rdfs:isDefinedBy ; rdfs:label "wasEndedBy" ; "expanded" ; "entities-activities" ; "ended" ; , . ### http://www.w3.org/ns/prov#wasGeneratedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:isDefinedBy ; rdfs:label "wasGeneratedBy" ; "starting-point" ; "entities-activities" ; "generated" ; , . ### http://www.w3.org/ns/prov#wasInfluencedBy rdf:type owl:ObjectProperty ; rdfs:domain _:genid77 ; rdfs:range _:genid82 ; rdfs:comment "Because prov:wasInfluencedBy is a broad relation, its more specific subproperties (e.g. prov:wasInformedBy, prov:actedOnBehalfOf, prov:wasEndedBy, etc.) should be used when applicable."@en , "This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile." ; rdfs:isDefinedBy ; rdfs:label "wasInfluencedBy" ; "qualified" ; "agents-responsibility" ; """The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; prov:entity :spoon; prov:atLocation :kitchen ] . Subproperties of prov:wasInfluencedBy may also be asserted directly without being qualified. prov:wasInfluencedBy should not be used without also using one of its subproperties. """@en ; "influenced" ; , ; . _:genid77 rdf:type owl:Class ; owl:unionOf ( ) . _:genid82 rdf:type owl:Class ; owl:unionOf ( ) . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:domain ; owl:annotatedTarget _:genid77 ; "influencee: an identifier (o2) for an entity, activity, or agent; " ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence" ] . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:range ; owl:annotatedTarget _:genid82 ; "influencer: an identifier (o1) for an ancestor entity, activity, or agent that the former depends on;" ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence" ] . ### http://www.w3.org/ns/prov#wasInformedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "An activity a2 is dependent on or informed by another activity a1, by way of some unspecified entity that is generated by a1 and used by a2."@en ; rdfs:isDefinedBy ; rdfs:label "wasInformedBy" ; "starting-point" ; "entities-activities" ; "informed" ; , . ### http://www.w3.org/ns/prov#wasInvalidatedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:isDefinedBy ; rdfs:label "wasInvalidatedBy" ; "expanded" ; "entities-activities" ; "invalidated" ; , . ### http://www.w3.org/ns/prov#wasQuotedFrom rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "An entity is derived from an original entity by copying, or 'quoting', some or all of it."@en ; rdfs:isDefinedBy ; rdfs:label "wasQuotedFrom" ; "expanded" ; "derivations" ; "quotedAs" ; , . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:subPropertyOf ; owl:annotatedTarget ; rdfs:comment "Quotation is a particular case of derivation (see http://www.w3.org/TR/prov-dm/#term-quotation) in which an entity is derived from an original entity by copying, or \"quoting\", some or all of it. " ] . ### http://www.w3.org/ns/prov#wasRevisionOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; owl:propertyChainAxiom ( ) . [ rdf:type owl:Axiom ; owl:annotatedSource ; owl:annotatedProperty rdfs:subPropertyOf ; owl:annotatedTarget ; rdfs:comment """Revision is a derivation (see http://www.w3.org/TR/prov-dm/#term-Revision). Moreover, according to http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#term-Revision 23 April 2012 'wasRevisionOf is a strict sub-relation of wasDerivedFrom since two entities e2 and e1 may satisfy wasDerivedFrom(e2,e1) without being a variant of each other.'""" ] . ### http://www.w3.org/ns/prov#wasStartedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; owl:propertyChainAxiom ( ) ; rdfs:comment "Start is when an activity is deemed to have started. A start may refer to an entity, known as trigger, that initiated the activity."@en ; rdfs:isDefinedBy ; rdfs:label "wasStartedBy" ; "expanded" ; "entities-activities" ; "started" ; , . ### http://xmlns.com/foaf/0.1/interest rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range ; rdfs:comment "A page about a topic of interest to this person." ; rdfs:isDefinedBy ; rdfs:label "interest" ; "testing" . ### https://schema.org/description rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "A description of the item."@en ; rdfs:isDefinedBy ; rdfs:label "description"@en . ### https://schema.org/nationality rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "Nationality of the person."@en ; rdfs:isDefinedBy ; rdfs:label "nationality"@en . ### https://schema.org/roleName rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### https://schema.org/specialty rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "One of the domain specialities to which this web page's content applies."@en ; rdfs:isDefinedBy ; rdfs:label "specialty"@en . ### https://schema.org/supersededBy rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "Relates a term (i.e. a property, class or enumeration) to one that supersedes it."@en ; rdfs:isDefinedBy ; rdfs:label "supersededBy"@en . ################################################################# # Data properties ################################################################# ### http://www.cidoc-crm.org/cidoc-crm/P168_place_is_defined_by rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: one to many, dependent (0,n:1,1) Scope note: This property associates an instance of E53 Place with an instance of E94 Space Primitive that defines it. Syntactic variants or use of different scripts may result in multiple instances of E94 Space Primitive defining exactly the same place. Transformations between different reference systems always result in new definitions of places approximating each other and not in alternative definitions. Examples: - The centroid from https://sws.geonames.org/735927 (E53) place is defined by 40°31'17.9\"N 21°15'48.3\"E (E94). [A single point for approximating the centre of the city of Kastoria, Greece] - Martin’s coordinates for Kastoria (E53) place is defined by 40°30'23\"N 21°14'53\"E, 40°31'40\"N 21°16'43\"E (E94). [A square covering the built settlement structure of Kastoria, Greece] - Martin’s centroid for Kastoria (E53) place is defined by 40°31'01.5\"N 21°15'48\"E (E94). [A point in the lake of Kastoria in the centre of the area covered by the city] - The position measured by Alexander von Humboldt for the Plaza Mayor in Cumaná, Sucre, Venezuela 1799-1800AD (E53) place is defined by 10°27'52\"N 66°30'02\"W (E94). [West of the Observatory of Paris = 64°09'51\"W of Greenwich, actually 1.1km east of today’s Plaza Andrés Eloy Blanco of Cumaná] (Humboldt, 1859) In First Order Logic: - P168(x,y) ⇒ E53(x) - P168(x,y) ⇒ E94(y) """@en ; rdfs:label "P168 lieu défini par"@fr , "P168 place is defined by"@en , "P168 мeсто опрeдeляeтся"@ru ; "P168"@en ; "lieu défini par"@fr , "place is defined by"@en , "мeсто опрeдeляeтся"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P171_at_some_place_within rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes the maximum spatial extent within which an instance of E53 Place falls. Since instances of E53 Places may not have precisely known spatial extents, the CIDOC CRM supports statements about maximum spatial extents of instances of E53 Place. This property allows an instance of E53 Place’s maximum spatial extent (i.e., its outer boundary) to be assigned an instance of E94 Space Primitive value. This property is a shortcut of the fully developed path from E53 Place, P89 falls within, E53 Place, P168 place is defined by to E94 Space Primitive through a declarative Place that is not explicitly documented, to a Space Primitive: declarative places are defined in CRMgeo (Doerr and Hiebel 2013). Examples: - The spatial extent of the Acropolis of Athens (E53) at some place within POLYGON ((37.969172 23.720787, 37.973122 23.721495 37.972741 23.728994, 37.969299 23.729735, 37.969172 23.720787)) (E94). In First Order Logic: - P171(x,y) ⇒ E53(x) - P171(x,y) ⇒ E94(y) - P171(x,y) ⇔ (∃z) [E53(z) ˄ P89(x,z) ˄ P168(z,y)] """@en ; rdfs:label "P171 at some place within"@en , "P171 quelque part dans"@fr , "P171 в нeкотором мeстe внутри"@ru ; "P171"@en ; "at some place within"@en , "quelque part dans"@fr , "в нeкотором мeстe внутри"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P172_contains rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property describes a minimum spatial extent which is contained within an instance of E53 Place. Since instances of E53 Place may not have precisely known spatial extents, the CIDOC CRM supports statements about minimum spatial extents of instances of E53 Place. This property allows an instance of E53 Place’s minimum spatial extent (i.e., its inner boundary or a point being within a Place) to be assigned an instance of E94 Space Primitive value. This property is a shortcut of the fully developed path from E53 Place, P89i contains, E53 Place, P168 place is defined by to E94 Space Primitive. Examples: - The spatial extent of the Acropolis of Athens (E53) contains POINT (37.971431 23.725947) (E94). In First Order Logic: - P172(x,y) ⇒ E53(x) - P172(x,y) ⇒ E94(y) - P172(x,y) ⇔ (∃z) [E53(z) ˄ P89i(x,z) ˄ P168(z,y)] """@en ; rdfs:label "P172 contains"@en , "P172 contient"@fr , "P172 содeржит"@ru ; "P172"@en ; "contains"@en , "contient"@fr , "содeржит"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P190_has_symbolic_content rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:comment """Quantification: many to many (0,n:0,n) Scope note: This property associates an instance of E90 Symbolic Object with a complete, identifying representation of its content in the form of an instance of E62 String. This property only applies to instances of E90 Symbolic Object that can be represented completely in this form. The representation may be more specific than the symbolic level defining the identity condition of the represented. This depends on the type of the symbolic object represented. For instance, if a name has type “Modern Greek character sequence”, it may be represented in a loss-free Latin transcription, meaning however the sequence of Greek letters. As another example, if the represented object has type “English words sequence”, American English or British English spelling variants may be chosen to represent the English word “colour” without defining a different symbolic object. If a name has type “European traditional name”, no particular string may define its content. Examples: - The materials description of the painting (E33) has symbolic content “Oil, French Watercolors on Paper, Graphite and Ink on Canvas, with an Oak frame.” (E62). - The title of Einstein’s 1915 text (E35) has symbolic content “Relativity, the Special and the General Theory” (E62). (Einstein, 2001) - The story of Little Red Riding Hood (E33) has symbolic content “Once upon a time there lived in a certain village.” (E62). (Lang, 1965) - The inscription on Rijksmuseum object SK-A-1601 (E34) has symbolic content “B” (E62). [reference: https://www.rijksmuseum.nl/en/collection/SK-A-1601/catalogue-entry (accessed 10(th) April 2021)] In First Order Logic: - P190(x,y) ⇒ E90(x) - P190(x,y) ⇒ E62(y) """@en ; rdfs:label "P190 a pour contenu symbolique"@fr , "P190 has symbolic content"@en , "P190 имeeт символичeскоe содeржаниe"@ru ; "P190"@en ; "a pour contenu symbolique"@fr , "has symbolic content"@en , "имeeт символичeскоe содeржаниe"@ru . ### http://www.cidoc-crm.org/cidoc-crm/P3_has_note rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: one to many (0,n:0,1) Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CIDOC CRM constructs. In particular, it captures the characterisation of the item itself, its internal structures, appearance, etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CIDOC CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CIDOC CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. “construction”, “decoration”, etc. An item may have many notes, but a note is attached to a specific item. Examples: - Coffee mug – OXCMS:1983.1.1 (E19) has note “chipped at edge of handle” (E62) has type Condition (E55). (fictitious) Properties: - P3.1 has type: E55 Type In First Order Logic: - P3(x,y) ⇒ E1(x) - P3(x,y) ⇒ E62(y) - P3(x,y,z) ⇒ [P3(x,y) ∧ E55(z)] """@en ; rdfs:label "P3 a pour note"@fr , "P3 has note"@en , "P3 hat Anmerkung"@de , "P3 tem nota"@pt , "P3 έχει επεξήγηση"@el , "P3 имeeт примeчаниe"@ru , "P3 有注释"@zh ; "P3"@en ; "a pour note"@fr , "has note"@en , "hat Anmerkung"@de , "tem nota"@pt , "έχει επεξήγηση"@el , "имeeт примeчаниe"@ru , "有注释"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P57_has_number_of_parts rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: many to one (0,1:0,n) Scope note: This property documents the number of parts, an instance of E60 Number, of which an instance of E19 Physical Object is composed. This may be used as a method of checking inventory counts with regard to aggregate or collective objects. What constitutes a part or component depends on the context and requirements of the documentation. Normally, the parts documented in this way would not be considered as worthy of individual attention. For a more complete description, objects may be decomposed into their components and constituents using P46 is composed of (forms parts of) and P45 consists of (is incorporated in). This allows each element to be described individually. Examples: - Chess set 233 (E22) has number of parts 33 (E60). (fictitious) In First Order Logic: - P57(x,y) ⇒ E19(x) - P57(x,y) ⇒ E60(y) """@en ; rdfs:label "P57 a pour nombre d’éléments"@fr , "P57 has number of parts"@en , "P57 hat Anzahl Teile"@de , "P57 tem número de partes"@pt , "P57 έχει αριθμό μερών"@el , "P57 имeeт число частeй"@ru , "P57 有组成部分数"@zh ; "P57"@en ; "a pour nombre d’éléments"@fr , "has number of parts"@en , "hat Anzahl Teile"@de , "tem número de partes"@pt , "έχει αριθμό μερών"@el , "имeeт число частeй"@ru , "有组成部分数"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P79_beginning_is_qualified_by rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:comment """Quantification: many to one (0,1:0,n) Scope note: This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the certainty, precision, sources etc. of its beginning. Such notes may also be used to elaborate arguments about constraints or to give explanations of alternatives. Examples: - The time-span of the Holocene (E52) beginning is qualified by “The formal definition and dating of the GSSP (GlobalStratotype Section and Point) for the base of the Holocene using the Greenland NGRIP ice core, and selected auxiliary records” (E62). (Walker et al., 2009) In First Order Logic: - P79(x,y) ⇒ E52(x) - P79(x,y) ⇒ E62(y) - P79(x,y) ⇒ P3(x,y) """@en ; rdfs:label "P79 a son début qualifié par"@fr , "P79 beginning is qualified by"@en , "P79 hat Anfangsbegründung"@de , "P79 início é qualificado por"@pt , "P79 αρχή προσδιορίζεται από"@el , "P79 начало ограничeно"@ru , "P79 起始限定"@zh ; "P79"@en ; "a son début qualifié par"@fr , "beginning is qualified by"@en , "hat Anfangsbegründung"@de , "início é qualificado por"@pt , "αρχή προσδιορίζεται από"@el , "начало ограничeно"@ru , "起始限定"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P80_end_is_qualified_by rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:comment """Quantification: many to one (0,1:0,n) Scope note: This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the end of this time-span concerning certainty, precision, sources etc. This property may also be used to describe arguments constraining possible dates and to distinguish reasons for alternative dates. Examples: - The time-span of the Holocene (E52) end is qualified by “still ongoing” (E62). (Walker et al., 2009) In First Order Logic: - P80(x,y) ⇒ E52(x) - P80(x,y) ⇒ E62(y) - P80(x,y) ⇒ P3(x,y) """@en ; rdfs:label "P80 a sa fin qualifiée par"@fr , "P80 end is qualified by"@en , "P80 final é qualificado por"@pt , "P80 hat Begründung des Endes"@de , "P80 τέλος προσδιορίζεται από"@el , "P80 конeц ограничeн"@ru , "P80 结束限定"@zh ; "P80"@en ; "a sa fin qualifiée par"@fr , "end is qualified by"@en , "final é qualificado por"@pt , "hat Begründung des Endes"@de , "τέλος προσδιορίζεται από"@el , "конeц ограничeн"@ru , "结束限定"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P81_ongoing_throughout rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property associates an instance of E52 Time-Span with an instance of E61 Time Primitive specifying a minimum period of time covered by it. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s minimum temporal extent (i.e., its inner boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different minimum extents without contradicting each other, the smallest interval including all these extents will be the best estimate. This should be taken into account for information integration. Examples: - The time-span of the development of the CIDOC CRM (E52) ongoing throughout “1996-2003” (E61). (Doerr, 2003) - The Time-Span of the Thirty Years War (E52) ongoing throughout “23(rd) May 1618 AD until 24(th) October 1648 AD” (E61). (Bonney, 2014) - The time-span of the First Intermediate Period of Ancient Egypt (7(th) to 10(th) dynasty) (E52) ongoing throughout “2181 BC – 2160 BC” (E61). (Reid, 1993) [This is the minimal common agreement of two conflicting dates: James Henry Breasted dates the First Intermediate Period of Ancient Egypt (7(th) to 10(th) dynasty) from 2475BC to 2160BC in his Ancient Records (first published in 1906), volume 1, sections 58–75 (Breasted, 1906). Ian Shaw dates it from 2181BC to 2125BC in his Oxford History of Ancient Egypt (published in 2000), pp. 479–483 (Shaw, 2000).] In First Order Logic: - P81(x,y) ⇒ E52(x) - P81(x,y) ⇒ E61(y) """@en ; rdfs:label "P81 a couvert"@fr , "P81 abrange no mínimo"@pt , "P81 andauernd während"@de , "P81 ongoing throughout"@en , "P81 καθόλη τη διάρκεια του/της"@el , "P81 длится в тeчeниe"@ru , "P81 最短范围是"@zh ; "P81"@en ; "a couvert"@fr , "abrange no mínimo"@pt , "andauernd während"@de , "ongoing throughout"@en , "καθόλη τη διάρκεια του/της"@el , "длится в тeчeниe"@ru , "最短范围是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P82_at_some_time_within rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: many to many, necessary (1,n:0,n) Scope note: This property describes the maximum period of time within which an E52 Time-Span falls. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s maximum temporal extent (i.e. its outer boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different maximum extents without contradicting each other, the resulting intersection of all these extents will be the best estimate. This should be taken into account for information integration. Examples: - The time-span of the development of the CIDOC CRM (E52) at some time within “1992-infinity” (E61). (Doerr, 2003) - The Time-Span of the Battle in the Teutoburg Forest (E52) at some time within “September 9 CE” (E61). (Andrews & Kesteven, 1977) - The time-Span of the death of Tut Ankh Amun (E52) at some time within “December 1324 BC to February 1323 BC” (E61). (Murdoch, 2003) - The time-span of the First Intermediate Period of Ancient Egypt (7(th) to 10(th) dynasty) (E52) at some time within “2475BC - 2125BC” (E61). (Reid, 1993) In First Order Logic: - P82(x,y) ⇒ E52(x) - P82(x,y) ⇒ E61(y) """@en ; rdfs:label "P82 a eu lieu durant"@fr , "P82 abrange no máximo"@pt , "P82 at some time within"@en , "P82 irgendwann innerhalb von"@de , "P82 κάποτε εντός"@el , "P82 в тeчeниe пeриода врeмeни"@ru , "P82 最长范围是"@zh ; "P82"@en ; "a eu lieu durant"@fr , "abrange no máximo"@pt , "at some time within"@en , "irgendwann innerhalb von"@de , "κάποτε εντός"@el , "в тeчeниe пeриода врeмeни"@ru , "最长范围是"@zh . ### http://www.cidoc-crm.org/cidoc-crm/P90_has_value rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:comment """Quantification: many to one, necessary (1,1:0,n) Scope note: This property allows an instance of E54 Dimension to be approximated by an instance of E60 Number primitive. Examples: - The height of silver cup 232 (E54) has value 226 (E60). (fictitious) - Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987 (E97) has value 24,750,000 (E60). In First Order Logic: - P90(x,y) ⇒ E54(x) - P90(x,y) ⇒ E60(y) """@en ; rdfs:label "P90 a pour valeur"@fr , "P90 has value"@en , "P90 hat Wert"@de , "P90 tem valor"@pt , "P90 έχει τιμή"@el , "P90 имeeт значeниe"@ru , "P90 有数值"@zh ; "P90"@en ; "a pour valeur"@fr , "has value"@en , "hat Wert"@de , "tem valor"@pt , "έχει τιμή"@el , "имeeт значeниe"@ru , "有数值"@zh . ### http://www.w3.org/ns/odrl/2/rightOperand rdf:type owl:DatatypeProperty . ### http://www.w3.org/ns/prov#atTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "The time at which an InstantaneousEvent occurred, in the form of xsd:dateTime."@en ; rdfs:isDefinedBy ; rdfs:label "atTime" ; "qualified" ; "entities-activities" ; ; , , , . ### http://www.w3.org/ns/prov#endedAtTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "The time at which an activity ended. See also prov:startedAtTime."@en ; rdfs:isDefinedBy ; rdfs:label "endedAtTime" ; "starting-point" ; "entities-activities" ; "It is the intent that the property chain holds: (prov:qualifiedEnd o prov:atTime) rdfs:subPropertyOf prov:endedAtTime."@en ; , . ### http://www.w3.org/ns/prov#generatedAtTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "The time at which an entity was completely created and is available for use."@en ; rdfs:isDefinedBy ; rdfs:label "generatedAtTime" ; "expanded" ; "entities-activities" ; "It is the intent that the property chain holds: (prov:qualifiedGeneration o prov:atTime) rdfs:subPropertyOf prov:generatedAtTime."@en ; , . ### http://www.w3.org/ns/prov#invalidatedAtTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "The time at which an entity was invalidated (i.e., no longer usable)."@en ; rdfs:isDefinedBy ; rdfs:label "invalidatedAtTime" ; "expanded" ; "entities-activities" ; "It is the intent that the property chain holds: (prov:qualifiedInvalidation o prov:atTime) rdfs:subPropertyOf prov:invalidatedAtTime."@en ; , . ### http://www.w3.org/ns/prov#startedAtTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "The time at which an activity started. See also prov:endedAtTime."@en ; rdfs:isDefinedBy ; rdfs:label "startedAtTime" ; "starting-point" ; "entities-activities" ; "It is the intent that the property chain holds: (prov:qualifiedStart o prov:atTime) rdfs:subPropertyOf prov:startedAtTime."@en ; , . ### http://www.w3.org/ns/prov#value rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:isDefinedBy ; rdfs:label "value" ; "expanded" ; "entities-activities" ; "Provides a value that is a direct representation of an entity."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-value"^^xsd:anyURI ; "This property serves the same purpose as rdf:value, but has been reintroduced to avoid some of the definitional ambiguity in the RDF specification (specifically, 'may be used in describing structured values')."@en , "The editor's definition comes from http://www.w3.org/TR/rdf-primer/#rdfvalue" . ################################################################# # Classes ################################################################# ### http://purl.org/dc/terms/Agent rdf:type owl:Class ; owl:equivalentClass . ### http://schema.org/Action rdf:type owl:Class . ### http://schema.org/CreativeWork rdf:type owl:Class ; owl:equivalentClass . ### http://schema.org/Organization rdf:type owl:Class . ### http://schema.org/Person rdf:type owl:Class . ### http://w3id.org/cacao/CACAO_0000002 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-11-13T16:18:33Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises agents, whether human individuals, groups, or non-human entities such as software applications, algorithms, or automated processes, that interact with digital systems or services by initiating actions, consuming resources, or producing outputs. Users are characterized by their capacity to perform intentional actions within a digital environment, for which they can be held responsible.​ Unlike E21 Person, which is limited to real or assumed human individuals, the class User encompasses a broader range of agents, including non-human actors that operate autonomously or semi-autonomously within digital contexts. This includes, but is not limited to, artificial intelligence models, automated scripts, and other algorithmic entities that engage with web services or digital platforms.​ The classification of an entity as a User does not necessitate legal personhood or consciousness; rather, it is based on the entity's functional role in interacting with digital systems in a manner that can be documented and attributed.​ Examples: - A registered individual accessing an online museum catalog.​ - An AI-driven recommendation engine suggesting artifacts to users.​ - A software bot performing automated data curation tasks.​"""@en ; rdfs:label "User"@en ; """rdfs:comment \"Scope note: This class comprises agents, whether human individuals, groups, or non-human entities such as software applications, algorithms, or automated processes, that interact with digital systems or services by initiating actions, consuming resources, or producing outputs. Users are characterized by their capacity to perform intentional actions within a digital environment, for which they can be held responsible.​ Unlike E21 Person, which is limited to real or assumed human individuals, the class User encompasses a broader range of agents, including non-human actors that operate autonomously or semi-autonomously within digital contexts. This includes, but is not limited to, artificial intelligence models, automated scripts, and other algorithmic entities that engage with web services or digital platforms.​ The classification of an entity as a User does not necessitate legal personhood or consciousness; rather, it is based on the entity's functional role in interacting with digital systems in a manner that can be documented and attributed.​ Examples: - A registered individual accessing an online museum catalog.​ - An AI-driven recommendation engine suggesting artifacts to users.​ - A software bot performing automated data curation tasks.​\"@en""" . ### http://w3id.org/cacao/CACAO_0000003 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-11-13T16:20:05Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises identifiable immaterial items, such as digital images, texts, multimedia objects, computer program code, algorithms, or mathematical formulae, that are created, modified, or stored in digital formats. Digital Artefacts have an objectively recognizable structure and are documented as single units. They exist independently of specific physical carriers and can reside on multiple digital mediums simultaneously. While E73 Information Objects encompass a broad range of immaterial items, including those stored in human memory or on physical media, Digital Artefacts are specifically associated with digital technologies. This subclassification aids in distinguishing between general information entities and those uniquely tied to digital environments.​ Examples: - A digital photograph of an ancient manuscript.​ - A 3D model of an archaeological excavation site.​ - The source code of a software application developed to catalog museum collections.​ - A dataset containing measurements of physical artefacts."""@en ; rdfs:label "Digital Artefact"@en ; """rdfs:comment \"Scope note: This class comprises identifiable immaterial items, such as digital images, texts, multimedia objects, computer program code, algorithms, or mathematical formulae, that are created, modified, or stored in digital formats. Digital Artefacts have an objectively recognizable structure and are documented as single units. They exist independently of specific physical carriers and can reside on multiple digital mediums simultaneously. While E73 Information Objects encompass a broad range of immaterial items, including those stored in human memory or on physical media, Digital Artefacts are specifically associated with digital technologies. This subclassification aids in distinguishing between general information entities and those uniquely tied to digital environments.​ Examples: - A digital photograph of an ancient manuscript.​ - A 3D model of an archaeological excavation site.​ - The source code of a software application developed to catalog museum collections.​ - A dataset containing measurements of physical artefacts.\"@en""" . ### http://w3id.org/cacao/CACAO_0000005 rdf:type owl:Class ; rdfs:subClassOf , ; ; "2024-11-19T12:02:07Z"^^xsd:dateTime ; rdfs:label "Historical Event"@en ; "A specialized version of E5_Event, where we only refer to events with historical value. Historical value reflects the role that the heritage item has played in a broader historical narrative, offering insights into cultural, political, social, or technological contexts of specific periods." . ### http://w3id.org/cacao/CACAO_0000010 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-11-19T12:50:33Z"^^xsd:dateTime ; "From wikidata (Q49773): loosely organized effort by a large group of people to achieve a particular set of goals" ; rdfs:comment """From wikidata (Q49773): loosely organized effort by a large group of people to achieve a particular set of goals Scope note: A Social Movement is a loosely organized effort by a large group of people to achieve a particular set of goals, typically aiming to promote or resist changes in society's structure or values. These movements are characterized by collective action, where individuals unite based on shared beliefs or objectives, often seeking social, political, economic, or cultural transformations. ​ Social movements differ from formal organizations in that they may lack a defined organizational structure or formal membership, relying instead on informal networks and shared commitments. They can vary widely in size and scope, ranging from localized grassroots initiatives to large-scale national or international campaigns. The methods employed can include protests, demonstrations, advocacy, and other forms of collective action aimed at influencing public opinion and policy. ​ Examples: - The Civil Rights Movement in the United States, - The Environmental Movement - The Feminist Movement, - The LGBTQ+ Rights Movement"""@en ; rdfs:label "Social movement"@en ; """rdfs:comment \"From wikidata (Q49773): loosely organized effort by a large group of people to achieve a particular set of goals Scope note: A Social Movement is a loosely organized effort by a large group of people to achieve a particular set of goals, typically aiming to promote or resist changes in society's structure or values. These movements are characterized by collective action, where individuals unite based on shared beliefs or objectives, often seeking social, political, economic, or cultural transformations. ​ Social movements differ from formal organizations in that they may lack a defined organizational structure or formal membership, relying instead on informal networks and shared commitments. They can vary widely in size and scope, ranging from localized grassroots initiatives to large-scale national or international campaigns. The methods employed can include protests, demonstrations, advocacy, and other forms of collective action aimed at influencing public opinion and policy. ​ Examples: - The Civil Rights Movement in the United States, - The Environmental Movement - The Feminist Movement, - The LGBTQ+ Rights Movement\"@en""" . ### http://w3id.org/cacao/CACAO_0000011 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-11-19T12:51:24Z"^^xsd:dateTime ; "Wikidata: Q1826286, social and ideological movement in the religious sphere" ; rdfs:comment """Wikidata: Q1826286, social and ideological movement in the religious sphere Scope note: A Religious Movement is a collective effort by a group of people aiming to promote, reform, or resist changes within religious beliefs, practices, or institutions. Examples: - The Protestant Reformation in the 16th century, which led to significant changes in Christian practices and beliefs.​ - The Charismatic Movement, emphasizing direct personal experience of God through baptism with the Holy Spirit.​ - The New Age Movement, a broad range of spiritual or religious beliefs and practices that developed in the Western world during the 1970s."""@en ; rdfs:label "Religious movement"@en ; """rdfs:comment \"Wikidata: Q1826286, social and ideological movement in the religious sphere Scope note: A Religious Movement is a collective effort by a group of people aiming to promote, reform, or resist changes within religious beliefs, practices, or institutions. Examples: - The Protestant Reformation in the 16th century, which led to significant changes in Christian practices and beliefs.​ - The Charismatic Movement, emphasizing direct personal experience of God through baptism with the Holy Spirit.​ - The New Age Movement, a broad range of spiritual or religious beliefs and practices that developed in the Western world during the 1970s.\"@en""" . ### http://w3id.org/cacao/CACAO_0000012 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-11-19T12:51:32Z"^^xsd:dateTime ; "Wikidata: Q2198855, period and movement in cultural history" ; rdfs:comment """Wikidata: Q2198855, period and movement in cultural history Scope note: A Cultural Movement is a collective effort by loosely affiliated individuals aiming to transform societal perspectives through the dissemination of ideas via various art forms and intentional lifestyle choices. These movements often overlap with social and political movements, making them integral to broader cultural transformations. ​ Examples: - The Renaissance - The Romanticism movement - The Alté Movement in Nigeria"""@en ; rdfs:label "Cultural movement"@en ; """rdfs:comment \"Wikidata: Q2198855, period and movement in cultural history Scope note: A Cultural Movement is a collective effort by loosely affiliated individuals aiming to transform societal perspectives through the dissemination of ideas via various art forms and intentional lifestyle choices. These movements often overlap with social and political movements, making them integral to broader cultural transformations. ​ Examples: - The Renaissance - The Romanticism movement - The Alté Movement in Nigeria\"@en""" . ### http://w3id.org/cacao/CACAO_0000013 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-11-19T12:51:42Z"^^xsd:dateTime ; "Wikidata: Q2738074, movement to obtain a political goal" ; rdfs:comment """Wikidata: Q2738074, movement to obtain a political goal Scope note: A Political Movement is a collective effort by a group of people aiming to influence government policy, social values, or achieve specific political objectives. These movements are typically organized around particular issues or ideologies and seek to bring about change within the political system. They differ from political parties, which aim to gain political office, by focusing on specific goals rather than seeking electoral power. ​ Examples: - The Anti-Apartheid Movement, which campaigned against the system of racial segregation in South Africa.​ - The Tea Party Movement in the United States, advocating for reduced government spending and taxation.​ - The Brexit Movement, which sought the United Kingdom's withdrawal from the European Union.""" ; rdfs:label "Political movement"@en ; """rdfs:comment \"Wikidata: Q2738074, movement to obtain a political goal Scope note: A Political Movement is a collective effort by a group of people aiming to influence government policy, social values, or achieve specific political objectives. These movements are typically organized around particular issues or ideologies and seek to bring about change within the political system. They differ from political parties, which aim to gain political office, by focusing on specific goals rather than seeking electoral power. ​ Examples: - The Anti-Apartheid Movement, which campaigned against the system of racial segregation in South Africa.​ - The Tea Party Movement in the United States, advocating for reduced government spending and taxation.​ - The Brexit Movement, which sought the United Kingdom's withdrawal from the European Union.\"""" . ### http://w3id.org/cacao/CACAO_0000014 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-12-06T13:27:25Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises categories or fields of specialized knowledge, disciplines, or areas of expertise that are used to classify and contextualize instances of CIDOC CRM classes. Instances of Domain represent specific spheres of human thought or activity, providing a framework for understanding the context, provenance, or thematic classification of cultural heritage information.​ The Domain class serves as a means to associate cultural heritage entities with particular areas of study or professional practice, facilitating interdisciplinary research and knowledge organization. For example, associating an artifact with the domain of \"archaeology\" or \"art history\" helps in understanding its scholarly context and the methodologies applied to its study.​ Examples: - Archaeology​ - Art History​ - Ethnomusicology​ - Conservation Science"""@en ; rdfs:label "Domain"@en ; """rdfs:comment \"Scope note: This class comprises categories or fields of specialized knowledge, disciplines, or areas of expertise that are used to classify and contextualize instances of CIDOC CRM classes. Instances of Domain represent specific spheres of human thought or activity, providing a framework for understanding the context, provenance, or thematic classification of cultural heritage information.​ The Domain class serves as a means to associate cultural heritage entities with particular areas of study or professional practice, facilitating interdisciplinary research and knowledge organization. For example, associating an artifact with the domain of \\\"archaeology\\\" or \\\"art history\\\" helps in understanding its scholarly context and the methodologies applied to its study.​ Examples: - Archaeology​ - Art History​ - Ethnomusicology​ - Conservation Science\"@en""" . ### http://w3id.org/cacao/CACAO_0000015 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-12-06T13:30:25Z"^^xsd:dateTime ; rdfs:comment """Scope note: Economic Relevance pertains to concepts that define the economic significance or impact of entities, events, or activities. This class encompasses terms and categories used to classify and assess the economic aspects of cultural heritage items, historical events, or societal practices. Examples: - The economic impact of the Silk Road trade routes on participating civilizations.​ - The assessment of a museum's collection in terms of its monetary value and contribution to tourism revenue.​ - Analysis of the financial significance of a historical event, such as the Industrial Revolution, on global markets."""@en ; rdfs:label "Economic Relevance"@en ; """rdfs:comment \"Scope note: This class comprises categories or fields of specialized knowledge, disciplines, or areas of expertise that are used to classify and contextualize instances of CIDOC CRM classes. Instances of Domain represent specific spheres of human thought or activity, providing a framework for understanding the context, provenance, or thematic classification of cultural heritage information.​ The Domain class serves as a means to associate cultural heritage entities with particular areas of study or professional practice, facilitating interdisciplinary research and knowledge organization. For example, associating an artifact with the domain of \\\"archaeology\\\" or \\\"art history\\\" helps in understanding its scholarly context and the methodologies applied to its study.​ Examples: - Archaeology​ - Art History​ - Ethnomusicology​ - Conservation Science\"@en""" . ### http://w3id.org/cacao/CACAO_0000016 rdf:type owl:Class ; rdfs:subClassOf ; ; "2024-12-06T13:43:53Z"^^xsd:dateTime ; rdfs:label "Symbolism"@en ; """Scope note: This class comprises the concepts, ideas, or qualities that an object, character, or event represents. Symbolism provides a deeper, often abstract, meaning that transcends the literal interpretation of an entity, reflecting cultural, religious, or historical contexts. It serves to connect a physical or conceptual entity to a broader narrative or ideology. Examples: - A dove representing peace. - The lion as a symbol of courage and royalty. - A skull symbolizing death and mortality (memento mori).""" . ### http://w3id.org/cacao/CACAO_0000019 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:38:37Z"^^xsd:dateTime ; rdfs:label "Building"@en ; """Scope note: This class comprises man-made structures with a roof and walls, created to stand more or less permanently in one place. It serves as a superclass for more specific types of structures defined by their function or form, such as religious, residential, or ceremonial buildings.""" . ### http://w3id.org/cacao/CACAO_0000020 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-04-11T08:31:05Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises organizations that are established to collect, preserve, research, interpret, and exhibit tangible and intangible cultural heritage for the purposes of education, study, and enjoyment. Museums operate as collective entities, often encompassing various departments and professionals, and may be public or private institutions.​ As instances of E74 Group, museums are characterized by their organizational structure and collective actions aimed at the stewardship of cultural artifacts and information. They may also engage in activities such as publishing, educational programming, and community outreach.​ Museums can vary widely in scope and specialization, including but not limited to art museums, history museums, science museums, and ethnographic museums. Their defining feature is the systematic curation and presentation of collections to the public or specific audiences.​ Examples: - The British Museum​ - The Louvre​ - The Metropolitan Museum of Art​ - The National Museum of Denmark"""@en ; rdfs:label "Museum"@en ; """rdfs:comment \"Scope note: This class comprises organizations that are established to collect, preserve, research, interpret, and exhibit tangible and intangible cultural heritage for the purposes of education, study, and enjoyment. Museums operate as collective entities, often encompassing various departments and professionals, and may be public or private institutions.​ As instances of E74 Group, museums are characterized by their organizational structure and collective actions aimed at the stewardship of cultural artifacts and information. They may also engage in activities such as publishing, educational programming, and community outreach.​ Museums can vary widely in scope and specialization, including but not limited to art museums, history museums, science museums, and ethnographic museums. Their defining feature is the systematic curation and presentation of collections to the public or specific audiences.​ Examples: - The British Museum​ - The Louvre​ - The Metropolitan Museum of Art​ - The National Museum of Denmark\"@en""" . ### http://w3id.org/cacao/CACAO_0000021 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:45:29Z"^^xsd:dateTime ; rdfs:label "Religious Buildings"@en ; """Scope note: This class comprises structures designed and utilized for religious or spiritual activities, including worship, ceremony, and contemplation. These buildings are often characterized by specific architectural forms and iconographic elements that reflect the beliefs and practices of a particular faith or denomination.""" . ### http://w3id.org/cacao/CACAO_0000022 rdf:type owl:Class ; rdfs:subClassOf , ; ; "2025-04-11T08:32:18Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises persons who are recognized for engaging in the creation or performance of works in the visual, performing, literary, or applied arts. This includes, but is not limited to, painters, sculptors, musicians, composers, writers, poets, actors, dancers, designers, and multimedia artists. An individual is regarded as an instance of Artist when there exists documented evidence of their engagement in artistic practices or when they are attributed with the authorship, performance, or conceptualization of artistic works, either by themselves or by third parties (such as curators, critics, or historical sources). Artists may be associated with specific cultural movements, artistic periods, or creative practices. The classification of a Person as an Artist does not require professional status or formal recognition; amateur and self-taught individuals are also included when their artistic activity is documented and contextually significant. In bibliographic or curatorial contexts, attribution of a creative work to an individual is sufficient to regard them as an Artist, even if the attribution is anonymous, pseudonymous, or contested. Examples: - Leonardo da Vinci - Frida Kahlo - William Shakespeare - Maya Deren"""@en ; rdfs:label "Artist"@en ; """Scope note: This class comprises persons who are recognized for engaging in the creation or performance of works in the visual, performing, literary, or applied arts. This includes, but is not limited to, painters, sculptors, musicians, composers, writers, poets, actors, dancers, designers, and multimedia artists. An individual is regarded as an instance of Artist when there exists documented evidence of their engagement in artistic practices or when they are attributed with the authorship, performance, or conceptualization of artistic works, either by themselves or by third parties (such as curators, critics, or historical sources). Artists may be associated with specific cultural movements, artistic periods, or creative practices. The classification of a Person as an Artist does not require professional status or formal recognition; amateur and self-taught individuals are also included when their artistic activity is documented and contextually significant. In bibliographic or curatorial contexts, attribution of a creative work to an individual is sufficient to regard them as an Artist, even if the attribution is anonymous, pseudonymous, or contested. Examples: - Leonardo da Vinci - Frida Kahlo - William Shakespeare - Maya Deren""" . ### http://w3id.org/cacao/CACAO_0000023 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-04-11T08:35:55Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises all persistent physical objects of any size that are purposely created by human activity and have physical boundaries that separate them completely in an objective way from other objects. The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen.​ Physical Artefacts are distinguished by their tangible nature and intentional creation, serving various purposes such as utility, artistic expression, or cultural significance. They may range from individual items like tools and artworks to assembled collections designed to function as a whole.​ Examples: - The Rosetta Stone - LNER Class A4 4468 Mallard [the World’s fastest steam locomotive, preserved at the National Railway Museum of York, UK] - The Portland Vase"""@en ; rdfs:label "Physical Artefact"@en . ### http://w3id.org/cacao/CACAO_0000024 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-04-11T08:37:01Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises physical artefacts that are primarily created as expressions of aesthetic, conceptual, or symbolic intent. Artworks encompass a wide range of tangible objects produced through artistic practices, including but not limited to paintings, sculptures, installations, and mixed-media pieces.​ Artworks are distinguished by their purpose of conveying artistic expression, emotion, or commentary, rather than serving utilitarian functions. They are often characterized by their unique form, style, and the creative processes involved in their production.​ While all artworks are physical artefacts, not all physical artefacts qualify as artworks; the classification depends on the creator's intent and the cultural context attributing artistic value to the object.​ CIDOC CRM Examples: - The Mona Lisa by Leonardo da Vinci​ - The Thinker by Auguste Rodin​ - The Starry Night by Vincent van Gogh​ - Balloon Dog (Red) by Jeff Koons"""@en ; rdfs:label "Artwork"@en . ### http://w3id.org/cacao/CACAO_0000025 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-04-11T08:37:08Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises physical artefacts that are intentionally created and utilized by humans to produce, modify, or measure sound, music, or other forms of audio. Instruments are designed with specific acoustic properties or mechanisms to facilitate the creation or manipulation of auditory phenomena. This includes, but is not limited to, musical instruments such as string, wind, percussion, and electronic instruments.​ Instruments are characterized by their functional design aimed at generating or controlling sound, distinguishing them from other physical artefacts. They may vary in complexity from simple objects like drums and flutes to intricate devices like synthesizers and orchestral instruments.​ Examples: - A Stradivarius violin​ - A Steinway grand piano​ - A traditional African djembe drum​ - A Moog synthesizer"""@en ; rdfs:label "Instrument"@en . ### http://w3id.org/cacao/CACAO_0000027 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-04-11T11:18:31Z"^^xsd:dateTime ; rdfs:comment """Scope note: The Genre class encompasses concepts that denote specific categories or styles of creative works, including but not limited to:​ - Music Genres: Such as classical, jazz, rock, or electronic.​ - Film Genres: Including drama, comedy, thriller, or documentary.​ - Artistic Genres: Like impressionism, surrealism, or abstract expressionism.​ - Literary Genres: Such as fiction, non-fiction, poetry, or drama.​ Instances of the Genre class provide a means to classify and contextualize creative works within their respective domains, enhancing the discovery and analysis of cultural heritage materials based on their genre-specific characteristics.​ Examples: - Jazz (music genre)​ - Film Noir (film genre)​ - Renaissance Art (artistic genre)​ - Science Fiction (literary genre)"""@en ; rdfs:label "Genre"@en ; """rdfs:comment \"Scope note: The Genre class encompasses concepts that denote specific categories or styles of creative works, including but not limited to:​ - Music Genres: Such as classical, jazz, rock, or electronic.​ - Film Genres: Including drama, comedy, thriller, or documentary.​ - Artistic Genres: Like impressionism, surrealism, or abstract expressionism.​ - Literary Genres: Such as fiction, non-fiction, poetry, or drama.​ Instances of the Genre class provide a means to classify and contextualize creative works within their respective domains, enhancing the discovery and analysis of cultural heritage materials based on their genre-specific characteristics.​ Examples: - Jazz (music genre)​ - Film Noir (film genre)​ - Renaissance Art (artistic genre)​ - Science Fiction (literary genre)\"@en""" . ### http://w3id.org/cacao/CACAO_0000028 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-04-11T11:18:41Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises concepts that denote areas of professional, academic, or creative activity in which individuals, groups, or organizations engage. Instances of Field of Work represent specific domains of expertise or practice, such as \"architecture,\" \"literature,\" or \"engineering,\" and are used to classify and contextualize the roles, contributions, or affiliations of persons within the CIDOC CRM framework.​ By associating persons with a Field of Work, one can provide semantic context regarding the nature of their activities or specializations. Examples: - Architecture​ - Literature​ - Engineering​ - Performing Arts​"""@en ; rdfs:label "Field Of Work"@en ; """rdfs:comment \"Scope note: This class comprises concepts that denote areas of professional, academic, or creative activity in which individuals, groups, or organizations engage. Instances of Field of Work represent specific domains of expertise or practice, such as \\\"architecture,\\\" \\\"literature,\\\" or \\\"engineering,\\\" and are used to classify and contextualize the roles, contributions, or affiliations of persons within the CIDOC CRM framework.​ By associating persons with a Field of Work, one can provide semantic context regarding the nature of their activities or specializations. Examples: - Architecture​ - Literature​ - Engineering​ - Performing Arts​\"@en""" . ### http://w3id.org/cacao/CACAO_0000029 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:45:45Z"^^xsd:dateTime ; rdfs:label "Churches"@en ; """Scope note: This class comprises buildings specifically designed and used for public Christian worship, prayer, and ceremony. The architectural form and features of a church are often symbolic of Christian beliefs and liturgical practices.""" . ### http://w3id.org/cacao/CACAO_0000036 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-04-12T09:17:34Z"^^xsd:dateTime ; rdfs:comment """Scope note: This class comprises concepts that denote distinct movements or scenes in the realms of literature, art, science, or philosophy. It is used to classify and contextualize creative and intellectual currents by grouping together works or individuals according to shared aesthetics, ideologies, methodologies, or historical trends. Examples: - Impressionism - Romanticism - Modernism - Existentialism"""@en ; rdfs:label "Movement"@en ; """rdfs:comment \"Scope note: This class comprises concepts that denote distinct movements or scenes in the realms of literature, art, science, or philosophy. It is used to classify and contextualize creative and intellectual currents by grouping together works or individuals according to shared aesthetics, ideologies, methodologies, or historical trends. Examples: - Impressionism - Romanticism - Modernism - Existentialism\"@en""" . ### http://w3id.org/cacao/CACAO_0000037 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:46:10Z"^^xsd:dateTime ; rdfs:label "Basilicas"@en ; """Scope note: This class comprises churches that have been granted special privileges by the Pope due to their historical, spiritual, or architectural significance. In architectural terms, it can also refer to a building style characterized by a rectangular plan with a central nave and aisles, and an apse at one or both ends.""" . ### http://w3id.org/cacao/CACAO_0000041 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:46:32Z"^^xsd:dateTime ; rdfs:label "Cathedrals"@en ; "This class comprises the principal church of a diocese, containing the bishop's official throne (cathedra). Cathedrals serve as the central church of a region and are often among the most architecturally significant and historically important buildings in their area." . ### http://w3id.org/cacao/CACAO_0000042 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:47:51Z"^^xsd:dateTime ; rdfs:label "Chapels"@en ; """Scope note: This class comprises small places of Christian worship, which may be part of a larger institution (like a cathedral, palace, or hospital), or can be a standalone building. They are often intended for private prayer or smaller services.""" . ### http://w3id.org/cacao/CACAO_0000043 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:48:27Z"^^xsd:dateTime ; rdfs:label "Temples"@en ; """Scope note: This class comprises buildings reserved for religious or spiritual rituals and activities such as prayer and sacrifice. It is a term used for houses of worship in many different religions.""" . ### http://w3id.org/cacao/CACAO_0000044 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:48:42Z"^^xsd:dateTime ; rdfs:label "Domus Ecclesiae"@en ; """Scope note: This class comprises private buildings adapted for Christian worship. These \"house churches\" were the earliest places of public worship for the Christian community, often established within existing residential structures.""" . ### http://w3id.org/cacao/CACAO_0000045 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:49:10Z"^^xsd:dateTime ; rdfs:label "Mosques"@en ; """Scope note: This class comprises buildings that serve as places of worship for Muslims. Mosques are characterized by specific features such as a mihrab (prayer niche indicating the direction of Mecca) and a minbar (pulpit).""" . ### http://w3id.org/cacao/CACAO_0000046 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:50:08Z"^^xsd:dateTime ; rdfs:label "Structures"@en ; """Scope note: This class comprises man-made objects that are constructed or organized in a particular way, often on a large scale. This class is a superclass for buildings and other constructed entities that may not be fully enclosed.""" . ### http://w3id.org/cacao/CACAO_0000049 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:52:27Z"^^xsd:dateTime ; rdfs:label "Mosaics"@en ; """Scope note: This class comprises artworks created by assembling small pieces of material, such as stone, glass, or ceramic, known as tesserae. These pieces are set into an adhesive surface, such as plaster or mortar, to form an image or pattern. Mosaics are typically used to decorate floors, walls, or ceilings.""" . ### http://w3id.org/cacao/CACAO_0000050 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:54:47Z"^^xsd:dateTime ; rdfs:label "Open Spaces"@en ; """Scope note: This class comprises unenclosed areas within a built environment that are designed for public use, gathering, or passage. These spaces are defined by the architectural and landscape elements that surround them.""" . ### http://w3id.org/cacao/CACAO_0000051 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:54:51Z"^^xsd:dateTime ; rdfs:label "Forums"@en ; """Scope note: This class comprises public squares or marketplaces in ancient Roman cities, which served as the center for judicial, civic, and commercial activities. They were typically surrounded by public buildings and colonnades.""" . ### http://w3id.org/cacao/CACAO_0000052 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:55:50Z"^^xsd:dateTime ; rdfs:label "Residential Buildings"@en ; """Scope note: This class comprises buildings designed and used for human habitation. It encompasses various forms of domestic architecture, from single-family homes to larger, more complex dwellings.""" . ### http://w3id.org/cacao/CACAO_0000053 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:56:01Z"^^xsd:dateTime ; rdfs:label "Houses"@en ; """Scope note: This class comprises buildings designed as a dwelling for a single family or a small group of individuals. It is a fundamental unit of residential architecture.""" . ### http://w3id.org/cacao/CACAO_0000054 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:56:22Z"^^xsd:dateTime ; rdfs:label "Villas"@en ; """Scope note: This class comprises large, luxurious country houses with substantial grounds. Originally referring to large Roman country estates, the term is now used for significant rural or suburban residences.""" . ### http://w3id.org/cacao/CACAO_0000055 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:56:56Z"^^xsd:dateTime ; rdfs:label "Domus"@en ; """Scope note: This class comprises a type of house occupied by the upper classes and some wealthy freedmen during the Roman Republic and Empire.""" . ### http://w3id.org/cacao/CACAO_0000056 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:58:09Z"^^xsd:dateTime ; rdfs:label "Complexes"@en ; """Scope note: This class comprises groups of interrelated buildings and structures that are designed to function as a single, integrated unit. These can be defined by a common purpose, architectural style, or historical period.""" . ### http://w3id.org/cacao/CACAO_0000057 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:58:22Z"^^xsd:dateTime ; rdfs:label "Cemeteries"@en ; """Scope note: This class comprises designated areas where the remains of deceased people are buried or otherwise interred. They are characterized by the presence of graves, tombs, or other forms of funerary monuments.""" . ### http://w3id.org/cacao/CACAO_0000058 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T13:58:31Z"^^xsd:dateTime ; rdfs:label "Necropolis"@en ; """Scope note: This class comprises large, designed cemeteries or burial sites from ancient civilizations. The term literally means \"city of the dead,\" and these sites often feature elaborate tomb structures.""" . ### http://w3id.org/cacao/CACAO_0000059 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T14:02:06Z"^^xsd:dateTime ; rdfs:label "Ceremonial Buildings"@en ; """Scope note: This class comprises buildings designed primarily for holding rites, ceremonies, or formal public events. Their function may be religious, civic, or commemorative in nature.""" . ### http://w3id.org/cacao/CACAO_0000060 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T14:02:13Z"^^xsd:dateTime ; rdfs:label "Tombs"@en ; """Scope note: This class comprises structures or chambers used for the burial or interment of the dead. Tombs can range from simple graves to elaborate mausoleums and pyramids.""" . ### http://w3id.org/cacao/CACAO_0000061 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T14:10:26Z"^^xsd:dateTime ; rdfs:label "Painting"@en ; """Scope note: This class comprises artworks created by applying paint, pigment, color or other medium to a solid surface (called the \"matrix\" or \"support\") such as a canvas, wall, or panel. The medium is commonly applied to the base with a brush, but other implements, such as knives, sponges, and airbrushes, can be used.""" . ### http://w3id.org/cacao/CACAO_0000062 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:01:48Z"^^xsd:dateTime ; rdfs:label "Clothing"@en ; """Scope note: This class comprises items worn on the body. Typically, clothing is made of fabrics or textiles, but over time it has included garments made from animal skin and other thin sheets of materials and natural products found in the environment, put together.""" . ### http://w3id.org/cacao/CACAO_0000063 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:03:15Z"^^xsd:dateTime ; rdfs:label "Main Garments"@en ; """Scope note: This class comprises the primary items of clothing that form the basis of an outfit, covering the torso and/or lower body.""" . ### http://w3id.org/cacao/CACAO_0000064 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:03:22Z"^^xsd:dateTime ; rdfs:label "Outerwear"@en ; """Scope note: This class comprises garments worn over other clothes, especially for warmth or protection when outdoors.""" . ### http://w3id.org/cacao/CACAO_0000065 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:03:30Z"^^xsd:dateTime ; rdfs:label "Underwear"@en ; """Scope note: This class comprises garments worn next to the skin, underneath other clothing.""" . ### http://w3id.org/cacao/CACAO_0000066 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:03:44Z"^^xsd:dateTime ; rdfs:label "Dresses"@en ; """Scope note: This class comprises one-piece garments for a woman or girl that consist of a bodice and a skirt.""" . ### http://w3id.org/cacao/CACAO_0000067 rdf:type owl:Class ; rdfs:subClassOf , ; ; "2025-06-06T16:04:01Z"^^xsd:dateTime ; rdfs:label "Coats"@en ; """Scope note: This class comprises outer garments with sleeves, worn outdoors over other clothes for warmth or protection.""" . ### http://w3id.org/cacao/CACAO_0000068 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:04:29Z"^^xsd:dateTime ; rdfs:label "Plaids"@en ; """Scope note: This class comprises a piece of cloth, typically with a tartan pattern, worn as part of Scottish Highland dress. It is draped over the shoulder as an accessory or used as a blanket.""" . ### http://w3id.org/cacao/CACAO_0000069 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:04:34Z"^^xsd:dateTime ; rdfs:label "Robes"@en ; """Scope note: This class comprises long, loose outer garments, often worn as a sign of office or for ceremonial occasions, or informally at home.""" . ### http://w3id.org/cacao/CACAO_0000070 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:04:39Z"^^xsd:dateTime ; rdfs:label "Suits"@en ; """Scope note: This class comprises a set of outer clothes made of the same fabric and designed to be worn together, typically consisting of at least a jacket and trousers or a skirt.""" . ### http://w3id.org/cacao/CACAO_0000071 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:04:46Z"^^xsd:dateTime ; rdfs:label "Tunics"@en ; """Scope note: This class comprises a simple garment, typically sleeveless or with short sleeves, that hangs from the shoulders to a length between the hips and the knees. It was a common garment in ancient Greece and Rome and remains a feature of some modern clothing styles.""" . ### http://w3id.org/cacao/CACAO_0000072 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:06:41Z"^^xsd:dateTime ; rdfs:label "Cloaks"@en ; """Scope note: This class comprises sleeveless outdoor overgarments which drape from the shoulders. They are worn for warmth, protection, or as part of ceremonial or formal dress.""" . ### http://w3id.org/cacao/CACAO_0000074 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:08:29Z"^^xsd:dateTime ; rdfs:label "Chemises"@en ; """Scope note: This class comprises a simple, loose-fitting garment worn next to the skin, serving as a shirt or undergarment for both men and women in various historical periods. It protected outer garments from sweat and body oils.""" . ### http://w3id.org/cacao/CACAO_0000075 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:08:38Z"^^xsd:dateTime ; rdfs:label "Underpants"@en ; """Scope note: This class comprises undergarments worn on the lower part of the body.""" . ### http://w3id.org/cacao/CACAO_0000076 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:08:46Z"^^xsd:dateTime ; rdfs:label "Underdresses"@en ; """Scope note: This class comprises a simple dress-like garment worn underneath a more elaborate outer dress, either for warmth, to provide structure, or to protect the outer layer.""" . ### http://w3id.org/cacao/CACAO_0000077 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:09:03Z"^^xsd:dateTime ; rdfs:label "Lingerie"@en ; """Scope note: This class comprises women's underwear and nightclothes, often characterized by being lightweight, decorative, and made from fine materials.""" . ### http://w3id.org/cacao/CACAO_0000078 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:09:13Z"^^xsd:dateTime ; rdfs:label "Underskirts"@en ; """Scope note: This class comprises skirts worn underneath an outer skirt for warmth, modesty, or to give the outer skirt a desired shape and volume.""" . ### http://w3id.org/cacao/CACAO_0000079 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:16:03Z"^^xsd:dateTime ; rdfs:label "Documents"@en ; """Scope note: This class comprises physical artefacts consisting of a piece of written, printed, or electronic matter that provides information or evidence or that serves as an official record.""" . ### http://w3id.org/cacao/CACAO_0000080 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:16:12Z"^^xsd:dateTime ; rdfs:label "Letters"@en ; """Scope note: This class comprises written messages from one person or group to another, conveyed by a postal service or by hand. They are a form of personal or official communication recorded on a physical medium.""" . ### http://w3id.org/cacao/CACAO_0000081 rdf:type owl:Class ; rdfs:subClassOf , ; ; "2025-06-06T16:18:13Z"^^xsd:dateTime ; rdfs:label "Medals"@en ; """Scope note: This class comprises small, portable artistic objects, typically made of metal and circular in shape, issued to commemorate a person or event, or as an award for distinction.""" . ### http://w3id.org/cacao/CACAO_0000082 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:23:00Z"^^xsd:dateTime ; rdfs:label "Awards"@en ; """Scope note: This class comprises tangible items given to a person or group in recognition of excellence in a certain field. They serve as a physical token of an honor or prize.""" . ### http://w3id.org/cacao/CACAO_0000083 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T16:23:05Z"^^xsd:dateTime ; rdfs:label "Cup"@en ; """Scope note: This class comprises trophy cups, which are awards in the form of a drinking vessel, often made of precious metal and mounted on a base, given as a prize in a competition.""" . ### http://w3id.org/cacao/CACAO_0000086 rdf:type owl:Class ; rdfs:subClassOf , ; ; "2025-06-06T17:06:03Z"^^xsd:dateTime ; rdfs:label "Image"@en ; """Scope note: This class comprises digital artefacts that represent visual information, such as a photograph, drawing, or graphic. They are stored as a raster or vector file format.""" . ### http://w3id.org/cacao/CACAO_0000087 rdf:type owl:Class ; rdfs:subClassOf , ; ; "2025-06-06T17:06:09Z"^^xsd:dateTime ; rdfs:label "3D Object"@en ; """Scope note: This class comprises digital artefacts that represent a three-dimensional object using a collection of points in 3D space, connected by various geometric entities such as triangles, lines, and curved surfaces.""" . ### http://w3id.org/cacao/CACAO_0000088 rdf:type owl:Class ; rdfs:subClassOf , ; ; "2025-06-06T17:06:14Z"^^xsd:dateTime ; rdfs:label "Video"@en ; """Scope note: This class comprises digital artefacts consisting of a recording of moving visual images. It can include synchronized audio.""" . ### http://w3id.org/cacao/CACAO_0000089 rdf:type owl:Class ; rdfs:subClassOf ; ; "2025-06-06T17:06:18Z"^^xsd:dateTime ; rdfs:label "Audio"@en ; """Scope note: This class comprises digital artefacts consisting of sound recordings. This includes music, spoken word, and other forms of auditory information stored in a digital format.""" . ### http://www.cidoc-crm.org/cidoc-crm/E10_Transfer_of_Custody rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises transfers of the physical custody or the legal responsibility for the physical custody of objects. The recording of the donor or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances, it may describe: 1. the beginning of custody (there is no previous custodian) 2. the end of custody (there is no subsequent custodian) 3. the transfer of custody (transfer from one custodian to the next) 4. the receipt of custody from an unknown source (the previous custodian is unknown) 5. the declared loss of an object (the current or subsequent custodian is unknown) In the event that only a single kind of transfer of custody occurs, either the legal responsibility for the custody or the actual physical possession of the object but not both, this difference should be expressed using the property P2 has type (is type of). The sense of physical possession requires that the object of custody be in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing. The interpretation of the museum notion of \"accession\" differs between institutions. The CIDOC CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these. Theft is a specific case of illegal transfer of custody. Examples: - the delivery of the paintings by Secure Deliveries Inc. to the National Gallery - the return of Picasso’s “Guernica” to Madrid’s Prado in 1981 (Chipp, 1988) - the transfer of custody of the work described as “Von der Velden ein Ufer an der See” from Johann Matthäus von Merian to the Auction House Heldevier (Jacob) for the purpose of sale, ca. 1716 - the transfer of custody of the painting ‘Mrs. Fitzherbert’ to the art dealer Knoedler from Parke-Bernet Galleries (New York, NY, USA) ca. March 1941 In First Order Logic: - E10(x) ⇒ E7(x) """@en ; rdfs:label "E10 Transfer of Custody"@en , "E10 Transfert de la garde"@fr , "E10 Transferência de Custódia"@pt , "E10 Übertragung des Gewahrsams"@de , "E10 Μεταβίβαση Κατοχής"@el , "E10 Пeрeдача Хранeния"@ru , "E10 转移监护权"@zh ; "E10"@en ; "Transfer of Custody"@en , "Transfert de la garde"@fr , "Transferência de Custódia"@pt , "Übertragung des Gewahrsams"@de , "Μεταβίβαση Κατοχής"@el , "Пeрeдача Хранeния"@ru , "转移监护权"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E11_Modification rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises instances of E7 Activity that are undertaken to create, alter or change instances of E24 Physical Human-Made Thing. This class includes the production of an item from raw materials and other so far undocumented objects. It also includes the conservation treatment of an object. Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in an instance of E11 Modification, and that others may be produced as a result of it. An event should also be documented using an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities. An activity undertaken on an object which was designed to alter it, but which, in fact, it did not in any seemingly significant way (such as the application of a solvent during conservation which failed to dissolve any part of the object), is still considered as an instance of E11 Modification. Typically, any such activity will leave at least forensic traces of evidence on the object. If the instance of E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material. Examples: - the construction of the SS Great Britain (E12) (Gregor, 1971) - the impregnation of the Vasa warship in Stockholm for preservation after 1956 (Håfors, 2010) - the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81) (Yakel, 2000) - the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan (Cali and Dougil, 2012) In First Order Logic: - E11(x) ⇒ E7(x) """@en ; rdfs:label "E11 Bearbeitung"@de , "E11 Modification"@en , "E11 Modification"@fr , "E11 Modificação"@pt , "E11 Τροποποίηση"@el , "E11 Измeнeниe"@ru , "E11 修改"@zh ; "E11"@en ; "Bearbeitung"@de , "Modification"@en , "Modification"@fr , "Modificação"@pt , "Τροποποίηση"@el , "Измeнeниe"@ru , "修改"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E12_Production rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """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) """@en ; rdfs:label "E12 Herstellung"@de , "E12 Production"@en , "E12 Production"@fr , "E12 Produção"@pt , "E12 Παραγωγή"@el , "E12 Изготовлeниe"@ru , "E12 生产"@zh ; "E12"@en ; "Herstellung"@de , "Production"@en , "Production"@fr , "Produção"@pt , "Παραγωγή"@el , "Изготовлeниe"@ru , "生产"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E13_Attribute_Assignment rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the actions of making assertions about one property of an object or any single relation between two items or concepts. The type of the property asserted to hold between two items or concepts can be described by the property P177 assigned property of type (is type of property assigned): E55 Type. For example, the class describes the actions of people making propositions and statements during certain scientific/scholarly procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on whether this information should be accessible by structured queries. This class allows for the documentation of how the respective assignment came about, and whose opinion it was. Note that all instances of properties described in a knowledge base are the opinion of someone. Per default, they are the opinion of the team maintaining the knowledge base. This fact must not individually be registered for all instances of properties provided by the maintaining team, because it would result in an endless recursion of whose opinion was the description of an opinion. Therefore, the use of instances of E13 Attribute Assignment marks the fact that the maintaining team is in general neutral to the validity of the respective assertion, but registers someone else’s opinion and how it came about. All properties assigned in such an action can also be seen as directly relating the respective pair of items or concepts. Multiple use of instances of E13 Attribute Assignment may possibly lead to a collection of contradictory values. Examples: - the examination of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad, 2010) - the assessment of the current ownership of Martin Doerr’s silver cup in February 1997 (fictitious) In First Order Logic: - E13(x) ⇒ E7(x) """@en ; rdfs:label "E13 Assignation d’attribut"@fr , "E13 Atribuição de Característica"@pt , "E13 Attribute Assignment"@en , "E13 Merkmalszuweisung"@de , "E13 Απόδοση Ιδιοτήτων"@el , "E13 Назначeниe Атрибута"@ru , "E13 属性赋值"@zh ; "E13"@en ; "Assignation d’attribut"@fr , "Atribuição de Característica"@pt , "Attribute Assignment"@en , "Merkmalszuweisung"@de , "Απόδοση Ιδιοτήτων"@el , "Назначeниe Атрибута"@ru , "属性赋值"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E14_Condition_Assessment rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class describes the act of assessing the state of preservation of an object during a particular period. The condition assessment may be carried out by inspection, measurement, or through historical research. This class is used to document circumstances of the respective assessment that is relevant to interpret its quality at a later stage, or to continue research on related documents. Examples: - last year’s inspection of humidity damage to the frescos in the St. George chapel in our village (fictitious) - the condition assessment of the endband cores of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad, 2010) - the condition assessment of the cover of MS Sinai Greek 418 by Nicholas Pickwoad in November 2003 (Honey & Pickwoad, 2010) In First Order Logic: - E14(x) ⇒ E13(x) """@en ; rdfs:label "E14 Avaliação do Estado Material"@pt , "E14 Condition Assessment"@en , "E14 Zustandsfeststellung"@de , "E14 Évaluation d’état matériel"@fr , "E14 Εκτίμηση Κατάστασης"@el , "E14 Оцeнка Состояния"@ru , "E14 状态评估"@zh ; "E14"@en ; "Avaliação do Estado Material"@pt , "Condition Assessment"@en , "Zustandsfeststellung"@de , "Évaluation d’état matériel"@fr , "Εκτίμηση Κατάστασης"@el , "Оцeнка Состояния"@ru , "状态评估"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E15_Identifier_Assignment rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An instance of E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure. Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when, and for what purpose an identifier is assigned to an item. The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment through the P2 has type (is type of) property. Examples: - replacement of the inventory number TA959a by GE34604 for a 17(th) century lamentation cloth at the Museum Benaki, Athens - assigning the author and uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” to a work - on 1(st) June 2001, assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” to Guillaume de Machaut (Kelly, 2014) In First Order Logic: - E15(x) ⇒ E13(x) """@en ; rdfs:label "E15 Assignation d’identifiant"@fr , "E15 Atribuição de Identificador"@pt , "E15 Identifier Assignment"@en , "E15 Kennzeichenzuweisung"@de , "E15 Απόδοση Αναγνωριστικού"@el , "E15 Назначeниe Идeнтификатора"@ru , "E15 标识符赋值"@zh ; "E15"@en ; "Assignation d’identifiant"@fr , "Atribuição de Identificador"@pt , "Identifier Assignment"@en , "Kennzeichenzuweisung"@de , "Απόδοση Αναγνωριστικού"@el , "Назначeниe Идeнтификатора"@ru , "标识符赋值"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E16_Measurement rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises actions measuring physical properties and other values that can be determined by a systematic, objective procedure of direct observation of particular states of physical reality. An instance of E16 Measurement may use simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Methods and devices employed should be associated with instances of E16 Measurement by properties such as P33 used specific technique: E29 Design or Procedure, P125 used object of type: E55 Type, P16 used specific object (was used for): E70 Thing, whereas basic techniques such as \"carbon-14 dating\" should be encoded using P2 has type (is type of): E55 Type. Details of methods and devices reused or reusable in other instances of E16 Measurement should be documented for these entities rather than the measurements themselves, whereas details of particular execution may be documented by free text or by instantiating adequate sub-activities, if the detail may be of interest for an overarching query. Regardless whether a measurement is made by an instrument or by human senses, it represents the initial transition from physical reality to information without any other documented information object in between within the reasoning chain that would represent the result of the interaction of the observer or device with reality. Therefore, determining properties of an instance of E90 Symbolic Object is regarded as an instance of E13 Attribute Assignment, which may be inferred from observing and measuring representative carriers. In the case that the carrier can be named, the property P16 used specific object (was used for) should be used to indicate the instance(s) of E18 Physical Thing that was used as the empirical basis for the attribute assignment. For instance, inferring properties of depicted items using image material, such as satellite images, is not regarded as an instance of E16 Measurement, but as a subsequent instance of E13 Attribute Assignment. Rather, only the production of the images, understood as arrays of radiation intensities, is regarded as an instance of E16 Measurement. The same reasoning holds for other sensor data. Examples: - measurement of the height of silver cup 232 on 31(st) August 1997 (fictitious) - the carbon 14 dating of the “Schoeninger Speer II” in 1996 [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995.] (Kouwenhoven, 1997) In First Order Logic: - E16(x) ⇒ E13(x) """@en ; rdfs:label "E16 Measurement"@en , "E16 Medição"@pt , "E16 Messung"@de , "E16 Mesurage"@fr , "E16 Μέτρηση"@el , "E16 Измeрeниe"@ru , "E16 测量"@zh ; "E16"@en ; "Measurement"@en , "Medição"@pt , "Messung"@de , "Mesurage"@fr , "Μέτρηση"@el , "Измeрeниe"@ru , "测量"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E17_Type_Assignment rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions, and concepts. This class allows for the documentation of the context of classification acts in cases where the value of the classification depends on the personal opinion of the classifier, and the date that the classification was made. This class also encompasses the notion of “determination,” i.e. the systematic and molecular identification of a specimen in biology. Examples: - the first classification of object GE34604 as Lamentation cloth at the Museum Benaki, Athens - the determination of a cactus in Martin Doerr’s garden as Cereus hildmannianus K.Schum., July 2003 In First Order Logic: - E17(x) ⇒ E13(x) """@en ; rdfs:label "E17 Assignation de type"@fr , "E17 Atribuição de Tipo"@pt , "E17 Type Assignment"@en , "E17 Typuszuweisung"@de , "E17 Απόδοση Τύπου"@el , "E17 Назначeниe Типа"@ru , "E17 类型赋值"@zh ; "E17"@en ; "Assignation de type"@fr , "Atribuição de Tipo"@pt , "Type Assignment"@en , "Typuszuweisung"@de , "Απόδοση Τύπου"@el , "Назначeниe Типа"@ru , "类型赋值"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises all persistent physical items with a relatively stable form, human-made or natural. Depending on the existence of natural boundaries of such things, the CIDOC CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land, etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter. An instance of E18 Physical Thing occupies not only a particular geometric space at any instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces, such as the interior of a box. For the purpose of more detailed descriptions of the presence of an instance of E18 Physical Thing in space and time it can be associated with its specific instance of E92 Spacetime Volume by the property P196 defines (is defined by). The CIDOC CRM is generally not concerned with amounts of matter in fluid or gaseous states, as long as they are not confined in an identifiable way for an identifiable minimal time-span. Examples: - the Cullinan Diamond (E19) (Scarratt and Shor, 2006) - the cave “Ideon Andron” in Crete (E26) (Smith, 1844-49) - the Mona Lisa (E22) (Mohen, 2006) In First Order Logic: - E18(x) ⇒ E72(x) """@en ; rdfs:label "E18 Chose matérielle"@fr , "E18 Coisa Material"@pt , "E18 Materielles"@de , "E18 Physical Thing"@en , "E18 Υλικό Πράγμα"@el , "E18 Матeриальный Прeдмeт"@ru , "E18 实物"@zh ; "E18"@en ; "Chose matérielle"@fr , "Coisa Material"@pt , "Materielles"@de , "Physical Thing"@en , "Υλικό Πράγμα"@el , "Матeриальный Прeдмeт"@ru , "实物"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E19_Physical_Object rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises items of a material nature that are units for documentation and have physical boundaries that separate them completely in an objective way from other objects. The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen. Typically, instances of E19 Physical Object can be moved (if not too heavy). In some contexts, such objects, except for aggregates, are also called “bona fide objects”, i.e. naturally defined objects (Smith & Varzi, 2000). The decision as to what is documented as a complete item, rather than by its parts or components, may be purely administrative or may be a result of the order in which the item was acquired. Examples: - Aphrodite of Milos (E22) (Kousser, 2005) - the Cullinan Diamond (Scarratt and Shor, 2006) - Apollo 13 at the time of launch (E22) (Lovell and Kluger, 1994) In First Order Logic: - E19(x) ⇒ E18(x) """@en ; rdfs:label "E19 Materieller Gegenstand"@de , "E19 Objet matériel"@fr , "E19 Objeto Material"@pt , "E19 Physical Object"@en , "E19 Υλικό Αντικείμενο"@el , "E19 Матeриальный Объeкт"@ru , "E19 物质对象"@zh ; "E19"@en ; "Materieller Gegenstand"@de , "Objet matériel"@fr , "Objeto Material"@pt , "Physical Object"@en , "Υλικό Αντικείμενο"@el , "Матeриальный Объeкт"@ru , "物质对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity rdf:type owl:Class ; rdfs:comment """Scope note: This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties: - Identification by name or appellation, and in particular by a preferred identifier - Classification by type, allowing further refinement of the specific subclass to which an instance belongs - Attachment of free text and other unstructured data for the expression of anything not captured by formal properties All other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity. Examples: - the earthquake in Lisbon 1755 (E5) (Chester, 2001) In First Order Logic: - E1(x) """@en ; rdfs:label "E1 CRM Entity"@en , "E1 CRM Entität"@de , "E1 CRM Сущность"@ru , "E1 CRM实体"@zh , "E1 Entidade CRM"@pt , "E1 Entité CRM"@fr , "E1 Οντότητα CIDOC CRM"@el ; "E1"@en ; "CRM Entity"@en , "CRM Entität"@de , "CRM Сущность"@ru , "CRM实体"@zh , "Entidade CRM"@pt , "Entité CRM"@fr , "Οντότητα CIDOC CRM"@el . ### http://www.cidoc-crm.org/cidoc-crm/E20_Biological_Object rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises individual items of a material nature, which live, have lived, or are natural products of or from living organisms. Artificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Human-Made Object. Examples: - me (fictitious) - Tut-Ankh-Amun (Edwards and Boltin, 1979) - Boukephalus [Horse of Alexander the Great] (Lamb, 2005) - petrified dinosaur excrement PA1906-344 In First Order Logic: - E20(x) ⇒ E19(x) """@en ; rdfs:label "E20 Biological Object"@en , "E20 Biologischer Gegenstand"@de , "E20 Objet biologique"@fr , "E20 Objeto Biológico"@pt , "E20 Βιολογικό Ακτικείμενο"@el , "E20 Биологичeский Объeкт"@ru , "E20 生物对象"@zh ; "E20"@en ; "Biological Object"@en , "Biologischer Gegenstand"@de , "Objet biologique"@fr , "Objeto Biológico"@pt , "Βιολογικό Ακτικείμενο"@el , "Биологичeский Объeкт"@ru , "生物对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E21_Person rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf , , ; rdfs:comment """Scope note: This class comprises real persons who live or are assumed to have lived. Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CIDOC CRM does not propose a specific form to support reasoning about possible identity. In a bibliographic context, a name presented following the conventions usually employed for personal names will be assumed to correspond to an actual real person (an instance of E21 Person), unless evidence is available to indicate that this is not the case. The fact that a persona may erroneously be classified as an instance of E21 Person does not imply that the concept comprises personae. Examples: - Tut-Ankh-Amun (Edwards and Boltin, 1979) - Nelson Mandela (Brown and Hort, 2006) In First Order Logic: - E21(x) ⇒ E20(x) - E21(x) ⇒ E39(x) """@en ; rdfs:label "E21 Person"@de , "E21 Person"@en , "E21 Personne"@fr , "E21 Pessoa"@pt , "E21 Πρόσωπο"@el , "E21 Личность"@ru , "E21 人物"@zh ; "E21"@en ; "Person"@de , "Person"@en , "Personne"@fr , "Pessoa"@pt , "Πρόσωπο"@el , "Личность"@ru , "人物"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E22_Human-Made_Object rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises all persistent physical objects of any size that are purposely created by human activity and have physical boundaries that separate them completely in an objective way from other objects. The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen. Examples: - the Rosetta Stone (E22) - LNER Class A4 4468 Mallard [the World’s fastest steam locomotive, preserved at the National Railway Museum of York, UK] (Solomon, 2003) - the Portland Vase (Walker, 2004) In First Order Logic: - E22(x) ⇒ E19(x) - E22(x) ⇒ E24(x) """@en ; rdfs:label "E22 Human-Made Object"@en , "E22 Objet élaboré par l’humain"@fr , "E22 Рукотворный Объeкт"@ru ; "E22"@en ; "Human-Made Object"@en , "Objet élaboré par l’humain"@fr , "Рукотворный Объeкт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E24_Physical_Human-Made_Thing rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises all persistent physical items of any size that are purposely created by human activity. This class comprises, besides others, human-made objects, such as a sword, and human-made features, such as rock art. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Human-Made Thing. Instances of E24 Physical Human-Made Thing may be the result of modifying pre-existing physical things, preserving larger parts or most of the original matter and structure, which poses the question if they are new or even human-made, the respective interventions of production made on such original material should be obvious and sufficient to regard that the product has a new, distinct identity and intended function and is human-made. Substantial continuity of the previous matter and structure in the new product can be documented by describing the production process also as an instance of E81 Transformation. Whereas interventions of conservation and repair are not regarded to produce a new instance of E24 Physical Human-Made Thing, the results of preparation of natural history specimens that substantially change their natural or original state should be regarded as instances of E24 Physical Human-Made Things, including the uncovering of petrified biological features from a solid piece of stone. On the other side, scribbling a museum number on a natural object should not be regarded to make it human-made. This notwithstanding, parts, sections, segments, or features of an instance of E24 Physical Human-Made Thing may continue to be non-human-made and preserved during the production process, for example natural pearls used as a part of an eardrop. Examples: - the Forth Railway Bridge (Shipway, Bouch, Baker and Fowler, 1990). - the Channel Tunnel (E25) (Holliday, Marcou and Vickerman, 1991) - the Palace of Knossos (Evans, 1921) - the Colosseum in Rome, Italy (Hopkins and Beard, 2011) - the Historical Collection of the Museum Benaki in Athens (E78) (Georgoula, 2005) - the Rosetta Stone (E22) - my paperback copy of Crime & 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) """@en ; rdfs:label "E24 Chose matérielle élaborée par l’humain"@fr , "E24 Physical Human-Made Thing"@en , "E24 Матeриальный Рукотворный Объeкт"@ru ; "E24"@en ; "Chose matérielle élaborée par l’humain"@fr , "Physical Human-Made Thing"@en , "Матeриальный Рукотворный Объeкт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E25_Human-Made_Feature rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc. In particular, it includes the information encoding features on mechanical or digital carriers. Examples: - the Manchester Ship Canal (Farnie, 1980) - Michael Jackson’s nose following plastic surgery - the laser-readable “pits” engraved June 2014 on Martin Doerr’s CD-R, copying songs of Edith Piaf - the carved letters on the Rosetta Stone In First Order Logic: - E25(x) ⇒ E24(x) - E25(x) ⇒ E26(x) """@en ; rdfs:label "E25 Caractéristique élaborée par l'humain"@fr , "E25 Human-Made Feature"@en , "E25 Искусствeнный Признак"@ru ; "E25"@en ; "Caractéristique élaborée par l'humain"@fr , "Human-Made Feature"@en , "Искусствeнный Признак"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E26_Physical_Feature rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises identifiable features that are physically attached in an integral way to particular physical objects. Instances of E26 Physical Feature share many of the attributes of instances of E19 Physical Object. They may have a one-dimensional, two-dimensional, or three-dimensional geometric extent, but there are no natural borders that separate them completely in an objective way from the carrier objects. For example, a doorway is a feature but the door itself, being attached by hinges, is not. Instances of E26 Physical Feature can be features in a narrower sense, such as scratches, holes, reliefs, surface colours, reflection zones in an opal crystal or a density change in a piece of wood. In the wider sense, they are portions of particular objects with partially imaginary borders, such as the core of the Earth, an area of property on the surface of the Earth, a landscape or the head of a contiguous marble statue. They can be measured and dated, and it is sometimes possible to state who or what is or was responsible for them. They cannot be separated from the carrier object, but a segment of the carrier object may be identified (or sometimes removed) carrying the complete feature. This definition coincides with the definition of “fiat objects”, with the exception of aggregates of “bona fide objects” (Smith & Varzi, 2000). Examples: - the cave of Dirou, Mani, Greece (Psimenos. 2005) - the temple in Abu Simbel before its removal, which was carved out of solid rock (E25) (Hawass, 2000) - Albrecht Duerer's signature on his painting of Charles the Great (E25) (Strauss, 1974) - the damage to the nose of the Great Sphinx in Giza (Temple, 2009) - Michael Jackson’s nose prior to plastic surgery In First Order Logic: - E26(x) ⇒ E18(x) """@en ; rdfs:label "E26 Característica Material"@pt , "E26 Caractéristique physique"@fr , "E26 Materielles Merkmal"@de , "E26 Physical Feature"@en , "E26 Υλικό Μόρφωμα"@el , "E26 Физичeский Признак"@ru , "E26 物理特征"@zh ; "E26"@en ; "Característica Material"@pt , "Caractéristique physique"@fr , "Materielles Merkmal"@de , "Physical Feature"@en , "Υλικό Μόρφωμα"@el , "Физичeский Признак"@ru , "物理特征"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E27_Site rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises pieces of land or sea floor. In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings, and maps. Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location. Examples: - the Amazon river basin (Hegen, 1966) - Knossos (Evans, 1921) - the Apollo 11 landing site (Siegler and Smrekar, 2014) - Heathrow Airport (Wicks, 2014) - the submerged harbour of the Minoan settlement of Gournia, Crete (Watrous, 2012) - the island of Crete In First Order Logic: - E27(x) ⇒ E26(x) """@en ; rdfs:label "E27 Gelände"@de , "E27 Lugar"@pt , "E27 Site"@en , "E27 Site"@fr , "E27 Φυσικός Χώρος"@el , "E27 Мeстоположeниe"@ru , "E27 场地"@zh ; "E27"@en ; "Gelände"@de , "Lugar"@pt , "Site"@en , "Site"@fr , "Φυσικός Χώρος"@el , "Мeстоположeниe"@ru , "场地"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E28_Conceptual_Object rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation, or historical implication. The production of such information might have been supported by the use of technical devices such as cameras or computers. Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc. They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost. Examples: - Beethoven’s “Ode an die Freude” (Ode to Joy) (E73) (Kershaw, 1999) - the definition of “ontology” in the Oxford English Dictionary (E73) (Oxford University Press, 1989) - the knowledge about the victory at Marathon carried by the famous runner (E89) (Lagos & Karyanos, 2020) - [Explanation note: The following examples illustrate the distinction between a propositional object, its names and its encoded forms. The Maxwell equations (Ball, 1962) are a good example, because they belong to the fundamental laws of physics and their mathematical content yields identical, unambiguous results regardless formulation and encoding.] - “Maxwell equations” (E41) [preferred subject access point from LCSH, http://lccn.loc.gov/sh85082387, accessed 18(th) April 2021. This is only the name for the Maxwell equations as standardized by the Library of Congress and not the equations themselves.] - “Equations, Maxwell” (E41) [variant subject access point from LCSH, http://lccn.loc.gov/sh85082387, accessed 18(th) April 2021. This is another name for the equation standardized by the Library of Congress and not the equations themselves.] - Maxwell's equations (E89) [This is the propositional content of the equations proper, independent of any particular notation or mathematical formalism.] (Ball, 1962) - The encoding of Maxwells equations as in https://upload.wikimedia.org/wikipedia/commons/c/c4/Maxwell%27sEquations.svg (E73) [accessed 18(th) April 2021. This is one possible symbolic encoding of the propositional content of the equations.] In First Order Logic: - E28(x) ⇒ E71(x) """@en ; rdfs:label "E28 Begrifflicher Gegenstand"@de , "E28 Conceptual Object"@en , "E28 Objet conceptuel"@fr , "E28 Objeto Conceitual"@pt , "E28 Νοητικό Αντικείμενο"@el , "E28 Концeптуальный Объeкт"@ru , "E28 概念对象"@zh ; "E28"@en ; "Begrifflicher Gegenstand"@de , "Conceptual Object"@en , "Objet conceptuel"@fr , "Objeto Conceitual"@pt , "Νοητικό Αντικείμενο"@el , "Концeптуальный Объeкт"@ru , "概念对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form, or contents. In particular, it comprises plans for deliberate human activities that may result in new instances of E71 Human-Made Thing or for shaping or guiding the execution of an instance of E7 Activity. Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 has association with (is associated with): E29 Design or Procedure. Designs or procedures can be seen as one of the following: 1. A schema for the activities it describes 2. A schema of the products that result from their application 3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci’s famous plans for flying machines Because designs or procedures may never be applied or only partially executed, the CIDOC CRM models a loose relationship between the plan and the respective product. Examples: - the ISO standardisation procedure - the musical notation for Beethoven’s “Ode to Joy” (Kershaw, 1999) - the architectural drawings for the Kölner Dom (Cologne Cathedral) in Cologne, Germany (Wolff, 1999) - the drawing found on Folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486 to 1490, kept in the Biblioteca Ambrosiana in Milan In First Order Logic: - E29(x) ⇒ E73(x) """@en ; rdfs:label "E29 Conceptualisation ou procédure"@fr , "E29 Design or Procedure"@en , "E29 Entwurf oder Verfahren"@de , "E29 Projeto ou Procedimento"@pt , "E29 Σχέδιο"@el , "E29 Проeкт или Процeдура"@ru , "E29 设计或程序"@zh ; "E29"@en ; "Conceptualisation ou procédure"@fr , "Design or Procedure"@en , "Entwurf oder Verfahren"@de , "Projeto ou Procedimento"@pt , "Σχέδιο"@el , "Проeкт или Процeдура"@ru , "设计或程序"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises all phenomena, such as the instances of E4 Periods and E5 Events, which happen over a limited extent in time. This extent in time must be contiguous, i.e., without gaps. In case the defining kinds of phenomena for an instance of E2 Temporal Entity cease to happen, and occur later again at another time, we regard that the former instance of E2 Temporal Entity has ended and a new instance has come into existence. In more intuitive terms, the same event cannot happen twice. In some contexts, such phenomena are also called perdurants. This class is disjoint from E77 Persistent Item and is an abstract class that typically has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing. Examples: - Bronze Age (E4) (Childe, 1963) - the earthquake in Lisbon 1755 (E5) (Chester, 2001) - the Peterhof Palace near Saint Petersburg being in ruins from 1944 to 1946 (E3) (Maddox, 2015) In First Order Logic: - E2(x) ⇒ E1(x) """@en ; rdfs:label "E2 Entidade Temporal"@pt , "E2 Entité temporelle"@fr , "E2 Geschehendes"@de , "E2 Temporal Entity"@en , "E2 Έγχρονη Οντότητα"@el , "E2 Врeмeнная Сущность"@ru , "E2 时序实体"@zh ; "E2"@en ; "Entidade Temporal"@pt , "Entité temporelle"@fr , "Geschehendes"@de , "Temporal Entity"@en , "Έγχρονη Οντότητα"@el , "Врeмeнная Сущность"@ru , "时序实体"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E30_Right rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises legal privileges concerning material and immaterial things or their derivatives. These include reproduction and property rights. Examples: - copyright held by ISO on ISO/CD 21127 - ownership of the “Mona Lisa” by the museum of the Louvre, Paris, France In First Order Logic: - E30(x) ⇒ E89(x) """@en ; rdfs:label "E30 Direitos"@pt , "E30 Droit"@fr , "E30 Recht"@de , "E30 Right"@en , "E30 Δικαίωμα"@el , "E30 Право"@ru , "E30 权限"@zh ; "E30"@en ; "Direitos"@pt , "Droit"@fr , "Recht"@de , "Right"@en , "Δικαίωμα"@el , "Право"@ru , "权限"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E31_Document rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises identifiable immaterial items that make propositions about reality. These propositions may be expressed in text, graphics, images, audiograms, videograms, or by other similar means. Documentation databases are regarded as instances of E31 Document. This class should not be confused with the concept “document” in Information Technology, which is compatible with E73 Information Object. Examples: - the Encyclopaedia Britannica (E32) (Kogan, 1958) - the image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E36) - Domesday Book [a manuscript record of the \"Great Survey\" of much of England and parts of Wales completed in 1086 by order of King William the Conqueror] (Hallam 1986) In First Order Logic: - E31(x) ⇒ E73(x) """@en ; rdfs:label "E31 Document"@en , "E31 Document"@fr , "E31 Documento"@pt , "E31 Dokument"@de , "E31 Τεκμήριο"@el , "E31 Докумeнт"@ru , "E31 文献"@zh ; "E31"@en ; "Document"@en , "Document"@fr , "Documento"@pt , "Dokument"@de , "Τεκμήριο"@el , "Докумeнт"@ru , "文献"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E32_Authority_Document rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use. Examples: - Webster's Dictionary (Herbert, 1994) - Getty Art and Architecture Thesaurus (Getty Trust, 1990) - the CIDOC Conceptual Reference Model (Gergatsoulis et al., 2010) In First Order Logic: - E32(x) ⇒ E31(x) """@en ; rdfs:label "E32 Authority Document"@en , "E32 Document de référence"@fr , "E32 Documento de Referência"@pt , "E32 Referenzdokument"@de , "E32 Πηγή Καθιερωμένων Όρων"@el , "E32 Официальный Докумeнт"@ru , "E32 规范文档"@zh ; "E32"@en ; "Authority Document"@en , "Document de référence"@fr , "Documento de Referência"@pt , "Referenzdokument"@de , "Πηγή Καθιερωμένων Όρων"@el , "Официальный Докумeнт"@ru , "规范文档"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E33_Linguistic_Object rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises identifiable expressions in natural language or languages. Instances of E33 Linguistic Object can be expressed in many ways: e.g. as written texts, recorded speech, or sign language. However, the CIDOC CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CIDOC CRM. These should be modelled as instances of E73 Information Object. In general, an instance of E33 Linguistic Object may also contain non-linguistic information, often of artistic or aesthetic value. Only in cases in which the content of an instance of E33 Linguistic Object can completely be expressed by a series of binary-encoded symbols, its content may be documented within a respective knowledge base by the property P190 has symbolic content: E62 String. Otherwise, it should be understood as an identifiable digital resource only available independently from the respective knowledge base. In other cases, such as pages of an illuminated manuscript or recordings containing speech in a language supported by a writing system, the linguistic part of the content of an instance of E33 Linguistic Object may be documented within a respective knowledge base in a note by P3 has note: E62 String. Otherwise, it may be described using the property P165 incorporates (is incorporated in): E73 Information Object as a different object with its own identity. Examples: - the text of the Ellesmere Chaucer manuscript (Hilmo, 2019) - the lyrics of the song “Blue Suede Shoes” (Cooper, 2008) - the text of the “Jabberwocky” by Lewis Carroll (Carroll, 1981) - the text of “Doktoro Jekyll kaj Sinjoro Hyde” [an Esperanto translation of Dr. Jekyll and Mr. Hyde]. (Stevenson, Morrison and Mann, 1909) - the free dialog in the local dialect recorded in 1958, Telemark, Norway stored on tape or.7-89.s1 (00.15:46-00:34), The Language Collection at the University Library in Bergen, Norway (verified on 2020) In First Order Logic: - E33(x) ⇒ E73(x) """@en ; rdfs:label "E33 Linguistic Object"@en , "E33 Objet linguistique"@fr , "E33 Objeto Lingüístico"@pt , "E33 Sprachlicher Gegenstand"@de , "E33 Γλωσσικό Αντικείμενο"@el , "E33 Лингвистичeский Объeкт"@ru , "E33 语言对象"@zh ; "E33"@en ; "Linguistic Object"@en , "Objet linguistique"@fr , "Objeto Lingüístico"@pt , "Sprachlicher Gegenstand"@de , "Γλωσσικό Αντικείμενο"@el , "Лингвистичeский Объeкт"@ru , "语言对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E34_Inscription rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises recognisable texts that can be attached to instances of E24 Physical Human-Made Thing. The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class is not intended to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CIDOC CRM as instances of E24 Physical Human-Made Thing. The relationship of a physical copy of a book to the text it contains is modelled using E18 Physical Thing. P128 carries (is carried by): E33 Linguistic Object. Examples: - “keep off the grass” [on a sign stuck in the lawn of the quad of Balliol College, Oxford, UK] - the text published in Corpus Inscriptionum Latinarum V 895 (Mommsen, 1872) - “Kilroy was here” In First Order Logic: - E34(x) ⇒ E33(x) - E34(x) ⇒ E37(x) """@en ; rdfs:label "E34 Inschrift"@de , "E34 Inscription"@en , "E34 Inscription"@fr , "E34 Inscrição"@pt , "E34 Επιγραφή"@el , "E34 Надпись"@ru , "E34 题识"@zh ; "E34"@en ; "Inschrift"@de , "Inscription"@en , "Inscription"@fr , "Inscrição"@pt , "Επιγραφή"@el , "Надпись"@ru , "题识"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E35_Title rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises the textual strings that within a cultural context can be clearly identified as titles due to their form. Being a subclass of E41 Appellation, E35 Title can only be used when such a string is actually used as a title of a work, such as a text, an artwork, or a piece of music. Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting”, or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group. This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts. Examples: - “The Merchant of Venice” (McCullough, 2005) - “Mona Lisa” (Mohen, Menu and Mottin, 2006) - “La Pie” (Bortolatto, 1981) - “Lucy in the Sky with Diamonds” (Lennon, 1967) In First Order Logic: - E35(x) ⇒ E33(x) - E35(x) ⇒ E41(x) """@en ; rdfs:label "E35 Titel"@de , "E35 Title"@en , "E35 Titre"@fr , "E35 Título"@pt , "E35 Τίτλος"@el , "E35 Названиe"@ru , "E35 题名"@zh ; "E35"@en ; "Titel"@de , "Title"@en , "Titre"@fr , "Título"@pt , "Τίτλος"@el , "Названиe"@ru , "题名"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E36_Visual_Item rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the intellectual or conceptual aspects of recognisable marks and images. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation, and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support. The E36 Visual Item class provides a means of identifying and linking together instances of E24 Physical Human-Made Thing that carry the same visual symbols, marks, or images, etc. The property P62 depicts (is depicted by) between E24 Physical Human-Made Thing and the depicted subjects (E1 CRM Entity) can be regarded as a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity, which in addition captures the optical features of the depiction. Examples: - the visual appearance of Monet’s “La Pie” (Bortolatto, 1981) - the Coca-Cola logo (E34) - the Chi-Rho (E37) - the communist red star (E37) - the surface shape of Auguste Rodin's statue \"Le Penseur\" [There exist more than 20 copies, even of different size. Therefore, this is a good example that it is only the common surface shape, an immaterial visual item, which justifies displaying these copies as works of Auguste Rodin. As usual practice, Rodin himself did not produce the bronze statue, but only the prototype model.] In First Order Logic: - E36(x) ⇒ E73(x) """@en ; rdfs:label "E36 Bildliches"@de , "E36 Entité visuelle"@fr , "E36 Item Visual"@pt , "E36 Visual Item"@en , "E36 Οπτικό Στοιχείο"@el , "E36 Визуальный Прeдмeт"@ru , "E36 可视项"@zh ; "E36"@en ; "Bildliches"@de , "Entité visuelle"@fr , "Item Visual"@pt , "Visual Item"@en , "Οπτικό Στοιχείο"@el , "Визуальный Прeдмeт"@ru , "可视项"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E37_Mark rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises symbols, signs, signatures, or short texts applied to instances of E24 Physical Human-Made Thing by arbitrary techniques, often in order to indicate such things as creator, owner, dedications, purpose, or to communicate information generally. Instances of E37 Mark do not represent the actual image of a mark, but the abstract ideal (or archetype) as used for codification in reference documents forming cultural documentation. This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Human-Made Feature. Examples: - Minoan double axe mark (Lowe Fri, 2011) - © - ☺ In First Order Logic: - E37(x) ⇒ E36(x) """@en ; rdfs:label "E37 Marca"@pt , "E37 Mark"@en , "E37 Marke"@de , "E37 Marque"@fr , "E37 Σήμανση"@el , "E37 Знак"@ru , "E37 标记"@zh ; "E37"@en ; "Marca"@pt , "Mark"@en , "Marke"@de , "Marque"@fr , "Σήμανση"@el , "Знак"@ru , "标记"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E39_Actor rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises people, either individually or in groups, who have the potential to perform intentional actions of kinds for which they can be held responsible. Examples: - London and Continental Railways (E74) - the Governor of the Bank of England in 1975 (E21) - Sir Ian McKellen (E21) (Gibson, 1986) In First Order Logic: - E39(x) ⇒ E77(x) """@en ; rdfs:label "E39 Actant"@fr , "E39 Actor"@en , "E39 Agente"@pt , "E39 Akteur"@de , "E39 Δράστης"@el , "E39 Дeйствующий Субъeкт"@ru , "E39 参与者"@zh ; "E39"@en ; "Actant"@fr , "Actor"@en , "Agente"@pt , "Akteur"@de , "Δράστης"@el , "Дeйствующий Субъeкт"@ru , "参与者"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E3_Condition_State rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the states of objects characterised by a certain condition over a time-span. An instance of this class describes the prevailing physical condition of any material object or feature during a specific instance of E52 Time-Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held. The nature of that condition can be described using P2 has type. For example, the instance of E3 Condition State “condition of the SS Great Britain between 22(nd) September 1846 and 27(th) August 1847” can be characterized as an instance “wrecked” of E55 Type. Examples: - the \"reconstructed\" state of the “Amber Room” in Tsarskoje Selo from summer 2003 until now (Owen, 2009) - the \"ruined\" state of Peterhof Palace near Saint Petersburg from 1944 to 1946 (Maddox, 2015) - the state of my turkey in the oven at 14:30 on 25(th) December 2002 [P2 has type: E55 Type “still not cooked”] (fictitious) - the topography of the leaves of Sinai Printed Book 3234.2361 on the 10(th) July 2007 [described as: of type \"cockled\"] (fictitious) In First Order Logic: - E3(x) ⇒ E2(x) """@en ; rdfs:label "E3 Condition State"@en , "E3 Estado Material"@pt , "E3 Zustandsphase"@de , "E3 État matériel"@fr , "E3 Κατάσταση"@el , "E3 Состояниe"@ru , "E3 条件状态"@zh ; "E3"@en ; "Condition State"@en , "Estado Material"@pt , "Zustandsphase"@de , "État matériel"@fr , "Κατάσταση"@el , "Состояниe"@ru , "条件状态"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E41_Appellation rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises all signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class within a certain context. Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e. other instances of E41 Appellation that are regarded as equivalent, regardless of the thing it denotes. Different languages may use different appellations for the same thing, such as the names of major cities. Some appellations may be formulated using a valid noun phrase of a particular language. In these cases, the respective instances of E41 Appellation should also be declared as instances of E33 Linguistic Object. Then the language using the appellation can be declared with the property P72 has language: E56 Language. Instances of E41 Appellation may be used to identify any instance of E1 CRM Entity and sometimes are characteristic for instances of more specific subclasses of E1 CRM Entity, such as for instances of E52 Time-Span (for instance “dates”), E39 Actor, E53 Place or E28 Conceptual Object. Postal addresses and E-mail addresses are characteristic examples of identifiers used by services transporting things between clients. Even numerically expressed identifiers for extents in space or time are also regarded as instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though they allow for determining some time or location by a known procedure starting from a reference point and by virtue of that fact play a double role as instances of E59 Primitive Value. E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment. Examples: - “Martin” - “Aquae Sulis Minerva” - “the Merchant of Venice” (E35) (McCullough, 2005) - “Spigelia marilandica (L.) L.” [not the species, just the name] (Hershberger, Robacker and Jenkins, 2015) - “information science” [not the science itself, but the name used to refer to the subject matter in an English-speaking context] - “安” [Chinese “an”, meaning “peace”] - “6°5’29”N 45°12’13”W” [example of a spatial coordinate] - “Black queen’s bishop 4” [chess coordinate, example of an identifier in a conceptual space (E89)] - “19-MAR-1922” [example of date] - “+41 22 418 5571” [example of contact point] - “weasel@paveprime.com” [example of contact point] - “CH-1211, Genève” [example of place appellation] - “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan” [example of a postal address] - “the poop deck of H.M.S Victory” [example of a section definition on a human-made object (E22)] - “the Venus de Milo’s left buttock” [example of a section definition on a human-made object (E22)] In First Order Logic: - E41(x) ⇒ E90(x) """@en ; rdfs:label "E41 Appellation"@en , "E41 Appellation"@fr , "E41 Benennung"@de , "E41 Designação"@pt , "E41 Ονομασία"@el , "E41 Обозначeниe"@ru , "E41 称谓"@zh ; "E41"@en ; "Appellation"@en , "Appellation"@fr , "Benennung"@de , "Designação"@pt , "Ονομασία"@el , "Обозначeниe"@ru , "称谓"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E42_Identifier rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. Postal addresses, telephone numbers, URLs and e-mail addresses are characteristic examples of identifiers used by services transporting things between clients. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents. Examples: - “MM.GE.195” - “13.45.1976” - “OXCMS: 1997.4.1” (fictitious) - “ISSN 0041-5278” [Identifier for “The UNESCO Courier (Print)”] - ISRC “FIFIN8900186” [Identifier for : Kraft (29 min 14 s) / Magnus Lindberg, comp. ; Toimii Ensemble ; Swedish Radio symphony orchestra ; Esa-Pekka Salonen, dir.] - Shelf mark “Res 8 P 10” - “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules] (Reaney, 1974) - “+41 22 418 5571” - “ weasel@paveprime.com” - “Rue David Dufour 5, CH-1211, Genève” - “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan” In First Order Logic: - E42(x) ⇒ E41(x) """@en ; rdfs:label "E42 Identifiant"@fr , "E42 Identificador de Objeto"@pt , "E42 Identifier"@en , "E42 Kennung"@de , "E42 Κωδικός Αναγνώρισης"@el , "E42 Идeнтификатор"@ru , "E42 标识符"@zh ; "E42"@en ; "Identifiant"@fr , "Identificador de Objeto"@pt , "Identifier"@en , "Kennung"@de , "Κωδικός Αναγνώρισης"@el , "Идeнтификатор"@ru , "标识符"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E4_Period rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises sets of coherent phenomena or cultural manifestations occurring in time and space. It is the social or physical coherence of these phenomena that identify an instance of E4 Period and not the associated spatiotemporal extent. This extent is only the “ground” or space in an abstract physical sense that the actual process of growth, spread and retreat has covered. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area and time as a sedentary culture. This also means that overlapping land use rights, common among first nations, amounts to overlapping periods. Often, this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the “Ming Dynasty” or the “McCarthy Era”, but also geopolitical units and activities of settlements are regarded as special cases of E4 Period. However, there are no assumptions about the scale of the associated phenomena. In particular all events are seen as synthetic processes consisting of coherent phenomena. Therefore, E4 Period is a superclass of E5 Event. For example, a modern clinical birth, an instance of E67 Birth, can be seen as both a single event, i.e. an instance of E5 Event, and as an extended period, i.e. an instance of E4 Period, that consists of multiple physical processes and complementary activities performed by multiple instances of E39 Actor. E4 Period is a subclass of E2 Temporal Entity and of E92 Spacetime Volume. The latter is intended as a phenomenal spacetime volume as defined in CIDOC CRMgeo (Doerr & Hiebel, 2013). By virtue of this multiple inheritance, it is possible to discuss the physical extent of an instance of E4 Period without representing each instance of it together with an instance of its associated spacetime volume. This model combines two quite different kinds of substance: an instance of E4 Period is a phenomenon while an instance of E92 Spacetime Volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance of E4 Period is regarded to be unique to it due to all its details and fuzziness; its identity and existence depends uniquely on the identity of the instance of E4 Period. Therefore, this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language. Typical use of this class in cultural heritage documentation is for documenting cultural and artistic periods. There are two different conceptualisations of ‘artistic style’, defined either by physical features or by historical context. For example, “Impressionism” can be viewed as a period in the European sphere of influence lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an instance of E4 Period, and the second defines morphological object types that fall under E55 Type. A geopolitical unit as a specific case of an instance of E4 Period is the set of activities and phenomena related to the claim of power, the consequences of belonging to a jurisdictional area and an administrative system that establishes a geopolitical unit. Examples from the modern period are countries or administrative areas of countries such as districts whose actions and structures define activities and phenomena in the area that they intend to govern. The borders of geopolitical units are often defined in contracts or treaties although they may deviate from the actual practice. The spatiotemporal properties of Geopolitical units can be modelled through the properties inherited from E92 Spacetime Volume. Another specific case of an instance of E4 Period is the actual extent of the set of activities and phenomena as evidenced by their physical traces that define a settlement, such as the populated period of Nineveh. Examples: - Jurassic (Hallam, 1975) - Populated Period of Nineveh - Imperial Rome under Marcus Aurelius - European Bronze Age (Harrison, 2004) - Italian Renaissance (Macdonald, 1992) - Thirty Years War (Lee, 1991) - Sturm und Drang (Berkoff, 2013) - Cubism (Cox, 2000) - The Capital of Russia (E4) [the capital of Russia in the sense of an administrative unit moved in historical times from Moscow to St Petersburg and then back to Moscow. This exemplifies an administrative unit changing place over time without temporal discontinuity] - The settling activity of the community of Helsinki (a.k.a. Helsingfors) (E7) [the original settlement called Helsinki was located in the area of the modern airport. The community moved later to settle on the coast. This exemplifies a continued activity changing place over time without temporal discontinuity] - Bronze Age (E4) [Bronze Age, in the sense of technological adoption, spread over disjoint areas including islands such as the British Isles without temporal discontinuity] - Japan, the state (E4) [In 2021, the Japanese state as a political unit comprised in 6852 islands extending along the Pacific coast of Asia] In First Order Logic: - E4(x) ⇒ E2(x) - E4(x) ⇒ E92(x) """@en ; rdfs:label "E4 Period"@en , "E4 Período"@pt , "E4 Phase"@de , "E4 Période"@fr , "E4 Περίοδος"@el , "E4 Пeриод"@ru , "E4 时期"@zh ; "E4"@en ; "Period"@en , "Período"@pt , "Phase"@de , "Période"@fr , "Περίοδος"@el , "Пeриод"@ru , "时期"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end, and a duration. Instances of E52 Time-Span have no semantic connotations about phenomena happening within the temporal extent they represent. They do not convey any meaning other than a positioning on the “time-line” of chronology. The actual extent of an instance of E52 Time-Span can be approximated by properties of E52 Time-Span giving inner and outer bounds in the form of dates (instances of E61 Time Primitive). Comparing knowledge about time-spans is fundamental for chronological reasoning. Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr & Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which people can infer knowledge about it, such as in relative chronologies. Some instances of E52 may be defined precisely as representing a declaration of a temporal extent, as, for instance, done in a business contract. They constitute declarative time-spans as defined in CRMgeo (Doerr & Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span. When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known. Examples: - 1961 - From 12-17-1993 to 12-8-1996 - 14h30 to 16h22 4(th) July 1945 - 9.30 am 1.1.1999 to 2.00 pm 1.1.1999 - the time-span of the Ming Dynasty (Chan, 2011) In First Order Logic: - E52(x) ⇒ E1(x) """@en ; rdfs:label "E52 Intervalle temporel"@fr , "E52 Período de Tempo"@pt , "E52 Time-Span"@en , "E52 Zeitspanne"@de , "E52 Χρονικό Διάστημα"@el , "E52 Интeрвал Врeмeни"@ru , "E52 时段"@zh ; "E52"@en ; "Intervalle temporel"@fr , "Período de Tempo"@pt , "Time-Span"@en , "Zeitspanne"@de , "Χρονικό Διάστημα"@el , "Интeрвал Врeмeни"@ru , "时段"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E53_Place rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises extents in the natural space where people live, in particular on the surface of the Earth, in the pure sense of physics: independent from temporal phenomena and matter. They may serve describing the physical location of things or phenomena or other areas of interest. Geometrically, instances of E53 Place constitute single contiguous areas or a finite aggregation of disjoint areas in space which are each individually contiguous. They may have fuzzy boundaries. The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks, but may also be determined by reference to mobile objects. A Place can be determined by combining a frame of reference and a location with respect to this frame. It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, people are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object, i.e. H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance. Any instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for). Examples: - the extent of the UK in the year 2003 - the position of the hallmark on the inside of my wedding ring (fictitious) - the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone” - here -> <- [the place between these two arrows in one of the reader's paper copy of this document. Each copy constitutes a different place of this spot.] In First Order Logic: - E53(x) ⇒ E1(x) """@en ; rdfs:label "E53 Lieu"@fr , "E53 Local"@pt , "E53 Ort"@de , "E53 Place"@en , "E53 Τόπος"@el , "E53 Мeсто"@ru , "E53 地点"@zh ; "E53"@en ; "Lieu"@fr , "Local"@pt , "Ort"@de , "Place"@en , "Τόπος"@el , "Мeсто"@ru , "地点"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E54_Dimension rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values, etc. An instance of E54 Dimension represents the empirical or theoretically derived quantity, including the precision tolerances resulting from the particular method or calculation. The identity of an instance of E54 Dimension depends on the method of its determination because each method may produce different values even when determining comparable qualities. For instance, the wingspan of a bird alive or dead is a different dimension. Thermoluminescence dating and Rehydroxylation [RHX] dating are different dimensions of temporal distance from now, even if they aim at dating the same object. The method of determination should be expressed using the property P2 has type (is type of). Note that simple terms such as “diameter” or “length” are normally insufficient to unambiguously describe a respective dimension. In contrast, “maximum linear extent” may be sufficient. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension adequate to the precision of the applied method of determination. If the respective quantity belongs to a non-discrete space according to the laws of physics, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that comparability of values described in different units depends critically on the representation as value regions. Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension, as appropriate. Examples: - the weight of the Luxor Obelisk [250 metric tons] - the vertical height of the statue of David by Michelangelo [5.17 metres] - the weight of the Great Star of Africa diamond [530.2 carats] - the calibrated C14 date for the Shroud of Turin [AD1262-1312, 1303-1384] - the horizontal diameter of the Stonehenge Sarsen Circle [33 metres] (Pryor, 2016) - the length of the sides of the Great Pyramid at Giza [230.34 metres] (Lehner and Hawass, 2017) - the duration of the time-span of the Battle of Issos/Issus on 15(th) November 333 B.C.E. [less than 12 hours] (Howard, 2012) - Christie’s hammer price, in British Pounds, for Vincent van Gogh's \"Still Life: Vase with Fifteen Sunflowers\" in London on 30(th) March 1987 (E97) [24.75 million GBP (British Pounds)] In First Order Logic: - E54(x) ⇒ E1(x) """@en ; rdfs:label "E54 Dimension"@en , "E54 Dimension"@fr , "E54 Dimensão"@pt , "E54 Maß"@de , "E54 Μέγεθος"@el , "E54 Размeр"@ru , "E54 度量规格"@zh ; "E54"@en ; "Dimension"@en , "Dimension"@fr , "Dimensão"@pt , "Maß"@de , "Μέγεθος"@el , "Размeр"@ru , "度量规格"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E55_Type rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts, in contrast to instances of E41 Appellation which are used to name instances of CIDOC CRM classes. E55 Type provides an interface to domain specific ontologies and thesauri. These can be represented in the CIDOC CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term): E55 Type. Such hierarchies may be extended with additional properties. Examples: - weight, length, depth [types for instances of E54 Dimension] - portrait, sketch, animation [types for instances of E36 Visual Item] - French, English, German [types for instances of E56 Language] - excellent, good, poor [types for instances of E3 Condition State] - Ford Model T, chop stick [types for instances of E22 Human-Made Object] - cave, doline, scratch [types for instances of E26 Physical Feature] - poem, short story [types for instances of E33 Linguistic Object] - wedding, earthquake, skirmish [types for instances of E5 Event] In First Order Logic: - E55(x) ⇒ E28(x) """@en ; rdfs:label "E55 Tipo"@pt , "E55 Type"@en , "E55 Type"@fr , "E55 Typus"@de , "E55 Tип"@ru , "E55 Τύπος"@el , "E55 类型"@zh ; "E55"@en ; "Tipo"@pt , "Type"@en , "Type"@fr , "Typus"@de , "Tип"@ru , "Τύπος"@el , "类型"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E56_Language rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts. This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g. “instances of Mandarin Chinese”. It is recommended that internationally or nationally agreed codes and terminology should be used to denote instances of E56 Language, such as those defined in ISO 639-3:2007 and later versions. Examples: - ell [Greek] - eng [English] - epo [Esperanto] - spa [Spanish] - fra [French] In First Order Logic: - E56(x) ⇒ E55(x) """@en ; rdfs:label "E56 Language"@en , "E56 Langue"@fr , "E56 Língua"@pt , "E56 Sprache"@de , "E56 Γλώσσα"@el , "E56 Язык"@ru , "E56 语种"@zh ; "E56"@en ; "Language"@en , "Langue"@fr , "Língua"@pt , "Sprache"@de , "Γλώσσα"@el , "Язык"@ru , "语种"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E57_Material rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class is a specialization of E55 Type and comprises the concepts of materials. Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of (forms part of): E18 Physical Thing). This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g. “instances of gold”. It is recommended that internationally or nationally agreed codes and terminology should be used. Examples: - brick (Gurcke, 1987) - gold (Watson, 1990) - aluminium (Norman, 1986) - polycarbonate (Mhaske, 2011) - resin (Barton, 1992) In First Order Logic: - E57(x) ⇒ E55(x) """@en ; rdfs:label "E57 Material"@de , "E57 Material"@en , "E57 Material"@pt , "E57 Matériau"@fr , "E57 Υλικό"@el , "E57 Матeриал"@ru , "E57 材质"@zh ; "E57"@en ; "Material"@de , "Material"@en , "Material"@pt , "Matériau"@fr , "Υλικό"@el , "Матeриал"@ru , "材质"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E58_Measurement_Unit rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc. This type is used categorically in the model without reference to instances of it, i.e. the model does not foresee the description of instances of instances of E58 Measurement Unit, e.g. “instances of cm”. Système International (SI) units or internationally recognized non-SI terms should be used whenever possible, such as those defined by ISO80000:2009. Archaic Measurement Units used in historical records should be preserved. Examples: - cm [centimetre] - km [kilometre] - m [metre] - m/s [metres per second] (Hau et al., 1999) - A [ampere] - GRD [Greek Drachma] (E98) (Daniel, 2014) - C [degrees centigrade] (Beckman, 1998) In First Order Logic: - E58(x) ⇒ E55(x) """@en ; rdfs:label "E58 Eдиница Измeрeния"@ru , "E58 Maßeinheit"@de , "E58 Measurement Unit"@en , "E58 Unidade de Medida"@pt , "E58 Unité de mesure"@fr , "E58 Μονάδα Μέτρησης"@el , "E58 测量单位"@zh ; "E58"@en ; "Eдиница Измeрeния"@ru , "Maßeinheit"@de , "Measurement Unit"@en , "Unidade de Medida"@pt , "Unité de mesure"@fr , "Μονάδα Μέτρησης"@el , "测量单位"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E5_Event rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises distinct, delimited and coherent processes and interactions of a material nature, in cultural, social or physical systems, involving and affecting instances of E77 Persistent Item in a way characteristic of the kind of process. Typical examples are meetings, births, deaths, actions of decision taking, making or inventing things, but also more complex and extended ones such as conferences, elections, building of a castle, or battles. While the continuous growth of a tree lacks the limits characteristic of an event, its germination from a seed does qualify as an event. Similarly, the blowing of the wind lacks the distinctness and limits of an event, but a hurricane, flood or earthquake would qualify as an event. Mental processes are considered as events, in cases where they are connected with the material externalization of their results; for example, the creation of a poem, a performance or a change of intention that becomes obvious from subsequent actions or declarations. The effects of an instance of E5 Event may not lead to relevant permanent changes of properties or relations of the items involved in it, for example an unrecorded performance. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event. While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example, the statements made during a meeting and the listening of the audience. Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analysed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the size of the phenomena. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy overall effect and are thus not instances of E5 Event. Examples: - the birth of Cleopatra (E67) (Pomeroy, 1984) - the destruction of Herculaneum by volcanic eruption in 79 AD (E6) (Camardo, 2013) - World War II (E7) (Barber, 1994) - the Battle of Stalingrad (E7) (Hoyt, 1993) - the Yalta Conference (E7) (Harbutt, 2010) - my birthday celebration 28-6-1995 (E7) - the falling of a tile from my roof last Sunday (fictitious) - the CIDOC conference 2003 (E7) In First Order Logic: - E5(x) ⇒ E4(x) """@en ; rdfs:label "E5 Ereignis"@de , "E5 Event"@en , "E5 Evento"@pt , "E5 Évènement"@fr , "E5 Συμβάν"@el , "E5 Событиe"@ru , "E5 事件"@zh ; "E5"@en ; "Ereignis"@de , "Event"@en , "Evento"@pt , "Évènement"@fr , "Συμβάν"@el , "Событиe"@ru , "事件"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E63_Beginning_of_Existence rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises events that bring into existence any instance of E77 Persistent Item. It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for both a terminus post quem and a terminus ante quem. Examples: - the birth of my child (E67) (fictitious) - the birth of Snoopy, my dog (fictitious) - the calving of the iceberg that sank the Titanic - the construction of the Eiffel Tower (E12) (Tissandier, 1889) In First Order Logic: - E63(x) ⇒ E5(x) """@en ; rdfs:label "E63 Beginning of Existence"@en , "E63 Daseinsbeginn"@de , "E63 Début d’existence"@fr , "E63 Início da Existência"@pt , "E63 Αρχή Ύπαρξης"@el , "E63 Начало Сущeствования"@ru , "E63 初始"@zh ; "E63"@en ; "Beginning of Existence"@en , "Daseinsbeginn"@de , "Début d’existence"@fr , "Início da Existência"@pt , "Αρχή Ύπαρξης"@el , "Начало Сущeствования"@ru , "初始"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E64_End_of_Existence rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises events that end the existence of any instance of E77 Persistent Item. It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook both a terminus post quem and a terminus ante quem. In cases where substance from an instance of E77 Persistent Item continues to exist in a new form, the process would be documented as instances of E81 Transformation. Examples: - the death of Snoopy, my dog (fictitious) - the melting of the snowman (E6) - the burning of the Temple of Artemis in Ephesos by Herostratos in 356 BC (E7, E6) (Trell, 1945) In First Order Logic: - E64(x) ⇒ E5(x) """@en ; rdfs:label "E64 Daseinsende"@de , "E64 End of Existence"@en , "E64 Fim da Existência"@pt , "E64 Fin d’existence"@fr , "E64 Τέλος Ύπαρξης"@el , "E64 Конeц Сущeствования"@ru , "E64 结束"@zh ; "E64"@en ; "Daseinsende"@de , "End of Existence"@en , "Fim da Existência"@pt , "Fin d’existence"@fr , "Τέλος Ύπαρξης"@el , "Конeц Сущeствования"@ru , "结束"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E65_Creation rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """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) """@en ; rdfs:label "E65 Begriffliche Schöpfung"@de , "E65 Creation"@en , "E65 Criação"@pt , "E65 Création"@fr , "E65 Δημιουργία"@el , "E65 Созданиe"@ru , "E65 创建"@zh ; "E65"@en ; "Begriffliche Schöpfung"@de , "Creation"@en , "Criação"@pt , "Création"@fr , "Δημιουργία"@el , "Созданиe"@ru , "创建"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E66_Formation rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation, or nation. E66 Formation does not include the arbitrary aggregation of people who do not act as a collective. The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining. Examples: - the formation of the CIDOC CRM Special Interest Group in 2000 - the formation of the Soviet Union (Pipes, 1964) - the conspiring of the murderers of Caesar (Irwin, 1935) In First Order Logic: - E66(x) ⇒ E7(x) - E66(x) ⇒ E63(x) """@en ; rdfs:label "E66 Formation"@en , "E66 Formation"@fr , "E66 Formação"@pt , "E66 Gruppenbildung"@de , "E66 Συγκρότηση Ομάδας"@el , "E66 Формированиe"@ru , "E66 组成"@zh ; "E66"@en ; "Formation"@en , "Formation"@fr , "Formação"@pt , "Gruppenbildung"@de , "Συγκρότηση Ομάδας"@el , "Формированиe"@ru , "组成"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E67_Birth rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living being.) Twins, triplets, etc. are brought into life by the same instance of E67 Birth. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood since the advent of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth. Examples: - the birth of Alexander the Great (Stoneman, 2004) In First Order Logic: - E67(x) ⇒ E63(x) """@en ; rdfs:label "E67 Birth"@en , "E67 Geburt"@de , "E67 Naissance"@fr , "E67 Nascimento"@pt , "E67 Γέννηση"@el , "E67 Рождeниe"@ru , "E67 出生"@zh ; "E67"@en ; "Birth"@en , "Geburt"@de , "Naissance"@fr , "Nascimento"@pt , "Γέννηση"@el , "Рождeниe"@ru , "出生"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E68_Dissolution rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """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) """@en ; rdfs:label "E68 Dissolution"@en , "E68 Dissolution"@fr , "E68 Dissolução"@pt , "E68 Gruppenauflösung"@de , "E68 Διάλυση Ομάδας"@el , "E68 Роспуск"@ru , "E68 解散"@zh ; "E68"@en ; "Dissolution"@en , "Dissolution"@fr , "Dissolução"@pt , "Gruppenauflösung"@de , "Διάλυση Ομάδας"@el , "Роспуск"@ru , "解散"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E69_Death rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the deaths of human beings. If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented as instances of E64 End of Existence. Examples: - the murder of Julius Caesar (E69, E7) (Irwin, 1935) - the death of Senator Paul Wellstone (Monast and Tao, 2002) In First Order Logic: - E69(x) ⇒ E64(x) """@en ; rdfs:label "E69 Death"@en , "E69 Mort"@fr , "E69 Morte"@pt , "E69 Tod"@de , "E69 Θάνατος"@el , "E69 Смeрть"@ru , "E69 死亡"@zh ; "E69"@en ; "Death"@en , "Mort"@fr , "Morte"@pt , "Tod"@de , "Θάνατος"@el , "Смeрть"@ru , "死亡"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E6_Destruction rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises events that destroy one or more instances of E18 Physical Thing, such that they lose their identity as the subjects of documentation. Some destruction events are intentional, while others are independent of human activity. Intentional destruction can be documented by classifying the event as both an instance of E6 Destruction and of E7 Activity. The decision to document an object as destroyed, transformed, or modified is context-sensitive: 1. If the matter remaining from the destruction is not documented, the event is modelled solely as an instance of E6 Destruction. 2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not. 3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as an instance of E11 Modification. Examples: - the destruction of Herculaneum by volcanic eruption in 79 AD (Camardo, 2013) - the destruction of Nineveh (E6, E7) (River, 2016) - the breaking of a champagne glass yesterday by my dog (fictitious) In First Order Logic: - E6(x) ⇒ E64(x) """@en ; rdfs:label "E6 Destruction"@en , "E6 Destruction"@fr , "E6 Destruição"@pt , "E6 Zerstörung"@de , "E6 Καταστροφή"@el , "E6 Разрушeниe"@ru , "E6 破坏"@zh ; "E6"@en ; "Destruction"@en , "Destruction"@fr , "Destruição"@pt , "Zerstörung"@de , "Καταστροφή"@el , "Разрушeниe"@ru , "破坏"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E70_Thing rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ; rdfs:comment """Scope note: This general class comprises discrete, identifiable, instances of E77 Persistent Item that are documented as single units, that either consist of matter or depend on being carried by matter and are characterized by relative stability. They may be intellectual products or physical things. They may, for instance, have a solid physical form, an electronic encoding, or they may be a logical concept or structure. Examples: - my photograph collection (E78) (fictitious) - the bottle of milk in my refrigerator (E22) (fictitious) - the Riss A1 plan of the Straßburger Münster (French: Cathédrale Notre-Dame de Strasbourg) (E29) (Liess, R., 1985) - the thing on the top of Otto Hahn’s desk (E19) - the form of the no-smoking sign (E36) - the cave of Dirou, Mani, Greece (E26) (Psimenos, 2005) In First Order Logic: - E70(x) ⇒ E77(x) """@en ; rdfs:label "E70 Chose"@fr , "E70 Coisa"@pt , "E70 Sache"@de , "E70 Thing"@en , "E70 Πράγμα"@el , "E70 Вeщь"@ru , "E70 事物"@zh ; "E70"@en ; "Chose"@fr , "Coisa"@pt , "Sache"@de , "Thing"@en , "Πράγμα"@el , "Вeщь"@ru , "事物"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E71_Human-Made_Thing rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises discrete, identifiable human-made items that are documented as single units. These items are either intellectual products or human-made physical things, and are characterized by relative stability. They may, for instance, have a solid physical form, an electronic encoding, or they may be logical concepts or structures. Examples: - Beethoven’s 5(th) Symphony (E73) (Lockwood, 2015) - Michelangelo’s David (E22) (Paoletti and Bagemihl, 2015) - Einstein’s Theory of General Relativity (E89) (Hartle, 2003) - the taxon ‘Fringilla coelebs Linnaeus,1758’ (E55) (Sinkevicius and Narusevicius, 2002) In First Order Logic: - E71(x) ⇒ E70(x) """@en ; rdfs:label "E71 Chose élaborée par l’humain"@fr , "E71 Human-Made Thing"@en , "E71 Рукотворный Прeдмeт"@ru ; "E71"@en ; "Chose élaborée par l’humain"@fr , "Human-Made Thing"@en , "Рукотворный Прeдмeт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E72_Legal_Object rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied. This is generally true for all instances of E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of an instance of E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CIDOC CRM. Examples: - the Cullinan diamond (E19) (Scarratt and Shor, 2006) - definition of the CIDOC Conceptual Reference Model Version 5.0.4 (E73) (ISO 21127: 2014) In First Order Logic: - E72(x) ⇒ E70(x) """@en ; rdfs:label "E72 Legal Object"@en , "E72 Objet juridique"@fr , "E72 Objeto Jurídico"@pt , "E72 Rechtsobjekt"@de , "E72 Νομικό Αντικείμενο"@el , "E72 Объeкт Права"@ru , "E72 法律对象"@zh ; "E72"@en ; "Legal Object"@en , "Objet juridique"@fr , "Objeto Jurídico"@pt , "Rechtsobjekt"@de , "Νομικό Αντικείμενο"@el , "Объeкт Права"@ru , "法律对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises identifiable immaterial items, such as poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. The encoding structure known as a “named graph” also falls under this class, so that each “named graph” is an instance of E73 Information Object. An instance of E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression. Examples: - image BM000038850.JPG from the Clayton Herbarium in London (E31) (Natural History Museum, 2021) - E. A. Poe's “The Raven” (Poe, 1869) - the movie “The Seven Samurai” by Akira Kurosawa (Mellen, 2002) - the text of Huray describing the Maxwell Equations (Huray, 2010) - the Getty AAT as published as Linked Open Data, accessed 1/10/2014 In First Order Logic: - E73(x) ⇒ E89(x) - E73(x) ⇒ E90(x) """@en ; rdfs:label "E73 Information Object"@en , "E73 Informationsgegenstand"@de , "E73 Objet informationnel"@fr , "E73 Objeto de Informação"@pt , "E73 Πληροφοριακό Αντικείμενο"@el , "E73 Информационный Объeкт"@ru , "E73 信息对象"@zh ; "E73"@en ; "Information Object"@en , "Informationsgegenstand"@de , "Objet informationnel"@fr , "Objeto de Informação"@pt , "Πληροφοριακό Αντικείμενο"@el , "Информационный Объeкт"@ru , "信息对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E74_Group rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises any gatherings or organizations of human individuals or groups that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. In such cases, it may happen that the group never had more than one member. A joint pseudonym (i.e. a name that seems indicative of an individual but that is actually used as a persona by two or more people) is a particular case of E74 Group. A gathering of people becomes an instance of E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modelled as membership in an instance of E74 Group. Married couples and other concepts of family are regarded as particular examples of E74 Group. Examples: - the Impressionists (Wilson, 1994) - the Navajo (Correll, 1972) - the Greeks (Williams, 1993) - the peace protestors in New York City on 15(th) February 2003 - Exxon-Mobil (Raymond, 2006) - King Solomon and his wives (Thieberger, 1947) - the President of the Swiss Confederation - Nicolas Bourbaki [the collective pseudonym of a group of mathematicians, predominantly French alumni of the École normale supérieure] (Aczel, 2007) - Betty Crocker (Crocker, 2012) - Ellery Queen [Ellery Queen is a pseudonym created in 1929 by American crime fiction writers Frederic Dannay and Manfred Bennington Lee.] (Wheat, 2005) - Greenpeace - Paveprime Ltd - the National Museum of Denmark In First Order Logic: - E74(x) ⇒ E39(x) """@en ; rdfs:label "E74 Group"@en , "E74 Groupe"@fr , "E74 Grupo"@pt , "E74 Menschliche Gruppe"@de , "E74 Ομάδα"@el , "E74 Группа"@ru , "E74 团体"@zh ; "E74"@en ; "Group"@en , "Groupe"@fr , "Grupo"@pt , "Menschliche Gruppe"@de , "Ομάδα"@el , "Группа"@ru , "团体"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E77_Persistent_Item rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises items that have persistent characteristics of structural nature substantially related to their identity and their integrity, sometimes known as “endurants” in philosophy. Persistent Items may be physical entities, such as people, animals or things, conceptual entities such as ideas, concepts, products of the imagination or even names. Instances of E77 Persistent Item may be present or be part of interactions in different periods or events. They can repeatedly be recognized at disparate occasions during their existence by characteristics of structural nature. The respective characteristics need not be exactly the same during all the existence of an instance of E77 Persistent Item. Often, they undergo gradual change, still bearing some similarities with that of previous times, or disappear completely and new emerge. For instance, a person, from the time of being born on, will gradually change all its features and acquire new ones, such as a scar. Even the DNA in different body cells will develop defects and mutations. Nevertheless, relevant characteristics used should be sufficiently similar to recognize the instance for some substantial period of time. The more specific criteria that determine the identity of instances of subclasses of E77 Persistent Item may vary considerably and are described or referred to in the respective scope notes. The decision about which exact criteria to use depends on whether the observable behaviour of the respective part of reality such confined conforms to the reasoning the user is interested in. For example, a building can be regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria, such as being bodily separated from other persons. Similarly, inanimate objects may be subject to exchange of parts and matter. On the opposite, the identity of a (version of a) text of a scientific publication is given by the exact arrangement of its relevant symbols. The main classes of objects that fall outside the scope of the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties. An instance of E77 Persistent Item does not require actual knowledge of the identifying features of the instance being currently known. There may be cases, where the actual identifying features of an instance of E77 Persistent Item are not decidable at a particular state of knowledge. Examples: - Leonardo da Vinci (E21) (Strano, 1953) - Stonehenge (E24) (Pryor, 2016) - the hole in the ozone layer (E4) (Hufford and Horwitz, 2005) - the First Law of Thermodynamics (E89) (Craig and Gislason, 2002) - the Bermuda Triangle (E53) (Dolan, 2005) In First Order Logic: - E77(x) ⇒ E1(x) """@en ; rdfs:label "E77 Entidade Persistente"@pt , "E77 Entité persistante"@fr , "E77 Persistent Item"@en , "E77 Seiendes"@de , "E77 Ον"@el , "E77 Постоянная Сущность"@ru , "E77 持久项"@zh ; "E77"@en ; "Entidade Persistente"@pt , "Entité persistante"@fr , "Persistent Item"@en , "Seiendes"@de , "Ον"@el , "Постоянная Сущность"@ru , "持久项"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E78_Curated_Holding rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. Typical instances of curated holdings are museum collections, archives, library holdings and digital libraries. A digital library is regarded as an instance of E18 Physical Thing because it requires keeping physical carriers of the electronic content. Items may be added or removed from an E78 Curated Holding in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Curated Holding who is often referred to using the name of the E78 Curated Holding (e.g. “The Wallace Collection decided…”). Collective objects in the general sense, like a tomb full of gifts, a folder with stamps, or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Curated Holding. This is because they form wholes, either because they are physically bound together or because they are kept together for their functionality. Examples: - the John Clayton Herbarium (Blake, 1918), (Natural History Museum, 2021) - the Wallace Collection (Ingamells, 1990) - Mikael Heggelund Foslie’s coralline red algae Herbarium at the Museum of Natural History and Archaeology, Trondheim, Norway (Woelkerling et al., 2005) - the Digital Collections of the Munich DigitiZation Center (MDZ) accessible via https://www.digitale-sammlungen.de/ at least in January 2018. In First Order Logic: - E78(x) ⇒ E24(x) """@en ; rdfs:label "E78 Collection"@fr , "E78 Curated Holding"@en , "E78 Отвeтствeнноe Хранeниe"@ru ; "E78"@en ; "Collection"@fr , "Curated Holding"@en , "Отвeтствeнноe Хранeниe"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E79_Part_Addition rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises activities that result in an instance of E18 Physical Thing being increased, enlarged, or augmented by the addition of a part. Typical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated instance of E78 Curated Holding. Both the E18 Physical Thing being augmented and the E18 Physical Thing that is being added are treated as separate identifiable wholes prior to the instance of E79 Part Addition. Following the addition of parts, the resulting assemblages are treated objectively as single identifiable wholes, made up of constituent or component parts bound together either physically (for example the engine becoming a part of the car), or by sharing a common purpose (such as the 32 chess pieces that make up a chess set). This class of activities forms a basis for reasoning about the history and continuity of identity of objects that are integrated into other objects over time, such as precious gemstones being repeatedly incorporated into different items of jewellery, or cultural artefacts being added to different museum instances of E78 Curated Holding over their lifespan. Examples: - the setting of the Koh-I-Noor diamond into the crown of Queen Elizabeth the Queen Mother (Dalrymple, 2017) - the addition of the painting “Room in Brooklyn” by Edward Hopper to the collection of the Museum of Fine Arts, Boston - the attachment of the bronze hand on the tree forming the Alpi Marittime [ https://giuseppepenone.com/en/words/maritime-alps] (Mangini, 2010) In First Order Logic: - E79(x) ⇒ E11(x) """@en ; rdfs:label "E79 Adição de Parte"@pt , "E79 Ajout d'élément"@fr , "E79 Part Addition"@en , "E79 Teilhinzufügung"@de , "E79 Προσθήκη Μερών"@el , "E79 Добавлeниe Части"@ru , "E79 部分增加"@zh ; "E79"@en ; "Adição de Parte"@pt , "Ajout d'élément"@fr , "Part Addition"@en , "Teilhinzufügung"@de , "Προσθήκη Μερών"@el , "Добавлeниe Части"@ru , "部分增加"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E7_Activity rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. This notion includes complex, composite, and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door. Examples: - the Battle of Stalingrad (Hoyt, 1993) - the Yalta Conference (Harbutt, 2010) - my birthday celebration 28-6-1995 - the writing of “Faust” by Goethe (E65) (Williams, 2020) - the formation of the Bauhaus 1919 (E66) (Droste, 2006) - the people of Iraq giving the name ‘Quyunjig’ to the place identified by the TGN as ‘7017998’ - Kira Weber working in glass art from 1984 to 1993 - Kira Weber working in oil and pastel painting from 1993 In First Order Logic: - E7(x) ⇒ E5(x) """@en ; rdfs:label "E7 Activity"@en , "E7 Activité"@fr , "E7 Atividade"@pt , "E7 Handlung"@de , "E7 Δράση"@el , "E7 Дeятeльность"@ru , "E7 活动"@zh ; "E7"@en ; "Activity"@en , "Activité"@fr , "Atividade"@pt , "Handlung"@de , "Δράση"@el , "Дeятeльность"@ru , "活动"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E80_Part_Removal rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the activities that result in an instance of E18 Physical Thing being decreased by the removal of a part. Typical scenarios include the detachment of an accessory, the removal of a component or part of a composite object, or the deaccessioning of an object from a curated collection, an instance of E78 Curated Holding. If the instance of E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an instance of E81 Transformation, i.e. a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be modelled as both an instance of E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewellery, or cultural artifacts being deaccessioned from different museum collections over their lifespan. Examples: - the removal of the Porite coral specimen from the Cocos Islands by Charles Darwin in April 1836 (Natural History Museum, 2021, b) - the removal of the engine from my car (fictitious) - the disposal of object number 1976:234 from the collection (fictitious) In First Order Logic: - E80(x) ⇒ E11(x) """@en ; rdfs:label "E80 Part Removal"@en , "E80 Remoção de Parte"@pt , "E80 Retrait d'élément"@fr , "E80 Teilentfernung"@de , "E80 Αφαίρεση Μερών"@el , "E80 Удалeниe Части"@ru , "E80 部分去除"@zh ; "E80"@en ; "Part Removal"@en , "Remoção de Parte"@pt , "Retrait d'élément"@fr , "Teilentfernung"@de , "Αφαίρεση Μερών"@el , "Удалeниe Части"@ru , "部分去除"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E81_Transformation rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises the events that result in the simultaneous destruction of one or more than one E18 Physical Thing and the creation of one or more than one E18 Physical Thing that preserves recognizable substance and structure from the first one(s) but has fundamentally different nature or identity. Although the old and the new instances of E18 Physical Thing are treated as discrete entities having separate, unique identities, they are causally connected through the E81 Transformation; the destruction of the old E18 Physical Thing(s) directly causes the creation of the new one(s) using or preserving some relevant substance and structure. Instances of E81 Transformation are therefore distinct from re-classifications (documented using E17 Type Assignment) or modifications (documented using E11 Modification) of objects that do not fundamentally change their nature or identity. Characteristic cases are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimen in natural history. Even though such instances of E81 Transformation are often motivated by a change of intended use, substantial material changes should justify the documentation of the result as a new instance of E18 Physical Thing and not just the change of function. The latter may be documented as an extended activity (instance of E7 Activity) of using it. Examples: - the mummification of Tut-Ankh-Amun (E81, E12) [the mummification of the body of the deceased is a human production process and simultaneously preserves structures of the body at and before death] (Carter and Mace 1977) - the death, carbonization and petrification of some people of Pompeii in 79AD by the intense heat of a pyroclastic cloud and ashes from the Eruption of Mount Vesuvius (E69, E81) - the transformation of the Hephaisteion temple in Athens, better known as “Theseion”, into a Christian church, dedicated to Saint George around AD 700 (E81,E12) [which actually helped preserving part of the antique temple structure from 449BC] In First Order Logic: - E81(x) ⇒ E63(x) - E81(x) ⇒ E64(x) """@en ; rdfs:label "E81 Transformation"@en , "E81 Transformation"@fr , "E81 Transformação"@pt , "E81 Umwandlung"@de , "E81 Μετατροπή"@el , "E81 Трансформация"@ru , "E81 转变"@zh ; "E81"@en ; "Transformation"@en , "Transformation"@fr , "Transformação"@pt , "Umwandlung"@de , "Μετατροπή"@el , "Трансформация"@ru , "转变"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E83_Type_Creation rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises activities formally defining new types of items. It is typically a rigorous scholarly or scientific process that ensures a type is exhaustively described and appropriately named. In some cases, particularly in archaeology and the life sciences, E83 Type Creation requires the identification of an exemplary specimen and the publication of the type definition in an appropriate scholarly forum. The activity modelled as an instance of E83 Type Creation is central to research in the life sciences, where a type would be referred to as a “taxon,” the type description as a “protologue,” and the exemplary specimens as “original element” or “holotype”. Examples: - creation of the taxon Penicillium brefeldianum (Dodge, 1933) - addition of class E85 Joining to the CIDOC CRM In First Order Logic: - E83(x) ⇒ E65(x) """@en ; rdfs:label "E83 Criação de Tipo"@pt , "E83 Création de type"@fr , "E83 Type Creation"@en , "E83 Typuserfindung"@de , "E83 Δημιουργία Τύπου"@el , "E83 Созданиe Типа"@ru , "E83 类型创建"@zh ; "E83"@en ; "Criação de Tipo"@pt , "Création de type"@fr , "Type Creation"@en , "Typuserfindung"@de , "Δημιουργία Τύπου"@el , "Созданиe Типа"@ru , "类型创建"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E85_Joining rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the activities that result in an instance of E39 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party. Typical scenarios include becoming a member of a social organisation, becoming an employee of a company, marriage, the adoption of a child by a family, and the inauguration of somebody into an official position. Examples: - the election of Sir Isaac Newton as Member of Parliament for the University of Cambridge to the Convention Parliament of 1689 (Gleick, 2003) - the inauguration of Mikhail Sergeyevich Gorbachev as leader of the Union of Soviet Socialist Republics (USSR) in 1985 (Butson, 1986) - the implementation of the membership treaty between EU and Denmark, 1(st) January 1993 In First Order Logic: - E85(x) ⇒ E7(x) """@en ; rdfs:label "E85 Adhésion"@fr , "E85 Beitritt"@de , "E85 Joining"@en , "E85 Вступлeниe"@ru , "E85 加入"@zh ; "E85"@en ; "Adhésion"@fr , "Beitritt"@de , "Joining"@en , "Вступлeниe"@ru , "加入"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E86_Leaving rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party. Typical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position. Examples: - the end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702 (Gleick, 2003) - George Washington’s leaving office in 1797 (Jones, 1979) - the implementation of the treaty regulating the termination of Greenland’s membership in EU between EU, Denmark and Greenland 1(st) February 1985 In First Order Logic: - E86(x) ⇒ E7(x) """@en ; rdfs:label "E86 Austritt"@de , "E86 Départ"@fr , "E86 Leaving"@en , "E86 Выход"@ru , "E86 离开"@zh ; "E86"@en ; "Austritt"@de , "Départ"@fr , "Leaving"@en , "Выход"@ru , "离开"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E87_Curation_Activity rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the activities that contribute to the management and the preservation and evolution of instances of E78 Curated Holding, following an implicit or explicit curation plan. It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded. Items are accumulated and organized following criteria such as subject, chronological period, material type, style of art, etc., and can be added or removed from an instance of E78 Curated Holding for a specific purpose and/or audience. The initial aggregation of items to form a collection is regarded as an instance of E12 Production Event, while the activities of evolving, preserving, and promoting a collection are regarded as instances of E87 Curation Activity. Examples: - the curation of Mikael Heggelund Foslie’s coralline red algae Herbarium 1876 to 1909 (when Foslie died), now at the Museum of Natural History and Archaeology, Norway (Woelkerling et al., 2005) In First Order Logic: - E87(x) ⇒ E7(x) """@en ; rdfs:label "E87 Activité curatoriale"@fr , "E87 Curation Activity"@en , "E87 Kuratorische Tätigkeit"@de , "E87 Кураторство"@ru , "E87 管理"@zh ; "E87"@en ; "Activité curatoriale"@fr , "Curation Activity"@en , "Kuratorische Tätigkeit"@de , "Кураторство"@ru , "管理"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse. This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object. Examples: - Maxwell’s Equations (Ball, 1962) - the ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in Oxford edition - the underlying prototype of any “no-smoking” sign (E36) - the common ideas of the plots of the movie “The Seven Samurai” by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges (Mellen, 2002) - the image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E36) - the character “Little Red Riding Hood”, variants of which appear amongst others in Grimm brothers’ “Rotkäppchen”, other oral fairy tales and the film “Hoodwinked” - the place “Havnor” as invented by Ursula K. Le Guin for her “Earthsea” book series, the related maps and appearing in derivative works based on these novels In First Order Logic: - E89(x) ⇒ E28(x) """@en ; rdfs:label "E89 Aussagenobjekt"@de , "E89 Objet propositionnel"@fr , "E89 Propositional Object"@en , "E89 Пропозициональный Объeкт"@ru , "E89 命题对象"@zh ; "E89"@en ; "Aussagenobjekt"@de , "Objet propositionnel"@fr , "Propositional Object"@en , "Пропозициональный Объeкт"@ru , "命题对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E8_Acquisition rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more other instances of E39 Actor. The class also applies to the establishment or loss of ownership of instances of E18 Physical Thing. It does not, however, imply changes of any other kinds of rights. The recording of the donor and/or recipient is optional. It is possible that in an instance of E8 Acquisition there is either no donor or no recipient. Depending on the circumstances, it may describe: 1. the beginning of ownership 2. the end of ownership 3. the transfer of ownership 4. the acquisition from an unknown source 5. the loss of title due to destruction of the item It may also describe events where a collector appropriates legal title, for example, by annexation or field collection. The interpretation of the museum notion of “accession” differs between institutions. The CIDOC CRM therefore models legal ownership (E8 Acquisition) and physical custody (E10 Transfer of Custody) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these. Examples: - the collection of a hammerhead shark, genus Sphyrna (Carchariniformes), by John Steinbeck and Edward Ricketts at Puerto Escondido in the Gulf of Mexico on 25(th) March 1940. (Steinbeck, 2000) - the acquisition of El Greco’s “The Apostles Peter and Paul” by the State Hermitage in Saint Petersburg. (https://hermitagemuseum.org/wps/portal/hermitage/digital-collection/01.+Paintings/32730) - the loss of my stuffed Fringilla coelebs due to insect damage last year (fictitious) In First Order Logic: - E8(x) ⇒ E7(x) """@en ; rdfs:label "E8 Acquisition"@en , "E8 Acquisition"@fr , "E8 Aquisição"@pt , "E8 Erwerb"@de , "E8 Απόκτηση"@el , "E8 Поступлeниe"@ru , "E8 采访"@zh ; "E8"@en ; "Acquisition"@en , "Acquisition"@fr , "Aquisição"@pt , "Erwerb"@de , "Απόκτηση"@el , "Поступлeниe"@ru , "采访"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E90_Symbolic_Object rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment """Scope note: This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code, or mathematical formulae that have an objectively recognizable structure and that are documented as single units. It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string. In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note and its subproperty P190 has symbolic content allow for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. “bit”, “Latin character”, RGB pixel). Examples: - ‘ecognizabl’ - the “no-smoking” sign (E36) - “BM000038850.JPG” (E41) [identifies a digital image] (Natural History Museum, 2021) - image BM000038850.JPG from the Clayton Herbarium in London (E36) [depicts specimen of Verbesina virginica] (Natural History Museum, 2021) - the distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E36) - the Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition “La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi” (E33) (Petrocchi, 1967) In First Order Logic: - E90(x) ⇒ E28(x) - E90(x) ⇒ E72(x) """@en ; rdfs:label "E90 Objet symbolique"@fr , "E90 Symbolic Object"@en , "E90 Symbolisches Objekt"@de , "E90 Символичeский Объeкт"@ru , "E90 符号对象"@zh ; "E90"@en ; "Objet symbolique"@fr , "Symbolic Object"@en , "Symbolisches Objekt"@de , "Символичeский Объeкт"@ru , "符号对象"@zh . ### http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises 4-dimensional point sets (volumes) in physical spacetime (in contrast to mathematical models of it) regardless of their true geometric forms. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, E53 Place, and E52 Time-Span are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of E92 Spacetime Volume is its projection on time. Examples: - the extent in space and time of the Event of Caesar’s murder (Irwin, 1935) - where and when the carbon 14 dating of the “Schoeninger Speer II” in 1996 took place (Kouwenhoven, 1997) - the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location (Goodwin, 2015) - the extent in space and time defined by a polygon approximating the Danube river flood in Austria between 6(th) and 9(th) August 2002 In First Order Logic: - E92(x) ⇒ E1(x) """@en ; rdfs:label "E92 Spacetime Volume"@en , "E92 Volume spatio-temporel"@fr , "E92 Область Пространства-Врeмeни"@ru ; "E92"@en ; "Spacetime Volume"@en , "Volume spatio-temporel"@fr , "Область Пространства-Врeмeни"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E93_Presence rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises instances of E92 Spacetime Volume, whose temporal extent has been chosen in order to determine the spatial extent of a phenomenon over the chosen time-span. Respective phenomena may, for instance, be historical events or periods, but can also be the diachronic extent and existence of physical things. In other words, instances of this class fix a slice of another instance of E92 Spacetime Volume in time. The temporal extent of an instance of E93 Presence typically is predetermined by the researcher so as to focus the investigation particularly on finding the spatial extent of the phenomenon by testing for its characteristic features. There are at least two basic directions such investigations might take. The investigation may wish to determine where something was during some time or it may wish to reconstruct the total passage of a phenomenon’s spacetime volume through an examination of discrete presences. Observation and measurement of features indicating the presence or absence of a phenomenon in some space allows for the progressive approximation of spatial extents through argumentation typically based on inclusion, exclusion and various overlaps. Examples: - the Roman Empire on 19(th) August AD 14 (Clare and Edwards, 1992) - Johann Joachim Winckelmann’s whereabouts in December 1775 (Leppmann, 1970) - Johann Joachim Winckelmann’s whereabouts from 19(th) November 1755 until 9(th) April 1768 (Leppmann, 1970) In First Order Logic: - E93(x) ⇒ E92(x) """@en ; rdfs:label "E93 Presence"@en , "E93 Présence"@fr , "E93 Присутствиe"@ru ; "E93"@en ; "Presence"@en , "Présence"@fr , "Присутствиe"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E96_Purchase rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more different instances of E39 Actor, where the transferring party is completely compensated by the payment of a monetary amount. In more detail, a purchase agreement establishes a fixed monetary obligation at its initialization on the receiving party, to the giving party. An instance of E96 Purchase begins with the contract or equivalent agreement and ends with the fulfilment of all contractual obligations. In the case that the activity is abandoned before both parties have fulfilled these obligations, the activity is not regarded as an instance of E96 Purchase. This class is a very specific case of the much more complex social business practices of exchange of goods and the creation and satisfaction of related social obligations. Purchase activities which define individual sales prices per object can be modelled by instantiating E96 Purchase for each object individually and as part of an overall instance of E96 Purchase transaction. Examples: - the purchase of 10 okka of nails by the captain A. Syrmas on 18(th) September 1895 in Thessaloniki (Syrmas, 1896) In First Order Logic: - E96(x) ⇒ E8(x) """@en ; rdfs:label "E96 Achat"@fr , "E96 Purchase"@en , "E96 Покупка"@ru ; "E96"@en ; "Achat"@fr , "Purchase"@en , "Покупка"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E97_Monetary_Amount rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises quantities of monetary possessions or obligations in terms of their nominal value with respect to a particular currency. These quantities may be abstract accounting units, the nominal value of a heap of coins or bank notes at the time of validity of the respective currency, the nominal value of a bill of exchange or other documents expressing monetary claims or obligations. It specifically excludes amounts expressed in terms of weights of valuable items, like gold and diamonds, and quantities of other non-currency items, like goats or stocks and bonds. Examples: - Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30(th) March 1987 In First Order Logic: - E97(x) ⇒ E54(x) """@en ; rdfs:label "E97 Monetary Amount"@en , "E97 Valeur monétaire"@fr , "E97 Дeнeжный Эквивалeнт"@ru ; "E97"@en ; "Monetary Amount"@en , "Valeur monétaire"@fr , "Дeнeжный Эквивалeнт"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E98_Currency rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises the units in which a monetary system, supported by an administrative authority or other community, quantifies and arithmetically compares all monetary amounts declared in the unit. The unit of a monetary system must describe a nominal value which is kept constant by its administrative authority and an associated banking system if it exists, and not by market value. For instance, one may pay with grams of gold, but the respective monetary amount would have been agreed as the gold price in US dollars on the day of the payment. Under this definition, British Pounds, U.S. Dollars, and European Euros are examples of currency, but “grams of gold” is not. One monetary system has one and only one currency. Instances of this class must not be confused with coin denominations, such as “Dime” or “Sestertius”. Non-monetary exchange of value in terms of quantities of a particular type of goods, such as cows, do not constitute a currency. Examples: - “As” [Roman mid republic] - “Euro” (Temperton, 1997) - “US Dollar” (Rose, 1978) In First Order Logic: - E98(x) ⇒ E58(x) """@en ; rdfs:label "E98 Currency"@en , "E98 Unité monétaire"@fr , "E98 Валюта"@ru ; "E98"@en ; "Currency"@en , "Unité monétaire"@fr , "Валюта"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E99_Product_Type rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises types that stand as the models for instances of E22 Human-Made Object that are produced as the result of production activities using plans exact enough to result in one or more series of uniform, functionally and aesthetically identical and interchangeable items. The product type is the intended ideal form of the manufacture process. It is typical of instances of E22 Human-Made Object that conform to an instance of E99 Product Type that its component parts are interchangeable with component parts of other instances of E22 Human-Made Object made after the model of the same instance of E99 Product Type. Frequently, the uniform production according to a given instance of E99 Product Type is achieved by creating individual tools, such as moulds or print plates that are themselves carriers of the design of the product type. Modern tools may use the flexibility of electronically controlled devices to achieve such uniformity. The product type itself, i.e. the potentially unlimited series of aesthetically equivalent items, may be the target of artistic design, rather than the individual object. In extreme cases, only one instance of a product type may have been produced, such as in a “print on demand” process which was only triggered once. However, this should not be confused with industrial prototypes, such as car prototypes, which are produced prior to the production line being set up, or test the production line itself. Examples: - Volkswagen Type 11 [Beetle] (Rieger, 2013) - Dragendorff 54 samian vessel - 1937 Edward VIII brass threepenny bit - Qin Crossbow trigger un-notched Part B (Bg2u) (Li, 2012) - Nokia Cityman 1320 [The first Nokia mobile phone] In First Order Logic: - E99(x) ⇒ E55(x) """@en ; rdfs:label "E99 Modèle de produit"@fr , "E99 Product Type"@en , "E99 Тип Продукта"@ru ; "E99"@en ; "Modèle de produit"@fr , "Product Type"@en , "Тип Продукта"@ru . ### http://www.cidoc-crm.org/cidoc-crm/E9_Move rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Scope note: This class comprises changes of the physical location of the instances of E19 Physical Object. Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event. Examples: - the relocation of London Bridge from the UK to the USA (Wildfang, 2005) - the movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15(th) September and 2(nd) November 2019 In First Order Logic: - E9(x) ⇒ E7(x) """@en ; rdfs:label "E9 Déplacement"@fr , "E9 Locomoção"@pt , "E9 Move"@en , "E9 Objektbewegung"@de , "E9 Μετακίνηση"@el , "E9 Пeрeмeщeниe"@ru , "E9 移动"@zh ; "E9"@en ; "Déplacement"@fr , "Locomoção"@pt , "Move"@en , "Objektbewegung"@de , "Μετακίνηση"@el , "Пeрeмeщeниe"@ru , "移动"@zh . ### http://www.w3.org/2000/01/rdf-schema#Class rdfs:Class rdf:type owl:Class . ### http://www.w3.org/2000/01/rdf-schema#Datatype rdfs:Datatype rdf:type owl:Class . ### http://www.w3.org/2000/01/rdf-schema#Literal rdfs:Literal rdf:type owl:Class . ### http://www.w3.org/2001/XMLSchema#anyURI xsd:anyURI rdf:type owl:Class . ### http://www.w3.org/2002/07/owl#Thing owl:Thing rdf:type owl:Class . ### http://www.w3.org/2004/02/skos/core#Collection rdf:type owl:Class . ### http://www.w3.org/2004/02/skos/core#Concept rdf:type owl:Class . ### http://www.w3.org/2006/vcard/ns#Agent rdf:type owl:Class . ### http://www.w3.org/2006/vcard/ns#Individual rdf:type owl:Class . ### http://www.w3.org/2006/vcard/ns#Organization rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Action rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3.org/ns/odrl/2/Agreement rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith , , , , , . ### http://www.w3.org/ns/odrl/2/Assertion rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith , , , , . ### http://www.w3.org/ns/odrl/2/Asset rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3.org/ns/odrl/2/AssetCollection rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3.org/ns/odrl/2/ConflictTerm rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Constraint rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Duty rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith , . ### http://www.w3.org/ns/odrl/2/LeftOperand rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/LogicalConstraint rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Offer rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith , , , . ### http://www.w3.org/ns/odrl/2/Operator rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Party rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### http://www.w3.org/ns/odrl/2/PartyCollection rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3.org/ns/odrl/2/PartyScope rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Permission rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith . ### http://www.w3.org/ns/odrl/2/Policy rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Privacy rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith , , . ### http://www.w3.org/ns/odrl/2/Prohibition rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3.org/ns/odrl/2/Request rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith , . ### http://www.w3.org/ns/odrl/2/RightOperand rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Rule rdf:type owl:Class . ### http://www.w3.org/ns/odrl/2/Set rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith . ### http://www.w3.org/ns/odrl/2/Ticket rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3.org/ns/odrl/2/UndefinedTerm rdf:type owl:Class . ### http://www.w3.org/ns/prov#Activity rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith ; rdfs:isDefinedBy ; rdfs:label "Activity" ; "starting-point" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities." ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Activity"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Activity"^^xsd:anyURI . ### http://www.w3.org/ns/prov#ActivityInfluence rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:maxCardinality "0"^^xsd:nonNegativeInteger ] ; owl:disjointWith ; rdfs:comment "ActivityInfluence provides additional descriptions of an Activity's binary influence upon any other kind of resource. Instances of ActivityInfluence use the prov:activity property to cite the influencing Activity."@en , "It is not recommended that the type ActivityInfluence be asserted without also asserting one of its more specific subclasses."@en ; rdfs:isDefinedBy ; rdfs:label "ActivityInfluence" ; rdfs:seeAlso ; "qualified" ; "ActivitiyInfluence is the capacity of an activity to have an effect on the character, development, or behavior of another by means of generation, invalidation, communication, or other."@en . ### http://www.w3.org/ns/prov#Agent rdf:type owl:Class ; owl:disjointWith ; rdfs:isDefinedBy ; rdfs:label "Agent" ; "starting-point" ; "agents-responsibility" ; "An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. "@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Agent"^^xsd:anyURI . ### http://www.w3.org/ns/prov#AgentInfluence rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "AgentInfluence provides additional descriptions of an Agent's binary influence upon any other kind of resource. Instances of AgentInfluence use the prov:agent property to cite the influencing Agent."@en , "It is not recommended that the type AgentInfluence be asserted without also asserting one of its more specific subclasses."@en ; rdfs:isDefinedBy ; rdfs:label "AgentInfluence" ; rdfs:seeAlso ; "qualified" ; "AgentInfluence is the capacity of an agent to have an effect on the character, development, or behavior of another by means of attribution, association, delegation, or other."@en . ### http://www.w3.org/ns/prov#Association rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:Association provides additional descriptions about the binary prov:wasAssociatedWith relation from an prov:Activity to some prov:Agent that had some responsiblity for it. For example, :baking prov:wasAssociatedWith :baker; prov:qualifiedAssociation [ a prov:Association; prov:agent :baker; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Association" ; "qualified" ; "agents-responsibility" ; "An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Association"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Attribution rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:Attribution provides additional descriptions about the binary prov:wasAttributedTo relation from an prov:Entity to some prov:Agent that had some responsible for it. For example, :cake prov:wasAttributedTo :baker; prov:qualifiedAttribution [ a prov:Attribution; prov:entity :baker; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Attribution" ; "qualified" ; "agents-responsibility" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; """Attribution is the ascribing of an entity to an agent. When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant."""@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribution"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribution"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Bundle rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "Note that there are kinds of bundles (e.g. handwritten letters, audio recordings, etc.) that are not expressed in PROV-O, but can be still be described by PROV-O."@en ; rdfs:isDefinedBy ; rdfs:label "Bundle" ; "expanded" ; "A bundle is a named set of provenance descriptions, and is itself an Entity, so allowing provenance of provenance to be expressed."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle-entity"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-bundle-declaration"^^xsd:anyURI . ### http://www.w3.org/ns/prov#Collection rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:isDefinedBy ; rdfs:label "Collection" ; "expanded" ; "collections" ; "A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection"^^xsd:anyURI . ### http://www.w3.org/ns/prov#Communication rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:Communication provides additional descriptions about the binary prov:wasInformedBy relation from an informed prov:Activity to the prov:Activity that informed it. For example, :you_jumping_off_bridge prov:wasInformedBy :everyone_else_jumping_off_bridge; prov:qualifiedCommunication [ a prov:Communication; prov:activity :everyone_else_jumping_off_bridge; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Communication" ; "qualified" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "Communication is the exchange of an entity by two activities, one activity using the entity generated by the other." ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Communication"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-wasInformedBy"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Delegation rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:Delegation provides additional descriptions about the binary prov:actedOnBehalfOf relation from a performing prov:Agent to some prov:Agent for whom it was performed. For example, :mixing prov:wasAssociatedWith :toddler . :toddler prov:actedOnBehalfOf :mother; prov:qualifiedDelegation [ a prov:Delegation; prov:entity :mother; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Delegation" ; "qualified" ; "agents-responsibility" ; """Delegation is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. For example, a student acted on behalf of his supervisor, who acted on behalf of the department chair, who acted on behalf of the university; all those agents are responsible in some way for the activity that took place but we do not say explicitly who bears responsibility and to what degree."""@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-delegation"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-delegation"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Derivation rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:Derivation provides additional descriptions about the binary prov:wasDerivedFrom relation from some derived prov:Entity to another prov:Entity from which it was derived. For example, :chewed_bubble_gum prov:wasDerivedFrom :unwrapped_bubble_gum; prov:qualifiedDerivation [ a prov:Derivation; prov:entity :unwrapped_bubble_gum; :foo :bar ]."@en , "The more specific forms of prov:Derivation (i.e., prov:Revision, prov:Quotation, prov:PrimarySource) should be asserted if they apply."@en ; rdfs:isDefinedBy ; rdfs:label "Derivation" ; "qualified" ; "derivations" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Derivation"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#Derivation-Relation"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#EmptyCollection rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3.org/ns/prov#End rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "An instance of prov:End provides additional descriptions about the binary prov:wasEndedBy relation from some ended prov:Activity to an prov:Entity that ended it. For example, :ball_game prov:wasEndedBy :buzzer; prov:qualifiedEnd [ a prov:End; prov:entity :buzzer; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ]."@en ; rdfs:isDefinedBy ; rdfs:label "End" ; "qualified" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "End is when an activity is deemed to have been ended by an entity, known as trigger. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as ender that generated the trigger."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-End"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-End"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Entity rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith ; rdfs:isDefinedBy ; rdfs:label "Entity" ; "starting-point" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. "@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-entity"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Entity"^^xsd:anyURI . ### http://www.w3.org/ns/prov#EntityInfluence rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "EntityInfluence provides additional descriptions of an Entity's binary influence upon any other kind of resource. Instances of EntityInfluence use the prov:entity property to cite the influencing Entity."@en , "It is not recommended that the type EntityInfluence be asserted without also asserting one of its more specific subclasses."@en ; rdfs:isDefinedBy ; rdfs:label "EntityInfluence" ; rdfs:seeAlso ; "qualified" ; "EntityInfluence is the capacity of an entity to have an effect on the character, development, or behavior of another by means of usage, start, end, derivation, or other. "@en . ### http://www.w3.org/ns/prov#Generation rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "An instance of prov:Generation provides additional descriptions about the binary prov:wasGeneratedBy relation from a generated prov:Entity to the prov:Activity that generated it. For example, :cake prov:wasGeneratedBy :baking; prov:qualifiedGeneration [ a prov:Generation; prov:activity :baking; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Generation" ; "qualified" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Generation"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Generation"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Influence rdf:type owl:Class ; rdfs:comment "An instance of prov:Influence provides additional descriptions about the binary prov:wasInfluencedBy relation from some influenced Activity, Entity, or Agent to the influencing Activity, Entity, or Agent. For example, :stomach_ache prov:wasInfluencedBy :spoon; prov:qualifiedInfluence [ a prov:Influence; prov:entity :spoon; :foo :bar ] . Because prov:Influence is a broad relation, the more specific relations (Communication, Delegation, End, etc.) should be used when applicable."@en , "Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication, prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable."@en ; rdfs:isDefinedBy ; rdfs:label "Influence" ; "qualified" ; "derivations" ; "Influence is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-influence"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#InstantaneousEvent rdf:type owl:Class ; rdfs:comment "An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous."@en ; rdfs:isDefinedBy ; rdfs:label "InstantaneousEvent" ; "qualified" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#dfn-event"^^xsd:anyURI ; "The PROV data model is implicitly based on a notion of instantaneous events (or just events), that mark transitions in the world. Events include generation, usage, or invalidation of entities, as well as starting or ending of activities. This notion of event is not first-class in the data model, but it is useful for explaining its other concepts and its semantics."@en . ### http://www.w3.org/ns/prov#Invalidation rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "An instance of prov:Invalidation provides additional descriptions about the binary prov:wasInvalidatedBy relation from an invalidated prov:Entity to the prov:Activity that invalidated it. For example, :uncracked_egg prov:wasInvalidatedBy :baking; prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :baking; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Invalidation" ; "qualified" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "Invalidation is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation." ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Invalidation"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Invalidation"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Location rdf:type owl:Class ; rdfs:isDefinedBy ; rdfs:label "Location" ; rdfs:seeAlso ; "expanded" ; "A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-location"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribute"^^xsd:anyURI . ### http://www.w3.org/ns/prov#Organization rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:isDefinedBy ; rdfs:label "Organization" ; "expanded" ; "agents-responsibility" ; "An organization is a social or legal institution such as a company, society, etc." ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types"^^xsd:anyURI . ### http://www.w3.org/ns/prov#Person rdf:type owl:Class ; rdfs:subClassOf , , ; rdfs:isDefinedBy ; rdfs:label "Person" ; "expanded" ; "agents-responsibility" ; "Person agents are people."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types"^^xsd:anyURI . ### http://www.w3.org/ns/prov#Plan rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "There exist no prescriptive requirement on the nature of plans, their representation, the actions or steps they consist of, or their intended goals. Since plans may evolve over time, it may become necessary to track their provenance, so plans themselves are entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to validate the execution as represented in the provenance record, to manage expectation failures, or to provide explanations."@en ; rdfs:isDefinedBy ; rdfs:label "Plan" ; "expanded" , "qualified" ; "agents-responsibility" ; "A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals." ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Association"^^xsd:anyURI . ### http://www.w3.org/ns/prov#PrimarySource rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:PrimarySource provides additional descriptions about the binary prov:hadPrimarySource relation from some secondary prov:Entity to an earlier, primary prov:Entity. For example, :blog prov:hadPrimarySource :newsArticle; prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :newsArticle; :foo :bar ] ."@en ; rdfs:isDefinedBy ; rdfs:label "PrimarySource" ; "qualified" ; "derivations" ; """A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. Because of the directness of primary sources, they 'speak for themselves' in ways that cannot be captured through the filter of secondary sources. As such, it is important for secondary sources to reference those primary sources from which they were derived, so that their reliability can be investigated. A primary source relation is a particular case of derivation of secondary materials from their primary sources. It is recognized that the determination of primary sources can be up to interpretation, and should be done according to conventions accepted within the application's domain."""@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-primary-source"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-original-source"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Quotation rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:Quotation provides additional descriptions about the binary prov:wasQuotedFrom relation from some taken prov:Entity from an earlier, larger prov:Entity. For example, :here_is_looking_at_you_kid prov:wasQuotedFrom :casablanca_script; prov:qualifiedQuotation [ a prov:Quotation; prov:entity :casablanca_script; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Quotation" ; "qualified" ; "derivations" ; "A quotation is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. Quotation is a particular case of derivation."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-quotation"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-quotation"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Revision rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "An instance of prov:Revision provides additional descriptions about the binary prov:wasRevisionOf relation from some newer prov:Entity to an earlier prov:Entity. For example, :draft_2 prov:wasRevisionOf :draft_1; prov:qualifiedRevision [ a prov:Revision; prov:entity :draft_1; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Revision" ; "qualified" ; "derivations" ; "A revision is a derivation for which the resulting entity is a revised version of some original. The implication here is that the resulting entity contains substantial content from the original. Revision is a particular case of derivation."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-revision"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Revision"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Role rdf:type owl:Class ; rdfs:isDefinedBy ; rdfs:label "Role" ; rdfs:seeAlso ; "qualified" ; "agents-responsibility" ; "A role is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-role"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribute"^^xsd:anyURI . ### http://www.w3.org/ns/prov#SoftwareAgent rdf:type owl:Class ; rdfs:subClassOf ; rdfs:isDefinedBy ; rdfs:label "SoftwareAgent" ; "expanded" ; "agents-responsibility" ; "A software agent is running software."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types"^^xsd:anyURI . ### http://www.w3.org/ns/prov#Start rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "An instance of prov:Start provides additional descriptions about the binary prov:wasStartedBy relation from some started prov:Activity to an prov:Entity that started it. For example, :foot_race prov:wasStartedBy :bang; prov:qualifiedStart [ a prov:Start; prov:entity :bang; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ] ."@en ; rdfs:isDefinedBy ; rdfs:label "Start" ; "qualified" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "Start is when an activity is deemed to have been started by an entity, known as trigger. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as starter, that generated the trigger."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Start"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Start"^^xsd:anyURI ; . ### http://www.w3.org/ns/prov#Usage rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "An instance of prov:Usage provides additional descriptions about the binary prov:used relation from some prov:Activity to an prov:Entity that it used. For example, :keynote prov:used :podium; prov:qualifiedUsage [ a prov:Usage; prov:entity :podium; :foo :bar ]."@en ; rdfs:isDefinedBy ; rdfs:label "Usage" ; "qualified" ; "entities-activities" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "Usage is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Usage"^^xsd:anyURI ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Usage"^^xsd:anyURI ; . ### http://xmlns.com/foaf/0.1/Agent rdf:type owl:Class ; rdfs:comment "An agent (eg. person, group, software or physical artifact)." ; rdfs:label "Agent" ; "stable" . ### http://xmlns.com/foaf/0.1/Document rdf:type owl:Class ; rdfs:comment "A document." ; rdfs:isDefinedBy ; rdfs:label "Document" ; "stable" . ### http://xmlns.com/foaf/0.1/Organization rdf:type owl:Class . ### http://xmlns.com/foaf/0.1/Person rdf:type owl:Class . ### https://schema.org/AdministrativeArea rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A geographical region, typically under the jurisdiction of a particular government."@en ; rdfs:isDefinedBy ; rdfs:label "AdministrativeArea"@en . ### https://schema.org/Class rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A class, also often called a 'Type'; equivalent to rdfs:Class."@en ; rdfs:isDefinedBy ; rdfs:label "Class"@en . ### https://schema.org/Country rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:comment "A country."@en ; rdfs:isDefinedBy ; rdfs:label "Country"@en . ### https://schema.org/CreativeWork rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "The most generic kind of creative work, including books, movies, photographs, software programs, etc."@en ; rdfs:isDefinedBy ; rdfs:label "CreativeWork"@en . ### https://schema.org/DataType rdf:type owl:Class ; rdfs:subClassOf rdfs:Class ; rdfs:comment "The basic data types such as Integers, Strings, etc."@en ; rdfs:isDefinedBy ; rdfs:label "DataType"@en . ### https://schema.org/Enumeration rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Lists or enumerations—for example, a list of cuisines or music genres, etc."@en ; rdfs:isDefinedBy ; rdfs:label "Enumeration"@en . ### https://schema.org/Intangible rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A utility class that serves as the umbrella for a number of 'intangible' things such as quantities, structured values, etc."@en ; rdfs:isDefinedBy ; rdfs:label "Intangible"@en . ### https://schema.org/MediaObject rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A media object, such as an image, video, audio, or text object embedded in a web page or a downloadable dataset i.e. DataDownload. Note that a creative work may have many media objects associated with it on the same web page. For example, a page about a single song (MusicRecording) may have a music video (VideoObject), and a high and low bandwidth audio stream (2 AudioObject's)."@en ; rdfs:isDefinedBy ; rdfs:label "MediaObject"@en . ### https://schema.org/Person rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A person (alive, dead, undead, or fictional)."@en ; rdfs:isDefinedBy ; rdfs:label "Person"@en . ### https://schema.org/Place rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Entities that have a somewhat fixed, physical extension."@en ; rdfs:isDefinedBy ; rdfs:label "Place"@en . ### https://schema.org/Property rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A property, used to indicate attributes and relationships of some Thing; equivalent to rdf:Property."@en ; rdfs:isDefinedBy ; rdfs:label "Property"@en . ### https://schema.org/Role rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Represents additional information about a relationship or property. For example a Role can be used to say that a 'member' role linking some SportsTeam to a player occurred during a particular time period. Or that a Person's 'actor' role in a Movie was for some particular characterName. Such properties can be attached to a Role entity, which is then associated with the main entities using ordinary properties like 'member' or 'actor'.

See also blog post."""@en ; rdfs:isDefinedBy ; rdfs:label "Role"@en . ### https://schema.org/Specialty rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Any branch of a field in which people typically develop specific expertise, usually after significant study, time, and effort."@en ; rdfs:isDefinedBy ; rdfs:label "Specialty"@en . ### https://schema.org/Text rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Data type: Text."@en ; rdfs:isDefinedBy ; rdfs:label "Text"@en . ### https://schema.org/TextObject rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A text file. The text can be unformatted or contain markup, html, etc."@en ; rdfs:isDefinedBy ; rdfs:label "TextObject"@en . ### https://schema.org/Thing rdf:type owl:Class ; rdfs:comment "The most generic type of item."@en ; rdfs:isDefinedBy ; rdfs:label "Thing"@en . ### https://schema.org/URL rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Data type: URL."@en ; rdfs:isDefinedBy ; rdfs:label "URL"@en . ### https://schema.org/WebPage rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A web page. Every web page is implicitly assumed to be declared to be of type WebPage, so the various properties about that webpage, such as breadcrumb may be used. We recommend explicit declaration if these properties are specified, but if they are found outside of an itemscope, they will be assumed to be about the page."@en ; rdfs:isDefinedBy ; rdfs:label "WebPage"@en . ### https://www.omg.org/spec/Commons/GeopoliticalEntities/GeopoliticalEntity rdf:type owl:Class . ################################################################# # Individuals ################################################################# ### http://creativecommons.org/ns#Attribution rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Attribution"@en ; "Credit be given to copyright holder and/or author."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#CommercialUse rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Commercial Use"@en ; "Exercising rights for commercial purposes."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#DerivativeWorks rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Derivative Works"@en ; "Distribution of derivative works."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#Distribution rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Distribution"@en ; "Distribution, public display, and publicly performance."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#Notice rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Notice"@en ; "Copyright and license notices be kept intact."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#Reproduction rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Reproduction"@en ; "Making multiple copies."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#ShareAlike rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Share Alike"@en ; "Derivative works be licensed under the same terms or compatible terms as the original work."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#Sharing rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Sharing"@en ; "Permits commercial derivatives, but only non-commercial distribution."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://creativecommons.org/ns#SourceCode rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Source Code"@en ; "Source code (the preferred form for making modifications) must be provided when exercising some rights granted by the license."@en ; "This term is defined by Creative Commons."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/prov-o rdf:type owl:NamedIndividual . ### http://www.w3.org/ns/prov-o-20130312 rdf:type owl:NamedIndividual . ### http://www.w3.org/ns/odrl/2/Action rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Agreement rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/All rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "All"@en ; owl:deprecated "true"^^xsd:boolean ; "Specifies that the scope of the relationship is all of the collective individuals within a context."@en ; "For example, may be used to indicate all the users of a specific social network the party is a member of. Note that “group” scope is also assumed."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/All2ndConnections rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "All Second-level Connections"@en ; owl:deprecated "true"^^xsd:boolean ; "Specifies that the scope of the relationship is all of the second-level connections to the Party."@en ; "For example, may be used to indicate all “friends of friends” of the Party. Note that “group” scope is also assumed."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/AllConnections rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "All First-Level Connections"@en ; owl:deprecated "true"^^xsd:boolean ; "Specifies that the scope of the relationship is all of the first-level connections of the Party."@en ; "For example, may be used to indicate all “friends” of the Party. Note that “group” scope is also assumed."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/AllGroups rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "All Group Connections"@en ; owl:deprecated "true"^^xsd:boolean ; "Specifies that the scope of the relationship is all of the group connections of the Party."@en ; "For example, may be used to indicate all groups that the Party is a member of. Note that “group” scope is also assumed."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/Assertion rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Asset rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/AssetCollection rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/AssetScope rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Asset Scope"@en ; owl:deprecated "true"^^xsd:boolean ; "Scopes for Asset Scope expressions."@en ; "Instances of the AssetScope class represent the terms for the scope property of Assets."@en . ### http://www.w3.org/ns/odrl/2/ConflictTerm rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Constraint rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Duty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Group rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Group"@en ; owl:deprecated "true"^^xsd:boolean ; "Specifies that the scope of the relationship is the defined group with multiple individual members."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/Individual rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Individual"@en ; owl:deprecated "true"^^xsd:boolean ; "Specifies that the scope of the relationship is the single Party individual."@en . ### http://www.w3.org/ns/odrl/2/LeftOperand rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/LogicalConstraint rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Offer rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Operator rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Party rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/PartyCollection rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/PartyScope rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Permission rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Policy rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Privacy rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Prohibition rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Request rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/RightOperand rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Rule rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Set rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/Ticket rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/UndefinedTerm rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/absolutePosition rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Absolute Asset Position"@en ; "A point in space or time defined with absolute coordinates for the positioning of the target Asset."@en ; "Example: The upper left corner of a picture may be constrained to a specific position of the canvas rendering it."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/absoluteSize rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Absolute Asset Size"@en ; "Measure(s) of one or two axes for 2D-objects or measure(s) of one to tree axes for 3D-objects of the target Asset."@en ; "Example: The image can be resized in width to a maximum of 1000px."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/absoluteSpatialPosition rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Absolute Spatial Asset Position"@en ; ; "The absolute spatial positions of four corners of a rectangle on a 2D-canvas or the eight corners of a cuboid in a 3D-space for the target Asset to fit."@en ; "Example: The upper left corner of a picture may be constrained to a specific position of the canvas rendering it. Note: see also the Left Operand Relative Spatial Asset Position. "@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/absoluteTemporalPosition rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Absolute Temporal Asset Position"@en ; ; "The absolute temporal positions in a media stream the target Asset has to fit."@en ; "Use with Actions including the target Asset in a larger media stream. The fragment part of a Media Fragment URI (https://www.w3.org/TR/media-frags/) may be used for the right operand. See the Left Operand realativeTemporalPosition.
Example: The MP3 music file must be positioned between second 192 and 250 of the temporal length of a stream."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/acceptTracking rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Accept Tracking"@en ; "To accept that the use of the Asset may be tracked."@en ; "The collected information may be tracked by the Assigner, or may link to a Party with the role 'trackingParty' function."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/action rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/adHocShare rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Ad-hoc sharing"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of sharing the asset to parties in close proximity to the owner."@en ; "This original term and URI from the OMA specification should be used: http://www.openmobilealliance.com/oma-dd/adhoc-share ."@en . ### http://www.w3.org/ns/odrl/2/aggregate rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Aggregate"@en ; "To use the Asset or parts of it as part of a composite collection."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/and rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/andSequence rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/annotate rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Annotate"@en ; "To add explanatory notations/commentaries to the Asset without modifying the Asset in any other way."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/anonymize rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Anonymize"@en ; "To anonymize all or parts of the Asset."@en ; "For example, to remove identifying particulars for statistical or for other comparable purposes, or to use the Asset without stating the author/source."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/append rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Append"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of adding to the end of an asset."@en ; . ### http://www.w3.org/ns/odrl/2/appendTo rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Append To"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of appending data to the Asset without modifying the Asset in any other way."@en ; . ### http://www.w3.org/ns/odrl/2/archive rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Archive"@en ; "To store the Asset (in a non-transient form)."@en ; "Temporal constraints may be used for temporal conditions."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/assignee rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/assigneeOf rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/assigner rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/assignerOf rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/attachPolicy rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Attach policy"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of keeping the policy notice with the asset."@en ; . ### http://www.w3.org/ns/odrl/2/attachSource rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Attach source"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of attaching the source of the asset and its derivatives."@en ; . ### http://www.w3.org/ns/odrl/2/attribute rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Attribute"@en ; "To attribute the use of the Asset."@en ; "May link to an Asset with the attribution information. May link to a Party with the role “attributedParty” function."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/attributedParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/attributingParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/commercialize rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Commercialize"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of using the asset in a business environment."@en ; . ### http://www.w3.org/ns/odrl/2/compensate rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Compensate"@en ; "To compensate by transfer of some amount of value, if defined, for using or selling the Asset."@en ; "The compensation may use different types of things with a value: (i) the thing is expressed by the value (term) of the Constraint name; (b) the value is expressed by operator, rightOperand, dataType and unit. Typically the assignee will compensate the assigner, but other compensation party roles may be used."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/compensatedParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/compensatingParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/concurrentUse rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Concurrent Use"@en ; "To create multiple copies of the Asset that are being concurrently used."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/conflict rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/consentedParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/consentingParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/consequence rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/constraint rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/contractedParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/contractingParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/copy rdf:type owl:NamedIndividual , , ; owl:sameAs ; rdfs:isDefinedBy ; rdfs:label "Copy"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of making an exact reproduction of the asset."@en ; . ### http://www.w3.org/ns/odrl/2/reproduce ### http://www.w3.org/ns/odrl/2/core rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "ODRL Core Profile"@en ; "Identifier for the ODRL Core Profile"@en . ### http://www.w3.org/ns/odrl/2/count rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Count"@en ; "Numeric count of executions of the action of the Rule."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/dataType rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/dateTime rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Datetime"@en ; "The date (and optional time and timezone) of exercising the action of the Rule. Right operand value MUST be an xsd:date or xsd:dateTime as defined by [[xmlschema11-2]]."@en ; "The use of Timezone information is strongly recommended. The Rule may be exercised before (with operator lt/lteq) or after (with operator gt/gteq) the date(time) defined by the Right operand.
Example: dateTime gteq 2017-12-31T06:00Z means the Rule can only be exercised after (and including) 6:00AM on the 31st Decemeber 2017 UTC time."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/delayPeriod rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Delay Period"@en ; "A time delay period prior to exercising the action of the Rule. The point in time triggering this period MAY be defined by another temporal Constraint combined by a Logical Constraint (utilising the odrl:andSequence operand). Right operand value MUST be an xsd:duration as defined by [[xmlschema11-2]]."@en ; "Only the eq, gt, gteq operators SHOULD be used.
Example: delayPeriod eq P60M indicates a delay of 60 Minutes before exercising the action."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/delete rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Delete"@en ; "To permanently remove all copies of the Asset after it has been used."@en ; "Use a constraint to define under which conditions the Asset must be deleted."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/deliveryChannel rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Delivery Channel"@en ; "The delivery channel used for exercising the action of the Rule."@en ; "Example: the asset may be distributed only on mobile networks."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/derive rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Derive"@en ; "To create a new derivative Asset from this Asset and to edit or modify the derivative."@en ; "A new asset is created and may have significant overlaps with the original Asset. (Note that the notion of whether or not the change is significant enough to qualify as a new asset is subjective). To the derived Asset a next policy may be applied."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/device rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Device"@en ; owl:deprecated "true"^^xsd:boolean ; "An identified device used for exercising the action of the Rule."@en ; ; "See System Device." . ### http://www.w3.org/ns/odrl/2/digitize rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Digitize"@en ; "To produce a digital copy of (or otherwise digitize) the Asset from its analogue form."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/display rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Display"@en ; "To create a static and transient rendition of an Asset."@en ; "For example, displaying an image on a screen. If the action is to be performed to a wider audience than just the Assignees, then the Recipient constraint is recommended to be used."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/distribute rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Distribute"@en ; "To supply the Asset to third-parties."@en ; "It is recommended to use nextPolicy to express the allowable usages by third-parties."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/duty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/elapsedTime rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Elapsed Time"@en ; "A continuous elapsed time period which may be used for exercising of the action of the Rule. Right operand value MUST be an xsd:duration as defined by [[xmlschema11-2]]."@en ; "Only the eq, lt, lteq operators SHOULD be used. See also Metered Time.
Example: elpasedTime eq P60M indicates a total elapsed time of 60 Minutes." ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/ensureExclusivity rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Ensure Exclusivity"@en ; "To ensure that the Rule on the Asset is exclusive."@en ; "If used as a Duty, the assignee should be explicitly indicated as the party that is ensuring the exclusivity of the Rule."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/eq rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Equal to"@en ; "Indicating that a given value equals the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/event rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Event"@en ; "An identified event setting a context for exercising the action of the Rule."@en ; "Events are temporal periods of time, and operators can be used to signal before (lt), during (eq) or after (gt) the event.
Example: May be taken during the “FIFA World Cup 2020” only."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/execute rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Execute"@en ; "To run the computer program Asset."@en ; "For example, machine executable code or Java such as a game or application."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/export rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Export"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of transforming the asset into a new form."@en ; . ### http://www.w3.org/ns/odrl/2/extract rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Extract"@en ; "To extract parts of the Asset and to use it as a new Asset."@en ; "A new asset is created and may have very little in common with the original Asset. (Note that the notion of whether or not the change is significant enough to qualify as a new asset is subjective). To the extracted Asset a next policy may be applied."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/extractChar rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Extract character"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of extracting (replicating) unchanged characters from the asset."@en ; "This original term and URI from the ONIX specification should be used: http://www.editeur.org/onix-pl/extract-char ."@en . ### http://www.w3.org/ns/odrl/2/extractPage rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Extract page"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of extracting (replicating) unchanged pages from the asset."@en ; "This original term and URI from the ONIX specification should be used: http://www.editeur.org/onix-pl/extract-page ."@en . ### http://www.w3.org/ns/odrl/2/extractWord rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Extract word"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of extracting (replicating) unchanged words from the asset."@en ; "This original term and URI from the ONIX specification should be used: http://www.editeur.org/onix-pl/extract-word ."@en . ### http://www.w3.org/ns/odrl/2/failure rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/fileFormat rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "File Format"@en ; "A transformed file format of the target Asset."@en ; "Example: An asset may be transformed into JPEG format."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/function rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/give rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Give"@en ; "To transfer the ownership of the Asset to a third party without compensation and while deleting the original asset."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/grantUse rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Grant Use"@en ; "To grant the use of the Asset to third parties."@en ; "This action enables the assignee to create policies for the use of the Asset for third parties. The nextPolicy is recommended to be agreed with the third party. Use of temporal constraints is recommended."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/gt rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Greater than"@en ; "Indicating that a given value is greater than the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/gteq rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Greater than or equal to"@en ; "Indicating that a given value is greater than or equal to the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/hasPart rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Has part"@en ; "A set-based operator indicating that a given value contains the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/hasPolicy rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/ignore rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Ignore Undefined Actions"@en ; owl:deprecated "true"^^xsd:boolean ; "The Action is to be ignored and is not part of the policy – and the policy remains valid."@en ; "Used to support actions not known to the policy system."@en . ### http://www.w3.org/ns/odrl/2/implies rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/include rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Include"@en ; "To include other related assets in the Asset."@en ; "For example: bio picture must be included in the attribution. Use of a relation sub-property is required for the related assets."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/includedIn rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/index rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Index"@en ; "To record the Asset in an index."@en ; "For example, to include a link to the Asset in a search engine database."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/industry rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Industry Context"@en ; "A defined industry sector setting a context for exercising the action of the Rule."@en ; "Example: publishing or financial industry."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/inform rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Inform"@en ; "To inform that an action has been performed on or in relation to the Asset."@en ; "May link to a Party with the role 'informedParty' function."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/informedParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/informingParty rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Informing Party"@en ; "The Party who provides the inform use data."@en ; "Maybe specified as part of the inform action."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/inheritAllowed rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Inheritance Allowed"@en ; owl:deprecated "true"^^xsd:boolean ; "Indicates if the Policy entity can be inherited."@en ; "A boolean value."@en . ### http://www.w3.org/ns/odrl/2/inheritFrom rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/inheritRelation rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Inherit Relation"@en ; owl:deprecated "true"^^xsd:boolean ; "Indentifies the type of inheritance."@en ; "For example, this may indicate the business scenario, such as subscription, or prior arrangements between the parties (that are not machine representable)."@en . ### http://www.w3.org/ns/odrl/2/install rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Install"@en ; "To load the computer program Asset onto a storage device which allows operating or running the Asset."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/invalid rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Void Policy"@en ; "The policy is void."@en ; "Used to indicate the policy is void for Conflict Strategy."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/isA rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Is a"@en ; "A set-based operator indicating that a given value is an instance of the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/isAllOf rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Is all of"@en ; "A set-based operator indicating that a given value is all of the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/isAnyOf rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Is any of"@en ; "A set-based operator indicating that a given value is any of the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/isNoneOf rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Is none of"@en ; "A set-based operator indicating that a given value is none of the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/isPartOf rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Is part of"@en ; "A set-based operator indicating that a given value is contained by the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/language rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Language"@en ; "A natural language used by the target Asset."@en ; "Example: the asset can only be translated into Greek. Must use [[bcp47]] codes for language values."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/lease rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Lease"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of making available the asset to a third-party for a fixed period of time with exchange of value."@en . ### http://www.w3.org/ns/odrl/2/leftOperand rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/lend rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Lend"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of making available the asset to a third-party for a fixed period of time without exchange of value."@en . ### http://www.w3.org/ns/odrl/2/license rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "License"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of granting the right to use the asset to a third-party."@en ; . ### http://www.w3.org/ns/odrl/2/lt rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Less than"@en ; "Indicating that a given value is less than the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/lteq rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Less than or equal to"@en ; "Indicating that a given value is less than or equal to the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/media rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Media Context"@en ; "Category of a media asset setting a context for exercising the action of the Rule."@en ; "Example media types: electronic, print, advertising, marketing. Note: The used type should not be an IANA MediaType as they are focused on technical characteristics. "@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/meteredTime rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Metered Time"@en ; "An accumulated amount of one to many metered time periods which were used for exercising the action of the Rule. Right operand value MUST be an xsd:duration as defined by [[xmlschema11-2]]."@en ; "Only the eq, lt, lteq operators SHOULD be used. See also Elapsed Time.
Example: meteredTime lteq P60M indicates an accumulated period of 60 Minutes or less." ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/modify rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Modify"@en ; "To change existing content of the Asset. A new asset is not created by this action."@en ; "This action will modify an asset which is typically updated from time to time without creating a new asset. If the result from modifying the asset should be a new asset the actions derive or extract should be used. (Note that the notion of whether or not the change is significant enough to qualify as a new asset is subjective)."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/move rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Move"@en ; "To move the Asset from one digital location to another including deleting the original copy."@en ; "After the Asset has been moved, the original copy must be deleted."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/neq rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Not equal to"@en ; "Indicating that a given value is not equal to the right operand of the Constraint."@en . ### http://www.w3.org/ns/odrl/2/nextPolicy rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Next Policy"@en ; "To grant the specified Policy to a third party for their use of the Asset."@en ; "Useful for downstream policies."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/obligation rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/obtainConsent rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Obtain Consent"@en ; "To obtain verifiable consent to perform the requested action in relation to the Asset."@en ; "May be used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role “consentingParty” function."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/operand rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/operator rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/or rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/output rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/partOf rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/pay rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Pay"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of paying a financial amount to a party for use of the asset."@en ; . ### http://www.w3.org/ns/odrl/2/payAmount rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Payment Amount"@en ; "The amount of a financial payment. Right operand value MUST be an xsd:decimal. "@en ; "Can be used for compensation duties with the unit property indicating the currency of the payment."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/payeeParty rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Payee Party"@en ; owl:deprecated "true"^^xsd:boolean ; "The Party is the recipient of the payment."@en ; ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/percentage rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Asset Percentage"@en ; "A percentage amount of the target Asset relevant for exercising the action of the Rule. Right operand value MUST be an xsd:decimal from 0 to 100."@en ; "Example: Extract less than or equal to 50%."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/perm rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Prefer Permissions"@en ; "Permissions take preference over prohibitions."@en ; "Used to determine policy conflict outcomes."@en . ### http://www.w3.org/ns/odrl/2/permission rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/play rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Play"@en ; "To create a sequential and transient rendition of an Asset."@en ; "For example, to play a video or audio track. If the action is to be performed to a wider audience than just the Assignees, then the Recipient constraint is recommended to be used." ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/policyUsage rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Policy Rule Usage"@en ; "Indicates the actual datetime the action of the Rule was exercised."@en ; "This can be used to express constraints with a LeftOperand relative to the time the rule is exercised. Operators indicate before (lt, lteq), during (eq) or after (gt, gteq) the usage of the rule.
Example: event lt policyUsage expresses that the identified event must have happened before the action of the rule is exercised."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/present rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Present"@en ; "To publicly perform the Asset."@en ; "The asset can be performed (or communicated) in public." ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/preview rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Preview"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of providing a short preview of the asset."@en ; "Use a time constraint with the appropriate action."@en . ### http://www.w3.org/ns/odrl/2/print rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Print"@en ; "To create a tangible and permanent rendition of an Asset."@en ; "For example, creating a permanent, fixed (static), and directly perceivable representation of the Asset, such as printing onto paper."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/product rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Product Context"@en ; "Category of product or service setting a context for exercising the action of the Rule."@en ; "Example: May only be used in the XYZ Magazine."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/profile rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Profile"@en ; "The identifier(s) of an ODRL Profile that the Policy conforms to."@en ; "The profile property is mandatory if the Policy is using an ODRL Profile."@en . ### http://www.w3.org/ns/odrl/2/prohibit rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Prefer Prohibitions"@en ; "Prohibitions take preference over permissions."@en ; "Used to determine policy conflict outcomes."@en . ### http://www.w3.org/ns/odrl/2/prohibition rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/proximity rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "proximity"@en ; owl:deprecated "true"^^xsd:boolean ; "An value indicating the closeness or nearness."@en ; "This original term and URI from the OMA specification should be used: http://www.openmobilealliance.com/oma-dd/proximity ."@en . ### http://www.w3.org/ns/odrl/2/purpose rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Purpose"@en ; "A defined purpose for exercising the action of the Rule."@en ; "Example: Educational use."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/read rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Read"@en ; "To obtain data from the Asset."@en ; "For example, the ability to read a record from a database (the Asset)."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/recipient rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Recipient"@en ; "The party receiving the result/outcome of exercising the action of the Rule."@en ; "The Right Operand must identify one or more specific Parties or category/ies of the Party."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/refinement rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/relation rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/relativePosition rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Relative Asset Position"@en ; "A point in space or time defined with coordinates relative to full measures the positioning of the target Asset."@en ; "Example: The upper left corner of a picture may be constrained to a specific position of the canvas rendering it."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/relativeSize rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Relative Asset Size"@en ; "Measure(s) of one or two axes for 2D-objects or measure(s) of one to tree axes for 3D-objects - expressed as percentages of full values - of the target Asset."@en ; "Example: The image can be resized in width to a maximum of 200%. Note: See the Left Operand absoluteSize. "@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/relativeSpatialPosition rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Relative Spatial Asset Position"@en ; ; "The relative spatial positions - expressed as percentages of full values - of four corners of a rectangle on a 2D-canvas or the eight corners of a cuboid in a 3D-space of the target Asset."@en ; "See also Absolute Spatial Asset Position."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/relativeTemporalPosition rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Relative Temporal Asset Position"@en ; ; "A point in space or time defined with coordinates relative to full measures the positioning of the target Asset."@en ; "See also Absolute Temporal Asset Position.
Example: The MP3 music file must be positioned between the positions at 33% and 48% of the temporal length of a stream. "@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/remedy rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/reproduce rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Reproduce"@en ; "To make duplicate copies the Asset in any material form."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/resolution rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Rendition Resolution"@en ; "Resolution of the rendition of the target Asset."@en ; "Example: the image may be printed at 1200dpi."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/reviewPolicy rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Review Policy"@en ; "To review the Policy applicable to the Asset."@en ; "Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/rightOperand rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/rightOperandReference rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Has Right Operand Reference"@en ; "A reference to a web resource providing the value for the right operand of a Constraint."@en ; "An IRI that MUST be dereferenced to obtain the actual right operand value. When used with set-based operators, a list of IRIs may be used"@en . ### http://www.w3.org/ns/odrl/2/scope rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Scope"@en ; owl:deprecated "true"^^xsd:boolean ; "The identifier of a scope that provides context to the extent of the entity."@en ; "Used to define scopes for Assets and Parties."@en . ### http://www.w3.org/ns/odrl/2/secondaryUse rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Secondary Use"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of using the asset for a purpose other than the purpose it was intended for."@en . ### http://www.w3.org/ns/odrl/2/sell rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Sell"@en ; "To transfer the ownership of the Asset to a third party with compensation and while deleting the original asset."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/share rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Share"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of the non-commercial reproduction and distribution of the asset to third-parties."@en ; . ### http://www.w3.org/ns/odrl/2/shareAlike rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Share-alike"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of distributing any derivative asset under the same terms as the original asset."@en ; . ### http://www.w3.org/ns/odrl/2/source rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Source"@en ; "Reference to a Asset/PartyCollection"@en ; "Used by AssetCollection and PartyCollection when constraints are applied."@en . ### http://www.w3.org/ns/odrl/2/spatial rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Geospatial Named Area"@en ; "A named and identified geospatial area with defined borders which is used for exercising the action of the Rule. An IRI MUST be used to represent this value."@en ; "A code value for the area and source of the code must be presented in the Right Operand.
Example: the [[iso3166]] Country Codes or the Getty Thesaurus of Geographic Names. "@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/spatialCoordinates rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Geospatial Coordinates"@en ; ; "A set of coordinates setting the borders of a geospatial area used for exercising the action of the Rule. The coordinates MUST include longitude and latitude, they MAY include altitude and the geodetic datum."@en ; "The default values are the altitude of earth's surface at this location and the WGS 84 datum."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/status rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Status"@en ; "the value generated from the leftOperand action or a value related to the leftOperand set as the reference for the comparison."@en . ### http://www.w3.org/ns/odrl/2/stream rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Stream"@en ; "To deliver the Asset in real-time."@en ; "The Asset maybe utilised in real-time as it is being delivered. If the action is to be performed to a wider audience than just the Assignees, then the Recipient constraint is recommended to be used." ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/support rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Support Undefined Actions"@en ; owl:deprecated "true"^^xsd:boolean ; "The Action is to be supported as part of the policy – and the policy remains valid."@en ; "Used to support actions not known to the policy system."@en . ### http://www.w3.org/ns/odrl/2/synchronize rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Synchronize"@en ; "To use the Asset in timed relations with media (audio/visual) elements of another Asset."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/system rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "System"@en ; owl:deprecated "true"^^xsd:boolean ; "An identified computing system used for exercising the action of the Rule."@en ; ; "See System Device" . ### http://www.w3.org/ns/odrl/2/systemDevice rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "System Device"@en ; "An identified computing system or computing device used for exercising the action of the Rule."@en ; , ; "Example: The system device can be identified by a unique code created from the used hardware."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/target rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/textToSpeech rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Text-to-speech"@en ; "To have a text Asset read out loud."@en ; "If the action is to be performed to a wider audience than just the Assignees, then the recipient constraint is recommended to be used." ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/timeInterval rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Recurring Time Interval"@en ; "A recurring period of time before the next execution of the action of the Rule. Right operand value MUST be an xsd:duration as defined by [[xmlschema11-2]]."@en ; "Only the eq operator SHOULD be used.
Example: timeInterval eq P7D indicates a recurring 7 day period." ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/timedCount rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Timed Count"@en ; owl:deprecated "true"^^xsd:boolean ; "The number of seconds after which timed metering use of the asset begins."@en ; "This original term and URI from the OMA specification should be used: http://www.openmobilealliance.com/oma-dd/timed-count ."@en . ### http://www.w3.org/ns/odrl/2/trackedParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/trackingParty rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/transfer rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Transfer Ownership"@en ; "To transfer the ownership of the Asset in perpetuity."@en . ### http://www.w3.org/ns/odrl/2/transform rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Transform"@en ; "To convert the Asset into a different format."@en ; "Typically used to convert the Asset into a different format for consumption on/transfer to a third party system."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/translate rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Translate"@en ; "To translate the original natural language of an Asset into another natural language."@en ; "A new derivative Asset is created by that action."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/uid rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Unique Identifier"@en ; "An unambiguous identifier"@en ; "Used by the Policy, Rule, Asset, Party, Constraint, and Logical Constraint Classes."@en . ### http://www.w3.org/ns/odrl/2/undefined rdf:type owl:NamedIndividual , ; rdfs:isDefinedBy ; rdfs:label "Handle Undefined Term"@en ; owl:deprecated "true"^^xsd:boolean ; "Relates the strategy used for handling undefined actions to a Policy."@en ; "If no strategy is specified, the default is invalid."@en . ### http://www.w3.org/ns/odrl/2/uninstall rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Uninstall"@en ; "To unload and delete the computer program Asset from a storage device and disable its readiness for operation."@en ; "The Asset is no longer accessible to the assignees after it has been used."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/unitOfCount rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Unit Of Count"@en ; "The unit of measure used for counting the executions of the action of the Rule."@en ; "Note: Typically used with Duties to indicate the unit entity to be counted of the Action.
Example: A duty to compensate and a unitOfCount constraint of 'perUser' would indicate that the compensation by multiplied by the 'number of users'."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/use rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Use"@en ; "To use the Asset"@en ; "Use is the most generic action for all non-third-party usage. More specific types of the use action can be expressed by more targetted actions."@en . ### http://www.w3.org/ns/odrl/2/version rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Version"@en ; "The version of the target Asset."@en ; "Example: Single Paperback or Multiple Issues or version 2.0 or higher."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/virtualLocation rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Virtual IT Communication Location"@en ; "An identified location of the IT communication space which is relevant for exercising the action of the Rule."@en ; "Example: an Internet domain or IP address range."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/watermark rdf:type owl:NamedIndividual , , ; ; rdfs:isDefinedBy ; rdfs:label "Watermark"@en ; "To apply a watermark to the Asset."@en ; "Non-Normative"@en . ### http://www.w3.org/ns/odrl/2/write rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Write"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of writing to the Asset."@en ; . ### http://www.w3.org/ns/odrl/2/writeTo rdf:type owl:NamedIndividual , , ; rdfs:isDefinedBy ; rdfs:label "Write to"@en ; owl:deprecated "true"^^xsd:boolean ; "The act of adding data to the Asset."@en ; . ### http://www.w3.org/ns/odrl/2/xone rdf:type owl:NamedIndividual , . ### http://www.w3.org/ns/odrl/2/#actionConcepts rdf:type owl:NamedIndividual , ; , , , ; "Action"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#actions rdf:type owl:NamedIndividual , ; , ; "Actions for Rules"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#actionsCommon rdf:type owl:NamedIndividual , ; , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ; "Actions for Rules"@en ; "ODRL Common Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#assetConcepts rdf:type owl:NamedIndividual , ; , ; "Asset"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#assetParty rdf:type owl:NamedIndividual , ; , ; "Asset and Party"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#assetRelations rdf:type owl:NamedIndividual , ; , ; "Asset Relations"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#assetRelationsCommon rdf:type owl:NamedIndividual , ; ; "Asset Relations"@en ; "ODRL Common Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#conflictConcepts rdf:type owl:NamedIndividual , ; , , , , ; "Policy Conflict Strategy"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#constraintLeftOperandCommon rdf:type owl:NamedIndividual , ; , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ; "Constraint Left Operands"@en ; "ODRL Common Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#constraintLogicalOperands rdf:type owl:NamedIndividual , ; , , , ; "Logical Constraint Operands"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#constraintRelationalOperators rdf:type owl:NamedIndividual , ; , , , , , , , , , , , ; "Constraint Operators"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#constraintRightOpCommon rdf:type owl:NamedIndividual , ; ; "Constraint Right Operands"@en ; "ODRL Common Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#constraints rdf:type owl:NamedIndividual , ; , , , , , , , , , , , , ; "Constraint"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#deprecatedTerms rdf:type owl:NamedIndividual , ; , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ; "Deprecated Terms"@en . ### http://www.w3.org/ns/odrl/2/#duties rdf:type owl:NamedIndividual , ; , , , , ; "Duty"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#logicalConstraints rdf:type owl:NamedIndividual , ; , ; "Logical Constraint"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#partyConcepts rdf:type owl:NamedIndividual , ; , ; "Party"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#partyRoles rdf:type owl:NamedIndividual , ; , , , ; "Party Functions"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#partyRolesCommon rdf:type owl:NamedIndividual , ; , , , , , , , , , , , ; "Party Functions"@en ; "ODRL Common Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#permissions rdf:type owl:NamedIndividual , ; , ; "Permission"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#policyConcepts rdf:type owl:NamedIndividual , ; , , , ; "Policy"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#policySubClasses rdf:type owl:NamedIndividual , ; , , ; "Policy Subclasses"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#policySubClassesCommon rdf:type owl:NamedIndividual , ; , , , ; "Policy Subclasses"@en ; "ODRL Common Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#prohibitions rdf:type owl:NamedIndividual , ; , ; "Prohibition"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/odrl/2/#ruleConcepts rdf:type owl:NamedIndividual , ; , , , ; "Rule"@en ; "ODRL Core Vocabulary Terms"@en . ### http://www.w3.org/ns/prov#EmptyCollection rdf:type owl:NamedIndividual . ### http://www.w3.org/ns/prov-o# rdf:type owl:NamedIndividual ; ; . ### https://schema.org/actionApplication rdf:type owl:NamedIndividual ; rdfs:comment "An application that can complete the request."@en ; rdfs:isDefinedBy ; rdfs:label "actionApplication"@en . ### https://schema.org/actionOption rdf:type owl:NamedIndividual ; rdfs:comment "A sub property of object. The options subject to this action."@en ; rdfs:isDefinedBy ; rdfs:label "actionOption"@en . ### https://schema.org/actor rdf:type owl:NamedIndividual ; rdfs:comment "An actor (individual or a group), e.g. in TV, radio, movie, video games etc., or in an event. Actors can be associated with individual items or with a series, episode, clip."@en ; rdfs:isDefinedBy ; rdfs:label "actor"@en . ### https://schema.org/actors rdf:type owl:NamedIndividual ; ; rdfs:comment "An actor, e.g. in TV, radio, movie, video games etc. Actors can be associated with individual items or with a series, episode, clip."@en ; rdfs:isDefinedBy ; rdfs:label "actors"@en . ### https://schema.org/album rdf:type owl:NamedIndividual ; rdfs:comment "A music album."@en ; rdfs:isDefinedBy ; rdfs:label "album"@en . ### https://schema.org/albums rdf:type owl:NamedIndividual ; ; rdfs:comment "A collection of music albums."@en ; rdfs:isDefinedBy ; rdfs:label "albums"@en . ### https://schema.org/application rdf:type owl:NamedIndividual ; ; rdfs:comment "An application that can complete the request."@en ; rdfs:isDefinedBy ; rdfs:label "application"@en . ### https://schema.org/area rdf:type owl:NamedIndividual ; ; rdfs:comment "The area within which users can expect to reach the broadcast service."@en ; rdfs:isDefinedBy ; rdfs:label "area"@en . ### https://schema.org/areaServed rdf:type owl:NamedIndividual ; rdfs:comment "The geographic area where a service or offered item is provided."@en ; rdfs:isDefinedBy ; rdfs:label "areaServed"@en . ### https://schema.org/arterialBranch rdf:type owl:NamedIndividual ; rdfs:comment "The branches that comprise the arterial structure."@en ; rdfs:isDefinedBy ; rdfs:label "arterialBranch"@en . ### https://schema.org/artworkSurface rdf:type owl:NamedIndividual ; rdfs:comment "The supporting materials for the artwork, e.g. Canvas, Paper, Wood, Board, etc."@en ; rdfs:isDefinedBy ; rdfs:label "artworkSurface"@en . ### https://schema.org/aspect rdf:type owl:NamedIndividual ; ; rdfs:comment "An aspect of medical practice that is considered on the page, such as 'diagnosis', 'treatment', 'causes', 'prognosis', 'etiology', 'epidemiology', etc."@en ; rdfs:isDefinedBy ; rdfs:label "aspect"@en . ### https://schema.org/assembly rdf:type owl:NamedIndividual ; ; rdfs:comment "Library file name, e.g., mscorlib.dll, system.web.dll."@en ; rdfs:isDefinedBy ; rdfs:label "assembly"@en . ### https://schema.org/attendee rdf:type owl:NamedIndividual ; rdfs:comment "A person or organization attending the event."@en ; rdfs:isDefinedBy ; rdfs:label "attendee"@en . ### https://schema.org/attendees rdf:type owl:NamedIndividual ; ; rdfs:comment "A person attending the event."@en ; rdfs:isDefinedBy ; rdfs:label "attendees"@en . ### https://schema.org/audience rdf:type owl:NamedIndividual ; rdfs:comment "An intended audience, i.e. a group for whom something was created."@en ; rdfs:isDefinedBy ; rdfs:label "audience"@en . ### https://schema.org/availableOnDevice rdf:type owl:NamedIndividual ; rdfs:comment "Device required to run the application. Used in cases where a specific make/model is required to run the application."@en ; rdfs:isDefinedBy ; rdfs:label "availableOnDevice"@en . ### https://schema.org/award rdf:type owl:NamedIndividual ; rdfs:comment "An award won by or for this item."@en ; rdfs:isDefinedBy ; rdfs:label "award"@en . ### https://schema.org/awards rdf:type owl:NamedIndividual ; ; rdfs:comment "Awards won by or for this item."@en ; rdfs:isDefinedBy ; rdfs:label "awards"@en . ### https://schema.org/benefits rdf:type owl:NamedIndividual ; ; rdfs:comment "Description of benefits associated with the job."@en ; rdfs:isDefinedBy ; rdfs:label "benefits"@en . ### https://schema.org/blogPost rdf:type owl:NamedIndividual ; rdfs:comment "A posting that is part of this blog."@en ; rdfs:isDefinedBy ; rdfs:label "blogPost"@en . ### https://schema.org/blogPosts rdf:type owl:NamedIndividual ; ; rdfs:comment "Indicates a post that is part of a Blog. Note that historically, what we term a \"Blog\" was once known as a \"weblog\", and that what we term a \"BlogPosting\" is now often colloquially referred to as a \"blog\"."@en ; rdfs:isDefinedBy ; rdfs:label "blogPosts"@en . ### https://schema.org/bookingAgent rdf:type owl:NamedIndividual ; ; rdfs:comment "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."@en ; rdfs:isDefinedBy ; rdfs:label "bookingAgent"@en . ### https://schema.org/branch rdf:type owl:NamedIndividual ; ; rdfs:comment "The branches that delineate from the nerve bundle. Not to be confused with branchOf."@en ; rdfs:isDefinedBy ; rdfs:label "branch"@en . ### https://schema.org/branchOf rdf:type owl:NamedIndividual ; ; rdfs:comment "The larger organization that this local business is a branch of, if any. Not to be confused with (anatomical) branch."@en ; rdfs:isDefinedBy ; rdfs:label "branchOf"@en . ### https://schema.org/broker rdf:type owl:NamedIndividual ; rdfs:comment "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."@en ; rdfs:isDefinedBy ; rdfs:label "broker"@en . ### https://schema.org/carrier rdf:type owl:NamedIndividual ; ; rdfs:comment "'carrier' is an out-dated term indicating the 'provider' for parcel delivery and flights."@en ; rdfs:isDefinedBy ; rdfs:label "carrier"@en . ### https://schema.org/catalog rdf:type owl:NamedIndividual ; ; rdfs:comment "A data catalog which contains this dataset."@en ; rdfs:isDefinedBy ; rdfs:label "catalog"@en . ### https://schema.org/clincalPharmacology rdf:type owl:NamedIndividual ; ; rdfs:comment "Description of the absorption and elimination of drugs, including their concentration (pharmacokinetics, pK) and biological effects (pharmacodynamics, pD)."@en ; rdfs:isDefinedBy ; rdfs:label "clincalPharmacology"@en . ### https://schema.org/clinicalPharmacology rdf:type owl:NamedIndividual ; rdfs:comment "Description of the absorption and elimination of drugs, including their concentration (pharmacokinetics, pK) and biological effects (pharmacodynamics, pD)."@en ; rdfs:isDefinedBy ; rdfs:label "clinicalPharmacology"@en . ### https://schema.org/codeSampleType rdf:type owl:NamedIndividual ; rdfs:comment "What type of code sample: full (compile ready) solution, code snippet, inline code, scripts, template."@en ; rdfs:isDefinedBy ; rdfs:label "codeSampleType"@en . ### https://schema.org/colleague rdf:type owl:NamedIndividual ; rdfs:comment "A colleague of the person."@en ; rdfs:isDefinedBy ; rdfs:label "colleague"@en . ### https://schema.org/colleagues rdf:type owl:NamedIndividual ; ; rdfs:comment "A colleague of the person."@en ; rdfs:isDefinedBy ; rdfs:label "colleagues"@en . ### https://schema.org/collection rdf:type owl:NamedIndividual ; ; rdfs:comment "A sub property of object. The collection target of the action."@en ; rdfs:isDefinedBy ; rdfs:label "collection"@en . ### https://schema.org/contactPoint rdf:type owl:NamedIndividual ; rdfs:comment "A contact point for a person or organization."@en ; rdfs:isDefinedBy ; rdfs:label "contactPoint"@en . ### https://schema.org/contactPoints rdf:type owl:NamedIndividual ; ; rdfs:comment "A contact point for a person or organization."@en ; rdfs:isDefinedBy ; rdfs:label "contactPoints"@en . ### https://schema.org/containedIn rdf:type owl:NamedIndividual ; ; rdfs:comment "The basic containment relation between a place and one that contains it."@en ; rdfs:isDefinedBy ; rdfs:label "containedIn"@en . ### https://schema.org/containedInPlace rdf:type owl:NamedIndividual ; rdfs:comment "The basic containment relation between a place and one that contains it."@en ; rdfs:isDefinedBy ; rdfs:label "containedInPlace"@en . ### https://schema.org/containsSeason rdf:type owl:NamedIndividual ; rdfs:comment "A season that is part of the media series."@en ; rdfs:isDefinedBy ; rdfs:label "containsSeason"@en . ### https://schema.org/course rdf:type owl:NamedIndividual ; ; rdfs:comment "A sub property of location. The course where this action was taken."@en ; rdfs:isDefinedBy ; rdfs:label "course"@en . ### https://schema.org/datasetTimeInterval rdf:type owl:NamedIndividual ; ; rdfs:comment "The range of temporal applicability of a dataset, e.g. for a 2011 census dataset, the year 2011 (in ISO 8601 time interval format)."@en ; rdfs:isDefinedBy ; rdfs:label "datasetTimeInterval"@en . ### https://schema.org/device rdf:type owl:NamedIndividual ; ; rdfs:comment "Device required to run the application. Used in cases where a specific make/model is required to run the application."@en ; rdfs:isDefinedBy ; rdfs:label "device"@en . ### https://schema.org/director rdf:type owl:NamedIndividual ; rdfs:comment "A director of e.g. TV, radio, movie, video gaming etc. content, or of an event. Directors can be associated with individual items or with a series, episode, clip."@en ; rdfs:isDefinedBy ; rdfs:label "director"@en . ### https://schema.org/directors rdf:type owl:NamedIndividual ; ; rdfs:comment "A director of e.g. TV, radio, movie, video games etc. content. Directors can be associated with individual items or with a series, episode, clip."@en ; rdfs:isDefinedBy ; rdfs:label "directors"@en . ### https://schema.org/employee rdf:type owl:NamedIndividual ; rdfs:comment "Someone working for this organization."@en ; rdfs:isDefinedBy ; rdfs:label "employee"@en . ### https://schema.org/employees rdf:type owl:NamedIndividual ; ; rdfs:comment "People working for this organization."@en ; rdfs:isDefinedBy ; rdfs:label "employees"@en . ### https://schema.org/encoding rdf:type owl:NamedIndividual ; rdfs:comment "A media object that encodes this CreativeWork. This property is a synonym for associatedMedia."@en ; rdfs:isDefinedBy ; rdfs:label "encoding"@en . ### https://schema.org/encodingFormat rdf:type owl:NamedIndividual ; rdfs:comment """Media type typically expressed using a MIME format (see IANA site and MDN reference), e.g. application/zip for a SoftwareApplication binary, audio/mpeg for .mp3 etc.

In cases where a CreativeWork has several media type representations, encoding can be used to indicate each MediaObject alongside particular encodingFormat information.

Unregistered or niche encoding and file formats can be indicated instead via the most appropriate URL, e.g. defining Web page or a Wikipedia/Wikidata entry."""@en ; rdfs:isDefinedBy ; rdfs:label "encodingFormat"@en . ### https://schema.org/encodings rdf:type owl:NamedIndividual ; ; rdfs:comment "A media object that encodes this CreativeWork."@en ; rdfs:isDefinedBy ; rdfs:label "encodings"@en . ### https://schema.org/episode rdf:type owl:NamedIndividual ; rdfs:comment "An episode of a TV, radio or game media within a series or season."@en ; rdfs:isDefinedBy ; rdfs:label "episode"@en . ### https://schema.org/episodes rdf:type owl:NamedIndividual ; ; rdfs:comment "An episode of a TV/radio series or season."@en ; rdfs:isDefinedBy ; rdfs:label "episodes"@en . ### https://schema.org/event rdf:type owl:NamedIndividual ; rdfs:comment "Upcoming or past event associated with this place, organization, or action."@en ; rdfs:isDefinedBy ; rdfs:label "event"@en . ### https://schema.org/events rdf:type owl:NamedIndividual ; ; rdfs:comment "Upcoming or past events associated with this place or organization."@en ; rdfs:isDefinedBy ; rdfs:label "events"@en . ### https://schema.org/executableLibraryName rdf:type owl:NamedIndividual ; rdfs:comment "Library file name, e.g., mscorlib.dll, system.web.dll."@en ; rdfs:isDefinedBy ; rdfs:label "executableLibraryName"@en . ### https://schema.org/exerciseCourse rdf:type owl:NamedIndividual ; rdfs:comment "A sub property of location. The course where this action was taken."@en ; rdfs:isDefinedBy ; rdfs:label "exerciseCourse"@en . ### https://schema.org/fileFormat rdf:type owl:NamedIndividual ; ; rdfs:comment "Media type, typically MIME format (see IANA site) of the content, e.g. application/zip of a SoftwareApplication binary. In cases where a CreativeWork has several media type representations, 'encoding' can be used to indicate each MediaObject alongside particular fileFormat information. Unregistered or niche file formats can be indicated instead via the most appropriate URL, e.g. defining Web page or a Wikipedia entry."@en ; rdfs:isDefinedBy ; rdfs:label "fileFormat"@en . ### https://schema.org/founder rdf:type owl:NamedIndividual ; rdfs:comment "A person or organization who founded this organization."@en ; rdfs:isDefinedBy ; rdfs:label "founder"@en . ### https://schema.org/founders rdf:type owl:NamedIndividual ; ; rdfs:comment "A person who founded this organization."@en ; rdfs:isDefinedBy ; rdfs:label "founders"@en . ### https://schema.org/free rdf:type owl:NamedIndividual ; ; rdfs:comment "A flag to signal that the item, event, or place is accessible for free."@en ; rdfs:isDefinedBy ; rdfs:label "free"@en . ### https://schema.org/hasMap rdf:type owl:NamedIndividual ; rdfs:comment "A URL to a map of the place."@en ; rdfs:isDefinedBy ; rdfs:label "hasMap"@en . ### https://schema.org/hasMenu rdf:type owl:NamedIndividual ; rdfs:comment "Either the actual menu as a structured representation, as text, or a URL of the menu."@en ; rdfs:isDefinedBy ; rdfs:label "hasMenu"@en . ### https://schema.org/hasMerchantReturnPolicy rdf:type owl:NamedIndividual ; rdfs:comment "Specifies a MerchantReturnPolicy that may be applicable."@en ; rdfs:isDefinedBy ; rdfs:label "hasMerchantReturnPolicy"@en . ### https://schema.org/hasProductReturnPolicy rdf:type owl:NamedIndividual ; ; rdfs:comment "Indicates a ProductReturnPolicy that may be applicable."@en ; rdfs:isDefinedBy ; rdfs:label "hasProductReturnPolicy"@en . ### https://schema.org/inLanguage rdf:type owl:NamedIndividual ; rdfs:comment "The language of the content or performance or used in an action. Please use one of the language codes from the IETF BCP 47 standard. See also availableLanguage."@en ; rdfs:isDefinedBy ; rdfs:label "inLanguage"@en . ### https://schema.org/incentiveCompensation rdf:type owl:NamedIndividual ; rdfs:comment "Description of bonus and commission compensation aspects of the job."@en ; rdfs:isDefinedBy ; rdfs:label "incentiveCompensation"@en . ### https://schema.org/incentives rdf:type owl:NamedIndividual ; ; rdfs:comment "Description of bonus and commission compensation aspects of the job."@en ; rdfs:isDefinedBy ; rdfs:label "incentives"@en . ### https://schema.org/includedDataCatalog rdf:type owl:NamedIndividual ; ; rdfs:comment "A data catalog which contains this dataset (this property was previously 'catalog', preferred name is now 'includedInDataCatalog')."@en ; rdfs:isDefinedBy ; rdfs:label "includedDataCatalog"@en . ### https://schema.org/includedInDataCatalog rdf:type owl:NamedIndividual ; rdfs:comment "A data catalog which contains this dataset."@en ; rdfs:isDefinedBy ; rdfs:label "includedInDataCatalog"@en . ### https://schema.org/ingredients rdf:type owl:NamedIndividual ; ; rdfs:comment "A single ingredient used in the recipe, e.g. sugar, flour or garlic."@en ; rdfs:isDefinedBy ; rdfs:label "ingredients"@en . ### https://schema.org/interactionCount rdf:type owl:NamedIndividual ; ; rdfs:comment "This property is deprecated, alongside the UserInteraction types on which it depended."@en ; rdfs:isDefinedBy ; rdfs:label "interactionCount"@en . ### https://schema.org/interactionStatistic rdf:type owl:NamedIndividual ; rdfs:comment "The number of interactions for the CreativeWork using the WebSite or SoftwareApplication. The most specific child type of InteractionCounter should be used."@en ; rdfs:isDefinedBy ; rdfs:label "interactionStatistic"@en . ### https://schema.org/isAccessibleForFree rdf:type owl:NamedIndividual ; rdfs:comment "A flag to signal that the item, event, or place is accessible for free."@en ; rdfs:isDefinedBy ; rdfs:label "isAccessibleForFree"@en . ### https://schema.org/isBasedOn rdf:type owl:NamedIndividual ; rdfs:comment "A resource from which this work is derived or from which it is a modification or adaptation."@en ; rdfs:isDefinedBy ; rdfs:label "isBasedOn"@en . ### https://schema.org/isBasedOnUrl rdf:type owl:NamedIndividual ; ; rdfs:comment "A resource that was used in the creation of this resource. This term can be repeated for multiple sources. For example, http://example.com/great-multiplication-intro.html."@en ; rdfs:isDefinedBy ; rdfs:label "isBasedOnUrl"@en . ### https://schema.org/jobBenefits rdf:type owl:NamedIndividual ; rdfs:comment "Description of benefits associated with the job."@en ; rdfs:isDefinedBy ; rdfs:label "jobBenefits"@en . ### https://schema.org/language rdf:type owl:NamedIndividual ; ; rdfs:comment "A sub property of instrument. The language used on this action."@en ; rdfs:isDefinedBy ; rdfs:label "language"@en . ### https://schema.org/mainContentOfPage rdf:type owl:NamedIndividual ; rdfs:comment "Indicates if this web page element is the main subject of the page."@en ; rdfs:isDefinedBy ; rdfs:label "mainContentOfPage"@en . ### https://schema.org/map rdf:type owl:NamedIndividual ; ; rdfs:comment "A URL to a map of the place."@en ; rdfs:isDefinedBy ; rdfs:label "map"@en . ### https://schema.org/maps rdf:type owl:NamedIndividual ; ; rdfs:comment "A URL to a map of the place."@en ; rdfs:isDefinedBy ; rdfs:label "maps"@en . ### https://schema.org/member rdf:type owl:NamedIndividual ; rdfs:comment "A member of an Organization or a ProgramMembership. Organizations can be members of organizations; ProgramMembership is typically for individuals."@en ; rdfs:isDefinedBy ; rdfs:label "member"@en . ### https://schema.org/members rdf:type owl:NamedIndividual ; ; rdfs:comment "A member of this organization."@en ; rdfs:isDefinedBy ; rdfs:label "members"@en . ### https://schema.org/menu rdf:type owl:NamedIndividual ; ; rdfs:comment "Either the actual menu as a structured representation, as text, or a URL of the menu."@en ; rdfs:isDefinedBy ; rdfs:label "menu"@en . ### https://schema.org/merchant rdf:type owl:NamedIndividual ; ; rdfs:comment "'merchant' is an out-dated term for 'seller'."@en ; rdfs:isDefinedBy ; rdfs:label "merchant"@en . ### https://schema.org/merchantReturnDays rdf:type owl:NamedIndividual ; rdfs:comment "Specifies either a fixed return date or the number of days (from the delivery date) that a product can be returned. Used when the returnPolicyCategory property is specified as MerchantReturnFiniteReturnWindow."@en ; rdfs:isDefinedBy ; rdfs:label "merchantReturnDays"@en . ### https://schema.org/merchantReturnLink rdf:type owl:NamedIndividual ; rdfs:comment "Specifies a Web page or service by URL, for product returns."@en ; rdfs:isDefinedBy ; rdfs:label "merchantReturnLink"@en . ### https://schema.org/musicGroupMember rdf:type owl:NamedIndividual ; ; rdfs:comment "A member of a music group—for example, John, Paul, George, or Ringo."@en ; rdfs:isDefinedBy ; rdfs:label "musicGroupMember"@en . ### https://schema.org/namedPosition rdf:type owl:NamedIndividual ; ; rdfs:comment "A position played, performed or filled by a person or organization, as part of an organization. For example, an athlete in a SportsTeam might play in the position named 'Quarterback'."@en ; rdfs:isDefinedBy ; rdfs:label "namedPosition"@en . ### https://schema.org/option rdf:type owl:NamedIndividual ; ; rdfs:comment "A sub property of object. The options subject to this action."@en ; rdfs:isDefinedBy ; rdfs:label "option"@en . ### https://schema.org/parent rdf:type owl:NamedIndividual ; rdfs:comment "A parent of this person."@en ; rdfs:isDefinedBy ; rdfs:label "parent"@en . ### https://schema.org/parentOrganization rdf:type owl:NamedIndividual ; rdfs:comment "The larger organization that this organization is a subOrganization of, if any."@en ; rdfs:isDefinedBy ; rdfs:label "parentOrganization"@en . ### https://schema.org/parents rdf:type owl:NamedIndividual ; ; rdfs:comment "A parents of the person."@en ; rdfs:isDefinedBy ; rdfs:label "parents"@en . ### https://schema.org/partOfSeries rdf:type owl:NamedIndividual ; rdfs:comment "The series to which this episode or season belongs."@en ; rdfs:isDefinedBy ; rdfs:label "partOfSeries"@en . ### https://schema.org/partOfTVSeries rdf:type owl:NamedIndividual ; ; rdfs:comment "The TV series to which this episode or season belongs."@en ; rdfs:isDefinedBy ; rdfs:label "partOfTVSeries"@en . ### https://schema.org/paymentDue rdf:type owl:NamedIndividual ; ; rdfs:comment "The date that payment is due."@en ; rdfs:isDefinedBy ; rdfs:label "paymentDue"@en . ### https://schema.org/paymentDueDate rdf:type owl:NamedIndividual ; rdfs:comment "The date that payment is due."@en ; rdfs:isDefinedBy ; rdfs:label "paymentDueDate"@en . ### https://schema.org/performer rdf:type owl:NamedIndividual ; rdfs:comment "A performer at the event—for example, a presenter, musician, musical group or actor."@en ; rdfs:isDefinedBy ; rdfs:label "performer"@en . ### https://schema.org/performers rdf:type owl:NamedIndividual ; ; rdfs:comment "The main performer or performers of the event—for example, a presenter, musician, or actor."@en ; rdfs:isDefinedBy ; rdfs:label "performers"@en . ### https://schema.org/photo rdf:type owl:NamedIndividual ; rdfs:comment "A photograph of this place."@en ; rdfs:isDefinedBy ; rdfs:label "photo"@en . ### https://schema.org/photos rdf:type owl:NamedIndividual ; ; rdfs:comment "Photographs of this place."@en ; rdfs:isDefinedBy ; rdfs:label "photos"@en . ### https://schema.org/produces rdf:type owl:NamedIndividual ; ; rdfs:comment "The tangible thing generated by the service, e.g. a passport, permit, etc."@en ; rdfs:isDefinedBy ; rdfs:label "produces"@en . ### https://schema.org/productReturnDays rdf:type owl:NamedIndividual ; ; rdfs:comment "The productReturnDays property indicates the number of days (from purchase) within which relevant product return policy is applicable."@en ; rdfs:isDefinedBy ; rdfs:label "productReturnDays"@en . ### https://schema.org/productReturnLink rdf:type owl:NamedIndividual ; ; rdfs:comment "Indicates a Web page or service by URL, for product return."@en ; rdfs:isDefinedBy ; rdfs:label "productReturnLink"@en . ### https://schema.org/provider rdf:type owl:NamedIndividual ; rdfs:comment "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."@en ; rdfs:isDefinedBy ; rdfs:label "provider"@en . ### https://schema.org/recipeIngredient rdf:type owl:NamedIndividual ; rdfs:comment "An ingredient or ordered list of ingredients and potentially quantities used in the recipe, e.g. 1 cup of sugar, flour or garlic. The ingredients can be represented as free text or more structured values."@en ; rdfs:isDefinedBy ; rdfs:label "recipeIngredient"@en . ### https://schema.org/requirements rdf:type owl:NamedIndividual ; ; rdfs:comment "Component dependency requirements for application. This includes runtime environments and shared libraries that are not included in the application distribution package, but required to run the application (examples: DirectX, Java or .NET runtime)."@en ; rdfs:isDefinedBy ; rdfs:label "requirements"@en . ### https://schema.org/review rdf:type owl:NamedIndividual ; rdfs:comment "A review of the item."@en ; rdfs:isDefinedBy ; rdfs:label "review"@en . ### https://schema.org/reviews rdf:type owl:NamedIndividual ; ; rdfs:comment "Review of the item."@en ; rdfs:isDefinedBy ; rdfs:label "reviews"@en . ### https://schema.org/roleName rdf:type owl:NamedIndividual . ### https://schema.org/runtime rdf:type owl:NamedIndividual ; ; rdfs:comment "Runtime platform or script interpreter dependencies (example: Java v1, Python 2.3, .NET Framework 3.0)."@en ; rdfs:isDefinedBy ; rdfs:label "runtime"@en . ### https://schema.org/runtimePlatform rdf:type owl:NamedIndividual ; rdfs:comment "Runtime platform or script interpreter dependencies (example: Java v1, Python 2.3, .NET Framework 3.0)."@en ; rdfs:isDefinedBy ; rdfs:label "runtimePlatform"@en . ### https://schema.org/sampleType rdf:type owl:NamedIndividual ; ; rdfs:comment "What type of code sample: full (compile ready) solution, code snippet, inline code, scripts, template."@en ; rdfs:isDefinedBy ; rdfs:label "sampleType"@en . ### https://schema.org/season rdf:type owl:NamedIndividual ; ; rdfs:comment "A season in a media series."@en ; rdfs:isDefinedBy ; rdfs:label "season"@en . ### https://schema.org/seasons rdf:type owl:NamedIndividual ; ; rdfs:comment "A season in a media series."@en ; rdfs:isDefinedBy ; rdfs:label "seasons"@en . ### https://schema.org/seller rdf:type owl:NamedIndividual ; rdfs:comment "An entity which offers (sells / leases / lends / loans) the services / goods. A seller may also be a provider."@en ; rdfs:isDefinedBy ; rdfs:label "seller"@en . ### https://schema.org/serviceArea rdf:type owl:NamedIndividual ; ; rdfs:comment "The geographic area where the service is provided."@en ; rdfs:isDefinedBy ; rdfs:label "serviceArea"@en . ### https://schema.org/serviceAudience rdf:type owl:NamedIndividual ; ; rdfs:comment "The audience eligible for this service."@en ; rdfs:isDefinedBy ; rdfs:label "serviceAudience"@en . ### https://schema.org/serviceOutput rdf:type owl:NamedIndividual ; rdfs:comment "The tangible thing generated by the service, e.g. a passport, permit, etc."@en ; rdfs:isDefinedBy ; rdfs:label "serviceOutput"@en . ### https://schema.org/sibling rdf:type owl:NamedIndividual ; rdfs:comment "A sibling of the person."@en ; rdfs:isDefinedBy ; rdfs:label "sibling"@en . ### https://schema.org/siblings rdf:type owl:NamedIndividual ; ; rdfs:comment "A sibling of the person."@en ; rdfs:isDefinedBy ; rdfs:label "siblings"@en . ### https://schema.org/significantLink rdf:type owl:NamedIndividual ; rdfs:comment "One of the more significant URLs on the page. Typically, these are the non-navigation links that are clicked on the most."@en ; rdfs:isDefinedBy ; rdfs:label "significantLink"@en . ### https://schema.org/significantLinks rdf:type owl:NamedIndividual ; ; rdfs:comment "The most significant URLs on the page. Typically, these are the non-navigation links that are clicked on the most."@en ; rdfs:isDefinedBy ; rdfs:label "significantLinks"@en . ### https://schema.org/softwareRequirements rdf:type owl:NamedIndividual ; rdfs:comment "Component dependency requirements for application. This includes runtime environments and shared libraries that are not included in the application distribution package, but required to run the application (examples: DirectX, Java or .NET runtime)."@en ; rdfs:isDefinedBy ; rdfs:label "softwareRequirements"@en . ### https://schema.org/step rdf:type owl:NamedIndividual ; rdfs:comment "A single step item (as HowToStep, text, document, video, etc.) or a HowToSection."@en ; rdfs:isDefinedBy ; rdfs:label "step"@en . ### https://schema.org/steps rdf:type owl:NamedIndividual ; ; rdfs:comment "A single step item (as HowToStep, text, document, video, etc.) or a HowToSection (originally misnamed 'steps'; 'step' is preferred)."@en ; rdfs:isDefinedBy ; rdfs:label "steps"@en . ### https://schema.org/subEvent rdf:type owl:NamedIndividual ; rdfs:comment "An Event that is part of this event. For example, a conference event includes many presentations, each of which is a subEvent of the conference."@en ; rdfs:isDefinedBy ; rdfs:label "subEvent"@en . ### https://schema.org/subEvents rdf:type owl:NamedIndividual ; ; rdfs:comment "Events that are a part of this event. For example, a conference event includes many presentations, each subEvents of the conference."@en ; rdfs:isDefinedBy ; rdfs:label "subEvents"@en . ### https://schema.org/surface rdf:type owl:NamedIndividual ; ; rdfs:comment "A material used as a surface in some artwork, e.g. Canvas, Paper, Wood, Board, etc."@en ; rdfs:isDefinedBy ; rdfs:label "surface"@en . ### https://schema.org/targetCollection rdf:type owl:NamedIndividual ; rdfs:comment "A sub property of object. The collection target of the action."@en ; rdfs:isDefinedBy ; rdfs:label "targetCollection"@en . ### https://schema.org/temporalCoverage rdf:type owl:NamedIndividual ; rdfs:comment """The temporalCoverage of a CreativeWork indicates the period that the content applies to, i.e. that it describes, either as a DateTime or as a textual string indicating a time period in ISO 8601 time interval format. In the case of a Dataset it will typically indicate the relevant time period in a precise notation (e.g. for a 2011 census dataset, the year 2011 would be written \"2011/2012\"). Other forms of content, e.g. ScholarlyArticle, Book, TVSeries or TVEpisode, may indicate their temporalCoverage in broader terms - textually or via well-known URL. Written works such as books may sometimes have precise temporal coverage too, e.g. a work set in 1939 - 1945 can be indicated in ISO 8601 interval format format via \"1939/1945\".

Open-ended date ranges can be written with \"..\" in place of the end date. For example, \"2015-11/..\" indicates a range beginning in November 2015 and with no specified final date. This is tentative and might be updated in future when ISO 8601 is officially updated."""@en ; rdfs:isDefinedBy ; rdfs:label "temporalCoverage"@en . ### https://schema.org/track rdf:type owl:NamedIndividual ; rdfs:comment "A music recording (track)—usually a single song. If an ItemList is given, the list should contain items of type MusicRecording."@en ; rdfs:isDefinedBy ; rdfs:label "track"@en . ### https://schema.org/tracks rdf:type owl:NamedIndividual ; ; rdfs:comment "A music recording (track)—usually a single song."@en ; rdfs:isDefinedBy ; rdfs:label "tracks"@en . ### https://schema.org/vendor rdf:type owl:NamedIndividual ; ; rdfs:comment "'vendor' is an earlier term for 'seller'."@en ; rdfs:isDefinedBy ; rdfs:label "vendor"@en . ### https://schema.org/warranty rdf:type owl:NamedIndividual ; rdfs:comment "The warranty promise(s) included in the offer."@en ; rdfs:isDefinedBy ; rdfs:label "warranty"@en . ### https://schema.org/warrantyPromise rdf:type owl:NamedIndividual ; ; rdfs:comment "The warranty promise(s) included in the offer."@en ; rdfs:isDefinedBy ; rdfs:label "warrantyPromise"@en . ################################################################# # Annotations ################################################################# rdfs:label "description" . rdfs:label "license" . rdfs:label "title" . rdfs:isDefinedBy ; rdfs:label "Action"@en ; "An operation on an Asset."@en ; "Actions may be allowed by Permissions, disallowed by Prohibitions, or made mandatory by Duties."@en . rdfs:isDefinedBy ; rdfs:label "Agreement"@en ; "A Policy that grants the assignee a Rule over an Asset from an assigner."@en ; "An Agreement Policy MUST contain at least one Permission or Prohibition rule, a Party with Assigner function, and a Party with Assignee function (in the same Permission or Prohibition). The Agreement Policy will grant the terms of the Policy from the Assigner to the Assignee."@en . rdfs:isDefinedBy ; rdfs:label "Assertion"@en ; "A Policy that asserts a Rule over an Asset from parties."@en ; "For example, a party (an assignee or assigner) can claim what terms they have over an Asset. An Assertion Policy does not grant such permissions/prohibitions but only asserts the parties claims. An Assetion Policy MUST contain a target Asset, a Party with any functional role, and at least one of a Permission or Prohibition rule."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Asset"@en ; "A resource or a collection of resources that are the subject of a Rule."@en ; "The Asset entity can be any form of identifiable resource, such as data/information, content/media, applications, or services. Furthermore, it can be used to represent other Asset entities that are needed to undertake the Policy expression, such as with the Duty entity. To describe more details about the Asset, it is recommended to use Dublin Core [[dcterms]] elements or other content metadata."@en . rdfs:isDefinedBy ; rdfs:label "Asset Collection"@en ; "An Asset that is collection of individual resources"@en . rdfs:isDefinedBy ; rdfs:label "Conflict Strategy Preference"@en ; "Used to establish strategies to resolve conflicts that arise from the merging of Policies or conflicts between Permissions and Prohibitions in the same Policy."@en ; "Instances of ConflictTerm describe strategies for resolving conflicts."@en . rdfs:isDefinedBy ; rdfs:label "Constraint"@en ; "A boolean expression that refines the semantics of an Action and Party/Asset Collection or declare the conditions applicable to a Rule."@en . rdfs:isDefinedBy ; rdfs:label "Duty"@en ; "The obligation to perform an Action"@en . rdfs:isDefinedBy ; rdfs:label "Left Operand"@en ; "Left operand for a constraint expression."@en ; "Instances of the LeftOperand class are used as the leftOperand of a Constraint."@en . rdfs:isDefinedBy ; rdfs:label "Logical Constraint"@en ; "A logical expression that refines the semantics of an Action and Party/Asset Collection or declare the conditions applicable to a Rule."@en . rdfs:isDefinedBy ; rdfs:label "Offer"@en ; "A Policy that proposes a Rule over an Asset from an assigner."@en ; "An Offer Policy MUST contain at least one Permission or Prohibition rule and a Party with Assigner function (in the same Permission or Prohibition). The Offer Policy MAY contain a Party with Assignee function, but MUST not grant any privileges to that Party."@en . rdfs:isDefinedBy ; rdfs:label "Operator"@en ; "Operator for constraint expression."@en ; "Instances of the Operator class representing relational operators."@en . rdfs:isDefinedBy ; rdfs:label "Party"@en ; "An entity or a collection of entities that undertake Roles in a Rule."@en ; "The Party entity could be a person, group of people, organisation, or agent. An agent is a person or thing that takes an active role or produces a specified effect. To describe more details about the Party, it is recommended to use W3C vCard Ontology [[vcard-rdf]] or FOAF Vocabulary [[foaf]]."@en . rdfs:isDefinedBy ; rdfs:label "Party Collection"@en ; "A Party that is a group of individual entities"@en . rdfs:isDefinedBy ; rdfs:label "Party Scope"@en ; owl:deprecated "true"^^xsd:boolean ; "Scopes for Party Scope expressions."@en ; "Instances of the PartyScope class represent the terms for the scope property of Parties."@en . rdfs:isDefinedBy ; rdfs:label "Permission"@en ; "The ability to perform an Action over an Asset."@en . rdfs:isDefinedBy ; rdfs:label "Policy"@en ; "A non-empty group of Permissions and/or Prohibitions."@en ; "A Policy may contain multiple Rules."@en . rdfs:isDefinedBy ; rdfs:label "Privacy Policy"@en ; "A Policy that expresses a Rule over an Asset containing personal information."@en ; "A Privacy Policy MUST contain a target Asset, a Party with Assigner is, a Party with Assignee function, and at least one of a Permission or Prohibition rule that MUST include a Duty. The target Asset SHOULD contain or relate to personal information about the Assignee. The Duty MUST describe obligations on the Assigner about managing the Asset. The Assignee is being granted the terms of the Privacy policy from the Assigner."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Prohibition"@en ; "The inability to perform an Action over an Asset."@en . rdfs:isDefinedBy ; rdfs:label "Request"@en ; "A Policy that proposes a Rule over an Asset from an assignee."@en ; "A Request Policy MUST contain a target Asset, a Party with Assignee function, and at least one of a Permission or Prohibition rule. The Request MAY also contain the Party with Assigner function if this is known. No privileges are granted to any Party."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Right Operand"@en ; "Right operand for constraint expression."@en ; "Instances of the RightOperand class are used as the rightOperand of a Constraint."@en . rdfs:isDefinedBy ; rdfs:label "Rule"@en ; "An abstract concept that represents the common characteristics of Permissions, Prohibitions, and Duties."@en ; "Rule is an abstract concept."@en . rdfs:isDefinedBy ; rdfs:label "Set"@en ; "A Policy that expresses a Rule over an Asset."@en ; "A Set Policy MUST contain a target Asset, and at least one Rule. A Set Policy is the default Policy subclass. The Set is aimed at scenarios where there is an open criteria for the semantics of the policy expressions and typically refined by other systems/profiles that process the information at a later time. No privileges are granted to any Party (if defined)."@en . rdfs:isDefinedBy ; rdfs:label "Ticket"@en ; "A Policy that grants the holder a Rule over an Asset from an assigner."@en ; "A Ticket Policy MUST contain a target Asset and at least one of a Permission or Prohibition rule. The Ticket MAY contain the Party with Assigner function and MUST NOT contain an Assignee. The Ticket Policy will grant the terms of the Policy to the holder of that Ticket. The holder of the Ticket MAY remain unknown or MAY have to be identified at some later stage."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Undefined Term"@en ; owl:deprecated "true"^^xsd:boolean ; "Is used to indicate how to support Actions that are not part of any vocabulary or profile in the policy expression system."@en ; "Instances of UndefinedTerm describe strategies for processing unsupported actions."@en . rdfs:isDefinedBy ; rdfs:label "Has Action"@en ; "The operation relating to the Asset for which the Rule is being subjected."@en . rdfs:isDefinedBy ; rdfs:label "And"@en ; "The relation is satisfied when all of the Constraints are satisfied."@en ; "This property MUST only be used for Logical Constraints, and the list of operand values MUST be Constraint instances."@en . rdfs:isDefinedBy ; rdfs:label "And Sequence"@en ; "The relation is satisfied when each of the Constraints are satisfied in the order specified."@en ; "This property MUST only be used for Logical Constraints, and the list of operand values MUST be Constraint instances. The order of the list MUST be preserved. The andSequence operator is an example where there may be temporal conditional requirements between the operands. This may lead to situations where the outcome is unresolvable, such as deadlock if one of the Constraints is unable to be satisfied. ODRL Processing systems SHOULD plan for these scenarios and implement mechanisms to resolve them."@en . rdfs:isDefinedBy ; rdfs:label "Assignee"@en ; "The Party is the recipient of the Rule."@en . rdfs:isDefinedBy ; rdfs:label "Assignee Of"@en ; "Identifies an ODRL Policy for which the identified Party undertakes the assignee functional role."@en ; "When assigneeOf has been asserted between a metadata expression and an ODRL Policy, the Party being identified MUST be inferred to undertake the assignee functional role of all the Rules of that Policy."@en . rdfs:isDefinedBy ; rdfs:label "Assigner"@en ; "The Party is the issuer of the Rule."@en . rdfs:isDefinedBy ; rdfs:label "Assigner Of"@en ; "Identifies an ODRL Policy for which the identified Party undertakes the assigner functional role."@en ; "When assignerOf has been asserted between a metadata expression and an ODRL Policy, the Party being identified MUST be inferred to undertake the assigner functional role of all the Rules of that Policy."@en . rdfs:isDefinedBy ; rdfs:label "Attributed Party"@en ; "The Party to be attributed."@en ; "Maybe specified as part of the attribute action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Attributing Party"@en ; "The Party who undertakes the attribution."@en ; "Maybe specified as part of the attribute action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Compensated Party"@en ; "The Party is the recipient of the compensation."@en ; "Maybe specified as part of the compensate duty action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Compensating Party"@en ; "The Party that is the provider of the compensation."@en ; "Maybe specified as part of the compensate duty action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Handle Policy Conflicts"@en ; "The conflict-resolution strategy for a Policy."@en ; "If no strategy is specified, the default is invalid."@en . rdfs:isDefinedBy ; rdfs:label "Consented Party"@en ; "The Party who obtains the consent."@en ; "Maybe specified as part of the obtainConsent action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Consenting Party"@en ; "The Party to obtain consent from."@en ; "Maybe specified as part of the obtainConsent action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Consequence"@en ; "Relates a Duty to another Duty, the latter being a consequence of not fulfilling the former."@en ; "The consequence property is utilised to express the repercussions of not fulfilling an agreed Policy obligation or duty for a Permission. If either of these fails to be fulfilled, then this will result in the consequence Duty also becoming a new requirement, meaning that the original obligation or duty, as well as the consequence Duty must all be fulfilled"@en . rdfs:isDefinedBy ; rdfs:label "Has Constraint"@en ; "Constraint applied to a Rule"@en ; "Constraints on Rules are used to determine if a rule is Active or not. Example: the Permission rule is only active during the year 2018."@en . rdfs:isDefinedBy ; rdfs:label "Contracted Party"@en ; "The Party who is being contracted."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Contracting Party"@en ; "The Party who is offering the contract."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Datatype"@en ; "The datatype of the value of the rightOperand or rightOperandReference of a Constraint."@en ; "In RDF encodings, use of the rdf:datatype MUST be used. In JSON-LD encoding, the use of @type MUST be used."@en . rdfs:isDefinedBy ; rdfs:label "Has Duty"@en ; "Relates an individual Duty to a Permission."@en ; "A Duty is a pre-condition which must be fulfilled in order to receive the Permission."@en . rdfs:isDefinedBy ; rdfs:label "Failure"@en ; "Failure is an abstract property that defines the violation (or unmet) relationship between Rules."@en ; "The parent property to sub-properties that express explicit failure contexts."@en . rdfs:isDefinedBy ; rdfs:label "Function"@en ; "Function is an abstract property whose sub-properties define the functional roles which may be fulfilled by a party in relation to a Rule."@en . rdfs:isDefinedBy ; rdfs:label "Target Policy"@en ; "Identifies an ODRL Policy for which the identified Asset is the target Asset to all the Rules."@en ; "The Asset being identified MUST be inferred to be the target Asset of all of the Rules of the Policy."@en . rdfs:isDefinedBy ; rdfs:label "Implies"@en ; "An Action asserts that another Action is not prohibited to enable its operational semantics."@en ; "The property asserts that an instance of Action entails that the other instance of Action is not prohibited."@en . rdfs:isDefinedBy ; rdfs:label "Included In"@en ; "An Action transitively asserts that another Action that encompasses its operational semantics."@en ; "The purpose is to explicitly assert that the semantics of the referenced instance of an other Action encompasses (includes) the semantics of this instance of Action. The includedIn property is transitive, and as such, the Actions form ancestor relationships."@en . rdfs:isDefinedBy ; rdfs:label "Informed Party"@en ; "The Party to be informed of all uses."@en ; "Maybe specified as part of the inform action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Inherits From"@en ; "Relates a (child) policy to another (parent) policy from which terms are inherited."@en ; "The child policy will inherit Rules from the parent policy"@en . rdfs:isDefinedBy ; rdfs:label "Has Left Operand"@en ; "The left operand in a constraint expression."@en . rdfs:isDefinedBy ; rdfs:label "Obligation"@en ; "Relates an individual Duty to a Policy."@en ; "The Duty is a requirement which must be fulfilled."@en . rdfs:isDefinedBy ; rdfs:label "Operand"@en ; "Operand is an abstract property for a logical relationship."@en ; "Sub-properties of operand are used for Logical Constraints."@en . rdfs:isDefinedBy ; rdfs:label "Has Operator"@en ; "The operator function applied to operands of a Constraint"@en . rdfs:isDefinedBy ; rdfs:label "Or"@en ; "The relation is satisfied when at least one of the Constraints is satisfied."@en ; "This property MUST only be used for Logical Constraints, and the list of operand values MUST be Constraint instances."@en . rdfs:isDefinedBy ; rdfs:label "Output"@en ; "The output property specifies the Asset which is created from the output of the Action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Part Of"@en ; "Identifies an Asset/PartyCollection that the Asset/Party is a member of."@en . rdfs:isDefinedBy ; rdfs:label "Has Permission"@en ; "Relates an individual Permission to a Policy."@en . rdfs:isDefinedBy ; rdfs:label "Has Prohibition"@en ; "Relates an individual Prohibition to a Policy."@en . rdfs:isDefinedBy ; rdfs:label "Refinement"@en ; "Constraint used to refine the semantics of an Action, or Party/Asset Collection"@en ; "Example: the Action print is only permitted on 50% of the asset."@en . rdfs:isDefinedBy ; rdfs:label "Relation"@en ; "Relation is an abstract property which creates an explicit link between an Action and an Asset."@en ; "Sub-properties of relation are used to define the nature of that link."@en . rdfs:isDefinedBy ; rdfs:label "Remedy"@en ; "Relates an individual remedy Duty to a Prohibition."@en ; "The remedy property expresses an agreed Duty that must be fulfilled in case that a Prohibition has been violated by being exercised."@en . rdfs:isDefinedBy ; rdfs:label "Has Right Operand"@en ; "The value of the right operand in a constraint expression."@en ; "When used with set-based operators, a list of values may be used."@en . rdfs:isDefinedBy ; rdfs:label "Target"@en ; "The target property indicates the Asset that is the primary subject to which the Rule action directly applies."@en . rdfs:isDefinedBy ; rdfs:label "Tracked Party"@en ; "The Party whose usage is being tracked."@en ; "May be specified as part of the acceptTracking action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Tracking Party"@en ; "The Party who is tracking usage."@en ; "May be specified as part of the acceptTracking action."@en ; "Non-Normative"@en . rdfs:isDefinedBy ; rdfs:label "Only One"@en ; "The relation is satisfied when only one, and not more, of the Constaints is satisfied"@en ; "This property MUST only be used for Logical Constraints, and the list of operand values MUST be Constraint instances."@en . rdfs:isDefinedBy ; rdfs:label "EmptyCollection"@en ; "expanded" ; "collections" ; "An empty collection is a collection without members."@en . rdfs:isDefinedBy ; rdfs:label "specializationOf" ; rdfs:seeAlso ; "expanded" ; "alternate" ; "http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig"^^xsd:anyURI ; "An entity that is a specialization of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. Examples of aspects include a time period, an abstraction, and a context associated with the entity."@en ; "http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-specialization"^^xsd:anyURI ; "generalizationOf" ; "http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-specialization"^^xsd:anyURI . rdfs:comment "A revision is a derivation that revises an entity into a revised version."@en ; rdfs:isDefinedBy ; rdfs:label "wasRevisionOf" ; "expanded" ; "derivations" ; "hadRevision" ; , . rdfs:comment "A role played, performed or filled by a person or organization. For example, the team of creators for a comic book might fill the roles named 'inker', 'penciller', and 'letterer'; or an athlete in a SportsTeam might play in the position named 'Quarterback'."@en ; rdfs:isDefinedBy ; rdfs:label "roleName"@en . ### Generated by the OWL API (version 5.1.18) https://github.com/owlcs/owlapi/