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

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

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

Title
type: Class
notation: E35
comment: This class comprises the names assigned to works, such as texts, artworks or pieces of music. Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group. This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.
subclass of: Linguistic Object
subclass of: Appellation

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

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.
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

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

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

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

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

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

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

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

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

Serial Transformation
type: Class
notation: Z1
comment: This class comprises activities that transform instances of F18 Serial Work into new instances of F18 Serial Work. An instance of Z1 Serial Transformation consists of having the idea of starting the publication of one or more than one new serial (this is a particular case of F27 Work Conception), with a distinct intention of thus prolonging, under a new identity, one or more than one earlier serial, the publication of which has ceased, either due directly to the transformation project, or for any other reason. The idea of starting a new serial can be contiguous with the disappearance of a serial, or occur quite some time after that event. A transformation can be complete or only partial (e.g., a serial devoted to history of the Middle Ages and Renaissance can cease to be published as such and be continued by a new serial that is devoted to the Middle Ages only). This information element can be reflected through the P2 has type (is type of): E55 Type from the CIDOC CRM model. The most frequent cases of serial transformation are: continuation (in which a serial undergoes a major title change), replacement (in which a new serial supersedes an earlier serial), split (in which one serial is transformed into at least two serials), and merger (in which at least two serials are transformed into one serial). The temporary substitution of a serial with another serial (either pre-existing or created for that purpose) is not regarded as a serial transformation but simply as an episode within the publication process of the serial that temporarily disappeared (see Scope Note for Z4 Temporary Substitution). Cases of separation and absorption are not regarded as serial transformations either, as they do not involve the combination of the disappearance of a serial and the appearance of another serial, but just either the latter or the former.
subclass of: Work Conception

Absorption
type: Class
notation: Z2
comment: This class comprises activities that result in instances of F18 Serial Work being absorbed by pre-existing instances of F18 Serial Work. An absorption can be complete or only partial (e.g., a serial devoted to history in general can absorb specifically the portion devoted to the history of the Middle Ages of another serial that is devoted to the Middle Ages and Renaissance, while the portion devoted to the Renaissance is just abandoned). This information element can be reflected through the P2 has type (is type of): E55 Type from the CIDOC CRM model.
subclass of: Activity

Separation
type: Class
notation: Z3
comment: This class comprises activities that result in new instances of F18 Serial Work coming into being as the ‘offspring’ of pre-existing instances of F18 Serial Work that continue to be published after the separation has occurred.
subclass of: Work Conception

Temporary Substitution
type: Class
notation: Z4
comment: This class comprises activities that consist of publishing an instance of F18 Serial Work as a temporary replacement for another instance of F18 Serial Work. The replacing instance of F18 Serial Work can either pre-exist the replacement, or be created specifically for the purpose of replacing the other instance of F18 Serial Work.

Issuing Rule Change
type: Class
notation: Z5
comment: This class comprises activities resulting in the modification of an element of the issuing policy followed in publishing a given continuing resource.
subclass of: Activity

Starting of Publication
type: Class
notation: Z6
comment: This class comprises activities that consist of publishing the first issue of a given continuing resource. An instance of Z6 Starting of Publication is part of the instance of F30 Publication Event that realises the entire continuing resource, and it is associated with it through property P116 starts (is started by) (i.e., the starting point of the instance of Z6 Starting of Publication coincides with the starting point of the instance of F30 Publication Event). This class and Z7 Ending of Publication are not declared as disjoint, as the publication of the first issue of a continuing resource can also be the publication of its last issue, in cases where only one issue of a continuing resource was ever published. If no other issue of a continuing resource is published after the first issue, then both the instance of Z6 Starting of Publication and the instance of Z7 Ending of Publication P114 [are] equal in time to the instance of F30 Publication Event. As a matter of fact, the same event is then an instance of all three classes.

Ending of Publication
type: Class
notation: Z7
comment: This class comprises activities that consist of publishing the latest known issue of a given continuing resource. An instance of Z7 Ending of Publication is part of the instance of F30 Publication Event that realises the entire continuing resource, and it is associated with it through property P115 finishes (is finished by) (i.e., the ending point of the instance of Z7 Ending of Publication coincides with the ending point of the instance of F30 Publication Event). This class and Z6 Starting of Publication are not declared as disjoint, as the publication of the first issue of a continuing resource can also be the publication of its latest known issue, in cases where only one issue of a continuing resource was ever published. If no other issue of a continuing resource is published after the first issue, then both the instance of Z6 Starting of Publication and the instance of Z7 Ending of Publication P114 [are] equal in time to the instance of F30 Publication Event. As a matter of fact, the same event is then an instance of all three classes.

Metadata Management
type: Class
notation: Z8
comment: This class comprises activities performed by ISSN agencies (either at the international or a regional level) and consisting of exerting a responsibility on the metadata relating to a continuing resource identified by an ISSN, which includes, among other things: storing and preserving the metadata, checking the accuracy of the recorded information, making decisions as to whether new records and new ISSNs are required or not due to modifications in the continuing resource described, checking the uniqueness of key titles, etc. Z8 Metadata Management does not necessarily include the activity of creating the metadata. A set of ISSN metadata can be managed by various agencies over time, but at a given point in time it cannot be managed by more than one agency. In practice, information relating to the agency that was previously responsible for a given set of metadata is erased from that set of metadata when the responsibility on it is handed over to another agency.
subclass of: Activity

Storage Unit
type: Class
notation: Z9
comment: This class comprises unique combinations of instances of E18 Physical Thing that are bound together, or otherwise physically united, for the sake of preservation, and are communicated to library users as single, indivisible units. The individual components of a given instance of Z9 Storage Unit are generally instances of F4 Manifestation Singleton and/or F5 Item, but the binding itself that holds them together can be a valuable piece of cultural heritage that is worth describing for its own sake. Z9 Storage Unit makes it possible to account indifferently for the description of the various materials (printed or manuscript or of any other type) that make up a holding, and of the binding (or any other type of device, e.g. a box, a casket, etc.) that was produced for that holding, if needed.
subclass of: Manifestation Singleton

Sequencing Pattern
type: Class
notation: Z10
comment: This class comprises ‘forms anticipated to be used in designating volumes/issues, etc. and/or dates for the individual units of the serial (e.g. Volume ..., number ...)’ [FRBR definition]. A sequencing pattern is a type exemplified in one or more than one statement transcribed from one or more than one issue of a serial. The type itself is never recorded as such, but is only inferred from the transcribed statements.
subclass of: Type

URL
type: Class
notation: Z11
comment: This class comprises identifiers for servers from which digital files can be obtained online.

Issuing Rule
type: Class
notation: Z12
comment: This class comprises plans that specify bits of the issuing policy followed at some point in time for instances of F18 Serial Work. The notion of issuing policy may include: regularity, frequency, sequencing pattern, the language of the linguistic objects contained in each issue, dimension of each issue, the font used to print each issue, the layout and editorial rules adhered to in each issue, etc. [Note: The notion of issuing rule is to be understood differently in PRESS OO than in FRBR OO. In FRBR OO , property R11 has issuing rule (is issuing rule) points to a complete issuing policy that comprises a variety of parameters (regularity, frequency, dimension, language, etc.), while in PRESS OO an instance of Z12 Issuing Rule focuses on only one of those parameters and consists of a plan for just the expected regularity, just the expected frequency, just the expected dimension, etc. This perspective shift was made necessary when it was realized that any change (i.e., any instance of Z5 Issuing Rule Change) in just one of those parameters led to a new instantiation of Z12 Issuing Rule and new instantiations of all the ranges of the associated properties, with exactly the same value for each of them except for the one parameter that changes. It was deemed preferable to associate an instance of Z12 Issuing Rule with just one parameter of the issuing policy, which makes it possible that, e.g., a monthly was transformed into a quarterly without having to repeat that the expected language of its issues remains English.]
subclass of: Design or Procedure

Monograph
type: Class
notation: Z13
comment: This class comprises instances of F19 Publication Work that are planned to result in an instance of F24 Publication Expression that should either be complete in one part, or completed within a finite (and predetermined) number of parts, as opposed to instances of F18 Serial Work. [Adapted from Appendix E: Glossary of ISBD, International Standard Bibliographic Description: Consolidated Edition, 2011] F18 Serial Work and Z13 Monograph are two distinct subclasses of F19 Publication Work; however, they are neither declared as disjoint nor complementary, in order to allow for a certain amount of uncertainty as to the actual nature of some publications.
subclass of: Publication Work

Storage Unit Creation
type: Class
notation: Z14
comment: This class comprises activities through which instances of Z9 Storage Unit are produced. Although the activity of producing a storage unit can be motivated by preservation only, it inevitably results in the creation of an expression that consists of the sum of all expressions conveyed by the individual items and/or manifestation singletons that make up the resulting storage unit. Z14 Storage Unit Creation is therefore declared as a subclass of F28 Expression Creation. A given instance of Z14 Storage Unit Creation can involve truly artistic endeavours, such as the conception and realisation of a binding which can be regarded as a piece of cultural heritage in its own right.
subclass of: Expression Creation

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

occurred in the presence of
type: Property
range:
  ressource: Persistent Item
comment: This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role. It connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers.
domain:
  ressource: Event

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
sub property of: occurred in the presence of

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

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

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

provided a continuation to
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that underwent a ‘major’ title change that transformed it into another instance of F18 Serial Work.
domain:
  ressource: Serial Transformation

initiated as continuation
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that resulted from a ‘major’ title change that affected another instance of F18 Serial Work.
domain:
  ressource: Serial Transformation
sub property of: initiated

provided a replacement to
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work the publication of which had ceased and that was superseded by one or more than one instance of F18 Serial Work.
domain:
  ressource: Serial Transformation

initiated as replacement
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that was created with the distinct intention of being published in lieu of another instance of F18 Serial Work the publication of which had ceased.
domain:
  ressource: Serial Transformation
sub property of: initiated

split
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that was split in order to create new instances of F18 Serial Work.
domain:
  ressource: Serial Transformation

initiated
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with one or more than one instance of F18 Serial Work that resulted from splitting another instance of F18 Serial Work.
domain:
  ressource: Serial Transformation
sub property of: initiated

merged
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with any one of the instances of F18 Serial Work that were merged with each other in order to create a new instance of F18 Serial Work.
domain:
  ressource: Serial Transformation

merged into
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with the instance of F18 Serial Work that resulted from merging other instances of F18 Serial Work.
domain:
  ressource: Serial Transformation

absorbed
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z2 Absorption with an instance of F18 Serial Work that was absorbed in another instance of F18 Serial Work.
domain:
  ressource: Absorption

enhanced
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z2 Absorption with an instance of F18 Serial Work that absorbed another instance of F18 Serial Work.
domain:
  ressource: Absorption
sub property of: used specific object

separated
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z3 Separation with an instance of F18 Serial Work that resulted from the separation.
domain:
  ressource: Separation
sub property of: initiated

separated from
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z3 Separation with the instance of F18 Serial Work that was diminished through the separation.
domain:
  ressource: Separation
sub property of: occurred in the presence of

provided surrogate to
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z4 Temporary Substitution with an instance of F18 Serial Work the publication of which was interrupted and replaced with the publication of a distinct instance of F18 Serial Work.
domain:
  ressource: Temporary Substitution

substituted with
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z4 Temporary Substitution with an instance of F18 Serial Work that temporarily replaced a distinct instance of F18 Serial Work the publication of which was interrupted.
domain:
  ressource: Temporary Substitution
sub property of: used specific object

replaced
type: Property
range:
  ressource: Issuing Rule
comment: This property associates an instance of Z5 Issuing Rule Change with the instance of Z12 Issuing Rule that became obsolete through that process.
domain:
  ressource: Issuing Rule Change
sub property of: occurred in the presence of

replaced with
type: Property
range:
  ressource: Issuing Rule
comment: This property associates an instance of Z5 Issuing Rule Change with the instance of Z12 Issuing Rule that came into force through that process.
domain:
  ressource: Issuing Rule Change
sub property of: used specific object

launched
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z6 Starting of Publication with the serial the first issue of which was published through that process.
domain:
  ressource: Starting of Publication

ended
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z7 Ending of Publication with the serial the last issue of which was published through that process.
domain:
  ressource: Ending of Publication

concerned
type: Property
range:
  ressource: CRM Entity
comment: This property associates an instance of Z8 Metadata Management with the instance of F18 Serial Work that is described in the metadata over which the ISSN agency performing the instance of Z8 Metadata Management has a responsibility.
domain:
  ressource: Metadata Management

foresees type
type: Property
range:
  ressource: Type
comment: This property associates an instance of Z12 Issuing Rule with an instance of E55 Type that the issues of the continuing resource published while the instance of Z12 Issuing Rule obtained should have.
domain:
  ressource: Issuing Rule
sub property of: refers to

foresees use of language
type: Property
range:
  ressource: Language
comment: This property associates an instance of Z12 Issuing Rule with one or more than one language in which the contents of the serial are planned to be expressed. The Y21.1 mode of use property of the property makes it possible to specify whether the language pointed to is envisioned as the language of the main body of text or of the abstracts only or as one of several parallel languages, etc.
domain:
  ressource: Issuing Rule
sub property of: foresees type

foresees sequencing pattern
type: Property
range:
  ressource: Sequencing Pattern
comment: This property associates an instance of Z12 Issuing Rule with a sequencing pattern foreseen for the issues of a serial that follows that policy. Typically, a sequencing pattern is not recorded in its archetypical form, but through the transcription of a statement found on one or more than one issue of the serial. The complete semantics of the relation between the serial described and the statement transcribed is contained in the following circle: F18 Serial Work R10 has member F19 Publication Work [ = the concepts of the individual issue from which the statement is transcribed] R3 is realised in F24 Publication Expression R15 has fragment F23 Expression Fragment Y43 is indicative of Z10 Sequencing Pattern Y22i is sequencing pattern foreseen in Z12 Issuing Rule Y37i is former or current issuing rule of F18 Serial Work. FRBR ER distinguishes between the archetypical Sequencing Pattern, an attribute of the Expression entity, and the actual Numbering, an attribute of the Manifestation entity. The FRBR ER Sequencing Pattern notion corresponds to Z10 Sequencing Pattern in PRESS OO , while the FRBR ER Numbering corresponds to the instance of F23 Expression Fragment used to convey the archetypical sequencing pattern and does not call for a specific class in PRESS OO.
domain:
  ressource: Issuing Rule
sub property of: foresees type

foresees dimension
type: Property
range:
  ressource: Dimension
comment: This property associates an instance of Z12 Issuing Rule with a dimension foreseen for exemplars of the issues of a serial that follows that policy. Typically, this property is observed on one exemplar of an issue of a serial, and extrapolated to all other exemplars of the issue and of other issues to come. This logical inference is an induction along the path that can be modelled as: F18 Serial Work Y37 has former or current issuing rule Z12 Issuing Rule, and F18 Serial Work R10 has member F19 Publication Work R3 is realised in F24 Publication Expression R6i is carried by F5 Item P39i was measured by E16Measurement P40 observed dimension E54 Dimension. [adapted from scope note for CLP43 should have dimension in FRBR OO ]
domain:
  ressource: Issuing Rule
sub property of: refers to

foresees use of title
type: Property
range:
  ressource: Title
comment: This property associates an instance of Z12 Issuing Rule with the title that each individual issue of a serial should display as long as that serial follows that policy. The property Y24.1 has type allows for specifying a particular type of title, the same way as the CIDOC CRM property P102 has title (is title of) from E71 Man-Made Thing to E35 Title has a property, P102.1 has type, that makes it possible to clarify the relationship between a man-made thing and the title associated with it. The key title and abridged key title used to identify a serial cannot be referred to through this property, as they are artificial constructs forged by cataloguers, even though they may happen to look identical with the title proper foreseen by the issuing policy. The relationship betweenan instance of F18 Serial Work and a key title or abridged key title is expressed by using the P48 has preferred identifier property from CIDOC CRM.
domain:
  ressource: Issuing Rule
sub property of: refers to

foresees association with
type: Property
range:
  ressource: Issuing Rule
comment: This property associates an instance of Z12 Issuing Rule with an instance of Z12 Issuing Rule associated with a continuing resource that the first instance of Z12 Issuing Rule regards as related in some way with the continuing resource of which it is an issuing rule. It can denote a dynamic, asymmetric relationship where the range expresses the dependant publication, if such a direction can be established. Otherwise, it denotes a symmetric relationship, where none of the two continuing resources is regarded as dependant on the other. The Y25.1 has type property of the property allows the nature of the association to be specified; examples of types of association between instances of Z12 Issuing Rule include: supplement, issued with, insert, etc.
domain:
  ressource: Issuing Rule
sub property of: has association with

foresees other edition
type: Property
range:
  ressource: Issuing Rule
comment: This property associates an instance of Z12 Issuing Rule with an instance of Z12 Issuing Rule associated with a continuing resource that the first instance of Z12 Issuing Rule regards as another edition of the continuing resource of which it is an issuing rule. It can denote a dynamic, asymmetric relationship where the range expresses the dependant publication, if such a direction can be established. Otherwise, it denotes a symmetric relationship, where none of the two continuing resources is regarded as dependant on the other. In addition to being a subproperty of Y25 foresees association with (foresees to be associated with), it can also be analysed as a shortcut of the more developed path: Z12 Issuing Rule Y37i is former or current issuing rule of F18 Serial Work R10i is member of F15 Complex Work R10 has member F18 Serial Work Y37 has former or current issuing rule Z12 Issuing Rule. The Y26.1 has type property of the property allows the nature of the association to be specified; examples of types of association between instances of Z12 Issuing Rule include: other edition, other format, local edition, other edition on a different type of carrier, abridged edition, edition in a different language, etc.
domain:
  ressource: Issuing Rule
sub property of: foresees association with

foresees translation in
type: Property
range:
  ressource: CRM Entity
comment: This property associates an instance of Z12 Issuing Rule with an instance of Z12 Issuing Rule associated with a continuing resource that, according to the respective issuing policies of the two continuing resources, should contain a translation of the content of the first continuing resource. This is not the same notion as the association of a continuing resource with one or more than one ‘edition in a different language’, which is expressed through property Y26 foresees other edition (foresees to be another edition of).
domain:
  ressource: Issuing Rule
sub property of: foresees other edition

foresees URL
type: Property
range:
  ressource: URL
comment: This property associates an instance of Z12 Issuing Rule with an instance of Z11 URL that identifies the server from which digital files containing the issues of the continuing resource with which the instance of Z12 Issuing Rule is associated are available on the Web.
domain:
  ressource: Issuing Rule
sub property of: refers to

evolved into
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of F18 Serial Work with the instance of F18 Serial Work into which it was transformed, due to a ‘major’ title change.
domain:
  ressource: Serial Work

was partially continued by
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of F18 Serial Work with an instance of F18 Serial Work that was separated from it through an instance of Z3 Separation.
domain:
  ressource: Serial Work

was superseded by
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that was created with the distinct intention of being published in lieu of another instance of F18 Serial Work the publication of which had ceased.
domain:
  ressource: Serial Work

was split into
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of F18 Serial Work with any one of the instances of F18 Serial Work that were created on the occasion of its split.
domain:
  ressource: Serial Work

was merged with
type: Property
range:
  ressource: Serial Work
comment: This symmetrical property associates an instance of F18 Serial Work with any one of the instances of F18 Serial Work with which it was merged in order to create a new instance of F18 Serial Work
domain:
  ressource: Serial Work

was merged to form
type: Property
range:
  ressource: Serial Work
comment: This property associates instances of F18 Serial Work with an instance of F18 Serial Work that was created by merging them.
domain:
  ressource: Serial Work

was absorbed in
type: Property
range:
  ressource: Serial Work
comment: This property associates instances of F18 Serial Work with the instances of F18 Serial Work that absorbed them.
domain:
  ressource: Serial Work

had surrogate
type: Property
range:
  ressource: Serial Work
comment: This property associates an instance of F18 Serial Work with an instance of F18 Serial Work that temporarily replaced it.
domain:
  ressource: Serial Work

has former or current issuing rule
type: Property
range:
  ressource: Issuing Rule
comment: This property associates an instance of F18 Serial Work with instances of Z12 Issuing Rule that specify aspects of the issuing policy planned at some time by this Work, such as sequencing pattern, expected frequency or expected regularity. This property does not specify whether these instances of Z12 Issuing Rule are still in force at the time of validity of the record or database containing the statement that uses this property, and it can point to obsolete instances of Z12 Issuing Rule.
domain:
  ressource: Serial Work
sub property of: has issuing rule

has current issuing rule
type: Property
range:
  ressource: Issuing Rule
comment: This property associates an instance of F18 Serial Work with instances of Z12 Issuing Rule that specify aspects of the issuing policy planned by this Work, such as sequencing pattern, expected frequency or expected regularity, at the time of validity of the record or database containing the statement that uses this property. If the publication has ceased, this property reflects the latest known issuing rules followed by the continuing resource when its last known issue was released (i.e., the issuing rules followed in the instance of Z7 Ending of Publication associated with the continuing resource), rather than the ‘current’ issuing rules (since in that case, strictly speaking, there are no ‘current’ issuing rules).
domain:
  ressource: Serial Work
sub property of: has former or current issuing rule

is enhanced by monograph
type: Property
range:
  ressource: Monograph
comment: This property associates an instance of F18 Serial Work with an instance of Z13 Monograph that constitutes an enhancement of its content. [Note. The relationship between a series and a monograph published as a volume within that series, or between a periodical and one of its regular issues, is not expressed through this property, but by stating that the monograph or regular issue is a member of the series or periodical, i.e., F18 Serial Work R10 has member (is member of) F19 Publication Work.Special issues of a periodical that are included in that periodical’s numbering are also modelled simply as members of the periodical, not as monographs that enhance it.] The Y39.1 has type property of the property allows the nature of the association to be specified; examples of types of enhancement of an instance of F18 Serial Work by a monograph include: supplementing monograph, special issue, etc.
domain:
  ressource: Serial Work

enhances monograph
type: Property
range:
  ressource: Monograph
comment: This property associates an instance of F18 Serial Work with an instance of Z13 Monograph the content of which is enhanced by the instance of F18 Serial Work. The Y40.1 has type property of the property allows the nature of the association to be specified; examples of types of enhancement of a monograph by an instance of F18 Serial Work include: supplemented monograph, base volume for an updating loose-leaf, etc.
domain:
  ressource: Serial Work

has former or current area of publication
type: Property
range:
  ressource: Place
comment: This property associates an instance of F18 Serial Work with an instance of E53 Place that corresponds to the country (in the sense of ISO standard ISO 3166) in which the publisher (or one of the publishers) of the serial work is established. It makes no statement as to whether the publisher whose headquarters is located within the country referred to is still the publisher of the serial work at the time of validity of the record or database containing the statement that uses this property, nor does it make any statement as to whether the publisher is still located within that country.
domain:
  ressource: Serial Work

has current area of publication
type: Property
range:
  ressource: Place
comment: This property associates an instance of F18 Serial Work with an instance of E53 Place that corresponds to the country (in the sense of ISO standard ISO 3166) in which the publisher (or one of the publishers) of the serial work is established, at the time of validity of the record or database containing the statement that uses this property. [Comment: The choice of the ISSN agency that performs an instance of Z8 Metadata Management on a given instance of F18 Serial Work is determined by the current area(s) of publication of that instance of F18 Serial Work.]
domain:
  ressource: Serial Work
sub property of: has former or current area of publication

is indicative of
type: Property
range:
  ressource: Sequencing Pattern
comment: This property associates an instance of F23 Expression Fragment with the instance of Z10 Sequencing Pattern of which it provides an example.
domain:
  ressource: Expression Fragment
sub property of: has type

foresees topic
type: Property
range:
  ressource: CRM Entity
comment: This property associates an instance of Z12 Issuing Rule with an instance of E1 CRM Entity that is the main subject that all articles aggregated in each single issue of the serial should be about, even more or less loosely.
domain:
  ressource: Issuing Rule
sub property of: refers to

created
type: Property
range:
  ressource: Storage Unit
comment: This property associates an instance of Z14 Storage Unit Creation with the instances of Z9 Storage Unit in which it resulted.
domain:
  ressource: Storage Unit Creation
sub property of: created

aggregated in a single storage unit
type: Property
range:
  ressource: Physical Thing
comment: This property associates an instance of Z14 Storage Unit Creation with the instances of E18 Physical Thing that were aggregated in a single storage unit through that process.
domain:
  ressource: Storage Unit Creation

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

was present at
type: Property
range:
  ressource: Event
comment: This property is the inverse of the forward property described in the scope note that follows. This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role. It connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers.
domain:
  ressource: Persistent Item

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
sub property of: was present at

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

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

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

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

was continued through
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that underwent a ‘major’ title change that transformed it into another instance of F18 Serial Work.
domain:
  ressource: Serial Work

was initiated as continuation through
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that resulted from a ‘major’ title change that affected another instance of F18 Serial Work.
domain:
  ressource: Serial Work
sub property of: was initiated by

was replaced through
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work the publication of which had ceased and that was superseded by one or more than one instance of F18 Serial Work.
domain:
  ressource: Serial Work

was initiated as replacement through
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that was created with the distinct intention of being published in lieu of another instance of F18 Serial Work the publication of which had ceased.
domain:
  ressource: Serial Work
sub property of: was initiated by

was split through
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with an instance of F18 Serial Work that was split in order to create new instances of F18 Serial Work.
domain:
  ressource: Serial Work

resulted from split
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with one or more than one instance of F18 Serial Work that resulted from splitting another instance of F18 Serial Work.
domain:
  ressource: Serial Work
sub property of: was initiated by

was merged through
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with any one of the instances of F18 Serial Work that were merged with each other in order to create a new instance of F18 Serial Work.
domain:
  ressource: Serial Work

resulted from merger
type: Property
range:
  ressource: Serial Transformation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z1 Serial Transformation with the instance of F18 Serial Work that resulted from merging other instances of F18 Serial Work.
domain:
  ressource: Serial Work

was absorbed through
type: Property
range:
  ressource: Absorption
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z2 Absorption with an instance of F18 Serial Work that was absorbed in another instance of F18 Serial Work.
domain:
  ressource: Serial Work

was enhanced through
type: Property
range:
  ressource: Absorption
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z2 Absorption with an instance of F18 Serial Work that absorbed another instance of F18 Serial Work.
domain:
  ressource: Serial Work
sub property of: was used for

was separated through
type: Property
range:
  ressource: Separation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z3 Separation with an instance of F18 Serial Work that resulted from the separation.
domain:
  ressource: Serial Work
sub property of: was initiated by

was diminished through
type: Property
range:
  ressource: Separation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z3 Separation with the instance of F18 Serial Work that was diminished through the separation.
domain:
  ressource: Serial Work
sub property of: was present at

had surrogate through
type: Property
range:
  ressource: Temporary Substitution
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z4 Temporary Substitution with an instance of F18 Serial Work the publication of which was interrupted and replaced with the publication of a distinct instance of F18 Serial Work.
domain:
  ressource: Serial Work

became surrogate through
type: Property
range:
  ressource: Temporary Substitution
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z4 Temporary Substitution with an instance of F18 Serial Work that temporarily replaced a distinct instance of F18 Serial Work the publication of which was interrupted.
domain:
  ressource: Serial Work
sub property of: was used for

was replaced through
type: Property
range:
  ressource: Issuing Rule Change
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z5 Issuing Rule Change with the instance of Z12 Issuing Rule that became obsolete through that process.
domain:
  ressource: Issuing Rule
sub property of: was present at

was introduced through
type: Property
range:
  ressource: Issuing Rule Change
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z5 Issuing Rule Change with the instance of Z12 Issuing Rule that came into force through that process.
domain:
  ressource: Issuing Rule
sub property of: was used for

was launched through
type: Property
range:
  ressource: Starting of Publication
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z6 Starting of Publication with the serial the first issue of which was published through that process.
domain:
  ressource: Serial Work

was ended through
type: Property
range:
  ressource: Ending of Publication
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z7 Ending of Publication with the serial the last issue of which was published through that process.
domain:
  ressource: Serial Work

was the concern of
type: Property
range:
  ressource: Metadata Management
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z8 Metadata Management with the instance of F18 Serial Work that is described in the metadata over which the ISSN agency performing the instance of Z8 Metadata Management has a responsibility.
domain:
  ressource: CRM Entity

is type foreseen in
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with an instance of E55 Type that the issues of the continuing resource published while the instance of Z12 Issuing Rule obtained should have.
domain:
  ressource: Type
sub property of: is referred to by

is language foreseen in
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with one or more than one language in which the contents of the serial are planned to be expressed. The Y21.1 mode of use property of the property makes it possible to specify whether the language pointed to is envisioned as the language of the main body of text or of the abstracts only or as one of several parallel languages, etc.
domain:
  ressource: Language
sub property of: is type foreseen in

is sequencing pattern foreseen in
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with a sequencing pattern foreseen for the issues of a serial that follows that policy. Typically, a sequencing pattern is not recorded in its archetypical form, but through the transcription of a statement found on one or more than one issue of the serial. The complete semantics of the relation between the serial described and the statement transcribed is contained in the following circle: F18 Serial Work R10 has member F19 Publication Work [ = the concepts of the individual issue from which the statement is transcribed] R3 is realised in F24 Publication Expression R15 has fragment F23 Expression Fragment Y43 is indicative of Z10 Sequencing Pattern Y22i is sequencing pattern foreseen in Z12 Issuing Rule Y37i is former or current issuing rule of F18 Serial Work. FRBR ER distinguishes between the archetypical Sequencing Pattern, an attribute of the Expression entity, and the actual Numbering, an attribute of the Manifestation entity. The FRBR ER Sequencing Pattern notion corresponds to Z10 Sequencing Pattern in PRESS OO , while the FRBR ER Numbering corresponds to the instance of F23 Expression Fragment used to convey the archetypical sequencing pattern and does not call for a specific class in PRESS OO.
domain:
  ressource: Sequencing Pattern
sub property of: is type foreseen in

is dimension foreseen in
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with a dimension foreseen for exemplars of the issues of a serial that follows that policy. Typically, this property is observed on one exemplar of an issue of a serial, and extrapolated to all other exemplars of the issue and of other issues to come. This logical inference is an induction along the path that can be modelled as: F18 Serial Work Y37 has former or current issuing rule Z12 Issuing Rule, and F18 Serial Work R10 has member F19 Publication Work R3 is realised in F24 Publication Expression R6i is carried by F5 Item P39i was measured by E16Measurement P40 observed dimension E54 Dimension. [adapted from scope note for CLP43 should have dimension in FRBR OO ]
domain:
  ressource: Dimension
sub property of: is referred to by

is title foreseen in
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with the title that each individual issue of a serial should display as long as that serial follows that policy. The property Y24.1 has type allows for specifying a particular type of title, the same way as the CIDOC CRM property P102 has title (is title of) from E71 Man-Made Thing to E35 Title has a property, P102.1 has type, that makes it possible to clarify the relationship between a man-made thing and the title associated with it. The key title and abridged key title used to identify a serial cannot be referred to through this property, as they are artificial constructs forged by cataloguers, even though they may happen to look identical with the title proper foreseen by the issuing policy. The relationship betweenan instance of F18 Serial Work and a key title or abridged key title is expressed by using the P48 has preferred identifier property from CIDOC CRM.
domain:
  ressource: Title
sub property of: is referred to by

foresees to be associated with
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with an instance of Z12 Issuing Rule associated with a continuing resource that the first instance of Z12 Issuing Rule regards as related in some way with the continuing resource of which it is an issuing rule. It can denote a dynamic, asymmetric relationship where the range expresses the dependant publication, if such a direction can be established. Otherwise, it denotes a symmetric relationship, where none of the two continuing resources is regarded as dependant on the other. The Y25.1 has type property of the property allows the nature of the association to be specified; examples of types of association between instances of Z12 Issuing Rule include: supplement, issued with, insert, etc.
domain:
  ressource: Issuing Rule
sub property of: is associated with

foresees to be another edition of
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with an instance of Z12 Issuing Rule associated with a continuing resource that the first instance of Z12 Issuing Rule regards as another edition of the continuing resource of which it is an issuing rule. It can denote a dynamic, asymmetric relationship where the range expresses the dependant publication, if such a direction can be established. Otherwise, it denotes a symmetric relationship, where none of the two continuing resources is regarded as dependant on the other. In addition to being a subproperty of Y25 foresees association with (foresees to be associated with), it can also be analysed as a shortcut of the more developed path: Z12 Issuing Rule Y37i is former or current issuing rule of F18 Serial Work R10i is member of F15 Complex Work R10 has member F18 Serial Work Y37 has former or current issuing rule Z12 Issuing Rule. The Y26.1 has type property of the property allows the nature of the association to be specified; examples of types of association between instances of Z12 Issuing Rule include: other edition, other format, local edition, other edition on a different type of carrier, abridged edition, edition in a different language, etc.
domain:
  ressource: Issuing Rule
sub property of: foresees to be associated with

foresees translation of
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with an instance of Z12 Issuing Rule associated with a continuing resource that, according to the respective issuing policies of the two continuing resources, should contain a translation of the content of the first continuing resource. This is not the same notion as the association of a continuing resource with one or more than one ‘edition in a different language’, which is expressed through property Y26 foresees other edition (foresees to be another edition of).
domain:
  ressource: CRM Entity
sub property of: foresees to be another edition of

is URL foreseen in
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with an instance of Z11 URL that identifies the server from which digital files containing the issues of the continuing resource with which the instance of Z12 Issuing Rule is associated are available on the Web.
domain:
  ressource: URL
sub property of: is referred to by

continues
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 F18 Serial Work into which it was transformed, due to a ‘major’ title change.
domain:
  ressource: Serial Work

was separated from
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 an instance of F18 Serial Work that was separated from it through an instance of Z3 Separation.
domain:
  ressource: Serial Work

superseded
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 Z1 Serial Transformation with an instance of F18 Serial Work that was created with the distinct intention of being published in lieu of another instance of F18 Serial Work the publication of which had ceased.
domain:
  ressource: Serial Work

resulted from splitting
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 any one of the instances of F18 Serial Work that were created on the occasion of its split.
domain:
  ressource: Serial Work

[NO_INVERSE_LABEL_FOUND]
type: Property
range:
  ressource: Serial Work
comment: This property is the inverse of the forward property described in the scope note that follows. This symmetrical property associates an instance of F18 Serial Work with any one of the instances of F18 Serial Work with which it was merged in order to create a new instance of F18 Serial Work
domain:
  ressource: Serial Work

resulted from merging
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 instances of F18 Serial Work with an instance of F18 Serial Work that was created by merging them.
domain:
  ressource: Serial Work

was enhanced by absorbing
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 instances of F18 Serial Work with the instances of F18 Serial Work that absorbed them.
domain:
  ressource: Serial Work

was surrogate for
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 an instance of F18 Serial Work that temporarily replaced it.
domain:
  ressource: Serial Work

is former or current 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 instances of Z12 Issuing Rule that specify aspects of the issuing policy planned at some time by this Work, such as sequencing pattern, expected frequency or expected regularity. This property does not specify whether these instances of Z12 Issuing Rule are still in force at the time of validity of the record or database containing the statement that uses this property, and it can point to obsolete instances of Z12 Issuing Rule.
domain:
  ressource: Issuing Rule
sub property of: is issuing rule of

is current 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 instances of Z12 Issuing Rule that specify aspects of the issuing policy planned by this Work, such as sequencing pattern, expected frequency or expected regularity, at the time of validity of the record or database containing the statement that uses this property. If the publication has ceased, this property reflects the latest known issuing rules followed by the continuing resource when its last known issue was released (i.e., the issuing rules followed in the instance of Z7 Ending of Publication associated with the continuing resource), rather than the ‘current’ issuing rules (since in that case, strictly speaking, there are no ‘current’ issuing rules).
domain:
  ressource: Issuing Rule
sub property of: is former or current issuing rule of

enhances serial
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 an instance of Z13 Monograph that constitutes an enhancement of its content. [Note. The relationship between a series and a monograph published as a volume within that series, or between a periodical and one of its regular issues, is not expressed through this property, but by stating that the monograph or regular issue is a member of the series or periodical, i.e., F18 Serial Work R10 has member (is member of) F19 Publication Work.Special issues of a periodical that are included in that periodical’s numbering are also modelled simply as members of the periodical, not as monographs that enhance it.] The Y39.1 has type property of the property allows the nature of the association to be specified; examples of types of enhancement of an instance of F18 Serial Work by a monograph include: supplementing monograph, special issue, etc.
domain:
  ressource: Monograph

is enhanced by serial
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 an instance of Z13 Monograph the content of which is enhanced by the instance of F18 Serial Work. The Y40.1 has type property of the property allows the nature of the association to be specified; examples of types of enhancement of a monograph by an instance of F18 Serial Work include: supplemented monograph, base volume for an updating loose-leaf, etc.
domain:
  ressource: Monograph

is former or current area of publication 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 an instance of E53 Place that corresponds to the country (in the sense of ISO standard ISO 3166) in which the publisher (or one of the publishers) of the serial work is established. It makes no statement as to whether the publisher whose headquarters is located within the country referred to is still the publisher of the serial work at the time of validity of the record or database containing the statement that uses this property, nor does it make any statement as to whether the publisher is still located within that country.
domain:
  ressource: Place

is current area of publication 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 an instance of E53 Place that corresponds to the country (in the sense of ISO standard ISO 3166) in which the publisher (or one of the publishers) of the serial work is established, at the time of validity of the record or database containing the statement that uses this property. [Comment: The choice of the ISSN agency that performs an instance of Z8 Metadata Management on a given instance of F18 Serial Work is determined by the current area(s) of publication of that instance of F18 Serial Work.]
domain:
  ressource: Place
sub property of: is former or current area of publication of

is exemplified by
type: Property
range:
  ressource: Expression Fragment
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of F23 Expression Fragment with the instance of Z10 Sequencing Pattern of which it provides an example.
domain:
  ressource: Sequencing Pattern
sub property of: is type of

is topic foreseen in
type: Property
range:
  ressource: Issuing Rule
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z12 Issuing Rule with an instance of E1 CRM Entity that is the main subject that all articles aggregated in each single issue of the serial should be about, even more or less loosely.
domain:
  ressource: CRM Entity
sub property of: is referred to by

was created by
type: Property
range:
  ressource: Storage Unit Creation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z14 Storage Unit Creation with the instances of Z9 Storage Unit in which it resulted.
domain:
  ressource: Storage Unit
sub property of: was created by

was aggregated in a single storage unit through
type: Property
range:
  ressource: Storage Unit Creation
comment: This property is the inverse of the forward property described in the scope note that follows. This property associates an instance of Z14 Storage Unit Creation with the instances of E18 Physical Thing that were aggregated in a single storage unit through that process.
domain:
  ressource: Physical Thing