RSC Strategy
Gordon Dunsire, Chair, RDA Steering Committee
Presented at Casalini Libri meeting, 27 May 2016,
Fiesole, Italy
RDA strategy
3 targets:
International communities
Cultural heritage communities
Linked data communities
RDA is a package of data elements, guidelines, and
instructions for creating library and cultural heritage
resource metadata that are well-formed according to
international models for user-focussed linked data
applications.
RDA data
RDA Toolkit provides the user-focussed
elements, guidelines, and instructions.
RDA Registry provides the infrastructure for
well-formed, linked, RDA data applications.
Open Metadata Registry provides the linked
data representation of RDA Reference.
RDA data infrastructure
RDA Reference data:
Elements, attributes, relationships, values
Open Metadata
Registry (RDF)
RDA Registry
RDA Toolkit
FRBR-LRM and RDA
LRM “a high-level conceptual model … intended as a guide or
basis on which to elaborate cataloguing rules”
RDA guidance, instructions, elements
“operates at a greater level of generality than FRBRoo, which
seeks to be comparable in terms of generality with CIDOC CRM”
RDA cultural heritage communities
LRM “this model is developed very much with semantic web
technologies in mind”
RDA linked data communities
RDA refines LRM
relationships as
element sub-types
(RDF sub-properties)
FRBR-LRM and RDA
Any Thing:
Covers all other
types of thing
W
has appellation
Nomen
is created by
E
Agent
Place
is type of
M
I
Res
Collective
agent
is modified by
P
F
C
is associated with
Timespan
Refinements
Coarse/General
Res1
is associated with
Res2
has creator
has artist
Res1
is associated with
Fine/Specific
Res2
is derivative (E)
is adapted as (E)
is adapted as graphic novel (E)
Nomens and appellations
Res
M1
has appellation
has title proper
N1
Nomen
has literal form
“My title”
has title proper
has identifier …
M1
has literal form
N2
has identifier …
“0123-4567”
4-fold path
RDA database implementation
The “4-fold path” supports RDA data in catalogue cards,
flat file schema, RDBMS, and linked data
Describing a related entity:
Unstructured description
Structured description
Identifier
URI
General guidance and
instructions:
Simple
Less duplication
Easier to translate
Converging paths
Res1
has related entity
N3
Res2
has appellation
“0123-4567”
N2
N1
“[Authorized Access Point]”
“[Unstructured description]”
“[Variant Access Point]”
LRM-A6 Extent
LRM-A6 Extent
A quantification of the extent of the expression
The value of the Extent attribute must consist of three
elements:
• a type of extent (e.g., length of text, envisioned duration of
performance of musical notation, actual duration of
recorded performance, etc.),
• a number,
• and a measurement unit (words, minutes, etc.).
LRM-A16 Manifestation statement
A statement appearing in the manifestation and
deemed to be significant for users to understand
how the resource represents itself.
… normally transcribed from a source in a
manifestation. Transcription conventions are
codified by each implementation.
WYSISWYG transcription (computer mediated)
Conventional transcription (human mediated)
Attributes => Relationships
has manifestation
statement
has place of publication
M
Place
Nomen
C
Nomen
Timespan
Nomen
has publisher’s name
has date of publication
Publication statement
Transcribed
Recorded
Translations
RDA
Translations Policy
Translations in
RDA Registry:
German
French
Spanish
Chinese
In process (RDA Toolkit):
Finnish
Italian
In process (RDA Reference):
Arabic
Dutch
Swedish
Chinese
Semantic
Web
Local
refinement
“audio belt”: refinement to Carrier type
via RDA/ONIX Framework
Maps for machines
Local policies
National Library of Australia
Policy Statement
British Library
Policy Statement
Germany, Austria,
Switzerland
Local vocabularies
Vocabulary removed
from “global” RDA
becomes a “local”
vocabulary
Thank you
• [email protected]
• RSC website
• http://www.rda-rsc.org/
• RDA Toolkit
• http://www.rdatoolkit.org/
• RDA Registry
• http://www.rdaregistry.info/
• RDA data, Jane-athons, etc.
• http://www.rballs.info/