Concept Search
Showing 2710 results:
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 4.1
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 6.1
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 5.0.2
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 6.2.2
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 5.1.2
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 6.0
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks, but may also be determined by reference to mobile objects. A Place can be determined by combining a frame of reference and a location with respect to this frame.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for).
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring (fictitious)
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <- [the place between these arrows in one of the reader's paper copy of this document. Each copy constitutes a different place of this spot]
Type: Entity
Belongs to version: version 7.1
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 6.2
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a section of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 5.0.1
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 6.2.1
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks, but may also be determined by reference to mobile objects. A Place can be determined by combining a frame of reference and a location with respect to this frame.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for).
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring (fictitious)
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <- [the place between these two arrows in one of the reader's paper copy of this document. Each copy constitutes a different place of this spot.]
Type: Entity
Belongs to version: version 7.1.1
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a section of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 4.1
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 6.1
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a section of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 5.0.2
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 6.2.2
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 5.1.2
E53 Place
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: “Fish collected at three miles north of the confluence of the Arve and the Rhone”
- here -> <-
Type: Entity
Belongs to version: Version 6.0
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e., by points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the empirical or theoretically derived quantity, including the precision tolerances resulting from the particular method or calculation. The identity of an instance of E54 Dimension depends on the method of its determination because each method may produce different values even when determining comparable qualities. For instance, the wingspan of a bird alive or dead is a different dimension. Thermoluninescence dating and Rehydroxylation [RHX] dating are different dimensions of temporal distance from now, even if they aim at dating the same object. The method of determination should be expressed using the property P2 has type (is type of). Note that simple terms such as “diameter” or “length” are normally insufficient to unambiguously describe a respective dimension. In contrast, “maximum linear extent” may be sufficient.
The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension adequate to the precision of the applied method of determination. If the respective quantity belongs to a non-discrete space according to the laws of physics, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that comparability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension, as appropriate.
Examples:
- The weight of the Luxor Obelisk [250 metric tons]
- The vertical height of the statue of David by Michaelangelo [5.17 metres]
- The weight of the Great Star of Africa diamond [530.2 carats]
- The calibrated C14 date for the Shroud of Turin [AD1262-1312, 1303-1384]
- The horizontal diameter of the Stonehenge Sarcen Circle [33 metres]
- The length of the sides of the Great Pyramid at Giza [755.9 feet]
- Christie’s hammer price for “Vase with Fifteen Sunflowers” in British Pounds (E97)
- The duration of the time span of the Battle of Issos/Issus on 15th November 333 B.C.E. [less than 12 hours] (Howard, 2012)
- Christie’s hammer price for Vincent van Gogh's "Still Life: Vase with Fifteen Sunflowers" in London on 1987/03/30 (E97) [GBP 24.75m]
Type: Entity
Belongs to version: version 7.1
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 6.2
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 5.0.1
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 6.2.1
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e., by points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the empirical or theoretically derived quantity, including the precision tolerances resulting from the particular method or calculation. The identity of an instance of E54 Dimension depends on the method of its determination because each method may produce different values even when determining comparable qualities. For instance, the wingspan of a bird alive or dead is a different dimension. Thermoluninescence dating and Rehydroxylation [RHX] dating are different dimensions of temporal distance from now, even if they aim at dating the same object. The method of determination should be expressed using the property P2 has type (is type of). Note that simple terms such as “diameter” or “length” are normally insufficient to unambiguously describe a respective dimension. In contrast, “maximum linear extent” may be sufficient.
The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension adequate to the precision of the applied method of determination. If the respective quantity belongs to a non-discrete space according to the laws of physics, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that comparability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension, as appropriate.
Examples:
- the weight of the Luxor Obelisk [250 metric tons]
- the vertical height of the statue of David by Michaelangelo [5.17 metres]
- the weight of the Great Star of Africa diamond [530.2 carats]
- the calibrated C14 date for the Shroud of Turin [AD1262-1312, 1303-1384]
- the horizontal diameter of the Stonehenge Sarsen Circle [33 metres] (Pryor, 2016)
- the length of the sides of the Great Pyramid at Giza [230.34 metres] (Lehner and Hawass, 2017)
- the duration of the time span of the Battle of Issos/Issus on 15th November 333 B.C.E. [less than 12 hours] (Howard, 2012)
- Christie’s hammer price, in British Pounds, for Vincent van Gogh's Still Life: Vase with Fifteen Sunflowers in London on 30th March 1987 (E97) [24.75 million GBP (Brithish Pounds)]
Type: Entity
Belongs to version: version 7.1.1
E54 Dimension
Scope note:
This class comprises quantifiable properties that are measured by some calibrated means and can be approximated by numerical values.
An instance of E54 Dimension is thought to be the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation. It is recommended to record all numerical approximations of instances of E54 Dimension as intervals of indeterminacy. Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 4.1
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 6.1
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 5.0.2
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- The 250 metric ton weight of the Luxor Obelisk
- The 5.17 m height of the statue of David by Michaelangelo
- The 530.2 carats of the Great Star of Africa diamond
- The AD1262-1312, 1303-1384 calibrated C14 date for the Shroud of Turin
- The 33 m diameter of the Stonehenge Sarcen Circle
- The 755.9 foot length of the sides of the Great Pyramid at Giza
- Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97) has currency British Pounds (E98)
Type: Entity
Belongs to version: Version 6.2.2
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 5.1.2
E54 Dimension
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter 26 mm
- weight 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
Type: Entity
Belongs to version: Version 6.0
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CIDOC CRM classes.
E55 Type is the CIDOC CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CIDOC CRM as subclasses of E55 Type, forming hierarchies of terms, i.e., instances of E55 Type linked via P127 has broader term (has narrower term): E55 Type. Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E36]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: version 7.1
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: Version 6.2
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54 Dimension]
- portrait, sketch, animation [types of E38 image]
- French, English, German [E56]
- excellent, good, poor [types of E3 Condition State]
- Ford Model T, chop stick [types of E22 Man-Made Object]
- cave, doline, scratch [types of E26 Physical Feature]
- poem, short story [types of E33 Linguistic Object]
- wedding, earthquake, skirmish [types of E5 Event]
Type: Entity
Belongs to version: Version 5.0.1
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: Version 6.2.1
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CIDOC CRM classes.
E55 Type is the CIDOC CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CIDOC CRM as subclasses of E55 Type, forming hierarchies of terms, i.e., instances of E55 Type linked via P127 has broader term (has narrower term): E55 Type. Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types for instances of E54]
- portrait, sketch, animation [types for instances of E36]
- French, English, German (E56)
- excellent, good, poor [types for instances of E3]
- Ford Model T, chop stick [types for instances of E22]
- cave, doline, scratch [types for instances of E26]
- poem, short story [types for instances of E33]
- wedding, earthquake, skirmish [types for instances of E5]
Type: Entity
Belongs to version: version 7.1.1
E55 Type
Scope note:
This class comprises arbitrary concepts (universals) and provides a mechanism for organising them into a hierarchy.
This hierarchy is intended to duplicate the names of all the classes present in the model. This allows additional refinement, through subtyping, of those classes which do not require further analysis of their formal properties, but which nonetheless represent typological distinctions important to a given user group.
It should be noted that the Model does not make the distinction between classes and types known from some knowledge representation systems and object-oriented programming languages. The class E55 Type can be regarded as a metaclass (a class whose instances are universals), used to denote a user-defined specialization of some class or property of the Model, without introducing any additional formal properties for this specialization.
It reflects the characteristic use of the term “object type” for naming data fields in museum documentation and particularly the notion of typology in archaeology. It has however nothing to do with the term “type” in Natural History (cf. E83 Type Creation), but it includes the notion of a “taxon”.
Ideally, instances of the class E55 Type should be organised into thesauri, with scope notes, illustrations, etc. to clarify their meaning. In general, it is expected that different domains and cultural groups will develop different thesauri in parallel. Consistent reasoning on the expansion of subterms used in a thesaurus is possible insofar as it conforms to both the classes and the hierarchies of the model.
E56 Language, E57 Material and E58 Measurement Unit have been defined explicitly as elements of the E55 Type hierarchy because they are used categorically in the model without reference to instances of them, i.e. the Model does not foresee the description of instances of instances of them, e.g., the property instance “P45 consists of : gold” does not refer to a particular instance of gold.
Examples:
- weight, length, depth [types of E54 Dimension]
- portrait, sketch, animation [types of E38 image]
- French, English, German [E56]
- excellent, good, poor [types of E3 Condition State]
- Ford Model T, chop stick [types of E22 Man-Made Object]
- cave, doline, scratch [types of E26 Physical Feature]
- poem, short story [types of E33 Linguistic Object]
- wedding, earthquake, skirmish [types of E5 Event]
Type: Entity
Belongs to version: Version 4.1
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: Version 6.1
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: Version 5.0.2
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: Version 6.2.2
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: Version 5.1.2
E55 Type
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54]
- portrait, sketch, animation [types of E38]
- French, English, German [E56]
- excellent, good, poor [types of E3]
- Ford Model T, chop stick [types of E22]
- cave, doline, scratch [types of E26]
- poem, short story [types of E33]
- wedding, earthquake, skirmish [types of E5]
Type: Entity
Belongs to version: Version 6.0
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639-1:2002 and later versions.
Examples:
- el [Greek] (Palmer, 1980)
- en [English] (Wilson, 1983)
- eo [Esperanto] (Nuessel, 2000)
- es [Spanish] (Pineda, 1993)
- fr [French] (Rickard, 1974)
Type: Entity
Belongs to version: version 7.1
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 6.2
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 5.0.1
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 6.2.1
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639-1:2002 and later versions.
Examples:
- el [Greek] (Palmer, 1980)
- en [English] (Wilson, 1983)
- eo [Esperanto] (Nuessel, 2000)
- es [Spanish] (Pineda, 1993)
- fr [French] (Rickard, 1974)
Type: Entity
Belongs to version: version 7.1.1
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 4.1
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 6.1
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 5.0.2
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 6.2.2
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 5.1.2
E56 Language
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Examples:
- el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Type: Entity
Belongs to version: Version 6.0
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of (forms part of): E18 Physical Thing).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- Brick (Gurcke, 1987)
- Gold (Watson, 1990)
- Aluminium (Norman, 1986)
- Polycarbonate (Mhaske, 2011)
- Resin (Barton, 1992)
Type: Entity
Belongs to version: version 7.1
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 6.2
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 5.0.1
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 6.2.1
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of (forms part of): E18 Physical Thing).
This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick (Gurcke, 1987)
- gold (Watson, 1990)
- aluminium (Norman, 1986)
- polycarbonate (Mhaske, 2011)
- resin (Barton, 1992)
Type: Entity
Belongs to version: version 7.1.1
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 4.1
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 6.1
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 5.0.2
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 6.2.2
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 5.1.2
E57 Material
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
Type: Entity
Belongs to version: Version 6.0
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible, such as those defined by ISO80000:2009. Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second] (Hau, 1999)
- A [Ampere]
- GRD [Greek Drachme] (E98) (Daniel, 2014)
- °C [degrees centigrade] (Beckman, 1998)
Type: Entity
Belongs to version: version 7.1
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
-
A [Ampere]
-
GRD [Greek Drachme]
Type: Entity
Belongs to version: Version 6.2
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
- A [Ampere]
- GRD [Greek Drachme]
- C [degrees centigrade]
Type: Entity
Belongs to version: Version 5.0.1
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
-
A [Ampere]
-
GRD [Greek Drachme]
Type: Entity
Belongs to version: Version 6.2.1
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible, such as those defined by ISO80000:2009. Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second] (Hau et al., 1999)
- A [Ampere]
- GRD [Greek Drachme] (E98) (Daniel, 2014)
- C [degrees centigrade] (Beckman, 1998)
Type: Entity
Belongs to version: version 7.1.1
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
- A [Ampere]
- GRD [Greek Drachme]
- C [degrees centigrade]
Type: Entity
Belongs to version: Version 4.1
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
-
A [Ampere]
-
GRD [Greek Drachme]
Type: Entity
Belongs to version: Version 6.1
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
- A [Ampere]
- GRD [Greek Drachme]
- C [degrees centigrade]
Type: Entity
Belongs to version: Version 5.0.2
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
-
A [Ampere]
-
GRD [Greek Drachme]
Type: Entity
Belongs to version: Version 6.2.2
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
-
A [Ampere]
-
GRD [Greek Drachme]
Type: Entity
Belongs to version: Version 5.1.2
E58 Measurement Unit
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”.
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
-
A [Ampere]
-
GRD [Greek Drachme]
Type: Entity
Belongs to version: Version 6.0
E59 Primitive Value
Scope note:
This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.
The instances of E59 Primitive Value and its subclasses are not considered elements of the universe of discourse the CIDOC CRM aims to define and analyze. Rather, they play the role of a symbolic interface between the scope of the model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular, they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless of the nature of their mathematical abstractions.
Therefore, in an implementation, instances of E59 Primitive should be represented directly in the encoded symbolic form supported by the respective platform, such as a character string or a formatted date. They must not be represented in an implementation indirectly via, another a universal resource identifier, which in turn is linked to the actual encoded symbolic form. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: version 7.1
E59 Primitive Value
Scope note:
This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 6.2
E59 Primitive Value
Scope note:
This class comprises primitive values used as documentation elements, which are not further elaborated upon within the model.
As such they are not considered as elements within our universe of discourse. No specific implementation recommendations are made. It is recommended that the primitive value system from the implementation platform be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 5.0.1
E59 Primitive Value
Scope note:
This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 6.2.1
E59 Primitive Value
Scope note:
This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.
The instances of E59 Primitive Value and its subclasses are not considered elements of the universe of discourse the CIDOC CRM aims to define and analyze. Rather, they play the role of a symbolic interface between the scope of the model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular, they comprise lexical forms encoded as strings or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless of the nature of their mathematical abstractions.
Therefore, in an implementation, instances of E59 Primitive should be represented directly in the encoded symbolic form supported by the respective platform, such as a character string or a formatted date. They must not be represented in an implementation indirectly via, another a universal resource identifier, which in turn is linked to the actual encoded symbolic form. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
Examples:
- “ABCDEFG” (E62)
- 3.14 (E60)
- 0 (E60)
- 1921-01-01 (E61)
Type: Entity
Belongs to version: version 7.1.1
E59 Primitive Value
Scope note:
This class comprises primitive values used as documentation elements, which are not further elaborated upon within the model.
As such they are not considered as elements within our universe of discourse. No specific implementation recommendations are made.
Examples:
- ABCDEFG
- 3.14
- 0
- 1921-01-01
Type: Entity
Belongs to version: Version 4.1
E59 Primitive Value
Scope note:
This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 6.1
E59 Primitive Value
Scope note:
This class comprises primitive values used as documentation elements, which are not further elaborated upon within the model.
As such they are not considered as elements within our universe of discourse. No specific implementation recommendations are made. It is recommended that the primitive value system from the implementation platform be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 5.0.2
E59 Primitive Value
Scope note:
This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 6.2.2
E59 Primitive Value
Scope note:
This class comprises primitive values used as documentation elements, which are not further elaborated upon within the model.
As such they are not considered as elements within our universe of discourse. No specific implementation recommendations are made. It is recommended that the primitive value system from the implementation platform be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 5.1.2
E59 Primitive Value
Scope note:
This class comprises primitive values used as documentation elements, which are not further elaborated upon within the model.
As such they are not considered as elements within our universe of discourse. No specific implementation recommendations are made. It is recommended that the primitive value system from the implementation platform be used to substitute for this class and its subclasses.
Examples:
- ABCDEFG (E62)
- 3.14 (E60)
- 0
- 1921-01-01 (E61)
Type: Entity
Belongs to version: Version 6.0
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
Type: Entity
Belongs to version: Version 6.0
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
Type: Entity
Belongs to version: Version 6.2.1
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Stuff such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Stuff is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Lisbon by earthquake in 1755
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
- the shooting of the last wolf (‘Canis lupus Linne, 1758’) of the Rhineland/Germany, in Birreskopf/Eifel 1860 (now Museum Alexander Koenig inventory no.: ZFMK 86.385) (E6, E7)
Type: Entity
Belongs to version: Version 4.1
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an instance of E6 Destruction and of E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as an instance of E6 Destruction.
2. An event should also be documented as an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as an instance of E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD (Camardo, 2013)
- the destruction of Nineveh (E6, E7) (River, 2016)
- the breaking of a champagne glass yesterday by my dog (fictitious)
Type: Entity
Belongs to version: version 7.1.1
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
Type: Entity
Belongs to version: Version 6.1
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
Type: Entity
Belongs to version: Version 5.0.2
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
Type: Entity
Belongs to version: Version 6.2.2
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
Type: Entity
Belongs to version: Version 5.1.2
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an instance of E6 Destruction and of E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as an instance of E6 Destruction.
2. An event should also be documented as an instance of E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as an instance of E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD (Camardo, 2013)
- the destruction of Nineveh (E6, E7) (River, 2016)
- the breaking of a champagne glass yesterday by my dog (fictitious)
Type: Entity
Belongs to version: version 7.1
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Herculaneum by volcanic eruption in 79 AD
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
Type: Entity
Belongs to version: Version 6.2
E6 Destruction
Scope note:
This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction.
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
Examples:
- the destruction of Lisbon by earthquake in 1755
- the destruction of Nineveh (E6, E7)
- the breaking of a champagne glass yesterday by my dog
- the shooting of the last wolf (‘Canis lupus Linne, 1758’) of the Rhineland/Germany, in Birreskopf/Eifel 1860 (now Museum Alexander Koenig inventory no.: ZFMK 86.385) (E6, E7)
Type: Entity
Belongs to version: Version 5.0.1
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 6.0
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from numerically expressed identifiers in continua, which are instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yieldother instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension.
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: version 7.1
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 6.2
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 5.0.1
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 6.2.1
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from numerically expressed identifiers in continua, which are instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension.
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: version 7.1.1