November 30, 2001
No changes.
July 31, 2001
This release contains bug fixes.
May 1, 2001
This release contains bug fixes.
February 14, 2001
This release contains bug fixes.
January 26, 2001
The only change between 9.0.0.0.0 and 1.0.1.0.0 is a change in version numbering.
October 17, 2000
Second Beta release of the Oracle XML Schema Processor. More complete implementation, bugfixes, and support for both the April/2000 and August/2000 versions of Schema.
July 11, 2000
First Beta release of the Oracle XML Schema Processor. Please note that this processor is written against the working draft Schema specification, so behavior is certain to change in the future.
Be sure to read the licensing agreement before using this product. The processor is currently available only for testing purposes. We expect to make it available for commercial use in the future.
Please post any questions, comments, or bug reports to the XML Forum on the Oracle Technology Network. At this time OTN is your only support resource.
The Schema processor is based on the April 7, 2000 version of the XML Schema Working Draft (in three parts):
The parser conforms to the following standards:
The following files and directories are found in this release:
| license.html | Licensing agreement |
| readme.html | This file |
| bin/ | Schema processor "schema" |
| doc/ | API documentation |
| include/ | Header files |
| lib/ | XML/XSL/Schema & support libraries |
| mesg/ | Error message files |
| sample/ | Example usage of the Schema processor |
| libxml9.a | XML Parser/XSL Processor |
| libxsd9.a | XML Schema Processor |
| libcore9.a | CORE functions |
| libnls9.a | National Language Support |
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.
An error message file is provided in the mesg/
subdirectory.
The parser currently only accepts file names for the document and the associated external entities. URIs for additional protocols may be accepted in future releases.
The parser currently supports the following encodings: UTF-8, UTF-16, US-ASCII, ISO-10646-UCS-2, ISO-8859-1, ISO-8859-2, ISO-8859-3, ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-8, ISO-8859-9, EUC-JP, SHIFT_JIS, BIG5, GB2312, KOI8-R, EBCDIC-CP-US, EBCDIC-CP-CA, EBCDIC-CP-NL, EBCDIC-CP-WT, EBCDIC-CP-DK, EBCDIC-CP-NO, EBCDIC-CP-FI, EBCDIC-CP-SE, EBCDIC-CP-IT, EBCDIC-CP-ES, EBCDIC-CP-GB, EBCDIC-CP-FR, EBCDIC-CP-HE, EBCDIC-CP-BE, EBCDIC-CP-CH, EBCDIC-CP-ROECE, EBCDIC-CP-YU, and EBCDIC-CP-IS. In addition, any character set specified in Appendix A, Character Sets, of the Oracle National Language Support Guide may be used.
In order to be able to use these encodings, you must have the ORACLE_HOME environment variable set and pointing to the location of your Oracle installation. In addition, the environment variables ORA_NLS, ORA_NLS32, and ORA_NLS33 must be set to point to the location of the NLS data files. On Unix systems, this is usually $ORACLE_HOME/ocommon/nls/admin/data. On Windows NT, this is usually $ORACLE_HOME/nlsrtl/admin/nlsdata.
The default encoding is UTF-8. It is recommended that you set the default encoding explicitly if using only single byte character sets (such as US-ASCII or any of the ISO-8859 character sets) for performance up to twice as fast as with multibyte character sets, such as UTF-8.