-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JsonBible #1
Comments
Thank you for the email. (You didn't leave your name, however)
As far as I'm concerned jsonBible.org/com is still in beta. The copyright
versions of the Bible I included because the project isn't finished. On my
site https://virtualBible.org, I include those versions but limit
retrieval to 3 verses at a time (for those versions).
However, if you go to my repo at https://github.com/DannyCarlton/osBible.org
you'll find mysql files for several public domain versions of the Bible,
plus scripting examples for using the data.
The samples are limited to the languages and technology I'm familiar with,
and I'm a bit old-school, so there aren't any newer examples (like rect,
view, etc.)
I hope that helps,
Danny Carlton
***@***.***
…On Tue, Mar 21, 2023 at 3:21 PM Bukunmi Ransome-kuti < ***@***.***> wrote:
Hi Danny 😊
Thank you for your work on this project and many of your awesome tools.
I have been unable to find your email address on your personal website and
here seems to be the only way I could connect. I am sorry for the derail.
I came across jsonBible, one of your projects, which seems to allow
retrieval of non open-access Bible versions like the Amplified and NIV, and
I wanted to know the long term plans for the project and whether it is
suitable for adoption at this stage.
I currently maintain BibleUp (https://bibleup.netlify.app), and after
checking for resources that allow retrieval of non open-access versions, I
discovered there isn't much option to gain access to many of these
contemporary versions since they require permissions and licencing
agreements - which is quite an hassle for non-profit and free tools.
I am considering the adoption of jsonBible but I need to know your plans
and the structure around the project, if there is fair usage requirements
on the API and rate limiting options.
I would appreciate your response on this.
Warn regards.
—
Reply to this email directly, view it on GitHub
<#1>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6OZFA53JWPBYCL2MNSRKTW5IEVZANCNFSM6AAAAAAWC6ESJM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I am Bukunmi Kuti I guess I would have to wait until jsonBible is out of beta and stable. Great work so far by the way. I wouldn't mind contributing to development if it were open-source, but I trust there is a reason why you want the development private. I once developed a backend service like osBible using Mysql and PHP, before I decided to adopt external API providers like api.bible. Thank you for your help |
Hi Danny 😊
Thank you for your work on this project and many of your awesome tools.
I have been unable to find your email address on your personal website and here seems to be the only way I could connect. I am sorry for the derail.
I came across jsonBible, one of your projects, which seems to allow retrieval of non open-access Bible versions like the Amplified and NIV, and I wanted to know the long term plans for the project and whether it is suitable for adoption at this stage.
I currently maintain BibleUp (https://github.com/bibleup/bibleup), and after checking for resources that allow retrieval of non open-access versions, I discovered there isn't much option to gain access to many of these contemporary versions since they require permissions and licencing agreements - which is quite an hassle for non-profit and free tools.
I am considering the adoption of jsonBible but I need to know your plans and the structure around the project, if there is fair usage requirements on the API and rate limiting options.
I would appreciate your response on this.
Warn regards.
The text was updated successfully, but these errors were encountered: