Over a decade after the peer reviewed citable edition of the Amos commentary was published, and after several false starts and a lot of unproductive work, I am returning to explore the possibilities for e-commentary.
One thing that has changed for the better is that now OSIS (Open Scripture Information Standard) is more firmly established. It will allow the material coded in such a way it can be shared across, and used within a number of Bible software front ends. Screenshot below shows a mockup of some commentary on Amos 1:1.
One thing that has not changed1 is that OSIS is infernally difficult to code and no convenient tool exists to let anyone but a markup geek work with the markup.
I am learning lots, I now know about modern Bigendians and why they are dangerous to meet. I am discovering the delights of disappearing titles and the vagaries of front end designers, more than I ever thought I’d want to know about file formats and relative paths… One detail I learned is that if you put a BOM where you should not everything blows up. But that is not why everything blew up this afternoon, I still have to discover that new piece of information!
If anyone reading this knows of a decent way for a human (who is not a markup geek) to compose text in OSIS markup I would be delighted to hear from you!
As part of my preparation I have been rereading my old papers describing how I envisaged the project a decade or a decade and a half back, in case anyone else would find them interesting I am uploading them to Academia.edu here are the 2004 ones I have been looking at recently:
- (Editorial) “Prophets, losses and electronic communication“, Stimulus, 2004, 12:3, 1-2
- “Hypertext Bible Commentary and Encyclopaedia: a New Zealand-based international electronic publishing project“, Stimulus, 2004, 12:3, 43–48
- “Hypertext and Publication in Biblical Studies” SBL Forum [http://sbl-site.org/Article.aspx?ArticleId=261]
- As far as I know so far. If you know otherwise PLEASE tell me! [↩]