Hi
On Tue, Sep 23, 2014 at 5:05 PM, Mohammad Ghufran <emghuf...@gmail.com> wrote:
> Hello,
>
> Thank you for your detailed response once again!
>
> On Mon, Sep 22, 2014 at 3:47 PM, Rupert Westenthaler <
> rupert.westentha...@gmail.com> wrote:
>
>> > So the model is selected behind the scenes based on the language
>> detected?
>>
>> Exactly.
>>
>> Okay, this is great. I didn't see any info in the output as to which
> engine was use. Is there a way to see the output of the different
> enhancement engines such as the POS tagger and the tokenizer etc?
NLP results are not written to the RDF enhancement results as this
would blow up the size of the results. However if you add the
"nlp2rdf" engine to your chain you will get such information. This
engine is not part of the launcher because it was never completely
finished. However for your purpose it should just be fine. The RDF
generated by this engine is based on NIF 1.0 but AFAIK does not fully
comply with the standard.
The engine is under "enhancement-engines/nlp2rdf" in the source tree.
Just install the bundle (as done with the OpenCalais engine).
>
>>
>> If you can not see the OpenCalais engine in this tab it means that you
>> do use an Stanbol Launcher that does not include the engine. In that
>> case you can simple install the required bundle (e.g. by copying the
>> jar to the "stanbol/fileinstall" folder or by installing it via the
>> Bundle tab of the Felix Webconsole.
>>
>> You can find the bundle at
>>
>>
>> enhancement-engines/opencalais/target/org.apache.stanbol.enhancer.engines.opencalais-{version}.jar
>>
>> in your local build. You can also download it from [1] but you will
>> need to rename the file to
>> "org.apache.stanbol.enhancer.engines.opencalais-1.0.0-SNAPSHOT.jar"
>>
>
> Okay, I didn't know that. I was simply using the stable launcher and
> assumed it should be good for this purpose. However, after adding
> OpenCalais with the help of what you described above, and registering an
> API key, I am still not able to run this engine. If i simply add the name
> of the engine in a chain like all the other engines, I get a message
> "opencalais (required, currently not available)".
>
> From the documentation, the only method mentioned to use opencalais is
> through curl like:
> curl -i -X POST -H "Content-Type:text/plain" -T test/cv2.txt
> http://localhost:8080/engines
>
> However, with this approach, I get an error saying that "/engines" is not
> available. Even though I can navigate to http://localhost:8080/engines in
> the browser. Would you have any insights on this?
I have not used this engine since years. So it might es well no longer
work. I tried to replicate your issue, but unfortunately I was not
able to create an OpenCalais key as their service told me that they
will send me the key per mail but I was not receiving any. I tried it
several times over the last few day with no luck. Will try it again in
Monday ...
The "/engines" endpoint is deprecated with the introduction of
Enhancement Chains. In current versions the "/engines" endpoint is
bound to the default Chain (the same as bound to the "/enhancer"
endpoint. The OpenCalais engine was implemented before the
introduction of Enhancement Chains. This is the reason why its README
still refers the "/engines" endpoint.
best
Rupert
>
> Best Regards,
> Ghufran
>
>
>
> Mohammad Ghufran
--
| Rupert Westenthaler rupert.westentha...@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
| REDLINK.CO
..........................................................................
| http://redlink.co/
