
	Where results make sense

Topic: Saxon XSLT

Related Topics

John Saxon

Saxons

Shaul

Shunning

Norman Conquest

Epica

Negret

Tribe

Witchcraft

Chatelaine

Bakha

Mintho

Nikita

Citium

Numerology

In the News (Fri 25 Jul 08)

Gordon Brown

Derby County

Mike Huckabee

Lute Olson

Pearl Harbor

Sonia Gandhi

Ricky Hatton

Narendra Modi

Jesus Christ

Rudy Giuliani

	Saxon - LearnThis.Info Enclyclopedia (Site not responding. Last check: 2007-10-12)
		Some Saxons, along with Angles, Jutes and Frisians, invaded Britain in the early Middle Ages, giving their names to the kingdoms of Essex, Sussex and Wessex (the lands respectively of the East, South and West Saxons), which with the shorter-lived Middlesex eventually became part of the kingdom of England.
		A majority of the Saxons remained in continental Europe, forming from the 8th century the Duchy of Saxony.
		The label "Saxons" was generally applied to German settlers who migrated during the 13th century to south-eastern Transylvania in present-day Romania, where their descendants numbered a quarter of a million in the early decades of the 20th century.
	encyclopedia.learnthis.info /s/sa/saxon.html (517 words)

	Saxon: Anatomy of an XSLT processor
		Saxon also allows the tree to be supplied to user-written code for further processing, or to be fed as input to another style sheet.
		Saxon's strategy is therefore to separate rules into two kinds: specific rules, where the node type and name are explicitly specified in the pattern, and general rules, where they aren't.
		Saxon achieves this optimization for a small number of common cases, where most of the attributes to the numbering algorithm are defaulted.
	www-128.ibm.com /developerworks/library/x-xslt2 (5660 words)

	XSLT and XPath Optimization
		The syntax analyser in Saxon is a hand-written recursive descent parser.
		Saxon therefore uses an internal data structure to represent the tree data model that is designed primarily for efficiency in its use of memory.
		Saxon is one of several XSLT processors that implements the standard tail-call optimization, whereby a recursive function or template call (in fact, any call whether recursive or not) that's the last thing done in the body of a template or function is performed after unwinding the stack, not before.
	idealliance.org /papers/dx_xmle04/papers/02-03-02/02-03-02.html (4638 words)

	About SAXON
		In addition, Saxon provides an extensive library of extension elements and extension functions, all implemented in conformance with the XSLT 1.0 standard to ensure that portable stylesheets can be written.
		SAXON is essentially a one-man project: I have done almost all the development myself, except for a small number of routines which I "borrowed" from other open source products, and a few add-ons contributed by users.
		SAXON comes with a bundled XML parser, a modified copy of the Ælfred parser, adapted to notify comments to the application.
	saxon.sourceforge.net /saxon6.5.3 (1547 words)

	[No title]
		He is also the editor of the W3C's XSLT 2.0 specification, which is currently a Last Call Working Draft, and his Java-based Saxon XSLT processor is one of the most successful and popular XSLT processors in the language's history.
		The new XSLT and XPath versions have double the capability of their predecessors, and XQuery is completely new, so there's a lot of new processing power arriving for XML.
		XSLT 2.0 is still better at processing data with unpredictable structure (the "document" end of the spectrum), and it's better for many transformation tasks.
	www.stylusstudio.com /michael_kay.html (2968 words)

	PRESS RELEASE Stylus Studio 5 XML IDE Adds Industry Leading Saxon XQuery Processor Support for Seamless XQuery ... (Site not responding. Last check: 2007-10-12)
		Saxon has always been designed for integration into such environments, and Stylus Studio has always been designed to allow components like Saxon to be seamlessly embedded, so there is a natural fit.
		Kay is the author of "XSLT Programmer's Reference" from Wrox Press, which is generally viewed as the definitive reference on XSLT, and the editor of the W3C's XSLT 2.0 specification, currently a "Last Call" Working Draft.
		Saxon was first released as an open source product in 1998, and has consistently maintained technology leadership and market share.
	www.marketwire.com /mw/release_html_b1?release_id=70265 (1163 words)

	Saxon - Wikipedia, the free encyclopedia
		Old Saxon, the ancestor language of modern Low German
		Saxon (album), the debut album by the heavy metal band of the same name
		This is a disambiguation page: a list of articles associated with the same title.
	en.wikipedia.org /wiki/Saxon (104 words)

	PerfectXML.com: Learn to use XML in your applications
		XSLT and CSS can be infact used together, for example, XSLT to convert XML to HTML and then CSS to present the HTML in the browser and separate the presentation details in a separate CSS stylesheet.
		SAXON in this case reports a "recoverable error" message and then chooses the template that occurs last in the stylesheet; on the other hand, MSXML and.NET also chooses the template that occurs last in the stylesheet, but does not show any errors or warnings.
		The XSLT 2.0 Working Draft removes the result tree fragment type and the temporary trees, which is a true node-set, can be constructed using xslt:variable, xslt:param, xslt:with-param, or xslt:result elements.
	www.perfectxml.com /TipsXSLT.asp (4456 words)

	Signs on the Sand: XSLT and XPath Optimization
		In this paper Michael reveals details of the XSLT and XPath optimizations performed internally by SAXON (XSLT and XQuery processor): This paper describes the main techniques used by the...
		Constant sub-expressions are surprisingly common in XSLT, because global variables often have a constant value; and it is often possible to get rid of large chunks of stylesheet code by pre-evaluating a condition such as .
		As I deal with large XSLT transformations it was easy to note that.NET XSLT does loop over all templates in priority order to find appropriate template and MSXML does some optimizations to index similiar match with similiar structure (the same attribute checked for different values) or just match for element name.
	www.tkachenko.com /blog/archives/000238.html (982 words)

	The SAXON XSLT and XQuery Processor
		Saxon 8.7 is the first release to be released simultaneously by Saxonica on the Java and.NET platforms.
		Saxon comes in two packages: Saxon-B implements the "basic" conformance level for XSLT 2.0 and XQuery, while Saxon-SA is a schema-aware XSLT and XQuery processor.
		Saxon 6.5.4 dropped support for certain rarely-used features of Saxon 6.5.3, notably support for JDK 1.1 and the Microsoft Java VM, support for FOP integration, and the applet interface.
	saxon.sourceforge.net (1058 words)

	Search Results for 'Saxon' (Site not responding. Last check: 2007-10-12)
		East Frisian Low Saxon, as a member of the Low Saxon language family is a dialect spoken in the Eastern Friesland peninsula of northwestern Lower Saxony.
		There are several dialects in Eastern Friesland Low Saxon: Standard East Frisian Low Saxon north of Leer, east of the river Ems and Brookmer Platt in the Brookmerland and Aurich (Auerk) area andRheiderländer Platt west of the river Ems around the city of Weener East Frisian Low Saxon differs fro...
		The Count of the Saxon Shore or comes litoris Saxonici was a military command of the later Roman Empire.
	www.worldhistory.com /wiki/S/Saxon.htm (1254 words)

	Installing an XSLT processor
		Saxon is a Java-based XSLT processor that is well respected for its adherence to the XSLT standard.
		Saxon is distributed as a zip file, so you need to unzip it into some suitable location.
		Saxon is a Java application that is executed from a command line.
	www.sagehill.net /docbookxsl/InstallingAProcessor.html (3096 words)

	[No title]
		Hello: The SAXON XSLT processor has an extremely useful proprietary extension "saxon:evaluate(string)" Here is the doc: The supplied string must contain an XPath expression.
		If there were an EXSLT evaluate function, I could code my XSLT transformer to use it, and then simply "roll my own" when using a processor that did not support it natively.
		These are currently: - 4XSLT - Saxon - libxslt (though that's not runnable from the command line, as far as I know) A couple of processors support xsl:script from XSLT 1.1, which enables you to define your own functions in java or javascript.
	lists.fourthought.com /pipermail/exslt/2001-November.txt (7184 words)

	Up-conversion using XSLT 2.0
		XSLT 2.0 provides a wide range of new features, many of which make light work of tasks that are notoriously difficult in XSLT 1.0, such as grouping and string manipulation.
		XSLT 2.0 will also be able to handle many situations where the structure is implicit in the text, or in markup designed for presentation purposes rather than to capture the information semantics.
		XSLT 1.0 has been much criticized for its rather primitive text-handling capabilities: the function library provided for string handling in XPath 1.0 is designed very much on "reduced instruction set computing" principles - you can achieve pretty well anything, but the complexity of the programming needed even for some quite simple tasks can be daunting.
	www.idealliance.org /proceedings/xml04/papers/111/mhk-paper.html (5186 words)

	XSLT Transformations > Using XSLT Stylesheets (Site not responding. Last check: 2007-10-12)
		He shows you the full XSLT syntax - from the most basic to the most advanced - and digs into many of the ways XSLT is used today.
		To illustrate how to make XSLT transformation happen, I'll be using an XML document called planets.xml that stores data about the planets Mercury, Venus, and Earth, such as their mass, length of their day, density, distance from the sun, and so on.
		The XSLT stylesheet I'll be using to transform planets.xml is called planets.xsl, and is shown in Listing 1.
	www.informit.com /articles/article.asp?p=21845&seqNum=3 (554 words)

	Saxon XSLT - Wikipedia, the free encyclopedia
		Saxon is an open-source Java XSLT and XQuery processor created by Michael Kay.
		Saxon 6 is the original product line and is no longer under development.
		Since version 8, Saxon has been available as
	en.wikipedia.org /wiki/Saxon_XSLT (70 words)

	Instant SAXON (Site not responding. Last check: 2007-10-12)
		This is no longer true; in fact, Saxon runs up to three times faster using Sun's JDK 1.3 Java VM than it does with the Microsoft Java VM.
		The XSLT processor is a complete implementation of the W3C XSLT 1.0 specification from the World Wide Web Consortium, found at http://www.w3.org/TR/1999/REC-xslt-19991116 (including the associated XPath syntax) with a number of powerful extensions
		Indicates the policy for handling recoverable errors in the stylesheet: w0 means recover silently, w1 means recover after writing a warning message to the system error output, w2 means signal the error and do not attempt recovery.
	users.breathe.com /mhkay/saxon/saxon6.2.2/instant.html (1177 words)

	XML.com: An Interview with Michael Kay
		His Java-based Saxon XSLT processor is one of the most successful and popular XSLT processors in the language's history.
		The branch of Saxon supporting XSLT 1.0 is currently at release 6.5.3, and regular readers of this column will know that the 7.x branch of Saxon has been implementing more and more support for XSLT 2.0.
		The impression I get is that a lot of people are using Saxon 7.x extensively for the second kind of production workload, but that most people with the first kind of environment are (quite rightly) sticking to Saxon 6.x (and XSLT 1.0) for the time being.
	www.xml.com /pub/a/2004/07/07/tr.html (1543 words)

	java.net: Extensible Code Generation with Java, Part 2
		We introduced a workflow in which an XML document was used to describe desired classes, whose source was then generated with XSLT, via the Saxon XSLT processor.
		You could argue that mixing the safe-zone code into the model is blasphemy, and in the case of XSLT you can have it read from more than one data source.
		I do think the article provides a unique perspective on using a templating language (XSLT) which is often used as a strictly output only mechanism as part of a circular code generation workflow.
	today.java.net /pub/a/today/2004/05/31/generation-pt2.html (1873 words)

	Microsoft XML Team's WebLog : XSLT planning
		Given that XSLT 2.0 has a lot more to offer than 1.0, and that compared to XQuery 1.0 is more applicable in the transformation area, it would seem to me logical that there should simply be XSLT 2.0 support, yes.
		If MS doesn't support XSLT 2.0, it will either fail to gain the industry permeation that will make it a safe choice, or the road to acceptance will be slower and more grueling.
		XSLT itself has no mem/perf problem for me, but XMLDiffView, when comparing two 250 KB docs, has the problem :-), but this is out of core.
	blogs.msdn.com /xmlteam/archive/2005/06/07/426511.aspx (3129 words)

	Fawcette.com - Why XSLT 2.0 Will Be Cool (Site not responding. Last check: 2007-10-12)
		XSLT 2.0 deserves the hype it receives, and so does the man working on the draft specification.
		He should know a little bit about XSLT implementations, having written and shepherded the Java-based Saxon XSLT parser through seven versions and any number of different platforms.
		Saxon 7.2, his latest magnum opus, is significant because it's designed as a reference implementation for XSLT 2.0 and XPath 2.0, along with a subset of the XML Query Language.
	www.fawcette.com /xmlmag/2002_09/online/xml_kcagle_09_09_02 (430 words)

	[No title]
		In the five years that Saxon has been available, it has established a reputation for fast performance, the highest level of conformance to the W3C specifications, excellent diagnostics, technical innovation, and responsive technical support direct from the original developer.
		Saxon is written in 100% Java and therefore runs on any popular platform.
		Saxon is the only product to offer XSLT and XQuery in an integrated package, allowing you to use each language for the things it does best.
	www.stylusstudio.com /saxon_xquery_processor.html (619 words)

	Resources
		Zvon.org has a tutorial introduction to XSLT with many examples and a funky multi-frame interface that lets you try out examples.
		XSLT, because of its original purpose as a transformation engine for formatting, has a one input, one output structure.
		Extensions to XSLT to allow multiple output files are quite popular, and are likely to be standardized.
	www.cs.brown.edu /courses/cs196-9/resources.html (591 words)

	Cafe con Leche XML News and Resources
		The porting of Saxon to.NET was pioneered by M. David Peterson, Pieter Siegers Kort, and others, and the process has now been brought in-house within Saxonica.
		Saxon 8.7 on.NET goes beyond previous Saxon.NET releases by providing greater integration with the.NET platform: in particular the System.Xml parser and utilities.
		Saxon is published in two versions for both of which Java 1.4 or later (or.NET) is required.
	www.ibiblio.org /xml (1927 words)

	Cover Pages: Software - Extensible Stylesheet Language (XSL)
		The stylesheets have been tested with the XT, Saxon, Xalan and Oracle XSLT processors; the last of these does not support multiple file output, which means that you cannot use the 'split' feature of the stylesheets to make multiple HTML files from one XML file.
		If you have not yet installed an XSLT processor, it is probably sensible to pick James Clark's XT, as it appears to be the fastest and most robust." Sebastian writes: "The TEI stylesheets have many small improvements, but remain ongoing work.
		However, SAXON was written explicitly to do things that are beyond the scope of the XSL standard: in particular: (1) It allows XSL processing and Java processing to be freely mixed, so you can always escape into procedural code to do something non-standard -- such as accessing a database; (2) It allows multiple output files.
	www.oasis-open.org /cover/xslSoftware.html (14876 words)

	Module extra from libxslt (Site not responding. Last check: 2007-10-12)
		implement some extension outside the XSLT namespace but not EXSLT with is in a different library.
		This is Michael Kay's Saxon processor namespace for extensions.
		Implement the node-set() XSLT function node-set node-set(result-tree) This function is available in libxslt, saxon or xt namespace.
	www.math.temple.edu /doc/packages/libxslt/html/libxslt-extra.html (69 words)

	Creating Some XPath 2.0 Examples
		Saxon is written in Java, so you'll need to have Java installed on your computer as well.
		Saxon supports a good deal of XSLT 2.0 as well as XPath 2.0, which is handy for use because we'll be able to put XPath 2.0 to work in XSLT 2.0 examples.
		Although this is not a book on XSLT 2.0, and although XSLT 2.0 is still in flux, we'll put Saxon to work here to show off some of the new power available in XSLT 2.0.
	www.developer.com /xml/article.php/3351251 (1132 words)

	Cover Pages: Experimental SAXON XSLT Processor Version 7.0 Supports New XSLT 2.0 and XPath 2.0 Specifications.
		The Saxon package is "a collection of tools for processing XML documents, including (a) an XSLT processor; (b) a Java library, which supports a similar processing model to XSL but allows full programming capability, which you need if you want to perform complex processing; (c) a slightly improved version of the Ælfred parser from Microstar.
		Saxon implements the XSLT 1.0 recommendation, including XPath 1.0, in its entirety; version 7.0 also implements many features defined in the XSLT 2.0 and XPath 2.0 working drafts, in particular: (1) Support for multiple output files using
		Note from Michael Kay: "[Saxon version 7.0 is] intended to allow familiarisation with the new features, and to gain feedback.
	xml.coverpages.org /ni2001-12-20-c.html (287 words)

	About SAXON (Site not responding. Last check: 2007-10-12)
		For a list of known bugs in Saxon 5.5.1, consult the Saxon 6.3 change log, which gives details of all bugs fixed in subsequent releases.
		For a list of known bugs in Instant Saxon 5.5.1, consult the Saxon 6.3 change log, which gives details of all bugs fixed in subsequent releases.
		For a list of known bugs in Saxon 6.2.2, consult the Saxon 6.3 change log, which gives details of all bugs fixed in Saxon 6.3.
	users.breathe.com /mhkay/saxon (581 words)

Try your search on: Qwika (all wikis)