A weblog following developments around the world in FRBR: Functional Requirements for Bibliographic Records.

Maintained by William Denton, Web Librarian at York University. Suggestions and comments welcome at wtd@pobox.com.


Confused? Try What Is FRBR? (2.8 MB PDF) by Barbara Tillett, or Jenn Riley's introduction. For more, see the basic reading list.

Books: FRBR: A Guide for the Perplexed by Robert Maxwell (ISBN 9780838909508) and Understanding FRBR: What It Is and How It Will Affect Our Retrieval Tools edited by Arlene Taylor (ISBN 9781591585091) (read my chapter FRBR and the History of Cataloging).

Calendar

February 2008
M T W T F S S
« Jan   Mar »
 123
45678910
11121314151617
18192021222324
2526272829  

7 February 2008

FRBRoo 0.9 draft

Filed under: FRBRoo — William Denton @ 7:01 am

FRBROO draft 0.9 (1.1 MB PDF), or, more formally, FRBR: Object-Oriented Definition and Mapping to FRBRER (version 0.9 draft), came out last month but I just found out about it.

This document is the draft definition of FRBR (object-oriented version, harmonised with CIDOC CRM), hereafter referred to as FRBROO, a formal ontology intended to capture and represent the underlying semantics of bibliographic information and to facilitate the integration, mediation, and interchange of bibliographic and museum information. Such a common view is necessary to provide interoperable information systems for those users interested in accessing common or related content. Beyond that, it results in a formalisation which is more suited for the implementation of FRBR concepts with object-oriented tools, and which facilitates the testing and adoption of FRBR concepts in implementations with different functional specifications and different environments. It applies empirical analysis and ontological structure to the entities and processes associated with works, to their properties, and to the relationships among them. Thereby it reveals a web of interrelationships, which is also applicable to information objects in non-bibliographic arenas2, and is useful to justify the need of information elements in different environments.

(Thanks to Tim Knight for the pointer.)