CRM Entity
type: Class
notation: E1
comment: This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model. It is an abstract concept providing for three general properties: Identification by name or appellation, and in particular by a preferred identifier Classification by type, allowing further refinement of the specific subclass an instance belongs to Attachment of free text for the expression of anything not captured by formal properties With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
subclass of: Thing

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

Period
type: Class
notation: E4
comment: This class comprises sets of coherent phenomena or cultural manifestations occurring in time and space. It 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. Often, 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. As 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 disconnec…
subclass of: Temporal Entity
subclass of: Spacetime Volume

Event
type: Class
notation: E5
comment: This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses. The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
subclass of: Period

Activity
type: Class
notation: E7
comment: This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door.
subclass of: Event

Modification
type: Class
notation: E11
comment: This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing. This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation. Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities. If the instance of the E29 Design or Procedure 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.
subclass of: Activity

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

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

Identifier Assignment
type: Class
notation: E15
comment: This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure. Examples 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. The 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.
subclass of: Attribute Assignment

Physical Thing
type: Class
notation: E18
comment: This class comprises all persistent physical items with a relatively stable form, man-made or natural. Depending on the existence of natural boundaries of such things, the CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter. An 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. We 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. The CIDOC C…
subclass of: Legal Object
subclass of: Spacetime Volume

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

Man-Made Object
type: Class
notation: E22
comment: This class comprises physical objects purposely created by human activity. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, an inscribed piece of rock or a preserved butterfly are both regarded as instances of E22 Man-Made Object.
subclass of: Physical Object
subclass of: Physical Man-Made Thing

Physical Man-Made Thing
type: Class
notation: E24
comment: This class comprises all persistent physical items that are purposely created by human activity. This class comprises man-made objects, such as a swords, and man-made features, such as rock art. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Man-Made Thing.
subclass of: Physical Thing
subclass of: Man-Made Thing

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

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

Right
type: Class
notation: E30
comment: This class comprises legal privileges concerning material and immaterial things or their derivatives. These include reproduction and property rights
subclass of: Propositional Object

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

Appellation
type: Class
notation: E41
comment: This class comprises signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class or category within a certain context. Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but instead by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes. Specific subclasses of E41 Appellation should be used when instances of E41 Appellation of a characteristic form are used for particular objects. Instances of E49 Time Appellation, for example, which take the form of instances of E50 Date, can be easily recognised. E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment
subclass of: Symbolic Object

Identifier
type: Class
notation: E42
comment: 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.
subclass of: Appellation

Time-Span
type: Class
notation: E52
comment: This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration. Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation. Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known. Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
subclass of: CRM Entity

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

Type
type: Class
notation: E55
comment: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes. E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
subclass of: Conceptual Object

Language
type: Class
notation: E56
comment: This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts. This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”. It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
subclass of: Type

Material
type: Class
notation: E57
comment: This class is a specialization of E55 Type and comprises the concepts of materials. Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of). This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”. It is recommended that internationally or nationally agreed codes and terminology are used.
subclass of: Type

Primitive Value
type: Class
notation: E59
comment: This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.They are not considered as elements of the universe of discourse this model aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.In particular they comprise lexical forms encoded as "strings" or series of characters and symbols based on encoding schemes (characterised by being a limited subset of the respective mathematical abstractions) such as UNICODE and values of datatypes that can be encoded in a lexical form, including quantitative specifications of time-spans and geometry. They have in common that instances of E59 Primitive Value define themselves by virtue of their encoded value, regardless the nature of their mathematical abstractions.Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class and its subclasses.
subclass of: Thing

Number
type: Class
notation: E60
comment: This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision. Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
subclass of: Primitive Value

String
type: Class
notation: E62
comment: This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc. E62 String is not further elaborated upon within the model
subclass of: Primitive Value

Beginning of Existence
type: Class
notation: E63
comment: This class comprises events that bring into existence any E77 Persistent Item. It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
subclass of: Event

Creation
type: Class
notation: E65
comment: 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.
subclass of: Activity
subclass of: Beginning of Existence

Thing
type: Class
notation: E70
comment: 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. They may be intellectual products or physical things. They may for instance have a solid physical form, an electronic encoding, or they may be a logical concept or structure.
subclass of: Persistent Item

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

Legal Object
type: Class
notation: E72
comment: This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied. This is true for all E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of the E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CRM.
subclass of: Thing

Information Object
type: Class
notation: E73
comment: 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.An E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression.
subclass of: Propositional Object
subclass of: Symbolic Object

Group
type: Class
notation: E74
comment: 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. A gathering of people becomes an E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be 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.
subclass of: Actor

Persistent Item
type: Class
notation: E77
comment: This class comprises items that have a persistent identity, sometimes known as “endurants” in philosophy. They can be repeatedly recognized within the duration of their existence by identity criteria rather than by continuity or observation. Persistent Items can be either physical entities, such as people, animals or things, or conceptual entities such as ideas, concepts, products of the imagination or common names. The criteria that determine the identity of an item are often difficult to establish -; the decision depends largely on the judgement of the observer. For example, a building is regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria. Similarly, inanimate objects may be subject to exchange of parts and matter. The class E77 Persistent Item does not take any position about the nature of the applicable identity criteria and if actual knowledge about identity of an instance of this class exists. There may be cases, where the identity of an E77 Persistent Item is not decidable by a certain state of knowledge.The main classes of objects that fall outside the scope the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties.
subclass of: CRM Entity

Information Carrier
type: Class
notation: E84
comment: This class comprises all instances of E22 Man-Made Object that are explicitly designed to act as persistent physical carriers for instances of E73 Information Object. An E84 Information Carrier may or may not contain information, e.g., a diskette. Note that any E18 Physical Thing may carry information, such as an E34 Inscription. However, unless it was specifically designed for this purpose, it is not an Information Carrier. Therefore the property P128 carries (is carried by) applies to E18 Physical Thing in general.
subclass of: Man-Made Object

Propositional Object
type: Class
notation: E89
comment: 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. This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
subclass of: Conceptual Object

Symbolic Object
type: Class
notation: E90
comment: This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units. It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string. In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).
subclass of: Conceptual Object
subclass of: Legal Object

Spacetime Volume
type: Class
notation: E92
comment: This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of 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. 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.
subclass of: CRM Entity

Work
type: Class
notation: F1
comment: This class comprises distinct concepts or combinations of concepts identified in artistic and intellectual expressions, such as poems, stories or musical compositions. Such concepts may appear in the course of the coherent evolution of an original idea into one or more expressions that are dominated by the original idea. A Work may be elaborated by one or more Actors simultaneously or over time. The substance of Work is ideas. A Work may have members that are works in their own right. A Work can be either individual or complex. If it is individual its concept is completely realised in a single F22 Self-Contained Expression. If it is complex its concept is embedded in an F15 Complex Work. An F15 Complex Work consists of alternative members that are either F15 Complex Works themselves or F14 Individual Works. A Work is the product of an intellectual process of one or more persons, yet only indirect evidence about it is at our hands. This can be contextual information such as the existence of an order for a work, reflections of the creators themselves that are documented somewhere, and finally the expressions of the work created. As ideas normally take shape during discussion, elaboration and implementation, it is not reasonable to assume that a work starts with a complete concept. In some cases, it can be very difficult or impossible to define the whole of the concept of a work at a particular time. The objective evidence for such a notion can only be based on a stage of expressions at a given time. In this sense, the sets of ideas that constitute particular self-contained expressions may be regarded as a kind of “snap-shot” of a work. A Work may include the concept of aggregating expressions of other works into a new expression. For instance, an anthology of poems is regarded as a work in its own right that makes use of expressions of the individual poems that have been selected and ordered as part of an intellectual process. This does not make the contents of the ag…
subclass of: Propositional Object

Expression
type: Class
notation: F2
comment: This class comprises the intellectual or artistic realisations of works in the form of identifiable immaterial objects, such as texts, poems, jokes, musical or choreographic notations, movement pattern, sound pattern, images, multimedia objects, or any combination of such forms that have objectively recognisable structures. The substance of F2 Expression is signs. Expressions cannot exist without a physical carrier, but do not depend on a specific physical carrier and can exist on one or more carriers simultaneously. Carriers may include human memory. Inasmuch as the form of F2 Expression is an inherent characteristic of the F2 Expression, any change in form (e.g., from alpha-numeric notation to spoken word, a poem created in capitals and rendered in lower case) is a new F2 Expression. Similarly, changes in the intellectual conventions or instruments that are employed to express a work (e.g., translation from one language to another) result in the creation of a new F2 Expression. Thus, if a text is revised or modified, the resulting F2 Expression is considered to be a new F2 Expression. Minor changes, such as corrections of spelling and punctuation, etc., are normally considered variations within the same F2 Expression. On a practical level, the degree to which distinctions are made between variant expressions of a work will depend to some extent on the nature of the F1 Work itself, and on the anticipated needs of users. The genre of the work may provide an indication of which features are essential to the expression. In some cases, aspects of physical form, such as typeface and page layout, are not integral to the intellectual or artistic realisation of the work as such, and therefore are not distinctive criteria for the respective expressions. For another work, features such as layout may be essential. For instance, the author or a graphic designer may wrap a poem around an image. An expression of a work may include expressions of other works within it. For instan…
subclass of: Information Object

Manifestation Product Type
type: Class
notation: F3
comment: This class comprises the definitions of publication products. An instance of F3 Manifestation Product Type is the “species”, and all copies of a given object are “specimens” of it. An instance of F3 Manifestation Product Type defines all of the features or traits that instances of F5 Item normally display in order that they may be recognised as copies of a particular publication. However, due to production problems or subsequent events, one or more instances of F5 Item may not exhibit all these features or traits; yet such instances still retain their relationship to the same instance of F3 Manifestation Product Type. The features that characterise a given instance of F3 Manifestation Product Type include: one instance of F24 Publication Expression, containing one or more than one instance of F2 Expression, reflecting the authors’ content of the manifestation and all additional input by the publisher; and the appropriate types of physical features for that form of the object. For example, hardcover and paperback are two distinct publications (i.e. two distinct instances of F3 Manifestation Product Type) even though authorial and editorial content are otherwise identical in both publications. The activity of cataloguing aims at the most accurate listing of features or traits of an instance of F3 Manifestation Product Type that are sufficient to distinguish it from another instance of F3 Manifestation Product Type.
subclass of: Type
subclass of: Legal Object

Manifestation Singleton
type: Class
notation: F4
comment: This class comprises physical objects that each carry an instance of F2 Expression, and that were produced as unique objects, with no siblings intended in the course of their production. It should be noted that if all but one copy of a given publication are destroyed, then that copy does not become an instance of F4 Manifestation Singleton, because it was produced together with sibling copies, even though it now happens to be unique. Examples of instances of F4 Manifestation Singleton include manuscripts, preparatory sketches and the final clean draft sent by an author or a composer to a publisher.
subclass of: Physical Man-Made Thing

Item
type: Class
notation: F5
comment: This class comprises physical objects (printed books, scores, CDs, DVDs, CD-ROMS, etc.) that carry a F24 Publication Expression and were produced by an industrial process involving an F3 Manifestation Product Type.
subclass of: Utilized Information Carrier

Concept
type: Class
notation: F6
comment: An abstract notion or idea. [FRBRER] Includes fields of knowledge, disciplines, schools of thought (philosophies, religions, political ideologies, etc.), etc. Includes theories, processes, techniques, practices, etc. [Definition from the FRAD model, unchanged] This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation or historical implication. The production of such information may have been supported by the use of technical devices such as cameras or computers. Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc. They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost. [Scope note for E28 Conceptual Object in CIDOC CRM version 5.0.1]
subclass of: Conceptual Object

Object
type: Class
notation: F7
comment: This class comprises all persistent physical items with a relatively stable form, man-made or natural. [This is the beginning of scope note for E18 Physical Object in CIDOC CRM version 5.0.1]
subclass of: Physical Thing

Event
type: Class
notation: F8
comment: This class comprises sets of coherent phenomena or cultural manifestations bounded in time and space. It is the social or physical coherence of these phenomena that identify an E4 Period and not the associated spatio-temporal bounds. These bounds are a mere approximation of the actual process of growth, spread and retreat. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area as a sedentary culture. Typically this class is used to describe prehistoric or historic periods such as the ‘Neolithic Period’, the ‘Ming Dynasty’ or the ‘McCarthy Era’. There are however 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. There are two different conceptualisations of “artistic style”, defined either by physical features or by historical context. For example, Impressionism can be viewed as a period lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an E4 Period, and the second defines morphological object types that fall under E55 Type. Another specific case of an E4 Period is the set of activities and phenomena associated with a settlement, such as the populated period of Nineveh. [This is the Scope note for E4 Period in CIDOC CRM version 5.0.1] [Note that in CIDOC CRM, E12 Production, E13 Attribute Assignment, and …
subclass of: Period

Place
type: Class
notation: F9
comment: This class comprises extents in space, in particular on the surface of the Earth, in the pure sense of physics: independent from temporal phenomena and matter. The instances of E53 Place are usually determined by reference to the position of immobile objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation. It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance. Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a section of an E19 Physical Object as a valid E53 Place determination. [Scope Note for E53 Place in CIDOC CRM version 5.0.1] Note that Places may be determined by the location of historical or contemporary objects, geographic features, events or geo-political units.

Person
type: Class
notation: F10
comment: This class comprises real persons who live or are assumed to have lived. Bibliographic identities or personae assumed by an individual or a group should be modelled as F12 Nomen and connected to the relevant person or group with an instance of F35 Nomen Use Statement, even if nothing more can be said about this person or group. In a bibliographic context, a name presented following the conventions usually employed for personal names will be assumed to correspond to an actual real person (F10 Person), unless evidence is available to indicate that this is not the case. The fact that a persona may erroneously be classified as an instance of F10 Person does not imply that the concept comprises personae

Corporate Body
type: Class
notation: F11
comment: This class comprises organisations and groups of two or more people and/or organisations acting as a unit. To be considered an F11 Corporate Body a gathering of people needs to bear a name and exhibit organisational characteristics sufficient to allow the body as a whole to participate in the creation, modification or production of an E73 Information Object. Groups such as conferences, congresses, expeditions, exhibitions, festivals, fairs, etc. are modelled as F11 Corporate Bodies when they are named and can take collective action, such as approving a report or publishing their proceedings.
subclass of: Group

Nomen
type: Class
notation: F12
comment: This class comprises any sign or arrangements of signs following a specific syntax (sequences of alphanumeric characters, chemical structure symbols, sound symbols, ideograms etc.) that are used or can be used to refer to and identify a specific instance of some class or category within a certain context. The scripts or type sets for the types of symbols used to compose an instance of F12 Nomen have to be explicitly specified. The identity of an instance of F12 Nomen is given by the order of its symbols and their individual role with respect to their scripts, regardless of the semantics of the larger structural components it may be built from. Structural tags occurring in the nomen string are regarded as symbols constituting the nomen. Spelling variants are regarded as different nomina, whereas the use of different fonts (visual representation variants) or different digital encodings do not change the identity.
subclass of: Appellation

Identifier
type: Class
notation: F13
comment: This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents. [Adapted from the Scope Note of CIDOC CRM E42 Identifier ver. 5.0.1]
subclass of: Identifier
subclass of: Nomen

Individual Work
type: Class
notation: F14
comment: This class comprises works that are realised by one and only one self-contained expression, i.e., works representing the concept as expressed by precisely this expression. Inherent to the notion of work is the completion of recognisable outcomes of the work. These outcomes, i.e. the Self-Contained Expressions, are regarded as the symbolic equivalents of Individual Works, which form the atoms of a complex work. Normally creators would characterise an outcome of a work as finished. In other cases, one could recognise an outcome of a work as complete from the elaboration or logical coherence of its content, or if there is any historical knowledge about the creator deliberately or accidentally never finishing (completing) that particular expression. In all those cases, one would regard the corresponding expression as equivalent to one Individual Work.
subclass of: Work

Complex Work
type: Class
notation: F15
comment: This class comprises works that have other works as members. The members of a Complex Work may constitute alternatives to, derivatives of, or self-contained components of other members of the same Complex Work. In practice, no clear line can be drawn between parallel and subsequent processes in the evolution of a work. One part may not be finished when another is already revised. An initially monolithic work may be taken up and evolve in pieces. The member relationship of Work is based on the conceptual relationship, and should not be confused with the internal structural parts of an individual expression. The fact that an expression may contain parts from other work(s) does not make the expressed work complex. For instance, an anthology for which only one version exists is not a complex work. The boundaries of a Complex Work have nothing to do with the value of the intellectual achievement but only with the dominance of a concept. Thus, derivations such as translations are regarded as belonging to the same Complex Work, even though in addition they constitute an Individual Work themselves. In contrast, a Work that significantly takes up and merges concepts of other works so that it is no longer dominated by the initial concept is regarded as a new work. In cataloguing practice, detailed rules are established prescribing which kinds of derivation should be regarded as crossing the boundaries of a complex work. Adaptation and derivation graphs allow the recognition of distinct sub-units, i.e. a complex work contained in a larger complex work. As a Complex Work can be taken up by any creator who acquires the spirit of its concept, it is never finished in an absolute sense.
subclass of: Work

Container Work
type: Class
notation: F16
comment: This class comprises works whose essence is to enhance or add value to expressions from one or more other works without altering them, by the selection, arrangement and/or addition of features of different form, such as layout to words, recitation and movement to texts, performance to musical scores etc. This does not make the contents of the incorporated expressions part of the Container Work, but only part of the resulting expression. Container Work may include the addition of new, original parts to the incorporated expressions, such as introductions, graphics, etc. This class is an “abstract class,” in that it only serves as an umbrella for its three subclasses. As a consequence, it can only be instantiated by instances of any of its subclasses: nothing can be an instance of it, unless it is an instance of either F17 Aggregation Work, F19 Publication Work, or F20 Performance Work. A new version of a container work does not make the resulting complex work a Container Work as well. The inclusion of expressions from a complex work in a Container Work does not make the Container Work itself complex.
subclass of: Work

Aggregation Work
type: Class
notation: F17
comment: This class comprises works whose essence is the selection and/or arrangement of expressions of one or more other works. This does not make the contents of the aggregated expressions part of this work, but only part of the resulting expression. F17 Aggregation Work may include additional original parts. An expression of a work may include expressions of other works within it. For instance, an anthology of poems is regarded as a work in its own right that makes use of expressions of the individual poems that have been selected and ordered as part of an intellectual process. A new version of an aggregate work does not make the resulting complex work an aggregate work as well. The inclusion of expressions from a complex work in an aggregation work does not make the aggregation work itself complex.
subclass of: Individual Work
subclass of: Container Work

Serial Work
type: Class
notation: F18
comment: This class comprises works that are, or have been, planned to result in sequences of Expressions or Manifestations with common features. Whereas a work can acquire new members during the time it evolves, Expressions and Manifestations are identified with a certain state achieved at a particular point in time. Therefore there is in general no single Expression or Manifestation representing a complete serial work, unless the serial work has ended. Serial Works may or may not have a plan for an overall expression. The retrospective reprinting of all issues of a Serial Work at once, in the form of a monograph, is regarded to be another member of a Complex Work, which contains the Serial Work and the Individual Work realised in the monograph. This does not make the monograph part of the Serial Work.
subclass of: Complex Work
subclass of: Publication Work

Publication Work
type: Class
notation: F19
comment: This class comprises works that have been planned to result in a manifestation product type or an electronic publishing service and that pertain to the rendering of expressions from other works
subclass of: Container Work

Performance Work
type: Class
notation: F20
comment: This class comprises the sets of concepts for rendering a particular or a series of like performances. F20 Performance Work is declared as a subclass of F16 Container Work. This implies that the incorporated expressions (such as the text of the staged play, the text of the argument for the ballet, the recorded music to be used for the ballet, or the content of the musical score to be used for a concert, etc.) are not by themselves a part of the expression of this F1 Work. Rather, an expression (F25 Performance Plan) of the instructions the stage production, choreography or musical performance consists of incorporates (P165) that textual or musical content. In other words, the text of ‘Hamlet’ is not a component of the concepts that underlie a given mise-en-scène of ‘Hamlet’, but any staging directions (F25 Performance Plan) that convey a given director’s vision of ‘Hamlet’ must necessarily incorporate the text of ‘Hamlet’.
subclass of: Container Work

Recording Work
type: Class
notation: F21
comment: This class comprises works that conceptualise the capturing of features of perdurants. The characteristics of the manifestation of a recording work are those of the product of the capture process. The characteristics of any other works recorded are distinct from those of the recording work itself. In the case where the recorded perdurant expresses some Work, the respective instance of F21 is also an F16 Container Work. The concept of recording is not necessarily linked to the use of modern devices that allow for mechanical recording, such as tape recorders or cameras. However, in practice, library catalogues tend to regard as recordings only the products of such mechanical devices. But the concept of recording is very much linked to the notion that there is something that is recorded. In general, photographs or animated images are not to be regarded as instances of F21 Recording Work just because of the use of the medium, but simply as instances of F1 Work (or F15 Complex Work). Only such photographs and animated images that can be used as documentation are to be regarded as recordings.
subclass of: Work

Self-Contained Expression
type: Class
notation: F22
comment: This class comprises the immaterial realisations of individual works at a particular time that are regarded as a complete whole. The quality of wholeness reflects the intention of its creator that this expression should convey the concept of the work. Such a whole can in turn be part of a larger whole. Inherent to the notion of work is the completion of recognisable outcomes of the work. These outcomes, i.e. the Self-Contained Expressions, are regarded as the symbolic equivalents of Individual Works, which form the atoms of a complex work. A Self-Contained Expression may contain expressions or parts of expressions from other work, such as citations or items collected in anthologies. Even though they are incorporated in the Self-Contained Expression, they are not regarded as becoming members of the expressed container work by their inclusion in the expression, but are rather regarded as foreign or referred to elements. F22 Self-Contained Expression can be distinguished from F23 Expression Fragment in that an F23 Expression Fragment was not intended by its creator to make sense by itself. Normally creators would characterise an outcome of a work as finished. In other cases, one could recognise an outcome of a work as complete from the elaboration or logical coherence of its content, or if there is any historical knowledge about the creator deliberately or accidentally never finishing (completing) that particular expression. In all those cases, one would regard an expression as self-contained.
subclass of: Expression

Expression Fragment
type: Class
notation: F23
comment: This class comprises parts of Expressions and these parts are not Self-Contained Expressions themselves. The existence of an instance of F23 Expression Fragment can be due to accident, such as loss of material over time, e.g. the only remaining manuscript of an antique text being partially eaten by worms, or due to deliberate isolation, such as excerpts taken from a text by the compiler of a collection of excerpts. An F23 Expression Fragment is only identified with respect to its occurrence in a known or assumed whole. The size of an instance of F23 Expression Fragment ranges from more than 99% of an instance of F22 Self-Contained Expression to tiny bits (a few words from a text, one bar from a musical composition, one detail from a still image, a two-second clip from a movie, etc.).
subclass of: Expression

Publication Expression
type: Class
notation: F24
comment: This class comprises complete sets of signs present in publications, reflecting publishers’ final decisions as to both selection of content and layout of the publications. Frequently the creation of a Publication Expression includes both adding graphical form and fonts to Expressions consisting of words alone and selecting illustrations and other content. As such, an instance of Publication Expression incorporates all Expressions combined for the resulting final form of rendering, whether visual, audio or tactile. An instance of Publication Expression is one entity regardless of the number of independent Expressions published within it, as long as it represents one unit of release. The published third party content can be associated via the property P165 incorporates (is incorporated in).
subclass of: Self-Contained Expression

Performance Plan
type: Class
notation: F25
comment: This class comprises sets of directions to which individual performances of theatrical, choreographic, or musical works and their combinations should conform. In the case of theatrical performances, such directions incorporate, but are not limited nor reducible to, the text of a given version of the play performed (e.g., a translated text, some passages of which are deliberately omitted, with some rephrased lines, etc.). In the case of choreographic performances, such directions may incorporate, but are neither limited nor reducible to, the notation of choreographic movements in systems such as labanotation. In the case of musical performances, such directions may incorporate, but are neither limited nor reducible to, the musical score. In case of electronic music, they may incorporate software instructions. These directions may or may not completely determine the form of the intended performance. Depending on the nature of the directions, the form of the intended performance, such as the sets of movements or the sound characteristics, may or may not be predictable from the directions. Note that a performance plan may be more or less elaborate, and may even foresee just improvisation.
subclass of: Design or Procedure
subclass of: Self-Contained Expression

Recording
type: Class
notation: F26
comment: This class comprises expressions which are created in instances of F29 Recording Event. A recording is intended to convey (and preserve) the features of one or more perdurants.
subclass of: Self-Contained Expression

Work Conception
type: Class
notation: F27
comment: This class comprises beginnings of evolutions of works. An instance of F27 Work Conception marks the initiation of the creation of a work. The work, as an intellectual construction, evolves from this point on, until the last known expression of it. The instance of E39 Actor with which a work is associated through the chain of properties F1 Work R16i was initiated by F27 Work Conception P14 carried out by E39 Actor corresponds to the notion of the “creator” of the work. In the case of commissioned works, it is not the commissioning that is regarded as the work conception, but the acceptance of the commission. This event does not always correlate with the date assigned in common library practice to the work, which is usually a later event (such as the date of completion of the first clean draft). In addition, F27 Work Conception can serve to document the circumstances that surrounded the appearance of the original idea for a work, when these are known.
subclass of: Creation

Expression Creation
type: Class
notation: F28
comment: This class comprises activities that result in instances of F2 Expression coming into existence. This class characterises the externalisation of an Individual Work. Although F2 Expression is an abstract entity, a conceptual object, the creation of an expression inevitably also affects the physical world: when you scribble the first draft of a poem on a sheet of paper, you produce an instance of F4 Manifestation Singleton; F28 Expression Creation is a subclass of E12 Production because the recording of the expression causes a physical modification of the carrying E18 Physical Thing. The work becomes manifest by being expressed on a physical carrier different from the creator’s brain. The spatio-temporal circumstances under which the expression is created are necessarily the same spatio-temporal circumstances under which the first instance of F4 Manifestation Singleton is produced. The mechanisms through which oral tradition (of myths, tales, music, etc.) operates are not further investigated in this model. As far as bibliographic practice is concerned, only those instances of F2 Expression that are externalised on physical carriers other than both the creator’s brain and the auditor’s brain are taken into account (for a discussion of the modelling of oral traditions, see: Nicolas, Yann. ‘Folklore Requirements for Bibliographic Records: oral traditions and FRBR.’ In: Cataloging Classification Quarterly (2005). Vol. 39, No. 3-4. P. 179-195). It is possible to use the P2 has type (is type of) property in order to specify that the creation of a given expression of a given work played a particular role with regard to the overall bibliographic history of that work (e.g., that it was the creation of the progenitor expression on which all other expressions of the same work are based; or that it was the creation of the critical edition that served as the basis for canonical references to the work).
subclass of: Production
subclass of: Creation

Recording Event
type: Class
notation: F29
comment: This class comprises activities that intend to convey (and preserve) the features of perdurants in a recording, such as a live recording of a performance, a documentary, or other capture of a perdurant. Such activities may follow the directions of a recording plan. They may include postproduction.
subclass of: Expression Creation

Publication Event
type: Class
notation: F30
comment: This class comprises the activities of publishing. Such an event includes the creation of an F24 Publication Expression and setting up the means of production. The end of this event is regarded as the date of publication, regardless of whether the carrier production is started. Publishing can be either physical or electronic. Electronic publishing is regarded as making an instance of F24 Publication Expression available in electronic form on a public network. Electronic Publishing does not mean producing a physical instance of F5 Item by partially electronic means. Making an electronic file available on a physical carrier can be regarded as equivalent to setting up the means of production; downloading the file is regarded as the electronic equivalent of F32 Carrier Production Event.
subclass of: Expression Creation

Performance
type: Class
notation: F31
comment: This class comprises activities that follow the directions of a performance plan, such as a theatrical play, an expression of a choreographic work or a musical work; i.e., they are intended to communicate directly or indirectly to an audience. Such activities can be identified at various levels of granularity, and can be contiguous or not. Any individual performance (with or without intermissions) is a single instance of F31 Performance. In addition, a complete run of performances can also be seen as an instance of F31 Performance, with individual performances as parts. A complete run of performances may comprise an original run plus any of its extensions and tours. Note that a performance plan may be more or less elaborate, and may even foresee just improvisation.
subclass of: Activity

Carrier Production Event
type: Class
notation: F32
comment: This class comprises activities that result in instances of F54 Utilised Information Carrier coming into existence. Both the production of a series of physical objects (printed books, scores, CDs, DVDs, CD-ROMS, etc.) and the creation of a new copy of a file on an electronic carrier are regarded as instances of F32 Carrier Production Event. Typically, the production of copies of a publication (no matter whether it is a book, a sound recording, a DVD, a cartographic resource, etc.) strives to produce items all as similar as possible to a prototype that displays all the features that all the copies of the publication should also display, which is reflected in property R27 used as source material F24 Publication Expression.
subclass of: Production

Reproduction Event
type: Class
notation: F33
comment: This class comprises activities that consist in making copies, more or less mechanically, of an instance of E84 Information Carrier (such as an F5 Item or an F4 Manifestation Singleton which is also instance of E84 Information Carrier), preserving the expression carried by it. A Reproduction Event results in new instances of E84 Information Carrier coming into existence. In general, the copy will have different attributes from the original and they are therefore not regarded as siblings. This class makes it possible to account for the legal distinction between private copying for the purpose of “fair use,” and mass production for the purpose of dissemination. It can prove difficult to determine where to draw the line between F33 Reproduction Event and F32 Carrier Production Event in cases where multiple copies are produced. In this case, the copies, but not the original, may be regarded as instances of F5 Item. It is the existence of an explicit production plan that makes the difference. As a consequence, F33 Reproduction Event and F32 Carrier Production Event are not declared as disjoint, which makes it possible to account for such situations that could be regarded as instances of both Production Event and Reproduction Event.
subclass of: Production

KOS
type: Class
notation: F34
comment: This class comprises documents that establish controlled terminology (nomina) for consistent use. They may also describe relationships between entities and controlled terminology and relationships between entities. Note that any meaningful change in a Knowledge Organisation System (KOS) that affects the validity status of its elements defines a new release (Expression) of the KOS. Note that identifiers created following a rule in a KOS are to be regarded as being taken from this KOS, even though not explicitly spelled out. This definition of KOS reflects current library practice and not the use of the term in general.
subclass of: Design or Procedure
subclass of: Expression

Nomen Use Statement
type: Class
notation: F35
comment: This class comprises statements relating a Thema with a particular Nomen and its usage in the context of a common Complex Work realized by one or more KOS.
subclass of: Design or Procedure
subclass of: Expression

Script Conversion
type: Class
notation: F36
comment: This class comprises rule sets for converting signs or arrangements of signs from one script or type set to another.
subclass of: Design or Procedure

Character
type: Class
notation: F38
comment: This class comprises fictional or iconographic individuals or groups of individuals (including families) appearing in works in a way relevant as subjects. Characters may be purely fictitious or based on real persons or groups, but as characters they may exhibit properties that would be inconsistent with a real person or group. Rather than merging characters with real persons, they should be described as disjoint, but related entities.
subclass of: Conceptual Object

Family
type: Class
notation: F39
comment: This class comprises groups of two or more persons presented as a family justified by relationships of birth, marriage, adoption, civil union, or similar social or legal status and an assumed common tradition, including examples such as royal families, dynasties, houses of nobility, etc.
subclass of: Group

Identifier Assignment
type: Class
notation: F40
comment: This class comprises activities that result in the allocation of an identifier to an instance of any subclass of E1 CRM Entity. An F40 Identifier Assignment may include the creation of the identifier from multiple constituents. Explicit reference to the used constituents can be made using the property P142 used constituent (was used in). The syntax of the identifier and the kinds of constituents to be used in constructing it may be declared in a rule. The construction of controlled access points for the names of persons, families and corporate bodies following specific cataloguing rules is a typical library application of identifier assignment. F40 Identifier Assignment also includes the assignment of controlled access points for works or expressions.
subclass of: Identifier Assignment

Representative Manifestation Assignment
type: Class
notation: F41
comment: This class comprises activities through which an Agency declares (implicitly or explicitly) that a given instance of F3 Manifestation Product Type or F4 Manifestation Singleton is representative for a given F2 Expression, i.e., that some features found on that instance of F3 Manifestation Product Type or F4 Manifestation Singleton (most prominently, information about the title) can be inferred to also apply to that instance of F2 Expression, no matter within which manifestation it is embodied. The reasoning behind is that the Work title is known through the title of an Expression that is deemed representative of the Work, and the title of the representative Expression is known through the title proper of a Manifestation that is deemed representative of the Expression representative of the Work.
subclass of: Attribute Assignment

Representative Expression Assignment
type: Class
notation: F42
comment: This class comprises activities through which an Agency declares (implicitly or explicitly) that a given instance of F2 Expression is representative for a given F15 Complex Work, i.e., that some attributes of that instance of F2 Expression (most prominently, information about the title) can be inferred to also apply to that instance of F15 Complex Work, no matter in which particular expression it is realised. The reasoning behind this is that the Work title is known through the title of an Expression that is deemed representative of the Work, and the title of the representative Expression is known through the title of a Manifestation that is deemed representative of the Expression that is representative of the Work. For instance, by using the qualified controlled access point ‘Poe, Edgar Allan, 1809-1849. Murders in the rue Morgue (French)’ for the French rendition of Poe’s ‘Murders in the rue Morgue’ by Baudelaire, an Agency implicitly states that the French text does not constitute a representative F2 Expression for Poe’s F1 Work, however the original English text does constitute a representative F2 Expression for Poe’s F1 Work.
subclass of: Attribute Assignment

Identifier Rule
type: Class
notation: F43
comment: This class comprises sets of instructions relating to the formulation of a unique identifier.
subclass of: Design or Procedure
subclass of: Expression

Bibliographic Agency
type: Class
notation: F44
comment: This class comprises agents who create the bibliographic description of publications and perform the authority control associated with such descriptions, for the description of copies of such publications actually held by libraries, and for the description of unique documents (manuscripts, objects…) held by libraries. The activity of creating such descriptions implies that one has to make decisions (as to the controlled access point for a work, as to whether an arrangement still belongs to the same work or is definitely a new work, etc.). Since such decisions always are debatable and different agencies can make different decisions about the same real-world entities, it is important to document which agency made which decision.

Controlled Access Point
type: Class
notation: F50
comment: This class comprises identifiers that are not only designed to be unique for the thing they identify, but also to ensure, by following adequate rules based on widely known and accepted properties for their generation, that an independent agency using the same rule would create the same identifier for the same thing. F50 Controlled Access Point covers the notion of both “preferred” and “variant” forms. It does not cover the notion of “cross references”. A cross reference may not uniquely identify one entity, but can be shared by two or more entities, regardless of whether it displays the same structural characteristics as preferred controlled access points.
subclass of: Identifier

Pursuit
type: Class
notation: F51
comment: This class comprises periods of continuous activity of an Actor in a specific professional or creative domain or field.
subclass of: Activity

Name Use Activity
type: Class
notation: F52
comment: This class comprises periods of continuous use of a specific instance of E41 Appellation for a particular instance of E1 CRM Entity by an E39 Actor. It includes in particular the use of the name by its carrier. Characteristically, actors performing an activity may choose a particular appellation for themselves in the context of this activity. Such cases should be modelled by additionally classifying these activities as instances of F52 Name Use Activity. It is possible to specify the type of name use, through the P2 has type property, e.g.: use of a pseudonym, use of a married name, use of a birth name, use of a blended name, use of a religious name, etc.
subclass of: Attribute Assignment

Material Copy
type: Class
notation: F53
comment: This class comprises the features created on an instance of E84 Information Carrier when an F24 Publication Expression is copied to it by an F32 Carrier Production Event. This is the typical result of an electronic publishing process.
subclass of: Utilized Information Carrier

Utilized Information Carrier
type: Class
notation: F54
comment: This class comprises physical objects that carry one or more instances of F24 Publication Expression.
subclass of: Information Carrier

Thing
type: Class
notation: Thing
comment: The class of OWL individuals.

should have type
type: Property
range:
  ressource: Type
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E55 Type, which all exemplars of that publication should belong to, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E55 Type. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type

should have dimension
type: Property
range:
  ressource: Dimension
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E54 Dimension, which all exemplars of that publication should have, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P39i was measured by E16 Measurement P40 observed dimension E54 Dimension. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type

should consist of
type: Property
range:
  ressource: Material
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E57 Material, which all exemplars of that publication should consist of, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E57 Material. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type

should be composed of
type: Property
range:
  ressource: Manifestation Product Type
comment: This property associates an instance of F3 Manifestation Product Type which prescribes that all its Items will contain as parts an Item of another instance of F3 Manifestation Product Type with that instance of F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type

should have number of parts
type: Property
range:
  ressource: Number
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E60 Number, which denotes the number of physical units all exemplars of that publication should consist of, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P57 has number of parts E60 Number. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type

subject to
type: Property
range:
  ressource: Right
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E30 Right, which applies to all exemplars of that publication, as long as they are recognised as exemplars of that publication. The rights covered by this property may include: acquisition or access authorisation; terms of availability; access restrictions on the Manifestation Product Type; etc.
domain:
  ressource: Manifestation Product Type

right held by
type: Property
range:
  ressource: Actor
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E39 Actor, who holds an instance of E30 Right on all exemplars of that publication, as long as they are recognised as exemplars of that publication.
domain:
  ressource: Manifestation Product Type

should carry
type: Property
range:
  ressource: Publication Expression
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F24 Publication Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item R6 carries F24 Publication Expression. It can happen that a given exemplar, or a subset of exemplars, originally produced, or intended to be produced with that characteristic, accidentally lacks part of the publication expression. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type

is identified by
type: Property
range:
  ressource: Appellation
comment: This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
domain:
  ressource: CRM Entity

has type
type: Property
range:
  ressource: Type
comment: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question.
domain:
  ressource: CRM Entity

has note
type: Property
range:
  ressource: String
comment: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. “construction”, “decoration” etc. An item may have many notes, but a note is attached to a specific item.
domain:
  ressource: CRM Entity

carried out by
type: Property
range:
  ressource: Actor
comment: This property describes the active participation of an E39 Actor in an E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property allows the nature of an Actor’s participation to be specified.
domain:
  ressource: Activity

used specific object
type: Property
range:
  ressource: Thing
comment: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.
domain:
  ressource: Activity

used specific technique
type: Property
range:
  ressource: Design or Procedure
comment: 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. The 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. Typical examples would include intervention plans for conservation or the construction plans of a building.
domain:
  ressource: Activity
sub property of: used specific object

assigned
type: Property
range:
  ressource: Identifier
comment: This property records the identifier that was assigned to an item in an Identifier Assignment activity.The same identifier may be assigned on more than one occasion.An Identifier might be created prior to an assignment.
domain:
  ressource: Identifier Assignment
sub property of: assigned

refers to
type: Property
range:
  ressource: CRM Entity
comment: 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.
domain:
  ressource: Propositional Object

has association with
type: Property
range:
  ressource: Design or Procedure
comment: 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.The 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.The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
domain:
  ressource: Design or Procedure

has created
type: Property
range:
  ressource: Conceptual Object
comment: This property allows a conceptual E65 Creation to be linked to the E28 Conceptual Object created by it. It represents the act of conceiving the intellectual content of the E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.
domain:
  ressource: Creation

is composed of
type: Property
range:
  ressource: Symbolic Object
comment: 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.
domain:
  ressource: Symbolic Object

has produced
type: Property
range:
  ressource: Physical Man-Made Thing
comment: This property identifies the E24 Physical Man-Made Thing that came into existence as a result of an E12 Production. The identity of an instance of E24 Physical Man-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Man-Made Thing.
domain:
  ressource: Production

carries
type: Property
range:
  ressource: Symbolic Object
comment: This property identifies an E90 Symbolic Object carried by an instance of E18 Physical Thing.
domain:
  ressource: Physical Thing
sub property of: shows features of

shows features of
type: Property
range:
  ressource: Thing
comment: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established.Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons.
domain:
  ressource: Thing

assigned attribute to
type: Property
range:
  ressource: CRM Entity
comment: This property indicates the item to which an attribute or relation is assigned.
domain:
  ressource: Attribute Assignment

assigned
type: Property
range:
  ressource: CRM Entity
comment: This property indicates the attribute that was assigned or the item that was related to the item denoted by a property P140 assigned attribute to in an Attribute assignment action.
domain:
  ressource: Attribute Assignment

has component
type: Property
range:
  ressource: Propositional Object
comment: 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.
domain:
  ressource: Propositional Object

is logical successor of
type: Property
range:
  ressource: Work
comment: This property associates an instance of F1 Work which logically continues the content of another instance of F1 Work with the latter.
domain:
  ressource: Work
sub property of: shows features of

is derivative of
type: Property
range:
  ressource: Work
comment: This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter. The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation etc.
domain:
  ressource: Work
sub property of: shows features of

is realised in
type: Property
range:
  ressource: Self-Contained Expression
comment: This property associates an instance of F22 Self-Contained Expression with an instance of F1 Work. This property expresses the association that exists between an expression (F22) and the work that this expression conveys. The semantics of the association will be different depending on what specific subtype of F1 Work the work is an instance of. If the work is an instance of F14 Individual Work, the F22 Self-Contained Expression completely conveys the individual work. If the work is an instance of F15 Complex Work, the F22 Self-Contained Expression conveys an alternative member of the complex work. Our factual knowledge of how a given work is realised into an expression is often limited and this property makes it possible to express the association between instances of F22 Self-Contained Expression and the work it conveys without using the more developed paths. The property R3.1 has type: E55 Type allows for specifying the role played by the referred to expression in the overall bibliographic history of the work (e.g., ‘progenitor expression’, on which all other expressions of the same work are based; ‘reference for canonical citations’, in the sense of the HuCit ontology developed by Matteo Romanello and Michele Pasin; ‘earliest draft’, ‘intermediate draft’, ‘final clean draft’, ‘princeps edition’, etc.).
domain:
  ressource: Work

carriers provided by
type: Property
range:
  ressource: Manifestation Product Type
comment: This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F2 Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This property is a shortcut of: F2 Expression P165i is incorporated in F24 Publication Expression CLR6i should be carried by F3 Manifestation Product Type.
domain:
  ressource: Expression
sub property of: carries

has component
type: Property
range:
  ressource: Self-Contained Expression
comment: This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X. It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by P165 incorporates.
domain:
  ressource: Expression
sub property of: has component

carries
type: Property
range:
  ressource: Publication Expression
comment: This property associates an instance of F54 Utilised Information Carrier with the unique instance of F24 Publication Expression it carries.
domain:
  ressource: Utilized Information Carrier
sub property of: carries

is example of
type: Property
range:
  ressource: Manifestation Product Type
comment: This property associates a publication with one of its exemplars. It is a shortcut of the more developed path: F5 Item R28i was produced by F32 Carrier Production R26 produced things of type (was produced by): F3 Manifestation Product Type.
domain:
  ressource: Item
sub property of: has type

consists of
type: Property
range:
  ressource: Symbolic Object
comment: This property associates an instance of F13 Identifier with one of the non-syntactic instances of E90 Symbolic Object which form part of it.
domain:
  ressource: Identifier
sub property of: is composed of

is realised in
type: Property
range:
  ressource: Self-Contained Expression
comment: This property associates an F14 Individual Work with the unique F22 Self-Contained Expression that completely conveys it. It is a shortcut for the more developed path: F14 Individual Work R19i was realised through F28 Expression Creation R17 created F22 Self-Contained Expression.
domain:
  ressource: Individual Work
sub property of: is realised in

has member
type: Property
range:
  ressource: Work
comment: This property associates an instance of F15 Complex Work with an instance of F1 Work that forms part of it.
domain:
  ressource: Complex Work
sub property of: has component

has issuing rule
type: Property
range:
  ressource: Design or Procedure
comment: This property associates an instance of F18 Serial Work with the instance of E29 Design or Procedure that specifies the issuing policy planned by this Work, such as sequencing pattern, expected frequency and expected regularity. This property is a shortcut of the full path: F18 Serial Work R23i was realised through F30 Publication Event P16 used specific object E29 Design or Procedure.
domain:
  ressource: Serial Work

is realised in
type: Property
range:
  ressource: Performance Plan
comment: This property associates an instance of F20 Performance Work with an instance of F25 Performance Plan that consists of signs (words, figures, etc.) which express the directions the instance of F20 Performance Work consists of.
domain:
  ressource: Performance Work
sub property of: is realised in

is realised in
type: Property
range:
  ressource: Recording
comment: This property associates an instance of F21 Recording Work with an instance of F26 Recording realising the instance of F21 Recording Work. This is a shortcut of the more elaborated path through R22 was realised through, F29 Recording Event and R21 created, which should be used when information about the recording event is available.
domain:
  ressource: Recording Work
sub property of: is realised in

has fragment
type: Property
range:
  ressource: Expression Fragment
comment: This property associates the fragment of an expression and the expression of which it is a fragment.
domain:
  ressource: Expression
sub property of: is composed of

initiated
type: Property
range:
  ressource: Work
comment: This property associates the first conception of a work and the work itself that ensued from a given initial idea. It marks the origin of the causality chain that results in a work’s coming into existence.
domain:
  ressource: Work Conception
sub property of: has created

created
type: Property
range:
  ressource: Expression
comment: This property associates the expression that was first externalised during a particular creation event with that particular creation event.
domain:
  ressource: Expression Creation
sub property of: has created

created
type: Property
range:
  ressource: Manifestation Singleton
comment: This property associates an instance of F28 Expression Creation with the first physical objects in which the resulting instance of F2 Expression was embodied.
domain:
  ressource: Expression Creation
sub property of: has produced

created a realisation of
type: Property
range:
  ressource: Work
comment: This property associates an instance of F28 Expression Creation with the corresponding instance of F14 Individual Work or an instance of F15 Complex Work of which the corresponding instance of F14 Individual Work is a member.
domain:
  ressource: Expression Creation
sub property of: used specific object

recorded
type: Property
range:
  ressource: Temporal Entity
comment: This property associates an instance of F29 Recording Event with the instance of E2 Temporal Entity which was captured.
domain:
  ressource: Recording Event

created
type: Property
range:
  ressource: Recording
comment: This property associates an instance of F29 Recording Event with the instance of F26 Recording that was created.
domain:
  ressource: Recording Event
sub property of: created

created a realisation of
type: Property
range:
  ressource: Recording Work
comment: This property associates an instance of F29 Recording Event with the instance of F21 Recording Work it realised.
domain:
  ressource: Recording Event
sub property of: created a realisation of

created a realisation of
type: Property
range:
  ressource: Publication Work
comment: This property associates an instance of F30 Publication Event with the instance of F19 Publication Work it realised.
domain:
  ressource: Publication Event
sub property of: is identified by

created
type: Property
range:
  ressource: Publication Expression
comment: This property associates the instance of F24 Publication Expression that was created during a particular F30 Publication Event with that F30 Publication Event.
domain:
  ressource: Publication Event
sub property of: created

performed
type: Property
range:
  ressource: Performance Plan
comment: This property associates an instance of F31 Performance with the instance of F25 Performance Plan to which all those participating in the performance were supposed to conform.
domain:
  ressource: Performance
sub property of: used specific technique

produced things of type
type: Property
range:
  ressource: Manifestation Product Type
comment: This property associates an instance of F32 Carrier Production Event with the instance of F3 Manifestation Product Type it produced items of.
domain:
  ressource: Carrier Production Event

used as source material
type: Property
range:
  ressource: Publication Expression
comment: This property associates an instance of F32 Carrier Production Event with the set of signs provided by the publisher to be carried by all of the produced items.
domain:
  ressource: Carrier Production Event
sub property of: used specific object

produced
type: Property
range:
  ressource: Utilized Information Carrier
comment: This property associates an instance of F32 Carrier Production Event with any one of the produced items (i.e., the instances of F5 Item or F53 Material Copy).
domain:
  ressource: Carrier Production Event
sub property of: has produced

reproduced
type: Property
range:
  ressource: Information Carrier
comment: This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it reproduces.
domain:
  ressource: Reproduction Event
sub property of: used specific object

produced
type: Property
range:
  ressource: Information Carrier
comment: This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it produces.
domain:
  ressource: Reproduction Event
sub property of: has produced

is reproduction of
type: Property
range:
  ressource: Information Carrier
comment: This property associates an instance of E84 Information Carrier which is a reproduction of another instance of E84 Information Carrier with the latter. It is considered that a reproduction of multiple originals resulting in a single product requires a merging of those objects prior to the reproduction. Therefore an Information Carrier is regarded to be a reproduction of one and only one original. This property is a shortcut of the more fully developed path from E84 Information Carrier through R30 produced (was produced by), F33 Reproduction Event R29 reproduced (was reproduced by) to E84 Information Carrier.
domain:
  ressource: Information Carrier
sub property of: shows features of

is warranted by
type: Property
range:
  ressource: Name Use Activity
comment: This property associates an instance of F35 Nomen Use Statement with an instance of F52 Name Use Activity which provides evidence for the use of the particular nomen in the stated sense. The association between this name use activity and a source for it may be described by the property P70 documents (is documented in).
domain:
  ressource: Nomen Use Statement
sub property of: refers to

has content
type: Property
range:
  ressource: String
comment: This property associates an instance of F12 Nomen with one or more equivalent serialized content models for it. In digital form the symbol arrangement constituting an instance of F12 Nomen can only be represented through a particular encoding, for example ASCII or Latin1 for the Latin script. We call such a representation a content model. The property R33.1 has encoding: E55 Type allows for specifying the encoding of a particular associated content model. Together with this specification, a content model allows for unambiguously defining a nomen independently from the encoding used for representing the content.
domain:
  ressource: Nomen
sub property of: has note

has validity period
type: Property
range:
  ressource: Time-Span
comment: This property associates an instance of F34 KOS with the instance of E52 Time-Span describing the period for which the particular KOS Expression was regarded as valid by its maintainers. Each change of validity status of a nomen use statement within a KOS should be associated with a release change of the KOS. The individual time-span of a validity state of a nomen would be the union of the time-spans of the KOS in which the Nomen was declared to have the particular validity status (provisional, accepted, obsolete etc...).
domain:
  ressource: KOS

specified by
type: Property
range:
  ressource: KOS
comment: This property associates an instance of F35 Nomen Use Statement with an instance of F34 KOS in which the Nomen Use Statement has a given status. The property R35.1 allows for specifying the particular status of the nomen use statement within the KOS. An instance of R35 is specified by should have only one status.
domain:
  ressource: Nomen Use Statement
sub property of: has component

uses script conversion
type: Property
range:
  ressource: Script Conversion
comment: This property associates an instance of F35 Nomen Use Statement with the instance of F36 Script Conversion that was used to create the Nomen referred to in the Nomen Use Statement. The source of this conversion may or may not be explicitly mentioned. Is shortcut of: F35 Nomen Use Statement R17 was created by (created) F28 Expression Creation P33 used specific technique (was used by) E29 Design or Procedure.
domain:
  ressource: Nomen Use Statement

states as nomen
type: Property
range:
  ressource: Nomen
domain:
  ressource: Nomen Use Statement
sub property of: refers to

refers to thema
type: Property
range:
  ressource: CRM Entity
comment: This property associates an instance of F35 Nomen Use Statement with the instance of E1 CRM Entity for which it declares the usage of a nomen.
domain:
  ressource: Nomen Use Statement

is intended for
type: Property
range:
  ressource: Group
comment: This property associates an instance of F35 Nomen Use Statement with an instance of E74 Group which is the target audience for which the associated nomen use is intended. To indicate that the associated nomen is declared as preferred in all contexts, the instance of E74 Group is ‘mankind’.
domain:
  ressource: Nomen Use Statement
sub property of: refers to

has representative expression
type: Property
range:
  ressource: Self-Contained Expression
comment: This property identifies an instance of F22 Self-Contained Expression that has been chosen as the most characteristic expression of the instance of F1 Work of which it is an expression. There is no other semantic implication to this notion of being characteristic than to be an adequate candidate to uniquely identify the Work realized by it. Prototypically, this is the instance of F22 Self-Contained Expression that is deemed characteristic of an instance of F15 Complex Work. Typically, any expression that is not regarded as “representative” for the work it expresses, would require a controlled access point, with qualifiers specifying the differences between that expression and a representative expression, although this may not always be done in practice. The title of a Work may not be one taken from a representative expression. A given work can have more than one representative expression, provided the differences between these expressions are not deemed “substantial.” If the anticipated needs of users are not considered to call for bibliographic distinctions between variant expressions of a work, then even expressions that differ significantly from each other can be regarded as equally representative for the work. (See FRBR: Final Report, p. 19-20). A given expression can be deemed representative for a work with regard to some of its aspects (e.g., the text contained in an edition the title proper of which reads ‘The tragicall historie of HAMLET Prince of Denmarke’, and the language of that text), and not representative for it with regard to some other aspects (e.g., the title proper ‘The tragicall historie of HAMLET Prince of Denmarke’ itself, which, being different from the title that is regarded as “representative” for Shakespeare’s work, will require the use of a controlled access point). R40 has representative expression is a shortcut of the more developed path F1 Work R50i was assigned by F42 Representative Expression Assignment R51 assigned F2 Expression.
domain:
  ressource: Work
sub property of: is realised in

has representative manifestation product type
type: Property
range:
  ressource: Manifestation Product Type
comment: This property identifies an instance of F3 Manifestation Product Type that has been chosen as the most characteristic Manifestation Product Type of the instance of F2 Expression of which it is a manifestation. Identifying an instance of F3 Manifestation Product Type that is representative for an instance of F2 Expression makes it possible in turn to identify an instance of F2 Expression that is representative for an instance of F1 Work, and to decide what should be regarded as the title of the work. The title of an Expression may not be one taken from a representative Manifestation Product Type or Manifestation Singleton. A given expression can have more than one Representative Manifestation Product Type. R41 has representative manifestation product type is a shortcut of the more developed path F2 Expression R48i was assigned by F41 Representative Manifestation Assignment R49 assigned F3 Manifestation Product Type.
domain:
  ressource: Expression
sub property of: carriers provided by

is representative manifestation singleton for
type: Property
range:
  ressource: Expression
comment: This property identifies an instance of Manifestation Singleton that has been declared as the unique representative for an instance of F2 Expression by some bibliographic agency. This property identifies an instance of F4 Manifestation Singleton that has been chosen as the most characteristic Manifestation Singleton of the instance of F2 Expression of which it is a manifestation. Identifying an instance of F4 Manifestation Singleton that is representative for an instance of F2 Expression makes it possible in turn to identify an instance of F2 Expression that is representative for an instance of F1 Work, and to decide what should be regarded as the title of the work. The title of an Expression may not be one taken from a representative Manifestation Product Type or Manifestation Singleton. A given expression can have more than one representative Manifestation Singleton. It is a shortcut for the more developed path: F2 Expression R48i was assigned by F41 Representative Manifestation Assignment R53 assigned F4 Manifestation Singleton.
domain:
  ressource: Manifestation Singleton
sub property of: carries

carried out by
type: Property
range:
  ressource: Bibliographic Agency
comment: This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which Manifestation (i.e., which instance of F3 Manifestation Product Type or F4 Manifestation Singleton) is representative for a given expression. In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.
domain:
  ressource: Representative Manifestation Assignment
sub property of: carried out by

carried out by
type: Property
range:
  ressource: Bibliographic Agency
comment: This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which expression is representative for a given Work. In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.
domain:
  ressource: Representative Expression Assignment
sub property of: carried out by

assigned to
type: Property
range:
  ressource: CRM Entity
comment: This property identifies the entity to which an actor, such as a bibliographic agency, assigned an instance of F13 Identifier.
domain:
  ressource: Identifier Assignment
sub property of: assigned attribute to

assigned to
type: Property
range:
  ressource: Identifier
comment: This property associates the instance of F13 Identifier assigned to an instance of E1 CRM Entity and the event of assigning it.
domain:
  ressource: Identifier Assignment
sub property of: assigned

assigned to
type: Property
range:
  ressource: Expression
comment: This property associates the event of assigning a representative instance of F3 Manifestation Product Type or F4 Manifestation Singleton with the expression to which it was assigned.
domain:
  ressource: Representative Manifestation Assignment
sub property of: assigned attribute to

assigned
type: Property
range:
  ressource: Manifestation Product Type
comment: This property associates the event of assigning a representative instance of F3 Manifestation Product Type with the F3 Manifestation Product Type which has been assigned.
domain:
  ressource: Representative Manifestation Assignment
sub property of: assigned

assigned to
type: Property
range:
  ressource: Complex Work
comment: This property associates the event of assigning a representative instance of F2 Expression with the instance of F15 Complex Work to which it was assigned.
domain:
  ressource: Representative Expression Assignment
sub property of: assigned attribute to

assigned
type: Property
range:
  ressource: Expression
comment: This property associates the event of assigning a representative instance of F2 Expression with the F2 Expression which has been assigned.
domain:
  ressource: Representative Expression Assignment
sub property of: assigned

used rule
type: Property
range:
  ressource: Identifier Rule
comment: This property associates the event of assigning an instance of F13 Identifier with the instructions followed by an actor, such as a Bibliographic Agency, in creating that identifier.
domain:
  ressource: Identifier Assignment
sub property of: used specific technique

assigned
type: Property
range:
  ressource: Manifestation Singleton
comment: This property associates the event of assigning a representative instance of F4 Manifestation Singleton with the F4 Manifestation Singleton which has been assigned.
domain:
  ressource: Representative Manifestation Assignment
sub property of: assigned

has nomen language
type: Property
range:
  ressource: Language
comment: This property associates an instance of F35 Nomen Use Statement with an instance of E56 Language which is a target language for the associated nomen use.
domain:
  ressource: Nomen Use Statement
sub property of: refers to

has nomen form
type: Property
range:
  ressource: Type
comment: This property associates an instance of F35 Nomen Use Statement with the instance of E55 Type that characterizes the Nomen referred to in the Nomen Use Statement, such as abbreviation, full name etc. In the case of abbreviations, the source of this form may or may not be explicitly mentioned.
domain:
  ressource: Nomen Use Statement
sub property of: refers to

has related use
type: Property
range:
  ressource: Nomen Use Statement
comment: This property associates an instance of F35 Nomen Use Statement with another instance of F35 Nomen Use Statement which has a related use in some context, such as alternative, lexical variant, replacing former use etc. The property R56.1 allows for specifying the particular kind of the nomen use statement relationship.
domain:
  ressource: Nomen Use Statement
sub property of: has association with

is based on
type: Property
range:
  ressource: Actor
comment: This property associates an instance of F38 Character with an instance of E39 Actor that the character is motivated by or is intended to represent. An instance of F38 Character may be based on a combination of features taken from several actors. This property is a shortcut of the more fully developed path from E28 Conceptual Object, restricted to F38 Character, through the inverse of P94 has created (was created by), E65 Creation P17 was motivated by (motivated) to E1 CRM Entity restricted to E39 Actor.
domain:
  ressource: Character

has fictional member
type: Property
range:
  ressource: Character
comment: This property associates an instance of F38 Character representing a group with another instance of F38 Character that is presented in relevant fiction as a member of the fictional group.
domain:
  ressource: Character

had typical subject
type: Property
range:
  ressource: CRM Entity
comment: This property associates an instance of F51 Pursuit with the instance of E1 CRM Entity that is the typical subject of the associated activity, such as an area of expertise in which the actor is engaged or was engaged.
domain:
  ressource: Pursuit

used to use language
type: Property
range:
  ressource: Language
comment: This property associates an instance of F51 Pursuit with the instance of E56 Language that was characteristically used for the products of the associated activity. The property R60.1 has type of use allows for specifying a particular form of use.
domain:
  ressource: Pursuit

occured in kind of context
type: Property
range:
  ressource: Type
comment: This property associates an instance of F52 Name Use Activity with the instance of E55 Type that characterises the kind of role or context within which the associated name was used.
domain:
  ressource: Name Use Activity

was used for membership in
type: Property
range:
  ressource: Group
comment: This property associates an instance of F52 Name Use Activity with the instance of E74 Group that characterises the context within which the associated name was used for membership in that group.
domain:
  ressource: Name Use Activity

named
type: Property
range:
  ressource: CRM Entity
comment: This property associates an instance of F52 Name Use Activity with the instance of E1 CRM Entity that the associated name was used for.
domain:
  ressource: Name Use Activity
sub property of: assigned attribute to

used name
type: Property
range:
  ressource: Appellation
comment: This property associates an instance of F52 Name Use Activity with the instance of E41 Appellation that was used for the associated entity.
domain:
  ressource: Name Use Activity
sub property of: used specific object

recorded aspects of
type: Property
range:
  ressource: Physical Thing
comment: This property associates an instance of F29 Recording Event with an instance of E18 Physical Thing some of whose features, at the time of recording, were recorded in that process.
domain:
  ressource: Recording Event

included performed version of
type: Property
range:
  ressource: Propositional Object
comment: This property associates an instance of F31 Performance with a product of the mind that was performed in the course of that instance of F31 Performance. According to the level of knowledge available about the performance, the range of this property can actually be specialised as either an instance of F1 Work (if nothing is known as to which specific expression of the work was performed), or of F2 Expression (if there is a reasonable amount of certainty as to which specific expression—e.g., a well identified translation of a play—of the work was performed). In addition to being a subproperty of P16 used specific object (was used for), this property also is a shortcut of the fully developed path that goes from F31 Performance to F1 Work through: R25 performed F25 Performance Plan P165 incorporates F22 Self-Contained Expression R3i realises. In this fully developed path, the specific instance of F22 Self-Contained Expression can be precisely identified and described for its own sake, or it can just be known to have necessarily existed.
domain:
  ressource: Performance
sub property of: used specific object

should be type of
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E55 Type, which all exemplars of that publication should belong to, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E55 Type. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Type

should be dimension of
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E54 Dimension, which all exemplars of that publication should have, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P39i was measured by E16 Measurement P40 observed dimension E54 Dimension. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Dimension

should be incorporated in
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E57 Material, which all exemplars of that publication should consist of, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E57 Material. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Material

may form part of
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F3 Manifestation Product Type which prescribes that all its Items will contain as parts an Item of another instance of F3 Manifestation Product Type with that instance of F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type

[NO_INVERSE_LABEL_FOUND]
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E60 Number, which denotes the number of physical units all exemplars of that publication should consist of, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P57 has number of parts E60 Number. It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Number

applies to
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E30 Right, which applies to all exemplars of that publication, as long as they are recognised as exemplars of that publication. The rights covered by this property may include: acquisition or access authorisation; terms of availability; access restrictions on the Manifestation Product Type; etc.
domain:
  ressource: Right

right on
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E39 Actor, who holds an instance of E30 Right on all exemplars of that publication, as long as they are recognised as exemplars of that publication.
domain:
  ressource: Actor

should be carried by
type: Property
range:
  ressource: Manifestation Product Type
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F24 Publication Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item R6 carries F24 Publication Expression. It can happen that a given exemplar, or a subset of exemplars, originally produced, or intended to be produced with that characteristic, accidentally lacks part of the publication expression. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
domain:
  ressource: Publication Expression

identifies
type: Property
range:
  ressource: CRM Entity
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
domain:
  ressource: Appellation

is type of
type: Property
range:
  ressource: CRM Entity
comment: This property is the inverse of the forward property described in the scope note that follows. This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question.
domain:
  ressource: Type

[NO_INVERSE_LABEL_FOUND]
type: Property
range:
  ressource: CRM Entity
comment: This property is the inverse of the forward property described in the scope note that follows. This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. “construction”, “decoration” etc. An item may have many notes, but a note is attached to a specific item.
domain:
  ressource: String

performed
type: Property
range:
  ressource: Activity
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the active participation of an E39 Actor in an E7 Activity. It implies causal or legal responsibility. The P14.1 in the role of property of the property allows the nature of an Actor’s participation to be specified.
domain:
  ressource: Actor

was used for
type: Property
range:
  ressource: Activity
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.
domain:
  ressource: Thing

was used by
type: Property
range:
  ressource: Activity
comment: This property is the inverse of the forward property described in the scope note that follows. 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. The 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. Typical examples would include intervention plans for conservation or the construction plans of a building.
domain:
  ressource: Design or Procedure
sub property of: was used for

was assigned by
type: Property
range:
  ressource: Identifier Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property records the identifier that was assigned to an item in an Identifier Assignment activity.The same identifier may be assigned on more than one occasion.An Identifier might be created prior to an assignment.
domain:
  ressource: Identifier
sub property of: was assigned by

is referred to by
type: Property
range:
  ressource: Propositional Object
comment: This property is the inverse of the forward property described in the scope note that follows. 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.
domain:
  ressource: CRM Entity

is associated with
type: Property
range:
  ressource: Design or Procedure
comment: This property is the inverse of the forward property described in the scope note that follows. 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.The 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.The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
domain:
  ressource: Design or Procedure

was created by
type: Property
range:
  ressource: Creation
comment: This property is the inverse of the forward property described in the scope note that follows. This property allows a conceptual E65 Creation to be linked to the E28 Conceptual Object created by it. It represents the act of conceiving the intellectual content of the E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.
domain:
  ressource: Conceptual Object

forms part of
type: Property
range:
  ressource: Symbolic Object
comment: This property is the inverse of the forward property described in the scope note that follows. 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.
domain:
  ressource: Symbolic Object

was produced by
type: Property
range:
  ressource: Production
comment: This property is the inverse of the forward property described in the scope note that follows. This property identifies the E24 Physical Man-Made Thing that came into existence as a result of an E12 Production. The identity of an instance of E24 Physical Man-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Man-Made Thing.
domain:
  ressource: Physical Man-Made Thing

is carried by
type: Property
range:
  ressource: Physical Thing
comment: This property is the inverse of the forward property described in the scope note that follows. This property identifies an E90 Symbolic Object carried by an instance of E18 Physical Thing.
domain:
  ressource: Symbolic Object
sub property of: features are also found on

features are also found on
type: Property
range:
  ressource: Thing
comment: This property is the inverse of the forward property described in the scope note that follows. This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established.Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons.
domain:
  ressource: Thing

was attributed by
type: Property
range:
  ressource: Attribute Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property indicates the item to which an attribute or relation is assigned.
domain:
  ressource: CRM Entity

was assigned by
type: Property
range:
  ressource: Attribute Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. 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.
domain:
  ressource: CRM Entity

is component of
type: Property
range:
  ressource: Propositional Object
comment: This property is the inverse of the forward property described in the scope note that follows. 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.
domain:
  ressource: Propositional Object

has successor
type: Property
range:
  ressource: Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F1 Work which logically continues the content of another instance of F1 Work with the latter.
domain:
  ressource: Work
sub property of: features are also found on

has derivative
type: Property
range:
  ressource: Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter. The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation etc.
domain:
  ressource: Work
sub property of: features are also found on

realises
type: Property
range:
  ressource: Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F22 Self-Contained Expression with an instance of F1 Work. This property expresses the association that exists between an expression (F22) and the work that this expression conveys. The semantics of the association will be different depending on what specific subtype of F1 Work the work is an instance of. If the work is an instance of F14 Individual Work, the F22 Self-Contained Expression completely conveys the individual work. If the work is an instance of F15 Complex Work, the F22 Self-Contained Expression conveys an alternative member of the complex work. Our factual knowledge of how a given work is realised into an expression is often limited and this property makes it possible to express the association between instances of F22 Self-Contained Expression and the work it conveys without using the more developed paths. The property R3.1 has type: E55 Type allows for specifying the role played by the referred to expression in the overall bibliographic history of the work (e.g., ‘progenitor expression’, on which all other expressions of the same work are based; ‘reference for canonical citations’, in the sense of the HuCit ontology developed by Matteo Romanello and Michele Pasin; ‘earliest draft’, ‘intermediate draft’, ‘final clean draft’, ‘princeps edition’, etc.).
domain:
  ressource: Self-Contained Expression

comprises carriers of
type: Property
range:
  ressource: Expression
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F2 Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This property is a shortcut of: F2 Expression P165i is incorporated in F24 Publication Expression CLR6i should be carried by F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type
sub property of: is carried by

is component of
type: Property
range:
  ressource: Expression
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X. It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by P165 incorporates.
domain:
  ressource: Self-Contained Expression
sub property of: is component of

is carried by
type: Property
range:
  ressource: Utilized Information Carrier
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F54 Utilised Information Carrier with the unique instance of F24 Publication Expression it carries.
domain:
  ressource: Publication Expression
sub property of: is carried by

has example
type: Property
range:
  ressource: Item
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a publication with one of its exemplars. It is a shortcut of the more developed path: F5 Item R28i was produced by F32 Carrier Production R26 produced things of type (was produced by): F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type
sub property of: is type of

forms part of
type: Property
range:
  ressource: Identifier
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F13 Identifier with one of the non-syntactic instances of E90 Symbolic Object which form part of it.
domain:
  ressource: Symbolic Object
sub property of: forms part of

realises
type: Property
range:
  ressource: Individual Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an F14 Individual Work with the unique F22 Self-Contained Expression that completely conveys it. It is a shortcut for the more developed path: F14 Individual Work R19i was realised through F28 Expression Creation R17 created F22 Self-Contained Expression.
domain:
  ressource: Self-Contained Expression
sub property of: realises

is member of
type: Property
range:
  ressource: Complex Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F15 Complex Work with an instance of F1 Work that forms part of it.
domain:
  ressource: Work
sub property of: is component of

is issuing rule of
type: Property
range:
  ressource: Serial Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F18 Serial Work with the instance of E29 Design or Procedure that specifies the issuing policy planned by this Work, such as sequencing pattern, expected frequency and expected regularity. This property is a shortcut of the full path: F18 Serial Work R23i was realised through F30 Publication Event P16 used specific object E29 Design or Procedure.
domain:
  ressource: Design or Procedure

realises
type: Property
range:
  ressource: Performance Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F20 Performance Work with an instance of F25 Performance Plan that consists of signs (words, figures, etc.) which express the directions the instance of F20 Performance Work consists of.
domain:
  ressource: Performance Plan
sub property of: realises

realises
type: Property
range:
  ressource: Recording Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F21 Recording Work with an instance of F26 Recording realising the instance of F21 Recording Work. This is a shortcut of the more elaborated path through R22 was realised through, F29 Recording Event and R21 created, which should be used when information about the recording event is available.
domain:
  ressource: Recording
sub property of: realises

is fragment of
type: Property
range:
  ressource: Expression
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the fragment of an expression and the expression of which it is a fragment.
domain:
  ressource: Expression Fragment
sub property of: forms part of

was initiated by
type: Property
range:
  ressource: Work Conception
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the first conception of a work and the work itself that ensued from a given initial idea. It marks the origin of the causality chain that results in a work’s coming into existence.
domain:
  ressource: Work
sub property of: was created by

was created by
type: Property
range:
  ressource: Expression Creation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the expression that was first externalised during a particular creation event with that particular creation event.
domain:
  ressource: Expression
sub property of: was created by

was created by
type: Property
range:
  ressource: Expression Creation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F28 Expression Creation with the first physical objects in which the resulting instance of F2 Expression was embodied.
domain:
  ressource: Manifestation Singleton
sub property of: was produced by

was realised through
type: Property
range:
  ressource: Expression Creation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F28 Expression Creation with the corresponding instance of F14 Individual Work or an instance of F15 Complex Work of which the corresponding instance of F14 Individual Work is a member.
domain:
  ressource: Work
sub property of: was used for

was recorded through
type: Property
range:
  ressource: Recording Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F29 Recording Event with the instance of E2 Temporal Entity which was captured.
domain:
  ressource: Temporal Entity

was created through
type: Property
range:
  ressource: Recording Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F29 Recording Event with the instance of F26 Recording that was created.
domain:
  ressource: Recording
sub property of: was created by

was realised through
type: Property
range:
  ressource: Recording Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F29 Recording Event with the instance of F21 Recording Work it realised.
domain:
  ressource: Recording Work
sub property of: was realised through

was realised through
type: Property
range:
  ressource: Publication Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F30 Publication Event with the instance of F19 Publication Work it realised.
domain:
  ressource: Publication Work
sub property of: identifies

was created through
type: Property
range:
  ressource: Publication Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the instance of F24 Publication Expression that was created during a particular F30 Publication Event with that F30 Publication Event.
domain:
  ressource: Publication Expression
sub property of: was created by

was performed in
type: Property
range:
  ressource: Performance
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F31 Performance with the instance of F25 Performance Plan to which all those participating in the performance were supposed to conform.
domain:
  ressource: Performance Plan
sub property of: was used by

was produced by
type: Property
range:
  ressource: Carrier Production Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F32 Carrier Production Event with the instance of F3 Manifestation Product Type it produced items of.
domain:
  ressource: Manifestation Product Type

was used by
type: Property
range:
  ressource: Carrier Production Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F32 Carrier Production Event with the set of signs provided by the publisher to be carried by all of the produced items.
domain:
  ressource: Publication Expression
sub property of: was used for

was produced by
type: Property
range:
  ressource: Carrier Production Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F32 Carrier Production Event with any one of the produced items (i.e., the instances of F5 Item or F53 Material Copy).
domain:
  ressource: Utilized Information Carrier
sub property of: was produced by

was reproduced by
type: Property
range:
  ressource: Reproduction Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it reproduces.
domain:
  ressource: Information Carrier
sub property of: was used for

was produced by
type: Property
range:
  ressource: Reproduction Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it produces.
domain:
  ressource: Information Carrier
sub property of: was produced by

has reproduction
type: Property
range:
  ressource: Information Carrier
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of E84 Information Carrier which is a reproduction of another instance of E84 Information Carrier with the latter. It is considered that a reproduction of multiple originals resulting in a single product requires a merging of those objects prior to the reproduction. Therefore an Information Carrier is regarded to be a reproduction of one and only one original. This property is a shortcut of the more fully developed path from E84 Information Carrier through R30 produced (was produced by), F33 Reproduction Event R29 reproduced (was reproduced by) to E84 Information Carrier.
domain:
  ressource: Information Carrier
sub property of: features are also found on

warrants
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with an instance of F52 Name Use Activity which provides evidence for the use of the particular nomen in the stated sense. The association between this name use activity and a source for it may be described by the property P70 documents (is documented in).
domain:
  ressource: Name Use Activity
sub property of: is referred to by

[NO_INVERSE_LABEL_FOUND]
type: Property
range:
  ressource: Nomen
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F12 Nomen with one or more equivalent serialized content models for it. In digital form the symbol arrangement constituting an instance of F12 Nomen can only be represented through a particular encoding, for example ASCII or Latin1 for the Latin script. We call such a representation a content model. The property R33.1 has encoding: E55 Type allows for specifying the encoding of a particular associated content model. Together with this specification, a content model allows for unambiguously defining a nomen independently from the encoding used for representing the content.
domain:
  ressource: String
sub property of: [NO_INVERSE_LABEL_FOUND]

is validity period of
type: Property
range:
  ressource: KOS
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F34 KOS with the instance of E52 Time-Span describing the period for which the particular KOS Expression was regarded as valid by its maintainers. Each change of validity status of a nomen use statement within a KOS should be associated with a release change of the KOS. The individual time-span of a validity state of a nomen would be the union of the time-spans of the KOS in which the Nomen was declared to have the particular validity status (provisional, accepted, obsolete etc...).
domain:
  ressource: Time-Span

specifies
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with an instance of F34 KOS in which the Nomen Use Statement has a given status. The property R35.1 allows for specifying the particular status of the nomen use statement within the KOS. An instance of R35 is specified by should have only one status.
domain:
  ressource: KOS
sub property of: is component of

is script conversion used in
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with the instance of F36 Script Conversion that was used to create the Nomen referred to in the Nomen Use Statement. The source of this conversion may or may not be explicitly mentioned. Is shortcut of: F35 Nomen Use Statement R17 was created by (created) F28 Expression Creation P33 used specific technique (was used by) E29 Design or Procedure.
domain:
  ressource: Script Conversion

is stated as nomen in
type: Property
range:
  ressource: Nomen Use Statement
domain:
  ressource: Nomen
sub property of: is referred to by

is thema of
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with the instance of E1 CRM Entity for which it declares the usage of a nomen.
domain:
  ressource: CRM Entity

is target audience in
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with an instance of E74 Group which is the target audience for which the associated nomen use is intended. To indicate that the associated nomen is declared as preferred in all contexts, the instance of E74 Group is ‘mankind’.
domain:
  ressource: Group
sub property of: is referred to by

is representative expression for
type: Property
range:
  ressource: Work
comment: This property is the inverse of the forward property described in the scope note that follows. This property identifies an instance of F22 Self-Contained Expression that has been chosen as the most characteristic expression of the instance of F1 Work of which it is an expression. There is no other semantic implication to this notion of being characteristic than to be an adequate candidate to uniquely identify the Work realized by it. Prototypically, this is the instance of F22 Self-Contained Expression that is deemed characteristic of an instance of F15 Complex Work. Typically, any expression that is not regarded as “representative” for the work it expresses, would require a controlled access point, with qualifiers specifying the differences between that expression and a representative expression, although this may not always be done in practice. The title of a Work may not be one taken from a representative expression. A given work can have more than one representative expression, provided the differences between these expressions are not deemed “substantial.” If the anticipated needs of users are not considered to call for bibliographic distinctions between variant expressions of a work, then even expressions that differ significantly from each other can be regarded as equally representative for the work. (See FRBR: Final Report, p. 19-20). A given expression can be deemed representative for a work with regard to some of its aspects (e.g., the text contained in an edition the title proper of which reads ‘The tragicall historie of HAMLET Prince of Denmarke’, and the language of that text), and not representative for it with regard to some other aspects (e.g., the title proper ‘The tragicall historie of HAMLET Prince of Denmarke’ itself, which, being different from the title that is regarded as “representative” for Shakespeare’s work, will require the use of a controlled access point). R40 has representative expression is a shortcut of the more developed path F1 Wor…
domain:
  ressource: Self-Contained Expression
sub property of: realises

is representative manifestation product type for
type: Property
range:
  ressource: Expression
comment: This property is the inverse of the forward property described in the scope note that follows. This property identifies an instance of F3 Manifestation Product Type that has been chosen as the most characteristic Manifestation Product Type of the instance of F2 Expression of which it is a manifestation. Identifying an instance of F3 Manifestation Product Type that is representative for an instance of F2 Expression makes it possible in turn to identify an instance of F2 Expression that is representative for an instance of F1 Work, and to decide what should be regarded as the title of the work. The title of an Expression may not be one taken from a representative Manifestation Product Type or Manifestation Singleton. A given expression can have more than one Representative Manifestation Product Type. R41 has representative manifestation product type is a shortcut of the more developed path F2 Expression R48i was assigned by F41 Representative Manifestation Assignment R49 assigned F3 Manifestation Product Type.
domain:
  ressource: Manifestation Product Type
sub property of: comprises carriers of

has representative manifestation singleton
type: Property
range:
  ressource: Manifestation Singleton
comment: This property is the inverse of the forward property described in the scope note that follows. This property identifies an instance of Manifestation Singleton that has been declared as the unique representative for an instance of F2 Expression by some bibliographic agency. This property identifies an instance of F4 Manifestation Singleton that has been chosen as the most characteristic Manifestation Singleton of the instance of F2 Expression of which it is a manifestation. Identifying an instance of F4 Manifestation Singleton that is representative for an instance of F2 Expression makes it possible in turn to identify an instance of F2 Expression that is representative for an instance of F1 Work, and to decide what should be regarded as the title of the work. The title of an Expression may not be one taken from a representative Manifestation Product Type or Manifestation Singleton. A given expression can have more than one representative Manifestation Singleton. It is a shortcut for the more developed path: F2 Expression R48i was assigned by F41 Representative Manifestation Assignment R53 assigned F4 Manifestation Singleton.
domain:
  ressource: Expression
sub property of: is carried by

performed
type: Property
range:
  ressource: Representative Manifestation Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which Manifestation (i.e., which instance of F3 Manifestation Product Type or F4 Manifestation Singleton) is representative for a given expression. In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.
domain:
  ressource: Bibliographic Agency
sub property of: performed

performed
type: Property
range:
  ressource: Representative Expression Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which expression is representative for a given Work. In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.
domain:
  ressource: Bibliographic Agency
sub property of: performed

was assigned by
type: Property
range:
  ressource: Identifier Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property identifies the entity to which an actor, such as a bibliographic agency, assigned an instance of F13 Identifier.
domain:
  ressource: CRM Entity
sub property of: was attributed by

was assigned by
type: Property
range:
  ressource: Identifier Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the instance of F13 Identifier assigned to an instance of E1 CRM Entity and the event of assigning it.
domain:
  ressource: Identifier
sub property of: was assigned by

was assigned by
type: Property
range:
  ressource: Representative Manifestation Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the event of assigning a representative instance of F3 Manifestation Product Type or F4 Manifestation Singleton with the expression to which it was assigned.
domain:
  ressource: Expression
sub property of: was attributed by

was assigned by
type: Property
range:
  ressource: Representative Manifestation Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the event of assigning a representative instance of F3 Manifestation Product Type with the F3 Manifestation Product Type which has been assigned.
domain:
  ressource: Manifestation Product Type
sub property of: was assigned by

was assigned by
type: Property
range:
  ressource: Representative Expression Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the event of assigning a representative instance of F2 Expression with the instance of F15 Complex Work to which it was assigned.
domain:
  ressource: Complex Work
sub property of: was attributed by

was assigned by
type: Property
range:
  ressource: Representative Expression Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the event of assigning a representative instance of F2 Expression with the F2 Expression which has been assigned.
domain:
  ressource: Expression
sub property of: was assigned by

was the rule used in
type: Property
range:
  ressource: Identifier Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the event of assigning an instance of F13 Identifier with the instructions followed by an actor, such as a Bibliographic Agency, in creating that identifier.
domain:
  ressource: Identifier Rule
sub property of: was used by

was assigned by
type: Property
range:
  ressource: Representative Manifestation Assignment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates the event of assigning a representative instance of F4 Manifestation Singleton with the F4 Manifestation Singleton which has been assigned.
domain:
  ressource: Manifestation Singleton
sub property of: was assigned by

is language of nomen in
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with an instance of E56 Language which is a target language for the associated nomen use.
domain:
  ressource: Language
sub property of: is referred to by

is nomen form in
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with the instance of E55 Type that characterizes the Nomen referred to in the Nomen Use Statement, such as abbreviation, full name etc. In the case of abbreviations, the source of this form may or may not be explicitly mentioned.
domain:
  ressource: Type
sub property of: is referred to by

is related use for
type: Property
range:
  ressource: Nomen Use Statement
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F35 Nomen Use Statement with another instance of F35 Nomen Use Statement which has a related use in some context, such as alternative, lexical variant, replacing former use etc. The property R56.1 allows for specifying the particular kind of the nomen use statement relationship.
domain:
  ressource: Nomen Use Statement
sub property of: is associated with

is basis for
type: Property
range:
  ressource: Character
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F38 Character with an instance of E39 Actor that the character is motivated by or is intended to represent. An instance of F38 Character may be based on a combination of features taken from several actors. This property is a shortcut of the more fully developed path from E28 Conceptual Object, restricted to F38 Character, through the inverse of P94 has created (was created by), E65 Creation P17 was motivated by (motivated) to E1 CRM Entity restricted to E39 Actor.
domain:
  ressource: Actor

is fictional member of
type: Property
range:
  ressource: Character
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F38 Character representing a group with another instance of F38 Character that is presented in relevant fiction as a member of the fictional group.
domain:
  ressource: Character

was typical subject of
type: Property
range:
  ressource: Pursuit
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F51 Pursuit with the instance of E1 CRM Entity that is the typical subject of the associated activity, such as an area of expertise in which the actor is engaged or was engaged.
domain:
  ressource: CRM Entity

was language used by
type: Property
range:
  ressource: Pursuit
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F51 Pursuit with the instance of E56 Language that was characteristically used for the products of the associated activity. The property R60.1 has type of use allows for specifying a particular form of use.
domain:
  ressource: Language

was kind of context for
type: Property
range:
  ressource: Name Use Activity
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F52 Name Use Activity with the instance of E55 Type that characterises the kind of role or context within which the associated name was used.
domain:
  ressource: Type

was context for
type: Property
range:
  ressource: Name Use Activity
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F52 Name Use Activity with the instance of E74 Group that characterises the context within which the associated name was used for membership in that group.
domain:
  ressource: Group

was named by
type: Property
range:
  ressource: Name Use Activity
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F52 Name Use Activity with the instance of E1 CRM Entity that the associated name was used for.
domain:
  ressource: CRM Entity
sub property of: was attributed by

was name used by
type: Property
range:
  ressource: Name Use Activity
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F52 Name Use Activity with the instance of E41 Appellation that was used for the associated entity.
domain:
  ressource: Appellation
sub property of: was used for

had aspects recorded through
type: Property
range:
  ressource: Recording Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F29 Recording Event with an instance of E18 Physical Thing some of whose features, at the time of recording, were recorded in that process.
domain:
  ressource: Physical Thing

had a performed version through
type: Property
range:
  ressource: Performance
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F31 Performance with a product of the mind that was performed in the course of that instance of F31 Performance. According to the level of knowledge available about the performance, the range of this property can actually be specialised as either an instance of F1 Work (if nothing is known as to which specific expression of the work was performed), or of F2 Expression (if there is a reasonable amount of certainty as to which specific expression—e.g., a well identified translation of a play—of the work was performed). In addition to being a subproperty of P16 used specific object (was used for), this property also is a shortcut of the fully developed path that goes from F31 Performance to F1 Work through: R25 performed F25 Performance Plan P165 incorporates F22 Self-Contained Expression R3i realises. In this fully developed path, the specific instance of F22 Self-Contained Expression can be precisely identified and described for its own sake, or it can just be known to have necessarily existed.
domain:
  ressource: Propositional Object
sub property of: was used for