SBL Greek New Testament

AMFBlog_FeaturedImage_SBLGNT

Wow!

The Society for Biblical Literature released a new text. While it may not seem big to most people, for biblical scholars, this may mark a critical point in the influence of technology on biblical studies as an academic discipline.

To paint a picture, here’s how fast the field has advanced in the past 30 years:

  • Prof. Margaret Mitchell, Dean of the University of Chicago Divinity School, wrote in the latest Circa that she used William Rainey Harper’s Greek textbook while studying for her PhD in the 1980s.  (Harper died in 1906)
  • I started using Greek computer software in my first year of undergraduate.  I’ve never had a “pure” Greek education where I only used paper resources (note: completely tongue-in-cheek).  In my 4 years of study, and 4 years now of non-study but casual reading, I’ve used two software packages, and I’m about to start using a third.
    • Gramcord was the first.  It was out of date, even when I started using it.  But it was still exciting.  Programmed by a true amateur (= one who loves it for its own sake), it didn’t need the latest bells and whistles of the newer operating systems to do its task.  I especially liked the morphology searches – as Daryl Schmidt taught me to use them on one of my exegesis papers on Mark.
    • Bibleworks was my second.  Ironically, it’s a Windows-only piece of software that I used on my slow Macbook running Windows XP in Parallels.  And even though it was slow, I loved copying and pasting to my note software (OmniOutliner).  In my “Old Testament in the Gospel of John” course, Prof. Klauck pointed that we could go through more of the cross references because I was quickly able to find  some of the obscure books.  Bibleworks was powerful, but I didn’t need it for most of its power.  The only time I taxed its processing power was to look up every reference of “ego eimi + article + participle” in its massive library of texts.
    • I’m looking for new software, but can’t decide which to pursue.  I’m working on so many different computers and platforms that none of them quite fit.  Heidi uses OliveTree reader on her iPad.  I’m looking at Logos and Accordance for my Mac, but am not willing to drop that amount of money for a software-based system.  I’m even considering a hybrid approach of Bibleworks on my Windows laptop and setting up a web service to pull texts when I need them.  (Although that would probably violate Bibleworks’ Terms of Service).
  • Until this SBL announcement, the current frontier I saw in technology for Biblical Scholarship was to complete the transition to Unicode formatting for texts.  I didn’t even know the SBL had a font (I’d always previously Gentium from SIL).
  • Now I’m wondering if the next frontier for technology in Biblical Scholarship will come from the computer science field.  One of my classmates in undergraduate studies at TCU is now doing his PhD at Carnegie Mellon and working on advancing language-analyzing supercomputer systems.  We may come to know more about the rhetorical patterns and wide variety of influences in the Hellenistic world from the studies of computer scientists than those of Biblical scholars.

What I find super-interesting about this announcement is that the SBL paired up with a commercial group to release the text.  Logos is a player, no doubt about it.  But I wonder what percentage of SBL members actually use Logos.  Those market share numbers would be interesting.

And I’m also thrilled that the released the raw text for free so other Bible software programs could use it.  Michael Hanel already ported the new critical text over to Bibleworks.

But now I wonder: is this just an opening in the floodgate of Biblical Criticism texts?  No doubt the Jesus Seminar could release the critical text they made for their latest project, The Authentic Letters of Paul?  Could each school create their own text?  I’m not saying the Nestle-Aland/United Bible Societies (and in particular the German Bible Society) should have priority or special ownership of the most commonly used edition.  But how will this release change scholarship?

Will it become as fragmented as our modern political discourse?  Will certain text choices shut off discussion amongst scholars?

In any case, the more accessible and high-quality texts, the richer the discussion.  I’m excited to start looking at some of the variances.

Launch – uppermidwestcc.org

AMFBlog_FeaturedImage_UpperMidwestCCLaunch

It’s hard not to have a love/hate relationship with my region’s website. I think every person who’s ever managed or designed a new version of it has this same love/hate relationship.

  • It lacks a clear audience. Presumably, the website is a resource for people who are already leading or worshipping with Disciples of Christ congregations in our four-state region. But it’s also for people looking for churches (either to move to or work at) from other parts of the country. Or it’s for non-Disciples wanting more collaboration, ecumenical partners. Or it’s for people looking for our great camping and conference center ministry. Or it’s for … (the list goes on).
  • Like the church, people think it should remain forever. To their point, I agree that permalinks and navigation shouldn’t break (often). But against their point — why do the registration forms for events three years prior still need to be accessible? And why is the website supposed to serve as a fixed repository, a place for them to dump all of their documents?!?
  • Often it’s at least 5 years behind the technology curve. And in many cases that’s not a bad thing. Churches who are “early adopters” with web technologies have to wade through the different compatibility issues their users face. They undoubtedly leave people behind. But five years ago, the big innovations were CSS and multiple device stylesheets. That’s what church websites should be current with now. Churches’ websites don’t need direct integration with mobile devices. (I, for one, don’t want to have to figure out how to program against the Blackberry calendar system …) Nor does our regional page need to be coded in the upcoming HTML5 bells and whistles; with so many of our users still on IE7, we can wait a couple of years to get there.

I built the latest version of the website on the Genesis Theme Framework put out by StudioPress. It’s optimized for search engines, it’s secure, and it has an amazing developer community behind it. It saved me a lot of hassle in migrating previous layouts, and it REALLY will save me time for future layouts.

This version of the website also marks a transition from Wufoo (the online form generator I recommend for churches), to Gravity Forms, a Wufoo-comparable AJAX WordPress plugin that is easier to embed in several places of the website at once. While Wufoo is awesome — I wanted something that was plug-n-play.

I’m not sure how long this version of the website will last. The previous version lasted 9 months, so I’d give this one at least 18 months before it needs another major overhaul.

Evolution of a Chalice logo

AMFBlog_FeaturedImage_ChaliceLogoEvolution

My denomination, the Christian Church (Disciples of Christ) almost treats our chalice as a sort of “flag pin.”  It can be our visual litmus test.  With so many congregations across the United States and Canada calling themselves “Christian Church,” we distinguish ourselves by our visual logo.  (Note: my reading on our church’s history is that our founders’ emphasis on unity would go against this litmus test — but, alas, we’re no longer the same group as when we began …)

There are many drawbacks to having this logo.  To read more about its history, visit the General Church’s page.  In practice, however, the logo is often confused as a MADD (Mothers Against Drunk Driving) logo.  The St. Andrew’s cross is interpreted as a mark of a rule or something forbidden.  Are people in our church allowed to take communion?  Not knowing the history behind the logo, you’d think the answer is “no.”  (The answer is an exclamatory “YES!,” but that’s one of our Gospel messages we’re still practicing).

So earlier this year I tried to find a way to “mess” with the Chalice to create a different studium:

  • I wanted its message to reflect our Region‘s identity: “Disciples Together”
  • It shouldn’t just involve communion — identity change through baptism is also who we are
  • At our core, Disciples know that our relationship to each other and to the whole church (beyond our brand of Christianity) is who we are
  • It must be scalable — large and small it should be clear who we are.

Here’s what I came up with. Click on the image for a full-sized version.

Even though I’ve marked the Final versions — I’m not sure it’s finished.  Several of my colleagues and fellow ministers said, “it’s fine, but what about our geographic location?”  I’ve worked with a version to make the shapes of our states (Iowa, Minnesota, South and North Dakota) into a table or plane that the chalice rests on.  But it still doesn’t quite work.

Launch – www.stbenedict.ws

St Benedict Launch Thumbnail

Stbenedict.ws Screenshot

Fridays — often a minister’s day of rest.

With my hybrid vocation, I often still work on Fridays.  And yet, the days still keep some of their retrospective character.  I can look back at my tasks for the week and give myself a sort of score card.

Publicly, I can share some of my recent work.

So, let me set the situation. In June I promised my wife a new website for her church by the end of the summer. Fast forward to the fourth week of August and I’m presenting a workshop at the School for Congregational Learning about congregational website setup and maintenance using WordPress. I get home from a long weekend and Heidi calls in the promise. The summer was almost over and she was missing a website.

Rather than doing everything custom, I retrofitted a stock theme (http://themeforest.net/item/light-of-peace-wordpress-template/120416) to work for her setting.

  • I replaced the logo with an “Episcopal” customized one with the Episcopal Shield.
  • I added a custom post type for events (treating events like taxonomies and as collections of posts so that any updates to event pages show up in RSS feeds).
  • Customized an RSS widget to automatically track the Revised Common Lectionary readings for the week from the Vanderbilt Divinity School Library’s website (http://lectionary.library.vanderbilt.edu/)
  • Some other UI tweaks of features that didn’t fit her congregation.

Thankfully, a team from her congregation transported most of the content from their old website to the new one.  They were also experts of this type of fall cleaning: they mercifully cut out lots of garbage or outdated information from the old website.

The site’s live at http://www.stbenedict.ws/

Source Control on the Mac

AMFBlog_FeaturedImage_CodaSubversion

Windows programmers have it easy. Not only are their compiler tools more robust (and therefore, full of infinitely more options — for better or worse), but Windows programmers have some easy network-able source control tools.

My team used to use Visual Source Safe, which came with Visual Studio. Even though it caused headaches and needed a database rebuild once, it was simple.

My team is now using Microsoft’s Team Foundation Server for some of our newer projects. Robust is just the start of the description. Team Foundation Server was crafted for collaboration.

So those are great for Windows programmers, but what am I to do with my Mac programming?

Here’re the needs:

  • Compatible with my Mac software: Coda (http://www.panic.com/coda/)
  • In the event of a crash, it’s the backup
  • So it has to be “off-site” (and not a local install of Subversion)
  • I don’t need the collaborative, syncing of latest versions (yet)
  • Free is good

So, even though the local install of Subversion is out, that’s still the best source control protocol for Coda.

The best walk-through I’ve seen for this setup is a video at: http://basementjack.com/uncategorized/video-coda-subversion-beanstalk-how-to/

Do any Mac programmers have a better setup?

I should also mention that I don’t do any compiling on my Mac. So I doubt this would work for XCode. I only use Coda.