<div dir="ltr">Chris:<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote"><span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">The version of the tagged OT text at <a href="http://github.com/openscriptures" style="color: rgb(0, 0, 204);" target="_blank">http://github.com/openscriptures</a> is also in
very good condition (prob better than the one at Crosswire). It appears
to only contain PD data - ie it doesn't include the more complete
morphology data which is copyrighted. </span><br></blockquote><br>FYI, Strong's tagging is just the first step; David Troidl, Daniel Owens et al are cooking up a full openly-licensed morphology for the Hebrew Bible as well.<br>
<br>On the group we had talked about releasing all of the Open Scriptures data under Creative Commons Attribution-ShareAlike (BY-SA); David, could you add a README to the MorphHB project root explaining this? Or was it your intention that it would be Public Domain without any Attribution or Share Alike condition?<br>
<br>Weston<br><br><br><div class="gmail_quote">On Wed, Apr 21, 2010 at 4:07 PM, Chris Burrell <span dir="ltr"><<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Daniel<div><br></div><div>I'm copying David IB from Tyndale House who is part of Tyndale House and leading the data side of the project. </div><div><br></div><div>A couple of emails have circulated on this previously on our blogs, which I've tried to capture (in part) on</div>
<div><a href="http://crosswire.org/bugs/browse/TYNSTEP-44" target="_blank">http://crosswire.org/bugs/browse/TYNSTEP-44</a></div><div><a href="http://crosswire.org/bugs/browse/TYNSTEP-45" target="_blank">http://crosswire.org/bugs/browse/TYNSTEP-45</a></div>
<div><br></div><div>I'm sure David IB will have more to input on this... I've copied his original email below</div><div>Chris</div><div><br></div><div>==========================================</div><div><span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">THis is the best lookup lexicon to use for Hebrew interlinear - it is tagged to Strongs, includes the pointed Hebrew and has an abbreviated BDB entry. And the version downloadable from <a href="http://github.com/openscriptures" style="color: rgb(0, 0, 204);" target="_blank">http://github.com/openscriptures</a> has even more corrections than mine. For all I know, it might finally be letter perfect! THis version is also packaged in nice XML which can easily be converted to any other DB format. <br>
<br>The equivalent lexicon at Crosswire for Greek is, I think, in a much better state, and didn't need all the work the Hebrew did. <br><br>The version of the tagged OT text at <a href="http://github.com/openscriptures" style="color: rgb(0, 0, 204);" target="_blank">http://github.com/openscriptures</a> is also in very good condition (prob better than the one at Crosswire). It appears to only contain PD data - ie it doesn't include the more complete morphology data which is copyrighted. <br>
<br>David IB</span></div><div><br></div><div><br><br><div class="gmail_quote">On 21 April 2010 23:22, Daniel Owens <span dir="ltr"><<a href="mailto:dhowens@pmbx.net" target="_blank">dhowens@pmbx.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Chris,<br>
<br>
I am not qualified to contribute code (though I lurk on sword-devel because of my module-creating disposition), but I am involved in producing content for the very purpose you mention. By the way, if you are at Tyndale House now, you may know Daniel Block. He is my PhD mentor at Wheaton College.<br>
<br>
There are two content areas with which I am involved and would be happy to collaborate on. One is Greek and Hebrew lexica. Currently at <a href="http://www.textonline.org" target="_blank">www.textonline.org</a> we are involved in collaboratively producing a modern replacement for Strongs. We're starting with a Strongs base but hope to provide a basic and up-to-date modern equivalent to Holladay for Hebrew or Newman for Greek, except that they will be released under a creative commons license. The challenge is finding people to contribute quality entries with little or no possibility of accolades in the guild of biblical studies (and certainly no money!). The other project is a collaboratively produced morphologically tagged Hebrew text (see <a href="http://www.OpenScriptures.org" target="_blank">www.OpenScriptures.org</a>). For that we are looking at Django and Pinax as the applications for collaborating on putting together the data. For me, the purpose of this is to fill a void of content for SWORD in order to serve the global church.<br>
<br>
I notice that full-text lexicons are part of the second phase of your plan. Is there any way we can begin to collaborate on that? I am open to your suggestions.<br>
<br>
Daniel<br>
<br>
On 4/21/2010 2:07 PM, Chris Burrell wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
*What is Tyndale STEP?*<div class="im"><div><br>
Tyndale STEP is an offline and online Java web application which aims to make ancient texts and maps as well as timeline data, genealogies, ... accessible to everyone, scholar and non-scholar alike, so that the Bible is illuminated by its full ancient context. [see roadmap below]. Tyndale House will also distribute the online version to pastors in the third world, who often cant afford commercial Bible software.<br>
<br>
A wiki page has been set up here: <a href="http://crosswire.org/wiki/Frontends:TyndaleStep" target="_blank">http://crosswire.org/wiki/Frontends:TyndaleStep</a> which has a lot more information!<br>
<br>
*Who are we looking for?*<br>
We need lots of help!<br>
*Java developers*: this code base is mainly in Java so we can do with all the help we can get!<br>
*User Interface designers*: there is currently a sketch of the user interface, created more to prove a point. We need proper guidance to make the software as user friendly and rich as possible<br>
*Data harvesters*: Tyndale House could do with a few extra pairs of hands to helpcollate the data and make it available to the wider CrossWire community<br>
<br>
*How do I start?*<br>
Get in touch!<br>
Read through the wiki page: <a href="http://crosswire.org/wiki/Frontends:TyndaleStep" target="_blank">http://crosswire.org/wiki/Frontends:TyndaleStep</a><br>
Build the code from: <a href="http://crosswire.org/wiki/Frontends:TyndaleStep_Build_Environment" target="_blank">http://crosswire.org/wiki/Frontends:TyndaleStep_Build_Environment</a><br>
Check out our feature/bug repository: <a href="http://crosswire.org/bugs/browse/TYNSTEP" target="_blank">http://crosswire.org/bugs/browse/TYNSTEP</a><br></div></div>
Have a look at the proof of concept sketches at <a href="http://crosswire.org:8080/%7Echrisburrell/" target="_blank">http://crosswire.org:8080/~chrisburrell/</a> <<a href="http://crosswire.org:8080/%7Echrisburrell/" target="_blank">http://crosswire.org:8080/%7Echrisburrell/</a>> (including timelines and interlinears on strong-tagged Bibles)<div>
<div></div><div class="h5"><div>
<div></div><div><br>
Peruse the blogs mentioned on the wiki to get a feel for the data and programming<br>
<br>
As you can see, theres plenty to do!<br>
<br>
*What does the roadmap look like?*<br>
<br>
*/1st phase: build a multi-platform structure for standard Bible-study tools:/*<br>
Bible texts, including original languages, translations and interlinears<br>
Language aids, including lookup-dictionaries concordance searches<br>
History tools, including an expandable timeline with scripture links<br>
Dictionary articles, culled from various sources and edited<br>
*/<br>
/*<br>
*/2nd phase: add detailed geographic, historic & linguistic data/*<br>
Gazetteer of all named places, with short articles and links to pictures<br>
Co-ordinates of identifiable places to GoogleEarth<br>
Map overlays of high-ref 1:20,000 maps of pre-urbanised Palestine<br>
Flexible timelines which can be altered at key points of uncertainty<br>
Full-text lexicons linked to the lookup dictionaries in tagged texts<br>
<br>
*/3rd phase: add translation aids and links to modern publications/*<br>
different possible translations for words and passages<br>
differences in manuscripts, with evidence for each variant<br>
expositions in modern and older commentaries, articles and books<br>
<br>
*/4th phase: adds link to extra-biblical literature with searching:/*<br>
search other ancient literature for similar passages in a similar context<br>
look up Greek and Hebrew words in other ancient literature<br>
view ancient texts with translations where possible<br>
<br>
These tools will put centuries of research into the hands of non-scholars. When the information is laid open like this, it is easy to see that the Bible is well preserved and translated, reflecting historical events in real places, and dealing with issues current in the ancient and modern work alike.<br>
<br>
If you have any more questions or want to get involved, please do let me know!<br>
Chris<br>
<br>
<br></div></div></div></div>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote>
</blockquote></div><br></div>
<br>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br></div>