[sword-devel] Sword Node.js wrapper
chris at burrell.me.uk
Sun Jun 16 03:41:53 MST 2013
In terms of Copyright/license, you fall under the "redistribution" category
as far as I can tell. As a result, you will need to seek permission for all
modules in the repository (apart from those that are public domain). Or at
least, that's my understanding. Publishing content on the web is a form of
redistribution. Normal Sword frontends benefit from the rights and
permissions CrossWire has sought from the various Copyright holders.
In terms of accessing the raw OSIS XML, you can certainly do that with
JSword, so I'd expect you could do something similar in Sword.
BTW, just so that you are aware, STEP is a webapp and already exposes a
JSON/Rest API and hopes to extend it further to support more use cases. It
wraps around JSword, rather than Sword.
May be worth chatting offline further around the overlap of our two
On 16 June 2013 11:33, Stephan <info at tetzels.de> wrote:
> in my spare time I develop a node.js libsword wrapper as a backend for a
> future web app. The node.js wrapper will download the requested module and
> What should I keep in mind to avoid a licence/contribution issue since the
> node.js app will hold a copy of all installed modules and do some data
> serialization (get the content/attributes of a verse key and convert it to
> JSON. The plain verse content will be on of the sword filter output)?
> Is there a way to access the raw content (like the underlying OSIS XML) of
> a module through the sword engine?
> I've started to work on a non-blocking nodejs wrapper for libsword.
>> you'll find the sources here: https://github.com/zefanja/**sword-addon<https://github.com/zefanja/sword-addon>
>> See app.js for how to use the API (in pre-alpha state...).
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel