An example of libraryand museum cooperation:

the FRBROO conceptual model

Patrick Le BoeufNational Library of France

CIDOC Annual Conference – 'Enriching Cultural Heritage' – Helsinki, 10-14 June 2012

Museums and libraries

akin but different…

mostly unique objects mostly copies of publications

How could they cooperate(at least as far as cataloguing is concerned)?

Museums and libraries

different but akin…

also non-unique objects also unique objects

… and interrelated objects

Museums and libraries

It does make sense to strive to make museums' and libraries' databases interoperable through a common conceptual model

Chronology and methodology

A striking coincidence

• 1998: release of a preliminary version of CIDOC CRM by ICOM CIDOC

• 1997: FRBR model approved by IFLA

FRBR and the 'FR family'

• FRBR = Functional Requirements for Bibliographic Records (1991-7, published 1998)– data pertaining to publications and holdings

• FRAD = Functional Requirements for Authority Data (published 2009)– data pertaining to authors and works

• FRSAD = Functional Requirements for Subject Authority Data (published 2011)– data pertaining to subjects and classification numbers

CIDOC CRM

• CRM = Conceptual Reference Model

• 1996: beginning of work

• 2000: formation of CIDOC CRM SIG (Special Interest Group)

• 2006: ISO standard ISO 21127:2006

FRBR/CIDOC CRM Harmonisation Group

• Formed 2003

• Representatives from– IFLA FRBR Review Group– CIDOC CRM SIG

• Objective: develop a unified model for descriptions of both unique and non-unique objects

How?

• Early decision: CIDOC CRM as reference point

• 'Translate' FRBR into the CIDOC CRM formalism

• Examine each attribute and relationship defined in FRBR

• Find equivalents in CIDOC CRM• Where no equivalent, declare new

subclasses and subproperties

How?

• Refine FRBR notions deemed too vague

• Add some new classes and properties to CIDOC CRM

• 2003-2012: 19 meetings

• June 2009: version 1.0 of FRBROO is released (OO = 'object-oriented')

• 2009-2012: work on FRAD and FRSAD

• 2012: version 2.0 is due

The FR family

An introduction

FRBR, or,How to make a catalogue

• FRBR entities reflect the way cataloguers organise their work

• First, they examine a physical object…

FRBR, or,How to make a catalogue

• Then, they extrapolate the characteristics of the publication the physical object belongs to

Publication Publication Publication Publication

FRBR, or,How to make a catalogue

• To end with, they use uniform titles to collocate publications with interrelated contents (e.g., the publication of a text and the publication of a translation of that text)

Publication Publication

Content Content

Family ofcontents

FRBR, or,How to make a catalogue

• Work

• Expression

• Manifestation

• Item

Publication Publication

Content Content

Family ofcontents

The Manifestation problem

• Manifestation = abstract definition (intension) of a set of items

• When a set has only one element, how to distinguish between intension and extension?

The Manifestation problem

No 'Manifestation' class in FRBROO

• Instead, two disjoint classes:

E28 ConceptualObject

E55 Type

F3 ManifestationProduct Type

E72 LegalObject

E24 PhysicalMan-Made Thing

F4 ManifestationSingleton

Work and Expression

• A distinction that did not exist in CIDOC CRM

• E73 Information Object = both concepts and their expression

CIDOC CRM had to be modified

• May 2008 (v. 4.2.5): introduction of E89 Propositional Object and E90 Symbolic Object

Work and Expression

E89 PropositionalObject

F1 Work

E73 InformationObject

E90 SymbolicObject

F2 Expression

Other FRBR entities

Expression

Manifestation

Item

Person

Corporate Body

Concept

Object

Event

Place

E39 Actor

Work

'is about'(= E89 Propositional Object. P129 is about (is subject of) E1 CRM Entity

Authority work

• Consists of– managing various appellations for any kind of

thing– stating relationships among those things

• Is modelled in FRAD and FRSAD

• Will be addressed in FRBROO v. 2.0

Michelangelo Buonarroti

Michael Angelo

Michelangiolo

Michel-Ange

Michał Anioł

Buonarroti, Michelagniolo

Authority workand CIDOC CRM

• Some aspects of authority work were deemed important enough to be introduced in CIDOC CRM

• Version 4.2.2 of CIDOC CRM (August 2007): E42 Object Identifier was renamed E42 Identifier, so as to apply to any kind of thing, like in the 'FR family'

Various types of Works

How the Work notionwas refined in FRBROO

The Work notion in FRBR

Work = 'a distinct intellectual or artistic creation'

The Work notion in FRBROO

F1 Work a sum of concepts…

F14 IndividualWork

F15 ComplexWork

… uniquely and completely expressed in a single 'text'

… expressed in a constellation of interrelated works

The boundaries of a 'complex work'

• Always somewhat arbitrary…– are these two distinct works, or just one work?

– With FRBR, such a question could lead to endless discussions…

– With FRBROO and F15 Complex Work it gets easier

Complex works in museums as well?

F14 IndividualWork

F15 ComplexWork

F14 IndividualWork

R10 has member (is member of) R10 has member (is member of)

Piranesi, Carceri d'invenzione,plate XIII

1st state 2nd state

A third subclass of F1 Work

F1 Work

F21 RecordingWork

A fourth subclass of F1 Work

F1 Work

F16 ContainerWork

F17 AggregationWork

F19 PublicationWork

F20 PerformanceWork

= work that adds value to expressions of other works by…

… putting them together (e.g., an anthology)

… publishing them … or performing them

Authority control

A new feature of FRBROO v. 2.0

What is authority control?

• An activity that consists of establishing controlled access points to uniquely identify any thing deemed to be of interest for users, and ensure it can be retrieved under its other forms of appellation

Leonardo, da Vinci, 1452-1519 Леонардо, да Винчи, 1452-1519

Dürer, Albrecht, 1471-1528. Kleine Passion Dürer, Albrecht, 1471-1528. Gospel for the unlearned

Mural painting and decoration Wall-painting

A model for authority control

E41 Appellation

F50 ControlledAccess Point

F13 Identifier

F12 Nomen

F35 Nomen UseStatement

F52 Name UseActivity

F34 KOS

R37 states as nomen

R35 is

spe

cified

by

R32 is warranted by

R64 used name

4000_ |a Леонардо, |c да Винчи, |d 1452-1519

Леонардо, да Винчи, 1452-1519

Леонардо да Винчи

Library of Congress Authorities

Authority data and interoperability

Buonarroti, Michelangelo Michelangelo Buonarroti, 1475-1564

CommonURI

(see also ICOM recommendation on Linked Open Data for museums, http://network.icom.museum/fileadmin/user_upload/minisites/cidoc/AGM_2011/LoD_For_Museums v1.6.pdf)

Introducing events in FRBR

How works,expressions, manifestations,and items come into being

The CIDOC CRMTop-level classes useful for integration

participate in

E39 Actors

E55 Types

E28 Conceptual Objects

E18 Physical Thing

E2 Temporal Entities

E41

Ap

pel

lati

ons

affect or / refer to

refer to / refine

refe

r to

/ i d

ent i f

y

location

atwithinE53 Places

E52 Time-Spans

E65 Creation

F27 WorkConception

R16 initiated(was initiated by) F1 Work

F2 ExpressionF28 Expression

Creation

E12 Production

R3 is realised in(realises)

R17 created(was created by)

F_ ManifestationCreation?

F3 ManifestationProduct Type

F4 ManifestationSingleton

E83 TypeCreation

CLR6 should carry (should be carried by)

F30 PublicationEvent

F24 PublicationExpression

E12 Production

F28 ExpressionCreation

P135 created type(was created by)

R24 created(was created through)

P108 produced (was produced by)

R18 created (was created by)

F32 CarrierProduction Event

R28 produced(was produced by)

E12 Production

F5 Item

F3 ManifestationProduct Type

R7 is example of(has example)

Introducing events in FRBR

Other types of events

F21 RecordingWork

F29 RecordingEvent

F26 Recording

F28 ExpressionCreation

F33 ReproductionEvent

E84 InformationCarrier

E84 InformationCarrier

E55 Type

{Reproduction}

R22 created a realisation of (was realised through)

E12 Production

R21 created (was created through)

R13 is realised in (realises)

R29 reproduced (was reproduced

by)R30 produced (was produced by)

P130 shows features of (features are also found on)

P130.1 kind of similarity

F31 Performance

E7 Activity

Introducing events in FRBR

Events relating to authority control

F40 IdentifierAssignment E42 Identifier

R46 assigned

(was assigned by)

F13 Identifier

F50 ControlledAccess Point

E1 CRM Entity

E90 SymbolicObject

E15 IdentifierAssignment

R45 assigned to

(was assigned by)

P142 used constituent (was used in)

Леонардо, да Винчи, 1452-1519

Леонардо

E41 Appellation

F35 Nomen UseStatement

F52 Name UseActivity

R32 is warranted by

(warrants)

R64 used name(was name used by)

F24 PublicationExpression

P67 refers to(is referred to by)

Леонардо да Винчи

F42 RepresentativeExpression Assignment

R50 assigned to

(was assigned by)

F41 RepresentativeManifestationAssignment

F15 ComplexWork

F2 Expression

F3 ManifestationProduct Type

F4 ManifestationSingleton

R51 assigned (was assigned by)

R48 assigned to

(was assigned by)

R49 assigned (was assigned by)

R53 assigned (was assigned by)

What remains to be done

What after FRBROO v. 2.0?

• Two types of resources were only partially modelled in FRBR:– Continuing resources– Digital resources

Partially modelled in FRBROO as well

What after FRBROO v. 2.0?

• Digital resources– See if CRMdig could be used in combination

with FRBROO?

• Continuing resources =– Serials (periodicals, bibliographic series)

• Some classes and properties to be added

– Integrating sources (loose-leaf publications, updating digital resources)

• To be checked

The work notionin libraries and museums

'Work' in libraries and museums

• Librarians would presumably feel urged to 'collocate' these 'expressions' through a reference to an alleged 'common work:'

• In museums this is not the case• F15 Complex Work supports both views

To conclude

From CIDOC CRM and FRBROO to Linked Data

Library and museum cooperationin the time of Linked Data

• No need to 'merge' our databases• FRBROO and CIDOC CRM can help

integrate the knowledge contained in our databases…

• … provided we agree on common rules for URI assignment!

• Linked Data is an opportunity for increased cooperation between libraries and museums

patrick.le-boeuf@bnf.fr