API for serverside querying of personal LT.com library for books

I'm implementing a module for drupal, integrating on the taxonomy module to allow for related books from the configured library to be shown based on the tags of the main content (node).

I'm kinda in a deadlock at the moment though; I want (for performance and integration reasons) to query the LT.com API serverside, but the only API that allows for querying a specific library is the JSON API.
The problem with the JSON API is that the license prohibits me from running it serverside, and personally, I'd prefer a REST XML-RPC API over a JSON API for serverside querying.

Did I miss an API, misread the license or is what I want really not allowed?

Could anyone elaborate on this or any possible new XML-RPC services coming out soon that would allow for serverside library querying?

Thanks in advance.

Can you read the JSON? Is the project commercial? I'd be happy with opening it to non-browser use if it's not.

1> I hope you're truly not in a deadlock. I'd hate to have to reboot you.

jjwilson61: lol ;)

timspalding:

Thanks for the flexibility towards the license and the quick response.

It's for my personal website (see my LT.com dev profile), but I was thinking on releasing it to the Drupal modules project (http://www.drupal.org/ and http://drupal.org/project/Modules). Drupal is released under GPLv2, the modules are non restricted in terms of licensing, but I was thinking about GPLv2 as well for the module. That would mean that it could be used by others for other purposes.
If that's in conflict with the LT.com intent and interests, I'm willing to keep the module private or only provide the source for reference purposes with a more restrictive license.

The JSON data is readable for both serverside and clientside, so that's workable.

In short; the choice for the license and how (or if) it's released is for LT.com to make. I'd just be happy if I could use the API serverside for my own personal website.

The question is what your personal website is doing with it? If you're basically doing a widget-like thing—showing some data—fine. If you're loading up multiple users, selling it or etc. then not.

The GPL license doesn't affect our data license. There are GPL modules for getting data from Google, Yahoo or Amazon. That doesn't moot their terms.

I'd be glad to say that use in this module is fine. Just thumbnail what it does for me? I'm sure it's fine. In the meantime, just go ahead and parse it. We're not actually testing where the data is being shown. We just don't want someone scraping us or otherwise screwing us.

I have to ask, Barre -- are you related to the late, great E W Dijkstra?

timspalding

Thanks.
A general outline is a personal website containing personal writings, my weblog, presentations, my coding projects and so forth.
The module is indeed a widget that shows related content from my LT library based on the tags of both the CMS and the filed LT books in my library.

sarahemmm
Same surname, same country, semi-same line of work, no other relations as far as I know. ;-)

>7 bdijkstra:

Sure. You have permission to use it for that end. Cheers, Tim