Transforming FRBR into FRBRoo

Transforming FRBRinto FRBROO

Ciclo “Biblioteche, libri, documenti: dall’informazione alla conoscenza” organizzato dalla prof.ssa Maria Teresa Biagetti

Rome, 10 May 2013Patrick Le Boeuf, National Library of France

INTRODUCTIONTransforming FRBR into FRBROO

FRBR:A Model for

the 19th century?

Charles A. Cutter, Catalogue of the

Library of the Boston Athenæum (1874-82)

FRBR: A Modelfor 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)

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

FRBR: A Modelfrom the Librarians’ Community

• In the meantime, in museums… 1995: development of ICOM’s CIDOC

CRMICOM: International Council of MuseumsCIDOC : International Committee for DocumentationCRM: Conceptual Reference Model

2006: CIDOC CRM published as ISO 21127

Today: refinements still being made in the CIDOC CRM

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)

QUICK REMINDER ON THE ‘FR FAMILY’

Transforming FRBR into FRBROO

Thema Nomen

Rules Agency

is governed by creates/modifies

applies

is about

Person

Corporate BodyFamily

ItemManifestation

Expression

ConceptObjectEventPlace

Work

ControlledAccess Point

is basis for

Name

Identifier

has appellation

FRBR + FRAD + FRSAD

BRIEF PRESENTATION OF CIDOC CRM


E39 Actor E28 Conceptual ObjectE18 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

‘IF THERE’S A DATE, THERE’S AN EVENT!’


What are the Dates you can think of in a

Bibliographic Record?

Publication Date vs. Printing Date

F30 Publication

EventP4 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

What does the FRBR attribute ‘Date of Expression’ mean?

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

Summary so far

F30 Publication

Event

F32 Carrier Production

Event


F5 Item

R6 carries

R24 created

R28 produced


R17 created F2 Expression

R14 incorporatesis a subclass of

What does the FRBR attribute

‘Date of Work’ mean?FRBR: ‘The date of the work is the date (normally the year) the work was originally created’

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?

From ‘the date the Workwas 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’

Work Conception

P4 has time-span

E52 Time-Span

E50 Date


P4 has time-span

E52 Time-Span

E50 Date



R17 createdF22 Self-Contained Expression

F1 WorkF27 Work Conception

E21 PersonE55 Type

P14 carried out byP14.1 in role of

E21 Person

E55 TypeP14 carried out by

P14.1 in role ofR16 initiated

R3 is realised in

(e.g., ‘author’)

(e.g., ‘translator’)

Further Dates, Further Events

F29 Recording

Event

P4 has time-span

E52 Time-Span

E50 Date


F31 Performance

P4 has time-span

E52 Time-Span

E50 Date


F33 Reproduction

Event

P4 has time-span

E52 Time-Span

E50 Date


(of recording) (of performance) (of reproduction)

What are the Dates you can think of in an

Authority Record?

‘Date’ Attribute for a Person

F51 Pursuit

P4 has time-span

E52 Time-Span

E50 Date


E21 Person

P14 carried out by

E67 Birth

P4 has time-span

E52 Time-Span

E50 Date


E69 Death

P4 has time-span

E52 Time-Span

E50 Date


P98 brought into life P100 was death of

(of birth) (of activity) (of death)

‘Date’ Attribute for a Family(declared, but not defined, in FRAD)

F51 Pursuit

P4 has time-span

E52 Time-Span

E50 Date


F39 Family

P14 carried out by

(of activity)

‘Date’ Attributefor 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


F11 Corporate

BodyP14 carried out by

F51 Pursuit

P4 has time-span

E52 Time-Span

E50 Date


F11 Corporate

BodyP14 carried out by

E66 Formation

P4 has time-span

E52 Time-Span

E50 Date


E68 Dissolution

P4 has time-span

E52 Time-Span

E50 Date


P95 formed P99 dissolved

(of meeting, conference,

etc.)

(of formation) (of activity) (of dissolution)

FRAD: ‘Dates of Usage’ Attribute for a Name

P4 has time-span E52 Time-Span

E50 Date


(of usage)

F52 Name Use Activity

E1 CRM Entity

E41 Appellation

P1 is identified by

R63 named R64 used name

A MODELFOR AUTHORITY WORK


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

R38 refers to

R37

sta

tes

R64

use

d na

me

R63 named

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

R45

ass

igne

d to

R46 assignedP142 used constituent

e.g., saying: “Ciao tutti!mi chiamo Umberto Eco”

e.g., Umberto Eco

e.g., RICA

e.g., ICCU

e.g., Eco, Umberto

e.g., statement in record IT\ICCU\0000019852

e.g., SBN as of April 10, 2013

e.g.,

Authority work in FRBROO (simplified view)

e.g., creating record IT\ICCU\0000019852

E31 Document

P70 documentse.g., Dizionario della letteratura…

WHAT ABOUT THE ‘WEMI’ CLASSES IN FRBROO?


WorkF1 Work

F14 Individual

WorkF15 Complex

WorkF21

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

ExpressionF2

Expression

is a subclass of

F22 Self-Contained Expression

F23 Expression Fragment


F25 Performance

PlanF26

Recording

F34 KOSF35 Nomen

Use Statement



Manifestation


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

Item

F5 Item

WHO USES FRBROO?Transforming FRBR into FRBROO

BY WAY OF CONCLUSIONTransforming FRBR into FRBROO

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

Data & Analytics

Transforming FRBR into FRBRoo