This is not the RDF you're looking for

One of the strangest things about RDF is that it is a data model that can be serialized using different data formats (XML, JSON, Turtle, n-triples etc). Sometimes the same graph can even be expressed differently using the same data format: so like different flavors XML or JSON for the same RDF graph. This plurality of serializations can often work to nudge users (of the data) into a situation where they feel like they MUST use an RDF processing library, even in cases where they would otherwise much rather reach for a more familiar parsing library that is core to the language they are writing code in. At work I’m part of a project where we are loading publicly available BIBFRAME RDF data from the Library of Congress into a database. The database is Postgres and we’re storing the RDF as JSON-LD using Postgres’ support for JSON. As we are storing the JSON we compact and frame the JSON-LD so that it has a consistent shape. It is my hope that this processing will help make the BIBFRAME…