<div dir="ltr">If your app is offline, then I think it counts as any other Sword frontend, in that your'e not redistributing content. This is the case for STEP as I understand it. But you need to distinguish between offline locally and offline while distributing content to others. So if by offline you mean local, then you're OK. If by offline you mean you're distributing to a closed network via a central server, then I'm not sure what the status is there.<div>
<br></div><div>I'm afraid I don't use the Sword Engine. I use the JSword engine. Someone else can probably help you in terms of the practical elements.</div><div><br></div><div>The STEP project's architecture sounds very similar to what you're doing, but comprises both the client side as well as the server (not using node.js, but Java). Our desktop version will work offline - as you suggest yours will - by hosting a tiny lightweight embedded server. Our desktop version is aimed especially at people whose internet connection is flaky, inexistent or slow. STEP already supports the "Install Manager" capability, as well as passage lookups, lexicon lookups and lots of different kinds of searches. I would love to join up efforts if that's something you'd consider.</div>
<div><br></div><div>Chris</div><div><br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 16 June 2013 13:25, Stephan <span dir="ltr"><<a href="mailto:info@tetzels.de" target="_blank">info@tetzels.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Chris,<br>
<br>
thank you for your answer.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In terms of Copyright/license, you fall under the "redistribution"<br>
category as far as I can tell. As a result, you will need to seek<br>
permission for all modules in the repository (apart from those that are<br>
public domain). Or at least, that's my understanding. Publishing content<br>
on the web is a form of redistribution. Normal Sword frontends benefit<br>
from the rights and permissions CrossWire has sought from the various<br>
Copyright holders.<br>
</blockquote>
<br></div>
The future web app will be an offline one. I only need the node.js wrapper to do the serialization. After you "install" a module in the web app it wil work without an internet connection. So is this also the "redistribution" category?<div class="im">
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In terms of accessing the raw OSIS XML, you can certainly do that with<br>
JSword, so I'd expect you could do something similar in Sword.<br>
</blockquote>
<br></div>
Can you give me some hints? If I use the OSIS Filter (FMT_OSIS) I don't get the raw OSIS content. I get OSIS XML, but without the text/body of a footnote e.g.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
BTW, just so that you are aware, STEP is a webapp and already exposes a<br>
JSON/Rest API and hopes to extend it further to support more use cases.<br>
It wraps around JSword, rather than Sword.<br>
</blockquote>
<br></div>
My plan is to build a REST API, too, but only to do the InstallMgr stuff and get the (raw) content of the module once to use it in a HTML/Javascript app.<br>
<br>
Stephan<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On 16 June 2013 11:33, Stephan <<a href="mailto:info@tetzels.de" target="_blank">info@tetzels.de</a><br></div><div class="im">
<mailto:<a href="mailto:info@tetzels.de" target="_blank">info@tetzels.de</a>>> wrote:<br>
<br>
Hi,<br>
<br>
in my spare time I develop a node.js libsword wrapper as a backend<br>
for a future web app. The node.js wrapper will download the<br>
requested module and serialize the data, so that a mobile javascript<br>
app can handle it.<br>
<br>
What should I keep in mind to avoid a licence/contribution issue<br>
since the node.js app will hold a copy of all installed modules and<br>
do some data serialization (get the content/attributes of a verse<br>
key and convert it to JSON. The plain verse content will be on of<br>
the sword filter output)?<br>
<br>
Is there a way to access the raw content (like the underlying OSIS<br>
XML) of a module through the sword engine?<br>
<br>
Regards,<br>
Stephan<br>
<br>
<br>
I've started to work on a non-blocking nodejs wrapper for libsword.<br>
you'll find the sources here:<br></div>
<a href="https://github.com/zefanja/__sword-addon" target="_blank">https://github.com/zefanja/__<u></u>sword-addon</a><div class="im"><br>
<<a href="https://github.com/zefanja/sword-addon" target="_blank">https://github.com/zefanja/<u></u>sword-addon</a>><br>
See app.js for how to use the API (in pre-alpha state...).<br>
<br>
<br></div>
______________________________<u></u>___________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<mailto:<a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.<u></u>org</a>><br>
<a href="http://www.crosswire.org/__mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/__<u></u>mailman/listinfo/sword-devel</a><div class="im"><br>
<<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/<u></u>mailman/listinfo/sword-devel</a>><br>
Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/<u></u>mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
<br>
</div></blockquote>
</blockquote></div><br></div>