Hi Year this does go in the direction what is planed. Let me summarize:
* new enhancer/task API: This will allow to send an EnhancementJob with the request. As part of the Request users will be able to define the EnhancementChain, EnhancementEngine parameters the content to analyze or an URI where Stanbol should retrieve the content from. Even asynchronous execution by parsing a callback URI is planed. * extension of the current RESTful enhancer service with some of the features of the task API. Parsing EnhancementEngine parameters as you suggested could be one of those. However to support all this we need first change the Enhancer services API: EnhancementEngines will get a 2nd parameter called enhancementProperties parsed in their canEnhance(..) and computeEnhancement(..) methods. The current idea is that enhancementProperties will use Dictionary<String,Object> to make them similar to the OSGI ComponentContext#getProperties(). Also the internal Enhancer API will change. We plan to add a new EnhancementJob Interface. The EnhancementJob will cover both Content specific information - the contentItem - and information describing the processing state. Processing specific data will include the EnhancementProperties, the EnhancementChain as well as the ExecutionMetadata. The EnhancementJobManager will get EnhancementJobs parsed and is responsible to execute them. EnhancementEngines will not have access to the EnhancementJob, but only to the EnhancementProperties. Al he above is also discussed referenced in >> >> [1] http://markmail.org/message/zqztwjhndwj74jqv >> With this system in place you will be able to parse EnhancementJob specific parameters to EnhancementEngines best Rupert best Rupert -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen On Sat, Feb 9, 2013 at 6:04 PM, harish suvarna <[email protected]> wrote: > Hi Rupert, > I am looking at the restful api description and one of the examples is > > curl -X POST -H "Accept: text/turtle" -H "Content-type: text/plain" \ > --data "The Stanbol enhancer can detect famous cities such as > Paris \ and people such as Bob Marley." \ > > "http://localhost:8080/enhancer/chain/dbpedia-keyword?uri=urn:fise-example-content-item&executionmetadata=true"; > So these params aply to the enitire chain? Are the params 'uri' and > 'executionmetadata' are predefined? Can't we add new params here > > http://localhost:8080/enhancer/chain/MY_OWN_CHAIN?maximumKeywordsNumber=20&applyModel=StanfordPOSFastModel"; > Whichever engine understands this, will use the params > maximumKeywordsNumber and applyModel. > > Reference: > http://stanbol.apache.org/docs/trunk/components/enhancer/enhancerrest.html > > -harish > > > > > On Fri, Feb 8, 2013 at 9:32 PM, Rupert Westenthaler < > [email protected]> wrote: > >> Hi Harish >> >> If you refer to request specific configuration, than this is currently >> not possible. However there was recently a long discussion about very >> similar things (see [1] and follow up mails). >> >> As the discussed features would require incompatible API changes in >> the Enhancer the decision was to continue on those as soon as the >> Enhancement Engines get released (hopefully next week, as Fabian is >> already forging the release). >> >> But as you can see from [1] most of the things are still in early >> stages meaning that feedback, usage scenarios ... are highly welcome >> >> best >> Rupert >> >> >> >> [1] http://markmail.org/message/zqztwjhndwj74jqv >> >> On Sat, Feb 9, 2013 at 3:57 AM, harish suvarna <[email protected]> wrote: >> > Is it possible to add additional parameters for the restful api for >> > enahancement engine? Lets say I want to tell it to compute the top 20 >> > keywords only. >> > >> > -- >> > Thanks >> > Harish >> >> >> >> -- >> | Rupert Westenthaler [email protected] >> | Bodenlehenstraße 11 ++43-699-11108907 >> | A-5500 Bischofshofen >> > > > > -- > Thanks > Harish -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
