Built-in schemas
Saxon includes built-in schemas for a number of namespaces.
These fall into two categories:
-
Hard-coded namespaces
Schemas for certain namespaces are hard-coded into the Saxon schema processor and cannot be replaced or extended in any way. The namespaces in this category are:
The
xmlnamespacehttp://www.w3.org/XML/1998/namespacewhich defines attributes such asxml:spaceandxml:id.The
fnnamespacehttp://www.w3.org/2005/xpath-functionswhich defines the structure of the document returned byfn:analyze-string()and also the XML representation of the JSON data model.The
xsinamespacehttp://www.w3.org/2001/XMLSchema-instancewhich defines attributes such asxsi:typeandxsi:schemaLocation.
-
Cached namespaces
Schemas for certain namespaces are held locally in the standard
xmlresolverdata cache which Saxon uses by default. If you reference one of these schemas in anxs:importdeclaration, Saxon will ignore any location hint in theschemaLocationattribute, and use its local copy in preference. If you want to use a non-standard version of one of these schemas from a location of your own choosing, you can use Saxon's resolver mechanisms to achieve this: for example you can supply your ownResourceResolvercallback, or you can register a catalog file that redirects the namespace URI to a different location.The schemas in this category are:
The
xlinknamespacehttp://www.w3.org/1999/xlinkThe
xhtmlnamespacehttp://www.w3.org/1999/xhtmlThe
xsdnamespacehttp://www.w3.org/2001/XMLSchemaThe
xsltnamespacehttp://www.w3.org/1999/XSL/Transform