[sword-devel] getBible.net JSON API is now HARD Linked to the Sword Modules

Sat Aug 12 08:32:05 EDT 2023

Some answers:

> What’s the reason for being so selective?

I believe we chose the current list of Bibles based on two perspectives:

1. From the list of Public Domain Bibles that can be utilized without any
constraints.
2. With the exception of those that were part of our old API v1 and were
reader-requested.

- Ou Vertaling - Afrikaans (which is my mother tongue)
- Smith and Van Dyke - Arabic.
- Breton New Testament- Breton.
- NCV Simplified - Chinese.
- NCV Traditional - Chinese.
- Czech CEP - Czech.
- Pyha Raamattu (1992) - Finnish.
- Louis Segond (1910) - French.
- Lithuanian - Lithuanian.
- Cornilescu - Romanian.
- Victor Zhuromsky NT - Russian.
- Reina Valera (1909) - Spanish.
- Thai from kjv - Thai.
- Turkish - Turkish.

So, in essence, we selected all Public Domain Bibles plus a few more that
our readers requested.

At present, we are employing only a few Bibles based on the permissions
granted to Crosswire. The bulk of the chosen Bibles are in the public
domain or under licenses that essentially permit non-commercial usage.

I'm eager to incorporate more, but only once we're confident that the
system we've established, with its HARD-LINKED connection to the Crosswire
Modules, genuinely covers us under the permissions granted to Crosswire. My
aim is to produce a system that meets all specifications and fully honors
all copyright and associated constraints. This is the reason it's taken me
years to finalize this—planning and investing the time to create a robust
and well-supported system was a significant challenge.

A further matter arising is how you handle DistributionLicense for each
> module?

Since we're currently using primarily Public Domain Bibles and a few that
have "permissions granted to Crosswire," I'm eager to understand how to
manage this aspect of the projects. I have the capability to restrict
access, and I can either remove them from the API (or web app) or adhere to
any guidelines necessary to meet expectations.

One thing that needs clarifying is whether you sync modules only to the
> main CrossWire repository, or whether you also make use of the other module
> sources listed in the CrossWire Master Repositories List?

This is the current complete list of Bibles we are using:
https://git.vdm.dev/getBible/v2_builder/src/branch/staging/conf/CrosswireModulesMap.json
(https://api.getbible.net/v2/translations.json)
As previously mentioned, we're highly selective at the moment, as we seek
guidance moving forward. Depending on what's permissible and appropriate,
we're prepared to either expand or reduce the getBible API.

*Kind regards*
*Llewellyn*

On Sat, Aug 12, 2023 at 12:38 AM David Haslam <dfhdfh at protonmail.com> wrote:

> Further question:
>
> Some SWORD modules in the CrossWire repository are not listed in the
> getBible.net website.
>
> The Anderson NT is just one example among many.
>
> What’s the reason for being so selective?
>
> Kind regards,
>
> David
>
> On Fri, Aug 11, 2023 at 20:01, Llewellyn van der Merwe <llewellyn at vdm.io
> <On+Fri,+Aug+11,+2023+at+20:01,+Llewellyn+van+der+Merwe+%3C%3Ca+href=>>
> wrote:
>
> Hi David
>
> Thank you for your email, I would like to think that since the text is
> exactly the same as the modules and kept in that state it would be looking
> on any screen the same as Xiphos or PocketSword. So I would say getBible is
> also a Crosswire project (format) like the above two mentioned projects.
>
> I am not at my desk right now, but will checkout the links you send me and
> answer the further questions in the next few days.
>
> Just a side note for now, each translation’s complete details (copyright
> notices) can be viewed on each page under the (i) menu icon.
>
> If any more official notices is needed to show the Crosswire relationship
> more than is already set in place, we will gladly add it.
>
> Kind regards
> Llewellyn
>
> On Fri, 11 Aug 2023 at 8:13 PM, David Haslam <dfhdfh at protonmail.com>
> wrote:
>
>> Hi Llewellyn,
>>
>> Further to my initial reply, I have just created a wiki page for
>> *getBible* and linked it from here.
>>
>> https://wiki.crosswire.org/Main_Page#Front-end_Bible_study_applications
>>
>> One thing that needs clarifying is whether you sync modules only to the
>> main CrossWire repository, or whether you also make use of the other module
>> sources listed in the CrossWire *Master Repositories List*? See
>>
>> https://wiki.crosswire.org/Official_and_Affiliated_Module_Repositories
>>
>> A further matter arising is how you handle *DistributionLicense* for
>> each module?
>>
>> cf. Some Bibles are copyright but the owner has granted permission for
>> CrossWire to distribute them *in SWORD format*. It's not completely
>> clear to an outsider looking at *getBible* for the first time whether
>> the sync'd Bibles are still in SWORD format, or are in a *derived*
>> format.
>>
>> If the latter, then it's essential that you speak with Troy A Griffitts
>> and discuss the details.
>>
>> Best regards,
>>
>> David Haslam
>>
>> Sent with Proton Mail <https://proton.me/> secure email.
>>
>> ------- Original Message -------
>>
>> On Friday, August 11th, 2023 at 5:45 PM, Llewellyn van der Merwe <
>> llewellyn at vdm.io> wrote:
>>
>> Greetings, in the wonderful name of the Lord Jesus.
>>
>> I spoke to the crosswire community (refdoc at crosswire.org) in 2019, and
>> at the time had to take down our API of the Bible since it was not kept in
>> sync with the Corsswire/Sword modules.
>>
>> Now this has been done, and it has been stable for three years.
>>
>> Here is our API documentation page:
>> https://git.vdm.dev/getBible/v2#v2-getbible-api
>>
>> Here is the build log: https://github.com/getbible/v2_builder/actions
>> (that sync the API with the crosswire modules once a month. Each build
>> takes about three hours.
>>
>> Here is the documentation on how this works:
>> https://github.com/getbible/v2_builder#guidelines
>>
>> We have now based on this API built a Joomla component:
>> https://git.vdm.dev/getBible/joomla-component
>>
>> Which can be used on any website, but here we run the same component on
>> our own website: https://getbible.net/
>>
>> So I would ask that you add getBible <https://getbible.net/> as a *Web-based
>> Software *to this page https://www.crosswire.org/applications/
>>
>> We have a detailed explanation in the component on how the sync process
>> works, if you open https://getbible.net/ you will see a hash value
>> beneath the scripture, with a question mark, just open the link to see the
>> full explanation. This new system will keep all websites that use this
>> system in-sync with the crosswire modules, which is a massive achievement
>> for Crosswire and the whole online Bible world.
>>
>> Please let me know if you have any further questions, your servant in
>> Chirst Jesus.
>>
>> *Kind regards*
>> Llewellyn van der Merwe
>> *Vast Development Method*
>> *llewellyn at vdm.io <llewellyn at vdm.io>*
>> *http://vdm.io <http://vdm.io/>*
>> *+264 (81) 248 7770*
>> *Senior Software Development Manager*
>>
>> Copyright © Vast Development Method <https://www.vdm.io/> | Terms of
>> Service <https://www.vdm.io/terms> | Privacy Policy
>> <https://www.vdm.io/privacy> | Company <https://www.vdm.io/company>
>>
>>
>> --
>
> *Kind regards*
> Llewellyn van der Merwe
> *Vast Development Method*
> *llewellyn at vdm.io <llewellyn at vdm.io>*
> *http://vdm.io <http://vdm.io/>*
> *+264 (81) 248 7770*
> *Senior Software Development Manager*
>
> Copyright © Vast Development Method <https://www.vdm.io/> | Terms of
> Service <https://www.vdm.io/terms> | Privacy Policy
> <https://www.vdm.io/privacy> | Company <https://www.vdm.io/company>
>
>

-- 
Copyright © Vast Development Method <https://www.vdm.io/> | Terms of 
Service <https://www.vdm.io/terms> | Privacy Policy 
<https://www.vdm.io/privacy> | Company <https://www.vdm.io/company>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://crosswire.org/pipermail/sword-devel/attachments/20230812/1ac4ea7d/attachment-0001.htm>