diff --git a/.gitignore b/.gitignore index 72364f9..f6b0aa8 100644 --- a/.gitignore +++ b/.gitignore @@ -87,3 +87,5 @@ ENV/ # Rope project settings .ropeproject + +.DS_Store diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 0000000..d63837d --- /dev/null +++ b/.travis.yml @@ -0,0 +1,17 @@ +language: python +python: + - '2.7' + - '3.3' + - '3.4' + - '3.5' +install: + - pip install -r requirements.txt + - pip install coveralls +notifications: + email: + recipients: + - jgomez@getty.edu +script: + coverage run --source=crmpy setup.py test +after_success: + coveralls diff --git a/README.md b/README.md index b1acd6b..dfc2876 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,5 @@ +[![Build Status](https://travis-ci.org/gri-is/Python-CIDOC-ORM.svg?branch=master)](https://travis-ci.org/gri-is/Python-CIDOC-ORM) [![Coverage Status](https://coveralls.io/repos/github/gri-is/Python-CIDOC-ORM/badge.svg?branch=master)](https://coveralls.io/github/gri-is/Python-CIDOC-ORM?branch=master) + # Python-CIDOC-ORM Python library to make creation of CIDOC CRM easier by mapping classes/predicates to python objects diff --git a/build_tsv/vocab_reader.py b/build_tsv/vocab_reader.py index 0a8f949..2cd0c5a 100644 --- a/build_tsv/vocab_reader.py +++ b/build_tsv/vocab_reader.py @@ -141,6 +141,6 @@ stuff.append([name, "property", ccname, label, comment, subProp, domn, rang, inverse]) outdata = '\n'.join(['\t'.join(x) for x in stuff]) -fh = codecs.open('crm_vocab.tsv', 'w', 'utf-8') +fh = codecs.open('../data/crm_vocab.tsv', 'w', 'utf-8') fh.write(outdata) fh.close() diff --git a/build_tsv/vocab_reader_old.py b/build_tsv/vocab_reader_old.py deleted file mode 100644 index eda267e..0000000 --- a/build_tsv/vocab_reader_old.py +++ /dev/null @@ -1,131 +0,0 @@ -from lxml import etree -import codecs - -fh = file('cidoc_inverse.xml') -data = fh.read() -fh.close() - -if True: - property_overrides = { - "P45": "made_of", - "P7i": "location_of", - "P5": "has_subState", - "P5i": "is_subState_of", - "P20i": "was_specific_purpose_of", - "P42": "assigned_type", - "P42i": "type_was_assigned_by", - "P37": "assigned_identifier", - "P37i": "identifier_was_assigned_by", - - "P46i": "physically_part_of", - "P86": "temporally_within", - "P86i": "temporally_contains", - "P89": "spatially_within", - "P89i": "spatially_contains", - "P106": "has_section", - "P106i": "is_section_of", - - "P78": "time_is_identified_by", - "P78i": "identifies_time", - "P87": "place_is_identified_by", - "P87i": "identifies_place", - "P131": "actor_is_identified_by", - "P131i": "identifies_actor", - "P149": "concept_is_identified_by", - "P149i": "identifies_concept", - - "P151i": "participated_in_formation", - "P165i": "is_included_in", - "P132": "volume_overlaps_with", - "P135i": "type_was_created_by" - } -else: - property_overrides = {} - -NS = {'rdf':"http://www.w3.org/1999/02/22-rdf-syntax-ns#", - 'xsd':"http://www.w3.org/2001/XMLSchema#", - 'rdfs':"http://www.w3.org/2000/01/rdf-schema#", - 'dcterms':"http://purl.org/dc/terms/", - 'owl':"http://www.w3.org/2002/07/owl#", - 'crm':"http://www.cidoc-crm.org/cidoc-crm/", - 'xml': "http://www.w3.org/XML/1998/namespace" -} - -dom = etree.XML(data) -stuff = [] - -classes = dom.xpath("//rdfs:Class", namespaces=NS) - -for c in classes: - label = c.xpath('./rdfs:label[@xml:lang="en"]/text()', namespaces=NS)[0] - try: - comment = c.xpath('./rdfs:comment/text()', namespaces=NS)[0] - comment = comment.strip() - comment = comment.replace('\n', '\\n').replace('\t', ' ') - except: - comment = "" - name = c.xpath('@rdf:about', namespaces=NS)[0] - - subCls = c.xpath('./rdfs:subClassOf/@rdf:resource', namespaces=NS) - if subCls: - # could be multiples - subCls = '|'.join(subCls) - else: - subCls = "" - - uc1 = name.find("_") - ccname = name[uc1+1:] - ccname = ccname.replace("_or_", "_Or_").replace("_of_", "_Of_") - ccname = ccname.replace('-', '').replace('_', '') - - stuff.append([name, "class", ccname, label, comment, subCls]) - -props = dom.xpath("//rdf:Property",namespaces=NS) -for p in props: - label = p.xpath('./rdfs:label[@xml:lang="en"]/text()', namespaces=NS)[0] - try: - comment = p.xpath('./rdfs:comment/text()', namespaces=NS)[0] - comment = comment.strip() - comment = comment.replace('\n', '\\n').replace('\t', ' ') - except: - comment = "" - name = p.xpath('@rdf:about', namespaces=NS)[0] - domn = p.xpath('./rdfs:domain/@rdf:resource', namespaces=NS) - if domn: - domn = domn[0] - for (k,v) in NS.items(): - domn = domn.replace(v,"%s:" % k) - else: - domn = "" - rang = p.xpath('./rdfs:range/@rdf:resource', namespaces=NS) - if rang: - rang = rang[0] - for (k,v) in NS.items(): - rang = rang.replace(v,"%s:" % k) - else: - rang = "" - subProp = p.xpath('./rdfs:subPropertyOf/@rdf:resource', namespaces=NS) - if subProp: - subProp = subProp[0] - else: - subProp = "" - - inverse = p.xpath('./owl:inverseOf/@rdf:resource', namespaces=NS) - if inverse: - inverse = inverse[0] - else: - inverse = "" - - uc1 = name.find("_") - pno = name[:uc1] - if property_overrides.has_key(pno): - ccname = property_overrides[pno] - else: - ccname = name[uc1+1:] - ccname = ccname.replace("-", "") - stuff.append([name, "property", ccname, label, comment, subProp, domn, rang, inverse]) - -outdata = '\n'.join(['\t'.join(x) for x in stuff]) -fh = codecs.open('crm_vocab.tsv', 'w', 'utf-8') -fh.write(outdata) -fh.close() diff --git a/crm_vocab.tsv b/crm_vocab.tsv deleted file mode 100644 index f883f30..0000000 --- a/crm_vocab.tsv +++ /dev/null @@ -1,377 +0,0 @@ -E1_CRM_Entity class CRMEntity CRM Entity This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. \nIt is an abstract concept providing for three general properties:\n1. Identification by name or appellation, and in particular by a preferred identifier\n2. Classification by type, allowing further refinement of the specific subclass an instance belongs to \n3. Attachment of free text for the expression of anything not captured by formal properties\nWith the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity. -E2_Temporal_Entity class TemporalEntity Temporal Entity This class comprises all phenomena, such as the instances of E4 Periods, E5 Events and states, which happen over a limited extent in time. \n 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. E1_CRM_Entity -E3_Condition_State class ConditionState Condition State This class comprises the states of objects characterised by a certain condition over a time-span. \nAn instance of this class describes the prevailing physical condition of any material object or feature during a specific E52 Time Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held.\n The nature of that condition can be described using P2 has type. For example, the E3 Condition State “condition of the SS Great Britain between 22 September 1846 and 27 August 1847” can be characterized as E55 Type “wrecked”. E2_Temporal_Entity -E4_Period class Period Period This class comprises sets of coherent phenomena or cultural manifestations occurring in time and space.\n\nIt is the social or physical coherence of these phenomena that identify an E4 Period and not the associated spatiotemporal extent. This extent is only the "ground" or space in an abstract physical sense that the actual process of growth, spread and retreat has covered. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area and time as a sedentary culture. This also means that overlapping land use rights, common among first nations, amounts to overlapping periods.\n\nOften, 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. However, there are no assumptions about the scale of the associated 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.\n\nAs the actual extent of an E4 Period in spacetime we regard the trajectories of the participating physical things during their participation in an instance of E4 Period. This includes the open spaces via which these things have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event. Examples include the air in a meeting room transferring the voices of the participants. Since these phenomena are fuzzy, we assume the spatiotemporal extent to be contiguous, except for cases of phenomena spreading out over islands or other separated areas, including geopolitical units distributed over disconnected areas such as islands or colonies.\n\nWhether the trajectories necessary for participants to travel between these areas are regarded as part of the spatiotemporal extent or not has to be decided in each case based on a concrete analysis, taking use of the sea for other purposes than travel, such as fishing, into consideration. One may also argue that the activities to govern disconnected areas imply travelling through spaces connecting 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.\n\nConsequently, an instance of E4 Period may occupy a number of disjoint spacetime volumes, however there must not be a discontinuity in the timespan covered by these spacetime volumes. This means that an instance of E4 Period must be contiguous in time. If it has ended in all areas, it has ended as a whole. However it may end in one area before another, such as in the Polynesian migration, and it continues as long as it is ongoing in at least one area.\n\nWe model E4 Period as a subclass of E2 Temporal Entity and of E92 Spacetime volume. The latter is intended as a phenomenal spacetime volume as defined in CRMgeo (Doerr and Hiebel 2013). By virtue of this multiple inheritance we can discuss the physical extent of an E4 Period without representing each instance of it together with an instance of its associated spacetime volume. This model combines two quite different kinds of substance: an instance of E4 Period is a phenomena while a space-time volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance of E4 Period is regarded to be unique to it due to all its details and fuzziness; its identity and existence depends uniquely on the identity of the instance of E4 Period. Therefore this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language.\n\nThere 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 instance of E4 Period, and the second defines morphological object types that fall under E55 Type.\n\nAnother specific case of an E4 Period is the set of activities and phenomena associated with a settlement, such as the populated period of Nineveh. E2_Temporal_Entity|E92_Spacetime_Volume -E5_Event class Event Event 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.\nThe 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. E4_Period -E6_Destruction class Destruction Destruction This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation. \nSome destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an E6 Destruction and E7 Activity. \nThe decision to document an object as destroyed, transformed or modified is context sensitive: \n1. If the matter remaining from the destruction is not documented, the event is modelled solely as E6 Destruction. \n2. 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 original. In this case, the new items have separate identities. Matter is preserved, but identity is not.\n3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification. E64_End_of_Existence -E7_Activity class Activity Activity 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. \nThis 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. E5_Event -E8_Acquisition class Acquisition Acquisition This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more other instances of E39 Actor. \nThe 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:\n1. the beginning of ownership\n2. the end of ownership\n3. the transfer of ownership\n4. the acquisition from an unknown source \n5. the loss of title due to destruction of the item\nIt 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. E7_Activity -E9_Move class Move Move This class comprises changes of the physical location of the instances of E19 Physical Object. \nNote, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event. E7_Activity -E10_Transfer_of_Custody class TransferOfCustody Transfer of Custody This class comprises transfers of physical custody of objects between instances of E39 Actor. \nThe recording of the donor and/or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient. Depending on the circumstances it may describe:\n1. the beginning of custody \n2. the end of custody \n3. the transfer of custody \n4. the receipt of custody from an unknown source\n5. the declared loss of an object\nThe distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type (is type of). A specific case of transfer of custody is theft.\nThe interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these. E7_Activity -E11_Modification class Modification Modification This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing. \nThis 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. \nSince 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. \nIf the instance of the E29 Design or Procedure utilized 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. E7_Activity -E12_Production class Production Production This class comprises activities that are designed to, and succeed in, creating one or more new items. \nIt 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. \nThis entity can be collective: the printing of a thousand books, for example, would normally be considered a single event. \nAn 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. E11_Modification|E63_Beginning_of_Existence -E13_Attribute_Assignment class AttributeAssignment Attribute Assignment This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts. \nThis 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. \nIn 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. E7_Activity -E14_Condition_Assessment class ConditionAssessment Condition Assessment This class describes the act of assessing the state of preservation of an object during a particular period. \nThe condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents. E13_Attribute_Assignment -E15_Identifier_Assignment class IdentifierAssignment Identifier Assignment This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.\nExamples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.\nThe fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property. E13_Attribute_Assignment -E16_Measurement class Measurement Measurement This class comprises actions measuring physical properties and other values that can be determined by a systematic procedure. \nExamples include measuring the monetary value of a collection of coins or the running time of a specific video cassette. \nThe E16 Measurement may use simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Details of methods and devices are best handled as free text, whereas basic techniques such as "carbon 14 dating" should be encoded using P2 has type (is type of:) E55 Type. E13_Attribute_Assignment -E17_Type_Assignment class TypeAssignment Type Assignment This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions and concepts. \nThis 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. E13_Attribute_Assignment -E18_Physical_Thing class PhysicalThing Physical Thing This class comprises all persistent physical items with a relatively stable form, man-made or natural.\n\nDepending 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.\n\nAn instance of E18 Physical Thing occupies not only a particular geometric space, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces, such as the interior of a box. Physical things consisting of aggregations of physically unconnected objects, such as a set of chessmen, occupy a number of individually contiguous spacetime volumes equal to the number of unconnected objects that constitute the set.\n\nWe model E18 Physical Thing to be a subclass of E72 Legal Object and of E92 Spacetime volume. The latter is intended as a phenomenal spacetime volume as defined in CRMgeo (Doerr and Hiebel 2013). By virtue of this multiple inheritance we can discuss the physical extent of an E18 Physical Thing without representing each instance of it together with an instance of its associated spacetime volume. This model combines two quite different kinds of substance: an instance of E18 Physical Thing is matter while a spacetime volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance of E18 Physical Thing is regarded to be unique to it, due to all its details and fuzziness; its identity and existence depends uniquely on the identity of the instance of E18 Physical Thing. Therefore this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language.\n\nThe CIDOC CRM is generally not concerned with amounts of matter in fluid or gaseous states. E72_Legal_Object|E92_Spacetime_Volume -E19_Physical_Object class PhysicalObject Physical Object 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. \nThe 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).\nIn some contexts, such objects, except for aggregates, are also called “bona fide objects” (Smith & Varzi, 2000, pp.401-420), i.e. naturally defined objects. \nThe 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. E18_Physical_Thing -E20_Biological_Object class BiologicalObject Biological Object This class comprises individual items of a material nature, which live, have lived or are natural products of or from living organisms. \nArtificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Man-Made Object. E19_Physical_Object -E21_Person class Person Person This class comprises real persons who live or are assumed to have lived. \nLegendary 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. E20_Biological_Object|E39_Actor -E22_Man-Made_Object class ManMadeObject Man-Made Object This class comprises physical objects purposely created by human activity.\nNo 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. E19_Physical_Object|E24_Physical_Man-Made_Thing -E24_Physical_Man-Made_Thing class PhysicalManMadeThing Physical Man-Made Thing This class comprises all persistent physical items that are purposely created by human activity.\nThis 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. E18_Physical_Thing|E71_Man-Made_Thing -E25_Man-Made_Feature class ManMadeFeature Man-Made Feature This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc. \nNo 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. E24_Physical_Man-Made_Thing|E26_Physical_Feature -E26_Physical_Feature class PhysicalFeature Physical Feature This class comprises identifiable features that are physically attached in an integral way to particular physical objects. \nInstances 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. \nInstances 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. \nThis definition coincides with the definition of "fiat objects" (Smith & Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”. E18_Physical_Thing -E27_Site class Site Site This class comprises pieces of land or sea floor. \nIn contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings and maps.\n Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location E26_Physical_Feature -E28_Conceptual_Object class ConceptualObject Conceptual Object 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.\nCharacteristically, 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.\nThey 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. E71_Man-Made_Thing -E29_Design_or_Procedure class DesignOrProcedure Design or Procedure This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular it comprises plans for deliberate human activities that may result in the modification or production of instances of E24 Physical Thing. \nInstances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 has association with (is associated with). \nDesigns or procedures can be seen as one of the following:\n1. A schema for the activities it describes\n2. A schema of the products that result from their application. \n3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci’s famous plans for flying machines.\nBecause designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product. E73_Information_Object -E30_Right class Right Right This class comprises legal privileges concerning material and immaterial things or their derivatives. \nThese include reproduction and property rights E89_Propositional_Object -E31_Document class Document Document This class comprises identifiable immaterial items that make propositions about reality.\nThese 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. E73_Information_Object -E32_Authority_Document class AuthorityDocument Authority Document This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use. E31_Document -E33_Linguistic_Object class LinguisticObject Linguistic Object This class comprises identifiable expressions in natural language or languages. \nInstances 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.\nThe text of an instance of E33 Linguistic Object can be documented in a note by P3 has note: E62 String E73_Information_Object -E34_Inscription class Inscription Inscription This class comprises recognisable, short texts attached to instances of E24 Physical Man-Made Thing. \nThe 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.\nThe 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. E33_Linguistic_Object|E37_Mark -E35_Title class Title Title This class comprises the names assigned to works, such as texts, artworks or pieces of music. \nTitles 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. \nThis class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts. E33_Linguistic_Object|E41_Appellation -E36_Visual_Item class VisualItem Visual Item This class comprises the intellectual or conceptual aspects of recognisable marks and images.\nThis 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. \nThe 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 P65 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. E73_Information_Object -E37_Mark class Mark Mark 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. \nThis 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. E36_Visual_Item -E38_Image class Image Image 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. \nThe 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. E36_Visual_Item -E39_Actor class Actor Actor 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.\nThe 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. E77_Persistent_Item -E40_Legal_Body class LegalBody Legal Body This class comprises institutions or groups of people that have obtained a legal recognition as a group and can act collectively as agents. \nThis 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. E74_Group -E41_Appellation class Appellation Appellation 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.\nInstances 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. \nSpecific 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.\nE41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment E90_Symbolic_Object -E42_Identifier class Identifier Identifier 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. E41_Appellation -E44_Place_Appellation class PlaceAppellation Place Appellation This class comprises any sort of identifier characteristically used to refer to an E53 Place. \nInstances 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. E41_Appellation -E45_Address class Address Address This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.\nAn E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address. E44_Place_Appellation|E51_Contact_Point -E46_Section_Definition class SectionDefinition Section Definition This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind. \nThe '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 ). E44_Place_Appellation -E47_Spatial_Coordinates class SpatialCoordinates Spatial Coordinates This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification. \n\nCoordinates 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. E44_Place_Appellation -E48_Place_Name class PlaceName Place Name This class comprises particular and common forms of E44 Place Appellation. \nPlace 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. E44_Place_Appellation -E49_Time_Appellation class TimeAppellation Time Appellation 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. \nThe 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’. E41_Appellation -E50_Date class Date Date This class comprises specific forms of E49 Time Appellation. E49_Time_Appellation -E51_Contact_Point class ContactPoint Contact Point This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. \nURLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor. E41_Appellation -E52_Time-Span class TimeSpan Time-Span This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration. \nTime 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. \nSince 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. \n Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive. E1_CRM_Entity -E53_Place class Place Place 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. \nThe 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.\n 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.\nAny 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. E1_CRM_Entity -E54_Dimension class Dimension Dimension 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.\nAn 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.\nNumerical 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. E1_CRM_Entity -E55_Type class Type Type 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. \nE55 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. E28_Conceptual_Object -E56_Language class Language Language This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts. \nThis 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”.\nIt 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. E55_Type -E57_Material class Material Material This class is a specialization of E55 Type and comprises the concepts of materials. \nInstances 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).\nThis 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”.\nIt is recommended that internationally or nationally agreed codes and terminology are used. E55_Type -E58_Measurement_Unit class MeasurementUnit Measurement Unit This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc. \nThis 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”.\nSyst?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. E55_Type -E63_Beginning_of_Existence class BeginningOfExistence Beginning of Existence This class comprises events that bring into existence any E77 Persistent Item. \nIt 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. E5_Event -E64_End_of_Existence class EndOfExistence End of Existence This class comprises events that end the existence of any E77 Persistent Item. \nIt 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. E5_Event -E65_Creation class Creation Creation 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. E7_Activity|E63_Beginning_of_Existence -E66_Formation class Formation Formation This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation. \nE66 Formation does not include the arbitrary aggregation of people who do not act as a collective.\nThe formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining. E7_Activity|E63_Beginning_of_Existence -E67_Birth class Birth Birth This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings). \nTwins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event. E63_Beginning_of_Existence -E68_Dissolution class Dissolution Dissolution This class comprises the events that result in the formal or informal termination of an E74 Group of people. \nIf the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity. E64_End_of_Existence -E69_Death class Death Death This class comprises the deaths of human beings. \nIf a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence. E64_End_of_Existence -E70_Thing class Thing Thing This general class comprises discrete, identifiable, instances of E77 Persistent Item that are documented as single units, that either consist of matter or depend on being carried by matter and are characterized by relative stability.\nThey 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. E77_Persistent_Item -E71_Man-Made_Thing class ManMadeThing Man-Made Thing This class comprises discrete, identifiable man-made items that are documented as single units. \nThese 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. E70_Thing -E72_Legal_Object class LegalObject Legal Object 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. \nThis 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. E70_Thing -E73_Information_Object class InformationObject Information Object This class comprises identifiable immaterial items, such as a poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. 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. \nAn 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. \nInstances 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 ideas without a reproducible expression. E89_Propositional_Object|E90_Symbolic_Object -E74_Group class Group Group This class comprises any gatherings or organizations of E39 Actors 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. In such cases, it may happen that the Group never had more than one member. 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.\nA 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 modeled as membership in an E74 Group (cf. HumanML markup). Married couples and other concepts of family are regarded as particular examples of E74 Group. E39_Actor -E75_Conceptual_Object_Appellation class ConceptualObjectAppellation Conceptual Object Appellation This class comprises appellations that are by their form or syntax specific to identifying instances of E28 Conceptual Object, such as intellectual products, standardized patterns etc. E41_Appellation -E77_Persistent_Item class PersistentItem Persistent Item This class comprises items that have a persistent identity, sometimes known as “endurants” in philosophy. \nThey 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.\nThe 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.\nThe 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. E1_CRM_Entity -E78_Collection class Collection Collection This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained ("curated" and "preserved", in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. \nItems may be added or removed from an E78 Collection in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Collection often referred to with the name of the E78 Collection (e.g. “The Wallace Collection decided…”).\nCollective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Collection. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality. E24_Physical_Man-Made_Thing -E79_Part_Addition class PartAddition Part Addition This class comprises activities that result in an instance of E24 Physical Man-Made Thing being increased, enlarged or augmented by the addition of a part. \nTypical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated E78 Collection. Objects to which parts are added are, by definition, man-made, since the addition of a part implies a human activity. Following the addition of parts, the resulting man-made assemblages are treated objectively as single identifiable wholes, made up of constituent or component parts bound together either physically (for example the engine becoming a part of the car), or by sharing a common purpose (such as the 32 chess pieces that make up a chess set). This class of activities forms a basis for reasoning about the history and continuity of identity of objects that are integrated into other objects over time, such as precious gemstones being repeatedly incorporated into different items of jewellery, or cultural artifacts being added to different museum instances of E78 Collection over their lifespan. E11_Modification -E80_Part_Removal class PartRemoval Part Removal This class comprises the activities that result in an instance of E18 Physical Thing being decreased by the removal of a part.\nTypical scenarios include the detachment of an accessory, the removal of a component or part of a composite object, or the deaccessioning of an object from a curated E78 Collection. If the E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an E81 Transformation, i.e. a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be regarded as both E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewelry, or cultural artifacts being deaccessioned from different museum collections over their lifespan. E11_Modification -E81_Transformation class Transformation Transformation This class comprises the events that result in the simultaneous destruction of one or more than one E77 Persistent Item and the creation of one or more than one E77 Persistent Item that preserves recognizable substance from the first one(s) but has fundamentally different nature and identity. \nAlthough the old and the new instances of E77 Persistent Item are treated as discrete entities having separate, unique identities, they are causally connected through the E81 Transformation; the destruction of the old E77 Persistent Item(s) directly causes the creation of the new one(s) using or preserving some relevant substance. Instances of E81 Transformation are therefore distinct from re-classifications (documented using E17 Type Assignment) or modifications (documented using E11 Modification) of objects that do not fundamentally change their nature or identity. Characteristic cases are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimen in natural history and the reorganization of a corporate body into a new one. E63_Beginning_of_Existence|E64_End_of_Existence -E82_Actor_Appellation class ActorAppellation Actor Appellation This class comprises any sort of name, number, code or symbol characteristically used to identify an E39 Actor. \nAn 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. E41_Appellation -E83_Type_Creation class TypeCreation Type Creation This class comprises activities formally defining new types of items. \nIt is typically a rigorous scholarly or scientific process that ensures a type is exhaustively described and appropriately named. In some cases, particularly in archaeology and the life sciences, E83 Type Creation requires the identification of an exemplary specimen and the publication of the type definition in an appropriate scholarly forum. The activity of E83 Type Creation is central to research in the life sciences, where a type would be referred to as a “taxon,” the type description as a “protologue,” and the exemplary specimens as “orgininal element” or “holotype”. E65_Creation -E84_Information_Carrier class InformationCarrier Information Carrier 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.\nAn 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. E22_Man-Made_Object -E85_Joining class Joining Joining This class comprises the activities that result in an instance of E39 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party.\nTypical scenarios include becoming a member of a social organisation, becoming employee of a company, marriage, the adoption of a child by a family and the inauguration of somebody into an official position. E7_Activity -E86_Leaving class Leaving Leaving This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party. It may be the initiative of a third party. \nTypical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position. E7_Activity -E87_Curation_Activity class CurationActivity Curation Activity This class comprises the activities that result in the continuity of management and the preservation and evolution of instances of E78 Collection, following an implicit or explicit curation plan. \nIt specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded.\nItems are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an E78 Collection for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity. E7_Activity -E89_Propositional_Object class PropositionalObject Propositional Object 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 topics of discourse. \n \nThis 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. E28_Conceptual_Object -E90_Symbolic_Object class SymbolicObject Symbolic Object 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.\n It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content.\n 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.\n In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized content model, such.. as the property P3 has note allows for describing this content model…P3.1 has type: E55 Type to specify the encoding.. E28_Conceptual_Object|E72_Legal_Object -E92_Spacetime_Volume class SpacetimeVolume Spacetime Volume This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. \n Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. \n Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time. E1_CRM_Entity -E93_Presence class Presence Presence This class comprises instances of E92 Spacetime Volume that result from intersection of instances of E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituing spacetime volume and the time-span. \n \nThis class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD. E92_Spacetime_Volume -E96_Purchase class Purchase Purchase E8_Acquisition -E97_Monetary_Amount class MonetaryAmount Monetary Amount E54_Dimension -E98_Currency class Currency Currency E55_Type -P1_is_identified_by property identified_by is identified by This property describes the naming or identification of any real world item by a name or any other identifier. \nThis 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. E1_CRM_Entity E41_Appellation P1i_identifies -P1i_identifies property identifies identifies E41_Appellation E1_CRM_Entity P1_is_identified_by -P2_has_type property classified_as has type This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. \nThe 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. E1_CRM_Entity E55_Type P2i_is_type_of -P2i_is_type_of property type_of is type of E55_Type E1_CRM_Entity P2_has_type -P3_has_note property note has note This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. \nIn particular it captures the characterisation of the item itself, its internal structures, appearance etc.\nLike 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. \nAn item may have many notes, but a note is attached to a specific item. E1_CRM_Entity rdfs:Literal P30_transferred_custody_of -P4_has_time-span property timespan has time-span This property describes the temporal confinement of an instance of an E2 Temporal Entity.\nThe 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. E2_Temporal_Entity E52_Time-Span P4i_is_time-span_of -P4i_is_time-span_of property timespan_of is time-span of E52_Time-Span E2_Temporal_Entity P4_has_time-span -P5_consists_of property subState consists of This property describes the decomposition of an E3 Condition State into discrete, subsidiary states. \nIt is assumed that the sub-states into which the condition state is analysed form a logical whole - although the entire story may not be completely known – and that the sub-states are in fact constitutive of the general condition state. For example, a general condition state of “in ruins” may be decomposed into the individual stages of decay E3_Condition_State E3_Condition_State P5i_forms_part_of -P5i_forms_part_of property subState_of forms part of E3_Condition_State E3_Condition_State P5_consists_of -P7_took_place_at property took_place_at took place at This property describes the spatial location of an instance of E4 Period. \n\nThe related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took 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.\nA period can take place at multiple locations.\nIt is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. E4_Period E53_Place P7i_witnessed -P7i_witnessed property location_of witnessed E53_Place E4_Period P7_took_place_at -P8_took_place_on_or_within property took_place_on_or_within took place on or within This property describes the location of an instance of E4 Period with respect to an E19 Physical Object. \nP8 took place on or within (witnessed) is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156 occupies (is occupied by) to E18 Physical Thing.\n\nIt describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. \nFor example, the French and German armistice of 22 June 1940 was signed in the same railway carriage as the armistice of 11 November 1918. E4_Period E18_Physical_Thing P8i_witnessed -P8i_witnessed property witnessed witnessed E18_Physical_Thing E4_Period P8_took_place_on_or_within -P9_consists_of property consists_of consists of This property associates an instance of E4 Period with another instance of E4 Period that is defined by a subset of the phenomena that define the former. Therefore the spacetime volume of the latter must fall within the spacetime volume of the former. P10i_contains E4_Period E4_Period P9i_forms_part_of -P9i_forms_part_of property forms_part_of forms part of P10_falls_within E4_Period E4_Period P9_consists_of -P10_falls_within property falls_within falls within This property associates an instance of E92 Spacetime Volume with another instance of E92 Spacetime Volume that falls within the latter. In other words, all points in the former are also points in the latter. E92_Spacetime_Volume E92_Spacetime_Volume P10i_contains -P10i_contains property contains contains E92_Spacetime_Volume E92_Spacetime_Volume P10_falls_within -P11_had_participant property participant had participant This property describes the active or passive participation of instances of E39 Actors in an E5 Event. \nIt 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. P12_occurred_in_the_presence_of E5_Event E39_Actor P11i_participated_in -P11i_participated_in property participated_in participated in P12i_was_present_at E39_Actor E5_Event P11_had_participant -P12_occurred_in_the_presence_of property occurred_in_the_presence_of occurred in the presence of This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role. \nIt 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. E5_Event E77_Persistent_Item P12i_was_present_at -P12i_was_present_at property present_at was present at E77_Persistent_Item E5_Event P12_occurred_in_the_presence_of -P13_destroyed property destroyed destroyed This property allows specific instances of E18 Physical Thing that have been destroyed to be related to a destruction event. \nDestruction implies the end of an item’s life as a subject of cultural documentation – the physical matter of which the item was composed may in fact continue to exist. A destruction event may be contiguous with a Production that brings into existence a derived object composed partly of matter from the destroyed object. P93_took_out_of_existence E6_Destruction E18_Physical_Thing P13i_was_destroyed_by -P13i_was_destroyed_by property destroyed_by was destroyed by P93i_was_taken_out_of_existence_by E18_Physical_Thing E6_Destruction P13_destroyed -P14_carried_out_by property carried_out_by carried out by This property describes the active participation of an E39 Actor in an E7 Activity. \nIt 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. P11_had_participant E7_Activity E39_Actor P14i_performed -P14i_performed property performed performed P11i_participated_in E39_Actor E7_Activity P14_carried_out_by -P15_was_influenced_by property influenced_by was influenced by This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it.\nThe property has more specific sub properties. E7_Activity E1_CRM_Entity P15i_influenced -P15i_influenced property influenced influenced E1_CRM_Entity E7_Activity P15_was_influenced_by -P16_used_specific_object property used_specific_object used specific object This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. \nThis 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.\nAnother 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. P12_occurred_in_the_presence_of E7_Activity E70_Thing P16i_was_used_for -P16i_was_used_for property used_for was used for P12i_was_present_at E70_Thing E7_Activity P16_used_specific_object -P17_was_motivated_by property motivated_by was motivated by This property describes an item or items that are regarded as a reason for carrying out the E7 Activity. \nFor example, the discovery of a large hoard of treasure may call for a celebration, an order from head quarters can start a military manoeuvre. P15_was_influenced_by E7_Activity E1_CRM_Entity P17i_motivated -P17i_motivated property motivated motivated P15i_influenced E1_CRM_Entity E7_Activity P17_was_motivated_by -P19_was_intended_use_of property intended_use_of was intended use of This property relates an E7 Activity with objects created specifically for use in the activity. \nThis is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)). E7_Activity E71_Man-Made_Thing P19i_was_made_for -P19i_was_made_for property made_for was made for E71_Man-Made_Thing E7_Activity P19_was_intended_use_of -P20_had_specific_purpose property specific_purpose had specific purpose This property identifies the relationship between a preparatory activity and the event it is intended to be preparation for.\nThis includes activities, orders and other organisational actions, taken in preparation for other activities or events. \nP20 had specific purpose (was purpose of) implies that an activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, one may document the unrealized intention using P21 had general purpose (was purpose of):E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure. E7_Activity E5_Event P20i_was_purpose_of -P20i_was_purpose_of property specific_purpose_of was purpose of E5_Event E7_Activity P20_had_specific_purpose -P21_had_general_purpose property general_purpose had general purpose This property describes an intentional relationship between an E7 Activity and some general goal or purpose. \nThis may involve activities intended as preparation for some type of activity or event. P21had general purpose (was purpose of) differs from P20 had specific purpose (was purpose of) in that no occurrence of an event is implied as the purpose. E7_Activity E55_Type P21i_was_purpose_of -P21i_was_purpose_of property purpose_of was purpose of E55_Type E7_Activity P21_had_general_purpose -P22_transferred_title_to property transferred_title_to transferred title to This property identifies the E39 Actor that acquires the legal ownership of an object as a result of an E8 Acquisition. \nThe property will typically describe an Actor purchasing or otherwise acquiring an object from another Actor. However, title may also be acquired, without any corresponding loss of title by another Actor, through legal fieldwork such as hunting, shooting or fishing.\nIn reality the title is either transferred to or from someone, or both. P14_carried_out_by E8_Acquisition E39_Actor P22i_acquired_title_through -P22i_acquired_title_through property acquired_title_through acquired title through P14i_performed E39_Actor E8_Acquisition P22_transferred_title_to -P23_transferred_title_from property transferred_title_from transferred title from This property identifies the E39 Actor or Actors who relinquish legal ownership as the result of an E8 Acquisition.\nThe property will typically be used to describe a person donating or selling an object to a museum. In reality title is either transferred to or from someone, or both. P14_carried_out_by E8_Acquisition E39_Actor P23i_surrendered_title_through -P23i_surrendered_title_through property surrendered_title_through surrendered title through P14i_performed E39_Actor E8_Acquisition P23_transferred_title_from -P24_transferred_title_of property transferred_title_of transferred title of This property identifies the E18 Physical Thing or things involved in an E8 Acquisition. \nIn reality, an acquisition must refer to at least one transferred item. E8_Acquisition E18_Physical_Thing P24i_changed_ownership_through -P24i_changed_ownership_through property changed_ownership_through changed ownership through E18_Physical_Thing E8_Acquisition P24_transferred_title_of -P25_moved property moved moved This property identifies an instance of E19 Physical Object that was moved by a move event. A move must concern at least one object.\n\nThe property implies the object's passive participation. For example, Monet's painting "Impression sunrise" was moved for the first Impressionist exhibition in 1874. P12_occurred_in_the_presence_of E9_Move E19_Physical_Object P25i_moved_by -P25i_moved_by property moved_by moved by P12i_was_present_at E19_Physical_Object E9_Move P25_moved -P26_moved_to property moved_to moved to This property identifies a destination of a E9 Move. \nA move will be linked to a destination, such as the move of an artefact from storage to display. A move may be linked to many terminal instances of E53 Place by multiple instances of this property. In this case the move describes a distribution of a set of objects. The area of the move includes the origin(s), route and destination(s).\nTherefore the described destination is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at. E9_Move E53_Place P26i_was_destination_of -P26i_was_destination_of property destination_of was destination of P7i_witnessed E53_Place E9_Move P26_moved_to -P27_moved_from property moved_from moved from This property identifies a starting E53 Place of an E9 Move.\n\nA move will be linked to an origin, such as the move of an artefact from storage to display. A move may be linked to many starting instances of E53 Place by multiple instances of this property. In this case the move describes the picking up of a set of objects. The area of the move includes the origin(s), route and destination(s).\nTherefore the described origin is an instance of E53 Place which P89 falls within (contains) the instance of E53 Place the move P7 took place at. E9_Move E53_Place P27i_was_origin_of -P27i_was_origin_of property origin_of was origin of P7i_witnessed E53_Place E9_Move P27_moved_from -P28_custody_surrendered_by property custody_surrendered_by custody surrendered by This property identifies the E39 Actor or Actors who surrender custody of an instance of E18 Physical Thing in an E10 Transfer of Custody activity. \nThe property will typically describe an Actor surrendering custody of an object when it is handed over to someone else’s care. On occasion, physical custody may be surrendered involuntarily – through accident, loss or theft.\nIn reality, custody is either transferred to someone or from someone, or both. P14_carried_out_by E10_Transfer_of_Custody E39_Actor P28i_surrendered_custody_through -P28i_surrendered_custody_through property surrendered_custody_through surrendered custody through P14i_performed E39_Actor E10_Transfer_of_Custody P28_custody_surrendered_by -P29_custody_received_by property custody_received_by custody received by This property identifies the E39 Actor or Actors who receive custody of an instance of E18 Physical Thing in an E10 Transfer of Custody activity. \nThe property will typically describe Actors receiving custody of an object when it is handed over from another Actor’s care. On occasion, physical custody may be received involuntarily or illegally – through accident, unsolicited donation, or theft.\nIn reality, custody is either transferred to someone or from someone, or both. P14_carried_out_by E10_Transfer_of_Custody E39_Actor P29i_received_custody_through -P29i_received_custody_through property received_custody_through received custody through P14i_performed E39_Actor E10_Transfer_of_Custody P29_custody_received_by -P30_transferred_custody_of property transferred_custody_of transferred custody of This property identifies an item or items of E18 Physical Thing concerned in an E10 Transfer of Custody activity. \nThe property will typically describe the object that is handed over by an E39 Actor to another Actor’s custody. On occasion, physical custody may be transferred involuntarily or illegally – through accident, unsolicited donation, or theft. E10_Transfer_of_Custody E18_Physical_Thing P30i_custody_transferred_through -P30i_custody_transferred_through property custody_transferred_through custody transferred through E18_Physical_Thing E10_Transfer_of_Custody P30_transferred_custody_of -P31_has_modified property modified has modified This property identifies the E24 Physical Man-Made Thing modified in an E11 Modification.\nIf a modification is applied to a non-man-made object, it is regarded as an E22 Man-Made Object from that time onwards. P12_occurred_in_the_presence_of E11_Modification E24_Physical_Man-Made_Thing P31i_was_modified_by -P31i_was_modified_by property modified_by was modified by P12i_was_present_at E24_Physical_Man-Made_Thing E11_Modification P31_has_modified -P32_used_general_technique property used_general_technique used general technique This property identifies the technique or method that was employed in an activity.\nThese techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques or methods such as embroidery, oil-painting, carbon dating, etc. Specific documented techniques should be described as instances of E29 Design or Procedure. This property identifies the technique that was employed in an act of modification. P125_used_object_of_type E7_Activity E55_Type P32i_was_technique_of -P32i_was_technique_of property technique_of was technique of P125i_was_type_of_object_used_in E55_Type E7_Activity P32_used_general_technique -P33_used_specific_technique property used_specific_technique used specific technique This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. \nThe property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. \nTypical examples would include intervention plans for conservation or the construction plans of a building. P16_used_specific_object E7_Activity E29_Design_or_Procedure P33i_was_used_by -P33i_was_used_by property used_by was used by P16i_was_used_for E29_Design_or_Procedure E7_Activity P33_used_specific_technique -P34_concerned property concerned concerned This property identifies the E18 Physical Thing that was assessed during an E14 Condition Assessment activity. \nConditions may be assessed either by direct observation or using recorded evidence. In the latter case the E18 Physical Thing does not need to be present or extant. P140_assigned_attribute_to E14_Condition_Assessment E18_Physical_Thing P34i_was_assessed_by -P34i_was_assessed_by property assessed_by was assessed by P140i_was_attributed_by E18_Physical_Thing E14_Condition_Assessment P34_concerned -P35_has_identified property identified has identified This property identifies the E3 Condition State that was observed in an E14 Condition Assessment activity. P141_assigned E14_Condition_Assessment E3_Condition_State P35i_was_identified_by -P35i_was_identified_by property condition_identified_by was identified by P141i_was_assigned_by E3_Condition_State E14_Condition_Assessment P35_has_identified -P37_assigned property assigned_identifier assigned This property records the identifier that was assigned to an item in an Identifier Assignment activity.\nThe same identifier may be assigned on more than one occasion.\nAn Identifier might be created prior to an assignment. P141_assigned E15_Identifier_Assignment E42_Identifier P37i_was_assigned_by -P37i_was_assigned_by property identifier_assigned_by was assigned by P141i_was_assigned_by E42_Identifier E15_Identifier_Assignment P37_assigned -P38_deassigned property deassigned deassigned This property records the identifier that was deassigned from an instance of E1 CRM Entity.\nDeassignment of an identifier may be necessary when an item is taken out of an inventory, a new numbering system is introduced or items are merged or split up. \nThe same identifier may be deassigned on more than one occasion. P141_assigned E15_Identifier_Assignment E42_Identifier P38i_was_deassigned_by -P38i_was_deassigned_by property deassigned_by was deassigned by P141i_was_assigned_by E42_Identifier E15_Identifier_Assignment P38_deassigned -P39_measured property measured measured This property associates an instance of E16 Measurement with the instance of E1 CRM Entity to which it applied. An instance of E1 CRM Entity may be measured more than once. Material and immaterial things and processes may be measured, e.g. the number of words in a text, or the duration of an event. P140_assigned_attribute_to E16_Measurement E1_CRM_Entity P39i_was_measured_by -P39i_was_measured_by property measured_by was measured by P140i_was_attributed_by E1_CRM_Entity E16_Measurement P39_measured -P40_observed_dimension property observed_dimension observed dimension This property records the dimension that was observed in an E16 Measurement Event.\nE54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.\nDimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant.\nEven though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made. P141_assigned E16_Measurement E54_Dimension P40i_was_observed_in -P40i_was_observed_in property observed_in was observed in P141i_was_assigned_by E54_Dimension E16_Measurement P40_observed_dimension -P41_classified property classified classified This property records the item to which a type was assigned in an E17 Type Assignment activity.\nAny instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified (was classified), 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). P140_assigned_attribute_to E17_Type_Assignment E1_CRM_Entity P41i_was_classified_by -P41i_was_classified_by property classified_by was classified by P140i_was_attributed_by E1_CRM_Entity E17_Type_Assignment P41_classified -P42_assigned property assigned_type assigned This property records the type that was assigned to an entity by an E17 Type Assignment activity. \nType 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).\nFor 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.\nA Type may be intellectually constructed independent from assigning an instance of it. P141_assigned E17_Type_Assignment E55_Type P42i_was_assigned_by -P42i_was_assigned_by property type_assigned_by was assigned by P141i_was_assigned_by E55_Type E17_Type_Assignment P42_assigned -P43_has_dimension property dimension has dimension This property records a E54 Dimension of some E70 Thing.\nIt 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.\nAn instance of E54 Dimension is specific to an instance of E70 Thing. E70_Thing E54_Dimension P43i_is_dimension_of -P43i_is_dimension_of property dimension_of is dimension of E54_Dimension E70_Thing P43_has_dimension -P44_has_condition property condition has condition This property records an E3 Condition State for some E18 Physical Thing.\nIt is a shortcut of the more fully developed path from E18 Physical Thing through P34 concerned (was assessed by), E14 Condition Assessment P35 has identified (was identified by) to E3 Condition State. It offers no information about how and when the E3 Condition State was established, nor by whom. \nAn instance of Condition State is specific to an instance of Physical Thing. E18_Physical_Thing E3_Condition_State P44i_is_condition_of -P44i_is_condition_of property condition_of is condition of E3_Condition_State E18_Physical_Thing P44_has_condition -P45_consists_of property made_of consists of This property identifies the instances of E57 Materials of which an instance of E18 Physical Thing is composed.\nAll 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.\nA Material, such as a theoretical alloy, may not have any physical instances E18_Physical_Thing E57_Material P45i_is_incorporated_in -P45i_is_incorporated_in property incorporated_in is incorporated in E57_Material E18_Physical_Thing P45_consists_of -P46_is_composed_of property part is composed of This property allows instances of E18 Physical Thing to be analysed into component elements.\n\nComponent 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 does not specify when and for how long a component element resided in the respective whole. If a component is not part of a whole from the beginning of existence or until the end of existence of the whole, the classes E79 Part Addition and E90 Part Removal can be used to document when a component became part of a particular whole and/or when it stopped being a part of it. For the time-span of being part of the respective whole, the component is completely contained in the place the whole occupies.\n\nThis 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.\n\nThe instances of E57 Material of which an item of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in). E18_Physical_Thing E18_Physical_Thing P46i_forms_part_of -P46i_forms_part_of property part_of forms part of E18_Physical_Thing E18_Physical_Thing P46_is_composed_of -P48_has_preferred_identifier property preferred_identifier has preferred identifier 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.\nMore than one preferred identifier may have been assigned to an item over time.\nUse of this property requires an external mechanism for assigning temporal validity to the respective CRM instance.\nP48 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. P1_is_identified_by E1_CRM_Entity E42_Identifier P48i_is_preferred_identifier_of -P48i_is_preferred_identifier_of property preferred_identifier_of is preferred identifier of P1i_identifies E42_Identifier E1_CRM_Entity P48_has_preferred_identifier -P49_has_former_or_current_keeper property former_or_current_keeper has former or current keeper This property identifies the E39 Actor or Actors who have or have had custody of an instance of E18 Physical Thing at\nsome time. This property leaves open the question if parts of this physical thing have\nbeen added or removed during the time-spans it has been under the custody of this\nactor, but it is required that at least a part which can unambiguously be identified as\nrepresenting the whole has been under this custody for its whole time. The way, in\nwhich a representative part is defined, should ensure that it is unambiguous who keeps\na part and who the whole and should be consistent with the identity criteria of the kept\ninstance of E18 Physical Thing.\nThe distinction with P50 has current keeper (is current keeper of) is that P49 has former or current\nkeeper (is former or current keeper of) leaves open the question as to whether the specified keepers are\ncurrent.\nP49 has former or current keeper (is former or current keeper of) is a shortcut for the more detailed\npath from E18 Physical Thing through P30 transferred custody of (custody transferred through), E10\nTransfer of Custody, P28 custody surrendered by (surrendered custody through) or P29 custody\nreceived by (received custody through) to E39 Actor. E18_Physical_Thing E39_Actor P49i_is_former_or_current_keeper_of -P49i_is_former_or_current_keeper_of property former_or_current_keeper_of is former or current keeper of E39_Actor E18_Physical_Thing P49_has_former_or_current_keeper -P50_has_current_keeper property current_keeper has current keeper 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.\n 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. P49_has_former_or_current_keeper E18_Physical_Thing E39_Actor P50i_is_current_keeper_of -P50i_is_current_keeper_of property current_keeper_of is current keeper of P49i_is_former_or_current_keeper_of E39_Actor E18_Physical_Thing P50_has_current_keeper -P51_has_former_or_current_owner property former_or_current_owner has former or current owner 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.\nThe 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. E18_Physical_Thing E39_Actor P51i_is_former_or_current_owner_of -P51i_is_former_or_current_owner_of property former_or_current_owner_of is former or current owner of E39_Actor E18_Physical_Thing P51_has_former_or_current_owner -P52_has_current_owner property current_owner has current owner This property identifies the E21 Person, E74 Group or E40 Legal Body that was the owner of an instance of E18 Physical Thing at the time of validity of the record or database containing the statement that uses this property.\nP52 has current owner (is 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, P22 transferred title to (acquired title through) to E39 Actor, if and only if this acquisition event is the most recent. P51_has_former_or_current_owner E18_Physical_Thing E39_Actor P52i_is_current_owner_of -P52i_is_current_owner_of property current_owner_of is current owner of P51i_is_former_or_current_owner_of E39_Actor E18_Physical_Thing P52_has_current_owner -P53_has_former_or_current_location property former_or_current_location has former or current location This property allows an instance of E53 Place to be associated as the former or current location of an instance of E18 Physical Thing.\nIn 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.\nIn the case of immobile objects, the Place would normally correspond to the Place of creation.\nP53 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. E18_Physical_Thing E53_Place P53i_is_former_or_current_location_of -P53i_is_former_or_current_location_of property former_or_current_location_of is former or current location of E53_Place E18_Physical_Thing P53_has_former_or_current_location -P54_has_current_permanent_location property current_permanent_location has current permanent location This property records the foreseen permanent location of an instance of E19 Physical Object at the time of validity of the record or database containing the statement that uses this property.\nP54 has current permanent location (is current permanent location of) is similar to P55 has current location (currently holds). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location. E19_Physical_Object E53_Place P54i_is_current_permanent_location_of -P54i_is_current_permanent_location_of property current_permanent_location_of is current permanent location of E53_Place E19_Physical_Object P54_has_current_permanent_location -P55_has_current_location property current_location has current location 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. \n This property is a specialisation of P53 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. \nP55 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. P53_has_former_or_current_location E19_Physical_Object E53_Place P55i_currently_holds -P55i_currently_holds property currently_holds currently holds P53i_is_former_or_current_location_of E53_Place E19_Physical_Object P55_has_current_location -P56_bears_feature property bears_feature bears feature This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears.\nAn 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.\nAn 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.\nP56 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\nDefinition of the CIDOC Conceptual Reference Model 149 within), E53 Place, P53 has former or current location (is former or current location of) to E26 Physical Feature. P46_is_composed_of E19_Physical_Object E26_Physical_Feature P56i_is_found_on -P56i_is_found_on property found_on is found on P46i_forms_part_of E26_Physical_Feature E19_Physical_Object P56_bears_feature -P57_has_number_of_parts property number_of_parts has number of parts This property documents the E60 Number of parts of which an instance of E19 Physical Object is composed.\nThis may be used as a method of checking inventory counts with regard to aggregate or collective objects. What constitutes a part or component depends on the context and requirements of the documentation. Normally, the parts documented in this way would not be considered as worthy of individual attention.\nFor a more complete description, objects may be decomposed into their components and constituents using P46 is composed of (forms parts of) and P45 consists of (is incorporated in). This allows each element to be described individually. E19_Physical_Object rdfs:Literal -P58_has_section_definition property section_definition has section definition This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found.\nThe 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.\nThis 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).\nA particular instance of a Section Definition only applies to one instance of Physical Thing. E18_Physical_Thing E46_Section_Definition P58i_defines_section -P58i_defines_section property defines_section defines section E46_Section_Definition E18_Physical_Thing P58_has_section_definition -P59_has_section property section has section This property links an area to the instance of E18 Physical Thing upon which it is found.\nIt is typically used when a named E46 Section Definition is not appropriate.\nE18 Physical Thing may be subdivided into arbitrary regions. \nP59 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. E18_Physical_Thing E53_Place P59i_is_located_on_or_within -P59i_is_located_on_or_within property located_on_or_within is located on or within E53_Place E18_Physical_Thing P59_has_section -P62_depicts property depicts depicts This property identifies something that is depicted by an instance of E24 Physical Man-Made Thing. Depicting is meant in the sense that the surface of the E24 Physical Man-Made Thing shows, through its passive optical qualities or form, a representation of the entity depicted. It does not pertain to inscriptions or any other information encoding.\n\nThis 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. E24_Physical_Man-Made_Thing E1_CRM_Entity P62i_is_depicted_by -P62i_is_depicted_by property depicted_by is depicted by E1_CRM_Entity E24_Physical_Man-Made_Thing P62_depicts -P65_shows_visual_item property shows_visual_item shows visual item This property documents an E36 Visual Item shown by an instance of E24 Physical Man-Made Thing.\nThis property is similar to P62 depicts (is depicted by) in that it associates an item of E24 Physical Man-Made Thing with a visual representation. However, P65 shows visual item (is shown by) differs from the P62 depicts (is depicted by) property in that it makes no claims about what the E36 Visual Item is deemed to represent. E36 Visual Item identifies a recognisable image or visual symbol, regardless of what this image may or may not represent.\nFor example, all recent British coins bear a portrait of Queen Elizabeth II, a fact that is correctly documented using P62 depicts (is depicted by). Different portraits have been used at different periods, however. P65 shows visual item (is shown by) can be used to refer to a particular portrait.\nP65 shows visual item (is shown by) may also be used for Visual Items such as signs, marks and symbols, for example the 'Maltese Cross' or the 'copyright symbol’ that have no particular representational content. \nThis property is part of the 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 which is shortcut by, P62 depicts (is depicted by). P128_carries E24_Physical_Man-Made_Thing E36_Visual_Item P65i_is_shown_by -P65i_is_shown_by property shown_by is shown by P128i_is_carried_by E36_Visual_Item E24_Physical_Man-Made_Thing P65_shows_visual_item -P67_refers_to property refers_to refers to This property documents that an E89 Propositional Object makes a statement about an instance of 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. E89_Propositional_Object E1_CRM_Entity P67i_is_referred_to_by -P67i_is_referred_to_by property referred_to_by is referred to by E1_CRM_Entity E89_Propositional_Object P67_refers_to -P68_foresees_use_of property foresees_use_of foresees use of This property identifies an E57 Material foreseeen to be used by an E29 Design or Procedure. \nE29 Designs and procedures commonly foresee the use of particular E57 Materials. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented.\nThis property is not intended for the documentation of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed. P67_refers_to E29_Design_or_Procedure E57_Material P68i_use_foreseen_by -P68i_use_foreseen_by property use_foreseen_by use foreseen by P67i_is_referred_to_by E57_Material E29_Design_or_Procedure P68_foresees_use_of -P69_is_associated_with property associated_with is associated with This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type.\nThe P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.\nThe property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures. E29_Design_or_Procedure E29_Design_or_Procedure -P70_documents property documents documents This property describes the CRM Entities documented by instances of E31 Document.\nDocuments 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. P67_refers_to E31_Document E1_CRM_Entity P70i_is_documented_in -P70i_is_documented_in property documented_in is documented in P67i_is_referred_to_by E1_CRM_Entity E31_Document P70_documents -P71_lists property lists lists This property documents a source E32 Authority Document for an instance of an E1 CRM Entity. P67_refers_to E32_Authority_Document E1_CRM_Entity P71i_is_listed_in -P71i_is_listed_in property listed_in is listed in P67i_is_referred_to_by E1_CRM_Entity E32_Authority_Document P71_lists -P72_has_language property language has language This property describes the E56 Language of an E33 Linguistic Object. \nLinguistic Objects are composed in one or more human Languages. This property allows these languages to be documented. E33_Linguistic_Object E56_Language P72i_is_language_of -P72i_is_language_of property language_of is language of E56_Language E33_Linguistic_Object P72_has_language -P73_has_translation property translation has translation This property describes the source and target of instances of E33Linguistic Object involved in a translation.\nWhen a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object. P130_shows_features_of E33_Linguistic_Object E33_Linguistic_Object P73i_is_translation_of -P73i_is_translation_of property translation_of is translation of P130i_features_are_also_found_on E33_Linguistic_Object E33_Linguistic_Object P73_has_translation -P74_has_current_or_former_residence property current_or_former_residence has current or former residence This property describes the current or former E53 Place of residence of an E39 Actor. \nThe residence may be either the Place where the Actor resides, or a legally registered address of any kind. E39_Actor E53_Place P74i_is_current_or_former_residence_of -P74i_is_current_or_former_residence_of property current_or_former_residence_of is current or former residence of E53_Place E39_Actor P74_has_current_or_former_residence -P75_possesses property possesses possesses This property identifies former or current instances of E30 Rights held by an E39 Actor. E39_Actor E30_Right P75i_is_possessed_by -P75i_is_possessed_by property possessed_by is possessed by E30_Right E39_Actor P75_possesses -P76_has_contact_point property contact_point has contact point This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax. E39_Actor E51_Contact_Point P76i_provides_access_to -P76i_provides_access_to property provides_access_to provides access to E51_Contact_Point E39_Actor P76_has_contact_point -P78_is_identified_by property time_identified_by is identified by This property identifies an E52 Time-Span using an E49Time Appellation. P1_is_identified_by E52_Time-Span E49_Time_Appellation P78i_identifies -P78i_identifies property identifies_time identifies P1i_identifies E49_Time_Appellation E52_Time-Span P78_is_identified_by -P79_beginning_is_qualified_by property beginning_is_qualified_by beginning is qualified by This property qualifies the beginning of an E52 Time-Span in some way. \nThe nature of the qualification may be certainty, precision, source etc. P3_has_note E52_Time-Span rdfs:Literal -P80_end_is_qualified_by property end_is_qualified_by end is qualified by This property qualifies the end of an E52 Time-Span in some way. \nThe nature of the qualification may be certainty, precision, source etc. P3_has_note E52_Time-Span rdfs:Literal -P81_ongoing_throughout property ongoing_throughout ongoing throughout This property describes the minimum period of time covered by an E52 Time-Span.\nSince 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 an E61 Time Primitive value. Time Primitives are treated by the CRM as application or system specific date intervals, and are not further analysed. E52_Time-Span rdfs:Literal P81a_end_of_the_begin -P82_at_some_time_within property at_some_time_within at some time within This property describes the maximum period of time within which an E52 Time-Span falls.\nSince 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 an E61 Time Primitive value. Time Primitives are treated by the CRM as application or system specific date intervals, and are not further analysed. E52_Time-Span rdfs:Literal P82a_begin_of_the_begin -P83_had_at_least_duration property at_least_duration had at least duration This property describes the minimum length of time covered by an E52 Time-Span. \nIt allows an E52 Time-Span to be associated with an E54 Dimension representing it’s minimum duration (i.e. it’s inner boundary) independent from the actual beginning and end. E52_Time-Span E54_Dimension P83i_was_minimum_duration_of -P83i_was_minimum_duration_of property minimum_duration_of was minimum duration of E54_Dimension E52_Time-Span P83_had_at_least_duration -P84_had_at_most_duration property at_most_duration had at most duration This property describes the maximum length of time covered by an E52 Time-Span. \nIt allows an E52 Time-Span to be associated with an E54 Dimension representing it’s maximum duration (i.e. it’s outer boundary) independent from the actual beginning and end. E52_Time-Span E54_Dimension P84i_was_maximum_duration_of -P84i_was_maximum_duration_of property maximum_duration_of was maximum duration of E54_Dimension E52_Time-Span P84_had_at_most_duration -P86_falls_within property temporally_within falls within This property describes the inclusion relationship between two instances of E52 Time-Span.\nThis property supports the notion that a Time-Span’s temporal extent falls within the temporal extent of another Time-Span. It addresses temporal containment only, and no contextual link between the two instances of Time-Span is implied. E52_Time-Span E52_Time-Span P86i_contains -P86i_contains property temporally_contains contains E52_Time-Span E52_Time-Span P86_falls_within -P87_is_identified_by property place_identified_by is identified by This property identifies an E53 Place using an E44 Place Appellation. \nExamples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc. P1_is_identified_by E53_Place E44_Place_Appellation P87i_identifies -P87i_identifies property identifies_place identifies P1i_identifies E44_Place_Appellation E53_Place P87_is_identified_by -P89_falls_within property spatially_within falls within This property identifies an instance of E53 Place that falls wholly within the extent of another E53 Place.\nIt addresses spatial containment only, and does not imply any relationship between things or phenomena occupying these places. E53_Place E53_Place P89i_contains -P89i_contains property spatially_contains contains E53_Place E53_Place P89_falls_within -P90_has_value property has_value has value This property allows an E54 Dimension to be approximated by an E60 Number primitive. E54_Dimension rdfs:Literal -P91_has_unit property unit has unit This property shows the type of unit an E54 Dimension was expressed in. E54_Dimension E58_Measurement_Unit P91i_is_unit_of -P91i_is_unit_of property unit_of is unit of E58_Measurement_Unit E54_Dimension P91_has_unit -P92_brought_into_existence property brought_into_existence brought into existence This property allows an E63 Beginning of Existence event to be linked to the E77 Persistent Item brought into existence by it.\nIt 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 P12_occurred_in_the_presence_of E63_Beginning_of_Existence E77_Persistent_Item P92i_was_brought_into_existence_by -P92i_was_brought_into_existence_by property brought_into_existence_by was brought into existence by P12i_was_present_at E77_Persistent_Item E63_Beginning_of_Existence P92_brought_into_existence -P93_took_out_of_existence property took_out_of_existence took out of existence This property allows an E64 End of Existence event to be linked to the E77 Persistent Item taken out of existence by it.\nIn the case of immaterial things, the E64 End of Existence is considered to take place with the destruction of the last physical carrier.\nThis 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. P12_occurred_in_the_presence_of E64_End_of_Existence E77_Persistent_Item P93i_was_taken_out_of_existence_by -P93i_was_taken_out_of_existence_by property taken_out_of_existence_by was taken out of existence by P12i_was_present_at E77_Persistent_Item E64_End_of_Existence P93_took_out_of_existence -P94_has_created property created has created This property allows a conceptual E65 Creation to be linked to the E28 Conceptual Object created by it. \nIt 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. P92_brought_into_existence E65_Creation E28_Conceptual_Object P94i_was_created_by -P94i_was_created_by property created_by was created by P92i_was_brought_into_existence_by E28_Conceptual_Object E65_Creation P94_has_created -P95_has_formed property formed has formed This property links the founding or E66 Formation for an E74 Group with the Group itself. P92_brought_into_existence E66_Formation E74_Group P95i_was_formed_by -P95i_was_formed_by property formed_by was formed by P92i_was_brought_into_existence_by E74_Group E66_Formation P95_has_formed -P96_by_mother property by_mother by mother This property links an E67 Birth event to an E21 Person as a participant in the role of birth-giving mother.\n\nNote that biological fathers are not necessarily participants in the Birth (see P97 from father (was father for)). The Person being born is linked to the Birth with the property P98 brought into life (was born). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. This is a sub-property of P11 had participant (participated in). P11_had_participant E67_Birth E21_Person P96i_gave_birth -P96i_gave_birth property gave_birth gave birth P11i_participated_in E21_Person E67_Birth P96_by_mother -P97_from_father property from_father from father This property links an E67 Birth event to an E21 Person in the role of biological father.\nNote that biological fathers are not seen as necessary participants in the Birth, whereas birth-giving mothers are (see P96 by mother (gave birth)). The Person being born is linked to the Birth with the property P98 brought into life (was born).\nThis is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. \nA Birth event is normally (but not always) associated with one biological father. E67_Birth E21_Person P97i_was_father_for -P97i_was_father_for property father_for was father for E21_Person E67_Birth P97_from_father -P98_brought_into_life property brought_into_life brought into life This property links an E67Birth event to an E21 Person in the role of offspring.\nTwins, triplets etc. are brought into life by the same Birth event. This is not intended for use with general Natural History material, only people. There is no explicit method for modelling conception and gestation except by using extensions. P92_brought_into_existence E67_Birth E21_Person P98i_was_born -P98i_was_born property born was born P92i_was_brought_into_existence_by E21_Person E67_Birth P98_brought_into_life -P99_dissolved property dissolved dissolved This property links the disbanding or E68 Dissolution of an E74 Group to the Group itself. P11_had_participant E68_Dissolution E74_Group P99i_was_dissolved_by -P99i_was_dissolved_by property dissolved_by was dissolved by P11i_participated_in E74_Group E68_Dissolution P99_dissolved -P100_was_death_of property death_of was death of This property property links an E69 Death event to the E21 Person that died. P93_took_out_of_existence E69_Death E21_Person P100i_died_in -P100i_died_in property died_in died in P93i_was_taken_out_of_existence_by E21_Person E69_Death P100_was_death_of -P101_had_as_general_use property as_general_use had as general use This property links an instance of E70 Thing to an E55 Type of usage.\nIt allows the relationship between particular things, both physical and immaterial, and general methods and techniques of use to be documented. Thus it can be asserted that a baseball bat had a general use for sport and a specific use for threatening people during the Great Train Robbery. E70_Thing E55_Type P101i_was_use_of -P101i_was_use_of property use_of was use of E55_Type E70_Thing P101_had_as_general_use -P102_has_title property title has title 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.\nThe 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.\nIt 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. P1_is_identified_by E71_Man-Made_Thing E35_Title P102i_is_title_of -P102i_is_title_of property title_of is title of P1i_identifies E35_Title E71_Man-Made_Thing P102_has_title -P103_was_intended_for property intended_for was intended for This property links an instance of E71 Man-Made Thing to an E55 Type of usage. \nIt creates a property between specific man-made things, both physical and immaterial, to Types of intended methods and techniques of use. Note: A link between specific man-made things and a specific use activity should be expressed using P19 was intended use of (was made for). E71_Man-Made_Thing E55_Type P103i_was_intention_of -P103i_was_intention_of property intention_of was intention of E55_Type E71_Man-Made_Thing P103_was_intended_for -P104_is_subject_to property subject_to is subject to This property links a particular E72 Legal Object to the instances of E30 Right to which it is subject.\nThe Right is held by an E39 Actor as described by P75 possesses (is possessed by). E72_Legal_Object E30_Right P104i_applies_to -P104i_applies_to property applies_to applies to E30_Right E72_Legal_Object P104_is_subject_to -P105_right_held_by property right_held_by right held by This property identifies the E39 Actor who holds the instances of E30 Right to an E72 Legal Object.\n It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object.\nP105 right held by (has right on) is a shortcut of the fully developed path from E72 Legal Object through P104 is subject to (applies to), E30 Right, P75 possesses (is possessed by) to E39 Actor. E72_Legal_Object E39_Actor P105i_has_right_on -P105i_has_right_on property right_on has right on E39_Actor E72_Legal_Object P105_right_held_by -P106_is_composed_of property composed_of is composed of 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. E90_Symbolic_Object E90_Symbolic_Object P106i_forms_part_of -P106i_forms_part_of property composed_from forms part of E90_Symbolic_Object E90_Symbolic_Object P106_is_composed_of -P107_has_current_or_former_member property current_or_former_member has current or former member This property relates an E39 Actor to the E74 Group of which that E39 Actor is a member.\nGroups, Legal Bodies and Persons, may all be members of Groups. A Group necessarily consists of more than one member.\nThis property is a shortcut of the more fully developed path from E74 Group through P144 joined with (gained member by), E85 Joining, P143 joined (was joined by) to E39 Actor\nThe property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group. E74_Group E39_Actor P107i_is_current_or_former_member_of -P107i_is_current_or_former_member_of property current_or_former_member_of is current or former member of E39_Actor E74_Group P107_has_current_or_former_member -P108_has_produced property produced has produced This property identifies the E24 Physical Man-Made Thing that came into existence as a result of an E12 Production.\nThe 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. P31_has_modified E12_Production E24_Physical_Man-Made_Thing P108i_was_produced_by -P108i_was_produced_by property produced_by was produced by P31i_was_modified_by E24_Physical_Man-Made_Thing E12_Production P108_has_produced -P109_has_current_or_former_curator property current_or_former_curator has current or former curator This property identifies the E39 Actor or Actors who assume or have assumed overall curatorial responsibility for an E78 Collection.\n\nIt does not allow a history of curation to be recorded. This would require use of an Event initiating a curator being responsible for a Collection. P49_has_former_or_current_keeper E78_Collection E39_Actor P109i_is_current_or_former_curator_of -P109i_is_current_or_former_curator_of property current_or_former_curator_of is current or former curator of P49i_is_former_or_current_keeper_of E39_Actor E78_Collection P109_has_current_or_former_curator -P110_augmented property augmented augmented This property identifies the E24 Physical Man-Made Thing that is added to (augmented) in an E79 Part Addition.\nAlthough a Part Addition event normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses. P31_has_modified E79_Part_Addition E24_Physical_Man-Made_Thing P110i_was_augmented_by -P110i_was_augmented_by property augmented_by was augmented by P31i_was_modified_by E24_Physical_Man-Made_Thing E79_Part_Addition P110_augmented -P111_added property added added This property identifies the E18 Physical Thing that is added during an E79 Part Addition activity P16_used_specific_object E79_Part_Addition E18_Physical_Thing P111i_was_added_by -P111i_was_added_by property added_by was added by P16i_was_used_for E18_Physical_Thing E79_Part_Addition P111_added -P112_diminished property diminished diminished This property identifies the E24 Physical Man-Made Thing that was diminished by E80 Part Removal.\nAlthough a Part removal activity normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single Part Removal activity. P31_has_modified E80_Part_Removal E24_Physical_Man-Made_Thing P112i_was_diminished_by -P112i_was_diminished_by property diminished_by was diminished by P31i_was_modified_by E24_Physical_Man-Made_Thing E80_Part_Removal P112_diminished -P113_removed property removed removed This property identifies the E18 Physical Thing that is removed during an E80 Part Removal activity. P12_occurred_in_the_presence_of E80_Part_Removal E18_Physical_Thing P113i_was_removed_by -P113i_was_removed_by property removed_by was removed by P12i_was_present_at E18_Physical_Thing E80_Part_Removal P113_removed -P114_is_equal_in_time_to property equal_in_time_to is equal in time to This symmetric property allows the instances of E2 Temporal Entity with the same E52 Time-Span to be equated. \nThis property is only necessary if the time span is unknown (otherwise the equivalence can be calculated).\nThis property is the same as the "equal" relationship of Allen’s temporal logic (Allen, 1983, pp. 832-843). E2_Temporal_Entity E2_Temporal_Entity -P115_finishes property finishes finishes This property allows the ending point for a E2 Temporal Entity to be situated by reference to the ending point of another temporal entity of longer duration. \nThis property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "finishes / finished-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). E2_Temporal_Entity E2_Temporal_Entity P115i_is_finished_by -P115i_is_finished_by property finished_by is finished by E2_Temporal_Entity E2_Temporal_Entity P115_finishes -P116_starts property starts starts This property allows the starting point for a E2 Temporal Entity to be situated by reference to the starting point of another temporal entity of longer duration. \nThis property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "starts / started-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). E2_Temporal_Entity E2_Temporal_Entity P116i_is_started_by -P116i_is_started_by property started_by is started by E2_Temporal_Entity E2_Temporal_Entity P116_starts -P117_occurs_during property occurs_during occurs during This property allows the entire E52 Time-Span of an E2 Temporal Entity to be situated within the Time-Span of another temporal entity that starts before and ends after the included temporal entity. \nThis property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "during / includes" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). E2_Temporal_Entity E2_Temporal_Entity P117i_includes -P117i_includes property includes includes E2_Temporal_Entity E2_Temporal_Entity P117_occurs_during -P118_overlaps_in_time_with property overlaps_in_time_with overlaps in time with This property identifies an overlap between the instances of E52 Time-Span of two instances of E2 Temporal Entity. \nIt implies a temporal order between the two entities: if A overlaps in time B, then A must start before B, and B must end after A. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated).\nThis property is the same as the "overlaps / overlapped-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). E2_Temporal_Entity E2_Temporal_Entity P118i_is_overlapped_in_time_by -P118i_is_overlapped_in_time_by property overlapped_in_time_by is overlapped in time by E2_Temporal_Entity E2_Temporal_Entity P118_overlaps_in_time_with -P119_meets_in_time_with property meets_in_time_with meets in time with This property indicates that one E2 Temporal Entity immediately follows another. \nIt implies a particular order between the two entities: if A meets in time with B, then A must precede B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated). \nThis property is the same as the "meets / met-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). E2_Temporal_Entity E2_Temporal_Entity P119i_is_met_in_time_by -P119i_is_met_in_time_by property met_in_time_by is met in time by E2_Temporal_Entity E2_Temporal_Entity P119_meets_in_time_with -P120_occurs_before property occurs_before occurs before This property identifies the relative chronological sequence of two temporal entities. \nIt implies that a temporal gap exists between the end of A and the start of B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated).\nThis property is the same as the "before / after" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). E2_Temporal_Entity E2_Temporal_Entity P120i_occurs_after -P120i_occurs_after property occurs_after occurs after E2_Temporal_Entity E2_Temporal_Entity P120_occurs_before -P121_overlaps_with property overlaps_with overlaps with This symmetric property allows the instances of E53 Place with overlapping geometric extents to be associated with each other. \nIt does not specify anything about the shared area. This property is purely spatial, in contrast to Allen operators, which are purely temporal. E53_Place E53_Place -P122_borders_with property borders_with borders with This symmetric property allows the instances of E53 Place which share common borders to be related as such. \nThis property is purely spatial, in contrast to Allen operators, which are purely temporal. E53_Place E53_Place -P123_resulted_in property resulted_in resulted in This property identifies the E77 Persistent Item or items that are the result of an E81 Transformation. \nNew items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the link to the common Transformation. P92_brought_into_existence E81_Transformation E77_Persistent_Item P123i_resulted_from -P123i_resulted_from property resulted_from resulted from P92i_was_brought_into_existence_by E77_Persistent_Item E81_Transformation P123_resulted_in -P124_transformed property transformed transformed This property identifies the E77 Persistent Item or items that cease to exist due to a E81 Transformation. \nIt is replaced by the result of the Transformation, which becomes a new unit of documentation. The continuity between both items, the new and the old, is expressed by the link to the common Transformation. P93_took_out_of_existence E81_Transformation E77_Persistent_Item P124i_was_transformed_by -P124i_was_transformed_by property transformed_by was transformed by P93i_was_taken_out_of_existence_by E77_Persistent_Item E81_Transformation P124_transformed -P125_used_object_of_type property used_object_of_type used object of type 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". E7_Activity E55_Type P125i_was_type_of_object_used_in -P125i_was_type_of_object_used_in property type_of_object_used_in was type of object used in E55_Type E7_Activity P125_used_object_of_type -P126_employed property employed employed This property identifies E57 Material employed in an E11 Modification.\nThe E57 Material used during the E11 Modification does not necessarily become incorporated into the E24 Physical Man-Made Thing that forms the subject of the E11 Modification. E11_Modification E57_Material P126i_was_employed_in -P126i_was_employed_in property employed_in was employed in E57_Material E11_Modification P126_employed -P127_has_broader_term property broader_term has broader term This property identifies a super-Type to which an E55 Type is related. \n It allows Types to be organised into hierarchies. This is the sense of "broader term generic (BTG)" as defined in ISO 2788 E55_Type E55_Type P127i_has_narrower_term -P127i_has_narrower_term property narrower_term has narrower term E55_Type E55_Type P127_has_broader_term -P128_carries property carries carries This property identifies an E90 Symbolic Object carried by an instance of E18 Physical Thing. P130_shows_features_of E18_Physical_Thing E90_Symbolic_Object P128i_is_carried_by -P128i_is_carried_by property carried_by is carried by P130i_features_are_also_found_on E90_Symbolic_Object E18_Physical_Thing P128_carries -P129_is_about property about is about This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity. P67_refers_to E89_Propositional_Object E1_CRM_Entity P129i_is_subject_of -P129i_is_subject_of property subject_of is subject of P67i_is_referred_to_by E1_CRM_Entity E89_Propositional_Object P129_is_about -P130_shows_features_of property shows_features_of shows features of This property generalises the notions of "copy of" and "similar to" into a directed relationship, where\nthe domain expresses the derivative, if such a direction can be established.\nOtherwise, the relationship is symmetric. If the reason for similarity is a sort of derivation process, i.e.,\nthat the creator has used or had in mind the form of a particular thing during the creation or production,\nthis process should be explicitly modelled. Moreover it expresses similarity in cases that can be stated\nbetween two objects only, without historical knowledge about its reasons. P73i_is_translation_of E70_Thing E70_Thing P130i_features_are_also_found_on -P130i_features_are_also_found_on property features_are_also_found_on features are also found on E70_Thing E70_Thing P130_shows_features_of -P131_is_identified_by property actor_identified_by is identified by This property identifies a name used specifically to identify an E39 Actor. \nThis property is a specialisation of P1 is identified by (identifies) is identified by. P1_is_identified_by E39_Actor E82_Actor_Appellation P131i_identifies -P131i_identifies property identifies_actor identifies P1i_identifies E82_Actor_Appellation E39_Actor P131_is_identified_by -P132_overlaps_with property volume_overlaps_with overlaps with This symmetric property associates two instances of E92 Spacetime Volume that have some of their\nextent in common. E92_Spacetime_Volume E92_Spacetime_Volume -P133_is_separated_from property distinct_from is separated from This symmetric property associates two instances of E92 Spacetime Volume that have no extent in\ncommon. E92_Spacetime_Volume E92_Spacetime_Volume -P134_continued property continued continued This property associates two instances of E7 Activity, where the domain is considered as an intentional continuation of the range. A continuation of an activity may happen when the continued activity is still ongoing or after the continued activity has completely ended. The continuing activity may have started already before it decided to continue the other one. Continuation implies a coherence of intentions and outcomes of the involved activities. P15_was_influenced_by E7_Activity E7_Activity P134i_was_continued_by -P134i_was_continued_by property continued_by was continued by P15i_influenced E7_Activity E7_Activity P134_continued -P135_created_type property created_type created type This property identifies the E55 Type, which is created in an E83Type Creation activity. P94_has_created E83_Type_Creation E55_Type P135i_was_created_by -P135i_was_created_by property type_created_by was created by P94i_was_created_by E55_Type E83_Type_Creation P135_created_type -P136_was_based_on property based_on was based on This property identifies one or more items that were used as evidence to declare a new E55 Type.\nThe examination of these items is often the only objective way to understand the precise characteristics of a new Type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the Type, such as "holotype" or "original element". P15_was_influenced_by E83_Type_Creation E1_CRM_Entity P136i_supported_type_creation -P136i_supported_type_creation property supported_type_creation supported type creation P15i_influenced E1_CRM_Entity E83_Type_Creation P136_was_based_on -P137_exemplifies property exemplifies exemplifies This property allows an item to be declared as a particular example of an E55 Type or taxon\n The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the Type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic role "lectotype" is not associated with the Type Creation (E83) itself, but selected in a later phase. P2_has_type E1_CRM_Entity E55_Type P137i_is_exemplified_by -P137i_is_exemplified_by property exemplified_by is exemplified by P2i_is_type_of E55_Type E1_CRM_Entity P137_exemplifies -P138_represents property represents represents This property establishes the relationship between an E36 Visual Item and the entity that it visually represents.\nAny entity may be represented visually. This property is part of the 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, which is shortcut by P62depicts (is depicted by). P138.1 mode of representation allows the nature of the representation to be refined.\nThis property is also used for the relationship between an original and a digitisation of the original by the use of techniques such as digital photography, flatbed or infrared scanning. Digitisation is here seen as a process with a mechanical, causal component rendering the spatial distribution of structural and optical properties of the original and does not necessarily include any visual similarity identifiable by human observation. P67_refers_to E36_Visual_Item E1_CRM_Entity P138i_has_representation -P138i_has_representation property representation has representation P67i_is_referred_to_by E1_CRM_Entity E36_Visual_Item P138_represents -P139_has_alternative_form property alternative_form has alternative form This property establishes a relationship of equivalence between two instances of E41 Appellation independent from any item identified by them. It is a dynamic asymmetric relationship, where the range expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. The relationship is not transitive.\nThe equivalence applies to all cases of use of an instance of E41 Appellation. Multiple names assigned to an object, which are not equivalent for all things identified with a specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies). \nP139.1 has type allows the type of derivation, such as “transliteration from Latin 1 to ASCII” be refined.. E41_Appellation E41_Appellation -P140_assigned_attribute_to property assigned_attribute_to assigned attribute to This property indicates the item to which an attribute or relation is assigned. E13_Attribute_Assignment E1_CRM_Entity P140i_was_attributed_by -P140i_was_attributed_by property attributed_by was attributed by E1_CRM_Entity E13_Attribute_Assignment P140_assigned_attribute_to -P141_assigned property assigned assigned 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. E13_Attribute_Assignment E1_CRM_Entity P141i_was_assigned_by -P141i_was_assigned_by property assigned_by was assigned by E1_CRM_Entity E13_Attribute_Assignment P141_assigned -P142_used_constituent property used_constituent used constituent This property associates the event of assigning an instance of E42 Identifier to an entity, with the instances of E41 Appellation that were used as elements of the identifier. P16_used_specific_object E15_Identifier_Assignment E90_Symbolic_Object P142i_was_used_in -P142i_was_used_in property used_in was used in P16i_was_used_for E90_Symbolic_Object E15_Identifier_Assignment P142_used_constituent -P143_joined property joined joined This property identifies the instance of E39 Actor that becomes member of a E74 Group in an E85 Joining.\n Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through P144 joined with (gained member by), E85 Joining, P143 joined (was joined by) to E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of). P11_had_participant E85_Joining E39_Actor P143i_was_joined_by -P143i_was_joined_by property joined_by was joined by P11i_participated_in E39_Actor E85_Joining P143_joined -P144_joined_with property joined_with joined with This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining.\nAlthough a Joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. \nJoining events allow for describing people becoming members of a group with a more detailed path from E74 Group through P144 joined with (gained member by), E85 Joining, P143 joined (was joined by) to E39 Actor, compared to the shortcut offered by P107 has current or former member (is current or former member of).\nThe property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group. P11_had_participant E85_Joining E74_Group P144i_gained_member_by -P144i_gained_member_by property gained_member_by gained member by P11i_participated_in E74_Group E85_Joining P144_joined_with -P145_separated property separated separated This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving. P11_had_participant E86_Leaving E39_Actor P145i_left_by -P145i_left_by property left_by left by P11i_participated_in E39_Actor E86_Leaving P145_separated -P146_separated_from property separated_from separated from This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving.\nAlthough a Leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well. P11_had_participant E86_Leaving E74_Group P146i_lost_member_by -P146i_lost_member_by property lost_member_by lost member by P11i_participated_in E74_Group E86_Leaving P146_separated_from -P147_curated property curated curated This property associates an instance of E87 Curation Activity with the instance of E78 Collection that is subject of that curation activity. E87_Curation_Activity E78_Collection P147i_was_curated_by -P147i_was_curated_by property curated_by was curated by E78_Collection E87_Curation_Activity P147_curated -P148_has_component property component has component 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. E89_Propositional_Object E89_Propositional_Object P148i_is_component_of -P148i_is_component_of property component_of is component of E89_Propositional_Object E89_Propositional_Object P148_has_component -P149_is_identified_by property concept_identified_by is identified by This property identifies an instance of E28 Conceptual Object using an instance of E75 Conceptual Object Appellation. P1_is_identified_by E28_Conceptual_Object E75_Conceptual_Object_Appellation P149i_identifies -P149i_identifies property identifies_concept identifies P1i_identifies E75_Conceptual_Object_Appellation E28_Conceptual_Object P149_is_identified_by -P150_defines_typical_parts_of property defines_typical_parts_of defines typical parts of This property associates an instance of E55 Type “A” with an instance of E55 Type “B”, when items\nof type “A” typically form part of items of type “B”, such as “car motors” and “cars”.\nIt allows types to be organised into hierarchies based on one type describing a typical part of another.\nThis property is equivalent to "broader term partitive (BTP)" as defined in ISO 2788 and\n“broaderPartitive” in SKOS. E55_Type E55_Type P150i_defines_typical_wholes_for -P150i_defines_typical_wholes_for property defines_typical_wholes_for defines typical wholes for E55_Type E55_Type P150_defines_typical_parts_of -P151_was_formed_from property formed_from was formed from This property associates an instance of E66 Formation with an instance of E74 Group from which the new group was formed preserving a sense of continuity such as in mission, membership or tradition. P11_had_participant E66_Formation E74_Group P151i_participated_in -P151i_participated_in property participated_in_formation participated in P11i_participated_in E74_Group E66_Formation P151_was_formed_from -P152_has_parent property parent has parent This property associates an instance of E21 Person with another instance of E21 Person who plays the role of the first instance’s parent, regardless of whether the relationship is biological parenthood, assumed or pretended biological parenthood or an equivalent legal status of rights and obligations obtained by a social or legal act. \n This property is, among others, a shortcut of the fully developed paths from ‘E21Person’ through ‘P98i was born’, ‘E67 Birth’, ‘P96 by mother’ to ‘E21 Person’, and from ‘E21Person’ through ‘P98i was born’, ‘E67 Birth’, ‘P97 from father’ to ‘E21 Person’. E21_Person E21_Person P152i_is_parent_of -P152i_is_parent_of property parent_of is parent of E21_Person E21_Person P152_has_parent -P156_occupies property occupies occupies This property describes the largest volume in space that an instance of E18 Physical Thing has occupied at any time during its existence, with respect to the reference space relative to itself. This allows you to describe the thing itself as a place that may contain other things, such as a box that may contain coins. In other words, it is the volume that contains all the points which the thing has covered at some time during its existence. In the case of an E26 Physical Feature the default reference space is the one in which the object that bears the feature or at least the surrounding matter of the feature is at rest. In this case there is a 1:1 relation of E26 Feature and E53 Place. For simplicity of implementation multiple inheritance (E26 Feature IsA E53 Place) may be a practical approach.\n\nFor instances of E19 Physical Objects the default reference space is the one which is at rest to the object itself, i.e. which moves together with the object. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces. \n\nThis property is a subproperty of P161 has spatial projection because it refers to its own domain as reference space for its range, whereas P161 has spatial projection may refer to a place in terms of any reference space. For some instances of E18 Physical Object the relative stability of form may not be sufficient to define a useful local reference space, for instance for an amoeba. In such cases the fully developed path to an external reference space and using a temporal validity component may be adequate to determine the place they have occupied.\n\nIn contrast to P156 occupies, the property P53 has former or current location identifies an instance of E53 Place at which a thing is or has been for some unspecified time span. Further it does not constrain the reference space of the referred instance of P53 Place. P161_has_spatial_projection E18_Physical_Thing E53_Place P156i_is_occupied_by -P156i_is_occupied_by property occupied_by is occupied by E53_Place E18_Physical_Thing P156_occupies -P157_is_at_rest_relative_to property at_rest_relative_to is at rest relative to This property associates an instance of P53 Place with the instance of E18 Physical Thing that determines a reference space for this instance of P53 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. P59i_is_located_on_or_within E53_Place E18_Physical_Thing P157i_provides_reference_space_for -P157i_provides_reference_space_for property provides_reference_space_for provides reference space for P59_has_section E18_Physical_Thing E53_Place P157_is_at_rest_relative_to -P160_has_temporal_projection property temporal_projection has temporal projection This property describes the temporal projection of an instance of an E92 Spacetime Volume. The property P4 has time-span is the same as P160 has temporal projection if it is used to document an instance of E4 Period or any subclass of it. E92_Spacetime_Volume E52_Time-Span -P161_has_spatial_projection property spatial_projection has spatial projection This property associates an instance of a E92 Spacetime Volume with an instance of E53 Place that is the result of the spatial projection of the instance of a E92 Spacetime Volume on a reference space. In general there can be more than one useful reference space to describe the spatial projection of a spacetime volume, such as that of a battle ship versus that of the seafloor. Therefore the projection is not unique.\nThis is part of the fully developed path that is shortcut by P7took place at (witnessed).The more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. E92_Spacetime_Volume E53_Place -P164_during property during during This property relates an instance of E93 Presence with an arbitrary instance of E52 Time-Span that\ndefines the section of the spacetime volume that this instance of E93 Presence is related to by the property P166 was a presence of (had presence). P160_has_temporal_projection E93_Presence E52_Time-Span P164i_was_time-span_of -P164i_was_time-span_of property timespan_of_presence was time-span of E52_Time-Span E93_Presence P164_during -P165_incorporates property incorporates incorporates This 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.\nThis 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.\nIt 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.\nIn 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.\nA digital photograph of a manuscript page incorporates the text of the manuscript page. P106_is_composed_of E73_Information_Object E90_Symbolic_Object P165i_is_incorporated_in -P165i_is_incorporated_in property included_in is incorporated in P106i_forms_part_of E90_Symbolic_Object E73_Information_Object P165_incorporates -P166_was_a_presence_of property a_presence_of was a presence of This property relates an E93 Presence with the STV it is part of… E93_Presence E92_Spacetime_Volume P166i_had_presence -P166i_had_presence property presence had presence E92_Spacetime_Volume E93_Presence P166_was_a_presence_of -P167_at property at at This property points to a wider area in which my thing /event was… E93_Presence E53_Place P167i_was_place_of -P167i_was_place_of property place_of was place of E53_Place E93_Presence P167_at -P168_place_is_defined_by property place_is_defined_by place is defined by This property associates an instance of E53 Place with an instance of E94 Space Primitive that defines it. Syntactic variants or use of different scripts may result in multiple instances of E94 Space Primitive defining exactly the same place. Transformations between different reference systems in general result in new definitions of places approximating each other and not in alternative definitions. Note that it is possible for a place to be defined by phenomena causal to it or other forms of identification rather than by an instance of E94 Space Primitive. In this case, this property must not be used for approximating the respective instance of E53 Place with an instance of E94 Space Primitive. E53_Place E92_Spacetime_Volume P168i_defines_place -P168i_defines_place property defines_place defines place E92_Spacetime_Volume E53_Place P168_place_is_defined_by -P81a_end_of_the_begin property end_of_the_begin end of the begin This is defined as the first boundary of the property P81 P81_ongoing_throughout E52_Time-Span xsd:dateTime -P81b_begin_of_the_end property begin_of_the_end begin of the end This is defined as the second boundary of the property P81 P81_ongoing_throughout E52_Time-Span xsd:dateTime -P82a_begin_of_the_begin property begin_of_the_begin begin of the begin This is defined as the first boundary of the property P82 P82_at_some_time_within E52_Time-Span xsd:dateTime -P82b_end_of_the_end property end_of_the_end end of the end This is defined as the second boundary of the property P82 P82_at_some_time_within E52_Time-Span xsd:dateTime -P179_had_sales_price property sales_price had sales price E96_Purchase P179i_was_sales_price_of -P179i_was_sales_price_of property sales_price_of was sales price of E97_Monetary_Amount P179_had_sales_price -P180_has_currency property currency has currency E97_Monetary_Amount P180i_was_currency_of -P180i_was_currency_of property currency_of was currency of E98_Currency P180_has_currency \ No newline at end of file diff --git a/cidoc_orm.py b/crom/cidoc_orm.py similarity index 96% rename from cidoc_orm.py rename to crom/cidoc_orm.py index f68e4ea..79bde70 100644 --- a/cidoc_orm.py +++ b/crom/cidoc_orm.py @@ -4,8 +4,7 @@ import codecs import inspect -# ### Mappings for duplicate properties ### - +### Mappings for duplicate properties ### ### See build_tsv/vocab_reader try: @@ -84,14 +83,18 @@ def __init__(self, base_url="", base_dir="", lang="", context="", full_names=Fal self.key_order_hash = {"@context": 0, "id": 1, "type": 2, "classified_as": 3, "label": 4, "value": 4, "note": 5, "description": 5, "identified_by": 10, + "carried_out_by": 18, "used_specific_object": 19, "timespan": 20, "begin_of_the_begin": 21, "end_of_the_begin": 22, "begin_of_the_end": 23, "end_of_the_end": 24, + "started_by": 25, "finished_by": 28, "height": 30, "width": 31, "paid_amount": 50, "paid_from": 51, "paid_to": 52, "transferred_title_of": 50, "transferred_title_from": 51, "transferred_title_to": 52, + + "offering_price": 48, "sales_price": 49, "consists_of": 100, "composed_of": 101 @@ -161,7 +164,7 @@ def _buildString(self, js, compact=True): else: out = json.dumps(js, indent=2) except UnicodeDecodeError: - print "Can't decode %r" % js + self.maybe_warn("Can't decode %r" % js) out = "" return out @@ -273,7 +276,7 @@ def __setattr__(self, which, value): def _check_prop(self, which, value): for c in self._classhier: - if c._properties.has_key(which): + if which in c._properties: rng = c._properties[which]['range'] if rng == str: return 1 @@ -287,7 +290,7 @@ def _list_all_props(self): props = {} for c in self._classhier: for k,v in c._properties.items(): - if not props.has_key(k): + if not k in props: props[k] = v['range'] return props @@ -304,13 +307,13 @@ def _check_reference(self, data): return True elif type(data) == list: for d in data: - if type(d) in STR_TYPES and not data.startswith('http'): + if type(d) in STR_TYPES and not d.startswith('http'): return False elif type(d) == dict and not 'id' in d: return False return True else: - print("expecing a resource, got: %r" % (data)) + self._factory.maybe_warn("expecing a resource, got: %r" % (data)) return True def maybe_warn(self, msg): @@ -334,7 +337,7 @@ def _set_magic_lang(self, which, value): if type(value) != dict: raise DataError("Should be a dict or a string") for k,v in value.items(): - if current.has_key(k): + if k in current: cv = current[k] if type(cv) != list: cv = [cv] @@ -367,9 +370,9 @@ def _set_magic_resource(self, which, value, inversed=False): # set the backwards ref inverse = None for c in self._classhier: - if c._properties.has_key(which): + if which in c._properties: v = c._properties[which] - if v.has_key('inverse'): + if inverse in v: inverse = v['inverse'] break if inverse: @@ -380,7 +383,7 @@ def _toJSON(self, top=False): # If we're already in the graph, return our URI only # This should only be called from the factory! - if self._factory.done.has_key(self.id): + if self.id in self._factory.done: return self.id d = self.__dict__.copy() @@ -431,20 +434,20 @@ def _toJSON(self, top=False): for (k,v) in d.items(): # look up the rdf predicate in _properties for c in reversed(self._classhier): - if c._properties.has_key(k): + if k in c._properties: nk = c._properties[k]['rdf'] nd[nk] = v break # Ensure full version uses basic @type - if nd.has_key("rdf:type"): + if "rdf:type" in nd: nd['@type'] = nd['rdf:type'] del nd['rdf:type'] # And type gets ganked for overlay classes (Painting) # plus for stupidity classes (DestructionActivity) # so add this back too - if not nd.has_key('@type') or not nd['@type']: + if not "@type" in nd or not nd['@type']: # find class up that has a type and use its name for c in reversed(self._classhier): if c._type: @@ -454,7 +457,7 @@ def _toJSON(self, top=False): KOH = self._factory.full_key_order_hash else: # Use existing programmer-friendly names for classes too - if not d.has_key('type'): + if not type in d: # find class up that has a type and use its name for c in self._classhier: if c._type: @@ -510,7 +513,7 @@ def build_class(crmName, parent, vocabData): name = str(data['className']) # check to see if we already exist - if globals().has_key(name): + if name in globals(): c = globals()[name] c.__bases__ += (parent,) return diff --git a/vocab_mapping.py b/crom/vocab_mapping.py similarity index 93% rename from vocab_mapping.py rename to crom/vocab_mapping.py index d3ffb5f..cc4f9bc 100644 --- a/vocab_mapping.py +++ b/crom/vocab_mapping.py @@ -5,7 +5,7 @@ ConceptualObject, TimeSpan, Actor, PhysicalThing, \ LinguisticObject, InformationObject, SpatialCoordinates, \ Activity, Group, Appellation, MonetaryAmount, Purchase, \ - Destruction + Destruction, AttributeAssignment def register_aat_class(name, parent, id): c = type(name, (parent,), {}) @@ -55,6 +55,13 @@ def register_aat_dimensionUnit(name, id): "Nationality": {"parent": Group, "vocab":"aat", "id":"300379842"}, "Auction": {"parent": Activity, "vocab": "aat", "id": "300054751"}, + "Curating": {"parent": Activity, "vocab": "aat", "id": "300054277"}, + "Inventorying": {"parent": Activity, "vocab": "aat", "id": "300077506"}, + "Provenance": {"parent": Activity, "vocab": "aat", "id": "300055863"}, + + "Attribution": {"parent": AttributeAssignment, "vocab": "aat", "id": "300056109"}, + "Appraising": {"parent": AttributeAssignment, "vocab": "aat", "id": "300054622"}, + "Dating": {"parent": AttributeAssignment, "vocab": "aat", "id": "300054714"}, "SupportPart": {"parent": PhysicalThing, "vocab":"aat", "id":"300014844"}, "FramePart": {"parent": PhysicalThing, "vocab":"aat", "id":"300404391"}, diff --git a/build_tsv/crm_vocab.tsv b/data/crm_vocab.tsv similarity index 100% rename from build_tsv/crm_vocab.tsv rename to data/crm_vocab.tsv diff --git a/example.py b/examples/example.py similarity index 100% rename from example.py rename to examples/example.py diff --git a/requirements.txt b/requirements.txt new file mode 100644 index 0000000..932a895 --- /dev/null +++ b/requirements.txt @@ -0,0 +1 @@ +mock diff --git a/setup.py b/setup.py new file mode 100644 index 0000000..929cb5e --- /dev/null +++ b/setup.py @@ -0,0 +1,22 @@ +from setuptools import setup, find_packages + +setup( + name = 'crmpy', + packages = find_packages(), + test_suite="test", + version = '0.0.1', + description = 'A library for mapping CIDOC-CRM classes to Python objects', + author = 'Getty Research Institute', + author_email = 'jgomez@getty.edu', + url = 'https://github.com/gri-is/crmpy', + classifiers = [ + "Programming Language :: Python", + "Programming Language :: Python :: 3", + "Programming Language :: Python :: 2", + "License :: OSI Approved :: Apache License", + "Development Status :: pre-Alpha", + "Intended Audience :: Developers", + "Operating System :: OS Independent", + "Topic :: Software Development :: Libraries :: Python Modules", + ] +) diff --git a/build_tsv/cidoc.xml b/utils/cidoc.xml similarity index 100% rename from build_tsv/cidoc.xml rename to utils/cidoc.xml diff --git a/crm_context.jsonld b/utils/crm_context.jsonld similarity index 100% rename from crm_context.jsonld rename to utils/crm_context.jsonld diff --git a/build_tsv/make_inverses.py b/utils/make_inverses.py similarity index 100% rename from build_tsv/make_inverses.py rename to utils/make_inverses.py diff --git a/make_jsonld_context.py b/utils/make_jsonld_context.py similarity index 100% rename from make_jsonld_context.py rename to utils/make_jsonld_context.py