Concept Search
Showing 2710 results:
E41 Appellation
Scope note:
This class comprises signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class or category within a certain context.
Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but instead by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes.
Specific subclasses of E41 Appellation should be used when instances of E41 Appellation of a characteristic form are used for particular objects. Instances of E49 Time Appellation, for example, which take the form of instances of E50 Date, can be easily recognised.
E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment
Examples:
- "Martin"
- "the Forth Bridge"
- "the Merchant of Venice" (E35)
- "Spigelia marilandica (L.) L." [not the species, just the name]
- "information science" [not the science itself, but the name through which we refer to it in an English-speaking context]
- “安” [Chinese “an”, meaning “peace”]
Type: Entity
Belongs to version: Version 5.1.2
E41 Appellation
Scope note:
This class comprises signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class or category within a certain context.
Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but instead by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes.
Specific subclasses of E41 Appellation should be used when instances of E41 Appellation of a characteristic form are used for particular objects. Instances of E49 Time Appellation, for example, which take the form of instances of E50 Date, can be easily recognised.
E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment
Examples:
- "Martin"
- "the Forth Bridge"
- "the Merchant of Venice" (E35)
- "Spigelia marilandica (L.) L." [not the species, just the name]
- "information science" [not the science itself, but the name through which we refer to it in an English-speaking context]
- “安” [Chinese “an”, meaning “peace”]
Type: Entity
Belongs to version: Version 6.0
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. Postal addresses, telephone numbers, urls and e-mail addresses are characteristic examples of identifiers used by services transporting things between clients.
The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules] (Reaney, 1974)
- “+41 22 418 5571”
- weasel@paveprime.com
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: version 7.1
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 6.2
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 5.0.1
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 6.2.1
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. Postal addresses, telephone numbers, urls and e-mail addresses are characteristic examples of identifiers used by services transporting things between clients.
The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1” (fictitious)
- “ISSN 0041-5278” [Identifier for “The Unesco courier (Print)”]
- “ISRC FIFIN8900186” [Identifier for : Kraft (29 min 14 s) / Magnus Lindberg, comp. ; Toimii Ensemble ; Swedish Radio symphony orchestra ; Esa-Pekka Salonen, dir.]
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules] (Reaney, 1974)
- “+41 22 418 5571”
- weasel@paveprime.com
- “Rue David Dufour 5, CH-1211, Genève”
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
Type: Entity
Belongs to version: version 7.1.1
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 6.1
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 5.0.2
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 6.2.2
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 5.1.2
E42 Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- “MM.GE.195”
- “13.45.1976”
- “OXCMS: 1997.4.1”
- ISSN “0041-5278”
- ISRC “FIFIN8900116”
- Shelf mark “Res 8 P 10”
- “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]
Type: Entity
Belongs to version: Version 6.0
E42 Object Identifier
Scope note:
This class comprises codes assigned to objects in order to identify them uniquely within the context of one or more organisations.
Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Object Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- MM.GE.195
- 13.45.1976
- DPS_1000
- OXCMS: 1997.4.1
Type: Entity
Belongs to version: Version 4.1
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
Type: Entity
Belongs to version: Version 6.2
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- Vienna
- CH-1211, Genève
- Aquae Sulis Minerva
- Bath
- Cambridge
- the Other Place
- the City
Type: Entity
Belongs to version: Version 5.0.1
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
Type: Entity
Belongs to version: Version 6.2.1
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- Vienna
- CH-1211, Genève
- Aquae Sulis Minerva
- Bath
- Cambridge
- the Other Place
- the City
Type: Entity
Belongs to version: Version 4.1
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
Type: Entity
Belongs to version: Version 6.1
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
Type: Entity
Belongs to version: Version 5.0.2
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
Type: Entity
Belongs to version: Version 6.2.2
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
Type: Entity
Belongs to version: Version 5.1.2
E44 Place Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- “Vienna”
- “CH-1211, Genève”
- “Aquae Sulis Minerva”
- “Bath”
- “Cambridge”
- “the Other Place”
- “the City”
Type: Entity
Belongs to version: Version 6.0
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: Version 5.1.2
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: Version 6.2
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- 1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan
- Rue David Dufour 5, CH-1211, Genève
Type: Entity
Belongs to version: Version 5.0.1
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: Version 6.2.1
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- 1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan
- Rue David Dufour 5, CH-1211, Genève
Type: Entity
Belongs to version: Version 4.1
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: Version 6.1
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: Version 5.0.2
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: Version 6.2.2
E45 Address
Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- “1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan”
- “Rue David Dufour 5, CH-1211, Genève”
Type: Entity
Belongs to version: Version 6.0
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- “the entrance lobby to the Ripley Center”
- “the poop deck of H.M.S Victory”
- “the Venus de Milo’s left buttock”
- “left inner side of my box”
Type: Entity
Belongs to version: Version 6.2
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- the entrance lobby to the Ripley Center
- the poop deck of H.M.S Victory
- the Venus de Milo’s left buttock
- left inner side of my box
Type: Entity
Belongs to version: Version 5.0.1
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- “the entrance lobby to the Ripley Center”
- “the poop deck of H.M.S Victory”
- “the Venus de Milo’s left buttock”
- “left inner side of my box”
Type: Entity
Belongs to version: Version 6.2.1
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- the entrance lobby to the Ripley Center
- the poop deck of H.M.S Victory
- the Venus de Milo’s left buttock
- left inner side of my box
Type: Entity
Belongs to version: Version 4.1
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- “the entrance lobby to the Ripley Center”
- “the poop deck of H.M.S Victory”
- “the Venus de Milo’s left buttock”
- “left inner side of my box”
Type: Entity
Belongs to version: Version 6.1
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- “the entrance lobby to the Ripley Center”
- “the poop deck of H.M.S Victory”
- “the Venus de Milo’s left buttock”
- “left inner side of my box”
Type: Entity
Belongs to version: Version 5.0.2
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- “the entrance lobby to the Ripley Center”
- “the poop deck of H.M.S Victory”
- “the Venus de Milo’s left buttock”
- “left inner side of my box”
Type: Entity
Belongs to version: Version 5.1.2
E46 Section Definition
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier ).
Examples:
- “the entrance lobby to the Ripley Center”
- “the poop deck of H.M.S Victory”
- “the Venus de Milo’s left buttock”
- “left inner side of my box”
Type: Entity
Belongs to version: Version 6.0
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
Type: Entity
Belongs to version: Version 6.2
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- 6°5’29”N 45°12’13”W
- Black queen’s bishop 4 [chess coordinate]
Type: Entity
Belongs to version: Version 5.0.1
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
Type: Entity
Belongs to version: Version 6.2.1
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- 6°5’29”N 45°12’13”W
- Black queen’s bishop 4 [chess coordinate]
Type: Entity
Belongs to version: Version 4.1
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
Type: Entity
Belongs to version: Version 6.1
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
Type: Entity
Belongs to version: Version 5.0.2
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
Type: Entity
Belongs to version: Version 6.2.2
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
Type: Entity
Belongs to version: Version 5.1.2
E47 Spatial Coordinates
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- “6°5’29”N 45°12’13”W”
- “Black queen’s bishop 4” [chess coordinate]
Type: Entity
Belongs to version: Version 6.0
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
Type: Entity
Belongs to version: Version 6.2
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- Greece
- Athens
- Geneva
- Lac Léman
Type: Entity
Belongs to version: Version 5.0.1
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
Type: Entity
Belongs to version: Version 6.2.1
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- Greece
- Athens
- Geneva
- Lac Léman
Type: Entity
Belongs to version: Version 4.1
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
Type: Entity
Belongs to version: Version 6.1
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
Type: Entity
Belongs to version: Version 5.0.2
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
Type: Entity
Belongs to version: Version 6.2.2
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
Type: Entity
Belongs to version: Version 5.1.2
E48 Place Name
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- “Greece”
- “Athens”
- “Geneva”
- “Lac Léman”
Type: Entity
Belongs to version: Version 6.0
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
Type: Entity
Belongs to version: Version 6.2
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- Meiji [Japanese term for a specific time-span]
- 1st half of the XX century
- Quaternary
- 1215 Hegira [a date in the Islamic calendar]
- Last century
Type: Entity
Belongs to version: Version 5.0.1
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
Type: Entity
Belongs to version: Version 6.2.1
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- Meiji [Japanese term for a specific time-span]
- 1st half of the XX century
- Quaternary
- 1215 Hegira [a date in the Islamic calendar]
- Last century
Type: Entity
Belongs to version: Version 4.1
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
Type: Entity
Belongs to version: Version 6.1
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
Type: Entity
Belongs to version: Version 5.0.2
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
Type: Entity
Belongs to version: Version 6.2.2
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
Type: Entity
Belongs to version: Version 5.1.2
E49 Time Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.
Examples:
- “Meiji” [Japanese term for a specific time-span]
- “1st half of the XX century”
- “Quaternary”
- “1215 Hegira” [a date in the Islamic calendar]
- “Last century”
Type: Entity
Belongs to version: Version 6.0
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 6.2.1
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Lisbon by earthquake in 1755 (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 4.1
E5 Event
Scope note:
This class comprises distinct, delimited and coherent processes and interactions of a material nature, in cultural, social or physical systems, involving and affecting instances of E77 Persistent Item in a way characteristic of the kind of process. Typical examples are meetings, births, deaths, actions of decision taking, making or inventing things, but also more complex and extended ones such as conferences, elections, building of a castle, or battles.
While the continuous growth of a tree lacks the limits characteristic of an event, its germination from a seed does qualify as an event. Similarly, the blowing of the wind lacks the distinctness and limits of an event, but a hurricane, flood or earthquake would qualify as an event. Mental processes are considered as events, in cases where they are connected with the material externalization of their results; for example, the creation of a poem, a performance or a change of intention that becomes obvious from subsequent actions or declarations.
The effects of an instance of E5 Event may not lead to relevant permanent changes of properties or relations of the items involved in it, for example an unrecorded performance. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event.
While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example, the statements made during a meeting and the listening of the audience.
Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analyzed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the size of the phenomena. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy overall effect and are thus not instances of E5 Event.
Examples:
- the birth of Cleopatra (E67) (Pomeroy, 1984)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6) (Camardo, 2013)
- World War II (E7) (Barber, 1994)
- the Battle of Stalingrad (E7) (Hoyt, 1993)
- the Yalta Conference (E7) (Harbutt, 2010)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday (fictitious)
- the CIDOC conference 2003 (E7)
Type: Entity
Belongs to version: version 7.1.1
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 6.1
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 5.1.2
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 5.0.2
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 6.2.2
E5 Event
Scope note:
This class comprises distinct, delimited and coherent processes and interactions of a material nature, in cultural, social or physical systems, involving and affecting instances of E77 Persistent Item in a way characteristic of the kind of process. Typical examples are meetings, births, deaths, actions of decision taking, making or inventing things, but also more complex and extended ones such as conferences, elections, building of a castle, or battles.
While the continuous growth of a tree lacks the limits characteristic of an event, its germination from a seed does qualify as an event. Similarly, the blowing of the wind lacks the distinctness and limits of an event, but a hurricane, flood or earthquake would qualify as an event. Mental processes are considered as events, in cases where they are connected with the material externalization of their results; for example, the creation of a poem, a performance or a change of intention that becomes obvious from subsequent actions or declarations.
The effects of an instance of E5 Event may not lead to relevant permanent changes of properties or relations of the items involved in it, for example an unrecorded performance. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event.
While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example, the statements made during a meeting and the listening of the audience.
Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analyzed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the size of the phenomena. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy overall effect and are thus not instances of E5 Event.
Examples:
- the birth of Cleopatra (E67) (Pomeroy, 1984)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6) (Camardo, 2013)
- World War II (E7) (Barber, 1994)
- the Battle of Stalingrad (E7) (Hoyt, 1993)
- the Yalta Conference (E7) (Harbutt, 2010)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday (fictitious)
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: version 7.1
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 6.2
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Herculaneum by volcanic eruption in 79 AD (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 6.0
E5 Event
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Lisbon by earthquake in 1755 (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
Type: Entity
Belongs to version: Version 5.0.1
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
Type: Entity
Belongs to version: Version 6.2
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- 1900
- 4-4-1959
- 19-MAR-1922
- 19640604
Type: Entity
Belongs to version: Version 5.0.1
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
Type: Entity
Belongs to version: Version 6.2.1
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- 1900
- 4-4-1959
- 19-MAR-1922
- 19640604
Type: Entity
Belongs to version: Version 4.1
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
Type: Entity
Belongs to version: Version 6.1
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
Type: Entity
Belongs to version: Version 5.0.2
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
Type: Entity
Belongs to version: Version 6.2.2
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
Type: Entity
Belongs to version: Version 5.1.2
E50 Date
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- “1900”
- “4-4-1959”
- “19-MAR-1922”
- “19640604”
Type: Entity
Belongs to version: Version 6.0
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
Type: Entity
Belongs to version: Version 6.2
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used..
Examples:
- +41 22 418 5571
- weasel@paveprime.com
Type: Entity
Belongs to version: Version 5.0.1
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
Type: Entity
Belongs to version: Version 6.2.1
E51 Contact Point
Scope note:
This class comprises identifiers used to communicate with instances of E39 Actor.
These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. The E45 Address subclass should be used in such cases.
Examples:
- +41 22 418 5571
- weasel@paveprime.com
Type: Entity
Belongs to version: Version 4.1
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
Type: Entity
Belongs to version: Version 6.1
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
Type: Entity
Belongs to version: Version 5.1.2
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used..
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
Type: Entity
Belongs to version: Version 5.0.2
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
Type: Entity
Belongs to version: Version 6.2.2
E51 Contact Point
Scope note:
This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
Examples:
- “+41 22 418 5571”
- “weasel@paveprime.com”
Type: Entity
Belongs to version: Version 6.0
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Instances of E52 Time-Span have no semantic connotations about phenomena happening within the temporal extent they represent. They do not convey any meaning other than a positioning on the “time-line” of chronology. The actual extent of an instance of E52 Time-Span can be approximated by properties of E52 Time-Span giving inner and outer bounds in the form of dates (instances of E61 Time Primitive). Comparing knowledge about time-spans is fundamental for chronological reasoning.
Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr & Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which we can infer knowledge about it, such as in relative chronologies.
Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr & Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which we can infer knowledge about it, such as in relative chronologies.
Some instances of E52 may be defined precisely as representing a declaration of a temporal extent, as, for instance, done in a business contract. They constitute declarative time-spans as defined in CRMgeo (Doerr & Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span.
When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty (Chan, 2011)
Type: Entity
Belongs to version: version 7.1
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 6.2
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 5.0.1
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Type: Entity
Belongs to version: Version 6.2.1
E52 Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Instances of E52 Time-Span have no semantic connotations about phenomena happening within the temporal extent they represent. They do not convey any meaning other than a positioning on the “time-line” of chronology. The actual extent of an instance of E52 Time-Span can be approximated by properties of E52 Time-Span giving inner and outer bounds in the form of dates (instances of E61 Time Primitive). Comparing knowledge about time-spans is fundamental for chronological reasoning.
Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr & Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which we can infer knowledge about it, such as in relative chronologies.
Some instances of E52 may be defined precisely as representing a declaration of a temporal extent, as, for instance, done in a business contract. They constitute declarative time-spans as defined in CRMgeo (Doerr & Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span.
When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known.
Examples:
- 1961
- From 12-17-1993 to 12-8-1996
- 14h30 – 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- the time-span of the Ming Dynasty (Chan, 2011)
Type: Entity
Belongs to version: version 7.1.1