Application of FRBR and FRSAD to classification systems MAJ A ŽUMER UNIVERSITY OF LJ UB LJ ANA, SLOVENIA & MARCIA LEI ZENG KENT STATE UNIVERSITY, USA Interational UDC Seminar 2015 Lisbon, Portugal 29.-30. 10. 2015
The FRBR family models: main entities and relationships FRSAD FRBR FRAD 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
A top-level view of the different Versions versions of the DDC emanating of a classification from DDC 22 German Italian system DDC 22 DDC 22 Swedish French -- Using DDC as an Mixed DDC 22 examlple DDC 22 Afrikaans Arabic English Chinese DDC 22 French French DDC Sach- DDC Gruppen German Summaries Italian (German) Norwegian Rhaeto- Portuguese Romansch Russian 200 Guide Religion Scots Gaelic (French) Class Spanish Swedish A14 Vietnamese French A14 A14 Hebrew Spanish A14 A14 Italian A14
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?
When dealing with multiple versions ... Classification as work Edition as work W W E E embodied in M M
More relationships introduced -- Another example
2. FRSAD and Classification Systems Modelling the subject relationship, aboutness
The core of the FRSAD conceptual model 1 . FRSAD Conceptual Model � Thema = “ any entity used as a subject of a work". NOMEN = any sign or arrangement of signs (alphanumeric characters, symbols, sound, etc.) that a thema is known by, referred to or addressed as
The core of the FRSAD conceptual model � FRSAD Part 1: FRSAD Part 2: WORK has as subject THEMA / THEMA has appellation NOMEN / THEMA is subject of WORK 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. Example: Nomen 1-8 Nomen 9 Source: STN Database Summary Sheet: USAN (The USP Dictionary of U.S. Adopted Names and International Drug Names)
nomen(s) THEMA – TO – THEMA RELATIONSHIPS within one classification system thema nomen(s) thema@schemeS thema Semantic relationships are nomen(s) established among themas: • hierarchical thema thema • associative • other-specific if nomen(s) needed thema thema
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
DDC in FRSAD has caption ‘ 546.663 ’ @ ddc ‘* Mercury ’ @ en has nomen class@ddc has super class has caption ‘ 546.66 ’ @ ddc ‘Group 12 ’ @ en has nomen
Thema: Class 025.04 “ including ” “ class here ” “ class elsewhere ”
Thema: Class 025.04 Thema-thema topics that are relationships functionally equivalent to the class associative relationship (poly)hierarchical relationship associative relationship
Core thema-nomen relationship 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
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 Classification and indexing Indexing and retrieval languages. 025.4 Classifications, thesauruses etc. and their construction Classification principles and procedure Characteristics of division. 025.4.01 Facets. Citation order. Filing order. Notation Practical application, uses of classification Shelf arrangement. 025.4.02 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 Indexing and retrieval languages for the whole of knowledge 025.4.05 Universal classifications. Universal thesauruses Indexing and retrieval languages for special subjects Special 025.4.06 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/
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 a label is only an attribute of a thema thema@schemeS Concept URI term@en term@fr entry-terms notation@scheme#1 notation@scheme#n alternative-notations notes nomen(s) labelB@ schemeX labelC@ schemeY labelD@ schemeZ
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).
recruitment From XYZ (URI hidden from display in this ppt)
recruitment From XYZ http://vocabs.lter- europe.net/EnvThes/USLterCV_458.html (URI hidden from display in this ppt) 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.
thema － based mapping Concept skos:exactMatch thema A ensures semantic inScheme @ schemeX skos:closeMatch interoperability CLC Nomen(s) : {has relation with} thema@ schemeS CCT Concept thema B skos:exactMatch nomen nomen(s) @ schemeY skos:closeMatch nomen(s) skos:broadMatch skos:narrowMatch skos:relatedMatch
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 Confirm end-user focus • • of the model Identify • Library internal • Select • processes are not Obtain • reflected in the tasks Explore • 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
Recommend
More recommend
