PRESSoo version 1.2
type: Ontology
imports: https://ontome.net/api/owl-wisski.rdf
version info: Exported from OntoME: PRESSoo version 1.2
comment: Extension of CIDOC CRM and FRBRoo for the modelling of bibliographic information pertaining to continuing resources. Version 1.2 - January 2016.

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.

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.

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…

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.

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.

Contact Point
type: Class
notation: E51
comment: This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used. URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.

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

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

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

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.

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.

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.

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

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

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.

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

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

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.
subclass of: Publication Event

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.
subclass of: Publication Event

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.
subclass of: Publication Event

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.
subclass of: Contact Point

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

provided a continuation to
type: ObjectProperty
range: 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.
notation: Y1
domain: Serial Transformation

initiated as continuation
type: ObjectProperty
range: 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.
notation: Y2
domain: Serial Transformation
sub property of: R16

provided a replacement to
type: ObjectProperty
range: 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.
notation: Y3
domain: Serial Transformation

initiated as replacement
type: ObjectProperty
range: 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.
notation: Y4
domain: Serial Transformation
sub property of: R16

split
type: ObjectProperty
range: 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.
notation: Y5
domain: Serial Transformation

initiated
type: ObjectProperty
range: 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.
notation: Y6
domain: Serial Transformation
sub property of: R16

merged
type: ObjectProperty
range: 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.
notation: Y7
domain: Serial Transformation

merged into
type: ObjectProperty
range: 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.
notation: Y8
domain: Serial Transformation

absorbed
type: ObjectProperty
range: 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.
notation: Y9
domain: Absorption

enhanced
type: ObjectProperty
range: 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.
notation: Y10
domain: Absorption
sub property of: P16

separated
type: ObjectProperty
range: Serial Work
comment: This property associates an instance of Z3 Separation with an instance of F18 Serial Work that resulted from the separation.
notation: Y11
domain: Separation
sub property of: R16

separated from
type: ObjectProperty
range: Serial Work
comment: This property associates an instance of Z3 Separation with the instance of F18 Serial Work that was diminished through the separation.
notation: Y12
domain: Separation
sub property of: P12

provided surrogate to
type: ObjectProperty
range: 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.
notation: Y13
domain: Temporary Substitution

substituted with
type: ObjectProperty
range: 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.
notation: Y14
domain: Temporary Substitution
sub property of: P16

replaced
type: ObjectProperty
range: 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.
notation: Y15
domain: Issuing Rule Change
sub property of: P12

replaced with
type: ObjectProperty
range: 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.
notation: Y16
domain: Issuing Rule Change
sub property of: P16

launched
type: ObjectProperty
range: 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.
notation: Y17
domain: Starting of Publication

ended
type: ObjectProperty
range: 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.
notation: Y18
domain: Ending of Publication

concerned
type: ObjectProperty
range: 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.
notation: Y19
domain: Metadata Management

foresees type
type: ObjectProperty
range: 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.
notation: Y20
domain: Issuing Rule
sub property of: P67

foresees use of language
type: ObjectProperty
range: 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.
notation: Y21
domain: Issuing Rule
sub property of: foresees type

foresees sequencing pattern
type: ObjectProperty
range: 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.
notation: Y22
domain: Issuing Rule
sub property of: foresees type

foresees dimension
type: ObjectProperty
range: 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 ]
notation: Y23
domain: Issuing Rule
sub property of: P67

foresees use of title
type: ObjectProperty
range: 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.
notation: Y24
domain: Issuing Rule
sub property of: P67

foresees association with
type: ObjectProperty
range: 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.
notation: Y25
domain: Issuing Rule
sub property of: P69

foresees other edition
type: ObjectProperty
range: 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.
notation: Y26
domain: Issuing Rule
sub property of: foresees association with

foresees translation in
type: ObjectProperty
range: 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).
notation: Y27
domain: Issuing Rule
sub property of: foresees other edition

foresees URL
type: ObjectProperty
range: 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.
notation: Y28
domain: Issuing Rule
sub property of: P67

evolved into
type: ObjectProperty
range: 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.
notation: Y29
domain: Serial Work

was partially continued by
type: ObjectProperty
range: 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.
notation: Y30
domain: Serial Work

was superseded by
type: ObjectProperty
range: 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.
notation: Y31
domain: Serial Work

was split into
type: ObjectProperty
range: 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.
notation: Y32
domain: Serial Work

was merged with
type: ObjectProperty
range: 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
notation: Y33
domain: Serial Work

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

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

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

has former or current issuing rule
type: ObjectProperty
range: 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.
notation: Y37
domain: Serial Work
sub property of: R11

has current issuing rule
type: ObjectProperty
range: 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).
notation: Y38
domain: Serial Work
sub property of: has former or current issuing rule

is enhanced by monograph
type: ObjectProperty
range: 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.
notation: Y39
domain: Serial Work

enhances monograph
type: ObjectProperty
range: 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.
notation: Y40
domain: Serial Work

has former or current area of publication
type: ObjectProperty
range: 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.
notation: Y41
domain: Serial Work

has current area of publication
type: ObjectProperty
range: 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.]
notation: Y42
domain: Serial Work
sub property of: has former or current area of publication

is indicative of
type: ObjectProperty
range: 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.
notation: Y43
domain: Expression Fragment
sub property of: P2

foresees topic
type: ObjectProperty
range: 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.
notation: Y44
domain: Issuing Rule
sub property of: P67

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

aggregated in a single storage unit
type: ObjectProperty
range: 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.
notation: Y46
domain: Storage Unit Creation