owl:Ontology
"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 team@biblissima-condorcet.fr"
"Ontologie Biblissima / Florus de Lyon"
Triples: 4366
Entity types:
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity
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
E11 Modification
E11 Modification
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
E11
| 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 |
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E11_Modification
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)
E12 Production
E12 Production
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
E12
| 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 |
URI: http://erlangen-crm.org/current/E13_Attribute_Assignment
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity
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
E13 Affectation d'attribut
E13 Attribute_Assignment
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
E13
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E13_Attribute_Assignment
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
E17 Type Assignment
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
E17
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object
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)
E18 Chose matérielle
E18 Physical Thing
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
E18
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E18_Physical_Thing
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
E19 Physical Object
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
E19
| 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 |
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
E1 Entity
E1 Entité CRM
E1
| 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 | |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E39_Actor
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
E21 Person
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
http://erlangen-crm.org/efrbroo/F10_Person
E21
| 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 | |
owl:Thing | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing
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
E22 Man-Made Object
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
E22
| 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 |
URI: http://erlangen-crm.org/current/E24_Physical_Man-Made_Thing
owl:Thing | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing
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)
E24 Chose matérielle fabriquée
E24 Physical Man-Made Thing
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
E24
| 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 |
URI: http://erlangen-crm.org/current/E25_Man-Made_Feature
owl:Thing | current:E26_Physical_Feature | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing
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
E25 Man-Made Feature
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
E25
| 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 |
URI: http://erlangen-crm.org/current/E26_Physical_Feature
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E18_Physical_Thing
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
E26 Physical Feature
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
E26
| 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 | |
URI: http://erlangen-crm.org/current/E28_Conceptual_Object
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing
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
E28 Objet conceptuel
E28 Conceptual Object
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
http://erlangen-crm.org/current/F6_Concept
E28
| 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 |
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
E2 Temporal Entity
E2 Entité temporelle
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
E2
| 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 |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object
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
E31 Document
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
E31
| 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 |
URI: http://erlangen-crm.org/current/E32_Authority_Document
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E31_Document
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
E32 Authority Document
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
E32
| 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 |
URI: http://erlangen-crm.org/current/E33_Linguistic_Object
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object
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)
E33 Linguistic Object
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
E33
| 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 |
owl:Thing | current:E36_Visual_Item | current:E37_Mark | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E33_Linguistic_Object
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
E34 Inscription
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
E34
| 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 |
owl:Thing | current:E41_Appellation | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E33_Linguistic_Object
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"
E35 Title
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
E35
| 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 | |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object
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)
E36 Visual Item
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
E36
| 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 |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E36_Visual_Item
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
E37 Mark
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
E37
| 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 |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E36_Visual_Item
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
E38 Image
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
E38
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item
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)
E39 Agent
E39 Actor
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
E39
| 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 | |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E39_Actor | current:E74_Group
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
E40 Legal Body
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
E40
| 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 | |
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object
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
E41 Appellation
E41 Appellation
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
E41
| 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 |
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation | efrbroo:F12_Nomen | efrbroo:F13_Identifier
Scope note:
This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
- "MM.GE.195"
- "13.45.1976"
- "OXCMS: 1997.4.1"
- ISSN "0041-5278"
- ISRC "FIFIN8900116"
- Shelf mark "Res 8 P 10"
- "Guillaume de Machaut (1300?-1377)" [a controlled personal name heading that follows
the French rules]
E42 Identifier
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
E42
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
| Properties from current:E42_Identifier | ||
| current:P48i_is_preferred_identifier_of | current:E1_CRM_Entity | |
URI: http://erlangen-crm.org/current/E44_Place_Appellation
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation
Scope note:
This class comprises any sort of identifier characteristically used to refer to an E53 Place.
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
Examples:
- "Vienna"
- "CH-1211, Genève"
- "Aquae Sulis Minerva"
- "Bath"
- "Cambridge"
- "the Other Place"
- "the City"
E44 Place Appellation
http://erlangen-crm.org/current/E7_Activity
http://erlangen-crm.org/current/E65_Creation
http://erlangen-crm.org/current/E5_Event
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Component_Production
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
http://erlangen-crm.org/current/E64_End_of_Existence
https://w3id.org/bibma/Binding
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Component
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Place_Assignment
http://erlangen-crm.org/current/E50_Date
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Scribe_Assignment
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
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/current/E63_Beginning_of_Existence
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/current/E49_Time_Appellation
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F27_Work_Conception
http://erlangen-crm.org/current/E4_Period
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Record_Creation
E44
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
URI: http://erlangen-crm.org/current/E46_Section_Definition
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation | current:E44_Place_Appellation
Scope note:
This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the "head" of a marble statue made out of one block (cf. E53 Place). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. (Section Definition is closely related to the term "segment" in Gerstl, P.& Pribbenow, S, 1996 " A conceptual theory of part – whole relations and its applications", Data & Knowledge Engineering 20 305-322, North Holland- Elsevier).
Examples:
- "the entrance lobby to the Ripley Center"
- "the poop deck of H.M.S Victory"
- "the Venus de Milo's left buttock"
- "left inner side of my box"
E46 Section Definition
https://w3id.org/bibma/Place_Assignment
http://erlangen-crm.org/current/E7_Activity
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/current/E5_Event
https://w3id.org/bibma/Annotation_Production
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
http://erlangen-crm.org/current/E64_End_of_Existence
https://w3id.org/bibma/Component
http://erlangen-crm.org/current/E49_Time_Appellation
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/current/E63_Beginning_of_Existence
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Time-Span_Assignment
http://erlangen-crm.org/current/E65_Creation
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/current/E4_Period
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/current/E50_Date
https://w3id.org/bibma/Digital_Surrogate
E46
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
| Properties from current:E46_Section_Definition | ||
| current:P58i_defines_section | current:E18_Physical_Thing | |
URI: http://erlangen-crm.org/current/E47_Spatial_Coordinates
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation | current:E44_Place_Appellation
Contentu de référentiels Biblissima !
Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- "6°5'29"N 45°12'13"W"
- "Black queen's bishop 4" [chess coordinate].
E47 Spatial Coordinates
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/efrbroo/F27_Work_Conception
http://erlangen-crm.org/current/E5_Event
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/current/E63_Beginning_of_Existence
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/current/E49_Time_Appellation
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Binding
http://erlangen-crm.org/current/E50_Date
http://erlangen-crm.org/current/E64_End_of_Existence
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/current/E84_Information_Carrier
https://w3id.org/bibma/Component
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Folio
http://erlangen-crm.org/current/E4_Period
http://erlangen-crm.org/current/E7_Activity
http://erlangen-crm.org/current/E65_Creation
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Illumination
E47
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation | current:E44_Place_Appellation
Scope note:
This class comprises particular and common forms of E44 Place Appellation.
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.
Examples:
- "Greece"
- "Athens"
- "Geneva"
- "Lac Léman"
E48 Place Name
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Binding
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Time-Span_Assignment
http://erlangen-crm.org/current/E65_Creation
http://erlangen-crm.org/current/E64_End_of_Existence
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/current/E7_Activity
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Component
http://erlangen-crm.org/current/E5_Event
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/current/E50_Date
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/current/E49_Time_Appellation
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/current/E63_Beginning_of_Existence
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/current/E4_Period
https://w3id.org/bibma/Folio
E48
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
URI: http://erlangen-crm.org/current/E49_Time_Appellation
Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, "Before Christ" for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. 'the duration of the Ming Dynasty'.
Examples:
- "Meiji" [Japanese term for a specific time-span]
- "1st half of the XX century"
- "Quaternary"
- "1215 Hegira" [a date in the Islamic calendar]
- "Last century"
E49 Time Appellation
http://erlangen-crm.org/efrbroo/F9_Place
http://erlangen-crm.org/current/E53_Place
E49
| 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:E52_Time-Span | ||
| current:P4i_is_time-span_of | Membre de CIDOC CRM CORE | current:E2_Temporal_Entity |
| current:P79_beginning_is_qualified_by | Scope note: This property qualifies the beginning of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) beginning is qualified by "approximately" | -- |
| current:P80_end_is_qualified_by | Scope note: This property qualifies the end of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) end is qualified by "approximately" | -- |
| current:P81_ongoing_throughout | Membre de CIDOC CRM CORE | -- |
| current:P82_at_some_time_within | Membre de CIDOC CRM CORE | -- |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity
Scope note:
This class comprises sets of coherent phenomena or cultural manifestations bounded in time and space.
It is the social or physical coherence of these phenomena that identify an E4 Period and not the associated spatio-temporal bounds. These bounds are a mere approximation of the actual process of growth, spread and retreat. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area as a sedentary culture.
Typically this
class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the
“Ming
Dynasty” or the “McCarthy Era”, but also geopolitical units and activities of settlements are
regarded as special cases of E4 Period.
Geopolitical units may
be distributed over disconnected areas,
such as islands or colonies. In
such cases
, the spatiotemporal extent is composed of more than one
spacetime volume. One may argue that the activities to govern disconnected areas imply travelling
through spaces con
necting them and that these areas hence are spatially connected in a way, but it
appears counterintuitive to consider for instance travel routes in international waters as extensions of
geopolitical units. Nevertheless, an instance of E4 Period must be con
tiguous in time. I.e., if it has
ended in all areas, it has ended as a whole, but
it may
involve
one
area
after
another
, such as the
Polynesian
migration, as long as it is ongoing at least in one area.
There are no
assumptions about the scale of the assoc
iated phenomena. In particular all events are seen
as synthetic processes consisting of coherent phenomena. Therefore E4 Period is a superclass of E5
Event. For example, a modern clinical E67 Birth can be seen as both an atomic E5 Event and as an E4
Period
that consists of multiple activities performed by multiple instances of E39 Actor.
There are two different conceptualisations of 'artistic style', defined either by physical features or by historical context. For example, "Impressionism" can be viewed as a period lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an E4 Period, and the second defines morphological object types that fall under E55 Type.
Another specific case of an E4 Period is the set of activities and phenomena associated with a settlement, such as the populated period of Nineveh.
Examples:
- Jurassic
- European Bronze Age
- Italian Renaissance
- Thirty Years War
- Sturm und Drang
- Cubism
Membre de CIDOC CRM CORE
E4 Période
E4 Period
https://w3id.org/bibma/Record
https://w3id.org/bibma/Electronic_Edition
http://erlangen-crm.org/current/E55_Type
http://erlangen-crm.org/current/E82_Actor_Appellation
http://erlangen-crm.org/current/E70_Thing
http://erlangen-crm.org/current/E77_Persistent_Item
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/efrbroo/F24_Publication_Expression
http://erlangen-crm.org/current/E72_Legal_Object
https://w3id.org/bibma/Binding
http://erlangen-crm.org/current/E73_Information_Object
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Incipit
http://erlangen-crm.org/current/E90_Symbolic_Object
http://erlangen-crm.org/current/E71_Man-Made_Thing
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation
http://erlangen-crm.org/efrbroo/F2_Expression
http://erlangen-crm.org/current/E89_Propositional_Object
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Component
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Style_of_Script
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/current/F6_Concept
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/current/E58_Measurement_Unit
http://erlangen-crm.org/current/E74_Group
http://erlangen-crm.org/efrbroo/F1_Work
http://erlangen-crm.org/efrbroo/F12_Nomen
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Folio
http://erlangen-crm.org/current/E56_Language
http://erlangen-crm.org/current/E57_Material
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F10_Person
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
http://erlangen-crm.org/efrbroo/F13_Identifier
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/efrbroo/F15_Complex_Work
E4
| 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 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 | |
owl:Thing | current:E1_CRM_Entity | current:E52_Time-Span | current:E49_Time_Appellation
Scope note:
This class comprises specific forms of E49 Time Appellation.
Dates may vary in their degree of precision.
Examples:
- "1900"
- "4-4-1959"
- "19-MAR-1922"
- "19640604"
E50 Date
http://erlangen-crm.org/efrbroo/F9_Place
http://erlangen-crm.org/current/E53_Place
E50
| 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:E52_Time-Span | ||
| current:P4i_is_time-span_of | Membre de CIDOC CRM CORE | current:E2_Temporal_Entity |
| current:P79_beginning_is_qualified_by | Scope note: This property qualifies the beginning of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) beginning is qualified by "approximately" | -- |
| current:P80_end_is_qualified_by | Scope note: This property qualifies the end of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) end is qualified by "approximately" | -- |
| current:P81_ongoing_throughout | Membre de CIDOC CRM CORE | -- |
| current:P82_at_some_time_within | Membre de CIDOC CRM CORE | -- |
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- from 12-17-1993 to 12-8-1996
- 14h30 - 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Membre de CIDOC CRM CORE
E52 Durée
E52 Time-Span
http://erlangen-crm.org/efrbroo/F9_Place
http://erlangen-crm.org/current/E53_Place
E52
| 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:E52_Time-Span | ||
| current:P4i_is_time-span_of | Membre de CIDOC CRM CORE | current:E2_Temporal_Entity |
| current:P79_beginning_is_qualified_by | Scope note: This property qualifies the beginning of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) beginning is qualified by "approximately" | -- |
| current:P80_end_is_qualified_by | Scope note: This property qualifies the end of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) end is qualified by "approximately" | -- |
| current:P81_ongoing_throughout | Membre de CIDOC CRM CORE | -- |
| current:P82_at_some_time_within | Membre de CIDOC CRM CORE | -- |
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of "immobile" objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: "Fish collected at three miles north of the confluence of the Arve and the Rhone"
- Here -> <-
Membre de CIDOC CRM CORE
E53 Place
E53 Lieu
http://erlangen-crm.org/efrbroo/F9_Place
E53
| 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:E53_Place | ||
| current:P157_is_at_rest_relative_to | Scope note: This property associates an instance of E53 Place with the instance of E18 Physical Thing that determines a reference space for this instance of E53 Place by being at rest with respect to this reference space. The relative stability of form of an E18 Physical Thing defines its default reference space. The reference space is not spatially limited to the referred thing. For example, a ship determines a reference space in terms of which other ships in its neighbourhood may be described. Larger constellations of matter, such as continental plates, may comprise many physical features that are at rest with them and define the same reference space. Examples: - The spatial extent of the municipality of Athens in 2014 (E53) is at rest relative to The Royal Observatory in Greenwich (E25) - The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22) | current:E18_Physical_Thing |
| current:P53i_is_former_or_current_location_of | current:E18_Physical_Thing | |
| current:P59i_is_located_on_or_within | current:E18_Physical_Thing | |
| current:P7i_witnessed | current:E4_Period | |
Membre de CIDOC CRM CORE
Scope note:
This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate.
Examples:
- currency: £26.00
- length: 3.9-4.1 cm
- diameter: 26 mm
- weight: 150 lbs
- density: 0.85 gm/cc
- luminescence: 56 ISO lumens
- tin content: 0.46 %
- taille au garot: 5 hands
- calibrated C14 date: 2460-2720 years, etc
E54 Dimensions
E54 Dimension
E54
| 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:E54_Dimension | ||
| current:P43i_is_dimension_of | Membre de CIDOC CRM CORE | current:E70_Thing |
| current:P90_has_value | Scope note: This property allows an E54 Dimension to be approximated by a value. Examples: - height of silver cup 232 (E54) has value "226" | -- |
| current:P91_has_unit | Scope note: This property shows the type of unit an E54 Dimension was expressed in. Examples: - height of silver cup 232 (E54) has unit mm (E58) | current:E58_Measurement_Unit |
owl:Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E28_Conceptual_Object
Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM's interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54 Dimension]
- portrait, sketch, animation [types of E38 image]
- French, English, German [E56]
- excellent, good, poor [types of E3 Condition State]
- Ford Model T, chop stick [types of E22 Man-Made Object]
- cave, doline, scratch [types of E26 Physical Feature]
- poem, short story [types of E33 Linguistic Object]
- wedding, earthquake, skirmish [types of E5 Event]
Membre de CIDOC CRM CORE
E55 Type
E55 Type
http://erlangen-crm.org/current/E65_Creation
https://w3id.org/bibma/Record_Creation
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/current/E5_Event
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/current/E63_Beginning_of_Existence
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/current/E7_Activity
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/current/E8_Acquisition
http://erlangen-crm.org/current/E84_Information_Carrier
https://w3id.org/bibma/Component
http://erlangen-crm.org/current/E64_End_of_Existence
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Folio
E55
| 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 inherited from current:E28_Conceptual_Object | ||
| current:P94i_was_created_by | Membre de CIDOC CRM CORE | current:E65_Creation |
| Properties from current:E55_Type | ||
| current:P125i_was_type_of_object_used_in | current:E7_Activity | |
| current:P2i_is_type_of | current:E1_CRM_Entity | |
| current:P32i_was_technique_of | current:E7_Activity | |
| current:P42i_was_assigned_by | current:E17_Type_Assignment | |
owl:Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E28_Conceptual_Object | current:E55_Type
Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: "instances of Mandarin Chinese".
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Example:
el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
E56 Language
https://w3id.org/bibma/Title_Assignment
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/E8_Acquisition
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Folio
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/current/E64_End_of_Existence
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F27_Work_Conception
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
https://w3id.org/bibma/Component
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/current/E65_Creation
http://erlangen-crm.org/current/E5_Event
E56
| 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 inherited from current:E28_Conceptual_Object | ||
| current:P94i_was_created_by | Membre de CIDOC CRM CORE | current:E65_Creation |
| Properties inherited from current:E55_Type | ||
| current:P125i_was_type_of_object_used_in | current:E7_Activity | |
| current:P2i_is_type_of | current:E1_CRM_Entity | |
| current:P32i_was_technique_of | current:E7_Activity | |
| current:P42i_was_assigned_by | current:E17_Type_Assignment | |
| Properties from current:E56_Language | ||
| current:P72i_is_language_of | current:E33_Linguistic_Object | |
owl:Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E28_Conceptual_Object | current:E55_Type
Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: "instances of gold".
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin
E57 Material
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
http://erlangen-crm.org/current/E64_End_of_Existence
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Component
https://w3id.org/bibma/Record_Creation
http://erlangen-crm.org/current/E7_Activity
http://erlangen-crm.org/current/E65_Creation
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/current/E5_Event
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
http://erlangen-crm.org/efrbroo/F27_Work_Conception
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Folio
http://erlangen-crm.org/current/E63_Beginning_of_Existence
https://w3id.org/bibma/Written_Area_Production
E57
| 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 inherited from current:E28_Conceptual_Object | ||
| current:P94i_was_created_by | Membre de CIDOC CRM CORE | current:E65_Creation |
| Properties inherited from current:E55_Type | ||
| current:P125i_was_type_of_object_used_in | current:E7_Activity | |
| current:P2i_is_type_of | current:E1_CRM_Entity | |
| current:P32i_was_technique_of | current:E7_Activity | |
| current:P42i_was_assigned_by | current:E17_Type_Assignment | |
| Properties from current:E57_Material | ||
| current:P45i_is_incorporated_in | current:E18_Physical_Thing | |
URI: http://erlangen-crm.org/current/E58_Measurement_Unit
owl:Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E28_Conceptual_Object | current:E55_Type
Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: "instances of cm".
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centrimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
- A [Ampere]
- GRD [Greek Drachme]
- C° [degrees centigrade]
individus dans thésaurus Biblissima
E58 Measurement Unit
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/current/E8_Acquisition
http://erlangen-crm.org/current/E84_Information_Carrier
https://w3id.org/bibma/Component
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/Annotation
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Annotation_Production
http://erlangen-crm.org/current/E7_Activity
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/current/E65_Creation
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/current/E5_Event
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/current/E63_Beginning_of_Existence
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Folio
E58
| 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 inherited from current:E28_Conceptual_Object | ||
| current:P94i_was_created_by | Membre de CIDOC CRM CORE | current:E65_Creation |
| Properties inherited from current:E55_Type | ||
| current:P125i_was_type_of_object_used_in | current:E7_Activity | |
| current:P2i_is_type_of | current:E1_CRM_Entity | |
| current:P32i_was_technique_of | current:E7_Activity | |
| current:P42i_was_assigned_by | current:E17_Type_Assignment | |
| Properties from current:E58_Measurement_Unit | ||
| current:P91i_is_unit_of | current:E54_Dimension | |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period
Membre de CIDOC CRM CORE
Scope note:
This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an 'instantaneous' change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
Examples:
- the birth of Cleopatra (E67)
- the destruction of Lisbon by earthquake in 1755 (E6)
- World War II (E7)
- the Battle of Stalingrad (E7)
- the Yalta Conference (E7)
- my birthday celebration 28-6-1995 (E7)
- the falling of a tile from my roof last Sunday
- the CIDOC Conference 2003 (E7)
E5 Événement
E5 Event
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/current/E90_Symbolic_Object
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F10_Person
http://erlangen-crm.org/efrbroo/F12_Nomen
http://erlangen-crm.org/efrbroo/F15_Complex_Work
http://erlangen-crm.org/current/E73_Information_Object
http://erlangen-crm.org/current/E70_Thing
http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Folio
http://erlangen-crm.org/current/E89_Propositional_Object
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
http://erlangen-crm.org/efrbroo/F13_Identifier
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/efrbroo/F1_Work
http://erlangen-crm.org/current/E72_Legal_Object
http://erlangen-crm.org/current/E82_Actor_Appellation
http://erlangen-crm.org/current/E74_Group
http://erlangen-crm.org/efrbroo/F2_Expression
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/current/F6_Concept
http://erlangen-crm.org/current/E77_Persistent_Item
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Component
http://erlangen-crm.org/current/E71_Man-Made_Thing
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Record
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F24_Publication_Expression
http://erlangen-crm.org/current/E84_Information_Carrier
E5
| 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 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 |
Scope Note: This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
E60 Number
E60
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
E61 Time Primitive
E61
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model.
E62 String
E62
URI: http://erlangen-crm.org/current/E63_Beginning_of_Existence
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Membre de CIDOC CRM CORE
E63 Début d'existence
E63 Beginning of Existence
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/current/F6_Concept
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F15_Complex_Work
http://erlangen-crm.org/current/E73_Information_Object
http://erlangen-crm.org/efrbroo/F13_Identifier
http://erlangen-crm.org/current/E84_Information_Carrier
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F2_Expression
http://erlangen-crm.org/current/E90_Symbolic_Object
http://erlangen-crm.org/current/E82_Actor_Appellation
http://erlangen-crm.org/efrbroo/F24_Publication_Expression
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
http://erlangen-crm.org/current/E72_Legal_Object
https://w3id.org/bibma/Record
http://erlangen-crm.org/current/E77_Persistent_Item
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Folio
http://erlangen-crm.org/efrbroo/F12_Nomen
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
http://erlangen-crm.org/efrbroo/F10_Person
https://w3id.org/bibma/Electronic_Edition
http://erlangen-crm.org/efrbroo/F1_Work
http://erlangen-crm.org/current/E89_Propositional_Object
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Style_of_Script
http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/current/E71_Man-Made_Thing
https://w3id.org/bibma/Component
http://erlangen-crm.org/current/E74_Group
http://erlangen-crm.org/current/E70_Thing
E63
| 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 from current:E63_Beginning_of_Existence | ||
| current:P92_brought_into_existence | Membre de CIDOC CRM CORE | current:E77_Persistent_Item |
URI: http://erlangen-crm.org/current/E64_End_of_Existence
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event
Membre de CIDOC CRM CORE
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
E64 Fin d'existence
E64 End of Existence
http://erlangen-crm.org/current/E89_Propositional_Object
https://w3id.org/bibma/Explicit
http://erlangen-crm.org/current/E71_Man-Made_Thing
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/efrbroo/F12_Nomen
http://erlangen-crm.org/current/E77_Persistent_Item
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F1_Work
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Binding
http://erlangen-crm.org/efrbroo/F13_Identifier
http://erlangen-crm.org/efrbroo/F15_Complex_Work
https://w3id.org/bibma/Record
https://w3id.org/bibma/Folio
http://erlangen-crm.org/current/E74_Group
http://erlangen-crm.org/current/E90_Symbolic_Object
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/current/E72_Legal_Object
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
http://erlangen-crm.org/current/E73_Information_Object
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/current/E82_Actor_Appellation
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/efrbroo/F10_Person
https://w3id.org/bibma/Component
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/efrbroo/F24_Publication_Expression
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/current/F6_Concept
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/current/E70_Thing
http://erlangen-crm.org/efrbroo/F2_Expression
E64
| 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 from current:E64_End_of_Existence | ||
| current:P93_took_out_of_existence | Membre de CIDOC CRM CORE | current:E77_Persistent_Item |
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Membre de CIDOC CRM CORE
E65 Création
E65 Creation
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
http://erlangen-crm.org/efrbroo/F15_Complex_Work
http://erlangen-crm.org/efrbroo/F13_Identifier
http://erlangen-crm.org/current/E72_Legal_Object
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Record
http://erlangen-crm.org/current/E77_Persistent_Item
http://erlangen-crm.org/current/E71_Man-Made_Thing
https://w3id.org/bibma/Component
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/current/F6_Concept
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F12_Nomen
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation
http://erlangen-crm.org/current/E73_Information_Object
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/current/E70_Thing
https://w3id.org/bibma/Electronic_Edition
http://erlangen-crm.org/current/E90_Symbolic_Object
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/efrbroo/F2_Expression
https://w3id.org/bibma/Incipit
http://erlangen-crm.org/current/E89_Propositional_Object
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/current/E74_Group
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
http://erlangen-crm.org/efrbroo/F10_Person
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/current/E82_Actor_Appellation
http://erlangen-crm.org/efrbroo/F1_Work
E65
| 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 from current:E65_Creation | ||
| current:P94_has_created | Membre de CIDOC CRM CORE | current:E28_Conceptual_Object |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item
Membre de CIDOC CRM CORE
Scope note:
This general class comprises discrete, identifiable, instances of E77 Persistent Item t
hat are documented as single units,
Definition of the CIDOC Conceptual Reference Model
180
that either consist of matter or depend on being carried by matter and are characterized by relative stability.
They may be intellectual products or physical things. They may for instance have a solid physical form, an
electronic
encoding, or they may be a logical concept or structure.
Examples:
- my photograph collection (E78 Collection)
- the bottle of milk in my refrigerator (E22)
- the plan of the Strassburger Muenster (E29)
- the thing on the top of Otto Hahn's desk (E19)
- the form of the non-smoking sign (E36)
- the cave of Dirou, Mani, Greece (E27)
E70 Thing
E70 Chose
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
http://erlangen-crm.org/current/E7_Activity
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Component_Production
E70
| 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: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 |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing
Scope note:
This class comprises discrete, identifiable man-made items that are documented as single units.
These items are either intellectual products or man-made physical things, and are characterized by relative stability. They may for instance have a solid physical form, an electronic encoding, or they may be logical concepts or structures.
Examples:
- Beethoven's 5th Symphony (E73)
- Michelangelo's David
- Einstein's Theory of General Relativity (E73)
- the taxon 'Fringilla coelebs Linnaeus, 1758' (E55)
Membre de CIDOC CRM CORE
E71 Chose fabriquée
E71 Man-Made Thing
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Annotation_Production
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/Place_Assignment
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Time-Span_Assignment
E71
| 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: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 |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing
Membre de CIDOC CRM CORE
Scope note:
This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied.
This is true for all E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of the E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CRM.
Examples:
- the Cullinan diamond (E19)
- definition of the CIDOC Conceptual Reference Model Version 2.1 (E73)
E72_Legal_Object
http://erlangen-crm.org/current/E7_Activity
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Annotation_Production
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Scribe_Assignment
E72
| 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 |
URI: http://erlangen-crm.org/current/E73_Information_Object
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object
Membre de CIDOC CRM CORE
Scope note:
This class comprises identifiable immaterial items, such as a poems, jokes, data sets, images, texts, multmedia objects, procedural prescriptions, computer program code, algorithm or mathe
matical formulae, that have an objectively recognizable structure and are documented as single units. The
encoding structure known as a "named graph" also falls under this class, so that each "named graph" is
an instance of an E73 Information Object.
An E73 Information Object does not depend on a specific physical carrier, which can include human
memory, and it can exist on one or more carriers simultaneously.
Instances of E73 Information Object of a linguistic nature should be declared as instances of
the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be
declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not
instances of E73 Information Object, nor are id
eas without a reproducible expression.
Examples:
- image BM000038850.JPG from the Clayton Herbarium in London
- E. A. Poe's "The Raven"
- the movie "The Seven Samurai" by Akira Kurosawa
- the Maxwell Equations
- The Getty AAT as published as Linked Open Data, accessed 1/10/2014
E73 Objet d'information
E73 Information Object
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Component
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Record_Creation
http://erlangen-crm.org/current/E7_Activity
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Title_Assignment
E73
| 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 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 |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E39_Actor
Scope note:
This class comprises any gatherings or organizations of two or more people that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. A joint pseudonym (i.e., a name that seems indicative of an individual but that is actually used as a persona by two or more people) is a particular case of E74 Group.
A gathering of people becomes an E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modelled as membership in an E74 Group (cf. HumanML markup). Married couples and other concepts of family are regarded as particular examples of E74 Group.
Examples:
- the impressionists
- the Navajo
- the Greeks
- the peace protestors in n New York City on February 15 2003
- Exxon-Mobil
- King Solomon and his wives
- the President of the Swiss Confederation
- Nicolas Bourbaki
- Betty Crocker
Membre de CIDOC CRM CORE
E74 Group
E74 Groupe
http://erlangen-crm.org/efrbroo/F27_Work_Conception
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/current/E7_Activity
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Scribe_Assignment
E74
| 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 | |
URI: http://erlangen-crm.org/current/E75_Conceptual_Object_Appellation
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation
Scope note:
This class comprises all appellations specific to intellectual products or standardized patterns.
Examples:
- "ISBN 3-7913-1418-1"
- "ISO 2788-1986 (F)"
E75 Conceptual Object Appellation
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Binding
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Time-Span_Assignment
http://erlangen-crm.org/current/E84_Information_Carrier
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Component
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/current/E7_Activity
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Annotation_Production
E75
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
Scope note:
This class comprises items that have a persistent identity, sometimes known as "endurants" in philosophy.
They can be repeatedly recognized within the duration of their existence by identity criteria rather than by continuity or observation. Persistent Items can be either physical entities, such as people, animals or things, or conceptual entities such as ideas, concepts, products of the imagination or common names.
The criteria that determine the identity of an item are often difficult to establish -; the decision depends largely on the judgement of the observer. For example, a building is regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria. Similarly, inanimate objects may be subject to exchange of parts and matter. The class E77 Persistent Item does not take any position about the nature of the applicable identity criteria and if actual knowledge about identity of an instance of this class exists. There may be cases, where the identity of an E77 Persistent Item is not decidable by a certain state of knowledge.
The main classes of objects that fall outside the scope the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties.
Examples:
- Leonardo da Vinci
- Stonehenge
- the hole in the ozone layer
- the First Law of Thermodynamics
- the Bermuda Triangle
Membre de CIDOC CRM CORE
E77 Persistent Item
E77 Entité persistante
http://erlangen-crm.org/efrbroo/F27_Work_Conception
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
http://erlangen-crm.org/current/E7_Activity
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Time-Span_Assignment
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Title_Assignment
E77
| 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: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 |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event
Scope note:
This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented.
This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door.
Examples:
- the Battle of Stalingrad
- the Yalta Conference
- my birthday celebration 28-6-1995
- the writing of "Faust" by Goethe (E65)
- the formation of the Bauhaus 1919 (E66)
- calling the place identified by TGN '7017998' 'Quyunjig' by the people of Iraq
Membre de CIDOC CRM CORE
E7 Activité
E7 Activity
http://erlangen-crm.org/current/E90_Symbolic_Object
https://w3id.org/bibma/Electronic_Edition
http://erlangen-crm.org/efrbroo/F2_Expression
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/efrbroo/F12_Nomen
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/current/F6_Concept
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Component
http://erlangen-crm.org/efrbroo/F15_Complex_Work
https://w3id.org/bibma/Record
https://w3id.org/bibma/Explicit
http://erlangen-crm.org/efrbroo/F13_Identifier
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
http://erlangen-crm.org/current/E82_Actor_Appellation
http://erlangen-crm.org/efrbroo/F1_Work
http://erlangen-crm.org/efrbroo/F10_Person
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Folio
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/current/E89_Propositional_Object
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F24_Publication_Expression
https://w3id.org/bibma/Dispersed_Manuscript
E7
| 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 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 |
URI: http://erlangen-crm.org/current/E82_Actor_Appellation
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation
Scope note:
This class comprises any sort of name, number, code or symbol characteristically used to identify an E39 Actor.
An E39 Actor will typically have more than one E82 Actor Appellation, and instances of E82 Actor Appellation in turn may have alternative representations. The distinction between corporate and personal names, which is particularly important in library applications, should be made by explicitly linking the E82 Actor Appellation to an instance of either E21 Person or E74 Group/E40 Legal Body. If this is not possible, the distinction can be made through the use of the P2 has type mechanism.
Examples:
- "John Doe"
- "Doe, J"
- "the U.S. Social Security Number 246-14-2304"
- "the Artist Formerly Known as Prince"
- "the Master of the Flemish Madonna"
- "Raphael's Workshop"
- "the Brontë Sisters"
- "ICOM"
- "International Council of Museums"
E82 Actor Appellation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Annotation_Production
http://erlangen-crm.org/current/E8_Acquisition
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Component
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/current/E84_Information_Carrier
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Provenance_Mark
E82
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
| Properties from current:E82_Actor_Appellation | ||
| current:P131i_identifies | current:E39_Actor | |
URI: http://erlangen-crm.org/current/E84_Information_Carrier
owl:Thing | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object
Scope note:
This class comprises all instances of E22 Man-Made Object that are explicitly designed to act as persistent physical
carriers for instances of E73 Information Object.
An E84 Information Carrier may or may not contain information, e.g., a diskette. Note that any E18 Physical Thing may
carry information, such as an E34 Inscription. However, unless it was specifically designed for this purpose, it is not an
Information Carrier. Therefore the property P128 carries (is carried by) applies to E18 Physical Thing in general.
Examples:
- the Rosetta Stone
- my paperpack copy of Crime & Punishment
- the computer disk at ICS-FORTH that stores the canonical Definition of the CIDOC CRM
E84 Information Carrier
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Explicit
http://erlangen-crm.org/current/E90_Symbolic_Object
https://w3id.org/bibma/Record_Creation
http://erlangen-crm.org/efrbroo/F2_Expression
https://w3id.org/bibma/Record
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/current/F6_Concept
http://erlangen-crm.org/efrbroo/F13_Identifier
http://erlangen-crm.org/efrbroo/F27_Work_Conception
http://erlangen-crm.org/efrbroo/F1_Work
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Annotation_Production
http://erlangen-crm.org/efrbroo/F15_Complex_Work
http://erlangen-crm.org/current/E89_Propositional_Object
https://w3id.org/bibma/Time-Span_Assignment
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Style_of_Script
http://erlangen-crm.org/current/E8_Acquisition
http://erlangen-crm.org/efrbroo/F24_Publication_Expression
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F12_Nomen
E84
| 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 |
| Properties from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
URI: http://erlangen-crm.org/current/E89_Propositional_Object
owl:Thing | current:E28_Conceptual_Object | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:F6_Concept
Membre de CIDOC CRM CORE
Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are "about" something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell's Equations
- the ideational contents of Aristotle's book entitled 'Metaphysics' as rendered in the
Greek texts translated in … Oxford edition…
- the underlying prototype of any "no-smoking" sign (E36)
- the common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and
the movie "The Magnificent Seven" by John Sturges
- the image content of the photo of the Allied Leaders at Yalta 1945 (E38)
E89_Propositional_Object
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/current/E8_Acquisition
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Component
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Time-Span_Assignment
E89
| 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: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: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 |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity
Scope note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more other instances of E39 Actor.
The class also applies to the establishment or loss of ownership of instances of E18 Physical Thing. It does not, however, imply changes of any other kinds of right. The recording of the donor and/or recipient is optional. It is possible that in an instance of E8 Acquisition there is either no donor or no recipient. Depending on the circumstances, it may describe:
1. the beginning of ownership
2. the end of ownership
3. the transfer of ownership
4. the acquisition from an unknown source
5. the loss of title due to destruction of the item
It may also describe events where a collector appropriates legal title, for example by annexation or field collection. The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership (E8 Acquisition) and physical custody (E10 Transfer of Custody) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the collection of a hammer-head shark of the genus Sphyrna (Carchariniformes) XXXtbc by John Steinbeck and Edward Ricketts at Puerto Escondido in the Gulf of Mexico on March 25th, 1940
- the acquisition of El Greco's "The Apostles Peter and Paul" by the State Hermitage in Saint Petersburg
- the loss of my stuffed chaffinch 'Fringilla coelebs Linnaeus, 1758' due to insect damage last year
E8 Acquisition
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Record
http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
http://erlangen-crm.org/efrbroo/F13_Identifier
https://w3id.org/bibma/Binding
http://erlangen-crm.org/current/F6_Concept
http://erlangen-crm.org/efrbroo/F10_Person
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Component
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F2_Expression
http://erlangen-crm.org/efrbroo/F12_Nomen
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
https://w3id.org/bibma/Dispersed_Manuscript
http://erlangen-crm.org/efrbroo/F24_Publication_Expression
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/current/E90_Symbolic_Object
https://w3id.org/bibma/Electronic_Edition
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Manuscript
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Incipit
http://erlangen-crm.org/efrbroo/F15_Complex_Work
http://erlangen-crm.org/efrbroo/F1_Work
E8
| 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 |
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object
Scope note:
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units. It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
Examples:
- ecognizabl’
- The “no-smoking” sign (E36)
- “BM000038850.JPG” (E75)
- image BM000038850.JPG from the Clayton Herbarium in London (E38)
- The distribution of form, tone and colour found on Leonardo da Vinci’s painting named “Mona Lisa” in daylight (E38)
- The Italian text of Dante’s “Divina Commedia” as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (E33)
Membre de CIDOC CRM CORE
E90 Symbolic Object
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Component
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Owner_Assignment
E90
| 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 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 | |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing
Scope note:
An abstract notion or idea. [FRBRER] Includes fields of knowledge, disciplines, schools of thought, etc. Includes philosophies, religions, political ideologies, etc. Includes theories, processes, techniques, practices, etc. [Definition from the FRAD draft model, unchanged] 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. [Scope note for E28 Conceptual Object in CIDOC CRM version 5.0.1]
Examples:
-Mankind [as a concept]
-Natural history of whales
-Cultural history of Wales
-The appreciation of Victor Hugo’s works in Germany between 1870 and 1914
F6 Concept
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Component_Production
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Component
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Folio_Extent
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Place_Assignment
F6
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E39_Actor
Scope note:
This class comprises real persons who live or are assumed to have lived. Bibliographic identities
or personae assumed by an individual or a group should be modelled as F12 Nomen and connected to the relevant person or group with an instance of F35 Nomen Use Statement, even if
nothing more can be said about this person or group. In a bibliographic context, a name
presented following the conventions usually employed for personal names will be assumed to
correspond to an actual real person (F10 Person), unless evidence is available to indicate that
this is not the case. The fact that a persona may erroneously be classified as an instance of F10
Person does not imply that the concept comprises personae.
Examples:
- Margaret Atwood
- Hans Christian Andersen
- Queen Victoria
F10 Person
https://w3id.org/bibma/Time-Span_Assignment
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Title_Assignment
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Place_Assignment
F10
| 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 | |
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation
Scope note:
This class comprises any sign or arrangements of signs following a specific syntax (sequences of alphanumeric characters, chemical structure symbols, sound symbols, ideograms etc.) that are used or can be used to refer to and identify a specific instance of some class or category within a certain context. The scripts or type sets for the types of symbols used to compose an instance of F12 Nomen have to be explicitly specified. The identity of an instance of F12 Nomen is given by the order of its symbols and their individual role with respect to their scripts, regardless of the semantics of the larger structural components it may be built from. Structural tags occurring in the nomen string are regarded as symbols constituting the nomen. Spelling variants are regarded as different nomina, whereas the use of different fonts (visual representation variants) or different digital encodings do not change the identity.
Examples :
- ‘甫杜’ [the name of a Chinese poet of the 8th century, in simplified Chinese characters]
- ‘Du Fu’ [Pinyin romanised form of the name of a Chinese poet of the 8th century]
- ‘Tu Fu’ [another romanised form of the name of a Chinese poet of the 8th century]
- ‘Thơ Ðô Phủ’ [Vietnamese form of the name of a Chinese poet of the 8th century]
-‘
جامعة صفاقس
’ [Arabic name of the Sfax University (Tunisia), in Arabic script]
- ‘Ğāmi‘at Ṣafāqis’ [Arabic name of the Sfax University (Tunisia), transliterated]
- ‘Université de Sfax’ [French name of the Sfax University (Tunisia)]
- ‘3-[(2S)-1-methylpyrrolidin-2-yl]pyridine’ [the IUPAC systematic name for nicotine]
- ‘Murders in the rue Morgue’ [English title of a textual work] (to put the image of the formula)
- ‘Poe, Edgar Allan, 1809-1849. Murders in the rue Morgue’ (F50) [controlled author/title access
point for a textual work]
- ‘modelling’ [not the activity, just the written signs that represent its English name in British
spelling]
- ‘modeling’ [not the activity, just the written signs that represent its English name in American
spelling]
F12 Nomen
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Component
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Annotation_Production
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Component_Production
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Binding
F12
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
owl:Thing | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E41_Appellation | efrbroo:F12_Nomen
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. [Adapted from the Scope Note of CIDOC CRM E42 Identifier ver. 5.0.1]
Examples:
- ISSN ‘0041-5278’
- ISRC ‘FIFIN8900116’
- Shelfmark ‘Res 8 P 10’
- ‘Guillaume de Machaut (1300?-1377)’ (F50) [a controlled personal name access point that follows the French rules]
- ‘Guillaume, de Machaut, ca. 1300-1377’ (F50) [a controlled personal name access point that follows the AACR rules]
- ‘Rite of spring (Choreographic work: Bausch)’ (F50)
F13_Identifier
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Component
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
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/Time-Span_Assignment
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Binding
F13
| 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 inherited from current:E41_Appellation | ||
| current:P1i_identifies | Membre de CIDOC CRM CORE | current:E1_CRM_Entity |
owl:Thing | current:E28_Conceptual_Object | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:F6_Concept | current:E89_Propositional_Object | efrbroo:F1_Work
Scope note:
This class comprises works that have more than one work as members.
The members of a Complex Work may constitute components of the overall concept or be alternatives to other members of the work. In practice, no clear line can be drawn between parallel and subsequent processes in the evolution of a work. One part may not be finished when another is already revised. An initially monolithic work may be taken up and evolve in pieces. The member relationship of Work is based on the conceptual relationship, and should not be confused with the internal structural parts of an individual expression. The fact that an expression may contain parts from other work(s) does not make the expressed work complex. For instance, an anthology for which only one version exists is not a complex work.
The boundaries of a Complex Work have nothing to do with the value of the intellectual achievement but only with the dominance of a concept. Thus, derivations such as translations are regarded as belonging to the same Complex Work, even though in addition they constitute an Individual Work themselves. In contrast, a Work that significantly takes up and merges concepts of other works so that it is no longer dominated by the initial concept is regarded as a new work. In cataloguing practice, detailed rules are established prescribing which kinds of derivation should be regarded as crossing the boundaries of a complex work. Adaptation and derivation graphs allow the recognition of distinct sub-units, i.e. a complex work contained in a larger complex work.
As a Complex Work can be taken up by any creator who acquires the spirit of its concept, it is never finished in an absolute sense.
Examples:
- Work entitled ‘La Porte de l’Enfer’ by Auguste Rodin
- Work entitled ‘Hamlet’ by William Shakespeare
- Work entitled ‘Der Ring der Nibelungen’ by Richard Wagner
- Work entitled ‘Carceri d’invenzione’ by Giovanni Battista Piranesi
- Work entitled ‘Mass in B minor BWV 232’ by Johann Sebastian Bach
F15_Complex_Work
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F27_Work_Conception
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Component
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Place_Assignment
F15
| 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: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: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 efrbroo:F1_Work | ||
| efrbroo:R16i_was_initiated_by | efrbroo:F27_Work_Conception | |
| efrbroo:R19i_was_realised_through | efrbroo:F28_Expression_Creation | |
| efrbroo:R2_is_derivative_of | Scope note: This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter. The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation etc. Examples: - William Schuman’s orchestration of Charles Ives’s ‘Variations on America’ (F15) R2 is derivative of Charles Ives’s ‘Variations on America’ (F15) R2.1 has type orchestration (E55) - Charles Ives’s musical work entitled ‘Variations on America’ (F15) R2 is derivative of the musical work titled ‘America’ (F15) R2.1 has type variations (E55) - The musical work entitled ‘America’ (F15) R2 is derivative of the musical work entitled ‘God save the King’ (F15) R2.1 has type same tune with different lyrics (E55) | efrbroo:F1_Work |
| efrbroo:R2i_has_derivative | efrbroo:F1_Work | |
| efrbroo:R3_is_realised_in | Scope note: This property associates an instance of F22 Self-Contained Expression with an instance of F1 Work. This property expresses the association that exists between an expression (F22) and the work that this expression conveys. The semantics of the association will be different depending on what specific subtype of F1 Work the work is an instance of. If the work is an instance of F14 Individual Work, the F22 Self-Contained Expression completely conveys the individual work. If the work is an instance of F15 Complex work, the F22 Self-Contained Expression conveys an alternative member of the complex work. Our factual knowledge of how a given work is realised into an expression is often limited and this property makes it possible to express the association between instances of F22 Self-Contained Expression and the work it conveys without using the more developed paths. Examples: - Dante’s work entitled ‘Inferno’ (F15) R3 is realised in the Italian text of Dante’s ‘Inferno’ as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (F22) - Mozart’s work entitled ‘Il dissoluto punito ossia il Don Giovanni’ (F15) R3 is realised in the notated music of the Prague version, as found on manuscript Ms 1548 of the National Library of France (F22) R3.1 has type autograph version (E55) | efrbroo:F22_Self_Contained_Expression |
| Properties from efrbroo:F15_Complex_Work | ||
| efrbroo:R10_has_member | Scope note: This property associates an instance of F15 Complex Work with an instance of F1 Work that forms part of it. The Work becomes complex by the fact that it has other instances of Work as members. Examples: - Dante’s textual work entitled ‘Divina Commedia’ (F15) R10 has member Dante’s textual work entitled ‘Inferno’ (F15) - Dante’s textual work entitled ‘Inferno’ (F15) R10 has member the abstract content of the pseudo-old French text of Émile Littré’s translation entitled ‘L’Enfer mis en vieux langage françois et en vers’ [a 19th century translation of Dante’s ‘Inferno’ into old French] published in Paris in 1879 (F14) - Giovanni Battista Piranesi’s graphic work entitled ‘Carceri’ (F15) R10 has member Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains’ (F15) - Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains’ (F15) R10 has member the abstract content of Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains: 2nd state’ (F14) | efrbroo:F15_Complex_Work |
owl:Thing | current:E28_Conceptual_Object | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:F6_Concept | current:E89_Propositional_Object
Scope note:
This class comprises distinct concepts or combinations of concepts identified in artistic and
intellectual expressions, such as poems, stories or musical compositions. Such concepts may
appear in the course of the coherent evolution of an original idea into one or more expressions
that are dominated by the original idea. A Work may be elaborated by one or more Actors
simultaneously or over time. The substance of Work is ideas. A Work may have members that
are works in their own right.
A Work can be either individual or complex. If it is individual its concept is completely realised
in a single F22 Self-Contained Expression. If it is complex its concept is embedded in an F15
Complex Work. An F15 Complex Work consists of alternative members that are either F15
Complex Works themselves or F14 Individual Works.
A Work is the product of an intellectual process of one or more persons, yet only indirect
evidence about it is at our hands. This can be contextual information such as the existence of an
order for a work, reflections of the creators themselves that are documented somewhere, and
finally the expressions of the work created. As ideas normally take shape during discussion,
elaboration and implementation, it is not reasonable to assume that a work starts with a complete
concept. In some cases, it can be very difficult or impossible to define the whole of the concept
of a work at a particular time. The objective evidence for such a notion can only be based on a
stage of expressions at a given time. In this sense, the sets of ideas that constitute particular selfcontained
expressions may be regarded as a kind of “snap-shot” of a work.
A Work may include the concept of aggregating expressions of other works into a new
expression. For instance, an anthology of poems is regarded as a work in its own right that
makes use of expressions of the individual poems that have been selected and ordered as part of
an intellectual process. This does not make the contents of the aggregated expressions part of
this work, but only parts of the resulting expression.
Examples:
- Abstract content of Giovanni Battista Piranesi’s ‘Carcere XVI: the pier with chains: 1st state’ (F14)
- ‘La Porte de l’Enfer’ by Auguste Rodin conceived between 1880 and 1917 (F15) ‘Hamlet’ by William Shakespeare (F15)
F1 Work
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Component
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Folio
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Dispersed_Manuscript
F1
| 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: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: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 from efrbroo:F1_Work | ||
| efrbroo:R16i_was_initiated_by | efrbroo:F27_Work_Conception | |
| efrbroo:R19i_was_realised_through | efrbroo:F28_Expression_Creation | |
| efrbroo:R2_is_derivative_of | Scope note: This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter. The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation etc. Examples: - William Schuman’s orchestration of Charles Ives’s ‘Variations on America’ (F15) R2 is derivative of Charles Ives’s ‘Variations on America’ (F15) R2.1 has type orchestration (E55) - Charles Ives’s musical work entitled ‘Variations on America’ (F15) R2 is derivative of the musical work titled ‘America’ (F15) R2.1 has type variations (E55) - The musical work entitled ‘America’ (F15) R2 is derivative of the musical work entitled ‘God save the King’ (F15) R2.1 has type same tune with different lyrics (E55) | efrbroo:F1_Work |
| efrbroo:R2i_has_derivative | efrbroo:F1_Work | |
| efrbroo:R3_is_realised_in | Scope note: This property associates an instance of F22 Self-Contained Expression with an instance of F1 Work. This property expresses the association that exists between an expression (F22) and the work that this expression conveys. The semantics of the association will be different depending on what specific subtype of F1 Work the work is an instance of. If the work is an instance of F14 Individual Work, the F22 Self-Contained Expression completely conveys the individual work. If the work is an instance of F15 Complex work, the F22 Self-Contained Expression conveys an alternative member of the complex work. Our factual knowledge of how a given work is realised into an expression is often limited and this property makes it possible to express the association between instances of F22 Self-Contained Expression and the work it conveys without using the more developed paths. Examples: - Dante’s work entitled ‘Inferno’ (F15) R3 is realised in the Italian text of Dante’s ‘Inferno’ as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (F22) - Mozart’s work entitled ‘Il dissoluto punito ossia il Don Giovanni’ (F15) R3 is realised in the notated music of the Prague version, as found on manuscript Ms 1548 of the National Library of France (F22) R3.1 has type autograph version (E55) | efrbroo:F22_Self_Contained_Expression |
URI: http://erlangen-crm.org/efrbroo/F22_Self_Contained_Expression
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | efrbroo:F2_Expression
Scope note:
This class comprises the immaterial realisations of individual works at a particular time that are regarded as a complete whole. The quality of wholeness reflects the intention of its creator that this expression should convey the concept of the work. Such a whole can in turn be part of a larger whole.
Inherent to the notion of work is the completion of recognisable outcomes of the work. These outcomes, i.e. the Self-Contained Expressions, are regarded as the symbolic equivalents of Individual Works, which form the atoms of a complex work. A Self-Contained Expression may contain expressions or parts of expressions from other work, such as citations or items collected in anthologies. Even though they are incorporated in the Self-Contained Expression, they are not regarded as becoming members of the expressed container work by their inclusion in the expression, but are rather regarded as foreign or referred to elements.
F22 Self-Contained Expression can be distinguished from F23 Expression Fragment in that an F23 Expression Fragment was not intended by its creator to make sense by itself. Normally creators would characterise an outcome of a work as finished. In other cases, one could recognise an outcome of a work as complete from the elaboration or logical coherence of its content, or if there is any historical knowledge about the creator deliberately or accidentally never finishing (completing) that particular expression. In all those cases, one would regard an expression as self-contained.
Examples:
- The Italian text of Dante’s ‘Inferno’ as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere
di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4)
- The musical notation of Franz Schubert’s lied known as ‘Ave Maria’
- The musical notation of Franz Schubert’s lieder cycle entitled ‘Seven Songs after Walter Scott’s
- The Lady of the Lake’, of which ‘Ave Maria’ is a distinct part
- The musical notation of Franz Liszt’s piano transcription of Franz Schubert’s lied known as ‘Ave Maria’
F22 Self Contained Expression
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Component
https://w3id.org/bibma/Binding
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Component_Production
F22
| 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 efrbroo:F2_Expression | ||
| efrbroo:R15_has_fragment | Scope note: This property associates the fragment of an expression and the expression of which it is a fragment. Examples: - The ancient Greek text of the four stanzas from an ode by Sappho that were quoted by Pseudo-Longinus in his textual work entitled ‘On the sublime’ (F23) R15 is fragment of the complete ancient Greek text, now irremediably lost, of Sappho’s ode currently identified as Sappho’s poem #2 (F22) - The statement ‘fasc. 111’ (abridgement for ‘fascicle no. 111’) indicating the sequential position of the publication identified by ISBN ‘2-7018-0037-4’ within the series entitled ‘Bibliothèque des Écoles françaises d’Athènes et de Rome’ and identified by ISSN ‘0257-4101’ (F23) R15 is fragment of the overall content of the publication identified by ISBN ‘2-7018-0037-4’ (F24) | efrbroo:F23_Expression_Fragment |
| efrbroo:R17i_was_created_by | efrbroo:F28_Expression_Creation | |
| efrbroo:R5_has_component | Scope note : This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X. It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by R14 incorporates. Examples: - The Italian text of Dante’s textual work entitled ‘Divina Commedia’ (F22) R5 has component the Italian text of Dante’s textual work entitled ‘Inferno’ (F22) - The musical notation of Mozart’s Singspiel entitled ‘Die Zauberflöte’ (F22) R5 has component the musical notation of Mozart’s aria entitled ‘Der Hölle Rache’, also known as ‘The Queen of the Night’s Aria’ (F22) - The visual content of the map entitled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) R5 has component the visual content of the inset entitled ‘Liverpool’, scale 1:200,000, set within the compass of the map titled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) | efrbroo:F22_Self_Contained_Expression |
| Properties from efrbroo:F22_Self_Contained_Expression | ||
| efrbroo:R3i_realises | efrbroo:F1_Work | |
| efrbroo:R5i_is_component_of | efrbroo:F2_Expression | |
URI: http://erlangen-crm.org/efrbroo/F23_Expression_Fragment
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | efrbroo:F2_Expression
Scope note:
This class comprises parts of Expressions and these parts are not Self-Contained Expressions themselves.
The existence of an instance of F23 Expression Fragment can be due to accident, such as loss of
material over time, e.g. the only remaining manuscript of an antique text being partially eaten by
worms, or due to deliberate isolation, such as excerpts taken from a text by the compiler of a
collection of excerpts.
An F23 Expression Fragment is only identified with respect to its occurrence in a known or
assumed whole. The size of an instance of F23 Expression Fragment ranges from more than
99% of an instance of F22 Self-Contained Expression to tiny bits (a few words from a text, one
bar from a musical composition, one detail from a still image, a two-second clip from a movie,
etc.).
Examples:
- The only remnants of Sappho’s poems
- The words ‘Beati pauperes spiritu’ (excerpted from Matthew’s Gospel 5,3 in Latin translation)
F23 Expression Fragment
https://w3id.org/bibma/Illumination_Production
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Component
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Written_Area_Production
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Dispersed_Manuscript
F23
| 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 efrbroo:F2_Expression | ||
| efrbroo:R15_has_fragment | Scope note: This property associates the fragment of an expression and the expression of which it is a fragment. Examples: - The ancient Greek text of the four stanzas from an ode by Sappho that were quoted by Pseudo-Longinus in his textual work entitled ‘On the sublime’ (F23) R15 is fragment of the complete ancient Greek text, now irremediably lost, of Sappho’s ode currently identified as Sappho’s poem #2 (F22) - The statement ‘fasc. 111’ (abridgement for ‘fascicle no. 111’) indicating the sequential position of the publication identified by ISBN ‘2-7018-0037-4’ within the series entitled ‘Bibliothèque des Écoles françaises d’Athènes et de Rome’ and identified by ISSN ‘0257-4101’ (F23) R15 is fragment of the overall content of the publication identified by ISBN ‘2-7018-0037-4’ (F24) | efrbroo:F23_Expression_Fragment |
| efrbroo:R17i_was_created_by | efrbroo:F28_Expression_Creation | |
| efrbroo:R5_has_component | Scope note : This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X. It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by R14 incorporates. Examples: - The Italian text of Dante’s textual work entitled ‘Divina Commedia’ (F22) R5 has component the Italian text of Dante’s textual work entitled ‘Inferno’ (F22) - The musical notation of Mozart’s Singspiel entitled ‘Die Zauberflöte’ (F22) R5 has component the musical notation of Mozart’s aria entitled ‘Der Hölle Rache’, also known as ‘The Queen of the Night’s Aria’ (F22) - The visual content of the map entitled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) R5 has component the visual content of the inset entitled ‘Liverpool’, scale 1:200,000, set within the compass of the map titled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) | efrbroo:F22_Self_Contained_Expression |
URI: http://erlangen-crm.org/efrbroo/F24_Publication_Expression
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | efrbroo:F2_Expression | efrbroo:F22_Self_Contained_Expression
Scope note:
This class comprises complete sets of signs present in publications, reflecting publishers’ final
decisions as to both selection of content and layout of the publications. Frequently the creation
of a Publication Expression includes both adding graphical form and fonts to Expressions
consisting of words alone and selecting illustrations and other content. As such, an instance of
Publication Expression incorporates all Expressions combined for the resulting final form of
rendering, whether visual, audio or tactile. An instance of Publication Expression is one entity
regardless of the number of independent Expressions published within it, as long as it represents
one unit of release. The published third party content can be associated via the property P165
incorporates (is incorporated in).
Examples:
-The text, its layout and the textual and graphic (Saur’s logo on p. [i]) content of front and back
cover, spine (spine title), and p. [i-iv] of the publication entitled ‘Functional Requirements for
Bibliographic Records: final report’, published by K. G. Saur in 1998, identified by ISBN ‘3-598-11382-X’
- The overall content of the book identified by ISBN ‘0-8014-9130-4’: the text of Stephen Crane’s complete poems as edited by Joseph Katz, the numbering system introduced by Joseph Katz in
order to identify each individual poem by Stephen Crane, page numbers, the text of Joseph
Katz’s dedication, preface, acknowledgements, and introduction, the table of contents, the index
of first lines, the statements found on title page, back of title page (including CIP bibliographic
record), cover front, back front, and spine, and the layout of the publication; for one of Stephen
Crane’s longer poems, printed on p. 142-143, a statement reads at bottom of p. 142: ‘[NO
STANZA BREAK]’: obviously, this statement does not belong to the Self-Contained Expression
intended by Stephen Crane, and presumably not to the one intended by editor Joseph Katz either,
but was more probably added by the publishing team, due to characteristics of the layout of the
publication: a cautious reader can easily interpret ‘[NO STANZA BREAK]’ as non-belonging to
the poem itself, but an OCR process would not make the distinction between the text of the
poem and the statement made by the publisher; ‘[NO STANZA BREAK]’ belongs to the
Publication Expression, although it does not belong to the Self-Contained Expression intended
by Stephen Crane and Joseph Katz
- The overall content of the LP sound recording identified by label and label number ‘CBS 34-
61237’: a recorded performance of Terry Riley’s musical work ‘In C’, the text of liner notes by
Paul Williams translated into French by Bernard Weinberg, technical statements such as
‘Stereo,’ publisher’s logo, series logo, title and statement of responsibility on front, back, and
spine of the cover and on the recording itself, duration statement, cover art by G. Joly, overall
layout, etc.; a special, shunting sound was added at the end of side one and beginning of side
two, as Terry Riley’s work is in the form of a continuous musical flow without any interruption
and the technical possibilities of vinyl LPs did not allow the complete performance to be
contained on just one side: that special, shunting sound was not intended in Riley’s score nor in
the performance but was added by the publisher (with or without Riley’s consent, this detail is
not documented), and as such it is part of the Publication Expression although it is not part of the
composer’s and the performers’ Self-Contained Expression (this shunting sound was no longer
needed in subsequent releases on CD)
- The overall content of the DVD entitled ‘The Aviator (2-Disc Full Screen Edition)’, released in
2004: Martin Scorsese’s movie itself; layout of the box and the two DVDs contained in the box;
pictures on the DVDs themselves; English, Spanish, and French subtitles; English and French
audio tracks; and bonuses: commentaries by director Martin Scorsese, editor Thelma
Schoonmaker, and producer Michael Mann; a deleted scene (‘Howard Tells Ava About His Car
Accident’); and featurettes ‘A Life Without Limits: The Making of The Aviator’; ‘The Role of
Howard Hughes in Aviation History’; ‘Modern Marvels: Howard Hughes, A Documentary by
the History Channel’; ‘The Visual Effects of The Aviator’; ‘The Affliction of Howard Hughes:
Obsessive Compulsive Disorder’; ‘The Age of Glamour: The Hair And Makeup of The Aviator’;
‘Costuming The Aviator: The Work of Sandy Powell’; ‘Constructing The Aviator: The Work of
Dante Ferretti’; ‘An evening with Leonardo DiCaprio and Alan Alda’; ‘OCD Panel Discussion
With Leonardo DiCaprio, Martin Scorsese, and Howard Hughes’ Widow Terry Moore’; ‘Still
Gallery’; ‘Scoring The Aviator: The Work Of Howard Shore’; and ‘The Wainwright Family –
Loudon, Rufus and Martha’
F24 Publication Expression
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Scribe_Assignment
http://erlangen-crm.org/efrbroo/F28_Expression_Creation
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Illumination
http://erlangen-crm.org/efrbroo/F27_Work_Conception
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Component
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Place_Assignment
F24
| 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 efrbroo:F2_Expression | ||
| efrbroo:R15_has_fragment | Scope note: This property associates the fragment of an expression and the expression of which it is a fragment. Examples: - The ancient Greek text of the four stanzas from an ode by Sappho that were quoted by Pseudo-Longinus in his textual work entitled ‘On the sublime’ (F23) R15 is fragment of the complete ancient Greek text, now irremediably lost, of Sappho’s ode currently identified as Sappho’s poem #2 (F22) - The statement ‘fasc. 111’ (abridgement for ‘fascicle no. 111’) indicating the sequential position of the publication identified by ISBN ‘2-7018-0037-4’ within the series entitled ‘Bibliothèque des Écoles françaises d’Athènes et de Rome’ and identified by ISSN ‘0257-4101’ (F23) R15 is fragment of the overall content of the publication identified by ISBN ‘2-7018-0037-4’ (F24) | efrbroo:F23_Expression_Fragment |
| efrbroo:R17i_was_created_by | efrbroo:F28_Expression_Creation | |
| efrbroo:R5_has_component | Scope note : This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X. It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by R14 incorporates. Examples: - The Italian text of Dante’s textual work entitled ‘Divina Commedia’ (F22) R5 has component the Italian text of Dante’s textual work entitled ‘Inferno’ (F22) - The musical notation of Mozart’s Singspiel entitled ‘Die Zauberflöte’ (F22) R5 has component the musical notation of Mozart’s aria entitled ‘Der Hölle Rache’, also known as ‘The Queen of the Night’s Aria’ (F22) - The visual content of the map entitled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) R5 has component the visual content of the inset entitled ‘Liverpool’, scale 1:200,000, set within the compass of the map titled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) | efrbroo:F22_Self_Contained_Expression |
| Properties inherited from efrbroo:F22_Self_Contained_Expression | ||
| efrbroo:R3i_realises | efrbroo:F1_Work | |
| efrbroo:R5i_is_component_of | efrbroo:F2_Expression | |
| Properties from efrbroo:F24_Publication_Expression | ||
| efrbroo:CLR6i_should_be_carried_by | efrbroo:F3_Manifestation_Product_Type | |
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E65_Creation
Scope note:
This class comprises beginnings of evolutions of works.
An instance of F27 Work Conception marks the initiation of the creation of a work. The work, as an intellectual construction, evolves from this point on, until the last known expression of it. The instance of E39 Actor with which a work is associated through the chain of properties F1 Work R16i was initiated by F27 Work Conception P14 carried out by E39 Actor corresponds to the notion of the “creator” of the work. In the case of commissioned works, it is not the commissioning that is regarded as the work conception, but the acceptance of the commission.
This event does not always correlate with the date assigned in common library practice to the work, which is usually a later event (such as the date of completion of the first clean draft).
In addition, F27 Work Conception can serve to document the circumstances that surrounded the appearance of the original idea for a work, when these are known.
Examples:
- Ludwig van Beethoven’s having the first ideas for his fifth symphony
- Pablo Picasso’s acceptance, in 1930, of Ambroise Vollard’s commission for a set of 100 etchings, now known as the ‘Vollard Suite’
- René Goscinny’s and Albert Uderzo’s first collaborative ideas for the comic book entitled ‘Asterix in Britain’ [comment: Goscinny wrote the script and Uderzo made the drawings; both are regarded as co-creators of that collaborative, at the same level of creative input, and no attempt is made to ascertain whether the ideas for the script preceded the ideas for the drawings, or vice-versa]
- The combination of activities, carried out, among others, by Alfred Hitchcock, that began the process which eventually resulted in the movie entitled ‘Psycho’ coming into being
- Oscar Wilde’s having by May 1897 the initial idea of writing his poem entitled ‘The ballad of the Reading gaol’, inspired by his stay in the Reading prison from November 20, 1895 to May 18, 1897, and the execution of Charles Thomas Woolridge on July 7, 1896
F27 Work Conception
https://w3id.org/bibma/Annotation
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Component
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Record
http://erlangen-crm.org/efrbroo/F2_Expression
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Digital_Surrogate
F27
| 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:E65_Creation | ||
| current:P94_has_created | Membre de CIDOC CRM CORE | current:E28_Conceptual_Object |
| Properties from efrbroo:F27_Work_Conception | ||
| efrbroo:R16_initiated | Scope note: This property associates the first conception of a work and the work itself that ensued from a given initial idea. It is usually not recorded in cataloguing practice as it is only exceptionally documented in real life but is required in this semantic model as it marks the origin of the causality chain that results in a work’s coming into existence. Examples: The creative spark that motivated Richard Wagner, during a stormy sea crossing in July/August 1839, to compose an opera (F27) R16 initiated Richard Wagner’s opera entitled ‘Der fliegende Holländer’ (F15) The creative spark that motivated Oscar Wilde, by May 1897, to write a poem inspired by his stay in the Reading prison in 1895-1897 (F27) R16 initiated Oscar Wilde’s poem entitled ‘The ballad of the Reading gaol’ (F15) | efrbroo:F1_Work |
| base:r70_carried_out_by_as_author | This property describes the participation of an author in creating a text. | current:E39_Actor |
URI: http://erlangen-crm.org/efrbroo/F28_Expression_Creation
owl:Thing | current:E65_Creation | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E11_Modification | current:E12_Production
Scope note:
This class comprises activities that result in instances of F2 Expression coming into
existence. This class characterises the externalisation of an Individual Work.
Although F2 Expression is an abstract entity, a conceptual object, the creation of an expression
inevitably also affects the physical world: when you scribble the first draft of a poem on a sheet
of paper, you produce an instance of F4 Manifestation Singleton; F28 Expression Creation is a subclass of E12 Production because the recording of the expression causes a physical
modification of the carrying E18 Physical Thing. The work becomes manifest by being
expressed on a physical carrier different from the creator’s brain. The spatio-temporal circumstances under which the expression is created are necessarily the same spatio-temporal
circumstances under which the first instance of F4 Manifestation Singleton is produced. The
mechanisms through which oral tradition
(of myths, tales, music, etc.) operates are not further investigated in this model. As far as bibliographic practice is concerned, only those instances of
F2 Expression that are externalised on physical carriers other than both the creator’s brain and
the auditor’s brain are taken into account (for a discussion of the modelling of oral traditions,
see: Nicolas, Yann. ‘Folklore Requirements for Bibliographic Records: oral traditions and
FRBR.’ In: Cataloging & Classification Quarterly (2005). Vol. 39, No. 3-4. P. 179-195).
It is possible to use the P2 has type (is type of) property in order to specify that the creation of a
given expression of a given work played a particular role with regard to the overall bibliographic
history of that work (e.g., that it was the creation of the progenitor expression on which all other
expressions of the same work are based; or that it was the creation of the critical edition that
served as the basis for canonical references to the work).
Examples:
- The creation of the ori
ginal manuscript score of ‘Uwertura tragiczna’ by Andrzej Panufnik in
1942 in Warsaw
- The reconstruction from memory of the manuscript score of ‘Uwertura tragiczna’ by Andrzej
Panufnik in 1945 after the original score was destroyed during the war
- The creation, by Lord Byron, of the English text of his work entitled ‘Manfred’ (P2 has type E55 Type {major original contribution})
- The creation, by Woldemar Starke, of his German translation of Lord Byron’s text entitled ‘Manfred’ (P2 has type E55 Type {translation})
- The recording of the third alternate take of ‘Blue Hawaii’ performed by Elvis Presley in Hollywood, Calif., Radio Recorders, on March 22nd, 1961 [each individual take is a distinct
instance of F2 Expression]
F28 Expression Creation
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Component
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Record
http://erlangen-crm.org/efrbroo/F2_Expression
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Provenance_Mark
F28
| Property | Description | Expected Type |
|---|---|---|
| Properties inherited from current:E65_Creation | ||
| current:P94_has_created | Membre de CIDOC CRM CORE | current:E28_Conceptual_Object |
| 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 inherited 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 |
| Properties from efrbroo:F28_Expression_Creation | ||
| efrbroo:R17_created | Scope note: This property associates the expression that was first externalised during a particular creation event with that particular creation event. Examples: - Richard Wagner’s writing the original manuscript of his opera entitled ‘Der fliegende Holländer’ (F28) R17 created the notational content of the original manuscript of Richard Wagner’s opera entitled ‘Der fliegende Holländer’ (F22) - Oscar Wilde’s writing the original manuscript of his poem entitled ‘The ballad of the Reading gaol’ (F28) R17 created the English text of Oscar Wilde’s poem entitled ‘The ballad of the Reading gaol’ (F22) | efrbroo:F2_Expression |
| efrbroo:R18_created | Scope note: This property associates an instance of F28 Expression Creation with the first physical objects in which the resulting instance of F2 Expression was embodied. Examples: - Emily Dickinson’s creating the text of one of the several extant versions of her poem known as ‘Safe in their alabaster chambers’ (F28) R18 created the manuscript now identified as ‘Massachusetts Cambridge Harvard University Houghton Library bMS Am 1118.3 (203c, 203d)’ (F4) - Emily Dickinson’s creating the text of another one of the several extant versions of her poem known as ‘Safe in their alabaster chambers’ (F28) R18 created the manuscript now identified as ‘Massachusetts Cambridge Harvard University Houghton Library bMS Am 1118.5 (74c)’ (F4) - The recording of the third alternate take of the musical work entitled ‘Blue Hawaii’ performed by Elvis Presley in Hollywood, Calif., Radio Recorders, on March 22nd, 1961 (F28) R18 created the master tape of the 3rd alternate take of the musical work entitled ‘Blue Hawaii’ performed by Elvis Presley in Hollywood, Calif., Radio Recorders, on March 22nd, 1961 (F4) (each individual take is a distinct expression) - The resource (a drawing) held by the New York Public Library and identified by call number ‘*MGZGB Far P Cop 1’ (F4) R18i was created by the creation, by the artist named ‘Peter Farmer’, of a costume design for the character named ‘War’ in the Act III Masque of the seasons, in the Festival Ballet of London production of the choreographic work entitled ‘Coppélia’, with choreography by Jack Carter after Petipa (F28) | efrbroo:F4_Manifestation_Singleton |
| efrbroo:R19_created_a_realisation_of | Scope note: This property associates an instance of F28 Expression Creation with the corresponding instance of F14 Individual Work or an instance of F15 Complex Work of which the corresponding instance of F14 Individual Work is a member. Examples: - Giovanni Battista Piranesi’s creating the image identified as ‘Carcere XVI: the pier with chains: 2nd state’ (F28) R19 created a realisation of the concept of Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains: 2nd state’ (F14) - Recording Glenn Gould’s performance of Johann Sebastian Bach’s musical work entitled ‘Toccata in C minor BWV 911’ on May 15 & 16, 1979, in Toronto, Eaton’s Auditorium (F29) R19 created a realisation of the concept of the recorded performance of Johann Sebastian Bach’s musical work entitled ‘Toccata in C minor BWV 911’ by Glenn Gould on May 15 & 16, 1979, in Toronto, Eaton’s Auditorium (F21) | efrbroo:F15_Complex_Work |
| base:used_as_source | This property describes the relation between a preparatory manuscript and the final manuscript, which is not a complete copy of the original, but rather comprises some excerpts from its source. Ex.: Lyon BM 478 served for preparation of the Augustinian compilation by Florus de Lyon found in Lyon BM 484. Note: To describe the relation between the original and its complete copy, use the property bibma_used_for_copy. | current:E84_Information_Carrier |
| base:used_for_copy | Cette propriété établit la relation entre un manuscrit-source et sa copie fidèle. Ex. : BnF Latin 2419 est une copie complète de BnF Latin 2859. Note : Pour décrire la relation entre un manuscrit préparatoire et le manuscrit final, utiliser la propriété bibma_used_as_source. | current:E84_Information_Carrier |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object
Scope note:
This class comprises the intellectual or artistic realisations of
works in the form of identifiable immaterial objects, such as texts, poems, jokes, musical or choreographic notations, movement
pattern, sound pattern, images, multimedia objects, or any combination of such forms that have
objectively recognisable structures. The substance of F2 Expression is signs.
Expressions cannot exist without a physical carrier, but do not depend on a specific physical
carrier and can exist on one or more carriers simultaneously. Carriers may include human
memory.
Inasmuch as the form of F2 Expression is an inherent characteristic of the F2 Expression, any
change in form (e.g., from alpha-numeric notation to spoken word, a poem created in capitals
and rendered in lower case) is a new F2 Expression. Similarly, changes in the intellectual
conventions or instruments that are employed to express a work (e.g., translation from one
language to another) result in the creation of a new F2 Expression. Thus, if a text is revised or
modified, the resulting F2 Expression is considered to be a new F2 Expression. Minor changes, such as corrections of spelling and punctuation, etc., are normally considered variations within
the same F2 Expression. On a practical level, the degree to which distinctions are made between
variant expressions of a work will depend to some extent on the nature of the F1 Work itself, and
on the anticipated needs of users.
The genre of the work may provide an indication of which features are essential to the
expression. In some cases, aspects of physical form, such as typeface and page layout, are not integral to the intellectual or artistic realisation of the
work as such, and therefore are not distinctive criteria for the respective expressions. For another work, features such as layout may
be essential. For instance, the author or a graphic designer may wrap a poem around an image.
An expression of a work may include expressions of other works within it. For instance, an
anthology of poems is regarded as a work in its own right that makes use of expressions of the
individual poems that have been selected and ordered as part of an intellectual process. This
does not make the contents of the aggregated expressions part of this work, but only parts of the
resulting expression.
If an instance of F2 Expression is of a specific form, such as text, image, etc., it may be
simultaneously instantiated in the specific classes representing these forms in CIDOC CRM.
Thereby one can make use of the more specific properties of these classes, such as language
(which is applicable to instances of E33 Linguistic Object only).
Examples:
- The Italian text of Dante’s ‘Divina Commedia’ as found in the authoritative critical edition ‘La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi’
, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (F22 and E33)
- The Italian text of Dante’s ‘Inferno’ as found in the same edition (F22 and E33) ‘Nel mezzo del cammin di nostra vita
mi ritrovai per una selva oscura ché la diritta via era smarrita’ [the Italian text of the first stanza of Dante’s ‘Inferno’ and ‘Divina
Commedia’] (F23 and E33)
- The signs which make up Christian Morgenstern’s ‘Fisches Nachtgesang’ [a poem consisting simply of ‘—’ and ‘ ̆’ signs, arranged in a determined combination] (F22)
F2 Expression
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Component
https://w3id.org/bibma/Owner_Assignment
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Digital_Surrogate
http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Illumination
F2
| 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 efrbroo:F2_Expression | ||
| efrbroo:R15_has_fragment | Scope note: This property associates the fragment of an expression and the expression of which it is a fragment. Examples: - The ancient Greek text of the four stanzas from an ode by Sappho that were quoted by Pseudo-Longinus in his textual work entitled ‘On the sublime’ (F23) R15 is fragment of the complete ancient Greek text, now irremediably lost, of Sappho’s ode currently identified as Sappho’s poem #2 (F22) - The statement ‘fasc. 111’ (abridgement for ‘fascicle no. 111’) indicating the sequential position of the publication identified by ISBN ‘2-7018-0037-4’ within the series entitled ‘Bibliothèque des Écoles françaises d’Athènes et de Rome’ and identified by ISSN ‘0257-4101’ (F23) R15 is fragment of the overall content of the publication identified by ISBN ‘2-7018-0037-4’ (F24) | efrbroo:F23_Expression_Fragment |
| efrbroo:R17i_was_created_by | efrbroo:F28_Expression_Creation | |
| efrbroo:R5_has_component | Scope note : This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X. It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by R14 incorporates. Examples: - The Italian text of Dante’s textual work entitled ‘Divina Commedia’ (F22) R5 has component the Italian text of Dante’s textual work entitled ‘Inferno’ (F22) - The musical notation of Mozart’s Singspiel entitled ‘Die Zauberflöte’ (F22) R5 has component the musical notation of Mozart’s aria entitled ‘Der Hölle Rache’, also known as ‘The Queen of the Night’s Aria’ (F22) - The visual content of the map entitled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) R5 has component the visual content of the inset entitled ‘Liverpool’, scale 1:200,000, set within the compass of the map titled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) | efrbroo:F22_Self_Contained_Expression |
URI: http://erlangen-crm.org/efrbroo/F33_Reproduction_Event
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E11_Modification | current:E12_Production
Scope note:
This class comprises activities that consist in making copies, more or less mechanically, of an instance of E84 Information Carrier (such as an F5 Item or an F4 Manifestation Singleton which is also instance of E84 Information Carrier), preserving the expression carried by it. A Reproduction Event results in new instances of E84 Information Carrier coming into existence. In general, the copy will have different attributes from the original and they are therefore not regarded as siblings.
This class makes it possible to account for the legal distinction between private copying for the purpose of “fair use,” and mass production for the purpose of dissemination.
It can prove difficult to determine where to draw the line between F33 Reproduction Event and F32 Carrier Production Event in cases where multiple copies are produced. In this case, the copies, but not the original, may be regarded as instances of F5 Item. It is the existence of an explicit production plan that makes the difference. As a consequence, F33 Reproduction Event and F32 Carrier Production Event are not declared as disjoint, which makes it possible to account for such situations that could be regarded as instances of both Production Event and Reproduction Event.
Examples:
- My photocopying now for my own private use an exemplar of the article entitled ‘Federal Court’s Ruling Against Photocopying Chain Will Not Destroy “Fair Use”’ by Kenneth D. Crews, issued in ‘Chronicle of higher education’, 17 April 1991, A48
- The BnF’s producing in 1997 the microfilm identified by call number ‘Microfilm M-12169’ of the exemplar identified by shelf mark ‘Res 8 P 10’ of Amerigo Vespucci’s ‘Mundus novus’ published in Paris ca. 1503-1504
- The BnF’s reproducing in 2001 the exemplar identified by call number ‘NC His Master’s Voice HC 20’ of a 78 rpm phonogram released by Gramophone in 1932, as part of the CD identified by call number ‘SDCR 2120’
- The BnF’s making in 2003 a digitisation, identified by call number ‘IFN 7701015’, of the collection of drawings (held by the BnF) that were made by Étienne-Louis Boullée in 1784 for his project of a ‘Newton Cenotaph’
F33 Reproduction Event
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Electronic_Edition
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Record
http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Component
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Digital_Surrogate
F33
| 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 inherited 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 |
| Properties from efrbroo:F33_Reproduction_Event | ||
| efrbroo:R29_reproduced | Scope note: This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it reproduces. Examples: - Making a photocopy of an exemplar of Eran Guter’s dissertation entitled ‘Where languages end: Ludwig Wittgenstein at the crossroads of music, language, and the world’ (F33) R29 reproduced one of the original exemplars of Eran Guter’s dissertation (E84) | current:E84_Information_Carrier |
| efrbroo:R30_produced | Scope note: This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it produces. Examples: - Making a photocopy of an exemplar of Eran Guter’s dissertation entitled ‘Where languages end: Ludwig Wittgenstein at the crossroads of music, language, and the world’ (F33) R30 produced the New York Public Library holding identified by call number ‘JMD 04-1060’ (E84) | current:E84_Information_Carrier |
URI: http://erlangen-crm.org/efrbroo/F3_Manifestation_Product_Type
owl:Thing | current:E72_Legal_Object | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E28_Conceptual_Object | current:E55_Type
Scope note:
This class comprises the definitions of publication products.
An instance of F3 Manifestation Product Type is the “species”, and all copies of a given object
are “specimens” of it. An instance of F3 Manifestation Product Type defines all of the features
or traits that instances of F5 Item normally display in order that they may be recognised as
copies of a particular publication. However, due to production problems or subsequent events,
one or more instances of F5 Item may not exhibit all these features or traits; yet such instances
still retain their relationship to the same instance of F3 Manifestation Product Type.
The features that characterise a given instance of F3 Manifestation Product Type include: one
instance of F24 Publication Expression, containing one or more than one instance of F2
Expression, reflecting the authors’ content of the manifestation and all additional input by the
publisher; and the appropriate types of physical features for that form of the object. For
example, hardcover and paperback are two distinct publications (i.e. two distinct instances of F3
Manifestation Product Type) even though authorial and editorial content are otherwise identical
in both publications. The activity of cataloguing aims at the most accurate listing of features or
traits of an instance of F3 Manifestation Product Type that are sufficient to distinguish it from
another instance of F3 Manifestation Product Type.
Examples:
-The publication product containing the text entitled ‘Harmonie universelle’ (authored by the
person named ‘Marin Mersenne’), issued in 1636 in Paris by the publisher named ‘Sébastien
Cramoisy’
-The publication product containing a modern reprint of Marin Mersenne’s ‘Harmonie
universelle’, issued in 1986 in Paris by the publisher named ‘Les éditions du CNRS’, and
identified by ISBN ‘2-222-00835-2’
-The publication product containing the third edition of the combination of texts and graphics
titled ‘Codex Manesse: die Miniaturen der großen Heidelberger Liederhandschrift,
herausgegeben und erläutert von Ingo F. Walther unter Mitarbeit von Gisela Siebert’, issued by
the publisher named ‘Insel-Verlag’ in 1988
-The publication product containing the cartographic resource titled ‘Ordnance Survey Explorer
Map 213, Aberystwyth & Cwm Rheidol’, issued in May 2005 by the publisher named
‘Ordnance Survey’ and identified by ISBN ‘0-319-23640-4’ (folded), 1:25,000 scale
-The publication product containing the recordings of musical works performed by the person
named ‘Florence Foster Jenkins’ gathered under the title ‘The Glory (????) of the human voice’,
identified by label and label number ‘RCA Victor Gold Seal GD61175’ (Note: the four question
marks within parentheses belong to the title itself)
F3 Manifestation Product Type
https://w3id.org/bibma/Provenance_Mark
http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Component
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Annotation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Illumination
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
| 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 inherited from current:E28_Conceptual_Object | ||
| current:P94i_was_created_by | Membre de CIDOC CRM CORE | current:E65_Creation |
| Properties inherited from current:E55_Type | ||
| current:P125i_was_type_of_object_used_in | current:E7_Activity | |
| current:P2i_is_type_of | current:E1_CRM_Entity | |
| current:P32i_was_technique_of | current:E7_Activity | |
| current:P42i_was_assigned_by | current:E17_Type_Assignment | |
| Properties from efrbroo:F3_Manifestation_Product_Type | ||
| efrbroo:CLR6_should_carry | Scope note: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F24 Publication Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item R6 carries F24 Publication Expression. It can happen that a given exemplar, or a subset of exemplars, originally produced, or intended to be produced with that characteristic, accidentally lacks part of the publication expression. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type. Examples: The publication, dated 1972, entitled ‘The complete poems of Stephen Crane, edited with an introduction by Joseph Katz’ (ISBN ‘0-8014-9130-4’) (F3) CLR6 should carry the overall content of the book identified by ISBN ‘0-8014-9130-4’, i.e.: the text of Stephen Crane’s complete poems as edited by Joseph Katz, the numbering system introduced by Joseph Katz in order to identify each individual poem by Stephen Crane, page numbers, the text of Joseph Katz’s dedication, preface, acknowledgements, and introduction, the table of contents, the index of first lines, the statements found on title page, back of title page (including CIP bibliographic record), cover front, back front, and spine, and the layout of the publication, and the occasional statement ‘[NO STANZA BREAK]’ (F24) | efrbroo:F24_Publication_Expression |
URI: http://erlangen-crm.org/efrbroo/F4_Manifestation_Singleton
owl:Thing | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing
Scope note:
This class comprises physical objects that each carry an instance of F2 Expression, and that were
produced as unique objects, with no siblings intended in the course of their production. It should
be noted that if all but one copy of a given publication are destroyed, then that copy does not
become an instance of F4 Manifestation Singleton, because it was produced together with
sibling copies, even though it now happens to be unique. Examples of instances of F4 Manifestation Singleton include manuscripts, preparatory sketches and the final clean draft sent
by an author or a composer to a publisher.
Examples:
- The manuscript known as ‘The Book of Kells’
- The manuscript score of Charles Racquet’s ‘Organ fantasy’, included in Marin Mersenne’s
personal copy of his own ‘Harmonie universelle’ [Marin Mersenne planned a second edition of his ‘Harmonie universelle’ after it had been first published in 1636, and he asked the composer
Charles Racquet to compose his organ fantasy especially for that planned second edition; but
Mersenne died before he could finish and publish the second edition and Racquet’s score
remained until the 20th century as a manuscript addition to Mersenne’s copy, held in Paris by the
Library of the Conservatoire national des arts et métiers]
- Marin Mersenne’s personal copy, held in Paris by the Library of the Conservatoire national des
arts et métiers, of his own ‘Harmonie universelle’, containing all of his manuscript additions for
a planned second edition that never took place before his death, but that served as a basis for the modern reprint published in 1986
F4 Manifestation Singleton
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Record
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Written_Area_Production
F4
| 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 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 |
| Properties from efrbroo:F4_Manifestation_Singleton | ||
| efrbroo:R18i_was_created_by | efrbroo:F28_Expression_Creation | |
Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense
of physics: independent from temporal phenomena and matter. The instances of E53 Place are
usually determined by reference to the position of immobile objects such as buildings, cities,
mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a
frame of reference and a location with respect to this frame. It may be identified by one or more
instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or
absolute reference systems. However, relative references are often more relevant in the context
of cultural documentation and tend to be more precise. In particular, we are often interested in
position in relation to large, mobile objects, such as ships. For example, the Place at which
Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the
vessel and the precise time of death, either of which may be revised, and the result would lack
historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees
the notion of a section of an E19 Physical Object as a valid E53 Place determination.
[Scope Note for E53 Place in CIDOC CRM version 5.0.1]
Note that Places may be determined by the location of
historical or contemporary objects, geographic features, events or geo-political units.
Examples:
- The area referred to as ‘Lutèce’
- The area referred to as ‘verso of the title page of the Library of Congress’s copy of the 1st edition of the novel entitled ‘Da Vinci Code’
F9 Place
F9
| 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 | |
owl:Thing | current:E26_Physical_Feature | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E25_Man-Made_Feature
Explication d'un mot ou d'un passage du texte, adjointe à ce texte et destinée à être transmise avec lui (Codicologia).
A word or words commenting on, elucidating, or translating those of the main text, often written in the margins or between the lines (British Library).
bibma Annotation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Record
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Annotation_Production
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Scribe_Assignment
| 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 |
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E11_Modification | current:E12_Production | base:Component_Production
Creation of a note (explanatory, critical etc.) in a manuscript.
Création d’une note (explicative, critique etc) dans un manuscrit.
bibma Annotation Production
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Binding
https://w3id.org/bibma/Record
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Component
| 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 inherited 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 |
| Properties from base:Annotation_Production | ||
| base:r40_carried_out_by_as_annotator | Cette propriété désigne la participation d’un annotateur à la création de notes dans un manuscrit. | current:E39_Actor |
owl:Thing | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object | current:E84_Information_Carrier | base:Component
Couverture d’un manuscrit ou d’un imprimé.
The covering of a manuscript or a printed book.
bibma Binding
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Record
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Component_Production
| 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 |
| Properties inherited from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
owl:Thing | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object | current:E84_Information_Carrier
Composant matériel d’un manuscrit.
Ex.: Un composant codicologique, comme une reliure, ou un composant qui correspond à une unité textuelle /artistique, comme une œuvre littéraire.
A physical component of a manuscript or a printed book.
Ex.: A codicological unit such as a binding, or a component matching a textual or artistic unit such as a literary work.
bibma Component
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Record
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Component_Production
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Time-Span_Assignment
| 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 |
| Properties inherited from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E11_Modification | current:E12_Production
Production of a physical component of a manuscript or a printed book.
Production d’un composant matériel du manuscrit ou de l’imprimé.
bibma Component Production
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Digital_Surrogate
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Dispersed_Manuscript
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Record
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Folio
| 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 inherited 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 |
owl:Thing | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object | current:E84_Information_Carrier
The digital copy of a manuscript or a printed book.
Reproduction numérique d’un manuscrit ou d’un imprimé.
bibma Digital Surrogate
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Record
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Style_of_Script
| 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 |
| Properties inherited from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
owl:Thing | efrbroo:F4_Manifestation_Singleton | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object | current:E84_Information_Carrier | base:Manuscript
Manuscrit autrefois complet dont les parties sont aujourd'hui séparées, souvent dispersées entre plusieurs lieux de conservation.
A previously complete, now dispersed manuscript, parts of which may be stored in several libraries.
bibma Dispersed Manuscript
https://w3id.org/bibma/Electronic_Edition
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Explicit
https://w3id.org/bibma/Record
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Title_Assignment
| Property | Description | Expected Type |
|---|---|---|
| Properties inherited from efrbroo:F4_Manifestation_Singleton | ||
| efrbroo:R18i_was_created_by | efrbroo:F28_Expression_Creation | |
| 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 |
| Properties inherited from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object
Édition électronique d’un texte.
An electronic edition of a text.
bibma Electronic Edition
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Owner_Assignment
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
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Time-Span_Assignment
| 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 |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E33_Linguistic_Object
Final words of a text.
Derniers mots d'un texte (Codicologia).
bibma Explicit
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Folio_Extent
https://w3id.org/bibma/Folio
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Illumination
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Illumination_Production
| 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 |
owl:Thing | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object | current:E84_Information_Carrier | base:Component
A leaf of a manuscript.
Feuillet dans un manuscrit.
bibma Folio
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Record
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Incipit
| 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 |
| Properties inherited from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
owl:Thing | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object | current:E84_Information_Carrier | base:Component
Groupe de feuillets dans un manuscrit auxquels on reconnaît une caractéristique commune.
A group of folios in a manuscript characterised by a common feature.
bibma Folio Extent
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Record
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Illumination_Production
https://w3id.org/bibma/Scribe_Assignment
| 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 |
| Properties inherited from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
owl:Thing | current:E26_Physical_Feature | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E25_Man-Made_Feature
A hand-painted image (drawing, illumination) in a manuscript.
Image (dessin, enluminure) exécutée à la main dans un manuscrit.
bibma Illumination
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Record
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Illumination_Production
| 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 |
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E11_Modification | current:E12_Production | base:Component_Production
Production of a hand-painted image in a manuscript.
Production d’une image exécutée à la main dans un manuscrit.
bibma Illumination Production
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Record
https://w3id.org/bibma/Incipit
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Written_Area
| 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 inherited 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 |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E33_Linguistic_Object
First few words of a text.
Premiers mots d'un texte (Codicologia).
bibma Incipit
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Manuscript
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Owner_Assignment
| 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 |
owl:Thing | efrbroo:F4_Manifestation_Singleton | current:E19_Physical_Object | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E22_Man-Made_Object | current:E84_Information_Carrier
A medieval or Renaissance hand-written book.
Livre écrit à la main de l’époque médiévale ou de la Renaissance.
bibma Manuscript
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Place_Assignment
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Owner_Assignment
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Record
| Property | Description | Expected Type |
|---|---|---|
| Properties inherited from efrbroo:F4_Manifestation_Singleton | ||
| efrbroo:R18i_was_created_by | efrbroo:F28_Expression_Creation | |
| 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 |
| Properties inherited from current:E84_Information_Carrier | ||
| efrbroo:R29i_was_reproduced_by | efrbroo:F33_Reproduction_Event | |
| efrbroo:R30i_was_produced_by | efrbroo:F33_Reproduction_Event | |
| base:was_used_as_source | efrbroo:F28_Expression_Creation | |
| base:was_used_for_copy | efrbroo:F28_Expression_Creation | |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E13_Attribute_Assignment
Identification of a previous owner of the manuscript made by a scholar, a librarian, or another person of authority.
Attribution d’un ancien possesseur au manuscrit par un chercheur, un conservateur de bibliothèque ou une autre personne d’autorité.
bibma Owner Assignment
https://w3id.org/bibma/Record
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Written_Area
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E13_Attribute_Assignment
Attribution d’un lieu (éventuellement d’origine d’un manuscrit) par un chercheur, un conservateur de bibliothèque ou une autre personne d’autorité.
Identification of a place (possibly of origin of a manuscript) made by a scholar, a librarian, or another person of authority.
bibma Place Assignment
https://w3id.org/bibma/Provenance_Mark
https://w3id.org/bibma/Record
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Style_of_Script
| 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 |
owl:Thing | current:E26_Physical_Feature | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E25_Man-Made_Feature
Marque de provenance (ex-dono, ex-libris).
A provenance mark (ex dono, ex libris).
bibma Provenance Mark
https://w3id.org/bibma/Record
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Style_of_Script
| 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 |
owl:Thing | current:E89_Propositional_Object | current:E28_Conceptual_Object | current:E71_Man-Made_Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E72_Legal_Object | current:E90_Symbolic_Object | current:E73_Information_Object | current:E31_Document
Notice bibliographique d’un catalogue.
A bibliographic record in a catalogue.
bibma Record
https://w3id.org/bibma/Record_Creation
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Scribe_Assignment
https://w3id.org/bibma/Time-Span_Assignment
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity
Création d’une notice bibliographique dans un catalogue.
Creation of a bibliographic record in a catalogue.
bibma Record Creation
https://w3id.org/bibma/Written_Area
https://w3id.org/bibma/Style_of_Script
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E13_Attribute_Assignment
Identification of a scribe in a manuscript (or its part) made by a scholar, a librarian, or another person of authority.
Attribution d'un manuscrit (ou de sa partie) à un copiste par un chercheur, un conservateur de bibliothèque ou une autre personne d’autorité.
bibma Scribe Assignment
https://w3id.org/bibma/Style_of_Script
https://w3id.org/bibma/Written_Area
| 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 |
owl:Thing | current:F6_Concept | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E28_Conceptual_Object | current:E55_Type
Type d’écriture médiévale.
A type of medieval script.
bibma Style of Script
https://w3id.org/bibma/Written_Area_Production
https://w3id.org/bibma/Time-Span_Assignment
https://w3id.org/bibma/Title_Assignment
https://w3id.org/bibma/Written_Area
| 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 inherited from current:E28_Conceptual_Object | ||
| current:P94i_was_created_by | Membre de CIDOC CRM CORE | current:E65_Creation |
| Properties inherited from current:E55_Type | ||
| current:P125i_was_type_of_object_used_in | current:E7_Activity | |
| current:P2i_is_type_of | current:E1_CRM_Entity | |
| current:P32i_was_technique_of | current:E7_Activity | |
| current:P42i_was_assigned_by | current:E17_Type_Assignment | |
| Properties from base:Style_of_Script | ||
| base:style_of_script_was_used | current:E12_Production | |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E13_Attribute_Assignment
Attribution d’une date (éventuellement de production d’un manuscrit) par un chercheur ou un conservateur de bibliothèque ou une autre personne d’autorité.
Identification of a date (possibly of a manuscript’s production) made by a scholar, a librarian, or another person of authority.
bibma Time-Span Assignment
https://w3id.org/bibma/Written_Area
| 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 |
owl:Thing | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E13_Attribute_Assignment
An act of ascribing a title by a scholar, a librarian, or another person of authority.
Attribution d’un titre par un chercheur ou un conservateur de bibliothèque ou une autre personne d’autorité.
bibma Title Assignment
https://w3id.org/bibma/Written_Area
| 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 |
owl:Thing | current:E26_Physical_Feature | current:E72_Legal_Object | current:E18_Physical_Thing | current:E1_CRM_Entity | current:E77_Persistent_Item | current:E70_Thing | current:E71_Man-Made_Thing | current:E24_Physical_Man-Made_Thing | current:E25_Man-Made_Feature
Zone d’écriture d’un manuscrit.
A handwritten area of a manuscript.
bibma Written Area
https://w3id.org/bibma/Written_Area_Production
| 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 |
owl:Thing | current:E63_Beginning_of_Existence | current:E1_CRM_Entity | current:E2_Temporal_Entity | current:E4_Period | current:E5_Event | current:E7_Activity | current:E11_Modification | current:E12_Production | base:Component_Production
Production d’une zone d’écriture du manuscrit.
Production of a handwritten area of a manuscript.
bibma Written Area Production
| 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 inherited 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 |
| Properties from base:Written_Area_Production | ||
| base:r0270_carried_out_by_as_scribe | Cette propriété désigne la participation d’un scribe à l’écriture d’un manuscrit ou de sa partie. | current:E39_Actor |
| current:P106_is_composed_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P106i_forms_part_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P10_falls_within | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P10i_contains | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P125_used_object_of_type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P125i_was_type_of_object_used_in | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P12_occurred_in_the_presence_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P12i_was_present_at | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P130_shows_features_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P130i_features_are_also_found_on | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P140_assigned_attribute_to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P140i_was_attributed_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P141_assigned | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P141i_was_assigned_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P148_has_component | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P148i_is_component_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P157_is_at_rest_relative_to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P157i_occupied | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P157i_provides_reference_space_for | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P15_was_influenced_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P15i_influenced | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P1_is_identified_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P1i_identifies | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P2_has_type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P2i_is_type_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P31_has_modified | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P31i_was_modified_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P43_has_dimension | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P43i_is_dimension_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P45_consists_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P45i_is_incorporated_in | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P46_is_composed_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P46i_forms_part_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P49_has_former_or_current_keeper | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P49i_is_former_or_current_keeper_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P4_has_time-span | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P4i_is_time-span_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P51_has_current_or_former_owner | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P51i_is_former_or_current_owner_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P53_has_former_or_current_location | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P53i_is_former_or_current_location_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P58_has_section_definition | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P58i_defines_section | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P62_depicts | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P62i_is_depicted_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P67_refers_to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P67i_is_referred_to_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P72_has_language | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P72i_is_language_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P7_took_place_at | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P7i_witnessed | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P91_has_unit | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| current:P91i_is_unit_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:CLR6_should_carry | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:CLR6i_should_be_carried_by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:R10_has_member | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:R10i_is_member_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:R19_created_a_realisation_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:R19i_was_realised_through | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:R5_has_component | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| efrbroo:R5i_is_component_of | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
P102.1 has type
P102.1
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)
P102 has title
P102
P102i is title of
http://erlangen-crm.org/current/P102_has_title
P102i
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)
P106 is composed of
P106 est composé de
http://erlangen-crm.org/current/P106i_forms_part_of
P106
P106i fait partie de
P106i forms part of
P106i
current:P31_has_modified | current:P12_occurred_in_the_presence_of | current:P92_brought_into_existence
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)
P108 has produced
P108 a produit
http://erlangen-crm.org/current/P108i_was_produced_by
P108
URI: http://erlangen-crm.org/current/P108i_was_produced_by
current:P12i_was_present_at | current:P92i_was_brought_into_existence_by | current:P31i_was_modified_by
current:E24_Physical_Man-Made_Thing
P108i was produced by
P108i a été produit par
P108i
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)
P10 s’insère dans le cours de
P10 falls within
P10
P10i contient
P10i contains
http://erlangen-crm.org/current/P10_falls_within
P10i
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)
P11 had participant
P11
URI: http://erlangen-crm.org/current/P11i_participated_in
P11i participated in
http://erlangen-crm.org/current/P11_had_participant
P11i
URI: http://erlangen-crm.org/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)
P125 used object of type
P125
URI: http://erlangen-crm.org/current/P125i_was_type_of_object_used_in
P125i was type of object used in
http://erlangen-crm.org/current/P125_used_object_of_type
P125i
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)
P128 est le support de
P128 carries
http://erlangen-crm.org/current/P128i_is_carried_by
P128
P128i a pour support
P128i is carried by
P128i
URI: http://erlangen-crm.org/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)
Membre de CIDOC CRM CORE
P12 est arrivé en présence de
P12 occurred in the presence of
P12
Membre de CIDOC CRM CORE
P12i was present at
P12i était présent à
http://erlangen-crm.org/current/P12_occurred_in_the_presence_of
P12i
URI: http://erlangen-crm.org/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)
P130 présente des caractéristiques de
P130 shows features of
P130
URI: http://erlangen-crm.org/current/P130i_features_are_also_found_on
P130i features are also found on
P130i a des caractéristiques se trouvant aussi sur
http://erlangen-crm.org/current/P130_shows_features_of
P130i
URI: http://erlangen-crm.org/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)
P131 is identified by
http://erlangen-crm.org/current/P131i_identifies
P131
P131i identifies
P131i
URI: http://erlangen-crm.org/current/P140_assigned_attribute_to
Membre de CIDOC CRM CORE
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)
P140 assigned attribute to
P140 a affecté un attribut à
P140
URI: http://erlangen-crm.org/current/P140i_was_attributed_by
Membre de CIDOC CRM CORE
P140i a reçu un attribut par
P140i was attributed by
http://erlangen-crm.org/current/P140_assigned_attribute_to
P140i
Membre de CIDOC CRM CORE
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
P141 assigned
P141 a attribué
P141
URI: http://erlangen-crm.org/current/P141i_was_assigned_by
Membre de CIDOC CRM CORE
P141i a été attribué par
P141i was assigned by
http://erlangen-crm.org/current/P141_assigned
P141i
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)
Membre de CIDOC CRM CORE
P148 has component
P148
URI: http://erlangen-crm.org/current/P148i_is_component_of
Membre de CIDOC CRM CORE
P148i is component of
http://erlangen-crm.org/current/P148_has_component
P148i
current:P12_occurred_in_the_presence_of | current:P11_had_participant
Scope note:
This property describes the active participation of an E39 Actor in an E7 Activity.
It implies causal or legal responsibility. The P14.1 in the role of property of the property allows the nature of an Actor's participation to be specified.
Examples:
- the painting of the Sistine Chapel (E7) carried out by Michaelangelo Buonaroti (E21) in the role of master craftsman (E55)
Membre de CIDOC CRM CORE
P14 carried out by
P14 réalisée par
P14
Scope note:
This property describes the active participation of an E39 Actor in an E7 Activity.
It implies causal or legal responsibility. The P14.1 in the role of property of the property allows the nature of an Actor’s participation to be specified.
Membre de CIDOC CRM CORE
P14i performed
P14i a exécuté
http://erlangen-crm.org/current/P14_carried_out_by
P14i
URI: http://erlangen-crm.org/current/P157_is_at_rest_relative_to
Scope note: This property associates an instance of E53 Place with the instance of E18 Physical Thing that determines a reference space for this instance of E53 Place by being at rest with respect to this reference space. The relative stability of form of an E18 Physical Thing defines its default reference space. The reference space is not spatially limited to the referred thing. For example, a ship determines a reference space in terms of which other ships in its neighbourhood may be described. Larger constellations of matter, such as continental plates, may comprise many physical features that are at rest with them and define the same reference space.
Examples:
- The spatial extent of the municipality of Athens in 2014 (E53) is at rest relative to The Royal Observatory in Greenwich (E25)
- The place where Lord Nelson died on H.M.S. Victory (E53) is at rest relative to H.M.S. Victory (E22)
P157 is at rest relative to (provides reference space for)
N4c25be6bda8746a980a103a6d982baa2
N4b2a6a69b16e4bd2bdd0828139d45f3e
http://erlangen-crm.org/current/P157i_provides_reference_space_for
P157
http://erlangen-crm.org/current/P157i_provides_reference_space_for
N62c093a1923f4228a2ac1e1d9b8334dd
http://erlangen-crm.org/current/P157_is_at_rest_relative_to
URI: http://erlangen-crm.org/current/P157i_provides_reference_space_for
P157i provides reference space for
N8634e02e50934134bb3ca71ae4f00df9
P157i
URI: http://erlangen-crm.org/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)
P15 was influenced by
http://erlangen-crm.org/current/P15i_influenced
P15
P15i influenced
P15i
current:P12_occurred_in_the_presence_of | current:P15_was_influenced_by | current:P16_used_specific_object
P16.1 mode of use
P16.1
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)
URI: http://erlangen-crm.org/current/P165i_is_incorporated_in
http://erlangen-crm.org/current/P165_incorporates
URI: http://erlangen-crm.org/current/P16_used_specific_object
current:P12_occurred_in_the_presence_of | current:P15_was_influenced_by
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)
Membre de CIDOC CRM CORE
P16 used specific object
http://erlangen-crm.org/current/P16i_was_used_for
P16
Membre de CIDOC CRM CORE
P16i was used for
P16i
Scope note:
This property describes the naming or identification of any real world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples:
- the capital of Italy (E53) is identified by "Rome" (E48)
- text 25014-32 (E33) is identified by "The Decline and Fall of the Roman Empire" (E35)
Membre de CIDOC CRM CORE
P1 est identifiée par
P1 is identified by
http://erlangen-crm.org/current/P1i_identifies
P1
Membre de CIDOC CRM CORE
P1i identifies
P1i identifie
P1i
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)
P2 has type
P2 est de type
http://erlangen-crm.org/current/P2i_is_type_of
P2
P2i is type of
P2i est le type de
P2i
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)
http://erlangen-crm.org/current/P31i_was_modified_by
URI: http://erlangen-crm.org/current/P31i_was_modified_by
URI: http://erlangen-crm.org/current/P32_used_general_technique
Scope note:
This property identifies the technique or method that was employed in an activity.
These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques such as embroidery, oil-painting, carbon dating, etc. Specific techniques may be further described as instances of E29 Design or Procedure. This property identifies the technique that was employed in an act of modification.
Examples:
- ornamentation of silver cup 113 (E11) used general technique gold-plating (E55) (Design or Procedure Type)
Example : F28_Expression_Creation -> P32_used_general_technique -> bibma_Writing_Direction ; values : right-to-left , left-to-right , bidirectional , top-to-bottom
P32 used general technique
P32
URI: http://erlangen-crm.org/current/P32i_was_technique_of
P32i was technique of
http://erlangen-crm.org/current/P32_used_general_technique
P32i
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)
P42 assigned
P42
URI: http://erlangen-crm.org/current/P42i_was_assigned_by
P42i was assigned by
http://erlangen-crm.org/current/P42_assigned
P42i
Membre de CIDOC CRM CORE
Scope note:
This property records a E54 Dimension of some E70 Thing.
It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.
An instance of E54 Dimension is specific to an instance of E70 Thing.
Examples:
- silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60)
P43 has dimension
P43 a pour dimension
P43
URI: http://erlangen-crm.org/current/P43i_is_dimension_of
Membre de CIDOC CRM CORE
P43i est dimension de
P43i is dimension of
http://erlangen-crm.org/current/P43_has_dimension
P43i
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)
P45 consists of
http://erlangen-crm.org/current/P45i_is_incorporated_in
P45
URI: http://erlangen-crm.org/current/P45i_is_incorporated_in
P45i is incorporated in
P45i
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)
P46 is composed of
P46 est composée de
http://erlangen-crm.org/current/P46i_forms_part_of
P46i fait partie de
P46i forms part of
P46i
URI: http://erlangen-crm.org/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)
P48 has preferred identifier
http://erlangen-crm.org/current/P48i_is_preferred_identifier_of
P48
URI: http://erlangen-crm.org/current/P48i_is_preferred_identifier_of
P48i is preferred identifier of
P48i
URI: http://erlangen-crm.org/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)
P49 has former or current keeper
http://erlangen-crm.org/current/P49i_is_former_or_current_keeper_of
P49
URI: http://erlangen-crm.org/current/P49i_is_former_or_current_keeper_of
P49i is former or current keeper of
P49i
Membre de CIDOC CRM CORE
Scope note:
This property describes the temporal confinement of an instance of an E2 Temporal Entity.
The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active, which make up the temporal entity instance. It does not convey any other meaning than a positioning on the "time-line" of chronology. The Time-Span in turn is approximated by a set of dates (E61 Time Primitive). A temporal entity can have in reality only one Time-Span, but there may exist alternative opinions about it, which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
Examples:
- the Yalta Conference (E7) has time-span Yalta Conference time-span (E52)
P4 a pour durée
P4 has time-span
P4
Membre de CIDOC CRM CORE
P4i est la durée de
P4i is time-span of
http://erlangen-crm.org/current/P4_has_time-span
P4i
URI: http://erlangen-crm.org/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)
P50 has current keeper
http://erlangen-crm.org/current/P50i_is_current_keeper_of
P50
URI: http://erlangen-crm.org/current/P50i_is_current_keeper_of
P50i is current keeper of
P50i
URI: http://erlangen-crm.org/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)
P51 has former or current owner
http://erlangen-crm.org/current/P51i_is_former_or_current_owner_of
P51
URI: http://erlangen-crm.org/current/P51i_is_former_or_current_owner_of
P51i is former or current owner of
P51i
URI: http://erlangen-crm.org/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)
Scope note:
This property allows an instance of E53 Place to be associated as the former or current location of an instance of E18 Physical Thing.
In the case of E19 Physical Objects, the property does not allow any indication of the Time-Span during which the Physical Object was located at this Place, nor if this is the current location.
In the case of immobile objects, the Place would normally correspond to the Place of creation.
has former or current location (is former or current location of) 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) or P27 moved from (was origin of) to E53 Place.
Examples:
- silver cup 232 (E22) has former or current location Display Case 4, Room 23, Museum of Oxford (E53)
P53 has former or current location
URI: http://erlangen-crm.org/current/P53i_is_former_or_current_location_of
P53i is former or current location of
http://erlangen-crm.org/current/P53_has_former_or_current_location
URI: http://erlangen-crm.org/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)
P55 has current location
http://erlangen-crm.org/current/P55i_currently_holds
P55
URI: http://erlangen-crm.org/current/P55i_currently_holds
http://erlangen-crm.org/current/P55_has_current_location
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)
P56 bears feature
http://erlangen-crm.org/current/P56i_is_found_on
P56
P56i is found on
P56i
URI: http://erlangen-crm.org/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)
P58 has section definition
P58
URI: http://erlangen-crm.org/current/P58i_defines_section
P58i defines section
http://erlangen-crm.org/current/P58_has_section_definition
P58i
current:P157i_occupied | current:P157i_provides_reference_space_for
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)
P59 has section
P59
URI: http://erlangen-crm.org/current/P59i_is_located_on_or_within
P59i is located on or within
http://erlangen-crm.org/current/P59_has_section
P59i
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)
P62 depicts
http://erlangen-crm.org/current/P62i_is_depicted_by
P62
P62i is depicted by
P62i
Scope note:
An E73 Information Object may refer to any other E1 CRM Entity.
This property documents that an E89 Propositional Object makes a statement about an instance of an E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the E89 Propositional Object.
Examples:
- the eBay auction listing for 4 July 2002 (E73) refers to silver cup 232 (E22) has type auction listing (E55)
Membre de CICOD CRM CORE
P67 fait référence à
P67 refers to
http://erlangen-crm.org/current/P67i_is_referred_to_by
P67
URI: http://erlangen-crm.org/current/P67i_is_referred_to_by
Membre de CICOD CRM CORE
P67i is referred to by
est référencé par
P67i
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)
P70 documents
http://erlangen-crm.org/current/P70i_is_documented_in
P70
URI: http://erlangen-crm.org/current/P70i_is_documented_in
P70i is documented in
P70i
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)
P72 has language
P72
P72i is language of
http://erlangen-crm.org/current/P72_has_language
P72i
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)
P7 took place at
P7
P7i witnessed
http://erlangen-crm.org/current/P7_took_place_at
P7i
Scope note:
This property shows the type of unit an E54 Dimension was expressed in.
Examples:
- height of silver cup 232 (E54) has unit mm (E58)
P91 has unit
P91
P91i is unit of
http://erlangen-crm.org/current/P91_has_unit
P91i
URI: http://erlangen-crm.org/current/P92_brought_into_existence
Membre de CIDOC CRM CORE
Scope note:
This property allows an E63 Beginning of Existence event to be linked to the E77 Persistent Item brought into existence by it.
It allows a "start" to be attached to any Persistent Item being documented i.e. E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, E51 Contact Point and E55 Type.
Examples:
- the birth of Mozart (E67) brought into existence Mozart (E21)
P92 a fait exister
P92 brought into existence
P92
URI: http://erlangen-crm.org/current/P92i_was_brought_into_existence_by
Membre de CIDOC CRM CORE
P92i was brought into existence by
P92i a commencé à exister du fait de
http://erlangen-crm.org/current/P92_brought_into_existence
P92i
URI: http://erlangen-crm.org/current/P93_took_out_of_existence
Membre de CIDOC CRM CORE
Scope note:
This property allows an E64 End of Existence event to be linked to the E77 Persistent Item taken out of existence by it.
In the case of immaterial things, the E64 End of Existence is considered to take place with the destruction of the last physical carrier.
This allows an "end" to be attached to any Persistent Item being documented i.e. E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, E51 Contact Point and E55 Type. For many Persistent Items we know the maximum life-span and can infer, that they must have ended to exist. We assume in that case an End of Existence, which may be as unnoticeable as forgetting the secret knowledge by the last representative of some indigenous nation.
Examples:
- the death of Mozart (E69) took out of existence Mozart (E21)
P93 took out of existence
P93 a fait cesser d’exister
P93
URI: http://erlangen-crm.org/current/P93i_was_taken_out_of_existence_by
Membre de CIDOC CRM CORE
P93i was taken out of existence by
P93i a cessé d’exister du fait de
http://erlangen-crm.org/current/P93_took_out_of_existence
P93i
current:P12_occurred_in_the_presence_of | current:P92_brought_into_existence
Membre de CIDOC CRM CORE
Scope note:
This property allows a conceptual E65 Creation to be linked to the E28 Conceptual Object created by it.
It represents the act of conceiving the intellectual content of the E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.
Examples:
- the composition of "The Four Friends" by A. A. Milne (E65) has created "The Four Friends" by A. A. Milne (E28)
P94 has created
P94 a créé
P94
current:P12i_was_present_at | current:P92i_was_brought_into_existence_by
Membre de CIDOC CRM CORE
P94i was created by
P94i a été créé par
http://erlangen-crm.org/current/P94_has_created
P94i
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)
P9 consists of
P9
P9i forms part of
http://erlangen-crm.org/current/P9_consists_of
P9i
R15i is fragment of
http://erlangen-crm.org/efrbroo/R15_has_fragment
R15i
Scope note:
This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with
an instance of F24 Publication Expression, which all exemplars of that publication should
carry, as long as they are recognised as complete exemplars of that publication. Typically, this
property is observed on one exemplar of a publication, and extrapolated to all other exemplars
of the same publication. This logical inference is an induction along the path that can be
modelled as: F3 Manifestation Product Type R7i has example F5 Item R6 carries F24
Publication Expression.
It can happen that a given exemplar, or a subset of exemplars, originally produced, or intended
to be produced with that characteristic, accidentally lacks part of the publication expression.
This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product
Type.
Examples:
The publication, dated 1972, entitled ‘The complete poems of Stephen Crane, edited with an
introduction by Joseph Katz’ (ISBN ‘0-8014-9130-4’) (F3) CLR6 should carry the overall
content of the book identified by ISBN ‘0-8014-9130-4’, i.e.: the text of Stephen Crane’s
complete poems as edited by Joseph Katz, the numbering system introduced by Joseph Katz in
order to identify each individual poem by Stephen Crane, page numbers, the text of Joseph
Katz’s dedication, preface, acknowledgements, and introduction, the table of contents, the
index of first lines, the statements found on title page, back of title page (including CIP
bibliographic record), cover front, back front, and spine, and the layout of the publication, and
the occasional statement ‘[NO STANZA BREAK]’ (F24)
CLR6 should carry
CLR6
URI: http://erlangen-crm.org/efrbroo/CLR6i_should_be_carried_by
CLR6i should be carried by
CLR6i
Scope note:
This property associates an instance of F15 Complex Work with an instance of F1 Work that forms part of it. The Work becomes complex by the fact that it has other instances of Work as members.
Examples:
- Dante’s textual work entitled ‘Divina Commedia’ (F15) R10 has member Dante’s textual work entitled ‘Inferno’ (F15)
- Dante’s textual work entitled ‘Inferno’ (F15) R10 has member the abstract content of the pseudo-old French text of Émile Littré’s translation entitled ‘L’Enfer mis en vieux langage françois et en vers’ [a 19th century translation of Dante’s ‘Inferno’ into old French] published in Paris in 1879 (F14)
- Giovanni Battista Piranesi’s graphic work entitled ‘Carceri’ (F15) R10 has member Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains’ (F15)
- Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains’ (F15) R10 has member the abstract content of Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains: 2nd state’ (F14)
R10 has member
http://erlangen-crm.org/efrbroo/R10i_is_member_of
R10
R10i is member of
R10i
Scope note:
This property associates the fragment of an expression and the expression of which it is a fragment.
Examples:
- The ancient Greek text of the four stanzas from an ode by Sappho that were quoted by Pseudo-Longinus in his textual work entitled ‘On the sublime’ (F23) R15 is fragment of the complete ancient Greek text, now irremediably lost, of Sappho’s ode currently identified as Sappho’s poem #2 (F22)
- The statement ‘fasc. 111’ (abridgement for ‘fascicle no. 111’) indicating the sequential position of the publication identified by ISBN ‘2-7018-0037-4’ within the series entitled ‘Bibliothèque des Écoles françaises d’Athènes et de Rome’ and identified by ISSN ‘0257-4101’ (F23) R15 is fragment of the overall content of the publication identified by ISBN ‘2-7018-0037-4’ (F24)
R15 has fragment
R15
current:P12_occurred_in_the_presence_of | current:P92_brought_into_existence | current:P94_has_created
Scope note:
This property associates the first conception of a work and the work itself that ensued from a given initial idea.
It is usually not recorded in cataloguing practice as it is only exceptionally documented in real life but is required in this semantic model as it marks the origin of the causality chain that results in a work’s coming into existence.
Examples: The creative spark that motivated Richard Wagner, during a stormy sea crossing in July/August 1839, to compose an opera (F27) R16 initiated Richard Wagner’s opera entitled ‘Der fliegende Holländer’ (F15)
The creative spark that motivated Oscar Wilde, by May 1897, to write a poem inspired by his stay in the Reading prison in 1895-1897 (F27) R16 initiated Oscar Wilde’s poem entitled ‘The ballad of the Reading gaol’ (F15)
R16 initiated
http://erlangen-crm.org/efrbroo/R16i_was_initiated_by
R16
URI: http://erlangen-crm.org/efrbroo/R16i_was_initiated_by
current:P12i_was_present_at | current:P92i_was_brought_into_existence_by | current:P94i_was_created_by
R16i was initiated by
R16i
current:P12_occurred_in_the_presence_of | current:P92_brought_into_existence | current:P94_has_created
efrbroo:F28_Expression_Creation
Scope note:
This property associates the expression that was first externalised during a particular creation event with that particular creation event.
Examples:
- Richard Wagner’s writing the original manuscript of his opera entitled ‘Der fliegende Holländer’ (F28) R17 created the notational content of the original manuscript of Richard Wagner’s opera entitled ‘Der fliegende Holländer’ (F22)
- Oscar Wilde’s writing the original manuscript of his poem entitled ‘The ballad of the Reading gaol’ (F28) R17 created the English text of Oscar Wilde’s poem entitled ‘The ballad of the Reading gaol’ (F22)
R17 created
http://erlangen-crm.org/efrbroo/R17i_was_created_by
R17
current:P12i_was_present_at | current:P92i_was_brought_into_existence_by | current:P94i_was_created_by
R17i was created by
R17i
current:P31_has_modified | current:P12_occurred_in_the_presence_of | current:P92_brought_into_existence | current:P108_has_produced
efrbroo:F28_Expression_Creation
Scope note:
This property associates an instance of F28 Expression Creation with the first physical objects in which the resulting instance of F2 Expression was embodied.
Examples:
- Emily Dickinson’s creating the text of one of the several extant versions of her poem known as ‘Safe in their alabaster chambers’ (F28) R18 created the manuscript now identified as ‘Massachusetts Cambridge Harvard University Houghton Library bMS Am 1118.3 (203c, 203d)’ (F4)
- Emily Dickinson’s creating the text of another one of the several extant versions of her poem known as ‘Safe in their alabaster chambers’ (F28) R18 created the manuscript now identified as ‘Massachusetts Cambridge Harvard University Houghton Library bMS Am 1118.5 (74c)’ (F4)
- The recording of the third alternate take of the musical work entitled ‘Blue Hawaii’ performed by Elvis Presley in Hollywood, Calif., Radio Recorders, on March 22nd, 1961 (F28) R18 created the master tape of the 3rd alternate take of the musical work entitled ‘Blue Hawaii’ performed by Elvis Presley in Hollywood, Calif., Radio Recorders, on March 22nd, 1961 (F4) (each individual take is a distinct expression)
- The resource (a drawing) held by the New York Public Library and identified by call number ‘*MGZGB Far P Cop 1’ (F4) R18i was created by the creation, by the artist named ‘Peter Farmer’, of a costume design for the character named ‘War’ in the Act III Masque of the seasons, in the Festival Ballet of London production of the choreographic work entitled ‘Coppélia’, with choreography by Jack Carter after Petipa (F28)
R18 created
http://erlangen-crm.org/efrbroo/R18i_was_created_by
R18
current:P12i_was_present_at | current:P92i_was_brought_into_existence_by | current:P31i_was_modified_by | current:P108i_was_produced_by
efrbroo:F4_Manifestation_Singleton
R18i was created by
R18i
URI: http://erlangen-crm.org/efrbroo/R19_created_a_realisation_of
Scope note:
This property associates an instance of F28 Expression Creation with the corresponding instance of F14 Individual Work or an instance of F15 Complex Work of which the corresponding instance of F14 Individual Work is a member.
Examples:
- Giovanni Battista Piranesi’s creating the image identified as ‘Carcere XVI: the pier with chains: 2nd state’ (F28) R19 created a realisation of the concept of Giovanni Battista Piranesi’s graphic work entitled ‘Carcere XVI: the pier with chains: 2nd state’ (F14)
- Recording Glenn Gould’s performance of Johann Sebastian Bach’s musical work entitled ‘Toccata in C minor BWV 911’ on May 15 & 16, 1979, in Toronto, Eaton’s Auditorium (F29) R19 created a realisation of the concept of the recorded performance of Johann Sebastian Bach’s musical work entitled ‘Toccata in C minor BWV 911’ by Glenn Gould on May 15 & 16, 1979, in Toronto, Eaton’s Auditorium (F21)
R19 created a realisation of
R19
URI: http://erlangen-crm.org/efrbroo/R19i_was_realised_through
R19i was realised through
http://erlangen-crm.org/efrbroo/R19_created_a_realisation_of
R19i
current:P12_occurred_in_the_presence_of | current:P15_was_influenced_by | current:P16_used_specific_object
efrbroo:F33_Reproduction_Event
Scope note:
This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it reproduces.
Examples:
- Making a photocopy of an exemplar of Eran Guter’s dissertation entitled ‘Where languages end: Ludwig Wittgenstein at the crossroads of music, language, and the world’ (F33) R29 reproduced one of the original exemplars of Eran Guter’s dissertation (E84)
R29 reproduced
R29
URI: http://erlangen-crm.org/efrbroo/R29i_was_reproduced_by
current:P15i_influenced | current:P12i_was_present_at | current:P16i_was_used_for
current:E84_Information_Carrier
R29i was reproduced by
http://erlangen-crm.org/efrbroo/R29_reproduced
R29i
Scope note:
This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter. The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation etc.
Examples:
- William Schuman’s orchestration of Charles Ives’s ‘Variations on America’ (F15) R2 is derivative of Charles Ives’s ‘Variations on America’ (F15) R2.1 has type orchestration (E55)
- Charles Ives’s musical work entitled ‘Variations on America’ (F15) R2 is derivative of the musical work titled ‘America’ (F15) R2.1 has type variations (E55)
- The musical work entitled ‘America’ (F15) R2 is derivative of the musical work entitled ‘God save the King’ (F15) R2.1 has type same tune with different lyrics (E55)
R2 is derivative of
http://erlangen-crm.org/efrbroo/R2i_has_derivative
R2
R2i has derivative
R2i
current:P31_has_modified | current:P12_occurred_in_the_presence_of | current:P92_brought_into_existence | current:P108_has_produced
efrbroo:F33_Reproduction_Event
Scope note:
This property associates an instance of F33 Reproduction Event with an instance of E84
Information Carrier it produces.
Examples:
- Making a photocopy of an exemplar of Eran Guter’s dissertation entitled ‘Where languages
end: Ludwig Wittgenstein at the crossroads of music, language, and the world’ (F33)
R30 produced the New York Public Library holding identified by call number ‘JMD 04-1060’
(E84)
R30 produced
http://erlangen-crm.org/efrbroo/R30i_was_produced_by
R30
URI: http://erlangen-crm.org/efrbroo/R30i_was_produced_by
current:P12i_was_present_at | current:P92i_was_brought_into_existence_by | current:P31i_was_modified_by | current:P108i_was_produced_by
current:E84_Information_Carrier
R30i was produced by
R30i
Scope note:
This property associates an instance of F22 Self-Contained Expression with an instance of F1 Work.
This property expresses the association that exists between an expression (F22) and the work that this expression conveys. The semantics of the association will be different depending on what specific subtype of F1 Work the work is an instance of. If the work is an instance of F14 Individual Work, the F22 Self-Contained Expression completely conveys the individual work. If the work is an instance of F15 Complex work, the F22 Self-Contained Expression conveys an alternative member of the complex work.
Our factual knowledge of how a given work is realised into an expression is often limited and this property makes it possible to express the association between instances of F22 Self-Contained Expression and the work it conveys without using the more developed paths.
Examples:
- Dante’s work entitled ‘Inferno’ (F15) R3 is realised in the Italian text of Dante’s ‘Inferno’ as found in the authoritative critical edition La Commedia secondo l’antica vulgata a cura di Giorgio Petrocchi, Milano: Mondadori, 1966-67 (= Le Opere di Dante Alighieri, Edizione Nazionale a cura della Società Dantesca Italiana, VII, 1-4) (F22)
- Mozart’s work entitled ‘Il dissoluto punito ossia il Don Giovanni’ (F15) R3 is realised in the notated music of the Prague version, as found on manuscript Ms 1548 of the National Library of France (F22) R3.1 has type autograph version (E55)
R3 is realised in
http://erlangen-crm.org/efrbroo/R3i_realises
R3
R3i realises
R3i
Scope note :
This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X.
It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by R14 incorporates.
Examples:
- The Italian text of Dante’s textual work entitled ‘Divina Commedia’ (F22) R5 has component the Italian text of Dante’s textual work entitled ‘Inferno’ (F22)
- The musical notation of Mozart’s Singspiel entitled ‘Die Zauberflöte’ (F22) R5 has component the musical notation of Mozart’s aria entitled ‘Der Hölle Rache’, also known as ‘The Queen of the Night’s Aria’ (F22)
- The visual content of the map entitled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22) R5 has component the visual content of the inset entitled ‘Liverpool’, scale 1:200,000, set within the compass of the map titled ‘Wales – The Midlands – South West England’, scale 1:400,000, issued by Michelin in 2005 (F22)
R5 has component
R5
R5i is component of
http://erlangen-crm.org/efrbroo/R5_has_component
R5i
URI: https://w3id.org/bibma/r0270_carried_out_by_as_scribe
current:P12_occurred_in_the_presence_of | current:P11_had_participant | current:P14_carried_out_by
This property describes the participation of a scribe in writing (a part of) a manuscript
Cette propriété désigne la participation d’un scribe à l’écriture d’un manuscrit ou de sa partie.
r0270_carried_out_by_as_scribe
https://w3id.org/bibma/r0270i_performed_as_scribe
URI: https://w3id.org/bibma/r0270i_performed_as_scribe
current:P12i_was_present_at | current:P11i_participated_in | current:P14i_performed
URI: https://w3id.org/bibma/r40_carried_out_by_as_annotator
current:P12_occurred_in_the_presence_of | current:P11_had_participant | current:P14_carried_out_by
This property describes the participation of an annotator in creating notes in a manuscript.
Cette propriété désigne la participation d’un annotateur à la création de notes dans un manuscrit.
r40_carried_out_by_as_annotator
URI: https://w3id.org/bibma/r40i_performed_as_annotator
current:P12i_was_present_at | current:P11i_participated_in | current:P14i_performed
https://w3id.org/bibma/r40_carried_out_by_as_annotator
URI: https://w3id.org/bibma/r70_carried_out_by_as_author
current:P12_occurred_in_the_presence_of | current:P11_had_participant | current:P14_carried_out_by
This property describes the participation of an author in creating a text.
Cette propriété désigne la participation d’un auteur à la création d’un texte.
r70_carried_out_by_as_author
https://w3id.org/bibma/r70i_performed_as_author
current:P12i_was_present_at | current:P11i_participated_in | current:P14i_performed
current:P125i_was_type_of_object_used_in | current:P32i_was_technique_of
bibma style of script was used
current:P12_occurred_in_the_presence_of | current:P15_was_influenced_by | current:P16_used_specific_object
efrbroo:F28_Expression_Creation
This property describes the relation between a preparatory manuscript and the final manuscript, which is not a complete copy of the original, but rather comprises some excerpts from its source.
Ex.: Lyon BM 478 served for preparation of the Augustinian compilation by Florus de Lyon found in Lyon BM 484.
Note: To describe the relation between the original and its complete copy, use the property bibma_used_for_copy.
Cette propriété décrit la relation entre un manuscrit préparatoire (manuscrit de travail) et le manuscrit final qui n’est pas une copie complète de l’original, mais contient des extraits copiés sur ce dernier.
Ex. : Lyon BM 478 a servi pour la préparation de la compilation augustinienne de Florus de Lyon conservé dans Lyon BM 484.
Note : Pour décrire la relation de l’original à sa copie complète, utiliser la propriété bibma_used_for_copy.
bibma used as source
current:P12_occurred_in_the_presence_of | current:P15_was_influenced_by | current:P16_used_specific_object
efrbroo:F28_Expression_Creation
Cette propriété établit la relation entre un manuscrit-source et sa copie fidèle.
Ex. : BnF Latin 2419 est une copie complète de BnF Latin 2859.
Note : Pour décrire la relation entre un manuscrit préparatoire et le manuscrit final, utiliser la propriété bibma_used_as_source.
This property describes the relation between a source manuscript and its faithful copy.
Ex.: BnF Latin 2419 is a complete copy of BnF Latin 2859.
Note: To describe the relation between a preparatory manuscript and the final manuscript, used the property bibma_used_as_source.
bibma used for copy
https://w3id.org/bibma/was_used_for_copy
current:P125_used_object_of_type | current:P32_used_general_technique
This property determines what type of script was used by a scribe to produce the manuscript.
Cette propriété identifie le type d’écriture qui fut utilisé par un copiste lors de la production du manuscrit.
bibma used style of script
https://w3id.org/bibma/style_of_script_was_used
current:P15i_influenced | current:P12i_was_present_at | current:P16i_was_used_for
current:E84_Information_Carrier
bibma was used as source
https://w3id.org/bibma/used_as_source
current:P15i_influenced | current:P12i_was_present_at | current:P16i_was_used_for
current:E84_Information_Carrier
bibma was used for copy
| current:P3_has_note | |||||||||||
| current:P79_beginning_is_qualified_by | |||||||||||
| current:P80_end_is_qualified_by | |||||||||||
| current:P81_ongoing_throughout | |||||||||||
| current:P82_at_some_time_within | |||||||||||
|
|||||||||||
| current:P90_has_value | |||||||||||
Membre de CIDOC CRM CORE
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"
P3 has note
P3
URI: http://erlangen-crm.org/current/P79_beginning_is_qualified_by
Scope note:
This property qualifies the beginning of an E52 Time-Span in some way.
The nature of the qualification may be certainty, precision, source etc.
Examples:
- the time-span of the Holocene (E52) beginning is qualified by "approximately"
P79 beginning is qualified by
P79
URI: http://erlangen-crm.org/current/P80_end_is_qualified_by
Scope note:
This property qualifies the end of an E52 Time-Span in some way.
The nature of the qualification may be certainty, precision, source etc.
Examples:
- the time-span of the Holocene (E52) end is qualified by "approximately"
P80 end is qualified by
P80
URI: http://erlangen-crm.org/current/P81_ongoing_throughout
Membre de CIDOC CRM CORE
Scope note:
This property describes the minimum period of time covered by an E52 Time-Span.
Since Time-Spans may not have precisely known temporal extents, the CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span's minimum temporal extent (i.e. its inner boundary) to be assigned a value.
Examples:
- the time-span of the development of the CIDOC CRM (E52) ongoing throughout "1996-2002"
P81 ongoing throughout
P81 couvre au moins
P81
URI: http://erlangen-crm.org/current/P82_at_some_time_within
Scope note:
This property describes the maximum period of time within which an E52 Time-Span falls.
Since Time-Spans may not have precisely known temporal extents, the CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span's maximum temporal extent (i.e. its outer boundary) to be assigned a value.
Examples:
- the time-span of the development of the CIDOC CRM (E52) at some time within "1992-infinity"
Membre de CIDOC CRM CORE
P82 couvre au plus
P82 at some time within
P82
URI: http://erlangen-crm.org/current/P82a_begin_of_the_begin
Scope note:
This property allows an E54 Dimension to be approximated by a value.
Examples:
- height of silver cup 232 (E54) has value "226"
P90 has value
P90
Page web basée sur les bibliothèques Python OntoSPy / Ontospyweb et RDFLib