- About this project:
- Tool: Protege
- Ecommerce Ontology:
- Ontology Translation(create other versions of Ontology from the original Enlish version) :
- Tool: Protege API in JAVA platform.
- Instructions: how to input the translated words
- Translation file: this file contains both the original(English) and transled(need input from any other language) Ecommerce terms.
- Translation tests
- Tested in Chinese: (works now)
- In the Protege, we can input chinese but doesn't show up correct fonts(Solution: change the font.properties file).
- In our translation program, communicated with Protege API, we got these error messages: Error
(The problem is solved now, I use:
BufferedReader in = new BufferedReader(new InputStreamReader(new FileInputStream(filename),"UTF8"));
to solve the problem)
- Here is the Chinese transaltion file used in this test: Translation file
- Translation tested in English - adds "UK" after each term to simulate as other language:
- Translated in German: translation sheet, protege, OWL and XML files.
- Translated in Russian: translation sheet, protege, OWL and XML in zip.
- Ontology Search
- Tools/Programming Language: Java/JSP,
Protege API,
Google API and
Tomcat Server
- Google API Search:
- Google API still have problems with some Asia languages
- In order to show all languages in Java programs, we have to deal with both web server and client.
Solution for displaying all languages in JSP with Google API:
- Save the jsp in utf-8 format
- Add the following directive to JSP:
<%@ page contentType="text/html; charset=utf-8" pageEncoding="utf-8" %>
- In JSP, set encoding to request object: request.setCharacterEncoding("UTF8");
- In HTML header, add: <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
- (Optional) In the FORM tag, add: <form action="..." method="post" accept-charset="UTF-8">
- Compare search programs between
Partial Multilingual version(Before the solution)
and Full version
- Interface procedure: flow chart 1 and flow chart 2
- Search with translation: Interface
- Translation from English to Russian is OK now
- Need to fix problem from Russian to English:(
-- It's working now! :)
- Working on the Protege API:
- To access the Ontology in the Protege, I run the program as a stand alone server in background.
- It works as "localhost" server in the PC: screen shot
- The ontology server is now running on ai3 host.
- The Ecommerce Terms can be translated between English, German and Russian.
For example, if an user first choose German as his input language, he uses the German version
of Ontology to choose the ecommerce terms. Then, he changes the input language to English,
he does need to choose the ecommerce terms (in English version) again. The system will
automatically translate the German terms to the expected output (English, Russian or
German) language.
- Links:
- M.O.R.E. System
|