Monday, January 10, 2005
Bible texts for the hypertext commentary ::
I should have started blogging this earlier, but just before the holiday I remembered to ask Zack if it was OK...
Seeing his Greek NT has started me thinking again about how we handle the provision of texts for the Hypertext Commentary. In the Amos prototype I have manually linked the text to small wordstudies. But for the "real thing" something like Zack's Greek NT set up would be close to ideal, if we could make the Bible open in one window (frame) and the lexicon etc. in another. I have begun a conversation with Zack about this.
What can we do for the Hebrew Bible though? The obvious answer is to do a similar job on the Westminster Hebrew Morphology Database. I have written to Steve Vanderhill, but we may have problems because the commentary does not yet, and may never generate an income to pay royalties - we'll see what he replies.
Another option would be to produce an open source/open access database of our own. For example each commentator could be asked to do the coding as they prepare comment, but this involves (a) reinventing the wheel and (b) authors in significant work, of a (computer) technical kind. Or we could do it as an open project...
I have also written to Steve Amato about the morphologically analyzed LXX.
¶ 10:02 AM
[to Del.icio.us]
I should have started blogging this earlier, but just before the holiday I remembered to ask Zack if it was OK...
Seeing his Greek NT has started me thinking again about how we handle the provision of texts for the Hypertext Commentary. In the Amos prototype I have manually linked the text to small wordstudies. But for the "real thing" something like Zack's Greek NT set up would be close to ideal, if we could make the Bible open in one window (frame) and the lexicon etc. in another. I have begun a conversation with Zack about this.
What can we do for the Hebrew Bible though? The obvious answer is to do a similar job on the Westminster Hebrew Morphology Database. I have written to Steve Vanderhill, but we may have problems because the commentary does not yet, and may never generate an income to pay royalties - we'll see what he replies.
Another option would be to produce an open source/open access database of our own. For example each commentator could be asked to do the coding as they prepare comment, but this involves (a) reinventing the wheel and (b) authors in significant work, of a (computer) technical kind. Or we could do it as an open project...
I have also written to Steve Amato about the morphologically analyzed LXX.
¶ 10:02 AM
[to Del.icio.us]
