crm:E53_Place leaf node


URI

http://www.cidoc-crm.org/cidoc-crm/E53_Place

Label

E53 Place

Description

Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.

The instances of E53 Place are usually determined by reference to the position of "immobile" objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.

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

Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.

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

In First Order Logic:
E53(x) ⊃ E1(x)

Superclasses (1)

Usage

Instances of crm:E53_Place can have the following properties:

PROPERTYTYPEDESCRIPTIONRANGE
From class crm:E53_Place
crm:P168_place_is_defined_by owl:DatatypeProperty 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 in general result in new definitions of places approximating each other and not in alternative definitions. Note that it is possible for a place to be defined by phenomena causal to it or other forms of identification rather than by an instance of E94 Space Primitive. In this case, this property must not be used for approximating the respective instance of E53 Place with an instance of E94 Space Primitive. In First Order Logic: P168(x,y) ⊃ E53(x) P168(x,y) ⊃ E94(y) owl:Thing
crm:P121_overlaps_with owl:ObjectProperty Scope note: This symmetric property allows the instances of E53 Place with overlapping geometric extents to be associated with each other. It does not specify anything about the shared area. This property is purely spatial, in contrast to Allen operators, which are purely temporal. Examples: - the territory of the United States (E53) overlaps with the Arctic (E53) In First Order Logic: P121(x,y) ⊃ E53(x) P121(x,y) ⊃ E53(y) P121(x,y) ⊃ P121(y,x) crm:E53_Place
crm:P122_borders_with owl:ObjectProperty Scope note: This symmetric property allows the instances of E53 Place which share common borders to be related as such. This property is purely spatial, in contrast to Allen operators, which are purely temporal. Examples: - Scotland (E53) borders with England (E53) In First Order Logic: P122(x,y) ⊃ E53(x) P122(x,y) ⊃ E53(y) P122(x,y) ⊃ P122(y,x) crm:E53_Place
crm:P157_is_at_rest_relative_to owl:ObjectProperty 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 E18 Physical Thing defines its default reference space. The reference space is not spatially limited to the referred thing. For example, a ship determines a reference space in terms of which other ships in its neighbourhood may be described. Larger constellations of matter, such as continental plates, may comprise many physical features that are at rest with them and define the same reference space. Examples: - The spatial extent of the municipality of Athens in 2014 (E53) is at rest relative to The Royal Observatory in Greenwich (E25) - The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22) In First Order Logic: P157(x,y) ⊃ E53(x) P157(x,y) ⊃ E18(y) crm:E18_Physical_Thing
crm:P167i_was_place_of owl:ObjectProperty crm:E93_Presence
crm:P26i_was_destination_of owl:ObjectProperty crm:E9_Move
crm:P27i_was_origin_of owl:ObjectProperty crm:E9_Move
crm:P53i_is_former_or_current_location_of owl:ObjectProperty crm:E18_Physical_Thing
crm:P54i_is_current_permanent_location_of owl:ObjectProperty crm:E19_Physical_Object
crm:P55i_currently_holds owl:ObjectProperty crm:E19_Physical_Object
crm:P59i_is_located_on_or_within owl:ObjectProperty crm:E18_Physical_Thing
crm:P74i_is_current_or_former_residence_of owl:ObjectProperty crm:E39_Actor
crm:P7i_witnessed owl:ObjectProperty crm:E4_Period
crm:P87_is_identified_by owl:ObjectProperty Scope note: This property identifies an E53 Place using an E44 Place Appellation. Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc. Examples: - the location of the Duke of Wellington's House (E53) is identified by "No 1 London" (E45) crm:E44_Place_Appellation
crm:P89_falls_within owl:ObjectProperty Scope note: This property identifies an instance of E53 Place that falls wholly within the extent of another E53 Place. It addresses spatial containment only, and does not imply any relationship between things or phenomena occupying these places. Examples: - the area covered by the World Heritage Site of Stonehenge (E53) falls within the area of Salisbury Plain (E53) In First Order Logic: P89(x,y) ⊃ E53(x) P89(x,y) ⊃ E53(y) crm:E53_Place
crm:P89i_contains owl:ObjectProperty crm:E53_Place
From class crm:E1_CRM_Entity
crm:P3_has_note owl:DatatypeProperty Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" (E62) has type Condition (E55) In First Order Logic: P3(x,y) ⊃ E1(x) P3(x,y) ⊃ E62(y) P3(x,y,z) ⊃ [P3(x,y) ∧ E55(z)] Properties: P3.1 has type: E55 Type owl:Thing
crm:P129i_is_subject_of owl:ObjectProperty crm:E89_Propositional_Object
crm:P136i_supported_type_creation owl:ObjectProperty crm:E83_Type_Creation
crm:P137_exemplifies owl:ObjectProperty Scope note: This property allows an item to be declared as a particular example of an E55 Type or taxon 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 Type Creation (E83) itself, but selected in a later phase. Examples: - Object BM000098044 of the Clayton Herbarium (E20) exemplifies Spigelia marilandica (L.) L. (E55) in the taxonomic role lectotype In First Order Logic: P137(x,y) ⊃ E1(x) P137(x,y) ⊃ E55(y) P137(x,y,z) ⊃ [P137(x,y) ∧ E55(z)] P137(x,y) ⊃ P2(x,y) Properties: P137.1 in the taxonomic role: E55 Type crm:E55_Type
crm:P138i_has_representation owl:ObjectProperty crm:E36_Visual_Item
crm:P140i_was_attributed_by owl:ObjectProperty crm:E13_Attribute_Assignment
crm:P141i_was_assigned_by owl:ObjectProperty crm:E13_Attribute_Assignment
crm:P15i_influenced owl:ObjectProperty crm:E7_Activity
crm:P17i_motivated owl:ObjectProperty crm:E7_Activity
crm:P1_is_identified_by owl:ObjectProperty 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. Examples: - the capital of Italy (E53) is identified by "Rome" (E48) - text 25014-32 (E33) is identified by "The Decline and Fall of the Roman Empire" (E35) In First Order Logic: P1(x,y) ⊃ E1(x) P1(x,y) ⊃ E41(y) crm:E41_Appellation
crm:P2_has_type owl:ObjectProperty Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) In First Order Logic: P2(x,y) ⊃ E1(x) P2(x,y) ⊃ E55(y) crm:E55_Type
crm:P39i_was_measured_by owl:ObjectProperty crm:E16_Measurement
crm:P41i_was_classified_by owl:ObjectProperty crm:E17_Type_Assignment
crm:P62i_is_depicted_by owl:ObjectProperty crm:E24_Physical_Man-Made_Thing
crm:P67i_is_referred_to_by owl:ObjectProperty crm:E89_Propositional_Object
crm:P70i_is_documented_in owl:ObjectProperty crm:E31_Document
crm:P71i_is_listed_in owl:ObjectProperty crm:E32_Authority_Document
From class owl:Thing
crm:P14i_performed owl:ObjectProperty crm:E7_Activity
crm:P165i_is_incorporated_in owl:ObjectProperty owl:Thing
crm:P22i_acquired_title_through owl:InverseFunctionalProperty crm:E8_Acquisition
crm:P23i_surrendered_title_through owl:ObjectProperty crm:E8_Acquisition
crm:P28i_surrendered_custody_through owl:ObjectProperty crm:E10_Transfer_of_Custody
crm:P29i_received_custody_through owl:ObjectProperty crm:E10_Transfer_of_Custody
crm:P48_has_preferred_identifier owl:ObjectProperty Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier "OXCMS:2001.1.32" (E42) In First Order Logic: P48(x,y) ⊃ E1(x) P48(x,y) ⊃ E42(y) P48(x,y) ⊃ P1(x,y) crm:E42_Identifier
crm:P50i_is_current_keeper_of owl:ObjectProperty crm:E18_Physical_Thing
crm:P52i_is_current_owner_of owl:ObjectProperty crm:E18_Physical_Thing

Implementation

@prefix crm: <http://www.cidoc-crm.org/cidoc-crm/> .
@prefix ecrm: <http://erlangen-crm.org/current/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

crm:E53_Place a owl:Class ;
    rdfs:label "E53 Place"@en ;
    rdfs:comment """Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.

The instances of E53 Place are usually determined by reference to the position of "immobile" objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.

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

Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.

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

In First Order Logic:
E53(x) ⊃ E1(x)"""@en ;
    rdfs:subClassOf [ a owl:Restriction ;
            owl:maxCardinality "1"^^xsd:nonNegativeInteger ;
            owl:onProperty crm:P59i_is_located_on_or_within ],
        crm:E1_CRM_Entity ;
    owl:equivalentClass ecrm:E53_Place ;
    skos:notation "E53"^^xsd:string .