Re: Apache stanbol: Enhancer service codification problem

Hi Jairo, I created STANBOL-813 [1] and implemented a fix with revision [2]. Your test case now works for me so it should be fine for you to. Note that this fix does not tackle the general issues as mentioned in my first replay so Stanbol might still write characters to the Enhancement structure

Re: "Error reloading cached bundle"

Hi Reto, I am now able to reproduce this by the following (1) start the Stanbol launcher within the target folder (2) make a mvn clean install while the stanbol is still running in the ./target folder (4) stop the Stanbol launcher (of the in the meantime deleted folder) (5) go to the newly create

Jenkins build is back to stable : stanbol-trunk-1.6 #1109

See

Jenkins build is back to stable : stanbol-trunk-1.6 » Apache Stanbol Integration Tests #1109

See

Stanbol ISBN Tutorial material

Hi all, Back in October I gave a tutorial at DERI in Galway on Stanbol with Andrea. The topic for my part was customizing and extending the Entityhub and Enhancer components to detect and annotate books mentioned by ISBN in text content. The exercises instructions + code skeleton and solution ar

Re: The KeywordLinkingEngine and the Stanbol NLP processing module (STANBOL-740)

On Thu, Nov 22, 2012 at 12:10 PM, Bertrand Delacretaz wrote: > > Isn't the "hub" part an implementation detail? > > EntityLinkingEngine sounds better to be - but no strong opinion, > whoever does the work decides. Good point. While refactoring the code I came to the same conclusion Currently I h

Re: (Back to the) Future of Clerezza and Stanbol

On Mon, Nov 19, 2012 at 9:00 PM, Andy Seaborne wrote: > On 19/11/12 14:13, Reto Bachmann-Gmür wrote: > >> > - Linked Data Platform: Reto I guess you have missed this >>> >presentation [1] at ApacheCon. IMO a Linked Data Platform is something >>> >that deserves an own project and as soon as there

Re: The KeywordLinkingEngine and the Stanbol NLP processing module (STANBOL-740)

On Thu, Nov 22, 2012 at 10:12 AM, Fabian Christ wrote: ... > +1 for EntityhubLinkingEngine... Isn't the "hub" part an implementation detail? EntityLinkingEngine sounds better to be - but no strong opinion, whoever does the work decides. -Bertrand

Re: stanbol internal dependencies to dependency management

I agree that if integration offer full coverage the will fail when a compatibility breaking change is introduced. However the advantage of statically typed languages is that you can detect this problems already at compile time. The two arguments you mention package split and interaction with host

Re: The KeywordLinkingEngine and the Stanbol NLP processing module (STANBOL-740)

+1 for option 2) + creating a tag before the merge as Bertrand suggested. +1 for EntityhubLinkingEngine 2012/11/22 Rupert Westenthaler > Hi > > thanks for the feedback. I think we should go for (2) renaming the > engine. First because the current name (KeywordExtractionEngine) is > anyway not