- From: Lieske, Christian <christian.lieske@sap.com>
- Date: Thu, 21 Dec 2006 17:37:09 +0100
- To: <public-i18n-its@w3.org>
- Message-ID: <544FBEB6875DAA46A08323B58D26B80194FE26@dewdfe14.wdf.sap.corp>
Hi, Here's a slightly modified text. It includes feedback from Felix (see http://lists.w3.org/Archives/Public/public-i18n-its/2006OctDec/0076.html) and Yves (see http://lists.w3.org/Archives/Public/public-i18n-its/2006OctDec/0078.html) Cheers, Christian === Caveat Related to XSLT-based Processing of ITS Selector Attributes The values of ITS "selector" attributes are XPath absolute location paths. Accordingly, the following is a legitimate value: myElement/descendant-or-self::*/@* Unfortunately, values like this cause trouble when they are used in XSLT-based processing of ITS where the values of the ITS "selector" attributes are used as values of "match" attributes of XSLT templates. The reason for this is the following: "match" attributes may only contain a restriction/subset of XPath expressions, so-called "patterns" (see http://www.w3.org/TR/xslt#patterns <http://www.w3.org/TR/xslt> ). Basically the following restrictions hold for patterns: - only axes "child" or "attribute" allowed - "//" or "/" possible - id() or key() function possible - predicates possible Using only XSLT patterns in ITS "selector" attributes helps to avoid this issue. In many cases, this is possible by using patterns with predicates. The value above may for example be rewritten as follows *[self::myElement]/@* | myElement//*/@*
Received on Thursday, 21 December 2006 16:43:30 UTC