From ff03d46b4f9f2b9324b3b660f570f683f204e1a3 Mon Sep 17 00:00:00 2001 From: Erik Siegel Date: Tue, 11 Jun 2019 15:49:54 +0100 Subject: [PATCH] Changed all match pattern to selection pattern and added a termdef for this --- xproc/src/main/xml/specification.xml | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/xproc/src/main/xml/specification.xml b/xproc/src/main/xml/specification.xml index e7bcfa3e8..b6ce75b0d 100644 --- a/xproc/src/main/xml/specification.xml +++ b/xproc/src/main/xml/specification.xml @@ -1967,8 +1967,14 @@ static analysis is implementation-defined. If an implementation supports XPath 2.0 or later, the data model constructed with which to - evaluate XPath expressions and match patterns should take advantage + evaluate XPath expressions and selection patterns should take advantage of as much PSVI information as possible. + + A selection pattern uses a + subset of the syntax for path expressions, and is defined to match a node if the + corresponding path expression would select the node. It is defined as in the + XSLT 3.0 + specification. Except as specified above, or in the descriptions of individual steps, @@ -3272,8 +3278,8 @@ are allowed anywhere, and attributes that are XPathExpression, XSLTSelectionPattern: As a string per , including whitespace normalization, and the further requirement to be a - conformant Expression per or selection - pattern per . + conformant Expression per or + selection pattern per . @@ -3353,12 +3359,12 @@ attribute">extension attributes. extension steps are encouraged to use this code for general failures. - In most steps which use a select expression or match pattern, any kind of node can + In most steps which use a select expression or selection pattern, any kind of node can be identified by the expression or pattern. However, some expressions and patterns on some steps are only applicable to some kinds of nodes (e.g., it doesn't make sense to speak of adding attributes to a comment!). It is a dynamic error if a select - expression or match pattern returns a node type that is not allowed by the + expression or selection pattern returns a node type that is not allowed by the step. @@ -3544,7 +3550,7 @@ each document in the sequence is processed in turn producing a sequence on the output. The match attribute specifies - an XSLT match pattern. Each matching node in the source document is wrapped in a document + an XSLT selection pattern. Each matching node in the source document is wrapped in a document node, as necessary, and provided, one at a time, to the viewport's subpipeline on a port named current. The base URI of the resulting document that is passed to the subpipeline is the base URI of the matched @@ -3576,8 +3582,8 @@ on the output. port. What appears on the output from the p:viewport will be a copy of the input document where each matching node is replaced by the result of - applying the subpipeline to the subtree rooted at that node. In other words, if the match - pattern matches a particular element then that element is wrapped in a document node and + applying the subpipeline to the subtree rooted at that node. In other words, if the + selection pattern matches a particular element then that element is wrapped in a document node and provided on the current port, the subpipeline in the p:viewport is evaluated, and the result that appears on the output port replaces the matched element.