1 / 19

FLAVIUS

FLAVIUS. Technical presentation ( Overblog , Qype , TVTrip ) - WP2 Platform architecture. FLAVIUS. Technical presentation ( Overblog , Qype , TVTrip ). FLAVIUS. Technical presentation. Presentation of 20 minutes for each partners (CMS, web technology , …) Overblog Qype TVTrip.

kareem
Download Presentation

FLAVIUS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FLAVIUS Technicalpresentation (Overblog, Qype, TVTrip) - WP2 Platform architecture

  2. FLAVIUS Technicalpresentation (Overblog, Qype, TVTrip)

  3. FLAVIUS Technicalpresentation • Presentation of 20 minutes for eachpartners (CMS, web technology, …) • Overblog • Qype • TVTrip

  4. FLAVIUS WP2 Platform architecture

  5. FLAVIUS • Introduction of WP2 – Platform architecture • FLAVIUS workflow • Analyzeuser’sneed • Specify the FLAVIUSplatform architecture • Implement the FLAVIUSplatform • Deliverables

  6. FLAVIUS WP2 : Platform architecture • Main objectives of WP2:analyze, define and implement the FLAVIUS architecture (and workflow) • Glossary and acronyms: • TM : Translation Memory • Compose of text segments in a source language and their translations into one or more target languages • Reduce cost of translation project • SMT : Statistical Machine Translation • Translations are generated on the basis of statistical models whose parameters are derived from the analysis of bilingual text corpora. • Post-edition • Featureallowing a webmaster to modifytranslatedtext

  7. FLAVIUS WP2 : Platform architecture

  8. FLAVIUS FLAVIUS Workflow • Different translation workflowwillbeavailableaccording to option selected by webmaster • Automatic/semi-automatic correction of source text • Create a personal translation dictionary • Post-edit the translation • Train SMT enginewithpersonal translation memory • Etc … • Feedback fromusers : • A widgetwillallow user to post their feedback about the translation • Webmaster willbe able to see and use this feedback

  9. FLAVIUS Translation with minimumintervention • Automatic correction • No terminology extraction • No use of translationmemory • SMT not customized • No post-edit

  10. FLAVIUS Translation with source textrevision • Automatic and semi-automaticcorrection • No terminology extraction • No use of translationmemory • SMT not customized • No post-edit

  11. FLAVIUS Translation with source textrevision, translation customization, …. • Automatic/Semi-automaticcorrection • Terminology extraction • Translation of terminologyusing TM or SMT. • Enrich personaldictionarywithterminology • SMT customizedwithhispersonaldictionary • Post-edition

  12. FLAVIUS Customized translation withpersonal translation memories • SMT customizedwith a personal TM : • Webmaster cansubmithisown TM • SMT istrainedwithhis TM • Workflowcanbe one of the threepreviousworkflow : • Automatic/Semi-automatic correction • Terminology extraction • Translation of terminologyusing TM or SMT. • SMT customizedwithhispersonaldictionary • Post-edition

  13. FLAVIUS Analyzeuser’sneed • Content thatFLAVIUSshouldbe able to translate : • Web technologies : asp, asp.net, php, html, xml, … • CMS : joomla, wiki-like… • Establish a gridcriteria to evaluate and select web technologies and CMS thatshouldbesupported • audience (number of websites, visitors, …) • workload (easy to implement) • Analyze the feasibility of generalizing CMS translation by considering SQL Database translation. • Establish a list of main CMS • Make a technicalanalysis (SQL database, web technology) • Generalize to other CMS if possible

  14. FLAVIUS Analyzeuser’sneed • Spelling and grammarchecker output usefull for a webmaster (semi-automatic correction) • Ease the process of translating a web site • Simple and efficient workflow • High availability of FLAVIUSplatform • High availability of partner applications • WarnFLAVIUSplatform in case of service degradation (raisederrors, …)

  15. FLAVIUS Specify the FLAVIUS platformarchitecture • Compatibility withpartner applications : • Internet browser supported (IE 6.0, 7.0, FF 3.0, 3.1, Safari, Chrome, ...) • Client-sidetechnologyused (Flash, Java, SVG, Ajax, …) • Handling CMS translation : • Translation of CMS « user-generated content » (direct translation, SQL dump, …) • request user to definefields to translate ? • Translation of CMS « label » (multilingual CMS issue, …) • do not translate already CMS translated label ? • Importing translation memory : • Format supported (TMX , Excel, ….) • Version of TMX (1.4, 1.3, ..)

  16. FLAVIUS Implement the FLAVIUS platform • Interoperability • Feedback frompartners about the interoperability of theirtechnology (known limitation) • Way of communication supported/available (webservice, REST) • Performance : • Feedback frompartners about performance issues of their applications. • Hosting : • Partner’s application canbehostedelsewhere ? • Hardware • Limitation

  17. FLAVIUS Deliverables • Technicalanalysis report • This document must contain : • Technologies thatwillbesupported • Explanation of workflow

  18. FLAVIUS Deliverables • Websitespecification • This document must contain : • Detailedplatform architecture • Integrationspecifications for each module • Planning : • (1) -> (4) : define the architecture • (5) -> (7) : defineintegration of partner application relative into the chosen architecture • (8) : write final document

  19. FLAVIUS Deliverables • Implementation plan • This document must contain : • Delivery dates • Integration and testing phases

More Related