Scaling linked data workflows

Associate Librarian, Laurentian University

2018-05-01

Disclaimer: I'm an idiot

Big Blue(s)

A few words about my own interest in the subject: prior to joining the library world in 2006 I spent eight years at IBM working on relational database software for Linux, UNIX, and Windows. (And OS2!) As part of IBM’s Software Division, I was surrounded by web services and enterprise service buses, much of which was focused on solving business problems by wrapping legacy COBOL applications in Java beans so that the new wave of web-based applications could talk to systems originally designed for a green screen.

While I appreciated the pragmatic approach, and cynically understood just how much service revenue the corporation would continue to rake in keeping those legacy systems alive, part of me wanted those customers to just reimplement their systems on a nice, clean relational database so that the data could flow freely and easily.

Solo systems

schema.org, RDFa, and the ILS

Zed Thirty Nine Dot Fifty

"Adopting web standards rather than library-specific ones"

Manifesto for Linked Libraries (and Museums and Archives and …) / https://library.stanford.edu/projects/linked-data

"Strange women lying in ponds distributing swords is no basis for a system of government"

Monty Python and the Quest for the Holy Grail / https://www.wikidata.org/wiki/Q25043

Global Open Knowledge Base (GOKb)

Beyond BIBFRAME

Possible directions?

Z39.50 / SRU	SPARQL
SIP / NCIP	Linked Data Platform
Upstream updates	Linked Data Notifications
OAI-PMH	LDP Paging
User data	Solid

While avoiding the Innovator's Dilemma, what must we not leave behind?