Parameters for rules?

• From: Yves Savourel <ysavourel@enlaso.com>
• Date: Fri, 20 Apr 2012 06:02:50 -0600
• To: "'Multilingual Web LT Public List'" <public-multilingualweb-lt@w3.org>
• Message-ID: <assp.0457e3684d.assp.0457d51092.001b01cd1eed$82b38d20$881aa760$@com>

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

Received on Friday, 20 April 2012 12:03:18 UTC