You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Alessandro Adamou <ad...@cs.unibo.it> on 2012/07/13 18:30:44 UTC
Turtle, Comments and form-urlencoded POST
Hi
I've been going literally MAD over the last few days on a bizarre
phenomenon:
if I POST an ontology
1) in Turtle/N3/N-Triple format on an OntoNet Scope/Session/whatever,
2) I use the service that accepts the payload as
application/x-www-form-urlencoded
3) and that ontology has inline comments (starting in '#'),
then whatever follows that comment is truncated.
Say I have the following code
==================
@prefix : <http://stanbol.apache.org/ontologies/test/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@base <http://stanbol.apache.org/ontologies/test/turtle/sample/comments> .
<http://stanbol.apache.org/ontologies/test/turtle/triples/sample/comments>
rdf:type owl:Ontology .
# Comment
:SomeClazz rdf:type owl:Class .
:SomeThing1 rdf:type :SomeClazz .
==================
stored in the file turtle-comments.rdf
then I do
% curl -i -X PUT http://localhost:8080/ontonet/session/s1
% curl -i -X POST -H "Content-type: text/turtle" -d @turtle-comments.rdf
http://localhost:8080//ontonet/session/s1
Then when I GET the new resource
curl -i -H "Accept: application/rdf+xml"
http://localhost:8080/ontonet/session/s1/http://stanbol.apache.org/ontologies/test/turtle/triples/sample/comments
the last two triples are missing!
Instead, if I force post binary data, as in
% curl -i -X POST -H "Content-type: text/turtle" --data-binary
@turtle-comments.rdf http://localhost:8080//ontonet/session/s1
it seems to work.
It also works if I POST using the multipart/form-data variant
% curl -i -X POST -F "format=text/turtle" -F file=@turtle-comments.rdf
http://localhost:8080/ontonet/session/s1
and both variants do exactly the same thing: they create a
GraphContentInputSource object out of a BufferedInputStream that wraps
the InputStream they get:
- for application/x-www-form-urlencoded it is a
org.mortbay.jetty.HttpParser.Input
- for multipart/form-data it is a FileInputStream
Something seems to be going very wrong when the hash character is
URLencoded, but apparently when it is used in namespaces it doesn't seem
to be a problem.
Not a big deal if I can just get away with it by using --data-binary,
but it's taken me two days to find out.
Does anybody know if this is normal?
Best,
Alessandro
--
M.Sc. Alessandro Adamou
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna - Italy
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy
"I will give you everything, just don't demand anything."
(Ettore Petrolini, 1917)
Not sent from my iSnobTechDevice
Re: DBpedia Spotlight Enhancement Engines
Posted by harish suvarna <hs...@gmail.com>.
One more clarification. I have the 1.19gb dbpedia solr index provided in
IKS conf in the USB. Does it contain all the 97 languages as advocated in
dbpedia.org? I know that there is a chinese dump in there as well in the
dbpedia download server. I hope if we have proper chinese segmentation
ahead in stanbol, dbpedia lookup for it works well.
Also, in your code, you indeed use language tag. Is the language tag used
for accessing the right dbpedia solr index for that language? Are the solr
indexes organized per langauge-field in one index or different language is
a different solr shard? any idea?
Thanks,
Harish
On Mon, Jul 30, 2012 at 10:29 AM, harish suvarna <hs...@gmail.com> wrote:
> 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 <iavor.jelev@babelmonkeys.com
> > 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
>>
>
>
Re: DBpedia Spotlight Enhancement Engines
Posted by Rupert Westenthaler <ru...@gmail.com>.
FYI there is a new Comment on the progress of STANBOL-706 (see
http://s.apache.org/ef).
At the end there are also two questions I would like to have feedback.
best
Rupert
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: DBpedia Spotlight Enhancement Engines
Posted by "Pablo N. Mendes" <pa...@gmail.com>.
Hi all,
I will try to be available on IRC. I added my comments to the ticket.
Cheers,
pablo
On Mon, Aug 20, 2012 at 2:38 PM, Rupert Westenthaler <
rupert.westenthaler@gmail.com> wrote:
> 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
> <ia...@babelmonkeys.com> 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
> >> <ia...@babelmonkeys.com>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
> >>>
> >>
> >
>
>
>
> --
> | Rupert Westenthaler rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
>
--
---
Pablo N. Mendes
http://pablomendes.com
Events: http://wole2012.eurecom.fr
Re: DBpedia Spotlight Enhancement Engines
Posted by Rafa Haro <rh...@zaizi.com>.
Hi Rupert,
I followed your instructions and now I have DBPedia Spotlight working
perfectly in my local machine.
Thanks a lot again for your help
Best 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 <rh...@zaizi.com> 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
>>> <ia...@babelmonkeys.com> 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
>>>>> <ia...@babelmonkeys.com>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.
Re: DBpedia Spotlight Enhancement Engines
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi all,
while there are still some improvements I would like to address (see
Open Issues at the end of http://s.apache.org/Aci) I think that we can
move the DBpedia Spotlight engine over to the trunk. So if nobody
objects I would do the same on Wednesday.
best
Rupert
On Fri, Sep 7, 2012 at 2:26 PM, Rupert Westenthaler
<ru...@gmail.com> wrote:
> Hi,
>
> The "configure" links do currently not work (no Idea how/when I broke
> this, but I noticed this already myself).
>
> On Fri, Sep 7, 2012 at 2:13 PM, Rafa Haro <rh...@zaizi.com> wrote:
>>
>> http://localhost:8080/enhancer/chain/system/console/configMgr/org.apache.stanbol.enhancer.chain.weighted.impl.WeightedChain.361c4c7a-b52b-4add-b537-07980fb63f0f
>>
>
> You need to remove the "/enhancer/chain" part from the URL. Try
>
> http://localhost:8080/system/console/configMgr/org.apache.stanbol.enhancer.chain.weighted.impl.WeightedChain.361c4c7a-b52b-4add-b537-07980fb63f0f
>
>> Anyway, I was wondering if is possible to configure the ContentHub to use
>> the already configured Enhancement Chain dbpedia-spotlight without create a
>> new index, upload an LDPath Program, etc.
>>
>
> The contenthub currently uses the "default" chain. So you need to make
> sure that the Dbpedia Spotlight chain is the default chain. Usually
> you want to rename it to "default" but there are other possibilities
> (see documentation [1] for details)
>
> [1] http://incubator.apache.org/stanbol/docs/trunk/components/enhancer/chains/#default-chain
>
> best
> Rupert
>
>> Thanks in advance
>>
>>
>> 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 <rh...@zaizi.com> 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
>>>>> <ia...@babelmonkeys.com> 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
>>>>>>> <ia...@babelmonkeys.com>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.
>
>
>
> --
> | Rupert Westenthaler rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: DBpedia Spotlight Enhancement Engines
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi,
The "configure" links do currently not work (no Idea how/when I broke
this, but I noticed this already myself).
On Fri, Sep 7, 2012 at 2:13 PM, Rafa Haro <rh...@zaizi.com> wrote:
>
> http://localhost:8080/enhancer/chain/system/console/configMgr/org.apache.stanbol.enhancer.chain.weighted.impl.WeightedChain.361c4c7a-b52b-4add-b537-07980fb63f0f
>
You need to remove the "/enhancer/chain" part from the URL. Try
http://localhost:8080/system/console/configMgr/org.apache.stanbol.enhancer.chain.weighted.impl.WeightedChain.361c4c7a-b52b-4add-b537-07980fb63f0f
> Anyway, I was wondering if is possible to configure the ContentHub to use
> the already configured Enhancement Chain dbpedia-spotlight without create a
> new index, upload an LDPath Program, etc.
>
The contenthub currently uses the "default" chain. So you need to make
sure that the Dbpedia Spotlight chain is the default chain. Usually
you want to rename it to "default" but there are other possibilities
(see documentation [1] for details)
[1] http://incubator.apache.org/stanbol/docs/trunk/components/enhancer/chains/#default-chain
best
Rupert
> Thanks in advance
>
>
> 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 <rh...@zaizi.com> 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
>>>> <ia...@babelmonkeys.com> 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
>>>>>> <ia...@babelmonkeys.com>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.
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: DBpedia Spotlight Enhancement Engines
Posted by Rafa Haro <rh...@zaizi.com>.
Hi again,
Once I have DBPedia Spotlight engine working properly, my next step is
to use ContentHub component to store documents with Spotlight's
enhancements. I suppose I need to configure the default enhancement
chain to use dbpspotlightannotate engine. When I try to do that, I'm
getting a 404 HTTP Error for this URL:
http://localhost:8080/enhancer/chain/system/console/configMgr/org.apache.stanbol.enhancer.chain.weighted.impl.WeightedChain.361c4c7a-b52b-4add-b537-07980fb63f0f
Anyway, I was wondering if is possible to configure the ContentHub to
use the already configured Enhancement Chain dbpedia-spotlight without
create a new index, upload an LDPath Program, etc.
Thanks in advance
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 <rh...@zaizi.com> 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
>>> <ia...@babelmonkeys.com> 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
>>>>> <ia...@babelmonkeys.com>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.
Re: DBpedia Spotlight Enhancement Engines
Posted by Rafa Haro <rh...@zaizi.com>.
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 <rh...@zaizi.com> 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
>>> <ia...@babelmonkeys.com> 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
>>>>> <ia...@babelmonkeys.com>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.
Re: DBpedia Spotlight Enhancement Engines
Posted by Rupert Westenthaler <ru...@gmail.com>.
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 <rh...@zaizi.com> 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
>> <ia...@babelmonkeys.com> 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
>>>> <ia...@babelmonkeys.com>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.
>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: DBpedia Spotlight Enhancement Engines
Posted by Rafa Haro <rh...@zaizi.com>.
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
> <ia...@babelmonkeys.com> 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
>>> <ia...@babelmonkeys.com>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.
Re: DBpedia Spotlight Enhancement Engines
Posted by Rupert Westenthaler <ru...@gmail.com>.
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
<ia...@babelmonkeys.com> 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
>> <ia...@babelmonkeys.com>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
>>>
>>
>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: DBpedia Spotlight Enhancement Engines
Posted by Iavor Jelev <ia...@babelmonkeys.com>.
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
> <ia...@babelmonkeys.com>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
>>
>
Re: DBpedia Spotlight Enhancement Engines
Posted by harish suvarna <hs...@gmail.com>.
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
<ia...@babelmonkeys.com>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
>
DBpedia Spotlight Enhancement Engines
Posted by Iavor Jelev <ia...@babelmonkeys.com>.
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
Re: contenthub CRUD
Posted by Suat Gonul <su...@gmail.com>.
Hi Melanie,
Glad to hear that!
Best,
Suat
On 07/31/2012 02:10 PM, Melanie Reiplinger wrote:
> Hi Suat,
>
> full CRUD access on the contenthub confirmed.
> Thank you a lot.
>
> Best,
> melanie
>
>
> Am 30.07.2012 13:36, schrieb Suat Gonul:
>> Hello Melanie,
>>
>> The changes in the [1] should have added the CORS support for deletion
>> of content items. I suspect that you may have been using some old
>> revisions, since there was a bug in the maven-clean-plugin
>> configurations of the full launcher. Also, I can delete content items
>> from a remote server successfully. I just fixed the bug in the full
>> launcher. Could you please update and rebuilt it?
>>
>> Best,
>> Suat
>>
>> [1]
>> http://svn.apache.org/viewvc/incubator/stanbol/trunk/contenthub/web/src/main/java/org/apache/stanbol/contenthub/web/resources/StoreResource.java?view=diff&r1=1362396&r2=1362397&pathrev=1362397
>>
>>
>> On 07/30/2012 01:06 PM, Melanie Reiplinger wrote:
>>> Hello Suat,
>>>
>>> thanks for your help. I updated and rebuilt the contenthub today, but
>>> it seems I still can't get through with the DELETE. When trying to
>>> delete a content item, the preflight keeps returning only GET, POST
>>> and OPTIONS to me as the allowed methods.
>>>
>>> 1.
>>> Request URL:
>>>
>>> http://lnv-89012.dfki.uni-sb.de:9001/contenthub/contenthub/store/urn:melaniesitem
>>> 2.
>>> Request Method:
>>> OPTIONS
>>> 3.
>>> Status Code:
>>> 200 OK(from cache)
>>> 4. Request Headersview source
>>> 1.
>>> Accept:
>>> */*
>>> 2.
>>> Accept-Charset:
>>> ISO-8859-1,utf-8;q=0.7,*;q=0.3
>>> 3.
>>> Accept-Encoding:
>>> gzip,deflate,sdch
>>> 4.
>>> Accept-Language:
>>> de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4
>>> 5.
>>> Access-Control-Request-Headers:
>>> origin, accept
>>> 6.
>>> Access-Control-Request-Method:
>>> DELETE
>>> 7.
>>> Connection:
>>> keep-alive
>>> 8.
>>> Host:
>>> lnv-89012.dfki.uni-sb.de:9001
>>> 9.
>>> Origin:
>>> http://localhost
>>> 10.
>>> Referer:
>>> http://localhost/VIE/test/?testNumber=56
>>> 11.
>>> User-Agent:
>>> Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML,
>>> like Gecko) Chrome/20.0.1132.57 Safari/536.11
>>> 5. Response Headersview source
>>> 1.
>>> Access-Control-Allow-Headers:
>>> origin, accept
>>> 2.
>>> Access-Control-Allow-Methods:
>>> GET, POST, OPTIONS
>>> 3.
>>> Access-Control-Allow-Origin:
>>> *
>>> 4.
>>> Access-Control-Expose-Headers:
>>> Location
>>> 5.
>>> Content-Length:
>>> 0
>>> 6.
>>> Server:
>>> Jetty(6.1.x)
>>>
>>>
>>> and when trying to delete an Index, I get '204 Not Content' and the
>>> response header looks pretty strange:
>>>
>>> 1.
>>> Allow:
>>> OPTIONS,DELETE
>>> 2.
>>> Server:
>>> Jetty(6.1.x)
>>> 3.
>>>
>>> Do I need to update something else apart from the contenthub?
>>>
>>> As to submitting new indices, I'm a bit confused now. When submitting
>>> an ldpath program via the web interface, a Form Data object seems to
>>> be used to carry the data:
>>>
>>> 1.
>>>
>>>
>>> 1. Form Dataview URL encoded
>>> 1.
>>> name:
>>> melaniesIndex
>>> 2.
>>> program:
>>> @prefix rdf : <http://www.w3.org/1999/02/22-rdf-syntax-ns#>;
>>> @prefix rdfs : <http://www.w3.org/2000/01/rdf-schema#>; @prefix
>>> db-ont : <http://dbpedia.org/ontology/>; title = rdfs:label ::
>>> xsd:string; dbpediatype = rdf:type :: xsd:anyURI; population =
>>> db-ont:populationTotal :: xsd:int;
>>>
>>>
>>> But anyway, the curl -d works as you say and I could also implement it
>>> for the XmlHttpRequest.
>>>
>>> Best,
>>> melanie
>>>
>>>
>>> Am 17.07.2012 10:14, schrieb Suat Gonul:
>>>> Hi Alessandro, Melanie,
>>>>
>>>> @Alessandro, thanks for the answer.
>>>>
>>>> @Melanie, to be able to submit an LDPath program, the correct usage
>>>> with
>>>> curl are is follows. Currently, this endpoint does not support sending
>>>> requests with (form-multipart) objects.
>>>>
>>>> curl -i -X POST -d "name=melaniesIndex&program=@prefix rdf :
>>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#
>>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>>; @prefix rdfs :
>>>> <http://www.w3.org/2000/01/rdf-schema#
>>>> <http://www.w3.org/2000/01/rdf-schema#>>; @prefix db-ont :
>>>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>>>> dbpediatype = rdf:type :: xsd:anyURI; population =
>>>> db-ont:populationTotal :: xsd:int;"
>>>> http://<stanbol>/contenthub/ldpath/program
>>>>
>>>> Also, I fixed the CORS support issues you mentioned. Please let me
>>>> know
>>>> if you have any other problems.
>>>>
>>>> Best,
>>>> Suat
>>>>
>>>>
>>>> On 07/16/2012 12:36 PM, Alessandro Adamou wrote:
>>>>> Hi Melanie,
>>>>>
>>>>> I can see that path has a preflight handling function, so it should
>>>>> support CORS.
>>>>>
>>>>> However it doesn't specify the allowed methods. Perhaps the line
>>>>>
>>>>> enableCORS(servletContext, res, headers);
>>>>>
>>>>> should be
>>>>>
>>>>> enableCORS(servletContext, res, headers, GET, POST, DELETE, OPTIONS);
>>>>>
>>>>> like I had to do for the ontologymanager endpoint to work?
>>>>>
>>>>> --Alessandro
>>>>>
>>>>>
>>>>> On 7/15/12 7:55 PM, Melanie Reiplinger wrote:
>>>>>> Hi Rupert, Alessandro.
>>>>>>
>>>>>> Is it possible that we still do not have CRUD access on the
>>>>>> contenthub?
>>>>>>
>>>>>> When doing a DELETE on
>>>>>>
>>>>>> <stanbol>/contenthub/contenthub/store/<itemID>,
>>>>>>
>>>>>> I'm getting
>>>>>>
>>>>>> Access-Control-Allow-Methods: GET, POST, OPTIONS
>>>>>>
>>>>>> as response to the preflight request (so DELETE would be missing
>>>>>> then).
>>>>>>
>>>>>> The same problem for
>>>>>> <stanbol>/contenthub/ldpath/program/<indexID>.
>>>>>>
>>>>>> When trying to create an index by sending a FormData object
>>>>>> (form-multipart) to contenthub/ldpath/program, my request gets
>>>>>> stuck.
>>>>>> I can't even get through with curl:
>>>>>>
>>>>>> curl -i -X POST -F 'name=melaniesIndex' -F "program='@prefix rdf :
>>>>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>; @prefix rdfs :
>>>>>> <http://www.w3.org/2000/01/rdf-schema#>; @prefix db-ont :
>>>>>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>>>>>> dbpediatype = rdf:type :: xsd:anyURI; population =
>>>>>> db-ont:populationTotal :: xsd:int;'"
>>>>>> http://<stanbol>/contenthub/ldpath/program
>>>>>>
>>>>>> I get Unsupported Media Type error. I guess there's some issue with
>>>>>> the @ symbols in the program (normally they are used to reference
>>>>>> files), but escaping them was of no use.
>>>>>>
>>>>>>
>>>>>> And one more minor thing:
>>>>>>
>>>>>> For
>>>>>> curl -i -X DELETE <stanbol>/contenthub/ldpath/program/melaniesIndex
>>>>>>
>>>>>> I get
>>>>>> HTTP/1.1 200 OK
>>>>>> Content-Length: 0
>>>>>> Server: Jetty(6.1.x)
>>>>>>
>>>>>> even if the index does not exist any more (i.e., if it has been
>>>>>> deleted before).
>>>>>>
>>>>>> g
>>>>>> melanie
>>>>>>
>>>>>>
>>>
>
>
Re: contenthub CRUD
Posted by Melanie Reiplinger <me...@dfki.de>.
Hi Suat,
full CRUD access on the contenthub confirmed.
Thank you a lot.
Best,
melanie
Am 30.07.2012 13:36, schrieb Suat Gonul:
> Hello Melanie,
>
> The changes in the [1] should have added the CORS support for deletion
> of content items. I suspect that you may have been using some old
> revisions, since there was a bug in the maven-clean-plugin
> configurations of the full launcher. Also, I can delete content items
> from a remote server successfully. I just fixed the bug in the full
> launcher. Could you please update and rebuilt it?
>
> Best,
> Suat
>
> [1]
> http://svn.apache.org/viewvc/incubator/stanbol/trunk/contenthub/web/src/main/java/org/apache/stanbol/contenthub/web/resources/StoreResource.java?view=diff&r1=1362396&r2=1362397&pathrev=1362397
>
> On 07/30/2012 01:06 PM, Melanie Reiplinger wrote:
>> Hello Suat,
>>
>> thanks for your help. I updated and rebuilt the contenthub today, but
>> it seems I still can't get through with the DELETE. When trying to
>> delete a content item, the preflight keeps returning only GET, POST
>> and OPTIONS to me as the allowed methods.
>>
>> 1.
>> Request URL:
>>
>> http://lnv-89012.dfki.uni-sb.de:9001/contenthub/contenthub/store/urn:melaniesitem
>> 2.
>> Request Method:
>> OPTIONS
>> 3.
>> Status Code:
>> 200 OK(from cache)
>> 4. Request Headersview source
>> 1.
>> Accept:
>> */*
>> 2.
>> Accept-Charset:
>> ISO-8859-1,utf-8;q=0.7,*;q=0.3
>> 3.
>> Accept-Encoding:
>> gzip,deflate,sdch
>> 4.
>> Accept-Language:
>> de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4
>> 5.
>> Access-Control-Request-Headers:
>> origin, accept
>> 6.
>> Access-Control-Request-Method:
>> DELETE
>> 7.
>> Connection:
>> keep-alive
>> 8.
>> Host:
>> lnv-89012.dfki.uni-sb.de:9001
>> 9.
>> Origin:
>> http://localhost
>> 10.
>> Referer:
>> http://localhost/VIE/test/?testNumber=56
>> 11.
>> User-Agent:
>> Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML,
>> like Gecko) Chrome/20.0.1132.57 Safari/536.11
>> 5. Response Headersview source
>> 1.
>> Access-Control-Allow-Headers:
>> origin, accept
>> 2.
>> Access-Control-Allow-Methods:
>> GET, POST, OPTIONS
>> 3.
>> Access-Control-Allow-Origin:
>> *
>> 4.
>> Access-Control-Expose-Headers:
>> Location
>> 5.
>> Content-Length:
>> 0
>> 6.
>> Server:
>> Jetty(6.1.x)
>>
>>
>> and when trying to delete an Index, I get '204 Not Content' and the
>> response header looks pretty strange:
>>
>> 1.
>> Allow:
>> OPTIONS,DELETE
>> 2.
>> Server:
>> Jetty(6.1.x)
>> 3.
>>
>> Do I need to update something else apart from the contenthub?
>>
>> As to submitting new indices, I'm a bit confused now. When submitting
>> an ldpath program via the web interface, a Form Data object seems to
>> be used to carry the data:
>>
>> 1.
>>
>>
>> 1. Form Dataview URL encoded
>> 1.
>> name:
>> melaniesIndex
>> 2.
>> program:
>> @prefix rdf : <http://www.w3.org/1999/02/22-rdf-syntax-ns#>;
>> @prefix rdfs : <http://www.w3.org/2000/01/rdf-schema#>; @prefix
>> db-ont : <http://dbpedia.org/ontology/>; title = rdfs:label ::
>> xsd:string; dbpediatype = rdf:type :: xsd:anyURI; population =
>> db-ont:populationTotal :: xsd:int;
>>
>>
>> But anyway, the curl -d works as you say and I could also implement it
>> for the XmlHttpRequest.
>>
>> Best,
>> melanie
>>
>>
>> Am 17.07.2012 10:14, schrieb Suat Gonul:
>>> Hi Alessandro, Melanie,
>>>
>>> @Alessandro, thanks for the answer.
>>>
>>> @Melanie, to be able to submit an LDPath program, the correct usage with
>>> curl are is follows. Currently, this endpoint does not support sending
>>> requests with (form-multipart) objects.
>>>
>>> curl -i -X POST -d "name=melaniesIndex&program=@prefix rdf :
>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#
>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>>; @prefix rdfs :
>>> <http://www.w3.org/2000/01/rdf-schema#
>>> <http://www.w3.org/2000/01/rdf-schema#>>; @prefix db-ont :
>>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>>> dbpediatype = rdf:type :: xsd:anyURI; population =
>>> db-ont:populationTotal :: xsd:int;"
>>> http://<stanbol>/contenthub/ldpath/program
>>>
>>> Also, I fixed the CORS support issues you mentioned. Please let me know
>>> if you have any other problems.
>>>
>>> Best,
>>> Suat
>>>
>>>
>>> On 07/16/2012 12:36 PM, Alessandro Adamou wrote:
>>>> Hi Melanie,
>>>>
>>>> I can see that path has a preflight handling function, so it should
>>>> support CORS.
>>>>
>>>> However it doesn't specify the allowed methods. Perhaps the line
>>>>
>>>> enableCORS(servletContext, res, headers);
>>>>
>>>> should be
>>>>
>>>> enableCORS(servletContext, res, headers, GET, POST, DELETE, OPTIONS);
>>>>
>>>> like I had to do for the ontologymanager endpoint to work?
>>>>
>>>> --Alessandro
>>>>
>>>>
>>>> On 7/15/12 7:55 PM, Melanie Reiplinger wrote:
>>>>> Hi Rupert, Alessandro.
>>>>>
>>>>> Is it possible that we still do not have CRUD access on the
>>>>> contenthub?
>>>>>
>>>>> When doing a DELETE on
>>>>>
>>>>> <stanbol>/contenthub/contenthub/store/<itemID>,
>>>>>
>>>>> I'm getting
>>>>>
>>>>> Access-Control-Allow-Methods: GET, POST, OPTIONS
>>>>>
>>>>> as response to the preflight request (so DELETE would be missing
>>>>> then).
>>>>>
>>>>> The same problem for
>>>>> <stanbol>/contenthub/ldpath/program/<indexID>.
>>>>>
>>>>> When trying to create an index by sending a FormData object
>>>>> (form-multipart) to contenthub/ldpath/program, my request gets stuck.
>>>>> I can't even get through with curl:
>>>>>
>>>>> curl -i -X POST -F 'name=melaniesIndex' -F "program='@prefix rdf :
>>>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>; @prefix rdfs :
>>>>> <http://www.w3.org/2000/01/rdf-schema#>; @prefix db-ont :
>>>>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>>>>> dbpediatype = rdf:type :: xsd:anyURI; population =
>>>>> db-ont:populationTotal :: xsd:int;'"
>>>>> http://<stanbol>/contenthub/ldpath/program
>>>>>
>>>>> I get Unsupported Media Type error. I guess there's some issue with
>>>>> the @ symbols in the program (normally they are used to reference
>>>>> files), but escaping them was of no use.
>>>>>
>>>>>
>>>>> And one more minor thing:
>>>>>
>>>>> For
>>>>> curl -i -X DELETE <stanbol>/contenthub/ldpath/program/melaniesIndex
>>>>>
>>>>> I get
>>>>> HTTP/1.1 200 OK
>>>>> Content-Length: 0
>>>>> Server: Jetty(6.1.x)
>>>>>
>>>>> even if the index does not exist any more (i.e., if it has been
>>>>> deleted before).
>>>>>
>>>>> g
>>>>> melanie
>>>>>
>>>>>
>>
Re: contenthub CRUD
Posted by Suat Gonul <su...@gmail.com>.
Hello Melanie,
The changes in the [1] should have added the CORS support for deletion
of content items. I suspect that you may have been using some old
revisions, since there was a bug in the maven-clean-plugin
configurations of the full launcher. Also, I can delete content items
from a remote server successfully. I just fixed the bug in the full
launcher. Could you please update and rebuilt it?
Best,
Suat
[1]
http://svn.apache.org/viewvc/incubator/stanbol/trunk/contenthub/web/src/main/java/org/apache/stanbol/contenthub/web/resources/StoreResource.java?view=diff&r1=1362396&r2=1362397&pathrev=1362397
On 07/30/2012 01:06 PM, Melanie Reiplinger wrote:
> Hello Suat,
>
> thanks for your help. I updated and rebuilt the contenthub today, but
> it seems I still can't get through with the DELETE. When trying to
> delete a content item, the preflight keeps returning only GET, POST
> and OPTIONS to me as the allowed methods.
>
> 1.
> Request URL:
>
> http://lnv-89012.dfki.uni-sb.de:9001/contenthub/contenthub/store/urn:melaniesitem
> 2.
> Request Method:
> OPTIONS
> 3.
> Status Code:
> 200 OK(from cache)
> 4. Request Headersview source
> 1.
> Accept:
> */*
> 2.
> Accept-Charset:
> ISO-8859-1,utf-8;q=0.7,*;q=0.3
> 3.
> Accept-Encoding:
> gzip,deflate,sdch
> 4.
> Accept-Language:
> de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4
> 5.
> Access-Control-Request-Headers:
> origin, accept
> 6.
> Access-Control-Request-Method:
> DELETE
> 7.
> Connection:
> keep-alive
> 8.
> Host:
> lnv-89012.dfki.uni-sb.de:9001
> 9.
> Origin:
> http://localhost
> 10.
> Referer:
> http://localhost/VIE/test/?testNumber=56
> 11.
> User-Agent:
> Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML,
> like Gecko) Chrome/20.0.1132.57 Safari/536.11
> 5. Response Headersview source
> 1.
> Access-Control-Allow-Headers:
> origin, accept
> 2.
> Access-Control-Allow-Methods:
> GET, POST, OPTIONS
> 3.
> Access-Control-Allow-Origin:
> *
> 4.
> Access-Control-Expose-Headers:
> Location
> 5.
> Content-Length:
> 0
> 6.
> Server:
> Jetty(6.1.x)
>
>
> and when trying to delete an Index, I get '204 Not Content' and the
> response header looks pretty strange:
>
> 1.
> Allow:
> OPTIONS,DELETE
> 2.
> Server:
> Jetty(6.1.x)
> 3.
>
> Do I need to update something else apart from the contenthub?
>
> As to submitting new indices, I'm a bit confused now. When submitting
> an ldpath program via the web interface, a Form Data object seems to
> be used to carry the data:
>
> 1.
>
>
> 1. Form Dataview URL encoded
> 1.
> name:
> melaniesIndex
> 2.
> program:
> @prefix rdf : <http://www.w3.org/1999/02/22-rdf-syntax-ns#>;
> @prefix rdfs : <http://www.w3.org/2000/01/rdf-schema#>; @prefix
> db-ont : <http://dbpedia.org/ontology/>; title = rdfs:label ::
> xsd:string; dbpediatype = rdf:type :: xsd:anyURI; population =
> db-ont:populationTotal :: xsd:int;
>
>
> But anyway, the curl -d works as you say and I could also implement it
> for the XmlHttpRequest.
>
> Best,
> melanie
>
>
> Am 17.07.2012 10:14, schrieb Suat Gonul:
>> Hi Alessandro, Melanie,
>>
>> @Alessandro, thanks for the answer.
>>
>> @Melanie, to be able to submit an LDPath program, the correct usage with
>> curl are is follows. Currently, this endpoint does not support sending
>> requests with (form-multipart) objects.
>>
>> curl -i -X POST -d "name=melaniesIndex&program=@prefix rdf :
>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#
>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>>; @prefix rdfs :
>> <http://www.w3.org/2000/01/rdf-schema#
>> <http://www.w3.org/2000/01/rdf-schema#>>; @prefix db-ont :
>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>> dbpediatype = rdf:type :: xsd:anyURI; population =
>> db-ont:populationTotal :: xsd:int;"
>> http://<stanbol>/contenthub/ldpath/program
>>
>> Also, I fixed the CORS support issues you mentioned. Please let me know
>> if you have any other problems.
>>
>> Best,
>> Suat
>>
>>
>> On 07/16/2012 12:36 PM, Alessandro Adamou wrote:
>>> Hi Melanie,
>>>
>>> I can see that path has a preflight handling function, so it should
>>> support CORS.
>>>
>>> However it doesn't specify the allowed methods. Perhaps the line
>>>
>>> enableCORS(servletContext, res, headers);
>>>
>>> should be
>>>
>>> enableCORS(servletContext, res, headers, GET, POST, DELETE, OPTIONS);
>>>
>>> like I had to do for the ontologymanager endpoint to work?
>>>
>>> --Alessandro
>>>
>>>
>>> On 7/15/12 7:55 PM, Melanie Reiplinger wrote:
>>>> Hi Rupert, Alessandro.
>>>>
>>>> Is it possible that we still do not have CRUD access on the
>>>> contenthub?
>>>>
>>>> When doing a DELETE on
>>>>
>>>> <stanbol>/contenthub/contenthub/store/<itemID>,
>>>>
>>>> I'm getting
>>>>
>>>> Access-Control-Allow-Methods: GET, POST, OPTIONS
>>>>
>>>> as response to the preflight request (so DELETE would be missing
>>>> then).
>>>>
>>>> The same problem for
>>>> <stanbol>/contenthub/ldpath/program/<indexID>.
>>>>
>>>> When trying to create an index by sending a FormData object
>>>> (form-multipart) to contenthub/ldpath/program, my request gets stuck.
>>>> I can't even get through with curl:
>>>>
>>>> curl -i -X POST -F 'name=melaniesIndex' -F "program='@prefix rdf :
>>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>; @prefix rdfs :
>>>> <http://www.w3.org/2000/01/rdf-schema#>; @prefix db-ont :
>>>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>>>> dbpediatype = rdf:type :: xsd:anyURI; population =
>>>> db-ont:populationTotal :: xsd:int;'"
>>>> http://<stanbol>/contenthub/ldpath/program
>>>>
>>>> I get Unsupported Media Type error. I guess there's some issue with
>>>> the @ symbols in the program (normally they are used to reference
>>>> files), but escaping them was of no use.
>>>>
>>>>
>>>> And one more minor thing:
>>>>
>>>> For
>>>> curl -i -X DELETE <stanbol>/contenthub/ldpath/program/melaniesIndex
>>>>
>>>> I get
>>>> HTTP/1.1 200 OK
>>>> Content-Length: 0
>>>> Server: Jetty(6.1.x)
>>>>
>>>> even if the index does not exist any more (i.e., if it has been
>>>> deleted before).
>>>>
>>>> g
>>>> melanie
>>>>
>>>>
>>>
>>
>
>
Re: contenthub CRUD
Posted by Melanie Reiplinger <me...@dfki.de>.
Hello Suat,
thanks for your help. I updated and rebuilt the contenthub today, but it
seems I still can't get through with the DELETE. When trying to delete a
content item, the preflight keeps returning only GET, POST and OPTIONS
to me as the allowed methods.
1.
Request URL:
http://lnv-89012.dfki.uni-sb.de:9001/contenthub/contenthub/store/urn:melaniesitem
2.
Request Method:
OPTIONS
3.
Status Code:
200 OK(from cache)
4. Request Headersview source
1.
Accept:
*/*
2.
Accept-Charset:
ISO-8859-1,utf-8;q=0.7,*;q=0.3
3.
Accept-Encoding:
gzip,deflate,sdch
4.
Accept-Language:
de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4
5.
Access-Control-Request-Headers:
origin, accept
6.
Access-Control-Request-Method:
DELETE
7.
Connection:
keep-alive
8.
Host:
lnv-89012.dfki.uni-sb.de:9001
9.
Origin:
http://localhost
10.
Referer:
http://localhost/VIE/test/?testNumber=56
11.
User-Agent:
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML,
like Gecko) Chrome/20.0.1132.57 Safari/536.11
5. Response Headersview source
1.
Access-Control-Allow-Headers:
origin, accept
2.
Access-Control-Allow-Methods:
GET, POST, OPTIONS
3.
Access-Control-Allow-Origin:
*
4.
Access-Control-Expose-Headers:
Location
5.
Content-Length:
0
6.
Server:
Jetty(6.1.x)
and when trying to delete an Index, I get '204 Not Content' and the
response header looks pretty strange:
1.
Allow:
OPTIONS,DELETE
2.
Server:
Jetty(6.1.x)
3.
Do I need to update something else apart from the contenthub?
As to submitting new indices, I'm a bit confused now. When submitting an
ldpath program via the web interface, a Form Data object seems to be
used to carry the data:
1.
1. Form Dataview URL encoded
1.
name:
melaniesIndex
2.
program:
@prefix rdf : <http://www.w3.org/1999/02/22-rdf-syntax-ns#>;
@prefix rdfs : <http://www.w3.org/2000/01/rdf-schema#>; @prefix
db-ont : <http://dbpedia.org/ontology/>; title = rdfs:label ::
xsd:string; dbpediatype = rdf:type :: xsd:anyURI; population =
db-ont:populationTotal :: xsd:int;
But anyway, the curl -d works as you say and I could also implement it
for the XmlHttpRequest.
Best,
melanie
Am 17.07.2012 10:14, schrieb Suat Gonul:
> Hi Alessandro, Melanie,
>
> @Alessandro, thanks for the answer.
>
> @Melanie, to be able to submit an LDPath program, the correct usage with
> curl are is follows. Currently, this endpoint does not support sending
> requests with (form-multipart) objects.
>
> curl -i -X POST -d "name=melaniesIndex&program=@prefix rdf :
> <http://www.w3.org/1999/02/22-rdf-syntax-ns#
> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>>; @prefix rdfs :
> <http://www.w3.org/2000/01/rdf-schema#
> <http://www.w3.org/2000/01/rdf-schema#>>; @prefix db-ont :
> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
> dbpediatype = rdf:type :: xsd:anyURI; population =
> db-ont:populationTotal :: xsd:int;"
> http://<stanbol>/contenthub/ldpath/program
>
> Also, I fixed the CORS support issues you mentioned. Please let me know
> if you have any other problems.
>
> Best,
> Suat
>
>
> On 07/16/2012 12:36 PM, Alessandro Adamou wrote:
>> Hi Melanie,
>>
>> I can see that path has a preflight handling function, so it should
>> support CORS.
>>
>> However it doesn't specify the allowed methods. Perhaps the line
>>
>> enableCORS(servletContext, res, headers);
>>
>> should be
>>
>> enableCORS(servletContext, res, headers, GET, POST, DELETE, OPTIONS);
>>
>> like I had to do for the ontologymanager endpoint to work?
>>
>> --Alessandro
>>
>>
>> On 7/15/12 7:55 PM, Melanie Reiplinger wrote:
>>> Hi Rupert, Alessandro.
>>>
>>> Is it possible that we still do not have CRUD access on the contenthub?
>>>
>>> When doing a DELETE on
>>>
>>> <stanbol>/contenthub/contenthub/store/<itemID>,
>>>
>>> I'm getting
>>>
>>> Access-Control-Allow-Methods: GET, POST, OPTIONS
>>>
>>> as response to the preflight request (so DELETE would be missing then).
>>>
>>> The same problem for
>>> <stanbol>/contenthub/ldpath/program/<indexID>.
>>>
>>> When trying to create an index by sending a FormData object
>>> (form-multipart) to contenthub/ldpath/program, my request gets stuck.
>>> I can't even get through with curl:
>>>
>>> curl -i -X POST -F 'name=melaniesIndex' -F "program='@prefix rdf :
>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>; @prefix rdfs :
>>> <http://www.w3.org/2000/01/rdf-schema#>; @prefix db-ont :
>>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>>> dbpediatype = rdf:type :: xsd:anyURI; population =
>>> db-ont:populationTotal :: xsd:int;'"
>>> http://<stanbol>/contenthub/ldpath/program
>>>
>>> I get Unsupported Media Type error. I guess there's some issue with
>>> the @ symbols in the program (normally they are used to reference
>>> files), but escaping them was of no use.
>>>
>>>
>>> And one more minor thing:
>>>
>>> For
>>> curl -i -X DELETE <stanbol>/contenthub/ldpath/program/melaniesIndex
>>>
>>> I get
>>> HTTP/1.1 200 OK
>>> Content-Length: 0
>>> Server: Jetty(6.1.x)
>>>
>>> even if the index does not exist any more (i.e., if it has been
>>> deleted before).
>>>
>>> g
>>> melanie
>>>
>>>
>>
>
Re: contenthub CRUD
Posted by Suat Gonul <su...@gmail.com>.
Hi Alessandro, Melanie,
@Alessandro, thanks for the answer.
@Melanie, to be able to submit an LDPath program, the correct usage with
curl are is follows. Currently, this endpoint does not support sending
requests with (form-multipart) objects.
curl -i -X POST -d "name=melaniesIndex&program=@prefix rdf :
<http://www.w3.org/1999/02/22-rdf-syntax-ns#
<http://www.w3.org/1999/02/22-rdf-syntax-ns#>>; @prefix rdfs :
<http://www.w3.org/2000/01/rdf-schema#
<http://www.w3.org/2000/01/rdf-schema#>>; @prefix db-ont :
<http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
dbpediatype = rdf:type :: xsd:anyURI; population =
db-ont:populationTotal :: xsd:int;"
http://<stanbol>/contenthub/ldpath/program
Also, I fixed the CORS support issues you mentioned. Please let me know
if you have any other problems.
Best,
Suat
On 07/16/2012 12:36 PM, Alessandro Adamou wrote:
> Hi Melanie,
>
> I can see that path has a preflight handling function, so it should
> support CORS.
>
> However it doesn't specify the allowed methods. Perhaps the line
>
> enableCORS(servletContext, res, headers);
>
> should be
>
> enableCORS(servletContext, res, headers, GET, POST, DELETE, OPTIONS);
>
> like I had to do for the ontologymanager endpoint to work?
>
> --Alessandro
>
>
> On 7/15/12 7:55 PM, Melanie Reiplinger wrote:
>> Hi Rupert, Alessandro.
>>
>> Is it possible that we still do not have CRUD access on the contenthub?
>>
>> When doing a DELETE on
>>
>> <stanbol>/contenthub/contenthub/store/<itemID>,
>>
>> I'm getting
>>
>> Access-Control-Allow-Methods: GET, POST, OPTIONS
>>
>> as response to the preflight request (so DELETE would be missing then).
>>
>> The same problem for
>> <stanbol>/contenthub/ldpath/program/<indexID>.
>>
>> When trying to create an index by sending a FormData object
>> (form-multipart) to contenthub/ldpath/program, my request gets stuck.
>> I can't even get through with curl:
>>
>> curl -i -X POST -F 'name=melaniesIndex' -F "program='@prefix rdf :
>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>; @prefix rdfs :
>> <http://www.w3.org/2000/01/rdf-schema#>; @prefix db-ont :
>> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
>> dbpediatype = rdf:type :: xsd:anyURI; population =
>> db-ont:populationTotal :: xsd:int;'"
>> http://<stanbol>/contenthub/ldpath/program
>>
>> I get Unsupported Media Type error. I guess there's some issue with
>> the @ symbols in the program (normally they are used to reference
>> files), but escaping them was of no use.
>>
>>
>> And one more minor thing:
>>
>> For
>> curl -i -X DELETE <stanbol>/contenthub/ldpath/program/melaniesIndex
>>
>> I get
>> HTTP/1.1 200 OK
>> Content-Length: 0
>> Server: Jetty(6.1.x)
>>
>> even if the index does not exist any more (i.e., if it has been
>> deleted before).
>>
>> g
>> melanie
>>
>>
>
>
Re: contenthub CRUD
Posted by Alessandro Adamou <ad...@cs.unibo.it>.
Hi Melanie,
I can see that path has a preflight handling function, so it should
support CORS.
However it doesn't specify the allowed methods. Perhaps the line
enableCORS(servletContext, res, headers);
should be
enableCORS(servletContext, res, headers, GET, POST, DELETE, OPTIONS);
like I had to do for the ontologymanager endpoint to work?
--Alessandro
On 7/15/12 7:55 PM, Melanie Reiplinger wrote:
> Hi Rupert, Alessandro.
>
> Is it possible that we still do not have CRUD access on the contenthub?
>
> When doing a DELETE on
>
> <stanbol>/contenthub/contenthub/store/<itemID>,
>
> I'm getting
>
> Access-Control-Allow-Methods: GET, POST, OPTIONS
>
> as response to the preflight request (so DELETE would be missing then).
>
> The same problem for
> <stanbol>/contenthub/ldpath/program/<indexID>.
>
> When trying to create an index by sending a FormData object
> (form-multipart) to contenthub/ldpath/program, my request gets stuck.
> I can't even get through with curl:
>
> curl -i -X POST -F 'name=melaniesIndex' -F "program='@prefix rdf :
> <http://www.w3.org/1999/02/22-rdf-syntax-ns#>; @prefix rdfs :
> <http://www.w3.org/2000/01/rdf-schema#>; @prefix db-ont :
> <http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
> dbpediatype = rdf:type :: xsd:anyURI; population =
> db-ont:populationTotal :: xsd:int;'"
> http://<stanbol>/contenthub/ldpath/program
>
> I get Unsupported Media Type error. I guess there's some issue with
> the @ symbols in the program (normally they are used to reference
> files), but escaping them was of no use.
>
>
> And one more minor thing:
>
> For
> curl -i -X DELETE <stanbol>/contenthub/ldpath/program/melaniesIndex
>
> I get
> HTTP/1.1 200 OK
> Content-Length: 0
> Server: Jetty(6.1.x)
>
> even if the index does not exist any more (i.e., if it has been
> deleted before).
>
> g
> melanie
>
>
--
M.Sc. Alessandro Adamou
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna - Italy
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy
"I will give you everything, just don't demand anything."
(Ettore Petrolini, 1917)
Not sent from my iSnobTechDevice
contenthub CRUD
Posted by Melanie Reiplinger <me...@dfki.de>.
Hi Rupert, Alessandro.
Is it possible that we still do not have CRUD access on the contenthub?
When doing a DELETE on
<stanbol>/contenthub/contenthub/store/<itemID>,
I'm getting
Access-Control-Allow-Methods: GET, POST, OPTIONS
as response to the preflight request (so DELETE would be missing then).
The same problem for
<stanbol>/contenthub/ldpath/program/<indexID>.
When trying to create an index by sending a FormData object
(form-multipart) to contenthub/ldpath/program, my request gets stuck. I
can't even get through with curl:
curl -i -X POST -F 'name=melaniesIndex' -F "program='@prefix rdf :
<http://www.w3.org/1999/02/22-rdf-syntax-ns#>; @prefix rdfs :
<http://www.w3.org/2000/01/rdf-schema#>; @prefix db-ont :
<http://dbpedia.org/ontology/>; title = rdfs:label :: xsd:string;
dbpediatype = rdf:type :: xsd:anyURI; population =
db-ont:populationTotal :: xsd:int;'"
http://<stanbol>/contenthub/ldpath/program
I get Unsupported Media Type error. I guess there's some issue with the
@ symbols in the program (normally they are used to reference files),
but escaping them was of no use.
And one more minor thing:
For
curl -i -X DELETE <stanbol>/contenthub/ldpath/program/melaniesIndex
I get
HTTP/1.1 200 OK
Content-Length: 0
Server: Jetty(6.1.x)
even if the index does not exist any more (i.e., if it has been deleted
before).
g
melanie
Re: Turtle, Comments and form-urlencoded POST
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Alessandro,
I think this is because of curl --data/-d option. Here are some excerpts
-d/--data is the same as --data-ascii. To post data purely binary,
you should instead use the --data-binary option. To URL-encode
the value of a form field you may use --data-urlencode.
If you start the data with the letter @, the rest should
be a file name to read the data from, or - if you want curl to read
the
data from stdin. The contents of the file must already
be URL-encoded. Multiple files can also be specified. Posting data
from a
file named 'foobar' would thus be done with --data @foobar.
so note that calling
> % curl -i -X POST -H "Content-type: text/turtle" -d @turtle-comments.rdf
> http://localhost:8080//ontonet/session/s1
would require the "turtle-comments.rdf" file to contain URL encoded content!
I think using the "--data-urlencode" option should solve your problem
as the documentation states
Data is posted in a similar manner as --data-ascii does,
except that newlines are preserved and conversions are never done.
best
Rupert
On Fri, Jul 13, 2012 at 6:30 PM, Alessandro Adamou <ad...@cs.unibo.it> wrote:
> Hi
>
> I've been going literally MAD over the last few days on a bizarre
> phenomenon:
>
> if I POST an ontology
>
> 1) in Turtle/N3/N-Triple format on an OntoNet Scope/Session/whatever,
>
> 2) I use the service that accepts the payload as
> application/x-www-form-urlencoded
>
> 3) and that ontology has inline comments (starting in '#'),
>
> then whatever follows that comment is truncated.
>
> Say I have the following code
>
> ==================
> @prefix : <http://stanbol.apache.org/ontologies/test/> .
> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
> @base <http://stanbol.apache.org/ontologies/test/turtle/sample/comments> .
>
> <http://stanbol.apache.org/ontologies/test/turtle/triples/sample/comments>
> rdf:type owl:Ontology .
>
> # Comment
>
> :SomeClazz rdf:type owl:Class .
>
> :SomeThing1 rdf:type :SomeClazz .
> ==================
>
> stored in the file turtle-comments.rdf
>
> then I do
>
> % curl -i -X PUT http://localhost:8080/ontonet/session/s1
>
> % curl -i -X POST -H "Content-type: text/turtle" -d @turtle-comments.rdf
> http://localhost:8080//ontonet/session/s1
>
> Then when I GET the new resource
>
> curl -i -H "Accept: application/rdf+xml"
> http://localhost:8080/ontonet/session/s1/http://stanbol.apache.org/ontologies/test/turtle/triples/sample/comments
>
> the last two triples are missing!
>
> Instead, if I force post binary data, as in
>
> % curl -i -X POST -H "Content-type: text/turtle" --data-binary
> @turtle-comments.rdf http://localhost:8080//ontonet/session/s1
>
> it seems to work.
>
> It also works if I POST using the multipart/form-data variant
>
> % curl -i -X POST -F "format=text/turtle" -F file=@turtle-comments.rdf
> http://localhost:8080/ontonet/session/s1
>
> and both variants do exactly the same thing: they create a
> GraphContentInputSource object out of a BufferedInputStream that wraps the
> InputStream they get:
>
> - for application/x-www-form-urlencoded it is a
> org.mortbay.jetty.HttpParser.Input
> - for multipart/form-data it is a FileInputStream
>
> Something seems to be going very wrong when the hash character is
> URLencoded, but apparently when it is used in namespaces it doesn't seem to
> be a problem.
>
> Not a big deal if I can just get away with it by using --data-binary, but
> it's taken me two days to find out.
>
> Does anybody know if this is normal?
>
> Best,
>
> Alessandro
>
> --
> M.Sc. Alessandro Adamou
>
> Alma Mater Studiorum - Università di Bologna
> Department of Computer Science
> Mura Anteo Zamboni 7, 40127 Bologna - Italy
>
> Semantic Technology Laboratory (STLab)
> Institute for Cognitive Science and Technology (ISTC)
> National Research Council (CNR)
> Via Nomentana 56, 00161 Rome - Italy
>
>
> "I will give you everything, just don't demand anything."
> (Ettore Petrolini, 1917)
>
> Not sent from my iSnobTechDevice
>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen