barcode generator github c# BUILDING XSLT APPLICATIONS in Font

Creation PDF417 in Font BUILDING XSLT APPLICATIONS

<Channel href="BBC2.xml" /> <Channel href="ITV.xml" /> ... </TVGuide> You already know one way to process all the <Channel> elements from these files: access all the <Channel> elements in TVGuide3.xml and apply templates to the document referenced in the href attribute (remembering to resolve the URL based on the location of the source document): <xsl:template match="TVGuide"> ... <xsl:apply-templates select="Channel/doc(resolve-uri(@href, base-uri(.))/Channel" /> ... </xsl:template>

Note If you prefer, you can use the document() function to do this, with the path Channel/

There s another way to do this. Rather than being a string, the first argument to the document() function can be a sequence. If it is a sequence, then the document() function returns a sequence of the nodes retrieved from all the documents referred to by the URLs in the sequence. What s more, if you don t have a second argument, then if the sequence contains a node, the URL specified by that node is resolved relative to the node itself. So another way of getting the documents referred to by the <Channel> elements is to select the sequence of href attributes as the only argument: <xsl:template match="TVGuide"> ... <xsl:apply-templates select="document(Channel/@href)/Channel" /> ... </xsl:template> The XSLT processor takes each href attribute in turn, resolves the URL based on the base URI of the href attribute, and accesses the XML document at that location.

Summary If the first argument to the document() function is a sequence, it returns the nodes referenced

by all the items in the sequence. If an item is a node, and you don t have a second argument, the URL is resolved relative to the base URI of the node itself.

Summary

As you create bigger XSLT applications, both the stylesheet and the source document can become very large and unwieldy. This chapter looked at two main ways of making XSLT applications more modular. In the first part of the chapter, you saw how to use <xsl:include> and <xsl:import> to split up a stylesheet into several stylesheets. There are two main advantages of splitting up a stylesheet: It makes the stylesheet easier to maintain. It allows you to reuse the same templates and other components in several stylesheets. Importing stylesheets into each other is often more useful than including them, particularly when it comes to reusing the same utility stylesheet in several XSLT applications, because it allows you to override the templates, global variables and parameters, keys, and so on that the imported stylesheet contains. In the second part of this chapter, you learned how to use the doc(), document(), and unparsed-text() functions to access information from documents other than the source of the transformation. The documents retrieved by the doc() and document() functions must be well-formed XML documents, but the documents retrieved by the unparsed-text() function can contain any text at all. These documents can hold information that supplements either the stylesheet or the main source document, for example: Data for performing operations like searching and replacing Lookup tables of various sorts User preferences and customization information Snippets of XHTML to be included in the result Additional information referenced by the source document The doc() and unparsed-text() functions simply retrieve documents based on a URL. If you want to retrieve a document whose URL is relative to the source document, you have to resolve the URL, using resolve-uri(), based on the base URL of a node in the source document, which you can get using the base-uri() function. The document() function has more sophisticated behavior than the doc() function, in several ways. First, the first argument to the document() function can be a sequence, in which case the result of the function call is a sequence of nodes, one for each URL in the sequence. Second, a second argument to the document() function can provide a node whose base URI is used to resolve any relative URLs from the first argument. Finally, the document() function allows you to use fragment identifiers within a URL in order to access specific nodes within a document, rather than always getting the document node.