Cidoc conceptual Reference Model
CIDOC CRM Property Declarations
Download 2.39 Mb.
|
- Navigate this page:
- P1 is identified by (identifies)
- P2 has type (is type of)
- P3 has note
- P4 has time-span (is time-span of)
CIDOC CRM Property DeclarationsThe properties of the CRM are comprehensively declared in this section using the following format:
The line “Examples:” provides illustrative examples showing how the property should be used. P1 is identified by (identifies)Domain: E1 CRM Entity Range: E41 Appellation Superproperty of: E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier E52 Time-Span. P78 is identified by (identifies): E49 Time Appellation E53 Place. P87 is identified by (identifies): E44 Place Appellation E71 Man-Made Thing. P102 has title (is title of): E35 Title E39 Actor. P131 is identified by (identifies): E82 Actor Appellation E28 Conceptual Object.P149 is identified by (identifies): E75 Conceptual Object Appellation Quantification: many to many (0,n:0,n)
Examples:
In First Order Logic: P1(x,y) ⊃ E1(x) P1(x,y) ⊃ E41(y) P2 has type (is type of)Domain: E1 CRM Entity Range: E55 Type Superproperty of. E1 CRM Entity.P137 exemplifies (is exemplified by):E55 Type Quantification: many to many (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: “enquiries@cidoc-crm.org” (E51) has type e-mail address (E55)
P2(x,y) ⊃ E1(x) P2(x,y) ⊃ E55(y)
Range: E62 String Superproperty of: E52 Time-Span. P79 beginning is qualified by: E62 String E52 Time-Span. P80 end is qualified by: E62 String Quantification: one to many (0,n:0,1)
Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. “construction”, “decoration” etc. An item may have many notes, but a note is attached to a specific item. Examples:
In First Order Logic: P3(x,y) ⊃ E1(x) P3(x,y) ⊃ E62(y) P3(x,y,z) ⊃ [P3(x,y) ∧ E55(z)]
Range: E52 Time-Span Quantification: many to one, necessary, dependent (1,1:1,n)
Examples:
In First Order Logic: P4(x,y) ⊃ E2(x) P4(x,y) ⊃ E52(y) Directory: docs docs -> Application for acem docs -> Observational Assessment of Teaching Practices Teaching Assessment Initiative Proposal Submitted to The Teachers for a New Era project docs -> Traditional British values docs -> From Warfighters to Crimefighters: The Origins of Domestic Police Militarization docs -> Borzoi Club of America Register of Merit Program I. What is a Register Of Merit docs -> Protecting the rights of the child in the context of migration docs -> United Nations E/C. 12/Esp/5 docs -> 9th May 1950 the schuman declaration docs -> Getting To Outcomes® in Services for Homeless Veterans 10 Steps for Achieving Accountability Download 2.39 Mb. Share with your friends:
|