11 16:20:05 (original) (raw)

2.2. Running XSV at your own installation

2.2.1. Win32 one-click installation

I've packaged the current version up in to aself-installing package for Win32 platforms: just fetch it, run it, and add the installation directory to your PATH, then

xsv [flags] target [schemas . ..]

target

The document to be processed (must be a URL, relative or absolute. Note this means forward-slashes only, even on WIN32 -- e.g. file:///C:/Project/xxx.xml).

schemas

Schema documents to process it with, also URLs.

-o errfile

Output error file to errfile rather than stderr.

-s stylefile

Include an XSL style PI tostylefile in the error output.

-r [alt|ind]

Reflect the augmented document infoset as an XML file to stdout(follow with alt to force old-style (alternating normal form) reflection, or ind (the default) for new-style (individual normal form) reflection. Use -r -r to get all schema components_other_ than those of the schema for schemas, and -r -r -r to get the complete PSVI reflection including the schema for schemas.

-w

Include warnings in error output.

-t

Show stage timings.

-k

Attempt instance validation even if schema(s) has/have errors.

-i

Input should all be schemas, assume they are meant to be complete and check them as such.

-D

Use DTD to pre-validate, not built-in schema-for-schemas.

-l

Scan the whole document for schema location hints, not just root and new-namespace-binding-introducers.

-E elt

Force document element to be named elt, an expanded name (i.e. either an unqualfied simple name in no known namespace, or a name of the form {namespaceName}localName).

-T type

Force document element to be validated against the type definition named type, an expanded name as for -E.

-N

Don't dereference namespace URIs looking for schema documents.

-e

Preserve the low-level error transcript file.

-n

Output the input document with normalized values and defaults.

-u URI

Provide a base URI for target and schemas.

-d

Show backtrace if crash occurs

2.2.2. Source distributions for the more adventurous

You can download the (Python) sources from the W3C public CVS repository, install Python 2.4 and do:

[set PYTHONPATH to whereever you installed XSV sources] python .../XSV/commandLine.py ...

No, the above instructions aren't sufficiently detailed, but you probably don't want the sources unless you can figure out how to make it work :-)

Previous versions of XSV required our fast Python/C hybrid XML parser---this version should work with either PyLTXML or PyXML:

PyLTXML

Downloads: Be sure to use the most recent version, currently PyLTXML-1.3, release 9. Installers for a number of architectures now available.

PyXML

Downloads. Although no longer supported, the old version 0.8.4 contains updated code which is available nowhere else and necessary for XSV to work properly.

2.2.3. Linux RPMs and DEBs

Packages are now available for those running some versions of Linux:

These have a dependency on PyLTXML-1.3 (and Python itself -- they were all built with Python2.4), see above.

2.2.4. Source tarball

A simple tar ball is also available, suitable for installation using Python's distutils:

[cd to whereever you unpacked the tarball] python setup.py install