RE: [ACTION-224] Provide a section of MT service provider as user

Dear Pedro and Jörg,

I support the current version with minor changes:

This type of service is intended to serve a broad user community => This type of service is intended for a broad user community / This type of service is intended to target a broad user community / This type of service is targeting a broad user community / This type of service is aimed for a broad user community / other alternatives.

These tasks consume and generate valuable metadata from and for third party consumers => These tasks consume and generate valuable metadata from and for third party clients / customers / users / other alternatives.

Just for the sake of avoiding the repetition ;)

processes and services, such as MT post-editing, MT training, and MT terminological enhancement => processes and services, such as MT post-editing, MT training and MT terminological enhancement (if we one follows UK grammar throughout the whole document)

With best wishes,
Tatiana

-----Original Message-----
From: Pedro L. Díez Orzas [mailto:pedro.diez@linguaserve.com] 
Sent: Tuesday, October 02, 2012 2:12 PM
To: joerg@bioloom.de
Cc: public-multilingualweb-lt@w3.org
Subject: RE: [ACTION-224] Provide a section of MT service provider as user

Thank you  very much Joerg. 

If Tatiana agrees, we can take this version you sent.
Best,
Pedro

-----Mensaje original-----
De: "Prof. Dr. Jörg Schütz" [mailto:joerg@bioloom.de] Enviado el: martes, 02 de octubre de 2012 11:16
Para: "Pedro L. Díez Orzas"
CC: public-multilingualweb-lt@w3.org
Asunto: Re: [ACTION-224] Provide a section of MT service provider as user

Hi Pedro and all,

Just some few additions and enhancements which you might use for the MT paragraph.

Cheers -- Jörg

******
This type of service is intended to serve a broad user community ranging from developers and integrators through translation companies and agencies, freelance translators and post-editors to ordinary translation consumers and other types of MT employment. Data categories are envisaged for supporting and guiding the different automated backend processes of this service type, thereby adding sustantial value to the service results as well as possible subsequent services. These processes include basic tasks, like parsing constraints and markup, and compositional tasks, such as disambiguation. These tasks consume and generate valuable metadata from and for third party consumers, for example, provenance information and quality scoring, and add relevant information for follow-on tasks, processes and services, such as MT post-editing, MT training, and MT terminological enhancement.
******

On Oct 01, 2012 at 17:14 (CEST), Pedro L. Díez Orzas wrote:
> Dear all,
>
> Here the paragraph I suggest to add:
>
> */Machine Translation /*
>
> This type of user comprises developers, integrators, translation 
> companies, post-editors, customers and other type of MT users. Data 
> categories are envisaged for different automated processing in the 
> input (from low level tasks, like parsing constraints and markup, to 
> high level tasks, such as disambiguation); to generate in the output 
> valuable metadata for third parties (for example, indicating 
> provenance or quality scoring); and to pass through relevant 
> information to needed tasks, such as MT post-editing, MT training and 
> MT terminological enrichment.
>
> Tatiana wanted to contribute to this. Please feel free to modify to 
> have it ready for tomorrow.
>
> Best,
>
> Pedro
>

Received on Wednesday, 3 October 2012 15:59:45 UTC