Re: [All] domain data category section proposal, please review

Hi Yves, all,

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

> Hi Felix,
>
> > thanks for your comments. I tried to implement the comments at
> >
> http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Jul/0112.html
> > Does that address your comments?
>
> Yes.
>
> Just one thing 'workflow' is used, but the reader may not know what this
> means. Maybe 'consumer tool'? or something more clear?
>

Thanks for the suggestions - Iu used "consumer tools" in the definition and
in the examples.


>
>
> > Regarding to your questions at
> >
> http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Jul/0115.html
> > Yes, you are right, and I updated the table at
> >
> http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#datacategories-defaults-etc
>
> Just a note "Global pointing to existing information" not sure if it
> should be yes or no.
>

Actually: "yes", thanks for checking, fixed.

"Global pointing to existing information" means that you have a "Pointer"
(like domainPointer, or langPointer) that points via a relative XPath
expression to existing values. We basically don't have the pointer
attributes for data categories that provide a fixed set of values, that is:
translate (only two values), directionality (four values), and elements
within text (three values). For these data categories, if there is existing
information, you can easily cover this with several rule elements, e.g.

Mapping the "0" value of "myTranslateAttribute" to ITS translate "no":
<its:translateRule selector="//*[@myTranslateAttribute='0']"
translate="no"/>

Mapping the "1" value of "myTranslateAttribute" to ITS translate "yes":
<its:translateRule selector="//*[@myTranslateAttribute='1']"
translate="yes"/>

Best,

Felix


> I can't recall the distinction exactly.
>
> -ys
>
>


-- 
Felix Sasaki
DFKI / W3C Fellow