- From: Ankit K. Srivastava <asrivastava@computing.dcu.ie>
- Date: Wed, 6 Mar 2013 12:27:41 +0000
- To: "Lieske, Christian" <christian.lieske@sap.com>, Milan Karasek <MilanK@moravia.com>
- Cc: "Dr. David Filip" <David.Filip@ul.ie>, David Lewis <dave.lewis@cs.tcd.ie>, "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
- Message-ID: <CABmQ8wpCP3_x2eMDZshA+q1D58rLFUXpxPNLTK3JZGwn8mcmSQ@mail.gmail.com>
Hi Christian, Re: MaTrEx (DCU) Details: General Documentation: http://www.w3.org/International/multilingualweb/lt/wiki/Simple_Segment_Machine_Translation_Use_Case_Demonstration Running Software: [MaTrEx: http://www.cngl.ie/mlwlt/ MaTrEx] Thanks, Ankit On Wed, Mar 6, 2013 at 11:57 AM, Milan Karasek <MilanK@moravia.com> wrote: > Hi Christian, > > my inputs for 2.11.3, specially part 'Moravia's implementation of M4Loc > and Moses with ITS 2.0 support' are as following: > > * Details: M4Loc processing of ITS2.0 enhanced XLIFF files > * Running software: http://mlwlt.moravia.com (testing site) > * Running software (web-service): > http://mlwlt.moravia.com/mlwlt-service-xliff-mt/mlwlt-service.asmx > * Source code: https://github.com/mkarasek/mlwlt-m4loc-xliff-mt > * General documentation: > https://github.com/mkarasek/mlwlt-m4loc-xliff-mt/wiki > > Please note that links to the running software are private and accessible > only to SOLAS system at the moment. They should become public next week. > > Regards, > Milan > > > -----Original Message----- > From: Lieske, Christian [mailto:christian.lieske@sap.com] > Sent: Tuesday, March 05, 2013 10:50 AM > To: Dr. David Filip; David Lewis; Ankit Srivastava; Milan Karasek > Cc: public-multilingualweb-lt@w3.org > Subject: RE: [All] high level use cases not yet ready to publish, please > have another look -DCU/UL (for SOLAS) - > > Hi David, > > Thanks for this. > > We now have the following to the Wiki: > > ===Description=== > * The tool - SOLAS - is a service-based architecture for orchestrating > localization workflows between XLIFF-aware components. > * SOLAS is basically a middleware component based on an RDF triple store > over an arbitrary CMS (tested with Alfresco, Drupal and Wikimedia). > * Can parse the source including most of the ITS 2.0 metadata and produce > XLIFF 1.2 according to a currently agreed mapping. After the roundtrip it > updates the RDF triple store accordingly. > > Two questions: > > 1. DF> This is currently with out TTO. > > Should this read "This is currently with our Technology Transfer Office."? > > 2. DF> This is currently with out TTO. All relevant stuff should be > released under a suitable Open Source License, most probably LGPL by summer > 2013, but currently, the relevant SOLAS components are on private Git > > Can I add this to the Wiki? > > I am awaiting info from Ankit and Milan on regarding LION, Matrex, and > M4Loc. > > Cheers, > Christian > -----Original Message----- > From: Dr. David Filip [mailto:David.Filip@ul.ie] > Sent: Montag, 4. März 2013 11:06 > To: Lieske, Christian; David Lewis; Ankit Srivastava; Milan Karasek > Cc: public-multilingualweb-lt@w3.org > Subject: Re: [All] high level use cases not yet ready to publish, please > have another look -DCU/UL (for SOLAS) - > > Hi Christina, I dumped some more info onto the wiki and am adding some > more info here, answering inline.. > > > > > 1. Is CMS-LION a specific CMS? Is it a middleware component? > It is a TCD devloped middleware component. It is basically an RDF triple > store over an arbitrary CMS. I belive that they are currently focusing on > Alfresco, but worked with Drupal and Wikimedia in the past. > It has an ability to parse the source including most of the ITS 2.0 > metadata and produce XLIFF 1.2 according to the currently agreed mapping. > After the roundtrip it updates the RDF triple store accordingly. > @Dave, correct me if I don't have it right > > > > > > > > > 2. Which components (e.g. workflow system and MT system) have been > tied > > together using SOLAS? > I added this info to the wiki, to summarize 1. Source Qulaity Assurance > tool - LKR 2. PM friendly viewer 3. several integrated MT solutions > > > > > > > > 3. Do you have any information for the following? > > > > > > > > * Details: > > > > * Running software: > > > > * Source code: > > > > * General documentation: > This is currently with out TTO. All relevant stuff should be released > under a suitable Open Source License, most probably LGPL by summer 2013, > but currently, the relevant SOLAS components are on private Git > > @Ankit, @Dave, @Milan, could you provide this info regarding LION, Matrex, > M4Loc? > > > > > > > Thanks in advance for your help. > > > > > > > > Of course, you are welcome to modify my current draft to come up with > > an enhanced version: > > > > > > > > http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_hi > > gh_level_summary#XLIFF-based_CMS-to-TMS_Roundtripping_for_HTML.26XML > > > > > > > > Cheers, > > > > Christian > > > > > > > > From: Felix Sasaki [mailto:fsasaki@w3.org] > > Sent: Saturday, February 16, 2013 2:34 AM > > To: public-multilingualweb-lt@w3.org > > Subject: [All] high level use cases not yet ready to publish, please > > have another look > > > > > > > > Hi all, esp. Christian, > > > > I had a brief look at > > http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_hi > > gh_level_summary and I think this is not yet ready even for a first > > public working draft. > > > > I won't point to specific sections here, but please have another look > > at "your" section with the following in mind: > > > > - Don't mention something that is not in the spec anymore, e.g. > > "Disambiguation". Call this "Text Analysis Annotation". > > - The "More Information and Implementation Status/Issues" sections are > > extremely heterogenous. Please, re-write them following this simple > > pattern taken from ENLASO: > > > > > > [ > > > > Tool: Okapi Framework (ENLASO). > > > > Detailed slides at http://tinyurl.com/8tmg49d Running software: > > http://code.google.com/p/okapi/downloads/list > > Source code: http://code.google.com/p/okapi/source/browse/ > > General documentation: http://www.opentag.com/okapi/wiki/ > > > > ] > > > > - Don't just "list" data categories. Describe their benefit in your > > implementation. > > - Use a simple & sweet language style like e.g. in > > http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_hi > > gh_level_summary#Simple_Machine_Translation > > > > > > The document should be a *high level* overview. Currently it has 20 > > pages - that's too long. We can provide details & more text in other > publications. > > > > NOTE for the EC project folks: this document is an important part for > > us to raise awareness for Rome and to give input for the Luxembourg > > review. Please invest the time to take above considerations into account. > > > > Please, do that by Tuesday EOB 19 February. > > > > Christian, what are your thoughts on editing this and making this > > ready for publication, also in terms fo timing. > > > > Best, > > > > Felix > > > > > > > > > > > > >
Received on Wednesday, 6 March 2013 12:28:10 UTC