- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Sat, 22 Sep 2012 05:31:38 -0600
- To: "'Felix Sasaki'" <fsasaki@w3.org>
- CC: <public-multilingualweb-lt@w3.org>
> Another solution would be to ask the tool XYZ to create a global rule: > <its:toolRule selector="//*[@its:someOtherStuff]" toolRef="#tXYZ"/> > That would not be done during stream based data category processing, > but separately. And asking a tool that produces "ts:someOtherStuff" attributes > to create even automatically the XPath expression "//*[@its:someOtherStuff]" is maybe OK? But if we have 2 tools doing this for the same data category (hence using the same selector) then we're back into one overriding the other. > I wouldn't force tools and wouldn't interrelate data categories. Tool information > is just a hint, like HTML "meta" generator. Like with "meta" generator, the tool > info cannot be checked (e.g. how to check that something has been > created by a Drupal CMS?). But then how can we have a reliable expectations? If a first tool generates one data category markup without tool-information and the next produces the same data category with tool-information, there is no way to be sure any of the tool-information is correct. > Another reason is that I wouldn't see a way to write test cases. Yes, that's another problem. -ys
Received on Saturday, 22 September 2012 11:32:14 UTC