<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="6204" public="1" featured="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="http://repositorio.febab.org.br/items/show/6204?output=omeka-xml" accessDate="2026-04-17T08:53:50-07:00">
  <fileContainer>
    <file fileId="5265">
      <src>http://repositorio.febab.org.br/files/original/56/6204/RDA_Chris_eng.pdf</src>
      <authentication>a113e6da1d7eb927f2d8e7361bc401ba</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="92">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="70626">
                  <text>RDA
for now and for the future
Chris Oliver
Chair, RDA Board
christine.oliver@uottawa.ca
1

�Organizing bibliographic information
Context for our work in the 21st century:
• users interact with bibliographic data in a broad, global context
• bibliographic data is managed inside and outside traditional catalogues

• no library is an island – everyone’s data is interconnected
• metadata supports linking to and aggregating with data from other
communities
• metadata can be harvested, re-used, and mined

2

�RDA: Resource Description and Access
RDA is a package of:
◦ data elements
◦ guidelines and instructions
→ for creating library and cultural heritage resource metadata
→ metadata that can be used in traditional catalogues
→ metadata that is ready for use in linked data applications

3

�2 significant facets of RDA
• RDA as a standard for use with current and emerging technologies
• RDA as a standard that is being intentionally internationalized

4

�RDA as a
standard for
use with
current and
emerging
technologies
Creator: ipopba -Credit: Getty
Images/iStockphoto

5

�A standard for the

st
21

century

• recording data, not strings

machine processing

• a shared element set

data interoperability

• suitable for wide range of
technological environments

flexibility

• optimized for linked data
environments

ready for the future

6

�RDA is a package of data elements
• data elements that can be understood by humans and processed by computers
• current reality = vast amounts of bibliographic data
• no longer practical to think that the management of bibliographic data will be
manually curated
• reality of reliance on machine processing

• but machines need good data to produce useful results

7

�RDA is a package of data elements
RDA = a set of precisely defined data elements (and controlled vocabularies)
• each data element contains only one type of data – unambiguous data
• RDA has elements for recording data about 13 entities
• RDA has over 3,000 elements

8

�RDA data designed for interoperability
• clearly defined element set
different types of RDA users all share the same element set
openly published controlled vocabularies to increase interoperability

definition and structure make it easier to map to non-RDA data
• recognizable structure for the data elements
explicit and widely accepted structure –
based on the internationally accepted bibliographic conceptual model:
IFLA Library Reference Model (IFLA LRM)

9

�Designed for flexibility
Four recording methods
• options according to the technological environment in which one operates:
• unstructured description
• structured description
• identifier
• IRI – internationalized resource identifier
“The methods are listed in order of increasing utility in general applications
of RDA data, from low utility to high utility or smart data.”
• IRI → for linked data

10

�One standard -- many ways to use it
an unstructured description
transcribe the name of the author from the title page
or
automated data capture of information on a title page
result = a string of characters
a human can decipher and understand
a computer cannot process effectively – only good enough for keyword
searching

11

�One standard -- many ways to use it
IRI – internationalized resource identifier
an Internet standard
a globally unique identifier, for example, use it to record the name of a person

result = a machine-readable string
• a human cannot easily decipher and understand
• a computer can process very effectively in a linked data application
• a computer can retrieve a large amount of information using the IRI and may
also link to other information connected to that IRI
• expands the potential for exploration

12

�Metadata
statement using
IRIs
subject, object and
predicate all recorded
using IRIs
Screen image from the RDA Toolkit
(www.rdatoolkit.org) used by permission
of the Copyright Holders for RDA
(American Library Association, Canadian
Federation of Library Associations, and
CILIP: Chartered Institute of Library and
Information Professionals).
13

�Ready for the future
• optimized for linked data
• record RDA data using RDF-based encoding schemes

viable alternatives to MARC, such as Bibframe and Share-VDE
• many will continue to use MARC formats for a while
• RDA is not optimized for MARC, but RDA in MARC still a useful step forward
• RDA, especially in the new Toolkit, starts reorienting our thinking in terms of
data elements, relationships, using IRIs, etc.

14

�Metadata standard for the
• ready for the future
• flexible

• data that can be used effectively for
automated processing

• promotes data interoperability

st
21

century

create metadata that can be used in
traditional catalogues and also for the
web and linked data environments

precise and unambiguous data in welldefined data elements with an
articulated structure

15

�RDA as a
standard that is
being
intentionally
internationalized
Flags globe at
shutterstock (vector)
ID: 111655109 by
Alhovik

16

�An international standard
• aligned with international standards

sound theoretical framework

• accommodating different local
traditions

responsive to local needs

• translations are an integral part of the
standard

different language versions for
use in communities around the
globe

• in use in countries around the globe

governance to reflect
international participation

17

�RDA aligned with international standards
• RDA is aligned with:
IFLA’s International Cataloguing Principles
IFLA’s bibliographic conceptual model: IFLA LRM
• also includes a statement of relationship to other international standards
for example, metadata that can be stored in different encoding schemes,
such as MARC 21 and RDF

18

�RDA: implementation of IFLA LRM
IFLA LRM = IFLA Library Reference Model
the bibliographic conceptual model that consolidates and
supersedes the three previous IFLA models:

FRBR Functional Requirements for Bibliographic Records
FRAD Functional Requirements for Authority Data
FRSAD Functional Requirements for Subject Authority Data

19

�Alignment with IFLA LRM
• RDA based on an internationally accepted understanding of the structure of
bibliographic data
• IFLA LRM provides:

• the basic structure and organization for the content of RDA
• a recognized theoretical framework that was developed through international
cooperation and consensus

• built-in focus on the needs of the end-user through the user tasks

20

�Not “one size fits all”
RDA is designed so that metadata can be created to meet the interests of local
communities within a global framework for interoperability.
– Gordon Dunsire, Accommodating local cataloguing traditions in a global context, 2018

• basis for data interoperability → the shared element set
→ data shares the same structure (IFLA LRM)

• focus on the common ground we share

21

�Internationalization – a design objective
• data harmonization
“RDA is designed for an international audience with the expectation that
cataloguing agents will make application decisions when desirable”
…
“Given the flexibility of the guidance and recording methods, the metadata
provided by different agents will not necessarily be identical, but as well-formed
data it will be understood by any agent when shared. The emphasis is on data
harmonization rather than strict compatibility.”
RDA &gt; Introduction to RDA &gt; Objectives and principles governing RDA

22

�Accommodation of variations
IFLA LRM provides the basic structure for bibliographic data
→ RDA provides:
option to use any of a large number of precise data elements
choices on how to record the data
options for which instructions to use
options for sources of controlled vocabularies (VES)
options on how to punctuate and order elements
→ a cataloguing community makes the choices that suit their needs

23

�Cataloguing community’s choice
For example, when using controlled vocabulary (vocabulary encoding scheme) to
record data:
Structured description
Instruction to use one of the RDA vocabulary encoding schemes
Followed by instruction to use another suitable vocabulary
encoding scheme
Examples in RDA also show use of RDA vocabularies and external vocabularies

24

�Instructions for
broadcast
standard

Screen image from the RDA Toolkit
(www.rdatoolkit.org) used by permission of
the Copyright Holders for RDA (American
Library Association, Canadian Federation of
Library Associations, and CILIP: Chartered
Institute of Library and Information
Professionals).

25

�Examples using
non-RDA VES at
accessibility
content

Screen image from the RDA Toolkit
(www.rdatoolkit.org) used by permission of the
Copyright Holders for RDA (American Library
Association, Canadian Federation of Library
Associations, and CILIP: Chartered Institute of
Library and Information Professionals).

26

�Cataloguing community’s decisions
• Places within RDA Toolkit for a community to record and share its decisions:
policy statements
application profiles and other documents (shared or not)
community resources

27

�A multilingual standard
RDA

an international standard

8 – full translations integrated into the original RDA Toolkit
14 – language versions integrated in the RDA Registry
(partial translations = names of elements and controlled vocabularies)
• a standard that places equal value on all its language versions
• English is treated as one of the language versions
• English is the version used as starting point for translations, but deliberately
called a “version”

28

�A multilingual standard
• seamless integration of all language versions in the one RDA Toolkit and RDA
Registry
• visibility of all the different language communities using RDA

• all using the same element set and vocabularies

29

�RDA, a global metadata standard
• designed to be easy to use by metadata creators around the globe

• a standard to be maintained and developed jointly with representatives from
all regions of the globe
RDA governance internationalizes decision-making and management
Representation from all 6 regions of the globe
Africa, Asia, Europe, Latin America and the Caribbean, North
America and Oceania
30

�RDA, a framework for interoperability
cataloguing communities around the globe operate in different contexts
• different technological environments
• conventions and practices differ
• different needs in linguistic, national, and cultural cataloguing communities
our common interest
-- providing metadata that fulfills the needs of our end-users
-- data that can be processed accurately by computers
-- compatibility of bibliographic data across communities

31

�?
christine.oliver@uottawa.ca

32

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="56">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="70563">
                <text>Encontro de RDA no Brasil - Edição: 2 - Ano: 2021 (Evento on-line)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70617">
              <text>RDA, for now and for the future </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70618">
              <text>Catalogação</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70619">
              <text>The presentation will focus on RDA in the new RDA Toolkit. It is still the same RDA as in the original RDA Toolkit. The standard follows the same objectives and principles, and it continues to support the same ways of working as in the original RDA Toolkit. There are changes, but these changes are not disruptive. The standard looks different, it has expanded in scope, and it has been deliberately internationalized, to accommodate the needs of local cataloguing communities around the globe. It has evolved more fully to achieve its purpose of being an international metadata standard for both current and future environments.&#13;
The presentation includes an overview of the major developments that occurred during the 3R Project: the impact of the 3R Project itself, the results of aligning RDA with IFLA’s Library Reference Model (IFLA LRM), and the outcomes of internationalization.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70620">
              <text>Chris Oliver</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70621">
              <text>2021</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70622">
              <text>pdf</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70623">
              <text>inglês</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70624">
              <text>texto</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="70625">
              <text>https://youtu.be/79TqQnGIwDg</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
