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

Hi Christian,

 

Find my comments inline.

 

Cheers.

__________________________________

Pablo Nieto Caride

Dpto. Técnico/I+D+i

Linguaserve Internacionalización de Servicios, S.A.

Tel.: +34 91 761 64 60 ext. 0422
Fax: +34 91 542 89 28 

E-mail:  <mailto:pablo.nieto@linguaserve.com> pablo.nieto@linguaserve.com

www.linguaserve.com <http://www.linguaserve.com/> 

 

«En cumplimiento con lo previsto con los artículos 21 y 22 de la Ley
34/2002, de 11 de julio, de Servicios de la Sociedad de Información y
Comercio Electrónico, le informamos que procederemos al archivo y
tratamiento de sus datos exclusivamente con fines de promoción de los
productos y servicios ofrecidos por LINGUASERVE INTERNACIONALIZACIÓN DE
SERVICIOS, S.A. En caso de que Vdes. no deseen que procedamos al archivo y
tratamiento de los datos proporcionados, o no deseen recibir comunicaciones
comerciales sobre los productos y servicios ofrecidos, comuníquenoslo a
clients@linguaserve.com, y su petición será inmediatamente cumplida.»

 

"According to the provisions set forth in articles 21 and 22 of Law 34/2002
of July 11 regarding Information Society and eCommerce Services, we will
store and use your personal data with the sole purpose of marketing the
products and services offered by LINGUASERVE INTERNACIONALIZACIÓN DE
SERVICIOS, S.A. If you do not wish your personal data to be stored and
handled, or you do not wish to receive further information regarding
products and services offered by our company, please e-mail us to
clients@linguaserve.com. Your request will be processed immediately.”

__________________________________

De: Lieske, Christian [mailto:christian.lieske@sap.com] 
Enviado el: domingo, 03 de marzo de 2013 9:49
Para: 'Ankit Srivastava'; Pablo Nieto Caride (pablo.nieto@linguaserve.com);
thomas.ruedesheim@lucysoftware.com
CC: public-multilingualweb-lt@w3.org
Asunto: RE: [All] high level use cases not yet ready to publish, please have
another look - Linguaserve/Cocomore -

 

Hi Ankit, Pablo, Thomas (and others at DCU, Linguaserver, and LucySoftware),

 

While editing the section on “Online MT System Internationalization” the
following specific questions came up. Hopefully, it is alright to contact
you with them …

 

1.      Can content editors/revisers work on both the source language and
the target language?

[PNC]: Not really, just the target language, the source content can only be
edited by the client, in his own environment, not ours. 

2.      “Domain” is used to “select the appropriate engine, corpus or
vocabulary”. Unfortunately, I am unsure about the “corpus” bit, since from
my understanding the corpus only comes into play while training a language
model.

[PNC]: Probably you’re very right, maybe Ankit can shed a light on this.

3.      Did I rewrite the data category information properly?

[PNC]: The edition is really good, thank very much!

4.      What is the semantics of “Source code: Restricted” Can it be
interpreted as “Closed source”?

[PNC]: It means that it’s not public, not available to download.

Thanks in advance for your help. 

 

Of course, you are welcome to modify my current draft to come up with an
enhanced version:

[PNC]: Thank you, don’t worry, it’s perfect, I just have to update running
software with a new live demo URL and new testing page to test metadata,
I’ll do this within this week.

http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_lev
el_summary#Content_Internationalization_and_Advanced_Machine_Translation

 

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_-_high_lev
el_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_lev
el_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