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

Hi Christian,

1. Finally WICS will support all ITS 2.0 data categories. In Rome we will present just a few examples: Translate, Localization Note and Terminology categories.

2. Yes, colour coding is one of a few available "inline" tools to reveal the presence of metadata. In case of content being just plain text without any visual formatting, we could implement also the following:
- underlined text
- colour of characters
- font in italics

Regards,
Renat

From: Lieske, Christian [mailto:christian.lieske@sap.com]
Sent: Thursday, February 28, 2013 7:49 PM
To: Renat Bikmatov
Cc: public-multilingualweb-lt@w3.org
Subject: RE: [All] high level use cases not yet ready to publish, please have another look - Logrus -

Hi Renat,

While editing the section related to WICS, two questions arouse. Hopefully, it is alright to contact you with them ...


1.      Which of the ITS 2.0 data categories are used in WICS?

Possible example: translate


2.      Inhowfar do the data categories that are being used control the WICS processing?

Possible example: translate="no" renders content in a specific colour

Cheers,
Christian

From: Felix Sasaki [mailto:fsasaki@w3.org]
Sent: Montag, 18. Februar 2013 17:23
To: Lieske, Christian
Subject: Fwd: Re: [All] high level use cases not yet ready to publish, please have another look - Logrus -

FYI.

- Felix


-------- Original-Nachricht --------
Betreff:

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

Datum:

Mon, 18 Feb 2013 17:22:25 +0100

Von:

Felix Sasaki <fsasaki@w3.org><mailto:fsasaki@w3.org>

An:

Renat Bikmatov <renatb@logrus.ru><mailto:renatb@logrus.ru>

Kopie (CC):

Serge Gladkoff <sgladkoff@logrus.ru><mailto:sgladkoff@logrus.ru>


Am 18.02.13 17:12, schrieb Renat Bikmatov:
Hi Felix,

Please find attached the shortened version of Section 2.16.2 of Logrus use case description.

Thanks, Renat, now at
http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary#ITS_2.0_Metadata:_Work-In-Context_Showcase

Best,

Felix



Regards,
Renat

From: Felix Sasaki [mailto:fsasaki@w3.org]
Sent: Saturday, February 16, 2013 2:34 AM
To: public-multilingualweb-lt@w3.org<mailto: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