CRM for Creative Processes Representation Version 1.5
type: Ontology
imports: https://ontome.net/api/owl-wisski.rdf
version info: Exported from OntoME: CRM for Creative Processes Representation Version 1.5
comment: Scope Creative Processes Representation Conceptual Reference Model (CRMcpr) is an ontological model harmonizing to the CIDOC CRM family of models that aims to facilitate the representation and integration of information related to creative processes and the materialization of ideas into reality. It has a particular focus on creative processes. The presently proposed model and its related classes and properties have been modelled to cover architectural practice, artistic production, and design activities considered broadly. Examples Used In order to illustrate the ontology's use, the specification provides a related set of examples from architecture, the rebuild project on the site of the World Trade Centre, NY, and art the "Gates of Hell" by Rodin. Future editions aim to carry examples from additional fields. Compatibility and Nomenclature This unofficial extension of the CIDOC CRM is formulated in relation to: CIDOC CRM v.7.1.2 FRBRoo v.2.4 The specification consists of a set of declarations for formalized classes and properties that extend the CIDOC CRM and the above official extensions. Please note that FRBRoo 2.4 was formulated originally in relation to CIDOC CRM 6.2. In order to harmonize to the latest CIDOC CRM while using the FRBRoo modelling strategy we have ensured to use only classes and properties that are compatible across these two models. We choose to retain the modelling patterns of FRBRoo rather than the new model LRMoo which further restricts its scope to only library practice and loses many of the features that interest us in the modelling of creative process. Adopting the conventions of the CIDOC CRM each class and property have been given an identifier in addition to their names. The naming convention adopted for this extension is: CC = class CP = property The choice of these names was arbitrary, making a conceptual connection with the official CRM representation while clearly distinguishing the new classes and properties from those of either CRM…

Model
type: Class
notation: CC1
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects created during the creative design phase in order to represent aesthetic concepts. The propositional content contained in a model provides information regarding an overall CC13 Design Concept and can be used to understand some aspect of the creator’s intent. Instances of this class are information objects produced as a result of design processes (instances of F28 Expression Creation) undertaken in relation to the goals of an instance of an overall CC15 Design Conception activity which, in turn, typically intends to comply with the specifications of an instance of CC6 Programme. As a subclass of F22 Self-Contained Expression, an instance of CC1 Model realizes, in whole or in part, the propositional content of the instance of CC13 Design Concept. As a subclass of CC5 Formulation, an instance of CC1 Model may function to project representations of the relations of space and materiality of the CC13 Design Concept, via CC12 Event Trigger Template, such that these representations can be used as guides for their eventual realization in some manufactured object.
subclass of: Formulation

Realization
type: Class
notation: CC2
comment: This class comprises the event of the instantiated realization of a planned artistic concept (CC20 Oeuvre), into an objective, concretized form (material and / or informational). This activity follows plans and projections delivered from one of more creative processes, such as CC14 Programme Conception, CC15 Design Conception and CC16 Realization Planning. Each of these is capable of delivering one or more outputs in the form of instances of CC5 Formulations which can be used by an instance of CC2 Realization to attempt to bring into existence the aimed for artistic object (E22 Human-made Object and/or E73 Information Object).
subclass of: Production
subclass of: Creation

Realization Concept
type: Class
notation: CC3
comment: This class comprises combinations of concepts such as are found in planning documents, including BIM, details, drawings, sketches, diagrams, blueprints, descriptions, 3D representations etc. which altogether aim to describe an approach for realizing an artistic concept. The instance of CC3 Realization Concept is a complex set of ideas that is proposed as the intellectual response to a certain projected CC13 Design Concept, which has itself typically been expressed in a number of instances of CC1 Model. An instance of CC3 Realization Concept is the overall approach for how to interpret the latter into a plan for the design’s physical realization or materialization (CC2 Realization). An instance of CC3 Realization Concept is typically elaborated by an actor acting as the “Maitrise d’Oeuvre” through different planning documents (instances of CC4 Realization Plan) that represent particular aspects of the overall plan. In the normal case, one of these proposals will be selected (CC19 Assessment) as satisfying the CC13 Design Concept expressed in some particular set of instances of CC1 Model and will serve as the instance of CC4 Realization Plan that expresses the proposed CC3 Realization Concept. The substance of CC3 Realization Concept is ideas; with regards to realizing objects into reality, the ideas proposed typically deal with the planning of the execution of a CC1 Model into a physical object, while taking into account various real-world constraints regarding the organization of the events necessary to bring this end about (CC12 Event Trigger Template). An instance of CC3 Realization Concept is complex by nature as it interacts with the set of constraints expressed in one or more instances of CC1 Model that detail the conceptual and physical aspects of the spatial projection selected as expressing the CC13 Design Concept. The specific functionality of this class is to indicate the sets of concepts generated in order to plan the execution of an act of artistic reali…
subclass of: Complex Work

Realization Plan
type: Class
notation: CC4
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects created during CC16 Realization Planning activities, in order to express and represent aspects of a projected CC2 Realization to be undertaken and its outcome. The propositional content contained in an instance of CC4 Realization Plan provides information regarding some aspect of an overall concept for a CC3 Realization Concept and can be used to understand the intent of the one who drafted the plan. Instances of this class are information objects produced as the result of realization planning processes (instances of F28 Expression Creation) undertaken in relation to the goals of an instance of an overall CC16 Realization Planning activity which, in turn, aims to comply with the specifications of an instance of CC1 Model. An instance of CC4 Realization Plan represents, in whole or in part, the propositional content of the instance of CC3 Realization Concept.
subclass of: Formulation

Formulation
type: Class
notation: CC5
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects generated during creative conception activities which project certain potential events and objects into the world. The propositional content contained in a formulation provides information which represents particular creative concepts proposed for a certain project and which may provide information pertaining to a projected generated object and the manner of its CC2 Realization. Instances of this class are information objects arising through an activity of F28 Expression Creation, undertaken in relation to the goals of an instance of CC9 Oeuvre Conception, aiming towards realizing a creative idea. An instance of CC5 Formulation represents, in whole or in part, the propositional content of the instance of CC20 Oeuvre.
subclass of: Design or Procedure
subclass of: Expression

Programme
type: Class
notation: CC6
comment: This class comprises the particularly expressed, immaterial, intellectual content of objects created during the creative programmation phase in order to express and represent CC17 Projective Requirements for a particular overall artistic project. This class comprises instances of information objects expressing projective requirements, wishes and needs for some CC20 Oeuvre in a formalized manner. A finalized, accepted CC6 Programme provides an expression of the requirements that will be employed to guide and constrain an eventual CC13 Design Concept. An instance of CC6 Programme comes into existence from an activity of expression creation (instance of F28 Expression Creation) and aims to represent, in whole or in part, the propositional content of the instance of CC17 Projective Requirements.
subclass of: Formulation

Oeuvre Conception
type: Class
notation: CC9
comment: This class comprises the evolution of a set of activities that aim towards the common intent of realizing a creative work in a broad sense. The coming into existence of an instance of CC9 Oeuvre Conception marks the initiation of an instance of CC20 Oeuvre. The latter intellectually gathers together the ideas and formulations contained in the various subworks (CC17 Projective Requirements, CC13 Design Concept, CC3 Realization Concept) and their formal expressions (CC6 Programme, CC1 Model, CC4 Realization Plan) that serve the common goal of the work’s final realization (CC2 Realization). In a commercial sphere, this is frequently undertaken with the participation of a client team acting as a client or patron and an executing team acting as a designer or service provider. An instance of this class often comes into being alongside the assignment of two groups as holding the roles of client and realizer who are formally attributed statuses as such. An associated ‘witness’ of such a will motivates the documentation of an instance of this event. Where possible, then, instances of CC9 Oeuvre Conception should be associated to instances of ZE6 Social Status through the property ZP75i is context for which document the actors causally implicated in willing the existence of the oeuvre and the roles that they play respectively, especially via their playing the role of client or patron / design or service provider. The instance of CC9 Oeuvre Conception is considered to be on-going and to encompass the sub-activities undertaken towards the realization of the main goal as long as the two parties continue to pursue this aim.
subclass of: Work Conception

Object Trigger Template
type: Class
notation: CC11
comment: This class comprises specifications of projected artistic and architectural objects that detail constraints, specified as desired or necessary, that the projected object should comply with, according to a documented instance of CC5 Formulation. The function of CC11 Object Trigger Template is to allow the specification of qualities which the realized object should have such as dimension, material, function etc. The qualities specified here should be considered to stand as valid constraints to downstream and potentially upstream creative activities (CC14 Programme Conception, CC15 Design Conception, CC16 Realization Planning) within the context of an ongoing CC9 Oeuvre Conception, which can be used as to check conformity between desired and delivered outcomes ranging across realized plans (CC6 Programme, CC1 Model and CC4 Realization Plan) as well as the artistic object (E22 Human-made Object and/or E73 Information Object) finally generated through an act of CC2 Realization. For the documentation of the details of the constraints on the projected creation activity of a physical object (E22 Human-made Object), an associated instance of CC12 Event Trigger Template should be instantiated and connected through the property cp14i is stipulated object outcome.
subclass of: Propositional Object

Event Trigger Template
type: Class
notation: CC12
comment: This class comprises specifications of projected creative activities towards the CC2 Realization of a creative work. It details guidelines and constraints that downstream and upstream creative activities should comply with, according to a documented instance of CC5 Formulation. The specified constraints can be instantiated on the level of kinds of processes, items or qualities and quantities involved in the action. The qualities specified here should be considered to stand as valid constraints on downstream and potentially upstream creative activities (CC14 Programme Conception, CC15 Design Conception, CC16 Realization Planning) within the context of an ongoing CC9 Oeuvre, which can be used as a check of conformity between desired and delivered outcomes ranging across instances of CC5 Formulation subtypes (i.e., CC6 Programme, CC1 Model and CC4 Realization Plan) as well as the act of CC2 Realization itself, unless a newer instance of CC5 Formulation is created to supersede. An instance of an expected kind of outcome in terms of object, e.g. design or building, is typically implied in most instances of CC12 Event Trigger Template and should be documented via an instance of CC11 Object Trigger Template.
subclass of: Propositional Object

Design Concept
type: Class
notation: CC13
comment: This class comprises combinations of concepts found in creative expressions, such as drawings, sketches, diagrams, plans, descriptions, 3D representations etc, which together form an overall concept for a design. An instance of CC13 Design Concept is a complex set of ideas that is proposed as the intellectual response to a certain, projected creative aim, that may be documented as an instance of CC6 Programme, expressing the latter as particular creative design proposals. The CC13 Design Concept is typically elaborated by an actor in the role of ‘Maitrise d’Oeuvre’ through different design documents (instances of CC1 Model) that represent various aspects of the overall idea. The substance of CC13 Design Concept is ideas. An instance of CC13 Design Concept is complex by nature as it interacts with the set of requirements typically expressed in an instance of CC6 Programme, which concretizes the requirements set out by an instance of CC17 Projective Requirements. It is articulated through various documents expressing different collective proposals that will go through processes of selection and filtering. In the normal case, one of these proposals will be selected as satisfying the CC17 Projective Requirements expressed in a CC6 Programme and serve as the accepted instance(s) of CC1 Model that expresses the final CC13 Design Concept.
subclass of: Complex Work

Programme Conception
type: Class
notation: CC14
comment: This class comprises the beginning of the evolution of a set of activities that aim towards the formulation of user or client’s (e.g.: a designated “Maîtrise d'Ouvrage”) needs, wishes and requirements for a projected CC20 Oeuvre. The substance of programming is intentional activity towards generated CC17 Projective Requirements that will typically be formally specified and approved in a requirements document, an instance of CC6 Programme. The instance of CC14 Programme Conception begins when the client starts to formulate their needs, with or without external party participation of the eventually designated realizing party (e.g., a designated ‘Maîtrise d'Oeuvre’).
subclass of: Work Conception

Design Conception
type: Class
notation: CC15
comment: This class comprises the beginning of the evolution of a set of activities that aim towards the formulation of a creative design concept (CC13), realized in one or more instances of CC1 Model, that usually respond to an instance of CC17 Projective Requirements formulated for a projected creative work (CC20). The substance of design conception is intentional activity towards the formalization of a proposal detailing a (series of) model(s) (CC1) aiming to satisfy the initiating client’s requirements expressed in a formal programme (CC6). The instance of design conception begins when the actor charged with realizing the creative work (e.g.: the designated ‘Maîtrise d'Oeuvre’) starts the activities to formulate a design proposal, with or without an external party participating, which may or may not include the designated ‘Maîtrise d'Ouvrage’.
subclass of: Work Conception

Realization Planning
type: Class
notation: CC16
comment: This class comprises the beginning of the evolution of a set of activities that aim towards the articulation of a CC3 Realization Concept, concretized in one or more CC4 Realization Plans, which aim to accurately incorporate a specific set of design documents (instances of CC1 Model) into a plan to realize a creative idea, typically as a physical work (E22 Human-made Object). The instance of this event begins when an actor, such as that designated ‘Maîtrise d'Oeuvre’, starts the activities of formulating the plan towards realization, with or without an external party participating, which may or may not include the ‘Maîtrise d'Ouvrage’.
subclass of: Work Conception

Projective Requirements
type: Class
notation: CC17
comment: This class comprises distinct concepts or combinations of concepts embodying the aim, will and/or desire of an actor with regards to a particular projected CC20 Oeuvre. The instance of CC17 Projective Requirements is elicited from an actor either by him/herself or, more usually, with others, in order to express it in some concrete, documented form which will be used to guide the activities of a CC15 Design Conception. The substance of an instance of CC17 Projective Requirements is ideas in the sense of an articulated will, aim and desire with regards to a projected outcome, which is usually elaborated and reformulated over time in different iterations and derivations of the initial will, and finally realized in one or more CC6 Programmes, to be adopted as a guide in the design phase.
subclass of: Complex Work

Assessment
type: Class
notation: CC19
comment: This class comprises acts of evaluation of an instance of E73 Information Object against an implicit or explicit standard by some actor. An instance of CC19 Assessment is undertaken in order to provide some form of feedback and evaluation on the assessed instance of E73 Information Object in the form of a categorical assessment, a reviewed information object or both. An act of assessment may result in the assignment of an evaluative categorical rank to the assessed conceptual pattern. An act of assessment may also result in a revised version of the assessed instance of E73 Information Object being produced by the assessor. The newly resultant assessed instance of E73 Information Object may include additions, deletions, modifications and commentaries relative to the original target of assessment. The resultant instance information object is, then, considered to incorporate elements of the original E73 Information Object. The edge cases of an act of assessment are the rejection or acceptance of the assessed E73 Information Object. In the case of rejection, the assessed information object has been categorized as a failure by the assessing actor, potentially terminating a direction of creation. In the case of approval, the assessed information object is considered to have been categorized as accepted in toto qua information object by the assessor, relative to the standard of evaluation. Acts of assessment are considered to generate and be generated by instances of F28 Expression Creation in a cycle that typically aims towards achieving an acceptance evaluation. Within the context of a cycle of creative processes, an act of assessment resulting in an assignment of approval typically indicates that the assessor considers the main idea and all relevant additional parameters of judgement with regards to the formulation of the object to be satisfactory and to express the instance of F15 Complex Work which it was formulated to materialize.
subclass of: Type Assignment
subclass of: Creation

Oeuvre
type: Class
notation: CC20
comment: This class comprises combinations of concepts that together represent a recognizable novel intellectual content that is intended to be realized into a particular physical or conceptual form. The substance of an instance of this class is its unique set of ideas. An instance of this class is complex in that it is typically composed of a set of other ideas which together form its content. An instance of CC20 Oeuvre is typically formed of member works consisting of a CC17 Project Requirement, CC13 Design Concept and a CC4 Realization Plan. Together these works are progressively realized in order to be able to bring into existence a particular creation, physical or intellectual, through a CC2 Realization act. An instance of this class comes to be through its initiation by an activity of creation (CC9 Oeuvre Conception) which, in turn, entails the willing of the realization of this idea by one or more parties acting as patrons and service providers in turn. The substance of CC20 Oeuvre is ideas. An instance of CC20 Oeuvre represents the most abstract level of a creative intellectual project, and gathers together all the particular ideas created towards its expression into a larger whole. CC20 Oeuvre stands apart from any individual physical or intellectual creation undertaken in the elaboration of a creative idea and stands for the idea itself. The documentation of an instance of CC20 Oeuvre thus allows both for the richer elaboration of the elements that lead to an eventual physical or intellectual instantiation of the idea through tracing the individual processes and components leading to a final as well as supporting the possibility to document partially realized or mostly unrealized creative projects.
subclass of: Complex Work

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.

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

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…

Site
type: Class
notation: E27
comment: This class comprises pieces of land or sea floor. In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings and maps. Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location

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.

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.

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.

Place
type: Class
notation: E53
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.

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.

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.

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.

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.

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.

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.

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…

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.

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.

projects (was projected by)
type: ObjectProperty
range: Event Trigger Template
comment: This property describes the relation between a CC5 Formulation and a projected event it plans for. Instances of CC5 Formulation may contain detailed, analytic information regarding how the plan formulates an intended event, or set of events, to occur, documenting also how and under what conditions a specific event can be said to have taken place and achieved according to a set of agreed terms. By instantiating this property, an activity plan can be connected to the analytic information it details for the projected manner of execution of the event that it foresees.
notation: CP4
domain: Formulation

stipulates type of object outcome
type: ObjectProperty
range: Type
comment: This property describes what type of object has been stipulated in a CC12 Event Trigger Template, as expected to be brought into existence through the event it projects. The form of stipulation is categorical, specifying a kind of object to be produced but not its particular features.
notation: CP5
domain: Event Trigger Template

stipulates event type
type: ObjectProperty
range: Type
comment: This property describes what form of activity the projected event is expected to consist in, stipulating its basic nature such as: production, communication, design.
notation: CP6
domain: Event Trigger Template

stipulates actor type
type: ObjectProperty
range: Type
comment: This property describes the kind(s) of actor that a projected activity is foreseen to involve. It thus allows the description of kinds of participants in the foreseen event at the categorical level. A plan may, thus, call for a certain type of professional to be involved, a certain category of individual etc.
notation: CP7
domain: Event Trigger Template

stipulates place
type: ObjectProperty
range: Place
comment: This property describes the expected, real-world place where the projected event is supposed to occur.
notation: CP8
domain: Event Trigger Template

stipulates time-span
type: ObjectProperty
range: Time-Span
comment: This property describes the expected time-span within which the projected event is supposed to occur.
notation: CP9
domain: Event Trigger Template

stipulates actor
type: ObjectProperty
range: Actor
comment: This property describes instances of particular individuals persons or groups that are expected to participate within the projected event.
notation: CP10
domain: Event Trigger Template

stipulates equipment
type: ObjectProperty
range: Physical Thing
comment: This property describes instances of equipment (E18) that are stipulated as expected to be used in the carrying out of the projected event.
notation: CP11
domain: Event Trigger Template

stipulates particular method
type: ObjectProperty
range: Design or Procedure
comment: This property describes instances of design or procedures that are stipulated to be followed in the carrying out of the projected event.
notation: CP12
domain: Event Trigger Template

stipulates specific budget
type: ObjectProperty
range: Dimension
comment: This property describes the budget that is stipulated as a constraint to the carrying out of the projected event.
notation: CP13
domain: Event Trigger Template

stipulates object outcome
type: ObjectProperty
range: Object Trigger Template
comment: This property relates an instance of Event Trigger Template to an instance of Objecter Trigger Template that is specified to be an outcome of the projected event.
notation: CP14
domain: Event Trigger Template

stipulates sub-event
type: ObjectProperty
range: Event Trigger Template
comment: This property enables the documentation of planned sub-events stipulated as part of an overall projected event. It is used to link an instance of Event Trigger Template to another instance of this class which would be an element of its own execution. The intention of this property is to enable the modelling of the projection of a complex event with sub-elements.
notation: CP15
domain: Event Trigger Template

stipulates material
type: ObjectProperty
range: Material
comment: This property describes the material of which the projected object is expected to be comprised.
notation: CP16
domain: Object Trigger Template

stipulates site
type: ObjectProperty
range: Site
comment: This property describes a particular real world site at which the projected object is expected to be installed or placed.
notation: CP17
domain: Object Trigger Template

stipulates dimension
type: ObjectProperty
range: Dimension
comment: This property describes the expected dimensions of the projected object.
notation: CP18
domain: Object Trigger Template

stipulates function
type: ObjectProperty
range: Type
comment: This property describes the expected function of the projected object.
notation: CP19
domain: Object Trigger Template

stipulates reference
type: ObjectProperty
range: Information Object
comment: This property associates an instance of Object Trigger Template with an Information Object which is to be used as a reference in the making of the projected object. The end result should show similarity to the referenced object
notation: CP20
domain: Object Trigger Template

stipulates part
type: ObjectProperty
range: Object Trigger Template
comment: This property enables the documentation of expected parts of a planned object and the particular features of those parts.
notation: CP21
domain: Object Trigger Template

assessed
type: ObjectProperty
range: Information Object
comment: This property indicates that an assessment activity was carried out on an instance of information object.
notation: CP22
domain: Assessment

produced revision
type: ObjectProperty
range: Information Object
comment: This property indicates that a new information object was created out of an assessment activity. The generated instance of information object will incorporate the assessed information object but may have added, removed, or modified its content as part of the assessment activity.
notation: CP24
domain: Assessment

concerns extant object
type: ObjectProperty
range: Physical Thing
comment: This property describes instances of things that are the main object concerned in the realization of the projected new configuration of an extant object. The execution of the object template may result in modification or transformation of the object indicated by this property.
notation: CP25
domain: Object Trigger Template