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

RE: [ACTION-155] (related to [ISSUE-16]) parameters for rules

From: Yves Savourel <ysavourel@enlaso.com>
Date: Fri, 6 Jul 2012 08:52:06 +0200
To: <public-multilingualweb-lt@w3.org>
Message-ID: <assp.0534b88949.assp.0534570690.002e01cd5b43$dc33a140$949ae3c0$@com>
Hi Felix, all,

> ...So in addition to the technical issues, we need to 
> think about whether global implementations of ITS 2.0
> will support this, for each data category they implement.
> ...
> I would be reluctant to complicate this by saying 
> "some processor MAY implement parameters, other not".
>
> Any thoughts?

Just a couple of notes:

- We don't have restrictions about not using variables in XPath expressions, but we don't have a way to declare them and provide defaults. So I think it's important to have <its:param> (isn't it like fixing a 1.0 oversight?)

- Should we make a distinction between:

A) supporting <its:param>, that it: understanding <its:param> and providing the defaults value to the XPath engine,

and B) (in addition) supporting overriding the ITS parameters, that is: providing a way (tool-specific) to set values other than the defaults?

I don't think it's very useful to support A without offering B. But from a conformance viewpoint maybe only A is required? I'm thinking that some tools may have issues implementing B. For example tools that currently rely on just processing the XML and the ITS rules (and have no way to set any addition options: no UI or no command-line options). But I'm probably just over-complicating things, and we don't need to make a distinction.

-ys
Received on Friday, 6 July 2012 06:52:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:47 UTC