In order to start the development of the mobile medslt gui we need two methods from the translation server.
I also attach the xml formated recognition result.
*Request: action(translate_nbest(<XMLRecResult>))
Response: (translation = TargetAtom) + (selected = Selected) + (target_lf =
TargetLF ) + ( interlingua = Interlingua ) [ok]
[Example: Client rcv msg: (translation='+tts "la douleur est-elle
frontale"')+(selected='is the pain
frontal')+(target_lf=[[body_part,frontal],[symptom,douleur],[tense,present]
,[utterance_type,sentence],[state,Otre]])+(interlingua=[[adj,frontal],[symp
tom,pain],[tense,present],[utterance_type,ynq],[verb,be]])]
error. [Something went wrong]
*Request: action(get_help_examples_nbest(<XMLRecResult>, <NExamples>))
Response: help('<HelpString>')
Example: help('when is the next meeting\nwhen is the next meeting in geneva')
error. [Something went wrong]
I suppose that there is already a method get_help_examples that supports this functionality
coming from the calendar dialogue server. Perhaps there is a name clash in the translation server
because the same method is used as: action(get_help_examples(<Words>, <NExamples>))
Logged In: YES
user_id=529904
Originator: NO
Nikos, just looked at the example XML-formatted request, and the semantic value is not well-formed:
<?xml version="1.0" encoding="UTF-8"?>
<result grammar="session:calendar.grammar">
<interpretation confidence="59">
<instance>
<value confidence="0">
((whq (apply (lambda x ((tense present) (existential there_is) (subj (x (duration ((spec next) (time_period week))))))) (
</value>
As you can see, the parentheses are unbalanced - looks like it got cut off in the middle. Passing item back to you to fix this...
Logged In: YES
user_id=1706491
Originator: NO
File Added: n-best result.txt
Logged In: YES
user_id=529904
Originator: NO
I have fixed the translation server to be able to handle XML-formatted N-best input, both for translation and for help. You need to update Regulus and MedSLT. I have tested using $MED_SLT2/Runtime/Prolog/translation_client.pl, and it appears to give the right behavior - though note that I was forced to change the form of the help message to avoid ambiguity. Reassigning bug to Nikos, to make sure this is working as required.