Oracle XML Schema Processor 9.2.0.2.0 (C)


Contents

General description

Revision history


The C/C++ Oracle XML Schema Processor supports the XML Schema W3C Recommendation. Note that it's not backwards compatible with any previous CR or working draft.

You may post any questions, comments, or bug reports to the XML Forum on the Oracle Technology Network. Oracle customers may also call Oracle Worldwide Support for assistance.

The schema processor is based on the May 2, 2001 XML Schema W3C Recommendation (in three parts):

The parser conforms to the following standards: The following files and directories are found in this release: The following libraries are included: The processor may be called as an executable by invoking bin/schema which takes two arguments, the XML instance document, and optionally a default schema to apply.

The schema processor may also be invoked by writing code using the supplied APIs. The code must be compiled using the headers in the include/ subdirectory and linked against the libraries in the lib/ subdirectory. Please see the Makefile in the sample/ subdirectory for full details of how to build your program. The processor currently implements most of the functionality stated in the specification except the following features:

The processor also implements pattern matching in a restrictive manner.  Similar to Unique Particle Attribution (3.8.6), the regular expression specified for the pattern must not be ambiguous.  For example, the following regular expression is ambiguous:

because the multi-character escape "." subsumes the character period or character strings "gif", "jpg", "jpeg", or "bmp".  If this regular expression is changed to then it's not ambiguous.  Most schema processors can process unambiguous regular expressions more efficiently.

This processor supports various encodings.  The schema file and instance XML document can be in different encodings.  However, when a parser context is created for both, they need to be in the same data encoding (i.e., the encoding that the final DOM tree resides in).  This is specified by providing the "outencoding" parameter to the xmlinitenc() function. If xmlinit() is used to set up the parsing context, data encoding will use the default which is UTF-8 on ASCII platforms and UTFE on non-ASCII platforms.  For documents in multi-byte encodings, the fastest path in the processor is chosen by selecting the data encoding to be in UTF-16.  Please see the sample programs in the sample/ subdirectory for full details.


Oracle XML Schema Processor 9.2.0.2.0 (C)


February 13, 2002

This release contains bug fixes.


Oracle XML Schema Processor 9.2.0.1.0 (C)


January 31, 2002

This release contains bug fixes.


Oracle XML Schema Processor 9.0.2.0.0D (C)

Nov 30, 2001

This is the first Beta release of the C/C++ Oracle XML Schema Processor that supports the XML Schema W3C Recommendation. Note that it's not backwards compatible with any previous CR or working draft.


Oracle XML Schema Processor 9.0.2.0.0C (C)


September 30, 2001

This release contains bug fixes.


Oracle XML Schema Processor 9.0.2.0.0B (C)

July 31, 2001

This release contains bug fixes.


Oracle XML Schema Processor 9.0.2.0.0A (C)

June 14, 2001

This release contains bug fixes.


Oracle XML Schema Processor 9.0.1.0.0 (C)

May 1, 2001

This release contains bug fixes.