Bodley MS 851

That’s, right, let’s begin with the Z-text.  For a first JSON post we are going to start with one of the earliest manuscripts, and I am going to do nothing but talk about JSON and describe the Z-text manuscript in valid JSON code.

So, to get going, let’s talk for a second about this horrifying acronym, “JSON,” which stands for Java Script Object Notation. JSON  is a simple way to store and send STRUCTURED DATA. It is typically used for allowing a web page to exchange data and messages with the server without the whole page having to refresh or update.  It’s simple, it’s complete, and it doesn’t interfere with your ongoing activity on a page but allows you to see more.  Think about things that pop up when you hover over an object, or a shopping cart that may show what’s in your cart without leaving the page you’re on.

Why JSON for data? Well, we are going to talk more about JSON-LD for linked data in the next blog post, but the simple answer is that it allows us to describe a real world object in code in such a way that the resulting script is BOTH human- and machine-readable.

I swear, it’s not scary at all.  Simple JSON often looks like this:


“name”: “Jane Medievalist”,

“institution”: “Medieval University”

“books”: [

“name”: “The Middle Ages Rock”,

“name”: “You wish you were medieval!”,

“name”: “So you think you can alliterate?”



What is this? Well, it’s a JSON Object, which we know because the whole thing is enclosed in the curly brackets { }. JSON operates on objects which can be as simple and elaborate as you like.  Today, I’m presenting the Z-text manuscript as a SINGLE JSON OBJECT.

Continue reading Bodley MS 851