Domain:

crm:E1 CRM Entity

Range:

crm:E55 Type

Quantification:

0,n:0,n

Superproperty of:

• crm:E1 CRM Entity → crm:P137 exemplifies (is exemplified by) → crm:E55 Type
• crm:E24 Physical Man-Made Thing → crm-sup:P1 has type (is type of physical human-made thing) → crm-sup:C4 Physical Human-Made Thing Type
• frbroo:F5 Item → crm-sup:P2 has item type (is item type of) → crm-sup:C5 Item Type
• frbroo:F2 Expression → crm-sup:P4 has expression type (is expression type of) → crm-sup:C6 Expression Type
• frbroo:F3 Manifestation Product Type → crm-sup:P5 has type of manifestation product type (is type of) → crm-sup:C8 Type of manifestation product type
• frbroo:F4 Manifestation Singleton → crm-sup:P6 has manifestation singleton type (is manifestation singleton type of) → crm-sup:C10 Manifestation Singleton Type
• sdh:C17 Construction → crm-sup:P9 has construction type (is construction type of) → sdh:C18 Construction Type
• crm:E7 Activity → crm-sup:P19 has activity type (is type of activity) → crm-sup:C3 Activity Type
• crm:E42 Identifier → crm-sup:P19 has identifier type (is identifier type of) → crm-sup:C24 Identifier Type
• crm:E73 Information Object → crm-sup:P26 has information object type (is type of) → crm-sup:C28 Information Object Type
• frbroo:F31 Performance → crm-sup:P27 has performance type (is type of) → crm-sup:C29 Performance Type
• crm:E21 Person → crm-sup:P33 has person type (is person type of) → crm-sup:C36 Person Type
• frbroo:F5 Item → frbroo:R7 is example of (has example) → frbroo:F3 Manifestation Product Type
• sdh:C11 Appellation in a Language → sdh:P14 has appellation for language type (is appellation for language type of) → sdh:C12 Appellation in a Language Type
• sdh:C23 Use → sdh:P29 has use type (is use type of) → sdh:C24 Use type
• sdh:C41 Relative Location of a Physical Thing → sdh:P46 has location reason (is reason of location) → sdh:C35 Location Reason
• crm:E5 Event → sdh:P47 has event type (is event type of) → sdh:C34 Event Type
• sdh:C46 Intentional Expression → sdh:P48 has intentional expression identifying type (is identifying type of) → sdh:C47 Intentional Expression Type
• sdh:C46 Intentional Expression → sdh:P48 has intentional expression identifying type (is identifying type of) → sdh:C47 Intentional Expression Type
• crm:E1 CRM Entity → sdh:P63 has preferred type (is preferred type of) → crm:E55 Type
• sdh-int:C5 Step → sdh-int:P12 has step type (is step type of) → sdh-int:C8 Step Type
• sdh-int:C4 Procedure → sdh-int:P13 has procedure type (is procedure type) → sdh-int:C7 Procedure Type
• sdh-int:C10 Bibliographic Citation → sdh-int:P19 has style (is style of) → sdh-int:C11 Citation Style
• sdh-int:C13 Propositional Datation → sdh-int:P27 has datation type (is type of) → sdh-int:C14 Datation Type
• sdh-so:C5 Membership → sdh-so:P3 has membership type (is membership type of) → sdh-so:C6 Membership Type
• sdh-so:C3 Social Relationship → sdh-so:P16 has relationship type (is relationship type of) → sdh-so:C4 Social Relationship Type
• sdh-so:C18 Persons' Interaction → sdh-so:P21 has type of interaction (is type of) → sdh-so:C10 Type of Persons' Interaction
• sdh-so:C17 Custom or Law → sdh-so:P32 has custom or law type (is type of) → sdh-so:C21 Custom or Law Type
• sdh-so:C12 Actor's Social Role → sdh-so:P50 has social role type (is type of) → sdh-so:C32 Social Role Type
• sdh-so:C28 Legal Location of an Actor → sdh-so:P51 has legal location type (is type of) → sdh-so:C33 Legal Location Type
• sdh-so:C25 Political or Administrative Entity → sdh-so:P71 has political or administrative entity type (is type of) → sdh-so:C42 Political or Administrative Entity Type

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)