debian/0000755000000000000000000000000012216320467007171 5ustar debian/libsaxonb-java-doc.doc-base0000644000000000000000000000053210752425734014241 0ustar Document: libsaxon8-java Title: Saxon XSLT Processor Documentation Author: Michael H. Kay Abstract: This manual describes what saxon is and how it can be used with XSL stylesheets. A nice XSLT reference is included. Section:Text Format: HTML Index: /usr/share/doc/libsaxon8-java-doc/api/index.html Files: /usr/share/doc/libsaxon8-java-doc/api/* debian/control0000644000000000000000000000251012216317715010574 0ustar Source: saxonb Section: java Priority: optional Maintainer: Debian Java Maintainers Uploaders: Rene Engelhard , Eugene Zhukov Build-Depends: debhelper (>= 7), cdbs, default-jdk, ant (>= 1.7), maven-repo-helper Build-Depends-Indep: libdom4j-java, libjdom1-java, libxom-java Standards-Version: 3.9.4 Homepage: http://saxon.sourceforge.net/ Vcs-Svn: svn://anonscm.debian.org/pkg-java/trunk/saxonb Vcs-Browser: http://anonscm.debian.org/viewvc/pkg-java/trunk/saxonb/ Package: libsaxonb-java Architecture: all Depends: libdom4j-java, libjdom1-java, libxom-java, ${misc:Depends} Suggests: libsaxonb-java-doc Description: Saxon-B XSLT Processor The saxon package is a collection of tools for processing XML documents and implements XSLT 2.0, XPath 2.0, and XQuery 1.0. . Saxon is known to work well for processing DocBook XML documents with the DocBook XSL Stylesheets. Related packages make the process straightforward. Package: libsaxonb-java-doc Section: doc Architecture: all Depends: ${misc:Depends} Description: Saxon-B XSLT Processor's documentation and javadoc The saxon package is a collection of tools for processing XML documents and implements XSLT 2.0, XPath 2.0, and XQuery 1.0. . This package contains the documentation and javadoc for Saxon. debian/compat0000644000000000000000000000000211257210024010356 0ustar 7 debian/saxonb.pom0000644000000000000000000001316012127005333011172 0ustar 4.0.0 net.sourceforge.saxon saxon 9.1.0.8 jar SaxonB http://saxon.sourceforge.net/ sourceforge http://www.sourceforge.net Saxon a complete and conformant implementation of the XSLT 2.0, XQuery 1.0, and XPath 2.0 Recommendations published on 23 January 2007 by W3C Mozilla Public License Version 1.0 http://www.mozilla.org/MPL/MPL-1.0.txt See http://saxon.sourceforge.net for other notices files scm:svn:http://saxon.svn.sourceforge.net/viewvc/saxon/tags/9.1.0.8 scm:svn:http://saxon.svn.sourceforge.net/viewvc/saxon/tags/9.1.0.8 http://saxon.svn.sourceforge.net/viewvc/saxon/tags/9.1.0.8 build-maven-upload-bundle package org.codehaus.mojo truezip-maven-plugin 1.0-beta-4 extract-javadoc-from-resource-bundle generate-sources copy ${basedir}/saxon-resources9-1-0-1.zip/doc/javadoc ${project.build.directory}/upload/${project.artifactId}-${project.version}-javadoc.jar org.apache.maven.plugins maven-antrun-plugin 1.2 copy-main-jars-to-staging-directory package run debian/scripts/0000755000000000000000000000000012216320467010660 5ustar debian/scripts/saxonb-xslt0000644000000000000000000000012710755374270013074 0ustar #!/bin/sh exec java -classpath /usr/share/java/saxonb.jar net.sf.saxon.Transform "$@" debian/scripts/saxonb-xquery0000644000000000000000000000012310755374270013433 0ustar #!/bin/sh exec java -classpath /usr/share/java/saxonb.jar net.sf.saxon.Query "$@" debian/patches/0000755000000000000000000000000012216320467010620 5ustar debian/patches/0001-disable-dotnet-support.patch0000644000000000000000000000311011626674571016636 0ustar From: Debian Java Maintainers Date: Mon, 29 Aug 2011 11:21:08 +0200 Subject: [PATCH] disable dotnet support --- bj/net/sf/saxon/Configuration.java | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/bj/net/sf/saxon/Configuration.java b/bj/net/sf/saxon/Configuration.java index b95f98d..4ecb53a 100644 --- a/bj/net/sf/saxon/Configuration.java +++ b/bj/net/sf/saxon/Configuration.java @@ -1,6 +1,6 @@ package net.sf.saxon; -/*DOTNETONLY*/ import net.sf.saxon.dotnet.DotNetPlatform; +/*DOTNETONLY*/ //import net.sf.saxon.dotnet.DotNetPlatform; import net.sf.saxon.event.*; import net.sf.saxon.evpull.PullEventSource; @@ -249,7 +249,7 @@ public class Configuration implements Serializable, SourceResolver { /*DOTNETONLY*/ /*JAVAONLY*/ if (System.getProperty("java.vendor").equals("Jeroen Frijters")) { //System.err.println("Call to create .NET platform currently disabled in Configuration.java (needed for JDK1.4)"); - /*DOTNETONLY*/ platform = DotNetPlatform.getInstance(); + /*DOTNETONLY*/ //platform = DotNetPlatform.getInstance(); /*DOTNETONLY*/ /*JAVAONLY*/ } // System.err.println(System.getProperty("java.vendor")); // System.err.println(platform.getClass().getName()); @@ -3540,4 +3540,4 @@ public class Configuration implements Serializable, SourceResolver { // Portions created by (your name) are Copyright (C) (your legal entity). All Rights Reserved. // // Contributor(s): none. -// \ No newline at end of file +// -- debian/patches/0002-disable-external-method-invocation.patch0000644000000000000000000000167211626674571021112 0ustar From: Debian Java Maintainers Date: Mon, 29 Aug 2011 11:21:08 +0200 Subject: [PATCH] disable external method invocation --- bj/net/sf/saxon/Configuration.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/bj/net/sf/saxon/Configuration.java b/bj/net/sf/saxon/Configuration.java index 4ecb53a..1ee5c5d 100644 --- a/bj/net/sf/saxon/Configuration.java +++ b/bj/net/sf/saxon/Configuration.java @@ -130,7 +130,7 @@ public class Configuration implements Serializable, SourceResolver { private transient OutputURIResolver outputURIResolver; private boolean timing = false; private boolean versionWarning = false; - private boolean allowExternalFunctions = true; + private boolean allowExternalFunctions = false; private boolean traceExternalFunctions = false; private boolean validation = false; private boolean allNodesUntyped = false; -- debian/patches/0003-disable-proprietary-saxon.patch0000644000000000000000000000513311626674571017346 0ustar From: Debian Java Maintainers Date: Mon, 29 Aug 2011 11:21:08 +0200 Subject: [PATCH] disable proprietary saxon --- bj/net/sf/saxon/ant/AntTransform.java | 12 ++++++------ bj/net/sf/saxon/s9api/SchemaManager.java | 13 ++----------- 2 files changed, 8 insertions(+), 17 deletions(-) diff --git a/bj/net/sf/saxon/ant/AntTransform.java b/bj/net/sf/saxon/ant/AntTransform.java index 5fba972..38db268 100644 --- a/bj/net/sf/saxon/ant/AntTransform.java +++ b/bj/net/sf/saxon/ant/AntTransform.java @@ -325,13 +325,13 @@ public class AntTransform extends MatchingTask implements XSLTLogger { public void execute() throws BuildException { log("AntTransform.execute() schema-aware=" + schemaAware + " version " + Version.getProductVersion()); - if (schemaAware) { - // remove this line to compile the code for use under Saxon-B only - config = Configuration.makeSchemaAwareConfiguration(null, null); - config.displayLicenseMessage(); - } else { +// if (schemaAware) { +// // remove this line to compile the code for use under Saxon-B only +// config = Configuration.makeSchemaAwareConfiguration(null, null); +// config.displayLicenseMessage(); +// } else { config = new Configuration(); - } +// } config.setAllowExternalFunctions(allowExtensions); config.setExpandAttributeDefaults(expandAttributeDefaults); diff --git a/bj/net/sf/saxon/s9api/SchemaManager.java b/bj/net/sf/saxon/s9api/SchemaManager.java index 9ab0b13..e62f5b8 100644 --- a/bj/net/sf/saxon/s9api/SchemaManager.java +++ b/bj/net/sf/saxon/s9api/SchemaManager.java @@ -96,11 +96,7 @@ public class SchemaManager { */ public void importComponents(Source source) throws SaxonApiException { - try { - config.importComponents(source); - } catch (XPathException err) { - throw new SaxonApiException(err); - } + throw new SaxonApiException("proprietary schema support disabled in this version"); } /** @@ -111,12 +107,7 @@ public class SchemaManager { */ public void exportComponents(Destination destination) throws SaxonApiException { - try { - Receiver out = destination.getReceiver(config); - config.exportComponents(out); - } catch (XPathException e) { - throw new SaxonApiException(e); - } + throw new SaxonApiException("proprietary schema support disabled in this version"); } -- debian/patches/series0000644000000000000000000000016511626657466012057 0ustar 0001-disable-dotnet-support.patch 0002-disable-external-method-invocation.patch 0003-disable-proprietary-saxon.patch debian/changelog0000644000000000000000000000626112216320422011037 0ustar saxonb (9.1.0.8+dfsg-1) unstable; urgency=low * Non-free upstream source removed, dfsg suffix added (Closes: #721925) * README.source with explanations added * Addressed file duplication issue * Removed obsolete d/README.Debian-source * Fixed typo in saxonb-xquery manpage * Canonicalized URLs for the Vcs-* fields in d/control -- Eugene Zhukov Wed, 18 Sep 2013 07:50:04 +0000 saxonb (9.1.0.8-3) unstable; urgency=low [ Eugene Zhukov ] * Fix classpath generation [ Mathieu Malaterre ] * Team upload. * Upload to sid * Remove article from Description (lintian) -- Mathieu Malaterre Wed, 15 May 2013 13:48:26 +0200 saxonb (9.1.0.8-2) experimental; urgency=low [ Eugene Zhukov ] * Adds /usr/share/maven-repo entry with relevant symbolic links * Standards-Version updated from 3.9.1 to 3.9.4, no changes needed [ Mathieu Malaterre ] * Team upload. * Remove Michael Koch from Uploaders. Closes: #654131 -- Mathieu Malaterre Wed, 03 Apr 2013 09:37:37 +0200 saxonb (9.1.0.8-1) unstable; urgency=low * Team upload. * Newer but not newest upstream release. (Closes: #576467, #599413) * Switch to source format 3.0. * Update debian/watch to look into subversions tags directory. But there are even newer versions than tags. * Remove Java runtime from Depends. * Update Standards-Version: 3.9.1. -- Torsten Werner Mon, 29 Aug 2011 13:34:44 +0200 saxonb (9.0.0.4+svn20080322-3) unstable; urgency=low [ Chris Cheney ] * (Build-)Depends on default-jdk (Closes: #508978). * Add missing Depends ${misc:Depends}. * Updated Standards-Version to 3.8.0.0. [ Michael Koch ] * Build-Depends on debhelper (>= 7). * Maved packaged to section 'java'. * Updated Standards-Version to 3.8.3. -- Michael Koch Fri, 25 Sep 2009 20:40:25 +0200 saxonb (9.0.0.4+svn20080322-2) unstable; urgency=low * add missing t in Depends: (closes: #495403) * fix -dom4j symlink (closes: #490767) * point to Apache 2.0 license instead of including a full copy in debian/copyright, thanks lintian -- Rene Engelhard Mon, 25 Aug 2008 01:21:53 +0200 saxonb (9.0.0.4+svn20080322-1) unstable; urgency=low * New upstream version. -- Michael Koch Sat, 05 Apr 2008 22:20:02 +0200 saxonb (9.0-3) unstable; urgency=low * Disabled external method invocation by default, as it is insecure. See README.Debian how to enable this if needed. Closes: #465885. Thanks to Stefano Zacchiroli for the patch. * Added helpers to call XSLT and XQuery processors and documentation about them in README.Debian. Closes: #465894. * Added manpages for saxonb-xquery and saxonb-xslt. * Added watch file. -- Michael Koch Sat, 16 Feb 2008 21:05:34 +0100 saxonb (9.0-2) unstable; urgency=low * Add libxom-java to (Build-)Depends. Closes: #464286 * Add Vcs-Svn and Vcs-Browse fields to control file. -- Michael Koch Wed, 06 Feb 2008 23:10:58 +0100 saxonb (9.0-1) unstable; urgency=low * Initial version. Closes: #350338, #408842. -- Michael Koch Tue, 18 Dec 2007 00:09:18 +0100 debian/saxonb/0000755000000000000000000000000012216320467010463 5ustar debian/saxonb/META-INF/0000755000000000000000000000000012216320467011623 5ustar debian/saxonb/META-INF/service/0000755000000000000000000000000012216320467013263 5ustar debian/saxonb/META-INF/service/javax.xml.transform.TransformerFactory0000644000000000000000000000004410752425734022765 0ustar net.sf.saxon.TransformerFactoryImpl debian/libsaxonb-java.manpages0000644000000000000000000000007610755631615013617 0ustar debian/manpages/saxonb-xquery.1 debian/manpages/saxonb-xslt.1 debian/rules0000755000000000000000000000452112216317715010255 0ustar #!/usr/bin/make -f #export DH_VERBOSE=1 include /usr/share/cdbs/1/class/ant.mk include /usr/share/cdbs/1/rules/debhelper.mk VERSION := $(DEB_UPSTREAM_VERSION) JAVA_HOME := /usr/lib/jvm/default-java ANT_HOME := /usr/share/ant DEB_JARS := dom4j jdom1 xom DEB_ANT_ARGS := -Dupstream-version=$(DEB_UPSTREAM_VERSION) DEB_ANT_BUILDFILE := $(CURDIR)/debian/build.xml DEB_ANT_BUILD_TARGET := jar javadoc DEB_BUILDDIR := bj install/libsaxonb-java:: install -m 644 -D dist/saxonb-ant-$(VERSION).jar debian/libsaxonb-java/usr/share/java/saxonb-ant-$(VERSION).jar install -m 644 -D dist/saxonb-dom4j-$(VERSION).jar debian/libsaxonb-java/usr/share/java/saxonb-dom4j-$(VERSION).jar install -m 644 -D dist/saxonb-dom-$(VERSION).jar debian/libsaxonb-java/usr/share/java/saxonb-dom-$(VERSION).jar install -m 644 -D dist/saxonb-jdom-$(VERSION).jar debian/libsaxonb-java/usr/share/java/saxonb-jdom-$(VERSION).jar install -m 644 -D dist/saxonb-sql-$(VERSION).jar debian/libsaxonb-java/usr/share/java/saxonb-sql-$(VERSION).jar install -m 644 -D dist/saxonb-xom-$(VERSION).jar debian/libsaxonb-java/usr/share/java/saxonb-xom-$(VERSION).jar install -m 644 -D dist/saxonb-xpath-$(VERSION).jar debian/libsaxonb-java/usr/share/java/saxonb-xpath-$(VERSION).jar dh_link -p libsaxonb-java /usr/share/java/saxonb-ant-$(VERSION).jar /usr/share/java/saxonb-ant.jar dh_link -p libsaxonb-java /usr/share/java/saxonb-dom4j-$(VERSION).jar /usr/share/java/saxonb-dom4j.jar dh_link -p libsaxonb-java /usr/share/java/saxonb-dom-$(VERSION).jar /usr/share/java/saxonb-dom.jar dh_link -p libsaxonb-java /usr/share/java/saxonb-jdom-$(VERSION).jar /usr/share/java/saxonb-jdom.jar dh_link -p libsaxonb-java /usr/share/java/saxonb-sql-$(VERSION).jar /usr/share/java/saxonb-spl.jar dh_link -p libsaxonb-java /usr/share/java/saxonb-xom-$(VERSION).jar /usr/share/java/saxonb-xom.jar dh_link -p libsaxonb-java /usr/share/java/saxonb-xpath-$(VERSION).jar /usr/share/java/saxonb-xpath.jar mh_installpoms -plibsaxonb-java mh_installjar -l -nsaxonb -plibsaxonb-java debian/saxonb.pom dist/saxonb-$(VERSION).jar clean:: mh_clean VERSION_DFSG := $(shell echo $(VERSION) | sed 's/+dfsg//') get-orig-source: uscan --download-version $(VERSION_DFSG) --force-download get-orig-pom: wget -O debian/saxonb.pom -U NoAgent-1.0 \ http://repo1.maven.org/maven2/net/sourceforge/saxon/saxon/$(VERSION)/saxon-$(VERSION).pom debian/manpages/0000755000000000000000000000000012216320467010764 5ustar debian/manpages/saxonb-parameters.ent0000644000000000000000000000225710755631615015143 0ustar Parameters At the end of the command line, a list of parameters can be given. Parameters are passed using the syntax NAME=VALUE, to specify parameters' names and values. A parameter name prefixed with "+" (plus sign) will be interpreted as a filesystem path parameter If the path points to a single file, that file will be parsed as XML and its document node will be passed as the parameter value. If the path points to a directory, all directly contained files will be parsed as XML files, and the sequence of their document nodes will be passed as the parameter value. A parameter name prefixed with "!" (exclamation mark) will be interpted as a output/serialization parameter. See the specifications of XQuery and XSLT 2.0 for more information on output/serialization parameters. To pass parameters belonging to the non-null namespace, the syntax {uri}localname=value is provided. debian/manpages/saxonb-xslt.10000644000000000000000000002537110755631615013346 0ustar .\" Title: saxonb-xslt .\" Author: .\" Generator: DocBook XSL Stylesheets v1.73.2 .\" Date: February 2008 .\" Manual: .\" Source: .\" .TH "SAXONB\-XSLT" "1" "February 2008" "" "" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .SH "NAME" saxonb-xslt - command line XSLT 2.0 processor .SH "SYNOPSIS" .HP 12 \fBsaxonb\-xslt\fR [\fIOPTION\fR...] [\fB\-s:\fR\fB\fISOURCEFILE\fR\fR] [\fB\-xsl:\fR\fB\fISTYLESHEET\fR\fR] [\fB\-o:\fR\fB\fIOUTPUT\fR\fR] [\fINAME\fR=\fIVALUE\fR...] .SH "DESCRIPTION" .PP This manual page documents briefly the \fBsaxonb\-xslt\fR command\. This page was written for the Debian(TM) distribution because the original program does not have a manual page\. Instead, it has HTML documentation which is shipped in the libsaxonb\-java\-doc package\. .PP \fBsaxonb\-xslt\fR is a command line wrapper around the Saxon\-B XSLT and XQuery processor\. Using \fBsaxonb\-xslt\fR you can process XML documents with \fIXSLT 2\.0\fR stylesheets directly from the command line\. Internally, \fBsaxonb\-xslt\fR is a wrapper around the Java class \fBnet\.sf\.saxon\.Transform\fR implemented by Saxon\-B\. .PP \fBsaxonb\-xslt\fR is usually invoked passing the 3 options made explicit in the above synopsis\. Usually, those options correspond respectively to the input XML file to be transformed, the XSLT stylesheet describing the desired transformation, and the output file where to save the result\. However, the meaning and the need of passing them is affected by a number of other options that can be specified\. See the option reference below for more information\. .SS "Parameters" .PP At the end of the command line, a list of \fIparameters\fR can be given\. Parameters are passed using the syntax \fINAME\fR=\fIVALUE\fR, to specify parameters\' names and values\. .PP A parameter name prefixed with "+" (plus sign) will be interpreted as a \fIfilesystem path parameter\fR If the path points to a single file, that file will be parsed as XML and its document node will be passed as the parameter value\. If the path points to a directory, all directly contained files will be parsed as XML files, and the sequence of their document nodes will be passed as the parameter value\. .PP A parameter name prefixed with "!" (exclamation mark) will be interpted as a output/serialization parameter\. See the specifications of XQuery and XSLT 2\.0 for more information on output/serialization parameters\. .PP To pass parameters belonging to the non\-null namespace, the syntax {\fIuri\fR}\fIlocalname\fR=\fIvalue\fR is provided\. .PP Parameters will be visible as global variables during XSLT processing, provided they have been declared with \. evaluation, provided they have been declared in the query prolog\. See the XSLT specification for more information on variables and their declarations\. .SH "OPTIONS" .PP A summary of supported options is included below\. Options can be passed in any order\. .PP We first report the options which are shared by \fBsaxonb\-xslt\fR and \fBsaxonb\-xquery\fR, then those specific to \fBsaxonb\-xslt\fR (or which have a different semantics)\. .PP Some options are flagged as "Saxon\-SA only", such options work only if Saxon\-SA is installed\. Note that Saxon\-SA is a commercial product, as such it is not available in Debian\. .SS "Common options" .PP \fB\-cr\fR:\fIclassname\fR .RS 4 Specify a class to be used for processing collection URIs passed to the \fBcollection()\fR function\. The class must implement net\.sf\.saxon\.CollectionURIResolver\. .RE .PP \fB\-dtd\fR: {[on] | [off]} .RS 4 Enable or disable DTD validation\. Default: off\. .RE .PP \fB\-expand\fR: {[on] | [off]} .RS 4 When validation is enabled, expand default values in validated documents\. This option enables or disables such an expansion\. Default: on\. .RE .PP \fB\-explain\fR [:\fIfilename\fR] .RS 4 Display an execution plan; the output is in XML format\. If filename is not given it will be displayed on standard output\. .RE .PP \fB\-ext\fR: {[on] | [off]} .RS 4 Enable or disable the ability to invoke external Java functions from query files and stylesheets\. Beware that enabling them is a potential security risk when processing untrusted files\. Default: off\. .RE .PP \fB\-l\fR: {[on] | [off]} .RS 4 Keep (when on) or throw away (when off) line numbers in tress corresponding to source documents\. When kept, line numbers can be accessed using the function \fBsaxon:line\-number()\fR\. Default: off\. .RE .PP \fB\-outval\fR: {[recover] | [fatal]} .RS 4 When validation is required, set whether validation errors are fatal (when "fatal" is passed) or if they only trigger warnings (when "recover" is)\. Default: fatal\. .RE .PP \fB\-p\fR: {[on] | [off]} .RS 4 Enable or disable usage of the PTreeURIResolver\. Saxon\-SA only\. .RE .PP \fB\-r\fR:\fIclassname\fR .RS 4 Specify a class to be used for resolving all URIs\. .RE .PP \fB\-repeat\fR:\fIN\fR .RS 4 Repeat the transformation N times\. For benchmarking purposes\. .RE .PP \fB\-sa\fR .RS 4 Perform Schema\-aware processing\. Saxon\-SA only\. .RE .PP \fB\-strip\fR: {[all] | [none] | [ignorable]} .RS 4 Specify whitespace stripping policy for source documents: strip all of them ("all"), strip none of them ("none"), strip ignorable whitespace only ("ignorable")\. Default: none\. .RE .PP \fB\-t\fR .RS 4 Display version, timing, and other debugging information on standard error\. .RE .PP \fB\-tree\fR: {[tiny] | [linked]} .RS 4 Select the implementation of the internal tree model: tiny tree model ("tiny") or linked tree model ("linked")\. See the Saxon documentation for more information on the internal tree model\. Default: tiny\. .RE .PP \fB\-T\fR [:\fIclassname\fR] .RS 4 Trace various aspect of the processing; an optional class name can be given to specify a user\-chosen tracer\. The class must implement net\.sf\.saxon\.trace\.TraceListener\. The default is a system supplied tracer\. This option implies \fB\-l\fR\. .RE .PP \fB\-TJ\fR .RS 4 Enable tracing of external Java method invocation\. See \fB\-ext\fR\. .RE .PP \fB\-u\fR .RS 4 Force interpretation of source document names as URI\. By default they are considered to be file names, unless they start with "file:" or "http:"\. .RE .PP \fB\-val\fR: {[strict] | [lax]} .RS 4 When validation is enabled, choose among "strict" or "lax" validation\. Saxon\-SA only\. .RE .PP \fB\-x\fR:\fIclassname\fR .RS 4 Specify a class to be used as SAX parser for input documents\. The class must implement either org\.xml\.sax\.Parser or org\.xml\.sax\.XMLReader\. .RE .PP \fB\-xi\fR .RS 4 Apply XInclude processing to all input documents\. .RE .PP \fB\-xmlversion\fR: {[1\.0] | [1\.1]} .RS 4 Choose the XML version for processing input documents\. "1\.1" must be specified to process XML 1\.1 and Namespaces 1\.1 constructs\. Default: 1\.0\. .RE .PP \fB\-?\fR .RS 4 Display a help message and exit\. .RE .SS "Options specific to saxonb\-xslt" .PP \fB\-a\fR .RS 4 Use the "" processing instruction from the source document to find the stylesheet to be used\. This option is not compatible with \fB\-xsl\fR\. .RE .PP \fB\-c\fR:\fIfilename\fR .RS 4 Use the compiled stylesheet stored in filename\. This option is not compatible with \fB\-xsl\fR\. .RE .PP \fB\-im\fR:\fImodename\fR .RS 4 Use modename as the initial mode used for the transformation\. Qualified modes can be specified as "{\fIuri\fR}\fIlocalname\fR"\. .RE .PP \fB\-it\fR:\fItemplatename\fR .RS 4 Use templatename as the initial named template for the transformation\. When this option is used, \fB\-xsl\fR is optional\. .RE .PP \fB\-m\fR:\fIclassname\fR .RS 4 Specify a class to be used as the receiver for messages generated by \. The class must implement net\.sf\.saxon\.event\.Receiver\. .RE .PP \fB\-o\fR:\fIpath\fR .RS 4 Specify the path to be used for saving generated output\. Usually path points to a filename where the main result document will be saved\. If not specified such a document will be written to standard output\. .sp Additional output documents generated using the command uses path as the basename for the "href" attribute of the command\. If \fB\-o\fR is missing they will be saved relatively to the current working directory\. .sp When \fB\-s\fR identifies a directory, also \fB\-o\fR should identify one\. All the output documents will then be written under such a directory\. .RE .PP \fB\-or\fR:\fIclassname\fR .RS 4 Specify a class to be used as the output resolver for the "href" attribute of \. The class must implement net\.sf\.saxon\.OutputURIResolver\. .RE .PP \fB\-s\fR:\fIpath\fR .RS 4 Specify the input file or directory\. This option is required unless \fB\-it\fR has been given\. If path points to a filename, that file will be parsed as an XML document and its document node will be the context item at the beginning of the transformation\. The special filename "\-" can be used to require reading the input document from standard input\. .sp If path points to a directory all files directly contained in it will be individually transformed\. In such a case \fB\-o\fR is required\. \fB\-u\fR affects the intepretation of path\. .RE .PP \fB\-versmsg\fR: {[on] | [off]} .RS 4 Enable or disable the warning about using an XSLT 2\.0 processor (which Saxon\-B is) on stylesheets which specify version="1\.0" in their root element\. Default: on\. .RE .PP \fB\-warnings\fR: {[silent] | [recover] | [fatal]} .RS 4 Set the policy for handling recoverable errors: "silent" for silent recovery, "recover" for recovery with warning output on standard error, "fatal" for no recovery\. Default: recover\. .RE .PP \fB\-xsl\fR:\fIfilename\fR .RS 4 Specify the main XSLT stylesheet to be used for the transformation\. This option is required unless \fB\-a\fR or \fB\-c\fR are specified\. The special filename "\-" can be used to require reading the sylesheet from standard input\. \fB\-u\fR affects the intepretation of filename\. .RE .PP \fB\-y\fR:\fIfilename\fR .RS 4 Specify a class to be used as SAX parser for stylesheets\. The class must implement either org\.xml\.sax\.Parser or org\.xml\.sax\.XMLReader\. See also \fB\-x\fR\. .RE .SH "SEE ALSO" .PP saxonb\-xquery (1), XSL Transformations (XSLT) Version 2\.0 (W3C Recommendation)\. .PP This program is fully documented by the HTML documentation of Saxon, available in the libsaxon\-java\-doc Debian package\. .SH "AUTHOR" .PP This manual page was written by Stefano Zacchiroli for the Debian(TM) system (but may be used by others)\. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation\. .PP On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common\-licenses/GPL\. .SH "COPYRIGHT" Copyright \(co 2008 Stefano Zacchiroli .br debian/manpages/saxonb-xslt.xml0000644000000000000000000002330210755631615013776 0ustar Stefano"> Zacchiroli"> February 2008"> 1"> zack@debian.org"> saxonb-xslt"> Debian"> GNU"> GPL"> ]>
&dhemail;
2008 &dhusername; &dhdate; &dhucpackage; &dhsection; &dhpackage; command line XSLT 2.0 processor &dhpackage; OPTION NAME=VALUE DESCRIPTION This manual page documents briefly the &dhpackage; command. This page was written for the &debian; distribution because the original program does not have a manual page. Instead, it has HTML documentation which is shipped in the libsaxonb-java-doc package. &dhpackage; is a command line wrapper around the Saxon-B XSLT and XQuery processor. Using &dhpackage; you can process XML documents with XSLT 2.0 stylesheets directly from the command line. Internally, &dhpackage; is a wrapper around the Java class net.sf.saxon.Transform implemented by Saxon-B. &dhpackage; is usually invoked passing the 3 options made explicit in the above synopsis. Usually, those options correspond respectively to the input XML file to be transformed, the XSLT stylesheet describing the desired transformation, and the output file where to save the result. However, the meaning and the need of passing them is affected by a number of other options that can be specified. See the option reference below for more information. ¶meters; Parameters will be visible as global variables during XSLT processing, provided they have been declared with <xsl:param>. evaluation, provided they have been declared in the query prolog. See the XSLT specification for more information on variables and their declarations. OPTIONS &common-options; Options specific to &dhpackage; Use the "<?xml-stylesheet ... ?>" processing instruction from the source document to find the stylesheet to be used. This option is not compatible with . :filename Use the compiled stylesheet stored in filename. This option is not compatible with . :modename Use modename as the initial mode used for the transformation. Qualified modes can be specified as "{uri}localname". :templatename Use templatename as the initial named template for the transformation. When this option is used, is optional. :classname Specify a class to be used as the receiver for messages generated by <xsl:message>. The class must implement net.sf.saxon.event.Receiver. :path Specify the path to be used for saving generated output. Usually path points to a filename where the main result document will be saved. If not specified such a document will be written to standard output. Additional output documents generated using the <xsl:result-document> command uses path as the basename for the "href" attribute of the command. If is missing they will be saved relatively to the current working directory. When identifies a directory, also should identify one. All the output documents will then be written under such a directory. :classname Specify a class to be used as the output resolver for the "href" attribute of <xsl:result-document>. The class must implement net.sf.saxon.OutputURIResolver. :path Specify the input file or directory. This option is required unless has been given. If path points to a filename, that file will be parsed as an XML document and its document node will be the context item at the beginning of the transformation. The special filename "-" can be used to require reading the input document from standard input. If path points to a directory all files directly contained in it will be individually transformed. In such a case is required. affects the intepretation of path. :onoff Enable or disable the warning about using an XSLT 2.0 processor (which Saxon-B is) on stylesheets which specify version="1.0" in their root element. Default: on. :silentrecoverfatal Set the policy for handling recoverable errors: "silent" for silent recovery, "recover" for recovery with warning output on standard error, "fatal" for no recovery. Default: recover. :filename Specify the main XSLT stylesheet to be used for the transformation. This option is required unless or are specified. The special filename "-" can be used to require reading the sylesheet from standard input. affects the intepretation of filename. :filename Specify a class to be used as SAX parser for stylesheets. The class must implement either org.xml.sax.Parser or org.xml.sax.XMLReader. See also . SEE ALSO saxonb-xquery (1), XSL Transformations (XSLT) Version 2.0 (W3C Recommendation). This program is fully documented by the HTML documentation of Saxon, available in the &docpackage; Debian package. AUTHOR This manual page was written by &dhusername; &dhemail; for the &debian; system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the &gnu; General Public License, Version 3 or any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. debian/manpages/saxonb-xquery.10000644000000000000000000002134412216317715013701 0ustar .\" Title: saxonb-xquery .\" Author: .\" Generator: DocBook XSL Stylesheets v1.73.2 .\" Date: February 2008 .\" Manual: .\" Source: .\" .TH "SAXONB\-XQUERY" "1" "February 2008" "" "" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .SH "NAME" saxonb-xquery - command line XQuery processor .SH "SYNOPSIS" .HP 14 \fBsaxonb\-xquery\fR [\fIOPTION\fR...] \fI\fIQUERYFILE\fR\fR [\fINAME\fR=\fIVALUE\fR...] .SH "DESCRIPTION" .PP This manual page documents briefly the \fBsaxonb\-xquery\fR command\. This page was written for the Debian(TM) distribution because the original program does not have a manual page\. Still, it has HTML documentation which is shipped in the libsaxonb\-java\-doc package\. .PP \fBsaxonb\-xquery\fR is a command line wrapper around the Saxon\-B XSLT and XQuery processor\. Using \fBsaxonb\-xquery\fR you can evaluate \fIXQuery\fR queries directly from the command line\. Internally, \fBsaxonb\-xquery\fR is a wrapper around the Java class \fBnet\.sf\.saxon\.Query\fR implemented by Saxon\-B\. .PP \fBsaxonb\-xquery\fR should be invoked passing a (required) filename containing the XQuery query to be evaluated; the special filename "\-" can be given to require reading the query from standard input\. .PP Before the query filename a list of options can be given, see below\. .SS "Parameters" .PP At the end of the command line, a list of \fIparameters\fR can be given\. Parameters are passed using the syntax \fINAME\fR=\fIVALUE\fR, to specify parameters\' names and values\. .PP A parameter name prefixed with "+" (plus sign) will be interpreted as a \fIfilesystem path parameter\fR If the path points to a single file, that file will be parsed as XML and its document node will be passed as the parameter value\. If the path points to a directory, all directly contained files will be parsed as XML files, and the sequence of their document nodes will be passed as the parameter value\. .PP A parameter name prefixed with "!" (exclamation mark) will be interpted as a output/serialization parameter\. See the specifications of XQuery and XSLT 2\.0 for more information on output/serialization parameters\. .PP To pass parameters belonging to the non\-null namespace, the syntax {\fIuri\fR}\fIlocalname\fR=\fIvalue\fR is provided\. .PP Parameters will be visible as external variables during query evaluation, provided they have been declared in the query prolog\. See the XQuery specification for more information on variables and their declarations\. .SH "OPTIONS" .PP A summary of supported options is included below\. Options can be passed in any order\. .PP We first report the options which are shared by \fBsaxonb\-xquery\fR and \fBsaxonb\-xslt\fR, then those specific to \fBsaxonb\-xquery\fR (or which have a different semantics)\. .PP Some options are flagged as "Saxon\-SA only", such options work only if Saxon\-SA is installed\. Note that Saxon\-SA is a commercial product, as such it is not available in Debian\. .SS "Common options" .PP \fB\-cr\fR:\fIclassname\fR .RS 4 Specify a class to be used for processing collection URIs passed to the \fBcollection()\fR function\. The class must implement net\.sf\.saxon\.CollectionURIResolver\. .RE .PP \fB\-dtd\fR: {[on] | [off]} .RS 4 Enable or disable DTD validation\. Default: off\. .RE .PP \fB\-expand\fR: {[on] | [off]} .RS 4 When validation is enabled, expand default values in validated documents\. This option enables or disables such an expansion\. Default: on\. .RE .PP \fB\-explain\fR [:\fIfilename\fR] .RS 4 Display an execution plan; the output is in XML format\. If filename is not given it will be displayed on standard output\. .RE .PP \fB\-ext\fR: {[on] | [off]} .RS 4 Enable or disable the ability to invoke external Java functions from query files and stylesheets\. Beware that enabling them is a potential security risk when processing untrusted files\. Default: off\. .RE .PP \fB\-l\fR: {[on] | [off]} .RS 4 Keep (when on) or throw away (when off) line numbers in tress corresponding to source documents\. When kept, line numbers can be accessed using the function \fBsaxon:line\-number()\fR\. Default: off\. .RE .PP \fB\-outval\fR: {[recover] | [fatal]} .RS 4 When validation is required, set whether validation errors are fatal (when "fatal" is passed) or if they only trigger warnings (when "recover" is)\. Default: fatal\. .RE .PP \fB\-p\fR: {[on] | [off]} .RS 4 Enable or disable usage of the PTreeURIResolver\. Saxon\-SA only\. .RE .PP \fB\-r\fR:\fIclassname\fR .RS 4 Specify a class to be used for resolving all URIs\. .RE .PP \fB\-repeat\fR:\fIN\fR .RS 4 Repeat the transformation N times\. For benchmarking purposes\. .RE .PP \fB\-sa\fR .RS 4 Perform Schema\-aware processing\. Saxon\-SA only\. .RE .PP \fB\-strip\fR: {[all] | [none] | [ignorable]} .RS 4 Specify whitespace stripping policy for source documents: strip all of them ("all"), strip none of them ("none"), strip ignorable whitespace only ("ignorable")\. Default: none\. .RE .PP \fB\-t\fR .RS 4 Display version, timing, and other debugging information on standard error\. .RE .PP \fB\-tree\fR: {[tiny] | [linked]} .RS 4 Select the implementation of the internal tree model: tiny tree model ("tiny") or linked tree model ("linked")\. See the Saxon documentation for more information on the internal tree model\. Default: tiny\. .RE .PP \fB\-T\fR [:\fIclassname\fR] .RS 4 Trace various aspect of the processing; an optional class name can be given to specify a user\-chosen tracer\. The class must implement net\.sf\.saxon\.trace\.TraceListener\. The default is a system supplied tracer\. This option implies \fB\-l\fR\. .RE .PP \fB\-TJ\fR .RS 4 Enable tracing of external Java method invocation\. See \fB\-ext\fR\. .RE .PP \fB\-u\fR .RS 4 Force interpretation of source document names as URI\. By default they are considered to be file names, unless they start with "file:" or "http:"\. .RE .PP \fB\-val\fR: {[strict] | [lax]} .RS 4 When validation is enabled, choose among "strict" or "lax" validation\. Saxon\-SA only\. .RE .PP \fB\-x\fR:\fIclassname\fR .RS 4 Specify a class to be used as SAX parser for input documents\. The class must implement either org\.xml\.sax\.Parser or org\.xml\.sax\.XMLReader\. .RE .PP \fB\-xi\fR .RS 4 Apply XInclude processing to all input documents\. .RE .PP \fB\-xmlversion\fR: {[1\.0] | [1\.1]} .RS 4 Choose the XML version for processing input documents\. "1\.1" must be specified to process XML 1\.1 and Namespaces 1\.1 constructs\. Default: 1\.0\. .RE .PP \fB\-?\fR .RS 4 Display a help message and exit\. .RE .SS "Options specific to saxonb\-xquery" .PP \fB\-mr:\fR\fB\fIclassname\fR\fR .RS 4 Use the specified class as a ModuleURIResolver to resolve query module URIs\. The class must implement net\.sf\.saxon\.query\.ModuleURIResolver\. .RE .PP \fB\-o\fR:\fIfilename\fR .RS 4 Send the query output to the specified filename\. If not specified the output will be sent to standard output\. See also \fB\-wrap\fR\. .RE .PP \fB\-pipe\fR: {[push] | [pull]} .RS 4 Internally, execute query in push or pull mode\. Mainly for testing purposes\. Push mode is usually faster when intermediate tree are constructed in memory\. Default: push\. .RE .PP \fB\-projection\fR: {[on] | [off]} .RS 4 Enable or disable document projection, i\.e\. the ability to throw away tree parts which will not be accessed by a query\. Saxon\-SA only\. .RE .PP \fB\-s\fR: {[\fIfile\fR] | [\fIURI\fR]} .RS 4 Read document input from the specified filename ("\-" can be given to read from standard input)\. The read document will be available to the query as the context node\. \fB\-u\fR affects how filename is interpreted\. .RE .PP \fB\-wrap\fR: {[on] | [off]} .RS 4 Enable or disable wrapping of query result in a XML structure which makes explicit the kind of each output node or atomic value\. For example free\-standing attributes will be wrapped in an explicit XML element stating that they are attributes\. When this is off, the query output will be wrapped only using a document node; in such a setting is possible that output parts, such as free\-standing attributes, can\'t be serialized\. Default: off\. .RE .SH "SEE ALSO" .PP saxonb\-xslt (1), XQuery 1\.0: An XML Query Language (W3C Recommendation)\. .PP This program is fully documented by the HTML documentation of Saxon, available in the libsaxon\-java\-doc Debian package\. .SH "AUTHOR" .PP This manual page was written by Stefano Zacchiroli for the Debian(TM) system (but may be used by others)\. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation\. .PP On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common\-licenses/GPL\. .SH "COPYRIGHT" Copyright \(co 2008 Stefano Zacchiroli .br debian/manpages/saxonb-xquery.xml0000644000000000000000000001517510755631615014352 0ustar Stefano"> Zacchiroli"> February 2008"> 1"> zack@debian.org"> saxonb-xquery"> Debian"> GNU"> GPL"> ]>
&dhemail;
2008 &dhusername; &dhdate; &dhucpackage; &dhsection; &dhpackage; command line XQuery processor &dhpackage; OPTION QUERYFILE NAME=VALUE DESCRIPTION This manual page documents briefly the &dhpackage; command. This page was written for the &debian; distribution because the original program does not have a manual page. Still, it has HTML documentation which is shipped in the libsaxonb-java-doc package. &dhpackage; is a command line wrapper around the Saxon-B XSLT and XQuery processor. Using &dhpackage; you can evaluate XQuery queries directly from the command line. Internally, &dhpackage; is a wrapper around the Java class net.sf.saxon.Query implemented by Saxon-B. &dhpackage; should be invoked passing a (required) filename containing the XQuery query to be evaluated; the special filename "-" can be given to require reading the query from standard input. Before the query filename a list of options can be given, see below. ¶meters; Parameters will be visible as external variables during query evaluation, provided they have been declared in the query prolog. See the XQuery specification for more information on variables and their declarations. OPTIONS &common-options; Options specific to &dhpackage; Use the specifed class as a ModuleURIResolver to resolve query module URIs. The class must implement net.sf.saxon.query.ModuleURIResolver. :filename Send the query output to the specified filename. If not specified the output will be sent to standard output. See also . :pushpull Internally, execute query in push or pull mode. Mainly for testing purposes. Push mode is usually faster when intermediate tree are constructed in memory. Default: push. :onoff Enable or disable document projection, i.e. the ability to throw away tree parts which will not be accessed by a query. Saxon-SA only. :fileURI Read document input from the specified filename ("-" can be given to read from standard input). The read document will be available to the query as the context node. affects how filename is interpreted. :onoff Enable or disable wrapping of query result in a XML structure which makes explicit the kind of each output node or atomic value. For example free-standing attributes will be wrapped in an explicit XML element stating that they are attributes. When this is off, the query output will be wrapped only using a document node; in such a setting is possible that output parts, such as free-standing attributes, can't be serialized. Default: off. SEE ALSO saxonb-xslt (1), XQuery 1.0: An XML Query Language (W3C Recommendation). This program is fully documented by the HTML documentation of Saxon, available in the &docpackage; Debian package. AUTHOR This manual page was written by &dhusername; &dhemail; for the &debian; system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the &gnu; General Public License, Version 3 or any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. debian/manpages/Makefile0000644000000000000000000000047710755631615012442 0ustar DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl MANPAGES = saxonb-xquery.1 saxonb-xslt.1 XML_ENTS = saxonb-common-options.ent saxonb-parameters.ent all: $(MANPAGES) clean: -rm $(MANPAGES) saxonb-xquery.xml: $(XML_ENTS) saxonb-xslt.xml: $(XML_ENTS) %.1: %.xml xsltproc -nonet $(DB2MAN) $< debian/manpages/saxonb-common-options.ent0000644000000000000000000001614510755631615015762 0ustar A summary of supported options is included below. Options can be passed in any order. We first report the options which are shared by &dhpackage; and &dhother;, then those specific to &dhpackage; (or which have a different semantics). Some options are flagged as "Saxon-SA only", such options work only if Saxon-SA is installed. Note that Saxon-SA is a commercial product, as such it is not available in Debian. Common options :classname Specify a class to be used for processing collection URIs passed to the collection() function. The class must implement net.sf.saxon.CollectionURIResolver. :onoff Enable or disable DTD validation. Default: off. :onoff When validation is enabled, expand default values in validated documents. This option enables or disables such an expansion. Default: on. :filename Display an execution plan; the output is in XML format. If filename is not given it will be displayed on standard output. :onoff Enable or disable the ability to invoke external Java functions from query files and stylesheets. Beware that enabling them is a potential security risk when processing untrusted files. Default: off. :onoff Keep (when on) or throw away (when off) line numbers in tress corresponding to source documents. When kept, line numbers can be accessed using the function saxon:line-number(). Default: off. :recoverfatal When validation is required, set whether validation errors are fatal (when "fatal" is passed) or if they only trigger warnings (when "recover" is). Default: fatal. :onoff Enable or disable usage of the PTreeURIResolver. Saxon-SA only. :classname Specify a class to be used for resolving all URIs. :N Repeat the transformation N times. For benchmarking purposes. Perform Schema-aware processing. Saxon-SA only. :allnoneignorable Specify whitespace stripping policy for source documents: strip all of them ("all"), strip none of them ("none"), strip ignorable whitespace only ("ignorable"). Default: none. Display version, timing, and other debugging information on standard error. :tinylinked Select the implementation of the internal tree model: tiny tree model ("tiny") or linked tree model ("linked"). See the Saxon documentation for more information on the internal tree model. Default: tiny. :classname Trace various aspect of the processing; an optional class name can be given to specify a user-chosen tracer. The class must implement net.sf.saxon.trace.TraceListener. The default is a system supplied tracer. This option implies . Enable tracing of external Java method invocation. See . Force interpretation of source document names as URI. By default they are considered to be file names, unless they start with "file:" or "http:". :strictlax When validation is enabled, choose among "strict" or "lax" validation. Saxon-SA only. :classname Specify a class to be used as SAX parser for input documents. The class must implement either org.xml.sax.Parser or org.xml.sax.XMLReader. Apply XInclude processing to all input documents. :1.01.1 Choose the XML version for processing input documents. "1.1" must be specified to process XML 1.1 and Namespaces 1.1 constructs. Default: 1.0. Display a help message and exit. debian/README.source0000644000000000000000000000055712216317715011361 0ustar Information about saxonb ------------------------------ bn and build folders are redundant for this package. bj/net/sf/saxon/dotnet package is dropped as it is also omitted from original build process by Saxonica. bj/javax and bj/net/sf/saxon/xqj packages are dropped as they violate DFSG. -- Eugene Zhukov Wed, 18 Sep 2013 13:19:39 +0000 debian/orig-tar.sh0000755000000000000000000000076512216317715011266 0ustar #!/bin/sh -e VERSION=$2 TAR=../saxonb_$VERSION+dfsg.orig.tar.gz DIR=saxonb-$VERSION TAG="$VERSION" svn export https://saxon.svn.sourceforge.net/svnroot/saxon/tags/${TAG}/ $DIR tar -c -z -f $TAR --exclude '*.class' --exclude 'build' --exclude 'bn' --exclude 'bj/net/sf/saxon/dotnet' --exclude 'bj/javax' --exclude 'bj/net/sf/saxon/xqj' $DIR rm -rf $DIR ../$TAG # move to directory 'tarballs' if [ -r .svn/deb-layout ]; then . .svn/deb-layout mv $TAR $origDir && echo "moved $TAR to $origDir" fi debian/build.xml0000644000000000000000000000565712144666234011034 0ustar debian/source/0000755000000000000000000000000012216320467010471 5ustar debian/source/format0000644000000000000000000000001411626657466011717 0ustar 3.0 (quilt) debian/libsaxonb-java.install0000644000000000000000000000011210755374270013462 0ustar debian/scripts/saxonb-xquery /usr/bin debian/scripts/saxonb-xslt /usr/bin debian/watch0000644000000000000000000000021112216317715010216 0ustar version=3 opts=dversionmangle=s/\+dfsg// \ https://saxon.svn.sourceforge.net/svnroot/saxon/tags/ (\d.*)/ \ debian debian/orig-tar.sh debian/libsaxonb-java-doc.install0000644000000000000000000000005210752425734014227 0ustar dist/api usr/share/doc/libsaxon8-java-doc debian/copyright0000644000000000000000000005502011053624061011121 0ustar This package was debianized by Michael Koch on Fri, 28 Dec 2007 17:18:24 -0400 It was downloaded from Upstream Author: Michael H. Kay Copyright: (C) 2006, 2007, 2008 Michael H. Kay License: MOZILLA PUBLIC LICENSE Version 1.0 ______________ 1. Definitions. 1.1. ``Contributor'' means each entity that creates or contributes to the creation of Modifications. 1.2. ``Contributor Version'' means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. 1.3. ``Covered Code'' means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. 1.4. ``Electronic Distribution Mechanism'' means a mechanism generally accepted in the software development community for the electronic transfer of data. 1.5. ``Executable'' means Covered Code in any form other than Source Code. 1.6. ``Initial Developer'' means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. 1.7. ``Larger Work'' means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. 1.8. ``License'' means this document. 1.9. ``Modifications'' means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. B. Any new file that contains any part of the Original Code or previous Modifications. 1.10. ``Original Code'' means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License. 1.11. ``Source Code'' means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or a list of source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge. 1.12. ``You'' means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, ``You'' includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, ``control'' means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity. 2. Source Code License. 2.1. The Initial Developer Grant. The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: (a) to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, or as part of a Larger Work; and (b) under patents now or hereafter owned or controlled by Initial Developer, to make, have made, use and sell (``Utilize'') the Original Code (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Original Code (or portions thereof) and not to any greater extent that may be necessary to Utilize further Modifications or combinations. 2.2. Contributor Grant. Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: (a) to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code or as part of a Larger Work; and (b) under patents now or hereafter owned or controlled by Contributor, to Utilize the Contributor Version (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Contributor Version (or portions thereof), and not to any greater extent that may be necessary to Utilize further Modifications or combinations. 3. Distribution Obligations. 3.1. Application of License. The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5. 3.2. Availability of Source Code. Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. 3.3. Description of Modifications. You must cause all Covered Code to which you contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code. 3.4. Intellectual Property Matters (a) Third Party Claims. If You have knowledge that a party claims an intellectual property right in particular functionality or code (or its utilization under this License), you must include a text file with the source code distribution titled ``LEGAL'' which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If you obtain such knowledge after You make Your Modification available as described in Section 3.2, You shall promptly modify the LEGAL file in all copies You make available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained. (b) Contributor APIs. If Your Modification is an application programming interface and You own or control patents which are reasonably necessary to implement that API, you must also include this information in the LEGAL file. 3.5. Required Notices. You must duplicate the notice in Exhibit A in each file of the Source Code, and this License in any documentation for the Source Code, where You describe recipients' rights relating to Covered Code. If You created one or more Modification(s), You may add your name as a Contributor to the notice described in Exhibit A. If it is not possible to put such notice in a particular Source Code file due to its structure, then you must include such notice in a location (such as a relevant directory file) where a user would be likely to look for such a notice. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. 3.6. Distribution of Executable Versions. You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. 3.7. Larger Works. You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. 4. Inability to Comply Due to Statute or Regulation. If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. 5. Application of this License. This License applies to code to which the Initial Developer has attached the notice in Exhibit A, and to related Covered Code. 6. Versions of the License. 6.1. New Versions. Netscape Communications Corporation (``Netscape'') may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number. 6.2. Effect of New Versions. Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License. 6.3. Derivative Works. If you create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), you must (a) rename Your license so that the phrases ``Mozilla'', ``MOZILLAPL'', ``MOZPL'', ``Netscape'', ``NPL'' or any confusingly similar phrase do not appear anywhere in your license and (b) otherwise make it clear that your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.) 7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. 8. TERMINATION. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. 9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered Code is a ``commercial item,'' as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of ``commercial computer software'' and ``commercial computer software documentation,'' as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein. 11. MISCELLANEOUS. This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in, the United States of America: (a) unless otherwise agreed in writing, all disputes relating to this License (excepting any dispute relating to intellectual property rights) shall be subject to final and binding arbitration, with the losing party paying all costs of arbitration; (b) any arbitration relating to this Agreement shall be held in Santa Clara County, California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to this Agreement shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. 12. RESPONSIBILITY FOR CLAIMS. Except in cases where another Contributor has failed to comply with Section 3.4, You are responsible for damages arising, directly or indirectly, out of Your utilization of rights under this License, based on the number of copies of Covered Code you made available, the revenues you received from utilizing such rights, and other relevant factors. You agree to work with affected parties to distribute responsibility on an equitable basis. The files src/net/sf/saxon/ant/AntTransform.java is licensed as follows: Upstream Authors: The Apache Ant team, see http://ant.apache.org/contributors.html for details Copyright: The Apache Software Foundation License is Apache License Version 2.0; on Debian systensm the full text can be found in /usr/share/common-licenses/Apache-2.0. The files src/net/sf/saxon/codenorm/Normalizer.java, src/net/sf/saxon/codenorm/NormalizerData.java and src/net/sf/saxon/codenorm/UnicodeDataGenerator.java are licensed as follows: Upstream Authors: Mark Davis Vladimir Weinstein Markus Scherer Copyright: 1991-2008 Unicode, Inc. License: Permission is hereby granted, free of charge, to any person obtaining a copy of the Unicode data files and any associated documentation (the "Data Files") or Unicode software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that (a) the above copyright notice(s) and this permission notice appear with all copies of the Data Files or Software, (b) both the above copyright notice(s) and this permission notice appear in associated documentation, and (c) there is clear notice in each modified Data File or in the Software as well as in the documentation associated with the Data File(s) or Software that the data or software has been modified. THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE DATA FILES OR SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in these Data Files or Software without prior written authorization of the copyright holder. The file src/net/sf/saxon/sort/GenericSorter.java is licensed as follows: Upstream Author: CERN - European Organization for Nuclear Research Copyright: 1999 CERN - European Organization for Nuclear Research License: Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. CERN makes no representations about the suitability of this software for any purpose. It is provided "as is" without expressed or implied warranty. debian/saxonb-xpath/0000755000000000000000000000000012216320467011605 5ustar debian/saxonb-xpath/META-INF/0000755000000000000000000000000012216320467012745 5ustar debian/saxonb-xpath/META-INF/service/0000755000000000000000000000000012216320467014405 5ustar debian/saxonb-xpath/META-INF/service/javax.xml.xpath.XPathFactory0000644000000000000000000000064010752425734021744 0ustar net.sf.saxon.xpath.XPathFactoryImpl http\://java.sun.com/jaxp/xpath/dom: net.sf.saxon.xpath.XPathFactoryImpl http\://saxon.sf.net/jaxp/xpath/om: net.sf.saxon.xpath.XPathFactoryImpl http\://www.xom.nu/jaxp/xpath/xom: net.sf.saxon.xpath.XPathFactoryImpl http\://jdom.org/jaxp/xpath/jdom: net.sf.saxon.xpath.XPathFactoryImpl http\://www.dom4j.org/jaxp/xpath/dom4j: net.sf.saxon.xpath.XPathFactoryImpl debian/libsaxonb-java.poms0000644000000000000000000000005012127005333012755 0ustar debian/saxonb.pom --has-package-version debian/README.Debian0000644000000000000000000000343010755632746011246 0ustar Command line XSLT 2.0 and XQuery 1.0 processing ----------------------------------------------- To invoke the XSLT 2.0 processor from the command line you can execute the following command: CLASSPATH=/usr/share/java/saxonb.jar \ java net.sf.saxon.Transform -s:input.xml -xsl:style.xsl -o:output.xml similarly, XQuery 1.0 processing can be invoked with: CLASSPATH=/usr/share/java/saxonb.jar \ java net.sf.saxon.Query query.xq In both cases, try -help to see other available options and see the command line reference manual available in the libsaxonb-java-doc package. Debian-specific helpers are provided to ease the invocations: saxonb-xslt [OPTIONS ...] saxonb-xquery [OPTIONS ...] the former will invoke the XSLT 2.0 processor passing it all given options, the latter will do the same for the XQuery 1.0 processor. -- Stefano Zacchiroli Fri, 15 Feb 2008 15:04:41 +0100 Calls on external Java functions disabled by default ---------------------------------------------------- By default, SaxonB enables calls on external Java functions to be embedded in stylesheets or queries. Such calls can invoke arbitrary Java methods and are thus a security risk when executing untrusted XSLT stylesheets of XQuery queries. For this reason, SaxonB in Debian comes with calls on external Java functions disabled by default. If you are using the command line interface to the XSLT 2.0 or XQuery processors of Saxon, you can enable this feature by passing the "-ext:on" flag to your command line invocation. If you are using SaxonB from its Java API you should set the Attribute "FeatureKeys.ALLOW_EXTERNAL_FUNCTIONS" to "true". See the API reference in the libsaxonb-java-doc package for more information. -- Stefano Zacchiroli Fri, 15 Feb 2008 14:47:43 +0100