W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > April 2012

RE: Parameters for rules?

From: Pedro L. Díez Orzas <pedro.diez@linguaserve.com>
Date: Fri, 20 Apr 2012 14:54:41 +0200
To: "'Phil Ritchie'" <philr@vistatec.ie>, "'Yves Savourel'" <ysavourel@enlaso.com>
Cc: "'Multilingual Web LT Public List'" <public-multilingualweb-lt@w3.org>
Message-ID: <A51227BDDC4B477896BE3866968C2340@newlas.local>
Me too. This could help also to allow just the update when necessary of the
list of values (for example what we talk about "domains"), without changing
the rest of the recommendation document.
Pedro


-----Mensaje original-----
De: Phil Ritchie [mailto:philr@vistatec.ie] 
Enviado el: viernes, 20 de abril de 2012 14:25
Para: Yves Savourel
CC: Multilingual Web LT Public List
Asunto: Re: Parameters for rules?


Sounds like a very useful feature to me.

Phil



On 20 Apr 2012, at 05:03, "Yves Savourel" <ysavourel@enlaso.com> wrote:

> Hi all,
>
> One thing I've noticed during the past years working with ITS 1.0 is
that, quite often, having a way to use 'variables' in ITS rules would have
been a lot more efficient having to create multiple ITS files.
>
> For example, imagine some rules that say:
>
> In file 1: <its:translateRule selector="//*[@stage=LevelA]"
translate="no"/>
>
> In file 2: <its:translateRule selector="//*[@stage=LevelB]"
translate="no"/>
>
> When the calling tool could instead use a single file with:
>
> <its:translateRule selector="//*[@stage=${LevelValue}]" translate="no"/>
>
> Or something similar.
>
> I imagine that with the new data categories, this kind of construct would
be even more handy than in ITS 1.0.
>
> This is not a possible requirement for a new data category, but rather an
enhancement of the overall mechanism. So a few questions:
>
> 1) Would having such variable mechanism (with possibly default values in
the rule file) be useful?
>
> 2) Is it ok to contemplate changes like this to the basic ITS mechanism,
or are they out-of-scope?
>
> 3) If this is something we'd like to include, where do we capture this in
the requirements document?
>
> Cheers,
> -yves
>
>
>
>


************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail.

www.vistatec.com
************************************************************
Received on Friday, 20 April 2012 12:56:57 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:24:55 UTC