1.
Digital Library Applications of Social Networking <br />Dr. Myungdae Cho<br />Library School<br />SungKyunKwan University<br />myungdae.cho@gmail.com <br />

2.
Agenda<br />

3.
1. Social Networking & Information Fluency<br />From PIM (Personal Information Management) level <br /> - Is Memex incarnated? <br /> - more than hyperlink …<br />To “Sociality” by Link and Tags<br /> -&gt; Inter-subjectivity <br /> - a thought in a user links to many thoughts in <br /> internet community <br /> -&gt;Principle of Emergence<br />

4.
Socialty<br />(Messaging,<br /> Blogging,<br /> Streaming media)<br />

5.
Machine, Humanand Socialty in Information Discovery <br />Forms Inter-subjectivity<br />Ontology (gives Subjective Path)<br />In other words: Top down + Bottom up <br />

6.
Another view of Machine, Humanand Socialty in Information Discovery <br />RDF vocabularies<br />or<br />(Ontology)<br />User-Created Metadata <br />Linked Data<br />(semantically organized data)<br />Mapped data from existing DB (such as MARC)<br />

7.
2. Social Networking in Libraries<br />Social networking could enable librarians and <br /> patrons not only to interact, but to share and <br /> changeresources dynamically in an electronic <br /> medium. <br />

8.
Why do libraries care about social networking sites?<br />The next big thing after Google is Social Networking.<br /> ( From “As facebook takes off, Myspace strikes <br /> back” Kirkpatrick, Davis. Foutune. Sept. 19, 2007)<br />

9.
2.1 Existing Library Application of Social Networking<br />Librarything in libraries<br />Delicious in libraries <br />Mashup….. couldbe as an application of Linked data<br />

10.
2.1.1 Librarything in libraries<br />http://www.librarything.com/<br />“Personalized desire from individual’s needs”<br />“Cataloguing thru Social Networking”<br />LibraryThing is a prominent social cataloging<br /> web application for storing and sharing personal library catalogs and book lists.<br />

11.
Librarything in libraries<br />LibraryThing helps you create a library-quality <br /> catalog of your books. <br />LibraryThing connects people based on the books <br /> they share.<br />

12.
2.1.2. Delicious in libraries <br />

13.
del.icio.us-like PennTags<br />PennTags - When card catalogs meet tags<br />http://tags.library.upenn.edu/<br />http://www.slideshare.net/laurie.allen/penntags-presentation-at-educause-2006<br />http://www.diglib.org/forums/fall2006/presentations/winkler-2006-11.pdf<br />

14.
2.1.3 Mash up in libraries <br />http://library20.ning.com/profiles/blogs/mashup-your-librarys-twitter<br />Mashup your Library&apos;s Twitter, Flickr, Youtube, <br />Facebook accounts! <br /><ul><li>Libraries mash up content, services and ideas</li></ul> http://www.oclc.org/fr/fr/nextspace/009/1.htm<br />Meebo Instant Messaging. Library Lookup. <br />Bookburro.<br />

15.
3. how to lift existing metadata into a semantic level<br />Mapping (Marc21 -&gt; DC, Marc -&gt; FRBR etc)<br />Open Sources (Open Api)<br />Linked Data<br />

16.
3.1 Open Source<br />Open Source Social Platforms: 10 of the Best<br />10 open source software platforms<br />http://mashable.com/2007/07/25/open-source-social-platforms/<br />www.programmableweb.com<br />SungKyunKwan University: Use ofOpen API http://lib.skku.edu/index.ax<br />

17.
3.2 Linked Data <br />“Oh my goodness, the original web of documents was just the tip of iceberg.”<br />( Sir Tim Berners Lee, July 2008)<br />

18.
What is it?<br />

19.
Closed containers of data<br />Information systems, such as library catalogs, have <br />been, and still are, for the greatest part closed <br />containers of data, or “silos” without connections <br />between them, inaccessible to Web architecture (No Url, no links) with a few exception.<br />(Tim Berners Lee)<br /> free from the capsules of the catalog<br />

20.
Linked Data<br />Linked Data is a methodology for providing <br /> meanings and relationships between things anywhere on the web, using <br />URISfor identifying, <br />RDF for describingand <br />HTTP for publishing<br />

21.
Two valuable notions from library community<br />Collocations<br /><ul><li>1876 / Charles Cutter

22.
Resources with the same or related content are grouped together.</li></ul>Disambiguation <br /><ul><li>clarification that follows from the </li></ul> removal of ambiguity <br />

23.
Collocations through Linked Data<br />Wiki: http://www.wikipedia.org/<br />vs<br />dbpedia : http://dbpedia.org/About<br />WorldCat: http://www.worldcat.org/<br />vs<br />Fictionfinder (FRBR model): http://fictionfinder.oclc.org<br />

24.
rdf identifiers as a disambiguation <br />http://rdf.freebase.com/?freebaseid<br />http://rdf.freebase.com/ns/en.blade_runner<br />

25.
rdf identifiers as a disambiguation <br />annotation<br />Disambiguation process<br />

26.
rdf identifiers as a disambiguation <br />

27.
Another disambiguation_dereferenceable URIs<br />

28.
In summary so far:Paradigm Shift in www <br />

29.
4. Library’s role in Semantic Web<br />Phase 1: Semantifying MARC, Thesaurus etc <br /> Translating LC controlled vocabularies and authority control for named entities, thesauri from domain specific societies and institutions into RDF/RDFS, OWL, SKOS with URIs assigned according to ‘Linked Data Design Principles (TBL, 2007)<br />Phase 2:<br /> Authority data discovery, sharing, and reuse, e.g., LC authorities & Vocabularies, OCLC’s Faceted Application of Subject Terminology (FAST) etc <br />Phase 3: Into the Semantic Web<br />Web of Linked data<br />DBPedia<br />GeoNames<br />Librarything<br />

30.
Case: OCLC Semantic Web Projects<br /><ul><li>FRBRising projects

31.
Developed FRBR work set algorithms’ andxISBN Web Services

32.
FictionFinderhttp://fictionfinder.oclc.org

33.
WorldCat Identifiers (20 million identifiers)</li></li></ul><li>CV: Why establish controlled vocabularies?<br />Control values that occur in metadata<br />Reduce ambiguity<br />Control synonyms<br />Make documentation available for reuse <br />validate terms (by subject heading /LCSH)<br />Establish formal relationships among values where appropriate<br />Controlled vocabularies: ALA program on Linked Data<br />ALA Annual 2009<br />

34.
Types of Controlled Vocabularies used in metadata standards<br />Lists of enumerated values <br />Code lists (e.g. language, country)<br />Taxonomies<br />Formal Thesauri<br />Locally controlled enumerated lists<br />Controlled vocabularies: ALA program on Linked Data<br />ALA Annual 2009<br />

35.
Thesauri<br />A thesaurus is a controlled vocabulary with multiple types of relationships<br />Example:<br />Rice<br /> UF Paddy<br />BT Cereals<br />BT Plant products<br />NT Brown rice<br />RT Rice straw<br />

36.
Standards maintained at LC contain controlled vocabularies<br />LCSH/NAF<br />Thesaurus of Graphic Materials<br />ISO 639-2 (language codes)<br />MARC (including code lists)<br />MODS<br />METS<br />PREMIS<br />MIX (XML schema for NISO Z39.87 Technical metadata for digital still images)<br />… and some others<br />

37.
Representing information about controlled vocabulary values<br />Data elements in metadata formats, e.g. MARC Authority format<br />XML schemas (sometimes as enumeration values)<br />RDF/XML and RDFS (Resource Description Framework)<br />SKOS<br />MADS (Metadata Authority Description Schema)<br />

38.
Reasons for developing a web service for vocabularies<br />Facilitate development and maintenance process for vocabularies<br />Make controlled lists “openly” available<br />Provide comprehensive information about controlled values<br />Experiment with semantic web technologies and linked data<br />Expose vocabularies to wider communities<br />

39.
Popular Rdf Vocabularies <br />People + Organisations<br />FOAF, HCard, Relationship, Resume<br />Places <br />Geonames, Geo<br />Events <br />RDFCalendar<br />Social Media <br />SIOC, Review<br />Topics + Tags <br />SKOS, MOAT, HolyGoat<br />eCommerce<br />GoodRelations, CC Licensing<br />More... <br />Scovo, DOAP, Recipes, Measurements, ... <br />

40.
SKOS<br />“Simple Knowledge Organisation System(s)”<br />A Semantic Web standard called Simple Knowledge Organization System (SKOS) defines the organization of terms into thesaurus form, with broader and narrower terms and alternate terms including alternate language entries<br />Simple, extensible, machine-understandable representation for “concept schemes”<br />Thesauri<br />Classification Schemes<br />Taxonomies<br />Subject Headings<br />Other types of ‘controlled vocabulary’…<br />Disadvantage: unusual concept schemes don’t fit into SKOS (original structure too complex)<br />

41.
A Method to Convert Thesauri to SKOS<br />Case1<br />Original XML data file: http://www.esd.org.uk/standards/ipsv/ipsv.xml<br />Original XML Schema filehttp://www.esd.org.uk/standards/xmlschemas/taxonomy-v3.0.xsd<br />Conversion program: convertipsv.pl (contains instructions for usage)<br />Resulting RDF: ipsv/rdf/ipsv.rdf<br />SKOS Core schema: http://www.w3.org/2004/02/skos/core/history/2005-10-14 (version used for this paper, for latest version seehere)<br />Additional IPSV schema: ipsv/ipsv1-eswc06.rdf<br />Case 2<br />Partial original data files: gtaa/SampleOfGTAA.zip<br />Conversion program: gtaa/GTAAtoSKOSinstanceRDFSv6.pl<br />Resulting RDF: gtaa/GTAAinstancesSKOSv7.rdf<br />SKOS Core schema: http://www.w3.org/2004/02/skos/core/history/2005-10-14 (version used for this paper, for latest version seehere)<br />Additional GTAA schema: gtaa/GTAAskosModelRDFSv4.rdfs<br />

42.
Converting into SKOS graph<br />Identify<br />Describe<br />Publish<br />

43.
Identify<br />Step 1: Identify concepts…<br /> http://www.example.com/concepts#lovehttp://www.example.com/concepts#awehttp://www.example.com/concepts#joy<br />

44.
Describe<br />Step 2: Describe…<br />

45.
Publish<br />Step 3: Publish…<br />Put the file on a web server for programs to download & process<br />Put the file on special RDF server on which you can query with SQL-like language:<br />Select * from … Where …<br />

46.
Publishing LCSH in the Web<br />Project LCSH into RDF (i.e., create an RDF representation)<br />Library of Congress Subject Headings available as linked-data using the SKOS vocabulary. http://lcsh.info<br />

47.
LCSH in SKOS<br /> <br />

48.
LCSH in SKOS<br />

49.
LCSH in SKOS<br />

50.
Skosuse cases_2: NSDL Metadata Registry<br />http://metadataregistry.org/<br />

51.
Skosuse cases_3: getty<br />http://www.getty.edu/research/conducting_research/vocabularies/download.html<br />

52.
Skosuse cases_4: Agricultural Information Management Standards (AIMS)<br />http://aims.fao.org/en/search/google/cow?query=cow&cx=011162950886884224513:ennli7xeebg&cof=FORID:11&sitesearch=&hl=en&ie=utf-8&oe=utf-8&lr=lang_en<br />

53.
FRBR conceptual model<br />Coyle (2008) advocates FRBR conceptual model <br /> as part of a semantic model in saying <br /> “Since FRBR is about entities and relationships, it seems to be perfectly positioned as the first step in the transformation of library data to the <br /> semantic web.”<br />

54.
FRBR<br />Expression of Core FRBR Concepts in RDF<br /> http://vocab.org/frbr/core.html<br />This vocabulary is an expression in RDF of the <br /> concepts and relations described in the IFLA <br /> report on the Functional Requirements for <br /> Bibliographic Records (FRBR).<br />

55.
FRBR as a RDF vocabulary<br />FRBR is a complete data model that is a new way of looking at our data, not just taking existing records and identifying work relationships.<br />FRBR a type of RDF vocabulary<br />entities and the relationships inFRBR is identifiable, <br /> linkable, usable, and reusable, and everything can <br /> be matched up. <br />

56.
FRBR-SKOS<br />

57.
RDA (Resource Description and Access) <br />The new cataloging rules, replacing AACR2<br />RDA -&gt; RDF<br />Joint DCMI/RDA task force<br />Seed funding to develop initial prototype RDF vocabularies for bibliographic information<br />Based on FRBR and data model implicit in RDA<br />Early stage year<br />http://dublincore.org/dcmirdataskgroup/<br />Karen Coyle<br />

58.
library related Linked Data projects<br />A brief and incomplete list of some library related <br /> Linked Data projects:<br />RDF BookMashup – Integration of Web 2.0 data sources like Amazon, Google or Yahoo into the Semantic Web. <br />Library of Congress Authorities – Exposing LoCAutorities and Vocabularies to the web using URI’s <br />DBPedia – Exposing structured data from WikiPedia to the web <br />LIBRIS – Linked Data interface to Swedish LIBRIS Union catalog <br />Scriblio+Wordpress+Triplify – “A social, semantic OPAC Union Catalogue” <br />

59.
Language of Interoperability<br />Universal identifiers (URIs): like written word <br /> – For “connecting the dots”<br />Abstract syntax (RDF triples): sentence grammar<br /> – Foundation of syntactic interoperability<br />Vocabularies: words and concepts<br /> – Foundation of semantic interoperability<br />Platform for compatible domain models<br /> – Application Profiles<br />Human-understandable – machine-processable<br />

60.
5. Proposed Models for Libraries with Linked data <br />A publisher provides basic information about a book<br /> (e.g., using onix)<br />The National Library adds bibliographic and authority <br /> control<br /> A local library adds holding information<br /> Some nice guy out there adds links from, say, Wikipedia<br /> A library’s IT staff creates a Webpage where I can find all related information regarding this book, links to related books from the same author, on the same subject, the author’s bio from wikipedia, comments from other Portals. <br />=&gt;Since, instead of following links between HTML pages, Linked Data browsers enable users to navigate between different data <br />sources by following RDF links.<br />How about User-created metadata<br />

61.
Advantages over other methods<br />No crosswalk/mapping<br /> - Each one uses his own metadata format, all triples can be aggregated<br />No data redundancy<br /> - Each one creates only the data he needs, and retrieves already existing information <br />No harvesting<br /> - The data is available directly on the Web<br />No branding issue<br /> - The URIs allow to track down the original data whatever its origin<br />No software-specific developments<br /> - Everything relies on open standards as RDF, SPARQL … no need to learn a new protocol or query<br /> language<br />

62.
Thank you for listening! <br />Questions? <br />