33 Oracle XML Developer's Kit Standards

DOM Standard for XDK for Java

The DOM APIs include support for candidate recommendations of DOM Level 3 Validation and DOM Level 3 Load and Save.

XSLT Standard for XDK for Java

The XSLT processor adds support for the current working drafts of XSLT 2.0, XPath 2.0, and the shared XPath/XQuery data model.

Note:

At the time of release of Oracle Database 10g Release 2 the World Wide Web Consortium (W3C) Extensible Stylesheet Language Transformation (XSLT) and XPath working group had not yet published the XSLT 2.0 and XPath 2.0 recommendations. Oracle will continue to track the evolution of the XSLT 2.0 and XPath 2.0 specifications, until they become recommendations. During this period, to follow the evolution of the XSLT 2.0 and XPath 2.0 specifications, Oracle may be forced to release updates to the XSLT 2.0 and XPath 2.0 implementation which are not backward compatible with previous releases or patch sets. During this period Oracle does not guarantee any backward compatibility between database releases or patch sets with our XSLT 2.0 and XPath 2.0 implementation. After the XSLT 2.0 and XPath 2.0 specifications become recommendations, Oracle will produce a release or patch set that includes an implementation of the XSLT 2.0 and XPath 2.0 recommendations. From that point on, standard Oracle policies for backward compatibility will apply to the Oracle XSLT 2.0 and XPath 2.0 implementation. See http://www.w3.org for the latest information on the status of XSLT 2.0 and XPath 2.0 specifications.

Some features of these specifications are not supported in the current release:

• The Schema Import and Static Typing features are not supported, but the XML Schema built-in types specified by the XPath 2.0 Datamodel are supported.

• The schema-element and schema-attribute nodetests are not supported.

• The XSLT instruction xsl:number uses XSLT 1.0 semantics and syntax.

• The use-when standard attribute is not supported.

• The processor does not honor the attribute of required on xsl:param.

• Tunnel parameters are not supported.

• Regular expression instructions are not supported in XSLT.

• The XPath 2.0 functions fn:tokenize, fn:matches, and fn:replace are not supported.

• format-dateTime, format-date, and format-time functions are not supported.

• The content model for xsl:attribute, xsl:comment, xsl:message and the way to compute key values of xsl:key and xsl:sort are still 1.0 behavior.

• attribute [xsl:]inherit-namespaces for xsl:copy, xsl:element, and literal result elements is not supported.

Updates to the W3C specifications for XPath 2.0 and XSLT 2.0 resulted in certain differences in behavior from 10g Release 1. For 10g Release 1 compatible behavior set the system property oracle.xdkjava.compatibility.version=10.1.0.

XPath 2.0—Differences between 10g Release 1 and 10g Release 2

1. RangeExpr, behavior for (m to n), where m > n changed. Earlier, it was treated as (n to m) reverse sequence. As described in the April 2005 draft, an empty sequence is returned.

2. isnot operator was removed, as described in the April 2005 draft.

3. getEffectiveBooleanValue definition (fn:boolean) updated, as described in the April 2005 draft. An empty string value causes an exception (FORG006) instead of returning false. All cases not handled by getEffectiveBooleanValue raise an exception (FORG006). XPath 1.0 behavior for fn:boolean remains the same.

XSLT 2.0—Difference between 10g Release 1 and 10g Release 2

normalize-unicode was changed to normalization-form, the allowed attribute values were changed from "yes" | "no" to "NFC" | "NFD" | "NKFC" | "NKFD" | \x{2026}\x{2026}, as described in the November 2004 draft.

JAXB Standard for XDK for Java

The XDK implementation of the Java Architecture for XML Binding (JAXB) specification does not support these features:

• Javadoc generation

• XML Schema component "any" and substitution groups

Pipeline Definition Language Standard for XDK for Java

The XML Pipeline processor differs from the W3C Note as follows:

• The parser processes DOMParserProcess and SAXParserProcess are included in the XML pipeline (Section 1).

• Only the final target output is checked to see if it is up-to-date with the available pipeline inputs. The XML Pipeline processor does not determine whether the intermediate outputs of every process are up-to-date (Section 2.2).

• For the select attribute, anything in between double quotation marks ("...") is considered to be a string literal.

• The XML Pipeline processor throws an error if more that one process produces the same infoset (Section 2.4.2.3).

• The <document> element is not supported (Section 2.4.2.8).