OntoME

Domain:

E1 CRM Entity

Range:

E55 Type

Superproperty of:

• E1 CRM Entity → P137 exemplifies (is exemplified by) → E55 Type
• C13 Geographical Place → P20 has geographical place type → C14 Geographical Place Type
• C15 Geographical Location (Temporal entity) → P19 has location type → C16 Geographical Location type
• F4 Manifestation Singleton → P6 has manifestation singleton type → C10 Manifestation singleton type
• F3 Manifestation Product Type → P5 has type of manifestation product type → C8 Type of manifestation product type
• F2 Expression → P4 has expression type → C6 Expression type
• C17 Built work → P9 has built work type → C18 Built work type
• E74 Group → P7 has group type → C9 Group type
• E5 Event → P8 has event type (is event type of) → C3 Event type
• C5 Membership → P3 has membership type → C6 Membership type
• C11 Appellation in a language (Temporal Entity) → P14 has appellation for language type (is appellation for language type of) → C12 Appellation in a language type
• C3 Relationship → P16 has relationship type (is relationship type of) → C4 Relationship type
• C9 Union → P21 has type of union (is type of union of) → C10 Type of union
• E22 Man-Made Object → P1 has type (is type of man-made object) → C4 Man-Made Object Type
• C20 Right Holding → P32 has right holding type (is right holding type of) → C21 Right holding type
• C5 Step → P12 has step type (is step type of) → C8 Step type
• C4 Procedure → P13 has procedure type (is procedure type) → C7 Procedure type
• C23 Use → P29 has use type (is use type of) → C24 Use type
• F5 Item → R7 is example of (has example) → F3 Manifestation Product Type

Quantification:

0,n:0,n

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:

No example yet.

In First Order Logic:

• P2(x,y) ⊃ E1(x)
• P2(x,y) ⊃ E55(y)