NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.
Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
Client-side XSLT (CSX) is often used in scenarios where data (in XML) from a remote server is provided to a user who processes it in some way, for example rendering it locally for display. That is, the server provides the data and the client does the work on that data to make it useful. However, that is not the only scenario in which CSX is useful. In an environment in which the user already has, or is in the process of creating, XML, CSX can be a convenient and powerful tool, enabling users to perform operations on their data, securely, on their own systems. The potential for this use of CSX is illustrated with uses of SaxonJS for several security-related applications.
Piez, W.
(2021),
Client-side XSLT, Validation and Data Security, Balisage Series on Markup Technologies, Washington, DC, US, [online], https://doi.org/10.4242/BalisageVol26.Piez01, https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=933217
(Accessed October 14, 2025)