We use Stanbol in production (at the library of a major public university) but in a slightly different way than has been described. We use the EntityHub in conjunction with the Open Refine RDF extension:
http://refine.deri.ie/ In fact, I would like to use some of the Enhancer tools, but I face a lot of opposition from librarians who are confused and frightened by change or automation. In any event, some thoughts on where the project might go: If it ends up moving to the attic, there are some components that seem to me to have places in other Apache projects. For example, some of the enhancer technology might find a home in UIMA (not speaking from expertise on UIMA, just as a casual observer). The EntityHub might work well as a component in Marmotta. It might be worth mapping out some of the potential moves so that we could start making connections with those communities. One of the things that has always held me back from getting involved with Stanbol more deeply is the relatively high barrier to development. I am a committer for Apache Jena, and it was not too difficult to delve into the codebase and begin to make real contributions (of course I am still learning). Stanbol's very complex module structure doesn't help in this regard. IMHO, it would also be nice if Stanbol used a more common OSGi provisioning system, like Karaf Features, but I am probably biased in that regard. Just some idle thoughts. I would like to take part in this conversation. I think there are some great ideas in Stanbol, and whatever happens to the project/codebase, it's important to find good homes for those ideas. --- A. Soroka The University of Virginia Library > On Jan 16, 2017, at 6:01 AM, Rafa Haro <rh...@apache.org> wrote: > > Hi Fabian and Devs, > > We also widely use Stanbol both as part of customers projects and within > our main product. I admit that we should been contributing further than we > currently do, but sometimes is difficult to find the time for preparing > something you have customize according to your concrete needs to a more > generic contribution. > > Apart from that, it seems that Stanbol nowadays covers a couple of well > known uses cases that most of the final users adopt where, in my opinion, > both further contributions and improvements will not likely arise. Still > under my opinion, one reason is because of the complexity of the code. > Another reason, taking into account that there is quite poor activity at > the list regarding this, is that Stanbol Enhancer features seem to be > enough for final users. > > I think we are not failing in the objective of making Apache Stanbol a > great tool for developers. We are probably failing, I don't know why, in > the objective of building and maintaining a community. > > Those are just my thoughts > > On Mon, Jan 16, 2017 at 11:48 AM Rafa Haro <rh...@apache.org> wrote: > >> Hi Arthi, >> >> I started to develop one: https://github.com/rafaharo/pystanbol >> >> It only covers Enhancer for now. Contributions are more than welcome. >> >> Rafa >> >> On Mon, Jan 16, 2017 at 11:41 AM <arthi.ven...@wipro.com> wrote: >> >> Hi, >> Stanbol is a great solution for entity extraction and many NLP problems. >> I have used it for different pilots and customer implementations. >> I also plan to use same in future. >> The community is also great and very helpful. >> If there is a way for non Java programmer say a Python programmer to more >> easily set up and consume the Rest services more folks can use. >> >> Thanks and Regards, >> Arthi >> >> >> >> -----Original Message----- >> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] >> Sent: Monday, January 16, 2017 3:40 PM >> To: dev@stanbol.apache.org >> Subject: Re: The Future of Apache Stanbol >> >> ** This mail has been sent from an external source ** >> >> Hi, >> >> On Mon, Jan 16, 2017 at 9:33 AM, Fabian Christ < >> christ.fab...@googlemail.com> wrote: >>> ...Maybe the time for Stanbol is over after 5 years of being a top >>> level Apache project. The ASF has the concept of moving projects to >>> the attic once there is not enough interest or community for a project >>> anymore.... >> >> To be precise, an ASF project has to move to Attic if there are less than >> 3 active PMC members, which is the minimum required to vote on releases. >> >> Or if the project is unable to respond to security or other critical bug >> reports, due to lack of available contributors. >> >> It's also fine to move to Attic voluntarily if people think the above >> criteria might not be met for much longer, of course - I just wanted to >> clarify the requirements. >> >> -Bertrand >> The information contained in this electronic message and any attachments >> to this message are intended for the exclusive use of the addressee(s) and >> may contain proprietary, confidential or privileged information. If you are >> not the intended recipient, you should not disseminate, distribute or copy >> this e-mail. Please notify the sender immediately and destroy all copies of >> this message and any attachments. WARNING: Computer viruses can be >> transmitted via email. The recipient should check this email and any >> attachments for the presence of viruses. The company accepts no liability >> for any damage caused by any virus transmitted by this email. >> www.wipro.com >> >>
