1 / 19

FUTURE OF BIBLIOGRAPHIC METADATA

FUTURE OF BIBLIOGRAPHIC METADATA. Peter Binkley LIS 598: SPECIAL TOPICS: Information Modeling in XML Aug. 2009. TOPICS. FRBR: Functional Requirements for Bibliographic Records RDA: Resource Description and Access RDF (Resource Document Framework) and the Semantic Web Linked Data

kale
Download Presentation

FUTURE OF BIBLIOGRAPHIC METADATA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FUTURE OF BIBLIOGRAPHIC METADATA Peter Binkley LIS 598: SPECIAL TOPICS: Information Modeling in XML Aug. 2009

  2. TOPICS • FRBR: Functional Requirements for Bibliographic Records • RDA: Resource Description and Access • RDF (Resource Document Framework) and the Semantic Web • Linked Data • … and how XML contributes to them all

  3. FRBR • Problem: how to relate multiple editions and formats of a work in a sensible way • Entities: • Work: Beowulf • Expression: ed. Klaeber, 3rd edition • Manifestation: the book published in 1950 • Item: Rutherford PR 1580 K63 1950 • Imagine the XML: <work id=“beowulf”> <expression id=“klaeber3”> <manifestation id=“book1950”> <item id=“rutherford”>

  4. XML-BASED FRBR EXAMPLE • LOC FRBR Display Tool • http://www.loc.gov/marc/marc-functional-analysis/tool.html • E.g. http://www.loc.gov/marc/marc-functional-analysis/frbr-welty.html

  5. RDA • Replacement for AACR2 (1978) • Founded on FRBR; designed for digital world • Characteristics • Separates content from presentation (no ISBD) • Can be embodied in MARC, XML, etc. • Designed for backward compatibility with AACR2

  6. RDF • Resource Document Framework: a data model for metadata • Note: it is an abstract data model, not a format • Can be serialized as XML or in other formats • Principles: • Everything has a URI • Namespaces provide context • Descriptions are in “triples”: “x has y relationship to z”

  7. RDF EXAMPLE <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/"> <rdf:Description rdf:about="urn:x-states:New%20York"> <dcterms:alternative>NY</dcterms:alternative> </rdf:Description> </rdf:RDF>

  8. RDF EXAMPLE: FOAF • “Friend of a Friend” • <rdf:RDF xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#”> <foaf:Person rdf:about="#PAB"> <foaf:name>Peter Binkley</foaf:name> <foaf:mbox rdf:resource="mailto:peter.binkley@ualberta.ca" /> <foaf:knows> <foaf:Person> <foaf:name>Kenton Good</foaf:name> </foaf:Person> </foaf:knows> </foaf:Person></rdf:RDF>

  9. SEMANTIC WEB • Machine-readable web, where the machines understand what they’re reading and know how to use it

  10. SEMANTIC WEB STACK Wikipedia

  11. ONTOLOGIES: KNOWLEDGE BASES • Expressed in OWL (Web Ontology Language) • E.g.: <owl:Class rdf:ID="Wine"> <rdfs:subClassOf rdf:resource="&food;PotableLiquid"/> <rdfs:label xml:lang="en">wine</rdfs:label> <rdfs:label xml:lang="fr">vin</rdfs:label> ... </owl:Class>

  12. RIF: RULE INTERCHANGE FORMAT • A buyer buys an item from a seller if the seller sells the item to the buyer. • John sells LeRif to Mary. Document( Prefix(cpt <http://example.com/concepts#>) Prefix(ppl <http://example.com/people#>) Prefix(bks <http://example.com/books#>) Group ( Forall ?Buyer ?Item ?Seller ( cpt:buy(?Buyer ?Item  ?Seller) :- cpt:sell(?Seller ?Item ?Buyer) ) cpt:sell(ppl:John bks:LeRif ppl:Mary) ) )

  13. IMAGINE A WORLD… • Where every thing and concept has a URI • Where web pages include tagging with those URIs • Where all our knowledge of the relationships between things and concepts has been encoded in ontologies • Where all our knowledge of the potential interactions of things and concepts has been encoded in rules engines

  14. CRITICISMS • Impractical • People lie • The required infrastructure is unimaginable • Hardware • Network • Software • Data

  15. LINKED DATA • Tim Berners Lee proposal • A practical step towards the Semantic Web • Principles: • Use URIs as names for things • Use HTTP URIs so that people can look up those names. • When someone looks up a URI, provide useful information, using the standards (RDF, SPARQL) • Include links to other URIs, so that they can discover more things.

  16. LINKED DATA EXAMPLE • Tim Berners-Lee’s FOAF file: • http://www.w3.org/People/Berners-Lee/card.rdf

  17. APPLICATIONS IN LIBRARIES • Addresses the “dark web” problem • Exposes our data for reuse in a standard way (as opposed to library-specific APIs)

  18. EXAMPLE: SWEDISH UNION CATALOGUE • http://article.gmane.org/gmane.culture.libraries.ngc4lib/4617 • A book: http://libris.kb.se/resource/bib/5060570 • Use “curl” to try it: • Book: curl --include --location --header accept:text/rdf+n3 "http://libris.kb.se/resource/bib/5060570" • Author: curl --include --location --header accept:text/rdf+n3 "http://libris.kb.se/resource/auth/220040"

  19. THE BIG QUESTIONS • Will the Semantic Web, or something like, come about? • Will the Linked Data idea have traction? • Will library data fit into this new world? • Will we expose our data for use? • Will the broader web find our data useful?

More Related