I just heard from Tobias Klein this morning that version 0.2 of the Ezra Project is now available on his production server. A couple of weeks ago I reviewed the Ezra Project, focusing on the innovative Scripture outlining tool. Now Tobias has released a tagging tool, along with a bunch of small but pleasing enhancements to the look and feel of the site. The tagging tool lets users create their own tags for each verse of the Bible -- it gives the user an interface to explore the Scriptural topics that they have found in their own reading and study. As Tobias says on his development site, his goal is to "help you to work with the Bible and end up with real study results." Unlike other Bible software packages that give you the results of other people's study, the focus is on letting each user develop their own Bible study content.
As an editor of Bible reference content, I know the value of reading Bible study materials written by others, as my own understanding of Scripture has been enriched enormously by using commentaries, Bible encyclopedias, and original language study tools of all kinds. At the same time, I know the value of creating my own annotations as I read -- it is a way for me to wrestle personally with the text of Scripture. So I am enthused to see what Tobias Klein is doing with the Ezra Project, and I wish him godspeed in his efforts.
Monday, April 12, 2010
Wednesday, April 7, 2010
Social Sharing and Biblical Interpretation
As our society has moved into the dialogue of interactive social media, people's use of Bible texts has become more fragmented and decontextualized, and is less and less controlled by what would be considered a "valid" interpretive process. This was the topics of the second part of Elizabeth Drescher's BibleTech 2010 session entitled "People of the Facebook." (In a previous post I reviewed the first part of this session.)
To set the context for this part of her talk, Dr. Drescher quoted Thomas Arundel, who was Archbishop of Canterbury at the beginning of the 1400s, who decreed that "no man, by his own authority, translate any text of Scripture into English or any other tongue." His concern was that theological error would creep into people's use of Scripture, and that the magisterial authority of the church would be undermined by private interpretation.
So in light of these pre-modern concerns about "private interpretation," Drescher looked at the use of Bible texts on three platforms: iPhone, Twitter, and Facebook.
On the iPhone, there are more than 400 Bible-related apps, and all different kinds of lenses are being applied to Christian Scriptures. For example, there is a Buddhist Bible, which selects Bible texts and interprets them through the lens of Buddhism. There is no central control on the interpretation of Christian Scripture -- anyone can interpret the Bible in any way they please.
On Twitter, a lot of people are tweeting the Bible text (you can find out more about this from Steven Smith's BibleTech talk, Tweeting the Bible). Elizabeth Drescher has noticed two things: (1) A lot of "private interpretation" is going on -- people are interpreting Bible texts in all kinds of ways, without regard for the textual or historical context in which the verses of the Bible were written (she gave as an example of this Jana Riess's Twitter feed, where she is summarizing each chapter of the Bible in a single tweet, from her own perspective). (2) There is not a lot of interaction of Twitter -- people are just broadcasting.
On Facebook, there is more interaction taking place. Drescher looked at three examples of Bible fan pages:
On all of these platforms, people are using Bible texts in a fragmented, de-contextualized fashion -- individual verses, interpreted apart from their textual or historical setting, and apart from the church, which functions as a community of interpretation. What can help people to interpret the Bible in a more "valid" way, according to accepted principles of hermeneutics (interpretation)?
Here Drescher introduces the "Wikipedia Effect", stating that the greater the general interest in the content, and the more textually and visually developed the content, and the more editorial access people have to the content, the greater the factual accuracy and critical quality of the content. Simply put, get more people interested, and more people involved, in developing shared understanding of Bible texts together, and the result will be higher accuracy and quality in what is being said.
I am interested in the development of an online platform for the co-creation of Bible-related content. But I have some questions:
To set the context for this part of her talk, Dr. Drescher quoted Thomas Arundel, who was Archbishop of Canterbury at the beginning of the 1400s, who decreed that "no man, by his own authority, translate any text of Scripture into English or any other tongue." His concern was that theological error would creep into people's use of Scripture, and that the magisterial authority of the church would be undermined by private interpretation.
So in light of these pre-modern concerns about "private interpretation," Drescher looked at the use of Bible texts on three platforms: iPhone, Twitter, and Facebook.
On the iPhone, there are more than 400 Bible-related apps, and all different kinds of lenses are being applied to Christian Scriptures. For example, there is a Buddhist Bible, which selects Bible texts and interprets them through the lens of Buddhism. There is no central control on the interpretation of Christian Scripture -- anyone can interpret the Bible in any way they please.
On Twitter, a lot of people are tweeting the Bible text (you can find out more about this from Steven Smith's BibleTech talk, Tweeting the Bible). Elizabeth Drescher has noticed two things: (1) A lot of "private interpretation" is going on -- people are interpreting Bible texts in all kinds of ways, without regard for the textual or historical context in which the verses of the Bible were written (she gave as an example of this Jana Riess's Twitter feed, where she is summarizing each chapter of the Bible in a single tweet, from her own perspective). (2) There is not a lot of interaction of Twitter -- people are just broadcasting.
On Facebook, there is more interaction taking place. Drescher looked at three examples of Bible fan pages:
- "The Bible" is a fan page with 2 million fans. On this page, there is thoughtful and meaningful engagement both with the text of Scripture and with others.
- Another page called "The Bible" (which I wasn't able to find) is a fan page with 30,000 fans. Here, there is only affirmative, non-critical interaction with what is being posted.
- A third page called "The Bible" belongs to an individual and has only a limited exchange of texts
On all of these platforms, people are using Bible texts in a fragmented, de-contextualized fashion -- individual verses, interpreted apart from their textual or historical setting, and apart from the church, which functions as a community of interpretation. What can help people to interpret the Bible in a more "valid" way, according to accepted principles of hermeneutics (interpretation)?
Here Drescher introduces the "Wikipedia Effect", stating that the greater the general interest in the content, and the more textually and visually developed the content, and the more editorial access people have to the content, the greater the factual accuracy and critical quality of the content. Simply put, get more people interested, and more people involved, in developing shared understanding of Bible texts together, and the result will be higher accuracy and quality in what is being said.
I am interested in the development of an online platform for the co-creation of Bible-related content. But I have some questions:
- What kind of platform can support the creation of shared Bible-related content? Something like Wikipedia with Bible references?
- Can we really suppose that having more people interact with the Bible text and edit the Bible-related content will result in higher accuracy and critical quality? I have my doubts, but perhaps the answer is to find a set of "rules," such as Wikipedia has (e.g., everything must be backed up by published citations), which will provide some kind of control on content without preventing all kinds of people from editing.
- How can get people from a variety of traditions to work together and to come together in a shared interpretive space? Or will people divide up into different "communities of interpretation" online? I see such divisions as highly likely if an open & shared Bible-related content system is developed.
Labels:
BibleTech,
interpretation,
social-media sharing
Tuesday, April 6, 2010
The Social Logic of Communication
Most of the sessions that I attended at BibleTech 2010 were focused on technical matters, but one of them was focused on humanity. Elizabeth Drescher's session, "People of the Facebook," addressed sociological issues around the use of digital technologies, and how this use impacts the interpretation of biblical texts. These are important issues that we need to think about and discuss as we dive more and more deeply into the use of digital technology, because as Dr. Drescher said, we are currently going through a digital reformation. Drescher is a professor and Director for the Center for Anglical Learning & Leadership at Church Divinity School of the Pacific, one of the official seminaries of the Episcopal Church of America.
She tackled this issue from an historical angle, explaining the development of "the social logic of communication," showing the relationship between communications technologies and the types of social interactions that these technologies have promoted.
One thing that Drescher didn't address is the fact that we now have print, broadcast, and digital communication cultures all overlapping, co-mingling, and interacting -- with no sign that any of these communication media and cultures is on the wane. The doomsayers say that print publishing is dying, but I expect that we will print more, not fewer, books in the future. I also expect both radio and t.v. to continue and thrive for a good long time. What I am interested in discussing is, what is the social logic of communication in a culture that contains all three of these approaches? Drescher also talked about how different types of communication have traditionally been associated both with people of different developmental ages, and with different social classes. She aligned these with the classical trivium of the liberal arts, as follows:
How does all of this affect what we do in digital Bibles? Some reflections:
We need to enable a greater level of dialogue and interaction around Bible texts and Bible-related texts in digital contexts. In the first 20+ years of Bible software, all digital interactions with the Bible have taken place offline in "desktop Bible software." In the first 10+ years of the web, there have been Bible texts online, but very little means of interaction -- most of this has been broadcast-only. Now, with the rise of social media, more and more people are sharing Bible texts with each other online and discussing them. There are problems with this -- problems that Drescher discussed in the second half of her talk, which I plan to review next time.
We need a way for people to have coherent dialogue in a coherent textual context -- so that their dialogue and interaction around the texts is not divorced from the texts, and the texts are not fragmented by being shared. Some online Bible sites have the ability for users to add their own comments on the text -- YouVersion seems to have the lead in this. But I don't see enough evidence that coherent dialogue is coming out of this; instead, people are simply putting up their own thoughts about the passages.
We need a way for people to create something together around the Bible text. Just as some very smart people have figured out how to let all kinds of people create Wikipedia together, we need some very smart folks to figure out how to let all kinds of people create together a kind of shared Bible-related text. There are so many issues and fears that hinder this -- the Bible is the central spiritual authority in the lives of tens of millions of people, and yet there are thousands of different ways of interpreting it, all of which have fierce adherents. In this kind of world, letting all kinds of people create together a shared Bible-related text is a dicey undertaking.
What else do we need? What are your thoughts about all of this?
I am grateful to the organizers of BibleTech 2010 for inviting Elizabeth Drescher to give this talk on the "social logic of communication." She is raising important issues, and we need more discussion about them.
She tackled this issue from an historical angle, explaining the development of "the social logic of communication," showing the relationship between communications technologies and the types of social interactions that these technologies have promoted.
- In the pre-modern era (before 1400), communication was rhetorical -- culture was oral, biblical texts were read aloud in community, and authority was in what is said.
- With the advent of print (1400s to present), communication became grammatical, dependent on reading texts privately; authority was in what is written. Drescher pointed out that this is the era in which the language of "personal relationship with God" became dominant -- which was only possible as people were able to have a private experience of the text, which they then took into their communities.
- Then, in the high-modern era (1920s to present), public broadcast became a central element of culture, so authority moved to what is presented. This is the era that we have all grown up in, gathering around the radio and then the t.v. to learn the news and to find out what is interesting in the world.
- But now, we have entered the postmodern digital era (1990s to present), in which communication is dialectical -- the digital culture is interactive, and authority is in what we create together.
One thing that Drescher didn't address is the fact that we now have print, broadcast, and digital communication cultures all overlapping, co-mingling, and interacting -- with no sign that any of these communication media and cultures is on the wane. The doomsayers say that print publishing is dying, but I expect that we will print more, not fewer, books in the future. I also expect both radio and t.v. to continue and thrive for a good long time. What I am interested in discussing is, what is the social logic of communication in a culture that contains all three of these approaches? Drescher also talked about how different types of communication have traditionally been associated both with people of different developmental ages, and with different social classes. She aligned these with the classical trivium of the liberal arts, as follows:
- Grammar: structure and rules == children, women, slaves
- Dialectic: reasoning and argument == adolescents, boys, peasants/laymen
- Rhetoric: presentation and persuasion == adults, men, lords/clergy, the learnèd
How does all of this affect what we do in digital Bibles? Some reflections:
We need to enable a greater level of dialogue and interaction around Bible texts and Bible-related texts in digital contexts. In the first 20+ years of Bible software, all digital interactions with the Bible have taken place offline in "desktop Bible software." In the first 10+ years of the web, there have been Bible texts online, but very little means of interaction -- most of this has been broadcast-only. Now, with the rise of social media, more and more people are sharing Bible texts with each other online and discussing them. There are problems with this -- problems that Drescher discussed in the second half of her talk, which I plan to review next time.
We need a way for people to have coherent dialogue in a coherent textual context -- so that their dialogue and interaction around the texts is not divorced from the texts, and the texts are not fragmented by being shared. Some online Bible sites have the ability for users to add their own comments on the text -- YouVersion seems to have the lead in this. But I don't see enough evidence that coherent dialogue is coming out of this; instead, people are simply putting up their own thoughts about the passages.
We need a way for people to create something together around the Bible text. Just as some very smart people have figured out how to let all kinds of people create Wikipedia together, we need some very smart folks to figure out how to let all kinds of people create together a kind of shared Bible-related text. There are so many issues and fears that hinder this -- the Bible is the central spiritual authority in the lives of tens of millions of people, and yet there are thousands of different ways of interpreting it, all of which have fierce adherents. In this kind of world, letting all kinds of people create together a shared Bible-related text is a dicey undertaking.
What else do we need? What are your thoughts about all of this?
I am grateful to the organizers of BibleTech 2010 for inviting Elizabeth Drescher to give this talk on the "social logic of communication." She is raising important issues, and we need more discussion about them.
Labels:
BibleTech,
communication,
culture,
dialogue,
digital Bibles,
rhetoric,
social logic
Thursday, April 1, 2010
Automatic Concordancing
The first session I attended at BibleTech was by Neil Rees from the United Bible Societies. Neil was demonstrating Paratext, a widely-used tool for doing Bible translation, and the Concordance Builder that works in Paratext.
Neil encouraged all of us who are involved in Bible translation to get onto Paratext. Paratext has 2000+ registered users and is being used on around 1000 Bible translation projects worldwide. So I went to the Paratext website and registered for an account. I'm still waiting to hear back. (It looks like Paratext is only available to people who can verify that they are involved in Bible translation in some fashion.)
The bulk of the talk concerned Concordance Builder. Neil reminded us that an intelligently edited concordance is an important tool for users of the Bible, to help them find concepts and topics by key terms. Now, it's certainly possible to provide an exhaustive concordance of every word mechanically, but this is much less useful for a number of reasons, including (1) too many hits, (2) no grouping of related word forms, and (3) no distinguishing between different meanings of the same word. Besides, it's impossible to print such a concordance in the back of a Bible. And even if your primary delivery is digital, a mechanically-generated concordance is much harder to use than one which has been intelligently edited.
So a concordance needs to be edited, and that's where all the time is spent in concordance-making. But this is where Concordance Builder really shines: (1) It aids grouping by word-stem; (2) it automatically generates lists of references for a given word or stem; (3) it comes with model concordances and statistical glossing functions to aid in creating these lists of references; (3) the generated list of references for each term can be edited; (4) the overall term list can also be edited, so as to exclude "structure" words like "the"; (5) it enables the inclusion of cross-references and alias terms; (6) it automates the process of selecting the portion of the sentence for display, based on column width; (7) it produces XML output that can be imported into typesetting software such as Adobe InDesign.
Using Concordance Builder, Neil says that an excellent, edited concordance for a new translation can be created in a few days or weeks rather than months or years.
More information about the theoretical basis for automatic concordance building can be found in an academic paper by the presenter, Neil Reese, and his colleague, J. D. Riding, entitled "Automatic Concordance Creation for Texts in Any Language." In addition, J. D. Riding has published a paper entitled "Statistical Glossing - Language Independent Analysis in Bible Translation", which is about the process of mapping one language to another, in order to give a head start at concordance building. More information about Concordance Builder and related topics is available at Neil Reese's and J. D. Riding's academic website.
For those who are involved in Bible translation work and making concordances, I have not seen a better toolset; and because it outputs XML and has been integrated into InDesign, it can be used in any Bible publisher's workflow.
Neil encouraged all of us who are involved in Bible translation to get onto Paratext. Paratext has 2000+ registered users and is being used on around 1000 Bible translation projects worldwide. So I went to the Paratext website and registered for an account. I'm still waiting to hear back. (It looks like Paratext is only available to people who can verify that they are involved in Bible translation in some fashion.)
The bulk of the talk concerned Concordance Builder. Neil reminded us that an intelligently edited concordance is an important tool for users of the Bible, to help them find concepts and topics by key terms. Now, it's certainly possible to provide an exhaustive concordance of every word mechanically, but this is much less useful for a number of reasons, including (1) too many hits, (2) no grouping of related word forms, and (3) no distinguishing between different meanings of the same word. Besides, it's impossible to print such a concordance in the back of a Bible. And even if your primary delivery is digital, a mechanically-generated concordance is much harder to use than one which has been intelligently edited.
So a concordance needs to be edited, and that's where all the time is spent in concordance-making. But this is where Concordance Builder really shines: (1) It aids grouping by word-stem; (2) it automatically generates lists of references for a given word or stem; (3) it comes with model concordances and statistical glossing functions to aid in creating these lists of references; (3) the generated list of references for each term can be edited; (4) the overall term list can also be edited, so as to exclude "structure" words like "the"; (5) it enables the inclusion of cross-references and alias terms; (6) it automates the process of selecting the portion of the sentence for display, based on column width; (7) it produces XML output that can be imported into typesetting software such as Adobe InDesign.
Using Concordance Builder, Neil says that an excellent, edited concordance for a new translation can be created in a few days or weeks rather than months or years.
More information about the theoretical basis for automatic concordance building can be found in an academic paper by the presenter, Neil Reese, and his colleague, J. D. Riding, entitled "Automatic Concordance Creation for Texts in Any Language." In addition, J. D. Riding has published a paper entitled "Statistical Glossing - Language Independent Analysis in Bible Translation", which is about the process of mapping one language to another, in order to give a head start at concordance building. More information about Concordance Builder and related topics is available at Neil Reese's and J. D. Riding's academic website.
For those who are involved in Bible translation work and making concordances, I have not seen a better toolset; and because it outputs XML and has been integrated into InDesign, it can be used in any Bible publisher's workflow.
Labels:
Automation,
Bible Translation,
BibleTech,
Concordancing,
Linguistics,
Paratext
Wednesday, March 31, 2010
The Ezra Project
I met Tobias Klein on the first day of BibleTech and learned about what he is doing when, at the end of a session, I walked out of the conference room and was waiting to talk to someone. Tobias was standing next to me, so I introduced myself to him and began to engage in chit-chat, and talked with him into the start of the next session. Tobias is temporarily living in the San Jose area, doing a church-based training program. On the side, he has recently been working on the "Ezra Project," which he described as a single function application for personal Bible study, and he offered to give me a demo.
What intrigues me the most about the Ezra Project outlining function is that it enables each user of the software to engage personally with understanding Scripture in terms of outlining. As Tobias says, making an outline is one of the key ways that people can really wrestle with how a book of the Bible fits together. So helping people to annotate Scripture in this way in a web-based tool has incredible possibilities for personal Bible study. The outlining function is already available online at the Ezra Project website, and it's a lot of fun to use. And when you're all finished, you can get an exported PDF of your outline for each book (XML or HTML would be nice, too!).
Outline Function
What Tobias has done is make it very easy for people to create their own outline of Scripture in a web-based interface. As he explained, making your own outline is one of the key ways that people can process their own understanding of how each book of the Bible is put together. I played with the outlining function for a few minutes and was impressed with the straightforward way in which it made Scripture outlining easy. I will say that Tobias had to explain briefly how to use the interface -- a weakness that should be easy to remedy, given Tobias's excellent user-interface sensibilities.What intrigues me the most about the Ezra Project outlining function is that it enables each user of the software to engage personally with understanding Scripture in terms of outlining. As Tobias says, making an outline is one of the key ways that people can really wrestle with how a book of the Bible fits together. So helping people to annotate Scripture in this way in a web-based tool has incredible possibilities for personal Bible study. The outlining function is already available online at the Ezra Project website, and it's a lot of fun to use. And when you're all finished, you can get an exported PDF of your outline for each book (XML or HTML would be nice, too!).
Tagging Function
Tobias also showed me, on his development notebook, a tagging function that is not yet in production (but is currently available in testing -- go to the development website for more information). The tagging function lets you create a selection of Scripture verses, then define tags that should be applied to each of those verses. The tags can either be global, across the entire Bible, or local to the specific book. Again, giving people the ability to annotate for themselves what topics they see as being covered by each verse can really help them to wrestle themselves with the meaning of Scripture.Conclusion
Tobias's work on the Ezra Project combines an excellent, intuitive user interface, with a clear vision for helping people to do personal Bible study. Rather that pre-digesting Scripture for people like most Bible study tools, these tools help people to digest Scripture for themselves. Frankly, I haven't seen anything else like it, so I'm looking forward to seeing what else Tobias dreams up for the Ezra Project.
Labels:
BibleTech,
Outlining,
People,
User Annotations
Tuesday, March 30, 2010
WordBloom
When we went down to the main BibleTech conference room on the first morning, there were only two tables for vendors. One of them was for a web application called WordBloom. Keith and I were intrigued by what looked like a visual thesaurus on screen and made a note to come back and find out more later. We ended up visiting with Doug Burrier, the owner of WordBloom. Doug is the energetic pastor of Northwest Church in Atlanta, and a warm and personable man. Doug had a vision of creating something like the visual thesaurus with Bible knowledge. and during the past year or so he brought together a team and built this application that allows you to explore the conceptual world of the Bible through a graph of connections between Scripture verse references and topics. Every time you search a topic or reference, the application displays a "word bloom," which is Doug's term for a network of connections to related terms. If you click another term in the bloom, it becomes the center of a new bloom. As you explore, at any point you can gather what you've found into studies, which can become the basis for your personal exploration of Scripture. A personal WordBloom subscription is $36/year. I'm looking forward to having more opportunity to explore this outstanding application.
Labels:
BibleTech,
graph,
People,
Visual Thesaurus,
WordBloom
Monday, March 29, 2010
BibleTech 2010 General Review
BibleTech, a conference sponsored and organized by Logos Bible Software, brings together all kinds of people interested in the intersection between the Bible and technology -- from Bible publishers, to Bible software developers, to interested users. I came to BibleTech with two goals: to meet a lot of people, and to learn about what everyone is doing around this intersection, which is the public square at the corner of Bible way and digital avenue. Both of my aims were amply satisfied by the rich content of the sessions and by the beginning of good relationships with a number of people.
I admit, I like keynotes, and I was disappointed not to have one to kick off the conference. I like being inspired and challenged, I like having the vision for the conference laid out at the beginning, setting the direction for the rest of the experience. But I will also admit that, for this particular conference, I really appreciated having the opportunity to find out who else is present. By the end of the session, I knew which other Bible publishers were present (Zondervan, Crossway, B&H, and Tyndale), and some people that I would really be interested in talking further with. My primary purpose at this conference was to connect with people and to find out what they're interested in and doing. The introductions session gave me a very good jump on doing that, so I'm grateful.
I did end up receiving an inspiring message the first day of the conference, but it came at the end of the day during the demo session, when Aaron Linne was talking about BibleNavigatorX on the Xbox360. More on that later.
Here are the sessions I attended on Day 1 -- more about each of them later:
Here are the sessions I attended on Day 2:
Most of what I learned this year was focused around specific people and their projects. In addition to the sessions that I attended, which resulted in a non-personal connection with each of the presenters and their projects, I made personal connections with quite a number of other people and the things that they're doing. Those connections are, I believe, even more valuable than the sessions I attended. They say that conferences are better for the connections you make than for the sessions you attend. For me, BibleTech 2010 was definitely that way. As I am able, and with the permission of those with whom I spoke, I hope to write about many of these people over the coming days.
I began writing this post while sitting at San Francisco airport on Saturday, Mar. 27 after two full days of conferencing and enjoying the California sunshine. Now it's Monday afternoon, Mar. 29, inside my office in the Chicago area. As the experience of BibleTech begins to meld into memories, I am hopeful that the relationships that were born there, and the experiences that I had, will benefit both my employer and many others. So I am grateful to Logos for hosting this conference, and I'm looking forward to next year.
How about you? Were you at BibleTech? Please let us know your thoughts in the comments and in links to your own blogs.
Sessions, Day 1
A typical conference begins, and perhaps ends, with a keynote session, giving a vision and inspiring attenders. But BibleTech is not a typical conference: There are no keynotes. Instead, Bob Pritchard likes to open these conferences with a simple time of introductions, going around the room and hearing who is present, so that we can begin to make connections with each other.I admit, I like keynotes, and I was disappointed not to have one to kick off the conference. I like being inspired and challenged, I like having the vision for the conference laid out at the beginning, setting the direction for the rest of the experience. But I will also admit that, for this particular conference, I really appreciated having the opportunity to find out who else is present. By the end of the session, I knew which other Bible publishers were present (Zondervan, Crossway, B&H, and Tyndale), and some people that I would really be interested in talking further with. My primary purpose at this conference was to connect with people and to find out what they're interested in and doing. The introductions session gave me a very good jump on doing that, so I'm grateful.
I did end up receiving an inspiring message the first day of the conference, but it came at the end of the day during the demo session, when Aaron Linne was talking about BibleNavigatorX on the Xbox360. More on that later.
Here are the sessions I attended on Day 1 -- more about each of them later:
- Automatic Concordancing for Scripture in Any Language, Neil Rees
- Using Computer Technologies in the Making of the New Bulgarian Translation of the Bible, Dony Donev
- People of the Facebook?: Biblical Conversation, Community, and Social Media, Elizabeth Drescher
- The Hulu Effect: A Call to Bible Publishers for Collaboration in Innovation, Paul Mikos
- Innovations in Mobile Bible Software, Drew Haninger
- DATR: Linguistic Description of Greek and Other Languages with Pedagogical Applications, Josh Cason
- Open Scriptures API: Unified Web Service for Scriptural Linked Data, Weston Ruter
- Demo night
Sessions, Day 2
Day 2 of BibleTech was, for me, quite a bit more focused and technical than Day 1. I didn't spend as much time meeting and talking with people, and it was a shorter day, since we had to leave the conference at 2:45 (2 hours before the end) in order to return our rental car on time to National Car Rental (whose service I recommend -- our inexpensive-to-rent Toyota Yaris was a great little car, a lot of fun to drive, effortless at, ahem, 90 mph, and very efficient with fuel).Here are the sessions I attended on Day 2:
- Annotating Linguistic Reference in the New Testament, Sean Boisen
- Going Between Two Horns of the Dilemma: A Systematic, Incremental Approach to Fleshing Out Higher Discourse Connections in the Greek New Testament, Randall Tan
- Greek Syntax Databases: Retrospect and Prospect, Michael Aubrey
- Using Pinax and Django For Collaborative Corpus Linguistics, James Tauber
General Reflections
BibleTech 2010 was a well-organized and well-run conference. Jayson Bradley of Logos organized it, and he did a great job of lining up interesting speakers and of dealing with last-minute cancellations. He also did a nice job of providing excellent meals and good coffee, and of being an all-around great guy.Most of what I learned this year was focused around specific people and their projects. In addition to the sessions that I attended, which resulted in a non-personal connection with each of the presenters and their projects, I made personal connections with quite a number of other people and the things that they're doing. Those connections are, I believe, even more valuable than the sessions I attended. They say that conferences are better for the connections you make than for the sessions you attend. For me, BibleTech 2010 was definitely that way. As I am able, and with the permission of those with whom I spoke, I hope to write about many of these people over the coming days.
I began writing this post while sitting at San Francisco airport on Saturday, Mar. 27 after two full days of conferencing and enjoying the California sunshine. Now it's Monday afternoon, Mar. 29, inside my office in the Chicago area. As the experience of BibleTech begins to meld into memories, I am hopeful that the relationships that were born there, and the experiences that I had, will benefit both my employer and many others. So I am grateful to Logos for hosting this conference, and I'm looking forward to next year.
How about you? Were you at BibleTech? Please let us know your thoughts in the comments and in links to your own blogs.
Subscribe to:
Posts (Atom)