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

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

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 6 Jul 2012 08:15:04 +0200
Message-ID: <CAL58czoSZdHiO7--=7=4XW79KZOK16xMmxigAaumjNB2PeMz+g@mail.gmail.com>
To: Yves Savourel <ysavourel@enlaso.com>
Cc: public-multilingualweb-lt@w3.org
Thanks a lot for the summary, Yves.

2012/7/6 Yves Savourel <ysavourel@enlaso.com>

> Hi all,
>
> To follow up on the discussion thread started here:
>
> http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Jun/0007.html
>
> - It looks like this possible addition to ITS would be limited to XPath
> variables, as no-one seem to have use cases outside XPath expressions.
>
> The new ITS element would be a <its:param>, child of <its:rules>:
>
> <its:param name='myParam'>default value</its:param>
>
> - The possible conflict between ITS parameters and tool-specific
> parameters (like for XSLT) could be worked out using QNames (see
> http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Jun/0077.html
> )
>
> This new element to set the defaults would not be a data category, but
> something all tools using <its:rules> would have to support.
>
> I assume tools should (but may not) implement a way to pass values to
> override the defaults.
>
> So, I think, we have resolve all the technical questions.
> Now we have to decide if we do this or not.
>


I want to bring one point to the attention of the implementors:
"This new element to set the defaults would not be a data category, but
something all tools using <its:rules> would have to support."

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. Currently, we have a very clear notion of conformance at

http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#conformance-product-processing-expectations

 Processors need to compute the ITS information that pertains to a node in
an XML document. The ITS processing expectations define how the computation
has to be carried out. Correct involves support for <a
href="#def-selection"shape
="rect">selection mechanism</a>, <a href="#datacategories-defaults-etc"
shape="rect">defaults / inheritance / overriding characteristics</a>, and <ahref
="#selection-precedence" shape="rect">precedence</a>


I would be reluctant to complicate this by saying "some processor MAY
implement parameters, other not".


Any thoughts?



Felix



>
> -ys
>
>
>
>
>


-- 
Felix Sasaki
DFKI / W3C Fellow
Received on Friday, 6 July 2012 06:15:28 UTC

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