1.
A Brief Presentation of PRESSOO
IFLA FRBR Review Group
Singapore, 19 August 2013

2.
A. METHODOLOGY

3.
Methodology
• January-March 2013: 7 meetings
– Examination of the semantics of each single
data element in the ISSN Manual
– Can this semantics be expressed using extant
FRBROO and CIDOC CRM classes and
properties?
– If not, then declare specific classes and
properties
– PRESSOO = sum of specific classes and
properties declared through that process

4.
B. SOME NECESSARY
REMINDERS ABOUT CIDOC
CRM AND FRBROO

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

6.
Some aspects of FRBROO
• F1 Work: a sum of
concepts
• F2 Expression: a sum of
signs
• 3 meanings for "Work":
– all concepts conveyed by
each individual Expression:
F14 Individual Work
– all concepts common to
various Expressions and
serving to identify
“bibliographic families”:
F15 Complex Work
– the concept of adding
something to Expressions
(e.g. by aggregating them):
F16 Container Work

7.
Serial Works in FRBROO
F1 Work
is a
is a
F15 Complex Work
F16 Container Work
is a
is a
F19 Publication Work
is a
F18 Serial Work
"There is no single expression
or manifestation representing
a complete serial work, unless
the serial work has ended."

8.
The publication process* in FRBROO
F19 Publication
Work
F30 Publication
Event
R3 is realised in
F24 Publication
Expression
CLR6 should carry
F32 Carrier
Production Event
R26 produced things of type
F3 Manifestation
Product Type
R7 is example of
R6 carries
F5 Item
*: for physical items; digital publishing is modelled slightly differently (no F3)

9.
C. PRESSOO

10.
Colour codes
• In the following slides:
E…
P…
= a property from CIDOC CRM
F…
R…, CLP… or CLR…
Z…
Y…
= a class from CIDOC CRM
= a class from FRBROO
= a property from FRBROO
= a class from PRESSOO
= a property from PRESSOO

11.
Chronological boundaries
F18 Serial Work
R23 created a realisation of
F30 Publication
Event
Z6 Starting of
Publication
Z7 Ending of
Publication
= Publication of earliest known issue
= Publication of latest known issue

12.
Describing a periodical
F18 Serial Work
Y38 has current issuing rule
Z12 Issuing Rule
Z12 Issuing Rule
Most of the description elements are not directly associated with the
instance of F18 Serial Work, but through multiple instances of Z12
Issuing Rule indicating various aspects of the plan for publication

13.
Describing a periodical:
aspects of a publication plan
Z12 Issuing Rule
Z12 Issuing Rule
Z12 Issuing Rule
Z12 Issuing Rule
Z12 Issuing Rule
Y24 foresees use of title
Y21 foresees use of language
Y22 foresees sequencing pattern
Y23 foresees dimension
Y20 foresees type
E35 Title
E56 Language
Z10 Sequencing Pattern
E54 Dimension
E55 Type
(of frequency, carrier, digital
format, content, medium…)
Z12 Issuing Rule
Y28 foresees URL
Z11 URL

14.
Describing a periodical:
changes in a publication plan
E50 Date
P78 is identified by
E52 Time-Span
P4 has time-span
Z5 Issuing Rule
Change
Y15 replaced
Z12 Issuing Rule
Y16 replaced with
Z12 Issuing Rule

15.
Relationships among
periodicals
Z12 Issuing Rule
Z12 Issuing Rule
Z12 Issuing Rule
Y25 foresees association with
(supplement, insert…)
Y26 foresees other edition
(different type of carrier,
abridged edition,
local edition…)
Y27 foresees translation in
Z12 Issuing Rule
Z12 Issuing Rule
Z12 Issuing Rule
(Not expressed directly from F18 Serial Work to F18
Serial Work, as the relationship can be stopped at any
time without loss of identity for the involved serials: the
relationship is therefore viewed as part of the production
plans for the two serials involved in the relationship)

16.
Relationships between
periodicals and monographs
F18 Serial Work
F18 Serial Work
Y39 is enhanced by monograph
(special issue,
supplementing monograph…)
Y40 enhances monograph
(base volume for an updating loose-leaf,
supplemented monograph…)
F19 Publication Work
F19 Publication Work
(Expressed directly from F18 Serial Work to F19
Publication Work, as the relationship remains valid at
any point in time throughout the life of the periodical)

17.
Continuations
F27 Work Conception
Z1 Serial
Transformation
Y29 evolved into
F18 Serial Work
Z7 Ending of
Publication
F30 Publication
Event
P134 continued
F18 Serial Work
Z6 Starting of
Publication
F30 Publication
Event

18.
„Supersedes‟ relationship
F27 Work Conception
Z1 Serial
Transformation
Y31 was superseded by
F18 Serial Work
Z7 Ending of
Publication
F30 Publication
Event
P134 continued
F18 Serial Work
Z6 Starting of
Publication
F30 Publication
Event

19.
Absorptions
E7 Activity
Z2 Absorption
Y35 was absorbed in
F18 Serial Work
F18 Serial Work
Z7 Ending of
Publication
F30 Publication
Event
F30 Publication
Event

20.
Separations
F27 Work Conception
Z3 Separation
Y30 was partially continued by
F18 Serial Work
F18 Serial Work
Z6 Starting of
Publication
F30 Publication
Event
F30 Publication
Event

21.
Mergers
F27 Work Conception
Y7 merged
Z1 Serial
Transformation
Y34 was merged to form
Z7 Ending of
Publication
F30 Publication
Event
Z7 Ending of
Publication
F18 Serial Work
F18 Serial Work
R23 created a
realisation of
F18 Serial Work
Z6 Starting of
Publication
F30 Publication
Event
P134 continued
P134 continued
P116 starts
F30 Publication
Event

22.
Splits
F27 Work Conception
Z1 Serial
Transformation
Y6 initiated
Y11 was split into
F18 Serial Work
Z7 Ending of
Publication
F30 Publication
Event
Z6 Starting of
Publication
F18 Serial Work
F18 Serial Work
Z6 Starting of
Publication
R23 created a realisation of
F30 Publication
Event
P134 continued
P134 continued
F30 Publication
Event

23.
Temporary replacements
R16 initiated
F18 Serial Work
Y36 had surrogate
R23 created a
realisation of
F27 Work
Conception
F18 Serial Work
R23 created a
realisation of
F30 Publication
Event
F30 Publication
Event
P10 falls within
(if the replacing serial pre-exists)
P9 consists of
F30
Publication
Event
F30 Publication
Event
P134
Z4 Temporary
Substitution
P134
F30 Publication
Event
P20 had specific purpose
(if the replacing serial
is created specifically
to replace the other one)