[sword-devel] CORS API

[Troy A. Griffitts]

Hi Simon,

Thanks for your ideas.  I'm interested to hear a little about the use 
cases you are targeting.  Are you trying to server offline browser users 
in general, or do you have a specific case you have in mind?

The background here is that we typically don't encourage transferring 
data from our format to another.  Though we've accumulated a large 
library of works and that, in itself, is useful to other engineer, we 
don't curate any of these individual modules and simply have done the 
work to track down each authoritative source, get permission for 
distribution and use as openly as can be obtained from their curator, 
and then to convert their primary data source into our module format.  
This doesn't pass along any rights for use to other projects outside 
those of CrossWire, and also doesn't provide a primary source for any of 
this material-- which an lead to multiplied data conversion issues when 
moving on to a second jump from the primary source.

We have a C++ engine which runs on most any device you might wish to 
support (including web server)-- with many bindings for most popular 
scripting languages, and also a native Java engine as well.  Both of 
these can be used to discover, install, and access our entire library, 
if you'd like to start a new application in our community or contribute 
to an existing solution.

Two web applications which use our engines and might interest you are:

http://crosswire.org/study

http://stepbible.org

Hope this helps.  Welcome!  Looking forward to sharing in service together,

Troy



On 12/26/2016 03:32 AM, Simon Biggs wrote:
> Hi,
>
> I was hoping to help set up a CORS API for transfer of crosswire 
> resources to web apps. My hope was to be able to make something 
> simple, probably written in Python with the Tornado module and using 
> the sword SWIG bindings.
>
> My thought is the API would simply send whole resources, such as a 
> whole Bible translation. Any webapp interfacing with the API would 
> likely download the resources once per user and store them within the 
> browser's IndexedDB.
>
> I'm not sure what is the best format to use for the transmitted 
> content. The easiest option might be using something like the plain 
> text OSIS format. From my limited exposure to this project that would 
> mean minimal work on the server end required to make as many resources 
> as possible able to be sent this way. What to then do with the OSIS 
> file and how to store it in the IndexedDB would be up to the client 
> side programmer.
>
> What are your thoughts? Does anyone have any recommendations for 
> improvement? If I made something like this, is this something that 
> crosswire would be willing to have running on their server for 
> resource distribution?
>
> Thank you,
> Simon
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20161227/efdd768c/attachment.html>