Application of FRBR and FRSAD to classification systems · MAJA ŽUMER UNIVERSITY OF LJUBLJANA, SLOVENIA & MARCIA LEI ZENG KENT STATE UNIVERSITY, USA Application of FRBR and FRSAD

M A J A Ž U M E R

U N I V E R S I T Y O F L J U B L J A N A , S L O V E N I A

&

M A R C I A L E I Z E N G

K E N T S T A T E U N I V E R S I T Y , U S A

Application of FRBR and FRSAD to classification systems

Interational UDC Seminar 2015 Lisbon, Portugal29.-30. 10. 2015

The FRBR family models: main entities and relationships

FRBR

FRAD

FRSAD

Source: Žumer, Zeng, and Salaba, 2010. FRBR: A Generalized Approach to Dublin Core Application Profiles. Proc. Int’l Conf. on Dublin Core and Metadata Applications 2010

1. FRBR and Classification Systems

Modelling versions of a classification system

French

DDC 22

German

DDC 22

Italian

DDC 22Swedish

Mixed

DDC 22

Italian

A14

Vietnamese

A14French

A14

Spanish A14Hebrew

A14

200

Religion

Class

Guide

(French)

DDC 22

A14

DDC Sach-

Gruppen

(German)

DDC

Summaries

English

French

Italian

Rhaeto-Romansch

Afrikaans

Arabic

Chinese

French

German

Norwegian

Portuguese

Russian

Scots Gaelic

Spanish

Swedish

Versions of a classification

system

-- Using DDC as an examlple

A top-level view of the different versions of the DDC emanating

from DDC 22

Classification Systems & FRBR Model

1. What is the “Work”?

Is it the system as a whole (“DDC”), or an edition of the system (“DDC 22”)?

Does this vary by system to be modelled?

2. How should the entities expression, manifestation and item be applied to classification systems?

Classification as work Edition as work

W

E

M

embodied in

When dealing with multiple versions ...

W

E

M

More relationships introduced -- Another example

2. FRSAD and Classification Systems

Modelling the subject relationship, aboutness

1. FRSAD Conceptual Model

The core of the FRSAD conceptual model

NOMEN = any sign or

arrangement of signs

(alphanumeric characters, symbols,

sound, etc.) that a thema is known

by, referred to or addressed as

Thema = “any entity

used as a subject of

a work".

The core of the FRSAD conceptual model

FRSAD Part 1:

WORK has as subject THEMA / THEMA is subject of WORK

FRSAD Part 2:

THEMA has appellation NOMEN / NOMEN is appellation of THEMA

Note: in a given scheme and within a domain, a nomen

should be an appellation of only one thema.

NOMEN = any sign or sequence of signs (alphanumeric characters, symbols,

sound, etc.) that a thema is known by, referred to or addressed as.

Source: STN Database Summary Sheet: USAN (The USP Dictionary of U.S. Adopted Names and International Drug Names)

Example:

Nomen 1-8

Nomen 9

THEMA –TO –THEMA RELATIONSHIPS

within one classification system

thema@schemeS nomen(s)

Semantic relationships are

established among themas:

• hierarchical

• associative

• other-specific if

needed

thema

thema

thema thema

thema thema

nomen(s)

nomen(s)

nomen(s)

DDC in FRSAD

• Each DDC class corresponds to a thema

• Notation associated with the class is a nomen

• Thema is the full category description of the class

• Nomen is the symbol (or surrogate) used to represent the full category description:

• dewey.info URI

• hierarchically contextualized caption

• Relative Index (RI) terms corresponding to functionally equivalent topics

‘546.663’ @ ddc

class@ddc

‘546.66’ @ ddc

has nomen

has nomen

has super class

‘*Mercury’ @ en

has caption

‘Group 12’ @ en

has caption

DDC in FRSAD

Thema: Class 025.04

“including”

“class here”

“class

elsewhere”

Thema: Class 025.04

Thema-thema

relationships

associative

relationship

associative relationship

(poly)hierarchical

relationship

topics that are

functionally

equivalent to the

class

Notation for / Caption of Class

Notation Hierarchically-contextualized caption

362.196462 Social problems of and services to groups of people / People with physical illnesses / Medical services / Diabetes

616.462 Medicine / Specific diseases / Diseases of endocrine system / Diabetes mellitus

616.46206 . . . / Diabetes mellitus / Treatment

618.3646 Medicine / Gynecology and obstetrics / Diseases and complications of pregnancy / Diabetes

618.92462 Medicine / Pediatrics / Diabetes mellitus

641.56314 Cooking for people with medical conditions / People with diabetes

Core thema-nomen relationship

Alternative nomens: Relative Index terms with equivalence relationship to class

More Classification Systems

Universal Decimal Classification (UDC)

Mathematics Subject Classification (MSC) 2010

WHO International Statistical Classification of Diseases and Related Health Problems (ICD-10)

Universal Decimal Classification (UDC) - example

025.3/.6 Departments concerned with exploitation, utilization of the literature

025.4Classification and indexing Indexing and retrieval languages. Classifications, thesauruses etc. and their construction

025.4.01Classification principles and procedure Characteristics of division. Facets. Citation order. Filing order. Notation

025.4.02Practical application, uses of classification Shelf arrangement. Catalogue arrangement. Bibliographic use

025.4.03 Searching and retrieval techniques

025.4.032 Manual search and retrieval

025.4.034 Mechanical sorting With punched card equipment

025.4.036 Computer-aided search and retrieval

025.4.05Indexing and retrieval languages for the whole of knowledge Universal classifications. Universal thesauruses

025.4.06Indexing and retrieval languages for special subjects Special classifications. Special thesauruses

Source: UDC English Edition online http://www.udc-hub.com/en/login.php

Mathematics Subject Classification (MSC) 2010 - example

Source: http://www.ams.org/msc/msc2010.html?t=62-XX&btn=Current

WHO International Statistical Classification of Diseases and Related Health Problems (ICD-10) -- example

source: http://apps.who.int/classifications/icd10/browse/2016/en

What is the motivation?

Clarifying and understanding

Thema vs. Nomen

Appropriate allocation of attributes and relationships

The structure

→ Enables

Mapping

Linking

Aligning

Nomen-based mapping will lead to incorrect matches

thema@schemeS

nomen(s)

labelB@schemeX

labelC@schemeY

labelD@schemeZ

Concept URI

term@enterm@frentry-terms

notation@scheme#1notation@scheme#nalternative-notations

notes

a label is only an attribute of a thema

They LOOK similar. But are they the same thing?

They LOOK similar. But are they the same thing?

This is the situation we can find in many nomen-based mapping results (string-string mapping, not concept-concept mapping, no context).

recruitmentFrom XYZ

(URI hidden from display in this ppt)

recruitment

http://vocabs.lter-europe.net/EnvThes/USLterCV_458.html

Possible reasons:• Automatic label mapping• Did not validate the broader concepts – wrong family• Did not have narrower concepts for double checking.The extension of a concept can help to identify the intension (meaning) of the concept.

(URI hidden from display in this ppt)

From XYZ

Concept

inScheme

CLC

:

CCT Concept

skos:exactMatch

skos:broadMatch

thema A

@schemeX

Nomen(s)

thema@

schemeS

skos:closeMatch

thema B

@ schemeY

skos:relatedMatch

{has relation with}

nomennomen(s)

nomen(s)

thema－based mappingensures semantic interoperability

skos:narrowMatch

skos:exactMatch

skos:closeMatch

Features:

• Each thema in a scheme is mapped

from individual themas (including built

and post- coordinated) from other

sources.

•Any thema retains its own semantic

relations.

•The degree of matching is indicated.

Advantages:

• nomens can be changed or added

easily (e.g., another language

version)

• new KOS can be included

continuously

Sneak peek preview

FRBR - Library Reference Model (LRM) - draft

High-level conceptual model

Expressed in entity-relationship framework

Consistent view of bibliographic universe

Work informed by Research with users

FRBRoo and CIDOC CRM

Experiences implementing FRBR, FRAD, FRSAD

Semantic Web and Linked Data context

In a nutshell

More general, high level model

Allows implementors to add details in a consistent way

WEMI and primary relationships remain unchanged

Agent introduced (Person and Collective agent as subclasses)

Attributes and relationships more general

Thema → Res

Nomen

Place and Time-span as entities

User Tasks

• Find

• Identify

• Select

• Obtain

• Explore

• Confirm end-user focus of the model

• Library internal processes are not reflected in the tasks

• Reworded definitions to be more general

The decision was to declare the relationships and attributes in a general, abstract way and thus enable implementers to include additional details in a consistent and coherent way by introducing additional specific types.

Appellation relationship

RES has appellation is appellation of NOMEN M to M

Responsibility relationships

WORK was created by created AGENT M to M

EXPRESSION was created by created AGENT M to M

MANIFESTATION was created by created AGENT M to M

MANIFESTATION is distributed by distributes AGENT M to M

MANIFESTATION was produced produced AGENT M to M

ITEM is owned by owns AGENT M to M

ITEM was modified by modified AGENT M to M

Other important relationships

WORK has as subject is subject of RES M to M

RES has association with is associated with PLACE M to M

RES has association with is associated with TIME-SPAN M to M

Next steps

• Review by IFLA Cataloguing, Classification and Indexing, and Bibliography sections

• World-wide review in early 2016

• Final approval in 2016

M A J A Ž U M E R

U N I V E R S I T Y O F L J U B L J A N A , S L O V E N I A

&

M A R C I A L E I Z E N G

K E N T S T A T E U N I V E R S I T Y , U S A

Application of FRBR and FRSAD to classification systems

THANK YOU!