Hi Rupert,
Thanks a lot. Gonna try it now. I will let you know if finally I install
it successfully.
Regards
El 07/09/12 10:07, Rupert Westenthaler escribió:
Hi
I was not able to reproduce the problem reported by Dave Butler so it
hard for me to comment on that.
Regarding the installation of the Spotlight engines I would:
1. "mvn clean install" the trunk
2. start a Stanbol launcher (any of them should work)
3. "mvn clean package" the spotlight branch (I use "package" instead
of "install" to not override the the trunk versions of the modules in
the local mvn repository with the versions in the branch).
4. "mvn clean install -PinstallBundle
-Dsling.url=http://localhost:8080/system/console";
You can validate the success by checking
* http://localhost:8080/enhancer/chain/dbpedia-spotlight
* in http://localhost:8080/system/console/bundles the "Apache Stanbol
Enhancer Enhancement Engine : DBPedia Spotlight
(org.apache.stanbol.enhancer.engines.dbpspotlight)" Bundle should be
active
* http://localhost:8080/system/console/components should note 4
Spotlight engines as active (search for "engines.dbpspotlight" to find
them)
For me this steps worked fine. If you have problems please report them.
best
Rupert
On Thu, Sep 6, 2012 at 12:31 PM, Rafa Haro <[email protected]> wrote:
Hi Rupert,
I'm trying to get dbpedia spotlight engines working within a local and clean
Stanbol. So, I checkout the branch and build it and then, I suppose that I
need to install the generated bundles within a running Apache Stanbol. I
have tried to work with the lastest trunk version and I'm having the same
problem that Dave Butler reported about OSGi console login. Do you know
which is the most recent revision without this problem?
Also I might be trying to install spotlight engines in a wrong way, so I'd
appreciate if you can point me a better way to do it.
Thanks. Regards
El 20/08/12 14:38, Rupert Westenthaler escribió:
Hi Iavor, Pablo, all
Back from vacation I started today the work on integrating the dbpedia
spotlight engines into the Apache Stanbol code base. My goal is to
have achieved this by the end of this week, but lets see how things
progress.
For this work I created an own branch
http://svn.apache.org/repos/asf/incubator/stanbol/branches/dbpedia-spotlight-engines/
that in includes just the Stanbol Enhancer (meaning
"{stanbol-trunk}/enhancer" is the root element).
I have already applied the patch provided with STANBOL-706 [2,3] and
added the new engines to the reactor POM files - so that they are
included in the default maven build. I have not yet looked at the code
nor tried to install the engines within a running Apache Stanbol
instance, but I can confirm that the build succeeds.
Comments on the proposed name changes of the used module paths,
artifactIds and package names are also welcome (see comment of
STANBOL-706 [1])
Iavor, Pablo if you are available you may want to join the #stanbol
channel on IRC. If not I will use comments on STANBOL-706 to ask
questions.
best
Rupert
[2] https://issues.apache.org/jira/browse/STANBOL-706
[3] http://svn.apache.org/viewvc?rev=1374984&view=rev (commit messages
wrongly states STANBOL-704 - sorry for that)
On Mon, Jul 30, 2012 at 7:51 PM, Iavor Jelev
<[email protected]> wrote:
Hi Harish,
thanks for your interest. Regarding details on the engine, please refer
to the following blog post (it should answer partly your first and
second question):
http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/
For a functioning demo of the described engines and chains, please refer
to the following Stanbol instance (please note that the engines are
rather "generously" configured, so they will return all results
currently. Filters based on confidence metrics can of course be applied
to improve precision):
http://spotlight.dbpedia.org/stanbol/enhancer/chain
Let me answer your second and third question too:
2) DBpedia Spotlight is a stand alone tool, which was designed to do a
similar task to the current default Stanbol chain. We merely integrated
it in Stanbol with this EnhancementEngines. It goes through the whole
annotation life cycle (NER, DBpedia resources candidate selection,
disambiguation, linking). So it basicly is an alternative to the already
existing engines, as we all know - results differ according to a use
case. So the more alternatives we have to combine (by that I mean
engine), the better optimization possibilities there are. For further
info on DBpedia Spotlight, please refer to the project Wiki
(https://github.com/dbpedia-spotlight/dbpedia-spotlight/wiki)
3) No, it doesn't. As I mentioned - DBpedia Spotlight is a stand alone
tool, and it has it's own indexes.
best,
Iavor
Am 30.07.2012 19:29, schrieb harish suvarna:
Thanks lavor. These will be great of usage.
1. How to use this engine? Should we form a new chain with [tika,
langid,
namedentityextractionenhancementengine, your-new-dbpedia-enginee] for
languages having NLP components.?
2. How is this new dbpedia engine different from dbpediaLinking
(NamedEntityTaggingEngine) or dbpediaKeyword (KeywordLinkingEngine) that
already exists in Stanbol today?
3. does it use the dbpedia solr index provided in the IKS dev conf
through
the USB?
Thanks,
Harish
On Mon, Jul 30, 2012 at 4:50 AM, Iavor Jelev
<[email protected]>wrote:
Hi all,
as mentioned before Pablo and I developed 4 EnhancementEngines, which
integrate the different aspects of DBpedia Spotlight in Apache Stanbol.
We contributed them in JIRA, so if you're interested, give them a try.
If there are any questions or improvement suggestions, I would
appreciate your feedback. Here is the JIRA issue:
https://issues.apache.org/jira/browse/STANBOL-706
kind regards,
Iavor
This message should be regarded as confidential. If you have received this
email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy
by an authorised signatory.
Zaizi Ltd is registered in England and Wales with the registration number
6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
London W10 5JJ, UK.
This message should be regarded as confidential. If you have received this
email in error please notify the sender and destroy it immediately. Statements
of intent shall only become binding when confirmed in hard copy by an
authorised signatory.
Zaizi Ltd is registered in England and Wales with the registration number
6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
London W10 5JJ, UK.
