http://www.cidoc-crm.org/cidoc-crm/E54_Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter: 26 mm
- weight: 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
In First Order Logic:
E54(x) ⊃ E1(x)
Instances of crm:E54_Dimension can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class crm:E54_Dimension | |||
| crm:P90_has_value | owl:DatatypeProperty | Scope note: This property allows an E54 Dimension to be approximated by an E60 Number primitive. Examples: - height of silver cup 232 (E54) has value 226 (E60) In First Order Logic: P90(x,y) ⊃ E54(x) P90(x,y) ⊃ E60(y) | owl:Thing |
| crm:P40i_was_observed_in | owl:ObjectProperty | crm:E16_Measurement | |
| crm:P43i_is_dimension_of | owl:ObjectProperty | crm:E70_Thing | |
| crm:P83i_was_minimum_duration_of | owl:ObjectProperty | crm:E52_Time-Span | |
| crm:P84i_was_maximum_duration_of | owl:ObjectProperty | crm:E52_Time-Span | |
| crm:P91_has_unit | owl:ObjectProperty | Scope note: This property shows the type of unit an E54 Dimension was expressed in. Examples: - height of silver cup 232 (E54) has unit mm (E58) In First Order Logic: P91(x,y) ⊃ E54(x) P91(x,y) ⊃ E58(y) | crm:E58_Measurement_Unit |
| 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 | |
@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:E54_Dimension a owl:Class ;
rdfs:label "E54 Dimension"@en ;
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 true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter: 26 mm
- weight: 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
In First Order Logic:
E54(x) ⊃ E1(x)"""@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:cardinality "1"^^xsd:nonNegativeInteger ;
owl:onProperty crm:P91_has_unit ],
crm:E1_CRM_Entity ;
owl:equivalentClass ecrm:E54_Dimension ;
skos:notation "E54"^^xsd:string .