Dear Pablo, Thanks for you advice. I'm composing the project proposal, especially the project plan. I need to evaluate the work time for the tasks. I'm not the guy who promises many but can not make it indeed. Once promised, I'll stick to my words to complete them with responsibility. I'll see what I can do.
Could you tell me more about the idea of "closing the feedback loop by having a linker learning from the feedback"? I'll try to enhance the feedback service task. 1. What's "feedback loop"? Do you mean that a user can submit feedbacks again and again to make a loop? 2. What's "linker learning"? Do you mean the links among the feedbacks, or among the feedbacks and the users? How to close a loop by a linker learning? It's greatly appreciated if you can show some examples. Thanks. Best regards, Siwei Yu On Sun, Apr 1, 2012 at 5:50 PM, Pablo Mendes <[email protected]> wrote: > Hi Siwei, > It is fine with me to push forward Chinese support as a task for you to do > as a member of the DBpedia Spotlight team instead of as a GSoC student. We > are always interested in good people joining the team. But I am afraid that > the effort needed for adding DBpedia Spotlight engines to Stanbol will not > be 1.5month full-time, neither will the /feedback service, therefore your > project looks a bit smaller than the others. This could be a good thing, if > you manage to show in your application that you know exactly what needs to > be done ,and that it requires that much time. But it might also make your > project weaker if you fail to convince us of that. > > Perhaps closing the feedback loop by having a linker learning from the > feedback is what you need in addition. > > Cheers > Pablo > > On Apr 1, 2012 7:28 AM, "Siwei Yu" <[email protected]> wrote:
