- From: Felix Sasaki <fsasaki@w3.org>
- Date: Wed, 12 Sep 2012 10:01:26 +0200
- To: Dave Lewis <dave.lewis@cs.tcd.ie>
- Cc: "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
- Message-ID: <CAL58czp_Rb9m8cuqYv3oZMPSVGG-gAYLM_fLx1m4zMPMb84+bw@mail.gmail.com>
HI Dave, thanks a lot for the template and the example. I would propose to simplify the description a lot. It is too detailed for a general audience. We can add more detailed descriptions in a separate section. But the main section could just consist of short descriptions - max 1 paragraph for each item - saying: - This is our implementation: CMS Lion, Statistical MT System. - The metadata solves the following problems: (bullet list). Example for "translate": "translate metadata assures that pieces of content are not translated - Benefits: better translation quality, ... - Example. I think all of the above is already in your text. The text is just not targeted to a general audience. We would need that both for the HTML folks and for a general best practice document. One very important thing is missing: a link to one or several running systems, implementing the use case. I had a discussion last week with our PO what the success criteria for our work are. The list above already contains one of them - better quality in localization / LT via metadata aware tools-, but the other one is: reproducibility. If one cannot recreate the result it is hard to claim a useful implementation. Maybe you don't have that ready yet, but it would be helpful to have that during interop testing (that is, early next year). Re-creating, btw., does not only mean "download link to open source tool". It can also be a link to a commercial tool, a web service etc. Another important point is the data categories used, We don't have translationAgent yet in the specification, so I would keep it out for the moment. The same for mtConfidence. Both are important, but if people don't have the time to resolve the issues around these, we will have to drop them from ITS 2.0. So they shouldn't be in a use case yet. Another aspect are data categories being produced, but not used in the example. E.g. language information is being created, but what is the benefit? I don't mean the benefit in general, but in Lion CMS or a different system that in the use case makes use of the metadata. If there is no such use, I would only mention that such metadata can be generated, but don't actually generate it in the example. Do you agree with the above points and do you think you could change the use case description? Best, Felix 2012/9/12 Dave Lewis <dave.lewis@cs.tcd.ie> > Hi All, > As discussed on the last call we are aiming to collect together peoples > plans for ITS implementation to present and where possible demo in Prague. > Based on that discussion I populated the agenda with implementations people > had mentioned > > Please check the list set out for session 3&4 at: > http://www.w3.org/**International/multilingualweb/** > lt/wiki/PragueSep2012#25_Sept:**_MLW-LT_WG_meeting_agenda<http://www.w3.org/International/multilingualweb/lt/wiki/PragueSep2012#25_Sept:_MLW-LT_WG_meeting_agenda> > > Let me know if there are any not listed there that you would like to > present. > > Also as discussed that the meeting, we need to start gathering more > details on these planned implementations, linked from the implementation > commitment page: > http://www.w3.org/**International/multilingualweb/** > lt/wiki/Implementation_**Commitments#Use_Case_**Demonstrations<http://www.w3.org/International/multilingualweb/lt/wiki/Implementation_Commitments#Use_Case_Demonstrations> > > I've revised the suggested documentation template: > http://www.w3.org/**International/multilingualweb/**lt/wiki/Use_Case_** > Demonstration_Template<http://www.w3.org/International/multilingualweb/lt/wiki/Use_Case_Demonstration_Template> > > In particular not the need to specifying which ITS features (datacategory > + HTML5|XML + GLOBAL|LOCAL) and specifying clearly which individual > components are being used for which ITS processing. This will help us gauge > the level of HTML5 implementation commitment that Felix has explained we > now really need. > > As an example I've put up a partially complete description of a simple > HTML-SMT roundtrip scenario what we've been on with DCU: > http://www.w3.org/**International/multilingualweb/** > lt/wiki/Simple_Segment_**Machine_Translation_Use_Case_** > Demonstration#Step_4:_**Assemble_Target_HTML5<http://www.w3.org/International/multilingualweb/lt/wiki/Simple_Segment_Machine_Translation_Use_Case_Demonstration#Step_4:_Assemble_Target_HTML5> > > comments welcome, > Dave > > > -- Felix Sasaki DFKI / W3C Fellow
Received on Wednesday, 12 September 2012 08:01:53 UTC