MarineTLO Ontology
type: Ontology
modified: 2014-04-24
issued: 2014-04-24
version info: 4.0
description: MarineTLO is a top-level ontology for the marine domain (also applicable to the terrestrial domain).
contributor: Carlo Allocca
rights: Copyright © FORTH ICS
contributor: Julien Barde
contributor: Nikos Minadakis
creator: Chrysoula Bekiari
creator: Carlo Allocca
contributor: Martin Doerr
creator: Nikos Minadakis
creator: Martin Doerr
contributor: Chrysoula Bekiari
license: http://creativecommons.org/licenses/by/3.0/
contributor: ~fafalios
creator: ~fafalios
contributor: aboutme.html
creator: aboutme.html
contributor: ~tzitzik
creator: ~tzitzik
publisher: isl

LC10 belongs to
type: ObjectProperty
comment: This property associates a physical thing like biotic or abiotic element with the biotic element or abiotic which is part of or member.
term status: stable
domain: BC35 Physical Thing
range: BC35 Physical Thing

LC10 has member
type: ObjectProperty
term status: stable

LC11 had participant
type: ObjectProperty
term status: stable
comment: This property describes the active or passive participation of instances of E39 Actors in an E5 Event. It connects the life-line of the related E39 Actor with the E53 Place and E50 Date of the event. The property implies that the Actor was involved in the event but does not imply any causal relationship. The subject of a portrait can be said to have participated in the creation of the portrait. [Scope Note for P11 had participant (participated in) CIDOC CRM version 5.1.2]
domain: BC10 Event
range: BC8 Actor

LC11 participated in
type: ObjectProperty
term status: stable
inverse of: LC11 had participant

LC12 assigned attribute to
type: ObjectProperty
term status: stable
comment: This property indicates the item to which an attribute or relation is assigned.
range: BC1 TLO Entity
domain: BC44 Attribute Assignment

LC12 was attributed by
type: ObjectProperty
term status: stable
inverse of: LC12 assigned attribute to

LC13 is carried out by
type: ObjectProperty
term status: stable
comment: This property describes the active participation of a BC8 Actor in an BC43 Activity.
domain: BC43 Activity
range: BC8 Actor

LC13 performed
type: ObjectProperty
term status: stable
inverse of: LC13 is carried out by

LC15 took place at
type: ObjectProperty
comment: This property describes the spatial location of an instance of a BC4 Temporal Phenomenon. The related BC3 Place should be seen as an approximation of the geographical area within which the phenomena that characterize the period in question occurred.
term status: stable
range: BC3 Place
domain: BC4 Temporal Phenomenon

LC15 witnessed
type: ObjectProperty
term status: stable
inverse of: LC15 took place at

LC16 forms part of
type: ObjectProperty
term status: stable
inverse of: LC16 is composed of

LC16 is composed of
type: ObjectProperty
term status: stable
comment: This property allows instances of E18 Physical Thing to be analysed into component elements. Component elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall. This property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property. The instances of E57 Materials of which an item of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in). [Scope Note for P46 is composed of (forms part of)CIDOC CRM version 5.1.2]
range: BC35 Physical Thing
domain: BC35 Physical Thing

LC17 observed
type: ObjectProperty
comment: This property identifies a thing, a feature, a phenomenon or its reaction that is observed by an activity of Observation.
term status: stable
domain: BC45 Observation
range: BC9 Observable Entity
inverse of: LC17 was observed during

LC19 has dimension
type: ObjectProperty
comment: This property records a E54 Dimension of some E70 Thing. It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. An instance of E54 Dimension is specific to an instance of E70 Thing. [Scope Note for P43 has dimension (is dimension of)CIDOC CRM version 5.1.2] This property records a E54 Dimension of some E70 Thing. It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. An instance of E54 Dimension is specific to an instance of E70 Thing. [Scope Note for P43 has dimension (is dimension of)CIDOC CRM version 5.1.2]
term status: stable
range: BC5 Dimension
domain: BC7 Thing

LC19 is dimension of
type: ObjectProperty
term status: stable
inverse of: LC19 has dimension

LC1 is identified by
type: ObjectProperty
term status: stable
comment: 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. [Scope Note for P1 is identified by (identifies). CIDOC CRM version 5.1.2].
domain: BC1 TLO Entity
range: BC30 Appellation

LC21 has unit
type: ObjectProperty
term status: stable
comment: This property shows the type of unit a BC5 Dimension was expressed in.
range: BC55 Measurement Unit
domain: BC5 Dimension

LC21 is unit of
type: ObjectProperty
term status: stable
inverse of: LC21 has unit

LC22 approximates
type: ObjectProperty
comment: This property approximates an BC3 Place which is defined in the same reference space. The property does not state the quality or accuracy of the approximation, but states the intention to approximate the place.
term status: stable
domain: BC20 Declarative Place
range: BC3 Place

LC23 is expressed in terms of
type: ObjectProperty
term status: stable
comment: This property defines the coordinate reference system in terms of which a geometric place expression is formulated.
range: BC29 Spatial Coordinate Reference System
domain: BC34 Geometric Place Expression

LC24 defines place
type: ObjectProperty
term status: stable
comment: This property associates an instance of BC34 Geometric Place Expression with the instance of BC20 Declarative Place it defines. Syntactic variants or use of different scripts may result in multiple instances of BC34 Geometric Place Expression defining exactly the same place. Transformations between different reference systems in general result in new definitions of places approximating each other.
range: BC20 Declarative Place
domain: BC34 Geometric Place Expression

LC27 has section
type: ObjectProperty
term status: stable
comment: This property links an area to the instance of E18 Physical Thing upon which it is found. [Scope Note for P59 has section (is located on or within)CIDOC CRM version 5.1.2]
domain: BC35 Physical Thing
range: BC3 Place

LC27 is located on or within
type: ObjectProperty
term status: stable
inverse of: LC27 has section

LC28 has dimension
type: ObjectProperty
term status: stable
comment: This property records a BC5 Dimension of a BC9 Observable Entity. It is a shortcut of the more fully developed path from a BC9 Observable Entity through LC37 measured (was measured by), BC54 Measurement LC34 observed dimension (was observed in) to BC5 Dimension. It offers no information about how and when an E54 Dimension was established.
range: BC5 Dimension
domain: BC9 Observable Entity

LC29 had output
type: ObjectProperty
comment: This property associates an instance of BC56 Digital Measurement Event with an instance of BC23 Digital Object which is the output of the activity.
term status: stable
range: BC23 Digital Object
domain: BC56 Digital Measurement Event

LC2 is referred by
type: ObjectProperty
term status: stable
inverse of: LC2 refers to

LC2 refers to
type: ObjectProperty
term status: stable
comment: This property documents that a BC18 Proposition makes a statement about an instance of BC1 TLO Entity.
domain: BC18 Proposition
range: BC1 TLO Entity

LC30 had input
type: ObjectProperty
comment: This property associates an instance of BC56 Digital Measurement Event with an instance of BC23 Digital Object which is the input used to specify the machine action.
term status: stable
range: BC23 Digital Object
domain: BC56 Digital Measurement Event

LC31 used software
type: ObjectProperty
term status: stable
comment: This property associates an instance of BC56 Digital Measurement Event with the instance of BC59 Software.
domain: BC56 Digital Measurement Event
range: BC59 Software

LC32 happened on device
type: ObjectProperty
term status: stable
comment: This property associates an instance of BC56 Digital Measurement Event with the instance of BC58 Digital Device that had used.
domain: BC56 Digital Measurement Event
range: BC58 Digital Device

LC33 captures
type: ObjectProperty
comment: This property associates an instance of BC61 Capture Activity with the instance of BC57 Capture.
term status: stable
range: BC57 Capture
domain: BC61 Capture Activity

LC34 observed dimension
type: ObjectProperty
term status: stable
comment: This property records the dimension that was observed in an E16 Measurement Event. E54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object. Dimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant. [Scope Note for P40 observed dimension (was observed in)CIDOC CRM version 5.1.2].
domain: BC54 Measurement
range: BC5 Dimension

LC35 describes
type: ObjectProperty
term status: stable
comment: This property associates an instance of SP4 Spatial Coordinate Reference System with the instance of SP3 Reference Space for which it can be used to describe locations. [Scope Note for Q7 Describes CRMgeo].
range: BC1 TLO Entity
domain: BC29 Spatial Coordinate Reference System

LC36 is fixed on
type: ObjectProperty
term status: stable
comment: This property defines the physical reference features that ground a spatial coordinate reference system in the real world. [Scope Note for Q8 is fixed on CRMgeo].
domain: BC29 Spatial Coordinate Reference System
range: BC35 Physical Thing

LC37 measured
type: ObjectProperty
comment: This property associates an instance of E16 Measurement with the instance of E1 CRM Entity to which it applied. An instance of E1 CRM Entity may be measured more than once. Material and immaterial things and processes may be measured, e.g. the number of words in a text, or the duration of an event. [Scope Note for P39 measured (was measured by)CIDOC CRM version 5.1.2].
term status: stable
range: BC1 TLO Entity
domain: BC54 Measurement

LC37 was measured by
type: ObjectProperty
term status: stable
inverse of: LC37 measured

LC38 folls within or overlaps
type: ObjectProperty
term status: stable
comment: This property identifies the instances of Places that overlaps or fall within the area covered by another Place.
domain: BC3 Place
range: BC3 Place
sub property of: topObjectProperty

LC43 occupied
type: ObjectProperty
comment: This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime. [Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM].
term status: stable
domain: BC4 Temporal Phenomenon
range: BC72 SpaceTime Volume

LC44 has temporal projection
type: ObjectProperty
term status: stable
comment: This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime. [Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM].
range: BC2 Time Span
domain: BC72 SpaceTime Volume

LC45 has spatial projection
type: ObjectProperty
term status: stable
comment: This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime. [Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM].
range: BC3 Place
domain: BC72 SpaceTime Volume

LC46 observed value
type: ObjectProperty
comment: This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime. [Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM]
term status: stable
range: BC1 TLO Entity
domain: BC45 Observation

LC47 took place at
type: ObjectProperty
term status: stable
comment: This property associates an instance of BC61 Capture Activity with an instance of BC3 Place at which the capture activity found or captured things. It identifies the narrower spatial location in which a thing was found at. This maybe known or given in absolute terms or relative to the thing found. It describes a position within the area in which the instance of the encounter event occurred and found something.
range: BC1 TLO Entity
domain: BC45 Observation

LC48 assigned dimension
type: ObjectProperty
comment: This property associates an instance of BC61 Capture Activity with an instance of BC3 Place at which the capture activity found or captured things. It identifies the narrower spatial location in which a thing was found at. This maybe known or given in absolute terms or relative to the thing found. It describes a position within the area in which the instance of the encounter event occurred and found something.
term status: stable
range: BC1 TLO Entity
domain: BC5 Dimension

LC4 has appellation
type: ObjectProperty
term status: stable
comment: This property associates an instance of BC1 TLO Entity with an instance of BC30 Appellation. This property is intended for names in general use. The property does not reveal anything about when, where and by whom this name was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through BC46 Identifier Assignment.
domain: BC1 TLO Entity
range: BC30 Appellation

LC4 is appellation of
type: ObjectProperty
term status: stable
inverse of: LC4 has appellation

LC5 has time span
type: ObjectProperty
term status: stable
comment: This property describes the temporal bounds of an instance of an E2 Temporal Phenomenon.
range: BC2 Time Span
domain: BC4 Temporal Phenomenon

LC5 is time span of
type: ObjectProperty
term status: stable
inverse of: LC5 has time span

LC6 has alternative form
type: ObjectProperty
comment: This property establishes a relationship of equivalence between two instances of E41 Appellation independent from any item identified by them. It is a dynamic asymmetric relationship, where the range expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. The relationship is not transitive. The equivalence applies to all cases of use of an instance of E41 Appellation. Multiple names assigned to an object, which are not equivalent for all things identified with a specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies). [Scope Note for P139 has alternative form CIDOC CRM version 5.1.2]
term status: stable

LC7 is about
type: ObjectProperty
comment: This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an E1 CRM Entity, in that it describes the primary subject or subjects of an E89 Propositional Object. [Scope Note for P129 is about (is subject of) CIDOC CRM version 5.1.2]
term status: stable
domain: BC18 Proposition
range: BC1 TLO Entity

LC8 occured in the presence of
type: ObjectProperty
comment: This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role. It connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers. [Scope Note for P12 occurred in the presence of (was present at) CIDOC CRM version 5.1.2]
term status: stable
domain: BC10 Event
range: BC6 Persistent Item

LC8 was present at
type: ObjectProperty
term status: stable
inverse of: LC8 occured in the presence of

LC9 assigned
type: ObjectProperty
term status: stable
comment: This property indicates the attribute that was assigned or the item that was related to the item denoted by a property P140 assigned attribute to in an Attribute assignment action. [Scope Note for P141 assigned (was assigned by) CIDOC CRM version 5.1.2]
range: BC1 TLO Entity
domain: BC44 Attribute Assignment

LC9 was assigned by
type: ObjectProperty
term status: stable
inverse of: LC9 assigned

LT1 usually is identified by
type: ObjectProperty
term status: stable
comment: This property describes the type of appellation of a TLO entity type.
domain: BC1 TLO Entity
range: BT14 Appellation Type
inverse of: LT1 usually identifies

LT2 usually consists of
type: ObjectProperty
comment: This property describes the types of components of an Temporal Phenomenon Type.
term status: stable
range: BT2 Temporal Phenomenon Type
domain: BT2 Temporal Phenomenon Type
sub property of: topObjectProperty

LT2 usually is component of
type: ObjectProperty
term status: stable
inverse of: LT2 usually consists of

LT3 usaually is component of
type: ObjectProperty
comment: This property connects the type of a biotic element with the type of the Ecosystem where it lives.
term status: stable
domain: BT10 Biotic Element Type
range: BT7 Ecosystem Type

LT3 usually has component
type: ObjectProperty
term status: stable
range: BT10 Biotic Element Type
domain: BT7 Ecosystem Type
inverse of: LT3 usaually is component of

LT4 usually appears to
type: ObjectProperty
term status: stable
inverse of: LT4 usually use to appear

LT4 usually use to appear
type: ObjectProperty
comment: This property connects the type of a biotic element with the type of a biotic element where it appears.
term status: stable
domain: BT10 Biotic Element Type
range: BT10 Biotic Element Type

LT5 usually is predator of
type: ObjectProperty
comment: This property connects the types of predators with their prey type.
term status: stable
range: BT10 Biotic Element Type
domain: BT10 Biotic Element Type

LT5 usually is prey of
type: ObjectProperty
term status: stable
inverse of: LT5 usually is predator of

LT6 usually is about
type: ObjectProperty
comment: This property associates a type of a conceptual object such as propositions or appellations with an entity type.
term status: stable
range: BT1 TLO Entity Type
domain: BT4 Conceptual Object Type

LT6 usually is subject of
type: ObjectProperty
term status: stable
inverse of: LT6 usually is about

LT7 usually is carried out by
type: ObjectProperty
term status: stable
comment: This property associates a type of activity with a type of actor.
domain: BT17 Human Activity Type
range: BT9 Actor Type

LT7 usually performed
type: ObjectProperty
term status: stable
inverse of: LT7 usually is carried out by

LT8 usually belongs to
type: ObjectProperty
term status: stable
comment: This property associates a type of biotic element with the type of biotic element which is part of or member.
domain: BT3 Physical Thing Type
range: BT3 Physical Thing Type

LT8 usually has member
type: ObjectProperty
term status: stable
inverse of: LT8 usually belongs to
sub property of: topObjectProperty

LX1 is identified by
type: ObjectProperty
term status: stable
comment: This property describes the types of identifiers, names or labels of any marineTLO item type.
range: BC30 Appellation
domain: BT1 TLO Entity Type

LX2 is about type
type: ObjectProperty
comment: This property documents that an instance of BC17 Conceptual Object is a subject of an instance of BT1 TLO Entity Type.
term status: stable
domain: BC17 Conceptual Object
range: BT1 TLO Entity Type

LX3 has type
type: ObjectProperty
comment: This property allows sub typing of MarineTLO entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus.
term status: stable
domain: BC1 TLO Entity
range: BT1 TLO Entity Type

LX4 has appellation
type: ObjectProperty
comment: This property associates an instance of BT1 TLO Entity Type with an instance of BC7 Appellation.
term status: stable
range: BC30 Appellation
domain: BT1 TLO Entity Type

LX6 assigned attribute to type
type: ObjectProperty
term status: stable
comment: This property indicates the type of item to which an attribute or relation is assigned.
domain: BC44 Attribute Assignment
range: BT32 Persisten Type

LX6 type was attributed by
type: ObjectProperty
term status: stable
inverse of: LX6 assigned attribute to type

LX7 observed propery
type: ObjectProperty
term status: stable
comment: This property identifies the type of Property that is observed by an activity of BC45 Observation. It describes assertions about types of properties of things.
domain: BC45 Observation
range: BT35 Property Type

LX7 was observed in
type: ObjectProperty
term status: stable
inverse of: LX7 observed propery

LX8 has language
type: ObjectProperty
comment: This property declares the Language of a BC18 Proposition.
term status: stable
domain: BC25 Linguistic Object
range: BT36 Language

LX8 is language of
type: ObjectProperty
term status: stable
inverse of: LX8 has language

LC20 has value
type: DatatypeProperty
term status: stable
comment: This property allows a BC5 Dimension to be approximated by Number primitive.
domain: BC5 Dimension
range: real

O3 has note
type: DatatypeProperty
term status: stable
comment: This property associates an entity to MarineTLO Environment with abstraction levels where it is defined.
range: string
domain: Thing

BC10 Event
type: Class
subclass of: BC4 Temporal Phenomenon
subclass of: BC9 Observable Entity
term status: stable
comment: 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. [Scope Note for E5 Event CIDOC CRM version 5.1.2]

BC11 Person
type: Class
subclass of: BC8 Actor
term status: stable
comment: This class comprises real persons who live or are assumed to have lived

BC12 Ecosystem
type: Class
subclass of: BC4 Temporal Phenomenon
comment: This class comprises specific systems consisting of observable material items, biotic, abiotic elements and interactions, as well as their associated relations and qualities in space time volume. Its coherence can be defined by the types of species and the types and frequency of interactions which can be observed in a space time volume.
term status: stable

BC13 Organization
type: Class
subclass of: BC8 Actor
term status: stable
comment: This class comprises any gatherings or organizations of two or more people that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country.

BC14 Ecosystem Environment
type: Class
subclass of: BC35 Physical Thing
comment: This class comprises the physical environment of an ecosystem.
term status: stable

BC15 Water Area
type: Class
subclass of: BC35 Physical Thing
comment: This class comprises generic portions of the sea. A water area can be a statistical area, or an economic zone, or a geographic feature.
term status: stable

BC16 Man-Made thing
type: Class
subclass of: BC7 Thing
term status: stable
comment: This class comprises discrete, identifiable man-made items that are documented as single units. These items are either intellectual products or man-made physical things, and are characterized by relative stability. They may for instance have a solid physical form, an electronic encoding, or they may be logical concepts or structures.

BC17 Conceptual Object
type: Class
subclass of: BC16 Man-Made thing
comment: This class comprises non-material products of our minds and other human produced data that have become objects of a discourse. The production of such information may have been supported by the use of technical devices such as cameras or computers. Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of BC17 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, book, electronic signals, marks, audio media, paintings, photos, human memories, etc. They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost.
term status: stable

BC18 Proposition
type: Class
subclass of: BC17 Conceptual Object
comment: This class comprises immaterial items, including but not limited to scientific papers, 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. Specific subclasses of BC8 Proposition should be used when instances of BC8 Proposition of a characteristic type such as publication, etc are used for particular objects
term status: stable

BC19 Title
type: Class
subclass of: BC25 Linguistic Object
subclass of: BC30 Appellation
term status: stable
comment: This class comprises the names assigned to works, such as texts, artworks or pieces of music. Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group. This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts. [Scope Note for E35 Title CIDOC CRM version 5.1.2]

BC1 TLO Entity
type: Class
term status: stable
comment: This class comprises all objects of the MarineTLO discourse. All classes within this level of the TLO are directly or indirectly specialisations of BC1 TLO Entity

BC20 Declarative Place
type: Class
subclass of: BC3 Place
term status: stable
comment: This class comprises instances of BC3 Place whose extent and position is defined by a BC34 Geometric Place Expression. Instances of BC20 Declarative Places may be used to approximate instances of BC3 Places or parts of them. They may as well be used to define the location and spatial extent of property rights or national borders. Example: Coordinate information in FAO like coordinates <-40,5 -41.0999847,5 -41.9000000,5 -42.200000763,5 -……39.2000000763,5 -40.5>

BC21 Data Set
type: Class
subclass of: BC18 Proposition
comment: This class comprises contents of a single database table, or a single statistical data matrix, where each column of the table represents a particular variable, and each row corresponds to a given member of the dataset in question. The dataset lists values for each of the variables, such as height and weight of an object, for each member of the dataset. Each value is known as a datum. The dataset may comprise data for one or more members, corresponding to the number of rows. The term dataset may also be used more loosely, to refer to the data in a collection of closely related tables, corresponding to a particular experiment or event.
term status: stable

BC22 Encounter Event
type: Class
subclass of: BC45 Observation
term status: stable
comment: This class comprises activities of BC45 Observation (substance) where a BC8 Actor encounters an instance of BC35 Physical Thing of a kind relevant for the mission of the observation or regarded as potentially relevant for some community (identity). This observation produces knowledge about the existence of the respective thing at a particular place in or on surrounding matter. This knowledge may be new to the group of people the actor belongs to. In that case we would talk about a discovery. The observer may recognize or assign an individual identity of the thing encountered or regard only the type as noteworthy in the associated documentation or report.The encounter event supports the detection of a new a new biological kind (“taxon”), also additional parameters may be recorded like the kind of ecosystem or what detection or catching devices have been used.

BC23 Digital Object
type: Class
subclass of: BC18 Proposition
comment: This class comprises identifiable immaterial items that can be represented as sets of bit sequences, such as data sets, e-texts, images, audio or video items, software, etc., and are documented as single units. Any aggregation of instances of BC23 Digital Object into a whole treated as single unit is also regarded as an instance of BC23 Digital Object. A BC23 Digital Object does not depend on a specific physical carrier, and it can exist on one or more carriers simultaneously.
term status: stable

BC24 Repository Object
type: Class
subclass of: BC23 Digital Object
term status: stable
comment: This class comprises data repositories of a set of integrated objects in computer science sense. These objects are modeled using structures defined in database schemas. Digital store includes not only data repositories like databases, it is a more general concept that includes also flat files that can store data. A digital store may contain binary datasets: raw data, normalized data, intermediate data of processing steps, scenes composed from several datasets, presentation objects, 3D models, 2D-Images and any kind of digital document (text, multimedia). It comprises a notion of complex objects, having datasets as parts. The content of a digital store is responsible for holding information about where data-files and their replicas can be found

BC25 Linguistic Object
type: Class
subclass of: BC18 Proposition
comment: This class comprises identifiable expressions in natural language or languages. Instances of BC25 Linguistic Object can be expressed in many ways: e.g. as written texts, recorded speech or sign language.
term status: stable

BC26 Place Name
type: Class
subclass of: BC31 Place Appellation
term status: stable
comment: 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. [Scope Note for E48 Place Name CIDOC CRM version 5.1.2]

BC27 Publication
type: Class
subclass of: BC18 Proposition
term status: stable
comment: This class comprises publication work.

BC29 Spatial Coordinate Reference System
type: Class
subclass of: BC18 Proposition
term status: stable
comment: This class compromises systems that are used to describe locations in a BC3 Place. An instance of BC29 Spatial Coordinate Reference System is composed of two parts: The first is a Coordinate System which is a set of coordinate axes with specified units of measurement and axis directions. The second part is a set of reference features at rest in the real world that relate the Coordinate System to real world locations.

BC2 Time Span
type: Class
subclass of: BC1 TLO Entity
comment: 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 phenomena valid for a certain time. [Scope Note for E52 Time Span in CIDOC CRM version 5.1.2] Instances of BC2 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of BC2 Time-Span are intended to allow these approximations to be expressed precisely.
term status: stable

BC30 Appellation
type: Class
subclass of: BC17 Conceptual Object
term status: stable
comment: 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. [Scope Note for E77 Persistent Item CIDOC CRM version 5.1.2]

BC31 Place Appellation
type: Class
subclass of: BC30 Appellation
term status: stable
comment: 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. [Scope Note for E44 Place Appellation CIDOC CRM version 5.1.2]

BC32 Identifier
type: Class
subclass of: BC30 Appellation
comment: This class comprises strings or codes assigned to instances of BC10 Persistent Item 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. Specific subclasses of BC4 Identifier should be used when instances of BC4 Identifier of a characteristic form or format are used for particular objects
term status: stable

BC33 Spatial Coordinate
type: Class
subclass of: BC30 Appellation
term status: stable
comment: 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. [Scope Note for E47 Spatial Coordinates CIDOC CRM version 5.1.2]

BC34 Geometric Place Expression
type: Class
subclass of: BC33 Spatial Coordinate
term status: stable
comment: This class comprises definitions of places by quantitative expressions. An instance of this class can be seen as a prescription of how to find the location meant by this expression in the real world, which is based on measuring where the quantities referred to in the expression lead to, beginning from the reference points of the respective reference system. A form of expression may be geometries or map elements defined in a Spatial Coordinate Reference System that unambiguously identify locations in a real world space. Other forms may refer to areas confined by imaginary lines connecting Phenomenal Places such as trees, islands, cities, mountain tops.

BC35 Physical Thing
type: Class
subclass of: BC7 Thing
term status: stable
comment: This class comprises constellations of matter with a relative stability of any form sufficient to associate them with a persistent identity, such as being confined to certain extent, which (confinement) can have a relative stability of form or structure, or containing a fixed amount of matter. In particular, it comprises physical things in the narrower sense and fluid bodies. It is an abstraction of physical substance for solid and non-solid things of matter.

BC36 Abiotic Element
type: Class
subclass of: BC35 Physical Thing
term status: stable
comment: This class refers to the abiotic components of an ecosystem. This class comprises nonliving physical components of a system, for example: rocks, soil, etc. in an environment.

BC37 Biological Object
type: Class
subclass of: BC51 Physical Object
comment: This class comprises individual items of a material nature, which live, have lived or are natural products of or from living organisms. Artificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Man-Made Object. [Scope Note for E20 Biological Object CIDOC CRM version 5.1.2]
term status: stable

BC38 Biotic Element
type: Class
subclass of: BC37 Biological Object
comment: This class refers to the biotic components of an ecosystem. This class compromises individual living things that can react to stimuli, reproduce, grow, and maintain homeostasis. It can be a virus, bacterium, protist, fungus, plant, an animal or a human being. [http://www.biology-online.org/]
term status: stable

BC39 Marine Animal
type: Class
subclass of: BC38 Biotic Element
term status: stable
comment: This class comprises any living thing in a marine environment that can move independently and that has senses for recognizing and reacting to the environment around it.

BC3 Place
type: Class
subclass of: BC1 TLO Entity
comment: This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter. The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation. It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
term status: stable

BC40 Physical Man-Made Thing
type: Class
subclass of: BC16 Man-Made thing
subclass of: BC35 Physical Thing
comment: This class comprises man-made objects, such as a swords, and man-made features, such as rock art. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Man-Made Thing. [Scope Note for E24 Physical Man-Made Thing CIDOC CRM version 5.1.2]
term status: stable

BC41 Man-Made Object
type: Class
subclass of: BC40 Physical Man-Made Thing
term status: stable
comment: This class comprises physical objects purposely created by human activity. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, an inscribed piece of rock or a preserved butterfly are both regarded as instances of E22 Man-Made Object. [Scope Note for E22 Man-Made Object CIDOC CRM version 5.1.2]

BC42 Collection
type: Class
subclass of: BC40 Physical Man-Made Thing
term status: stable
comment: This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. Items may be added or removed from an E78 Collection in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Collection often referred to with the name of the E78 Collection (e.g. “The Wallace Collection decided…”). Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Collection. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality. [Scope Note for E78 Collection CIDOC CRM version 5.1.2]

BC43 Activity
type: Class
subclass of: BC10 Event
term status: stable
comment: This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door. [Scope Note for E7 Activity CIDOC CRM version 5.1.2]

BC44 Attribute Assignment
type: Class
subclass of: BC43 Activity
term status: stable
comment: This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts. This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules. In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries. [Scope Note for E13 Attribute Assignment CIDOC CRM version 5.1.2]

BC45 Observation
type: Class
subclass of: BC44 Attribute Assignment
term status: stable
comment: This class comprises the activity of gaining scientific knowledge about particular states of physical reality gained by empirical evidence, experiments and by measurements. We define observation in the sense of natural sciences, as a kind of human activity: at some Place and within some Time-Span, certain Physical Things and their behavior and interactions are observed, either directly by human sensory impression, or enhanced with tools and measurement devices. The output of the internal processes of measurement devices that do not require additional human interaction are in general regarded as part of the observation and not as additional inference. Manual recordings may serve as additional evidence. Measurements and witnessing of events are special cases of observations. Observations result in a belief about certain propositions. In this model, the degree of confidence in the observed properties is regarded to be “true” per default, but could be described differently by adding a property LC7 is about to an instance of BC45 Observation, or by reification of the property O16 observed value. Primary data from measurement devices are regarded in this model to be results of observation and can be interpreted as propositions believed to be true within the (known) tolerances and degree of reliability of the device. Observations represent the transition between reality and propositions in the form of instances of a formal ontology, and can be subject to data evaluation from this point on.

BC46 Identifier Assignment
type: Class
subclass of: BC44 Attribute Assignment
comment: This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure. [Scope Note for E15 Identifier Assignment CIDOC CRM version 5.1.2]
term status: stable

BC47 Image
type: Class
subclass of: BC18 Proposition
comment: This class comprises distributions of form, tone and colour that may be found on surfaces such as photos, paintings, prints and sculptures or directly on electronic media. The degree to which variations in the distribution of form and colour affect the identity of an instance of BC5 Image depends on a given purpose.
term status: stable

BC48 Database
type: Class
subclass of: BC18 Proposition
comment: This class comprises organized collections of data. The data are typically organized to model relevant aspects of reality , in a way that supports processes requiring this information. This organized collection maybe digitized or not.
term status: stable

BC4 Temporal Phenomenon
type: Class
subclass of: BC1 TLO Entity
comment: This class comprises all sets of phenomena, such as Periods, Events and states, Ecosystems, bounded in time and space. It is the social or physical coherence of these phenomena that identify a BC4 Temporal Phenomenon and not the associated spatio-temporal bounds. These bounds are approximations of the actual process of growth, spread and retreat. Consequently, different ecosystems can overlap and coexist in time and space, such as when a nomadic culture exists in the same area as a sedentary culture.
term status: stable

BC51 Physical Object
type: Class
subclass of: BC35 Physical Thing
term status: stable
comment: This class comprises items of a material nature that are units for documentation and have physical boundaries that separate them completely in an objective way from other objects. The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen. Typically, instances of E19 Physical Object can be moved (if not too heavy). In some contexts, such objects, except for aggregates, are also called “bona fide objects” (Smith & Varzi, 2000, pp.401-420), i.e. naturally defined objects. The decision as to what is documented as a complete item, rather than by its parts or components, may be a purely administrative decision or may be a result of the order in which the item was acquired. [Scope Note for E15 Identifier Assignment CIDOC CRM version 5.1.2]

BC53 Specimen
type: Class
subclass of: BC38 Biotic Element
subclass of: BC41 Man-Made Object
term status: stable
comment: This class comprises individuals, selected by taxonomist, which typify the described species. Type specimens are placed in museums for study by taxonomists. Often the type specimen does not represent all the variation within a species. The type specimen becomes the name bearer of the species

BC54 Measurement
type: Class
subclass of: BC45 Observation
term status: stable
comment: This class comprises actions measuring physical properties and other values that can be determined by a systematic procedure. Examples include measuring the monetary value of a collection of coins or the running time of a specific video cassette. The E16 Measurement may use simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Details of methods and devices are best handled as free text, whereas basic techniques such as "carbon 14 dating" should be encoded using P2 has type (is type of:) E55 Type. [Scope Note for E16 Measurement CIDOC CRM version 5.1.2]

BC55 Measurement Unit
type: Class
subclass of: BC17 Conceptual Object
comment: This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc. This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: “instances of cm”. Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved. [Scope Note for E58 Measurement Unit CIDOC CRM version 5.1.2]
term status: stable

BC56 Digital Measurement Event
type: Class
subclass of: BC54 Measurement
comment: This class comprises actions measuring physical properties using a digital device, that are determined by a systematic procedure and creates an instance of BC23 Digital Object.
term status: stable

BC57 Capture
type: Class
subclass of: BC35 Physical Thing
comment: This class is a specialization of BC42 Collection. As reported in “Hall, M. A. (1996). On bycatches. Reviews in Fish Biology and Fisheries, 6(3), 319-352” a collection of such kind contains everything that is caught and retained in the net (or other type of gear)
term status: stable

BC58 Digital Device
type: Class
subclass of: BC16 Man-Made thing
term status: stable
comment: This class comprises identifiable material items such as computers, scanners, cameras, etc. that have the capability to process or produce instances of BC51 Digital Object.

BC59 Software
type: Class
subclass of: BC23 Digital Object
term status: stable
comment: This class comprises software codes, computer programs, procedures, and functions that are used to operate a system of digital objects.

BC5 Dimension
type: Class
subclass of: BC1 TLO Entity
term status: stable
comment: This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc. An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions. Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate. [Scope Note for E54 Dimension CIDOC CRM version 5.1.2

BC60 Software Execution
type: Class
subclass of: BC43 Activity
term status: stable
comment: This class comprises events by which a digital device runs a software program or a series of computing operations on a digital object as a single task, which is completely determined by its digital input, the software and the generic properties of the device.

BC61 Capture Activity
type: Class
subclass of: BC43 Activity
term status: stable
comment: This class compromises activities of BC45 Observation where an BC8 Actor encounters an instance of BC35 Physical Thing of a kind relevant for the mission of the observation or a biological activity such as fishing, etc. This observation produces knowledge about the existence of the respective thing at a particular place in or on surrounding matter. This knowledge may be new to the group of people the actor belongs to. In that case we would talk about a discovery. The observer may recognize or assign an individual identity of the thing encountered or regard only the type as noteworthy in the associated documentation or report. Additional parameters may be recorded like the kind of ecosystem, if the biological individual survives the observation, what detection or catching devices have been used or if the capture activity have been supported the detection of a new biological kind (“taxon”).

BC62 Statistic Indicator
type: Class
subclass of: BC17 Conceptual Object
term status: stable
comment: this class comprises indicators of a species that have been calculated using a specific procedure, methods, dataset, etc. Examples: I1 Catches per Species per Ocean, I2 Catches per Species per Ocean per Fishing Gear type, I3 Catches per Species per Month per Year per Fishing Gear type, I4 Catches per Species per Month per Year per Fishing Gear type per Ocean (should be Area), I5 Catches per Species per Month per Year per Fishing Gear type per Ocean (should be Area), for biodiversity / ecological datasets (IRD+OBIS+GBIF…)

BC63 Global Statistic Landing
type: Class
subclass of: BC44 Attribute Assignment
term status: stable
comment: This class comprises the assignment of attributes characterizing a globally (world wide) amount of a species that has been landed w.r.t the method and countries only.

BC64 Design or Procedure
type: Class
subclass of: BC17 Conceptual Object
term status: stable
comment: This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular it comprises plans for deliberate human activities that may result in the modification or production of instances of E24 Physical Thing. Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 is associated with. Designs or procedures can be seen as one of the following: 1. schema for the activities it describes 2. A schema of the products that result from their application. 3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci's famous plans for flying machines. 4. Because designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product. [Scope Note for E29 Design or Procedure (CIDOC CRM)]

BC6 Persistent Item
type: Class
subclass of: BC1 TLO Entity
term status: stable
comment: This class comprises items that have a persistent identity, sometimes known as “endurants” in philosophy. They can be repeatedly recognized within the duration of their existence by identity criteria rather than by continuity or observation. Persistent Items can be either physical entities, such as people, animals or things, or conceptual entities such as ideas, concepts, products of the imagination or common names. The criteria that determine the identity of an item are often difficult to establish -; the decision depends largely on the judgement of the observer. For example, a building is regarded as no longer existing if it is dismantled and the materials reused in a different configuration. [Scope Note for E77 Persistent Item CIDOC CRM version 5.1.2] On the other hand, human beings or elements of ecosystems or water areas go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria. Similarly, inanimate objects may be subject to exchange of parts and matter.

BC70 Group
type: Class
subclass of: BC8 Actor
comment: This class comprises any gatherings or organizations of two or more people that actcollectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. A joint pseudonym (i.e., a name that seems indicative of an individual but that is actually used as a persona by two or more people) is a particular case of E74 Group. A gathering of people becomes an E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modelled as membership in an E74 Group (cf. HumanML markup). Married couples and other concepts of family are regarded as particular examples of E74 Group. [Scope Note for E74 Group (CIDOC CRM)]
term status: stable

BC71 Name Use Activity
type: Class
subclass of: BC44 Attribute Assignment
comment: This class comprises periods of continuous use of a specific instance of E41 Appellation for a particular instance of E1 CRM Entity by an E39 Actor. It includes in particular the use of the name by its carrier. Characteristically, actors performing an activity may choose a particular appellation for themselves in the context of this activity. Such cases should be modelled by additionally classifying these activities as instances of F52 Name Use Activity. [Scope Note for F52 Name Use Activity (FRBR CRM)]
term status: stable

BC72 SpaceTime Volume
type: Class
subclass of: BC1 TLO Entity
comment: 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 BC72 Spacetime Volume, Place and Timespan are also regarded as instances of BC72 Spacetime Volume. An instance of BC72 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.
term status: stable

BC7 Thing
type: Class
subclass of: BC6 Persistent Item
term status: stable
comment: This general class comprises usable discrete, identifiable, instances of E77 Persistent Item that are documented as single units. [Scope Note for E70 Thing CIDOC CRM version 5.1.2] They can be either intellectual products or physical things which are constellations of matter with a relative stability of any form sufficient to associate them with a persistent identity, such as being confined to certain extent, which (confinement) can have a relative stability of form or structure, or containing a fixed amount of matter. It is an abstraction of products of intellectual, physical nature.

BC8 Actor
type: Class
subclass of: BC6 Persistent Item
comment: This class comprises people, either individually or in groups, who have the potential to perform intentional actions for which they can be held responsible.
term status: stable

BC9 Observable Entity
type: Class
subclass of: BC1 TLO Entity
comment: This class comprises the behaviour and interaction of physical things, being observed through events or activities or state, either directly by human sensory impression, or enhanced with tools and measurement devices.
term status: stable

BT10 Biotic Element Type
type: Class
subclass of: BT3 Physical Thing Type
comment: This metaclass comprises types of material nature items which live, have lived or are natural products of or from living organisms. Such types of material nature items includes types of plants, types of fauna(animals), types of bacteria, fungi etc.
term status: stable

BT11 Equipment Type
type: Class
subclass of: BT3 Physical Thing Type
comment: This class comprises types of physical objects purposely created by human activity.
term status: stable

BT12 Scientific Data Type
type: Class
subclass of: BT4 Conceptual Object Type
comment: This class comprises the types of Scientific data which are produced by Scientific Activity.
term status: stable

BT13 Digital Object Type
type: Class
subclass of: BT4 Conceptual Object Type
comment: This class comprises types of file formats, physical medium, or dimensions of the resource of digital objects, corresponds to dc format of Dublin core.
term status: stable

BT14 Appellation Type
type: Class
subclass of: BT4 Conceptual Object Type
comment: This class comprises types of Appellation that are used or can be used to identify a specific instance of some class within a certain context.
term status: stable

BT16 Visual Type
type: Class
subclass of: BT4 Conceptual Object Type
comment: This metaclass comprises types of intellectual or conceptual aspects of recognisable marks and images.
term status: stable

BT17 Human Activity Type
type: Class
subclass of: BT6 Human Event Type
term status: stable
comment: This metaclass comprises types of actions carried out by humans that result in changes of state in ecological or physical systems.

BT18 Kingdom
type: Class
subclass of: BT10 Biotic Element Type
comment: This metaclass comprises types of organisms (taxa) that are classified as Kingdom.
term status: stable

BT19 Phylum
type: Class
subclass of: BT10 Biotic Element Type
term status: stable
comment: This metaclass comprises types of organisms (taxa) that are classified as Phylum.

BT1 TLO Entity Type
type: Class
term status: stable
comment: This class comprises types of things in the universe of discourse of the MarineTLO.

BT20 SubPhylum
type: Class
subclass of: BT10 Biotic Element Type
comment: This metaclass comprises types of organisms (taxa) that are classified as Subphylum.
term status: stable

BT21 SuperClass
type: Class
subclass of: BT10 Biotic Element Type
comment: This metaclass comprises types of organisms (taxa) that are classified as Superclass.
term status: stable

BT22 Class
type: Class
subclass of: BT10 Biotic Element Type
term status: stable
comment: This metaclass comprises types of organisms (taxa) that are classified as Class.

BT23 SubClass
type: Class
subclass of: BT10 Biotic Element Type
term status: stable
comment: This metaclass comprises types of organisms (taxa) that are classified as Subclass.

BT24 Family
type: Class
subclass of: BT10 Biotic Element Type
comment: This metaclass comprises types of organisms (taxa) that are classified as Family.
term status: stable

BT25 SubFamily
type: Class
subclass of: BT10 Biotic Element Type
term status: stable
comment: This metaclass comprises types of organisms (taxa) that are classified as Subfamily.

BT26 Genus
type: Class
subclass of: BT10 Biotic Element Type
term status: stable
comment: This metaclass comprises types of organisms (taxa) that are classified as Genus.

BT27 Species
type: Class
subclass of: BT10 Biotic Element Type
term status: stable
comment: This metaclass comprises types of organisms (taxa) that are classified as Species.

BT28 Scientific Activity Type
type: Class
subclass of: BT17 Human Activity Type
term status: stable

BT29 Industrial Activity Type
type: Class
subclass of: BT17 Human Activity Type
term status: stable

BT2 Temporal Phenomenon Type
type: Class
subclass of: BT1 TLO Entity Type
term status: stable
comment: This class comprises all types of phenomena, such as types of Periods, Events and states, which happen over a limited extent in time.

BT30 Identifier Assignment Type
type: Class
subclass of: BT17 Human Activity Type
term status: stable

BT31 Biological Part Time
type: Class
subclass of: BT10 Biotic Element Type
comment: This metaclass comprises types of biological parts of a biological object.
term status: stable

BT32 Persisten Type
type: Class
subclass of: BT1 TLO Entity Type
term status: stable
comment: This class comprises types items that have a persistent identity, sometimes known as “endurants” in philosophy. The items of this type can be repeatedly recognized within the duration of their existence by identity criteria rather than by continuity or observation. These can be either types of physical entities, such as people, animals or things, or conceptual entities such as ideas, concepts, products of the imagination or common names.

BT33 Marine Animal Type
type: Class
subclass of: BT10 Biotic Element Type
comment: This class comprises types marine animals that have a persistent identity.
term status: stable

BT34 Order
type: Class
subclass of: BT10 Biotic Element Type
term status: stable
comment: This metaclass comprises types of organisms (taxa) that are classified as Order.

BT35 Property Type
type: Class
subclass of: BT4 Conceptual Object Type
term status: stable
comment: This class comprises any property concept that is used in scientific propositions about reality. Typically, instances of BT35 Property Type would be taken from an ontology or terminological system.

BT36 Language
type: Class
subclass of: BT4 Conceptual Object Type
comment: This class comprises the natural languages in the sense of concepts, i.e. the Model does not foresee the description of instances of BT36 Language, e.g.: “instances of French”. It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of BT36 Language, such as those defined in ISO 639:1988. [CIDOC CRM].
term status: stable

BT3 Physical Thing Type
type: Class
subclass of: BT32 Persisten Type
term status: stable
comment: This class comprises types of constellations of matter with a relative stability of any form sufficient to associate them with a persistent identity, such as being confined to certain extent, having a relative stability of form or structure, or containing a fixed amount of matter. In particular, it comprises physical things in the narrower sense and fluid bodies. It is an abstraction of physical substance for solid and non-solid things of matter.

BT4 Conceptual Object Type
type: Class
subclass of: BT32 Persisten Type
term status: stable
comment: This metaclass comprises types of identifiable immaterial items, such as, types of data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units.

BT5 Legislative Zone Type
type: Class
subclass of: BT2 Temporal Phenomenon Type
comment: This class comprises types of extents in space where real world phenomenon can be observed or measured.
term status: stable

BT6 Human Event Type
type: Class
subclass of: BT2 Temporal Phenomenon Type
term status: stable
comment: This class comprises types of actions intentionally carried out by humans that result in changes of state in the scientific, social, or physical systems documented.

BT7 Ecosystem Type
type: Class
subclass of: BT2 Temporal Phenomenon Type
term status: stable
comment: This metaclass comprises types of coherent ecological phenomena bounded in time and space. The coherence of these phenomena is given by the type of interaction characteristic for biological systems. This coherence identifies the ecosystem and not the associated spatio-temporal bounds. These bounds are a mere approximation of the actual process of growth, spread and retreat. Consequently, different ecosystems can overlap and coexist in time and space.

BT8 Abiotic Element Type
type: Class
subclass of: BT3 Physical Thing Type
term status: stable
comment: This metaclass comprises types of abiotic components of a type of Ecosystem.

BT9 Actor Type
type: Class
subclass of: BT32 Persisten Type
comment: This class comprises types of human agents either individually or in groups, who have the potential to perform intentional actions for which they can be held responsible.
term status: stable