Definition of Object-Oriented frbr

6.2. Amendments to Version 1.0.2

F40 Identifier Assignment

In the 17^th FRBR-CIDOC CRM meeting joined with the 23^rd meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9, it is decided to change the scope note of F40 for being compatible with Controlled Access Points from FRAD. So the scope note has been changed from:
Scope note: This class comprises activities that result in the allocation of an identifier to any Entity. An Identifier Assignment may include the creation of the identifier from multiple constituents. The syntax and kinds of constituents to be used may be declared in a rule. It also includes the assignment of uniform titles.

Examples: Assigning the author-title heading ‘Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.’ as a uniform title for a work

Assigning the title heading ‘Bible. English. American Standard’ as a uniform title for an expression

To:

Scope note: This class comprises activities that result in the allocation of an identifier to any E1 CRM Entity. An F40 Identifier Assignment may include the creation of the identifier from multiple constituents. 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. F40 Identifier Assignment also includes the assignment of uniform titles as controlled access points for works or expressions

Examples: Assigning the name heading 'William, Prince, Duke of Cambridge, 1982-' as a controlled access point for a personal name using the Anglo-American Cataloguing Rules, 2nd edition

Assigning the name heading 'Library and Archives Canada' as an authorised controlled access point for a corporate body name using the Anglo-American Cataloguing Rules, 2nd edition

Assigning the name heading 'Bibliothèque et Archives Canada' as an authorised controlled access point for a corporate body name using the Règles de catalogage anglo-américaines, 2e édition

Assigning the author-title heading ‘Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.’ as a uniform title for a work

Assigning the title heading ‘Bible. English. American Standard’ as a uniform title for an expression

F43 Identifier Rule

In the 18th FRBR - CIDOC CRM Harmonization meeting joined with the 24th meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9, it is decided that F43 Design or Procedure is a subclass of F2 Expression. This was one of the outcomes of the discussion about FRAD Rules. This decision produced the following changes in the document:

Page 129: The F43 Identifier Rule has been added to the superproperty section of F2

Page 131: The F2 is declared to Subproperty section of F43 Identifier Rule

in the table of FRBROO Property Hierarchy aligned with (part of) CIDOC CRM Property Hierarchy

R14 incorporates (is incorporated in)

In the 18th FRBR - CIDOC CRM Harmonization meeting joined with the 24th meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9, it is decided that R14 is also subproperty of P106 is composed of (forms part of). This decision produced the following changes in the document:

Page 59: The P106 has been added to the Subproperty section of the definition of R14

Page 34: The R14 is declared to Subproperty of P106 in the table of FRBROO Property Hierarchy aligned with (part of) CIDOC CRM Property Hierarchy

This is related to the issue 192

R15 has fragment (is fragment of)

In the 18th FRBR - CIDOC CRM Harmonization meeting joined with the 24th meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9, it is decided that R15 is not subproperty of P148 has component (is component of).

R40 has representative expression (is representative expression for)

For consistency purposes the frbr-crm group decided by email to make the following updates to the range, subproperty and scope note of R40.
From:

Domain: F1 Work

Range: F22 Self-contained Expression

Superproperty of:

Subproperty of: F1 Work.R3 is realised in (realises): F22 Self-contained Expression

Quantification: (0:n,0:n)

Scope note: This property identifies an instance of F2 Expression that has been chosen as the most characteristic expression of the instance of F15 Complex Work of which it is an expression.

Typically, any expression that is not regarded as “representative” for the work it expresses, would require a uniform title, 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 uniform title).

R40 has representative expression is a shortcut of the more developed path F1 Work R50B was assigned by F42 Representative Expression Assignment R51 assigned F2 Expression. "

To:

Domain: F1 Work

Range:F2 Expression

Superproperty of:

Subproperty of: E70 Thing. P130 shows features of (features are also found on): E70 Thing

Quantification: (0:n,0:n)

Scope note: This property identifies an instance of F2 Expression that has been chosen as the most characteristic expression of the instance of F1 Work of which it is an expression.

Typically, any expression that is not regarded as “representative” for the work it expresses, would require a uniform title, 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 uniform title).

R40 has representative expression is a shortcut of the more developed path F1 Work R50B was assigned by F42 Representative Expression Assignment R51 assigned F2 Expression.

This change produced the following updates:

Page 127: Figure 12 has been updated

Page 133: update property hierarchy table

Page 134: update the definition of R40

R47 used constituent (was used in)

In the 18^th FRBR-CIDOC CRM meeting joined with the 24^rd meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9, it is decided to change the range of R47 in order to cover situations where “whole and part” are applied in subject Authority Systems and the forms of names are not only represented in natural language but also are represented in artificial languages as codes, formulas, graphs etc as it is stated in FRSAD.

Thus the range of R47 was changed from F12 Name to E90 Symbolic Object. This change produces the following updates:

Page 126: Figure 11 has been updated

Page 130: update the range of R47 from F12 Name to E90 Symbolic Object in the property definition section of F40

Page 133: update the entry of R47 in Property Hierarchy Table

Proofreading

Page 9: The version number of CIDOC CRM from 5.0.1 became 5.0.4

Page 10: The word “draft” is deleted from the first sentence in the introduction.

Page 17: In the figure 4 the name of the property P128 has been corrected.

Page 19: In c. the code number of the relation R5 has been corrected from R15 to R5 and the figure 6 is updated.

Page 28: The class hierarchy of F16 Container work and F21 Recording Work has been corrected

Page 29: The FRBR_OO Class Hierarchy aligned with (part of) CIDOC CRM Class Hierarchy is updated

Page 32, 35 : In the line of R15, the domain and the range of the property has been corrected by interchanging them. This produced the following changes:

Page 19: In item b, the domain and the range of the property R15 has been corrected

Page 48: the declared property R15 in the definition of F23 has been deleted

Page 38: the R15 has been added to the properties of F2

Page 60: The domain and the range of the property R15 has been interchanged. In the section of the examples the direction of the property is corrected.

Page 127: Figure 12 has been updated

Page 34: The Property Hierarchy aligned with (part of) CIDOC CRM Property Hierarchy updated

Page 38: The underline has been removed from the text “The signs which make up” in the fourth example of F2

Page 42: the text “that was used to create a bibliographic record for that publication” from the second example of F9 has been dropped.

Page 126: The notation of R52 property has been corrected

Page 128: The class hierarchy of the FRBRoo Identifier Creation Model Aligned with CIDOC CRM has been updated. The entries of F42, F43 have been corrected

Page 133: Minor corrections to the property hierarchy table

Page 144: Updates to the referred CIDOC CRM Entities