XSLT 2.0 and XPath 2.0 Programmer's Reference, 4th Edition (728 page)

Sometimes we just want to display the year:

Finally, there's one more function we will be using, which converts a string so that the initial letter is a capital:

And that's the end of the preliminaries. Now we can get on with some actual template rules.

The root template rule starts by testing to see if the outermost element of the source document is a GEDCOM element. It doesn't just test the name of the element: the sequence type descriptor
schema-element(GEDCOM)
also checks that the type annotation is appropriate. If the user supplies a source document that hasn't been validated, then this test will fail, even if the document is actually valid, and the stylesheet will proceed no further. If this check weren't present here, some strange and difficult-to-diagnose failures could occur later on, because we are relying on the type annotations being present in the input data.

The entire transformation is then wrapped inside an

instruction. This instruction is usually used only when producing multiple result trees, but in this case we're using it for the primary result tree, in order to request validation. It's not actually specifying what the type of the result document must be, only that it must be what it says it is:
validation=“strict”
will cause a failure if the outermost element in the result tree isn't defined in some imported schema, or if the result tree isn't valid against that definition. In this case, the intent is to check that the result is valid XHTML.

The outline of the HTML page is produced when we process the selected

element, as one might expect:

This template rule works through the process of generating the output page. Some observations:

• The title in the HTML header is generated by first creating a variable, and then copying the value of the variable to the