# Conformance Documentation

This information will be updated for XSLT 2.0 and XQuery 1.0 once the conformance rules are fully stable.

The XSLT specification says that the documentation for an implementation should specify which URI schemes are supported. Saxon supports the URI scheme implemented by the Java `java.net.URL` class, with the optional addition of a fragment identifier, as described below. Additionally, Saxon allows the user to nominate a URIResolver class which can be used to implement any URI scheme the user wants.

The XSLT specification says that the documentation for an implementation should specify for which media types fragment identifiers are supported. The standard URI resolver supports access to XML documents only. A simple fragment identifier is allowed, consisting of the value of an ID attribute in the document. The effect is to return the subdocument rooted at the element with this identifier if there is one, or an empty document otherwise. For example, the URI mydoc.xml#aaa locates the XML document mydoc.xml, and if it contains an element <eeee id="aaa">, where id is an attribute of type ID, then the document retrieved is an XML document with this <eeee> element as its outermost (document) element.

The values of the vendor-specific system properties accessible through the `system-property()` function in XSLT are:

Property | Value
xsl:version | 2.0
xsl:vendor | SAXON n.n.n from Saxonica
xsl:vendor-url | http://saxon.sf.net/
xsl:product-name | SAXON
xsl:product-version | n.n.n

All these values are subject to change in future releases. Users wishing to test whether the processor is Saxon are advised to test whether the `xsl:product` system property has the value "SAXON".

Expand | Next