RDA Vocabularies in The Semantic Web by Diane Hillmann

The RDA Vocabularies
What They Are, How They Work

What We’ll be Doing Today
Sorting out some important definitions
A brief history of the RDA Vocabularies
A structural tour of the vocabularies,
including:
Rationale and decision making
General and FRBR-constrained elements
Potential for extension
Language versions of RDA Vocabularies
Important related work
Putting it all together, and shifting our focus
2 ALA TechSource Webinar:RDA May 25, 2011

What We Can’t Show You Yet
How RDA will be working in the real world
WHY?: There aren’t tools yet, and we don’t
really know what they’ll look like …
But maybe we can make some educated
guesses?
Most likely the tools will be form-based (like
the MARC tools are)
There are likely to be fewer places where
text is typed in and more where pull-down
lists are available (the benefit of
vocabularies)
The FRBR structure, if used intelligently by
3 vendors,
ALA TechSource should
Webinar:RDAsave time and money, as
May 25, 2011
re-use of data will be easier
About the RDA Vocabularies
Where we started; where we are now


A Brief History
It all started in London, the last day of April

2007
What Was Accomplished
The participants agreed that DCMI and
the Joint Steering Committee for the
Development of RDA should work
together to:
Develop an RDA Element Vocabulary
Expose RDA Value Vocabularies
Develop an RDA Application Profile,
based on FRBR and FRAD
The first two are largely complete and
under review; the third is started

Why Was This Meeting
Important?
It represented a recognition on the part
of library leaders of the importance of a
more web-focused approach
The collaboration begun at that meeting
has significantly changed the
conversation around library data
standards
We’re talking about new ways of creating
and managing data
We’re broadening our view of the role of
libraries within the larger world of
information
Our new world is collaborative, multi-lingual,
Building the Vocabularies
Decisions and reasoning


The General Strategy
lWe used the Semantic Web as our “mental
model”
lWanted to create a “bridge” between XML
and RDF to support innovation in the library
community as a whole, not just those at the
cutting edge or the trailing edge
lWe registered the FRBR entities as classes in
a ‘FRBR in RDA’ vocabulary, to enable
specific relationships between RDA
properties and FRBR
lIFLA has followed suit using the Open
Metadata Registry to add the ‘official’ FRBR
entities, FRAD, FRSAR and ISBD
ALA TechSource Webinar:RDA May 25, 2011
9 l This provides exciting opportunities to relate
Structure: Rationale &
Decisions
Property and value vocabularies are
registered in the Open Metadata Registry
(formerly the NSDL Registry):
http://metadataregistry.org/rdabrowse.htm
Used RDF Schema (RDFS), Simple
Knowledge Organisation System (SKOS)
and Web Ontology Language (OWL)
Decisions were oriented to favor approaches
that can be generalized to make other
vocabulary based standards web-friendly,
available for use in applications, and easily
updated and mapped by communities of
10 practice
The Structure, Simplified
FRBR in RDA Vocabulary declared as classes
RDA Properties declared as a ‘generalized’
vocabulary, with no explicit relationship to
FRBR entities
Subproperties for the generalized elements
include those explicitly related to FRBR
entities (using ‘domain’)
Label/Name includes (Work) or other class to
provide unique name (unless the entity
name already appears in the name of the
property)
Other generalized subproperties usable by
11 others Webinar:RDA
ALA TechSource not tied to FRBR May 25, 2011
Why Generalized Properties?
We think of the ‘generalized’ RDA properties
as the real RDA vocabulary
The ‘bounded’ properties should be seen as
the first pass at an RDA Application Profile
Extensions can be built easily from the
generalized properties
Mapping will be simpler and cleaner using
the generalized properties (since most
properties mapped to or mapped from RDA
will not be based on FRBR)
Generalized properties are much more
acceptable to non-library implementers
(not often using FRBR)

Property (Generalized, no FRBR relationship) S e m a n tic
W eb
Subproperty (with relationship to one FRBR entity)
FRBR Entity
T h e S im p le C a se :
Lib ra ry A p p lica tio n s O n e Pro p e rty --
O n e FR B R E n tity

Book format Semantic
Web
Book format (Manifestation)
Manifestation
The Simple Case:

Library One Property--
Applications One FRBR Entity

http://RDVocab.info/Elements/bookFormatManifestation

More Complex Relationships
lThere are multiple techniques used in
RDA to make the connection between
FRBR entities and RDA properties
lWe tried to reconcile those in the RDA
Vocabularies
lSome properties related to more than
one FRBR entity
lRelationships in Appendix J actually
include the name of the FRBR entity in
the name and have separate definitions
(we re-used this strategy for the FRBR-
bounded properties)
lOther properties and sub-properties
16 appearWebinar:RDA
ALA TechSource multiple times in the text and
May 25, 2011
ERDs, with the same definitions and no

Property (Generalized, no FRBR relationship) Semantic
Web
FRBR Entity
FRBR Entity
Library The Not-So-Simple Case:

Applications One Property—more than
One FRBR Entity
Extent Semantic
Web
Extent (Manifestation)
FRBR Manifestation
Extent (Item)
FRBR Item
Library The Not-So-Simple Case:

Applications One Property—more than
One FRBR Entity
Roles: Attributes or
Properties?
In 2005, the DC Usage Board worked with
LC to build a formal representation of
the MARC Relators so that these terms
could be used with DC
lThis work provided a template for the
registration of the role terms in RDA (in
Appendix I) and, by extension, the other
RDA relationships
lRole and relationship properties are
registered at the same level as
elements, rather than as attributes (as
MARC does with relators, and the RDA
Toolkit does in its XML schemas)
20 l Applications can choose either approach
Mapping,
Etc.
“Super” Property
Semantic
Subproperty (Generalized, no FRBR relationship) Web
FRBR Entity
Library The Roles Case:

Applications Properties, Subproperties
and FRBR Entities
Mapping,
Etc.
RDA:Creator
Semantic
RDArole:Composer Web
RDArole:Composer (Work)
Work
Library The Roles Case:

Applications Properties, Subproperties
and FRBR Entities
Aggregated Statements
lRDA sets up Publication, Distribution,
Manufacture and Production
statements very much the way they
have been done since catalog card
days:
lAggregation of Place, Name and
Date are obvious leftovers from
catalog cards
lWe viewed those aggregations as
‘Syntax Encoding Schemes’ (as
23
defined in the Dublin Core Abstract
Model)
Pre-coordinated Statements: Structure
Aggregated Statement (no domain or range)
Domain: FRBR Entity

Aggregated Statement Subproperty
Range: RDA Syntax Encoding Scheme (Subclass of RDF Datatype)
Range: [Specific] Encoding Scheme (Subclass)
General Property (no domain or range)
Subproperty
Option 1
Pre-coordinated Statements: Example
Publication Statement (no domain or range)
Domain: Manifestation
Publication Statement (Manifestation)
Range: RDA Syntax Encoding Scheme (Subclass of RDF Datatype)
Range: Publication Statement Encoding Scheme (Subclass)
Place of publication (no domain or range)
Place of publication (Manifestation)

Option 1
Time for Questions?

Why This Works
How do we take full advantage of
the RDA Vocabulary infrastructure?
Relationships between properties is
built-in, allowing ‘bottom up’
aggregation of data
Repeating the property relationships
in ‘nested’ schemas is redundant
Tools to enable easier data creation
(with machine assistance) are critical
Humans using these tools will have
access to the structure but need not
know all the details
ID=
234
5 6 h
asE
Statements on the Floor?
dit
ion ID
Sta =2
tem
ent 34
“1 st 56
tra ha
7 d e sP
e “1 9 8 ” e dit ub
i o n Da t i o li
b l ic a t n ” sh
h as P u er
4 56 ”
ID=23 s h “De
la
g li co En g lish”
guratege
n “
“E a lL an
o n
6 h a sOrigin Pr
es
s i D 23 4 5
e s I = s”
r ID=
E xp 23
O f 45
e
ID=23456 hasAuthor u a“Kurt Vonnegut” 6 ha
g
ang sP
la
s L ce
ha ID=23456 isFormOfWork Of
Pu “Novel”
ID=2 45 6 bl
324356 ic
= h a sPref at
ID e rredT io
itle n
“Ne
“Blue w
beard Yo
, a n rk
ovel” ”
Is This Really
Chaos?
ID=
234
5 6 h
asE
dit
ion
Sta
tem ID ID
ent = =2
“1 st 23 34
tra 45 56
d e 6 ha
ID=23456 hasAuthor “KurtatVonnegut e “ 1987 ” edihtas
”
sP
a t i o n D ioPnl ub
P u bl ic s h ””ac li
h as g l i e sh“Novel”
D 2 3456 i oID
n “
= n
E23456 Of
isFormOfWork
P er
I =
x p r e s s u b “ En g lish”
g u a g eOfE li
c l L an g uaDeglea “
ID=2
3 46 h a sLan h a s Originaatio co
rt
D 2 3 45 56 ha D 23 4 56 n e
I = sPref I = “Ne Pr
erred w es
Title Yo s”
“Blue rk
beard ”
29 ALA TechSource Webinar:RDA , a n May 25, 2011
ovel”
ID=23456 hasAuthor “Kurt Vonnegut”
Or an Aggregation
ID=
In the Making?
234
5 6 h
asE
dit
ion
Sta
tem ID ID
ent = =2
“1 st 23 34
tra 45 56
d e 6 ha
te “ 1 987 ” ediha
t sP
a t i o n Da isoPnl ub
D 2 3456 i oID
n “
= n
E23456 Of
isFormOfWork
P er
I =
g u a g eOfE li
ID=2
3 46 h a sLan h a s Originaatio co
rt
D 2 3 45 56 ha D 23 4 56 n e
I = sPref I = “Ne Pr
erred w es
Title Yo s”
“Blue rk
beard ”
30 ALA TechSource Webinar:RDA , a n May 25, 2011
ovel”
ID=23456 hasPreferredTitle “Bluebeard, a novel”
ID=
234
5 6 h
asE
dit
ion
Sta
tem ID ID
ent = =2
“1 st 23 34
tra 45 56
d e 6 ha
te “ 1 987 ” ediha
t sP
a t i o n Da isoPnl ub
D 2 3456 i oID
n “
= n
E23456 Of
isFormOfWork
P er
I =
g u a g eOfE li
6 h a sLan h a s Originaatio co
rt
D 2 3 45 D 23 4 56 n e
I = I = “Ne Pr
w es
Yo s”
rk
”
ID=23456 hasOriginalLanguage “English”

ID=
234
5 6 h
asE
dit
ion
Sta
tem ID ID
ent = =2
“1 st 23 34
tra 45 56
d e 6 ha
te “ 1 987 ” ediha
t sP
a ti o n Da isoPnl ub
P u b l ic s h ””ac li
D = 2 3456 i oID
n “
= n
E23456 Of
isFormOfWork
P er
I e s s u
a g e OfExpr bl
i c
“De
la
s L an gu at co
6 h a io rt
D = 2 3 45 n e
I “Ne Pr
w es
Yo s”
rk
”
ID=23456 isFormOfWork “Novel”

ID ID
= =2
ID= 23 34
234 45 56
56 6 ha
has t e “ 1 987 ” ha sP
Edi Da sP
tiPoublication hl”a c
ub
li
h as n S t g l is e sh
D 2 3456 ate
m o n “ En Of
P er
I = ent pressi u bl
a g e OfE“1xst i c
“De
la
s L an gu tra at co
6 h a de io rt
D 2 3 45 edi n e
I = tio “ N Pr
n” ew es
Yo s”
rk
”
Work
ID=23456 isFormOfWork “Novel”

ID ID
= =2
ID= 23 34
234 45 56
56 6 ha
has t e “ 1 987 ” ha sP
Edi Da sP
tiPoublication hl” ac
ub
li
h as n S t g l is e sh
D 2 3456 ate
m o n “ En Of
P er
I = ent pressi u bl
a g e OfE“1xst ic
“De
la
s L an gu tra at co
6 h a de io rt
D 2 3 45 edi n e
I = tio “ N Pr
n” ew es
Yo s”
rk
”
ID=23456 hasLanguageOfExpression “English”
ID ID
= =2
ID= 23 34
234 45 56
56 6 ha
has te “ 1 987 ” ha sP
Edi Da sP
tiPoublication la
c
ub
li
h as nS t e sh
D = 2 3456 ate
m
Of
P er
I ent ub “De
“1 st li la
tra cat co
de io rt
edi n e
tio “ N Pr
n” ew es
Yo s”
rk
”
ID=23456 hasLanguageOfExpression “English”
Expression
ID= ID ID
234 = =2
56 234 34
has 56 56
Edi 1 987 ” ha ha
tio n Da t e “ sP sP
n ic a ti o l ub
as PuSb
tla ac li
3456 h t eme e Of sh
ID = 2 nt P er
“1 st u bl “De
ic la
tra at co
de io rt
edi n e
tio “Ne Pr
n” w es
Yo s”
rk
”
ID=23456 hasPublicationDate “1987”
ID= ID ID
234 =2 =2
56 34 34
has 56 56
Edi ha ha
tio sP sP
nSt la ub
ate ce li
men Of sh
Pu er
t “ bl “De
1 st ic la
tra at co
de io rt
edi n e
tio “Ne Pr
n” w es
Yo s”
rk
”
=23456 hasEditionStatement “1st trade edition”
ID ID
=2 =2
34 34
56 56
ha ha
sP sP
la ub
ce li
Of sh
Pu er
bl “De
ic la
at co
io rt
n e
“Ne Pr
w es
Yo s”
rk
”
ID=23456 hasPublisher “Delacorte Press”
ID
=2
34
56
ha
sP
la
ce
Of
Pu
bl
ic
at
io
n
“Ne
w
Yo
rk
”

Manifestation
ID=23456 hasPublisher “Delacorte Press”
ID=23456 hasPlaceOfPublication “New York”

that Edition Statement is a Manifestation Property
Edition
Statement
Edition Statement (Manifestation)

R e la tio n sh ip d e fin e d h e re

Extension
The inclusion of generalized properties
provides a path for extension of RDA into
specialized library communities and non-
library communities
They may have a different notion of how
FRBR ‘aggregates’
For example, a colorized version of a film
may be viewed as a separate work
They may not wish to use FRBR at all
They may have additional properties to
include, that have a relationship to the
RDA properties
This allows other communities to use
this data without problems
R D A : a d a p te d A s
ha
y sSu
bp
ro
pe
rt
R D A : a d a p te d A sA R a d io S crip t

hasSu
R D A : a d a p te d A s y bprop
ert
ha
y
sS
ub
pr
op
er
t
K id Lit: a d a p te d A sA Pictu re B o o k

hasSu
R D A : a d a p te d A s y bprop
ert
ha
y
sS
ub
pr
has
y
op
er
Sub
t
pro
per
K id Lit: a d a p te d A sA Pictu re B o o k
t
KidLit:adaptedAsAChapterBook

What Does This Structure Buy
Us?
Release from the tyranny of records
Potential for use with a variety of
encodings
Ability to maintain statements at a
more granular level
Opportunity to re-think how we build,
maintain and share data
Potential for sharing data beyond the
library silo
A challenge to our old notions of what
library data can do and should be doing

What We’ve Learned
We wrote about the decisions we made
for RDA in DLib Magazine:
http://dlib.org/dlib/january10/hillmann/01hillmann.
We need to continue to disclose what
we’ve learned and work on building
best practices documentation in this
environment
We need research and innovation to help
us move forward!
Review by JSC is in process, and
announcements will be made when
49 vocabularies are ‘published’
What About
Internationalization?
And other library vocabularies?


Multi-Lingual RDA
Registered elements and vocabularies
can include multiple languages
The Open Metadata Registry has been
working with the Deutsche
Nationalbibliothek to demonstrate this
with German translations in the OMR
Other language versions being discussed
with national libraries and language groups
by ALA Publishing in conjunction with
translations of RDA guidance text
OMR enhancements are planned to
51
make building of language versions
easier
Important Related Work: IFLA
“Functional Requirements” family or
“FRBR family of models”:
FRBR, 1998: Bibliographic Records [data]
FRAD, 2009: Authority Data
FRSAD, 2010: Subject Authority Data
Consolidated model in development
RDF/XML representation of the consolidated
edition of ISBD in development
Relating FR, ISBD and RDA, SKOS, FOAF, etc.

FR in RDF
Representation of FRBRer model element set
is mainly complete
Classes and properties have “approved”
status
FRAD and FRSAD close behind
Representation in Resource Description
Framework Schema (RDFS) is informing
work on combining and consolidating the
model family
Also supplies “learning curve” for Semantic
Web environment
FRBR is a conceptual model built on the E-R
methodology which is intrinsically
54
applicable to representation in RDF, May
ALA TechSource Webinar:RDA while
25, 2011
ISBD is a data standard
RDA
p ro p e rtie s
E xte n
t
E xte n t E xte n t o f textE xte n t o f stillim a g e E xte n t ( I/)

( M /)
E xte n t o f te xt E xte n t o f text ( I/)E xte n t o f stillim a g e ( I/)E xte n t o f stillim a g e ( M /)

( M /)
La b e l S u b p ro p e r
( Domain / Range ) ty

R D A / IFLA p ro p e rtie s ( m in im a l
lin ka g e )
E xte n has
t exte n t
h a s exte n t
( R /)
h a s exte n t o f th e ca rrie r
E xte n t o f te xt E xte n t h a s exte n t o f th e ca rrie r ( M /)

( M /)
N o te : M a n ife sta tio n su b -cla ss- o f

R e so u rce
E xte n t o f te xt
( M /)
FR B R lite IS B D lite
S u b p ro p e r Sam e
La b e l RD FR B IS B
ty As
( Domain / Range ) A R D

R D A / IFLA p ro p e rtie s ( m a xim u m
lin ka g e )
E xte n has
t exte n t
h a s exte n t
( R /)
h a s exte n t o f th e ca rrie r

( M /)
E xte n t o f te xt
( M /)
RD FR B IS B
A R D
La b e l S u b p ro p e r Sam e FR B R lite IS B D lite
( Domain / Range ) ty As
R D A / IFLA / o th e r p ro p e rtie s ( m in im a l
lin ka g e )
fo rm a
t
E xte n has
t exte n t E xte n t
h a s exte n t o f th e ca rrie r (/ S )
h a s exte n t
( R /)
( M /)
E xte n t o f te xt
( M /)
n u m Pa g e s n u m V o lu m e s
( D / l) ( C / l)
a sse s: M a n ife sta tio n , R e so u rce , C o lle ctio n , D o cu m e n t, S ize O rD u ra tio n , N o te : D o cu m e n t su b -cla ss- o f
e ra l R e so u rce
S u b p ro p e r Sam e
La b e l ty As RD FR B IS B DC B IB
( Domain / Range ) A R D T O
58 ALA TechSource Webinar:RDA D FR B R lite IS B D lite May 25, 2011
C
Clearing Up Some Confusion
…
What we are (and aren’t) talking about …


The XML Model of ‘the World’
XML assumes a 'closed' world
(domain), usually defined by an
XML schema:
"We know all of the data describing
this resource. The single description
must be a valid document according
to our schema. The data must be
valid.”
XML's document model provides
a neat equivalence to a
60
metadata 'record’

The RDF Model of ‘the World’
RDF (Resource Description
Framework, language of the Semantic
Web) assumes an 'open' world:
"There's an infinite amount of unknown data
describing this resource yet to be
discovered. It will come from an infinite
number of providers. There will be an
infinite number of descriptions. Those
descriptions must be consistent."
RDF's statement-oriented data
model has no notion of 'record’
(rather, statements can be
aggregated for a fuller description
In Both, We Talk About
Statements
In XML these are ‘attribute/value pairs’
Where, in the context of a bounded record
structure we know what we’re describing
(there’s an identifier of some kind in the
record telling us we’re describing
‘Huckleberry Finn’)
Ex.: Author = Twain, Mark
In RDF, these are independent statements,
in the form of ‘triples’:
Ex.: The author of Huckleberry Finn is Mark
Twain, or
Subject = Huckeberry Finn
Predicate = hasAuthor
Object = Mark Twain
Shifting the Way We Think
We need to see ourselves as data
consumers and data providers in a
much wider world
Our thinking about how we build
and share data needs to reflect
modern ideas about data creation
and use
‘Records’ are aggregations of
information, not units
Our new tools may continue to look
63 like we’re
ALA TechSource creating ‘records’ but
Webinar:RDA Maythey
25, 2011
The Old World
V e n d o r R e co rd s
O C LC
C a ta lo g
Human-based Updates
S p e cia l C o lle ctio n s

The Newer World V e n d o r R e co rd s
User
Interface(s)
Web
Lib ra ry D a ta Data
O C LC
Human-based Updates
S p e cia l C o lle ctio n s
Data
Services
What Are Data Services?
D a ta Data Improvement Services

S e rvice s
Ex.: Match text versions of names with URIs

Ex.: Transform MARC records to RDA
Ex.: Fix date formats

D a ta Harvesting/Distribution Service
S e rvice s
Ex.: Routinely harvest new statements from

approved sources
Ex.: Expose new human and service created
for use by other services

D a ta Indexing Services
S e rvice s
Ex.: Index full text resources for combined

metadata/text search
Ex.: Support specialized filtering

D a ta Mapping Services
S e rvice s
Ex.: Provide extended search/browse across forma

using a variety of property and value maps
Ex.: Support creation and maintenance of mappin
and relationships

The Big WHY?
What are the implications of these changes in the

way we see our world?

What Does This Imply for Us?
We need to expand our ideas of what
machines can and should do for us, and
how to share the load
We need to articulate better what we, as
humans, bring to the table (and stop
thinking we need to control it ALL)
We need to educate ourselves about this
new world we live in (what it is and
isn’t)
We need to understand enough to work
with our vendors to make it happen in
71 our libraries
Friendlier Information for Humans?

The World is Waking Up …
LCCN
VIAF
SELIBR

And Beginning to Understand
…

Who’s Doing This?
 OCLC
Creating persistent URIs for VIAF authority
records, so that the can be linked from places
like Wikipedia
Extracting data from Wikipedia and attempting
to match data with information already in VIAF
(or potential candidates)
Thinking about working with Wikipedia to supply
more VIAF and WorldCat Identities links to
them
 Library of Congress
The Linkypedia pages (and RSS feed) were
created by Ed Summers, an LC staffer
Talking about replacing MARC:
http://www.loc.gov/marc/transition/news/framework
76 .html Webinar:RDA
ALA TechSource May 25, 2011
More Questions?

Links and Contact Info
DCMI/RDA Task Group Wiki:
http://dublincore.org/dcmirdataskgroup/
RDA Vocabularies:
http://metadataregistry.org/rdabrowse.htm
Diane: metadata.maven@gmail.com

Slides on IFLA Vocabularies by Gordon

Dunsire
Flickr images thanks to: Trois TÃªtes (TT),
Craft*ology


RDA Vocabularies in The Semantic Web by Diane Hillmann

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RDA Vocabularies in The Semantic Web by Diane Hillmann

Uploaded by

Copyright:

Available Formats

The RDA Vocabularies

What They Are, How They Work

2 ALA TechSource Webinar:RDA May 25, 2011

4 ALA TechSource Webinar:RDA May 25, 2011

6 ALA TechSource Webinar:RDA May 25, 2011

8 ALA TechSource Webinar:RDA May 25, 2011

Subproperty (with relationship to one FRBR entity)

13 ALA TechSource Webinar:RDA May 25, 2011

Book format (Manifestation)

The Simple Case:

14 ALA TechSource Webinar:RDA May 25, 2011

15 ALA TechSource Webinar:RDA May 25, 2011

ERDs, with the same definitions and no

Subproperty (with relationship to one FRBR entity)

Subproperty (with relationship to one FRBR entity)

Library The Not-So-Simple Case:

Library The Not-So-Simple Case:

Subproperty (with relationship to one FRBR entity)

Library The Roles Case:

Library The Roles Case:

Aggregated Statement (no domain or range)

Domain: FRBR Entity

Range: RDA Syntax Encoding Scheme (Subclass of RDF Datatype)

Range: [Specific] Encoding Scheme (Subclass)

General Property (no domain or range)

Publication Statement (no domain or range)

Range: RDA Syntax Encoding Scheme (Subclass of RDF Datatype)

Range: Publication Statement Encoding Scheme (Subclass)

Place of publication (no domain or range)

Place of publication (Manifestation)

26 ALA TechSource Webinar:RDA May 25, 2011

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 hasOriginalLanguage “English”

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 hasOriginalLanguage “English”

ID=23456 isFormOfWork “Novel”

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 isFormOfWork “Novel”

=23456 hasEditionStatement “1st trade edition”

=23456 hasEditionStatement “1st trade edition”

ID=23456 hasPublisher “Delacorte Press”

=23456 hasEditionStatement “1st trade edition”

ID=23456 hasPlaceOfPublication “New York”

40 ALA TechSource Webinar:RDA May 25, 2011

Edition Statement (Manifestation)

41 ALA TechSource Webinar:RDA May 25, 2011

43 ALA TechSource Webinar:RDA May 25, 2011

45 ALA TechSource Webinar:RDA May 25, 2011

46 ALA TechSource Webinar:RDA May 25, 2011

47 ALA TechSource Webinar:RDA May 25, 2011

50 ALA TechSource Webinar:RDA May 25, 2011

53 ALA TechSource Webinar:RDA May 25, 2011

E xte n t E xte n t o f textE xte n t o f stillim a g e E xte n t ( I/)

E xte n t o f te xt E xte n t o f text ( I/)E xte n t o f stillim a g e ( I/)E xte n t o f stillim a g e ( M /)

55 ALA TechSource Webinar:RDA May 25, 2011

E xte n t o f te xt E xte n t h a s exte n t o f th e ca rrie r ( M /)

N o te : M a n ife sta tio n su b -cla ss- o f

56 ALA TechSource Webinar:RDA May 25, 2011

E xte n t o f te xt E xte n t h a s exte n t o f th e ca rrie r ( M /)

59 ALA TechSource Webinar:RDA May 25, 2011

64 ALA TechSource Webinar:RDA May 25, 2011

D a ta Data Improvement Services