INTRODUCTION
[PR: a new introduction to be written]
DESCRIPTION OF THE MODEL
Naming Conventions
[PR: revised, new text added re non-reuse of identifiers]
All declared classes were assigned a name and an identifier based on the CIDOC CRM model, with class identifiers starting with the letter "F" followed by a number Similarly, resulting properties received names and identifiers, beginning with "R" and followed by a number, with an "i" added when the property is referenced in its inverted form The letters "F" and "R" were selected during the development of FRBROO and represent the initial letters of "FRBR," with no additional significance In CIDOC CRM naming conventions, these correspond to "E" for "entity" (now referred to as "classes") and "P" for "property."
LRMOO retains the same identifiers for classes and properties that were previously assigned in FRBROO, ensuring continuity in definitions However, identifiers for deprecated classes and properties from FRBROO are not reused, leading to gaps in the numbering system New classes and properties introduced in LRMOO are assigned the next available identifier in the sequence.
As in CIDOC CRM, properties with the character of states are named in the present tense, such as
“embodies” “has validity period”, whereas properties related to events are named in the past tense, such as
Classes and properties directly derived from the CIDOC CRM are labeled according to their original designations, with class identifiers starting with "E" and property identifiers starting with "P."
When selecting the domain of properties and the sequence of their names, the following priority hierarchy should be followed: first, Temporal Entity and its subclasses; second, Thing and its subclasses; third, Actor and its subclasses; and finally, Other.
Property Quantifiers
Quantifiers for properties are intended solely for semantic clarification and should not be considered as recommendations for implementation Consequently, the term "cardinality constraints" is deliberately omitted, as it is generally associated with specific implementations.
This document presents a comprehensive table of property quantifiers, detailing their notation and providing clear explanations It employs two widely recognized notations for clarity: a verbal notation, which includes phrases like "one to many," and a numeric notation, represented by expressions such as "(0,n:0,1)." While terms like "one," "many," and "necessary" are straightforward, the term "dependent" refers to a scenario where a range instance cannot exist without a corresponding property instance, indicating that the property is essential for its range.
The property is classified as unconstrained, meaning that both the individual domain and range instances can have zero, one, or multiple occurrences of this property This indicates that the property is optional and can be repeated for its domain and range, allowing for a one-to-many relationship.
An individual domain instance of this property can have multiple occurrences, while an individual range instance can only be associated with one instance of this property This means the property is optional for both its domain and range, but can be repeated within the domain This scenario is often referred to as a "fan-out" in certain contexts, illustrating a many-to-one relationship.
In a domain instance, this property can have zero or one occurrence, while a range instance may be linked to zero, one, or multiple occurrences of the same property This indicates that the property is optional for both the domain and range, but can be repeated for the range This scenario is often referred to as a "fan-in," highlighting the many-to-many relationship that can occur within this context.
An individual domain instance of this property can possess multiple instances, making it necessary and repeatable, while an individual range instance may have zero, one, or more instances, indicating that it is optional yet repeatable This creates a one-to-many relationship where the property is essential for the domain but not for the range.
An individual domain instance of this property can have multiple instances, while an individual range instance can only be referenced by one instance of this property This means that the property is necessary and repeatable for its domain, but optional and not repeatable for its range This scenario is often referred to as a "fan-out," illustrating a many-to-one relationship where the domain is essential.
Each individual instance of this property must have a single corresponding instance within its domain, while an individual instance in the range can be associated with none, one, or multiple instances of this property This establishes that the property is mandatory and non-repeatable for the domain, yet optional and repeatable for the range, a scenario often referred to as “fan-in.” This relationship exemplifies a one-to-many dependency.
An individual domain instance of this property can have multiple instances, while each range instance must be linked to exactly one instance of this property This means that the property is optional and repeatable for its domain, but necessary and singular for its range This relationship is often referred to as a "fan-out," highlighting the one-to-many dependency between the domain and range.
In this property structure, an individual domain instance can possess multiple instances, while each range instance must be linked to a single instance of this property This creates a necessary and repeatable relationship for the domain, while the range relationship is necessary but not repeatable This scenario is often referred to as a "fan-out," illustrating a many-to-one dependency.
Each individual domain instance of this property requires a single instance, while a range instance can be associated with multiple domain instances This means the property is essential and non-repeatable for the domain but necessary and repeatable for the range, a scenario often referred to as “fan-in.” This relationship exemplifies a many-to-many connection, highlighting the necessity of the property in both contexts.
This property is essential and dependent, allowing for multiple instances within both an individual domain and an individual range.
(1,n:1,n) repeatable for both its domain and its range. one to one
Each instance of this property must have a unique corresponding instance for both its domain and range, meaning that it is essential and cannot be duplicated This establishes a many-to-one relationship between the domain and range instances.
An individual domain instance of this property requires a minimum of two instances, while an individual range instance can be associated with none, one, or multiple instances of this property.
Certain properties are categorized as essential for their domain or as reliant on their range, as outlined in the previous table If a property is not explicitly stated for a specific instance within the domain or range, it indicates that the property is present, but the corresponding value on one side remains unknown.
In the case of optional properties, the methodology proposed by LRMOO does not distinguish between a value being unknown or the property not being applicable at all.
Presentation Conventions
All occurrences of the 'E41 Appellation' are enclosed in single quotation marks, regardless of whether they refer to the appellation itself or the items it designates Additionally, any punctuation that follows an instance of 'E41 Appellation' is placed outside the single quotation marks, as it is not part of the appellation.
In this article, we refer to instances of the E90 Symbolic Object as a content model, denoted within single quotation marks, for example, ‘abc’ The term 'content model' specifically describes the sequence of symbols that make up the symbolic object.
British spelling is used throughout the original English version of this document, except for occasional quotations and examples.
Double quotation marks are used to indicate an informal name or term E.g.: The “lower member” consists of sandstone with minor shale.
Class & Property Hierarchies
[PR: text to be reviewed based on format adopted for the hierarchies]
Compact monohierarchical presentations of class and property isA hierarchies greatly enhance the understanding and navigation of LRMOO, despite not offering exhaustive definitions.
The class hierarchy presented below has the following format:
Each line features a distinct class identifier, starting with the letter "F" followed by a number This identifier is succeeded by a series of em dashes ("—"), which denote the class's hierarchical position within the isA hierarchy.
– The English name of the class appears to the right of the em dashes.
– The index is ordered by hierarchical level, in a “depth first” manner, from the smaller to the larger subhierarchies.
– Classes that appear in more than one position in the class hierarchy as a result of multiple inheritance are shown first in roman typeface, then in italic typeface.
The property hierarchy presented below has the following format:
Each property is designated by a unique identifier, starting with the letter "R" followed by a number This identifier is succeeded by a series of em dashes, which denote the property's position within the isA hierarchy.
– The English name of the property appears to the right of the em dashes, followed by its inverse name in parentheses for reading in the range to domain direction.
– The domain class for which the property is declared.
– The range class that the property references.
– The index is ordered by hierarchical level, in a “depth first” manner, from the smaller to the larger subhierarchies, and by property number between equal siblings.
– Properties that appear in more than one position in the property hierarchy as a result of multiple inheritance are shown in an italic typeface.
LRMOO and CIDOC CRM utilize separate layouts for their class and property hierarchies, ensuring clarity in their distinct structures This differentiation highlights the unique characteristics of LRMOO classes and properties compared to those in CIDOC CRM.
[PR: updated up to 2021-06-29; includes SIG#50 proposals and results Classes to transfer to CRMsoc are highlighted in blue.]
2.5.2 LRM OO Class Hierarchy Aligned with (Part of) CIDOC CRM Class
LRMoo class hierarchy with CIDOC CRM 7.1.1 direct superclasses added as the first column.
Retained order by F class numbers.
[PR: updated up to 2021-06-29; includes SIG#50 proposals and results Classes to transfer to CRMsoc are highlighted in blue.]
E29 Design or Procedure F36 Script Conversion
[PR: updated up to 2021-06-29; includes SIG#50 proposals and results, unapproved changes/deprecations in magenta Properties to transfer to CRMsoc are highlighted in blue.]
Range entities from CIDOC CRMbase are in bold.
Property id Property Name Entity – Domain Entity – Range
R1 is logical successor of (has successor) F1 Work F1 Work
R2 is derivative of (has derivative) F1 Work F1 Work
— R68 is inspiration for (was inspired by) F1 Work F1 Work
R3 is realised in (realises) F1 Work F2 Expression
R4 embodies (is embodied in) F3 Manifestation F2 Expression
R5 has component (is component of) F2 Expression F2 Expression
R7 is materialization of (is materialized in) F5 Item F3 Manifestation
R8 combines (is combined to form) F12 Nomen
(depr) has member (is member of) F1 Work F1 Work
(move) has part (is part of) F1 Work F1 Work
(depr) has elaboration (is elaboration of) F1 Work F1 Work
R11 has issuing rule (is issuing rule of) F18 Serial Work E29 Design or
R15 has fragment (is fragment of) F2 Expression E90 Symbolic
R16 initiated (was initiated by) F27 Work Conception F1 Work
(move) was remembered in (contains memory of) F56 Externalization
— R17 created (was created by) F28 Expression
— — R24 created (was created through) F30 Manifestation
R18 created (was created by) F28 Expression
R19 created a realisation of (was realised through)
R20 recorded (was recorded through) F29 Recording Event E2 Temporal
F31 Performance R26 produced things of type (was produced by) F32 Carrier Production
R27 materialized (was materialized by) F32 Carrier Production
R28 produced (was produced by) F32 Carrier Production
R29 reproduced object (was object reproduced by) F33 Reproduction
Property id Property Name Entity – Domain Entity – Range
R30 reproduced publication (was publication reproduced by) F33 Reproduction
R34 has validity period (is validity period of) F34 Controlled
R35 is specified by (specifies) F12 Nomen F2 Expression
R36 uses script conversion (is script conversion used in) F12 Nomen F36 Script
Conversion socR45 assigned to (was assigned by) socF52 Name Use
R54 has nomen language (is language of nomen in) F12 Nomen E56 Language
R56 is associated with F12 Nomen, while R57 serves as the foundation for F38 Character R58 denotes a fictional member of F38 Character, and R59 represents a typical subject of F51 Pursuit, which is an E1 CRM Entity R60 indicates the language utilized by F51 Pursuit, identified as E56 Language, and R61 describes the context in which F52 Name Use occurred.
Activity E55 Type socR62 was used for membership in (was context for) socF52 Name Use
Activity E74 Group socR63 named (was named by) socF52 Name Use
Activity E1 CRM Entity socR64 used name (was name used by) socF52 Name Use
(depr) recorded aspects of (had aspects recorded through) F29 Recording Event E18 Physical Thing
R66 included performed version of (had a performed version through) F31 Performance E89 Propositional
R67 has part (is part of) F1 Work F1 Work
R69 has physical form (is physical form of) F3 Manifestation E55 Type
R70 has dimension (is dimension of) F3 Manifestation E54 Dimension
R71 has part (is part of) F3 Manifestation F3 Manifestation
(depr) specifies number of parts (is the specified number of parts for) F3 Manifestation E60 Number
Property id Property Name Entity – Domain Entity – Range
(bears representative attribute for) F1 Work F2 Expression
R74 uses expression of (has expression used in) F1 Work F1 Work
R75 incorporates (is incorporated in) F2 Expression F2 Expression
Rnn3 was remembered in (contains memory of) F56 Externalization
— R17 created (was created by) F28 Expression
— — R24 created (was created through) F30 Manifestation
2.5.4 LRM OO Property Hierarchy Aligned with (Part of) CIDOC CRM Property Hierarchy
LRMOO Class Declaration
[PR: this explanation to be reviewed for accuracy]
The classes of LRMOO are comprehensively declared in this section using the following format:
• Class names are presented as headings in bold face, preceded by the class’s unique identifier;
• The line “Subclass of:” declares the superclass of the class, being the class from which this class inherits properties;
• The line “Superclass of:” is a cross-reference to the subclasses of this class;
• The line “Scope note:” contains the textual definition of the concept the class represents;
The "Examples:" section includes a list of instances belonging to a specific class, with subclass identifiers noted in parentheses when applicable If an example represents multiple classes, both unique identifiers are provided in parentheses Additionally, non-fictitious examples may be accompanied by explanatory notes in brackets.
• The line “Properties:” declares the list of the class’s properties;
• Each property is represented by its unique identifier, its forward and reverse names, and the range class that it links to, separated by a colon;
• Inherited properties are not represented;
• Properties of properties are provided indented and in parentheses beneath their respective domain property.
Scope note: This class comprises distinct intellectual ideas conveyed in artistic and intellectual creations, such a poems, stories or musical compositions
A work is the result of an intellectual process involving one or more individuals and is characterized by recognizable expressions Typically, works are considered complete when the creator declares them finished or when their content exhibits logical coherence However, some works may be acknowledged as existing yet unfinished, particularly if the creators have intentionally or unintentionally left behind incomplete expressions.
In the absence of explicit information about the initial conception, which is rarely available, the first expression created constitutes witness of the beginning of existence of a Work.
A Work can develop over time through revised editions and can be enhanced by multiple Actors simultaneously or sequentially This ongoing process allows for the continuous creation of additional expressions of the Work.
The boundaries of a Work have nothing to do with the value of the intellectual achievement but only with the dominance of a concept
The primary goal of this class is to unite intellectually comparable expressions, allowing users to view all available alternatives that convey the same intellectual or artistic content.
abstract content of Giovanni Battista Piranesi’s ‘Carcere XVI: the pier with chains: 1st state’
‘La Porte de l’Enfer’ by Auguste Rodin conceived between 1880 and 1917
The anthology "American Women Poets of the Nineteenth Century," edited by Cheryl Walker and published by Rutgers University Press in July 1992, presents a curated collection that highlights the significant contributions of female poets during this era This compilation not only showcases the diverse voices and styles of women writers but also emphasizes their pivotal role in shaping American literature Through careful aggregation and arrangement, the anthology offers readers a comprehensive understanding of the themes and challenges faced by these poets, ultimately celebrating their artistic achievements and cultural impact.
‘Codes for the representation of names of languages’ (ISO 639)
the Dewey Decimal Classification (DDC)
Properties: R1 is logical successor of (has successor): F1 Work
R2 is derivative of (has derivative): F1 Work (R2.1 has type: E55 Type) R3 is realised in (realises): F2 Expression
R10 is a member of F1 Work, while R67 is part of the same work Additionally, R68 serves as inspiration for F1 Work R73 bears a representative attribute for F2 Expression, and R74 incorporates expressions used in F1 Work.
Rnn has elaboration (is elaboration of): F1 Work
This class encompasses the intellectual and artistic expressions of works manifested as identifiable immaterial objects, including texts, poems, jokes, musical or choreographic notations, movement patterns, sound patterns, images, multimedia objects, or combinations thereof These creations possess objectively recognizable structures, with the essence of F2 Expression being represented through signs.
An Expression is the outcome of the intellectual or creative process of realizing a Work.Subsequent expressions conveying the same work may be created over time.
Expressions do not depend on a specific physical carrier and can exist on one or more carriers simultaneously, including human memory, but expressions cannot persist without a carrier
The F2 Expression's form is a fundamental attribute, where variations in form signify distinct Expressions, such as transitioning from text to spoken word or creating a transcript Additionally, changes in language or performance methods, like translations or instrumental arrangements, also result in different Expressions Consequently, any revision or modification of a text is regarded as a new F2 Expression Although theoretically any alteration in signs produces a new Expression, the context and usage typically dictate the conventions for differentiating among them.
Examples: the Italian text of Dante’s ‘Divina Commedia’ as found in the authoritative critical edition ‘La
The article discusses the edition of Dante Alighieri's works titled "Commedia secondo l’antica vulgata," edited by Giorgio Petrocchi and published by Mondadori in 1966-67 This edition, part of the National Edition curated by the Società Dantesca Italiana, includes the Italian text of Dante's "Inferno." Additionally, it references Christian Morgenstern's poem "Fisches Nachtgesang," which is uniquely composed of specific signs arranged in a particular order The article also outlines the instructions for producing a Yiddish translation of this textual work.
In 1935, Sergei Radlov directed 'King Lear' in Moscow, showcasing a significant theatrical interpretation Pina Bausch's choreography for the ballet 'Rite of Spring' in Wuppertal in 1975 further exemplified innovative dance techniques Additionally, Bruno Walter's instructions for Gustav Mahler’s 9th Symphony were imparted to the Columbia Symphony Orchestra during rehearsals in Hollywood in 1961, as documented in the CD 'Bruno Walter conducts and talks about Mahler symphony No 9: rehearsal & performance.' Furthermore, the "performance handbook" for Luigi Nono’s musical work 'À Pierre' provides essential guidelines for its execution.
Properties: R5 has component (is component of): F2 Expression
R15 has fragment (is fragment of): E90 Symbolic Object R75 incorporates (is incorporated in): F2 Expression
This class includes products that deliver one or more Expressions, where a Manifestation is characterized by its content and presentation form The essence of F3 Manifestation encompasses not just the signs themselves, but also how they are presented for user consumption, including the types of media used.
An F3 Manifestation results from a publication process involving one or more F2 Expressions intended for public sharing Additionally, it can also refer to a distinct form created directly on a medium without the intention of formal publication.
An F3 Manifestation consists of one or more F2 Expressions that convey unique logical content, along with any additional contributions from a publisher, such as text layout and cover design, especially when the roles of author and publisher are distinct Furthermore, an F3 Manifestation can be differentiated by its physical characteristics based on the distribution medium; for instance, hardcover and paperback editions represent two separate instances of F3 Manifestation, despite having the same authorial and editorial content.
In the realm of industrial products, including printed books, music CDs, and digital materials, an instance of F3 Manifestation serves as the prototype for all copies This instance outlines the essential features that F5 Items must exhibit to be recognized as copies of a specific publication Furthermore, instances of F3 Manifestation are classified as E99 Product Types, typically identified by unique identifiers like ISBN numbers.
The publication titled 'Harmonie universelle,' authored by Marin Mersenne, was first issued in 1636 in Paris by publisher Sébastien Cramoisy A modern reprint of this work was released in 1986 by Les éditions du CNRS, identified by ISBN 2-222-00835-2 Additionally, the third edition of a combination of texts and graphics related to this work has also been published.
‘Codex Manesse: die Miniaturen der groòen Heidelberger Liederhandschrift, herausgegeben und erlọutert von Ingo F Walther unter Mitarbeit von Gisela Siebert’, issued by the publisher named
LRMOO Property Declaration
[PR: this explanation to be reviewed for accuracy]
The properties of LRMOO are comprehensively declared in this section using the following format:
• Property names are presented as headings in bold face, preceded by unique property identifiers;
• The line “Domain:” declares the class for which the property is defined;
• The line “Range:” declares the class to which the property points, or that provides the values for the property;
• The line “Equal to:” declares the CIDOC CRM property that covers the same concept as the LRMOO property; [there should not be any more of these]
The phrase "Shortcut of:" indicates the connection between CIDOC CRM and/or LRMOO properties when the LRMOO property serves as a shortcut that cannot be classified as a subproperty of an existing property It is important to note that if an LRMOO property functions both as a subproperty and a shortcut, the specific path it shortcuts will only be referenced in the scope note.
• The line “Is covered by shortcut:” declares the CIDOC CRM property that constitutes a shortcut for a more detailed path of which the LRMOO property is a part;
• The line “Superproperty of:” is a cross-reference to any subproperties the property may have;
The "Subproperty of:" line indicates any superproperties associated with a property in CIDOC CRM or LRMOO All LRMOO properties that relate to CIDOC CRM are subproperties of at least one CIDOC CRM property, either directly or indirectly However, this line will be empty for LRMOO properties that serve as shortcuts to more complex paths involving CIDOC CRM properties and their LRMOO subproperties.
• The line “Quantification:” declares the possible number of occurrences for domain and range class instances for the property Possible values are enumerated in section 2.3;
• The line “Scope note:” contains the textual definition of the concept the property represents;
The section titled "Examples:" presents a list of instances demonstrating this property, with any examples that also qualify as instances of a subproperty indicated by the unique identifier of the subproperty in parentheses.
If the example instantiates two properties, the unique identifiers of both properties are added in parenthesis;
• The line “Properties:” introduces any properties the property may have.
In certain instances, a property's superproperty may be categorized as "Out of Scope," signifying that the intended superproperty falls beyond the reach of CIDOC CRM Notably, R34 represents the most recent example of such a classification.
R1 is logical successor of (has successor)
Subproperty of: E70 Thing P130 shows features of (features are also found on): E70 Thing
Scope note: This property associates an instance of F1 Work which logically continues the content of another instance of F1 Work with the latter This property is transitive.
Examples: Albrecht Dürer’s woodcut from ‘The Large Woodcut Passion’ entitled ‘The Agony in the
Garden’ (F1), conceived ca 1496-98, is logical successor of Albrecht Dürer’s woodcut from
‘The Large Woodcut Passion’ entitled ‘The Last Supper’ (F1), dated 1510.
The original Star Wars trilogy, released between 1977 and 1983, serves as a logical predecessor to the prequel trilogy that followed from 1999 to 2005, highlighting a narrative continuity that transcends chronological order.
R2 is derivative of (has derivative)
Superproperty of: R68 is inspiration for (was inspired by): F1 Work
Subproperty of: E70 Thing P130 shows features of (features are also found on): E70 Thing
Scope note: This property associates an instance of F1 Work which modifies the content of another instance of F1 Work with the latter This property is transitive
The property R2.1 has type of this property allows for specifying the kind of derivation, such as adaptation, summarisation, etc.
Examples: William Schuman’s orchestration of Charles Ives’s ‘Variations on America’ (F1) is derivative of Charles Ives’s ‘Variations on America’ (F1), with has type orchestration (E55).
Charles Ives’s musical work entitled ‘Variations on America’ (F1) is derivative of the musical work titled ‘America’ (F1), with has type variations (E55).
The musical work entitled ‘America’ (F1) is derivative of the musical work entitled ‘God save the King’ (F1), with has type same tune with different lyrics (E55).
Subproperty of: E70 Thing P130 shows features of (features are also found on): E70 Thing
Scope note: This property associates an instance of F2 Expression with an instance of F1 Work.
This property highlights the connection between an expression and the work it represents, acknowledging that our understanding of how a work is historically transformed into expressions is often restricted It allows for the representation of the relationship between a specific instance of F2 Expression and the corresponding instance of F1 Work it conveys, without the need to pinpoint the exact instances of F2 Expression involved in the derivation process from the original source.
Dante's 'Inferno' is presented in the authoritative critical edition 'La Commedia secondo l’antica vulgata,' edited by Giorgio Petrocchi and published by Mondadori in 1966-67 This edition is part of the National Edition of Dante Alighieri's works, curated by the Società Dantesca Italiana.
Mozart's opera 'Il dissoluto punito ossia il Don Giovanni' is based on the notated music from the Prague version, preserved in manuscript Ms 1548 at the National Library of France.
In 1935, Sergei Radlov's mise-en-scène for a Yiddish translation of Shakespeare's 'King Lear' in Moscow is encapsulated in a detailed set of production instructions, guiding the adaptation of this classic text.
Sergei Radlov in Moscow in 1935 (F2).
Pina Bausch's choreography of the ballet 'Rite of Spring,' produced in Wuppertal in 1975, serves as a foundational framework for the ballet's production instructions This innovative interpretation highlights Bausch's unique artistic vision and its impact on the performance of 'Rite of Spring.'
In 1961, Bruno Walter provided a set of instructions for performing Gustav Mahler's 9th Symphony to the Columbia Symphony Orchestra during rehearsals in Hollywood This performance concept is partially documented in the CD titled "Bruno Walter conducts and talks about Mahler Symphony No 9: rehearsal & performance."
The "performance handbook" for Luigi Nono's composition 'À Pierre' (F1) is encapsulated in the detailed set of instructions provided in the performance handbook for this work (F2).
The third alternate take of Elvis Presley's musical work "Blue Hawaii," recorded on March 22, 1961, at Radio Recorders in Hollywood, California, showcases a unique interpretation of the song This version is characterized by distinct elements that differentiate it from the original, highlighting the artistic evolution of Presley's performance.
Hawaii’ as performed by Elvis Presley in Hollywood, Calif., Radio Recorders, on March 22nd,
In February 1945, the historic meeting of the three Allied leaders at Yalta was captured in a renowned photograph, symbolizing their collaboration during World War II.
Oceania Project’s concept of making a large digital acoustic data archive dedicated to East Australian humpback whale songs (F1) is realised in the audio content of the album entitled
‘Songlines – Songs of the East Australian Humpback Whales’ released in 2011 (F2).
The concept of recording Louise Bourgeois’s artistic activity in the documentary entitled
‘Louise Bourgeois: The Spider, the Mistress, and the Tangerine’ (F1) is realised in the audiovisual content of the documentary entitled ‘Louise Bourgeois: The Spider, the Mistress, and the Tangerine’ (F2).
Subproperty of: E73 Information Object P165 incorporates (is incorporated in): E90 Symbolic Object
Scope note: This property associates an instance of F3 Manifestation with one or more instances of F2
The F3 Manifestation instance presents expressions in a specific format for public presentation, determining the intended sensory experience, such as visual or auditory elements Meanwhile, the content of the F2 Expression instances is defined at a more abstract symbolic level, like text or notated music, which is distinct from the tangible F3 Manifestation instances, such as books or musical scores.
Examples: The publication identified by ISBN ‘2-222-00835-2’ (F3) embodies the text of Marin
LRMER TO LRMOO MAPPING
[PR: insert completed mapping when finished]
REFERRED TO CIDOC CRM CLASSES AND PROPERTIES
List of Referred to CIDOC CRM Classes
This section provides a list of classes from the CIDOC CRM Conceptual Reference Model version 7.1.1, as referenced by LRMOO Classes that are indirectly included in the LRMOO Model, either as superclasses or as the domain or range of associated CRM properties, are highlighted in bold This list encompasses the classes essential for mapping LRMer entities.
[PR: to be revised, use latest CRMbase, v.7.1.1 and final mapping]
List of Referred to CIDOC CRM Properties
This section outlines the properties of CIDOC CRM version 7.1.1 as referenced by LRMOO, highlighting those that are indirectly represented in the LRMOO Model as superproperties of the defined properties, which are emphasized in bold.
[PR: to be revised, use latest CRMbase, v.7.1.1 and final mapping]
4.3 List of Classes Transferred to CRMsoc
In this section, we present as a list, the classes from the LRMOO model that will transition to the CRMsoc Model.
4.4 List of Properties Transferred to CRMsoc
This section outlines the properties from the LRMOO model that will be incorporated into the CRMsoc Model It is essential to verify if these properties are included in the LRM(er) mapping or if they are exclusively part of the transition from FRBRoo.
Property id Property Name Entity – Domain Entity – Range
R45 assigned to (was assigned by) F52 Name Use Activity E1 CRM Entity
R57 is based on (is basis for) F38 Character E39 Actor
R58 has fictional member (is fictional member of) F38 Character F38 Character
R59 had typical subject (was typical subject of) F51 Pursuit E1 CRM Entity R60 used to use language (was language used by) F51 Pursuit E56 Language
R61 occurred in kind of context (was kind of context for) F52 Name Use Activity E55 Type
R62 was used for membership in (was context for) F52 Name Use Activity E74 Group
R63 named (was named by) F52 Name Use Activity E1 CRM Entity
R64 used name (was name used by) F52 Name Use Activity E41 Appellation