Dear Pablo, Rupert, Thanks a lot for your instructions!
According to your comments, let me summarise the current status of the service mapped to the four stages: (1) Spotting, (2) Candidate Selection, (3) Disambiguation, (4) Filtering /annotate: (1) (2) (3)first (4) /candidate: (1) (2) (3)all /disambiguation: (3) /feedback: not implemented Please let me know if the previous summary is incorrect. However, the On Wed, Mar 21, 2012 at 4:27 PM, Rupert Westenthaler <[email protected]> wrote: > > Hi Siwei Yu, Pablo > > see my comments inline. To make it better readable I also removed the > parts of the mail that are not relevant to my comments. > > On Wed, Mar 21, 2012 at 12:01 AM, Pablo Mendes <[email protected]> wrote: > > On Tue, Mar 20, 2012 at 4:24 PM, Siwei Yu <[email protected]> wrote: > >> 2. Should I develop one Enhancement Engine containing three services, > >> or three engines (i.e. each service as an engine)? It's maybe related > >> to the service function granularity. What's your opinion? > > > > > > We could have one engine for each task separately, and an enhancement chain > > should connect them together. We should also introduce a REST API /spot for > > (1). We could perhaps make /candidates implement only (2) and make /annotate > > accept a &verbose=on to act like the current /candidates does. > > > > Besides all of this reorganization that has to happen, Rupert is the guy > > from Stanbol that can help you position your application in that regard. > > > > I fully agree with that. > > Having separate EnhancementEngines for spotting, candidates selection > and disambiguation would provide a lot of additional flexibility to > experienced Stanbol users as they could even use parts of the DBpedia > Spotlight functionalities within their existing enhancement engines. > > The definition of a DBpedia Spotlight EnhancementChain ensures that > typical users can use Spotlight without the need to know the inner > working. Users would just need to send enhancement requests to > "http://{host}:{port}/enhancer/chin/dbpedia"; assuming that the DBpedia > Spotlight chain is called "dbpedia". There would even be the > possibility to make the Dbpedia Spotlight EnhancementChain the default > enhancement chain so that requests to "/enhancer" would be processed > by it. > > >> > >> By the way, my name is Siwei Yu. I have good knowledge of semantic > >> technologies, such as RDF, OWL, SPARQL. I'm also familiar with the > >> mainstream Java based RDF/OWL processing tools like owlapi, Jena, > >> Sesame, AllegroGraph. I have strong Java coding skills with of good > >> knowledge of the software design patterns. My research background > >> meets the requirements very well. I believe it'll be a wonderful > >> summer working with the DBpedia Spotlight community. > > > > > > It would be good if you leveraged some of your Semantic Web background in > > your application. The idea of a /feedback API, which receives corrections > > made by the users could fit well in this regard. > > > > A feedback API is also something that would be interesting for the > Stanbol Enhancer. > > best > Rupert Westenthaler > > -- > | Rupert Westenthaler [email protected] > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Dbp-spotlight-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbp-spotlight-users
