Concept Search
Showing 2710 results:
P37 assigned
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:
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned 232 (E42)
Type: Property
Belongs to version: Version 5.0.1
P37 assigned
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:
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned “232” (E42)
Type: Property
Belongs to version: Version 6.1
P37 assigned
Quantification: many to many (0,n:0,n)
Scope note:
This property records the identifier that was assigned to an item in an instance of P37 Identifier Assignment activity.
The same identifier may be assigned on more than one occasion.
An Identifier might be created prior to an assignment.
Examples:
- 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned “232” (E42) (fictitious)
Type: Property
Belongs to version: version 7.1
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
Type: Property
Belongs to version: Version 6.2.2
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
Type: Property
Belongs to version: Version 5.0.2
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
Type: Property
Belongs to version: Version 6.2
P38 deassigned
Quantification: many to many (0,n,0,n)
Scope note:
This property records the identifier that was deassigned from an object.
Deassignment of an identifier may be necessary when an object is taken out of an inventory, a new numbering system is introduced or objects are merged or split up.
The same identifier may be deassigned on more than one occasion.
Examples:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned 232 (E42)
Type: Property
Belongs to version: Version 4.1
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
Type: Property
Belongs to version: Version 6.0
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
Type: Property
Belongs to version: Version 6.2.1
P38 deassigned
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.
De-assignment 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:
- The identifier assignment on 31st July 2001 of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42). (fictitious)
Type: Property
Belongs to version: version 7.1.1
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
Type: Property
Belongs to version: Version 5.1.2
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned 232 (E42)
Type: Property
Belongs to version: Version 5.0.1
P38 deassigned
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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42)
Type: Property
Belongs to version: Version 6.1
P38 deassigned
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.
De-assignment 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:
- 31 July 2001 Identifier Assignment of the silver cup OXCMS:2001.1.32 (E15) deassigned “232” (E42) (fictitious)
Type: Property
Belongs to version: version 7.1
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.2.2
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 5.0.2
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.2
P39 measured
Quantification: many to one,necessary (1,1,0,n)
Scope note:
This property records the E70 Stuff that was the subject of an instance of E16 Measurement
Event.Stuff may be measured more than once. Both material and immaterial stuff may be measured, e.g. the number of words in a text.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 4.1
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.0
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.2.1
P39 measured
Quantification: many to one,necessary (1,1,0,n)
Scope note:
This property associates an instance of E16 Measurement with the instance of E18 Physical Thing upon which it acted. The instance of E16 Measurement is specific to the measured object. An instance of E18 Physical Thing may be measured more than once with different results, constituting different instances of E16 Measurement.
Examples:
- The measurement of the height of silver cup 232 on 31st of August 1997 (E16) measured silver cup 232 (E22). (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) measured the “Schoeninger Speer II” (E22). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niedersachsen, Germany, in 1995. See also, E16 Measurement.] (Kouwenhoven, 1997)
Type: Property
Belongs to version: version 7.1.1
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 5.1.2
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 5.0.1
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.1
P39 measured
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:
- 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) 31 August 1997 measurement of height of silver cup 232 (E16) measured silver cup 232 (E22) (fictitious)
Type: Property
Belongs to version: version 7.1
P4 has time-span
Quantification: many to one,necessary,dependent (1,1,1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity.
The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active, which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span, but there may exist alternative opinions about it, which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
Type: Property
Belongs to version: Version 5.0.2
P4 has time-span
Quantification: many to one, necessary, dependent (1,1:1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity. The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span but there may exist alternative opinions about it which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
Type: Property
Belongs to version: Version 6.2
P4 has time-span
Quantification: many to one,necessary,dependent (1,1,1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity.
The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active, which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span, but there may exist alternative opinions about it, which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52), ongoing throughout 11 February 1945 (E61)
Type: Property
Belongs to version: Version 4.1
P4 has time-span
Quantification: many to one, necessary, dependent (1,1:1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity. The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span but there may exist alternative opinions about it which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
Type: Property
Belongs to version: Version 6.2.1
P4 has time-span
Quantification: many to one, necessary, dependent (1,1:1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity. The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span but there may exist alternative opinions about it which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
Type: Property
Belongs to version: Version 6.0
P4 has time-span
Quantification: many to one,necessary (1,1,0,n)
Scope note:
This property associates an instance of E2 Temporal Entity with the instance of E52 Time-Span during which it was on-going. The associated instance of E52 Time-Span is understood as the real time-span during which the phenomena making up the temporal entity instance were active. More than one instance of E2 Temporal Entity may share a common instance of E52 Time-Span only if they come into being and end being due to identical declarations or events.
Examples:
- The Yalta Conference (E7) has time-span Yalta Conference time-span (E52). (Harbutt, 2010)
Type: Property
Belongs to version: version 7.1.1
P4 has time-span
Quantification: many to one, necessary, dependent (1,1:1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity. The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span but there may exist alternative opinions about it which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
Type: Property
Belongs to version: Version 5.1.2
P4 has time-span
Quantification: many to one,necessary,dependent (1,1,1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity.
The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active, which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span, but there may exist alternative opinions about it, which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52), ongoing throughout 11 February 1945 (E61)
Type: Property
Belongs to version: Version 5.0.1
P4 has time-span
Quantification: many to one, necessary, dependent (1,1:1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity. The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span but there may exist alternative opinions about it which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
Type: Property
Belongs to version: Version 6.1
P4 has time-span
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property associates an instance of E2 Temporal Entity with the instance of E52 Time-Span during which it was on-going. The associated instance of E52 Time-Span is understood as the real time-span during which the phenomena making up the temporal entity instance were active. More than one instance of E2Temporal Entity may share a common instance of E52 Time-Span only if they come into being and end being due to identical declarations or events.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52) (Harbutt, 2010)
Type: Property
Belongs to version: version 7.1
P4 has time-span
Quantification: many to one, necessary, dependent (1,1:1,n)
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity. The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span but there may exist alternative opinions about it which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
Type: Property
Belongs to version: Version 6.2.2
P40 observed dimension
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 6.2.2
P40 observed dimension
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 5.0.2
P40 observed dimension
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 6.2
P40 observed dimension
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the dimension that was observed in a E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Stuff. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured stuff does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 4.1
P40 observed dimension
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 6.0
P40 observed dimension
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 6.2.1
P40 observed dimension
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- The measurement of the height of silver cup 232 on 31st of August 1997 (E16) observed dimension silver cup 232 height (E54). [which has unit mm (E58), has value 224 (E60) ] (fictitious)
- The carbon 14 dating of the “Schoeninger Speer II” in 1996 (E16) observed dimension the carbon 14 based temporal distance from 1996 to the growth of the wood of the “Schoeninger Speer II” (E60). [The carbon 14 dating of an approximately 400.000 year old complete Old Palaeolithic wooden spear found in Schoeningen, Niederachsen, Germany, in 1995. See also: E16 Measurement.] (Kouwenhoven, 1997)
Type: Property
Belongs to version: version 7.1.1
P40 observed dimension
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 5.1.2
P40 observed dimension
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 5.0.1
P40 observed dimension
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 6.1
P40 observed dimension
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the dimension that was observed in an E16 Measurement Event.
E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.
Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
Examples:
- 31 August 1997 measurement of height of silver cup 232 (E16) observed dimension silver cup 232 height (E54) has unit mm (E58), has value 224 (E60) (fictitious)
Type: Property
Belongs to version: version 7.1
P41 classified
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.2.2
P41 classified
Quantification: many to one,necessary (1,1,0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 5.0.2
P41 classified
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.2
P41 classified
Quantification: many to one,necessary (1,1,0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 4.1
P41 classified
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.0
P41 classified
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.2.1
P41 classified
Quantification: many to one,necessary (1,1,0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- The classification of silver cup 232 on 31st of August 1997 (E17) classified silver cup 232 (E22). (fictitious)
Type: Property
Belongs to version: version 7.1.1
P41 classified
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 5.1.2
P41 classified
Quantification: many to one,necessary (1,1,0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 5.0.1
P41 classified
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)
Type: Property
Belongs to version: Version 6.1
P41 classified
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property records the item to which a type was assigned in an E17 Type Assignment activity.
Any instance of a CIDOC CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM EntitythroughP41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
Examples:
- 31 August 1997 classification of silver cup 232 (E17) classified silver cup 232 (E22)(fictitious)
Type: Property
Belongs to version: version 7.1
P42 assigned
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 6.2.2
P42 assigned
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 5.0.2
P42 assigned
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 6.2
P42 assigned
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 4.1
P42 assigned
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 6.0
P42 assigned
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 6.2.1
P42 assigned
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- The classification of silver cup 232 on 31st August 1997 (E17) assigned goblet (E55). (fictitious)
Type: Property
Belongs to version: version 7.1.1
P42 assigned
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 5.1.2
P42 assigned
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 5.0.1
P42 assigned
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55)
Type: Property
Belongs to version: Version 6.1
P42 assigned
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property records the type that was assigned to an entity by an E17 Type Assignment activity.
Type assignment events allow a more detailed path from E1 CRM EntitythroughP41i was classified by, E17 Type Assignment, P42 assigned, to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of).
For example, a fragment of an antique vessel could be assigned the type “attic red figured belly handled amphora” by expert A. The same fragment could be assigned the type “shoulder handled amphora” by expert B.
A Type may be intellectually constructed independent from assigning an instance of it.
Examples:
- 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55) (fictitious)
Type: Property
Belongs to version: version 7.1
P43 has dimension
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
Type: Property
Belongs to version: Version 6.2.2
P43 has dimension
Quantification: one to many,dependent (0,n,1.1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
Type: Property
Belongs to version: Version 5.0.2
P43 has dimension
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
Type: Property
Belongs to version: Version 6.2
P43 has dimension
Quantification: one to many,dependent (0,n,1.1)
Scope note:
This property records a E54 Dimension of some E70 Stuff.
It is a shortcut of the more fully developed path from E70 Stuff through P39 measured (was measured by), E16 Measurement Event P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Stuff.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 4.1
P43 has dimension
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
Type: Property
Belongs to version: Version 6.0
P43 has dimension
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
Type: Property
Belongs to version: Version 6.2.1
P43 has dimension
Quantification: one to many,dependent (0,n,1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
In the case that the recorded property is a result of a measurement of an instance of E18 Physical Thing, this property is a shortcut of the more fully developed path from E18 Physical Thing through P39i was measured by, E16 Measurement, P40 observed dimension to E54 Dimension.
It offers no information about how and when an E54 Dimension was established, nor by whom. Knowledge about an instance of E54 Dimension need not be the result of a measurement; it may be the result of evaluating data or other information, which should be documented as an instance of E13 Attribute Assignment.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- Silver cup 232 (E22) has dimension height of silver cup 232 (E54). [which has unit (P91) mm (E58), has value (P90) 224 (E60) ] (fictitious)
Type: Property
Belongs to version: version 7.1.1
P43 has dimension
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
Type: Property
Belongs to version: Version 5.1.2
P43 has dimension
Quantification: one to many,dependent (0,n,1.1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit mm (E58), has value 224 (E60)
Type: Property
Belongs to version: Version 5.0.1
P43 has dimension
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
Type: Property
Belongs to version: Version 6.1
P43 has dimension
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records a E54 Dimension of some E70 Thing.
This property is a shortcut of the more fully developed path from E70 ThingthroughP39i was measured by, E16 Measurement, P40 observed dimension, toE54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60) (fictitious)
Type: Property
Belongs to version: version 7.1
P44 has condition
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 6.2.2
P44 has condition
Quantification: one to many,dependent (0,n,1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 5.0.2
P44 has condition
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 6.2
P44 has condition
Quantification: one to many,dependent (0,n,1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Stuff.
It is a shortcut of the more fully developed path from E18 Physical Stuff through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Stuff.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 4.1
P44 has condition
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 6.0
P44 has condition
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 6.2.1
P44 has condition
Quantification: one to many,dependent (0,n,1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
This property is a shortcut of the more fully developed path from E18 Physical Thing through P34i was assessed by, E14 Condition Assessment, P35 has identified to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of E18 Physical Thing.
Examples:
- Silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3). [which has type (P2) oxidation traces (E55)] (fictitious)
Type: Property
Belongs to version: version 7.1.1
P44 has condition
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 5.1.2
P44 has condition
Quantification: one to many,dependent (0,n,1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 5.0.1
P44 has condition
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records an E3 Condition State for some E18 Physical Thing.
It is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of Physical Thing.
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type oxidation traces (E55)
Type: Property
Belongs to version: Version 6.1
P44 has condition
Quantification: one to many, dependent (0,n:1,1)
Scope note:
This property records an E3 Condition State for someE18 Physical Thing.
This property is a shortcut of the more fully developed path from E18 Physical ThingthroughP34i was assessed by, E14 Condition Assessment, P35 has identified, toE3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom.
An instance of Condition State is specific to an instance of E18 Physical Thing
Examples:
- silver cup 232 (E22) has condition oxidation traces were present in 1997 (E3) has type (P2) oxidation traces (E55) (fictitious)
Type: Property
Belongs to version: version 7.1
P45 consists of
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 6.2.2
P45 consists of
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 5.0.2
P45 consists of
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 6.2
P45 consists of
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Stuff is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 4.1
P45 consists of
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 6.0
P45 consists of
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 6.2.1
P45 consists of
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different materials to be recorded. P45 consists of (is incorporated in) refers here to observed material as opposed to the consumed raw material.
A material, such as a theoretical alloy, may not have any physical instances.
Examples:
- Silver cup 232 (E22) consists of silver (E57). (fictitious)
Type: Property
Belongs to version: version 7.1.1
P45 consists of
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 5.1.2
P45 consists of
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.
All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material.
A Material, such as a theoretical alloy, may not have any physical instances.
Examples:
- silver cup 232 (E22) consists of silver (E57)
Type: Property
Belongs to version: Version 5.0.1