Cidoc conceptual Reference Model
P32 used general technique (was technique of)
Download 2.39 Mb.
|
- Navigate this page:
- P33 used specific technique (was used by)
- P34 concerned (was assessed by)
- P35 has identified (was identified by)
- P37 assigned (was assigned by)
- P38 deassigned (was deassigned by)
- P39 measured (was measured by)
P32 used general technique (was technique of)Domain: E7 Activity Range: E55 Type Subproperty of: E7 Activity. P125 used object of type (was type of object used in): E55 Type Superproperty of: Quantification: many to many (0,n:0,n) Scope note: This property identifies the technique or method that was employed in an activity. These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques or methods such as embroidery, oil-painting, carbon dating, etc. Specific documented techniques should be described as instances of E29 Design or Procedure. This property identifies the technique that was employed in an act of modification. Examples:
In First Order Logic: P32(x,y) ⊃ E7(x) P32(x,y) ⊃ E55(y) P32(x,y) ⊃ P125(x,y)
Range: E29 Design or Procedure Subproperty of: E7 Activity. P16 used specific object (was used for): E70 Thing Quantification: many to many (0,n:0,n) Scope note: This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. Typical examples would include intervention plans for conservation or the construction plans of a building Examples:
In First Order Logic: P33(x,y) ⊃ E7(x) P33(x,y) ⊃ E29(y) P33(x,y) ⊃ P16(x,y)
Range: E18 Physical Thing Subproperty of: E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the E18 Physical Thing that was assessed during an E14 Condition Assessment activity. Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the E18 Physical Thing does not need to be present or extant. Examples:
In First Order Logic: P34(x,y) ⊃ E14(x) P34(x,y) ⊃ E18(y) P34(x,y) ⊃ P140(x,y)
Range: E3 Condition State Subproperty of: E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity Quantification: many to many, necessary (1,n:0,n) Scope note: This property identifies the E3 Condition State that was observed in an E14 Condition Assessment activity. Examples:
In First Order Logic: P35(x,y) ⊃E14(x) P35(x,y) ⊃ E3(y) P35(x,y) ⊃ P141(x,y)
Range: E42 Identifier Subproperty of: E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity Quantification: many to many (0,n:0,n) Scope note: This property records the identifier that was assigned to an item in an Identifier Assignment activity. The same identifier may be assigned on more than one occasion. An Identifier might be created prior to an assignment. Examples:
In First Order Logic: P37(x,y) ⊃ E15(x) P37(x,y) ⊃ E42(y) P37(x,y) ⊃ P141(x,y)
Range: E42 Identifier Subproperty of: E13 Attribute Assignment. P141 assigned (was assigned by): E1 CRM Entity Quantification: many to many (0,n:0,n) Scope note: This property records the identifier that was deassigned from an instance of E1 CRM Entity. Deassignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. The same identifier may be deassigned on more than one occasion. Examples:
In First Order Logic: P38(x,y) ⊃ E15(x) P38(x,y) ⊃ E42(y) P38(x,y) ⊃ P141(x,y)
Range: E1 CRM Entity Subproperty of: E13 Attribute Assignment. P140 assigned attribute to (was attributed by): E1 CRM Entity Quantification: many to one, necessary (1,1:0,n) Scope note: This property associates an instance of E16 Measurement with the instance of E1 CRM Entity to which it applied. An instance of E1 CRM Entity may be measured more than once. Material and immaterial things and processes may be measured, e.g. the number of words in a text, or the duration of an event. Examples:
In First Order Logic: P39(x,y) ⊃ E16(x) P39(x,y) ⊃ E1(y) P39(x,y) ⊃ P140(x,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:
|