Conferenza tenuta presso la ex SSAB da Patrick Le Boeuf (Bibliothèque Nationale de France) il 10-05-2013 nell'ambito del 7. ciclo "Biblioteche libri documenti: dall'informazione alla conoscenza", a.a. 2012-2013, Prof.ssa M.T. Biagetti

1. Transforming FRBR
into FRBROO
Ciclo “Biblioteche, libri, documenti: dall‟informazione alla conoscenza”
organizzato dalla prof.ssa Maria Teresa Biagetti
Rome, 10 May 2013
Patrick Le Boeuf, National Library of France

2. INTRODUCTION
Transforming FRBR into FRBROO

3. FRBR:
A Model
for the 19th
century?
Charles A. Cutter,
Catalogue of the Library
of the Boston Athenæum
(1874-82)

4. FRBR: A Model
for the 21st century?
• 2009: International Cataloguing Principles, ICP
(replacing the ‘Paris Principles’)
• 2009: Regole italiane di catalogazione, REICAT
(replacing RICA)
• 2010: Resource Description and Access, RDA
(replacing AACR)

5. FRBR: A Family of Models
• 1998: Functional Requirements for
Bibliographic Records, FRBR
• 2009: Functional Requirements for
Authority Data, FRAD
• 2011: Functional Requirements for
Subject Authority Data, FRSAD
• 20..: on the agenda: a single model
merging FRBR, FRAD, FRSAD

6. FRBR: A Model
from the Librarians’ Community
• In the meantime, in museums…
 1995: development of ICOM’s CIDOC CRM
ICOM: International Council of Museums
CIDOC : International Committee for Documentation
CRM: Conceptual Reference Model
 2006: CIDOC CRM published as ISO 21127
 Today: refinements still being made in the
CIDOC CRM

7. FRBR + CIDOC CRM = FRBROO
• 2003: International Working Group on
FRBR and CIDOC CRM Harmonization
• 2009: FRBROO version 1.0
(bibliographic data only)
• 2012-2013: FRBROO version 2.0
(bibliographic + authority data)

8. QUICK REMINDER ON THE
‘FR FAMILY’
Transforming FRBR into FRBROO

9. Thema Nomen
Rules Agency
is governed by creates/
modifies
applies
is about
Person
Corporate Body
Family
Item
Manifestation
Expression
Concept
Object
Event
Place
Work
Controlled
Access Point
is basis for
Name
Identifier
has appellation
FRBR + FRAD + FRSAD

10. BRIEF PRESENTATION OF
CIDOC CRM
Transforming FRBR into FRBROO

11. E39 Actor E28 Conceptual Object
E18 Physical Thing
E52 Time-Span E53 Place
E55 TypeE41 Appellation
involves affects
occurs during occurs in
identifies any of
serves to categorize any of
E5 Event
The Core of CIDOC CRM

12. ‘IF THERE’S A DATE,
THERE’S AN EVENT!’
Transforming FRBR into FRBROO

14. Publication Date vs. Printing Date
F30 Publication
Event
P4 has time-span
F32 Carrier
Production Event
F19 Publication
Work
F24 Publication
Expression
F5 Item
E52 Time-Span
E50 Date
E52 Time-Span
E50 Date
P4 has time-span
P78 is identified by P78 is identified by
(in FRBR: „Date of Manifestation‟ attribute) (in FRBR: no attribute declared;
would be „Date of Item‟)
R3 is realised in
R6 carries
R24 created
R23 created a realisation of
R28 produced

16. Externalizing an Expression
F28 Expression
Creation
R17 created
E65 Creation E12 Production
F2 Expression
F4 Manifestation
Singleton
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
R18 created
is a subclass of is a subclass of

17. Summary so far
F30 Publication
Event
F32 Carrier
Production Event
F24 Publication
Expression
F5 Item
R6 carries
R24 created
R28 produced
F28 Expression
Creation
R17 created
F2 Expression
R14 incorporatesis a subclass of

18. FRBR: ‘The date of the work is
the date (normally the year) the
work was originally created’

19. When was a Work
‘originally created’?
• = Earliest known Expression?
• = Earliest known Manifestation Singleton?
• But, then, Work Creation is in no way
distinct from Expression Creation? How to
model the notion of ‘earliest known …’
without using complex algorithms?

20. From ‘the date the Work
was originally created’…
• … to:
‘the date the Work was originally conceived‟
• Controversial:
 How do we know?
 What if a Work is conceived by A and realized by B?
• However, useful in order to express
the notion of ‘Creator of the Work’

21. Work Conception
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
F28 Expression
Creation
R17 createdF22 Self-Contained
Expression
F1 Work
F27 Work
Conception
E21 Person
E55 Type
P14 carried out byP14.1 in role of
E21 Person
E55 TypeP14 carried out by
P14.1 in role of
R16 initiated
R3 is realised in
(e.g., „author‟)
(e.g., „translator‟)

22. Further Dates, Further Events
F29 Recording
Event
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
F31 Performance
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
F33 Reproduction
Event
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
(of recording) (of performance) (of reproduction)

24. ‘Date’ Attribute for a Person
F51 Pursuit
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
E21 Person
P14 carried out by
E67 Birth
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
E69 Death
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
P98 brought into life P100 was death of
(of birth) (of activity) (of death)

25. ‘Date’ Attribute for a Family
(declared, but not defined, in FRAD)
F51 Pursuit
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
F39 Family
P14 carried out by
(of activity)

26. ‘Date’ Attribute
for a Corporate Body
Date of meeting,
conference, etc.
Date of establishment,
dates of existence
E7 Activity
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
F11 Corporate
Body
P14 carried out by
F51 Pursuit
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
F11 Corporate
Body
P14 carried out by
E66 Formation
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
E68
Dissolution
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
P95 formed P99 dissolved
(of meeting,
conference, etc.)
(of formation) (of activity) (of dissolution)

27. FRAD: ‘Dates of Usage’
Attribute for a Name
P4 has time-span
E52 Time-Span
E50 Date
P78 is identified by
(of usage)
F52 Name Use
Activity
E1 CRM Entity E41 Appellation
P1 is identified by
R63 named R64 used name

28. A MODEL
FOR AUTHORITY WORK
Transforming FRBR into FRBROO

30. F35 Nomen Use
Statement
F52 Name Use
Activity
E1 CRM Entity
(i.e., anything in
the real world)
F50 Controlled
Access Point
E41 Appellation
R32 is warranted by
R37states
R64usedname
R8 consists of
F34 KOS
(i.e., authority file)
R35 is specified by
F40 Identifier
Assignment
F43 Identifier Rule
R52 used ruleF44 Bibliographic
Agency
P14 carried out by
R45assignedto
e.g., saying:
“Ciao tutti!
mi chiamo
Umberto Eco”
e.g., Umberto Eco
e.g., RICAe.g., ICCU
e.g., Eco, Umberto
e.g., statement in record ITICCU0000019852
e.g., SBN as of April 10, 2013
e.g.,
Authority work in FRBROO
(simplified view)
e.g., creating record ITICCU0000019852
E31 Document
P70 documents
e.g., Dizionario della letteratura…

31. WHAT ABOUT THE ‘WEMI’
CLASSES IN FRBROO?
Transforming FRBR into FRBROO

32. Work
F1 Work
F14 Individual
Work
F15 Complex
Work
F21 Recording
Work
F16 Container
Work
F17 Aggregation
Work
F19 Publication
Work
F20 Performance
Work
F18 Serial
Work
is a subclass ofis a subclass of is a subclass of is a subclass of
is a subclass of is a subclass of is a subclass of
is a subclass of
is a subclass of

33. Expression
F2 Expression
is a subclass of
F22 Self-Contained
Expression
F23 Expression
Fragment
F24 Publication
Expression
F25 Performance
Plan
F26 Recording
F34 KOS
F35 Nomen
Use Statement
is a subclass of is a subclass of
is a subclass of
is a subclass of is a subclass of is a subclass of

34. Manifestation
F24 Publication
Expression
F3 Manifestation
Product Type
CLR6 should carry
F4 Manifestation
Singleton
F3 Manifestation
Product Type
CLR6 should carry
e.g., hardcover e.g., paperbacka unique carrier,
e.g., a manuscript

35. Item
F5 Item

36. WHO USES FRBROO?
Transforming FRBR into FRBROO

42. IS FRBR/FRBROO ALREADY
OUTMODED?
Transforming FRBR into FRBROO

43. A Declaration of Imperialist War
• November 2012: publication of the
BIBFRAME model by Library of Congress
 Incompatible with RDA
 Incompatible with International Cataloguing
Principles
 Incompatible with FRBR
 Basically only compatible with MARC21 and
AACR
 … but curiously, partially compatible with FRBROO:

44. F24 Publication
Expression
F3 Manifestation
Product Type
CLR6 should carry

45. BY WAY OF CONCLUSION
Transforming FRBR into FRBROO

46. By Way of Conclusion
• No need to make FRBROO visible by end-users
• No need to make FRBROO visible by cataloguers
• FRBROO is not a display tool
• FRBROO is a formalization of the meaning of the
information embedded in catalogues
• FRBROO is a tool to interpret and interconnect
existing data sets
• FRBROO may well be more widely used in the
future outside libraries than within them