> Are you now asking how this could be made available via the /api/tasks API > you proposed?
Yep, should it be then restricted to that specific URL [1] or would the engine be allowed to create an additional end-point at /api/tasks? BR, David [1] http://{host}:{port}/{stanbol-root}/enhancer/engine/{engine-name} On Mon, Jan 14, 2013 at 2:21 PM, Fabian Christ <christ.fab...@googlemail.com > wrote: > 2013/1/14 David Riccitelli <da...@insideout.io> > > > About point a) I have a question. As the API allow for selection of the > > Enhancement Chain, how would that work if we move the API in an engine. > The > > engine can be executed outside of the scope of an enhancement chain? > > > > You can call single engine [1] by using > > http://{host}:{port}/{stanbol-root}/enhancer/engine/{engine-name} > > Are you now asking how this could be made available via the /api/tasks API > you proposed? > > [1] > http://stanbol.apache.org/docs/trunk/components/enhancer/engines/index.html > > > > Shall we move this thread on a JIRA thread? > > > > No, discussing this here is totally fine. We should create a JIRA that > describes what to do/implement after the discussion and we have some > consensus. > > Best, > - Fabian > > > -- > Fabian > http://twitter.com/fctwitt > -- David Riccitelli -- check the Swagger for WordLift <http://bit.ly/VtoM5H> ******************************************************************************** InsideOut10 s.r.l. P.IVA: IT-11381771002 Fax: +39 0110708239 --- LinkedIn: http://it.linkedin.com/in/riccitelli Twitter: ziodave --- Layar Partner Network<http://www.layar.com/publishing/developers/list/?page=1&country=&city=&keyword=insideout10&lpn=1> ********************************************************************************
