https://w3id.org/bibma/   Namespaces

rdf:type

owl:Ontology

rdfs:comment

"L’ontologie "Florus" est une version simplifiée et modifiée de l’ontologie Biblissima. L’ontologie a été adaptée aux besoins de l’étude du cas concret qu’est la bibliothèque de Florus de Lyon. Elle continue d'être enrichie. Pour toute question concernant l'ontologie Biblissima n'hésitez pas à contacter stefanie.gehrke@biblissima-condorcet.fr et pauline.charbonnier@biblissima-condorcet.fr."

rdfs:label

"Ontologie Biblissima / Florus de Lyon"

Triples: 4366

Entity types:

owl:Thing
current:E1_CRM_Entity
current:E2_Temporal_Entity
current:E52_Time-Span
current:E53_Place
current:E54_Dimension
current:E77_Persistent_Item
current:E39_Actor
current:E70_Thing
current:E71_Man-Made_Thing
current:E24_Physical_Man-Made_Thing
current:E28_Conceptual_Object
current:F6_Concept
current:E72_Legal_Object
current:E18_Physical_Thing
current:E90_Symbolic_Object
efrbroo:F3_Manifestation_Product_Type
efrbroo:F9_Place

rdfs:comment

Membre de CIDOC CRM CORE

Scope note:
This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing.
This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
If the instance of the E29 Design or Procedure utilised for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.

Examples:
- the construction of the SS Great Britain (E12)
- the impregnation of the Vasa warship in Stockholm for preservation after 1956
- the transformation of the Enola Gay into a museum exhibit by the National Air and Space Museum in Washington DC between 1993 and 1995 (E12, E81)
- the last renewal of the gold coating of the Toshogu shrine in Nikko, Japan

rdfs:label

E11 Modification

E11 Modification

owl:disjointWith

https://w3id.org/bibma/Binding

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/current/E24_Physical_Man-Made_Thing

http://erlangen-crm.org/current/E47_Spatial_Coordinates

https://w3id.org/bibma/Annotation

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

http://erlangen-crm.org/efrbroo/F10_Person

http://erlangen-crm.org/current/E18_Physical_Thing

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/current/E25_Man-Made_Feature

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/current/E72_Legal_Object

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E46_Section_Definition

http://erlangen-crm.org/current/E39_Actor

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/current/E19_Physical_Object

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

http://erlangen-crm.org/efrbroo/F2_Expression

https://w3id.org/bibma/Manuscript

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/current/E56_Language

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Record

http://erlangen-crm.org/current/E58_Measurement_Unit

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E74_Group

https://w3id.org/bibma/Folio

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E77_Persistent_Item

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/current/E40_Legal_Body

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/current/E42_Identifier

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/current/E55_Type

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Digital_Surrogate

http://erlangen-crm.org/current/F6_Concept

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/current/E70_Thing

http://erlangen-crm.org/current/E71_Man-Made_Thing

https://w3id.org/bibma/Component

http://erlangen-crm.org/current/E28_Conceptual_Object

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E21_Person

http://erlangen-crm.org/current/E26_Physical_Feature

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/current/E35_Title

http://erlangen-crm.org/current/E38_Image

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/efrbroo/F1_Work

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/current/E22_Man-Made_Object

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Electronic_Edition

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/efrbroo/F12_Nomen

skos:notation

E11

Instances of current:E11_Modification can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E2_Temporal_Entity
current:P4_has_time-span Membre de CIDOC CRM CORE current:E52_Time-Span
Properties inherited from current:E4_Period
current:P10_falls_within Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occupied by the latter. The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of), P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different nature. Examples: - the Great Plague (E4) falls within The Gothic period (E4) current:E4_Period
current:P10i_contains current:E4_Period
current:P7_took_place_at Scope note: his property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period "Révolution française" can be said to have taken place in "France", the "Victorian" period, may be said to have taken place in "Britain" and its colonies, as well as other parts of Europe and north America. A period can take place at multiple locations. Examples - the period "Révolution française" (E4) took place at France (E53) current:E53_Place
current:P9_consists_of Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occup ied by the former and which is defined by phenomena that form part of or are refinements of the phenomena that define the former. Examples: - Cretan Bronze Age (E4) consists of Middle Minoan (E4) current:E4_Period
current:P9i_forms_part_of current:E4_Period
Properties inherited from current:E5_Event
current:P11_had_participant Scope note: 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. Examples: - Napoleon (E21) participated in The Battle of Waterloo (E7) - Maria (E21) participated in Photographing of Maria (E7) current:E39_Actor
current:P12_occurred_in_the_presence_of Scope note: 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. Examples: - Deckchair 42 (E19) was present at The sinking of the Titanic (E5) current:E77_Persistent_Item
Properties inherited from current:E7_Activity
current:P125_used_object_of_type Scope note: This property defines the kind of objects used in an E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer". Examples: - at the Battle of Agincourt (E7), the English archers used object of type long bow (E55) current:E55_Type
current:P14_carried_out_by Membre de CIDOC CRM CORE current:E39_Actor
current:P15_was_influenced_by Scope note: This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties. Examples: - the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22) current:E1_CRM_Entity
current:P16.1_mode_of_use current:E70_Thing
current:P16_used_specific_object Scope note: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use. Examples: - the writing of this scope note (E7) used specific object Nicholas Crofts' computer (E22) mode of use Typing Tool; Storage Medium (E55) - the people of Iraq calling the place identified by TGN '7017998' (E7) used specific object "Quyunjig" (E44) mode of use Current; Vernacular (E55) current:E70_Thing
current:P32_used_general_technique Example : F28_Expression_Creation -> P32_used_general_technique -> bibma_Writing_Direction ; values : right-to-left , left-to-right , bidirectional , top-to-bottom current:E55_Type
Properties from current:E11_Modification
current:P31_has_modified Scope note: This property identifies the E24 Physical Man-Made Thing modified in an E11 Modification. If a modification is applied to a non-man-made object, it is regarded as an E22 Man-Made Object from that time onwards. Examples: - rebuilding of the Reichstag (E11) has modified the Reichstag in Berlin (E24) current:E24_Physical_Man-Made_Thing

rdfs:comment

Membre de CIDOC CRM CORE

Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered "new" if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered "new" because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.

Examples:
- the construction of the SS Great Britain
- the first casting from the Little Mermaid at the harbour of Copenhagen
- Rembrandt's creating of the seventh state of his etching "Woman sitting half dressed beside a stove", 1658, identified by Bartsch Number 197 (E12,E65,E81)

rdfs:label

E12 Production

E12 Production

owl:disjointWith

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/current/E58_Measurement_Unit

https://w3id.org/bibma/Style_of_Script

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/current/E56_Language

https://w3id.org/bibma/Provenance_Mark

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/efrbroo/F12_Nomen

https://w3id.org/bibma/Manuscript

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/current/E24_Physical_Man-Made_Thing

http://erlangen-crm.org/current/E72_Legal_Object

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/current/E46_Section_Definition

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/current/E18_Physical_Thing

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/current/E42_Identifier

https://w3id.org/bibma/Annotation

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/current/E34_Inscription

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E74_Group

https://w3id.org/bibma/Component

http://erlangen-crm.org/current/E25_Man-Made_Feature

http://erlangen-crm.org/current/E71_Man-Made_Thing

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E89_Propositional_Object

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/efrbroo/F1_Work

https://w3id.org/bibma/Electronic_Edition

http://erlangen-crm.org/current/E22_Man-Made_Object

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/current/E21_Person

http://erlangen-crm.org/current/E26_Physical_Feature

https://w3id.org/bibma/Record

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/current/E35_Title

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Binding

http://erlangen-crm.org/current/E77_Persistent_Item

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/current/E55_Type

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E19_Physical_Object

http://erlangen-crm.org/current/E39_Actor

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/current/E40_Legal_Body

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/efrbroo/F10_Person

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E28_Conceptual_Object

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Digital_Surrogate

http://erlangen-crm.org/current/E70_Thing

skos:notation

E12

Instances of current:E12_Production can have the following properties:

Property Description Expected Type
Properties inherited from current:E63_Beginning_of_Existence
current:P92_brought_into_existence Membre de CIDOC CRM CORE current:E77_Persistent_Item
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E2_Temporal_Entity
current:P4_has_time-span Membre de CIDOC CRM CORE current:E52_Time-Span
Properties inherited from current:E4_Period
current:P10_falls_within Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occupied by the latter. The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of), P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different nature. Examples: - the Great Plague (E4) falls within The Gothic period (E4) current:E4_Period
current:P10i_contains current:E4_Period
current:P7_took_place_at Scope note: his property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period "Révolution française" can be said to have taken place in "France", the "Victorian" period, may be said to have taken place in "Britain" and its colonies, as well as other parts of Europe and north America. A period can take place at multiple locations. Examples - the period "Révolution française" (E4) took place at France (E53) current:E53_Place
current:P9_consists_of Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occup ied by the former and which is defined by phenomena that form part of or are refinements of the phenomena that define the former. Examples: - Cretan Bronze Age (E4) consists of Middle Minoan (E4) current:E4_Period
current:P9i_forms_part_of current:E4_Period
Properties inherited from current:E5_Event
current:P11_had_participant Scope note: 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. Examples: - Napoleon (E21) participated in The Battle of Waterloo (E7) - Maria (E21) participated in Photographing of Maria (E7) current:E39_Actor
current:P12_occurred_in_the_presence_of Scope note: 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. Examples: - Deckchair 42 (E19) was present at The sinking of the Titanic (E5) current:E77_Persistent_Item
Properties inherited from current:E7_Activity
current:P125_used_object_of_type Scope note: This property defines the kind of objects used in an E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer". Examples: - at the Battle of Agincourt (E7), the English archers used object of type long bow (E55) current:E55_Type
current:P14_carried_out_by Membre de CIDOC CRM CORE current:E39_Actor
current:P15_was_influenced_by Scope note: This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties. Examples: - the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22) current:E1_CRM_Entity
current:P16.1_mode_of_use current:E70_Thing
current:P16_used_specific_object Scope note: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use. Examples: - the writing of this scope note (E7) used specific object Nicholas Crofts' computer (E22) mode of use Typing Tool; Storage Medium (E55) - the people of Iraq calling the place identified by TGN '7017998' (E7) used specific object "Quyunjig" (E44) mode of use Current; Vernacular (E55) current:E70_Thing
current:P32_used_general_technique Example : F28_Expression_Creation -> P32_used_general_technique -> bibma_Writing_Direction ; values : right-to-left , left-to-right , bidirectional , top-to-bottom current:E55_Type
Properties inherited from current:E11_Modification
current:P31_has_modified Scope note: This property identifies the E24 Physical Man-Made Thing modified in an E11 Modification. If a modification is applied to a non-man-made object, it is regarded as an E22 Man-Made Object from that time onwards. Examples: - rebuilding of the Reichstag (E11) has modified the Reichstag in Berlin (E24) current:E24_Physical_Man-Made_Thing
Properties from current:E12_Production
current:P108_has_produced Scope note: This property identifies the E24 Physical Man-Made Thing that came into existence as a result of an E12 Production. The identity of an instance of E24 Physical Man-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Man-Made Thing. Examples: - the building of Rome (E12) has produced Τhe Colosseum (E22) current:E24_Physical_Man-Made_Thing
base:used_style_of_script Cette propriété identifie le type d’écriture qui fut utilisé par un copiste lors de la production du manuscrit. base:Style_of_Script

rdfs:comment

Scope note:
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.

Examples:
- the assessment of the current ownership of Martin Doerr's silver cup in February 1997

Membre de CIDOC CRM CORE

rdfs:label

E13 Affectation d'attribut

E13 Attribute_Assignment

owl:disjointWith

https://w3id.org/bibma/Written_Area

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/current/E28_Conceptual_Object

http://erlangen-crm.org/current/E40_Legal_Body

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

http://erlangen-crm.org/current/E19_Physical_Object

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/current/E36_Visual_Item

https://w3id.org/bibma/Record

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/E39_Actor

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/current/E72_Legal_Object

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/current/E24_Physical_Man-Made_Thing

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/efrbroo/F12_Nomen

http://erlangen-crm.org/current/E56_Language

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/current/E26_Physical_Feature

http://erlangen-crm.org/current/E22_Man-Made_Object

https://w3id.org/bibma/Electronic_Edition

http://erlangen-crm.org/current/E57_Material

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/current/E25_Man-Made_Feature

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/current/E71_Man-Made_Thing

https://w3id.org/bibma/Component

http://erlangen-crm.org/current/E21_Person

https://w3id.org/bibma/Folio_Extent

https://w3id.org/bibma/Annotation

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/current/E18_Physical_Thing

http://erlangen-crm.org/current/E42_Identifier

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E46_Section_Definition

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/current/E37_Mark

https://w3id.org/bibma/Binding

http://erlangen-crm.org/current/E55_Type

http://erlangen-crm.org/current/E74_Group

http://erlangen-crm.org/current/E77_Persistent_Item

https://w3id.org/bibma/Folio

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/efrbroo/F10_Person

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/efrbroo/F1_Work

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E47_Spatial_Coordinates

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/current/E35_Title

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/current/E70_Thing

http://erlangen-crm.org/current/E58_Measurement_Unit

http://erlangen-crm.org/current/F6_Concept

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Manuscript

skos:notation

E13

Instances of current:E13_Attribute_Assignment can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E2_Temporal_Entity
current:P4_has_time-span Membre de CIDOC CRM CORE current:E52_Time-Span
Properties inherited from current:E4_Period
current:P10_falls_within Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occupied by the latter. The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of), P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different nature. Examples: - the Great Plague (E4) falls within The Gothic period (E4) current:E4_Period
current:P10i_contains current:E4_Period
current:P7_took_place_at Scope note: his property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period "Révolution française" can be said to have taken place in "France", the "Victorian" period, may be said to have taken place in "Britain" and its colonies, as well as other parts of Europe and north America. A period can take place at multiple locations. Examples - the period "Révolution française" (E4) took place at France (E53) current:E53_Place
current:P9_consists_of Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occup ied by the former and which is defined by phenomena that form part of or are refinements of the phenomena that define the former. Examples: - Cretan Bronze Age (E4) consists of Middle Minoan (E4) current:E4_Period
current:P9i_forms_part_of current:E4_Period
Properties inherited from current:E5_Event
current:P11_had_participant Scope note: 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. Examples: - Napoleon (E21) participated in The Battle of Waterloo (E7) - Maria (E21) participated in Photographing of Maria (E7) current:E39_Actor
current:P12_occurred_in_the_presence_of Scope note: 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. Examples: - Deckchair 42 (E19) was present at The sinking of the Titanic (E5) current:E77_Persistent_Item
Properties inherited from current:E7_Activity
current:P125_used_object_of_type Scope note: This property defines the kind of objects used in an E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer". Examples: - at the Battle of Agincourt (E7), the English archers used object of type long bow (E55) current:E55_Type
current:P14_carried_out_by Membre de CIDOC CRM CORE current:E39_Actor
current:P15_was_influenced_by Scope note: This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties. Examples: - the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22) current:E1_CRM_Entity
current:P16.1_mode_of_use current:E70_Thing
current:P16_used_specific_object Scope note: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use. Examples: - the writing of this scope note (E7) used specific object Nicholas Crofts' computer (E22) mode of use Typing Tool; Storage Medium (E55) - the people of Iraq calling the place identified by TGN '7017998' (E7) used specific object "Quyunjig" (E44) mode of use Current; Vernacular (E55) current:E70_Thing
current:P32_used_general_technique Example : F28_Expression_Creation -> P32_used_general_technique -> bibma_Writing_Direction ; values : right-to-left , left-to-right , bidirectional , top-to-bottom current:E55_Type
Properties from current:E13_Attribute_Assignment
current:P140_assigned_attribute_to Scope note: This property indicates the item to which an attribute or relation is assigned. Examples: - February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned attribute to Martin Doerr's silver cup (E19) - 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E19) current:E1_CRM_Entity
current:P141_assigned Scope note: 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. Examples: - February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned Martin Doerr (E21) - 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned object identifier 232 current:E1_CRM_Entity

rdfs:comment

Scope note:
This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions and concepts.
This class allows for the documentation of the context of classification acts in cases where the value of the classification depends on the personal opinion of the classifier, and the date that the classification was made. This class also encompasses the notion of "determination", i.e. the systematic and molecular identification of a specimen in biology.

Examples:
- the first classification of object GE34604 as Lament Cloth, October 2nd
- the determination of a cactus in Martin Doerr's garden as 'Cereus hildmannianus K.Schumann', July 2003

rdfs:label

E17 Type Assignment

owl:disjointWith

http://erlangen-crm.org/current/E46_Section_Definition

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E24_Physical_Man-Made_Thing

http://erlangen-crm.org/current/E74_Group

http://erlangen-crm.org/current/E19_Physical_Object

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E56_Language

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/efrbroo/F10_Person

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/current/E72_Legal_Object

https://w3id.org/bibma/Record

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/current/E34_Inscription

https://w3id.org/bibma/Written_Area

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E84_Information_Carrier

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Provenance_Mark

http://erlangen-crm.org/current/E40_Legal_Body

http://erlangen-crm.org/current/E35_Title

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/current/E39_Actor

http://erlangen-crm.org/current/E58_Measurement_Unit

http://erlangen-crm.org/current/E36_Visual_Item

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/current/E70_Thing

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Digital_Surrogate

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

http://erlangen-crm.org/current/E28_Conceptual_Object

http://erlangen-crm.org/current/E21_Person

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/efrbroo/F1_Work

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/current/E37_Mark

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E77_Persistent_Item

http://erlangen-crm.org/current/E71_Man-Made_Thing

http://erlangen-crm.org/current/E25_Man-Made_Feature

https://w3id.org/bibma/Component

http://erlangen-crm.org/current/E55_Type

https://w3id.org/bibma/Electronic_Edition

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/efrbroo/F12_Nomen

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/current/E26_Physical_Feature

https://w3id.org/bibma/Annotation

http://erlangen-crm.org/current/E42_Identifier

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/current/E22_Man-Made_Object

http://erlangen-crm.org/current/E18_Physical_Thing

skos:notation

E17

Instances of current:E17_Type_Assignment can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E2_Temporal_Entity
current:P4_has_time-span Membre de CIDOC CRM CORE current:E52_Time-Span
Properties inherited from current:E4_Period
current:P10_falls_within Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occupied by the latter. The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of), P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different nature. Examples: - the Great Plague (E4) falls within The Gothic period (E4) current:E4_Period
current:P10i_contains current:E4_Period
current:P7_took_place_at Scope note: his property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period "Révolution française" can be said to have taken place in "France", the "Victorian" period, may be said to have taken place in "Britain" and its colonies, as well as other parts of Europe and north America. A period can take place at multiple locations. Examples - the period "Révolution française" (E4) took place at France (E53) current:E53_Place
current:P9_consists_of Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occup ied by the former and which is defined by phenomena that form part of or are refinements of the phenomena that define the former. Examples: - Cretan Bronze Age (E4) consists of Middle Minoan (E4) current:E4_Period
current:P9i_forms_part_of current:E4_Period
Properties inherited from current:E5_Event
current:P11_had_participant Scope note: 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. Examples: - Napoleon (E21) participated in The Battle of Waterloo (E7) - Maria (E21) participated in Photographing of Maria (E7) current:E39_Actor
current:P12_occurred_in_the_presence_of Scope note: 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. Examples: - Deckchair 42 (E19) was present at The sinking of the Titanic (E5) current:E77_Persistent_Item
Properties inherited from current:E7_Activity
current:P125_used_object_of_type Scope note: This property defines the kind of objects used in an E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer". Examples: - at the Battle of Agincourt (E7), the English archers used object of type long bow (E55) current:E55_Type
current:P14_carried_out_by Membre de CIDOC CRM CORE current:E39_Actor
current:P15_was_influenced_by Scope note: This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties. Examples: - the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22) current:E1_CRM_Entity
current:P16.1_mode_of_use current:E70_Thing
current:P16_used_specific_object Scope note: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use. Examples: - the writing of this scope note (E7) used specific object Nicholas Crofts' computer (E22) mode of use Typing Tool; Storage Medium (E55) - the people of Iraq calling the place identified by TGN '7017998' (E7) used specific object "Quyunjig" (E44) mode of use Current; Vernacular (E55) current:E70_Thing
current:P32_used_general_technique Example : F28_Expression_Creation -> P32_used_general_technique -> bibma_Writing_Direction ; values : right-to-left , left-to-right , bidirectional , top-to-bottom current:E55_Type
Properties inherited from current:E13_Attribute_Assignment
current:P140_assigned_attribute_to Scope note: This property indicates the item to which an attribute or relation is assigned. Examples: - February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned attribute to Martin Doerr's silver cup (E19) - 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E19) current:E1_CRM_Entity
current:P141_assigned Scope note: 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. Examples: - February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned Martin Doerr (E21) - 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned object identifier 232 current:E1_CRM_Entity
Properties from current:E17_Type_Assignment
current:P42_assigned Scope note: This property records the type that was assigned to an entity by an E17 Type Assignment activity. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified by), E17 Type Assignment, P42 assigned (was assigned by) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type (is type of). For example, a fragment of an antique vessel could be assigned the type "attic red figured belly handled amphora" by expert A. The same fragment could be assigned the type "shoulder handled amphora" by expert B. A Type may be intellectually constructed independent from assigning an instance of it. Examples: - 31 August 1997 classification of silver cup 232 (E17) assigned goblet (E55) current:E55_Type

rdfs:comment

Membre de CIDOC CRM CORE

Scope note:
This class comprises all persistent physical items with a relatively stable form, man-made or natural.
Depending on the existence of natural boundaries of such things, the CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter.
The CRM is generally not concerned with amounts of matter in fluid or gaseous states.

Examples:
- the Cullinan Diamond (E19)
- the cave "Ideon Andron" in Crete (E26)
- the Mona Lisa (E22)

rdfs:label

E18 Chose matérielle

E18 Physical Thing

owl:disjointWith

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/efrbroo/F12_Nomen

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E55_Type

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/efrbroo/F1_Work

https://w3id.org/bibma/Written_Area_Production

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/current/E46_Section_Definition

https://w3id.org/bibma/Electronic_Edition

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/current/E42_Identifier

http://erlangen-crm.org/current/E2_Temporal_Entity

http://erlangen-crm.org/current/E35_Title

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/efrbroo/F13_Identifier

https://w3id.org/bibma/Record

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/current/E56_Language

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E28_Conceptual_Object

https://w3id.org/bibma/Incipit

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/current/E58_Measurement_Unit

http://erlangen-crm.org/current/E36_Visual_Item

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/current/E90_Symbolic_Object

skos:notation

E18

Instances of current:E18_Physical_Thing can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties from current:E18_Physical_Thing
current:P128_carries Scope note: This property identifies an E90 Symbolic Object carried by an instance of E24 Physical Man-Made Thing. In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items. Examples: - Matthew's paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73) current:E90_Symbolic_Object
current:P157i_provides_reference_space_for current:E53_Place
current:P45_consists_of Scope note: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material. A Material, such as a theoretical alloy, may not have any physical instances. silver cup 232 (E22) consists of silver (E57) current:E57_Material
current:P46_is_composed_of Scope note: 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). Examples: - the Royal carriage (E22) forms part of the Royal train (E22) - the "Hog's Back" (E24) forms part of the "Fosseway" (E24) current:E18_Physical_Thing
current:P46i_forms_part_of current:E18_Physical_Thing
current:P49_has_former_or_current_keeper Scope note: This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at some time. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody received by (received custody through) to E39 Actor. Examples: - paintings from The Iveagh Bequest (E18) has former or current keeper Secure Deliveries Inc. (E40) current:E39_Actor
current:P50_has_current_keeper Scope note: This property identifies the E39 Actor or Actors who had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. P50 has current keeper (is current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P29 custody received by (received custody through) to E39 Actor. Examples: - painting from The Iveagh Bequest (E18) has current keeper The National Gallery (E40) current:E39_Actor
current:P51_has_current_or_former_owner Scope note: This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor. Examples: - paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21) current:E39_Actor
current:P53_has_former_or_current_location Biblissima uses this property for both, the current or former location of a book and the location of an E34_Inscription like a Provenance Mark on a folio. Example: E34_Inscription -> P128i_is_carried_by -> E25_Man-Made_Feature -> _has_former_or_current_location -> E53_Place (URI folio; e.g. ARK: BnF/Shelfmark/Folio) -> P87_is_idenfied_by -> E46_Section_Definition (label folio; e.g.) -> P58i defindes section -> F4 (URI manuscript) current:E53_Place
current:P58_has_section_definition Scope note: This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing. Examples: - HMS Victory (E22) has section definition "poop deck of HMS Victory" (E46) current:E46_Section_Definition
current:P59_has_section Scope note: This property links an area to the instance of E18 Physical Thing upon which it is found. It is typically used when a named E46 Section Definition is not appropriate. E18 Physical Thing may be subdivided into arbitrary regions. P59 has section (is located on or within) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed (i.e. indirect) path from E18 Physical Thing through P58 has section definition (defines section), E46 Section Definition, P87 is identified by (identifies) to E53 Place. A Place can only be located on or within one Physical Object. Examples: - HMS Victory (E22) has section HMS Victory section B347.6 (E53) current:E53_Place

rdfs:comment

Scope note:
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.

Examples:
- John Smith
- Aphrodite of Milos
- the Palace of Knossos
- the Cullinan diamond
- Apollo 13 at the time of launch

rdfs:label

E19 Physical Object

owl:disjointWith

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E56_Language

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/current/E55_Type

https://w3id.org/bibma/Record

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

http://erlangen-crm.org/current/E35_Title

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/current/E58_Measurement_Unit

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/current/E46_Section_Definition

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/efrbroo/F1_Work

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/efrbroo/F12_Nomen

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E42_Identifier

https://w3id.org/bibma/Style_of_Script

https://w3id.org/bibma/Electronic_Edition

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E2_Temporal_Entity

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E48_Place_Name

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E28_Conceptual_Object

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E82_Actor_Appellation

https://w3id.org/bibma/Title_Assignment

skos:notation

E19

Instances of current:E19_Physical_Object can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E18_Physical_Thing
current:P128_carries Scope note: This property identifies an E90 Symbolic Object carried by an instance of E24 Physical Man-Made Thing. In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items. Examples: - Matthew's paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73) current:E90_Symbolic_Object
current:P157i_provides_reference_space_for current:E53_Place
current:P45_consists_of Scope note: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material. A Material, such as a theoretical alloy, may not have any physical instances. silver cup 232 (E22) consists of silver (E57) current:E57_Material
current:P46_is_composed_of Scope note: 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). Examples: - the Royal carriage (E22) forms part of the Royal train (E22) - the "Hog's Back" (E24) forms part of the "Fosseway" (E24) current:E18_Physical_Thing
current:P46i_forms_part_of current:E18_Physical_Thing
current:P49_has_former_or_current_keeper Scope note: This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at some time. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody received by (received custody through) to E39 Actor. Examples: - paintings from The Iveagh Bequest (E18) has former or current keeper Secure Deliveries Inc. (E40) current:E39_Actor
current:P50_has_current_keeper Scope note: This property identifies the E39 Actor or Actors who had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. P50 has current keeper (is current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P29 custody received by (received custody through) to E39 Actor. Examples: - painting from The Iveagh Bequest (E18) has current keeper The National Gallery (E40) current:E39_Actor
current:P51_has_current_or_former_owner Scope note: This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor. Examples: - paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21) current:E39_Actor
current:P53_has_former_or_current_location Biblissima uses this property for both, the current or former location of a book and the location of an E34_Inscription like a Provenance Mark on a folio. Example: E34_Inscription -> P128i_is_carried_by -> E25_Man-Made_Feature -> _has_former_or_current_location -> E53_Place (URI folio; e.g. ARK: BnF/Shelfmark/Folio) -> P87_is_idenfied_by -> E46_Section_Definition (label folio; e.g.) -> P58i defindes section -> F4 (URI manuscript) current:E53_Place
current:P58_has_section_definition Scope note: This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing. Examples: - HMS Victory (E22) has section definition "poop deck of HMS Victory" (E46) current:E46_Section_Definition
current:P59_has_section Scope note: This property links an area to the instance of E18 Physical Thing upon which it is found. It is typically used when a named E46 Section Definition is not appropriate. E18 Physical Thing may be subdivided into arbitrary regions. P59 has section (is located on or within) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed (i.e. indirect) path from E18 Physical Thing through P58 has section definition (defines section), E46 Section Definition, P87 is identified by (identifies) to E53 Place. A Place can only be located on or within one Physical Object. Examples: - HMS Victory (E22) has section HMS Victory section B347.6 (E53) current:E53_Place
Properties from current:E19_Physical_Object
current:P55_has_current_location Scope note: This property records the location of an E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. This property is a specialisation of has former or current location (is former or current location of). It indicates that the E53 Place associated with the E19 Physical Object is the current location of the object. The property does not allow any indication of how long the Object has been at the current location. P55 has current location (currently holds) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P25 moved (moved by), E9 Move P26 moved to (was destination of) to E53 Place if and only if this Move is the most recent. Examples: - silver cup 232 (E22) has current location Display cabinet 23, Room 4, British Museum (E53) current:E53_Place
current:P56_bears_feature Scope note: This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears. An E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An E27 Site should be considered as an E26 Physical Feature on the surface of the Earth. An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i found on the same E19 Physical Object as A. P56 bears feature (is found on) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P59 has section (is located on or within), E53 Place, has former or current location (is former or current location of) to E26 Physical Feature. Examples: - silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26) current:E26_Physical_Feature

rdfs:subClassOf

owl:Thing

rdfs:comment

Scope note:
This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model.

It is an abstract concept providing for three general properties:
1. Identification by name or appellation, and in particular by a preferred identifier
2. Classification by type, allowing further refinement of the specific subclass an instance belongs to
3. Attachment of free text for the expression of anything not captured by formal properties
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.

Examples:
- the earthquake in Lisbon 1755 (E5)

Membre de CIDOC CRM CORE

rdfs:label

E1 Entity

E1 Entité CRM

skos:notation

E1

Instances of current:E1_CRM_Entity can have the following properties:

Property Description Expected Type
Properties from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document

rdfs:comment

Scope note:
This class comprises real persons who live or are assumed to have lived.
Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CRM does not propose a specific form to support reasoning about possible identity.

Examples:
- Tut-Ankh-Amun
- Nelson Mandela

rdfs:label

E21 Person

owl:disjointWith

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Component_Production

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/current/E2_Temporal_Entity

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

owl:equivalentClass

http://erlangen-crm.org/efrbroo/F10_Person

skos:notation

E21

Instances of current:E21_Person can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E39_Actor
current:P11i_participated_in current:E5_Event
current:P131_is_identified_by Scope note: This property identifies a name used specifically to identify an E39 Actor. This property is a specialisation of P1 is identified by (identifies) is identified by. Examples: - Tyler Withersopp IV (E39) is identified by "US social security number 619-17-4204" (E82) current:E82_Actor_Appellation
current:P14i_performed Membre de CIDOC CRM CORE current:E7_Activity
current:P49i_is_former_or_current_keeper_of current:E18_Physical_Thing
current:P50i_is_current_keeper_of current:E18_Physical_Thing
current:P51i_is_former_or_current_owner_of current:E18_Physical_Thing
base:r0270i_performed_as_scribe base:Written_Area_Production
base:r40i_performed_as_annotator base:Annotation_Production
base:r70i_performed_as_author efrbroo:F27_Work_Conception

rdfs:comment

Scope note:
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.

Examples:
- Mallard (the World's fastest steam engine)
- the Portland Vase
- the Coliseum

rdfs:label

E22 Man-Made Object

owl:disjointWith

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/current/E38_Image

https://w3id.org/bibma/Electronic_Edition

http://erlangen-crm.org/current/E57_Material

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/current/E35_Title

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/current/E28_Conceptual_Object

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/current/E55_Type

http://erlangen-crm.org/current/E42_Identifier

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E73_Information_Object

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Record

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E2_Temporal_Entity

http://erlangen-crm.org/current/E58_Measurement_Unit

http://erlangen-crm.org/current/E56_Language

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E33_Linguistic_Object

https://w3id.org/bibma/Written_Area_Production

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/efrbroo/F1_Work

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/current/E46_Section_Definition

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/efrbroo/F12_Nomen

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/efrbroo/F27_Work_Conception

skos:notation

E22

Instances of current:E22_Man-Made_Object can have the following properties:

Property Description Expected Type
Properties inherited from current:E19_Physical_Object
current:P55_has_current_location Scope note: This property records the location of an E19 Physical Object at the time of validity of the record or database containing the statement that uses this property. This property is a specialisation of has former or current location (is former or current location of). It indicates that the E53 Place associated with the E19 Physical Object is the current location of the object. The property does not allow any indication of how long the Object has been at the current location. P55 has current location (currently holds) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P25 moved (moved by), E9 Move P26 moved to (was destination of) to E53 Place if and only if this Move is the most recent. Examples: - silver cup 232 (E22) has current location Display cabinet 23, Room 4, British Museum (E53) current:E53_Place
current:P56_bears_feature Scope note: This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears. An E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An E27 Site should be considered as an E26 Physical Feature on the surface of the Earth. An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i found on the same E19 Physical Object as A. P56 bears feature (is found on) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P59 has section (is located on or within), E53 Place, has former or current location (is former or current location of) to E26 Physical Feature. Examples: - silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26) current:E26_Physical_Feature
Properties inherited from current:E18_Physical_Thing
current:P128_carries Scope note: This property identifies an E90 Symbolic Object carried by an instance of E24 Physical Man-Made Thing. In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items. Examples: - Matthew's paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73) current:E90_Symbolic_Object
current:P157i_provides_reference_space_for current:E53_Place
current:P45_consists_of Scope note: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material. A Material, such as a theoretical alloy, may not have any physical instances. silver cup 232 (E22) consists of silver (E57) current:E57_Material
current:P46_is_composed_of Scope note: 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). Examples: - the Royal carriage (E22) forms part of the Royal train (E22) - the "Hog's Back" (E24) forms part of the "Fosseway" (E24) current:E18_Physical_Thing
current:P46i_forms_part_of current:E18_Physical_Thing
current:P49_has_former_or_current_keeper Scope note: This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at some time. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody received by (received custody through) to E39 Actor. Examples: - paintings from The Iveagh Bequest (E18) has former or current keeper Secure Deliveries Inc. (E40) current:E39_Actor
current:P50_has_current_keeper Scope note: This property identifies the E39 Actor or Actors who had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. P50 has current keeper (is current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P29 custody received by (received custody through) to E39 Actor. Examples: - painting from The Iveagh Bequest (E18) has current keeper The National Gallery (E40) current:E39_Actor
current:P51_has_current_or_former_owner Scope note: This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor. Examples: - paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21) current:E39_Actor
current:P53_has_former_or_current_location Biblissima uses this property for both, the current or former location of a book and the location of an E34_Inscription like a Provenance Mark on a folio. Example: E34_Inscription -> P128i_is_carried_by -> E25_Man-Made_Feature -> _has_former_or_current_location -> E53_Place (URI folio; e.g. ARK: BnF/Shelfmark/Folio) -> P87_is_idenfied_by -> E46_Section_Definition (label folio; e.g.) -> P58i defindes section -> F4 (URI manuscript) current:E53_Place
current:P58_has_section_definition Scope note: This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing. Examples: - HMS Victory (E22) has section definition "poop deck of HMS Victory" (E46) current:E46_Section_Definition
current:P59_has_section Scope note: This property links an area to the instance of E18 Physical Thing upon which it is found. It is typically used when a named E46 Section Definition is not appropriate. E18 Physical Thing may be subdivided into arbitrary regions. P59 has section (is located on or within) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed (i.e. indirect) path from E18 Physical Thing through P58 has section definition (defines section), E46 Section Definition, P87 is identified by (identifies) to E53 Place. A Place can only be located on or within one Physical Object. Examples: - HMS Victory (E22) has section HMS Victory section B347.6 (E53) current:E53_Place
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E24_Physical_Man-Made_Thing
current:P108i_was_produced_by current:E12_Production
current:P31i_was_modified_by current:E11_Modification
current:P62_depicts Scope note: This property identifies something that is depicted by an instance of E24 Physical Man-Made Thing. This property is a shortcut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined. Examples: - the painting "La Liberté guidant le peuple" by Eugène Delacroix (E84) depicts the French "July Revolution" of 1830 (E7) - the 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E24) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55) current:E1_CRM_Entity

rdfs:comment

Membre de CIDOC CRM CORE

Scope note:
This class comprises all persistent physical items that are purposely created by human activity.
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.

Examples:
- the Forth Railway Bridge (E22)
- the Channel Tunnel (E25)
- the Historical Collection of the Museum Benaki in Athens (E78)

rdfs:label

E24 Chose matérielle fabriquée

E24 Physical Man-Made Thing

owl:disjointWith

http://erlangen-crm.org/current/E35_Title

http://erlangen-crm.org/current/E73_Information_Object

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/efrbroo/F12_Nomen

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/current/E56_Language

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/current/E58_Measurement_Unit

https://w3id.org/bibma/Record

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E90_Symbolic_Object

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E28_Conceptual_Object

https://w3id.org/bibma/Incipit

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/current/E2_Temporal_Entity

http://erlangen-crm.org/current/E55_Type

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/efrbroo/F1_Work

http://erlangen-crm.org/current/E82_Actor_Appellation

https://w3id.org/bibma/Written_Area_Production

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/current/E46_Section_Definition

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E42_Identifier

https://w3id.org/bibma/Electronic_Edition

skos:notation

E24

Instances of current:E24_Physical_Man-Made_Thing can have the following properties:

Property Description Expected Type
Properties inherited from current:E18_Physical_Thing
current:P128_carries Scope note: This property identifies an E90 Symbolic Object carried by an instance of E24 Physical Man-Made Thing. In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items. Examples: - Matthew's paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73) current:E90_Symbolic_Object
current:P157i_provides_reference_space_for current:E53_Place
current:P45_consists_of Scope note: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material. A Material, such as a theoretical alloy, may not have any physical instances. silver cup 232 (E22) consists of silver (E57) current:E57_Material
current:P46_is_composed_of Scope note: 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). Examples: - the Royal carriage (E22) forms part of the Royal train (E22) - the "Hog's Back" (E24) forms part of the "Fosseway" (E24) current:E18_Physical_Thing
current:P46i_forms_part_of current:E18_Physical_Thing
current:P49_has_former_or_current_keeper Scope note: This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at some time. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody received by (received custody through) to E39 Actor. Examples: - paintings from The Iveagh Bequest (E18) has former or current keeper Secure Deliveries Inc. (E40) current:E39_Actor
current:P50_has_current_keeper Scope note: This property identifies the E39 Actor or Actors who had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. P50 has current keeper (is current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P29 custody received by (received custody through) to E39 Actor. Examples: - painting from The Iveagh Bequest (E18) has current keeper The National Gallery (E40) current:E39_Actor
current:P51_has_current_or_former_owner Scope note: This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor. Examples: - paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21) current:E39_Actor
current:P53_has_former_or_current_location Biblissima uses this property for both, the current or former location of a book and the location of an E34_Inscription like a Provenance Mark on a folio. Example: E34_Inscription -> P128i_is_carried_by -> E25_Man-Made_Feature -> _has_former_or_current_location -> E53_Place (URI folio; e.g. ARK: BnF/Shelfmark/Folio) -> P87_is_idenfied_by -> E46_Section_Definition (label folio; e.g.) -> P58i defindes section -> F4 (URI manuscript) current:E53_Place
current:P58_has_section_definition Scope note: This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing. Examples: - HMS Victory (E22) has section definition "poop deck of HMS Victory" (E46) current:E46_Section_Definition
current:P59_has_section Scope note: This property links an area to the instance of E18 Physical Thing upon which it is found. It is typically used when a named E46 Section Definition is not appropriate. E18 Physical Thing may be subdivided into arbitrary regions. P59 has section (is located on or within) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed (i.e. indirect) path from E18 Physical Thing through P58 has section definition (defines section), E46 Section Definition, P87 is identified by (identifies) to E53 Place. A Place can only be located on or within one Physical Object. Examples: - HMS Victory (E22) has section HMS Victory section B347.6 (E53) current:E53_Place
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties from current:E24_Physical_Man-Made_Thing
current:P108i_was_produced_by current:E12_Production
current:P31i_was_modified_by current:E11_Modification
current:P62_depicts Scope note: This property identifies something that is depicted by an instance of E24 Physical Man-Made Thing. This property is a shortcut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined. Examples: - the painting "La Liberté guidant le peuple" by Eugène Delacroix (E84) depicts the French "July Revolution" of 1830 (E7) - the 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E24) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55) current:E1_CRM_Entity

rdfs:comment

Scope note:
This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc.
No assumptions are made as to the extent of modification required to justify regarding a feature as man-made. For example, rock art or even "cup and ring" carvings on bedrock a regarded as types of E25 Man-Made Feature.

Examples:
- the Manchester Ship Canal
- Michael Jackson's nose following plastic surgery

rdfs:label

E25 Man-Made Feature

owl:disjointWith

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/E33_Linguistic_Object

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E42_Identifier

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/current/E48_Place_Name

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Written_Area_Production

http://erlangen-crm.org/current/E35_Title

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E28_Conceptual_Object

https://w3id.org/bibma/Style_of_Script

https://w3id.org/bibma/Electronic_Edition

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E2_Temporal_Entity

http://erlangen-crm.org/current/E56_Language

http://erlangen-crm.org/current/E37_Mark

https://w3id.org/bibma/Record

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/current/E55_Type

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E89_Propositional_Object

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E46_Section_Definition

http://erlangen-crm.org/current/E41_Appellation

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/current/E34_Inscription

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/efrbroo/F12_Nomen

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/current/E58_Measurement_Unit

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/efrbroo/F1_Work

http://erlangen-crm.org/efrbroo/F13_Identifier

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/current/E31_Document

skos:notation

E25

Instances of current:E25_Man-Made_Feature can have the following properties:

Property Description Expected Type
Properties inherited from current:E26_Physical_Feature
current:P56i_is_found_on current:E19_Physical_Object
Properties inherited from current:E18_Physical_Thing
current:P128_carries Scope note: This property identifies an E90 Symbolic Object carried by an instance of E24 Physical Man-Made Thing. In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items. Examples: - Matthew's paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73) current:E90_Symbolic_Object
current:P157i_provides_reference_space_for current:E53_Place
current:P45_consists_of Scope note: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material. A Material, such as a theoretical alloy, may not have any physical instances. silver cup 232 (E22) consists of silver (E57) current:E57_Material
current:P46_is_composed_of Scope note: 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). Examples: - the Royal carriage (E22) forms part of the Royal train (E22) - the "Hog's Back" (E24) forms part of the "Fosseway" (E24) current:E18_Physical_Thing
current:P46i_forms_part_of current:E18_Physical_Thing
current:P49_has_former_or_current_keeper Scope note: This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at some time. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody received by (received custody through) to E39 Actor. Examples: - paintings from The Iveagh Bequest (E18) has former or current keeper Secure Deliveries Inc. (E40) current:E39_Actor
current:P50_has_current_keeper Scope note: This property identifies the E39 Actor or Actors who had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. P50 has current keeper (is current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P29 custody received by (received custody through) to E39 Actor. Examples: - painting from The Iveagh Bequest (E18) has current keeper The National Gallery (E40) current:E39_Actor
current:P51_has_current_or_former_owner Scope note: This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor. Examples: - paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21) current:E39_Actor
current:P53_has_former_or_current_location Biblissima uses this property for both, the current or former location of a book and the location of an E34_Inscription like a Provenance Mark on a folio. Example: E34_Inscription -> P128i_is_carried_by -> E25_Man-Made_Feature -> _has_former_or_current_location -> E53_Place (URI folio; e.g. ARK: BnF/Shelfmark/Folio) -> P87_is_idenfied_by -> E46_Section_Definition (label folio; e.g.) -> P58i defindes section -> F4 (URI manuscript) current:E53_Place
current:P58_has_section_definition Scope note: This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing. Examples: - HMS Victory (E22) has section definition "poop deck of HMS Victory" (E46) current:E46_Section_Definition
current:P59_has_section Scope note: This property links an area to the instance of E18 Physical Thing upon which it is found. It is typically used when a named E46 Section Definition is not appropriate. E18 Physical Thing may be subdivided into arbitrary regions. P59 has section (is located on or within) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed (i.e. indirect) path from E18 Physical Thing through P58 has section definition (defines section), E46 Section Definition, P87 is identified by (identifies) to E53 Place. A Place can only be located on or within one Physical Object. Examples: - HMS Victory (E22) has section HMS Victory section B347.6 (E53) current:E53_Place
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E24_Physical_Man-Made_Thing
current:P108i_was_produced_by current:E12_Production
current:P31i_was_modified_by current:E11_Modification
current:P62_depicts Scope note: This property identifies something that is depicted by an instance of E24 Physical Man-Made Thing. This property is a shortcut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1 CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined. Examples: - the painting "La Liberté guidant le peuple" by Eugène Delacroix (E84) depicts the French "July Revolution" of 1830 (E7) - the 20 pence coin held by the Department of Coins and Medals of the British Museum under registration number 2006,1101.126 (E24) depicts Queen Elizabeth II (E21) mode of depiction Profile (E55) current:E1_CRM_Entity

rdfs:comment

Scope note:
This class comprises identifiable features that are physically attached in an integral way to particular physical objects.
Instances of E26 Physical Feature share many of the attributes of instances of E19 Physical Object. They may have a one-, two- or three-dimensional geometric extent, but there are no natural borders that separate them completely in an objective way from the carrier objects. For example, a doorway is a feature but the door itself, being attached by hinges, is not.
Instances of E26 Physical Feature can be features in a narrower sense, such as scratches, holes, reliefs, surface colours, reflection zones in an opal crystal or a density change in a piece of wood. In the wider sense, they are portions of particular objects with partially imaginary borders, such as the core of the Earth, an area of property on the surface of the Earth, a landscape or the head of a contiguous marble statue. They can be measured and dated, and it is sometimes possible to state who or what is or was responsible for them. They cannot be separated from the carrier object, but a segment of the carrier object may be identified (or sometimes removed) carrying the complete feature.
This definition coincides with the definition of "fiat objects" (Smith & Varzi, 2000, pp.401-420), with the exception of aggregates of "bona fide objects".

Examples:
- the temple in Abu Simbel before its removal
- Albrecht Duerer's signature on his painting of Charles the Great
- the damage to the nose of the Great Sphinx in Giza
- Michael Jackson's nose prior to plastic surgery

rdfs:label

E26 Physical Feature

owl:disjointWith

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/efrbroo/F13_Identifier

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/current/E90_Symbolic_Object

http://erlangen-crm.org/current/E46_Section_Definition

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/current/E89_Propositional_Object

https://w3id.org/bibma/Explicit

http://erlangen-crm.org/current/E41_Appellation

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/current/E58_Measurement_Unit

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/efrbroo/F12_Nomen

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E35_Title

http://erlangen-crm.org/current/E56_Language

http://erlangen-crm.org/efrbroo/F15_Complex_Work

https://w3id.org/bibma/Record

http://erlangen-crm.org/current/E2_Temporal_Entity

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/current/E42_Identifier

http://erlangen-crm.org/current/E55_Type

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E73_Information_Object

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/current/F6_Concept

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

http://erlangen-crm.org/current/E28_Conceptual_Object

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Electronic_Edition

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/efrbroo/F1_Work

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E31_Document

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/current/E33_Linguistic_Object

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Record_Creation

skos:notation

E26

Instances of current:E26_Physical_Feature can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E18_Physical_Thing
current:P128_carries Scope note: This property identifies an E90 Symbolic Object carried by an instance of E24 Physical Man-Made Thing. In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items. Examples: - Matthew's paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73) current:E90_Symbolic_Object
current:P157i_provides_reference_space_for current:E53_Place
current:P45_consists_of Scope note: This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed. All physical things consist of physical materials. P45 consists of (is incorporated in) allows the different Materials to be recorded. P45 consists of (is incorporated in) refers here to observed Material as opposed to the consumed raw material. A Material, such as a theoretical alloy, may not have any physical instances. silver cup 232 (E22) consists of silver (E57) current:E57_Material
current:P46_is_composed_of Scope note: 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). Examples: - the Royal carriage (E22) forms part of the Royal train (E22) - the "Hog's Back" (E24) forms part of the "Fosseway" (E24) current:E18_Physical_Thing
current:P46i_forms_part_of current:E18_Physical_Thing
current:P49_has_former_or_current_keeper Scope note: This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at some time. The distinction with P50 has current keeper (is current keeper of) is that P49 has former or current keeper (is former or current keeper of) leaves open the question as to whether the specified keepers are current. P49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody received by (received custody through) to E39 Actor. Examples: - paintings from The Iveagh Bequest (E18) has former or current keeper Secure Deliveries Inc. (E40) current:E39_Actor
current:P50_has_current_keeper Scope note: This property identifies the E39 Actor or Actors who had custody of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property. P50 has current keeper (is current keeper of) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10 Transfer of Custody, P29 custody received by (received custody through) to E39 Actor. Examples: - painting from The Iveagh Bequest (E18) has current keeper The National Gallery (E40) current:E39_Actor
current:P51_has_current_or_former_owner Scope note: This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor. Examples: - paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21) current:E39_Actor
current:P53_has_former_or_current_location Biblissima uses this property for both, the current or former location of a book and the location of an E34_Inscription like a Provenance Mark on a folio. Example: E34_Inscription -> P128i_is_carried_by -> E25_Man-Made_Feature -> _has_former_or_current_location -> E53_Place (URI folio; e.g. ARK: BnF/Shelfmark/Folio) -> P87_is_idenfied_by -> E46_Section_Definition (label folio; e.g.) -> P58i defindes section -> F4 (URI manuscript) current:E53_Place
current:P58_has_section_definition Scope note: This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing. Examples: - HMS Victory (E22) has section definition "poop deck of HMS Victory" (E46) current:E46_Section_Definition
current:P59_has_section Scope note: This property links an area to the instance of E18 Physical Thing upon which it is found. It is typically used when a named E46 Section Definition is not appropriate. E18 Physical Thing may be subdivided into arbitrary regions. P59 has section (is located on or within) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed (i.e. indirect) path from E18 Physical Thing through P58 has section definition (defines section), E46 Section Definition, P87 is identified by (identifies) to E53 Place. A Place can only be located on or within one Physical Object. Examples: - HMS Victory (E22) has section HMS Victory section B347.6 (E53) current:E53_Place
Properties from current:E26_Physical_Feature
current:P56i_is_found_on current:E19_Physical_Object

rdfs:comment

Scope note:
This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation or historical implication. 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 E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, 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.

Examples:
- Beethoven's "Ode an die Freude" (Ode to Joy) (E73)
- the definition of "ontology" in the Oxford English Dictionary
- the knowledge about the victory at Marathon carried by the famous runner

Membre de CIDOC CRM CORE

rdfs:label

E28 Objet conceptuel

E28 Conceptual Object

owl:disjointWith

https://w3id.org/bibma/Folio_Extent

https://w3id.org/bibma/Component

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Provenance_Mark

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E2_Temporal_Entity

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/current/E84_Information_Carrier

https://w3id.org/bibma/Binding

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Component_Production

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Scribe_Assignment

https://w3id.org/bibma/Place_Assignment

owl:equivalentClass

http://erlangen-crm.org/current/F6_Concept

skos:notation

E28

Instances of current:E28_Conceptual_Object can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation

rdfs:comment

Scope note:
This class comprises all phenomena, such as the instances of E4 Periods, E5 Events and states, which
happen over a limited extent in time.
Thi
s extent in time must be contiguous, i.e., without gaps. In case
the defining kinds of phenomena for an instance of E2 Temporal Entity cease to happen, and occur
later again at another time, we regard that the former E2 Temporal Entity has ended and a new
instance
has come into existence. In more intuitive terms, the same event cannot happen twice.
In some contexts, these are also called perdurants. This class is disjoint from E77 Persistent Item. This
is an abstract class and has no direct instances. E2
Temporal Entity is specialized into E4 Period, which
applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3
Condition State, which applies to instances of E18 Physical Thing.

Examples:
- Bronze Age (E4)
- the earthquake in Lisbon 1755 (E5)
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 – 1946 (E3)

Membre de CIDOC CRM CORE

rdfs:label

E2 Temporal Entity

E2 Entité temporelle

owl:disjointWith

http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression

http://erlangen-crm.org/current/E34_Inscription

http://erlangen-crm.org/efrbroo/F1_Work

http://erlangen-crm.org/current/E47_Spatial_Coordinates

http://erlangen-crm.org/current/E89_Propositional_Object

http://erlangen-crm.org/current/E74_Group

http://erlangen-crm.org/current/E33_Linguistic_Object

https://w3id.org/bibma/Record

http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation

http://erlangen-crm.org/current/E90_Symbolic_Object

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Annotation

http://erlangen-crm.org/current/E58_Measurement_Unit

http://erlangen-crm.org/current/E44_Place_Appellation

http://erlangen-crm.org/current/E46_Section_Definition

http://erlangen-crm.org/current/E39_Actor

http://erlangen-crm.org/efrbroo/F23_Expression_Fragment

https://w3id.org/bibma/Incipit

http://erlangen-crm.org/efrbroo/F2_Expression

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E77_Persistent_Item

https://w3id.org/bibma/Explicit

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/current/E37_Mark

http://erlangen-crm.org/current/E41_Appellation

http://erlangen-crm.org/efrbroo/F10_Person

http://erlangen-crm.org/current/E55_Type

http://erlangen-crm.org/current/E32_Authority_Document

http://erlangen-crm.org/current/E82_Actor_Appellation

http://erlangen-crm.org/current/E56_Language

http://erlangen-crm.org/current/E70_Thing

http://erlangen-crm.org/efrbroo/F15_Complex_Work

http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type

http://erlangen-crm.org/current/E35_Title

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Folio

http://erlangen-crm.org/current/E48_Place_Name

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Electronic_Edition

http://erlangen-crm.org/current/E36_Visual_Item

http://erlangen-crm.org/current/E42_Identifier

http://erlangen-crm.org/current/E38_Image

http://erlangen-crm.org/current/E73_Information_Object

https://w3id.org/bibma/Style_of_Script

http://erlangen-crm.org/efrbroo/F12_Nomen

https://w3id.org/bibma/Written_Area

http://erlangen-crm.org/efrbroo/F24_Publication_Expression

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/current/F6_Concept

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E40_Legal_Body

https://w3id.org/bibma/Binding

http://erlangen-crm.org/current/E31_Document

https://w3id.org/bibma/Component

http://erlangen-crm.org/efrbroo/F13_Identifier

http://erlangen-crm.org/current/E57_Material

http://erlangen-crm.org/current/E71_Man-Made_Thing

http://erlangen-crm.org/current/E72_Legal_Object

skos:notation

E2

Instances of current:E2_Temporal_Entity can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties from current:E2_Temporal_Entity
current:P4_has_time-span Membre de CIDOC CRM CORE current:E52_Time-Span

rdfs:comment

Scope note:
This class comprises identifiable immaterial items that make propositions about reality.
These propositions may be expressed in text, graphics, images, audiograms, videograms or by other similar means. Documentation databases are regarded as a special case of E31 Document. This class should not be confused with the term "document" in Information Technology, which is compatible with E73 Information Object.

Examples:
- the Encyclopaedia Britannica (E32)
- The image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E38)
- the Doomsday Book

rdfs:label

E31 Document

owl:disjointWith

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Component

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Scribe_Assignment

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Component_Production

https://w3id.org/bibma/Folio

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Illumination

https://w3id.org/bibma/Written_Area

skos:notation

E31

Instances of current:E31_Document can have the following properties:

Property Description Expected Type
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object
Properties from current:E31_Document
current:P70_documents Scope note: This property describes the CRM Entities documented by instances of E31 Document. Documents may describe any conceivable entity, hence the link to the highest-level entity in the CRM hierarchy. This property is intended for cases where a reference is regarded as being of a documentary character, in the scholarly or scientific sense. Examples: - the British Museum catalogue (E31) documents the British Museum's Collection (E78) current:E1_CRM_Entity

rdfs:comment

Scope note:
This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.

Examples:
- Webster's Dictionary
- Getty Art and Architecture Thesaurus
- CIDOC Conceptual Reference Model

rdfs:label

E32 Authority Document

owl:disjointWith

https://w3id.org/bibma/Manuscript

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Scribe_Assignment

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Component

https://w3id.org/bibma/Digital_Surrogate

skos:notation

E32

Instances of current:E32_Authority_Document can have the following properties:

Property Description Expected Type
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object
Properties inherited from current:E31_Document
current:P70_documents Scope note: This property describes the CRM Entities documented by instances of E31 Document. Documents may describe any conceivable entity, hence the link to the highest-level entity in the CRM hierarchy. This property is intended for cases where a reference is regarded as being of a documentary character, in the scholarly or scientific sense. Examples: - the British Museum catalogue (E31) documents the British Museum's Collection (E78) current:E1_CRM_Entity

rdfs:comment

Scope note:
This class comprises identifiable expressions in natural language or languages.
Instances of E33 Linguistic Object can be expressed in many ways: e.g. as written texts, recorded speech or sign language. However, the CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CRM. These should be modelled as instances of E73 Information Object.
The text of an instance of E33 Linguistic Object can be documented in a note by P3 has note: E62 String

Examples:
- the text of the Ellesmere Chaucer manuscript
- the lyrics of the song "Blue Suede Shoes"
- the text of the Jabberwocky by Lewis Carroll
- the text of "Doktoro Jekyll kaj Sinjoro Hyde" (an Esperanto translation of Dr Jekyll and Mr Hyde)

rdfs:label

E33 Linguistic Object

owl:disjointWith

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Illumination

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E84_Information_Carrier

https://w3id.org/bibma/Component

https://w3id.org/bibma/Written_Area

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Binding

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Dispersed_Manuscript

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Component_Production

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Provenance_Mark

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Written_Area_Production

skos:notation

E33

Instances of current:E33_Linguistic_Object can have the following properties:

Property Description Expected Type
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object
Properties from current:E33_Linguistic_Object
current:P72_has_language Scope note: This property describes the E56 Language of an E33 Linguistic Object. Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented. Examples: - the American Declaration of Independence (E33) has language 18th Century English (E56) current:E56_Language

rdfs:comment

Scope note:
This class comprises recognisable, short texts attached to instances of E24 Physical Man-Made Thing.
The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CRM as E24 Physical Man-Made Thing.
The relationship of a physical copy of a book to the text it contains is modelled using E84 Information Carrier. P128 carries (is carried by): E33 Linguistic Object.

Examples:
- "keep of the grass" on a sign stuck in the lawn of the quad of Balliol College
- Kilroy was here
- the text published in Corpus Inscriptionum LatinarumV 895

rdfs:label

E34 Inscription

owl:disjointWith

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Folio_Extent

https://w3id.org/bibma/Component

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E84_Information_Carrier

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Written_Area

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Illumination

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Digital_Surrogate

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Written_Area_Production

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E65_Creation

skos:notation

E34

Instances of current:E34_Inscription can have the following properties:

Property Description Expected Type
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object
Properties inherited from current:E33_Linguistic_Object
current:P72_has_language Scope note: This property describes the E56 Language of an E33 Linguistic Object. Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented. Examples: - the American Declaration of Independence (E33) has language 18th Century English (E56) current:E56_Language

rdfs:comment

Scope note:
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.

Examples:
- "The Merchant of Venice"
- "Mona Lisa"
- "La Pie or The Magpie"
- "Lucy in the Sky with Diamonds"

rdfs:label

E35 Title

owl:disjointWith

https://w3id.org/bibma/Written_Area_Production

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Binding

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Component

https://w3id.org/bibma/Written_Area

http://erlangen-crm.org/current/E84_Information_Carrier

https://w3id.org/bibma/Folio_Extent

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Illumination

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

skos:notation

E35

Instances of current:E35_Title can have the following properties:

Property Description Expected Type
Properties inherited from current:E41_Appellation
current:P1i_identifies Membre de CIDOC CRM CORE current:E1_CRM_Entity
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object
Properties inherited from current:E33_Linguistic_Object
current:P72_has_language Scope note: This property describes the E56 Language of an E33 Linguistic Object. Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented. Examples: - the American Declaration of Independence (E33) has language 18th Century English (E56) current:E56_Language
Properties from current:E35_Title
current:P102i_is_title_of current:E71_Man-Made_Thing

rdfs:comment

Scope note:
This class comprises the intellectual or conceptual aspects of recognisable marks and images.
This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support.
The class E36 Visual Item provides a means of identifying and linking together instances of E24 Physical Man-Made Thing that carry the same visual symbols, marks or images etc. The property P62 depicts (is depicted by) between E24 Physical Man-Made Thing and depicted subjects (E1 CRM Entity) can be regarded as a short-cut of the more fully developed path from E24 Physical Man-Made Thing through P6 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity, which in addition captures the optical features of the depiction.

Examples:
- the visual appearance of Monet's "La Pie" (E38)
- the Coca-Cola logo (E34)
- the Chi-Rho (E37)
- the communist red star (E37)

rdfs:label

E36 Visual Item

owl:disjointWith

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Folio

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Component_Production

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Scribe_Assignment

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Component

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Written_Area_Production

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

skos:notation

E36

Instances of current:E36_Visual_Item can have the following properties:

Property Description Expected Type
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object

rdfs:comment

Scope note:
This class comprises symbols, signs, signatures or short texts applied to instances of E24 Physical Man-Made Thing by arbitrary techniques in order to indicate the creator, owner, dedications, purpose, etc.
This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Man-Made Feature.

Examples:
- Minoan double axe mark
- the "copyright sign"
- the smiley symbol

rdfs:label

E37 Mark

owl:disjointWith

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Folio_Extent

https://w3id.org/bibma/Manuscript

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Component

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Folio

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Provenance_Mark

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Written_Area

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Scribe_Assignment

skos:notation

E37

Instances of current:E37_Mark can have the following properties:

Property Description Expected Type
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object

rdfs:comment

Scope note:
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 E38 Image depends on a given purpose. The original painting of the Mona Lisa in the Louvre may be said to bear the same instance of E38 Image as reproductions in the form of transparencies, postcards, posters or T-shirts, even though they may differ in size and carrier and may vary in tone and colour. The images in a "spot the difference" competition are not the same with respect to their context, however similar they may at first appear.

Examples:
- the front side of all 20 Frs notes
- the image depicted on all reproductions of the Mona Lisa

rdfs:label

E38 Image

owl:disjointWith

https://w3id.org/bibma/Manuscript

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Folio_Extent

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Folio

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Annotation

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Component

skos:notation

E38

Instances of current:E38_Image can have the following properties:

Property Description Expected Type
Properties inherited from current:E89_Propositional_Object
current:P148_has_component Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) current:E89_Propositional_Object
current:P148i_is_component_of Membre de CIDOC CRM CORE current:E89_Propositional_Object
current:P67_refers_to Membre de CICOD CRM CORE current:E1_CRM_Entity
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties inherited from current:E73_Information_Object
current:P165_incorporates ThThis property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page. Examples: The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) current:E90_Symbolic_Object

rdfs:comment

Membre de CIDOC CRM CORE

Scope note:
This class comprises people, either individually or in groups, who have the potential to perform intentional actions of
kinds for which someone may be held responsible.
The CRM does not attempt to model the inadvertent actions of such actors. Individual people should be documented as instances of E21 Person, whereas groups should be documented as instances of either E74 Group or its subclass E40 Legal Body.

Examples:
- London and Continental Railways (E40)
- the Governor of the Bank of England in 1975 (E21)
- Sir Ian McKellan (E21)

rdfs:label

E39 Agent

E39 Actor

owl:disjointWith

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Time-Span_Assignment

http://erlangen-crm.org/current/E65_Creation

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Title_Assignment

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

skos:notation

E39

Instances of current:E39_Actor can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties from current:E39_Actor
current:P11i_participated_in current:E5_Event
current:P131_is_identified_by Scope note: This property identifies a name used specifically to identify an E39 Actor. This property is a specialisation of P1 is identified by (identifies) is identified by. Examples: - Tyler Withersopp IV (E39) is identified by "US social security number 619-17-4204" (E82) current:E82_Actor_Appellation
current:P14i_performed Membre de CIDOC CRM CORE current:E7_Activity
current:P49i_is_former_or_current_keeper_of current:E18_Physical_Thing
current:P50i_is_current_keeper_of current:E18_Physical_Thing
current:P51i_is_former_or_current_owner_of current:E18_Physical_Thing
base:r0270i_performed_as_scribe base:Written_Area_Production
base:r40i_performed_as_annotator base:Annotation_Production
base:r70i_performed_as_author efrbroo:F27_Work_Conception

rdfs:comment

Scope note:
This class comprises institutions or groups of people that have obtained a legal recognition as a group and can act collectively as agents.
This means that they can perform actions, own property, create or destroy things and can be held collectively responsible for their actions like individual people. The term 'personne morale' is often used for this in French.

Examples:
- Greenpeace
- Paveprime Ltd
- the National Museum of Denmark

rdfs:label

E40 Legal Body

owl:disjointWith

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Title_Assignment

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Component_Production

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Record_Creation

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E8_Acquisition

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/efrbroo/F27_Work_Conception

http://erlangen-crm.org/current/E63_Beginning_of_Existence

http://erlangen-crm.org/current/E64_End_of_Existence

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Illumination_Production

http://erlangen-crm.org/current/E5_Event

skos:notation

E40

Instances of current:E40_Legal_Body can have the following properties:

Property Description Expected Type
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E39_Actor
current:P11i_participated_in current:E5_Event
current:P131_is_identified_by Scope note: This property identifies a name used specifically to identify an E39 Actor. This property is a specialisation of P1 is identified by (identifies) is identified by. Examples: - Tyler Withersopp IV (E39) is identified by "US social security number 619-17-4204" (E82) current:E82_Actor_Appellation
current:P14i_performed Membre de CIDOC CRM CORE current:E7_Activity
current:P49i_is_former_or_current_keeper_of current:E18_Physical_Thing
current:P50i_is_current_keeper_of current:E18_Physical_Thing
current:P51i_is_former_or_current_owner_of current:E18_Physical_Thing
base:r0270i_performed_as_scribe base:Written_Area_Production
base:r40i_performed_as_annotator base:Annotation_Production
base:r70i_performed_as_author efrbroo:F27_Work_Conception

rdfs:comment

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”]

Membre de CIDOC CRM CORE

rdfs:label

E41 Appellation

E41 Appellation

owl:disjointWith

http://erlangen-crm.org/current/E4_Period

http://erlangen-crm.org/current/E5_Event

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/current/E7_Activity

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Binding

https://w3id.org/bibma/Folio_Extent

https://w3id.org/bibma/Scribe_Assignment

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Component

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Annotation

http://erlangen-crm.org/current/E84_Information_Carrier

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Owner_Assignment

https://w3id.org/bibma/Component_Production

https://w3id.org/bibma/Annotation_Production

https://w3id.org/bibma/Place_Assignment

https://w3id.org/bibma/Illumination

https://w3id.org/bibma/Digital_Surrogate

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Folio

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Manuscript

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Title_Assignment

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

skos:notation

E41

Instances of current:E41_Appellation can have the following properties:

Property Description Expected Type
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier OXCMS:2001.1.32 (E42) current:E42_Identifier
current:P62i_is_depicted_by current:E24_Physical_Man-Made_Thing
current:P67i_is_referred_to_by Membre de CICOD CRM CORE current:E89_Propositional_Object
current:P70i_is_documented_in current:E31_Document
Properties inherited from current:E77_Persistent_Item
current:P12i_was_present_at Membre de CIDOC CRM CORE current:E5_Event
current:P92i_was_brought_into_existence_by Membre de CIDOC CRM CORE current:E63_Beginning_of_Existence
current:P93i_was_taken_out_of_existence_by Membre de CIDOC CRM CORE current:E64_End_of_Existence
Properties inherited from current:E70_Thing
current:P130_shows_features_of Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) current:E70_Thing
current:P130i_features_are_also_found_on current:E70_Thing
current:P16i_was_used_for Membre de CIDOC CRM CORE current:E7_Activity
current:P43_has_dimension Membre de CIDOC CRM CORE current:E54_Dimension
Properties inherited from current:E90_Symbolic_Object
current:P106_is_composed_of Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - this Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) current:E90_Symbolic_Object
current:P106i_forms_part_of current:E90_Symbolic_Object
current:P128i_is_carried_by current:E24_Physical_Man-Made_Thing
current:P165i_is_incorporated_in current:E73_Information_Object
Properties from current:E41_Appellation
current:P1i_identifies Membre de CIDOC CRM CORE current:E1_CRM_Entity

rdfs:comment

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]

rdfs:label

E42 Identifier

owl:disjointWith

http://erlangen-crm.org/current/E64_End_of_Existence

https://w3id.org/bibma/Component

https://w3id.org/bibma/Component_Production

https://w3id.org/bibma/Written_Area

https://w3id.org/bibma/Folio_Extent

https://w3id.org/bibma/Annotation

http://erlangen-crm.org/current/E5_Event

https://w3id.org/bibma/Place_Assignment

http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton

http://erlangen-crm.org/current/E84_Information_Carrier

http://erlangen-crm.org/current/E65_Creation

https://w3id.org/bibma/Annotation_Production

http://erlangen-crm.org/efrbroo/F33_Reproduction_Event

http://erlangen-crm.org/efrbroo/F27_Work_Conception

https://w3id.org/bibma/Time-Span_Assignment

https://w3id.org/bibma/Record_Creation

http://erlangen-crm.org/current/E63_Beginning_of_Existence

https://w3id.org/bibma/Folio

http://erlangen-crm.org/current/E4_Period

https://w3id.org/bibma/Owner_Assignment

http://erlangen-crm.org/current/E7_Activity

https://w3id.org/bibma/Written_Area_Production

https://w3id.org/bibma/Dispersed_Manuscript

https://w3id.org/bibma/Illumination_Production

https://w3id.org/bibma/Title_Assignment

https://w3id.org/bibma/Provenance_Mark

https://w3id.org/bibma/Illumination

http://erlangen-crm.org/efrbroo/F28_Expression_Creation

https://w3id.org/bibma/Scribe_Assignment

https://w3id.org/bibma/Digital_Surrogate

https://w3id.org/bibma/Manuscript

http://erlangen-crm.org/current/E8_Acquisition

https://w3id.org/bibma/Binding

skos:notation

E42

Instances of current:E42_Identifier can have the following properties:

Property Description Expected Type
Properties inherited from current:E28_Conceptual_Object
current:P94i_was_created_by Membre de CIDOC CRM CORE current:E65_Creation
Properties inherited from current:E71_Man-Made_Thing
current:P102.1_has_type The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. current:E55_Type
current:P102_has_title Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - The first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) current:E35_Title
Properties inherited from current:E1_CRM_Entity
current:P140i_was_attributed_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P141i_was_assigned_by Membre de CIDOC CRM CORE current:E13_Attribute_Assignment
current:P15i_influenced current:E7_Activity
current:P1_is_identified_by Membre de CIDOC CRM CORE current:E41_Appellation
current:P2_has_type Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) current:E55_Type
current:P3_has_note Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" --
current:P48_has_preferred_identifier Scope note: