Showing posts with label Selecting Biblical Software. Show all posts
Showing posts with label Selecting Biblical Software. Show all posts

21 December 2011

Picking a Bible App for your Smart Phone.

Picking up Kevin Purcell's blog on this title.
Http://www.kevinpurcell.org/1530/how-to-pick-a-bible-app-for-your-smart-phone-or-tablet/
He makes a good point in dividing apps into three groups:
* Bible Readers;
* Digital Bible Study;
* Public domain only material;
I haven't kept count, but the majority of so-called Bible applications I've come across are of the third type. There is nothing wrong with public domain content.  However, i've seen some extremely expensive packages for content that is available gratis in other formats.
The biggest difference between his list of recommended software, and mine is:
# The Sword Project: He excludes it. I include/highly recommend it;
* Accordance: He includes it. I exclude it, because it is not cross-platform. Mac OS X and iOS version. [Correction added after commentator pointed out my error.];
* WordSearch: He includes it. I exclude it, because it is not cross-platform. Windows only. Mobile device versions are under development;
* Mantis Bible: He includes it. I exclude it, because it is iOS only;
% GloBible: He includes it.  It has not hit my radar. Looking at the website: Mac, PC, iPhone, iPod touch, iPad.  What they mean is Mac OS X, WinXP/Vista/7, and iOS.  The website is amazingly silent on the theological bias of the maps. It is equally silent on the supported canon;

14 December 2011

Selecting Biblical Software: Future Proofing

A New York Times editorial ( http://www.nytimes.com/2010/06/20/opinion/20sun4.html ) pondered on replacing cell phones. Clouds cites thirty three months as the life expectancy of a cell phone. ( http://www.cloudsmagazine.com/cellphone-reviews-and-news/the-spanish-mobile-home-to-nearly-two-and-a-half-years.html )

Laptops and desktops are routinely replaced every three to five years. Those who want the latest and greatest will update their system at least once a year. When the computer is replaced, the operating system and software is replaced. The file format used by the older software is usually not readable by the newer software. In some instances, a program update can remove the ability to read data.

Hard copy books are expensive. Nobody denies that. Even at thrift stores, a 1,000 volume theological library will set one back between two and three thousand dollars. Purchased new from CBD, one's wallet will be at least ten thousand dollars lighter. Purchased elsewhere, one could easily be down twenty to thirty thousand dollars. However, with a hard copy book, the book is mine to use as I see fit. If I want to decorate it with ten thousand different colours, I can do so. If I want to add so many notes to it, that I can't read the original text, I can do so. If I want to give it away, I can do so. If my great-niece wants to study it, she can do so.

With software, and data for software, what is sold is a license to use the material. One does not own the content in any meaningful, or even meaningless way. (I'm aware of the Denver Federal Court of Appeals ruling that implies that when one purchases a DVD from Target, one purchases the copyright to all of the content on that DVD. That unfortunate ruling is best described as an aberration by judges who failed to understand both the facts of that specific case, and the law that was being argued by the defendant. There have been repeated demonstrations that the plaintiff knowingly and wilfully attempted to mislead everybody.)

By licensing content, and refusing all rights, with the possible exception of viewing the content, the license holder can require the licensee to do anything. As Amazon has demonstrated, that includes removing content from one's system. (The other major book whose removal would starkly emphasis the plot, would be removing Fahrenheit 451.)

A "safe bet" is that your next computer will require software that is incompatible with your existing computer.
Two things to note:
  • What an organization claims about its software need not be objectively factual;
  • Two programs with the same name, but run on different platforms, need not have anything in common;
Whilst some organizations that provide software for three or more different platforms, also provide tools to migrate between those platforms, that does not mean that all resources will be migrated. Those tools are useful only if both your old platform, and your new platform are supported by the vendor. The cost of that migration can range from gratis to effectively repurchasing the entire library again.

For all practical purposes, there is only one organization1 whose data can be relied upon, to migrate smoothly from your old platform, to your new platform: The Sword Project. This is a function of:
  • TSP supporting more platforms than any other organization;
  • Copyright holders being terrified of the ramifications of Open Source Software;
Even more important than migrating to a new platform is: "What happens if your vendor goes out of business?" Will you still be able to use your software?

If the resources are on your system, and the software to use it does not require a call home, then you will be able to use the software:
  • If the resource is in the virtual cloud, it won't be available for you to use when the cloud is not available. Your Internet connection might be down. The Internet connection of the virtual cloud vendor might be down. Internet congestion might delay packets so much that the system times out;
  • If the software requires calling home, Microsoft has repeatedly demonstrated that even legitimate, authenticated software can be mis-labeled as "pirated", simply because the authentication systems are down, or otherwise functioning incorrectly;
Taking another common situation. You've spent hours studying the Bible using the software. Can you easily export your work product into an ISO certified file format, for use elsewhere? (The short answer to that answer is "no", because none of the currently available Biblical software supports ISO certified file formats.)
Alternatively, can you export your work product into something that can be easily converted into an ISO certified file format, without losing either presentation markup, or semantic markup?
For clergy, and those employed by religious organizations, the inability to export work product to another file format, might put them in breach of their contract with their employer. For those employees that don't have written contracts, some case law in the United States supports the legal theory that the intellectual property rights of your work product are owned by the organization that hired you, and as such, your failure to turn over that work product, regardless of the reason for that failure, means that you have stolen their property.

I am not a lawyer. This is not legal advice.

1 A second option is to write your own Biblical software, and port it to your new platform, as appropriate.

21 September 2011

Selecting Biblical Software: Data Portability

PDAs, as stand alone devices are, for all practical purposes, dead. Arguably single function electronic devices, such as GPS units, eBook readers, and mp3 players, are dying.

Phones have become multi-function devices.  Carriers differentiates between three types of phones:
  •     The dumb mobile phone;
  •     The feature phone;
  •     The smart phone;
Mobile cell phone carriers are phasing out the "dumb mobile phone". This phone can make and receive phone calls and text messages. The feature phone is the low end version of a phone with PDA functionality. The smart phone is the high end version of a phone with PDA functionality.

"Mobile Device" is a catch all phrase that refers to any device that has Internet connectivity, does not require an external power source, and can be easily carried. It includes, but is not limited to mobile phones, PDAs, Tablets, netbooks, ebooks, and laptops.

Tablet: These are mobile devices that have a touch screen.  The most common tablets run either Android Operating System, or iOS.

Netbook.  The original definition of a netbook was a low cost, low power device that could be used anywhere.  Microsoft, in a self-admitted abuse of its monopoly, redefined the term, to try to prevent the widespread adoption of Linux.

Laptop: These are computers that do not require an external power source. Mac OS X is the most common operating system in this space.

Desktop: These are computers that require an external power source. Typically, they have more RAM, and more disk storage space that laptops. Desktops are sold with Windows Operating System due to contracts that grant extremely unfavourable terms to OEMS that ship systems without a Microsoft operating system.

Cloud Server: These are computers that serve up applications to you. Typically, the server is controlled by a third party. Linux is the most common operating system in this space.

Game Console: This are units that are specifically designed for playing games. Examples are the Wii, x-Box 360, and Sony Playstation 3.

Are the same resources available for your:
  •     PDA
  •     Cell Phone
  •     Mobile Device
  •     Tablet
  •     Netbook
  •     Laptop
  •     Desktop
  •     Cloud Server
  •     Game Console
Can content be synchronized between two, or more devices?  

Whilst the question is aimed at users of, say, a tablet, and a desktop, it also applies to users with a desktop at home, and a desktop at work.

Ideally, the tool resides on one device, and enables transmission to the other device, without going through any network that is not owned, controlled and operated by the user.

Does that synchronization require the assistance of a third party?

With the rise of third party vendors such as DropBox, it has become fairly simple to synchronize between devices of the same type.

The problem with third party vendors, is that your data may not stay private.  Whilst a copy of the NIV, or KJV probably won't be damaging, personal notes could be extremely damaging.  The things that an individual struggles with.

Laridian offers tools to ease the migration between devices.  These tools can also be used to synchronize between devices. The downside is that Laridian confines itself to the mobile device space.

Olive Tree
offers a clear migration between devices.  They also appear to offer synchronization between devices. However, like Laridian, they confine themselves to the mobile device space.

Logos: The 800 pound gorilla in the Biblical Software market.  They offer a version for Windows Operating System, Mac OS X, iOS, and Android. Their current expectation is that one will use either Mac OS X, or Windows Operating System, on one's major device.   Android and iOS devices are viewed as secondary devices. Whilst it is possible to use Logos exclusively on one of the two latter, one loses a number of the virtues of the desktop edition.  Furthermore, some copyright holders have not allowed their content to be distributed on specific platforms.

The Sword Project offers more front ends, for more platforms, than any other organization that delivers Biblical software. It does not provide tools to migrate between platforms.  It does not provide tools to synchronize between platforms.  The documentation does cover ways to easily do both functions, using basic command line operations.

The need for data portability is driven by the number of platforms that are available to one.  If one only has one device, then there is nothing to synchronize with.  One either has the device, or does not have the device.

The problems occur when one has two or more devices. The resource may be on a device that one does not have with one.  Transferring notes may require rewriting them by hand. How frequently these issues occur, depends upon how frequently one uses two or more different devices.

There are two different ways that data portability can be defined:
  • The same file format is usable on all platforms;
  • The same content can be converted between platforms;
The Sword Project is an example of the same file format being usable on all platforms. This approach usually restricts software to the limitations of the least powerful hardware that it can be run on.

Laridian data portability is achieved through the use of vendor supplied and based conversion software.

Pocket e-Sword/e-Sword data portability is achieved through the use of user provided conversion software.

I have a desktop computer, and smartphone. These devices run different operating systems.  I use e-Sword on the desktop, and Pocket e-sword on the smartphone. However, if it was not for the availability of Ben's e-Sword Tool v 2.0, I would not be able to migrate resources between e-Sword, and Pocket e-Sword. I was given a Xoom for my birthday. I have to use yet another Biblical software program for that device. There is software that  converts between e-Sword and MySword. It can run on either the Xoom, or the desktop. This is data portability by using user provided conversion software.

Were I to switch to Bible Time or Xiphos on my desktop, SwordReader or Bible Time Mini for the Smartphone, and AndBible on the Xoom, then the data portability is achieved through the use of the same file format.

15 August 2011

Selecting Biblical Software: Software License


Software License

For users, the issue is what the license permits, and prohibits. It is all too easy to click through a license, when installing new software. US Courts have consistently upheld that click-through licenses are legally binding. 

Select software that allows one to do the type of Bible Study one desires.

The Terms of Use of The Watchtower Library CD states
2. Who may have a copy of Watchtower Library? This is a research tool for Jehovah's Witnesses, not for the public or for institutions such as schools or libraries.

Obviously this restricts individuals that are not Jehovah's Witnesses from using this software.

A clause from the license for Bible Analyzer:
Bible Analyzer must not be used to criticize, undermine, subvert, or in any way question the accuracy and integrity of biblical Christianity or the Authorized King James Version of 1611 or 1769.
The Watch Tower Bible and Tract Society, The Holy Roman Catholic, and Apostolic Church, and The Living Stream Ministry all claim to practice Biblical Christianity.  The theology of those three groups is so different from each other, that one might not realize that they used the same source, to come to their mutually exclusive conclusions.

Consider the License Agreement for The Scroll, Multimedia Study Bible for Window. (http://web.archive.org/web/20090326043014/http://www.abu.nb.ca/ecm/products/copyrigt.htm)
ADDENDUM. The Software may be used for educational purposes in schools and Churches for teaching and instructional purposes only. Requests for quotations in excess of 2,000 words must be directed to and written approval received from Electronic Christian Media, 19 Dresden St. Riverview, NB E1B 3G8
Does that clause permit you to use the Biblical software where you teach others?


In other Biblical software I've seen clauses about payment of property tax, legality of using the software, and non-commercial usage, amongst other things.

Read the license carefully. Understand what words, phrases, clauses, sentences, and paragraphs mean. If you don't understand something, find out what it means, before accepting the license.

11 August 2011

Selecting Biblical Software: Biblical Canon Supported

Expanding upon Point One in Criteria Set One of 
http://sword-and-scabbard.blogspot.com/2011/08/selecting-bible-study-software.html.

Biblical Canon Supported

I use the Orthodox Christian Canon. As such I consider the absence of support for the Anagignoskomena to be a bug. 


For those that use the 66 Book Protestant Canon, the presence of support for the Anagignoskomena is often considered to be a bug.


Which Biblical Canon to support, is the prerogative of the developer of the Biblical software. 

If the Biblical software does not support the Biblical canon that one uses, then one can not grow in the Lord, by using that software. That sounds harsh, but consider the following examples of hypothetical Biblical software:
  • Support is present for the Torah, Psalms, and Gospels. No support for other books, because the developer, following the teachings of his faith, considers them to be heretical;
  • Support is present for the 22 Book Peshitta.  No support for other books, because the developer considers them to be heretical;
  1. How well can you teach the core principles and articles of your Christian faith, using either of those canons?
  2. How much better equipped would you be, to teach the core principles and articles of your Christian faith, using the Biblical canon of your faith?

Therefore thou, O Lord, God of the righteous,
hast not appointed repentance for the righteous,
for Abraham and Isaac and Jacob, who did not sin against thee,
but thou hast appointed repentance for me, who am a sinner.
PrMan 1:8 RSVA
 

Selecting Bible Study Software

Since I've been asked twice in the last week why I don't use Bible Study Program X, it seems appropriate to blog once more about selecting Biblical Software.

Criteria Set One:
  • Biblical Canon Supported;
  • Software license permits one to use it for what one intends to use the software for;
Criteria Set Two:
  • Data Portability;
  • Future Proofing;
  • Currently Available Resources;
  • User Created Resources;
  • Cross Platform Support;

Criteria Set Three: Bible Study Methods:
I'm aware of roughly 500 different ways to study the Bible. Most of them fall into one of the following six categories:
  • Book, chapter, verse orientated;
  • Chronologically orientated;
  • Creed/Catechism orientated;
  • Original Language orientated;
  • Topically orientated;
  • Who/where orientated;
How many of those points of departure are supported out of the box by the software?

Criteria Set Four: Accessibility:

What functionality is lost by removing:
  • The keyboard;
  • The mouse;
  • The monitor;
  • The monitor and the mouse;
  • The monitor and the keyboard;
  • The keyboard and the mouse;
  • The monitor, mouse, and keyboard;
Criteria Set Five: The 2009 SBL Bible Software Shootout:

These were the five challenges each presenter had to address:
1. Give the parsing of a word and its meaning from a standard source.
2. Show all the occurrences of a word in the NT and LXX and show the Hebrew word which corresponds with the Greek in the LXX (if there is a correspondence).
3. Find all the occurrences of oi de in Matthew’s gospel followed by a finite verb within the clause.
4. I want to study a part of speech, e. g., demonstrative pronouns or interjections. How do I get all of the lemmas for that part of speech, get all the occurrences of those lemmas, and the results organized in such a way that I could write an article/monograph on that part of speech from the data?
5. I want to study the inflections of the Hebrew middle weak verb, and I want to see what the range of possible variations is for each of the conjugations (perfect, imperative, etc.) person, number, gender, and stem. This means I need to find all the middle weak verbs, find all their occurrences, and organize them in such a way that the variation of their inflections are immediately apparent. The goal of the data organization would be to allow me to write an article about the variations of the Hebrew middle weak verb


In future posts, I'll expand upon each point in the first four sets of criteria.