<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BibleTech Blog &#187; Uncategorized</title>
	<atom:link href="http://blog.bibletechconference.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bibletechconference.com</link>
	<description>Discussing the Intersection of the Bible and Technology</description>
	<lastBuildDate>Wed, 16 Nov 2011 19:27:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Selecting Bible Study Software</title>
		<link>http://blog.bibletechconference.com/selecting-bible-study-software/</link>
		<comments>http://blog.bibletechconference.com/selecting-bible-study-software/#comments</comments>
		<pubDate>Fri, 19 Mar 2010 23:07:09 +0000</pubDate>
		<dc:creator>Jonathon Blake</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.bibletechconference.com/blog/?p=851</guid>
		<description><![CDATA[This is some material that was originally  going to be in my talk The Ecology of e-Sword at BibleTech 2010. Data portability Are the same resources available for your: PDA; Cell Phone; Mobile Device; Netbook; Laptop; Desktop; Can content between those devices be synchronized? Laridian almost passes the “Data Portability” requirement. If your netbook, laptop, [...]]]></description>
			<content:encoded><![CDATA[<p>This is some material that was originally  going to be in my talk <span style="color: #000000"><span style="font-family: Tahoma"><span style="color: #0000ff"><span style="font-family: Tahoma"><em>The Ecology of e-Sword</em></span></span></span></span><span style="color: #0000ff"><span style="font-family: Tahoma"><em> </em></span></span>at BibleTech 2010.</p>
<dl>
<dl>
<dd>
<p lang="en-US"><span style="color: #ff0000"><span style="font-family: Tahoma"><span style="font-size: small">Data portability</span></span></span></p>
</dd>
</dl>
</dl>
<p><span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Are the same resources available for your:</span></span></span></p>
<ul>
<li> <span style="color: #081910"><span style="font-family: Tahoma"><span style="font-size: small">PDA;</span></span></span></li>
<li> <span style="color: #081910"><span style="font-family: Tahoma"><span style="font-size: small">Cell Phone;</span></span></span></li>
<li> <span style="color: #081910"><span style="font-family: Tahoma"><span style="font-size: small">Mobile Device;</span></span></span></li>
<li> <span style="color: #081910"><span style="font-family: Tahoma"><span style="font-size: small">Netbook;</span></span></span></li>
<li> <span style="color: #081910"><span style="font-family: Tahoma"><span style="font-size: small">Laptop;</span></span></span></li>
<li> <span style="color: #081910"><span style="font-family: Tahoma"><span style="font-size: small">Desktop;</span></span></span></li>
</ul>
<p><span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Can content between those devices be synchronized?</span></span></span></p>
<dl>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>Laridian</em></span></span><em> </em>almost passes the “Data Portability” requirement. If your netbook, laptop, and desktop run 32 bit Windows, it might “pass”. If your desktop is on a different OS, then it barely &#8220;fails&#8221;. </span></span></span> </dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>Olive Tree Software</em></span></span> offers products for most mobile devices, but doesn’t appear to offer a way to synchronize between them.</span></span></span> </dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>The Sword Project</em></span></span> offers front ends for more operating systems, and platforms than any other organization that delivers Bible Study Software. However, they currently don’t offer tools to synchronize between programs.</span></span></span> </dt>
<dl>
<dd>
<p lang="en-US"><span style="color: #ff0000"><span style="font-family: Tahoma"><span style="font-size: small">Future Proofing</span></span></span></p>
</dd>
</dl>
</dl>
<ul>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Can your existing resources be used on your new computer/mobile device?</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Can the resources that you create be easily imported into the program?</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Can the resources that you create be easily exported from that program?</span></span></span></li>
</ul>
<dl>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>Laridian</em></span></span><em> </em>almost passes the “Future Proofing” requirement. If your new<br />
platform is a mobile device, the odds are that they have a product<br />
for that device. They also offer <span style="color: #685558"><span style="font-family: Tahoma"><em>BookBuilder</em></span></span>, which enables one to create one’s original content as a resource for their software.</span></span></span> </dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>Olive Tree Software</em></span></span> &#8212;  the other player in the mobile device Bible Study Software market &#8212; offers specifications for <span style="color: #685558"><span style="font-family: Tahoma"><em>Olive Tree Markup Language</em></span></span>. What is not easilly discovered, is where, and how that markup language  can be used</span></span></span>. </dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>The Sword Project</em></span></span> offers a plethora of tools that enable one to create their own resources. It also offers tools that enable one to easily extract the data from the resources. All existing <span style="color: #000000"><span style="font-family: Tahoma"><em>Sword Project</em></span></span> resources can be used on any current<a class="sdfootnoteanc" name="sdfootnote67anc" href="#sdfootnote67sym"><sup>67</sup></a><sup> </sup>front end. The “catch” is that not all front ends are equal<a class="sdfootnoteanc" name="sdfootnote68anc" href="#sdfootnote68sym"><sup>68</sup></a>.</span></span></span> </dt>
<dl>
<dd>
<p lang="en-US"><span style="color: #ff0000"><span style="font-family: Tahoma"><span style="font-size: small">Resources</span></span></span></p>
</dd>
</dl>
<dt> <span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">The primary issue is: “Which Bible Study Program <span style="color: #000000"><span style="font-family: Tahoma"><strong>currently</strong></span></span><br />
offers the resources that your will use?<a class="sdfootnoteanc" name="sdfootnote69anc" href="#sdfootnote69sym"><sup>69</sup></a>”</span></span></span></dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><br />
</span></span></span></dt>
</dl>
<ul>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"> Not what resources they plan to offer.</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"> </span></span></span><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Not what resources are currently available<a class="sdfootnoteanc" name="sdfootnote70anc" href="#sdfootnote70sym"><sup>70</sup></a>.</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"> Not what tools are available for creating resources<a class="sdfootnoteanc" name="sdfootnote71anc" href="#sdfootnote71sym"><sup>71</sup></a>.</span></span></span></li>
</ul>
<dl>
<dt></dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>Laridian</em></span></span>, and, to a lesser extent <span style="color: #000000"><span style="font-family: Tahoma"><em>Olive Tree</em></span></span>, operate on the theory that people won’t be carrying around large digital libraries. “Large” means anything more than somewhere between 100 and 500 digital works. </span></span></span></dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><br />
</span></span></span></dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><span style="color: #000000"><span style="font-family: Tahoma"><em>Libronix</em></span></span> operates on the theory that 1 500 digital works in one’s library<br />
will constitute a “small” library. As such, they currently offer resource collections that cover most of the spectrum of Christian Theology<a class="sdfootnoteanc" name="sdfootnote72anc" href="#sdfootnote72sym"><sup>72</sup></a>.</span></span></span></dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><br />
</span></span></span></dt>
<dt> </dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Whilst more 10 000 user created resources<a class="sdfootnoteanc" name="sdfootnote73anc" href="#sdfootnote73sym"><sup>73</sup></a> are available<a class="sdfootnoteanc" name="sdfootnote74anc" href="#sdfootnote74sym"><sup>74</sup></a><sup> </sup>for <span style="color: #0066cc"><span style="font-family: Tahoma"><em>e Sword</em></span></span>, less than a third of them can be legally distributed<a class="sdfootnoteanc" name="sdfootnote75anc" href="#sdfootnote75sym"><sup>75</sup></a>. Roughly 500 have been officially distributed. The results of a poll on <span style="color: #0000ff"><span style="font-family: Tahoma"><span style="text-decoration: underline">e Sword-users.org</span></span></span><span style="text-decoration: underline"> </span>imply that the majority of <span style="color: #0066cc"><span style="font-family: Tahoma"><em>e Sword</em></span></span><em> </em>users have less than 300 resources installed on their system &#8212; a claim that Rick Meyers has made for years.</span></span></span> </dt>
<dl>
<dd>
<p lang="en-US"><span style="color: #ff0000"><span style="font-family: Tahoma"><span style="font-size: small">Tools to create Resources</span></span></span></p>
</dd>
</dl>
<dt> <span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">A pastor, preaching fifty new sermons a year, can publish a book every six months. If that content can be digitally published, in a format that<br />
integrates with the recommended Bible Study Program for the congregation, it is a win for both the congregation, and the<br />
pastor<a class="sdfootnoteanc" name="sdfootnote76anc" href="#sdfootnote76sym"><sup>76</sup></a>.</span></span></span></dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><br />
</span></span></span></dt>
<dt> </dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">The core issue here is whether or not users will experience any functional<br />
difference between the digital content that is distributed by their pastor, and that distributed by the program developers.</span></span></span></dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><br />
</span></span></span></dt>
<dt> </dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Molly Mormon, whose sole content creation is limited to taking notes at<br />
Church and Bible Study, can generate a significant amount of content<br />
over the course of time. Content that can be digitally distributed with others<a class="sdfootnoteanc" name="sdfootnote77anc" href="#sdfootnote77sym"><sup>77</sup></a>, for their edification.</span></span></span> </dt>
<dl>
<dd>
<p lang="en-US"><span style="color: #ff0000"><span style="font-family: Tahoma"><span style="font-size: small">How do you study the Bible</span></span></span></p>
</dd>
</dl>
<dt> <span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">I’m not going to list all of the different ways to study the Bible here. I<br />
am aware of roughly 200 different points of departure, in studying<br />
the Bible. </span></span></span></p>
</dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Most<a class="sdfootnoteanc" name="sdfootnote78anc" href="#sdfootnote78sym"><sup>78</sup></a> of those can be listed under one of the following:</span></span></span></dt>
</dl>
<ul>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Book, chapter, verse orientated;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Chronologically orientated;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Creed/Catechism orientated;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Original Language orientated;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Topically orientated;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Who/where orientated;</span></span></span></li>
</ul>
<dl>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Each of those points of departure requires a different set of functions, and resources.</span></span></span></dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><br />
</span></span></span></dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Does the software program offer:</span></span></span></dt>
</dl>
<ul>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The appropriate tools?</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The  appropriate resources?</span></span></span></li>
</ul>
<dl>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">For book, chapter, verse orientated study:</span></span></span></dt>
</dl>
<ol>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Do the Bibles contain the books that are canonical for your branch of Christianity<a class="sdfootnoteanc" name="sdfootnote79anc" href="#sdfootnote79sym"><sup>79</sup></a>?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Does the versification scheme reflect that of your<br />
branch of Christianity<a class="sdfootnoteanc" name="sdfootnote80anc" href="#sdfootnote80sym"><sup>80</sup></a>, or denomination<a class="sdfootnoteanc" name="sdfootnote81anc" href="#sdfootnote81sym"><sup>81</sup></a> within that branch?</span></span></span></li>
</ol>
<p>If  your study is chronologically orientated:</p>
<ol>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Do the tools assist you in</span></span></span><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"> locating texts of the same period in time?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Can you alter those tools, so that they reflect the chronology that one believes to be accurate, or to include passages that were omitted<a class="sdfootnoteanc" name="sdfootnote82anc" href="#sdfootnote82sym"><sup>82</sup></a>.</span></span></span></li>
</ol>
<p>If your study  you study is orientated along creed/catechism lines:</p>
<ol>
<li>Does it include the Creed or Catechism that you use?</li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Are the references within it also available as resources for that program?<br />
</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Are those references linkable from the creed or catechism?</span></span></span></li>
</ol>
<p>If your study is orientated along original languages, or linguistic analysis</p>
<ol>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Does it contain resources in the languages that you study<a class="sdfootnoteanc" name="sdfootnote83anc" href="#sdfootnote83sym"><sup>83</sup></a>?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Does it offer tools that help one do morphological analysis?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Does it offer tools that enable one to do linguistic analysis?<br />
</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">For advanced users, can all five requests laid out at the <span style="color: #0000ff"><span style="font-family: Tahoma"><em>SBL<br />
Bible Software Shootout</em></span></span> be easily  done?</span></span></span></li>
</ol>
<p>If your study is topically orientated:</p>
<ol>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">How do the available tools aid that process?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">How do the available tools hinder that process?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Do the available resources cover the topics you study?</span></span></span></li>
</ol>
<p>If you study is who/where orientated:</p>
<ol>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Is a list of all of the characters, both named, and unnamed, that are mentioned in the Bible, available?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Is a list of all places, both named, and unnamed, that are mentioned in the Bible, available?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Are these lists fully congruent with the one that you use in your study?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Are these lists congruent with your theology?  (Maps are especially susceptible to theological bias.)<br />
</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Do the provided tools enable one to see a timeline of the place, and the individual, simultaneously?</span></span></span></li>
</ol>
<dl>
<dl>
<dd>
<p lang="en-US"><span style="color: #ff0000"><span style="font-family: Tahoma">Accessibility</span></span></p>
</dd>
</dl>
</dl>
<p>What<span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"> functionality is lost by removing:</span></span></span></p>
<ul>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The keyboard;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The mouse;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The monitor;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The monitor and the mouse;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The monitor and the keyboard;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The keyboard and the mouse;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">The monitor, mouse, and keyboard;</span></span></span></li>
</ul>
<dl>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">If any functionality is lost by the removal of any, much less all of those, then the program is not accessible<a class="sdfootnoteanc" name="sdfootnote84anc" href="#sdfootnote84sym"><sup>84</sup></a>. If program functionality requires any of those items, then it should be rejected on sight, regardless of any other merits it might have. This applies regardless of any current accessibility requirements of the potential user<a class="sdfootnoteanc" name="sdfootnote85anc" href="#sdfootnote85sym"><sup>85</sup></a>.</span></span></span></dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small"><br />
</span></span></span></dt>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">For both the User Interface, and the resources, how easy is it for the user<br />
to change:</span></span></span></dt>
</dl>
<ul>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Fonts;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Font size;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Font background colour;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Font foreground colour;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Overall foreground colour;</span></span></span></li>
<li> <span style="color: #011d13"><span style="font-family: Tahoma"><span style="font-size: small">Overall background colour;</span></span></span></li>
</ul>
<dl>
<dt> </dt>
</dl>
<ol>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Does the program offer the ability to selectively magnify sections of the screen?</span></span></span></li>
<li><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Can every item on the menu be reached by a keystroke combination?</span></span></span></li>
<li> <span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Is the functionality of every icon instantly recognizable?</span></span></span></li>
<li> <span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">Are icon labels coherent<a class="sdfootnoteanc" name="sdfootnote86anc" href="#sdfootnote86sym"><sup>86</sup></a>?</span></span></span></li>
</ol>
<dl>
<dt> </dt>
<dt><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: small">#####<br />
</span></span></span></dt>
<dt> </dt>
</dl>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote67sym" href="#sdfootnote67anc">67</a> The specifications that define the file format used by <span style="color: #000000"><span style="font-family: Tahoma"><em>The Sword Project</em></span></span> have changed over the last decade. The front ends have not always incorporated those changes in file<br />
format specifications.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote68sym" href="#sdfootnote68anc">68</a> <span style="color: #292319"><span style="font-family: Tahoma"><em>Xiphos</em></span></span><em> </em>probably is best described as being the bleeding edge of <span style="color: #000000"><span style="font-family: Tahoma"><em>The<br />
Sword Project</em></span></span> front ends. </span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote69sym" href="#sdfootnote69anc">69</a> This is the virtue of the <span style="color: #0000ff"><span style="font-family: Tahoma"><em>Watch Tower Library CD (2008)</em></span></span>, for adherents of the<br />
theology of <span style="color: #000000"><span style="font-family: Tahoma"><em>the Watch Tower Bible and Tract Society</em></span></span>, or <span style="color: #0000ff"><span style="font-family: Tahoma"><em>LSD Library 2009</em></span></span>, for adherents of <span style="color: #000000"><span style="font-family: Tahoma"><em>The Church of Jesus Christ of Latter Day Saints</em></span></span>.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote70sym" href="#sdfootnote70anc">70</a> A critical edition of <span style="color: #0000ff"><span style="font-family: Tahoma"><em>Science and Health with a Key to the Scriptures</em></span></span> is of little use to those who do not study the writings of Mary Baker Eddy. </span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote71sym" href="#sdfootnote71anc">71</a> Whilst the ability to create one’s own resources is a virtue, the limiting factor is the amount of time one has to both learn how to create the resource, and then to create it.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote72sym" href="#sdfootnote72anc">72</a> Material on the fringes of Christian theology, such as Christian Atheism, and Christian Wicca is not represented in their resource collections. Nor have I been able to find any individual resources in those areas.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote73sym" href="#sdfootnote73anc">73</a> Resources for both Christian Atheism, and Christian Wicca can be found! </span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote74sym" href="#sdfootnote74anc">74</a> This refers to resources that have been publicly distributed at some point in time. It does not include resources that were never distributed by their creator.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote75sym" href="#sdfootnote75anc">75</a> Giving users the ability to easily create resources also gives them the ability to easily violate copyright law.  Whether or not providing that ability is “criminal conspiracy to violate copyright law” has not yet been tested in the courts. It is, however, a stick that publishers have considered using.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote76sym" href="#sdfootnote76anc">76</a> Roughly five years ago I studied some essays and sermons written by the pastor of the church I currently attend. About a year after I started attending my current church,  &#8212; three years after I studied that material &#8212; that I connected that material, with the pastor of my current church. </span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote77sym" href="#sdfootnote77anc">77</a> I am reminded  here of the spinster who, every year purchased a new leather Bible, and read it daily. At the end of the year, she gave her Bible to a pastor, so he could take advantage of the notes, markup, and other things that she had written in it, over the course of the year.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote78sym" href="#sdfootnote78anc">78</a> The points of departure that don’t fall into those six groups have their own separate, specific issues.  Nonetheless, the two fundamental questions remain:  Resources and tools appropriate to that specific point of departure.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote79sym" href="#sdfootnote79anc">79</a> Perhaps an extreme, but consider <span style="color: #0000ff"><span style="font-family: Tahoma"><em>The Ethiopiac Canon of Eighty One (Narrower Canon)</em></span></span>.<br />
AFAIK, none of the currently available Bible Study programs can “correctly” handle that canon.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote80sym" href="#sdfootnote80anc">80</a> Contrast the versification scheme of the Russian Orthodox Synod Bible, with<br />
that of the KJV<br />
</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote81sym" href="#sdfootnote81anc">81</a> For example, The German Lutheran Bible uses a versification scheme that is different from both the KJV, and the LXX/TR.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote82sym" href="#sdfootnote82anc">82</a> As one example, all of the Chronological Bibles I have used, omit <span style="color: #008000"><span style="font-family: Tahoma"><em>Psalm 151</em></span></span>.  Most of them also manage to place<span style="color: #008000"><span style="font-family: Tahoma"><em> John 1:1</em></span></span> at a fairly distant point in time from<span style="color: #008000"><span style="font-family: Tahoma"><em> Genesis 1:1</em></span></span>.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote83sym" href="#sdfootnote83anc">83</a> One of the issues within Aramaic Primacy, is that no generally accepted critical edition of the Peshitta exists. This lack hampers critical research in Aramaic Studies.  A side effect is that “missing” critical research, is that Bible Study Software developers are in the lurch, not knowing if the resources they do provide, are going to the “academic” choice in the near future, much less intermediate future.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote84sym" href="#sdfootnote84anc">84</a> I recognize that programming for this is very difficult. However, like most alternations that are done to enhance accessibility, those changes will have a greater impact on those who do not have accessibility requirements, than those that do.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote85sym" href="#sdfootnote85anc">85</a> Learning to use accessible hardware and software is a steep enough learning curve, without having to simultaneously learn to use software that replaces the old, inaccessible  software that one was using. </span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote86sym" href="#sdfootnote86anc">86</a> More than one popular program labels its icons as “icon1”, “icon2”, “icon3”, “icon4”.</span></span></span></p>
</div>
<div>
<p><span style="color: #000000"><span style="font-family: Tahoma"><span style="font-size: x-small"><a class="sdfootnotesym" name="sdfootnote87sym" href="#sdfootnote87anc">87</a> This footnote is for tracking purposes only.</span></span></span></p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.bibletechconference.com/selecting-bible-study-software/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Apple iPad Opens the Door for Innovation in Mobile Bible Study</title>
		<link>http://blog.bibletechconference.com/apple-ipad-opens-the-door-for-innovation-in-mobile-bible-study/</link>
		<comments>http://blog.bibletechconference.com/apple-ipad-opens-the-door-for-innovation-in-mobile-bible-study/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 23:33:39 +0000</pubDate>
		<dc:creator>Drew Haninger</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.bibletechconference.com/blog/?p=348</guid>
		<description><![CDATA[Along with technology blogs and Twitter feeds everywhere, Olive Tree’s office has been buzzing with excitement since Wednesday’s announcement of the new Apple iPad. The iPad is the latest device in the iPhone OS family, a tablet with iPhone’s familiar multi-touch interface, a larger screen, and massive possibilities for expanding what Bible study looks like [...]]]></description>
			<content:encoded><![CDATA[<p>Along with technology blogs and Twitter feeds everywhere, Olive Tree’s office has been buzzing with excitement since Wednesday’s announcement of the new Apple iPad. The iPad is the latest device in the iPhone OS family, a tablet with iPhone’s familiar multi-touch interface, a larger screen, and massive possibilities for expanding what Bible study looks like for mobile devices.</p>
<p>iPad is built on the iPhone OS (operating system), which means that iPhone BibleReader runs on iPad today. Here at Olive Tree, we downloaded the iPad emulator on Wednesday afternoon and got our first glimpse of BibleReader on the iPad’s new larger screen. BibleReader is one of the many apps that will transfer directly to iPad when it ships in March, so you can expect to see BibleReader for iPad available from day one.</p>
<p>But, of course, we’re looking to do more. We’re committed to bringing the best Bible Study experience to iPhone OS, which now includes the iPad. And iPad’s new features give us the room to dream big.</p>
<p>Olive Tree has always specialized in mobile technology, and we’re excited about the iPad because it signals the direction all mobile technology is headed—becoming powerful, flexible, and useful enough to fit more than one category, transcending the current boundaries between mobile computing devices and other computers.</p>
<p>And that’s where BibleReader is headed too. We plan to make the BibleReader experience far more than just reading a book. And we’re glad the new Apple iPad will give us the opportunity to create a deeper experience of the Bible.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.bibletechconference.com/apple-ipad-opens-the-door-for-innovation-in-mobile-bible-study/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How eBibleReading is Different from eBook Reading</title>
		<link>http://blog.bibletechconference.com/how-ebiblereading-is-different-from-ebook-reading/</link>
		<comments>http://blog.bibletechconference.com/how-ebiblereading-is-different-from-ebook-reading/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 23:27:06 +0000</pubDate>
		<dc:creator>Drew Haninger</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.bibletechconference.com/blog/?p=342</guid>
		<description><![CDATA[We&#8217;ve witnessed the release of Amazon Kindle, the Nook, Sony eReader, and other eBook reading devices, and now we&#8217;re waiting on the iPad with iBooks, Apple&#8217;s new ePublishing outlet. Some Olive Tree users have been wondering: What makes BibleReader different from Kindle and other eBook readers? The main difference is that BibleReader is tailored to [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve witnessed the release of Amazon Kindle, the Nook, Sony eReader, and other eBook reading devices, and now we&#8217;re waiting on the iPad with iBooks, Apple&#8217;s new ePublishing outlet.  Some Olive Tree users have been wondering: What makes BibleReader different from Kindle and other eBook readers?</p>
<p>The main difference is that BibleReader is <strong>tailored to the experience of reading and studying the Bible</strong>.  BibleReader is <strong>Bible-centric technology</strong>.  In contrast, reviewers have pointed out that Kindle is “<a href="http://www.useit.com/alertbox/kindle-usability-review.html">dominated by the book metaphor</a>.”  Kindle reads and handles almost exactly like a book (and not like a magazine, reference work, newspaper, or website).  If all you read is fiction, or linear non-fiction—books where you start on page one and read, page by page, straight through to the end, the way you’d read a novel—then Kindle and other traditional eBook readers may work well for you.</p>
<p>But as anyone who has done any Bible reading or study can tell you, that’s not the way most people interact with their Bibles. Certainly, reading the Bible from cover to cover is a valuable practice, and if you’ve never done it, you should try it at least once. But for many people, <strong>daily Bible reading and study takes place in primarily non-linear ways</strong>.</p>
<p>And that’s where the <strong>specialized features and usability of BibleReader</strong> come into play.</p>
<ul>
<li>Say you want to open your Bible to a specific place—not just the third chapter of the book of John, but John 3:16 exactly. BibleReader’s Verse Chooser lets you navigate quickly to any verse in the Bible.</li>
<li>Suppose you wonder how the word “spirit” is used throughout the Bible. BibleReader’s search function lets you look up every occurrence of the word “spirit” in both the Old and New Testaments. And when you scroll through the search results, it takes just one click to open the Bible of your choice to that verse.</li>
<li>What if you’re reading Nehemiah, and you need more historical background on the Temple and its importance in Jewish culture? BibleReader’s versified commentaries let you switch to the commentary of your choice that opens right to Nehemiah, or wherever you were reading in your Bible.</li>
<li>BibleReader’s split-screen reading makes commentary or other Bible reference works instantly available as you read—the two screens are linked so your commentary is always open to the right verse. Or you can use split screens to read two different Bible translations side-by-side.</li>
<li>Many Bibles have additional information like textual notes, cross-references, or Strong’s numbers. BibleReader includes hyperlinked notes that are available with one touch.</li>
<li>If you make a personal note on a specific verse in the Bible, you can access these notes in any Bible version, tied to the same verse.</li>
</ul>
<p>While you might not need any of these functions while reading an eBook, reading the Bible is a different story. BibleReader was created with the unique experience of Bible reading in mind, and its features are designed to let you get the most out of your Bible reading and study.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.bibletechconference.com/how-ebiblereading-is-different-from-ebook-reading/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: blog.bibletechconference.com @ 2012-05-17 15:45:12 -->
