forked from mikesub/xsls
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathquestions.txt
32 lines (26 loc) · 1.24 KB
/
questions.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
apply templates vs. for-each
call-template
element
xpath вверх по дереву.
варианты узнать, что данные узлы на самом деле один и тот же узел?
тематические ресурсы
приоритеты и алгоритм выбора шаблона который отработает
1. imports
2. priorities
* node 0
* namespace:* -0.25
* node() or * -0.5
* otherwise 0.5
Built-in Template Rules
<xsl:template match="*|/">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="*|/" mode="m">
<xsl:apply-templates mode="m"/>
</xsl:template>
<xsl:template match="text()|@*">
<xsl:value-of select="."/>
</xsl:template>
<xsl:template match="processing-instruction()|comment()"/>
The built-in template rule for namespace nodes is also to do nothing. There is no pattern that can match a namespace node; so, the built-in template rule is the only template rule that is applied for namespace nodes.
The built-in template rules are treated as if they were imported implicitly before the stylesheet and so have lower import precedence than all other template rules. Thus, the author can override a built-in template rule by including an explicit template rule.