- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Thu, 20 Sep 2012 18:40:15 -0600
- To: <public-multilingualweb-lt@w3.org>
Hi Felix, all, The solution of some tool information being declared outside the usual selector mechanism may work for one set of instances of a given data category, but not several. For example: In an XLIFF document I'd like to use the its:mtConfidenceScore attribute for each <m:match> element that holds a translation candidate for an entry (This is a likely real-life case, not just a random example). You can have multiple matches per entry, and they are very likely to be from different engines. Having a document-level tool information does not work. In this case we do need to have the tool information per entry. Looking again at the "partial override" solution I don't think pointers are a problem. They just tell where to get the information to apply to the node, as far as overriding goes it's no different than setting directly the information. The case of the stand-off markup is specific (so far) to Localization Quality Issue. I haven't thought yet about what that implies for the "partial override" but it's likely that there are ways to specify what is done in those cases. The bottom line is that all those local/global/standoff attributes specify information and are applies in a given order: we've got to be able to know if the information ABC exists or not when we apply the next rule, and therefore be able to keep the current value or override it depending on whether the next rule re-define that information or not. Cheers, -ys
Received on Friday, 21 September 2012 00:40:48 UTC