Mobile Ministry Magazine

In a conversation via Twitter (yes, I know that's a bit of an oxymoron) after yesterday's post, the idea that content needs to be independent was in some respects validated, but there's that aspect of publishers and developer rights that's rarely heard in this discussion. So I asked, what would this question of content independence look like if we didn't just say "we want it" but actually proposed a "how to do it?"

So let's try and answer that. And your feedback is key (especially those of you with some vested careers in this).

Here are some thoughts I have:

• Start with the content that is already within the domain of users (notes, bookmarks, etc.). This content should already be using an XML-based format that is readable in any Bible application regardless of platform (PC, mobile, Windows, Mac, Linux, etc.). This much should be done now. I'd say a commonly supported plugin that any Bible application can use that would unify formatting and content types would be enough for this.
• Concerning those newer translations which are already available in the public domain through publisher agreements (thinking ESV, NET, and a few others); where can open source developers and advocates join together in coding and marketing this raw content to whatsoever persons/orgs need it? In this way, we leverage open source not so much for the cost savings, but for the people-energy that it generates. Allow the push to use the software come from the grassroots angle (small groups, the pastorate, etc.) and then also the bigger angles (software and educational organizations banding together to promote code and/or study camps for example). Use that energy to create points of engagement and interest from those outside of those groups.
• Publishers have a vested interest in keeping their formats licensed, so how about instead of attaching the license to the Bibles, the license is attached to the user(s). Much like what some software companies do, publishers would allow a user or group of users to purchase a license which allows limited usage of that content; and a digital token is given that is simply asked to be reregistered a few times a year at no cost. Publishers get sales and metrics; people get content in as many ways as they can view it.

Those are some of my ideas. What about yours?

Labels: accessiblity, accountability, Bible, content, open source, software, tech