crm:P2_has_type

@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:P2_has_type a owl:ObjectProperty ;
    rdfs:label "P2 has type"@en ;
    rdfs:comment """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)"""@en ;
    rdfs:domain crm:E1_CRM_Entity ;
    rdfs:range crm:E55_Type ;
    owl:equivalentProperty ecrm:P2_has_type ;
    owl:inverseOf crm:P2i_is_type_of ;
    skos:notation "P2"^^xsd:string .