Caspar Van der Linden's personal annotations on this page
Cvdlinden bookmarked
on 2009-02-05
-
Today's reporting applications use XML extensively to format data, regardless of the different data sources. More specifically, Web-based reporting applications usually use XSL transformations to present this XML data to different clients. The standard flow for current reporting systems is more or less represented by this chain: legacy data source > XML > XSL transformation > Web browser. Note that you can perform the XSL transformation step either on the server side or the client side (the browser). The choice generally depends on nonfunctional requirements; for example, in a system with a high request rate, moving the XSL transformation to the client could result in performance and scalability benefits. The Web page coming from the XSL transformation must be internationalized. However, when the XSL transformation is performed on the client, the internationalization should be handled during the transformation itself. This means that the XSL transformation should manage the translation of the messages dynamically. In this article, we propose a general solution to address this issue.
This link has been bookmarked by 1 people . It was first bookmarked on 25 Mar 2009, by Caspar Van der Linden.
-
-
Today's reporting applications use XML extensively to format data, regardless of the different data sources. More specifically, Web-based reporting applications usually use XSL transformations to present this XML data to different clients. The standard flow for current reporting systems is more or less represented by this chain: legacy data source > XML > XSL transformation > Web browser. Note that you can perform the XSL transformation step either on the server side or the client side (the browser). The choice generally depends on nonfunctional requirements; for example, in a system with a high request rate, moving the XSL transformation to the client could result in performance and scalability benefits. The Web page coming from the XSL transformation must be internationalized. However, when the XSL transformation is performed on the client, the internationalization should be handled during the transformation itself. This means that the XSL transformation should manage the translation of the messages dynamically. In this article, we propose a general solution to address this issue.
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.