FRBR

From MusicBrainz Wiki
Revision as of 00:03, 20 April 2006 by Shepard (talk | contribs) (status notice (Imported from MoinMoin))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Alert.png Status: This page does not generally describe the term yet but as is reflects the opinion of one WikiZen. If you're familiar with the topic, please try to make this page more objective.

FRBR is short for Functional Requirements for Bibliographic Records, the title of a document released in 1998 by IFLA, the International Federation of Library Associations. FRBR specifies a data model for how MusicBrainz should be organized. If this is news to you, you should at least read Wikipedia's introduction. You can also read the full document from IFLA's website. If you google for FRBR there are plenty of easier-to-read presentations of the core ideas.

What it says

FRBR specifies a data model consisting of three groups of entities:

  • Products, i.e. books, films and records. These follow a hierarchy of four entities:
    • Works, e.g. the novel Robinson Crusoe by Defoe
    • Expressions, e.g. the written novel, a translation, a film script based on the novel, an illustrated abridged version for children
    • Manifestations, e.g. a print edition of this translation of that novel
    • Items or physical copies, worn and torn, one of three held by your local library, each having a unique inventory number
  • People or corporate bodies (i.e. artists, groups, record companies) responsible for each entity of a product, e.g. the author of a story, the translator, the printer, the publisher, the library that owns a copy
  • Subjects, e.g. events and places where the story takes place, the date when the book was printed, etc.

History

Despite this spec being almost a decade old, nobody in the library world has really implemented it yet. It is on the verge of becoming the "flying car" of library catalogs, a utopian dream never fulfilled. The Library of Congress catalog is still structured as a bunch of MARC records, which is little more than a 1960s digital equivalent of a 19th century card catalog. One reason for this delay is that FRBR doesn't specify who is going to do the job, it only says how it ought to be done. (And then the Y2K bug and dotcom crisis got in between.) Traditionally every library has a catalog of the books it owns. The idea that information about books (bibliography) could be separated from the local inventory was all new to libraries in the 1960s, when cooperative institutions like OCLC were born. With time these coops have started to act more and more like private monopoly suppliers that libraries depend on but really hate. Here, have some bibliographic data, the first samples are free, then you have to pay your soul, and we will supply your institution for the rest of its life. Throw in a lifetime subscription to the Encyclopædia Britannica as well.

Enter the 21st century and Wikipedia. The common knowledge needs not be owned by a monopoly supplier. Every private music collector and library can keep their local inventory in the shape of links to existing, shared information at MusicBrainz. Find an error, fix it in the shared pool, not in your local inventory. This is how OCLC and Gracenote work. Except that no single entity owns Wikipedia or MusicBrainz, because the contents can be copied freely by anybody. This answers the who question.

Unfortunately, Wikipedia and MusicBrainz were created not by the old experts whose life-long experience was summarized in the FRBR specification, but by some kids from the filesharing generation. And so we see a shortsightedly crippled data model with just albums, tracks, and artists, applied only to recorded music. That's not the final solution.