W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > February 2013

RE: [All] high level use cases not yet ready to publish, please have another look

From: Lieske, Christian <christian.lieske@sap.com>
Date: Mon, 18 Feb 2013 08:39:36 +0100
To: Felix Sasaki <fsasaki@w3.org>, "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
Message-ID: <8EA44C66E2911C4AB21558F4720695DC60E0C8E896@DEWDFECCR01.wdf.sap.corp>
Dear all,

Based on Felix' observation (Thanks!) and his call for action, I did not yet work extensively on the document. So far, I mainly addressed the following:


1.       Drafted an Introduction/Overview

2.       Ran a spell checker on the document, and corrected accordingly

3.       Corrected a few syntactical/stylistic issues (e.g. split infinitives)

While doing that, I made a couple of observations and came up with a number of ideas that possibly could help to move forward things quickly:


1.       Use US English :) (thus, write "localization" and not "localization")

2.       The Wiki is able to detect some spelling errors - look at them and correct them

3.       I think a glossary/terminology section (possibly even a separate Wiki page) would be great. This would for example help to be consistent. Example: Do we talk about "ITS 2.0 properties", "ITS 2.0 mark-up", "ITS 2.0 Markup", ...?

If time permits, you may want to weed out the following passive voice, fragments, too many nouns.

Cheers,
Christian

From: Felix Sasaki [mailto:fsasaki@w3.org]
Sent: Freitag, 15. Februar 2013 23:34
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_-_high_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_-_high_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 Monday, 18 February 2013 07:40:08 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:25:08 UTC