This HTML5 document contains 7 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
skoshttp://www.w3.org/2004/02/skos/core#
rdfshttp://www.w3.org/2000/01/rdf-schema#
ecrmhttp://erlangen-crm.org/current/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
ecrm:P2_has_type
rdf:type
owl:ObjectProperty
owl:inverseOf
ecrm:P2i_is_type_of
rdfs:label
P2 has type
rdfs:domain
ecrm:E1_CRM_Entity
rdfs:range
ecrm:E55_Type
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)
skos:notation
P2