Apertium going SOA - Revision history

Francis Tyers at 07:37, 8 March 2018

2018-03-08T07:37:28Z

Shardulc: GitHub migration

2018-03-08T05:50:51Z

GitHub migration

Bech: Link to French page + iz... changed !

2014-10-07T14:44:31Z

Link to French page + iz... changed !

Bech: Documentation in English

2011-09-03T18:20:53Z

Documentation in English

Francis Tyers: Reverted edits by 140.115.30.226 (Talk) to last revision by Unhammer

2010-04-23T18:31:42Z

Reverted edits by 140.115.30.226 (Talk) to last revision by Unhammer

140.115.30.226: cvaLK6 zdjkajnshlir, [url=http://dlzkpryotert.com/]dlzkpryotert[/url], [link=http://kwkdhyzxyrex.com/]kwkdhyzxyrex[/link], http://whuzvitjbenq.com/

2010-04-23T18:11:25Z

cvaLK6 <a href="http://zdjkajnshlir.com/">zdjkajnshlir</a>, [url=http://dlzkpryotert.com/]dlzkpryotert[/url], [link=http://kwkdhyzxyrex.com/]kwkdhyzxyrex[/link], http://whuzvitjbenq.com/

Unhammer at 07:26, 21 December 2009

2009-12-21T07:26:27Z

Jacob Nordfalk at 12:49, 9 October 2009

2009-10-09T12:49:38Z

Deadbeef at 19:06, 6 July 2009

2009-07-06T19:06:08Z

79.2.76.48: /* Development status - 24/06/2009 */

2009-06-24T15:14:45Z

Development status - 24/06/2009

@@ Line 1: / Line 1: @@
 [[L'architecture orientée service d'Apertium|En français]]
+{{Github-migration-check}}
 [[Image:ApertiumServerComponentDiagram.png|thumb|400px|Sample Component Diagram: an Apertium Server implements a XML-RPC interface (and eventually others), that can be accessed using an Apertium Client or a Web Service (the Web Service can be accessed using a REST or a SOAP interface). It's easy then, for external applications written in various languages, to access Apertium's capabilities by using a Web Service (for example, to integrate translation in an Ajax application, in an IM client, in a Translation Service of a large IT service-oriented and geographically distributed infrastructure (for example, to collaborate easier with engineers in an offshore country), and so on).]]

@@ Line 4: / Line 4: @@
 [[Image:ApertiumServerSequenceDiagram.png|thumb|400px|Sequence Diagram showing how an IM Client can use Apertium Server's capabilities (accessed through a Web Service interface) to implement real-time translation (bot in input and output) of instant messages.]]
+'''NOTE:''' After Apertium's migration to GitHub, this tool is '''read-only''' on the SourceForge repository and does not exist on GitHub. If you are interested in migrating this tool to GitHub, see [[Migrating tools to GitHub]].
 '''UPDATE''': This project has actually moved from ''branches/gsoc2009/deadbeef/'' to ''trunk/'', and its sources are available here:

@@ Line 1: / Line 1: @@
+[[L'architecture orientée service d'Apertium|En français]]
 [[Image:ApertiumServerComponentDiagram.png|thumb|400px|Sample Component Diagram: an Apertium Server implements a XML-RPC interface (and eventually others), that can be accessed using an Apertium Client or a Web Service (the Web Service can be accessed using a REST or a SOAP interface). It's easy then, for external applications written in various languages, to access Apertium's capabilities by using a Web Service (for example, to integrate translation in an Ajax application, in an IM client, in a Translation Service of a large IT service-oriented and geographically distributed infrastructure (for example, to collaborate easier with engineers in an offshore country), and so on).]]
@@ Line 23: / Line 25: @@
-== A possible Use Case: an Healthcare organization ==
+== A possible Use Case: an Healthcare organisation ==
 [[Image:ApertiumServerUseCase.png|thumb|400px|This sample shows how Apertium Server's capabilities can be exposed by a Translation Service inside an existing service-oriented IT infrastructure; in this case, the Actor (a non english-speaking Medic) interacts with a manager of Clinical Documents by storing some Health Records: those records often include natural-language text that needs external tools like MetaMap to be mapped on ontologies or concepts. In this case, the non-English natural-language text is first translated in the English language using a Translation Service using Apertium Server, and the result is then given to MetaMap, that maps the now-English text into concepts (then stored in a Knowledge Base for futher analysis).]]
-In Healthcare Information Systems (HIS), to improve external services' access and integration, there's a general trend to implement IT infrastructure based on a SOA model; in this use case, I show how an Healthcare Organization of non English speaking countries can greatly benefit of the integration of a Translation Service implemented using Apertium in their IT infrastructure.
+In Healthcare Information Systems (HIS), to improve external services' access and integration, there's a general trend to implement IT infrastructure based on a SOA model; in this use case, I show how an Healthcare Organisation of non English speaking countries can greatly benefit of the integration of a Translation Service implemented using Apertium in their IT infrastructure.
 MetaMap is an online application that allows mapping text to UMLS Metathesaurus concepts, which is very useful interoperability among different languages and systems within the biomedical domain. MetaMap Transfer (MMTx) is a Java program that makes MetaMap available to biomedical researchers. Currently MetaMap only works effectively on text written in the English language, which difficult the use of UMLS Metathesaurus to extract concepts from non-English biomedical texts.
@@ Line 132: / Line 134: @@
-''N-Gram-Based Text Categorization'' (1994), by William B. Cavnar, John M. Trenkle
+''N-Gram-Based Text Categorisation'' (1994), by William B. Cavnar, John M. Trenkle
 In ''Proceedings of SDAIR-94, 3rd Annual Symposium on Document Analysis and Information Retrieval''
@@ Line 191: / Line 193: @@
-Resulting in '''~40 ms''' to complete each request; BTW actually this protype lacks of some optimization that haven't still been introduced to make the development process easier: by introducing those optimizations, I think we can easily get to '''~20-25 ms''' per request. In addition, those requests have been executed in sequence, without taking advantage of this service's multithreading capabilities.
+Resulting in '''~40 ms''' to complete each request; BTW actually this protype lacks of some optimisation that haven't still been introduced to make the development process easier: by introducing those optimisations, I think we can easily get to '''~20-25 ms''' per request. In addition, those requests have been executed in sequence, without taking advantage of this service's multithreading capabilities.
@@ Line 379: / Line 381: @@
 = Development status - 17/06/2009 =
-I just started implementing some optimizations, like the Object Pooling pattern for {de, re}formatters too (so that regexes don't have to be recompiled each time), and actually '''I've lowered the time required for each translation from ~40ms to less than 5ms :)'''
+I just started implementing some optimisations, like the Object Pooling pattern for {de, re}formatters too (so that regexes don't have to be recompiled each time), and actually '''I've lowered the time required for each translation from ~40ms to less than 5ms :)'''
 Now I should clean up the code (now it's very hacky) and put everything in trunk/ (actually all those hacks are in branches/gsoc2009/deadbeef/Core/)
@@ Line 434: / Line 436: @@
 = Development status - 06/07/2009 =
-Hi :D I must admit I took some few days to finish some projects for the university (and lookup some papers about the Lexical Selection problem; I hope I can help realizing something!); I've made a SOAP interface to access the service, you can check the WSDL here:
+Hi :D I must admit I took some few days to finish some projects for the university (and lookup some papers about the Lexical Selection problem; I hope I can help to realize something!); I've made a SOAP interface to access the service, you can check the WSDL here:
 http://www.neuralnoise.com/ApertiumWeb2/soap.php?wsdl
-The next step will be realizing a REST interface to the service; I already realized one using the WSO2 framework, but since it's pretty huge and painful to install, I'm now trying to create something enough small/general/well-designed by myself.
+The next step will be to realize a REST interface to the service; I already realized one using the WSO2 framework, but since it's pretty huge and painful to install, I'm now trying to create something enough small/general/well-designed by myself.
 [[Category:Documentation]]

← Older revision		Revision as of 18:20, 3 September 2011
Line 442:		Line 442:

	[[Category:Documentation]]		[[Category:Documentation]]
			[[Category:Documentation in English]]

@@ Line 12: / Line 12: @@
 Simple installation instructions are at [[Apertium-service]].
+= Introduction =
-cvaLK6  <a href="http://zdjkajnshlir.com/">zdjkajnshlir</a>, [url=http://dlzkpryotert.com/]dlzkpryotert[/url], [link=http://kwkdhyzxyrex.com/]kwkdhyzxyrex[/link], http://whuzvitjbenq.com/
+The aim of this project is to design and implement an "Apertium Service" that can be easy integrated into IT systems implemented using a model based on a Service-Oriented Architecture (SOA).
+Actually, to translate a big corpus of document, many Apertium processes are created and each one must load the required transducers, grammars etc., causing a waste of resources and, so, a reduction of scalability.
+To solve this problem, a solution is to implement an Apertium Service that doesn't need to reload all the resources for every translation task. In addition, this kind of service would be able to handle multiple request at the same time (useful, for example, in a Web 2.0-oriented enviroment), would improve scalability, and could be easily included into existing business processes and integrated in existing IT infrastructures with the minimum effort.
+In addition, this project aims also to implement a Web Service acting as a gateway between the Apertium Service and external applications (loading Apertium inside the Web Service itself would be nonsense, since a Web Service is stateless and it wouldn't solve the scalability problem): the Web Service will offer both a SOAP and a REST interface, to make it easier for external applications/services (for example: IM clients, web sites, large IT business processes..) to include translation capabilities without importing the entire Apertium application.
+== A possible Use Case: an Healthcare organization ==
+[[Image:ApertiumServerUseCase.png|thumb|400px|This sample shows how Apertium Server's capabilities can be exposed by a Translation Service inside an existing service-oriented IT infrastructure; in this case, the Actor (a non english-speaking Medic) interacts with a manager of Clinical Documents by storing some Health Records: those records often include natural-language text that needs external tools like MetaMap to be mapped on ontologies or concepts. In this case, the non-English natural-language text is first translated in the English language using a Translation Service using Apertium Server, and the result is then given to MetaMap, that maps the now-English text into concepts (then stored in a Knowledge Base for futher analysis).]]
+In Healthcare Information Systems (HIS), to improve external services' access and integration, there's a general trend to implement IT infrastructure based on a SOA model; in this use case, I show how an Healthcare Organization of non English speaking countries can greatly benefit of the integration of a Translation Service implemented using Apertium in their IT infrastructure.
+MetaMap is an online application that allows mapping text to UMLS Metathesaurus concepts, which is very useful interoperability among different languages and systems within the biomedical domain. MetaMap Transfer (MMTx) is a Java program that makes MetaMap available to biomedical researchers. Currently MetaMap only works effectively on text written in the English language, which difficult the use of UMLS Metathesaurus to extract concepts from non-English biomedical texts.
+A possible solution to this problem is to translate the non-English biomedical texts into English, so MetaMap (and similar Text Mining tools) can effectively work on it.
 = Service's internals =

@@ Line 89: / Line 89: @@
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import xmlrpclib
->>> proxy = xmlrpclib.ServerProxy("http://www.neuralnoise.com:1234/ApertiumServer")
+>>> proxy = xmlrpclib.ServerProxy("http://xixona.dlsi.ua.es:8080/RPC2")
+>>> proxy.translate("Hello world", "en", "es")
+'Hola Mundo'
 >>> proxy.listLanguagePairs()
 ['en-eo', 'es-en', 'en-es']
->>> proxy.translate("Hello world", "en-es")
-'Hola Mundo'
->>>
 </pre>
@@ Line 111: / Line 110: @@
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import xmlrpclib
->>> proxy = xmlrpclib.ServerProxy("http://www.neuralnoise.com:1234/ApertiumServer")
+>>> proxy = xmlrpclib.ServerProxy("http://xixona.dlsi.ua.es:8080/RPC2")
->>> proxy.translate("How are you?", "en-es")
+>>> proxy.translate("How are you?", "en", "es")
 u'C\xf3mo te es?'
 >>> print proxy.translate("How are you?", "en-es")
@@ Line 215: / Line 214: @@
 require 'xmlrpc/client'
-server = XMLRPC::Client.new("www.neuralnoise.com", "/ApertiumServer", 1234)
+server = XMLRPC::Client.new("xixona.dlsi.ua.es", "/RPC2", 8080)
-puts server.call("translate", "This is a test for the machine translation program.", "en-es")
+puts server.call("translate", "This is a test for the machine translation program.", "en", "es")
 </pre>
@@ Line 226: / Line 225: @@
 import xmlrpclib
-proxy = xmlrpclib.ServerProxy("http://www.neuralnoise.com:1234/ApertiumServer")
+proxy = xmlrpclib.ServerProxy("http://xixona.dlsi.ua.es:8080/RPC2")
-print proxy.translate("This is a test for the machine translation program.", "en-es")
+print proxy.translate("This is a test for the machine translation program.", "en", "es")
 </pre>
@@ Line 243: / Line 242: @@
 XmlRpcClientConfigImpl config = new XmlRpcClientConfigImpl();
-config.setServerURL(new URL("http://www.neuralnoise.com:1234/ApertiumServer"));
+config.setServerURL(new URL("http://xixona.dlsi.ua.es:8080/RPC2"));
 XmlRpcClient client = new XmlRpcClient();
@@ Line 250: / Line 249: @@
 client.setConfig(config);
-client.execute("translate", new Object[] { "This is a test for the machine translation program.", "en-es" });
+client.execute("translate", new Object[] { "This is a test for the machine translation program.", "en", "es" });
 </pre>
@@ Line 261: / Line 260: @@
 require RPC::XML::Client;
-my $client = RPC::XML::Client->new("http://www.neuralnoise.com:1234/ApertiumServer");
+my $client = RPC::XML::Client->new("http://xixona.dlsi.ua.es:8080/RPC2");
-my $res = $client->send_request("translate", "This is a test for the machine translation program.", "en-es");
+my $res = $client->send_request("translate", "This is a test for the machine translation program.", "en", "es");
 binmode(STDOUT, ":utf8");

@@ Line 421: / Line 421: @@
 = Development status - 24/06/2009 =
-I took some time to clean up the code and fix eventual thread safety issues that may arise when running multiple concurrent translations; actually, there was a small issue with using multiple instances of the class FSTProcessor in the same program, and I wrote the following patch to fix it:
+I took some time to clean up the code and fix eventual thread safety issues that may arise when running multiple concurrent translations; actually, there was a small issue in lttoolbox with using multiple instances of the class FSTProcessor in the same program, and I wrote the following patch to fix it:
 http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/apertium-service/lttoolbox_FSTProcessor_ThreadSafety.diff
-After having applied this patch, the service is able to handle an arbitrary number of concurrent translations without any problems.
+After having applied this patch to lttoolbox, the service is able to handle an arbitrary number of concurrent translations without any problems.
 Some more details about the patch are available here[http://sourceforge.net/mailarchive/message.php?msg_name=7f231e00906220759h67728d7wc59dbae89abaf100@mail.gmail.com].