@inproceedings{ kay04,
  crossref = {xmleu2004},
  author = {Michael Kay},
  title = {XSLT and XPath Optimization},
  uri = {http://idealliance.org/papers/dx_xmle04/papers/02-03-02/02-03-02.html},
  topic = {xpath1[0.9] xslt1[0.9]},
  abstract = {This paper describes the main techniques used by the Saxon XSLT and XQuery processor to optimize the execution of XSLT stylesheets and XPath expressions, and reviews some additional XSLT and XPath optimization techniques that are not (yet) used in Saxon. The primary focus is on XPath rather than XSLT, partly because Saxon does relatively little optimization at the XSLT level (other than in the way pattern matching works). Recent releases of Saxon support XQuery 1.0 as well as XSLT 2.0. However, the XQuery processor is an in-memory processor, not a database query engine. Optimizing database queries is an entirely different art, because it relies so heavily on rearranging queries to exploit persistent indexes. An in-memory processor does not have this opportunity, because the only indexes available are those that are constructed transiently for the duration of a transformation or query. Saxon's processing can be divided into three phases: parsing, static analysis, and run-time execution. These are described in the three main sections of this paper.}
}

{"_id":{"_str":"53ff72c17c90ec6e13001125"},"__v":0,"authorIDs":[],"author_short":["Kay, M."],"bibbaseid":"kay-xsltandxpathoptimization","bibdata":{"downloads":0,"role":"author","bibbaseid":"kay-xsltandxpathoptimization","uri":"http://idealliance.org/papers/dx_xmle04/papers/02-03-02/02-03-02.html","type":"inproceedings","topic":"xpath1[0.9] xslt1[0.9]","title":"XSLT and XPath Optimization","key":"kay04","id":"kay04","crossref":"xmleu2004","bibtype":"inproceedings","bibtex":"@inproceedings{ kay04,\n crossref = {xmleu2004},\n author = {Michael Kay},\n title = {XSLT and XPath Optimization},\n uri = {http://idealliance.org/papers/dx_xmle04/papers/02-03-02/02-03-02.html},\n topic = {xpath1[0.9] xslt1[0.9]},\n abstract = {This paper describes the main techniques used by the Saxon XSLT and XQuery processor to optimize the execution of XSLT stylesheets and XPath expressions, and reviews some additional XSLT and XPath optimization techniques that are not (yet) used in Saxon. The primary focus is on XPath rather than XSLT, partly because Saxon does relatively little optimization at the XSLT level (other than in the way pattern matching works). Recent releases of Saxon support XQuery 1.0 as well as XSLT 2.0. However, the XQuery processor is an in-memory processor, not a database query engine. Optimizing database queries is an entirely different art, because it relies so heavily on rearranging queries to exploit persistent indexes. An in-memory processor does not have this opportunity, because the only indexes available are those that are constructed transiently for the duration of a transformation or query. Saxon's processing can be divided into three phases: parsing, static analysis, and run-time execution. These are described in the three main sections of this paper.}\n}","author_short":["Kay, M."],"author":["Kay, Michael"],"abstract":"This paper describes the main techniques used by the Saxon XSLT and XQuery processor to optimize the execution of XSLT stylesheets and XPath expressions, and reviews some additional XSLT and XPath optimization techniques that are not (yet) used in Saxon. The primary focus is on XPath rather than XSLT, partly because Saxon does relatively little optimization at the XSLT level (other than in the way pattern matching works). Recent releases of Saxon support XQuery 1.0 as well as XSLT 2.0. However, the XQuery processor is an in-memory processor, not a database query engine. Optimizing database queries is an entirely different art, because it relies so heavily on rearranging queries to exploit persistent indexes. An in-memory processor does not have this opportunity, because the only indexes available are those that are constructed transiently for the duration of a transformation or query. Saxon's processing can be divided into three phases: parsing, static analysis, and run-time execution. These are described in the three main sections of this paper."},"bibtype":"inproceedings","biburl":"http://dret.net/biblio/dret.bib","creationDate":"2014-08-28T18:19:45.950Z","downloads":0,"keywords":[],"search_terms":["xslt","xpath","optimization","kay"],"title":"XSLT and XPath Optimization","year":null,"dataSources":["mL7NKvaepNEWFcMvG"]}