Re: ITS - process overlay

Thanks, yes i was thinking initially of a usecase where text analysis and term were performed on the source format, before it got sucked into the xliff portion of the workflow. But you can see from those xliff examples we're now doing that within the xliff portion of the workflow, and we will be using this for the rome demo, so i'll make this figure consistent.

In general though, outside the context of this particular demo, im not sure that one approach would be more preferable than another, it would depend on the broader content workflow. for example one might run the text analysis and terminology on the source for general consistency reasons beyond its advantages in localisation. In that case, translation of the content to provide a translation glossary could be a separate step.

Thanks,
Dave

On 19 Feb 2013, at 01:52, Yves Savourel <ysavourel@enlaso.com> wrote:

> Hi Dave,
> 
> Just a note. It seems your diagram 'start' at content-I18N, then you have Text Analysis, identify Terms, and then Extraction.
> Wouldn't it be morelogical to have Extraction first?
> 
> -ys
> 
> -----Original Message-----
> From: Dave Lewis [mailto:dave.lewis@cs.tcd.ie] 
> Sent: Tuesday, February 12, 2013 6:55 PM
> To: public-multilingualweb-lt@w3.org
> Subject: ITS - process overlay
> 
> Hi all,
> I've had a stab as a powerpoint figure that we might be able to customise and use across the different ITS use case posters in Rome. 
> Comments welcome!
> 
> I need to do a bit more graphical tidying for sure.
> 
> Let discuss on the wednesday call whether this might give us a common figure we can refactor to use on the different posters.
> 
> cheers,
> Dave
> 
> 
>

Received on Tuesday, 19 February 2013 08:00:41 UTC