FRBR2.4-draft.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--
FRBRoo v2.4  DRAFT  harmonised with CIDOC CRM v6.2.1 encoded in RDFS
A formal ontology intended to capture and represent the underlying semantics of bibliographic information 
and to facilitate the integration, mediation, and interchange of bibliographic and museum information. 

International Working Group on FRBR/CIDOC CRM Harmonisation
affiliated to the IFLA FRBR Review Group and the CIDOC CRM Special Interest Group (CRM-SIG)

Created by ICS-FORTH (ISL-ICS) Thursday 16 June 2016

Encoding Rules:
1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores.
   The blank between the concept identifier and concept name is replaced by underscores.
   For instance "F3_Manifestation_Product_Type" or "R1_is_logical_successor_of".

2. RDF does not allow to instantiate properties beginning from a range value.
   Therefore, each FRBRoo property is represented as two RDFS properties.
   For instance "R1 is logical successor of (has successor)" is represented as:
   "R1_is_logical_successor_of" for the domain to range direction and "R1i_has_successor" for the range to domain direction.

3. Scope notes are represented as <rdf:comment> elements.
   
4. Any other differences in labels, scope notes  and semantic relationships of this encoding 
to the authoritative definition of the FRBRoo v2.4 (November 2015) are not intended transfer errors. 
FORTH appreciates your feed-back on such errors.

-->
<rdf:RDF xml:lang="en" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xml:base="http://iflastandards.info/ns/fr/frbr/frbroo/">

<rdfs:Class rdf:about="F1_Work">
	<rdfs:label xml:lang="en">Work</rdfs:label>
	<rdfs: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 aggregated expressions part of this work, but only parts of the resulting expression.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
</rdfs:Class>

<rdfs:Class rdf:about="F2_Expression">
	<rdfs:label xml:lang="en">Expression</rdfs:label>
	<rdfs: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 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 aggregated expressions part of this work, but only parts of the resulting expression.
If an instance of F2 Expression is of a specific form, such as text, image, etc., it may be simultaneously instantiated in the specific classes representing these forms in CIDOC CRM. Thereby one can make use of the more specific properties of these classes, such as language (which is applicable to instances of E33 Linguistic Object only).
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
</rdfs:Class>

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

<rdfs:Class rdf:about="F4_Manifestation_Singleton">
	<rdfs:label xml:lang="en">Manifestation Singleton</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E24_Physical_Man-Made_Thing"/>
</rdfs:Class>

<rdfs:Class rdf:about="F5_Item">
	<rdfs:label xml:lang="en">Item</rdfs:label>
	<rdfs:comment>This class comprises physical objects (printed books, scores, CDs, DVDs, CD-ROMS, etc.) that carry a F24 Publication Expression and were produced by an industrial process involving an F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F54_Utilized_Information_Carrier"/>
</rdfs:Class>

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

<rdfs:Class rdf:about="F7_Object">
	<rdfs:label xml:lang="en">Object</rdfs:label>
	<rdfs:comment>This class comprises all persistent physical items with a relatively stable form, man-made or natural.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdfs:Class>

<rdfs:Class rdf:about="F8_Event">
	<rdfs:label xml:lang="en">Event</rdfs:label>
	<rdfs:comment>This class comprises sets of coherent phenomena or cultural manifestations bounded in time and space.
It is the social or physical coherence of these phenomena that identify an E4 Period and not the associated spatio-temporal bounds. These bounds are a mere approximation of the actual process of growth, spread and retreat. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area as a sedentary culture.
Typically this class is used to describe prehistoric or historic periods such as the ‘Neolithic Period’, the ‘Ming Dynasty’ or the ‘McCarthy Era’. There are however no assumptions about the scale of the associated phenomena. In particular all events are seen as synthetic processes consisting of coherent phenomena. Therefore E4 Period is a superclass of E5 Event. For example, a modern clinical E67 Birth can be seen as both an atomic E5 Event and as an E4 Period that consists of multiple activities performed by multiple instances of E39 Actor.
There are two different conceptualisations of “artistic style”, defined either by physical features or by historical context. For example, Impressionism can be viewed as a period lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an E4 Period, and the second defines morphological object types that fall under E55 Type.
Another specific case of an E4 Period is the set of activities and phenomena associated with a settlement, such as the populated period of Nineveh.
[This is the Scope note for E4 Period in CIDOC CRM version 5.0.1]
[Note that in CIDOC CRM, E12 Production, E13 Attribute Assignment, and E65 Creation are indirect subclasses of E4 Period = F8 Event; as a consequence, F8 Event is an indirect superclass of: F27 Work Conception, F28 Expression Creation, F40 Identifier Assignment, F41 Representative Manifestation Assignment, F42 Representative Expression Assignment, F32 Carrier Production Event, F33 Reproduction Event, and F30 Publication Event]
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E4_Period"/>
</rdfs:Class>

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

<rdfs:Class rdf:about="F10_Person">
	<rdfs:label xml:lang="en">Person</rdfs:label>
	<rdfs:comment>This class comprises real persons who live or are assumed to have lived. Bibliographic identities or personae assumed by an individual or a group should be modelled as F12 Nomen and connected to the relevant person or group with an instance of F35 Nomen Use Statement, even if nothing more can be said about this person or group. In a bibliographic context, a name presented following the conventions usually employed for personal names will be assumed to correspond to an actual real person (F10 Person), unless evidence is available to indicate that this is not the case. The fact that a persona may erroneously be classified as an instance of F10 Person does not imply that the concept comprises personae
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E21_Person"/>
</rdfs:Class>

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

</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E74_Group"/>
</rdfs:Class>

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

<rdfs:Class rdf:about="F13_Identifier">
	<rdfs:label xml:lang="en">Identifier</rdfs:label>
	<rdfs:comment>This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents. [Adapted from the Scope Note of CIDOC CRM E42 Identifier ver. 5.0.1]
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E42_Identifier"/>
	<rdfs:subClassOf rdf:resource="F12_Nomen"/>
</rdfs:Class>

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

<rdfs:Class rdf:about="F15_Complex_Work">
	<rdfs:label xml:lang="en">Complex Work</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F1_Work"/>
</rdfs:Class>

<rdfs:Class rdf:about="F16_Container_Work">
	<rdfs:label xml:lang="en">Container Work</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F1_Work"/>
</rdfs:Class>

<rdfs:Class rdf:about="F17_Aggregation_Work">
	<rdfs:label xml:lang="en">Aggregation Work</rdfs:label>
	<rdfs:comment>This class comprises works whose essence is the selection and/or arrangement of expressions of one or more other works. This does not make the contents of the aggregated expressions part of this work, but only part of the resulting expression. F17 Aggregation Work may include additional original parts.
An expression of a work may include expressions of other works within it. For instance, an anthology of poems is regarded as a work in its own right that makes use of expressions of the individual poems that have been selected and ordered as part of an intellectual process.
A new version of an aggregate work does not make the resulting complex work an aggregate work as well. The inclusion of expressions from a complex work in an aggregation work does not make the aggregation work itself complex.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F14_Individual_Work"/>
	<rdfs:subClassOf rdf:resource="F16_Container_Work"/>
</rdfs:Class>

<rdfs:Class rdf:about="F18_Serial_Work">
	<rdfs:label xml:lang="en">Serial Work</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F15_Complex_Work"/>
	<rdfs:subClassOf rdf:resource="F19_Publication_Work"/>
</rdfs:Class>

<rdfs:Class rdf:about="F19_Publication_Work">
	<rdfs:label xml:lang="en">Publication Work</rdfs:label>
	<rdfs: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
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F16_Container_Work"/>
</rdfs:Class>

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

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

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

<rdfs:Class rdf:about="F23_Expression_Fragment">
	<rdfs:label xml:lang="en">Expression Fragment</rdfs:label>
	<rdfs: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.).
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F2_Expression"/>
</rdfs:Class>

<rdfs:Class rdf:about="F24_Publication_Expression">
	<rdfs:label xml:lang="en">Publication Expression</rdfs:label>
	<rdfs:comment>This class comprises complete sets of signs present in publications, reflecting publishers’ final decisions as to both selection of content and layout of the publications. Frequently the creation of a Publication Expression includes both adding graphical form and fonts to Expressions consisting of words alone and selecting illustrations and other content. As such, an instance of Publication Expression incorporates all Expressions combined for the resulting final form of rendering, whether visual, audio or tactile. An instance of Publication Expression is one entity regardless of the number of independent Expressions published within it, as long as it represents one unit of release. The published third party content can be associated via the property P165 incorporates (is incorporated in).
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F22_Self-Contained_Expression"/>
</rdfs:Class>

<rdfs:Class rdf:about="F25_Performance_Plan">
	<rdfs:label xml:lang="en">Performance Plan</rdfs:label>
	<rdfs:comment>This class comprises sets of directions to which individual performances of theatrical, choreographic, or musical works and their combinations should conform.
In the case of theatrical performances, such directions incorporate, but are not limited nor reducible to, the text of a given version of the play performed (e.g., a translated text, some passages of which are deliberately omitted, with some rephrased lines, etc.).
In the case of choreographic performances, such directions may incorporate, but are neither limited nor reducible to, the notation of choreographic movements in systems such as labanotation.
In the case of musical performances, such directions may incorporate, but are neither limited nor reducible to, the musical score. In case of electronic music, they may incorporate software instructions.
These directions may or may not completely determine the form of the intended performance. Depending on the nature of the directions, the form of the intended performance, such as the sets of movements or the sound characteristics, may or may not be predictable from the directions.
Note that a performance plan may be more or less elaborate, and may even foresee just improvisation.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
	<rdfs:subClassOf rdf:resource="F22_Self-Contained_Expression"/>
</rdfs:Class>

<rdfs:Class rdf:about="F26_Recording">
	<rdfs:label xml:lang="en">Recording</rdfs:label>
	<rdfs:comment>This class comprises expressions which are created in instances of F29 Recording Event. A recording is intended to convey (and preserve) the features of one or more perdurants.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F22_Self-Contained_Expression"/>
</rdfs:Class>

<rdfs:Class rdf:about="F27_Work_Conception">
	<rdfs:label xml:lang="en">Work Conception</rdfs:label>
	<rdfs: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.

</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E65_Creation"/>
</rdfs:Class>

<rdfs:Class rdf:about="F28_Expression_Creation">
	<rdfs:label xml:lang="en">Expression Creation</rdfs:label>
	<rdfs: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).
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E12_Production"/>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E65_Creation"/>
</rdfs:Class>

<rdfs:Class rdf:about="F29_Recording_Event">
	<rdfs:label xml:lang="en">Recording Event</rdfs:label>
	<rdfs:comment>This class comprises activities that intend to convey (and preserve) the features of perdurants in a recording, such as a live recording of a performance, a documentary, or other capture of a perdurant. Such activities may follow the directions of a recording plan. They may include postproduction.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F28_Expression_Creation"/>
</rdfs:Class>

<rdfs:Class rdf:about="F30_Publication_Event">
	<rdfs:label xml:lang="en">Publication Event</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="F28_Expression_Creation"/>
</rdfs:Class>

<rdfs:Class rdf:about="F31_Performance">
	<rdfs:label xml:lang="en">Performance</rdfs:label>
	<rdfs:comment>This class comprises activities that follow the directions of a performance plan, such as a theatrical play, an expression of a choreographic work or a musical work; i.e., they are intended to communicate directly or indirectly to an audience.
Such activities can be identified at various levels of granularity, and can be contiguous or not. Any individual performance (with or without intermissions) is a single instance of F31 Performance. In addition, a complete run of performances can also be seen as an instance of F31 Performance, with individual performances as parts. A complete run of performances may comprise an original run plus any of its extensions and tours.
Note that a performance plan may be more or less elaborate, and may even foresee just improvisation.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
</rdfs:Class>

<rdfs:Class rdf:about="F32_Carrier_Production_Event">
	<rdfs:label xml:lang="en">Carrier Production Event</rdfs:label>
	<rdfs:comment>This class comprises activities that result in instances of F54 Utilised Information Carrier coming into existence. Both the production of a series of physical objects (printed books, scores, CDs, DVDs, CD-ROMS, etc.) and the creation of a new copy of a file on an electronic carrier are regarded as instances of F32 Carrier Production Event.
Typically, the production of copies of a publication (no matter whether it is a book, a sound recording, a DVD, a cartographic resource, etc.) strives to produce items all as similar as possible to a prototype that displays all the features that all the copies of the publication should also display, which is reflected in property R27 used as source material F24 Publication Expression.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E12_Production"/>
</rdfs:Class>

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

<rdfs:Class rdf:about="F34_KOS">
	<rdfs:label xml:lang="en">KOS</rdfs:label>
	<rdfs:comment>This class comprises documents that establish controlled terminology (nomina) for consistent use. They may also describe relationships between entities and controlled terminology and relationships between entities. Note that any meaningful change in a Knowledge Organisation System (KOS) that affects the validity status of its elements defines a new release (Expression) of the KOS. Note that identifiers created following a rule in a KOS are to be regarded as being taken from this KOS, even though not explicitly spelled out. This definition of KOS reflects current library practice and not the use of the term in general.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E32_Authority_Document"/>
	<rdfs:subClassOf rdf:resource="F2_Expression"/>
</rdfs:Class>

<rdfs:Class rdf:about="F35_Nomen_Use_Statement">
	<rdfs:label xml:lang="en">Nomen Use Statement</rdfs:label>
	<rdfs:comment>This class comprises statements relating a Thema with a particular Nomen and its usage in the context of a common Complex Work realized by one or more KOS.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
	<rdfs:subClassOf rdf:resource="F2_Expression"/>
</rdfs:Class>

<rdfs:Class rdf:about="F36_Script_Conversion">
	<rdfs:label xml:lang="en">Script Conversion</rdfs:label>
	<rdfs:comment>This class comprises rule sets for converting signs or arrangements of signs from one script or type set to another.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
</rdfs:Class>

<rdfs:Class rdf:about="F38_Character">
	<rdfs:label xml:lang="en">Character</rdfs:label>
	<rdfs:comment>This class comprises fictional or iconographic individuals or groups of individuals (including families) appearing in works in a way relevant as subjects. Characters may be purely fictitious or based on real persons or groups, but as characters they may exhibit properties that would be inconsistent with a real person or group. Rather than merging characters with real persons, they should be described as disjoint, but related entities.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E28_Conceptual_Object"/>
</rdfs:Class>

<rdfs:Class rdf:about="F39_Family">
	<rdfs:label xml:lang="en">Family</rdfs:label>
	<rdfs:comment>This class comprises groups of two or more persons presented as a family justified by relationships of birth, marriage, adoption, civil union, or similar social or legal status and an assumed common tradition, including examples such as royal families, dynasties, houses of nobility, etc.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E74_Group"/>
</rdfs:Class>

<rdfs:Class rdf:about="F40_Identifier_Assignment">
	<rdfs:label xml:lang="en">Identifier Assignment</rdfs:label>
	<rdfs:comment>This class comprises activities that result in the allocation of an identifier to an instance of any subclass of E1 CRM Entity. An F40 Identifier Assignment may include the creation of the identifier from multiple constituents. Explicit reference to the used constituents can be made using the property P142 used constituent (was used in). The syntax of the identifier and the kinds of constituents to be used in constructing it may be declared in a rule. The construction of controlled access points for the names of persons, families and corporate bodies following specific cataloguing rules is a typical library application of identifier assignment. F40 Identifier Assignment also includes the assignment of controlled access points for works or expressions.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E15_Identifier_Assignment"/>
</rdfs:Class>

<rdfs:Class rdf:about="F41_Representative_Manifestation_Assignment">
	<rdfs:label xml:lang="en">Representative Manifestation Assignment</rdfs:label>
	<rdfs:comment>This class comprises activities through which an Agency declares (implicitly or explicitly) that a given instance of F3 Manifestation Product Type or F4 Manifestation Singleton is representative for a given F2 Expression, i.e., that some features found on that instance of F3 Manifestation Product Type or F4 Manifestation Singleton (most prominently, information about the title) can be inferred to also apply to that instance of F2 Expression, no matter within which manifestation it is embodied.
The reasoning behind is that the Work title is known through the title of an Expression that is deemed representative of the Work, and the title of the representative Expression is known through the title proper of a Manifestation that is deemed representative of the Expression representative of the Work.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E13_Attribute_Assignment"/>
</rdfs:Class>

<rdfs:Class rdf:about="F42_Representative_Expression_Assignment">
	<rdfs:label xml:lang="en">Representative Expression Assignment</rdfs:label>
	<rdfs:comment>This class comprises activities through which an Agency declares (implicitly or explicitly) that a given instance of F2 Expression is representative for a given F15 Complex Work, i.e., that some attributes of that instance of F2 Expression (most prominently, information about the title) can be inferred to also apply to that instance of F15 Complex Work, no matter in which particular expression it is realised.
The reasoning behind this is that the Work title is known through the title of an Expression that is deemed representative of the Work, and the title of the representative Expression is known through the title of a Manifestation that is deemed representative of the Expression that is representative of the Work.
For instance, by using the qualified controlled access point ‘Poe, Edgar Allan, 1809-1849. Murders in the rue Morgue (French)’ for the French rendition of Poe’s ‘Murders in the rue Morgue’ by Baudelaire, an Agency implicitly states that the French text does not constitute a representative F2 Expression for Poe’s F1 Work, however the original English text does constitute a representative F2 Expression for Poe’s F1 Work.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E13_Attribute_Assignment"/>
</rdfs:Class>

<rdfs:Class rdf:about="F43_Identifier_Rule">
	<rdfs:label xml:lang="en">Identifier Rule</rdfs:label>
	<rdfs:comment>This class comprises sets of instructions relating to the formulation of a unique identifier.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
	<rdfs:subClassOf rdf:resource="F2_Expression"/>
</rdfs:Class>

<rdfs:Class rdf:about="F44_Bibliographic_Agency">
	<rdfs:label xml:lang="en">Bibliographic Agency</rdfs:label>
	<rdfs:comment>This class comprises agents who create the bibliographic description of publications and perform the authority control associated with such descriptions, for the description of copies of such publications actually held by libraries, and for the description of unique documents (manuscripts, objects…) held by libraries.
The activity of creating such descriptions implies that one has to make decisions (as to the controlled access point for a work, as to whether an arrangement still belongs to the same work or is definitely a new work, etc.). Since such decisions always are debatable and different agencies can make different decisions about the same real-world entities, it is important to document which agency made which decision.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E40_Legal_Body"/>
</rdfs:Class>

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

<rdfs:Class rdf:about="F51_Pursuit">
	<rdfs:label xml:lang="en">Pursuit</rdfs:label>
	<rdfs:comment>This class comprises periods of continuous activity of an Actor in a specific professional or creative domain or field.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
</rdfs:Class>

<rdfs:Class rdf:about="F52_Name_Use_Activity">
	<rdfs:label xml:lang="en">Name Use Activity</rdfs:label>
	<rdfs:comment>This class comprises periods of continuous use of a specific instance of E41 Appellation for a particular instance of E1 CRM Entity by an E39 Actor. It includes in particular the use of the name by its carrier. Characteristically, actors performing an activity may choose a particular appellation for themselves in the context of this activity. Such cases should be modelled by additionally classifying these activities as instances of F52 Name Use Activity.
It is possible to specify the type of name use, through the P2 has type property, e.g.: use of a pseudonym, use of a married name, use of a birth name, use of a blended name, use of a religious name, etc.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E13_Attribute_Assignment"/>
</rdfs:Class>

<rdfs:Class rdf:about="F53_Material_Copy">
	<rdfs:label xml:lang="en">Material Copy</rdfs:label>
	<rdfs:comment>This class comprises the features created on an instance of E84 Information Carrier when an F24 Publication Expression is copied to it by an F32 Carrier Production Event. This is the typical result of an electronic publishing process.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E25_Man-Made_Feature"/>
	<rdfs:subClassOf rdf:resource="F54_Utilized_Information_Carrier"/>
</rdfs:Class>

<rdfs:Class rdf:about="F54_Utilized_Information_Carrier">
	<rdfs:label xml:lang="en">Utilized Information Carrier</rdfs:label>
	<rdfs:comment>This class comprises physical objects that carry one or more instances of F24 Publication Expression.
</rdfs:comment>
	<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
</rdfs:Class>

<rdf:Property rdf:about="CLP2_should_have_type">
	<rdfs:label xml:lang="en">should have type</rdfs:label>
	<rdfs:comment>This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E55 Type, which all exemplars of that publication should belong to, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E55 Type.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
</rdf:Property>

<rdf:Property rdf:about="CLP2i_should_be_type_of">
	<rdfs:label xml:lang="en">should be type of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="CLP43_should_have_dimension">
	<rdfs:label xml:lang="en">should have dimension</rdfs:label>
	<rdfs:comment>This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E54 Dimension, which all exemplars of that publication should have, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P39i was measured by E16 Measurement P40 observed dimension E54 Dimension.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
</rdf:Property>

<rdf:Property rdf:about="CLP43i_should_be_dimension_of">
	<rdfs:label xml:lang="en">should be dimension of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="CLP45_should_consist_of">
	<rdfs:label xml:lang="en">should consist of</rdfs:label>
	<rdfs:comment>This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E57 Material, which all exemplars of that publication should consist of, as long as they are recognised as exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P41i was classified by E17 Type Assignment P42 assigned E57 Material.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E57_Material"/>
</rdf:Property>

<rdf:Property rdf:about="CLP45i_should_be_incorporated_in">
	<rdfs:label xml:lang="en">should be incorporated in</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E57_Material"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="CLP46_should_be_composed_of">
	<rdfs:label xml:lang="en">should be composed of</rdfs:label>
	<rdfs:comment>This property associates an instance of F3 Manifestation Product Type which prescribes that all its Items will contain as parts an Item of another instance of F3 Manifestation Product Type with that instance of F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="CLP46i_may_form_part_of">
	<rdfs:label xml:lang="en">may form part of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="CLP57_should_have_number_of_parts">
	<rdfs:label xml:lang="en">should have number of parts</rdfs:label>
	<rdfs:comment>This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E60 Number, which denotes the number of physical units all exemplars of that publication should consist of, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication. This logical inference is an induction along the path that can be modelled as: F3 Manifestation Product Type R7i has example F5 Item P57 has number of parts E60 Number.
It can happen that a given exemplar, or subset of exemplars, originally produced, or intended to be produced, with that characteristic, accidentally lacks it. This fact should be recorded as a property of F5 Item, and not of F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>

<rdf:Property rdf:about="CLP104_subject_to">
	<rdfs:label xml:lang="en">subject to</rdfs:label>
	<rdfs:comment>This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E30 Right, which applies to all exemplars of that publication, as long as they are recognised as exemplars of that publication.
The rights covered by this property may include: acquisition or access authorisation; terms of availability; access restrictions on the Manifestation Product Type; etc.
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E30_Right"/>
</rdf:Property>

<rdf:Property rdf:about="CLP104i_applies_to">
	<rdfs:label xml:lang="en">applies to</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E30_Right"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="CLP105_right_held_by">
	<rdfs:label xml:lang="en">right held by</rdfs:label>
	<rdfs:comment>This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of E39 Actor, who holds an instance of E30 Right on all exemplars of that publication, as long as they are recognised as exemplars of that publication.
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E39_Actor"/>
</rdf:Property>

<rdf:Property rdf:about="CLP105i_right_on">
	<rdfs:label xml:lang="en">right on</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E39_Actor"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

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

<rdf:Property rdf:about="CLR6i_should_be_carried_by">
	<rdfs:label xml:lang="en">should be carried by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F24_Publication_Expression"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R1_is_logical_successor_of">
	<rdfs:label xml:lang="en">is logical successor of</rdfs:label>
	<rdfs:comment>This property associates an instance of F1 Work which logically continues the content of another instance of F1 Work with the latter.
</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R1i_has_successor">
	<rdfs:label xml:lang="en">has successor</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R2_is_derivative_of">
	<rdfs:label xml:lang="en">is derivative of</rdfs:label>
	<rdfs:comment>This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter. The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation etc.
</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R2i_has_derivative">
	<rdfs:label xml:lang="en">has derivative</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

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

<rdf:Property rdf:about="R3i_realises">
	<rdfs:label xml:lang="en">realises</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F22_Self-Contained_Expression"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R4_carriers_provided_by">
	<rdfs:label xml:lang="en">carriers provided by</rdfs:label>
	<rdfs:comment>This property associates a publication, i.e. an instance of F3 Manifestation Product Type, with an instance of F2 Expression, which all exemplars of that publication should carry, as long as they are recognised as complete exemplars of that publication. Typically, this property is observed on one exemplar of a publication, and extrapolated to all other exemplars of the same publication.
This property is a shortcut of: F2 Expression P165i is incorporated in F24 Publication Expression CLR6i should be carried by F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R4i_comprises_carriers_of">
	<rdfs:label xml:lang="en">comprises carriers of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R5_has_component">
	<rdfs:label xml:lang="en">has component</rdfs:label>
	<rdfs:comment>This property associates an F2 Expression X with a structural component Y that conveys in itself the complete concept of a work that is member of (R10) the overall work realized by X.
It does not cover the relationship that exists between pre-existing expressions that are re-used in a new, larger expression and that new, larger expression. Such a relationship is modelled by P165 incorporates.
</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F22_Self-Contained_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R5i_is_component_of">
	<rdfs:label xml:lang="en">is component of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F22_Self-Contained_Expression"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R6_carries">
	<rdfs:label xml:lang="en">carries</rdfs:label>
	<rdfs:comment>This property associates an instance of F54 Utilised Information Carrier with the unique instance of F24 Publication Expression it carries.
</rdfs:comment>
	<rdfs:domain rdf:resource="F54_Utilized_Information_Carrier"/>
	<rdfs:range rdf:resource="F24_Publication_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R6i_is_carried_by">
	<rdfs:label xml:lang="en">is carried by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F24_Publication_Expression"/>
	<rdfs:range rdf:resource="F54_Utilized_Information_Carrier"/>
</rdf:Property>

<rdf:Property rdf:about="R7_is_example_of">
	<rdfs:label xml:lang="en">is example of</rdfs:label>
	<rdfs:comment>This property associates a publication with one of its exemplars.
It is a shortcut of the more developed path: F5 Item R28i was produced by F32 Carrier Production R26 produced things of type (was produced by): F3 Manifestation Product Type.
</rdfs:comment>
	<rdfs:domain rdf:resource="F5_Item"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R7i_has_example">
	<rdfs:label xml:lang="en">has example</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="F5_Item"/>
</rdf:Property>

<rdf:Property rdf:about="R8_consists_of">
	<rdfs:label xml:lang="en">consists of</rdfs:label>
	<rdfs:comment>This property associates an instance of F13 Identifier with one of the non-syntactic instances of E90 Symbolic Object which form part of it.
</rdfs:comment>
	<rdfs:domain rdf:resource="F13_Identifier"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E90_Symbolic_Object"/>
</rdf:Property>

<rdf:Property rdf:about="R8i_forms_part_of">
	<rdfs:label xml:lang="en">forms part of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E90_Symbolic_Object"/>
	<rdfs:range rdf:resource="F13_Identifier"/>
</rdf:Property>

<rdf:Property rdf:about="R9_is_realised_in">
	<rdfs:label xml:lang="en">is realised in</rdfs:label>
	<rdfs:comment>This property associates an F14 Individual Work with the unique F22 Self-Contained Expression that completely conveys it.
It is a shortcut for the more developed path: F14 Individual Work R19i was realised through F28 Expression Creation R17 created F22 Self-Contained Expression.
</rdfs:comment>
	<rdfs:domain rdf:resource="F14_Individual_Work"/>
	<rdfs:range rdf:resource="F22_Self-Contained_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R9i_realises">
	<rdfs:label xml:lang="en">realises</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F22_Self-Contained_Expression"/>
	<rdfs:range rdf:resource="F14_Individual_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R10_has_member">
	<rdfs:label xml:lang="en">has member</rdfs:label>
	<rdfs:comment>This property associates an instance of F15 Complex Work with an instance of F1 Work that forms part of it. 
</rdfs:comment>
	<rdfs:domain rdf:resource="F15_Complex_Work"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R10i_is_member_of">
	<rdfs:label xml:lang="en">is member of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F15_Complex_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R11_has_issuing_rule">
	<rdfs:label xml:lang="en">has issuing rule</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:domain rdf:resource="F18_Serial_Work"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
</rdf:Property>

<rdf:Property rdf:about="R11i_is_issuing_rule_of">
	<rdfs:label xml:lang="en">is issuing rule of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
	<rdfs:range rdf:resource="F18_Serial_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R12_is_realised_in">
	<rdfs:label xml:lang="en">is realised in</rdfs:label>
	<rdfs:comment>This property associates an instance of F20 Performance Work with an instance of F25 Performance Plan that consists of signs (words, figures, etc.) which express the directions the instance of F20 Performance Work consists of.
</rdfs:comment>
	<rdfs:domain rdf:resource="F20_Performance_Work"/>
	<rdfs:range rdf:resource="F25_Performance_Plan"/>
</rdf:Property>

<rdf:Property rdf:about="R12i_realises">
	<rdfs:label xml:lang="en">realises</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F25_Performance_Plan"/>
	<rdfs:range rdf:resource="F20_Performance_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R13_is_realised_in">
	<rdfs:label xml:lang="en">is realised in</rdfs:label>
	<rdfs:comment>This property associates an instance of F21 Recording Work with an instance of F26 Recording realising the instance of F21 Recording Work.
This is a shortcut of the more elaborated path through R22 was realised through, F29 Recording Event and R21 created, which should be used when information about the recording event is available.
</rdfs:comment>
	<rdfs:domain rdf:resource="F21_Recording_Work"/>
	<rdfs:range rdf:resource="F26_Recording"/>
</rdf:Property>

<rdf:Property rdf:about="R13i_realises">
	<rdfs:label xml:lang="en">realises</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F26_Recording"/>
	<rdfs:range rdf:resource="F21_Recording_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R15_has_fragment">
	<rdfs:label xml:lang="en">has fragment</rdfs:label>
	<rdfs:comment>This property associates the fragment of an expression and the expression of which it is a fragment.
</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F23_Expression_Fragment"/>
</rdf:Property>

<rdf:Property rdf:about="R15i_is_fragment_of">
	<rdfs:label xml:lang="en">is fragment of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F23_Expression_Fragment"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R16_initiated">
	<rdfs:label xml:lang="en">initiated</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:domain rdf:resource="F27_Work_Conception"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R16i_was_initiated_by">
	<rdfs:label xml:lang="en">was initiated by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F27_Work_Conception"/>
</rdf:Property>

<rdf:Property rdf:about="R17_created">
	<rdfs:label xml:lang="en">created</rdfs:label>
	<rdfs:comment>This property associates the expression that was first externalised during a particular creation event with that particular creation event.
</rdfs:comment>
	<rdfs:domain rdf:resource="F28_Expression_Creation"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R17i_was_created_by">
	<rdfs:label xml:lang="en">was created by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F28_Expression_Creation"/>
</rdf:Property>

<rdf:Property rdf:about="R18_created">
	<rdfs:label xml:lang="en">created</rdfs:label>
	<rdfs: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.
</rdfs:comment>
	<rdfs:domain rdf:resource="F28_Expression_Creation"/>
	<rdfs:range rdf:resource="F4_Manifestation_Singleton"/>
</rdf:Property>

<rdf:Property rdf:about="R18i_was_created_by">
	<rdfs:label xml:lang="en">was created by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F4_Manifestation_Singleton"/>
	<rdfs:range rdf:resource="F28_Expression_Creation"/>
</rdf:Property>

<rdf:Property rdf:about="R19_created_a_realization_of">
	<rdfs:label xml:lang="en">created a realization of</rdfs:label>
	<rdfs:comment>This property associates an instance of F28 Expression Creation with the corresponding instance of F14 Individual Work or an instance of F15 Complex Work of which the corresponding instance of F14 Individual Work is a member.
</rdfs:comment>
	<rdfs:domain rdf:resource="F28_Expression_Creation"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R19i_was_realised_through">
	<rdfs:label xml:lang="en">was realised through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F28_Expression_Creation"/>
</rdf:Property>

<rdf:Property rdf:about="R20_recorded">
	<rdfs:label xml:lang="en">recorded</rdfs:label>
	<rdfs:comment>This property associates an instance of F29 Recording Event with the instance of E2 Temporal Entity which was captured.
</rdfs:comment>
	<rdfs:domain rdf:resource="F29_Recording_Event"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity"/>
</rdf:Property>

<rdf:Property rdf:about="R20i_was_recorded_through">
	<rdfs:label xml:lang="en">was recorded through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity"/>
	<rdfs:range rdf:resource="F29_Recording_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R21_created">
	<rdfs:label xml:lang="en">created</rdfs:label>
	<rdfs:comment>This property associates an instance of F29 Recording Event with the instance of F26 Recording that was created.
</rdfs:comment>
	<rdfs:domain rdf:resource="F29_Recording_Event"/>
	<rdfs:range rdf:resource="F26_Recording"/>
</rdf:Property>

<rdf:Property rdf:about="R21i_was_created_through">
	<rdfs:label xml:lang="en">was created through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F26_Recording"/>
	<rdfs:range rdf:resource="F29_Recording_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R22_created_a_realization_of">
	<rdfs:label xml:lang="en">created a realization of</rdfs:label>
	<rdfs:comment>This property associates an instance of F29 Recording Event with the instance of F21 Recording Work it realised.
</rdfs:comment>
	<rdfs:domain rdf:resource="F29_Recording_Event"/>
	<rdfs:range rdf:resource="F21_Recording_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R22i_was_realised_through">
	<rdfs:label xml:lang="en">was realised through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F21_Recording_Work"/>
	<rdfs:range rdf:resource="F29_Recording_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R23_created_a_realization_of">
	<rdfs:label xml:lang="en">created a realization of</rdfs:label>
	<rdfs:comment>This property associates an instance of F30 Publication Event with the instance of F19 Publication Work it realised.
</rdfs:comment>
	<rdfs:domain rdf:resource="F30_Publication_Event"/>
	<rdfs:range rdf:resource="F19_Publication_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R23i_was_realised_through">
	<rdfs:label xml:lang="en">was realised through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F19_Publication_Work"/>
	<rdfs:range rdf:resource="F30_Publication_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R24_created">
	<rdfs:label xml:lang="en">created</rdfs:label>
	<rdfs:comment>This property associates the instance of F24 Publication Expression that was created during a particular F30 Publication Event with that F30 Publication Event.
</rdfs:comment>
	<rdfs:domain rdf:resource="F30_Publication_Event"/>
	<rdfs:range rdf:resource="F24_Publication_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R24i_was_created_through">
	<rdfs:label xml:lang="en">was created through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F24_Publication_Expression"/>
	<rdfs:range rdf:resource="F30_Publication_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R25_performed">
	<rdfs:label xml:lang="en">performed</rdfs:label>
	<rdfs:comment>This property associates an instance of F31 Performance with the instance of F25 Performance Plan to which all those participating in the performance were supposed to conform.
</rdfs:comment>
	<rdfs:domain rdf:resource="F31_Performance"/>
	<rdfs:range rdf:resource="F25_Performance_Plan"/>
</rdf:Property>

<rdf:Property rdf:about="R25i_was_performed_in">
	<rdfs:label xml:lang="en">was performed in</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F25_Performance_Plan"/>
	<rdfs:range rdf:resource="F31_Performance"/>
</rdf:Property>

<rdf:Property rdf:about="R26_produced_things_of_type">
	<rdfs:label xml:lang="en">produced things of type</rdfs:label>
	<rdfs:comment>This property associates an instance of F32 Carrier Production Event with the instance of F3 Manifestation Product Type it produced items of.
</rdfs:comment>
	<rdfs:domain rdf:resource="F32_Carrier_Production_Event"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R26i_was_produced_by">
	<rdfs:label xml:lang="en">was produced by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="F32_Carrier_Production_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R27_used_as_source_material">
	<rdfs:label xml:lang="en">used as source material</rdfs:label>
	<rdfs:comment>This property associates an instance of F32 Carrier Production Event with the set of signs provided by the publisher to be carried by all of the produced items.
</rdfs:comment>
	<rdfs:domain rdf:resource="F32_Carrier_Production_Event"/>
	<rdfs:range rdf:resource="F24_Publication_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R27i_was_used_by">
	<rdfs:label xml:lang="en">was used by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F24_Publication_Expression"/>
	<rdfs:range rdf:resource="F32_Carrier_Production_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R28_produced">
	<rdfs:label xml:lang="en">produced</rdfs:label>
	<rdfs:comment>This property associates an instance of F32 Carrier Production Event with any one of the produced items (i.e., the instances of F5 Item or F53 Material Copy).
</rdfs:comment>
	<rdfs:domain rdf:resource="F32_Carrier_Production_Event"/>
	<rdfs:range rdf:resource="F54_Utilized_Information_Carrier"/>
</rdf:Property>

<rdf:Property rdf:about="R28i_was_produced_by">
	<rdfs:label xml:lang="en">was produced by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F54_Utilized_Information_Carrier"/>
	<rdfs:range rdf:resource="F32_Carrier_Production_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R29_reproduced">
	<rdfs:label xml:lang="en">reproduced</rdfs:label>
	<rdfs:comment>This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it reproduces.
</rdfs:comment>
	<rdfs:domain rdf:resource="F33_Reproduction_Event"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
</rdf:Property>

<rdf:Property rdf:about="R29i_was_reproduced_by">
	<rdfs:label xml:lang="en">was reproduced by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
	<rdfs:range rdf:resource="F33_Reproduction_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R30_produced">
	<rdfs:label xml:lang="en">produced</rdfs:label>
	<rdfs:comment>This property associates an instance of F33 Reproduction Event with an instance of E84 Information Carrier it produces.
</rdfs:comment>
	<rdfs:domain rdf:resource="F33_Reproduction_Event"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
</rdf:Property>

<rdf:Property rdf:about="R30i_was_produced_by">
	<rdfs:label xml:lang="en">was produced by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
	<rdfs:range rdf:resource="F33_Reproduction_Event"/>
</rdf:Property>

<rdf:Property rdf:about="R31_is_reproduction_of">
	<rdfs:label xml:lang="en">is reproduction of</rdfs:label>
	<rdfs:comment>This property associates an instance of E84 Information Carrier which is a reproduction of another instance of E84 Information Carrier with the latter. It is considered that a reproduction of multiple originals resulting in a single product requires a merging of those objects prior to the reproduction. Therefore an Information Carrier is regarded to be a reproduction of one and only one original. This property is a shortcut of the more fully developed path from E84 Information Carrier through R30 produced (was produced by), F33 Reproduction Event R29 reproduced (was reproduced by) to E84 Information Carrier.
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
</rdf:Property>

<rdf:Property rdf:about="R31i_has_reproduction">
	<rdfs:label xml:lang="en">has reproduction</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
</rdf:Property>

<rdf:Property rdf:about="R32_is_warranted_by">
	<rdfs:label xml:lang="en">is warranted by</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with an instance of F52 Name Use Activity which provides evidence for the use of the particular nomen in the stated sense. The association between this name use activity and a source for it may be described by the property P70 documents (is documented in).
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="F52_Name_Use_Activity"/>
</rdf:Property>

<rdf:Property rdf:about="R32i_warrants">
	<rdfs:label xml:lang="en">warrants</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F52_Name_Use_Activity"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R33_has_content">
	<rdfs:label xml:lang="en">has content</rdfs:label>
	<rdfs:comment>This property associates an instance of F12 Nomen with one or more equivalent serialized content models for it. In digital form the symbol arrangement constituting an instance of F12 Nomen can only be represented through a particular encoding, for example ASCII or Latin1 for the Latin script. We call such a representation a content model. The property R33.1 has encoding: E55 Type allows for specifying the encoding of a particular associated content model. Together with this specification, a content model allows for unambiguously defining a nomen independently from the encoding used for representing the content.
</rdfs:comment>
	<rdfs:domain rdf:resource="F12_Nomen"/>
	<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>

<rdf:Property rdf:about="R34_has_validity_period">
	<rdfs:label xml:lang="en">has validity period</rdfs:label>
	<rdfs:comment>This property associates an instance of F34 KOS with the instance of E52 Time-Span describing the period for which the particular KOS Expression was regarded as valid by its maintainers. Each change of validity status of a nomen use statement within a KOS should be associated with a release change of the KOS. The individual time-span of a validity state of a nomen would be the union of the time-spans of the KOS in which the Nomen was declared to have the particular validity status (provisional, accepted, obsolete etc...).
</rdfs:comment>
	<rdfs:domain rdf:resource="F34_KOS"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span"/>
</rdf:Property>

<rdf:Property rdf:about="R34i_is_validity_period_of">
	<rdfs:label xml:lang="en">is validity period of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span"/>
	<rdfs:range rdf:resource="F34_KOS"/>
</rdf:Property>

<rdf:Property rdf:about="R35_specified_by">
	<rdfs:label xml:lang="en">specified by</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with an instance of F34 KOS in which the Nomen Use Statement has a given status. The property R35.1 allows for specifying the particular status of the nomen use statement within the KOS. An instance of R35 is specified by should have only one status.
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="F34_KOS"/>
</rdf:Property>

<rdf:Property rdf:about="R35i_specifies">
	<rdfs:label xml:lang="en">specifies</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F34_KOS"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R36_uses_script_conversion">
	<rdfs:label xml:lang="en">uses script conversion</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with the instance of F36 Script Conversion that was used to create the Nomen referred to in the Nomen Use Statement. The source of this conversion may or may not be explicitly mentioned. Is shortcut of: F35 Nomen Use Statement R17 was created by (created) F28 Expression Creation P33 used specific technique (was used by) E29 Design or Procedure.
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="F36_Script_Conversion"/>
</rdf:Property>

<rdf:Property rdf:about="R36i_is_script_conversion_used_in">
	<rdfs:label xml:lang="en">is script conversion used in</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with the instance of F12 Nomen for which it declares usage.
</rdfs:comment>
	<rdfs:domain rdf:resource="F36_Script_Conversion"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R37_states_as_nomen">
	<rdfs:label xml:lang="en">states as nomen</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="F12_Nomen"/>
</rdf:Property>

<rdf:Property rdf:about="R37i_is_stated_as_nomen_in">
	<rdfs:label xml:lang="en">is stated as nomen in</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F12_Nomen"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R38_refers_to_thema">
	<rdfs:label xml:lang="en">refers to thema</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with the instance of E1 CRM Entity for which it declares the usage of a nomen.
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdf:Property>

<rdf:Property rdf:about="R38i_is_thema_of">
	<rdfs:label xml:lang="en">is thema of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R39_is_intended_for">
	<rdfs:label xml:lang="en">is intended for</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with an instance of E74 Group which is the target audience for which the associated nomen use is intended. To indicate that the associated nomen is declared as preferred in all contexts, the instance of E74 Group is ‘mankind’.
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E74_Group"/>
</rdf:Property>

<rdf:Property rdf:about="R39i_is_target_audience_in">
	<rdfs:label xml:lang="en">is target audience in</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E74_Group"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

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

</rdfs:comment>
	<rdfs:domain rdf:resource="F1_Work"/>
	<rdfs:range rdf:resource="F22_Self-Contained_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R40i_is_representative_expression_for">
	<rdfs:label xml:lang="en">is representative expression for</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F22_Self-Contained_Expression"/>
	<rdfs:range rdf:resource="F1_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R41_has_rep_manifestation_product_type">
	<rdfs:label xml:lang="en">has rep manifestation product type</rdfs:label>
	<rdfs:comment>This property identifies an instance of F3 Manifestation Product Type that has been chosen as the most characteristic Manifestation Product Type of the instance of F2 Expression of which it is a manifestation.
Identifying an instance of F3 Manifestation Product Type that is representative for an instance of F2 Expression makes it possible in turn to identify an instance of F2 Expression that is representative for an instance of F1 Work, and to decide what should be regarded as the title of the work.
The title of an Expression may not be one taken from a representative Manifestation Product Type or Manifestation Singleton.
A given expression can have more than one Representative Manifestation Product Type.
R41 has representative manifestation product type is a shortcut of the more developed path F2 Expression R48i was assigned by F41 Representative Manifestation Assignment R49 assigned F3 Manifestation Product Type.

</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R41i_is_rep_manifestation_product_type_for">
	<rdfs:label xml:lang="en">is rep manifestation product type for</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

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

</rdfs:comment>
	<rdfs:domain rdf:resource="F4_Manifestation_Singleton"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R42i_has_representative_manifestation_singleton">
	<rdfs:label xml:lang="en">has representative manifestation singleton</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F4_Manifestation_Singleton"/>
</rdf:Property>

<rdf:Property rdf:about="R43_carried_out_by">
	<rdfs:label xml:lang="en">carried out by</rdfs:label>
	<rdfs:comment>This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which Manifestation (i.e., which instance of F3 Manifestation Product Type or F4 Manifestation Singleton) is representative for a given expression.
In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.
</rdfs:comment>
	<rdfs:domain rdf:resource="F41_Representative_Manifestation_Assignment"/>
	<rdfs:range rdf:resource="F44_Bibliographic_Agency"/>
</rdf:Property>

<rdf:Property rdf:about="R43i_performed">
	<rdfs:label xml:lang="en">performed</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F44_Bibliographic_Agency"/>
	<rdfs:range rdf:resource="F41_Representative_Manifestation_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R44_carried_out_by">
	<rdfs:label xml:lang="en">carried out by</rdfs:label>
	<rdfs:comment>This property associates a bibliographic agency (represented by one or more of its cataloguers) and the assigning of which expression is representative for a given Work.
In cataloguing practice, such a relationship is usually just implicit. However, it can become explicit, for example when a bibliographic agency creates an authority record for a given work and fills the “Source” field with information about the publication that contains the expression that was used by the bibliographic agency to establish the controlled access point for the work realised in that expression.

</rdfs:comment>
	<rdfs:domain rdf:resource="F42_Representative_Expression_Assignment"/>
	<rdfs:range rdf:resource="F44_Bibliographic_Agency"/>
</rdf:Property>

<rdf:Property rdf:about="R44i_performed">
	<rdfs:label xml:lang="en">performed</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F44_Bibliographic_Agency"/>
	<rdfs:range rdf:resource="F42_Representative_Expression_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R45_assigned_to">
	<rdfs:label xml:lang="en">assigned to</rdfs:label>
	<rdfs:comment>This property identifies the entity to which an actor, such as a bibliographic agency, assigned an instance of F13 Identifier.
</rdfs:comment>
	<rdfs:domain rdf:resource="F40_Identifier_Assignment"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdf:Property>

<rdf:Property rdf:about="R45i_was_assigned_by">
	<rdfs:label xml:lang="en">was assigned by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
	<rdfs:range rdf:resource="F40_Identifier_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R46_assigned_to">
	<rdfs:label xml:lang="en">assigned to</rdfs:label>
	<rdfs:comment>This property associates the instance of F13 Identifier assigned to an instance of E1 CRM Entity and the event of assigning it.
</rdfs:comment>
	<rdfs:domain rdf:resource="F40_Identifier_Assignment"/>
	<rdfs:range rdf:resource="F13_Identifier"/>
</rdf:Property>

<rdf:Property rdf:about="R46i_was_assigned_by">
	<rdfs:label xml:lang="en">was assigned by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F13_Identifier"/>
	<rdfs:range rdf:resource="F40_Identifier_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R48_assigned_to">
	<rdfs:label xml:lang="en">assigned to</rdfs:label>
	<rdfs:comment>This property associates the event of assigning a representative instance of F3 Manifestation Product Type or F4 Manifestation Singleton with the expression to which it was assigned.
</rdfs:comment>
	<rdfs:domain rdf:resource="F41_Representative_Manifestation_Assignment"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R48i_was_assigned_by">
	<rdfs:label xml:lang="en">was assigned by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F41_Representative_Manifestation_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R49_assigned">
	<rdfs:label xml:lang="en">assigned</rdfs:label>
	<rdfs:comment>This property associates the event of assigning a representative instance of F3 Manifestation Product Type with the F3 Manifestation Product Type which has been assigned.
</rdfs:comment>
	<rdfs:domain rdf:resource="F41_Representative_Manifestation_Assignment"/>
	<rdfs:range rdf:resource="F3_Manifestation_Product_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R49i_was_assigned_by">
	<rdfs:label xml:lang="en">was assigned by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F3_Manifestation_Product_Type"/>
	<rdfs:range rdf:resource="F41_Representative_Manifestation_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R50_assigned_to">
	<rdfs:label xml:lang="en">assigned to</rdfs:label>
	<rdfs:comment>This property associates the event of assigning a representative instance of F2 Expression with the instance of F15 Complex Work to which it was assigned.
</rdfs:comment>
	<rdfs:domain rdf:resource="F42_Representative_Expression_Assignment"/>
	<rdfs:range rdf:resource="F15_Complex_Work"/>
</rdf:Property>

<rdf:Property rdf:about="R50i_was_assigned_by">
	<rdfs:label xml:lang="en">was assigned by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F15_Complex_Work"/>
	<rdfs:range rdf:resource="F42_Representative_Expression_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R51_assigned">
	<rdfs:label xml:lang="en">assigned</rdfs:label>
	<rdfs:comment>This property associates the event of assigning a representative instance of F2 Expression with the F2 Expression which has been assigned.
</rdfs:comment>
	<rdfs:domain rdf:resource="F42_Representative_Expression_Assignment"/>
	<rdfs:range rdf:resource="F2_Expression"/>
</rdf:Property>

<rdf:Property rdf:about="R51i_was_assigned_by">
	<rdfs:label xml:lang="en">was assigned by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F2_Expression"/>
	<rdfs:range rdf:resource="F42_Representative_Expression_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R52_used_rule">
	<rdfs:label xml:lang="en">used rule</rdfs:label>
	<rdfs:comment>This property associates the event of assigning an instance of F13 Identifier with the instructions followed by an actor, such as a Bibliographic Agency, in creating that identifier.
</rdfs:comment>
	<rdfs:domain rdf:resource="F40_Identifier_Assignment"/>
	<rdfs:range rdf:resource="F43_Identifier_Rule"/>
</rdf:Property>

<rdf:Property rdf:about="R52i_was_the_rule_used_in">
	<rdfs:label xml:lang="en">was the rule used in</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F43_Identifier_Rule"/>
	<rdfs:range rdf:resource="F40_Identifier_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R53_assigned">
	<rdfs:label xml:lang="en">assigned</rdfs:label>
	<rdfs:comment>This property associates the event of assigning a representative instance of F4 Manifestation Singleton with the F4 Manifestation Singleton which has been assigned.
</rdfs:comment>
	<rdfs:domain rdf:resource="F41_Representative_Manifestation_Assignment"/>
	<rdfs:range rdf:resource="F4_Manifestation_Singleton"/>
</rdf:Property>

<rdf:Property rdf:about="R53i_was_assigned_by">
	<rdfs:label xml:lang="en">was assigned by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F4_Manifestation_Singleton"/>
	<rdfs:range rdf:resource="F41_Representative_Manifestation_Assignment"/>
</rdf:Property>

<rdf:Property rdf:about="R54_has_nomen_language">
	<rdfs:label xml:lang="en">has nomen language</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with an instance of E56 Language which is a target language for the associated nomen use.
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E56_Language"/>
</rdf:Property>

<rdf:Property rdf:about="R54i_is_language_of_nomen_in">
	<rdfs:label xml:lang="en">is language of nomen in</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E56_Language"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R55_has_nomen_form">
	<rdfs:label xml:lang="en">has nomen form</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with the instance of E55 Type that characterizes the Nomen referred to in the Nomen Use Statement, such as abbreviation, full name etc. In the case of abbreviations, the source of this form may or may not be explicitly mentioned.
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R55i_is_nomen_form_in">
	<rdfs:label xml:lang="en">is nomen form in</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R56_has_related_use">
	<rdfs:label xml:lang="en">has related use</rdfs:label>
	<rdfs:comment>This property associates an instance of F35 Nomen Use Statement with another instance of F35 Nomen Use Statement which has a related use in some context, such as alternative, lexical variant, replacing former use etc. The property R56.1 allows for specifying the particular kind of the nomen use statement relationship.
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R56i_is_related_use_for">
	<rdfs:label xml:lang="en">is related use for</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F35_Nomen_Use_Statement"/>
	<rdfs:range rdf:resource="F35_Nomen_Use_Statement"/>
</rdf:Property>

<rdf:Property rdf:about="R57_is_based_on">
	<rdfs:label xml:lang="en">is based on</rdfs:label>
	<rdfs:comment>This property associates an instance of F38 Character with an instance of E39 Actor that the character is motivated by or is intended to represent. An instance of F38 Character may be based on a combination of features taken from several actors. This property is a shortcut of the more fully developed path from E28 Conceptual Object, restricted to F38 Character, through the inverse of P94 has created (was created by), E65 Creation P17 was motivated by (motivated) to E1 CRM Entity restricted to E39 Actor.
</rdfs:comment>
	<rdfs:domain rdf:resource="F38_Character"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E39_Actor"/>
</rdf:Property>

<rdf:Property rdf:about="R57i_is_basis_for">
	<rdfs:label xml:lang="en">is basis for</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E39_Actor"/>
	<rdfs:range rdf:resource="F38_Character"/>
</rdf:Property>

<rdf:Property rdf:about="R58_has_fictional_member">
	<rdfs:label xml:lang="en">has fictional member</rdfs:label>
	<rdfs:comment>This property associates an instance of F38 Character representing a group with another instance of F38 Character that is presented in relevant fiction as a member of the fictional group.
</rdfs:comment>
	<rdfs:domain rdf:resource="F38_Character"/>
	<rdfs:range rdf:resource="F38_Character"/>
</rdf:Property>

<rdf:Property rdf:about="R58i_is_fictional_member_of">
	<rdfs:label xml:lang="en">is fictional member of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="F38_Character"/>
	<rdfs:range rdf:resource="F38_Character"/>
</rdf:Property>

<rdf:Property rdf:about="R59_had_typical_subject">
	<rdfs:label xml:lang="en">had typical subject</rdfs:label>
	<rdfs:comment>This property associates an instance of F51 Pursuit with the instance of E1 CRM Entity that is the typical subject of the associated activity, such as an area of expertise in which the actor is engaged or was engaged.
</rdfs:comment>
	<rdfs:domain rdf:resource="F51_Pursuit"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdf:Property>

<rdf:Property rdf:about="R59i_was_typical_subject_of">
	<rdfs:label xml:lang="en">was typical subject of</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
	<rdfs:range rdf:resource="F51_Pursuit"/>
</rdf:Property>

<rdf:Property rdf:about="R60_used_to_use_language">
	<rdfs:label xml:lang="en">used to use language</rdfs:label>
	<rdfs:comment>This property associates an instance of F51 Pursuit with the instance of E56 Language that was characteristically used for the products of the associated activity.
The property R60.1 has type of use allows for specifying a particular form of use.
</rdfs:comment>
	<rdfs:domain rdf:resource="F51_Pursuit"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E56_Language"/>
</rdf:Property>

<rdf:Property rdf:about="R60i_was_language_used_by">
	<rdfs:label xml:lang="en">was language used by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E56_Language"/>
	<rdfs:range rdf:resource="F51_Pursuit"/>
</rdf:Property>

<rdf:Property rdf:about="R61_occured_in_kind_of_context">
	<rdfs:label xml:lang="en">occured in kind of context</rdfs:label>
	<rdfs:comment>This property associates an instance of F52 Name Use Activity with the instance of E55 Type that characterises the kind of role or context within which the associated name was used.
</rdfs:comment>
	<rdfs:domain rdf:resource="F52_Name_Use_Activity"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
</rdf:Property>

<rdf:Property rdf:about="R61i_was_kind_of_context_for">
	<rdfs:label xml:lang="en">was kind of context for</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
	<rdfs:range rdf:resource="F52_Name_Use_Activity"/>
</rdf:Property>

<rdf:Property rdf:about="R62_was_used_for_membership_in">
	<rdfs:label xml:lang="en">was used for membership in</rdfs:label>
	<rdfs:comment>This property associates an instance of F52 Name Use Activity with the instance of E74 Group that characterises the context within which the associated name was used for membership in that group.
</rdfs:comment>
	<rdfs:domain rdf:resource="F52_Name_Use_Activity"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E74_Group"/>
</rdf:Property>

<rdf:Property rdf:about="R62i_was_context_for">
	<rdfs:label xml:lang="en">was context for</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E74_Group"/>
	<rdfs:range rdf:resource="F52_Name_Use_Activity"/>
</rdf:Property>

<rdf:Property rdf:about="R63_named">
	<rdfs:label xml:lang="en">named</rdfs:label>
	<rdfs:comment>This property associates an instance of F52 Name Use Activity with the instance of E1 CRM Entity that the associated name was used for.
</rdfs:comment>
	<rdfs:domain rdf:resource="F52_Name_Use_Activity"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdf:Property>

<rdf:Property rdf:about="R63i_was_named_by">
	<rdfs:label xml:lang="en">was named by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
	<rdfs:range rdf:resource="F52_Name_Use_Activity"/>
</rdf:Property>

<rdf:Property rdf:about="R64_used_name">
	<rdfs:label xml:lang="en">used name</rdfs:label>
	<rdfs:comment>This property associates an instance of F52 Name Use Activity with the instance of E41 Appellation that was used for the associated entity.
</rdfs:comment>
	<rdfs:domain rdf:resource="F52_Name_Use_Activity"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E41_Appellation"/>
</rdf:Property>

<rdf:Property rdf:about="R64i_was_name_used_by">
	<rdfs:label xml:lang="en">was name used by</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E41_Appellation"/>
	<rdfs:range rdf:resource="F52_Name_Use_Activity"/>
</rdf:Property>

<rdf:Property rdf:about="R65_recorded_aspects_of">
	<rdfs:label xml:lang="en">recorded aspects of</rdfs:label>
	<rdfs:comment>This property associates an instance of F29 Recording Event with an instance of E18 Physical Thing some of whose features, at the time of recording, were recorded in that process.
</rdfs:comment>
	<rdfs:domain rdf:resource="F29_Recording_Event"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>

<rdf:Property rdf:about="R65i_had_aspects_recorded_through">
	<rdfs:label xml:lang="en">had aspects recorded through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
	<rdfs:range rdf:resource="F29_Recording_Event"/>
</rdf:Property>

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

</rdfs:comment>
	<rdfs:domain rdf:resource="F31_Performance"/>
	<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
</rdf:Property>

<rdf:Property rdf:about="R66i_had_a_performed_version_through">
	<rdfs:label xml:lang="en">had a performed version through</rdfs:label>
	<rdfs:comment>
</rdfs:comment>
	<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
	<rdfs:range rdf:resource="F31_Performance"/>
</rdf:Property>
</rdf:RDF>