The document discusses moving away from traditional library data models based on catalog records towards a model using semantic web standards. It envisions describing resources with statements about properties and values linked by URIs, rather than constrained data elements within records. This allows for more flexible aggregation of descriptive data from various sources to describe resources in different ways. An example shows how bibliographic data could be broken into simple statements that could then be reassembled in various meaningful descriptions.

1. Getting from Here to ThereAnd where is ‘There’ exactly, Anyway?

2. What Does ‘There’ Look LikeNot like catalog cardsNot MARC recordsNot necessarily ‘records’ at allNot entirely our dataData sharing, but probably not with a center pointMore open, less constrained by old assumptions about functionalityIncludes more collaborators outside the library silo7/13/10AALL 2010 Denver2

3. Standards Upgrade!7/13/103AALL 2010 Denver

4. Why RDA?RDA is a FRBR-based approach to structuring bibliographic dataIt contains more explicitly machine-friendly linkages (preferably with URIs)There’s more emphasis on relationships and roles …… and less emphasis on cataloger-created notes and text strings (particularly for identification)Less emphasis on transcription (important in an increasingly digital world) 7/13/104AALL 2010 Denver

5. RDA & FRBR: Registered!RDA WEMI Elements: http://metadataregistry.org/schema/show/id/1.htmlRDA Roles:http://metadataregistry.org/schema/show/id/4.htmlRDA Vocabulary: Base Materialhttp://metadataregistry.org/vocabulary/show/id/35.htmlFRBRer Modelhttp://metadataregistry.org/schemaprop/list/schema_id/5.html7/13/105AALL 2010 Denver

6. Who’s Doing This?DCMI/RDA Task GroupSee: http://dublincore.org/dcmirdataskgroup/Set up during the April 2007 London meeting between JSC and DCMIGordon Dunsire and Diane Hillmann, co-chairsKaren Coyle & Alistair Miles, consultantsIFLA Classification and Indexing SectionGordon Dunsire, Centre for Digital Library Research, University of Strathclyde, registering FRBR entities and relationships, FRAD, ISBD, etc.7/13/106AALL 2010 Denver

7. Walking through a concrete example …From the Cataloger Scenarios7/13/10AALL 2010 Denver7

8. Jane Cataloger is assigned to work on a gift collection. Her first selection is a Latvian translation of Kurt Vonnegut's "Bluebeard: a novel." She searches the library database for the original work, and finds:*Author: Kurt Vonnegut *Title of the work: Bluebeard: a novel *Form of work: Novel *Original language of the work: English87/13/10AALL 2010 DenverA Cataloger Scenario

9. 7/13/10AALL 2010 Denver9Translated to RDA/XML:<frbrWork ID="rda.basic/01”> <rdarole:author>Kurt Vonnegut</rdarole:author> <titleOfTheWork>Bluebeard: a novel</titleOfTheWork> <formOfWork>Novel</formOfWork> <originalLanguageOfTheWork>English<originalLanguageOfTheWork></frbrWork>Upgraded to RDA/XML with Links:<frbrWork ID="rda.basic/01”> <rdarole:author>http://lcnaf.info/79062641</rdarole:author> <titleOfTheWork>Bluebeard: a novel</titleOfTheWork> <formOfWork>http://RDVocab.info/genre/1008</formOfWork> <originalLanguageOfTheWork>http://marclang.info/eng </></frbrWork>

10. 7/13/10AALL 2010 Denver10with links to the following expression information:*Language of expression: English *Content type: Textand one manifestation:*Statement designating edition: 1st trade edition *Place of publication: New York *Publisher’s name: Delacorte Press *Date of publication: 1987 *Extent of text: 300 pages *Identifier for the manifestation: [ISBN]0385295901

11. 7/13/10AALL 2010 Denver11Translated to RDA/XML:<frbrExpression ID="rda.basic/07”> <contentType>Text</contentType> <languageOfExpression>English<languageOfExpression></frbrExpression>Upgraded to RDA/XML with Links:<frbrExpression ID="rda.basic/07”><formOfWork>http://RDVocab.info/termList/RDAContentType/1020</> <languageOfExpression>http://marclang.info/eng </></frbrExpression>

12. 7/13/10AALL 2010 Denver12Translated to RDA/XML (with links below):<frbrManifestation ID="rda.basic/09”> <statementDesignatingEdition>1st Trade Edition</> <placeOfPublication>New York<placeOfPublication> <publishersName>Delacorte Press</publishersName> <dateOfPublication>1987</dateOfPublication> <extentOfText>300 pages</extentOfText> <identifierForTheManifestation>[ISBN]0385295901</></frbrManifestation><frbrManifestatiion ID="rda.basic/09”><statementDesignatingEdition>1st Trade Edition</> <placeOfPublication>http://www.getty.edu/tgn/7007567</> <publishersName>http://onixpub.info/2039987</> <dateOfPublication>1987</dateOfPublication> <extentOfText>300 pages</extentOfText> <identifierForTheManifestation>urn:ISBN:0385295901</></frbrManifestation>

13. 7/13/10AALL 2010 Denver13FRBR Group 1WorkExp: engMan: eng

14. 7/13/10AALL 2010 Denver14Jane begins her description by linking to the existing Work entity. She then creates an expression description:*Content type: text*Language of expression: Latvian*Translator:Grigulis, ArvīdsShe creates an authority record for the translator since none yet existed. She continues by creating a fuller description for the new manifestation, linking to the authority record for the Latvian publisher (what luck, it already existed!).*Title: [in Latvian]*Place of publication: Riga*Publisher’s name: Liesma*Date of publication: 1997*Extent of Text: 315 pages

15. 7/13/10AALL 2010 Denver15Translated to RDA/XML:<frbrExpression ID="rda.basic/11”> <contentType>text</contentType> <languageOfExpression>Latvian<languageOfExpression> <rdarole:translator>Grigulis, Arvīds</rdarole:translator></frbrExpression>Upgraded to RDA/XML with Links:<frbrExpression ID="rda.basic/11”><formOfWork>http://RDVocab.info/termList/RDAContentType/1020</> <languageOfExpression>http://marclang.info/lav</> <rdarole:translator>http://lcnaf.info/83219993 </frbrExpression>

16. 7/13/10AALL 2010 Denver16Translated to RDA/XML (with links below):<frbrManifestation ID="rda.basic/09”> <title>[in Latvian]</> <placeOfPublication>Riga<placeOfPublication> <publishersName>Liesma</publishersName> <dateOfPublication>1997</dateOfPublication> <extentOfText>315 pages</extentOfText></frbrManifestation><frbrManifestatiion ID="rda.basic/09”><placeOfPublication>http://www.getty.edu/tgn/7006484</> <publishersName>http://onixpub.info/6770094</> <dateOfPublication>1997</dateOfPublication> <extentOfText>315 pages</extentOfText></frbrManifestation>

17. 7/13/10AALL 2010 Denver17FRBR Group 1WorkExp: engExp: lavMan: engMan: lav

18. 7/13/10AALL 2010 Denver18FRBR Group 2FRBR Group 1WorkAuthorTranslatorPublisherExp: engExp: lavMan: engMan: lav

19. 7/13/10AALL 2010 Denver19FRBR Group 2FRBR Group 1WorkAuthorTranslatorExp: engExp: lavPublisherFRBR Group 3ConceptsObjectsEventsPlacesMan: engMan: lavSubjects

20. 7/13/10AALL 2010 Denver20FRBR Group 2FRBR Group 1WorkAuthorTranslatorExp: engExp: lavPublisherFRBR Group 3ConceptsObjectsEventsPlacesMan: engMan: lavSubjectsRelationshipVocabulariesContent VocabulariesOther InformationIn the “Cloud”Media Vocabularies

21. Can Standards Help?Not Necessarily Library Standards …7/13/10AALL 2010 Denver21

22. Semantic Web StandardsRDF: Resource Description FrameworkStatements about Web resources in the form of subject-predicate-object expressions, called triplesE.g. “This presentation” –“has creator” –“Diane Hillmann”RDF SchemaVocabulary description language of RDFSKOS: Simple Knowledge Organisation SystemExpresses the basic structure and content of concept schemes such as thesauri and other types of controlled vocabulariesAn RDF applicationOWL (Web Ontology Language)Explicitly represents the meaning of terms in vocabularies and the relationships between them7/13/1022AALL 2010 Denver

23. Semantic Web Building BlocksEach component of an RDF statement (triple) is a “resource”RDF is about making machine-processable statements, requiringA machine-processable language for representing RDF statementsExtensible Markup Language (XML) A system of machine-processable identifiers for resources (subjects, predicates, objects)Uniform Resource Identifier (URI) For full machine-processing potential, an RDF statement is a set of three URIs7/13/1023AALL 2010 Denver

24. Things Requiring IdentificationObject “This presentation”e.g. its electronic location (URL)Predicate “has creator”e.g. http://purl.org/dc/terms/creatorObject “Diane Hillmann”One option: URI of entry in Library of Congress Name Authority File (real soon now?)NAF: nr2001015786Declaring vocabularies/values in SKOS and OWL provides URIs—essential for the Semantic Web7/13/1024AALL 2010 Denver

25. Examining RDA GeneticsRDA’s model is primarily FRBR and FRAD, but also takes some of its DNA from Dublin CoreDC’s Abstract Model de-composes traditional metadata “records” and re-composes them with additional levels above and below what we’ve traditionally thought of as our “atomic level”The DCAM also talks about “statements” in ways that help connect RDA to the Semantic Web7/13/10AALL 2010 Denver25

26. 7/13/10AALL 2010 Denver26A Dublin Core View of the WorldDCMI Abstract Model: http://dublincore.org/documents/abstract-model/

27. 7/13/10AALL 2010 Denver27A Dublin Core View of the WorldDCMI Abstract Model: http://dublincore.org/documents/abstract-model/

28. 7/13/10AALL 2010 Denver28Anatomy of a StatementPropertyValuePlace of Production: New YorkValueString

29. 7/13/10AALL 2010 Denver29Anatomy of a StatementPropertyValuePlace of Production: http://www.getty.edu/tgn/7007567RelatedDescription

30. 7/13/10AALL 2010 Denver30Description Sets a Key Concept!

31. Description Set=“A set of one or more descriptions, each of which describes a single resource.”*31*DCAM Definition7/13/10AALL 2010 Denver

32. A Different StrategyWhat Happens When We Give Up the Record as Our Basic Unit?7/13/10AALL 2010 Denver32

33. Our View of the Internet, 1995“The turning point for the World Wide Web was the introduction[4] of the Mosaic web browser[5] in 1993, a graphical browser developed by a team at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign (UIUC), led by Marc Andreessen.” -- Wikipedia7/13/10AALL 2010 Denver33

34. What Would Happen If …We stopped thinking about our data as ‘records’Instead, we started thinking of our data as ‘statements’We started thinking of these statements as able to be aggregated in a variety of ways, for a variety of purposesIncluding sharing with others, both within the library and beyondWhat would that look like?7/13/10AALL 2010 Denver34

35. 7/13/10AALL 2010 Denver35Statements on the Floor?ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPublicationDate “1987”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasOriginalLanguage “English”ID=23456 hasLanguageOfExpression “English”ID=23456 hasAuthor “Kurt Vonnegut”ID=23456 isFormOfWork “Novel”ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasPreferredTitle “Bluebeard, a novel”

36. 7/13/10AALL 2010 Denver36Is This Really Chaos?ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasAuthor “Kurt Vonnegut”ID=23456 hasPublicationDate “1987”ID=23456 isFormOfWork “Novel”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasLanguageOfExpression “English”ID=23456 hasOriginalLanguage “English”ID=23456 hasPreferredTitle “Bluebeard, a novel”

37. 7/13/10AALL 2010 Denver37ID=23456 hasAuthor “Kurt Vonnegut”Or Just an AggregationIn the Making?ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPublicationDate “1987”ID=23456 isFormOfWork “Novel”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasLanguageOfExpression “English”ID=23456 hasOriginalLanguage “English”ID=23456 hasPreferredTitle “Bluebeard, a novel”

38. 7/13/10AALL 2010 Denver38ID=23456 hasAuthor “Kurt Vonnegut”ID=23456 hasPreferredTitle “Bluebeard, a novel”ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPublicationDate “1987”ID=23456 isFormOfWork “Novel”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasLanguageOfExpression “English”ID=23456 hasOriginalLanguage “English”

39. 7/13/10AALL 2010 Denver39ID=23456 hasAuthor “Kurt Vonnegut”ID=23456 hasPreferredTitle “Bluebeard, a novel”ID=23456 hasOriginalLanguage “English”ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPublicationDate “1987”ID=23456 isFormOfWork “Novel”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasLanguageOfExpression “English”

40. 7/13/10AALL 2010 Denver40ID=23456 hasAuthor “Kurt Vonnegut”ID=23456 hasPreferredTitle “Bluebeard, a novel”ID=23456 hasOriginalLanguage “English”ID=23456 isFormOfWork “Novel”ID=23456 hasPublicationDate “1987”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasLanguageOfExpression “English”

41. 7/13/10AALL 2010 Denver41ID=23456 hasAuthor “Kurt Vonnegut”ID=23456 hasPreferredTitle “Bluebeard, a novel”WorkID=23456 hasOriginalLanguage “English”ID=23456 isFormOfWork “Novel”ID=23456 hasPublicationDate “1987”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasLanguageOfExpression “English”

42. 7/13/10AALL 2010 Denver42ID=23456 hasLanguageOfExpression “English”ID=23456 hasPublicationDate “1987”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPlaceOfPublication “New Yorkl”

43. 7/13/10AALL 2010 Denver43ID=23456 hasLanguageOfExpression “English”ID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPublicationDate “1987”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPlaceOfPublication “New Yorkl”

44. 7/13/10AALL 2010 Denver44ID=23456 hasLanguageOfExpression “English”ExpressionID=23456 hasStatementOfEdition “1st trade edition”ID=23456 hasPublicationDate “1987”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPlaceOfPublication “New Yorkl”

45. 7/13/10AALL 2010 Denver45ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasPublicationDate “1987”ID=23456 hasPublisher “Delacorte Press”

46. 7/13/10AALL 2010 Denver46ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPublicationDate “1987”

47. 7/13/10AALL 2010 Denver47ID=23456 hasPlaceOfPublication “New Yorkl”ID=23456 hasPublisher “Delacorte Press”ID=23456 hasPublicationDate “1987”

48. 7/13/10AALL 2010 Denver48ID=23456 hasPlaceOfPublication “New Yorkl”ManifestationID=23456 hasPublisher “Delacorte Press”ID=23456 hasPublicationDate “1987”

49. Extensible PotentialBecause of the way the RDA Vocabularies are built, specialized communities can extend them in ways that support (not break) interoperabilityThe aggregation of statements into FRBR ‘packages’ could be done in a completely different way to suit a particular community's needs without losing interoperabilityThis is an entirely different way of thinking about data:It doesn’t require up-front consensusIt doesn’t imply losers and winners when needs conflictIt sets communities free to build interoperable data on their own terms7/13/10AALL 2010 Denver49

50. Yet More ChallengesWe need application profiles that express more than one notion of “Work” and more than one communitypoint of view JSC still seeing the process through the lens of a text cataloger The law library community (and others) have many unmet needs with the current RDAMoving the MARC legacy data into RDAOCLC has yet to reveal any details about their planningThe eXtensible Catalog Project has a running start on thisMulti-lingual and specialized extensionsNon-Anglo-American communities eager to participate7/13/1050AALL 2010 Denver

51. Multi-lingual RDAThe Registry approach:Translations of labels, definitions and comments reside within the save vocabulary, with separate language attributesURIs stay the same, as do relationshipsResponsibility for updating translations rests with translation “owner”—who is enabled as a maintainer in the main vocabularyRequires a “web of trust” and organizational commitmentSo far, seems to have support from JSC and ALA Publishing7/13/10AALL 2010 Denver51

52. Some Questions (not answers)If we base our notions of aggregation on FRBR, does that imply that we exchange data as FRBR WEMI packages?Do those packages include all four levels, or one level only?How will we manage the identity of these packages? Identity is key to making sharing work wellWill we need to manage these statements as aggregates?How will we continually upgrade and add data to these aggregations? 7/13/10AALL 2010 Denver52

53. The BIG Questions RemainingWhat do we anticipate will be different about our changed working environment?How will workflow change?How will the data look?What will the library vendor systems do with it?How will we integrate user data? What kinds of user data?What do we need to know to operate in this new environment?7/13/10AALL 2010 Denver53

54. Thanks & AcknowledgementsThanks for your attention!Slides will be available on Slideshare: http://slideshare.net/smartbroad/Contact for Diane:Email: metadata.maven@gmail.comWebsite: http://managemetadata.com/7/13/1054AALL 2010 Denver