#bibframe
BF Vibe 1.0.0 is out, my desktop app for creating BIBFRAME records.

Describe a resource in chat and get a draft BIBFRAME RDF/XML record. The record is checked against validation rules and notes where each part of the record came from and what is left for the cataloger. doi.org/10.5281/zeno...
November 15, 2026 at 1:35 AM
LOD is still being talked about in GLAM settings (see this week's SWIB conference: forum.swib.org/t/swib26-pro...), but the field has matured where specific applications of LOD ideas are often the focus (BIBFRAME, Wikidata, Linked Art, Sinopia, BlueCore) rather than LOD as a generic concept.
SWIB26 Programme
Monday, 16 November ℹ On Monday, five hands-on 🔨 workshops will happen spread over three time slots. To register your participation in a workshop click on the “Going” button on the respective worksho...
forum.swib.org
November 18, 2026 at 12:22 AM
Editing
At work I’ve spent a significant amount of time over the past year helping the Blue Core team re-engineer some of the Sinopia tooling. It really has been a privilege to return to some of the core ideas around Linked Data and cataloging, to see what has worked and what hasn’t. Part of this recent work has been ensuring that the RDF that is being stored in our PostgreSQL database as JSON uses the (brand new) bibframe-json JSON-LD context and schema. This may seem like a small thing, to store data consistently in a database. But unfortunately when you are talking about RDF data it’s not always a given. RDF supports many serialization formats, and even within a format, like JSON-LD, there are multiple ways to say the same thing. Some people think this is a strength of RDF in that it is a data model, rather than a particular data format. They’re not wrong. But when you are building tools to use the data and aren’t using a triplestore it is _extremely_ helpful to know the structure of the JSON when you want to parse it as JSON and use it, instead of needing to parse it as RDF and using the resulting graph. I’m really hopeful that the Blue Core project, in its use of bibframe-json, can provide a JSON friendly format for BIBFRAME data. It’s still early days as it’s just at v0.1, and there are already some things that could be improved. The Blue Core API follows the robustness principle in that its endpoints let you send BIBFRAME RDF in multiple serialization formats. However the received RDF data is framed and stored in the database with a specific JSON-LD context. This means users of the API can expect the BIBFRAME JSON-LD to look a particular way. This is super important for interoperability because it means clients using the data can just treat it like any other JSON that they would get from any other Web API, and not have to process it as RDF (unless they really want to). This isn’t a new idea. It’s called Linked Open Usable Data (LOUD), which Rob Sanderson distilled from the IIIF projects successful use of Linked Data. Having a consistent shape of JSON-LD opens some doors for experimenting with different BIBFRAME editors that don’t need to be RDF aware. They simply load and edit the JSON, and can use the JSON Schema as a guide for what is possible to say. One such experiment is the bluecore-editor. It was designed and coded relatively quickly (in a couple days) with Claude Code. When working with Claude to design bluecore-editor I started with (and evolved) a few design principles. I thought I would jot them down here, in case anyone else is interested in the experiment, and maybe creating their own. ## Records not Resources Catalogers think in terms of bibliographic and authority _records_ when doing cataloging. They can learn how to think in terms of BIBFRAME Works, Instances, and Hubs. But when they have a book in front of them, they are creating a single description, that happens to consist of several types of resources. The editor should _compose_ these resources into a single editing surface and not require them to edit resources separately, while holding the big picture in their head. So the editor is organized with a hopefully familiar ISBD layout, and the underlying resources can be revealed by clicking on a “Hints” toggle, which displays what properties are associated with Works, and which with Instances, as well as what the related BIBFRAME vocabulary term is. It even displays related MARC information for catalogers who are familiar with those. If you want you can see the resources visualized as a graph, where you click on each resource to see what it is. Which leads to the next point. ## But still, Resources! As that graph makes clear, when catalogers describe a book (or some other type of item) they use many resources, including authority records for people, organizations, subjects, and controlled vocabulary terms for languages, countries, relators, etc. These resources are all referenced using a URI (this is Linked Data after all). But catalogers need to see more than just the URI. They need to see a description of the resource to decide whether to use it or not. The “context pane” in bluecore-editor lets catalogers see information about these resources in the context of their work, as they need it, and doesn’t require an extra click and context shift to another browser window to do that. For example when editing this audiobook version of War and Peace you click on Tolstoy’s name, and see information from the LC Name Authority File, Wikidata and Wikipedia (if those links exist): One of the challenges here when editing one part of the description could impact other descriptions. The canonical example this is in Authority Control work when someone changes the subject heading or name authority which ideally would update all uses of the record, but more often than not means all those descriptions need to be updated. But knowing when a change could impact other descriptions is important, especially in BIBFRAME where editing properties related to a Work could impact its other Instances. That’s why the bibframe-editor notifies you, and asks for your approval, when one of your edits could impact other descriptions. I think this is why Linked Data is (still) a powerful concept for cataloging. RDF is really just a means to an end. The end-goal is for catalogers to be able to build up bibliographic descriptions by reusing, updating and creating bibliographic resources for people, topics, etc. ## Suggestions not Templates Templates (aka Profiles) in Sinopia have proven to be difficult to create, update and maintain over time. Templates do multiple things. They decide what assertions a description can contain, what the editing interface needs to show, and how it should behave. Profiles need to do these things as the resource descriptions and other profiles change. We have been trying solve this by _versioning_ templates and attaching them to the resources (instances, works, and hubs) that used them. This means that the minute that a template is updated, all the resources that used the template are instantly stale, and need some attention to bring them up to date. Templates can have sub-template references, which compounds these problems. When a child template changes that change then ripples up to a change its parent. _bluecore-editor_ takes a different approach by analyzing existing BIBFRAME records from LC to build up a statistical profile of what vocabulary terms have been used with what resource types. It then uses this information as a set of _Suggestions_ , by type (book, map, etc), when the cataloger is working. The editor also includes _overrides_ which allow you to suggest something that’s not common, or remove something that is not desired. But suggestions are ultimately driven by cataloging practice rather than top-down rules. This is just an experiment at the moment, and not meant to replace Sinopia Editor. But I’m hopeful that the ability to use consistently shaped JSON from the Blue Core API, without needing to understand RDF will unlock other use cases, and bluecore-editor is just one example. I’m also hopeful other projects that want to use BIBFRAME, and want to use JSON, will find their lives made a bit easier. If you have ideas please get in touch in the issue tracker.
inkdroid.org
November 15, 2026 at 3:03 PM
These are the same people who have been panicking about Folio and Bibframe.
November 5, 2026 at 7:00 PM
Oh thanks! Fairly old at this point, maybe I should update it. A lot of current good bibframe info at our new primer doc: bibframe.org/docs/view/do...
Documentation Tool
bibframe.org
October 25, 2026 at 2:46 PM
Immersed in a #BIBFRAME course (from @libjuiceacademy.bsky.social) and this Visualisation of the BIBFRAME 2.0 data model has blown my mind!
Credit: @thisismattmiller.com
medium.com/@thisismattm...
Diagramming Bibframe 2.0
The LC Bibframe 2.0 data model contains close to 200 classes and a similar number of properties. I was interested in trying to visualize…
medium.com
October 23, 2026 at 10:41 AM
Eh eh, y FRBR y BIBFRAME?
October 18, 2026 at 10:00 PM
From @ed@digipres.club: Yesterday I gave a talk about BIBFRAME data that was secretly just a way to socialize the idea of using JSON Schema to make interoperability feasible. If you have any practical use for this idea please get in touch?

inkdroid.org/2026/10/01/s...
Shipping BIBFRAME
October 1, 2026 json libraries data bibframe
inkdroid.org
October 2, 2026 at 8:07 AM
📚 A novel, its paperback edition, and your library’s copy are different things.

BIBFRAME from @librarycongress.bsky.social models them as Work, Instance, and Item—bringing library catalogs into Linked Data.

openknowledgegraphs.com/resource/bib...

#LinkedData #Libraries
BIBFRAME - Open Knowledge Graphs
data model and vocabulary for bibliographic description
openknowledgegraphs.com
October 2, 2026 at 2:35 AM
Shipping BIBFRAME
Yesterday Kevin Ford and I gave a presentation (slides) at the LD4 conference about the use of BIBFRAME “bounded descriptions” at the Library of Congress (LC) and in the Blue Core project. BIBFRAME data is RDF that gets serialized in many different ways. One of the challenges of building tooling around BIBFRAME is that you don’t necessarily know if you have to follow your nose in the data (resolve URLs) to get some of the data, or if it will be present in the data you have in hand. This may seem like a small thing, but when you are building BIBFRAME editors, or doing a large bulk loading operations (as LC and the Blue Core project are doing) it is helpful to have it on hand. The _bounded description_ is a convention for making certain information available in the BIBFRAME data. The initial idea for the talk was to describe some interoperability problems that we experienced when loading data that had been designed for XML processing in a RDF processing centered workflow. But rather than focus on those specific problems it shifted instead to talk about the role of bounded description for interoperability more generally. The bounded description aside, one thing that fell out of this work for me was the importance of having a JSON schema for BIBFRAME. You might wonder why on earth you would want a JSON Schema for BIBFRAME RDF data – wouldn’t that be overly prescriptive, since RDF can be represented using XML, JSON, Turtle, N3, etc? The answer is yes, and that is completely the point. Following along with the principles of Linked Open Usable Data (LOUD), it is extremely useful for tool building purposes to have a clear idea of how the JSON-LD is structured. Even within JSON-LD there are many ways of representing the same exact RDF graph. Working with this variety of serialization formats requires tools to use an RDF parser. For some in the Linked Data community this isn’t a big deal. But most people working with data on the Web are used to loading some JSON with their programming language’s JSON support, and interacting with it like a data structure: hash maps, lists, strings, integers, etc. If they can’t reliably do that it is a major interoperability problem. If BIBFRAME is really going to replace MARC I think it’s important to let the ontology and RDF serializations exist, while providing a strict and easy to use representation for the many people who aren’t engaging at that level. The bibframe-json site is brand new. We are storing JSON-LD in the Blue Core data store, and making it available via an API. But we aren’t actively using this schema (or any other) for validating the data on the way into the data store…at least not yet. The schema was developed rapidly with Claude Code, mostly as a provocation for the LD4 talk. It’s my (probably unpopular) belief that if we can’t represent BIBFRAME data using JSON Schema then BIBFRAME really isn’t going to see widespread adoption, ever. I’m sure that there ways for this initial version to be improved. If you have ideas or suggestions please consider contributing to the work, or get in touch with me directly.
inkdroid.org
October 1, 2026 at 2:57 PM
Cataloging and digital collections bluesky: Anyone migrated special collections into Bibframe yet? I'm interested in looking at the underlying LOD.
September 30, 2026 at 7:55 PM
Sinopia BIBFRAME Editor can be used to more clearly express the relationships between 'Bound-withs' - moving from a flat MARC record to a more three-dimensional model - BUT still waiting for Alma to support BIBFRAME Items - on the roadmap for 2027! #RLUKDSF
September 30, 2026 at 1:39 PM
Now Alison Hazelaaar and Kim Taylor form @leedsunilibraries.bsky.social speak about the @exlibrisclvt.bsky.social Linked Open Data Working Group to explore the potential of #BIBFRAME & using #WIKIDATA to complement NACO. #RLUKDSF
September 30, 2026 at 1:31 PM
BIBFRAME enables relationships to be more clearly stated, and copy-specific information can be recorded at the Item Level #RLUKDSF
September 30, 2026 at 1:34 PM
This will only work if a critical mass of Libraries get behind it & work together to enhance Linked Data Entities into a connected ecosystem - Linked Data will eventually replace MARC (via BIBFRAME) but collaboration & investment is essential for libraries to move forward coherently #RLUKDSF
September 30, 2026 at 1:28 PM
Had a fun time connecting with the library linked data community again: hdl.handle.net/2142/133605
September 29, 2026 at 11:17 PM
#LinkedArt mention in the #LD4 presentation on adapting Bibframe to describe manuscripts and other cultural heritage objects.
September 28, 2026 at 3:44 PM
Ah the side-quests we engage in when we are not copy editing our dissertation: A hub family explorer testing out hugging face storage capabilities and observable: jimfhahn-bibframe-hub-explorer.static.hf.space/hub-family-e...
BIBFRAME Hub family explorer
jimfhahn-bibframe-hub-explorer.static.hf.space
September 19, 2026 at 12:32 PM
Hubo un congreso sobre BIBFRAME la semana pasada y parece que viene fuerte y con intención de sustituir las catalogación en MARC21 en las bibliotecas.
September 14, 2026 at 8:35 AM
BIBFRAME in Europe Workshop 2027 will be 8-9 Sept at Trinity College Dublin in Ireland! - Stay tuned to www.bfwe.eu for more details #bfwe2026
BIBFRAME Workshop in Europe
The aim of the BIBFRAME Workshop in Europe is to be a forum for sharing knowledge about the practice of, production with, and planning of BIBFRAME implementation.
www.bfwe.eu
September 9, 2026 at 2:31 PM
"Bridging the Gap: Implementing BIBFRAME in Small-
Staff Environments" with Joanna M. Fuchs, Brandeis University.
Shifting from MARC21 to BIBFRAME presents hurdles for smaller metadata or cataloguing teams, even in an English-speaking, Global North context.
#bfwe2026
September 9, 2026 at 1:01 PM
Of interest to #metadata professionals wondering about #BIBFRAME implementation alongside adoption of #OfficialRDA with the retirement of Original RDA Toolkit occurring in May 2027 #libraries #cataloguing #LinkedData
"Mapping from RDA to BIBFRAME: Logistical and Technical Issues" with Chris Holden, Library of Congress and RDA Steering Committee.
RDA: Resource Description and Access is a package of data elements, guidelines, and instructions for creating library and cultural heritage resource metadata
#bfwe2026
September 9, 2026 at 2:36 PM
This is partly to try and get BIBFRAME closer to the WEMI structure that the library community has become used to via the LRM & RDA (& previously FRBR) - there is a risk here that we may end up reproducing the complexity of MARC that BIBFRAME was designed to reduce #bfwe2026
September 9, 2026 at 2:18 PM
We have to think about production continuity - sustaining MARC21 cataloguing for daily acquisitions alongside competency development that shifts mindset to graph-based linked data concepts in BIBFRAME #bfwe2026
September 9, 2026 at 1:04 PM
This is what keeps me up at night... how we get ~200 years' worth of very variable MARC collections metadata 'ready' for conversion to BIBFRAME without any additional staffing resource #bfwe2026
There is a need to evaluate legacy MARC21 records to ensure that older, pre-RDA records are upgraded ahead of BIBFRAME transformation. #bfwe2026
September 9, 2026 at 1:20 PM