Morbus Iff took an interest in FRBR a few years ago and began some work on it, making a start on a Drupal (a web site content management system) module that would use it: LibDB. As the datestamps show, he abandoned it, as often happens.
But he says, “I never stopped thinking about it.” In Drupal 7 and FRBR: A Mental Model, he puts down what he’s been thinking about regarding getting FRBR into the newest version of Drupal. (Which from what little I know is going to be really good.) It’s Drupal-heavy, so if you don’t use Drupal you might get confused.
Drupal 7 is “nearing” release and I’m once again thinking about FRBR. 7 now has the ability to add custom fields to its content types, functionality that previously required the contributed module CCK. While CCK, as a framework, had tons of additional third-party modules that mocked up different types of fields, Drupal 7 doesn’t, solely because it isn’t in the wild yet. I don’t consider this bad news, really, because I’ve always been of the opinion that most of the contributed modules available to Drupal are crap. They scratch itches, certainly, but very few of them are what I’d consider quality productions. So, for me, thinking about Drupal 7 and FRBR is thus constrained to “core” and “my own custom code”. Primarily, I’m interested to see just how much of FRBR could be modeled without custom code at all, so I’ve made some odd decisions to accentuate this. One could even accuse me of “just” making a boring old cataloguing system: regardless, I’m doing it with FRBR’s model fully in mind.