http://www.cidoc-crm.org/cidoc-crm/E55_Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM's interface to domain specific ontologies and thesauri. These can be represented in the 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). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
In First Order Logic:
E55(x) ⊃ E28(x)
Instances of crm:E55_Type can have the following properties:
PROPERTY | TYPE | DESCRIPTION | RANGE |
---|---|---|---|
From class crm:E55_Type | |||
crm:P101i_was_use_of | owl:ObjectProperty | crm:E70_Thing | |
crm:P103i_was_intention_of | owl:ObjectProperty | crm:E71_Man-Made_Thing | |
crm:P125i_was_type_of_object_used_in | owl:ObjectProperty | crm:E7_Activity | |
crm:P127_has_broader_term | owl:ObjectProperty | Scope note: This property identifies a super-Type to which an E55 Type is related. It allows Types to be organised into hierarchies. This is the sense of "broader term generic (BTG)" as defined in ISO 2788 Examples: - dime (E55) has broader term coin (E55) In First Order Logic: P127(x,y) ⊃ E55(x) P127(x,y) ⊃ E55(y) | crm:E55_Type |
crm:P127i_has_narrower_term | owl:ObjectProperty | crm:E55_Type | |
crm:P135i_was_created_by | owl:ObjectProperty | crm:E83_Type_Creation | |
crm:P137i_is_exemplified_by | owl:ObjectProperty | crm:E1_CRM_Entity | |
crm:P150_defines_typical_parts_of | owl:ObjectProperty | Scope note: The property “broaderPartitive” 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. This is the sense of "broader term partitive (BTP)" as defined in ISO 2788 and “broaderPartitive” in SKOS. Examples: - Car motors (E55) defines typical parts of cars (E55) In First Order Logic: P150(x,y) ⊃ (E55 Type) P150(x,y) ⊃ E55(y) | crm:E55_Type |
crm:P150i_defines_typical_wholes_for | owl:ObjectProperty | crm:E55_Type | |
crm:P21i_was_purpose_of | owl:ObjectProperty | crm:E7_Activity | |
crm:P2i_is_type_of | owl:ObjectProperty | crm:E1_CRM_Entity | |
crm:P32i_was_technique_of | owl:ObjectProperty | crm:E7_Activity | |
crm:P42i_was_assigned_by | owl:ObjectProperty | crm:E17_Type_Assignment | |
From class crm:E28_Conceptual_Object | |||
crm:P149_is_identified_by | owl:ObjectProperty | Scope note: This property identifies an instance of E28 Conceptual Object using an instance of E75 Conceptual Object Appellation. Examples: - The German edition of the CIDOC CRM (E73) is identified by ISBN 978-3-00-030907-6 (E75) In First Order Logic: P149(x,y) ⊃ E28(x) P149(x,y) ⊃ E75(y) P149(x,y) ⊃ P1(x,y) | crm:E75_Conceptual_Object_Appellation |
crm:P94i_was_created_by | owl:ObjectProperty | crm:E65_Creation | |
From class crm:E71_Man-Made_Thing | |||
crm:P102_has_title | owl:ObjectProperty | Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. 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 man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - the first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) In First Order Logic: P102(x,y) ⊃ E71(x) P102(x,y) ⊃ E35(y) P102(x,y,z) ⊃ [P102(x,y) ∧ E55(z)] P102(x,y) ⊃ P1(x,y) Properties: P102.1 has type: E55 Type | crm:E35_Title |
crm:P103_was_intended_for | owl:ObjectProperty | Scope note: This property links an instance of E71 Man-Made Thing to an E55 Type of usage. It creates a property between specific man-made things, both physical and immaterial, to Types of intended methods and techniques of use. Note: A link between specific man-made things and a specific use activity should be expressed using P19 was intended use of (was made for). Examples: - this plate (E22) was intended for being destroyed at wedding reception (E55) In First Order Logic: P103(x,y) ⊃ E71(x) P103(x,y) ⊃ E55(y) | crm:E55_Type |
crm:P19i_was_made_for | owl:ObjectProperty | crm:E7_Activity | |
From class crm:E70_Thing | |||
crm:P101_had_as_general_use | owl:ObjectProperty | Scope note: This property links an instance of E70 Thing to an E55 Type of usage. It allows the relationship between particular things, both physical and immaterial, and general methods and techniques of use to be documented. Thus it can be asserted that a baseball bat had a general use for sport and a specific use for threatening people during the Great Train Robbery. Examples: - Tony Gill's Ford Mustang (E22) had as general use transportation (E55) In First Order Logic: 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) | crm:E55_Type |
crm:P130_shows_features_of | owl:ObjectProperty | Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a shortcut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) 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,y) ⊃ P130(y,x) Properties: P130.1 kind of similarity: E55 Type | crm:E70_Thing |
crm:P130i_features_are_also_found_on | owl:ObjectProperty | crm:E70_Thing | |
crm:P16i_was_used_for | owl:ObjectProperty | crm:E7_Activity | |
crm:P43_has_dimension | owl:ObjectProperty | Scope note: This property records a E54 Dimension of some E70 Thing. It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. An instance of E54 Dimension is specific to an instance of E70 Thing. Examples: - silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60) In First Order Logic: P43(x,y) ⊃ E70(x) P43(x,y) ⊃ E54(y) | crm:E54_Dimension |
From class crm:E77_Persistent_Item | |||
crm:P123i_resulted_from | owl:ObjectProperty | crm:E81_Transformation | |
crm:P124i_was_transformed_by | owl:ObjectProperty | crm:E81_Transformation | |
crm:P12i_was_present_at | owl:ObjectProperty | crm:E5_Event | |
crm:P92i_was_brought_into_existence_by | owl:ObjectProperty | crm:E63_Beginning_of_Existence | |
crm:P93i_was_taken_out_of_existence_by | owl:ObjectProperty | crm:E64_End_of_Existence | |
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:E55_Type a owl:Class ;
rdfs:label "E55 Type"@en ;
rdfs:comment """Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM's interface to domain specific ontologies and thesauri. These can be represented in the 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). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
In First Order Logic:
E55(x) ⊃ E28(x)"""@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:maxCardinality "1"^^xsd:nonNegativeInteger ;
owl:onProperty crm:P135i_was_created_by ],
crm:E28_Conceptual_Object ;
owl:equivalentClass ecrm:E55_Type ;
skos:notation "E55"^^xsd:string .