Tag Archives: Digital Bible Society

Multi-Lingual Digital Libraries

Responding to a friend’s email, we were asked what might be some of the best multi-lingual digital libraries? First, a small listing, then some reasoning to why this isn’t a separate page on this site (unlike the way we’ve done apps, resources, and services).

Reasons Why This Isn’t A Separate Page

When this question was asked, I remembered a conversation with the late WS Keel as to why this wasn’t out there already? Why is it that people have to search  far and hard to find a semblance of a library of digital content that works with various connected and mobile devices? My answer to him was quite simple: “a digital library is of no good use when there’s nothing to read it on.” MMM took the approach of pointing to mobile containers for this content. And left it to the greater digital-enabled Body to develop the hooks to connect content into these and former relevant media spaces.

The other reason that you don’t see this as a separate page is that there’s really not much in they way of local content except by a few providers. When you speak of audio content, much of it comes through Faith Comes By Hearing. They really are the leaders of audio biblical resources in this respect. That also means that if there’s work being done, its either under their umbrella, or overshadowed by the legal and logistical issues of being a small fish in a big pond.

Lastly, and most importantly, the legal issues. Instead of writing this again, I recommend the Copyright and the Kingdom (slideshow, PDF) from Tim Jore of Distant Shores Media.

Now, if there’s enough buzz from this post (probably from those libraries that I’ve missed), to make this a page to itself, I’ll do it. But, until the Body gets it together in several facets, we’ll continue to have a hard go of things finding not just multi-lingual Christian resources, but simply finding resources at all.

Content Submission

If you create content and would like to submit it for inclusion into any of these libraries, let me recommend that you do so to open libraries such as Open Bible Stories, Project Gutenberg, and Open Church. Its not that the others aren’t good, its just that they aren’t open to all of the world (yet).

7in of Near Perfection

iPad (1st gen) and Amazon Kindle Fire HD

There are just so many new gadgets out there, and for the most part, its a crazier world when it comes to tablets. For those who might have been coming from a PDA or eReader background, the idea of a 10in tablet is wrought with some significant risks (weight, platform lock-in, etc.) alongside the obvious gains. And so the 7in tablet begins to take some root as a potential alternative. From a physical standpoint, we’re talking about something with a bent towards reading (unless you’ve got a Samsung or HTC model with a stylus and those neat styli tricks). From a software perspective, we are mostly talking about Android (I’m still wishing for something solid to come from the Mer/MeeGo camp). And then from a usability and faith end, we get that really interesting ask of how this shape of device fosters a maturing faith perspective and a life lived in light of such perspectives.

I’ve recently purchased a Kindle Fire HD to potentially replace my 1st gen iPad. And while I’ve begun to note some of my impressions about it, I’m not yet completely comfortable giving the KF-HD all the work that I gave my iPad. These are different devices, and not everything that one tablet can do should be done on all others. At least how they have come across so far, the iPad is more of a canvas (you can’t do much until you add the paint of various applications), and the KF-HD is a catalog (the 21st century Sears/JC Penny catalog) – I dig into that distinction some on my personal blog.

Still, I can’t help but thinking that there’s a legitimate space for this size of device, and what we can continue to refine about our understandings about mobile as it relates to faith. For example, a few days ago Mobile Advance asked (via Twitter) something specific towards the Google Nexus 7 tablet for an upcoming African trip. Of note to his question was this ability to utilize a device in a mostly offline context. Here were some of the apps recommended in that conversation stream:

Essentially, these are apps which enable taking a 7in tablet and treating it more like a Moleskine notebook and not just a browser/ebook device. I don’t know that anyone can disagree with that perspective. But, its neat that in a device that is this size, that such a use-case isn’t so far away from normalcy. (And in rethinking about it, I forgot to mention a multi-language dictionary; too many years going online for those moments, whoops)

And besides that, you’ve got to think about how that shifts how you use your mobile device. In my case, having the KF-HD makes me use my smartphone more. I don’t know if its because I haven’t adapted to using it as easily as I have my iPad, or that its just faster to continue on this current workflow by using my N8 (and a recently acquired Lumia 900). I can see how someone who has a laptop and doesn’t want to remove that from their lifestyle will use a 7in tablet alongside a low or mid-range smartphone and be just fine in some of their computing pursuits. At least with the Kindle Fire/FireHD, I’m not sure that this is a perfect size to be a netbook/laptop replacement – even though the range of solid 7in tablets and their attending software points in that direction. I do think that its a near-perfect size though to replace a high-end smartphone and larger tablet. Which might make for some interesting decisions for many when it comes to costs of computing over time.

As with the iPad, I expect use and perspectives to mature over time with this new tablet. And to be honest, I’m not totally sold on it just yet either. Its nearly perfect, but as I’ve said in some other ramblings, my usage could be better done with a phablet (phone+tablet) like the Galaxy Note II, or a solution like the Asus Padfone 2. I’m a weird one though. My device choice here is honed for a question to be answered much later. For you, the 7in (or even 8.9in and 10in) tablets might fit your usage needs a bit better. Much like we’ve talked about building a Bible app from the perspective of a layman, not a pastor, there’s something to be said for a smaller screen that might fit the usage and mental models of a different type of person that just isn’t as widely heard. We’re listening for that here now, and whatsoever the results of adding this to the #mobmin utility belt might bring.

Apps, Services (and Skills?) for Serminaries

BibleWorks, Logos, and Accordance logo compliation
If you’ve been following along via Twitter recently (@mobileminmag), then you might have seen a few tweets in reference to articles posted at one of our favorite sites – Biblical Studies and Technological Tools (BS&TT). Certainly one of the oldest and most theologically grounded tech websites, BS&TT, there’s always the kind of content there that gets you to the point of readily applying tech in faith. Of note, a recent post took at look at a few applications relevant for the seminarian, but left also with a standing question about how other seminaries approach making the decision about which application(s) prefered for students’ learning. By the end of this piece, I questioned if its really an app (or service) that seminaries should steer towards, or should the skill of knowing how to build a Bible app be included into the curriculim.

Apps and Services for Serminaries

The BS&TT article mentions these, and we’ve added a few others from previous discussions:

These are only a few of the applications available. Check out our Bible apps page for a more exhaustive listing for several computiing devices and contexts.

Or, Should Seminaries Focus [Also] on Skills to Build the Ideal App/Service?
As mentioned earlier in this article, the BS&TT article left me with the question of “what specifically are these apps doing that is necessary to the study of, application to, and teaching of Scripture?” When I looked at it through this lens, the approach wasn’t that a specific application should be chosen, but perhaps seminaries should focus on those skills common to these applications. If this focus on those skills becomes the lesson, could it be a better lesson to teach how to build a Bible reader app suitable for use in seminary – engaging into the discussions that can better happen when you are closer to the publishing of the text, rather than the transcription of it?

Here’s my comment as posted with the BS&TT piece:

…Why aren’t you teaching folks how to build a Bible reader?

I understand that some of the issues related to Bible software has to do with not so much the content, but knowing the needed features for instruction, learning, and application. What you seem to be wanting here is some easier or more grounded means of teaching specific ways of using these software packages in studies. That doesn’t happen solely by concentrating on a specific package, but pooling their features, plus the needed skills, into something of a lesson.

If I could make the recommendation in this wise, it would be to take John Dyer and the DBS’s work with Browser Bible, and make that the introduciton to tech and Biblical studies, alongside Hebrew and Greek beginnings. To learn how to program the code that makes the letters appear, how to manage a websites oval website, and see directly the challenge of language support and user in traces, that’s what makes for the kind of core compentencies in the text that transcend just knowing an app or having a specific library.

Plus, you end up with a suite of folks who will know first hand the issues of restrictive licensing and publishing, which is every seminary’s real issue with the text as taught.

So, instead of learning the user interface as Logos/OliveTree/etc have designed it, you are learning how to build one that fits your contexts or concepts of learning. For example, with the base of HTML, CSS, and JavaScript, you could address the lack of non-English resources as you learn the

This is one of those discussions that ends up having two questions knit together:

  • What are some of the computing apps and services found to be helpful for those of you in seminary?
  • Should seminary policy focus on apps and the core skills between them, or the core features of using tech tools for Biblical studies and knowing how to build your own ideal environment?

I admit, this is a challenging topic. But, probablyh one worth having over the larger expanse of the wants and needs of techn tools for faith.

John Dyer and Digital Bible Society Introduce Bible Browser

Was meandering about the web when I saw a note from John Dyer speaking about a new(ish) project he worked on with the Digital Bible Society (DBS). Called the Bible Browser, its very similar to the apprach I’ve taken with the All Books Project in terms of making a Bible reader that is built with HTML, CSS, and jQuery. John’s a better coder (by a few country miles) than I, and there were several groups participating in this project, so the end result is a good bit more polished, and further ahead. Still, the Bible Browser represents what I think should be the base level of performace and integration we should be seeing in the use of HTML as a platform for publishing with the Bible starting as the foundation.

Here’s a bit more about the project from John’s announcement:

…Now, there are already lots of amazing Bible website and applications out there today built by wonderful Christian brothers and sisters, so it might seem unnecessary to build yet another Bible application. Each of these has a place in what God is doing in the world, but the software that DBS creates has some special requirements that necessitates something new:

  • Must be able to run without Internet access
  • Must be able to run without being “installed”
  • Must be able to run in any browser on any device

In a country where it’s illegal to follow Christ or ask about Christianity, installing Bible software and accessing Bible website are big no-nos, so this security is absolutely paramount. The best solution we have so far is to create an HTML/JavaScript application that runs on whatever browser the user has installed.

The challenged is that HTML-based applications can be a bit slower than full desktop software (like the awesome apps Logos, Accordance, or SWORD) and since we are designing them to run without Internet access (like the amazing YouVersion or Biblia) they can’t have a powerful server to do things like process search queries. This makes for some interesting programming challenges, but it’s also part of the fun of doing something different to serve the church at large. The app also needs to be able to run on very basic phones with limited HTML/CSS support, another fun challenge.

For those technically inclined, the basic setup is that each chapter of the Bible is a separate HTML file linked together by jQuery Mobile which makes browsing the Bible work really well on basic phones all the way up to iPhone/Android. Then a desktop application reads these same HTML files and uses them to produces the multi-pane application you see in the video above…

Very cool stuff. We’ve added it to the Bible Apps page and definitely want to encourage you to check out the Digital Bible Society’s website and support their efforts. John Dyer also has some other neat projects which are great to take a look into (Bib.ly, Bible Web App, etc.) and support.

Now, back to work on All Books… am encouraged to continue and persue this project’s direction.