OntoME

Domain:

E1 CRM Entity

Range:

E55 Type

Subproperty of:

• Thing Thing → topObjectProperty → Thing Thing

Superproperty of:

• E1 CRM Entity → P137 exemplifies → E55 Type
• histC8 Geographical Place → histP8 has geographical place type → histC9 Geographical place type
• histC2 Geographical localisation → histP7 has localisation type → histC16 Geographical localisation type
• F4 Manifestation Singleton → histP20 has manifestation singleton type → histC17 Manifestation singleton type
• F3 Manifestation Product Type → histP21 has type of manifestation product type → histC19 Type of manifestation product type
• F2 Expression → histP22 has expression type → histC21 Expression type
• socE Social Bond → socP9 has role → socE Social Role
• KnUn Knowledge Unit → TyRo98 est de type (type) → GenAbOb Generic Abstract Object
• geovC5 Expression portion → geovP9 has expression portion type → geovC6 Expression portion type
• T2 Entering → L1 has entering type → T22 Entering Type
• T7 Textile Fabric → L2 has textile fabric type → T23 Textile Fabric Type
• T15 Thread → L3 has thread type → T28 Thread Type
• T3 Spinning → L4 has spinning type → T27 Spinning Type
• T20 Twist → L5 has twist type → T29 Twist Type
• T16 Warp → L6 has warp type → T30 Warp Type
• T5 Warping → L13 has warping type → T31 Warping Type
• T17 Weft → L15 has weft type → T33 Weft 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)
• P2(x,y) ⊃ topObjectProperty(x,y)