I think the client shows that many of the Stanbol API are overly complex. However I don't we should introduce different APIs for external clients than for clients within the JVM (i.e. other bundles). We should have easy yet powerful api which can have implementation which issue request to a remote instance or which are implemented locally.
Cheers, Reto On Tue, Mar 26, 2013 at 6:08 PM, Rüdiger Kurz <[email protected]> wrote: > Hi Rafa, > > Rafa Haro: > > Dear all, >> >> We have recently released a new version of our Java Apache Stanbol >> Client >> (https://github.com/zaizi/**apache-stanbol-client<https://github.com/zaizi/apache-stanbol-client>). >> The project >> intention is to ease Apache Stanbol integrators to use Stanbol in their >> Java projects. The tool covers almost the full REST API for the >> following Stanbol components: Enhancer, ContenHub, EntityHub and Sparql. >> >> If anyone is interested on use it for his own projects, it would be >> great for us to have some feedback, suggestions, improvements.....We >> also encourage all of you to participate in its development if you find >> it useful. >> >> Regards! >> > > looks interesting for us - it opens a new way for a Stanbol integration > into OpenCms. Hopefully in June I will have some time for experiments. > > -Rüdiger > > ------------------- > Alkacon Software GmbH - The OpenCms Experts > > http://www.alkacon.com > http://www.opencms.org >
