Good question. For mathematicians and linguists, a graph is a diagram that consists of nodes and edges. For the rest of us, who must communicate using words that we hope others will readily understand, graphs are diagrams that consist of points and lines between them. For our purposes, any diagram that consists of points and lines is a graph.
You may have noticed I haven’t been blogging much lately. Mostly, I’ve been too busy working on the Andersen-Forbes Hebrew Syntax project. As part of that work, I recently went down to Melbourne, Australia to visit with Frank Andersen and Dean Forbes, the gentlemen themselves. It’s rare that the two of them are ever in the same room, since Dean lives in California and Frank lives half a world away in Melbourne. When we found out that Dean would be visiting Melbourne for a month to work with Frank, we decided that I should crash the party.*
Last week, I posted an article about “Word Groups” in the OpenText.org Syntactic Annotation. I promised some follow-up; and now it’s time for that.
There are obvious uses for this level of annotation in the realm of searching, but what about in just reading the text? Or in working through a passage exegetically?
The good news is that the visualization (graph) supports most operations you’re used to performing from a standard morphologically tagged Greek NT in Logos Bible Software. This article is about some of those options.
One of the neatest features supported in the next release of Logos Bible Software is the Biblical People database. It has been included in the alpha releases since the end of June, but I wanted to give everyone a chance to see it.
The example here shows a visualization of all of the biblically-attested relationships of Aaron. The graph shows everyone Aaron is related to and the nature of the relationship. Nodes in the graph are colored by gender, if known, and labeled by relationship. Every relationship is attested to by one or more Bible verses, shown at the left side of the graph. Clicking on a person’s name regenerates the graph with them at the center.
The graphs can be generated for any person in the Bible, and a specialized version of the graph is included in the Passage Guide to show all of the people in the selected passage and their relationships to each other.
Logos Bible Software is more than just an electronic version of a paper library. And it is tools like this that demonstrate how software can help you see and explore the Bible in ways you never could before.
Since Bob posted about the sentence diagrammer, I thought I’d follow that up just to let folks know that these groovy new syntax graphs we’re developing (see previous post) are able to be copied into the Sentence Diagrammer.
See? Click on each image to see what happens. The first image is a right-click and copy (the blue arrows and such indicate what is selected). The second image is the syntax graph pasted into the sentence diagrammer as a live object. Arrows are arrows; words are words. You can grab stuff and move it around.
Small disclaimer: The first graphic shows stuff like “add to general notes” on the right-click menu. At present, it is unclear whether we’ll support notes within these graph resources.
As mentioned in a previous post, the OpenText.org syntactic analysis consists of three primary levels of annotation:
- Base Level Analysis (Word)
- Word Group Analysis
- Clause Analysis
This post will introduce you to the Word Group level of analysis. If this sort of stuff floats your boat, then read on.
Searching on the name led me to a site with some other, older diagramming systems. The photo here shows Genesis 1:1 diagrammed by the Clark method. (Do we need to add support for this?)
The next release of Logos Bible Software will support flowing columns of text with user-adjustable margins and tabs. It is hard to explain but easy to use, and it is designed to support the outlining / phrasing / aligning / arcing advocated in some recent guides to exegesis. (These diagrams still support the line drawing objects, allowing you to mix shapes and flowing text.)
We are calling these “sentence flow diagrams,” after Gordon Fee’s description in New Testament Exegesis. But if you know a better or more accurate name, let us know!
I introduced a series of posts on upcoming Greek Syntax tools last week. This is the second post (first post after the intro, you haven’t missed anything) in that series.
We have two different data sets that will be made available. If you’re at either the ETS or SBL conferences in November, you can see them demo’d. To keep my sanity (and yours) I’ll only discuss one data set at a time.
This first series of posts will discuss the OpenText.org Syntactically Analyzed Greek New Testament, as implemented within Logos Bible Software.
Interested in utilizing syntax within your study of the New Testament? Read on!
Here’s another of Wendell Stavig’s questions to one of my earlier posts:
What is a MARC record?
MARC stands for Machine Readable Catalog, and is a Library of Congress standard way of specifying resource metadata, that is, information about the book. Think of it as an electronic card catalog entry. You could use the MARC record information to do a library search, and if you printed this information out and took it to your local library, your librarian would probably know what she was looking at, but mostly the MARC record represents cataloging information that is used by the Libronix DLS to help organize and find resources in your library.
If you want to learn more about the MARC format in all its splendor, the Library of Congress has a page for you. If you follow that link, I recommend that you refrain from operating heavy machinery for at least twelve hours afterward. Better make it twenty-four, just to be safe.
Anyway, this illustrates one of the things that sets the Libronix DLS apart from other Bible software programs: We really have built an electronic library, and not simply a Bible study program. To be sure, the Libronix DLS is an excellent Bible study program, but that’s not all it is; the features we’ve built for Bible study are simply specialized ways to access certain kinds of information in your electronic library shelves.
Say it with me: It’s not a program, it’s a library.
This is why, for example, we call books “resources” — a library has all sorts of resources, not just books. (So do we: A video resource isn’t a “book,” it’s … a video resource.) We are not tied down to presenting only one kind of information. Just like a library.
This is also why the My Library browser shows you not only the actual title of each book, but also alternate titles, popular titles, and any abbreviated titles we know about. You can type “Little Kittel” into the My Library browser to find The Theological Dictionary of the New Testament, Abridged in One Volume. Or you can find them by subject. Or by author. There’s more than one way to find the book you’re looking for.
Just like a library.
That article got long, and I promised to follow it up later. Well … it’s later. And this is the follow-up.
The Morphology Filter is good for word-level and paragraph-level work. That is, when you are reading through the text and noticing morphological trends, the Morphology Filter helps these sorts of things jump out at you.
Upon noticing what seems to be a concentration of a particular morphological criteria in a particular paragraph or section, the next question is: Does this happen elsewhere in the book, or is this unique? In other words, with the Morphology Filter, you’re looking at the trees (or perhaps a particular grove of trees). But you need to step back and look at the whole forest now. This is what Verb Rivers help you to do.
(Holding back the urge to mix metaphors and crack a joke about going “over the river and through the woods” … )