Concept Search
Showing 2710 results:
E87 Curation Activity
Scope note:
This class comprises the activities that result in the continuity of management and the preservation and evolution of instances of E78 Collection, following an implicit or explicit curation plan.
It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded.
Items are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an E78 Collection for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity.
Examples:
- The curation of Mikael Heggelund Foslie’s coralline red algae Herbarium 1876 – 1909 (when Foslie died), now at Museum of Natural History and Archaeology, Norway
Type: Entity
Belongs to version: Version 5.0.2
E87 Curation Activity
Scope note:
This class comprises the activities that result in the continuity of management and the preservation and evolution of instances of E78 Collection, following an implicit or explicit curation plan.
It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded.
Items are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an E78 Collection for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity.
Examples:
- The curation of Mikael Heggelund Foslie’s coralline red algae Herbarium 1876 – 1909 (when Foslie died), now at Museum of Natural History and Archaeology, Norway
Type: Entity
Belongs to version: Version 6.2.2
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Type: Entity
Belongs to version: Version 6.0
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations (Huray, 2010)
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E36)
- The character "Little Red Riding Hood" variants of which appear amongst others in Grimm brothers’ ‘Rotkäppchen’, other oral fairy tales and the film 'Hoodwinked'
- The place "Havnor" as invented by Ursula K. Le Guin for her ‘Earthsea’ book series, the related maps and appearing in derivative works based on these novels
Type: Entity
Belongs to version: version 7.1
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Type: Entity
Belongs to version: Version 6.2
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or mental things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie The Seven Samurai by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Type: Entity
Belongs to version: Version 5.0.1
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Type: Entity
Belongs to version: Version 6.2.1
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations (Ball, 1962)
- the ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in Oxford edition
- the underlying prototype of any “no-smoking” sign (E36)
- the common ideas of the plots of the movie The Seven Samurai by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges (Mellen, 2002)
- the image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E36)
- the character Little Red Riding Hood, variants of which appear amongst others in Grimm brothers’ ‘Rotkäppchen’, other oral fairy tales and the film 'Hoodwinked'
- the place Havnor as invented by Ursula K. Le Guin for her ‘Earthsea’ book series, the related maps and appearing in derivative works based on these novels
Type: Entity
Belongs to version: version 7.1.1
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Type: Entity
Belongs to version: Version 6.1
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Type: Entity
Belongs to version: Version 5.1.2
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or mental things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie The Seven Samurai by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Type: Entity
Belongs to version: Version 5.0.2
E89 Propositional Object
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- The ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the Greek texts translated in … Oxford edition…
- The underlying prototype of any “no-smoking” sign (E36)
- The common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and the movie “The Magnificent Seven” by John Sturges
- The image content of the photo of the Allied Leaders at Yalta 1945 (E38)
- The character "Little Red Riding Hood" variants of which appear amongst others in Grimm brothers’ ‘Rotkäppchen’, other oral fairy tales and the film 'Hoodwinked'
- The place "Havnor" as invented by Ursula K. Le Guin for her ‘Earthsea’ book series, the related maps and appearing in derivative works based on these novels
Type: Entity
Belongs to version: Version 6.2.2
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
Type: Entity
Belongs to version: Version 6.2.1
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
Type: Entity
Belongs to version: Version 6.0
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tutankhamun” 1976-1979
Type: Entity
Belongs to version: Version 4.1
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA. (Wildfang, 2005)
- the movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between 15th September and 2nd November 2019.
Type: Entity
Belongs to version: version 7.1.1
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
Type: Entity
Belongs to version: Version 6.1
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
Type: Entity
Belongs to version: Version 5.1.2
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
Type: Entity
Belongs to version: Version 5.0.2
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
Type: Entity
Belongs to version: Version 6.2.2
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA. (Wildfang, 2005)
- the movement of the exhibition “Tutankhamun: Treasures of the Golden Pharaoh” between Sept 15 and Nov 2 2019.
Type: Entity
Belongs to version: version 7.1
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tut-Ankh-Amun” 1976-1979
Type: Entity
Belongs to version: Version 6.2
E9 Move
Scope note:
This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.
Examples:
- the relocation of London Bridge from the UK to the USA
- the movement of the exhibition “Treasures of Tutankhamun” 1976-1979
Type: Entity
Belongs to version: Version 5.0.1
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 6.0
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note and its subproperty P190 has symbolic content allow for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g., "bit", "Latin character", RGB pixel).
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E41)
- image BM000038850.JPG from the Clayton Herbarium in London (E36)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E36)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: version 7.1
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 6.2
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- ‘BM000038850.JPG’ (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 5.0.1
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 6.2.1
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note and its subproperty P190 has symbolic content allow for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g., bit, Latin character, RGB pixel).
Examples:
- ‘ecognizabl’
- the “no-smoking” sign (E36)
- “BM000038850.JPG” (E41) [identifies a digital image] (Natural History Museum, 2021)
- image BM000038850.JPG from the Clayton Herbarium in London (E36) [depicts specimen of Verbesina virginica] (Natural History Museum, 2021)
- the distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E36)
- the Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (Petrocchi, 1967) (E33)
Type: Entity
Belongs to version: version 7.1.1
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 6.1
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 5.1.2
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 5.0.2
E90 Symbolic Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
Examples:
- ‘ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Type: Entity
Belongs to version: Version 6.2.2
E91 Co-Reference Assignment
Scope note:
This class comprises actions of making the assertion whether two or more particular instances of E89 Propositional Object refer to the same instance of E1 CRM Entity. The assertion is based on the assumption that this was an implicit fact being made explicit by this assignment. Use of this class allows for the full description of the context of this assignment. The Actor making the assertion may have different kinds of confidence in the truth of the asserted fact of co-reference, because it may imply an interpretation of the (past) knowledge behind the propositional objects assumed to be co-referring. This kind of confidence can be described by using the property P2 has type (is type of). In case different propositional attitudes should be expressed per asserted propositional object, the assertion has accordingly to be divided into one instance of E91 Co-Reference Assignment for each kind of confidence.
This class aims at the problem of interpreting within a particular passage of an historical text, to which real-world entity a particular name, pronoun or equivalent expression was intended to refer by the texts author. In other words, it expresses the uncertainty of the creator of the assertion about the meaning of the information provided by another person.
Each such interpretation can only be documented with respect to another reference – either found in another text by the same or a different author, and/or by referring to the world known to the creator of the co-reference assertion. To do the latter, the property P155 has co-reference target (is co-reference target of) allows for referring to an instance of CRM Entity of the creator’s world. In a sense, the respective instance of E91 Co-Reference Assignment using the property P155 has co-reference target (is co-reference target of) in a knowledge base forms propositional object referring to the creator’s target entity, since a knowledge base as a whole can be seen as a propositional object. Consequently, if in a Semantic Web implementation the target entity is instantiated by a URI, the meaning of this identifier must be unambiguous to the creator of the co-reference assignment. Similarly, a URI of another authority, such as an author catalogue of a library, can be interpreted as a referring proposition of this catalogue, and be referred to by the property P153 assigned co-reference to (was regarded to co-refer by) or P154 assigned non co-reference to (was regarded not to co-refer by): E89 Propositional Object in order to express that it does not immediately represent the creator’s known world. In this case, the authority that knows the meaning of this URI must be unambiguous by the form of the URI itself.
In contrast, the meaning of the property ‘owl:same_as’ of the OWL knowledge representation language cannot specify who’s knowledge it represents and cannot express kind of confidence. Therefore it is not adequate to model the progress of scholarly co-reference research .
Examples:
- the assertion that the author name “Hans Jæger” on the title page of the novel “Fra Christiania-Bohêmen” refers to the same historical person as the motive of the painting “Forfatteren Hans Jæger” by Edvard Munch.
- the assertion that the author name “Hans Jæger” on the title page of the novel “Fra Christiania-Bohêmen” does not refer to the same historical person as the author of the collection of drawings “Til Julebordet : ti Pennetegninger / af H.J.” incorrectly attributed to Hans Jæger in the Bibsys database.
Type: Entity
Belongs to version: Version 6.0
E91 Co-Reference Assignment
Scope note:
This class comprises actions of making the assertion whether two or more particular instances of E89 Propositional Object refer to the same instance of E1 CRM Entity. The assertion is based on the assumption that this was an implicit fact being made explicit by this assignment. Use of this class allows for the full description of the context of this assignment.(MD will write an extension about the levels of belief)
Examples:
- the assertion that the author name “Hans Jæger” on the title page of the novel “Fra Christiania-Bohêmen” refers to the same historical person as the motive of the painting “Forfatteren Hans Jæger” by Edvard Munch.
- the assertion that the author name “Hans Jæger” on the title page of the novel “Fra Christiania-Bohêmen” does not refer to the same historical person as the author of the collection of drawings “Til Julebordet : ti Pennetegninger / af H.J.” incorrectly attributed to Hans Jæger in the Bibsys database.
Type: Entity
Belongs to version: Version 5.1.2
E92 Spacetime Volume
Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.
Examples:
- the spacetime Volume of the Event of Ceasars murder
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
Type: Entity
Belongs to version: Version 6.0
E92 Spacetime Volume
Scope note:
This class comprises 4-dimensional point sets (volumes) in physical spacetime (in contrast to mathematical models of it) regardless their true geometric forms. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, E53 Place and E52 Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of E92 Spacetime Volume is its projection on time.
Examples:
- the extent in space and time of the Event of Caesar’s murder
- where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
- the extent in space and time defined by a polygon approximating the Danube river flood in Austria between 6thand 9thof August 2002
Type: Entity
Belongs to version: version 7.1
E92 Spacetime Volume
Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.
Examples:
- the spacetime Volume of the Event of Ceasars murder
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
Type: Entity
Belongs to version: Version 6.2
E92 Spacetime Volume
Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.
Examples:
- the spacetime Volume of the Event of Ceasars murder
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
Type: Entity
Belongs to version: Version 6.2.1
E92 Spacetime Volume
Scope note:
This class comprises 4-dimensional point sets (volumes) in physical spacetime (in contrast to mathematical models of it) regardless their true geometric forms. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, E53 Place and E52 Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of E92 Spacetime Volume is its projection on time.
Examples:
- the extent in space and time of the Event of Caesar’s murder (Irwin, 1935)
- where and when the carbon 14 dating of the Schoeninger Speer II in 1996 took place (Kouwenhoven, 1997)
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location (Goodwin, 2015)
- the extent in space and time defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
Type: Entity
Belongs to version: version 7.1.1
E92 Spacetime Volume
Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.
Examples:
- the spacetime Volume of the Event of Ceasars murder
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
Type: Entity
Belongs to version: Version 6.1
E92 Spacetime Volume
Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.
Examples:
- the spacetime Volume of the Event of Ceasars murder
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
Type: Entity
Belongs to version: Version 6.2.2
E92 Spacetime Volume
Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.
Examples:
- the spacetime Volume of the Event of Ceasars murder
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
Type: Entity
Belongs to version: Version 5.1.2
E93 Presence
Scope note:
This class comprises instances of E92 Spacetime Volume, whose temporal extent has been chosen in order to determine the spatial extent of a phenomenon over the chosen time-span. Respective phenomena may, for instance, be historical events or periods, but can also be the diachronic extent and existence of physical things. In other words, instances of this class fix a slice of another instance of E92 Spacetime Volume in time.
The temporal extent of an instance of E93 Presence typically is predetermined by the researcher so as to focus the investigation particularly on finding the spatial extent of the phenomenon by testing for its characteristic features. There are at least two basic directions such investigations might take. The investigation may wish to determine where something was during some time or it may wish to reconstruct the total passage of a phenomenon’s spacetime volume through an examination of discrete presences. Observation and measurement of features indicating the presence or absence of a phenomenon in some space allows for the progressive approximation of spatial extents through argumentation typically based on inclusion, exclusion and various overlaps.
Examples:
- The Roman Empire on 19 August AD 14
- Johann Joachim Winkelmann’s whereabouts in December 1775
- Johann Joachim Winkelmann’s whereabouts from November 19 1755 until April 9 1768I
Type: Entity
Belongs to version: version 7.1
E93 Presence
Scope note:
This class comprises instances of E92 Spacetime Volume that result from intersection of instances of E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituing spacetime volume and the time-span.
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
Type: Entity
Belongs to version: Version 6.2
E93 Presence
Scope note:
This class comprises instances of E92 Spacetime Volume that result from intersection of instances of E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituing spacetime volume and the time-span.
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
Type: Entity
Belongs to version: Version 6.2.1
E93 Presence
Scope note:
This class comprises instances of E92 Spacetime Volume, whose temporal extent has been chosen in order to determine the spatial extent of a phenomenon over the chosen time-span. Respective phenomena may, for instance, be historical events or periods, but can also be the diachronic extent and existence of physical things. In other words, instances of this class fix a slice of another instance of E92 Spacetime Volume in time.
The temporal extent of an instance of E93 Presence typically is predetermined by the researcher so as to focus the investigation particularly on finding the spatial extent of the phenomenon by testing for its characteristic features. There are at least two basic directions such investigations might take. The investigation may wish to determine where something was during some time or it may wish to reconstruct the total passage of a phenomenon’s spacetime volume through an examination of discrete presences. Observation and measurement of features indicating the presence or absence of a phenomenon in some space allows for the progressive approximation of spatial extents through argumentation typically based on inclusion, exclusion and various overlaps.
Examples:
- the Roman Empire on 19 August AD 14 (Clare and Edwards, 1992)
- Johann Joachim Winckelmann’s whereabouts in December 1775 (Leppmann, 1970)
- Johann Joachim Winckelmann’s whereabouts from November 19 1755 until April 9 1768 (Leppmann, 1970)
Type: Entity
Belongs to version: version 7.1.1
E93 Presence
Scope note:
This class comprises instances of E92 Spacetime Volume, whose arbitrary temporal extent has been chosen in order to determine the spatial extent of a phenomenon over the chosen time-span. Respective phenomena may, for instance, be historical events or periods, but can also be physical things seen in their diachronic existence and extent. In other words, instances of this class fix a slice of a Spacetime Volume in time.
The temporal extent typically is predetermined by the researcher so as to focus the investigation particularly on finding the spatial extent of the phenomenon by testing for its characteristic features. There are at least two basic directions such investigations might take. The investigation may wish to determine where something was during some time or it may wish to reconstruct the total passage of a phenomenon’s Spacetime Volume through an examination of discrete presences. Observation and measurement of features indicating the presence or absence of a phenomenon in some space allows for the progressive approximation of spatial extents through argumentation typically based on inclusion, exclusion and various overlaps.
Type: Entity
Belongs to version: Version 6.2.2
E93 Spacetime Snapshot
Scope note:
This class comprises instances of E92 Spacetime Volume that result from intersections between instances of E92 Spacetime Volume, instances of E53 Place, or instances of E52 Time-Span. The identity of an instance of this class is determined by the identities of its constituting items. Those are one or more of the following:
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
This class comprises instances of E92 Spacetime Volume that result from intersection of instances of E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituting space time volume and the time-span.
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a space time volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
Type: Entity
Belongs to version: Version 6.0
E93 Spacetime Snapshot
Scope note:
This class comprises instances of E92 Spacetime Volume that result from intersections between instances of E92 Spacetime Volume, instances of E53 Place, or instances of E52 Time-Span. The identity of an instance of this class is determined by the identities of its constituting items. Those are one or more of the following:
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
This class comprises instances of E92 Spacetime Volume that result from intersection of instances of E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituting space time volume and the time-span.
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a space time volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
Type: Entity
Belongs to version: Version 6.1
E93 Spacetime Snapshot
Scope note:
This class comprises instances of E92 Spacetime Volume that result from intersections of instances of E92 Spacetime Volume, E53 Place or E52 Time-Span. The identity of an instance of this class is determined by the identities of its constituting items. Those are one or more of the following:
1) two or more instances of E92 Spacetime Volume
2) one or more instances of E92 Spacetime Volume AND one or more instances of E53 Place.
3) one or more instances of E92 Spacetime Volume AND one or more instances of E52 Time-Span
4) one or more instances of E53 Place AND one or more instances of E52 Time-Span
This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. It can also be used to define a spatial snapshot, such as cutting the E92 Spacetime Volume occupied by the Iron Age by the current spatial extent of Austria. It can also be used to define intersections of two or more real spatiotemporal components, such as the E92 Spacetime Volume occupied by the E4 Period of Impressionism with the E92 Spacetime Volume occupied by the life of Van Gogh, or the E92 Spacetime Volume occupied by Imperial China with that claimed by Imperial Vietnam.
In particular, it can be used to define partial spatial or temporal projections of spacetime volumes, such as the time-spans of foreign occupation of a country, or the spatial extent of a flood at some particular hour.
Type: Entity
Belongs to version: Version 5.1.2
E94 Space Primitive
Scope note:
This class comprises instances of E59 Primitive Value for space that should be implemented with appropriate validation, precision and references to spatial coordinate systems to express geometries on or relative to Earth, or on any other stable constellations of matter, relevant to cultural and scientific documentation.
An instance of E94 Space Primitive definesan instance of E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr & Hiebel 2013), which means that the identity of the place is derived from its geometric definition. Such a declarative place may allow for the approximation of instances of E53 Place defined by the actual extent of some phenomenon, such as a settlement or a riverbed, or other forms of identification rather than by an instance of E94 Space Primitive. Note that using an instance of E94 Space Primitive for approximating the actual extent of some place always defines a (declarative) instance of E53 Place in its own right.
Definitions of instances of E53 Place using different spatial reference systems are always definitions of different instances of E53 Place.
Instances of E94 Space Primitive provide the ability to link CIDOC CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualization of the instances of E53 Place they define, in their geographic context and forcomputing topological relations between places based on these geometries. E94 Space Primitive is not further elaborated upon within this model. It is considered good practice to maintain compatibility with OGC standards.
Examples:
- Coordinate Information in GML like <gml:Point gml:id="p21" srsName="http://www.opengis.net/def/crs/EPSG/0/4326"> <gml:coordinates>45.67, 88.56</gml:coordinates> </gml:Point>
- Coordinate Information in lat, long 48,2 13,3
- Well Known Text like POLYGON ((30 10, 40 40, 20 40, 10 20, 30 10))
Type: Entity
Belongs to version: version 7.1
E94 Space Primitive
Scope note:
This class comprises instances of E59 Primitive Value for space that should be implemented with appropriate validation, precision and references to spatial coordinate systems to express geometries on or relative to earth, or any other stable constellations of matter, relevant to cultural and scientific documentation.
An E94 Space Primitive defines an E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr and Hiebel 2013), which means that the identity of the place is derived from its geometric definition. This declarative place allows for the application of all place properties to relate phenomenal places to their approximations expressed with geometries.
Instances of E94 Space Primitive provide the ability to link CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualisation of the instances of E53 Place they define, in their geographic context and for computing topological relations between places based on these geometries.
E94 Space Primitive is not further elaborated upon within this model. Statement of compatibility with OPENGIS
Examples:
- Coordinate Information in GML like <gml:Point gml:id="p21" srsName="http://www.opengis.net/def/crs/EPSG/0/4326"> <gml:coordinates>45.67, 88.56</gml:coordinates> </gml:Point>
- Coordinate Information in lat, long 48,2 13,3
- Well Known Text like POLYGON ((30 10, 40 40, 20 40, 10 20, 30 10))
Type: Entity
Belongs to version: Version 6.2
E94 Space Primitive
Scope note:
This class comprises instances of E59 Primitive Value for space that should be implemented with appropriate validation, precision and references to spatial coordinate systems to express geometries on or relative to earth, or any other stable constellations of matter, relevant to cultural and scientific documentation.
An E94 Space Primitive defines an E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr and Hiebel 2013), which means that the identity of the place is derived from its geometric definition. This declarative place allows for the application of all place properties to relate phenomenal places to their approximations expressed with geometries.
Instances of E94 Space Primitive provide the ability to link CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualisation of the instances of E53 Place they define, in their geographic context and for computing topological relations between places based on these geometries.
E94 Space Primitive is not further elaborated upon within this model. Statement of compatibility with OPENGIS
Examples:
- Coordinate Information in GML like <gml:Point gml:id="p21" srsName="http://www.opengis.net/def/crs/EPSG/0/4326"> <gml:coordinates>45.67, 88.56</gml:coordinates> </gml:Point>
- Coordinate Information in lat, long 48,2 13,3
- Well Known Text like POLYGON ((30 10, 40 40, 20 40, 10 20, 30 10))
Type: Entity
Belongs to version: Version 6.2.1
E94 Space Primitive
Scope note:
This class comprises instances of E59 Primitive Value for space that should be implemented with appropriate validation, precision and references to spatial coordinate systems to express geometries on or relative to Earth, or on any other stable constellations of matter, relevant to cultural and scientific documentation.
An instance of E94 Space Primitive defines an instance of E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr & Hiebel 2013), which means that the identity of the place is derived from its geometric definition. Such a declarative place may allow for the approximation of instances of E53 Place defined by the actual extent of some phenomenon, such as a settlement or a riverbed, or other forms of identification rather than by an instance of E94 Space Primitive. Note that using an instance of E94 Space Primitive for approximating the actual extent of some place always defines a (declarative) instance of E53 Place in its own right.
Definitions of instances of E53 Place using different spatial reference systems are always definitions of different instances of E53 Place.
Instances of E94 Space Primitive provide the ability to link CIDOC CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualization of the instances of E53 Place they define, in their geographic context and for computing topological relations between places based on these geometries. E94 Space Primitive is not further elaborated upon within this model. It is considered good practice to maintain compatibility with OGC standards.
Examples:
- <gml:Point gml:id=p21 srsName=http://www.opengis.net/def/crs/EPSG/0/4326> <gml:coordinates>45.67, 88.56</gml:coordinates> </gml:Point> [Coordinate Information in GML]
- “40°31'17.9N 21°15'48.3E” [A single point for approximating the centre of the city of Kastoria, Greece]
- POLYGON ((30 10, 40 40, 20 40, 10 20, 30 10)) [Well-Known Text (WKT)]
Type: Entity
Belongs to version: version 7.1.1
E94 Space Primitive
Scope note:
This class comprises instances of E59 Primitive Value for space that should be implemented with appropriate validation, precision and references to spatial coordinate systems to express geometries on or relative to earth, or any other stable constellations of matter, relevant to cultural and scientific documentation.
An E94 Space Primitive defines an E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr and Hiebel 2013), which means that the identity of the place is derived from its geometric definition. This declarative place allows for the application of all place properties to relate phenomenal places to their approximations expressed with geometries.
Definitions of instances of E53 Place using different spatial reference systems always result in definitions of different instances of E53 place approximating each other.
Instances of E94 Space Primitive provide the ability to link CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualisation of the instances of E53 Place they define, in their geographic context and for computing topological relations between places based on these geometries.
Note that it is possible for a place to be defined by phenomena causal to it or other forms of identification rather than by an instance of E94 Space Primitive. In this case, this property must not be used for approximating the respective instance of E53 Place with an instance of E94 Space Primitive. E94 Space Primitive is not further elaborated upon within this model. Compatibility with OGC standards are recommended
Examples:
- Coordinate Information in GML like <gml:Point gml:id="p21" srsName="http://www.opengis.net/def/crs/EPSG/0/4326"> <gml:coordinates>45.67, 88.56</gml:coordinates> </gml:Point>
- Coordinate Information in lat, long 48,2 13,3
- Well Known Text like POLYGON ((30 10, 40 40, 20 40, 10 20, 30 10))
Type: Entity
Belongs to version: Version 6.2.2
E95 Spacetime Primitive
Scope note:
This class comprises instances of E59 Primitive Value for spacetime volumes that should be implemented with appropriate validation, precision and reference systems to express geometries being limited and varying over time on or relative to Earth, or any other stable constellations of matter, relevant to cultural and scientific documentation.
An instance of E95 Spacetime Primitive may consist of one expression including temporal and spatial information such as in GML or a different form of expressing spacetime in an integrated way such as a formula containing all 4 dimensions.An instance of E95 Spacetime Primitive defines an instance of E92 Spacetime Volume in the sense of a declarative spacetime volume as defined in CRMgeo (Doerr & Hiebel 2013), which means that the identity of the instance of E92 Spacetime Volume is derived from its geometric and temporal definition. This declarative spacetime volume allows for the application of all E92 Spacetime Volume properties to relate phenomenal spacetime volumes of periods and physical things to propositions about their spatial and temporal extents.
Instances of E92 Spacetime Volume defined by P169 defines spacetime volume (spacetime volume is defined by) that use different spatiotemporal referring systems are always regarded as different instances of the E92 Spacetime Volume.
It is possible for a spacetime volume to be defined by phenomena causal to it, such as an expanding and declining realm, a settlement structure or a battle, or other forms of identification rather than by an instance of E95 Spacetime Primitive. Any spatiotemporal approximation of such a phenomenon by an instance of E95 Spacetime Primitive constitutes an instance of E92 Spacetime Volume in its own right.
E95 Spacetime Primitive is not further elaborated upon within this model. Compatibility with OGC standards is recommended.
Examples:
• Spatial and temporal information in KML for the maximum extent of the Byzantine Empire
<Placemark>
<name> Byzantine Empire </name>
<styleUrl>#style_1</styleUrl>
<TimeSpan>
<begin>330</begin>
<end>1453</end>
</TimeSpan>
<Polygon><altitudeMode>clampToGround</altitudeMode><outerBoundaryIs><LinearRing>
<coordinates>18.452787460,40.85553626,0 17.2223187,40.589098,........0 17.2223,39.783
</coordinates>
</Polygon>
</Placemark>
Type: Entity
Belongs to version: version 7.1
E95 Spacetime Primitive
Scope note:
This class comprises instances of E59 Primitive Value for spacetime volumes that should be implemented with appropriate validation, precision, interval logic and reference systems to express date ranges and geometries relevant to cultural documentation. A Spacetime Primitive may consist of one expression including temporal and spatial information like in GML or a different form of expressing spacetime in an integrated way like a formula containing all 4 dimensions.
An E95 Spacetime Primitive defines an E92 Spacetime Volume in the sense of a declarative spacetime volume as defined in CRMgeo (Doerr & Hiebel 2013), which means that the identity of the spacetime volume is derived from its geometric and temporal definition. This declarative spacetime volume allows for the application of all E92 Spacetime Volume properties to relate phenomenal spacetime volumes of periods and physical things to propositions about their spatial and temporal extents.
Definitions of spacetime volumes using different spacetime reference systems always result in definitions of different spacetime volumes approximating each other.
Note that it is possible for a spacetime volume to be defined by phenomena causal to it or other forms of identification rather than by an instance of E95 Spacetime Primitive. In this case, this property must not be used for approximating the respective instance of E92 Spacetime volume with an instance of E95 Spacetime Primitive.
E95 Spacetime Primitive is not further elaborated upon within this model. Compatibility with OGC standards are recommended.
Examples:
• Spatial and temporal information in KML for the maximum extent of the Byzantine Empire
<Placemark>
<name> Byzantine Empire </name>
<styleUrl>#style_1</styleUrl>
<TimeSpan>
<begin>330</begin>
<end>1453</end>
</TimeSpan>
<Polygon><altitudeMode>clampToGround</altitudeMode><outerBoundaryIs><LinearRing>
<coordinates>18.452787460,40.85553626,0 17.2223187,40.589098,........0 17.2223,39.783
</coordinates>
</Polygon>
</Placemark>
Type: Entity
Belongs to version: Version 6.2.2
E95 Spacetime Primitive
Scope note:
This class comprises instances of E59 Primitive Value for spacetime volumes that should be implemented with appropriate validation, precision and reference systems to express geometries being limited and varying over time on or relative to Earth, or any other stable constellations of matter, relevant to cultural and scientific documentation. An instance of E95 Spacetime Primitive may consist of one expression including temporal and spatial information such as in GML or a different form of expressing spacetime in an integrated way such as a formula containing all 4 dimensions.
An instance of E95 Spacetime Primitive defines an instance of E92 Spacetime Volume in the sense of a declarative spacetime volume as defined in CRMgeo (Doerr & Hiebel 2013), which means that the identity of the instance of E92 Spacetime Volume is derived from its geometric and temporal definition. This declarative spacetime volume allows for the application of all E92 Spacetime Volume properties to relate phenomenal spacetime volumes of periods and physical things to propositions about their spatial and temporal extents.
Instances of E92 Spacetime Volume defined by P169 defines spacetime volume (spacetime volume is defined by) that use different spatiotemporal referring systems are always regarded as different instances of the E92 Spacetime Volume.
It is possible for a spacetime volume to be defined by phenomena causal to it, such as an expanding and declining realm, a settlement structure or a battle, or other forms of identification rather than by an instance of E95 Spacetime Primitive. Any spatiotemporal approximation of such a phenomenon by an instance of E95 Spacetime Primitive constitutes an instance of E92 Spacetime Volume in its own right.
E95 Spacetime Primitive is not further elaborated upon within this model. Compatibility with OGC standards is recommended.
Examples:
- <Placemark>
- <name> Byzantine Empire </name>styleUrl>#style_1</styleUrl>
- <TimeSpan>
- <begin>330</begin><end>1453</end>
- </TimeSpan>
- <Polygon>
- <altitudeMode>clampToGround</altitudeMode>
- <outerBoundaryIs>
- <LinearRing>
- <coordinates>18.452787460,40.85553626,0 17.2223187,40.589098,....0 17.2223,39.783
- </coordinates>
- </LinearRing>
- </outerBoundaryIs>
- </Polygon>
- </Placemark>
- [spatial and temporal information in KML for the maximum extent of the Byzantine Empire]
Type: Entity
Belongs to version: version 7.1.1
E96 Purchase
Scope note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more different instances of E39 Actor, where the transferring party is completely compensated by the payment of a monetary amount. In more detail, a purchase agreement establishes a fixed monetary obligation at its initialization on the receiving party, to the giving party. An instance of E96 Purchase begins with the contract or equivalent agreement and ends with the fulfilment of all contractual obligations. In the case that the activity is abandoned before both parties have fulfilled these obligations, the activity is not regarded as an instance of E96 Purchase.
This class is a very specific case of the much more complex social business practices of exchange of goods and the creation and satisfaction of related social obligations. Purchase activities which define individual sales prices per object can be modelled by instantiating E96 Purchase for each object individually and as part of an overall instance of E96 Purchase transaction.
Examples:
- the purchase of 10 okka of nails by the captain A. Syrmas on 18/9/1895 in Thessaloniki
Type: Entity
Belongs to version: version 7.1
E96 Purchase
Scope note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more different instances of E39 Actor, where the transferring party is completely compensated by the payment of a monetary amount. In more detail, a purchase agreement establishes a fixed monetary obligation at its initialization on the receiving party, to the giving party. An instance of E96 Purchase begins with the contract or equivalent agreement and ends with the fulfilment of all contractual obligations. In the case that the activity is abandoned before both parties have fulfilled these obligations, the activity is not regarded as an instance of E96 Purchase.
This class is a very specific case of the much more complex social business practices of exchange of goods and the creation and satisfaction of related social obligations. Purchase activities which define individual sales prices per object can be modelled by instantiating E96 Purchase for each object individually and as part of an overall E96 Purchase transaction.
Type: Entity
Belongs to version: Version 6.2.2
E96 Purchase
Scope note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more different instances of E39 Actor, where the transferring party is completely compensated by the payment of a monetary amount. In more detail, a purchase agreement establishes a fixed monetary obligation at its initialization on the receiving party, to the giving party. An instance of E96 Purchase begins with the contract or equivalent agreement and ends with the fulfilment of all contractual obligations. In the case that the activity is abandoned before both parties have fulfilled these obligations, the activity is not regarded as an instance of E96 Purchase.
This class is a very specific case of the much more complex social business practices of exchange of goods and the creation and satisfaction of related social obligations. Purchase activities which define individual sales prices per object can be modelled by instantiating E96 Purchase for each object individually and as part of an overall instance of E96 Purchase transaction.
Examples:
- the purchase of 10 okka of nails by the captain A. Syrmas on 18th September 1895 in Thessaloniki (Syrmas, 1896)
Type: Entity
Belongs to version: version 7.1.1
E97 Monetary Amount
Scope note:
This class comprises quantities of monetary possessions or obligations in terms of their nominal value with respect to a particular currency. These quantities may be abstract accounting units, the nominal value of a heap of coins or bank notes at the time of validity of the respective currency, the nominal value of a bill of exchange or other documents expressing monetary claims or obligations. It specifically excludes amounts expressed in terms of weights of valuable items, like gold and diamonds, and quantities of other non-currency items, like goats or stocks and bonds.
Examples:
• Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97) has currency British Pounds (E98)
Type: Entity
Belongs to version: version 7.1
E97 Monetary Amount
Scope note:
This class comprises quantities of monetary possessions or obligations in terms of their nominal value with respect to a particular currency. These quantities may be abstract accounting units, the nominal value of a heap of coins or bank notes at the time of validity of the respective currency, the nominal value of a bill of exchange or other documents expressing monetary claims or obligations. It specifically excludes amounts expressed in terms of weights of valuable items, like gold and diamonds, and quantities of other non-currency items, like goats or stocks and bonds.
Examples:
• Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97) has currency British Pounds (E98)
Type: Entity
Belongs to version: Version 6.2.2
E97 Monetary Amount
Scope note:
This class comprises quantities of monetary possessions or obligations in terms of their nominal value with respect to a particular currency. These quantities may be abstract accounting units, the nominal value of a heap of coins or bank notes at the time of validity of the respective currency, the nominal value of a bill of exchange or other documents expressing monetary claims or obligations. It specifically excludes amounts expressed in terms of weights of valuable items, like gold and diamonds, and quantities of other non-currency items, like goats or stocks and bonds.
Examples:
- Christies’ hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30th March 1987
Type: Entity
Belongs to version: version 7.1.1
E98 Currency
Scope note:
This class comprises the units in which a monetary system, supported by an administrative authority or other community, quantifies and arithmetically compares all monetary amounts declared in the unit. The unit of a monetary system must describe a nominal value which is kept constant by its administrative authority and an associated banking system if it exists, and not by market value. For instance, one may pay with grams of gold, but the respective monetary amount would have been agreed as the gold price in US dollars on the day of the payment. Under this definition, British Pounds, U.S. Dollars, and European Euros are examples of currency, but “grams of gold” is not. One monetary system has one and only one currency. Instances of this class must not be confused with coin denominations, such as “Dime” or “Sestertius”. Non-monetary exchange of value in terms of quantities of a particular type of goods, such as cows, do not constitute a currency.
Examples:
- “As” (Roman mid republic)
- “Euro”, (Temperton, 1997)
- “US Dollar” (Rose, 1978)
Type: Entity
Belongs to version: version 7.1
E98 Currency
Scope note:
This class comprises the units in which a monetary system, supported by an administrative authority or other community, quantifies and arithmetically compares all monetary amounts declared in the unit. The unit of a monetary system must describe a nominal value which is kept constant by its administrative authority and an associated banking system if it exists, and not by market value. For instance, one may pay with grams of gold, but the respective monetary amount would have been agreed as the gold price in US dollars on the day of the payment. Under this definition, British Pounds, U.S. Dollars, and European Euros are examples of currency, but “grams of gold” is not. One monetary system has one and only one currency. Instances of this class must not be confused with coin denominations, such as “Dime” or “Sestertius”. Non-monetary exchange of value in terms of quantities of a particular type of goods, such as cows, do not constitute a currency.
Examples:
“As” (Roman mid republic)
“Euro”,
“US Dollar”
Type: Entity
Belongs to version: Version 6.2.2
E98 Currency
Scope note:
This class comprises the units in which a monetary system, supported by an administrative authority or other community, quantifies and arithmetically compares all monetary amounts declared in the unit. The unit of a monetary system must describe a nominal value which is kept constant by its administrative authority and an associated banking system if it exists, and not by market value. For instance, one may pay with grams of gold, but the respective monetary amount would have been agreed as the gold price in US dollars on the day of the payment. Under this definition, British Pounds, U.S. Dollars, and European Euros are examples of currency, but “grams of gold” is not. One monetary system has one and only one currency. Instances of this class must not be confused with coin denominations, such as “Dime” or “Sestertius”. Non-monetary exchange of value in terms of quantities of a particular type of goods, such as cows, do not constitute a currency.
Examples:
- “As” [Roman mid republic]
- “Euro”, (Temperton, 1997)
- “US Dollar” (Rose, 1978)
Type: Entity
Belongs to version: version 7.1.1
E99 Product Type
Scope note:
This classes comprises types that stand as the models for instances of E22 Human-Made Object that are produced as the result of production activities using plans exact enough to result in one or more series of uniform, functionally and aesthetically identical and interchangeable items. The product type is the intended ideal form of the manufacture process. It is typical of instances of E22 that conform to an instance of E99 Product Type that its component parts are interchangeable with component parts of other instances of E22 made after the model of the same instance of E99. Frequently, the uniform production according to given instance of E99 Product Type is achieved by creating individual tools, such as moulds or print plates that are themselves carriers of the design of the product type. Modern tools may use the flexibility of electronically controlled devices to achieve such uniformity. The product type itself, i.e., the potentially unlimited series of aesthetically equivalent items, may be the target of artistic design, rather than the individual object. In extreme cases, only one instance of a product type may have been produced, such as in a "print on demand" process which was only triggered once. However, this should not be confused with industrial prototypes, such as car prototypes, which are produced prior to the production line being set up, or test the production line itself.
Examples:
- Volkswagen Type 11 (Beetle)
- Dragendorff 54 samian vessel
- 1937 Edward VIII brass threepenny bit
- Qin Crossbow trigger un-notched Part B (Bg2u)
- Nokia Cityman 1320 (The first Nokia mobile phone)
Type: Entity
Belongs to version: version 7.1
E99 Product Type
Scope note:
This classes comprises types that stand as the models for instances of E22 Man-Made Object that are produced as the result of production activities using plans exact enough to result in one or more series of uniform, functionally and aesthetically identical and interchangeable items. The product type is the intended ideal form of the manufacture process. It is typical of instances of E22 that conform to an instance of E99 Product Type that its component parts are interchangeable with component parts of other instances of E22 made after the model of the same instance of E99. Frequently, the uniform production according to a set E99 Product Type is achieved by creating individual tools, such as moulds or print plates that are themselves carriers of the design of the product type. Modern tools may use the flexibility of electronically controlled devices to achieve such uniformity. The product type itself, i.e., the potentially unlimited series of aesthetically equivalent items, may be the target of artistic design, rather than the individual object. In extreme cases, only one instance of a product type may have been produced, such as in a "print on demand" process which was only triggered once. However, this should not be confused with industrial prototypes, such as car prototypes, which are produced prior to the production line being set up, or test the production line itself.
Examples:
Volkswagen Type 11 (Beetle)
Dragendorff 54 samian vessel
1937 Edward VIII brass threepenny bit
Qin Crossbow trigger un-notched Part B (Bg2u)
Nokia Cityman 1320 (The first Nokia mobile phone)
Proposed properties: A unique plan, a required, unique tool.
Type: Entity
Belongs to version: Version 6.2.2
E99 Product Type
Scope note:
This classes comprises types that stand as the models for instances of E22 Human-Made Object that are produced as the result of production activities using plans exact enough to result in one or more series of uniform, functionally and aesthetically identical and interchangeable items. The product type is the intended ideal form of the manufacture process. It is typical of instances of E22 that conform to an instance of E99 Product Type that its component parts are interchangeable with component parts of other instances of E22 made after the model of the same instance of E99. Frequently, the uniform production according to a given instance of E99 Product Type is achieved by creating individual tools, such as moulds or print plates that are themselves carriers of the design of the product type. Modern tools may use the flexibility of electronically controlled devices to achieve such uniformity. The product type itself, i.e., the potentially unlimited series of aesthetically equivalent items, may be the target of artistic design, rather than the individual object. In extreme cases, only one instance of a product type may have been produced, such as in a print on demand process which was only triggered once. However, this should not be confused with industrial prototypes, such as car prototypes, which are produced prior to the production line being set up, or test the production line itself.
Examples:
- Volkswagen Type 11 (Beetle) (Rieger, 2013)
- Dragendorff 54 samian vessel
- 1937 Edward VIII brass threepenny bit
- Qin Crossbow trigger un-notched Part B (Bg2u) (Li, 2012)
- Nokia Cityman 1320 [The first Nokia mobile phone]
Type: Entity
Belongs to version: version 7.1.1
Existence Information
Comment:
Motivation for this unit has been expert knowledge about the coming into existence and end of existence of different items, as well as interpretation of characteristic database schema elements from relevant collection management systems.
Type: Functional Overview
Group Dynamics
Comment:
Motivation for this unit has been expert knowledge about group dynamics ( joining and leaving a group), as well as interpretation of characteristic database schema elements from relevant collection management systems.
Type: Functional Overview
Image Information,Objects and Carriers
Comment:
Motivation for this unit has been the ImageInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about images and other information objects and their carriers, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, image information supports Security, Accountability, Access and an Historic archive. Particularly valuable in the recovery of missing or stolen property, without an image it may be impossible to prove ownership or certain identification or an object. Image information also supports visually the textual information about the object recorded elsewhere and should record the following information categories:
- Image type
- Image reference number
Type: Functional Overview
Institution Information
Comment:
Motivation for this graph has been the InstitutionInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about institutions, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, this information primarily supports Accountability, and Access. It is essential when exchanging object information with other institutions as it provides a location for the documentation of an object, and in many cases for the object itself and should record the following information categories:
- Institution name
- Institution sub body
- Institution address
- Institution country
Type: Functional Overview
Location Information
Comment:
Motivation for this unit has been the LocationInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, location information supports Security, Accountability, and Access. Without Location information it is not possible to fulfil the basic responsibilities of a museum, in that the custodian should always know where objects are and be able to provide physical access when necessary. In relation to location the following information categories should be recorded:
- Current location
- Current location type
- Current location date
- Normal location
Type: Functional Overview
Mark and Inscription Information
Comment:
Motivation for these graphs has been the Mark and Inscription Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about marks and inscriptions, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, mark and inscription information supports Security, Accountability, Access, and an Historic archive. It enables the retrieval of lost property and the unique identification of otherwise similar objects and can be of particular research significance. In relation to marks and inscriptions the following information categories should be recorded:
- Mark/inscription text
- Mark/inscription type
- Mark/inscription description
- Mark/inscription technique
- Mark/inscription position
- Mark/inscription language
- Mark/inscription translation
In the CIDOC CRM the inscription is regarded on one side as a man-made feature (E25) which is found on a place (E53) located on the carrier object (E18). On the other side it is regarded as an immaterial visual item, which can be found on many carriers in the same form.
Type: Functional Overview
Material and Technique Information
Comment:
Motivation for this graph has been the Material and Technique Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about the materials and techniques that were used on museum things, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, material and technique information supports Security, Access, and an Historic archive. It can be of primary importance in identifying high value, and therefore high risk, objects. It is also a key information area for the research of man made objects and should record the following information categories:
- Material
- Technique
- Part or component description
Type: Functional Overview
Measurement Information
Comment:
Motivation for this unirt has been the MeasurementInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about the activity of measuring things, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, Object Measurement information supports Security, Accountability, and Access in that it may be the only way of establishing whether or not an object is really that which is described in the documentation. It can be of particular research importance for natural science collections. Measurements can also indicate how easy it is to access and move an object and should record the following information categories:
- Dimension
- Measurement
- Measurement unit
- Measured part
Type: Functional Overview
Object Association Information
Comment:
Motivation for this unit has been the Object Association Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, object association information supports Access and an Historic archive. It can be recorded for all types of collection disciplines and should include the following information categories:
- Associated place
- Associated date
- Associated group/person name
- Association type
- Original function
Type: Functional Overview
Object Collection Information
Comment:
Motivation for this unit has been the Object Collection Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge about object collection, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, origin information supports Security, Accountability, Access, and an Historic archive. It can be applied to collections management areas as well as object history and description areas. It supports the documentation of the collection or the discovery of natural science specimens and archaeological and ethnographical objects and can be recorded for all types of collection disciplines. It should include the following information categories:
- Collection place
- Collection date
- Collector
- Collection method
Type: Functional Overview
Object Entry Information
Comment:
Motivation for this graph has been the Object EntryInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, Object entry information supports Security, Accountability, Access, and an Historic archive. Enabling the recording of information about objects in a museum's custody but which it does not necessarily own, Object entry information should be recorded for objects deposited temporarily or on loan to the museum. It should include the following information categories:
- Current owner
- Depositor
- Entry date
- Entry number
- Entry reason
Type: Functional Overview
Object Name and Classification Information
Comment:
Motivation for this unit has been the Object Name Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, this information primarily supports Accountability, Access, and an Historic archive. At a collection level the Object name is of primary importance in establishing the range of object or specimen type available. It should include the following information categories:
- Object name
- Object name type
- Object name authority
Frequently object names are confused with classification. The CIDOC CRM regards as object name only proper names (such as “Mona Lisa”) and object identifiers. ‘Names’ such as “wine goblet” are indeed classes (E55 Type).
Type: Functional Overview
Object Number Information
Comment:
Motivation for this unit has been the Object NumberInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, this information supports Security, Accountability, and Access. Without an Object number it is not possible either to uniquely identify an object or to link an object with its documentation. The Object number should be marked on, or otherwise physically associated with the object. The following information categories should be recorded:
- Object number
- Object number type
- Object number date
Type: Functional Overview
Object Production Information
Comment:
This unit should be seen together with Materials and Techniques.
Motivation for this unit has been the Object Production Information Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, object production information supports Security, Accountability, Access, and an Historic archive. It can be applied to collections management areas as well as object history and description areas. It supports the documentation of the production of man made objects. As such it is required for all types of collection disciplines. The following information categories should be recorded:
- Production place
- Production date
- Production group/person name
- Production role
Type: Functional Overview
Object Title Information
Comment:
Motivation for this unit has been the Object TitleInformation Group of the International Guidelines for Museum Object Information: The CIDOC Information Categories and other domain expert knowledge, as well as interpretation of characteristic database schema elements from relevant collection management systems.
According to the International Guidelines for Museum Object Information: The CIDOC Information Categories, Object title information supports Security, Access, and an Historic archive. Often the primary identification of fine art and other high value objects, the Object title is essential for describing such collections. It is also a primary point of access to object information for all types of user. It should include the following information categories.
- Title
- Title type
- Title translation
Type: Functional Overview
P1 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use which form part of the world the model intends to describe and not merely for internal database identifiers which are specific to a technical system unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 6.0
P1 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 5.0.2
P1 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use which form part of the world the model intends to describe and not merely for internal database identifiers which are specific to a technical system unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 6.2
P1 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by Rome (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 4.1
P1 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use which form part of the world the model intends to describe and not merely for internal database identifiers which are specific to a technical system unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 6.2.1
P1 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the naming or identification of any real-world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e., indirect) path through E15 Identifier Assignment.
This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned to E42 Identifier.
It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form to E41 Appellation.
Examples:
- The capital of Italy (E53) is identified by “Rome” (E41). (Leach, 2017)
- Text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35). (Gibbon, 2013)
Type: Property
Belongs to version: version 7.1.1
P1 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use which form part of the world the model intends to describe and not merely for internal database identifiers which are specific to a technical system unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 5.1.2
P1 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 5.0.1
P1 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use which form part of the world the model intends to describe and not merely for internal database identifiers which are specific to a technical system unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 6.1
P1 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
This property is a shortcut for the path from E1 CRM Entity through P140i was attributed by, E15 Identifier Assignment, P37 assigned, E42 Identifier.
It is also a shortcut for the path from E1 CRM Entity through P1 is identified by, E41 Appellation, P139 has alternative form, E41 Appellation..
Examples:
- the capital of Italy (E53) is identified by “Rome” (E41) (Leach 2017)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35) (Gibbon 2013)
Type: Property
Belongs to version: version 7.1
P1 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier.
Examples:
- the capital of Italy (E53) is identified by “Rome” (E48)
- text 25014–32 (E33) is identified by “The Decline and Fall of the Roman Empire” (E35)
Type: Property
Belongs to version: Version 6.2.2
P10 falls within
Quantification: many to many (0,n:0,n)
Scope note:
This property associates an instance of E92 Spacetime Volume with another instance of E92 Spacetime Volume that falls within the latter. In other words, all points in the former are also points in the latter.
This property is transitive.
Examples:
- the Great Plague (E4) falls within The Gothic period (E4)
Type: Property
Belongs to version: Version 6.2.2
P10 falls within
Quantification: many to many (0,n:0,n)
Scope note:
This property describes an instance of E4 Period which falls within the E53 Place and E52 Time-Span of another. The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of) P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different type.
Examples:
- the Great Plague (E4) falls within The Gothic period (E4)
Type: Property
Belongs to version: Version 6.0
P10 falls within
Quantification: many to many (0,n,0,n)
Scope note:
This property describes an instance of E4 Period, which falls within the E53 Place and E52 Time-Span of another.
The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of), P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different type.
Examples:
- the Great Plague (E4) falls within The Gothic period (E4)
Type: Property
Belongs to version: Version 5.0.2