From: Linked Data: what cataloguers need to know. A CIG event. 25 November 2013, Birmingham. #cigld
http://www.cilip.org.uk/cataloguing-and-indexing-group/events/linked-data-what-cataloguers-need-know-cig-event
Accompanying write-up from Catalogue & Index 174: http://discovery.ucl.ac.uk/1449460/
1. BIBFRAME
Linked Data: what cataloguers need to know #cigld
CILIP Cataloguing and Indexing Group (CIG)
25 November 2013
Thomas Meehan
tom@aurochs.org @orangeaurochs
4. Why?
• On the Record / Library of Congress Working
Group on the Future of Bibliographic Control
(January 2008)
• Report and Recommendations of the U.S. RDA
Test Coordinating Committee (June 2011)
"Demonstrate credible progress towards a
replacement for MARC".
5. Who
Library of Congress
Consultants:
• Zepheira
Partners (Early Experimenters) and among others:
• British Library,
• Deutsche Nationalbibliothek,
• George Washington University,
• National Library of Medicine,
• OCLC,
• and Princeton University
9. BIBFRAME Model: Resource
A BIBFRAME Resource can be anything: a Work, Instance, Authority, or
Annotation
bf:authorizedAccessPoint
bf:identifier
bf:label
bf:relatedTo
http://bibframe.org/vocab/Resource.html
10. BIBFRAME Model: Work 1/2
Work: A resource reflecting a conceptual essence of the cataloging resource. (A FRBR Work/Expression)
bf:classificationLcc
bf:contains
bf:creator
bf:hasDerivative
bf:note
bf:language
bf:originalVersion
bf:relatedWork
bf:series
bf:title
bf:workTitle
bf:subject
12. BIBFRAME Model: Instance 1/2
Instance: A resource reflecting an individual, material embodiment of
the Work. (A FRBR Manifestation)
bf:contributor
bf:dimensions
bf:extent
bf:isbn10
bf:isbn13
bf:isbn
bf:publication
bf:instanceOf
bf:titleStatement
http://bibframe.org/vocab/Instance.html
14. BIBFRAME Model: Authority (Person)
Authority: A resource reflecting key authority concepts that have defined
relationships reflected in the Work and Instance.
bf:hasAuthority
bf:authorizedAccessPoint
http://bibframe.org/vocab/Authority.html
http://bibframe.org/documentation/bibframe-authority/
15. More on BIBFRAME Authorities
Direct Approach
ex:wk666
a bf:Work ;
bf:creator lc_names:no97080492 .
Indirect Approach, or, The lightweight abstraction layer
ex:wk666
ex:person99
a bf:Work ;
bf:creator ex:person99 .
a bf:Person ;
authorizedAccessPoint "Waugh, Evelyn,1903-1966." ;
hasAuthority lc_names:no97080492 .
16. Even More on BIBFRAME Authorities
Work
Work
creator
creator
Bibframe
LC
hasAuthority
LC
17. BIBFRAME Model: Annotation
Annotation: A resource that decorates other BIBFRAME resources with additional
information, e.g. holdings, cover art, reviews.
bf:annotates
bf:annotationAssertedBy
bf:annotationBody
bf:annotationSource
bf:annotationDate
http://bibframe.org/vocab/Annotation.html
http://bibframe.org/documentation/annotations/
18. BIBFRAME Annotations Example
ex:wk005 a bf:Work ;
bf:hasAnnotation ex:ann010 .
ex:ann010 a bf:Annotation ;
bf:describes ex:wk005 ;
bf:annotationAssertedBy <http://id.loc.gov/vocabulary/organizations/ukluc> ;
bf:payloadSource <http://dbpedia.org/resource/Dbpedia> ;
bf:payloadSourceLink < http://dbpedia.org/resource/ Decline_and_Fall > ;
dateOfAssertion "20131125" ;
bf:beginningOfDescription "Decline and Fall is a novel by the English author Evelyn
Waugh, first published in 1928. It was Waugh's first published novel; an earlier attempt, entitled
The Temple at Thatch, was destroyed by Waugh while still in manuscript form. Decline and Fall is
based in part on Waugh's undergraduate years at Hertford College, Oxford, and his experience as
a teacher in Wales. It is a social satire that employs the author's characteristic black humour in
lampooning various features of British society in the 1920s. The novel's title is a contraction of
Edward Gibbon's The History of the Decline and Fall of the Roman Empire. " .
19. Getting BIBFRAME Examples
1. BIBFRAME Compare:
http://bibframe.org/tools/compare/
2. Enter an LC number (e.g. 10342843).
3. Select BIBFRAME RDF/XML view
4. Copy the result and paste it into the Input Field at this
RDF converter http://rdf-translator.appspot.com/
5. Select N3 (i.e. Turtle) output.
6. Submit!
7. Figure out what's going on.
20. BIBFRAME Example
Legend: Work, Instance, Authority
@prefix bf: <http://bibframe.org/vocab/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix madsrdf: <http://www.loc.gov/mads/rdf/v1#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<http://id.loc.gov/resources/bibs/10342843> a bf:LanguageMaterial,
bf:Work ;
bf:authorizedAccessPoint "Berners-Lee, C. M. Models for decision;" ;
bf:class-ddc "658.5" ;
bf:class-lcc <http://id.loc.gov/authorities/classification/HF5548> ;
bf:creator [ a bf:Person ;
bf:authorizedAccessPoint "Berners-Lee, C. M." ;
bf:hasAuthority [ a madsrdf:Authority ;
madsrdf:authoritativeLabel "Berners-Lee, C. M." ] ;
bf:label "Berners-Lee, C. M." ;
bf:resourceRole "ed." ] ;
bf:derivedFrom <http://id.loc.gov/resources/bibs/10342843> ;
bf:hasInstance [ a bf:Instance ;
bf:contributor [ a bf:Organization ;
bf:authorizedAccessPoint "British Computer Society." ;
bf:hasAuthority [ a madsrdf:Authority ;
madsrdf:authoritativeLabel "British Computer Society." ] ;
bf:label "British Computer Society." ],
[ a bf:Organization ;
bf:authorizedAccessPoint "Operational Research Society." ;
bf:hasAuthority [ a madsrdf:Authority ;
madsrdf:authoritativeLabel "Operational Research Society." ] ;
bf:label "Operational Research Society." ],
[ a bf:Organization ;
bf:authorizedAccessPoint "Institution of Electrical Engineers." ;
bf:hasAuthority [ a madsrdf:Authority ;
madsrdf:authoritativeLabel "Institution of Electrical Engineers." ] ;
bf:label "Institution of Electrical Engineers." ] ;
bf:derivedFrom <http://id.loc.gov/resources/bibs/10342843> ;
bf:derivedFromLccn <http://id.loc.gov/authorities/identifiers/lccn/66003612> ;
bf:dimensions "23 cm." ;
bf:extent "x, 149 p." ;
bf:hasHolding [ a bf:Holding ;
bf:callno-lcc "HF5548.2.B4" ;
bf:label "HF5548.2.B4" ] ;
bf:illustrativeContentNote "illus." ;
bf:instanceOf <http://id.loc.gov/resources/bibs/10342843> ;
bf:note ""A conference under the auspices of the United Kingdom Automation Council organised by the British Computer Society and the Operational Research Society." Held Oct. 13-14, 1964 at the Institute of Electrical Engineers, London." ;
bf:oclc-number <http://oclc.org/oclc-number/1162695> ;
bf:publication [ a bf:ProviderEntity ;
bf:providerDate "1965" ;
bf:providerName "English Universities Press" ;
bf:providerPlace "London" ] ;
bf:title "Models for decision;" ] ;
bf:note ""A conference under the auspices of the United Kingdom Automation Council organised by the British Computer Society and the O perational Research Society." Held Oct. 13-14, 1964 at the Institute of Electrical Engineers, London." ;
bf:primaryLanguage <http://id.loc.gov/vocabulary/languages/eng> ;
bf:subject [ a bf:Topic ;
bf:authorizedAccessPoint "Public administration--Data processing" ;
bf:hasAuthority [ a madsrdf:Authority,
madsrdf:ComplexSubject ;
madsrdf:authoritativeLabel "Public administration--Data processing"@en ] ;
bf:label "Public administration--Data processing" ],
[ a bf:Topic ;
bf:authorizedAccessPoint "Electronic data processing" ;
bf:hasAuthority [ a madsrdf:Authority,
madsrdf:Topic ;
madsrdf:authoritativeLabel "Electronic data processing"@en ] ;
bf:label "Electronic data processing" ] ;
bf:title "Models for decision;" .
22. Bibframe Example 2/4: Work
<http://id.loc.gov/resources/bibs/10342843> a bf:LanguageMaterial,
bf:Work ;
bf:authorizedAccessPoint "Berners-Lee, C. M. Models for decision;" ;
bf:class-ddc "658.5" ;
bf:class-lcc <http://id.loc.gov/authorities/classification/HF5548> ;
bf:creator [ a bf:Person ;
bf:authorizedAccessPoint "Berners-Lee, C. M." ;
bf:hasAuthority [ a madsrdf:Authority ;
madsrdf:authoritativeLabel "Berners-Lee, C. M." ] ;
bf:label "Berners-Lee, C. M." ;
bf:resourceRole "ed." ] ;
bf:derivedFrom <http://id.loc.gov/resources/bibs/10342843> ;
23. Bibframe Example 3/4: Instance
bf:hasInstance [ a bf:Instance ;
bf:contributor [ a bf:Organization ;
bf:authorizedAccessPoint "British Computer Society." ;
bf:hasAuthority [ a madsrdf:Authority ;
madsrdf:authoritativeLabel "British Computer Society." ] ;
bf:label "British Computer Society." ],
bf:derivedFrom <http://id.loc.gov/resources/bibs/10342843> ;
bf:derivedFromLccn <http://id.loc.gov/authorities/identifiers/lccn/66003612> ;
bf:dimensions "23 cm." ;
bf:extent "x, 149 p." ;
bf:hasHolding [ a bf:Holding ;
bf:callno-lcc "HF5548.2.B4" ;
bf:label "HF5548.2.B4" ] ;
bf:illustrativeContentNote "illus." ;
bf:instanceOf <http://id.loc.gov/resources/bibs/10342843> ;
bf:note ""A conference under the auspices of the United Kingdom Automation Council organised by the British Computer
Society and the Operational Research Society." Held Oct. 13-14, 1964 at the Institute of Electrical Engineers, London." ;
bf:oclc-number <http://oclc.org/oclc-number/1162695> ;
bf:publication [ a bf:ProviderEntity ;
bf:providerDate "1965" ;
bf:providerName "English Universities Press" ;
bf:providerPlace "London" ] ;
bf:title "Models for decision;" ] ;
24. Bibframe Example 4/4: Work cont'd
bf:note ""A conference under the auspices of the United Kingdom Automation Council organised by
the British Computer Society and the Operational Research Society." Held Oct. 13-14, 1964 at the
Institute of Electrical Engineers, London." ;
bf:primaryLanguage <http://id.loc.gov/vocabulary/languages/eng> ;
bf:subject [ a bf:Topic ;
bf:authorizedAccessPoint "Public administration--Data processing" ;
bf:hasAuthority [ a madsrdf:Authority,
madsrdf:ComplexSubject ;
madsrdf:authoritativeLabel "Public administration--Data processing"@en ] ;
bf:label "Public administration--Data processing" ],
[ a bf:Topic ;
bf:authorizedAccessPoint "Electronic data processing" ;
bf:hasAuthority [ a madsrdf:Authority,
madsrdf:Topic ;
madsrdf:authoritativeLabel "Electronic data processing"@en ] ;
bf:label "Electronic data processing" ] ;
bf:title "Models for decision;" .
25. Find Out More
BIBFRAME.org
http://bibframe.org/
BIBFRAME Model and vocabulary.
http://bibframe.org/vocab/
BIBFRAME Model Primer (pdf).
http://www.loc.gov/bibframe/pdf/marcld-report-11-212012.pdf
BIBFRAME mailing list.
http://listserv.loc.gov/listarch/bibframe.html
26. References
• On the Record / Library of Congress Working Group on the Future
of Bibliographic Control (January 2008).
http://www.loc.gov/bibliographic-future/news/lcwg-ontherecordjan08-final.pdf
• Report and Recommendations of the U.S. RDA Test Coordinating
Committee. Executive Summary (June 2011).
http://www.loc.gov/bibliographic-future/rda/source/rdaexecsummary-public-13june11.pdf
• A Bibliographic Framework for the Digital Age (October 31, 2011).
http://www.loc.gov/bibframe/news/framework-103111.html
• FRBR as cake / Karen Coyle (Coyle's InFormation, 2011)
http://kcoyle.blogspot.co.uk/2011/04/frbr-as-cake.html
• Open Annotations Model / W3C. http://www.w3.org/ns/oa
Notes de l'éditeur
"The library community's data carrier, MARC, is based on forty-year old techniques for data management and is out of step with programming styles of today. No community other than the library community uses this record format, severely compromising its utility to other communities as a data transmission tool. Bibliographic applications being developed outside of the library environment are not making use of, and may not be compatible with, records encoded in MARC. New and anticipated uses of bibliographic data require a format that will accommodate and distinguish expert-, automated-, and user-generated metadata, including annotations (reviews, comments) and usage data. Flexible design should allow for the selective (modular) use of metadata in different environments (e.g., use of controlled vocabularies appropriate to specific domains). The existing Z39.2/MARC “stack” is not an appropriate starting place for a new bibliographic data carrier because of the limitations placed upon it by the formats of the past."—On the Record."Many survey respondents expressed doubt that RDA changes would yield significant benefits without a change to the underlying MARC carrier."Most felt any benefits of RDA would be largely unrealized in a MARC environment. MARC may hinder the separation of elements and ability to use URIs in a linked data environment. "While the Coordinating Committee tried to gather RDA records produced in schemas other than MARC, very few records were received.""Demonstrate credible progress towards a replacement for MARC"-- Report and Recommendations of the U.S. RDA Test Coordinating Committee. Executive Summary"Bibliographic framework is intended to indicate an environment rather than a "format"" according to the A Bibliographic Framework for the Digital Age (October 2011). However, most people when they are talking about Bibframe are in fact talking about this idea, which is what I'm going to focus on.
Zepheira are consultants with expertise and experience with the Semantic Web. Worked with OCLC on schema.org as well as a new project with University of California, Davis to "investigate the future of research library operations, particularly the production of metadata — or data on data — and deployment on the Web." Its president, Eric Miller, has been prominent in the development of the Semantic Web and RDF.Interestingly not a formal collaborative effort.
This is the basic Bibframe model. "BIBFRAME has worked on modelling works as Works within the BIBFRAME model, similar to the RDA modelling work, itself modelled on the work on the FRBR model of Works and Expressions. A BIBFRAME Work is a creative work, perhaps a FRBR Work, or an RDA FRBR Work but it also expresses a FRBR Expression, and of course an RDA FRBR Expression. A Work may express another Work based on others’ work, not just a FRBR Work or an RDA Work. That also works. FRBR Works or RDA Works expressed as BIBFRAME Works can relate to FRBR Expressions (BIBFRAME Works or RDA Expressions). So, Works are works that can be Works but also Expressions linked to Works that really are Works."
ABibframe resource can be anything the same as as RDF resource is anything that can be given a URI.authorizedAccessPoint: "Controlled string form of a resource label intended to help uniquely identify it, such as a unique title or a unique name plus title." For the resource, not one of its access points.identifier: something not covered by another property.label: "Text string expressing the property value."relatedTo: "Any relationship between resources."
classificationLcc: Other classifications are available.contains: "Work that is a discrete component of a larger work."creator: [Doesn't appear on the list of properties!]hasDerivative: "Work has a modification for which it is the source. Work that has been translated, i.e., the text expressed in a language different from that of the original workp)."NB. expressionOf and hasExpression!hasInstance: "Work has a related Instance/manifestation."!bf:title: [Doesn't appear in the list of properties!]. bf:workTitle does, but not in examples?
contributor: [Not in the list of attributes, but turns up in examples!]dimensions: "Measurements of the carrier or carriers and/or the container of a resource."isbn10, isbn13: More specific than bf:identifierbf:publication: Seems to have replaced the previous attributes bf:placePub, bf:provider, bf:pubDate to provide a more event-based model (like the BL's). See example on next slide.titleStatement: "Title transcribed from an instance."For FRBR, note instanceOf. Also, at least in examples, the split between creator for work, and contributor for instances.
Previous properties included resourceRole, isnni, orcid, and viaf. Resourcerole is tricky.
The first is what most people would assume would happen and is the classic linked data approach. Indeed, it's basically a recreation of the first example I showed you this morning.The second is Bibframe's attempt to deal with some essentially practical problems:Local indexingLocal variationAllows augmentation from other sourcesDeals with people not in authority files without a pre-existing URIAlthough many of these things are possible by simply making use of existing techniques. There is also the danger that the notion of an authority is confused with that of a person. They are not the same thing
When knowing WHO is asserting the additional information is important!!!There is other work which approaches the same problems: named graphs, an already established Open Annotations Model from the W3C whose outline Bibframe follows but not exactly. This could prove troublesome.
bf:describes is a subproperty of bf:annotatesbf:annotationAssertedBy: a URI of whoever asserted this was the case. The important bit for Annotations! In this case, UCL