RE: Readiness definition

Hi Dave,

 

Thanks for the quick response, find my comments inline. 

 

Cheers,

Pablo.

 

 

comments inline: 

On 27/08/2013 11:27, Pablo Nieto Caride wrote:

Hi Dave and other potential implementers of Readiness,

 

Attached is the latest document with info related to the Readiness
definition and implementation that I possess, I don’t know whether there is
something more recent or not, if so, please send it to me or point where it
can be found.

 

thanks pablo for advancing this topic, I'll take a look.
[PNC]: Great thanks.



I am writing because our client is interested in using this extension to
mark content that must be post-edited after the machine translation, the
problem we encountered is that the process of post-edition depends on the
target language, that is, if the quality of the machine translation in the
target language is high maybe the process of post-edition is not needed. I
thought of including a new optional attribute, targetLanguage, that can
contain a comma separated list of values based on
http://www.rfc-editor.org/rfc/bcp/bcp47.txt, if it is absent that means that
applies to all target languages. Any thoughts on this?


I'll think about that. initially I'd say that the readiness approach was
defined as being generic to process beyond just translation, e.g. for source
QA or text analysis, so this should at the very least be optional. 

When we discussed this originally, i think the concensus was that this sort
of information was better in a project descriptor of some kind - perhaps
taken from LinPort. It could be added as additional meta-data, but from a
linport related namespace, or via a pointer to a separate project
description. The core readiness should be restricted to information about
the fact that the annotated content is ready for some processing and for
what exactly - otherwise you could apply the same argument to many other
types of meta-data. 

[PNC]: Ok I understand, looks like the aim of the data category is to inform
that the content is ready to being processed regardless of the target
language if it involves a translation.



 

And one last thing, I don’t quite see how the parameter “revised” works, I
mean, how can you differentiate one version from another, anyone can give an
example? Do you think it is useful?


the intention of this was to cover the situation where the annotated content
is revised after the initial readiness meta-data was added but probably
before the required processing has been completed. This provides a way of
alerting the process that is consuming the content to this change, and take
action if necessary, e.g. re-fetch the revised content and retranslate the
changed content. It was intended to avoid the need for a full version
control system and to support the fact that content is becoming increasingly
dynamic - especially if extracting from a live web CMS. 



[PNC]: Ok I see, thanks for the tip.


cheers,
Dave




 

Thanks,

Pablo.

__________________________________

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.”

__________________________________