FRBR 20 years onKaren CoyleRome, Feb. 2014

FRBR Timeline1990 Stockholm meeting1992 Terms of reference completed1994? First draft for comment1998 Final draft2009 Current draft

Stated goalsDevelop a framework for understanding purposes of the bibliographic recordRecommend basic level of functionality for national library bibliographic recordsDevelop core-level standard to reduce cataloging costsEnsure that records meet user needs

Leading up to FRBRThe rise of the work in the 20th century

Levels of bibliographic abstractionCollocation of works (Lubetzky)Expansion of catalogs to the 2nd kind of power (Wilson)Addition of the work to cataloging with uniform titles in AACR

Bibliographic relationshipsTilletts doctoral dissertation and lifes work

The Studhorse Manas a Wilsonian familySmiraglia, 2001Bibliographic Families (Wilson)A library is a growing organismS.R. Ranganathan

E-R modelRequired methodology in Terms of Reference document, 1992Derived from database design methodologyIdentify entitiesExplore relationshipsDefine attributes

FRBR is not a data model. FRBR is not a metadata scheme. FRBR is not a system design structure. It is a conceptual model of the bibliographic universe. B. Tillett, 2005

E-R modeling for database designConceptual modelmain entities and relationships, macro level; not actionable; independent of technologyLogical modeladds detail; resolves links; defines values; normalizes; operational in terms of applicationsPhysical modeldescribes a database, with tables, keys, normalized data; responsive to applications.

Results142 pages of text3 diagrams

Reading E-R

Ron Murray From Moby Dick to Mashups

Alternate modelsEvent-driven modelsContent-emphasizing modelsModels that categorize more than describeFRBRCore and the linked data cloud

actors and actionsIn music, expression often a performance by someone other than creatorManifestation is usually the action of a third party (except in fine art)

FRBRooCIDOC Conceptual Reference ModelbyInternational Council of Museums

FRBRooObject-oriented modelCoordinates CRM & FRBR conceptsMultiple layers of works and expressionsPublished and non-published works

event-oriented

content and carriervariations

Expression-Level Bibliographic RecordShoichi Taniguchicontentcarrier

classes and categorizationSemantic Publishing and ReferencingSPARPublishing materials, mostly texts, in the academic environment

FaBiO, the FRBR-aligned Bibliographic Ontologytreats WEMI as classessub-classes bibliographic types to W E MManifestation is physical description only

Work sub-classes announcement, artistic work, biography, case for support, correction, critical edition, dataset, essay, examination paper, grant application, image, instructional work, metadata, model, opinion, policy, proposition, questionnaire, reference work, reply, report, research paper, review, sound recording, specification, vocabulary, work collection, work package, working paper

Expression sub-classes Gantt chart, abstract, addendum, article, audio document, book, brief report, call for applications, case for support document, chapter, comment, computer program, conference paper, conference poster, cover, data file, data management plan, database, dust jacket, e-mail, editorial, excerpt, expression collection, figure, grant application document, index, instruction manual, lecture notes, letter, manuscript, metadata document, movie, news item, oration, patent application document, patent document, periodical issue, periodical volume, personal communication, policy document, presentation, project plan, quotation, rapid communication, report document, repository, spreadsheet, structured summary, supplement, supplementary information file, table, vocabulary document, vocabulary mapping document, web content, workshop paperManifestation sub-classesanalog manifestation, digital manifestation, manifestation collection

:article a fabio:JournalArticle ;dc:title "Nicotinamide-2,2,2-trifluoroethanol (2/1)" ;dcterms:creator [ a foaf:Person ;foaf:name "Johnston, B.F." ] ;dcterms:creator [ a foaf:Person ;foaf:name "Florence, A.J." ] ;dc:rights ;dc:language "en" ;fabio:hasPublicationYear "2009" ;fabio:publicationDate "2009-04-01" ;frbr:embodiment :printedArticle , :webArticle ;frbr:partOf :issue ;fabio:doi "10.1107/S1600536809007594" ;

:volume a fabio:JournalVolume ;prism:volume "65" ;frbr:partOf :journal .

:issue a fabio:JournalIssue ;prism:issueIdentifier "4" ;frbr:partOf :volume

FaBIOs Expression ~ Taniguchis

FRBRCore (in RDF)Developed by Ian Davis and Richard Newman in 2005Not sanctioned by IFLAUsed by FaBiO, Scholarly Works Application Profile (SWAP), Europeana Data Model, and othersOver 30 million uses on LOD Cloud (mostly German libraries)

BIBFRAME

Two-level bibliographic model

bf:Work = frbr:Work+frbr:Expression bf:Instance = frbr:Manifestation

RDARules organized around FRBR conceptsRecord and data store neutral.

Summarya conceptual model, to be interpreted and integrateda network, not a treeactors and actionsseparation of content and carrierthe need for flexibility

Thank you!kcoyle@kcoyle.nethttp://kcoyle.net

Not a goal, a methodology to arrive at the goal. *What does E-R modeling accomplish?*These three diagrams are what most people know about FRBR. However, it should be obvious that a few simple diagrams do not carry all of the information of the full text of the study groups document. This all proves the power of 5-7 the number of items that we can absorb in a single thought. *One of the problems of using E-R modeling is that many of the readers of FRBR will not be familiar with it. Unfortunately, the notation used in the diagrams is not intuitive. So while most people would look at this and see a hierarchy or a tree, from work to multiple expressions, etc. In fact this diagram represents a network. And remember that this diagram does not include the relationships, that is the lines with arrows, between works, or between expressions. So it does not include the adaptations or translations or other interesting relationships that the FRBR study revealed.*An expression may be embodied in a manifestation, but how does it get there? Library cataloging has been very THING oriented, but other communities put more emphasis on the processes that bring content into being, and the actors involved in that process. *Indecs was developed around sales their first diagram was known as people create stuff/people do deals about stuff. Library data has tended to take a static view library records are created and do not change. But adding relationships between items in the librarys collection to the catalog means that the catalog and its data must be dynamic.*Not every community creates the same division between content and carrier, and not all put the same emphasis on them as library cataloging does. *Expression includes all of the content data, including statement of responsibility, secondary creators. Manifestation is limited to publication and physical format information. If you ask a user to describe some document, they will rarely mention published in New York by Putnam, 356p. That is carrier, while title and author, according to Taniguchi, are content. So he would create a different division between expression and manifestation, by creating an expression that is all about the content, and leaving the manifestation to be the carrier.*Has elements of action-oriented view; and is primarily interested in the interaction between documents and the workflows that manage them.*Remember, FRBR is not a record format. So it is quite plausible to implement FRBR concepts with any number of levels (and well soon see that can mean increasing the number as well as decreasing it). Does not claim to be an implementation of FRBR, but says that it will be able to carry FRBR data, as well as RDA data.

BIBFRAME is not nearly complete, and it has the difficult task of accommodating RDA and MARC. It isnt clear yet how it will compare to the FRBR attributes.*