Hi everyone,

On 3/3/14, 7:55 AM, Sourish Dasgupta wrote:
> Hello all,
>
> I agree with Marco that we should be concentrating on English for the
> moment. This is because every language has some innate characteristic
> linguistic nuances which may not be found in other languages.
>
> However, I still feel that techniques borrowed from computational
> semantics might be helpful in improving the accuracy significantly. By
> and large languages follow the SVO structure (Subject Verb Object). It
> covers approx. 42% of world languages [1]. So the research insights that
> we get in working with English, both at a statistical and at a
> linguistic level, might be very important for future extension.
That's exactly my point, more technically explained.
If we manage to implement simple questions that fit well in all SVO 
languages, this would be a dramatic added value in terms of multilingual 
support.

Cheers!
>
> Sourish
>
> [1]: Russell Tomlin, "Basic Word Order: Functional Principles", Croom
> Helm, London, 1986,
>
>
> On Mon, Mar 3, 2014 at 12:18 AM, Pablo N. Mendes <pablomen...@gmail.com
> <mailto:pablomen...@gmail.com>> wrote:
>
>
>     I just want to suggest caution with multilinguality. Doesn't seem to
>     me like an easy problem. QA is already hard enough in one language,
>     if one tries to solve it for all languages at once, it will be
>     overwhelming in three months. I'd suggest focusing on English, but
>     not hardcoding anything that is language specific, keeping them in
>     configuration files and properly engineered subclasses, thinking
>     that one day it will all be ported to another language.
>
>     On Mar 1, 2014 1:10 AM, "Ankur Padia" <padiaan...@gmail.com
>     <mailto:padiaan...@gmail.com>> wrote:
>
>         Hello Marco,
>
>             This is inform that I am resending a copy of the mail send
>         before as I forgot to CC the author of the referred paper who is
>         working in the direction of development of QA system using DL as
>         tool for language representation.
>
>               I think Google Translator API would come handy to perform
>         the conversion of an foreign language question to English
>         language question for cases where particular knowledge or triple
>         is missing [2] in given chapter and then after firing it against
>         English Knowledge Base which do have one. However, there is a
>         paper on Wh-questions by Dr. Sourish Dasgupta (cc) and its
>         possible semantic formalization in description logics [1].
>
>         - Ankur.
>
>         Reference :
>         ---------------
>         [1] http://arxiv.org/abs/1312.6948
>         [2] Approach taken in QAKiS.
>
>         On Fri, Feb 28, 2014 at 4:54 PM, Marco Fossati
>         <hell.j....@gmail.com <mailto:hell.j....@gmail.com>> wrote:
>
>             Also, I think a crucial point will be the multilingual
>             capabilities of the tool. In this way, all the DBpedia
>             chapters can benefit from it.
>
>             So, the first implementation should focus on very simple
>             questions, but in multiple languages.
>             WH questions would be great.
>             Of course, this requires language-specific validation. We
>             will definitely need the help of the worldwide community.
>
>             Sounds like the project is getting more and more exciting!
>             Cheers,
>
>             On 2/28/14, 12:08 PM, Marco Fossati wrote:
>
>                 Hi Ankur,
>
>                 On 2/28/14, 2:00 AM, Ankur Padia wrote:
>
>                         Among the approach listed before, I will prefer
>                     TBSL as it scope is
>                     relatively wider.
>
>                 All right, go ahead with that.
>
>                           Ideally QA engine for DBpedia should be able
>                     to handle all kinds of
>                     question with its appropriate semantic parsing and
>                     satisfactory
>                     conversion to SPARQL queries. To address the scope
>                     for a QA system, it
>                     would highly depend on the time at hand. For example
>                     given a span of
>                     GSoC, addressing even a small number of English
>                     nuances in queries would
>                     be ambitious (Correct me if I am wrong).
>
>                 Exactly, keep in mind that a successful project implies
>                 a tool that
>                 actually works.
>                 Hence, I suggest to proceed first with the
>                 implementation of single
>                 predicate queries, in order to provide a reasonable
>                 coverage of simple
>                 questions.
>                 Cheers,
>
>
>             --
>             Marco Fossati
>             http://about.me/marco.fossati
>             Twitter: @hjfocs
>             Skype: hell_j
>
>
>
>
>         
> ------------------------------------------------------------------------------
>         Flow-based real-time traffic analytics software. Cisco certified
>         tool.
>         Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow
>         Analyzer
>         Customize your own dashboards, set traffic alerts and generate
>         reports.
>         Network behavioral analysis & security monitoring. All-in-one tool.
>         
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
>         _______________________________________________
>         Dbpedia-gsoc mailing list
>         Dbpedia-gsoc@lists.sourceforge.net
>         <mailto:Dbpedia-gsoc@lists.sourceforge.net>
>         https://lists.sourceforge.net/lists/listinfo/dbpedia-gsoc
>
>

-- 
Marco Fossati
http://about.me/marco.fossati
Twitter: @hjfocs
Skype: hell_j

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Dbpedia-gsoc mailing list
Dbpedia-gsoc@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-gsoc

Reply via email to