From Legacy Data to Linked Data: Preparing Libraries for Web 3.0. Presented at ALA Annual, Monday, June 13th, 8:00-10:00 AM Session blurb: "How can library cataloging data be transformed to function within “Web 3.0” and be understood by non-library web applications? Speakers from both the library and Semantic Web communities will explore the situation in a non-technical manner and describe current work underway to transform legacy library data into linked data.

1. Are Libraries Ready for Linked Data? A not-too-technical look at the question at hand … Diane I. Hillmann Information Institute of Syracuse/ Metadata Management Associates

2. To Re-phrase the question … If “linked data” is about relationships … And we’re done (pretty much) with expressing relationships using textual notes (as we have done for decades—nay, CENTURIES—first on catalog cards, then using AACR and MARC) And we understand that we need machine-based methods to really do the job well … THEN … 7/13/09 2 ALA Annual: Linked Data Program

3. We’re READY! 7/13/09 3 ALA Annual: Linked Data Program

4. Getting Real--Defining READY Availability of schemas and vocabularies RDA is full of relationships, from the FRBR model to the extensive relationship vocabularies currently registered and near completion Availability of applications and tools that can help us use linked data Started, certainly, but not entirely there yet [Jennifer will talk a bit about this part] 7/13/09 4 ALA Annual: Linked Data Program

5. Starting at the Grass Level 7/13/09 5 ALA Annual: Linked Data Program

6. What’s All This About Triples? In traditional cataloging, you get attribute/value pairs: Title = Bluebeard Author = Vonnegut, Kurt And you know what the object of the statements are because they’re part of a RECORD 7/13/09 6 ALA Annual: Linked Data Program

7. What’s All This About Triples? In traditional cataloging, you get a record package, with an ID: Title = Bluebeard Author = Vonnegut, Kurt The record is identifiable and shareable, but the statements within that package cannot stand alone Record ID=abc12345 7/13/09 7 ALA Annual: Linked Data Program

8. Person Book Has Author You’ve seen this before … 7/13/09 8 ALA Annual: Linked Data Program

9. Book Person Has Author Has Name Has Title Vonnegut, Kurt Bluebeard And this … 7/13/09 9 ALA Annual: Linked Data Program

10. Object & Agent Have Identifiers Book Person Has Author Relationships Have Identifiers Has Name Has Title Vonnegut, Kurt Bluebeard Identifiers are critical for Linked Data! Libraries are used to providing identifiers for Agents and Objects, but not for Relationships 7/13/09 10 ALA Annual: Linked Data Program

11. Q: How do we make Identifiers for Relationships?A: We already have them, in RDA 7/13/09 11 ALA Annual: Linked Data Program

12. URI Definition For use with this FRBR entity 7/13/09 12 ALA Annual: Linked Data Program

13. More specific properties 7/13/09 13 ALA Annual: Linked Data Program

14. 7/13/09 14 ALA Annual: Linked Data Program

15. Registered Elements Contain: Names and labels Resolvable URIs (for machine use, primarily) Reciprocal relationships between elements Relationships between RDA Elements and FRBR entities (FRBR entities will be maintained by IFLA) Administrative properties (status, update date, notes, maintainer) 7/13/09 15 ALA Annual: Linked Data Program

16. 7/13/09 16 ALA Annual: Linked Data Program 262 Relationships?

17. URI Parent Property Status Language 7/13/09 17 ALA Annual: Linked Data Program

18. Please Note: The fact that the registration of RDA vocabularies supports a linked data future for libraries is NOT ACCIDENTAL We owe a great deal to the funders of the DCMI/RDA Task Group (The British Library and Siderean Software), who had the vision to wade in and support this work The vocabularies will be complete, reviewed and with status “published” when RDA is released 7/13/09 18 ALA Annual: Linked Data Program

19. Thank you! 7/13/09 19 ALA Annual: Linked Data Program