Hi Adrian,

After some digging around - I visited the SVN repo where the opencalais for stanbol is implemented - I think I found the issue. The current Stanbol implementation of the enhancer for opencalais is configured for the old URL ( http://api.opencalais.com/enlighten/rest/ ) whereas it should be configured to the new URL ( https://api.thomsonreuters.com/permid/calais ). As I am not a member of the Stanbol committers forum I cannot make the changes but I suppose you can request this small change from the Stanbol forum.

Alternatively you can try to configure the new Calais URL by using the 'Configuration' tab of the Apache Felix Web Console of your Stanbol instance.

Please let me know how you manage this.

Regards,

Eyal

Hi Adrian,

Can you please provide the code sample you are using and also describe what you are trying to do? Thanks.

@Eyal.Kenigsvain

Hi Eyal, thank you for your reply. I was testing within the browser, http://localhost:8080/enhancer/chain/all-active , below:

Enhancement Chain: all-active all 9 engines available < List of Enhancement Chains >

• tika( required , TikaEngine)
• xmpextractor( required , XmpExtractorEngine)
• langid( required , LangIdEnhancementEngine)
• langdetect( required , LanguageDetectionEnhancementEngine)
• ner( required , NamedEntityExtractionEnhancementEngine)
• dbpspotlightannotate( required , DBPSpotlightAnnotateEnhancementEngine)
• dbpspotlightspot( required , DBPSpotlightSpotEnhancementEngine)
• dbpspotlightcandidates( required , DBPSpotlightCandidatesEnhancementEngine)
• opencalais( required , OpenCalaisEngine)

Paste some text below and submit the form to let the Enhancement Chain all-active enhance it:

• Bottom of Form

The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley

Execution of Chain R2_chain failed in 2.00sec.

• 09-05-58.085: completed in 2ms : xmpextractor ( required , start: 09-05-58.085, completion: 09-05-58.087)
• 09-05-58.086: completed in 2ms : tika ( required , start: 09-05-58.086, completion: 09-05-58.088)
• 09-05-58.088: completed in 8ms : langid ( required , start: 09-05-58.088, completion: 09-05-58.096)
• 09-05-58.088: completed in 10ms : langdetect ( required , start: 09-05-58.088, completion: 09-05-58.098)
• 09-05-58.099: completed in 9ms : ner ( required , start: 09-05-58.099, completion: 09-05-58.108)
• 09-05-58.108: completed in 461ms : dbpspotlightannotate ( required , start: 09-05-58.108, completion: 09-05-58.569)
• 09-05-58.569: completed in 317ms : dbpspotlightspot ( required , start: 09-05-58.569, completion: 09-05-58.886)
• 09-05-58.887: completed in 358ms : dbpspotlightcandidates ( required , start: 09-05-58.887, completion: 09-05-59.245)
• 09-05-59.246: failed in 837ms : opencalais ( required , start: 09-05-59.246, completion: 09-06-00.083)

The OpenCalais engine is configured and active, as shown in the screenshots

http://semantic.r-2apps.com/Stanbol.Calais_1.png

http://semantic.r-2apps.com/Stanbol.Calais_2.png

http://semantic.r-2apps.com/Stanbol.Calais_3.png

Is there anything else I need to set/change in order for it to function? Thanks.

@Eyal.Kenigsvain

Thank you Eyal for taking the time to dig into this.. "Unfortunately" Stanbol was already configured with the new URL ( https://api.thomsonreuters.com/permid/calais ) when I tested it, please see http://semantic.r-2apps.com/Stanbol.Calais_1.png.

OK then... it seems I'll have to access OpenCalais outside Stanbol. Thanks again. Adrian