This record type represents the components of a URI.
The original URI. This element is returned by
The URI scheme (e.g., “https” or “file”).
The URI is an absolute URI.
Whether the URI is hierarchical or not.
The authority portion of the URI (e.g., “example.com:8080”).
Any userinfo that was passed as part of the authority.
The host passed as part of the authority (e.g., “example.com”).
The port passed as part of the authority (e.g., “8080”).
The path portion of the URI.
Any query string.
Any fragment identifier.
Parsed and unescaped path segments.
Parsed and unescaped query key-value pairs.
The path of the URI, treated as a filepath.
This record type represents the properties of a simple or complex type in a schema.
The name of the type. Empty in the case of an anonymous type. Corresponds to
True for a simple type, false for a complex type.
Function item returning the base type (the type from which this type is derived by restriction
or extension). The function is always present, and returns an empty sequence
in the case of the type xs:anyType. Corresponds to the
For an atomic type, a function item returning the primitive type from which this
type is ultimately derived. Corresponds to the
xs:anyAtomicType. If this is a primitive type, the
function item is idempotent.
For a simple type, one of "atomic", "list", or "union", corresponding to the
"empty", "simple", "element-only", or "mixed",
corresponding to the xs:anySimpleType.
For a simple type with variety "union", a function that returns a sequence of
records representing the member types of the union, in order, corresponding to the
"list",
a function that returns a record representing the item type of the list type, corresponding to
the
For a complex type with variety "simple" (that is, a complex type with simple content),
a function that returns a record representing the relevant simple type, corresponding to
the
For a
For a simple type, a function item that can be used to construct instances of this type. In the case of a named
type that is present in the dynamic context, the result is the same function as returned by
xs:anyAtomicType,
xs:anySimpleType, and
xs:NOTATION. It is also absent for all
This record type is used to hold the result of the
This map (V ) contains one entry for each public
global variable declared in the library module. The key of the
entry is the name of the variable, as an xs:QName
value; the associated value is the value of the variable.
This map (F ) contains one entry for each distinct QName
Q that represents the name of a public and non-external
function declared in the library module. The key of the entry is
Q, as an xs:QName value; the associated value
is a map A. This map (A) contains one entry for
each arity N within the arity range of any of the function
declarations with the given name; its key is N, as an
xs:integer value, and its associated value is a function
item obtained as if by evaluating a named function reference
Q#N, using the static and dynamic context of the call on
This record type is used to hold the result of the
This entry holds a sequence of strings containing column names.
The content depends on the setting of the header
entry in $options:
With "header":false() (which is the default),
the value of this entry is an empty sequence.
With "header":true(), the value is a sequence
of strings taken from the first row of the data. The strings have
leading and trailing whitespace trimmed, regardless of the value of the
trim-whitespace option. The sequence
of strings will potentially be truncated if the number-of-columns
option is specified, and it will potentially be reordered if the
filter-columns option is specified. Any strings that are
zero-length or duplicated are retained
If the value of the header option is a sequence
of strings, then the value is taken from the supplied sequence.
The order of names is select-columns
option; the supplied list of names is expected to refer to columns
in the result, not to columns in the input.
This entry holds a map from column names (as strings) to
column positions (as 1-based positive integers).
The content depends on the setting of the header
entry in $options:
With "header":false() (which is the default),
the value of this entry is an empty map.
With "header":true(), the map
contains entries based on the contents of the first row of the data.
The strings have
leading and trailing whitespace trimmed, regardless of the value of the
trim-whitespace option. Any string appearing in the header
row that is non-zero-length and is not equal (using codepoint collation) to
any previous string appearing in the header results in an entry
pairing that string to its 1-based position in the header row.
If the select-columns
option is present then the entries are adjusted (or removed) to
reflect their position in the adjusted data rows.
If the value of the header option is a
sequence of strings, then the map contains entries based on the supplied value.
Any string appearing in the option value that is non-zero-length and
is not equal (using codepoint collation) to
any previous string results in an entry
pairing that string to its 1-based position in the sequence.
The allocation of column numbers is select-columns
option; the supplied list of names is expected to refer to columns
in the result, not to columns in the input.
This entry is a sequence of arrays of strings, holding the parsed
rows of the CSV data. The format is the same as the result of the
header
option is true. If there are no data rows in the CSV, the
value will be an empty sequence.
A function providing ready access to a given field in a given
row. The get function has signature:
The function takes two arguments: the first is an integer giving the row number (1-based), the second identifies a column either by its name or by its 1-based position.
Except in error cases (described below),
the function call $csv?get($R, $C), where $C
is an integer, returns the value of $csv?rows[$R] => array:get($C, ""),
and the function call $csv?get($R, $K), where $K
is a string, returns the value of $csv?get($R, $csv?column-index($K)).
The properties of the function are as follows:
Absent
(xs:positiveInteger, (xs:positiveInteger | xs:string)) => xs:string
None
As described in the specification above
A dynamic error
The function returns a field in the result.
The first argument $row selects a row within the sequence of rows
returned as rows by position (one-based). If the value is out of range for the number
of rows returned, the get function returns a zero-length
string.
The second argument $col may be either an integer or a string.
If $col is an integer then it selects a field within the
selected row by position (one-based). If the value is out of range for the number
of fields in the selected row, the get function returns a zero-length
string.
If $col is a string, the string is mapped to an integer using the
map in the returned column-index. If the string is not present
in this map, then an error is raised $col directly.
This record type is used to represent the result of a call on
the
An xs:double greater than or equal
to zero (0.0e0), and less than one (1.0e0).
A zero-arity function that can be called to return another random number generator.
The properties of this function are as follows:
name: absent
parameter names: ()
signature: () => random-number-generator-record
non-local variable bindings: none
implementation: implementation-dependent
A function with arity 1 (one), which takes an arbitrary sequence as its argument, and returns a random permutation of that sequence.
The properties of this function are as follows:
name: absent
parameter names: "arg"
signature: (item()*) => item()*
non-local variable bindings: none
body: implementation-dependent
Returns the name of a node, as an xs:QName.
If the argument is omitted, it defaults to the context value (.).
If $node is the empty sequence, the empty sequence is returned.
Otherwise, the function returns the result of the dm:node-name accessor as
defined in
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?,
type error
For element and attribute nodes, the name of the node is returned as an
xs:QName, retaining the prefix, namespace URI, and local part.
For processing instructions, the name of the node is returned as an
xs:QName in which the prefix and namespace URI are
For a namespace node, the function returns an empty sequence if the node represents the
default namespace; otherwise it returns an xs:QName in which prefix and
namespace URI are
For all other kinds of node, the function returns the empty sequence.
One
Two
Returns information about the type of a value, as a string.
The function returns a string, whose lexical form will always match
the grammar of $value.
If $value is the empty sequence, the function returns the string "empty-sequence()".
Otherwise, the returned string is the concatenation of:
A string representing the distinct item types that are present in $value,
formed as follows:
For each item in $value, construct a string representing its item type
as described below.
Eliminate duplicate strings from this list by applying the
If $ss contains only one string, use that string.
Otherwise, return the result of the expression `({ fn:string-join($ss, "|") })`.
An occurrence indicator: absent if $value contains exactly one item, or
"+" if it contains more than one item.
The string representing the type of an individual item J is constructed as follows:
If J is an
"document-node()""element()""attribute()""text()""processing-instruction()""comment()""namespace-node()"
If J is a jnode(T), where T is the result of
applying the
If J is an atomic item, the result is a string chosen as follows:
Let T be the type denoted by the type annotation of J.
If T is an anonymous type, set T to the base type of T, and repeat until a type is reached that is not anonymous.
If the name of T is in the namespace http://www.w3.org/2001/XMLSchema,
return the string "xs:local" where local is the local part of the
name of T.
Otherwise, return the name of T in the form of a
"Q{uri}local",
or "Q{}local" if the name is in no namespace).
If J is a function item:
If J is an array, return "array(*)".
If J is a map, return "map(*)".
Otherwise, return "function(*)".
If the $value argument is omitted and the context value is
In general, an item matches more than one type, and there are cases where there is no single matching type that is more specific than all the others. This is especially true with functions, maps, and arrays. This function therefore selects one of the types that matches the item, which is not necessarily the most specific type.
This function should not be used as a substitute for an instance of test. The precise type annotation
of the result of an expression is not always predictable, because processors are free to deliver a more specific type
than is mandated by the specification. For example, if $n is of type xs:positiveInteger,
then the result of abs($n) is guaranteed to be an instance of xs:integer, but an
implementation might reasonably return the supplied value unchanged: that is, a value whose actual type
annotation is xs:positiveInteger. Similarly the type annotation of the value returned by
position() might be xs:long rather than xs:integer.
Implementations xs:string.
One
Two
New in 4.0
Returns true for an element that is
If the argument is omitted, it defaults to the context value (.).
If $node is the empty sequence, the function returns the empty sequence.
Otherwise the function returns the result of the dm:nilled accessor as
defined in
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?, type error
If $node is not an element node, the function returns the empty
sequence.
If $node is an untyped element node, the function returns false.
In practice, the function returns true only for an element node that has
the attribute xsi:nil="true" and that is successfully validated against a
schema that defines the element to be nillable; the detailed rules, however, are defined
in
Returns the value of $value represented as an xs:string.
In the zero-argument version of the function, $value defaults to the context
value. That is, calling fn:string() is equivalent to calling
fn:string(.).
If $value is the empty sequence, the function returns the zero-length
string.
If $value is an dm:string-value accessor defined in
If $value is a string(jnode-content($value)).
This will fail in the case where jnode-content($value) is a map or an array.
If $value is an atomic item, the function returns the result of the expression $value cast
as xs:string (see
In all other cases, a dynamic error occurs (see below).
The following errors may be raised when $value is omitted:
If the context value is
If the context value is not an instance of the sequence type item()?, type error
A type error is raised $value is a function item (this includes maps and arrays).
Every node has a string value, even an element with element-only
content (which has no typed value). Moreover, casting an atomic item to a string always
succeeds. Functions, maps, and arrays have no string value, so these
satisfy the type signature but cause failure. Applying the
Returns the result of atomizing a sequence. This process flattens arrays, and replaces nodes by their typed values.
If the argument is omitted, it defaults to the context value (.).
The result of $input:
If the item is an atomic item, it is appended to the result sequence.
If the item is an dm:typed-value accessor as defined in
If the item is a
If the item is an array, the result of applying
A type error is raised $input is a node that does not have a typed value.
A type error is raised $input is a function item other than
an array.
A type error is raised $input is omitted and the context value is
The process of applying the
The result of atomizing an empty sequence is an empty sequence.
The result of atomizing an empty array is an empty sequence.
Returns the base URI of a node.
The zero-argument version of the function returns the base URI of the context node: it
is equivalent to calling fn:base-uri(.).
The single-argument version of the function behaves as follows:
If $node is the empty sequence, the function returns the empty
sequence.
Otherwise, the function returns the value of the dm:base-uri accessor
applied to the node $node. This accessor is defined, for each kind of
node, in the XDM specification (See
As explained in XDM, document, element and processing-instruction nodes have a base-uri property which may be empty. The base-uri property for all other node kinds is the empty sequence. The dm:base-uri accessor returns the base-uri property of a node if it exists and is non-empty; otherwise it returns the result of applying the dm:base-uri accessor to its parent, recursively. If the node does not have a parent, or if the recursive ascent up the ancestor chain encounters a parentless node whose base-uri property is empty, the empty sequence is returned. In the case of namespace nodes, however, the result is always an empty sequence — it does not depend on the base URI of the parent element.
See also
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?, type error
Returns the URI of a resource where a document can be found, if available.
If the argument is omitted, it defaults to the context value (.).
If $node is the empty sequence, the function returns the empty sequence.
If $node is not a document node, the function returns the empty
sequence.
Otherwise, the function returns the value of the document-uri accessor
applied to $node, as defined in
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?, type error
In the 3.1 version of this specification, it was mandated that two distinct documents could
not have the same document-uri property: more specifically, it was guaranteed that for any document node
$D, either document-uri($D) would be absent, or doc(document-uri($D))
would return $D.
For various reasons, this constraint has proved impractical. Different parts of an application
may read the same external resource in different ways, for example with or without validation or
whitespace stripping, leading to different document nodes derived from the same external
resource having the same document-uri property. In addition, the specification
explicitly allows implementations, at user request, to relax the requirements for determinism
of resource access functions, which makes it possible for multiple calls of functions such as
Although the uniqueness of the document-uri property is no longer
an absolute constraint, it is still desirable that implementations should where possible
respect the principle that URIs are usable as identifiers for resources.
In the case of a document node $D returned by the fn:document-uri($D) returns a URI $U
such that a call on fn:doc($U) in the same dynamic context will return the same document
node $D. The URI $U will not necessarily be the same URI that was originally
passed to the
It is
The constraints on the result of the function have been relaxed.
Calling the
This function never returns a value. Instead it always raises an error. The effect of the error is identical to the effect of dynamic errors raised implicitly, for example when an incorrect argument is supplied to a function.
The parameters to the
There are three pieces of information that may be associated with an error.
The $code is an error code that distinguishes this error from others.
It is an xs:QName; the namespace URI conventionally identifies the
component, subsystem, or authority responsible for defining the meaning of the
error code, while the local part identifies the specific error condition. The
namespace URI http://www.w3.org/2005/xqt-errors is used for errors
defined in this specification; other namespace URIs may be used for errors defined
by the application.
If the external processing environment expects the error code to be returned as a
URI or a string rather than as an xs:QName, then an error code with
namespace URI NS and local part LP will be returned in
the form NS#LP. The namespace URI part of the error code should
therefore not include a fragment identifier.
If no value is supplied for the $code argument, fn:QName('http://www.w3.org/2005/xqt-errors', 'err:FOER0000').
The $description is a natural-language description of the error
condition.
If no value is supplied for the $description
argument,
The $value is an arbitrary value used to convey additional
information about the error, and may be used in any way the application
chooses.
If no value is supplied for the $value
argument
This function always raises a dynamic error. By default, it raises
The value of the $description parameter may need to be localized.
Since the function never returns a value, the declared return type of item()*
is a convenient fiction. It is relevant insofar as a function item such as error#1
may (as a consequence of function coercion) be supplied in contexts where a function with a more specific
return type is required.
Any QName may be used as an error code; there are no reserved names or namespaces. The error is always classified as a dynamic error, even if the error code used is one that is normally used for static errors or type errors.
http://www.w3.org/2005/xqt-errors#FOER0000 (or the corresponding
xs:QName) to the external processing environment, unless the error
is caught using a try/catch construct in the host language.http://www.example.com/HR#toohighsal and the
xs:string
"Salary is too high" (or the corresponding
xs:QName) to the external processing environment, unless the error
is caught using a try/catch construct in the host language.All three arguments are now optional, and each argument can be set
to an empty sequence. Previously if $description was supplied, it could not be empty.
Provides an execution trace intended to be used in debugging queries.
The function returns $input, unchanged.
In addition, the values of $input, typically serialized and converted
to an xs:string, and $label (if supplied
Any serialization of the implementation’s trace output
The format of the trace output and its order are
If the trace information is unrelated to a specific value,
Consider a situation in which a user wants to investigate the actual value passed to
a function. Assume that in a particular execution, $v is an
xs:decimal with value 124.84.
Writing fn:trace($v, 'the value of $v is:') will return $v.
The processor "124.84" and
"the value of $v is:" to an
The following two XPath expressions are identical, but only the second provides trace feedback to the user:
//book[xs:decimal(@price) gt 100]
//book[xs:decimal(@price) gt 100] => trace('books more expensive than €100:')
The $label argument can now be set
to an empty sequence. Previously if $label was supplied, it could not be empty.
Outputs trace information and discards the result.
Similar to $input,
typically serialized and converted to an xs:string, and $label
(if supplied and non-empty)
In contrast to
Any serialization of the implementation’s log output
The format of the log output and its order are
The function can be used for debugging. It can also be helpful in productive environments, e.g. to store dynamic input and evaluations to log files.
The following two XPath expressions are identical, but only the second logs any feedback:
//book[xs:decimal(@price) lt 1000]
//book[if (xs:decimal(@price) lt 1000) then true() else message(@price, @title || ' is unexpectedly expensive: ')]
New in 4.0
+ operator when
applied to two numeric valuesReturns the arithmetic sum of its operands: ($arg1 + $arg2).
General rules: see
For xs:float or xs:double values, if one of the operands is a
zero or a finite number and the other is INF or -INF,
INF or -INF is returned. If both operands are
INF, INF is returned. If both operands are
-INF, -INF is returned. If one of the operands is
INF and the other is -INF, NaN is
returned.
- operator when
applied to two numeric values. Returns the arithmetic difference of its operands: ($arg1 - $arg2).
General rules: see
For xs:float or xs:double values, if one of the operands is a
zero or a finite number and the other is INF or -INF, an
infinity of the appropriate sign is returned. If both operands are INF or
-INF, NaN is returned. If one of the operands is
INF and the other is -INF, an infinity of the appropriate
sign is returned.
* operator when
applied to two numeric values.Returns the arithmetic product of its operands: ($arg1 * $arg2).
General rules: see
For xs:float or xs:double values, if one of the operands is a
zero and the other is an infinity, NaN is returned. If one of the operands
is a non-zero number and the other is an infinity, an infinity with the appropriate sign
is returned.
div operator when
applied to two numeric values.Returns the arithmetic quotient of its operands: ($arg1 div $arg2).
General rules: see
As a special case, if the types of both $arg1 and $arg2 are
xs:integer, then the return type is xs:decimal.
A dynamic error is raised xs:decimal
and xs:integer operands, if the divisor is (positive or negative) zero.
For xs:float and xs:double operands, floating point division
is performed as specified in INF. A negative number divided by positive zero
returns -INF. Division by negative zero returns -INF and
INF, respectively. Positive or negative zero divided by positive or
negative zero returns NaN. Also, INF or -INF
divided by INF or -INF returns NaN.
idiv operator when
applied to two numeric values.Performs an integer division.
General rules: see
If $arg2 is INF or -INF, and $arg1
is not INF or -INF, then the result is zero.
Otherwise, subject to limits of precision and overflow/underflow conditions, the result
is the largest (furthest from zero) xs:integer value $N such
that the following expression is true:
The second term in this condition ensures that the result has the correct sign.
The implementation may adopt a different algorithm provided that it is equivalent to
this formulation in all cases where xs:decimal
division.
A dynamic error is raised
A dynamic error is raised NaN or if $arg1 is INF or
-INF.
Except in situations involving errors, loss of precision, or overflow/underflow, the
result of $a idiv $b is the same as ($a div $b) cast as
xs:integer.
The semantics of this function are different from integer division as defined in programming languages such as Java and C++.
mod operator when
applied to two numeric values.Returns the remainder resulting from dividing $arg1, the dividend, by
$arg2, the divisor.
General rules: see
The operation a mod b for operands that are xs:integer or
xs:decimal, or types derived from them, produces a result such that
(a idiv b) * b + (a mod b) is equal to a and the magnitude of
the result is always less than the magnitude of b. This identity holds even
in the special case that the dividend is the negative integer of largest possible
magnitude for its type and the divisor is -1 (the remainder is 0). It follows from this
rule that the sign of the result is the sign of the dividend.
For xs:float and xs:double operands the following rules
apply:
If either operand is NaN, the result is NaN.
If the dividend is positive or negative infinity, or the divisor is positive or
negative zero (0), or both, the result is NaN.
If the dividend is finite and the divisor is an infinity, the result equals the dividend.
If the dividend is positive or negative zero and the divisor is finite, the result is the same as the dividend.
In the remaining cases, where neither positive or negative infinity, nor positive
or negative zero, nor NaN is involved, the result obeys (a idiv
b)*b+(a mod b) = a.
Division is truncating division, analogous to integer division, not
A dynamic error is raised xs:integer
and xs:decimal operands, if $arg2 is zero.
+ operator
applied to a numeric value.Returns its operand with the sign unchanged: (+ $arg).
General rules: see
The returned value is equal to $arg, and is an instance of
xs:integer, xs:decimal, xs:double, or
xs:float depending on the type of $arg.
Because coercion rules are applied in the normal way, the unary
+ operator can be used to force conversion of an untyped node to a
number: the result of +@price is the same as xs:double(@price)
if the type of @price is xs:untypedAtomic.
- operator when
applied to a numeric value.Returns its operand with the sign reversed: -$arg.
General rules: see
The returned value is an instance of xs:integer, xs:decimal,
xs:double, or xs:float depending on the type of
$arg.
For xs:integer and xs:decimal arguments, 0 and
0.0 return 0 and 0.0, respectively. For
xs:float and xs:double arguments, NaN returns
NaN, 0.0E0 returns -0.0E0 and vice versa.
INF returns -INF. -INF returns
INF.
eq operator when applied to two numeric values, and is also used in defining the
semantics of ne, le and ge.Returns true if and only if the value of $arg1 is equal to the value of
$arg2.
General rules: see
For xs:float and xs:double values, positive zero and negative
zero compare equal. INF equals INF and -INF
equals -INF. If $arg1 or $arg2 is
NaN, the function returns false.
lt operator when applied to two numeric values, and is also used in defining the
semantics of le, gt, and ge.Returns true if and only if $arg1 is numerically less than
$arg2.
General rules: see
For xs:float and xs:double values, positive infinity is
greater than all other non-NaN values; negative infinity is less than all
other non-NaN values. Positive and negative zero compare equal.
If $arg1 or $arg2 is
NaN, the function returns false.
Returns the absolute value of $value.
General rules: see
If $value is negative the function returns -$value, otherwise it
returns $value.
For the four types xs:float,
xs:double, xs:decimal and xs:integer, it is
guaranteed that if the type of $value is an instance of type T then
the result will also be an instance of T. The result $value is an instance of xs:positiveInteger then the value of
$value
For xs:float and xs:double arguments, if the argument is
positive zero or negative zero, then positive zero is returned. If the argument is
positive or negative infinity, positive infinity is returned.
Rounds $value upwards to a whole number.
General rules: see
The function returns the smallest (closest to negative infinity) number with no
fractional part that is not less than $value.
For the four types xs:float,
xs:double, xs:decimal and xs:integer, it is
guaranteed that if the type of $value is an instance of type T then
the result will also be an instance of T. The result $value is an instance of xs:decimal then the result xs:integer.
For xs:float and xs:double arguments, if the argument is
positive zero, then positive zero is returned. If the argument is negative zero, then
negative zero is returned. If the argument is less than zero and greater than -1,
negative zero is returned. If the argument is positive or negative infinity,
the value of the argument is returned.
Rounds $value downwards to a whole number.
General rules: see
The function returns the largest (closest to positive infinity) number with no
fractional part that is not greater than $value.
For the four types xs:float,
xs:double, xs:decimal and xs:integer, it is
guaranteed that if the type of $value is an instance of type T then
the result will also be an instance of T. The result $value is an instance of xs:decimal then the result xs:integer.
For xs:float and xs:double arguments, if the argument is
positive zero, then positive zero is returned. If the argument is negative zero, then
negative zero is returned. If the argument is positive or negative infinity,
the value of the argument is returned.
Rounds a value to a specified number of decimal places, with control over how the rounding takes place.
General rules: see
The function returns a value that is close to $value
and that is a multiple of ten to the power of minus
$precision. The default value of $precision
is zero, in which case the function returns a whole number (but not necessarily
an xs:integer).
The detailed way in which rounding is performed depends on the value of
$mode, as follows. Here L
means the highest multiple of ten to the power
of minus $precision that is less than or equal to $value,
U means the lowest multiple of ten to the power
of minus $precision that is greater than or equal to $value,
N means the multiple of ten to the power
of minus $precision that is numerically closest to $value,
and $value is equal to the arithmetic
mean of L and U.
| Rounding Mode | Meaning |
|---|---|
|
Returns L. |
|
Returns U. |
|
Returns L if |
|
Returns U if |
|
Returns N, unless midway, in which case L. |
|
Returns N, unless midway, in which case U. This is the default. |
|
Returns N, unless midway, in which case it
returns L if |
|
Returns N, unless midway, in which case it
returns U if |
|
Returns N, unless midway, in which case it returns whichever of L and U has a last significant digit that is even. |
For the four types xs:float,
xs:double, xs:decimal and xs:integer, it is
guaranteed that if the type of $value is an instance of type T then
the result will also be an instance of T. The result $value is an instance of xs:decimal and $precision is
less than one, then the result xs:integer.
If the second argument is omitted or is an empty sequence,
the function produces the same result as when
$precision = 0 (that is, it rounds to a whole number).
When $value is of type xs:float and xs:double:
If $value is NaN, positive or negative zero, or positive or negative
infinity, then the result is the same as the argument.
For other values, the argument is cast to xs:decimal using an
implementation of xs:decimal that imposes no limits on the number of
digits that can be represented. The function is applied to this
xs:decimal value, and the resulting xs:decimal is
cast back to xs:float or xs:double as appropriate to
form the function result. If the resulting xs:decimal value is zero,
then positive or negative zero is returned according to the sign of
$value.
There may be $precision is outside this range, it should
be adjusted to the nearest value supported by the implementation.
This function is typically used with a non-zero $precision in financial
applications where the argument is of type xs:decimal. For arguments of
type xs:float and xs:double the results may be
counter-intuitive. For example, consider round(35.425e0, 2). The result is
not 35.43, as might be expected, but 35.42.
This is because the xs:double written as 35.425e0
has an exact value equal to 35.42499999999..., which is closer to
35.42 than to 35.43.
The call round($v, 0, "floor") is equivalent to floor($v).
The call round($v, 0, "ceiling") is equivalent to ceiling($v).
The call round($v, $p, "half-to-even") is equivalent to round-half-to-even($v, $p).
A third argument has been added, providing control over the rounding mode.
It is explicitly stated that the limits for $precision
are implementation-defined.
Rounds a value to a specified number of decimal places, rounding to make the last digit even if two such values are equally near.
General rules: see
The function returns the nearest (that is, numerically closest) value to
$value that is a multiple of ten to the power of minus
$precision. If two such values are equally near (e.g. if the fractional
part in $value is exactly .500...), the function returns the one whose least
significant digit is even.
For the four types xs:float,
xs:double, xs:decimal and xs:integer, it is
guaranteed that if the type of $value is an instance of type T then
the result will also be an instance of T. The result $value is an instance of xs:decimal and $precision
is less than one, then the result xs:integer.
If the second argument is omitted or an empty sequence,
the function produces the same result as the two-argument version with
$precision = 0.
For arguments of type xs:float and xs:double:
If the argument is NaN, positive or negative zero, or positive or
negative infinity, then the result is the same as the argument.
In all other cases, the argument is cast to xs:decimal using an
implementation of xs:decimal that imposes no limits on the number of digits that
can be represented. The function is applied to this xs:decimal value,
and the resulting xs:decimal is cast back to xs:float or
xs:double as appropriate to form the function result. If the
resulting xs:decimal value is zero, then positive or negative zero is
returned according to the sign of the original argument.
There may be $precision is outside this range, it should
be adjusted to the nearest value supported by the implementation.
This function is typically used in financial applications where the argument is of type
xs:decimal. For arguments of type xs:float and
xs:double the results may be counter-intuitive. For example, consider
round-half-to-even(xs:float(150.015), 2).
The result is not 150.02 as might be expected, but 150.01.
This is because the conversion of the
xs:float value represented by the literal 150.015 to an
xs:decimal produces the xs:decimal
value 150.014999389..., which is closer to
150.01 than to 150.02.
From 4.0, the effect of this function can also be achieved by
calling "half-to-even".
It is explicitly stated that the limits for $precision
are implementation-defined.
Divides one xs:decimal by another to a defined precision, returning
both the quotient and the remainder.
The function returns a record with two fields:
quotient is the xs:decimal value
furthest from zero such that:
quotient is an exact multiple of ten to the power
of minus $precision;
the absolute value of quotient
multipled by $divisor is less than or equal to the absolute
value of $value;
the sign of quotient is the same as the sign
of op:numeric-divide($value, $divisor).
remainder is the exact result of subtracting quotient
multiplied by $divisor from $value.
There may be $precision is outside this range, it should
be adjusted to the nearest value supported by the implementation.
A dynamic error is raised $divisor is zero.
New in 4.0.
Formats an integer according to a given picture string, using the conventions of a given natural language if specified.
If $value is an empty sequence, the function returns a zero-length
string.
In all other cases, the $picture argument describes the format in which
$value is output.
The rules that follow describe how non-negative numbers are output. If the value of
$value is negative, the rules below are applied to the absolute value of
$value, and a minus sign is prepended to the result.
The value of $picture consists of the following, in order:
An optional radix, which is an integer in the range 2 to 36, written using ASCII
digits (0-9) without any leading zero;
A circumflex (^), which is present if the radix is present, and absent otherwise.
A circumflex is recognized as marking the presence of a radix only
if (a) it is immediately preceded by an integer
in the range 2 to 36, and (b) it is
followed (somewhere within the primary format token) by an "X"
or "x". In other cases, the circumflex is treated as a grouping separator.
For example, the picture 9^000 outputs the number
2345 as "2^345", whereas 9^XXX outputs "3185".
This rule is to ensure backwards compatibility.
A primary format token. This is always present and
An optional format modifier.
If the string contains one or more semicolons then the last semicolon is taken as terminating the primary format token, and everything that follows is taken as the format modifier; if the string contains no semicolon then the format modifier is taken to be absent (which is equivalent to supplying a zero-length string).
If a radix is present, then the primary format token must follow the rules for a digit-pattern.
The primary format token is classified as one of the following:
A digit-pattern made up of optional-digit-signs, mandatory-digit-signs, and grouping-separator-signs.
The optional-digit-sign is the character #.
0 through 9.
Within the format token, these digits are
interchangeable: a three-digit number may thus be indicated equivalently by
000, 001, or 999.
If the primary format token contains at least one Unicode digit,
then the primary format token is taken
as a decimal digit pattern, and in this case it ^((\p{Nd}|#|[^\p{N}\p{L}])+?)$. If it contains a
digit but does not match this pattern, a dynamic error is raised
"x"
or "X". If any mandatory-digit-sign is upper-case "X", then all
mandatory-digit-signs must be upper-case "X". The digit family
used in the output comprises the first R characters of the
alphabet 0123456789abcdefghijklmnopqrstuvwxyz, but using upper-case
letters in place of lower-case if an upper-case "X" is used
as the mandatory-digit-sign.
In this case the primary format token ^(([Xx#]|[^\p{N}\p{L}])+?)$
a grouping-separator-sign is a non-alphanumeric character, that
is a
If a semicolon is to be used as a grouping separator, then the primary format token as a whole must be followed by another semicolon, to ensure that the grouping separator is not mistaken as a separator between the primary format token and the format modifier.
There
The corresponding output is a number in the specified radix, using this digit family, with at least as many digits as there are mandatory-digit-signs in the format token. Thus:
A format token 1 generates the sequence 0 1
2 ... 10 11 12 ...
A format token 01 (or equivalently,
00 or 99) generates the sequence 00 01 02 ...
09 10 11 12 ... 99 100 101
A format token of ١ then ٢
then ٣ ...
A format token of 16^xx generates the sequence 00 01 02 03
... 08 09 0a 0b 0c 0d 0e 0f 10 11 ...
A format token of 16^X generates the sequence 0 1 2 3
... 8 9 A B C D E F 10 11 ...
The grouping-separator-signs are handled as follows:
The position of grouping separators within the format token, counting backwards from the last digit, indicates the position of grouping separators to appear within the formatted number, and the character used as the grouping-separator-sign within the format token indicates the character to be used as the corresponding grouping separator in the formatted number.
More specifically, the
Grouping separators are defined to be
There is at least one grouping separator.
Every grouping separator is the same character (call it C).
There is a positive integer G (the grouping size) such that:
The position of every grouping separator is an integer multiple of G, and
Every positive integer multiple of G that is less than the number of optional-digit-signs and mandatory-digit-signs in the primary format token is the position of a grouping separator.
The
If grouping separators are regular, then the grouping separator template contains one pair of the form (n×G, C)
for every positive integer n where G is the grouping size and C is the grouping character.
Otherwise (when grouping separators are not regular), the grouping separator template contains one pair of the form
(P, C) for every grouping separator found in the primary formatting token, where C is the grouping
separator character and P is its position.
If there are no grouping separators, then the grouping separator template is an empty set.
The number is formatted as follows:
Let S/1 be the result of formatting the supplied number
xs:string.
Let S/2 be the result of padding S/1 on the left with as many leading zeroes as are needed to ensure that it contains at least as many digits as the number of mandatory-digit-signs in the primary format token.
Let S/3 be the result of replacing all decimal digits (0-9) in S/2 with the corresponding
digits from the selected digit family.
Let S/4 be the result of inserting grouping separators into S/3: for every (position P, character C) pair in the grouping separator template where P is less than the number of digits in S/3, insert character C into S/3 at position P, counting from the right-hand end.
Let S/5 be the result of converting S/4 into ordinal form, if an ordinal modifier is present, as described below.
The result of the function is then S/5.
The format token A, which generates the sequence A B C ... Z AA
AB AC....
The format token a, which generates the sequence a b c ... z aa
ab ac....
The format token i, which generates the sequence i ii iii iv v
vi vii viii ix x ....
The format token I, which generates the sequence I II III IV V
VI VII VIII IX X ....
The format token w, which generates numbers written as lower-case
words, for example in English, one two three four ...
The format token W, which generates numbers written as upper-case
words, for example in English, ONE TWO THREE FOUR ...
The format token Ww, which generates numbers written as title-case
words, for example in English, One Two Three Four ...
Any other format token, which indicates a numbering sequence in which that token
represents the number 1 (one) (but see the note below).
It is 1.
In some traditional numbering sequences additional signs are added to denote
that the letters should be interpreted as numbers, for example, in ancient Greek
For all format tokens other than a digit-pattern, there
1.
The above expansions of numbering sequences for format tokens such as a and
i are indicative but not prescriptive. There are various conventions in
use for how alphabetic sequences continue when the alphabet is exhausted, and differing
conventions for how roman numerals are written (for example, IV versus
IIII as the representation of the number 4). Sometimes alphabetic
sequences are used that omit letters such as i and o. This
specification does not prescribe the detail of any sequence other than those sequences
consisting entirely of decimal digits.
Many numbering sequences are language-sensitive. This applies especially to the sequence
selected by the tokens w, W and Ww. It also
applies to other sequences, for example different languages using the Cyrillic alphabet
use different sequences of characters, each starting with the letter $language argument specifies which
language conventions are to be used. If the argument is specified, the value
xml:lang attribute (see
The set of languages for which numbering is supported is $language argument is absent, or is
set to an empty sequence, or is invalid, or is not a language supported by the
implementation, then the number is formatted using the default language from the dynamic
context.
The format modifier ^([co](\(.+\))?)?[at]?$. That is, if it is present it must
consist of one or more of the following, in order:
either c or o, optionally followed by a sequence of
characters enclosed between parentheses, to indicate cardinal or ordinal numbering
respectively, the default being cardinal numbering
either a or t, to indicate alphabetic or traditional
numbering respectively, the default being
If the o modifier is present, this indicates a request to output ordinal
numbers rather than cardinal numbers. For example, in English, when used with the format
token 1, this outputs the sequence 1st 2nd 3rd 4th ..., and
when used with the format token w outputs the sequence first second
third fourth ....
The string of characters between the parentheses, if present, is used to select between
other possible variations of cardinal or ordinal numbering sequences. The interpretation
of this string is
It is
The use of the a or t modifier disambiguates between numbering
sequences that use letters. In many languages there are two commonly used numbering
sequences that use letters. One numbering sequence assigns numeric values to letters in
alphabetic sequence, and the other assigns numeric values to each letter in some other
manner traditional in that language. In English, these would correspond to the numbering
sequences specified by the format tokens a and i. In some
languages, the first member of each sequence is the same, and so the format token alone
would be ambiguous. In the absence of the a or t modifier, the
default is
A dynamic error is raised
Note the careful distinction between conditions that are errors and conditions where fallback occurs. The principle is that an error in the syntax of the format picture will be reported by all processors, while a construct that is recognized by some implementations but not others will never result in an error, but will instead cause a fallback representation of the integer to be used.
The following notes apply when a digit-pattern is used:
If grouping-separator-signs
appear at regular intervals within the format token, then the sequence is extrapolated to
the left, so grouping separators will be used in the formatted number at every
multiple of N. For example, if the format token is 0'000
then the number one million will be formatted as 1'000'000, while the
number fifteen will be formatted as 0'015.
The only purpose of optional-digit-signs is to mark the position of
grouping-separator-signs. For example, if the format token is
#'##0 then the number one million will be formatted as
1'000'000, while the number fifteen will be formatted as
15. A grouping separator is included in the formatted number only
if there is a digit to its left, which will only be the case if either (a) the
number is large enough to require that digit, or (b) the number of
mandatory-digit-signs in the format token requires insignificant
leading zeros to be present.
Grouping separators are (365)123-9876. In general they are not
suitable for such purposes because (a) only single characters are allowed, and (b) they
cannot appear at the beginning or end of the number.
Numbers will never be truncated. Given the digit-pattern
01, the number three hundred will be output as 300,
despite the absence of any optional-digit-sign.
The following notes apply when ordinal numbering is selected using the o modifier.
In some languages, the form of numbers (especially ordinal numbers) varies depending
on the grammatical context: they may have different genders and may decline with the
noun that they qualify. In such cases the string appearing in parentheses after the
letter c or o may be used to indicate the variation of the
cardinal or ordinal number required.
The way in which the variation is indicated will depend on the conventions of the language.
For inflected languages that vary the ending of the word, the approach recommended
in the previous version of this specification was to indicate the required ending,
preceded by a hyphen: for example in German, appropriate values might be
o(-e), o(-er), o(-es), o(-en).
Another approach, which might usefully be adopted by an implementation based on the
open-source ICU localization library o(%spellout-ordinal-masculine), or c(%spellout-cardinal-year).
The following notes apply when the primary format token is neither a digit-pattern nor one of the seven other defined format tokens (A, a, i, I, w, W, Ww), but is an arbitrary token representing the number 1:
Unexpected results may occur for traditional numbering. For example, in an
implementation that supports traditional numbering system in Greek, the example
format-integer(19, "α;t") might return δπιιιι or
ιθ, depending upon whether the ancient acrophonic or late antique
alphabetic system is supported.
Unexpected results may also occur for alphabetic numbering. For example, in an
implementation that supports alphabetic numbering system in Greek, someone
writing format-integer(19, "α;a") might expect the nineteenth Greek
letter, format-integer(18, "Α;a") might expect the eighteenth Greek capital letter,
format-integer(123, 'w') might return "one hundred and
twenty-three"
Ordinal numbering in Italian: The specification "1;o(-º)" with $language equal to
it, if supported, should produce the sequence:
The specification "Ww;o" with $language equal to
it, if supported, should produce the sequence:
format-integer(14, 'Ww;o(-e)', 'de') might return
"Vierzehnte"
The function has been extended to allow output in a radix other than 10, for example in hexadecimal.
Returns a string containing a number formatted according to a given picture string and decimal format.
The function formats $value as a string using the $picture argument and a decimal format.
The $value argument may be of any numeric data type
(xs:double, xs:float, xs:decimal, or their
subtypes including xs:integer). Note that if an xs:decimal is
supplied, it is not automatically converted to an xs:double, as such
conversion can involve a loss of precision.
If the supplied value of the $value argument is an empty sequence, the
function behaves as if the supplied value were the xs:double value
NaN.
If $options is absent, or if it is supplied as an empty sequence or an empty
map, then the number is formatted using the properties of the unnamed
decimal format in the static context.
For backwards compatibility reasons, the decimal format can be supplied as
an instance of xs:string. If the value of the $options
argument is an xs:string, then its value
EQName
as defined in the XPath 4.0 grammar, that is one of the following:
A lexical QName, which is expanded using the statically known namespaces. The default namespace is not used (no prefix means no namespace).
A URIQualifiedName using the syntax Q{uri}local,
where the URI can be zero-length to indicate a name in no namespace.
The effective value of the $options argument is then the map
{ 'format-name': $FN } where $FN is the
xs:QName result of expanding this EQName.
The entries that may appear in the $options map are as follows.
The
In the table, the type xs:string (: matching '.' :)
represents a single-character string, that is, a restriction of xs:string
with the facet pattern=".", while the type
xs:string (: matching '.|.:.*' :) indicates a string
that is either a single character, or a single character followed by
The default value for absent options (other than
format-name) is taken from a decimal format in the static context; the default
values shown in the table are the values used if no specific value is assigned in the
static context.
xs:NCName
represents the local part of an xs:QName in no namespace.
NaN
in the formatted number.0 then any of the
digits 0 to 9 may be used (interchangeably)
in the picture string to represent a mandatory digit,
and in the formatted number the characters 0 to 9
will be used to represent the digits zero to nine. The value must be
a character in Unicode category Nd with decimal digit value 0 (zero).
A base decimal format is established as follows:
If the format-name option is present, then
the decimal format in the static context identified by this name.
Otherwise, the unnamed decimal format in the static context.
The base decimal format is then modified using the other entries in the
supplied $options map.
The evaluation of the
The analysis phase takes as its inputs the
The result of the function is the formatted string representation of the supplied number.
A dynamic error is raised $options argument is supplied as an xs:string
that isURIQualifiedName, or if it uses a prefix that is not found in the
statically known namespaces; or if the static context does not contain a declaration of
a decimal format with a matching expanded QName; or if $options?format-name
is present and the static context does
not contain a declaration of a decimal format whose name matches $options?format-name.
If the processor is able to detect the
error statically (for example, when the argument is supplied as a string literal), then
the processor
A dynamic error is raised $format is not valid for the associated property, or if the properties
of the decimal format resulting from a supplied $options
map do not have distinct values.
A string is an ordered sequence of characters, and this specification uses terms such as “left” and “right”, “preceding” and “following” in relation to this ordering, irrespective of the position of the characters when visually rendered on some output medium. Both in the picture string and in the result string, digits with higher significance (that is, representing higher powers of ten) always precede digits with lower significance, even when the rendered text flow is from right to left.
In previous versions of XSLT and XQuery, decimal formats were typically defined in the
static context using custom declarations (<xsl:decimal-format> in XSLT,
declare decimal-format in XQuery) and then selected by name in a call on
$options argument of the
The following examples assume a default decimal format in which the chosen digits are
the ASCII digits 0-9, the decimal separator is ., the grouping separator is ,,
the minus-sign is -, and the percent-sign is %.
The following examples assume the existence of a decimal format named
de in which the grouping separator is . and the
decimal separator is ,:
The following examples assume that the exponent separator
in decimal format fortran is E:
The decimal format name can now be supplied
as a value of type xs:QName,
as an alternative to supplying a lexical QName as an instance of xs:string.
Decimal format parameters can now be supplied directly as a map in the third argument, rather than referencing a format defined in the static context.
For selected properties including percent and exponent-separator,
it is now possible to specify a single-character marker to be used in the picture string,
together with a multi-character rendition to be used in the formatted output.
Converts a string to an integer, recognizing any radix in the range 2 to 36.
If $value is an empty sequence, the result is an empty sequence.
The supplied $radix must be in the range 2 to 36 inclusive.
The string $value is preprocessed by stripping all whitespace characters (including internal whitespace)
and underscore characters.
After this process, the supplied value
must consist of an optional sign (+ or -)
followed by a sequence of one or more generalized digits drawn from the first $radix characters
in the alphabet 0123456789abcdefghijklmnopqrstuvwxyz; upper-case alphabetics
A-Z may be used in place of their lower-case equivalents.
The value of a generalized digit corresponds to its position in this alphabet.
A dynamic error is raised $radix is not in the range 2 to 36.
A dynamic error is raised $value is a zero-length string,
or if it contains a character
that is not among the first $radix characters in the
alphabet 0123456789abcdefghijklmnopqrstuvwxyz, or the
upper-case equivalent of such a character.
A dynamic error is raised xs:integer.
When $radix takes its default value of 10,
the function delivers the same result as casting $value
(after removal of whitespace and underscores) to xs:integer.
If underscores or whitespace in the input need to be rejected, then
the string should first be validated, perhaps using
If other characters may legitimately appear in the input, for example
a leading 0x, then this must first be removed by pre-processing the input.
If the input uses a different family of digits, then the value should first
be converted to the required digits using
A string in the lexical space of xs:hexBinary will always
be an acceptable input, provided it is not too long. So, for example, the expression
"1DE=" => xs:base64Binary() => xs:hexBinary() => xs:string() => parse-integer(16)
can be used to convert the Base 64 value 1DE= to the integer 54321, via the
hexadecimal string D431.
Alphabetic base-26 numbering systems (hexavigesimal) can be parsed via translation. Note, enumerating systems that do not assign a symbol to zero (e.g., spreadsheet columns) must be preprocessed in a different fashion.
Digit-based numeration systems comparable to the Arabic numbers 0 through 9 can be parsed via translation.
New in 4.0
Returns an approximation to the mathematical constant π.
This function returns the xs:double value whose lexical representation is
3.141592653589793e0
The expression 60 * (math:pi() div 180) converts an angle of 60 degrees
to radians.
Returns an approximation to the mathematical constant e.
This function returns the xs:double value whose lexical representation is
2.718281828459045e0
New in 4.0
Returns the value of ex where x is the argument value.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is the mathematical constant e raised to the power of
$value, as defined in the exp function applied to 64-bit binary floating point values.
The treatment of overflow and underflow is defined in
Returns the value of 10x, where x is the supplied argument value.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is ten raised to the power of $value, as defined in the
exp10 function applied
to 64-bit binary floating point values.
The treatment of overflow and underflow is defined in
Returns the natural logarithm of the argument.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is the natural logarithm of $value, as defined in the
log function applied
to 64-bit binary floating point values.
The treatment of divideByZero and invalidOperation exceptions
is defined in -INF, and if it is negative, the result is NaN
Returns the base-ten logarithm of the argument.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is the base-10 logarithm of $value, as defined in the
log10 function applied
to 64-bit binary floating point values.
The treatment of divideByZero and invalidOperation exceptions
is defined in -INF, and if it is negative, the result is NaN
Returns the non-negative square root of the argument.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is the mathematical non-negative square root of $value
as defined in the squareRoot function applied to 64-bit binary floating point values.
The treatment of the invalidOperation exception is defined in NaN.
If $value is positive or negative zero, positive infinity, or
NaN, then the result is $value. (Negative zero is the only
case where the result can have negative sign)
Returns the result of raising the first argument to the power of the second.
If $x is the empty sequence, the function returns the empty sequence.
If $y is an instance of xs:integer, the result is
$x raised to the power of $y as defined in the pown function applied to a
64-bit binary floating point value and an integer.
Otherwise $y is cast to an xs:double,
and the result is $x raised to the power of
$y as defined in the pow function applied to two 64-bit binary floating point values.
The treatment of the divideByZero and invalidOperation
exceptions is defined in
Returns the sine of the argument. The argument is an angle in radians.
If $radians is the empty sequence, the function returns the empty
sequence.
Otherwise the result is the sine of $radians (which is treated as an angle in
radians) as defined in the sin function applied to 64-bit binary floating point values.
The treatment of the invalidOperation and underflow exceptions
is defined in
If $radians is positive or negative zero, the result is
$radians.
If $radians is positive or negative infinity, or NaN,
then the result is NaN.
Otherwise the result is always in the range -1.0e0 to +1.0e0
Returns the cosine of the argument. The argument is an angle in radians.
If $radians is the empty sequence, the function returns the empty
sequence.
If $radians is positive or negative infinity, or NaN,
then the result is NaN.
Otherwise the result is the cosine of $radians (which is treated as an angle in
radians) as defined in the cos function applied to 64-bit binary floating point values.
The treatment of the invalidOperation exception is defined in
If $radians is positive or negative zero, the result is
$radians.
If $radiansis positive or negative infinity, or NaN,
then the result is NaN.
Otherwise the result is always in the range -1.0e0 to +1.0e0
Returns the tangent of the argument. The argument is an angle in radians.
If $radians is the empty sequence, the function returns the empty
sequence.
Otherwise the result is the tangent of $radians (which is treated as an angle
in radians) as defined in the tan function applied to 64-bit binary floating point values.
The treatment of the invalidOperation and underflow exceptions
is defined in
If $radians is positive or negative infinity, or NaN,
then the result is NaN.
math:pi() div 2
returns an approximation, the result of math:tan(math:pi() div 2) will be a large
but finite number.-math:pi() div 2
returns an approximation, the result of math:tan(-math:pi() div 2) will be a large
but finite negative number.Returns the arc sine of the argument.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is the arc sine of $value as defined in the asin function applied to 64-bit binary floating point values.
The result is in the range -π/2 to +π/2 radians.
The treatment of the invalidOperation and underflow exceptions
is defined in
If $value is positive or negative zero, the result is $value.
If $value is NaN, or if its absolute value is greater than one,
then the result is NaN.
In other cases, the result is an xs:double value representing an angle
θ in radians in the range -math:pi() div 2 <=
θ <= math:pi() div 2.
Returns the arc cosine of the argument.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is the arc cosine of $value, as defined in the acos function applied to 64-bit binary floating point values.
The result is in the range zero to +π radians.
The treatment of the invalidOperation exception is defined in
If $value is NaN, or if its absolute value is greater than one,
then the result is NaN.
In other cases, the result is an xs:double value representing an angle
θ in radians in the range 0 <= θ <=
math:pi().
Returns the arc tangent of the argument.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise the result is the arc tangent of $value, as defined
in the atan function applied to 64-bit binary floating point values.
The result is in the range -π/2
to +π/2 radians.
The treatment of the underflow exception is defined in
If $value is positive or negative zero, the result is $value.
If $value is NaN then the result is NaN.
In other cases, the result is an xs:double value representing an angle
θ in radians in the range -math:pi() div 2 <=
θ <= math:pi() div 2.
Returns the angle in radians subtended at the origin by the point on a plane with coordinates (x, y) and the positive x-axis.
The result is the value of atan2(y, x) as defined in the atan2 function applied to
64-bit binary floating point values. The result is in the range -π
to +π radians.
The treatment of the underflow exception is defined in
If either argument is NaN then the result is NaN.
If $x is positive, then the value of
atan2($y, $x) is atan($y div $x).
If $x is negative, then:
If $y is positive, then the value of atan2($y, $x) is
atan($y div $x) + π.
If $y is negative, then the value of atan2($y, $x) is
atan($y div $x) - π.
Some results for special values of the arguments are shown in the examples below.
Returns the hyperbolic sine of the argument.
If $value is the empty sequence, the function returns the empty
sequence.
Otherwise the result is the hyperbolic sine of $value as defined in the
sinh function applied
to 64-bit binary floating point values.
The treatment of the overflow and underflow exceptions
is defined in
If $value is positive or negative zero, the result is
$value.
If $value is positive or negative infinity, or NaN,
the result is NaN.
New in 4.0
Returns the hyperbolic cosine of the argument.
If $value is the empty sequence, the function returns the empty
sequence.
Otherwise the result is the hyperbolic cosine of $value as defined in the
cosh function applied
to 64-bit binary floating point values.
The treatment of the overflow exception
is defined in
If $value is positive or negative zero, the result is
1.
If $value is positive or negative infinity,
the result is INF.
If $value is NaN,
the result is NaN.
In other cases, the result is an xs:double in the range
+1.0 to INF.
New in 4.0
Returns the hyperbolic tangent of the argument.
If $value is the empty sequence, the function returns the empty
sequence.
Otherwise the result is the hyperbolic tangent of $value as defined in the
tanh function applied
to 64-bit binary floating point values.
The treatment of the underflow exception
is defined in
If $value is positive or negative zero, the result is
$value.
If $value is positive infinity, the result is +1.0.
If $value is negative infinity, the result is -1.0.
In other cases, the result is an xs:double in the range
-1.0 to +1.0.
New in 4.0
Returns an xs:string whose characters have supplied
The function returns the string made up from the $values. This will be the zero-length string if $values
is the empty sequence.
A dynamic error is raised $values is not a
It is no longer automatically an error if the input
contains a codepoint that is not valid in XML. Instead, the codepoint
must be a
Returns the sequence of xs:string value.
The function returns a sequence of integers, each integer being the Unicode $value.
If $value is a zero-length string or the empty sequence, the function returns
the empty sequence.
Returns -1, 0, or 1, depending on whether
the first value is less than, equal to, or greater than the second value.
Compares two atomic items $value1 and $value2 for order, and
returns the integer value -1, 0, or 1,
depending on whether $value1 is less than, equal to, or greater than
$value2, respectively.
This function differs from the operators lt, eq,
and gt in that decimal values are not converted to doubles. This means that
the comparison is fully transitive, which makes it safe for use in sorting algorithms.
It is used to underpin sorting in XQuery 4.0 and XSLT 4.0, and is also available as a
free-standing function in its own right.
If either $value1 or $value2 is the empty sequence,
the function returns the empty sequence.
Otherwise, the result is determined as follows:
If $value1 is an instance of xs:string,
xs:anyURI or xs:untypedAtomic, and if
$value2 is an instance of xs:string, xs:anyURI
or xs:untypedAtomic, the values are compared as strings, and the
result reflects the order according to the rules of the collation that is used.
The collation is determined according to the rules in
eq, ne,
gt, lt, le and ge
operators on xs:string values.
If both $value1 and $value2 are instances of
xs:numeric, the function relies on a total order, which is
defined as follows:
A value $f of type xs:float is in all cases equal
to the value xs:double($f). The remaining rules therefore only consider
instances of xs:double and xs:decimal.
NaN is equal to itself and less than any other value.
Negative infinity is equal to itself and less than any other
value except NaN.
Positive infinity is equal to itself and greater than any other value.
Negative zero is equal to positive zero.
Other xs:double and xs:decimal values (that is,
values other than the infinities, NaN, and negative zero) are ordered
according to their mathematical magnitude, the comparison being done without any
rounding or loss of precision. This effect can be achieved by converting
xs:double values to xs:decimal using an implementation
of xs:decimal that imposes no limits on precision or scale, or an
implementation whose limits are such that all xs:double values can
be represented precisely.
If both $value1 and $value2 are instances of
xs:boolean, then:
-1 is returned if
op:boolean-less-than($value1, $value2) returns true.
0 is returned if
op:boolean-equal($value1, $value2) returns true.
1 is returned otherwise.
If $value1 is an instance of xs:hexBinary or
xs:base64Binary, and if $value2 is an instance of
xs:hexBinary or xs:base64Binary, then:
-1 is returned if
op:binary-less-than($value1, $value2) returns true.
0 is returned if
op:binary-equal($value1, $value2) returns true.
1 is returned otherwise.
If both $value1 and $value2 are instances of
xs:date, then:
-1 is returned if
op:date-less-than($value1, $value2) returns true.
0 is returned if
op:date-equal($value1, $value2) returns true.
1 is returned otherwise.
If both $value1 and $value2 are instances of
xs:time, then:
-1 is returned if
op:time-less-than($value1, $value2) returns true.
0 is returned if
op:time-equal($value1, $value2) returns true.
1 is returned otherwise.
If both $value1 and $value2 are instances of
xs:dateTime, then:
-1 is returned if
op:dateTime-less-than($value1, $value2) returns true.
0 is returned if
op:dateTime-equal($value1, $value2) returns true.
1 is returned otherwise.
If both $value1 and $value2 are instances of
xs:dayTimeDuration, then:
-1 is returned if
op:dayTimeDuration-less-than($value1, $value2) returns true.
0 is returned if
op:duration-equal($value1, $value2) returns true.
1 is returned otherwise.
If both $value1 and $value2 are instances of
xs:yearMonthDuration, then:
-1 is returned if
op:yearMonthDuration-less-than($value1, $value2) returns true.
0 is returned if
op:duration-equal($value1, $value2) returns true.
1 is returned otherwise.
For any other combination of types, a type error
For numeric values, consider the xs:double value written as
0.1e0 and the xs:decimal value written as 0.1:
The mathematical magnitude of this xs:double value is
0.1000000000000000055511151231257827021181583404541015625.
Therefore, compare(0.1e0, 0.1) returns +1. By contrast,
0.1e0 lt 0.1 is false and 0.1e0 eq 0.1
is true, because those expressions convert the xs:decimal value
0.1 to the xs:double value 0.1e0
before the comparison.
Although operations such as sorting and the NaN differently.
ssand the German letter
ß.
ssand the German letter
ß.
The function has been expanded in scope to handle comparison of values other than strings.
The spec has been corrected to note that the function depends on the implicit timezone.
Returns true if two strings are equal, considered codepoint-by-codepoint.
If either argument is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns true or false depending on
whether $value1 is equal to
$value2, according to the Unicode codepoint collation
(http://www.w3.org/2005/xpath-functions/collation/codepoint).
This function allows xs:anyURI values to be compared without having to
specify the Unicode codepoint collation.
|| operator.Returns the concatenation of the arguments, treated as sequences of strings.
Unlike all other functions, this function is defined to be variadic, as indicated by the ellipsis in the function signature. Conceptually, there is an infinite set of functions with different numbers of arguments (minimum arity zero, maximum arity unbounded):
concat() returns a zero-length string, "".
concat("a") returns "a".
concat("a", "b") returns "ab".
concat("a", "b", "c") returns "abc".
concat("a", "b", "c", "d") returns "abcd".
and so on.
It is equally possible to supply a single argument containing a sequence of strings:
concat(()) returns a zero-length string, "".
concat(("a")) returns "a".
concat(("a", "b")) returns "ab".
concat(("a", "b", "c")) returns "abc".
concat(("a", "b", "c", "d")) returns "abcd".
and so on.
More generally, any argument can be a sequence of strings:
concat(("a", "b"), "c") returns "abc".
concat(("a", "b"), (), ("c", "d")) returns "abcd".
A static call on the
Each of the parameters has the required type
xs:anyAtomicType*. The coercion rules ensure that each supplied argument is first converted to
a sequence of atomic items by applying atomization. These sequences are then combined (by
If XPath 1.0 compatibility mode is set to true in the static context of a
static function call to $v is first reduced to a single
string, the result of the expression xs:string($v[1]). This is special-case
processing for the
A named function reference can be used to create a function item with any arity: for example
concat#3 returns a function item that takes three arguments, which it concatenates.
Similarly partial function application can be used to construct a function that concatenates fixed and
variable values: for example concat('[', ?, ']') returns a function item that takes a single
argument and wraps the string value of this argument in square brackets. Similarly,
concat(?, '-', ?) returns a function item of arity two; it returns the string values of
the two arguments separated by a hyphen.
As mentioned in xs:string
returned by
where the ? represents either the actual Unicode character ̈, will return:
"I plan to go to Mu?nchen in September"
where the ? again represents either the actual Unicode character ̈.
It is worth noting that the returned value is not normalized in NFC; however, it is normalized in NFD.
However, the following XQuery:
where ? represents either the actual Unicode character ̈, will return:
"I plan to go to München in September"
This returned result is normalized in NFC.
Alternatives to the || (for example $x || '-' || $y), the use of string templates
(for example `{ $x }-{ $y }`), and the
The function can now take any number of arguments (previously it had to be two or more), and the arguments can be sequences of strings rather than single strings.
Returns a string created by concatenating the items in a sequence, with a defined separator between adjacent items.
If the second argument is omitted or an empty sequence, the effect is the same as
calling the two-argument version with $separator set to a zero-length
string.
The coercion rules ensure that the supplied $values argument is first converted to
a sequence of atomic items by applying atomization.
The function then returns an xs:string created by casting each item
in the atomized sequence to an xs:string,
and then concatenating the result strings in order,
using the value of $separator as a
separator between adjacent strings. If $separator is the zero-length
string, then the items in $values are concatenated without a separator.
If $values is the empty sequence, the function returns the
zero-length string.
Returns the part of $value beginning at the position
indicated by $start and continuing for the number of $length.
If $value is the empty sequence, the function returns
the zero-length string.
Otherwise, the function returns a string comprising those $value whose index position (counting
from one) is greater than or equal to $start (rounded to an
integer), and (if $length is specified
$start and $length (both rounded to integers).
The characters returned do not extend beyond $value. If
$start is zero or negative, only those characters in positions greater
than zero are returned.
More specifically, the three argument version of the function returns the characters in
$value whose position $p satisfies:
fn:round($start) <= $p and $p < fn:round($start) + fn:round($length)
The two argument version of the function assumes that $length is infinite
and thus returns the $value whose position $p satisfies:
fn:round($start) <= $p
In the above computations, the rules for op:numeric-less-than
The first character of a string is located at position 1, not position 0.
The second and third arguments allow xs:double values (rather than
requiring xs:integer) in order to achieve compatibility with XPath 1.0.
A surrogate pair counts as one character, not two.
The consequences of supplying values such as NaN or positive or negative
infinity for the $start or $length arguments follow from the
above rules, and are not always intuitive.
$sourceString are selected.0 div 0E0 returns NaN, and
NaN compared to any other number returns false, no
characters are selected.INF are selected.-INF + INF is NaN, no
characters are selected.The third argument can now be supplied as an empty sequence.
Returns the number of
The function returns an xs:integer equal to the length in $value.
Calling the zero-argument version of the function is equivalent to calling
fn:string-length(fn:string(.)).
If $value is the empty sequence, the function returns the
xs:integer value 0.
If $value is not specified and the context value is
As a consequence of the rules given above, a type error is raised
Unlike some programming languages, a
There are situations where fn:string-length() has a different effect
from fn:string-length(.). For example, if the context value
is an attribute node typed as an xs:integer with the string value 000001,
then fn:string-length() returns 6
(the length of the string value of the node), while
fn:string-length(.) raises a type error (because the result of atomization
is not an xs:string).
Returns $value with leading and trailing whitespace removed, and
sequences of internal whitespace reduced to a single space character.
If $value is the empty sequence, the function returns the
zero-length string.
The function returns a string constructed by stripping leading and trailing whitespace
from $value, and replacing sequences of one or more adjacent
whitespace characters with a single space,
The whitespace characters are defined in the metasymbol S (Production 3) of
If no argument is supplied, then $value defaults to the string value
(calculated using .).
If no argument is supplied and the context value is
As a consequence of the rules given above, a type error is raised
The definition of whitespace is unchanged in
S ::= (#x20 | #x9 | #xD | #xA)+
Returns $value after applying Unicode normalization.
If $value is the empty sequence, the function returns the
zero-length string.
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument version with $form set to the string
"NFC".
Otherwise, the function returns $value normalized according to
the rules of the normalization form identified by the value of
$form.
The effective value of $form is the value of the expression
fn:upper-case(fn:normalize-space($form)).
If the effective value of $form is NFC
,
then the function returns $value converted to Unicode
Normalization Form C (NFC).
If the effective value of $form is NFD
,
then the function returns $value converted to Unicode
Normalization Form D (NFD).
If the effective value of $form is NFKC
,
then the function returns $value in Unicode Normalization
Form KC (NFKC).
If the effective value of $form is NFKD
,
then the function returns $value converted to Unicode
Normalization Form KD (NFKD).
If the effective value of $form is
FULLY-NORMALIZED
, then the function returns
$value converted to fully normalized form.
If the effective value of $form is the zero-length
string, no normalization is performed and $value is returned.
Normalization forms NFC, NFD, NFKC, and NFKD, and the algorithms to be used for
converting a string to each of these forms, are defined in
The motivation for normalization form FULLY-NORMALIZED is explained in
A string is
A composing character is a character that is one or both of the following:
the second character in the canonical decomposition mapping of some
character that is not listed in the Composition Exclusion Table defined in
of non-zero canonical combining class (as defined in
A string is converted to FULLY-NORMALIZED form as follows:
if the first character in the string is a composing character, prepend a single space (x20);
convert the resulting string to normalization form NFC.
Conforming implementations NFC and
NFD, NFKC, NFKD, and
FULLY-NORMALIZED. They
It is
A $form argument is not one of the values
supported by the implementation.
Converts a string to upper case.
If $value is the empty sequence, the zero-length string is
returned.
Otherwise, the function returns $value after translating every
Case mappings may change the length of a string. In general, the
fn:lower-case(fn:upper-case($s)) is not guaranteed to
return $s, nor is fn:upper-case(fn:lower-case($s)). The
character
These functions may not always be linguistically appropriate (e.g. Turkish i without dot) or appropriate for the application (e.g. titlecase). In cases such as Turkish, a simple translation should be used first.
Because the function is not sensitive to locale, results will not always match user
expectations. In Quebec, for example, the standard uppercase equivalent of è is È,
while in metropolitan France it is more commonly E; only one of these is supported by
the functions as defined.
Many characters of class Ll lack uppercase equivalents in the Unicode case mapping tables; many characters of class Lu lack lowercase equivalents.
Converts a string to lower case.
If t$value is the empty sequence, the zero-length string is
returned.
Otherwise, the function returns $value after translating every
Case mappings may change the length of a string. In general, the
fn:lower-case(fn:upper-case($s)) is not guaranteed to
return $s, nor is fn:upper-case(fn:lower-case($s)). The
character
These functions may not always be linguistically appropriate (e.g. Turkish i without dot) or appropriate for the application (e.g. titlecase). In cases such as Turkish, a simple translation should be used first.
Because the function is not sensitive to locale, results will not always match user
expectations. In Quebec, for example, the standard uppercase equivalent of è is È,
while in metropolitan France it is more commonly E; only one of these is supported by
the functions as defined.
Many characters of class Ll lack uppercase equivalents in the Unicode case mapping tables; many characters of class Lu lack lowercase equivalents.
Returns $value modified by replacing or removing individual
characters.
If $value is the empty sequence, the function returns the
zero-length string.
Otherwise, the function returns a result string constructed by processing each $value, in order,
according to the following rules:
If the character does not appear in $replace then it
is added to the result string unchanged.
If the character first appears in $replace at some
position $with is
$with is added to the result string.
If the character first appears in $replace at some
position $with is less than
If $replace is the zero-length string then the function returns
$value unchanged.
If a character occurs more than once in $replace, then the first
occurrence determines the action taken.
If $with is longer than $replace, the excess
characters are ignored.
Returns the results of a specified hash, checksum, or cyclic redundancy check function applied to the input.
If $value is the empty sequence, the function returns the empty sequence.
If $value is an instance of xs:string, it is converted to a sequence
of octets on the basis of UTF-8 encoding. If $value is an instance of
xs:base64Binary or xs:hexBinary, it is converted to a sequence of
octets.
The $algorithm argument, if present, determines the algorithm to be used to
calculate a checksum, hash, or cyclic redundancy check. If empty or absent,
MD5 will be used. The effective value of the algorithm is determined by
passing the value through fn:upper-case(fn:normalize-space()).
Conforming implementations
MD5: the MD5 Message-Digest algorithm, defined by
SHA-1: the SHA-1 algorithm, defined by
SHA-256: the SHA-256 algorithm, defined by
BLAKE3: the BLAKE3 algorithm defined by
CRC-32: the CRC-32 algorithm, defined by xs:hexBinary value representing this integer in
big-endian order (that is, most significant byte first).
Some libraries, notably System.IO.Hashing.Crc32 in .NET, return
the result in little-endian order.
Conforming implementations $options argument, if present, defines additional parameters
controlling how the process is conducted.
The function returns as xs:hexBinary the octets returned by passing
$value as an octet sequence through the selected algorithm.
The process is followed even if the input octet sequence is empty.
A dynamic error is raised algorithm is not one of the values supported by the implementation.
It is common for secure algorithms to be cryptographically broken, as has happened to
the algorithms MD5, SHA-1, and SHA-256.
And the CRC-32 algorithm is not intended for cryptographic purposes.
Developers are responsible for ensuring that the algorithm chosen meets any expected
security protocols, if relevant.
The BLAKE3 algorithm is included in the list of hashing algorithms
because at the time of writing it appears to be a promising candidate as a secure and
fast algorithm that shows signs of gaining widespread support.
However, this is a fast moving field and the community group recognizes that this
decision might eventually not stand the test of time.
As the technology evolves in the future, implementations are free to drop support
for this algorithm and substitute another that appears to better meet requirements.
Additional security practices, such as salting, may be applied as a preprocessing step,
or fn:hash() can be incorporated into more complex functions.
In most cases, the xs:hexBinary output of the function will be sought in
string form. Because of serialization rules, casting to a string renders the hash in
uppercase, and rendering in lowercase (as adopted by
New in 4.0
Encodes reserved characters in a string that is intended to be used in the path segment of a URI.
If $value is the empty sequence, the function returns the zero-length
string.
This function applies the URI escaping rules defined in section 2 of xs:string supplied as $value. The
effect of the function is to escape reserved characters. Each such character in the
string is replaced with its percent-encoded form as described in
Since
All characters are escaped except those identified as “unreserved” by A to Z,
the digits 0 to 9, HYPHEN-MINUS (-),
LOW LINE (_), FULL STOP (.), and TILDE (~).
This function escapes URI delimiters and therefore cannot be used indiscriminately to encode “invalid” characters in a path segment.
This function is invertible but not idempotent. This is because a string containing a
percent character will be modified by applying the function: for example
100% becomes 100%25, while 100%25 becomes
100%2525.
Decodes URI-escaped characters in a string.
This function returns the original representation of a URI-escaped string.
If $value is the empty sequence, the function returns the zero-length
string.
Otherwise, the value is first converted to a sequence of octets. Each plus sign
(+) is replaced with the octet representing a space character
(x20), and any substring that matches the regular expression
%[a-fA-F0-9][a-fA-F0-9] is replaced with an octet for the two-digit
hexadecimal number that follows the percent sign. Characters that are not part of
such a substring are replaced with the octets of their UTF-8 encoding.
For example, "A%42+C" results in the octets x41,
x42, x20, x43, and "💡" yields
xF0, x9F, x92, and xA1.
If % is followed by up to two characters that are not hexadecimal digits,
these characters are replaced by octets xEF, xBF,
and xBD, that is, the UTF-8 encoding of the Unicode replacement character
("%", "%X", "%AX", and "%XA" are all
replaced with these octets. For the string "%1X!", the octets xEF,
xBF, xBD, and x21 are returned.
Next, the resulting octets are interpreted as UTF-8. For example,
x41, x42, x20, and x43
becomes "AB C", and xF0, x9F,
x92, and xA1 becomes "💡".
If an invalid UTF-8 octet sequence is encountered, the octets that have successfully been parsed are replaced with a Unicode replacement character. Examples:
The single octet xF0 is converted to "�".
The octets xF0, x9F, x92, and
x41 are converted to "�A":
The bit pattern of the first octet indicates that the UTF-8 character comprises
four octets. As the fourth octet is invalid, a Unicode replacement character is
added for the first three octets, and the fourth (invalid) octet is parsed as a
new character.
Similarly, the octets xF0, xF0, x9F,
x92, and xA1 are converted to "�💡":
The second octet is invalid, but it becomes valid when being parsed as the
first octet of the remaining UTF-8 sequence.
Similarly, a UTF-8 octet sequence that represents a codepoint that is not a
valid XML character is replaced with a Unicode replacement character.
For example, x00 becomes "�".
New in 4.0
Converts a string containing an IRI into a URI according to the rules of
If $value is the empty sequence, the function returns the zero-length
string.
Otherwise, the function converts $value into a URI according to
the rules given in Section 3.1 of $value contains a character
that is invalid in an IRI, such as the space character (see note below), the invalid
character is replaced by its percent-encoded form as described in
Since
The function is idempotent but not invertible. Both the inputs My Documents
and My%20Documents will be converted to the output
My%20Documents.
This function does not check whether $iri is a valid IRI. It treats it as
an
The following printable ASCII characters are invalid in an IRI: <, >,
", , {, }, |,
\, ^, and `. Since these
characters should not appear in an IRI, if they do appear in $iri they will
be percent-encoded. In addition, characters outside the range
Since this function does not escape the character % to a URI should manually escape %
by replacing it with %25.
Escapes a URI in the same way that HTML user agents handle attribute values expected to contain URIs.
If $value is the empty sequence, the function returns the zero-length
string.
Otherwise, the function escapes all $value to be escaped is replaced by an escape sequence, which is
formed by encoding the character as a sequence of octets in UTF-8, and then representing
each of these octets in the form %HH, where HH is the hexadecimal representation of the
octet. This function must always generate hexadecimal values using the upper-case
letters A-F.
The behavior of this function corresponds to the recommended handling of non-ASCII
characters in URI attribute values as described in
Returns true if the string $value contains $substring as a
substring, taking collations into account.
If $value or $substring is the empty sequence, or
contains only ignorable collation units, it is interpreted as the zero-length
string.
If $substring is the zero-length string, then the function returns
true.
If $value is the zero-length string, the function returns
false.
The collation used by this function is determined according to the rules in
The function returns an xs:boolean indicating whether or not
$value contains (at the beginning, at the end, or anywhere within) at
least one sequence of collation units that provides a $substring, according to the collation that is
used.
A
The collation used in some of these examples, $coll, is a
collation in which both - and * are ignorable collation units.
“Ignorable collation unit” is equivalent to “ignorable collation element” in
Returns true if the string $value contains $substring as a leading
substring, taking collations into account.
If $value or $substring is the empty sequence, or
contains only ignorable collation units, it is interpreted as the zero-length
string.
If $substring is the zero-length string, then the function returns
true. If $value is the zero-length string and
$substring is not the zero-length string, then the function returns
false.
The collation used by this function is determined according to the rules in
The function returns an xs:boolean indicating whether or not
$value starts with a sequence of collation units that provides a
$substring according to the
collation that is used.
A
The collation used in some of these examples, $coll, is a
collation in which both - and * are ignorable collation units.
“Ignorable collation unit” is equivalent to “ignorable collation element” in
Returns true if the string $value contains $substring as a trailing
substring, taking collations into account.
If $value or $substring is the empty sequence, or
contains only ignorable collation units, it is interpreted as the zero-length
string.
If $substring is the zero-length string, then the function returns
true. If $value is the zero-length string and
the value of $substring is not the zero-length string, then the function returns
false.
The collation used by this function is determined according to the rules in
The function returns an xs:boolean indicating whether or not
$value ends with a sequence of collation units that provides a
$substring according to the
collation that is used.
A
The collation used in some of these examples, $coll, is a
collation in which both - and * are ignorable collation units.
“Ignorable collation unit” is equivalent to “ignorable collation element” in
Returns the part of $value that precedes the first occurrence of
$substring, taking collations into account.
If $value or $substring is the empty sequence, or
contains only ignorable collation units, it is interpreted as the zero-length
string.
If $substring is the zero-length string, then the function returns
the zero-length string.
If $value does not contain a string that is equal to
$substring, then the function returns the zero-length string.
The collation used by this function is determined according to the rules in
The function returns the substring of $value that precedes in
$value the first occurrence of a sequence of collation units
that provides a $substring
according to the collation that is used.
A
The collation used in some of these examples, $coll, is a
collation in which both - and * are ignorable collation units.
“Ignorable collation unit” is equivalent to “ignorable collation element” in
Returns the part of $value that follows the first occurrence of
$substring, taking collations into account.
If $value or $substring is the empty sequence, or
contains only ignorable collation units, it is interpreted as the zero-length
string.
If $substring is the zero-length string, then the function returns
the value of $value.
If $value does not contain a string that is equal to
$substring, then the function returns the zero-length string.
The collation used by this function is determined according to the rules in
The function returns the substring of $value that follows in
$value the first occurrence of a sequence of collation units
that provides a $substring
according to the collation that is used.
A dynamic error
The collation used in some of these examples, $coll, is a
collation in which both - and * are ignorable collation units.
“Ignorable collation unit” is equivalent to “ignorable collation element” in
Returns true if the supplied string matches a given regular expression.
If $value is the empty sequence, it is interpreted as the zero-length
string.
If the $flags argument is omitted or if it is an empty sequence,
the effect is the same as setting $flags to a zero-length string.
Flags are defined in
The function returns true if the set of $value against the regular expression $pattern,
with the associated $flags, is non-empty. Otherwise, the function returns false.
A dynamic error is raised $pattern is invalid according to the rules described in
A dynamic error is raised $flags is invalid according to the rules described in
Unless the metacharacters ^ and $ are used as anchors, the
string is considered to match the pattern if any substring matches the pattern. But if
anchors are used, the anchors must match the start/end of the string (in string mode),
or the start/end of a line (in multi-line mode).
This is different from the behavior of patterns in
Regular expression matching is defined on the basis of Unicode codepoints; it takes no account of collations.
It is valid for the regular expression to match a zero-length segment of $value.
For example, the result of the expression matches($s, "") is always true, regardless
of the value of $s.
Returns a string produced from the input string by replacing any segments that match a given regular expression with a supplied replacement string, provided either literally, or by invoking a supplied function.
If $value is the empty sequence, it is interpreted as the zero-length
string.
If the $flags argument is omitted or if it is an empty sequence,
the effect is the same as setting $flags to a zero-length string.
Flags are defined in
The string $value is matched against the regular expression $pattern,
using the supplied $flags, to obtain a set of $replacement argument, by applying the first
of the following rules that applies:
If $replacement is absent or empty, R is a zero-length
string.
If $replacement is a function item F, then
R is obtained by calling F, and then applying the
function
The first argument to F is the string to be replaced,
provided as xs:untypedAtomic.
The second argument to F provides the captured
groups as an xs:untypedAtomic sequence.
The Nth item in this sequence is the string value of the segment captured by
the Nth capturing subexpression. If the
Nth capturing subexpression was not matched, the Nth item
will be the zero-length string.
Note that the rules for function coercion mean that the function actually supplied for F may be an arity-1 function: the second argument does not need to be declared if it is not used.
If $replacement is a string and the
q flag is present, R is the value
of $replacement.
Otherwise, the value of $replacement is processed as follows.
Within the supplied $replacement string, a variable marker $N (where
N is an unsigned integer) may
be used to refer to the Nth captured group associated with M.
The replacement string R is obtained by replacing each of these variable markers
with the string value of the relevant captured group.
The variable marker $0 refers to the substring captured by the regular expression as a
whole.
A literal $ character within the
replacement string must be written as \$, and a literal \
character must be written as \\.
More specifically, the rules are as follows, where S is the number of
capturing subexpressions in the regular expression, and N is the
decimal number formed by taking all the digits that consecutively follow the
$ character in $replacement:
If N=0, then the variable is replaced by the string value of M.
If 1<=N<=S, then the variable marker is
replaced by the string value of the Nth captured group associated
with M. If the
Nth parenthesized sub-expression was not matched, then the
variable marker is replaced by the zero-length string.
If S<N<=9, then the variable marker is
replaced by the zero-length string.
Otherwise (if N>S and
N>9), the last digit of N is taken to
be a literal character to be included “as is” in the replacement string, and the
rules are reapplied using the number N formed by stripping off this
last digit.
For example, if the replacement string is
"$23"
and there are 5 substrings, the result contains the value of the substring that
matches the second capturing subexpression, followed by the digit
3.
The function returns the xs:string that is obtained by replacing each
of the $value with
the corresponding value of R.
A dynamic error is raised $pattern is invalid according to the rules described in section
A dynamic error is raised $flags is invalid according to the rules described in section
In the absence of the q flag,
a dynamic error is raised $replacement contains a dollar sign ($) character that is not
immediately followed by a digit 0-9 and not immediately preceded by a
backslash (\).
In the absence of the q flag,
a dynamic error is raised $replacement contains a backslash (\) character that is not part of a
\\ pair, unless it is immediately followed by a dollar sign ($)
character.
A dynamic error is raised $replacement
and $action arguments are supplied, and neither is an empty sequence.
If the input string contains no substring that matches the regular expression, the result of the function is a single string identical to the input string.
If two overlapping substrings of $value both match the
$pattern, then only the first one (that is, the one whose first $value string) is
replaced.
If two alternatives within the pattern both match at the same position in the
$input, then the match that is chosen is the one matched by the first
alternative. For example:
The rules for .*
will typically produce two matches: one matching segment containing all the characters in the
input string, and a second zero-length matching seqment at the end position of the string.
d is replaced.The $replacement argument can now be a function
that computes the replacement strings.
It is now permitted for the regular expression to match a zero-length string.
Returns a sequence of strings constructed by splitting the input wherever a separator is found; the separator is any substring that matches a given regular expression.
The following rules apply when the $pattern argument is omitted,
or is set to an empty sequence:
The function splits the supplied string at whitespace boundaries.
More specifically, calling fn:tokenize($value) fn:tokenize($value, ())fn:tokenize(fn:normalize-space($value), ' ')) where the second argument
is a single space character (x20).
The $flags argument is ignored.
The following rules apply when the $pattern argument is supplied as a single string:
If the $flags argument is omitted or if it is an empty sequence,
the effect is the same as setting $flags to a zero-length string.
Flags are defined in
If $value is the empty sequence, or if $value is the
zero-length string, the function returns the empty sequence.
The function returns a sequence of strings formed by breaking the $value
string into a sequence of strings, treating any substring that matches
$pattern as a separator. The separators themselves are not returned.
More specifically:
Let M0 be the sequence of $value against $pattern in the presence
of $flags.
Unless the first segment in M0 is zero-length and starts at the first $value, prepend a zero-length segment that starts at the start of $value:
call the result M1.
Unless the last segment in M1 is zero-length and starts at the last $value (that is, the character position after the last character), append a zero-length
segment that starts at the last character position of $value. Call the result M2.
For each pair of adjacent segments in M2 (say, S/n and S/n+1),
construct a string (possibly zero-length) that is the substring of $value containing all characters
that follow S/n and that precede S/n+1. Return this sequence of strings, in order.
A dynamic error is raised $pattern is invalid according to the rules described in section
A dynamic error is raised $flags is invalid according to the rules described in section
If the input string is not zero length, and no separators are found in the input string, the result of the function is a single string identical to the input string.
For the one-argument form of the function:
The function has a similar effect to
the two-argument form with \s+ as the separator pattern, except that the one-argument
form strips leading and trailing whitespace, whereas the two-argument form delivers an extra
zero-length token if leading or trailing whitespace is present.
The separator used is any sequence
of tab (
For the two-argument form of the function:
The function returns no information about the separators that were found
in the string. If this information is required, the (?<=,) will start a new token after every comma,
including the comma as part of the previous token.
If a separator occurs at the start of $value, and is not zero-length, the result
sequence will start with a zero-length string. Similarly, zero-length strings will also occur in
the result sequence if a non-zero-length separator occurs at the end of $value,
or if two adjacent substrings match the supplied $pattern.
If two alternatives within the supplied $pattern both match at the same
position in the $value string, then the match that is chosen is the first.
For example:
The pattern may match zero-length segments of the input string. For example, the
expression tokenize("Do not eat", "\b") returns the sequence
"Do", " ", "not", " ", "eat".
A string may be split into individual characters (producing the same effect as the
tokenize("xyz", ""),
or any other regular expression such as .?? that matches every zero-length string, regardless
of position.
Unlike the split method in some other popular languages, however,
not every regular expression that matches a zero-length string produces this
behavior: for example the regular expression \b splits the string
before and after every word.
The second argument can now be an empty sequence.
It is now permitted for the regular expression to match a zero-length string.
Analyzes a string using a regular expression, returning an XML structure that identifies which parts of the input string matched or failed to match the regular expression, and in the case of matched substrings, which substrings matched each capturing group in the regular expression.
If the $flags argument is omitted or if it is an empty sequence,
the effect is the same as setting $flags to a zero-length string.
Flags are defined in
If $value is the empty sequence the function behaves as if
$value were the zero-length string.
The function returns an element node whose local name is
analyze-string-result. This element and all its descendant elements have
the namespace URI http://www.w3.org/2005/xpath-functions. The namespace
prefix is fn:match and fn:non-match elements. This sequence
is formed by breaking the $value string into a sequence of strings,
returning any substring that matches $pattern as the content of an
fn:match element, and any intervening substring as the content of an
fn:non-match element.
More specifically, the function starts by matching the regular expression against the string,
using the supplied $flags, to obtain the fn:match child, whose string value is
the string value of the segment. Before, between, or after these fn:match
elements, as required to ensure that the string value of the fn:analyze-string-result
element is the same as $value, it inserts fn:non-match elements.
The content of an fn:non-match element is always a single (non-empty) text node,
and two fn:non-match elements never appear as adjacent siblings.
The captured groups for each fn:group or fn:lookahead-group
children of the corresponding fn:match element. Groups captured by a subexpression within
a lookahead assertion are referred to as lookahead groups; those not within a lookahead
assertion are called ordinary groups.
The content of a fn:match element is in general:
A sequence of text nodes and fn:group element children,
whose string-values when concatenated comprise the string value of the matching segment,
followed by
A sequence of zero or more fn:lookahead-group elements,
representing the lookahead groups
The string value of an fn:match element may be empty.
An fn:group element
with a nr attribute having the integer value N identifies
the substring captured by an ordinary group, specifically the string value of the Nth captured group.
For each ordinary capturing subexpression there will be at most one corresponding
fn:group element in each fn:match element in the
result.
By contrast, lookahead groups are represented by fn:lookahead-group elements,
which (if they appear at all) must follow all text node and fn:group element children
of the fn:match element. These groups may overlap the matching and non-matching substrings, and
indeed may overlap each other. They must appear in ascending numerical order of group number.
The attributes of the fn:lookahead-group element are as follows:
nr: the group number, based on the position of the capturing subexpression
that captured the group;
value: the string value of the segment that was captured;
position: the one-based start position of the segment within the input string.
If the function is called twice with the same arguments, it is
The base URI of the element nodes in the result is
A schema is defined for the structure of the returned element: see
The result of the function will always be such that validation against this schema would succeed.
However, it is
A dynamic error is raised $pattern is invalid according to the rules described in section
A dynamic error is raised $flags is invalid according to the rules described in section
It is
The declarations and definitions in the schema are not automatically available in
the static context of the
The schema defines the outermost element, analyze-string-result, in such
a way that mixed content is permitted. In fact the element will only have element nodes (match
and non-match) as its children, never text nodes. Although this might have originally been an
oversight, defining the analyze-string-result element with mixed="true" allows it
to be atomized, which is potentially useful (the atomized value will be the original input string),
and the capability has therefore been retained for compatibility with the 3.0 version of this
specification.
The rules for .*
will typically produce two matches: one matching segment containing all the characters in the
input string, and a second zero-length matching seqment at the end position of the string.
In the following examples, the result document is shown in serialized form, with whitespace between the element nodes. This whitespace is not actually present in the result.
The output of the function is extended to allow the represention of captured groups found within lookahead assertions.
It is now permitted for the regular expression to match a zero-length string.
Determines whether or not any of the supplied strings, when tokenized at whitespace boundaries, contains the supplied token, under the rules of the supplied collation.
If $value is the empty sequence, the function returns false.
Leading and trailing whitespace is trimmed from $token.
If the trimmed value of $token
is a zero-length string, the function returns false.
The collation used by this function is determined according to the rules in
The function returns true if and only if there is string in $value which,
after tokenizing at whitespace boundaries, contains a token
that is equal to the trimmed value of $token under
the rules of the selected collation.
Interior whitespace within $token will cause the function to return false,
unless such whitespace is ignored by the selected collation.
This function can be used for processing space-separated attribute values
(for example, the XHTML and DITA class attribute),
where one often needs to test for the presence
of a single token in a space-separated list. The function is designed to work
both when the attribute has been validated against an XSD list type, and when it
appears as a single untyped string. It differs from the
HTML 5 definition in that HTML 5 recognizes form feed (x0C) as a separator.
To reproduce the HTML token matching behavior, the HTML ASCII case-insensitive collation
should be used: see
Resolves a relative IRI reference against an absolute IRI.
The function is defined to operate on IRI references as defined in
The following rules apply in order:
If $href is the empty sequence, the function returns the empty
sequence.
If $href is an absolute IRI (as defined above), then it is returned
unchanged.
If the $base argument is not supplied,
If the $base.
Otherwise, a dynamic error is raised:
The function resolves the relative IRI reference $href
against the base IRI $base using the algorithm defined in
The first form of this function resolves $href against the value of the
base-uri property from the static context. A dynamic error is raised
A dynamic error is raised $href
is not a valid IRI according to the rules of RFC3987, extended with an
implementation-defined subset of the extensions permitted in LEIRI, or if it is not a
suitable relative reference to use as input to the RFC3986 resolution algorithm extended
to handle additional unreserved characters.
A dynamic error is raised $base is
not a valid IRI according to the rules of RFC3987, extended with an
implementation-defined subset of the extensions permitted in LEIRI, or if it is not a
suitable IRI to use as input to the chosen resolution algorithm (for example, if it is a
relative IRI reference
A dynamic error is raised
Resolving a URI does not dereference it. This is merely a syntactic operation on two
The algorithms in the cited RFCs include some variations that are optional or recommended rather than mandatory; they also describe some common practices that are not recommended, but which are permitted for backwards compatibility. Where the cited RFCs permit variations in behavior, so does this specification.
Throughout this family of specifications, the phrase "resolving a relative URI (or IRI) reference" should be understood as using the rules of this function, unless otherwise stated.
RFC3986 defines an algorithm for resolving relative references
in the context of the URI syntax defined in that RFC. RFC3987 describes a modification
to that algorithm to make it applicable to IRIs (specifically: additional characters
permitted in an IRI are handled the same way that RFC3986 handles unreserved characters).
The LEIRI specification does not explicitly define a resolution algorithm, but suggests
that it
The optional second argument can now be supplied as an empty sequence.
Returns the xs:boolean value true.
The result is equivalent to xs:boolean("1").
Returns the xs:boolean value false.
The result is equivalent to xs:boolean("0").
eq
operator when applied to two xs:boolean values.Returns true if the two arguments are the same boolean value.
The function returns true if both arguments are true or if
both arguments are false. It returns false if one of the
arguments is true and the other argument is false.
lt operator when applied to two xs:boolean values. Also
used in the definition of the ge operator.Returns true if the first argument is false and the second is true.
The function returns true if $arg1 is false and
$arg2 is true. Otherwise, it returns
false.
Computes the effective boolean value of the sequence $input.
The function computes the effective boolean value of a sequence, defined according to
the following rules. See also
If $input is the empty sequence, false.
If $input is a sequence whose first item is a true.
If $input is a singleton value of type xs:boolean or of a type
derived from xs:boolean, $input.
If $input is a singleton value of type xs:untypedAtomic,
xs:string, xs:anyURI, or a type derived from xs:string
or xs:anyURI, false if the operand value has
zero length; otherwise it returns true.
If $input is a singleton value of any numeric type or a type derived
from a numeric type, false if the
operand value is NaN or is numerically equal to zero; otherwise it
returns true.
In all cases other than those listed above,
The result of this function is not necessarily the same as $input cast as
xs:boolean. For example, fn:boolean("false") returns the value
true whereas "false" cast as xs:boolean (which can also be
written xs:boolean("false")) returns false.
fn:boolean($abc) raises a type error
fn:boolean([]) raises a type error
Returns true if the effective boolean value of $input is
false, or false if it is true.
The value of $input is first reduced to an effective boolean value by
applying the fn:boolean() function. The function returns true
if the effective boolean value is false, or false if the
effective boolean value is true.
fn:not(1 to 10) raises a type error
lt operator when applied to two xs:yearMonthDuration
values. Also used in the definition of the ge operator.Returns true if $arg1 is a shorter duration than $arg2.
If the number of months in $arg1 is numerically less than the
number of months in $arg2, the function returns true.
Otherwise, the function returns false.
Either or both durations may be negative.
lt operator when applied to two xs:dayTimeDuration values.
Also used in the definition of the ge operator.Returns true if $arg1 is a shorter duration than $arg2.
If the number of seconds in $arg1 is numerically less than the
number of seconds in $arg2, the function returns true.
Otherwise, the function returns false.
Either or both durations may be negative
eq operators when applied to two xs:duration values. Also
used in the definition of the ne operator.Returns true if $arg1 and $arg2 are durations of the same
length.
If the xs:yearMonthDuration components of $arg1 and
$arg2 are equal and the xs:dayTimeDuration components of
$arg1 and $arg2 are equal, the function returns
true.
Otherwise, the function returns false.
The semantics of this function are:
that is, the function returns true if the months and seconds values of the
two durations are equal.
Note that this function, like any other, may be applied to arguments that are derived
from the types given in the function signature, including the two subtypes
xs:dayTimeDuration and xs:yearMonthDuration. With the
exception of the zero-length duration, no instance of xs:dayTimeDuration
can ever be equal to an instance of xs:yearMonthDuration.
Returns an xs:dayTimeDuration whose length is a given number of seconds.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:dayTimeDuration value whose length
in seconds is equal to $value.
If $value is negative then the result will be a negative duration.
For handling of overflow and underflow, see
The result of seconds($n) is approximately equal to the result of
the expression xs:dayTimeDuration('PT1S') * $n. The equivalence is only
approximate, because seconds($n) uses the exact xs:decimal
value supplied, whereas multiplying a duration by a number first converts the number
to an xs:double value, which may lose precision.
xs:dateTime valuexs:dateTime value to a Unix timestampNew in 4.0
Returns the number of years in a duration.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer representing the years
component in $value. Given that a duration
is a ($months, $seconds) tuple, the result is the value of ($months idiv 12).
If $value is a negative duration then the result will be negative.
If $value is an xs:dayTimeDuration the function
returns 0.
xs:dayTimeDuration component, it must first be converted to an
xs:yearMonthDuration.Returns the number of months in a duration.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer representing the months
component in $value. Given that a duration
is a ($months, $seconds) tuple, the result is the value of ($months mod 12).
If $value is a negative duration then the result will be negative.
If $value is an xs:dayTimeDuration the function
returns 0.
xs:dayTimeDuration component, it must first be converted to an
xs:yearMonthDuration.Returns the number of days in a duration.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer representing the days
component in $value. Given that a duration
is a ($months, $seconds) tuple, the result is ($seconds idiv 86400).
If $value is a negative duration then the result will be negative.
If $value is an xs:yearMonthDuration the function returns 0.
xs:yearMonthDuration
component, it must first be converted to an
xs:dayTimeDuration.Returns the number of hours in a duration.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer representing the hours
component in $value. ($months, $seconds) tuple, the result is the value of ($seconds mod 86400) idiv 3600
If $value is a negative duration then the result will be negative.
If $value is an xs:yearMonthDuration the function returns 0.
xs:yearMonthDuration
component, it must first be converted to an
xs:dayTimeDuration.Returns the number of minutes in a duration.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer representing the minutes
component in $value. Given that a duration
is a ($months, $seconds) tuple, the result is the value of ($seconds mod 3600) idiv 60.
If $value is a negative duration then the result will be negative.
If $value is an xs:yearMonthDuration the function returns 0.
xs:yearMonthDuration
component, it must first be converted to an
xs:dayTimeDuration.Returns the number of seconds in a duration.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:decimal representing the seconds
component in $value. Given that a duration
is a ($months, $seconds) tuple, the result is the value of ($seconds mod 60)
as an xs:decimal.
If $value is a negative duration then the result will be negative.
If $value is an xs:yearMonthDuration the function returns 0.
xs:yearMonthDuration
component of an xs:duration, it must first be converted to an
xs:dayTimeDuration.xs:yearMonthDuration
component, it must first be converted to an
xs:dayTimeDuration.+ operator when applied to two xs:yearMonthDuration values.Returns the result of adding two xs:yearMonthDuration values.
The function returns the result of adding $arg1 to $arg2.
The result will be an xs:yearMonthDuration whose
length in months is equal to the length in months of $arg1 plus the length
in months of $arg2.
For handling of overflow, see
Either duration (and therefore the result) may be negative.
- operator when applied to two xs:yearMonthDuration values.Returns the result of subtracting one xs:yearMonthDuration value from
another.
The function returns the result of subtracting $arg2 from
$arg1. The result will be an xs:yearMonthDuration
whose length in months is equal to the length in months of $arg1 minus the
length in months of $arg2.
For handling of overflow, see
Either duration (and therefore the result) may be negative.
* operator when applied to an xs:yearMonthDuration and a numeric
value.Returns the result of multiplying $arg1 by $arg2.
The result is rounded to the nearest month.
The result is the xs:yearMonthDuration whose length in months is equal to
the result of applying the $arg1 by the value of
$arg2.
If $arg2 is positive or negative zero, the result is a zero-length
duration. If $arg2 is positive or negative infinity, the result overflows
and is handled as described in
For handling of overflow, underflow, and rounding, see
A dynamic error is raised $arg2 is
NaN.
Either duration (and therefore the result) may be negative.
div operator when applied to an xs:yearMonthDuration and a numeric
value.Returns the result of dividing $arg1 by $arg2.
The result is rounded to the nearest month.
The result is the xs:yearMonthDuration whose length in months is equal to
the result of applying the $arg1 by the value of
$arg2.
If $arg2 is positive or negative infinity, the result is a zero-length
duration. If $arg2 is positive or negative zero, the result overflows and
is handled as described in
For handling of overflow, underflow, and rounding,
see
A dynamic error is raised $arg2 is
NaN.
Either operand (and therefore the result) may be negative.
div operator when applied to two xs:yearMonthDuration values.Returns the ratio of two xs:yearMonthDuration values.
The function returns the result of dividing the length in months of $arg1
by the length in months of $arg2, according to the rules of the
op:numeric-divide function for integer operands.
For handling of overflow, underflow, and rounding,
see
Either duration (and therefore the result) may be negative.
The following example demonstrates how to calculate the length of an
xs:yearMonthDuration value in months:
+
operator when applied to two xs:dayTimeDuration values.Returns the sum of two xs:dayTimeDuration values.
The function returns the result of adding $arg1 to
$arg2. The result is the xs:dayTimeDuration whose length in
seconds is equal to the sum of the length in seconds of the two input durations.
For handling of overflow, see
Either duration (and therefore the result) may be negative.
-
operator when applied to two xs:dayTimeDuration values.Returns the result of subtracting one xs:dayTimeDuration from another.
The function returns the result of subtracting $arg2 from
$arg1. The result is the xs:dayTimeDuration whose
length in seconds is equal to the length in seconds of $arg1 minus the
length in seconds of $arg2.
For handling of overflow, see
Either duration (and therefore the result) may be negative.
*
operator when applied to an xs:dayTimeDuration and a numeric
value.Returns the result of multiplying a xs:dayTimeDuration by a number.
The function returns the result of multiplying $arg1 by
$arg2. The result is the xs:dayTimeDuration whose length in
seconds is equal to the length in seconds of $arg1 multiplied by the
numeric value $arg2.
If $arg2 is positive or negative zero, the result is a zero-length
duration. If $arg2 is positive or negative infinity, the result overflows
and is handled as described in
For handling of overflow, underflow, and rounding, see
A dynamic error is raised $arg2 is
NaN.
Either operand (and therefore the result) may be negative.
div operator when applied to two xs:dayTimeDuration values.Returns the result of multiplying a xs:dayTimeDuration by a number.
The function returns the result of dividing $arg1 by
$arg2. The result is the xs:dayTimeDuration whose length in
seconds is equal to the length in seconds of $arg1 divided by the numeric
value $arg2.
If $arg2 is positive or negative infinity, the result is a zero-length
duration. If $arg2 is positive or negative zero, the result overflows and
is handled as described in
For handling of overflow, underflow, and rounding, see
A dynamic error is raised $arg2 is
NaN.
Either operand (and therefore the result) may be negative.
div operator when applied to two xs:dayTimeDuration values.Returns the ratio of two xs:dayTimeDuration values, as a decimal
number.
The function returns the result of dividing $arg1 by
$arg2. The result is the xs:dayTimeDuration whose length in
seconds is equal to the length in seconds of $arg1 divided by the length in
seconds of $arg2. The calculation is performed by applying
op:numeric-divide to the two xs:decimal operands.
For handling of overflow, underflow, and rounding,
see
Either operand (and therefore the result) may be negative.
This examples shows how to determine the number of seconds in a duration.
Returns an xs:dateTime value created by combining an xs:date
and an xs:time.
If either $date or $time is the empty sequence the function
returns the empty sequence.
Otherwise, the function returns an xs:dateTime whose date component is
equal to $date and whose time component is equal to $time.
The timezone of the result is computed as follows:
If neither argument has a timezone, the result has no timezone.
If exactly one of the arguments has a timezone, or if both arguments have the same timezone, the result has this timezone.
A dynamic error is raised
"24:00:00" is an alternate lexical form
for "00:00:00"Returns a dateTime value for a Unix time.
The function returns a dateTime value in UTC timezone for the Unix time specified
by $value in milliseconds. If the value is absent or an empty sequence,
0 is used. The Unix time is defined in
If the implementation supports data types from XSD 1.1 then the returned value will be
an instance of xs:dateTimeStamp. Otherwise, the only guarantees are that it
will be an instance of xs:dateTime and will have a timezone component.
By calling this convenience function, it can be ensured that the correct timezone is used for computing the Unix time.
Note that Unix time does not account for leap seconds. It assumes that every day has 86,400 seconds.
Calculate the Unix time associated with a xs:dateTime value:
New in 4.0
eq operator when applied to two xs:dateTime values. Also
used in the definition of the ne, le and ge operators.Returns true if the two supplied xs:dateTime values refer to the same
instant in time.
If either $arg1 or $arg2 has no timezone component, the
effective value of the argument is obtained by substituting the implicit timezone from
the dynamic evaluation context.
The function then returns true if and only if the effective value of
$arg1 is equal to the effective value of $arg2 according to
the algorithm defined in section 3.2.7.4 of Order relation on dateTime
for xs:dateTime values with
timezones. Otherwise the function returns false.
Assume that the dynamic context provides an implicit timezone value of
-05:00
lt operator when applied to two xs:dateTime values. Also
used in the definition of the ge operator.Returns true if the first argument represents an earlier instant in time
than the second argument.
If either $arg1 or $arg2 has no timezone component, the
effective value of the argument is obtained by substituting the implicit timezone from
the dynamic evaluation context.
The function then returns true if and only if the effective value of
$arg1 is less than the effective value of $arg2 according
to the algorithm defined in section 3.2.7.4 of Order relation on dateTime
for xs:dateTime values with
timezones. Otherwise the function returns false.
eq operator when applied to two xs:date values. Also used
in the definition of the ne, le and ge operators.Returns true if and only if the starting instants of the two supplied
xs:date values are the same.
The starting instant of an xs:date is the xs:dateTime at time
00:00:00 on that date.
The function returns the result of the expression:
xs:dateTime("2004-12-25T00:00:00Z") and
xs:dateTime("2004-12-25T00:00:00+07:00"). These are normalized to
xs:dateTime("2004-12-25T00:00:00Z") and
xs:dateTime("2004-12-24T17:00:00Z"). lt operator when applied to two xs:date values. Also used in the
definition of the ge operator.Returns true if and only if the starting instant of $arg1 is
less than the starting instant of $arg2. Returns false
otherwise.
The starting instant of an xs:date is the xs:dateTime at time
00:00:00 on that date.
The function returns the result of the expression:
eq operator when applied to two xs:time values. Also used
in the definition of the ne, le and ge operators.Returns true if the two xs:time values represent the same
instant in time, when treated as being times on the same date, before adjusting the
timezone.
Each of the supplied xs:time values is expanded to an
xs:dateTime value by associating the time with an arbitrary date. The
function returns the result of comparing these two xs:dateTime values using
op:dateTime-equal.
The result of the function is thus the same as the value of the expression:
Assume that the date components from the reference xs:dateTime
correspond to 1972-12-31.
1972-12-31T08:00:00+09:00 and
1972-12-31T17:00:00-06:00, respectively, and normalize to
1972-12-30T23:00:00Z and 1972-12-31T23:00:00Z.
xs:dateTime
values, a time of 24:00:00 is equivalent to 00:00:00 on
the following day. For xs:time, the normalization from
24:00:00 to 00:00:00 happens before the
xs:time is converted into an xs:dateTime for the
purpose of the equality comparison. For xs:time, any operation on
24:00:00 produces the same result as the same operation on
00:00:00 because these are two different lexical representations
of the same value. lt operator when applied to two xs:time values. Also used in the
definition of the ge operator.Returns true if the first xs:time value represents an earlier
instant in time than the second, when both are treated as being times on the same date,
before adjusting the timezone.
Each of the supplied xs:time values is expanded to an
xs:dateTime value by associating the time with an arbitrary date. The
function returns the result of comparing these two xs:dateTime values using
op:dateTime-less-than.
The result of the function is thus the same as the value of the expression:
Assume that the dynamic context provides an implicit timezone value of
-05:00.
eq operator when applied to two xs:gYearMonth values. Also
used in the definition of the ne operator.Returns true if the two xs:gYearMonth values have the same starting
instant.
The starting instants of $arg1 and $arg2 are calculated by
supplying the missing components of $arg1 and $arg2 from the
xs:dateTime template xxxx-xx-01T00:00:00. The function
returns the result of comparing these two starting instants using
op:dateTime-equal.
Assume that the dynamic context provides an implicit timezone value of
-05:00.
op:gYearMonth-equal(xs:gYearMonth("1986-02"), xs:gYearMonth("1986-03"))
returns false(). The starting instants are
1986-02-01T00:00:00-05:00 and 1986-03-01T00:00:00,
respectively.
op:gYearMonth-equal(xs:gYearMonth("1978-03"), xs:gYearMonth("1986-03Z"))
returns false(). The starting instants are
1978-03-01T00:00:00-05:00 and 1986-03-01T00:00:00Z,
respectively.
eq operator when applied to two xs:gYear values. Also used in the
definition of the ne operator.Returns true if the two xs:gYear values have the same starting instant.
The starting instants of $arg1 and $arg2 are calculated by
supplying the missing components of $arg1 and $arg2 from the
xs:dateTime template xxxx-01-01T00:00:00. The function
returns the result of comparing these two starting instants using
op:dateTime-equal.
Assume that the dynamic context provides an implicit timezone value of
-05:00. Assume, also, that the xs:dateTime template is
xxxx-01-01T00:00:00.
op:gYear-equal(xs:gYear("2005-12:00"), xs:gYear("2005+12:00")) returns
false(). The starting instants are
2005-01-01T00:00:00-12:00 and 2005-01-01T00:00:00+12:00,
respectively, and normalize to 2005-01-01T12:00:00Z and
2004-12-31T12:00:00Z.
eq operator when applied to two xs:gMonthDay values. Also
used in the definition of the ne operator.Returns true if the two xs:gMonthDay values have the same starting instant,
when considered as days in the same year.
The starting instants of $arg1 and $arg2 are calculated by
supplying the missing components of $arg1 and $arg2 from the
xs:dateTime template 1972-xx-xxT00:00:00 or an equivalent.
The function returns the result of comparing these two starting instants using
op:dateTime-equal.
Assume that the dynamic context provides an implicit timezone value of
-05:00. Assume for the purposes of illustration that the
xs:dateTime template used is 1972-xx-xxT00:00:00 (this
does not affect the result).
1972-12-25T00:00:00-14:00 and
1972-12-26T00:00:00+10:00, respectively, and normalize to
1972-12-25T14:00:00Z and 1972-12-25T14:00:00Z.
eq operator when applied to two xs:gMonth values. Also used
in the definition of the ne operator.Returns true if the two xs:gMonth values have the same starting instant,
when considered as months in the same year.
The starting instants of $arg1 and $arg2 are calculated by
supplying the missing components of $arg1 and $arg2 from the
xs:dateTime template 1972-xx-01T00:00:00 or an equivalent.
The function returns the result of comparing these two starting instants using
op:dateTime-equal.
Assume that the dynamic context provides an implicit timezone value of
-05:00. Assume, also, that the xs:dateTime template
chosen is 1972-xx-01T00:00:00.
1972-12-01T00:00:00-14:00 and
1972-12-01T00:00:00+10:00, respectively, and normalize to
1972-11-30T14:00:00Z and 1972-12-01T14:00:00Z.
eq operator when applied to two xs:gDay values. Also used in the
definition of the ne operator.Returns true if the two xs:gDay values have the same starting instant, when
considered as days in the same month of the same year.
The starting instants of $arg1 and $arg2 are calculated by
supplying the missing components of $arg1 and $arg2 from the
xs:dateTime template 1972-12-xxT00:00:00 or an equivalent.
The function returns the result of comparing these two starting instants using
op:dateTime-equal.
Assume that the dynamic context provides an implicit timezone value of
-05:00. Assume, also, that the xs:dateTime template is
1972-12-xxT00:00:00.
1972-12-25T00:00:00-14:00 and
1972-12-25T00:00:00+10:00, respectively, and normalize to
1972-12-25T14:00:00Z and 1972-12-24T14:00:00Z.
Returns the year component of a
If $value is the empty sequence, or if the year component is absent,
the function returns the empty sequence.
Otherwise, the function returns an xs:integer representing the year
component in $value. The result may be negative.
Ignoring complications that arise with midnight on the last day of the year, the year returned is the same numeric value that appears in the lexical representation, which for negative years means the meaning may vary depending on whether XSD 1.0 or XSD 1.1 conventions are in use.
The function has been extended to handle other Gregorian types such as xs:gYearMonth.
Returns the month component of a
If $value is the empty sequence, or if it contains no month component,
the function returns the empty sequence.
Otherwise, the function returns an xs:integer between 1 and
12, both inclusive, representing the month component in
$value.
The function has been extended to handle other Gregorian types such as xs:gYearMonth.
Returns the day component of a
If $value is the empty sequence, or if it contains no day component,
the function returns the empty sequence.
Otherwise, the function returns an xs:integer between 1 and
31, both inclusive, representing the day component in the
local value of $value.
The function has been extended to handle other Gregorian types such as xs:gMonthDay.
Returns the hours component of a
If $value is the empty sequence, or if it contains no hours
component, the function returns the empty sequence.
Otherwise, the function returns an xs:integer between 0 and
23, both inclusive, representing the hours component in $value.
The function has been extended to handle other types including xs:time.
Returns the minute component of a
If $value is the empty sequence, or if it contains no minutes
component, the function returns the empty sequence.
Otherwise, the function returns an xs:integer value between 0
and 59, both inclusive, representing the minute component in the local value of
$value.
The function has been extended to handle other types including xs:time.
Returns the seconds component of a
If $value is the empty sequence, or if it contains no seconds
component, the function returns the empty sequence.
Otherwise, the function returns an xs:decimal value greater than or equal
to zero and less than 60, representing the seconds and fractional seconds in $value.
Returns the timezone component of a
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns the timezone component of $value, if any. If
$value has a timezone component, then the result is an
xs:dayTimeDuration that indicates deviation from UTC; its value may
range from +14:00 to -14:00 hours, both inclusive. If $value has no timezone
component, the result is the empty sequence.
The function has been extended to handle other types such as xs:gYearMonth.
Returns the year component of an xs:date.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer representing the year in the
local value of $value. The value may be negative.
The year returned is the same numeric value that appears in the lexical representation, which for negative years means the meaning may vary depending on whether XSD 1.0 or XSD 1.1 conventions are in use.
Returns the month component of an xs:date.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer between
1 and 12, both
inclusive, representing the month component in the local value of $value.
Returns the day component of an xs:date.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer between
1 and 31, both
inclusive, representing the day component in the localized value of
$value.
Returns the timezone component of an xs:date.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns the timezone component of $value, if any. If
$value has a timezone component, then the result is an
xs:dayTimeDuration that indicates deviation from UTC; its value may
range from +14:00 to -14:00 hours, both inclusive. If $value has no timezone
component, the result is the empty sequence.
Returns the hours component of an xs:time.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer between
0 and 23, both
inclusive, representing the value of the hours component in the local value of
$value.
Assume that the dynamic context provides an implicit timezone value of
-05:00.
Returns the minutes component of an xs:time.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:integer value between 0
and 59, both inclusive, representing the value of the minutes component
in the local value of $value.
Returns the seconds component of an xs:time.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns an xs:decimal value greater than or equal
to zero and less than 60, representing the seconds and fractional seconds in the local
value of $value.
Returns the timezone component of an xs:time.
If $value is the empty sequence, the function returns the empty sequence.
Otherwise, the function returns the timezone component of $value, if any. If
$value has a timezone component, then the result is an
xs:dayTimeDuration that indicates deviation from UTC; its value may
range from +14:00 to -14:00 hours, both inclusive. If $value has no timezone
component, the result is the empty sequence.
Adjusts an xs:dateTime value to a specific timezone, or to no timezone at
all.
If $timezone is not specified, then the effective value of
$timezone is the value of the implicit timezone in the dynamic
context.
If $value is the empty sequence, then the function returns the empty
sequence.
If $value does not have a timezone component and $timezone is
the empty sequence, then the result is $value.
If $value does not have a timezone component and $timezone is
not the empty sequence, then the result is $value with $timezone
as the timezone component.
If $value has a timezone component and $timezone is the empty
sequence, then the result is the local value of $value without its timezone
component.
If $value has a timezone component and $timezone is not the
empty sequence, then the result is the xs:dateTime value that is equal to
$value and that has a timezone component equal to
$timezone.
A dynamic error is raised $timezone
is less than -PT14H or greater than PT14H or is not an
integral number of minutes.
Assume the dynamic context provides an implicit timezone of -05:00
(-PT5H0M).
Adjusts an xs:date value to a specific timezone, or to no timezone at all;
the result is the date in the target timezone that contains the starting instant of the
supplied date.
If $timezone is not specified, then the effective value of
$timezone is the value of the implicit timezone in the dynamic
context.
If $value is the empty sequence, then the function returns the empty
sequence.
If $value does not have a timezone component and $timezone is
the empty sequence, then the result is $value.
If $value does not have a timezone component and $timezone is
not the empty sequence, then the result is $value with $timezone
as the timezone component.
If $value has a timezone component and $timezone is the empty
sequence, then the result is the local value of $value without its timezone
component.
If $value has a timezone component and $timezone is not the
empty sequence, then:
Let $dt be the value of fn:dateTime($arg,
xs:time('00:00:00')).
Let $adt be the value of fn:adjust-dateTime-to-timezone($dt,
$timezone)
The function returns the value of xs:date($adt)
A dynamic error is raised $timezone
is less than -PT14H or greater than PT14H or is not an
integral number of minutes.
Assume the dynamic context provides an implicit timezone of -05:00
(-PT5H0M).
$value is converted to
xs:dateTime("2002-03-07T00:00:00-07:00"). This is adjusted to the
implicit timezone, giving "2002-03-07T02:00:00-05:00".
$value is converted to
xs:dateTime("2002-03-07T00:00:00-07:00").
This is adjusted to the given timezone,
giving "2002-03-06T21:00:00-10:00". Adjusts an xs:time value to a specific timezone, or to no timezone at
all.
If $timezone is not specified, then the effective value of
$timezone is the value of the implicit timezone in the dynamic
context.
If $value is the empty sequence, then the function returns the empty
sequence.
If $value does not have a timezone component and $timezone is
the empty sequence, then the result is $value.
If $value does not have a timezone component and $timezone is
not the empty sequence, then the result is $value with $timezone
as the timezone component.
If $value has a timezone component and $timezone is the empty
sequence, then the result is the localized value of $value without its
timezone component.
If $value has a timezone component and $timezone is not the
empty sequence, then:
Let $dt be the xs:dateTime value
fn:dateTime(xs:date('1972-12-31'), $value).
Let $adt be the value of fn:adjust-dateTime-to-timezone($dt,
$timezone)
The function returns the xs:time value
xs:time($adt).
A dynamic error is raised $timezone
is less than -PT14H or greater than PT14H or if does not
contain an integral number of minutes.
Assume the dynamic context provides an implicit timezone of -05:00
(-PT5H0M).
Returns the timezone offset from UTC that is in conventional use at a given place and time.
This function uses a database of civil timezones (including daylight savings time) to return
the timezone offset for a given date/time and place. For example, the timezone offset for New York
on 31 December 2024 would be -PT5H.
If the $place argument is omitted or empty then the
If the supplied $value has no timezone then the implicit timezone from the dynamic
context is used. This is unrelated to the timezone applicable to the requested $place.
The intended use of the $place argument is to identify
the place where an event
represented by the $value argument took place or will take place.
The value must be an IANA timezone name as defined in the IANA timezone database "America/New_York" and "Europe/Rome".
The result of the function is the civil timezone offset applicable to the given date/time and place, as determined by the IANA timezone database or an alternative authoritative source.
A dynamic error is raised
The expression:
returns the current civil date and time in New York.
If the default place is a location in the same timezone as (say) Paris, then the expression
returns PT2H.
New in 4.0
-
operator when applied to two xs:dateTime values.Returns an xs:dayTimeDuration representing the amount of elapsed time
between the instants arg2 and arg1.
If either $arg1 or $arg2 do not contain an explicit timezone
then, for the purpose of the operation, the implicit timezone provided by the dynamic
context (See
The function returns the elapsed time between the date/time instant arg2
and the date/time instant arg1, computed according to the algorithm given
in Appendix E of xs:dayTimeDuration.
If the normalized value of $arg1 precedes in time the normalized value of
$arg2, then the returned value is a negative duration.
Assume that the dynamic context provides an implicit timezone value of
-05:00.
- operator
when applied to two xs:date values.Returns the xs:dayTimeDuration that corresponds to the elapsed time between
the starting instant of $arg2 and the starting instant of
$arg2.
If either $arg1 or $arg2 do not contain an explicit timezone
then, for the purpose of the operation, the implicit timezone provided by the dynamic
context (See
The starting instant of an xs:date is the xs:dateTime at
00:00:00 on that date.
The function returns the result of subtracting the two starting instants using
op:subtract-dateTimes.
If the starting instant of $arg1 precedes in time the starting instant of
$arg2, then the returned value is a negative duration.
Assume that the dynamic context provides an implicit timezone value of
Z.
{ 2000,
10, 30, 0, 0, 0, xs:dayTimeDuration("PT0S") } and { 1999, 11, 28, 0, 0, 0,
xs:dayTimeDuration("PT0S") }.Now assume that the dynamic context provides an implicit timezone value of
+05:00.
{ 2000,
10, 29, 19, 0, 0, xs:dayTimeDuration("PT0S") } and { 1999, 11, 28, 0, 0, 0,
xs:dayTimeDuration("PT0S") }.- operator
when applied to two xs:time values.Returns the xs:dayTimeDuration that corresponds to the elapsed time between
the values of $arg2 and $arg1 treated as times on the same
date.
The function returns the result of the expression:
Any other reference date would work equally well.
Assume that the dynamic context provides an implicit timezone value of
-05:00. Assume, also, that the date components of the reference
xs:dateTime correspond to "1972-12-31".
xs:dateTime
value { 1972, 12, 31, 11, 12, 0, xs:dayTimeDuration("PT0S") } the xs:dateTime
value { 1972, 12, 31, 9, 0, 0, xs:dayTimeDuration("PT0S") }.xs:dateTime values are { 1972, 12, 31, 11,
0, 0, xs:dayTimeDuration("-PT5H") } and { 1972, 12, 31, 21, 30, 0, xs:dayTimeDuration("PT5H30M") }. These
normalize to { 1972, 12, 31, 16, 0, 0, xs:dayTimeDuration("PT0S") }
and { 1972, 12, 31, 16, 0, 0, xs:dayTimeDuration("PT0S") }.
xs:dateTime values are { 1972,
12, 31, 23, 0, 0, xs:dayTimeDuration("PT0S") } and { 1972, 12, 30, 23, 0, 0,
xs:dayTimeDuration("PT0S") }.xs:dateTime values are { 1972,
12, 31, 0, 0, 0, () } and { 1972, 12, 31, 23, 59, 59.0,
() }.+ operator when applied to an xs:dateTime and an
xs:yearMonthDuration value. Returns the xs:dateTime that is a given duration after a specified
xs:dateTime (or before, if the duration is negative).
The function returns the result of adding $arg2 to the value of
$arg1 using the algorithm described in Appendix E of $arg2
is negative, then the result xs:dateTime precedes $arg1.
The result has the same timezone as $arg1. If $arg1 has no
timezone, the result has no timezone.
+ operator when applied to an xs:dateTime and an
xs:dayTimeDuration value. Returns the xs:dateTime that is a given duration after a specified
xs:dateTime (or before, if the duration is negative).
The function returns the result of adding $arg2 to the value of
$arg1 using the algorithm described in Appendix E of $arg2
is negative, then the result xs:dateTime precedes $arg1.
The result has the same timezone as $arg1. If $arg1 has no
timezone, the result has no timezone.
- operator when applied to an xs:dateTime and an
xs:yearMonthDuration value. Returns the xs:dateTime that is a given duration before a specified
xs:dateTime (or after, if the duration is negative).
The function returns the xs:dateTime computed by negating
$arg2 and adding the result to $arg1 using the
function op:add-yearMonthDuration-to-dateTime.
- operator when applied to an xs:dateTime an and
xs:dayTimeDuration valuesReturns the xs:dateTime that is a given duration before a specified
xs:dateTime (or after, if the duration is negative).
The function returns the xs:dateTime computed by negating
$arg2 and adding the result to $arg1 using the
function op:add-dayTimeDuration-to-dateTime.
+ operator when applied to an xs:date and an
xs:yearMonthDuration value. Returns the xs:date that is a given duration after a specified
xs:date (or before, if the duration is negative).
The function returns the result of casting $arg1 to an
xs:dateTime, adding $arg2 using the function
op:add-yearMonthDuration-to-dateTime, and casting the result back to an
xs:date.
+ operator when applied to an xs:date and an
xs:dayTimeDuration value. Returns the xs:date that is a given duration after a specified
xs:date (or before, if the duration is negative).
The function returns the result of casting $arg1 to an
xs:dateTime, adding $arg2 using the function
op:add-dayTimeDuration-to-dateTime, and casting the result back to an
xs:date.
xs:dateTime value { 2004, 10, 30, 0, 0, 0, xs:dayTimeDuration("PT0S") }.
Adding the second argument to this gives the xs:dateTime value
{ 2004, 11, 1, 2, 30, 0, xs:dayTimeDuration("PT0S") }. The time components are then
discarded. - operator when applied to an xs:date and an
xs:yearMonthDuration value. Returns the xs:date that is a given duration before a specified
xs:date (or after, if the duration is negative).
Returns the xs:date computed by negating $arg2 and adding the
result to $arg1 using the function
op:add-yearMonthDuration-to-date.
- operator when applied to an xs:date and an
xs:dayTimeDuration. Returns the xs:date that is a given duration before a specified
xs:date (or after, if the duration is negative).
Returns the xs:date computed by negating $arg2 and adding the
result to $arg1 using the function
op:add-dayTimeDuration-to-date.
+ operator when applied to an xs:time and an
xs:dayTimeDuration value.Returns the xs:time value that is a given duration after a specified
xs:time (or before, if the duration is negative or causes wrap-around
past midnight)
First, the days component in the canonical lexical representation of $arg2
is set to zero (0) and the value of the resulting xs:dayTimeDuration is
calculated. Alternatively, the value of $arg2 modulus 86,400 is used as the
second argument. This value is added to the value of $arg1 converted to an
xs:dateTime using a reference date such as 1972-12-31, and
the time component of the result is returned. Note that the xs:time
returned may occur in a following or preceding day and may be less than
$arg1.
The result has the same timezone as $arg1. If $arg1 has no
timezone, the result has no timezone.
{ 0, 0, 0, 2, 27, 0, xs:dayTimeDuration("PT3H") }- operator when applied to an xs:time and an
xs:dayTimeDuration value. Returns the xs:time value that is a given duration before a specified
xs:time (or after, if the duration is negative or causes wrap-around
past midnight)
The function returns the result of negating $arg2 and adding the result to
$arg1 using the function op:add-dayTimeDuration-to-time.
Returns a string containing an xs:dateTime value formatted for display.
See
The 3rd, 4th, and 5th arguments are now optional; previously the function required either 2 or 5 arguments.
Returns a string containing an xs:date value formatted for display.
See
The 3rd, 4th, and 5th arguments are now optional; previously the function required either 2 or 5 arguments.
Returns a string containing an xs:time value formatted for display.
See
The 3rd, 4th, and 5th arguments are now optional; previously the function required either 2 or 5 arguments.
Parses a string containing the date and time in IETF format, returning the corresponding
xs:dateTime value.
The function accepts a string matching the production input in the
following grammar:
input
|
::=
|
S? (dayname ","? S)? ((datespec S time) | asctime) S?
|
dayname
|
::=
|
"Mon" | "Tue" | "Wed" | "Thu" | "Fri" | "Sat" | "Sun" | "Monday | "Tuesday"
| "Wednesday" | "Thursday" | "Friday" | "Saturday" | "Sunday"
|
datespec
|
::=
|
daynum dsep monthname dsep year
|
asctime
|
::=
|
monthname dsep daynum S time S year
|
dsep
|
::=
|
S | (S? "-" S?)
|
daynum
|
::=
|
digit digit?
|
year
|
::=
|
digit digit (digit digit)?
|
digit
|
::=
|
[0-9]
|
monthname
|
::=
|
"Jan" | "Feb" | "Mar" | "Apr" | "May" | "Jun" | "Jul" | "Aug" | "Sep" |
"Oct" | "Nov" | "Dec"
|
time
|
::=
|
hours ":" minutes (":" seconds)? (S? timezone)?
|
hours
|
::=
|
digit digit? |
minutes
|
::=
|
digit digit
|
seconds
|
::=
|
digit digit ("." digit+)?
|
timezone
|
::=
|
tzname | tzoffset (S? "(" S? tzname S? ")")?
|
tzname
|
::=
|
"UT" | "UTC" | "GMT" | "EST" | "EDT" | "CST" | "CDT" | "MST" | "MDT" | "PST"
| "PDT"
|
tzoffset
|
::=
|
("+"|"-") hours ":"? minutes? |
S
|
::=
|
(x09 | x0A | x0D | x20)+
|
The input is case-insensitive: upper-case and lower-case distinctions in the above grammar show the conventional usage, but otherwise have no significance.
If the input is an empty sequence, the result is an empty sequence.
The dayname, if present, is ignored.
The daynum, monthname, and year supply the day,
month, and year of the resulting xs:dateTime value. A two-digit year
The hours, minutes, and seconds (including
fractional seconds) values supply the corresponding components of the resulting
xs:dateTime value; if the seconds value
If both a tzoffset and a tzname are supplied then the
tzname is ignored.
If a tzoffset is supplied then this defines the hours and minutes parts of the timezone offset:
If it contains a colon, this separates the hours part from the minutes part.
Otherwise, the grammar allows a sequence of from one to four digits. These are interpreted
as H, HH, HMM, or HHMM respectively, where H
or HH is the hours part, and MM (if present) is the minutes part.
If the minutes part is absent it defaults to 00.
If a tzname is supplied with no tzoffset then it is translated
to a timezone offset as follows:
| tzname | Offset |
|---|---|
| UT, UTC, GMT | 00:00 |
| EST | -05:00 |
| EDT | -04:00 |
| CST | -06:00 |
| CDT | -05:00 |
| MST | -07:00 |
| MDT | -06:00 |
| PST | -08:00 |
| PDT | -07:00 |
If neither a tzoffset nor tzname is supplied, a timezone
offset of 00:00 is assumed.
A dynamic error is raised "31 February").
The parse-ietf-date function attempts to interpret its input as a date
in any of the three formats specified by HTTP
These formats are used widely on the Internet to represent timestamps, and were specified in:
POSIX asctime() format
The grammar for this function is slightly more liberal than the RFCs (reflecting the internet tradition of being liberal in what is accepted). For example the function:
Accepts a single-digit value where appropriate in place of a two-digit value with a leading zero (so
"Wed 1 Jun" is acceptable in place of "Wed 01 Jun",
"-5:00" is equivalent to "-05:00")
Accepts one or more whitespace characters (x20, x09, x0A, x0D) wherever a single space is required, and allows whitespace to be omitted where it is not required for parsing
Accepts and ignores whitespace characters (x20, x09, x0A, x0D) at the start or end of the string.
In new protocols IETF recommends the format of
An "[FNn3], [D01] [MNn3] [Y04] [H01]:[m01]:[s01] [Z0000]".
Returns an xs:QName value (that is, an expanded-QName) by taking an
xs:string that has the lexical form of an xs:QName (a
string in the form "prefix:local-name" or "local-name")
and resolving it using the in-scope namespaces for a given element.
If $value is the empty sequence, returns the empty sequence.
More specifically, the function searches the namespace bindings of $element
for a binding whose name matches the prefix of $value, or the zero-length
string if it has no prefix, and returns an expanded-QName whose local name is taken
from the supplied $value, and whose namespace URI is taken from the string
value of the namespace binding.
If the $value has no prefix, and there is no namespace binding for
$element corresponding to the default (unnamed) namespace, then the
resulting expanded-QName has no namespace part.
The prefix (or absence of a prefix) in the supplied $value argument is
retained in the returned expanded-QName, as described in
A dynamic error is raised $value does
not have the correct lexical form for an instance of xs:QName.
A dynamic error is raised $value has
a prefix and there is no namespace binding for $element that matches this
prefix.
Sometimes the requirement is to construct an xs:QName without using the
default namespace. This can be achieved by writing:
If the requirement is to construct an xs:QName using the namespaces in the
static context, then the xs:QName constructor should be used.
Assume that the element bound to $element has a single namespace binding
bound to the prefix eg.
fn:resolve-QName("hello", $element) returns a QName with local name
"hello" that is in no namespace.
fn:resolve-QName("eg:myFunc", $element) returns an xs:QName
whose namespace URI is specified by the namespace binding corresponding to the prefix
"eg" and whose local name is "myFunc".
Returns an xs:QName value formed using a supplied namespace URI and lexical QName.
The namespace URI in the returned QName is taken from $uri. If
$uri is the zero-length string or the empty sequence, it represents
“no namespace”.
The prefix (or absence of a prefix) in $qname is retained in the
returned xs:QName value.
The local name in the result is taken from the local part of
$qname.
A dynamic error is raised $qname
does not have the correct lexical form for an instance of xs:QName.
A dynamic error is raised $uri
is the zero-length string or the empty sequence, and the value of
$qname contains a colon (:).
A dynamic error $uri is not a valid URI (XML Namespaces 1.0) or IRI (XML Namespaces
1.1).
fn:QName("http://www.example.com/example", "person") returns an
xs:QName with namespace URI "http://www.example.com/example",
local name "person" and prefix "".
fn:QName("http://www.example.com/example", "ht:person") returns an
xs:QName with namespace URI "http://www.example.com/example",
local name "person" and prefix "ht".
Returns an xs:QName value formed by parsing an EQName.
If $value is an empty sequence, the result is an empty sequence.
Otherwise, leading and trailing whitespace in $value is stripped.
If the resulting $value is castable to xs:NCName,
the result is fn:QName("", $value): that is, a QName in no namespace.
Otherwise, if the resulting $value is in the lexical space of xs:QName
(that is, if it is in the form prefix:local), the result is xs:QName($value).
Note that this result depends on the in-scope prefixes in the static context, and may result in
various error conditions.
Otherwise, if the resulting $value takes the form of an
XPath Q{uri}local, where the uri part may be zero-length),
then the result is fn:QName(uri, local).
The rules used for parsing a <
and & to be escaped).
A dynamic error is raised $value, after whitespace normalization,
does not match the XPath production
A dynamic error is raised $value, after whitespace normalization,
is in the form prefix:local (with a non-absent prefix), and
the prefix cannot be resolved to a namespace URI using the in-scope namespace
bindings from the static context.
fn:parse-QName("Q{http://www.example.com/example}person") returns an
xs:QName with namespace URI "http://www.example.com/example",
local name "person" and prefix "".
fn:parse-QName("person") returns an
xs:QName with absent namespace URI, local
name "person" and prefix "".
fn:parse-QName("Q{}person") returns an
xs:QName with absent namespace URI, local
name "person" and prefix "".
fn:parse-QName("p:person") returns an
xs:QName with namespace URI obtained from the static context, local
name "person" and prefix "p"
(The result is the same as the QName literal #p:person).
New in 4.0
Returns a string representation of an xs:QName in the format Q{uri}local.
If $value is the empty sequence, returns the empty sequence.
The result is a string in the format Q{uri}local, where:
uri
is the result of fn:string(fn:namespace-uri-from-QName($value))
(which will be a zero-length string if the QName is in no namespace), and
local is the result of
fn:local-name-from-QName($value).
There is no escaping of special characters in the namespace URI. If the namespace URI
contains curly braces, the resulting string will not be a valid
New in 4.0
eq and ne operators when applied to two values of type xs:QName. Returns true if two supplied QNames have the same namespace URI and the
same local part.
The function returns true if the namespace URIs of $arg1 and
$arg2 are equal and the local names of $arg1 and
$arg2 are equal.
Otherwise, the function returns false.
The namespace URI parts are considered equal if they are both
The local parts are also compared under the rules of the
The prefix parts of $arg1 and $arg2, if any, are ignored.
Returns the prefix component of the supplied QName.
If $value is the empty sequence the function returns the empty sequence.
If $value has no prefix component the function returns the empty
sequence.
Otherwise, the function returns an xs:NCName representing the prefix
component of $value.
Returns the local part of the supplied QName.
If $value is the empty sequence the function returns the empty sequence.
Otherwise, the function returns an xs:NCName representing the local part of
$value.
Returns the namespace URI part of the supplied QName.
If $value is the empty sequence the function returns the empty sequence.
Otherwise, the function returns an xs:anyURI representing the namespace URI
part of $value.
If $value is in no namespace, the function returns the zero-length
xs:anyURI.
Returns the namespace URI of one of the in-scope namespaces for $element,
identified by its namespace prefix.
The function returns the result of the expression map:get(fn:in-scope-namespaces($element), string($value)).
Reformulated in 4.0 in terms of the new
Returns the in-scope namespaces of an element node, as a map.
The function returns a map representing the prefixes of the in-scope
namespaces for $element. The map contains one entry
for each in-scope namespace: the key of the entry is the namespace
prefix or a zero-length string, and the corresponding value is the namespace URI.
For namespace bindings that have a prefix, the key represents the prefix as an
instance of xs:NCName. For the default namespace, which has no prefix, the key is
the zero-length string as an instance of xs:string.
The order of entries in the returned map is
The XML namespace is in scope for every element, so the result will always include an entry
with key "xml" and corresponding value http://www.w3.org/XML/1998/namespace.
New in 4.0
Returns the prefixes of the in-scope namespaces for an element node.
The function returns the result of the expression
map:keys(fn:in-scope-namespaces($element)) (but in no defined order).
The XML namespace is in scope for every element, so the result will always include the string "xml".
Reformulated in 4.0 in terms of the new
eq and ne operators when applied to two xs:hexBinary
or xs:base64Binary values.Returns true if both binary values contain the same octet
sequence.
The function returns true if $value1 and $value2
are of the same length, measured in binary octets, and contain the same octets in the
same order. Otherwise, it returns false.
Atomic items of types xs:hexBinary
and xs:base64Binary are now mutually comparable.
lt operator when applied to two xs:hexBinary or
xs:base64Binaryvalues. Also used in the
definition of the ge operator.Returns true if the first argument is less than the second.
Each of the two arguments are converted to a sequence of octets, $A and
$B, and the first octet in each sequence, $a and
$b, are compared.
If $a is empty and $b is non-empty return true.
If $b is empty return false.
Otherwise (neither $a nor $b are empty):
If $a and $b are identical the result is obtained
by applying these same rules recursively to fn:tail($A) and
fn:tail($B).
Otherwise, if $a is less than $b,
treating the value of each octet as an unsigned integer in the range 0 to
255, then return true, otherwise return false.
Atomic items of types xs:hexBinary
and xs:base64Binary are now mutually comparable.
eq and ne operators when applied to two values of type
xs:NOTATION. Returns true if the two xs:NOTATION values have the same
namespace URI and the same local part.
The function returns true if the namespace URIs of $arg1 and
$arg2 are equal and the local names of $arg1 and
$arg2 are equal.
Otherwise, the function returns false.
The namespace URI parts are considered equal if they are both
The local parts are also compared under the rules of the
The prefix parts of $arg1 and $arg2, if any, are ignored.
Returns the name of a node, as an xs:string that is either the zero-length
string, or has the lexical form of an xs:QName.
If the argument is omitted, it defaults to the context value (.).
If the argument is supplied and is the empty sequence, the function returns the zero-length string.
If the node identified by $node has no name (that is, if it is a document
node, a comment, a text node, or a namespace node having no name), the function returns
the zero-length string.
Otherwise, the function returns the value of the expression
fn:string(fn:node-name($node)).
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?, type error
Because the result depends on the choice of namespace prefixes in the source document,
it is not good practice to use the result of this function for anything other than display
purposes. For example, the test name(.) = 'my:profile' will fail if the source
document uses an unexpected namespace prefix. Such a test (assuming it relates to an element node)
is better written as boolean(self::my:profile).
One
Two
Returns the local part of the name of $node as an xs:string
that is either the zero-length string, or has the lexical form of an
xs:NCName.
If the argument is omitted, it defaults to the context value (.).
If the argument is supplied and is the empty sequence, the function returns the zero-length string.
If the node identified by $node has no name (that is, if it is a document
node, a comment, a text node, or a namespace node having no name), the function returns
the zero-length string.
Otherwise, the function returns the local part of the expanded-QName of the node
identified by $node, as determined by the dm:node-name accessor
defined in xs:string whose lexical form is an xs:NCName.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not a single node, type error
One
Two
Returns the namespace URI part of the name of $node, as an
xs:anyURI value.
If the argument is omitted, it defaults to the context node (.).
If the node identified by $node is neither an element nor an attribute node,
or if it is an element or attribute node whose expanded-QName (as determined by the
dm:node-name accessor in the xs:anyURI
value.
Otherwise, the result will be the namespace URI part of the expanded-QName of the node
identified by $node, as determined by the dm:node-name accessor
defined in xs:anyURI value.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?, type error
One
Two
Returns the value indicated by $value or, if $value is not
specified, the context value after atomization, converted to an xs:double.
Calling the zero-argument version of the function is defined to give the same result as
calling the single-argument version with the context value (.). That is,
fn:number() is equivalent to fn:number(.), as defined by
the rules that follow.
If $value is the empty sequence or if $value cannot be converted
to an xs:double, the xs:double value NaN is
returned.
Otherwise, $value is converted to an xs:double following the
rules of xs:double
fails, the xs:double value NaN is returned.
A type error is raised $value is omitted and the context value is
As a consequence of the rules given above, a type error is raised
XSD 1.1 allows the string +INF as a representation of positive infinity;
XSD 1.0 does not. It is
Generally NaN rather than raising a dynamic
error if the argument cannot be converted to xs:double. However, a type
error is raised in the usual way if the supplied argument cannot be atomized or if the
result of atomization does not match the required argument type.
This function tests whether the language of $node, or the context value if
the second argument is omitted, as specified by xml:lang attributes is the
same as, or is a sublanguage of, the language specified by $language.
The behavior of the function if the second argument is omitted is exactly the same as if
the context value (.) had been passed as the second argument.
The language of the argument $node, or the context value if the second
argument is omitted, is determined by the value of the xml:lang attribute
on the node, or, if the node has no such attribute, by the value of the
xml:lang attribute on the nearest ancestor of the node that has an
xml:lang attribute. If there is no such ancestor, then the function
returns false.
If $language is the empty sequence it is interpreted as the zero-length
string.
The relevant xml:lang attribute is determined by the value of the XPath
expression:
If this expression returns an empty sequence, the function returns false.
Otherwise, the function returns true if and only if, based on a caseless
default match as specified in section 3.13 of
$language is equal to the string-value of the relevant
xml:lang attribute, or
$language is equal to some substring of the string-value of the
relevant xml:lang attribute that starts at the start of the
string-value and ends immediately before a hyphen, -
(HYPHEN-MINUS, #x002D).
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not a single node, type error
The expression fn:lang("en") would return true if the
context node were any of the following four elements:
<para xml:lang="en"/>
<div xml:lang="en"><para>And now, and
forever!</para></div>
<para xml:lang="EN"/>
<para xml:lang="en-us"/>
The expression fn:lang("fr") would return false if the
context node were <para xml:lang="EN"/>
Returns a path expression that can be used to select the supplied node relative to the root of its containing document.
The behavior of the function if the $nodeargument is omitted is exactly the same as if the
context value (.) had been passed as the argument.
If $node is the empty sequence, the function returns the empty sequence.
The $options argument, if present, defines additional parameters controlling
how the output is formatted. The
$node. If present,
the returned path will be a relative path that selects $node
starting from the supplied origin node, rather than from the root of the
containing tree.
Q{uri}local notation.
Let R be the GNode supplied in the origin option,
or the root GNode of the tree containing $node otherwise.
If $node is a document node, or a JNode with no parent,
the function returns the string "/".
Otherwise, the function returns a string that consists of a sequence of steps, one
for each ancestor-or-self of $node that is not an ancestor-or-self
of R.
If R is an XNode other than a document node and the origin option
is absent or empty, then this string is preceded by
a string notionally representing a call to the fn:root function,
expressed as follows:
If the lexical option is present with the value true,
then the string "fn:root()".
If the namespaces option is present and defines a mapping from a
non empty prefix P
to the namespace URI http://www.w3.org/2005/xpath-functions, then
"P:root()"
If the namespaces option is present and defines a mapping from the empty string
to the namespace URI http://www.w3.org/2005/xpath-functions, then
"root()"
Otherwise, "Q{http://www.w3.org/2005/xpath-functions}root()".
Each step is the concatenation of:
The character "/", which is omitted for the first step
if the origin option is present;
A string whose form depends on the kind of node selected by that step, as follows:
For an element node, the concatenation of:
A representation of the element name, chosen as follows:
If the lexical option is present with the value
true, then the result of applying the
Otherwise, if the namespaces option is present
and the element is in a namespace U and the namespaces option
includes a mapping from a prefix P to the namespace U,
then the string P:L, where L
is the local part of the element name.
If there is more than one such prefix, then one of them is chosen arbitrarily.
Otherwise, if the namespaces option is present
and the element is in a namespace U and the namespaces option
includes a mapping from the zero-length string to the namespace U,
then the local part of the element name.
Otherwise, if the namespaces option is present
and the element is in no namespace and the namespaces option
includes no mapping from the zero-length string to any namespace,
then the local part of the element name.
Otherwise, the string Q{U}L,
where U is the namespace URI of the element name or the
empty string if the element is in no namespace, and L is
the local part of the element name.
Unless the indexes option is present
with the value false,
a string in the form [position] where position is an
integer representing the one-based position of the selected node among its like-named
siblings.
For an attribute node, the concatenation of:
The character "@"
If the lexical option is present with the value
true, then the result of applying the
Otherwise, if the attribute node is in no namespace, the local part of the attribute name.
Otherwise, if the namespaces option is present, and if it includes a mapping
from a non-empty namespace prefix P to the namespace URI of the attribute, then
a string in the form P:L, where L
is the local part of the attribute name.
If there is more than one such prefix, then one of them is chosen arbitrarily.
Otherwise, the string Q{U}L,
where U is the namespace URI of the attribute name, and L is
the local part of the attribute name.
For a text node: text()[position] where
position is an integer representing the position
of the selected node among its text node siblings.
The suffix [position] is omitted if the indexes
option is present with the value false.
For a comment node: comment()[position] where
is an integer representing the position
of the selected node among its comment node siblings.
The suffix [position] is omitted if the indexes
option is present with the value false.
For a processing-instruction node:
processing-instruction(local)[position]
where is the name of the processing instruction
node and is an integer representing the
position of the selected node among its like-named processing-instruction node
siblings.
The suffix [position] is omitted if the indexes
option is present with the value false.
For a namespace node:
If the namespace node has a name:
namespace::, where
is the local part of the name of the
namespace node (which represents the namespace prefix).
If the namespace node has no name (that is, if it represents the default
namespace):
namespace::*[Ulocal-name() = ""]
Here Ulocal-name() represents a call on the function
fn:local-name and is formatted using the same
conventions as the call on fn:root described earlier.
For a JNode where the ·content· property of the parent
is an array, then as the string *[N] where N
is the value of the ·selector· property.
For any other JNode (including the case where the ·content· property of the parent is a map):
If the value is an xs:string, xs:untypedAtomic,
or xs:anyURI that is castable to xs:NCName, then
the result of casting the value to xs:NCName.
If the value is an xs:string, xs:untypedAtomic,
or xs:anyURI that is not castable to xs:NCName, then
then as the string get("S")
where S is the string value.
If the value is numeric, then as the string get(N)
where N is the result of casting the numeric value to
xs:string.
If the value is an xs:QName, then as the string
get(#Q{uri}local) where uri
and local are the namespace URI and local name parts of the QName.
If the value is an xs:boolean, then as the string
get(true()) or get(false()).
If the value is of any other type, then as the string
get(xs:T("S")) where T is the
local part of the most specific built-in atomic type of which the value
is an instance, and S is the result of casting the value to
xs:string.
TODO: Better handling of the case where the parent is neither a map nor an array, for example where it is a sequence of several maps or several arrays. It's hard to provide a better path for these when there is no AxisStep for selecting within such values.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?, type error
If the value of the origin option is a node that is not an ancestor
of $node (or in the absence of $node, the context value),
dynamic error
Using the namespaces option to shorten the generated path is often convenient,
but the resulting path may be unusable if the input tree contains multiple bindings for the same prefix.
Similarly, using the lexical option is convenient if there is no need for precise
namespace information: it is especially suitable when the containing node tree declares no namespaces.
If the supplied argument is a map or an array, it will automatically be coerced to a JNode. This
however is not useful, because this will be a root JNode, yielding the path /.
Options are added to customize the form of the output.
The function is extended to handle JNodes.
Returns the root of the tree to which $node belongs. The
function can be applied both to
If the function is called without an argument, the context value (.) is used
as the default argument.
The function returns the value of the expression
$node/ancestor-or-self::gnode()[last()].
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type
gnode()?, type error
These examples use some variables which could be defined in
Or they could be defined in
root($i) returns the element node $i
root($o/quantity) returns the element node $o
root($odoc//quantity) returns the document node $odoc
root($newi) returns the element node $o
The final three examples could be made type-safe by wrapping their operands with
exactly-one().
Returns true if the supplied GNode has one or more child nodes (of any kind).
If the argument is omitted, it defaults to the context value (.).
Provided that the supplied argument $node matches the expected type
gnode()?, the result of the function call
fn:has-children($node) is defined to be the same as the result of the
expression fn:exists($node/child::gnode()).
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type gnode()?, type error
If $node is an empty sequence the result is false.
The motivation for this function is to support streamed evaluation. According to the
streaming rules in
This is because it makes two downward selections to read the child row
elements. The use of xsl:if conditional
is intended to circumvent this restriction.
Although the function was introduced to support streaming use cases, it has general utility as a convenience function.
If the supplied argument is a map or an array, it will automatically be coerced to a JNode.
One
Three
]]>Generalized to work with JNodes as well as XNodes.
Removes duplicate GNodes and sorts the input into document order.
Any duplicate GNodes (that is, XNodes or JNodes) in the input
(based on node identity) are discarded. The remaining GNodes
are returned in
Document order is
$x//b expressions select the same node; one of these
is eliminated as a duplicate. The $x//c expression selects two nodes
that have distinct identity, so both are retained.New in 4.0
Returns every GNode within the input sequence that is not an ancestor of another member of the input sequence; the GNodes are returned in document order with duplicates eliminated.
The effect of the function call fn:innermost($nodes) is defined to be
equivalent to the result of the expression:
That is, the function takes as input a sequence of GNodes, and returns every GNode within the sequence that is not an ancestor of another GNode within the sequence; the GNodes are returned in document order with duplicates eliminated.
If the supplied argument includes a map or an array, it will automatically be coerced to a JNode.
"c"[1,2], [3,4], [5,6], [7,8]Generalized to work with JNodes as well as XNodes.
Returns every GNode within the input sequence that has no ancestor that is itself a member of the input sequence; the nodes are returned in document order with duplicates eliminated.
The effect of the function call fn:outermost($nodes) is defined to be
equivalent to the result of the expression:
That is, the function takes as input a sequence of GNodes, and returns every GNode within the sequence that does not have another GNode within the sequence as an ancestor; the GNodes are returned in document order with duplicates eliminated.
The formulation $nodes except $nodes/descendant::node() might appear to be
simpler, but does not correctly account for attribute nodes, as these are not
descendants of their parent element.
The motivation for the function was based on XSLT streaming use cases. There are cases
where the outermost(//section) but do not allow //section; the
function can therefore be useful in cases where it is known that sections will not be
nested, as well as cases where the application actually wishes to process all sections
except those that are nested within another.
If the supplied argument includes a map or an array, it will automatically be coerced to a JNode.
"a"3Generalized to work with JNodes as well as XNodes.
Returns a sequence of positive integers giving the positions within the sequence
$input of items that are equal to $target.
The function returns a sequence of positive integers giving the positions within the
sequence $input of items that are equal to $target.
The collation used by this function is determined according to the rules in
The items in the sequence $input are compared with $target under
the rules for the eq operator. Values of type xs:untypedAtomic
are compared as if they were of type xs:string. Values that cannot be
compared, because the eq operator is not defined for their types, are
considered to be distinct. If an item compares equal, then the position of that item in
the sequence $input is included in the result.
The first item in a sequence is at position 1, not position 0.
The result sequence is in ascending numeric order.
If $input is the empty sequence, or if no item in
$input matches $target, then the function returns the empty
sequence.
No error occurs if non-comparable values are encountered. So when comparing two atomic
items, the effective boolean value of fn:index-of($a, $b) is true if
$a and $b are equal, false if they are not equal or not
comparable.
If @a is an attribute of type xs:NMTOKENS whose string
value is "red green blue", and whose typed value is therefore
("red", "green", "blue"), then fn:index-of(@a, "blue")
returns 3. This is because the function calling mechanism atomizes the
attribute node to produce a sequence of three xs:NMTOKEN values.
Returns true if the argument is the empty sequence.
If $input is the empty sequence, the function returns
true; otherwise, the function returns false.
Assuming $break is an element with no children:
The result is false().
Returns the supplied GNode together with its siblings, in document order.
If the $node argument is omitted, it defaults to the context value (.).
If the value of $node is an empty sequence, the function returns an empty sequence.
If $node is a child of some parent GNode P, the function returns all the
children of P (including $node), in document order, as determined
by the value of $node/child::gnode().
Otherwise (specifically, if $node is parentless, or if it is an attribute or namespace node),
the function returns $node.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type node()?, type error
The result of siblings($n) (except in error cases) is the same as
the result of $n/(preceding-sibling::node() | following-sibling-or-self::node()).
It is also the same as $n/(preceding-sibling-or-self::node() | following-sibling::node())
As with names such as parent and child, the word
New in 4.0
Returns true if the argument is a non-empty sequence.
If $input is a non-empty sequence, the function returns
true; otherwise, the function returns false.
Assuming $break is an element with no children:
The result is true().
Returns the values that appear in a sequence, with duplicates eliminated.
The function returns the sequence that results from removing from $values all
but one of a set of values that are considered equal to one another.
fn:deep-equal($J, $K, $coll) is true,
where $coll is the collation selected according to the rules in
The ordering of the result is as follows:
For any set of values that compare equal, the one that is
returned is the one that appears first in $values.
The items that are returned appear in the order of their first
appearance within $values.
If $values is the empty sequence, the function returns the empty sequence.
Values of type xs:untypedAtomic are compared as if they were of type
xs:string.
Values that cannot be compared, because the eq operator is not defined for
their types, are considered to be distinct.
For xs:float and xs:double values, positive zero is equal to
negative zero and, although NaN does not equal itself, if $values
contains multiple NaN values a single NaN is returned.
If xs:dateTime, xs:date or xs:time values do not
have a timezone, they are considered to have the implicit timezone provided by the
dynamic context for the purpose of comparison. Note that xs:dateTime,
xs:date or xs:time values can compare equal even if their
timezones are different.
Changed in 4.0 to use transitive equality comparisons for numeric values.
The order of results is now prescribed; it was previously implementation-dependent.
Atomic items of types xs:hexBinary
and xs:base64Binary are now mutually comparable. In rare cases, where an
application uses both types and assumes they are distinct, this can represent a backwards
incompatibility.
Returns the values that appear in a sequence more than once.
The items of $values are compared against each other, according to the
rules of $coll as the collation
selected according to the rules in
From each resulting set of values that are considered equal, one value will be returned if the set contains more than one value.
Specifically, the function returns those items in $values that are
equal (under this definition) to exactly one item appearing earlier in the sequence
This means that the ordering of the result is as follows:
For any set of values that compare equal, the one that is
returned is the one that appears second in $values.
The items that are returned appear in the order of their second
appearance within $values.
"1" and the untyped value of the
element node are considered equal, whereas the string "2"
and the integer are considered unequal.Raise an error for duplicates in an ID sequence:
New in 4.0
Returns its argument value.
The function returns $input.
The function is useful in contexts where a function must be supplied, but no processing is required.
New in 4.0
Returns a sequence constructed by inserting an item or a sequence of items at a given position within an existing sequence.
The value returned by the function consists of all items of $input whose
1-based position is less than $position, followed by all items of
$insert, followed by the remaining elements of $input, in
that order.
If $input is the empty sequence, $insert is returned. If
$insert is the empty sequence, $input is returned.
If $position is less than one (1), the first position, the effective value
of $position is one (1). If $position is greater than the
number of items in $input, then the effective value of
$position is equal to the number of items in $input plus
1.
The value of $input is not affected by the sequence construction.
Returns a new sequence containing all the items of $input
The function returns a sequence consisting of all items of $input $positions.
Any integer in $positions that is less than 1 or greater than the number of items in
$input is effectively ignored.
If $input is the empty sequence, the empty sequence is returned.
If $positions is an empty sequence, the input sequence $input is returned unchanged.
The second argument can now be a sequence of integers.
Returns the first item in a sequence.
The function returns the first item in $input; if $input
is empty, it returns an empty sequence.
Returns all but the first item in a sequence.
The function all items in $input except the first, retaining order.
If $input is the empty sequence, or a sequence containing a single item, then
the empty sequence is returned.
Returns all but the last item in a sequence.
The function returns all items in $input except the last, retaining order.
If $input is the empty sequence, or a sequence containing a single item, then
the empty sequence is returned.
New in 4.0
Produces multiple copies of a sequence.
The function returns the value of (1 to $count) ! $input.
If $input is the empty sequence, the empty sequence is returned.
The $count argument is declared as xs:nonNegativeInteger,
which means that a type error occurs if it is called with a negative value.
If the input sequence contains nodes, these are not copied: instead, the result sequence contains
multiple references to the same node. So, for example, fn:count(fn:replicate(/, 6)|())
returns 1, because the
New in 4.0
Inserts a separator between adjacent items in a sequence.
The function inserts a separator between adjacent items in a sequence.
The input is returned unchanged if $separator is the empty sequence
or if $input contains less than two items.
Insert an empty hr element between adjacent paragraphs:
New in 4.0
Returns the last item in a sequence.
The function returns the value of the expression $input[last()]
If $input is the empty sequence the empty sequence is returned.
New in 4.0
Reverses the order of items in a sequence.
The function returns a sequence containing the items in $input in reverse
order.
If $input is the empty sequence, the empty sequence is returned.
Returns the contiguous sequence of items in $input
beginning at the position indicated by $start and
continuing for the number of items indicated by $length.
In the two-argument case
In the three-argument case, the function returns:
The first item of a sequence is located at position 1, not position 0.
If $input is the empty sequence, the empty sequence is returned.
In the two-argument case, the function returns a sequence comprising those items of
$input whose 1-based position
is greater than or equal to $start (rounded to an integer).
No error occurs if $start is zero or negative.
In the three-argument case, The function returns a sequence comprising those items of
$input whose 1-based position
is greater than or equal to $start (rounded to an integer), and
less than the sum of $start and $length (both rounded to integers).
No error occurs if $start is zero or negative, or if $start
plus $length exceeds the number of items in the sequence, or if
$length is negative.
As a consequence of the general rules, if $start is
-INF and $length is +INF, then
fn:round($start) + fn:round($length) is NaN; since
position() lt NaN always returns false, the result is an empty sequence.
The reason the function accepts arguments of type xs:double is that many
computations on untyped data return an xs:double result; and the reason for
the rounding rules is to compensate for any imprecision in these floating-point
computations.
The optional third argument can now be supplied as an empty sequence.
Returns a contiguous sequence of items from $input, with the start and end
points located by applying predicates.
Informally, the function returns the subsequence of $input starting with the
first item that matches the $from predicate, and ending with the first subsequent
item that matches the $to predicate. If $from is not supplied, it defaults
to the start of $input; if $to is not supplied, it defaults to the
end of $input. If $from does not match any items in $input,
the result is the empty sequence; if $to does not match any items, all items up
to the last are included in the result.
The result includes both the item that matches the $from condition
and the item that matches the $to condition. To select a subsequence that
starts after the $from item, apply the $to item,
apply the
The predicate functions supplied to the $from and $to
parameters can include an integer position argument as well as the item itself.
This position will always be 1-based, relative to the start of $input.
This means it is possible to select items based on their absolute position in the
$input sequence, but there is no mechanism to select an end position
relative to the start position. If this is needed, the function can be combined with others:
for example, to select a subsequence of four items starting with "Barbara",
use $input => subsequence-where(fn { . eq "Barbara" }) => slice(end := 4).
If the requirement is to select all elements stopping before the first h2
element if it exists, or up to the end of the sequence otherwise, the simplest
solution is perhaps to write:
A return value of () from the $from or $to
predicate is treated as false.
New in 4.0
Returns a sequence containing the items from $input
at positions defined by $at, in the order specified.
Returns the items in $input at the positions listed
in $at, in order of the integers in the $at argument.
In the simplest case where $at is a single integer,
fn:items-at($input, 3) returns the same result as $input[3].
Compared with a simple positional filter expression, the function is useful because:
It can select items at multiple positions, and unlike
The $at expression can depend on the focus.
The order of the returned items can differ from their order in the $input sequence.
If any integer in $at is outside the range 1 to count($input), that integer
is effectively ignored: no error occurs.
If either of the arguments is an empty sequence, the result is an empty sequence.
If $at contains duplicate integers, the result also contains duplicates. No de-duplication
occurs. If the input sequence contains nodes, these are not copied: instead, the result
sequence contains multiple references to the same node.
New in 4.0
Returns a sequence containing selected items from a supplied input sequence based on their position.
If $input is the empty sequence, the function returns the empty sequence.
Let $S be the first of the following that applies:
If $start is absent, empty, or zero, then 1.
If $start is negative, then fn:count($input) + $start + 1.
Otherwise, $start.
Let $E be the first of the following that applies:
If $end is absent, empty, or zero, then fn:count($input).
If $end is negative, then fn:count($input) + $end + 1.
Otherwise, $end.
Let $STEP be the first of the following that applies:
If $step is absent, empty, or zero, then:
If $E ge $S, then +1
Otherwise -1
Otherwise, $step.
If $STEP is negative, the function returns
$input => fn:reverse() => fn:slice(-$S, -$E, -$STEP).
Otherwise the function returns the result of the expression:
The function is inspired by the slice operators in Javascript and Python, but it differs
in detail to accommodate the tradition of 1-based addressing in XPath. The end position is
inclusive rather than exclusive, so that in the simple case where $start and
$end are positive and $end > $start,
fn:slice($in, $start, $end)
returns the same result as $in[position() = $start to $end].
This function can be used to enhance the RangeExpression, defined
in
New in 4.0
Determines whether one sequence starts with another, using a supplied callback function to compare items.
Informally, the function returns true if $input starts with $subsequence,
when items are compared using the supplied (or default) $compare function.
There is no requirement that the $compare function should have the traditional qualities
of equality comparison. The result is well-defined, for example, even if $compare is not transitive
or not symmetric. A return value of () from the function is treated as false.
"a".New in 4.0
Determines whether one sequence ends with another, using a supplied callback function to compare items.
Informally, the function returns true if $input ends with $subsequence,
when items are compared using the supplied (or default) $compare function.
There is no requirement that the $compare function should have the traditional qualities
of equality comparison. The result is well-defined, for example, even if $compare is not transitive
or not symmetric.
A return value of () from the function is treated as false.
New in 4.0
Determines whether one sequence contains another as a contiguous subsequence, using a supplied callback function to compare items.
Informally, the function returns true if $input contains a consecutive subsequence matching $subsequence,
when items are compared using the supplied (or default) $compare function.
There is no requirement that the $compare function should have the traditional qualities
of equality comparison. The result is well-defined, for example, even if $compare is not transitive
or not symmetric.
A return value of () from the function is treated as false.
p children of the chap element form a contiguous subsequence."a".New in 4.0
Returns the items of $input in an
The function returns the items of $input in an
Query optimizers may be able to do a better job if the order of the output sequence is not specified. For example, when retrieving prices from a purchase order, if an index exists on prices, it may be more efficient to return the prices in index order rather than in document order.
This function does not guarantee that the resulting sequence will be in an order different from the input sequence. Many times the two sequences will be identical.
Absorbs the argument.
The function absorbs the supplied $input argument and
returns an empty sequence.
The function can be used to discard unneeded output of expressions (functions, third-party libraries, etc.).
It can also be used to discard results during development.
It is
New in 4.0
Returns input if it contains zero or one items. Otherwise, raises an
error.
Except in error cases, the function returns $input unchanged.
A dynamic error is raised $input
contains more than one item.
Returns $input if it contains one or more items. Otherwise, raises an error.
Except in error cases, the function returns $input unchanged.
A dynamic error is raised $input is an
empty sequence.
Returns $input if it contains exactly one item. Otherwise, raises an error.
Except in error cases, the function returns $input unchanged.
A dynamic error is raised $input is an
empty sequence or a sequence containing more than one item.
This function assesses whether two sequences are deep-equal to each other. To be
deep-equal, they must contain items that are pairwise deep-equal; and for two items to
be deep-equal, they must either be atomic items that compare equal, or nodes of the
same kind, with the same name, whose children are deep-equal
The $options argument, if present, defines additional parameters controlling
how the comparison is done. If it is supplied as a map, then the
For backwards compatibility reasons, the $options argument can also be set
to a string containing a collation name. Supplying a string $S for this argument is equivalent
to supplying the map { 'collation': $S }. Omitting the argument, or supplying the
empty sequence, is equivalent to supplying an empty map.
If the two sequences ($input1 and $input2)
are both empty, the function returns true.
If the two sequences are of different lengths, the function returns
false.
If the two sequences are of the same length, the comparison is controlled by the
ordered option:
By default, the option is true: The function returns
true if and only if every item in the sequence $input1 is
deep-equal to the item at the same position in the sequence $input2.
If the option is set to false, the function returns
false if and only if every item in the sequence $input1
is deep-equal to an item at some position in the sequence $input2,
and vice versa.
The rules for deciding whether two items are deep-equal appear below.
The entries that may appear in the $options map are as follows. The detailed rules
for the interpretation of each option appear later.
base-uri of a node is significant.
false.
When this option is set and the two inputs are found to be not equal, the implementation
id property of elements and attributes is significant.
idrefs property of elements and attributes is significant.
true
or false to indicate that two items are or are not
equal, overriding the normal rules that would apply to those items;
or it can return an empty sequence, to indicate that the normal
rules should be followed. Note that returning ()
is false.
xs:QName values (particularly
the names of elements and attributes) are significant.
nilled property of elements and attributes is significant.
preserve retains all whitespace. The value strip ignores text nodes
consisting entirely of whitespace.
The value normalize ignores whitespace text nodes in the same way as
the strip option, and additionally compares text and attribute nodes after
normalizing whitespace in accordance with the rules of the xml:space attributes.
As a general rule for boolean options (but not invariably), the value true indicates
that the comparison is more strict.
In the following rules, where a recursive call on $options as the original call.
The rules reference a function equal-strings which compares two xs:string
or xs:anyURI values as follows:
If the whitespace option is set to normalize, then each string is processed
by calling the
If the normalization-form option is present, each string is then normalized
by calling the
The two strings are then compared for equality under the requested collation.
More formally, the equal-strings function is equivalent to the following
implementation in XQuery:
The rules for deciding whether two items $i1 and $i2 are deep-equal
are as follows.
The two items are first compared using the function supplied in the items-equal
option. If this returns true then the items are deep-equal. If it returns
false then the items are not deep-equal. If it returns an empty sequence
(which is always the case if the option is not explicitly specified)
then the two items are deep-equal if one or more of the following conditions are true:
All of the following conditions are true:
$i1 is an atomic item.
$i2 is an atomic item.
Either the type-annotations option is false, or both atomic items have
the same type annotation.
One of the following conditions is true:
If both $i1 and $i2 are instances of
xs:string, xs:untypedAtomic, or xs:anyURI,
equal-strings($i1, $i2, $collation, $options)
returns true.
If both $i1 and $i2 are instances of
xs:date, xs:time or xs:dateTime,
$i1 eq $i2
returns true.
Otherwise, fn:atomic-equal($i1, $i2)
returns true.
If $i1 and $i2 are not comparable, that is,
if the expression ($i1 eq $i2) would raise an error, then the function
returns false; it does not report an error.
One of the following conditions is true:
Option namespace-prefixes is false.
Neither $i1 nor $i2 is of type
xs:QName or xs:NOTATION.
$i1 and $i2 are qualified names with the same namespace prefix.
One of the following conditions is true:
Option timezones is false.
Neither $i1 nor $i2 is of type
xs:date, xs:time, xs:dateTime,
xs:gYear, xs:gYearMonth, xs:gMonth,
xs:gMonthDay, or xs:gDay.
Neither $i1 nor $i2 has a timezone component.
Both $i1 and $i2 have a timezone component and the
timezone components are equal.
All of the following conditions are true:
$i1 is a map.
$i2 is a map.
Both maps have the same number of entries.
For every entry in the first map, there is an entry in the second map that:
has the
has the same associated value (compared using the
Either map-order is false, or the entries in both maps appear in the same order,
that is, the Nth key in the first map is the
All the following conditions are true:
$i1 is an array.
$i2 is an array.
Both arrays have the same number of members (array:size($i1) eq
array:size($i2)).
Members in the same position of both arrays are deep-equal to each other: that is,
every $p in 1 to array:size($i1) satisfies deep-equal($i1($p), $i2($p),
$collation, $options).
All the following conditions are true:
$i1 is a function item and is not a map or array.
$i2 is a function item and is not a map or array.
$i1 and $i2 have the same function identity.
The concept of function identity is explained in
All the following conditions are true:
$i1 is a node (specifically, an XNode).
$i2 is a node (specifically, an XNode).
Both nodes have the same node kind.
Either the base-uri option is false, or both nodes have the same value
for their base URI property, or both nodes have an absent base URI.
Let significant-children($parent) be the sequence of nodes obtained by applying the following
steps to the children of $parent, in turn:
Comment nodes are discarded if the option comments is false.
Processing instruction nodes are discarded if the option processing-instructions is false.
Adjacent text nodes are merged.
Whitespace-only text nodes are discarded if both the following conditions are true:
The option whitespace is set to strip
or normalize; and
The text node is not within the scope
of an element that has the attribute xml:space="preserve".
Whitespace text nodes will already have been discarded if
$parent is a schema-validated element node whose type annotation
is a complex type with an element-only or empty content model.
One of the following conditions is true.
Both nodes are document nodes, and the sequence significant-children($i1)
is deep-equal to the sequence significant-children($i2).
Both nodes are element nodes, and all the following conditions are true:
The two nodes have the same name, that is (node-name($i1) eq
node-name($i2)).
Either the option namespace-prefixes is false, or both element
names have the same prefix.
Either the option in-scope-namespaces is false, or both element
nodes have the same in-scope namespace bindings.
Either the option type-annotations is false, or both
element nodes have the same type annotation.
Either the option id-property is false, or both element
nodes have the same value for their is-id property.
Either the option idrefs-property is false, or both element
nodes have the same value for their is-idrefs property.
Either the option nilled-property is false, or both element
nodes have the same value for their nilled property.
One of the following conditions is true:
The option type-variety is false.
Both nodes are annotated as having simple content.
For this purpose
Both nodes are annotated as having complex content. For this purpose
It is a consequence of this rule that, by default, validating a document D against a schema will usually (but not necessarily) result in a document that is not deep-equal to D. The exception is when the schema allows all elements to have mixed content.
The two nodes have the same number of attributes, and for every attribute
$a1 in $i1/@* there exists an attribute
$a2 in $i2/@* such that node-name($a1) eq node-name($a2)
and $a1 and $a2 are deep-equal.
Attributes, like other items, may be compared using the supplied items-equal
function. However, this function will not be called to compare two attribute nodes unless
they have the same name.
One of the following conditions holds:
Both element nodes are annotated as having simple content (as defined
above), the typed-values option is true,
and the typed value of $i1 is deep-equal
to the typed value of $i2.
The typed value of an element node is used only when the element has simple content, which means that no error can occur as a result of atomizing a node with no typed value.
Both element nodes are annotated as having simple content (as defined
above), the typed-values option is false,
and the equal-strings function returns true when
applied to the string value of $i1
and the string value of $i2.
Both element nodes have a type annotation that is a complex type with
element-only, mixed, or empty content,
the (common) element name is not present in the unordered-elements option,
and the sequence significant-children($i1) is
deep-equal to the sequence significant-children($i2).
Both element nodes have a type annotation that is a complex type with
element-only, mixed, or empty content,
the (common) element name is present in the unordered-elements option,
and the sequence significant-children($i1) is
deep-equal to some permutation of the sequence significant-children($i2).
Elements annotated as xs:untyped fall into this category.
Including an element name in the unordered-elements list is unlikely
to be useful except when the relevant elements have element-only content, but
this is not a requirement: the rules apply equally to elements with mixed content,
or even (trivially) to elements with empty content.
Both nodes are attribute nodes, and all the following conditions are true:
The two attribute nodes have the same name, that is (node-name($i1) eq
node-name($i2)).
Either the option namespace-prefixes is false, or both
attribute names have the same prefix.
Either the option type-annotations is false, or both
attribute nodes have the same type annotation.
Either the option id-property is false, or both attribute nodes
have the same value for their is-id property.
Either the option idrefs-property is false, or both attribute nodes
have the same value for their is-idrefs property.
Let T be true if the option typed-value is true
and both attributes $i1 and $i2 have a type
annotation other than xs:untypedAtomic.
Then either T is true and the typed value of $i1
is deep-equal to the typed value of $i2, or T is false
and the equal-strings function returns true when applied to the
string value of $i1 and the string value of $i2.
Both nodes are processing instruction nodes, and all the following conditions are true:
The two nodes have the same name, that is (node-name($i1) eq
node-name($i2)).
The equal-strings function returns true when applied to
the string value of $i1
and the string value of $i2.
Both nodes are namespace nodes, and all the following conditions are true:
The two nodes either have the same name or are both nameless, that is
fn:deep-equal(node-name($i1), node-name($i2)).
The string value of $i1 is equal to the string value of
$i2 when compared using the Unicode codepoint collation.
Namespace nodes are not considered directly unless they appear in the top-level sequences
passed explicitly to the
Both nodes are comment nodes, and the equal-strings function
returns true when applied to their string values.
Both nodes are text nodes, and the equal-strings function
returns true when applied to their string values.
All the following conditions are true:
$i1 is a JNode.
$i2 is a JNode.
The $i1
is deep-equal to the $i2.
The other properties of the two JNodes, such as
In all other cases the result is false.
A type error is raised $options includes an entry whose key is defined
in this specification, and whose value is not of the permitted type for that key.
A dynamic error is raised $options includes an entry whose key is defined
in this specification, and whose value is not a permitted value for that key.
By default, whitespace in text nodes and attributes is considered significant. There are various ways whitespace differences can be ignored:
If nodes have been schema-validated, setting the typed-values
option to true causes the typed values rather
than the string values to be compared. This will typically cause whitespace to be ignored
except where the type of the value is xs:string.
Setting the whitespace option to normalize causes all
text and attribute nodes to have leading and trailing whitespace removed, and intermediate
whitespace reduced to a single character.
By default, two nodes are not required to have the same type annotation, and they are not
required to have the same in-scope namespaces. They may also differ in their parent,
their base URI, and the values returned by the is-id and
is-idrefs accessors (see
By default, the contents of comments and processing instructions are significant only if these nodes
appear directly as items in the two sequences being compared. The content of a comment
or processing instruction that appears as a descendant of an item in one of the
sequences being compared does not affect the result.
Comparing items of different kind (for example, comparing an atomic
item to a node, or a map to an array, or an integer to an xs:date) returns false,
it does not return an error. So
the result of fn:deep-equal(1, current-dateTime()) is false.
The items-equal callback function may be used to override the default rules
for comparing individual items. For example, it might return true unconditionally
when comparing two @timestamp attributes, if there is no expectation that the
two trees will have identical timestamps. Given two nodes $n1 and $n2,
it might compare them using the is operator, so that instead of comparing the
descendants of the two nodes, the function simply checks whether they are the same node.
Given two function items $f1 and $f2 it might return true unconditionally,
knowing that there is no effective way to test if the functions are equivalent. Given
two numeric values, it might return true if they are equal to six decimal places.
It is good practice for the items-equal callback function to be reflexive,
symmetric, and transitive; if it is not, then the NaN)
should be equal to itself; items-equal(A, B)
should return the same result as items-equal(B, A), and items-equal(A, B) and items-equal(B, C) should
imply items-equal(A, C).
Setting the ordered option to false or supplying the
unordered-elements option may result in poor performance when comparing
long sequences, especially if the items-equal callback function is supplied.
unordered-elements option means that the ordering of the children
of a is ignored.style attribute
and the whitespace text node preceding the span element are significant.whitespace option causes both the leading space
in the attribute value and the whitespace preceding the
span element to be ignored.When comments and processing instructions are ignored, any text nodes either side of the comment or processing instruction are now merged prior to comparison.
The $options parameter has been added,
absorbing the $collation parameter.
A callback function can be supplied for comparing individual items.
Atomic items of types xs:hexBinary
and xs:base64Binary are now mutually comparable. In rare cases, where an
application uses both types and assumes they are distinct, this can represent a backwards
incompatibility.
Returns the number of items in a sequence.
The function returns the number of items in $input.
The function returns 0 if $input is the empty sequence.
Returns the average of the values in the input sequence $values, that is, the
sum of the values divided by the number of values.
If $values is the empty sequence, the empty sequence is returned.
Any item in $values that is an instance of xs:untypedAtomic
is cast to xs:double.
After this conversion, one of the following conditions must be true:
Every item in $values is an instance of xs:yearMonthDuration.
Every item in $values is an instance of xs:dayTimeDuration.
Every item in $values is an instance of xs:numeric.
The function returns the average of the values as sum($values) div
count($values); but the implementation may use an otherwise equivalent algorithm
that avoids arithmetic overflow. Note that the
A type error is raised
xs:decimal.fn:avg(($d1, $seq3)) raises a type error
In 3.1, given a mixed input sequence such as (1, 3, 4.2e0), the specification was unclear whether it was permitted to add the first two integer items using integer arithmetic, rather than converting all items to doubles before performing any arithmetic. The 4.0 specification is clear that this is permitted; but since the items can be reordered before being added, this is not required.
Returns a value that is equal to the highest value appearing in the input sequence.
Any item in $values that is an instance of xs:untypedAtomic
is first cast to xs:double. The resulting sequence is referred to as the
converted sequence.
All pairs of values in the converted sequence must be mutually comparable. Two values are mutually comparable if one or more of the following conditions applies:
Both values are instances of xs:string or xs:anyURI.
Both values are instances of xs:numeric.
Both values are instances of xs:hexBinary or xs:base64Binary.
Both values are instances of xs:date.
Both values are instances of xs:dateTime.
Both values are instances of xs:time.
Both values are instances of xs:dayTimeDuration.
Both values are instances of xs:yearMonthDuration.
Both values are instances of xs:boolean.
If the converted sequence contains a single value then it must be comparable to itself under the above rules. (So the
input cannot be, for example, a singleton xs:QName.)
If the converted sequence is empty, the function returns the empty sequence.
If the converted sequence contains the value NaN, the value
NaN is returned
xs:float or xs:double as appropriate)
Two items $v1 and $v2 from the converted sequence are compared as follows:
If both values are instances of xs:string or xs:anyURI, they
are compared using fn:compare($v1, $v2, $collation), where $collation
is determined by the rules in
In other cases, $collation is ignored.
If both values are instances of xs:numeric, they are compared
using fn:compare($v1, $v2).
In all other cases, the values are compared using the lt and eq
operators appropriate to their type.
The result of the function is a value from the converted sequence that is greater than
or equal to every other value under the above rules. If there is more than one such value, then it is
A type error is raised
If there are two or items that are
“equal highest”, the specific item whose value is returned is xs:dateTime
values compare equal despite being in different timezones.
If the converted sequence contains exactly one value then that value is returned.
The default type when the xs:untypedAtomic values is xs:double. This differs from the
default type for operators such as lt, and for sorting in XQuery and XSLT,
which is xs:string.
In version 4.0, if $values is a sequence of xs:decimal values
(including the case where it is a sequence of xs:integer values), then
the result will be one of these xs:decimal or xs:integer values.
In earlier versions it would
be the result of converting this xs:decimal to xs:double.
xs:integer or the xs:float,
since they are equal.max((3, 4, "Zero")) raises a type error
The way that xs:integer or xs:decimal values, the result is an xs:integer or
xs:decimal, rather than the result of converting this to an xs:double
Returns a value that is equal to the lowest value appearing in the input sequence.
Any item in $values that is an instance of xs:untypedAtomic
is first cast to xs:double. The resulting sequence is referred to as the
converted sequence.
All pairs of values in the converted sequence must be mutually comparable. Two values are mutually comparable if one or more of the following conditions applies:
Both values are instances of xs:string or xs:anyURI.
Both values are instances of xs:numeric.
Both values are instances of xs:hexBinary or xs:base64Binary.
Both values are instances of xs:date.
Both values are instances of xs:dateTime.
Both values are instances of xs:time.
Both values are instances of xs:dayTimeDuration.
Both values are instances of xs:yearMonthDuration.
Both values are instances of xs:boolean.
If the converted sequence contains a single value then it must be comparable to itself under the above rules. (So the
input cannot be, for example, a singleton xs:QName.)
If the converted sequence is empty, the function returns the empty sequence.
If the converted sequence contains the value NaN, the value
NaN is returned
xs:float or xs:double as appropriate)
Two items $v1 and $v2 from the converted sequence are compared as follows:
If both values are instances of xs:string or xs:anyURI, they
are compared using fn:compare($v1, $v2, $collation), where $collation
is determined by the rules in
In other cases, $collation is ignored.
If both values are instances of xs:numeric, they are compared
using fn:compare($v1, $v2).
In all other cases, the values are compared using the lt and eq
operators appropriate to their type.
The result of the function is a value from the converted sequence that is less than
or equal to every other value under the above rules. If there is more than one such value, then it is
A type error is raised
If there are two or items that are
“equal lowest”, the specific item whose value is returned is xs:dateTime
values compare equal despite being in different timezones.
If the converted sequence contains exactly one value then that value is returned.
The default type when the xs:untypedAtomic values is xs:double. This differs from the
default type for operators such as lt, and for sorting in XQuery and XSLT,
which is xs:string.
In version 4.0, if $values is a sequence of xs:decimal values
(including the case where it is a sequence of xs:integer values), then
the result will be one of these xs:decimal or xs:integer values.
In earlier versions it would
be the result of converting this xs:decimal to xs:double.
xs:integer or the xs:float,
since they are equal.min((3, 4, "Zero")) raises a type error
The way that xs:integer or xs:decimal values, the result is an xs:integer or
xs:decimal, rather than the result of converting this to an xs:double
Returns a value obtained by adding together the values in $values.
Any value of type xs:untypedAtomic in $values is cast to
xs:double. The items in the resulting sequence may be reordered in an
arbitrary order. The resulting sequence is referred to below as the converted
sequence.
If the converted sequence is empty, then the function returns
the value of the argument $zero, which defaults to
the xs:integer value 0.
In other cases the items in the converted sequence are added pairwise according
the rules of the + operator.
Specifically, the result of the function is the value of the expression:
where $c is the converted sequence.
This has the effect that a type error will occur unless one of the following conditions is satisfied:
Every item in $values is an instance of xs:yearMonthDuration.
Every item in $values is an instance of xs:dayTimeDuration.
Every item in $values is an instance of xs:numeric.
A type error is raised
The second argument allows an appropriate value to be defined to represent the sum of an empty sequence. For example, when summing a sequence of durations it would be appropriate to return a zero-length duration of the appropriate type. This argument is necessary because a system that does dynamic typing cannot distinguish “an empty sequence of integers", for example, from “an empty sequence of durations”.
The explicit or implicit value of
the $zero argument is used only when the input sequence is empty, not
when a non-empty sequence sums to zero. For example, sum((-1, +1), xs:double('NaN'))
returns the xs:integer value 0, not NaN.
The sum of a sequence of integers will be an integer, while the
sum of a numeric sequence that includes at least one xs:double will be an
xs:double.
If the converted sequence contains exactly one value then that value is returned.
If the converted sequence contains the value NaN, NaN is
returned.
In edge cases the fact that the input sequence may be reordered makes the result
slightly unpredictable. For example, if the input contains two xs:decimal
values and an xs:float, then the decimal values might be added using
decimal arithmetic, or they might both be converted to xs:float
(potentially losing precision) before any arithmetic is performed.
$zero value should be
the same type as the items in $value, or even that it should belong to
a type that supports addition.fn:sum(($d1, 9E1)) raises a type error
In 3.1, given a mixed input sequence such as (1, 3, 4.2e0), the specification was unclear whether it was permitted to add the first two integer items using integer arithmetic, rather than converting all items to doubles before performing any arithmetic. The 4.0 specification is clear that this is permitted; but since the items can be reordered before being added, this is not required.
Returns the sequence of element nodes that have an ID value matching the
value of one or more of the IDREF values supplied in $values.
The function returns a sequence, in document order with duplicates eliminated,
containing every element node E that satisfies all the following
conditions:
E is in the target document. The target document is the document
containing $node, or the document containing the context value
(.) if the second argument is omitted. The behavior of the
function if $node is omitted is exactly the same as if the context
value had been passed as $node.
E has an ID value equal to one of the candidate
IDREF values, where:
An element has an ID value equal to V if either
or both of the following conditions are true:
The is-id property (See true, and the typed value
of the element node is equal to V under the rules of the
eq operator using the Unicode codepoint collation
(http://www.w3.org/2005/xpath-functions/collation/codepoint).
The element has an attribute node whose is-id property
(See true and whose typed
value is equal to V under the rules of the
eq operator using the Unicode code point collation
(http://www.w3.org/2005/xpath-functions/collation/codepoint).
Each xs:string in $values is parsed as if it were of
type IDREFS, that is, each xs:string in
$values is treated as a whitespace-separated sequence of
tokens, each acting as an IDREF. These tokens are then included
in the list of candidate IDREFs. If any of the tokens is not a
lexically valid IDREF (that is, if it is not lexically an
xs:NCName), it is ignored. Formally, the candidate
IDREF values are the strings in the sequence given by the
expression:
If several elements have the same ID value, then E is
the one that is first in document order.
A dynamic error is raised $node, or the context value if the second argument is absent, is a node
in a tree whose root is not a document node.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not a single node, type error
The effect of this function is anomalous in respect of element nodes with the
is-id property. For legacy reasons, this function returns the element
that has the is-id property, whereas it would be more appropriate to return
its parent, that being the element that is uniquely identified by the ID. A new function
If the data model is constructed from an Infoset, an attribute will have the
is-id property if the corresponding attribute in the Infoset had an
attribute type of ID: typically this means the attribute was declared as an
ID in a DTD.
If the data model is constructed from a PSVI, an element or attribute will have the
is-id property if its typed value is a single atomic item of type
xs:ID or a type derived by restriction from xs:ID.
No error is raised in respect of a candidate IDREF value that does not
match the ID of any element in the document. If no candidate
IDREF value matches the ID value of any element, the
function returns the empty sequence.
It is not necessary that the supplied argument should have type xs:IDREF
or xs:IDREFS, or that it should be derived from a node with the
is-idrefs property.
An element may have more than one ID value. This can occur with synthetic
data models or with data models constructed from a PSVI where the element and one of its
attributes are both typed as xs:ID.
If the source document is well-formed but not valid, it is possible for two or more
elements to have the same ID value. In this situation, the function will
select the first such element.
It is also possible in a well-formed but invalid document to have an element or
attribute that has the is-id property but whose value does not conform to
the lexical rules for the xs:ID type. Such a node will never be selected by
this function.
xml:id attribute has the is-id property,
so the employee element is selected.empnr element is given the type
xs:ID as a result of schema validation, the element will have the
is-id property and is therefore selected. Note the difference from
the behavior of Returns the sequence of element nodes that have an ID value matching the
value of one or more of the IDREF values supplied in $values.
The effect of this function is identical to is-id property. However, it
behaves differently in respect of element nodes with the is-id property.
Whereas the is-id property, this function returns the element identified by the ID,
which is the parent of the element having the is-id property.
The function returns a sequence, in document order with duplicates eliminated,
containing every element node E that satisfies all the following
conditions:
E is in the target document. The target document is the document
containing $node, or the document containing the context value
(.) if the second argument is omitted. The behavior of the
function if $node is omitted is exactly the same as if the context
value had been passed as $node.
E has an ID value equal to one of the candidate
IDREF values, where:
An element has an ID value equal to V if either
or both of the following conditions are true:
The element has an child element node whose is-id
property (See true and
whose typed value is equal to V under the rules of the
eq operator using the Unicode code point collation
(http://www.w3.org/2005/xpath-functions/collation/codepoint).
The element has an attribute node whose is-id property
(See true and whose typed
value is equal to V under the rules of the
eq operator using the Unicode code point collation
(http://www.w3.org/2005/xpath-functions/collation/codepoint).
Each xs:string in $values is parsed as if it were of
type IDREFS, that is, each xs:string in
$values is treated as a whitespace-separated sequence of
tokens, each acting as an IDREF. These tokens are then included
in the list of candidate IDREFs. If any of the tokens is not a
lexically valid IDREF (that is, if it is not lexically an
xs:NCName), it is ignored. Formally, the candidate
IDREF values are the strings in the sequence given by the
expression:
If several elements have the same ID value, then E is
the one that is first in document order.
A dynamic error is raised $node, or the context value if the second argument is omitted, is a node
in a tree whose root is not a document node.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not a single node, type error
This function is equivalent to the
If the data model is constructed from an Infoset, an attribute will have the
is-id property if the corresponding attribute in the Infoset had an
attribute type of ID: typically this means the attribute was declared as an
ID in a DTD.
If the data model is constructed from a PSVI, an element or attribute will have the
is-id property if its typed value is a single atomic item of type
xs:ID or a type derived by restriction from xs:ID.
No error is raised in respect of a candidate IDREF value that does not
match the ID of any element in the document. If no candidate
IDREF value matches the ID value of any element, the
function returns the empty sequence.
It is not necessary that the supplied argument should have type xs:IDREF
or xs:IDREFS, or that it should be derived from a node with the
is-idrefs property.
An element may have more than one ID value. This can occur with synthetic
data models or with data models constructed from a PSVI where the element and one of its
attributes are both typed as xs:ID.
If the source document is well-formed but not valid, it is possible for two or more
elements to have the same ID value. In this situation, the function will
select the first such element.
It is also possible in a well-formed but invalid document to have an element or
attribute that has the is-id property but whose value does not conform to
the lexical rules for the xs:ID type. Such a node will never be selected by
this function.
xml:id attribute has the is-id property,
so the employee element is selected.empnr element is given the type
xs:ID as a result of schema validation, the element will have the
is-id property and is therefore its parent is selected. Note the
difference from the behavior of Returns the sequence of element or attribute nodes with an IDREF value
matching the value of one or more of the ID values supplied in
$values.
The function returns a sequence, in document order with duplicates eliminated,
containing every element or attribute node $N that satisfies all the
following conditions:
$N is in the target document. The target document is the document
containing $node, or the document containing the context value
(.) if the second argument is omitted. The behavior of the
function if $node is omitted is exactly the same as if the context
value had been passed as $node.
$N has an IDREF value equal to one of the candidate
ID values, where:
A node $N has an IDREF value equal to
V if both of the following conditions are true:
The is-idrefs property (see $N is true.
The sequence
contains a string that is
equal to V under the rules of the eq
operator using the Unicode code point collation
(http://www.w3.org/2005/xpath-functions/collation/codepoint).
Each xs:string in $values is parsed as if it were of
lexically of type xs:ID. These xs:strings are then
included in the list of candidate xs:IDs. If any of the strings
in $values is not a lexically valid xs:ID (that is,
if it is not lexically an xs:NCName), it is ignored. More
formally, the candidate ID values are the strings in the
sequence:
A dynamic error is raised $node, or the context value if the second argument is omitted, is a node
in a tree whose root is not a document node.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not a single node, type error
An element or attribute typically acquires the is-idrefs property by being
validated against the schema type xs:IDREF or xs:IDREFS, or
(for attributes only) by being described as of type IDREF or
IDREFS in a DTD.
Because the function is sensitive to the way in which the data model is constructed, calls on this function are not always interoperable.
No error is raised in respect of a candidate ID value that does not match
the IDREF value of any element or attribute in the document. If no
candidate ID value matches the IDREF value of any element or
attribute, the function returns the empty sequence.
It is possible for two or more nodes to have an IDREF value that matches a
given candidate ID value. In this situation, the function will return all
such nodes. However, each matching node will be returned at most once, regardless how
many candidate ID values it matches.
It is possible in a well-formed but invalid document to have a node whose
is-idrefs property is true but that does not conform to the lexical
rules for the xs:IDREF type. The effect of the above rules is that
ill-formed candidate ID values and ill-formed IDREF values are
ignored.
If the data model is constructed from a PSVI, the typed value of a node that has the
is-idrefs property will contain at least one atomic item of type
xs:IDREF (or a type derived by restriction from xs:IDREF).
It may also contain atomic items of other types. These atomic items are treated as
candidate ID values xs:NCName, and there must be at least one instance of xs:IDREF
in the typed value of the node. If these conditions are not satisfied, such values are ignored.
manager has the is-idref property, the call on manager element. If, instead, the manager had a ref
attribute with the is-idref property, the call on employee/deputy has the is-idref property, the call on deputy element.Retrieves a document using a URI supplied as an xs:string, and returns the
corresponding document node.
If $source is the empty sequence, the result is an empty sequence.
If $source is a relative URI reference, it is resolved relative to the value
of the xs:string.
If the
The URI may include a fragment identifier.
The $options argument, if present and non-empty, defines the detailed behavior of the
function. The
DOCTYPE declaration to identify
the DTD to be used for validation. The DTD may be internal or external.
DOCTYPE declaration is present, then it is read, for example
to perform entity expansion.
true, but this may be overridden
by implementation-defined configuration options.xsl:strip-space
and xsl:preserve-space declarations provide detailed control
based on the parent element name.)xml:space="preserve",
or (b) XSD validation identifies that the parent element has a simple type or a complex
type with simple content.
xi:include elements in the input
are to be processed using an XInclude processor.xi:include elements are expanded. If there are
xi:include elements and no XInclude processor is available then
a dynamic error is raised.
xi:include elements are handled as
ordinary elements without expansion.
validate expression to the result,
with corresponding options.xsi:schemaLocation or xsi:noNamespaceSchemaLocation
attributes within the source document are to be used. The option is ignored
if XSD validation does not take place.xsi:schemaLocation or xsi:noNamespaceSchemaLocation
attributes in addition to the schema components present in the static context;
these components must be compatible as described in xsi:schemaLocation and xsi:noNamespaceSchemaLocation
attributes in the document are ignored.By default, this function is true:
This equivalence applies only because the two calls on
the
The requirement to deliver a deterministic result has performance implications,
and for this reason implementations may provide a user option to evaluate
the function without a guarantee of determinism. The manner in which any such option is
provided is
If the $source URI is obtained from a source document, it is generally appropriate to
resolve it relative to the base URI property of the relevant node in the source
document. This can be achieved by calling the
If two calls to this function supply different absolute URI References as arguments, the same document node may be returned if the implementation can determine that the two arguments refer to the same resource.
By defining the semantics of this function in terms of a string-to-document-node
mapping in the dynamic context, the specification is acknowledging that the results of
this function are outside the purview of the language specification itself, and depend
entirely on the run-time environment in which the expression is evaluated. This run-time
environment includes not only an unpredictable collection of resources (“the web”), but
configurable machinery for locating resources and turning their contents into document
nodes within the XPath data model. Both the set of resources that are reachable, and the
mechanisms by which those resources are parsed and validated, are
One possible processing model for this function is as follows. The resource identified
by the URI Reference is retrieved. If the resource cannot be retrieved, a dynamic error
is raised "text", the content is parsed in the same way as if the media type were text/xml;
otherwise, it is parsed in the same way as if the media type were application/xml. If
the contents cannot be parsed successfully, a dynamic error is raised
Various aspects of this processing are
The set of URI schemes that the implementation recognizes is implementation-defined. Implementations may allow the mapping of URIs to resources to be configured by the user, using mechanisms such as catalogs or user-written URI handlers.
The handling of non-XML media types is implementation-defined. Implementations may allow instances of the data model to be constructed from non-XML resources, under user control.
It is
Implementations may provide user-defined error handling options that allow processing to continue following an error in retrieving a resource, or in parsing and validating its content. When errors have been handled in this way, the function may return either an empty sequence, or a fallback document provided by the error handler.
Implementations may provide user options that relax the requirement for the function to return deterministic results.
The effect of a fragment identifier in the supplied URI
is
A dynamic error $source is not a valid URI
A dynamic error is raised
A dynamic error is raised
A dynamic error is raised
A dynamic error is raised
The rule that multiple calls on
An $options parameter is added. Note that the rules for the $options parameter
control aspects of processing that were implementation-defined in earlier versions of this
specification. An implementation may provide configuration options designed to retain backwards-compatible
behavior when no explicit options are supplied.
The function returns true if and only if the function call fn:doc($source, $options)
would return a document node.
If $source is an empty sequence, this function returns false.
If a call on fn:doc($source, $options) would return a document node, this function
returns true.
In all other cases this function returns false.
The recognized values for $options are the same as for the stable
option is set to true, then a result of true from this function guarantees
that a call on false from this function guarantees that the corresponding call on stable option is set to false, then the result of this
function provides no guarantees regarding the outcome of a call on
An $options parameter is added. Note that the rules for the $options parameter
control aspects of processing that were implementation-defined in earlier versions of this
specification. An implementation may provide configuration options designed to retain backwards-compatible
behavior when no explicit options are supplied.
Returns a sequence of items identified by a collection URI; or a default collection if no URI is supplied.
This function takes an xs:string as argument and returns a sequence of
$source as an xs:anyURI and
resolving it according to the mapping specified in
If
If $source is not specified, the function returns the sequence of
If $source is a relative URI reference, it is resolved relative to the value
of the xs:string.
If $source is the empty sequence, the function behaves as if it had been
called without an argument. See above.
By default, this function is
There is no requirement that
A dynamic error is raised
A dynamic error is raised
A dynamic error is raised
A dynamic error $source is not
a valid xs:anyURI.
In earlier versions of this specification, the primary use for the xs:base64Binary.
The abstract concept of a collection might be realized in different ways by different implementations, and the ways in which URIs map to collections can be equally variable. Specifying resources using URIs is useful because URIs are dynamic, can be parameterized, and do not rely on an external environment.
Returns a sequence of xs:anyURI values representing the URIs in a URI
collection.
The zero-argument form of the function returns the URIs in the
If $source is a relative URI reference, it is resolved relative to the value
of the xs:string.
If $source is the empty sequence, the function behaves as if it had been
called without an argument. See above.
The single-argument form of the function returns the sequence of URIs corresponding to
the supplied URI in the
By default, this function is
There is no requirement that the URIs returned by this function should all be distinct, and no assumptions can be made about the order of URIs in the sequence, unless the implementation defines otherwise.
A dynamic error is raised
A dynamic error is raised
A dynamic error is raised
A dynamic error $source is not
a valid xs:anyURI.
In some implementations, there might be a close relationship between
In the case where
It allows different URIs for different kinds of resource to be dereferenced in
different ways: for
example, the returned URIs might be referenced using the
In XSLT 3.0 it allows the documents in a collection to be processed in streaming mode using the
xsl:stream instruction.
It allows recovery from failures to read, parse, or validate individual documents,
by calling the
It allows selection of which documents to read based on their URI, for example
they can be filtered to select those whose URIs end in .xml, or those
that use the https scheme.
An application might choose to limit the number of URIs processed in a single run, for example it might process only the first 50 URIs in the collection; or it might present the URIs to the user and allow the user to select which of them need to be further processed.
It allows the URIs to be modified before they are dereferenced, for example by adding or removing query parameters, or by redirecting the request to a local cache or to a mirror site.
For some of these use cases, this assumes that the cost of calling
The
The $source argument
If $source is a relative URI reference, it is resolved relative to the value
of the xs:string.
The $options argument, for backwards compatibility reasons, may be supplied
either as a map, or as a string. Supplying a value $S that is not a map
is equivalent to supplying the map { "encoding": $S }.
After that substitution, the
The entries that may appear in the $options map are as follows:
The mapping of URIs to the string representation of a resource is the mapping defined in
the
If the $source argument is an empty sequence, the function
returns an empty sequence.
The encoding option, if present
encoding attribute in
an XML declaration. The only values which every
implementation is utf-8 and utf-16.
The encoding of the external resource is determined by applying the following rules, in order:
External encoding information is used if available.
If the media type of the resource is text/xml or
application/xml (see text/*+xml or application/*+xml (see
The encoding option is used if present.
If the initial octets represent a byte order mark in a known encoding, then the corresponding encoding is used: specifically:
Initial octets FE FF imply UTF-16LE.
Initial octets FF FE imply UTF-16BE.
Initial octets EF BB BF imply UTF-8.
The processor
UTF-8 is assumed.
The result of the function is a string containing the string representation of the
resource retrieved using the URI, decoded according to the specified encoding.
If the first codepoint, after decoding, is
A dynamic error is raised $source argument
contains a fragment identifier,
A dynamic error is raised encoding option is not a valid encoding name, if the
processor does not support the specified encoding, if
the string representation of the retrieved resource contains octets that cannot be
decoded into Unicode
A dynamic error is raised encoding option
is absent and the processor cannot infer the
encoding using external information and the actual encoding is not UTF-8.
If it is appropriate to use a base URI other than the
There is no essential relationship between the sets of URIs accepted by the two
functions
There are no constraints on the MIME type of the resource.
The fact that the resolution of URIs is defined by a mapping in the dynamic context
means that in effect, various aspects of the behavior of this function are
The set of URI schemes that the implementation recognizes is implementation-defined. Implementations may allow the mapping of URIs to resources to be configured by the user, using mechanisms such as catalogs or user-written URI handlers.
The handling of media types is implementation-defined.
Implementations may provide user options that relax the requirement for the function to return deterministic results.
Implementations may provide user-defined error handling options that allow processing to continue following an error in retrieving a resource, or in reading its content. When errors have been handled in this way, the function may return a fallback document provided by the error handler.
The rules for determining the encoding are chosen for consistency with
If the text file contains characters such as < and &,
these will typically be output as < and & if
the string is serialized as XML or HTML. If these characters actually represent markup
(for example, if the text file contains HTML), then an XSLT stylesheet can attempt to
write them as markup to the output file using the disable-output-escaping
attribute of the xsl:value-of instruction. Note, however, that XSLT
implementations are not required to support this feature.
This XSLT example attempts to read a file containing “boilerplate” HTML and copy it directly to the serialized output file:
The $options parameter has been added.
It is no longer automatically an error if the resource (after decoding)
contains a codepoint that is not valid in XML. Instead, the codepoint
must be a
The specification now describes how an initial BOM should be handled.
The
The unparsed-text-lines function reads an external resource (for example, a
file) and returns its string representation as a sequence of strings, separated at
newline boundaries.
The $options argument, for backwards compatibility reasons, may be supplied
either as a map, or as a string. Supplying a value $S that is not a map
is equivalent to supplying the map { "encoding": $S }.
After that substitution, the
The entries that may appear in the $options map are as follows:
The result of the function is the same as the result of the expression:
The result is thus a sequence of strings containing the text of the resource retrieved
using the URI, each string representing one line of text. Lines may be delimited by
any of the character sequences
Error conditions are the same as for the
See the notes for
The $options parameter has been added.
Allows an application to determine
whether a call on
The
If the first argument is an empty sequence, the function returns false.
In other cases, the function returns true if a call on
false if a call on
The functions unparsed-text with the same arguments.
This function was introduced before XQuery and XSLT allowed errors to be caught;
with current versions of these host languages, catching an error from
The specification requires that the if (unparsed-text-available(A)) then unparsed-text(A) else ... to
generate a single call internally.
Since the function
The $options parameter has been added.
The fn:unparsed-binary function reads an external resource (for example, a
file) and returns its contents in binary.
The $source argument
If $source is a relative URI reference, it is resolved relative to the value
of the xs:string.
The mapping of URIs to the binary representation of a resource is the mapping defined in
the
If the $source argument is an empty sequence, the function
returns an empty sequence.
The result of the function is an atomic item of type xs:base64Binary
containing the binary representation of the
resource retrieved using the URI.
A dynamic error is raised $source argument
contains a fragment identifier,
If it is appropriate to use a base URI other than the
fn:resolve-uri
function before passing it to the fn:unparsed-text function.
There is no essential relationship between the sets of URIs accepted by the
function fn:unparsed-binary and other functions such as
fn:doc and fn:unparsed-text (a URI accepted by one
may or may not be accepted by the others), and if a URI is accepted by more than
one of these functions then there is no
essential relationship between the results (different resource representations are
permitted by the architecture of the web).
There are no constraints on the MIME type of the resource.
The fact that the resolution of URIs is defined by a mapping in the dynamic context
means that in effect, various aspects of the behavior of this function are
The set of URI schemes that the implementation recognizes is implementation-defined. Implementations may allow the mapping of URIs to resources to be configured by the user, using mechanisms such as catalogs or user-written URI handlers.
The handling of media types is implementation-defined.
Implementations may provide user options that relax the requirement for the function to return deterministic results.
Implementations may provide user-defined error handling options that allow processing to continue following an error in retrieving a resource, or in reading its content. When errors have been handled in this way, the function may return a fallback document provided by the error handler.
There is no function (analogous to fn:doc-available or fn:unparsed-text-available)
to determine whether a suitable resource is available. In XQuery and XSLT, try/catch
constructs are available to catch the error.
The choice of xs:base64Binary rather than xs:hexBinary for the
result is arbitrary. The two types have the same value space and are interchangeable for nearly
all purposes, the notable exception being conversion to xs:string.
A comprehensive set of functions for manipulating binary data is available in the
EXPath binary module: see file:read-binary with similar functionality to
fn:unparsed-binary, the notable differences being (a) that it takes
a file name rather than a URI, and (b) that it is defined to be nondeterministic.
The following XQuery, adapted from an example in the EXPath binary module
The example assumes that the functions in the EXPath binary module are available.
New in 4.0
Returns the value of a system environment variable, if it exists.
The set of available
If the $name argument matches the name of one of these pairs, the function
returns the corresponding value.
If there is no environment variable with a matching name, the function returns the empty sequence.
The collation used for matching names is
The function is
On many platforms, the term “environment variable” has a natural meaning in terms of facilities provided by the operating system. This interpretation of the concept does not exclude other interpretations, such as a mapping to a set of configuration parameters in a database system.
Environment variable names are usually case sensitive. Names are usually of the form
(letter|_) (letter|_|digit)*, but this varies by platform.
On some platforms, there may sometimes be multiple environment variables with the same
name; in this case, it is implementation-dependent as to which is returned; see for
example
The requirement to ensure that the function is deterministic means in practice that the implementation must make a snapshot of the environment variables at some time during execution, and return values obtained from this snapshot, rather than using live values that are subject to change at any time.
Operating system environment variables may be associated with a particular process,
while queries and stylesheets may execute across multiple processes (or multiple
machines). In such circumstances implementations
Security advice: Queries from untrusted sources should not be permitted unrestricted
access to environment variables. For example, the name of the account under which the
query is running may be useful information to a would-be intruder. An implementation may
therefore choose to restrict access to the environment, or may provide a facility to
make
Returns a list of environment variable names that are suitable for passing to
The function returns a sequence of strings, being the names of the environment variables
in the dynamic context in some
The function is
The function returns a list of strings, containing no duplicates.
It is intended that the strings in this list should be suitable for passing to
See also the note on security under the definition of the
This function returns a string that uniquely identifies a given GNode.
If the argument is omitted, it defaults to the context value (.).
If the argument is the empty sequence, the result is the zero-length string.
In other cases, the function returns a string that uniquely identifies a given node.
fn:codepoint-equal(fn:generate-id($N), fn:generate-id($M)) returns true
if and only if ($M is $N) returns true.
The returned identifier
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type
gnode()?, type error
An implementation is free to generate an identifier in any convenient way provided that it always generates the same identifier for the same GNode and that different identifiers are always generated from different GNodes. An implementation is under no obligation to generate the same identifiers each time a document is transformed or queried.
There is no guarantee that a generated unique identifier will be distinct from any unique IDs specified in the source document.
There is no inverse to this function; it is not directly possible to find the GNode with
a given generated ID. Of course, it is possible to search a given sequence of GNodes
using an expression such as $nodes[generate-id()=$id].
It is advisable, but not required, for implementations to generate IDs that are distinct even when compared using a case-blind collation.
The primary use case for this function is to generate hyperlinks. For example, when
generating HTML, an anchor for a given section $sect can be generated by
writing (in either XSLT or XQuery):
]]>
and a link to that section can then be produced with code such as:
here]]>
Note that anchors generated in this way will not necessarily be the same each time a document is republished.
Since the keys in a map must be atomic items, it is possible to use generated IDs
as surrogates for nodes when constructing a map. For example, in some implementations,
testing whether a node $N is a member of a large node-set $S
using the expression exists($N intersect $S) may be expensive; there
may then be performance benefits in creating a map:
let $SMap := map:merge($S ! { generate-id(.) : . })
and then testing for membership of the node-set using:
map:contains($SMap, generate-id($N))
This function takes as input an XML document, and returns the document node at the root of an XDM tree representing the parsed document.
If $value is the empty sequence, the function returns the empty sequence.
In other cases, $value is expected to contain an XML document supplied
either as a string or a binary value. If it is supplied as a binary value, an optional
byte order mark or XML declaration may contain the input encoding, and the input will be
processed like a resource retrieved by the
The $options argument, if present and non-empty, defines the detailed behavior of the
function. The
DOCTYPE declaration to identify
the DTD to be used for validation. The DTD may be internal or external.
DOCTYPE declaration is present, then it is read, for example
to perform entity expansion.
parse-xml failing
with a dynamic error if present.
xsl:strip-space
and xsl:preserve-space declarations are ignored.)xml:space="preserve",
or (b) XSD validation identifies that the parent element has a simple type or a complex
type with simple content.
xi:include elements in the input
are to be processed using an XInclude processor.xi:include elements are expanded. If there are
xi:include elements and no XInclude processor is available then
a dynamic error is raised.
xi:include elements are handled as
ordinary elements without expansion.
validate expression to the result,
with corresponding options.xsi:schemaLocation or xsi:noNamespaceSchemaLocation
attributes within the source document are to be used. The option is ignored
if XSD validation does not take place.xsi:schemaLocation or xsi:noNamespaceSchemaLocation
attributes in addition to the schema components present in the static context;
these components must be compatible as described in xsi:schemaLocation and xsi:noNamespaceSchemaLocation
attributes in the document are ignored.Except to the extent defined by these options, the precise process used
to construct the XDM instance is
The document URI of the returned node is
The function is
Options set in $options may be supplemented or modified based on
configuration options defined externally using
A dynamic error is raised $value is not a well-formed and namespace-well-formed XML document.
A dynamic error is raised $value is not valid against the relevant DTD.
A dynamic error is raised xsd-validation option is not one of the
permitted values (for example, if the string that follows "type"
is not a valid EQName, or if it does not identify a type that is present in the
static context).
A dynamic error is raised xsd-validation option is set to anything
other than skip when the processor is not schema-aware. (XSLT 4.0
and XQuery 4.0 define schema-awareness as an optional feature; other host languages
may set their own rules.)
A dynamic error is raised
A dynamic error is raised $value is not valid against the relevant XSD schema.
Since the XML document is presented to the parser as a string, rather than as a sequence of octets, the encoding specified within the XML declaration has no meaning. If the XML parser accepts input only in the form of a sequence of octets, then the processor must ensure that the string is encoded as octets in a way that is consistent with rules used by the XML parser to detect the encoding.
A common use case for this function is to handle input documents that contain nested
XML documents embedded within CDATA sections. Since the content of the CDATA section is
exposed as text, the receiving query or stylesheet may pass this text to the
Similarly, nested XML within comments is sometimes encountered, and lexical XML is sometimes returned by extension functions, for example, functions that access web services or read from databases.
A use case arises in XSLT where there is a need to preprocess an input document before
parsing. For example, an application might wish to edit the document to remove its
DOCTYPE declaration. This can be done by reading the raw text using the
The expression fn:parse-xml("<alpha>abcd</alpha>") returns a newly
created document node, having an alpha element as its only child; the
alpha element in turn is the parent of a text node whose string value
is "abcd".
The expression fn:parse-xml("<alpha><beta> </beta></alpha>", { "strip-space": true() }) returns a newly
created document node, having an alpha element as its only child; the
alpha element in turn is the parent of a beta
element whose content is empty, as a result of whitespace stripping.
The $options parameter has been added.
Additional error conditions have been defined.
Additional options to control DTD and XInclude processing have been added.
Support for binary input has been added.
This function takes as input an XML external entity represented as a string, and returns the document node at the root of an XDM tree representing the parsed document fragment.
If $value is the empty sequence, the function returns the empty sequence.
If the input is supplied as a binary value, the function detects the encoding using the
same rules as the text/xml and application/xml may be skipped.
Otherwise, if the input is a string, any byte order mark as well as the encoding specified
in an optional XML declaration
The input must be a namespace-well-formed external general parsed entity. More
specifically, it must conform to the production rule
The input is parsed to form a sequence of nodes which become children of the new document node, in the same way as the content of any element is converted into a sequence of children for the resulting element node.
The $options argument, if present and non-empty, defines the detailed behavior of the
function. The
xml:space="preserve".
DTD validation is DOCTYPE declaration.
Schema validation is
XInclude processing is
Except as explicitly defined, the precise process used to construct the XDM instance is
The document URI of the returned node is
The function is
A dynamic error is raised $value is not a well-formed external general parsed entity, if it contains
entity references other than references to predefined entities, or if a document that
incorporates this well-formed parsed entity would not be namespace-well-formed.
See also the notes for the
The main differences between
Note that all whitespace outside the strip-space
option is set.
One use case for this function is to handle XML fragments stored in databases, which
frequently allow zero-or-more top level element nodes. Another use case is to parse the
contents of a CDATA section embedded within another XML document.
The expression
parse-xml-fragment("<alpha>abcd</alpha><beta>abcd</beta>")
returns a newly created document node, having two elements named alpha
and beta as its children; each of these elements in turn is the parent
of a text node.
The expression parse-xml-fragment("He was <i>so</i> kind")
returns a newly created document node having three children: a text node whose string
value is "He was ", an element node named i having a child
text node with string value "so", and a text node whose string value is
" kind".
The expression parse-xml-fragment("") returns a document node having
no children.
The expression parse-xml-fragment(" ") returns a document node whose
children comprise a single text node whose string value is a single space.
The expression parse-xml-fragment(" ", { "strip-space": true() })
returns a document node having no children.
The expression parse-xml-fragment('<?xml version="1.0" encoding="utf8"
standalone="yes"?><a/>') results in a dynamic error standalone keyword is not permitted in the text
declaration that appears at the start of an external general parsed entity. (Thus, it
is not the case that any input accepted by the
The $options parameter has been added.
Support for binary input has been added.
Given an XSD schema, delivers a function item that can be invoked to validate a document or element node against this schema.
The
The details of how the schema is assembled, and the way it is used, are defined by the supplied $options.
If the $options argument is absent or empty the effect is to use the schema components from the
static context of the call on
The static context of the function call
Explicitly supplied schema documents
Schema components referenced in xsi:schemaLocation and xsi:noNamespaceSchemaLocation
attributes within the instance document being validated.
More details of schema assembly appear below. Taken together, the assembled components must constitute a valid schema.
The function is designed to separate the process of assembling a schema from the process of performing instance
validation. However, if the schema is to include components identified in
xsi:schemaLocation and xsi:noNamespaceSchemaLocation attributes, then the process of
assembling the schema cannot be completed until the instance document is available.
The options recognized are as follows. The
xsi:schemaLocation or xsi:noNamespaceSchemaLocation
attributes in the instance document being validated. If false, these attributes are ignored.type option is absent.type option is present.typed-node which contains a copy of the
target node augmented with type annotations and expanded default values. If false, the typed
node is not included in the result. If a node containing type annotations is to be returned,
then the schema used for validation must be compatible with all other schemas used within
the same query or stylesheet, as described in The first task of the function is to assemble a schema (that is, a collection of schema components). Schema components can come from a number of sources, and a schema can be assembled from more than one source, provided that the total collection of components comprises a valid schema: the main thing that will prevent this is if two sources contain conflicting definitions of the same named component.
The default is to use the in-scope schema components from the static context of the function call.
Instead, or in addition, schema components may be loaded explictly for this validator. Supplementary schema components may be requested in a number of ways:
The schema-location option can specify one or more URIs that
are interpreted as locations for source XSD schema documents, which are then
assembled into a schema as described in the XSD specifications.
The schema option can be used to identify one or more
xs:schema element nodes holding source schema documents. This allows
a schema to be constructed dynamically by the application, or to be held as
a global variable in the source code of a query or stylesheet module.
The target-namespace option can be used to supply
the target namespaces of additional schema components that are known to the
system or that are made available using some external mechanism. For example,
the system might have built-in schemas for common namespaces such as
the xml, fn, or xlink namespaces,
or it might have a mechanism allowing schemas for a particular namespace
to be registered using an external API or configuration mechanism.
The use-xsi-schema-location also allows the application
to request that schema documents referenced from xsi:schemaLocation
or xsi:noNamespaceSchemaLocation attributes should be included
in the schema. By default these attributes are ignored.
It is acceptable to assemble a schema from more than one of these
sources. In addition, any of these sources can bring in additional components
by the use of the XSD directives xsl:include and xsl:import.
The important constraint is that the result should be a valid schema. This will only
be the case if the sources used to assemble the schema are
The XSD specification allows a schema to be used for validation even when
it contains unresolved
references to absent schema components. It is
Having assembled a schema, the next task is to validate a supplied node (and the subtree rooted at that node).
This description is a deliberate simplification. If the use-xsi-schema-location
option is true, then assembly of the schema is not completed until the instance document
is available, and in practice overlaps with the validation process.
The
V has an arity of one. Call the value of the supplied argument
$target. The required type of $target
is (document-node(*) | element(*) | attribute(*))?:
that is, it accepts either a well-formed
document node, or an element node, or an attribute node, or an empty sequence.
If the argument is an empty sequence then the result of V is also an empty sequence.
In other cases, the result of a call on V is a record containing the following fields:
is-valid as xs:boolean. This field is always present, and indicates
whether the supplied $target node was found to be valid against the schema.
The value is true if either (a) the validation outcome was valid, or
(b) lax validation was requested and the validation outcome was notKnown.
In other cases it is false.
typed-node as (document-node(*) | element(*) | attribute(*)).
This field is present
only when (a) the option return-typed-node was set (explicitly or implicitly)
to true, and (b) the value of the is-valid field is true.
It represents the root of a tree that is a deep copy of the input tree,
augmented with type annotations and default values.
error-details as map(*)*. This field is present only when (a) the option
return-error-details was set
to true, and (b) the supplied document was found to be invalid. The value is a sequence
of maps, each containing details of one invalidity that was found. The precise details of the
invalidities are
message. A string containing the text of an error message, intended
for a human reader.
rule. A reference to the rule in the XSD specification that was violated.
This is a string comprising four parts separated by the character
"1.0" or "1.1" indicating whether the reference is to the XSD 1.0 or 1.1 specification.
"1" or "2" indicating whether the reference is to part 1 or part 2 of the specification.
The name of the validation rule (for example "Datatype Valid").
The clause number within that validation rule (for example "2.3").
For example, if an attribute is declared to be of type xs:integer, but the
actual value is not in the lexical space of xs:integer, the value of rule
might be "1.1|2|Datatype Valid|2.1".
node. The node that was found to be invalid. Note that when a containing element
C is invalid because a child element D is not allowed by its content
model, the invalid node is C, not D.
error-node. The node whose presence led to detection of the invalidity. In the
above example, this would be D.
error-uri. The URI of the XML entity in which the error was detected.
line-number. The line number where the error was detected, within its external entity.
column-number. The column number where the error was detected, within the error line number.
The validation is performed as described in $target as the operand node.
If the use-xsi-schema-location option is true and a failure
occurs processing an xsi:schemaLocation or xsi:noNamespaceSchemaLocation
attribute (for example, because a schema document cannot be retrieved, or because the referenced
schema document is invalid, or because it is incompatible with other schema components)
this is treated as an invalidity, not as a dynamic error:
V returns successfully with is-valid set to false.
The function V may fail with a dynamic error if it is not possible to determine whether or not the instance document is valid. This may happen, for example, if processor-defined limits are exceeded.
A dynamic error is raised
A dynamic error is raised
Both XQuery and XSLT provide capabilities for XSD-based schema validation in earlier versions of the specifications, and those are retained in 4.0. This function provides additional capability:
It is possible to control validation more precisely, through a wider range of options;
It is possible to validate different instance documents against different schemas;
Information about any invalidities is made available to the application, rather than simply causing a dynamic error;
The capability is provided by means of a function rather than custom syntax, making it easier to integrate into an application.
The capability is available through XPath alone, and therefore with host languages other than XQuery and XSLT.
Three possible ways of using the function include:
To simply test whether or not a document is valid against a schema, set the options
return-typed-node and return-error-details to false,
and simply test the value of the is-valid field returned when the validation function
is called.
To obtain a typed XDM tree from an input document that is expected to be valid, set the
option return-typed-node to true. On return from the validation function, test the
value of the is-valid field; call typed-node property of the result. The main benefit of using a typed
XDM tree is that it allows static type checking of path expressions: this benefit only applies
when the schema used for validation is the imported schema used in the static context. However, there
are cases where validation against a different schema is appropriate, for example when validating the
result of one query or transformation that is to be used as input to another.
To validate an input document and provide feedback to the document author about any validity
problems that were found, set return-error-details to true. If the result
of the validation function has is-valid = false(), process the returned error-details.
The information available for this part of the processing may not be 100% interoperable, though with care it
should be possible to write the query in such a way that it works with different processors.
The validation process is explained in more detail in the XQuery (
The function has no effect on the static context. Schemas loaded using this function, either directly or
via the effect of xsi:schemaLocation and xsi:noNamespaceSchemaLocation attributes, are not
added to the static context and have no effect on any other validation episodes. A processor may cache schema
components to reduce the cost of processing the same schema repeatedly, but this has no observable effect other than
on performance.
New in 4.0
This function serializes the supplied input sequence $input as described in
The value of the first argument $input acts as the input sequence to the serialization process,
which starts with sequence normalization.
The second argument $options, if present, provides serialization parameters. These may be supplied in either
of two forms:
As an output:serialization-parameters
element, having the format described in element(output:serialization-parameters).
As a map. In this case the type of the supplied argument must match the required type map(*)
The single-argument version of this function has the same effect as the two-argument
version called with $options set to an empty sequence. This in turn is the
same as the effect of passing an output:serialization-parameters element
with no child elements.
The final stage of serialization, that is, encoding, is skipped. If the serializer does not allow this phase to be skipped, then the sequence of octets returned by the serializer is decoded into a string by reversing the character encoding performed in the final stage.
If the second argument is omitted, or is supplied in the form of an output:serialization-parameters
element, then the values of any serialization parameters that are not explicitly specified is
If the second argument is supplied as a map, then the
Each entry in the map defines one serialization parameter.
The key of the entry is an xs:string value in the cases of parameter names defined in these specifications, or an
xs:QName (with non-absent namespace) in the case of implementation-defined serialization parameters.
The required type of each parameter, and its default value, are defined by the following table. The default value is used when the map contains no entry for the parameter in question, and also when an entry is present, with the empty sequence as its value. The table also indicates how the value of the map entry is to be interpreted in cases where further explanation is needed.
| Parameter | Required type | Interpretation | Default Value |
|---|---|---|---|
allow-duplicate-names
|
xs:boolean?
|
true() means "yes", false() means "no" |
no
|
byte-order-mark
|
xs:boolean?
|
true() means "yes", false() means "no" |
no
|
cdata-section-elements
|
xs:QName*
|
()
|
|
doctype-public
|
xs:string?
|
Zero-length string and () both represent "absent" |
absent |
doctype-system
|
xs:string?
|
Zero-length string and () both represent "absent" |
absent |
encoding
|
xs:string?
|
utf-8
|
|
escape-solidus
|
xs:boolean?
|
true() means "yes", false() means "no" |
yes
|
escape-uri-attributes
|
xs:boolean?
|
true() means "yes", false() means "no" |
yes
|
html-version
|
xs:decimal?
|
5
|
|
include-content-type
|
xs:boolean?
|
true() means "yes", false() means "no" |
yes
|
indent
|
xs:boolean?
|
true() means "yes", false() means "no" |
no
|
item-delimiter
|
xs:string?
|
absent | |
json-lines
|
xs:boolean?
|
true() means "yes", false() means "no" |
no
|
json-node-output-method
|
(xs:string | xs:QName)?
|
See Notes 1, 2 |
xml
|
media-type
|
xs:string?
|
(a media type suitable for the chosen method) |
|
method
|
(xs:string | xs:QName)?
|
See Notes 1, 2 |
xml
|
normalization-form
|
xs:string?
|
none
|
|
omit-xml-declaration
|
xs:boolean?
|
true() means "yes", false() means "no" |
yes
|
standalone
|
xs:boolean?
|
true() means "yes", false() means "no", () means "omit" |
omit
|
suppress-indentation
|
xs:QName*
|
()
|
|
undeclare-prefixes
|
xs:boolean?
|
true() means "yes", false() means "no" |
no
|
use-character-maps
|
map(xs:string, xs:string)?
|
See Note 3 |
{}
|
version
|
xs:string?
|
1.0
|
Notes to the table:
The notation (A | B) represents a union type whose member types are A
and B.
If an xs:QName is supplied method or json-node-output-method
options,xml and json
are defined as strings, not as xs:QName values.
use-character-maps optionxs:string instances),
and whose corresponding values are the strings to be substituted for these characters.
A type error $options argument
is present and does not match either of the types element(output:serialization-parameters)?
or map(*).
This is defined as a type error so that it can be enforced via the function signature by implementations that generalize the type system in a suitable way.
If the host language makes serialization an optional feature and the implementation does
not support serialization, then a dynamic error
When the second argument is supplied as a map,
and the supplied value is of the wrong type for the particular parameter, for example if the value of indent
is a string rather than a boolean, then as defined by the use-character-maps includes a key that is a string whose length is not one (1)).
If any serialization error occurs, including the detection of an invalid value for a
serialization parameter as described above, this results in the
One use case for this function arises when there is a need to construct an XML document
containing nested XML documents within a CDATA section (or on occasions within a
comment). See
Another use case arises when there is a need to call an extension function that expects a lexical XML document as input.
Another use case for this function is serializing instances of the data model into a human
readable format for the purposes of debugging. Using the output:serialization-parameters, allows for serializing any valid
XDM instance without raising a serialization error.
There are also use cases where the application wants to post-process the output of a
query or transformation, for example by adding an internal DTD subset, or by inserting
proprietary markup delimiters such as the <% ... %> used by some
templating languages.
The ability to specify the serialization parameters in an output:serialization-parameters
element provides backwards compatibility with the 3.0 version of this specification; the ability to
use a map takes advantage of new features in the 3.1 version. The default parameter values are
implementation-defined when an output:serialization-parameters
element is used (or when the argument is omitted), but are fixed by this specification in the
case where a map (including an empty map) is supplied for the argument.
Given the variables:
The following call might produce the output shown:
The following call would also produce the output shown (though the second argument could equally well be supplied
as an empty map ({}), since both parameters are given their default values):
This function takes as input an HTML document, and returns the document node at the root of an XDM tree representing the parsed document.
If $value is the empty sequence the function returns the empty sequence.
In other cases, $value is expected to contain an HTML document supplied
either as a string or a binary value.
The entries that may appear in the $options map are as follows:
The character encoding to use to decode a sequence of octets that represents an HTML document.
Indicates whether the function should fail with a dynamic error if the input is not syntactically valid.
Defines how to handle elements in the HTMLTemplateElement.content
property.
If this option is true, the template element’s
children are the children of the content property’s document
fragment node.
If this option is false, the template element’s
children are the empty sequence.
The default behaviour is
This allows an implementation to support the behaviour defined in
template elements with XSLT and XPath
This option would default to true for an XSLT processor
operating on an HTML DOM constructed from an XHTML document.
This option would default to false for an XPath processor
using the
The
If $value is not the empty sequence, an input byte stream is constructed as follows:
If $value is an xs:string, then in principle no decoding is needed.
Conceptually, however, the HTML parsing algorithm always starts by decoding an octet
stream. The string is therefore first encoded using UTF-8, and the resulting octet
stream is then passed to the HTML parser with a
If the first codepoint of the string is
If the type of $value is a sequence of octets (xs:hexBinary or
xs:base64Binary) the encoding of the input byte stream is determined in a
way consistent with
The encoding key of $options is interpreted in step 2 of
If the encoding key of $options is not specified, step 2
of
The resulting byte stream is then used to construct an XDM representation of the HTML document in a way that is equivalent to:
Tokenizing the byte stream according to the HTML parsing algorithm as described in
Constructing a HTMLDocument object for HTML documents, or an
XMLDocument for XML/XHTML documents as described in
Building an XDM representation of the HTMLDocument or XMLDocument
according to the rules in
The implementation
The implementation
The function is
A dynamic error is raised $value is not a well-formed HTML document.
If the HTML parser accepts a string as the input then that may be used directly when
$value is an xs:string instead of converting the string to
a sequence of octets in an
The WHATWG Encoding specification defines the ISO 8859-1 (latin1) and ASCII encodings as aliases of the windows-1252 encoding.
The expression parse-html(()) returns ().
The expression parse-html("<p>Hello</p>") returns an XDM
document node equivalent to the result of parsing the XML
Hello
]]>The expression parse-html("<p>Hi</p>", method:="html")
is equivalent to parse-html("<p>Hi</p>").
New in 4.0
Reads an external resource containing HTML, and returns the result of parsing the resource as HTML.
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The effect of the two-argument function call fn:html-doc($H, $M)is equivalent to the function composition
fn:unparsed-binary($H) => fn:parse-html($M).
If $source is the empty sequence, the function returns the empty sequence.
The function may raise any error defined for the
New in 4.0
Returns the context position from the dynamic context.
Returns the context position from the dynamic context. (See
A type error is raised
Returns the context size from the dynamic context.
Returns the context size from the dynamic context. (See
A type error is raised
Under most circumstances, the context size is absent only if the context value is absent. However, XSLT 3.0 with streaming defines situations in which the context value and context position are known, but the context size is unknown.
Returns the current date and time (with timezone).
Returns the current dateTime (with timezone) from the dynamic context. (See xs:dateTime that is current at some time during the evaluation of a
query or transformation in which
This function is fn:current-dateTime() is
If the implementation supports data types from XSD 1.1 then the returned value will be
an instance of xs:dateTimeStamp. Otherwise, the only guarantees are that it
will be an instance of xs:dateTime and will have a timezone component.
The returned xs:dateTime will always have an associated timezone, which
will always be the same as the implicit timezone in the dynamic context
current-dateTime() returns an xs:dateTimeStamp
corresponding to the current date and time. For example, a call of
current-dateTime() might return
2004-05-12T18:17:15.125Z corresponding to the current time on May 12,
2004 in timezone Z.
Returns the current date.
Returns xs:date(fn:current-dateTime()). This is an xs:date
(with timezone) that is current at some time during the evaluation of a query or
transformation in which
This function is
The returned date will always have an associated timezone, which will always be the same as the implicit timezone in the dynamic context
current-date() returns an xs:date corresponding to the
current date. For example, a call of current-date() might return
2004-05-12+01:00.
Returns the current time.
Returns xs:time(fn:current-dateTime()). This is an xs:time
(with timezone) that is current at some time during the evaluation of a query or
transformation in which
This function is fn:current-time() is
The returned time will always have an associated timezone, which will always be the same as the implicit timezone in the dynamic context
current-time() returns an xs:time corresponding to the
current time. For example, a call of current-time() might return
23:17:00.000-05:00.
Returns the value of the implicit timezone property from the dynamic context.
Returns the value of the implicit timezone property from the dynamic context. Components
of the dynamic context are described in
Returns the value of the default collation property from the
Returns the value of the default collation property from the
The default collation property can never be absent. If it is not explicitly defined, a
system defined default can be invoked. If this is not provided, the Unicode codepoint
collation (http://www.w3.org/2005/xpath-functions/collation/codepoint) is
used.
In most cases, the default collation is known statically,
and a call on this function can therefore be pre-evaluated during static analysis. The only
notable exception is when a call on default-collation() is used to define
the default value of a parameter to a user-defined function. In this case it is interpreted
as a reference to the default collation in the context of the relevant function call,
which may differ from the default collation of the function definition.
Returns the value of the default language property from the dynamic context.
Returns the value of the default language property from the dynamic context. Components
of the dynamic context are described in
The default language property can never be absent. The functions
This function returns the value of the
The function (despite its name)
returns the value of the
Components of the dynamic context are described in
The executable base URI will in many cases be the same as the static base URI in the static context.
However, XQuery and XSLT give an implementation freedom to use different base URIs during
the static analysis phase and the dynamic evaluation phase, that is, for retrieval of compile-time
and run-time resources respectively. This is appropriate when the implementation allows
the output of static analysis (a “compiled” query or stylesheet) to be deployed for execution
to a different location from the one where static analysis took place. In this situation, the
If a call on the
Returns
A call to $name and the arity supplied as
$arity. There can be at most one such function definition.
If no function definition can be identified (by name and arity), then an empty sequence is returned.
If a function definition is identified, then a function item is obtained from the function
definition using the same rules as for evaluation of a named function reference
(see
If the arguments to
An error is raised if the identified function depends on
components of the static or dynamic context that are not present, or that have
unsuitable values. For example function-lookup( #fn:name, 0 )
if the context value is absent, and function-lookup( #fn:id, 1 ) if the
context value is not a single node in a tree that is rooted at a document node.
The error that is raised is the same as the error that would be raised by the
corresponding function if called with the same static and dynamic context.
This function can be useful where there is a need to make a dynamic decision on which of several statically known functions to call. It can thus be used as a substitute for polymorphism, in the case where the application has been designed so several functions implement the same interface.
The function can also be useful in cases where a query or stylesheet module is written
to work with alternative versions of a library module. In such cases the author of the
main module might wish to test whether an imported library module contains or does not
contain a particular function, and to call a function in that module only if it is
available in the version that was imported. A static call would cause a static error if
the function is not available, whereas getting the function using
If the function that is retrieved by
However, the static and dynamic context of the call to
User-defined XSLT or XQuery functions should be accessible to
The function identity is determined in the same way as for
a named function reference. Specifically, if there is no context dependency, two calls
on
These specifications do not define any circumstances in which the dynamic context will
contain functions that are not present in the static context, but neither do they rule
this out. For example an API
The mere fact that a function exists and has a name does not of itself mean that the
function is present in the dynamic context. For example, functions obtained through
use of the
The expression (fn:function-lookup( #xs:dateTimeStamp, 1 ),
xs:dateTime#1)[1] ('2011-11-11T11:11:11Z') returns an
xs:dateTime value set to the specified date, time, and timezone; if
the implementation supports XSD 1.1 then the result will be an instance of the
derived type xs:dateTimeStamp. The query is written to ensure that no
failure occurs when the implementation does not recognize the type
xs:dateTimeStamp.
The expression
zip:binary-entry($source, $entry) if the function is available, or
an empty sequence otherwise.
Returns the name of the function identified by a function item.
If $function refers to a named function, fn:function-name($func)
returns the name of that function.
Otherwise ($function refers to an anonymous function),
fn:function-name($function) returns an empty sequence.
The prefix part of the returned QName is
Returns the arity of the function identified by a function item.
The $function.
Returns a string representing the identity of a function item.
The $function.
The returned string has the property that fn:function-identity($f1)
and fn:function-identity($f2) are codepoint-equal if and only if $f1
and $f2 have the same function identity. Apart from this property, the
result is
In the case of maps and arrays, the result follows the following rule:
If $X and $Y are both maps or arrays then fn:function-identity($X)
fn:function-identity($Y) unless
$X and $Y are indistinguishable, that is unless every operator or function applied
to $X returns the same result as for $Y. Even in this case, however, the
result of the comparison fn:function-identity($X) eq fn:function-identity($Y)
is
This function enables applications to test whether two expressions or variables reference the same function item. This may be useful, for example, to allow caching of function results to avoid repeated evaluation. The results of previous function invocations might be held in a map whose key is the function identity.
The function identity, by definition, is generated upon the creation of a function item.
Specific expressions that create function items have their own rules for the identity
of the returned functions: for example, it is guaranteed that evaluation of a function
reference to a system function with no captured context (such as fn:abs#1)
will always return the same function item.
It is not meaningful to store or compare the result of calling
The result of an expression such as function-identity(abs#1) eq function-identity(abs(?))
may be either true or false, because it is abs#1 and abs(?) return the same function item.
Similarly, function-identity({ 1:() }) eq function-identity(map:entry(1, ()))
may be either true or false.
Returns the annotations of the function item.
The fn:function-annotations function returns the annotations of
$function as a sequence of
The result is a sequence of map(xs:QName, xs:anyAtomicType*).
If a function (for example, a built-in function) has no annotations,
the result of the function is an empty sequence.
For each annotation, a map is returned, with a single entry. The
key of the map entry is the name of the annotation as an xs:QName.
The value of the entry is the value of the annotation as a sequence of atomic items.
If the annotation has no values, the associated value is an empty sequence.
In the common case where the annotation names are all unique,
the result of the function can readily be converted into single map by applying the function
map:merge.
Changes the function to return a sequence of key-value pairs rather than a map.
Changes the function to return a sequence of key-value pairs rather than a map.
Applies the function item $action to every item from the sequence $input
in turn, returning the concatenation of the resulting sequences in order.
The function calls $action($item, $pos) for each item in $input,
where $item is the item in question and $pos is its 1-based
ordinal position in $input. The final result is the sequence concatenation
of the result of these calls, preserving order.
The $action callback function accepts an optional position argument.
Returns those items from the sequence $input for which the supplied function
$predicate returns true.
The function returns a sequence containing those items from $input
for which $predicate($item, $pos) returns true, where $item
is the item in question, and $pos is its 1-based ordinal position within $input.
As a consequence of the function signature and the function calling rules, a type error
occurs if the supplied $predicate function returns anything other than a single
xs:boolean item or an empty sequence; there is no conversion to an effective boolean
value, but an empty sequence is interpreted as false.
If $predicate is an arity-1 function,
the function call fn:filter($input, $predicate) has a very similar effect to the
expression $input[$predicate(.)]. There are some differences, however. In the case of
$F is required to return an optional boolean;
there is no special treatment for numeric predicate values, and no conversion to an
effective boolean value. Also, with a filter expression $input[$predicate(.)],
the focus within the predicate is different from that outside; this means that the use of a
context-sensitive function such as fn:lang#1 will give different results in
the two cases.
() when there is no @id attribute;
this is treated as false.The $predicate callback function accepts an optional position argument.
The $predicate callback function may return an empty sequence (meaning false).
Processes the supplied sequence from left to right, applying the supplied function repeatedly to each item in turn, together with an accumulated result value.
If $input is empty, the function returns $init.
If $input contains at least one item, the function calls
$action($init, $input[1]), returning a value A1.
If $input contains a second item, the function then calls
$action(A1, $input[2]), returning A2; to process the nth
item it calls $action(A/n-1, $input[N]).
This continues in the same way until the end of the $input sequence; the final result is
the result of the last call on $action.
As a consequence of the function signature and the function calling rules, a type error
occurs if the supplied function $action cannot be applied to two arguments, where
the first argument is either the value of $init or the result of a previous
application of $action, and the second
is any single item from the sequence $input.
This operation is often referred to in the functional programming literature as
“folding” or “reducing” a sequence. It typically takes a function that operates on a pair of
values, and applies it repeatedly, with an accumulated result as the first argument, and
the next item in the sequence as the second argument. The accumulated result is
initially set to the value of the $init argument, which is conventionally a
value (such as zero in the case of addition, one in the case of multiplication, or a
zero-length string in the case of string concatenation) that causes the function to
return the value of the other argument unchanged.
Unlike other functions that apply a user-supplied callback function to successive
items in a sequence, this function does not supply the current position to the callback function
as an optional argument. If positional information is required, this can be achieved by
first forming the sequence $input ! { 'position': position(), 'item': . }
and then applying the
true if any item in the sequence has an effective boolean
value of truetrue only if every item in the sequence has an effective
boolean value of trueProcesses the supplied sequence from right to left, applying the supplied function repeatedly to each item in turn, together with an accumulated result value.
If $input is empty, the function returns $init.
Let I/n be the last item in $input, and let A/n be $init.
The function starts by calling $action(I/n, $init), producing
a result A/n-1.
If there is a previous item, I/n-1,
the function then calls $action(I/n-1, A/n-1), producing
the result A/n-2.
This continues in the same way until the start of the $input sequence is reached; the final result is
the value A/0.
As a consequence of the function signature and the function calling rules, a type error
occurs if the supplied function $action cannot be applied to two arguments, where
the first argument is any item in the sequence $input, and the second is either
the value of $init or the result of a previous application of
$action.
This operation is often referred to in the functional programming literature as
“folding” or “reducing” a sequence. It takes a function that operates on a pair of
values, and applies it repeatedly, with the next item in the sequence as the first
argument, and the result of processing the remainder of the sequence as the second
argument. The accumulated result is initially set to the value of the $init
argument, which is conventionally a value (such as zero in the case of addition, one in
the case of multiplication, or a zero-length string in the case of string concatenation)
that causes the function to return the value of the other argument unchanged.
In cases where the function performs an associative operation on its two arguments (such
as addition or multiplication),
Unlike other functions that apply a user-supplied callback function to successive
items in a sequence, this function does not supply the current position to the callback function
as an optional argument. If positional information is required, this can be achieved by
first forming the sequence $input ! { 'position': position(), 'item': . }
and then applying the
Processes a supplied value repeatedly, continuing while some condition remains true, and returning the first value that does not satisfy the condition.
Informally, the function behaves as follows:
$pos is initially set to 1.
$predicate($input, $pos) is evaluated. If the result is
false or (), the function returns the value of $input.
Otherwise, $action($input, $pos) is evaluated, the resulting value is
used as a new $input, and the process repeats from step 2 with
$pos incremented by 1.
While-do loops are very common in procedural programming languages, and this function provides a way to write functionally clean and interruptible iterations without side-effects. As long as a given condition is met, an new value is computed and tested again. Depending on the use case, the value can be a simple atomic item or an arbitrarily complex data structure.
The function
Note that, just as when writing recursive functions, it is easy to construct infinite loops.
The following example generates random doubles. It is interrupted once a number exceeds a given limit:
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Processes a supplied value repeatedly, continuing when some condition is false, and returning the value that satisfies the condition.
Informally, the function behaves as follows:
$pos is initially set to 1.
$action($input, $pos) is evaluated, and the resulting value
is used as a new $input.
$predicate($input, $pos) is evaluated. If the result is
true, the function returns the value of $input.
Otherwise, the process repeats from step 2 with $pos incremented by
1.
When the predicate returns an empty sequence, this is treated as false.
Do-until loops are very common in procedural programming languages, and this function provides a way to write functionally clean and interruptible iterations without side-effects. A new value is computed and tested until a given condition fails. Depending on the use case, the value can be a simple atomic item or an arbitrarily complex data structure.
The function
Note that, just as when writing recursive functions, it is easy to construct infinite loops.
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Applies the function item $action to successive pairs of items taken one from
$input1 and one from $input2, returning the concatenation of the
resulting sequences in order.
The function returns the value of the expression:
If one sequence is longer than the other, excess items in the longer sequence are ignored.
The $action callback function accepts an optional position argument.
Sorts a supplied sequence, based on the value of a sort key supplied as a function.
This function is retained for compatibility from version 3.1 of this specification. Version 4.0
introduces two more powerful functions,
The function call fn:sort($input, $collation, $key) is defined to have the same effect as the
call fn:sort-by($input, { 'key': $key, 'collation': $collation, 'order': 'ascending'}).
See
The result of the function is a sequence that contains all the items from $input,
typically in a different order, the order being defined by the supplied sort key definitions.
If the set of computed sort keys contains values that are not comparable using the lt operator then the sort
operation will fail with a type error (
To sort a set of strings $in using Swedish collation:
To sort a sequence of employees by last name as the major sort key and first name as the minor sort key, using the default collation:
Sorts a supplied sequence, based on the value of a number of sort keys supplied as functions.
The result of the function is a sequence that contains all the items from $input,
typically in a different order, the order being defined by the supplied
A
key: A fn:data#1,
which atomizes the item.
collation: A xs:string or xs:untypedAtomic. If no collation is supplied, the default
collation from the static context is used.
When comparing values of types other than xs:string or xs:untypedAtomic,
the collation is ignored (but an error
order: An "ascending" or
"descending". The default is "ascending".
The number of sort key definitions is determined by the number of records supplied
in the $keys argument. If the argument is absent or empty, the default is
a single sort key definition using the function data#1, using the default collation
from the static context, and with order ascending.
The result of the fn:sort-by function is obtained as follows:
The result sequence contains the same items as the input sequence $input,
but generally in a different order.
The sort key definitions are established as described above.
The sort key definitions are in major-to-minor order. That is, the position of two
items $A and $B in the result sequence is determined first by the
relative magnitude of their
primary sort key values, which are computed by evaluating the
When a pair of corresponding sort key values of $A and $B are
found to be not equal,
then $A precedes $B in the result sequence
if both the following conditions are true, or if both conditions are false:
The sort key value for $A is less than the sort key value for $B,
as defined below.
The "ascending".
If all the sort key values for $A and $B are pairwise equal, then
$A precedes $B in the result sequence if and only if
$A precedes $B in the input sequence.
That is, the sort is
Each sort key value for a given item is obtained by applying the sort key
function of the corresponding sort key definition to that item. The result
of this function is in the general case a sequence of atomic items.
Two sort key values $a and $b are compared as follows:
Let $C be the collation in the corresponding sort key definition.
Let $REL be the result of evaluating op:lexicographic-compare($key($A), $key($B), $C)
where op:lexicographic-compare($a, $b, $C) is defined as follows:
Here op:simple-compare($k1, $k2) is defined as follows:
This raises an error if two keys are not comparable, for example
if one is a string and the other is a number, or if both belong to a non-ordered
type such as xs:QName.
If $REL is zero, then the two sort key values are deemed
equal; if $REL is -1 then $a is deemed less than
$b, and if $REL is +1 then $a is deemed greater than
$b
If the set of computed sort keys contains values that are not comparable using the lt operator then the sort
operation will fail with a type error (
The function is a generalization of the
If the sort key for an item evaluates to an empty sequence, the effect of the rules is that this item
precedes any value for which the key is non-empty. This is equivalent to the effect of the XQuery option
empty least. The effect of the option empty greatest can be achieved by adding an
extra sort key definition with { 'key': fn { empty(K(.) } }: when comparing boolean sort keys,
false precedes true.
To sort a set of strings $in using Swedish collation:
To sort a sequence of employees by last name as the major sort key and first name as the minor sort key, using the default collation:
To sort a sequence of employees first by increasing last name (using Swedish collation order) and then by decreasing salary:
New in 4.0.
Sorts a supplied sequence, according to the order induced by the supplied comparator functions.
Informally, the items of the supplied $input are compared against each other,
using the supplied $comparators. The result is a sorted sequence.
Each comparator function takes two items and returns an xs:integer that
defines the relationship between these items, in accordance with the
The comparators are evaluated one after the other, either completely or
until the result is an integer other than 0.
If the last integer returned is negative or 0, the first item is
returned before the second.
Otherwise, the second item is returned first.
Users are responsible for supplying transitive comparators; otherwise, the result
might not be correctly sorted. An example for a non-transitive and thus unsuitable
comparator is fn($a, $b) { if ($a mod 2 = 1) then 1 else -1 },
as it considers odd numbers to be greater than even numbers.
Sorting is
More formally, assuming that the comparators raise no errors and are transitive, the effect of the function is equivalent to the following implementation in XQuery:
An implementation is free to choose any sorting algorithm as long as the result returned is stable and matches the result of the implementation in XQuery.
New in 4.0
Returns all the GNodes reachable from a given start GNode by applying a supplied function repeatedly.
The function works with both XNodes and JNodes.
The value of $node is a node from which navigation starts. If $node is an
empty sequence, the function returns an empty sequence.
The value of $step is a function that takes a single GNode as input, and returns a set of GNodes as its result.
The result of the $node by applying the $step function one or more times.
Although $step may return any sequence of GNodes, the result is treated as a set: the order of GNodes
in the sequence is ignored, and duplicates are ignored. The result of of the
transitive-closure function will always be a sequence of GNodes in document order with no duplicates.
Cycles in the data are not a problem; the function stops searching when it finds no new GNodes.
The function may fail to terminate if the supplied $step function constructs and returns
new GNodes. A processor
The $node GNodes is not included in the result, unless it is reachable by applying
the $step function one or more times. If a result is required that does include $node,
it can be readily added to the result using the union operator:
$node | transitive-closure($node, $step).
The following example, given $root as the root of an XSLT stylesheet module, returns the URIs
of all stylesheet modules reachable using xsl:import and xsl:include declarations:
This example uses the XSLT-defined document() function.
New in 4.0
Makes a dynamic call on a function with an argument list supplied in the form of an array.
The result of the function is obtained by invoking the supplied function $function with arguments
taken from the members of the supplied array $arguments. The first argument of the function call is the first
member of $arguments, the second argument is the second member of $arguments, and so on.
The arity of the supplied function $function must be less than or equal to the size
of the array $arguments.
The effect of calling fn:apply($f, [$a, $b, $c, ...]) is the same as the effect of the dynamic function call
$f($a, $b, $c, ....). For example, the coercion rules are applied to the supplied arguments
in the usual way. Among other things this means that excess arguments are ignored.
A dynamic error is raised if the arity of the function $function is greater than the size of the
array $arguments (
The function is useful where the arity of a function item is not known statically.
The expression apply($f, array:subarray([ "a", "b", "c", "d", "e", "f" ], 1, function-arity($f)))
calls the supplied function $f supplying the number of arguments required by its arity.
As a result of changes to the coercion rules, the number of supplied arguments can be greater than the number required: extra arguments are ignored.
Performs partial application of a function item by binding values to selected arguments.
The result is a function obtained by binding values to selected arguments of
the function item $function. The arguments to be bound are represented
by entries in the $arguments map: an entry with key $i
and value $v causes the argument at position $i (1-based)
to be bound to $v.
Any entries in $arguments whose keys are greater than the arity of
$function are ignored.
If $arguments is an empty map then the function returns $function
unchanged.
For example, the effect of calling fn:partial-apply($f, { 2: $x })
is the same as the effect of the partial
appplication $f(?, $x, ?, ?, ....).
The coercion rules are applied to the supplied arguments
in the usual way.
Unlike a partial application using place-holder arguments:
The arity of $function need not be statically known.
It is possible to bind all the arguments of $function: the effect
is to return a zero-arity function.
The result is a
See also
$function minus the
number of parameters in $function that map to supplied
arguments in $arguments.
$function
that do not map to supplied
arguments in $arguments.
$function
that do not map to supplied
arguments in $arguments,
retaining order. The result type of the returned function
is the same as the result type of $function.
An implementation that can determine a more specific signature (for example, through use of type analysis) is permitted to do so.
$function.
$function, augmented,
for each supplied argument, with
a binding of the converted argument value
to the corresponding parameter name.
A type error is raised if any of the supplied arguments, after applying the coercion rules, does not match the required type of the corresponding function parameter.
In addition, a dynamic error may be raised if any of the supplied arguments does not match other constraints on the value of that argument (for example, if the value supplied for a parameter expecting a regular expression is not a valid regular expression); or if the processor is able to establish that evaluation of the resulting function will fail for any other reason (for example, if an error is raised while evaluating a subexpression in the function body that depends only on explicitly supplied and defaulted parameters).
See also
The function is useful where the arity of a function item is not known statically, or where all arguments in a function are to be bound, returning a zero-arity function.
New in 4.0
Returns a function whose effect is to apply a supplied binary operator to two arguments.
The supplied operator must be one of:
",", "and", "or", "+",
"-", "*", "div", "idiv",
"mod", "=", "<", "<=",
">", ">=", "!=", "eq",
"lt", "le", "gt", "ge",
"ne", "<<", ">>",
"precedes", "follows",
"is", "is-not", "||", "|", "union",
"except", "intersect", "to",
"otherwise".
The result of calling fn:op("⊙"), where ⊙ is one of the above operators, is
the function represented by the XPath expression:
fn($x, $y) { $x ⊙ $y }
For example, op("+") returns fn($x, $y) { $x + $y }.
A type error is raised
The function is useful in contexts where an arity-2 callback function needs to be supplied, and a standard operator meets the requirement.
For example, the XSLT xsl:map instruction
has an on-duplicates attribute that expects such a function. Specifying
on-duplicates="op(',')" is equivalent to specifying
on-duplicates="fn($x, $y) { $x, $y }
The function is also useful in cases where the choice of operator to apply is made dynamically.
Some operators (such as and, or, and otherwise)
have custom error handling semantics, with the effect that evaluating one of the operands cannot
cause an error unless the other operand has a particular value
(see op('and')(X, Y)
will have the normal semantics of a dynamic function call, where the arguments are evaluated in any order,
and a failure evaluating any argument may cause the function call as a whole to fail.
New in 4.0
Returns a record containing information about the type annotation of an atomic value.
Given an atomic value, the function returns a
The result will always have ?is-simple = true() and ?variety = "atomic". In a non-schema-aware
environment the type will always be a built-in atomic type in the xs namespace: see
Note that under the function coercion rules, it is possible to supply a node as the argument, which
will then be atomized. In simple cases the type annotation on the atomized value will be the same as
the type annotation on the node. But this is not always true: for example the type annotation on
the node might be a complex type with simple content, while the type annotation on its atomized
value is the corresponding simple content type. To get the type annotation on the node, use the function
This function should not be used as a substitute for an instance of test. The precise type annotation
of the result of an expression is not always predictable, because processors are free to deliver a more specific type
than is mandated by the specification. For example, if $n is of type xs:positiveInteger,
then the result of abs($n) is guaranteed to be an instance of xs:integer, but an
implementation might reasonably return the supplied value unchanged: that is, a value whose actual type
annotation is xs:positiveInteger. Similarly the type annotation of the value returned by
position() might be xs:long rather than xs:integer.
Implementations xs:string.
New in 4.0
Returns a record containing information about the type annotation of an element or attribute node.
Given an element or attribute node, the function returns a
For an element that has not been schema-validated, the type annotation is always xs:untyped.
For an attribute that has not been schema-validated, the type annotation is always xs:untypedAtomic.
The type annotation of an attribute node is always a simple type; the type annotation of an element node may be simple or complex.
New in 4.0
Returns a record containing information about a named schema type in the static context.
If the static context (specifically, the $name,
the function returns a
New in 4.0
Determines whether two atomic items are equal, under the rules used for comparing keys in a map.
The function eq operator):
Any two atomic items can be compared, regardless of their type.
No dynamic error is ever raised (the result is either true or false).
The result of the comparison never depends on the static or dynamic context.
Every value (including NaN) is equal to itself.
The comparison is symmetric: if A equals B, then B equals A.
The comparison is transitive: if A equals B and B equals C, then A equals C.
The function returns true if and only if one of the following conditions is true:
All of the following conditions are true:
$value1 is an instance of xs:string, xs:anyURI, or xs:untypedAtomic
$value2 is an instance of xs:string, xs:anyURI, or xs:untypedAtomic
fn:codepoint-equal($value1, $value2)
Strings are compared without any dependency on collations.
All of the following conditions are true:
$value1 is an instance of xs:decimal, xs:double, or xs:float
$value2 is an instance of xs:decimal, xs:double, or xs:float
One of the following conditions is true:
Both $value1 and $value2 are NaN
xs:double('NaN') is the same key as xs:float('NaN')
Both $value1 and $value2 are positive infinity
xs:double('INF') is the same key as xs:float('INF')
Both $value1 and $value2 are negative infinity
xs:double('-INF') is the same key as xs:float('-INF')
$value1 and $value2 when converted to decimal numbers with no rounding or loss of precision
are mathematically equal.
Every instance of xs:double, xs:float, and xs:decimal can be represented
exactly as a decimal number provided enough digits are available both before and after the decimal point. Unlike the eq
relation, which converts both operands to xs:double values, possibly losing precision in the process, this
comparison is transitive.
Positive and negative zero compare equal.
All of the following conditions are true:
One of the following conditions is true:
$value1 and $value2 are both instances of xs:date.
$value1 and $value2 are both instances of xs:time.
$value1 and $value2 are both instances of xs:dateTime.
$value1 and $value2 are both instances of xs:gYear.
$value1 and $value2 are both instances of xs:gYearMonth.
$value1 and $value2 are both instances of xs:gMonth.
$value1 and $value2 are both instances of xs:gMonthDay.
$value1 and $value2 are both instances of xs:gDay.
One of the following conditions is true:
Both $value1 and $value2 have a timezone
Neither $value1 nor $value2 has a timezone
$value1 eq $value2
Values having a timezone are never equal to values without one. The implicit timezone is not used.
All of the following conditions are true:
$value1 is an instance of xs:hexBinary or xs:base64Binary
$value2 is an instance of xs:hexBinary or xs:base64Binary
op:binary-equal($value1, $value2)
All of the following conditions are true:
One of the following conditions is true:
$value1 and $value2 are both instances of xs:boolean.
$value1 and $value2 are both instances of xs:QName.
$value1 and $value2 are both instances of xs:NOTATION.
$value1 and $value2 are both instances of xs:duration.
$value1 eq $value2
The internal function op:same-key was introduced in an earlier version of this specification
for comparing keys within a map.
In this version of the specification, the functionality is unchanged, but the function is exposed so that it
is available directly to applications.
The function is used to assess whether two atomic
items are considered to be duplicates when used as keys in a map. A map cannot
contain two separate entries whose keys are
The rules for comparing keys in a map are chosen to ensure that the comparison is:
true or false, never an error
Two atomic items may be distinguishable even though they are equal under this comparison. For example: they may have
different type annotations; dates and times may have different timezones; xs:QName values may have different
prefixes.
Unlike the eq operator and the xs:hexBinary and
xs:base64Binary values are considered distinct. This decision was made in order to preserve backwards
compatibility: if the values were treated as interchangeable, it would become impossible to construct certain maps that
could be validly constructed using earlier versions of the specification, and it would be difficult to make maps fully
interoperable between processors supporting different language versions, for example when calling
As always, any algorithm that delivers the right result is acceptable. For example, when testing whether an xs:double
value D is the same key as an xs:decimal value that has N significant digits, it is not
necessary to know all the digits in the decimal expansion of D to establish the result: computing the first N+1
significant digits (or indeed, simply knowing that there are more than N significant digits) is sufficient.
New in 4.0. The function replaces the internal op:same-key
function in 3.1
Atomic items of types xs:hexBinary
and xs:base64Binary are now mutually comparable. In rare cases, where an
application uses both types and assumes they are distinct, this can represent a backwards
incompatibility.
Returns a map that combines the entries from a number of existing maps.
The function $maps
argument.
Informally, the supplied maps are combined as follows:
There is one entry in the returned map for each distinct key present in the union
of the input maps, where two keys are distinct if they are not the
If there are duplicate keys, that is, if two or more maps contain entries having the
$options.
The $options argument takes the same values (with the same meanings)
as the map:merge, the default for duplicate keys is use-first.
The difference is for backwards compatibility reasons.
With the default options, when duplicate entries occur:
There will be a single entry in the result corresponding to a set of duplicate entries in the input.
The value of that entry will be taken from the first of the duplicates.
The position of that entry in the
The key of the combined entry
will correspond to the key of one of the duplicates: it is
xs:dateTime
values in different timezones.)
An error is raised $options indicates that duplicates are to be rejected, and a duplicate key is encountered.
An error is raised $options includes an entry whose key is defined
in this specification, and whose value is not a permitted value for that key.
If the input is an empty sequence, the result is an empty map.
If the input is a sequence of length one, the result map is indistinguishable from the input map.
There is no requirement that
the supplied input maps should have the same or compatible
types. The type of a map (for example map(xs:integer, xs:string)) is
descriptive of the entries it currently contains, but is not a constraint on how the map
may be combined with other maps.
The XSLT 3.0 recommendation included a specification of this function that incorrectly used
the option value { 'duplicates': 'unspecified' } in place of
{ 'duplicates': 'use-any' }. XSLT implementations wishing to
preserve backwards compatibility
$week, supplemented with an additional
entry.$week, with one entry replaced by a
new entry. Both input maps contain an entry with the key 6; the
one used in the result is the one that comes last in the input
sequence.$week, with one entry replaced by a
new entry. Both input maps contain an entry with the key 6; the
one used in the result is the one that comes first in the input
sequence.$week, with one entry replaced by a
new entry. Both input maps contain an entry with the key 6; the
entry that appears in the result is the For consistency with the new function duplicates option.
Returns a sequence containing all the keys present in a map.
Informally, the function $map argument and returns
the keys that are present in the map as a sequence of atomic items,
in
The number of items in the result will be the same as the number of entries in the map, and the result sequence will contain no duplicate values.
Returns a sequence containing selected keys present in a map.
Informally, the function $map argument. The
$predicate function takes the key and the value of the corresponding
map entry as an argument, and the result is a sequence containing the keys of those
entries for which the predicate function returns true, in
A return value of () from the predicate function is
treated as false.
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Returns a sequence containing all the values present in a map, in order.
The function $map argument and returns the values that are present in the map as
a sequence, in
The effect of the function is equivalent to $map?*.
New in 4.0
Returns a sequence containing all the key-value pairs present in a map, each represented
as a
The function $map argument and returns the key-value pairs that are present in the map as
a sequence of
New in 4.0
Tests whether a supplied map contains an entry for a given key.
The function true if the $map contains an entry with the $key; otherwise it returns false.
Returns true if the supplied map contains no entries.
The function returns true if and only if $map contains no
entries, that is, if map:size($map) eq 0.
New in 4.0
Returns the value associated with a supplied key in a given map.
The function $map that has
the $key. If there is such an entry, it returns the associated value;
if not, it returns the supplied $default value, which defaults to the empty sequence.
A return value of () from (), or it could
indicate that the key is not present in the map. The two cases can be distinguished by
either by calling $default value to return a value known never to appear in the map.
Invoking the get with no $default
argument: that is, when $map is a map, the expression
$map($K) is equivalent to map:get($map, $K). Similarly, the
expression map:get(map:get(map:get($map, 'employee'), 'name'), 'first') can
be written as $map('employee')('name')('first').
A third argument is added, allowing user control of how absent keys should be handled.
Searches the supplied input sequence and any contained maps and arrays for a map entry with the supplied key, and returns the corresponding values.
The function $input
looking for map entries whose key is the $key. The associated value in any such map entry (each being in general a sequence)
is returned as a member of the result array.
The search processes the $input sequence using the following recursively defined rules
(any equivalent algorithm may be used provided it delivers
the same result, respecting those rules that constrain the order of the result):
To process a sequence, process each of its items in order.
To process an item that is an array, process each of its members in order (each member is, in general, a sequence).
To process an item that is a map, then for each key-value entry (K, V)
in the map (in
If K is the $key,
then add V as a new member to the end of the result array.
Process V (which is, in general, a sequence).
To process an item that is neither a map nor an array, do nothing. (Such items are ignored).
If $input is an empty sequence, map, or array, or if the requested $key is not found,
the result will be a zero-length array.
Enhanced to allow for ordered maps.
Returns a map containing all the contents of the supplied map, but with an additional entry, which replaces any existing entry for the same key.
If $map contains an entry whose key is the $key, the function returns
a map in which that entry is replaced (at the same relative position)
with a new entry whose value is $value. It is
$key.
All other entries in the map are unchanged, and retain their relative order.
Otherwise, when $map contains no such entry, the function
returns a map containing all entries from the supplied $map
(retaining their relative position) followed by a new entry whose key
is $key and whose associated value is $value.
There is no requirement that the type of $key and $value be consistent with the types
of any existing keys and values in the supplied map.
It is possible to force the new entry to go at the end of the sequence by calling
map:remove before calling map:put.
It can happen that the supplied $key is the $map, but nevertheless
differs from the existing key in some way:
for example, it might have a different type annotation, or it might be an xs:dateTime
value in a different timezone. In this situation it is
$key or the existing key.
Enhanced to allow for ordered maps.
It is no longer guaranteed that the new key replaces the existing key.
The function $key, and its associated value is $value.
The function
The
Returns a map containing all the entries from a supplied map, except
The function $map except for any entry whose key is
the $keys.
No failure occurs $keys does not correspond to any entry in $map;
that key value is simply ignored
The relative position of retained entries in the result map
is the same as their relative position in $map.
Enhanced to allow for ordered maps.
Applies a supplied function to every entry in a map, returning the
The function $map argument and applies the supplied function
to each entry in the map, in
The function supplied as $action takes two arguments. It is called
supplying the key of the map entry as the first argument, and the associated value as
the second argument.
map:keys.This XQuery example converts the entries in a map to attributes on a newly constructed element node:
The result is the element <box height="3" width="4"
depth="5"/>.
Enhanced to allow for ordered maps.
Selects entries from a map, returning a new map.
The function $map argument and applies the supplied function
to each entry in the map; the result is a new map containing those entries for which
the function returns true. A return value of () from the
predicate is treated as false.
The function supplied as $predicate takes two arguments. It is called
supplying the key of the map entry as the first argument, and the associated value as
the second argument.
The relative $map.
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Enhanced to allow for ordered maps.
Returns a map that typically contains one entry for each item in a supplied input sequence.
Informally, the function processes each item in $input in order.
It calls the $key function on that item to obtain a sequence of key values,
and the $value function to obtain an associated value.
Then, for each key value:
If the key is not already present in the target map, the processor adds a new key-value pair to the map, with that key and that value.
If the key is already present, the processor combines the new value for the key
with the existing value; the way they are combined is determined by the
duplicates option.
By default, when two duplicate entries occur:
A single combined entry will be present in the result.
This entry will contain the
The position of the combined entry in the
The key of the combined entry
will correspond to the key of one of the duplicates: it is
xs:dateTime values in different timezones.)
The $options argument can be used to control the
way in which duplicate keys are handled.
The $options map are as follows:
fn($a, $b){ $a }.
The effect is that the first of the duplicates is chosen.
fn($a, $b){ $b }.
The effect is that the last of the duplicates is chosen.
fn($a, $b){ one-of($a, $b) }
where one-of chooses either $a or $b in
an fn($a, $b){ $a, $b }
(or equivalently, the function op(",")).
The effect is that the result contains the fn(item()*, item()*) as item()*.
The function is called for any entry in the input sequence that has the
X => F(Y) => F(Z).
An error is raised $options indicates that duplicates are to be rejected, and a duplicate key is encountered.
An error is raised $options includes an entry whose key is defined
in this specification, and whose value is not a permitted value for that key.
The default function for both $key and $value is the identity function.
Although it is permitted to default both, this serves little purpose: usually at least one of these arguments
will be supplied.
. mod 3. The
function to compute the value is the identity function, and duplicates are combined by
sequence concatenation.The following expression creates a map whose keys are employee @ssn values, and whose
corresponding values are the employee nodes:
The following expression creates a map whose keys are employee @location values, and whose
corresponding values represent the number of employees at each distinct location. Any employees that
lack an @location attribute will be excluded from the result.
The following expression creates a map whose keys are employee @location values, and whose
corresponding values contain the employee node for the highest-paid employee at each distinct location:
The following expression creates a map allowing efficient access to every element in a document by means
of its
The following expression creates a map allowing efficient access to values in a recursive JSON structure using hierarchic paths:
The result is the map:
New in 4.0
Returns the number of entries in the supplied map.
The function $map argument and returns the number of entries that are present
in the map.
Constructs a collation URI with requested properties.
The function is supplied with a map defining the properties required of the collation, and returns a collation URI with these properties.
Specifically, it returns a string in the form of a URI with the scheme and path
http://www.w3.org/2013/collation/UCA followed by an optional
query part. The query part is absent if options is empty.
Otherwise it consists of a question mark followed
by a sequence of one or more semicolon-separated parameters. Each parameter
is a keyword-value pair, the keyword and value being separated by an equals sign.
There is one keyword-value pair for each entry in the options map:
the keyword is the same as the string value of the key in the map, and the value
is the string value of the corresponding value, except where the value is of
type xs:boolean, in which case true and false
are translated to yes and no.
The function does not check whether the implementation actually recognizes
the resulting collation URI: that can be achieved using the
The properties available are as defined for the Unicode Collation Algorithm
(see
The
If the option key is of type xs:string, xs:anyURI,
or xs:untypedAtomic then it is converted to a string, and produces
a URI query parameter which is handled as described in
If the option key is of any other type then the function fails with a
type error
The following options are defined:
A type error is raised options includes an entry whose key is not of
type xs:string, xs:anyURI,
or xs:untypedAtomic, or whose corresponding value
is not castable to xs:string.
The expression collation({ 'lang': default-language() })
returns a collation suitable for the default language in the
dynamic context.
New in 4.0
Asks whether a collation URI is recognized by the implementation, and whether it has required properties.
The first argument is a candidate collation URI.
The second argument establishes the intended usage of the collation URI. The value is a sequence containing zero or more of the following:
compare indicates that the intended purpose of the collation
URI is to compare strings for equality or ordering, for example in functions such as
key indicates that the intended purpose of the collation
URI is to obtain collation keys for strings using the
substring indicates that the intended purpose of the collation
URI is to establish whether one string is a substring of another, for example
in functions such as
The function returns true if and only if the implementation recognizes the candidate
collation URI as one that can be used for each of the purposes listed in the
$usage argument. If the $usage argument is absent
or set to an empty sequence, the function returns true only if the collation is
available for all purposes.
If the candidate collation is a UCA collation specifying fallback=yes,
then this function will always return true: implementations are required to recognize
such a collation and use fallback behavior if there is no direct equivalent available.
The expression collation({ 'lang': default-language() })
returns a collation suitable for the default language in the
dynamic context.
New in 4.0
Given a string value and a collation, generates an internal value called a collation key, with the property that the matching and ordering of collation keys reflects the matching and ordering of strings under the specified collation.
Calling the one-argument version of this function is equivalent to calling the two-argument version supplying the default collation as the second argument.
The function returns an $K1 and $K2:
collation-key($K1, $C) eq collation-key($K2, $C) if and only if
compare($K1, $K2, $C) eq 0
collation-key($K1, $C) lt collation-key($K2, $C) if and only if
compare($K1, $K2, $C) lt 0
The collation used by this function is determined according to the rules in xs:base64Binary values
to ensure unambiguous and context-free comparison semantics.
An implementation is free to generate a collation key in any convenient way provided
that it always generates the same collation key for two strings that are equal under the
collation, and different collation keys for strings that are not equal. This holds only
within a single
It is possible to define collations that do not have the ability to generate collation
keys. Supplying such a collation will cause the function to fail. The ability to
generate collation keys is an
An error is raised
The function is provided primarily for use with maps. If a map is required where
codepoint equality is inappropriate for comparing keys, then a common technique is to
normalize the key so that equality matching becomes feasible. There are many ways
keys can be normalized, for example by use of functions such as
The result of the function is defined to be an xs:base64Binary value. Binary values
are chosen because they have unambiguous and context-free comparison semantics, because the value space
is unbounded, and because the ordering rules are such that between any two values in the ordered value space, an
arbitrary number of further values can be interpolated. The choice between xs:base64Binary
and xs:hexBinary is arbitrary; the only operation that behaves differently between the two binary
data types is conversion to/from a string, and this operation is not one that is normally required for
effective use of collation keys.
For collations based on the Unicode Collation Algorithm, an algorithm for computing
collation keys is provided in
The fact that collation keys are ordered can be exploited in XQuery, whose order by
clause does not allow the collation to be selected dynamically. This restriction can be circumvented
by rewriting the clause order by $e/@key collation "URI" as order by fn:collation-key($e/@key, $collation),
where $collation allows the collation to be chosen dynamically.
Note that xs:base64Binary becomes an ordered type
in XPath 3.1, making binary collation keys possible.
The
"A" and "a" have the same collation key under this
collation.As the above examples illustrate, it is important that when the
collation-key function is used to add entries to a map, then it must
also be used when retrieving entries from the map. This process can be made less
error-prone by encapsulating the map within a function:
fn($k) { $M(collation-key($k, $collation) }.
Parses a string supplied in the form of a JSON text, returning the results in the form
of an XML
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The first argument is a JSON text as defined in
If $value is an empty sequence, the function returns the empty sequence.
The $options argument can be used to control the way in which the parsing
takes place. The
The entries that may appear in the $options map are as follows:
JSON-text in escape option is set to truevalidate is true then reject, otherwise retain.validate=true
liberal option has the value true.
fallback function
as described below; in the absence of a fallback function, they are replaced by
the character escaped and escaped-key will not be present in the XDM output.
all codepoints in the range
all codepoints that do not represent characters that are valid in the version of XML supported by the processor, including codepoints representing unpaired surrogates;
the backslash character itself (
\t), or a six-character escape sequence otherwise
(for example \uDEAD). Characters other than these will not be escaped in the result,
even if they were escaped in the input. In the result:
Any string element whose string value contains a
backslash character must have the attribute value escaped="true".
Any element that contains a key attribute whose string value
contains a backslash character must have the attribute
escaped-key="true".
The values of the escaped and
escaped-key attributes are immaterial when there is no backslash
present, and it is never necessary to include either attribute when its value
is false.
fallback option if the escape
option is present with the value true.
liberal:true() is specified):
for example \b or \uFFFF or \uDEAD.
By default, the escape sequence is replaced with the Unicode
REPLACEMENT CHARACTER. The function is \x0A).
The string, which results from invoking
number element generated in
the result will be the value obtained by calling the supplied function, and
then converting its result to a string by calling fn:string#1.
By default, numbers are represented in the XML output exactly as they
were written in the input.
Supplying the value xs:double#1 will cause the value to be
convered to type xs:double (which will then be represented
in the XML by converting the xs:double to a string).
Similarly xs:decimal#1 will convert to xs:decimal
(which potentially retains more precision, but disallows exponential notation), while
supplying a function that casts to (xs:decimal | xs:double) will treat
the value as xs:decimal if there is no exponent, or as xs:double
otherwise. The default value fn:identity#1 causes the value to be retained
unchanged as an xs:untypedAtomic. Before calling the supplied number-parser,
the value is first checked to ensure that it conforms to the JSON grammar (for example,
a leading plus sign and redundant leading zeroes are not allowed); these checks are disabled
if the liberal option is set to true. Note that the
option validate=true will cause the result to be validated
as type xs:double (disallowing NaN and infinity).
The various structures that can occur in JSON are transformed recursively to XDM values
according to the rules given in
The function returns a document node, whose only child is the element node representing the outermost construct in the JSON text.
The function is
The base URI of the returned document node is taken from the
The choice of namespace prefix (or absence of a prefix) in the names of constructed
nodes is
The XDM tree returned by the function does not contain any
unnecessary (albeit valid) nodes such as whitespace text nodes, comments, or processing instructions.
It does not include any whitespace in the value of number or boolean
element nodes, nor in the value of escaped or escaped-key
attribute nodes.
If the result is typed, every element named string will have an attribute named
escaped whose value is either true or false, and every element having
an attribute named key will also have an attribute named escaped-key whose value is either
true or false.
If the result is untyped, the attributes escaped and escaped-key will
either be present with the value true, or will be absent. They will never be present with the value false.
An error is raised $value does not conform to the JSON grammar as defined
by "liberal":true() is present and
the processor chooses to accept the deviation.
An error is raised validate option is true and the processor does not support
schema validation or typed data.
An error is raised $options includes an entry whose key is defined in this specification,
and whose value is not a permitted value for that key.
To read a JSON file, this function can be used in conjunction with the
Many JSON implementations allow commas to be used after the last item in an object or
array, although the specification does not permit it. The option
spec="liberal" is provided to allow such deviations from the
specification to be accepted. Some JSON implementations also allow constructors such as
new Date("2000-12-13") to appear as values: specifying
spec="liberal" allows such extensions to be accepted, but does not
guarantee it. If such extensions are accepted, the resulting value is
implementation-defined, and will not necessarily conform to the schema at
If the input starts with a byte order mark, this function ignores it. The byte order mark may have been added to the data stream in order to facilitate decoding of an octet stream to a character string, but since this function takes a character string as input, the byte order mark serves no useful purpose.
The possibility of the input containing characters that are not valid in XML (for example, unpaired surrogates)
arises only when such characters are expressed using JSON escape sequences. This is the only possibility because the input to the function
is an instance of xs:string, which by definition can contain only those characters that are valid in XML.
escaped attribute
on the second string element.The following example illustrates use of the fallback function to
handle characters that are invalid in XML.
Converts an XML tree, whose format corresponds to the XML representation of JSON defined in this specification, into a string conforming to the JSON grammar.
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The first argument $node is a node; the subtree rooted at this node will typically be
the XML representation of a JSON document as defined in
If $node is the empty sequence, the function returns the empty sequence.
The $options argument can be used to control the way in which the conversion
takes place. The
The entries that may appear in the $options map are as follows:
\/. By default the character is escaped, but this is only necessary
when the resulting JSON is embedded in HTML.The node supplied as $node must be one of the following:
An element node whose name matches the name of a global element declaration in the schema given in
If the type annotation of the element matches the type of the relevant element declaration in the schema (indicating that the element has been validated against the schema), then the element is considered valid.
Otherwise, the processor
Otherwise (if the processor does not attempt validation using the schema),
the processor http://www.w3.org/2005/xpath-functions, is such that validation
against the schema would have an outcome of
The process described here is not precisely equivalent to schema validation.
For example, schema validation will fail if there is an invalid xsi:type
or xsi:nil attribute, whereas this process will ignore such attributes.
An element node E having a key attribute and/or an escaped-key attribute
provided that E would satisfy one of the above
conditions if the key and/or escaped-key attributes were removed.
A document node having exactly one element child and no text node children, where the element child satisfies one of the conditions above.
Furthermore, $node must satisfy the following constraint
(which cannot be conveniently expressed in the schema). Every element M that is a descendant-or-self of
$node and has local name map and namespace URI http://www.w3.org/2005/xpath-functions
must satisfy the following rule: there must not be two distinct children of M (say C/1 and C/2)
such that the normalized key of C/1 is equal to the normalized key of C/2. The normalized key
of an element C is as follows:
If C has the attribute value escaped-key="true", then the value of the
key attribute of C, with all JSON escape sequences replaced by the corresponding Unicode characters
according to the JSON escaping rules.
Otherwise (the escaped-key attribute of C is absent or set to false),
the value of the key attribute of C.
Nodes in the input tree are handled by applying the following rules, recursively. In these rules the phrase
“an element named N” means “an element node whose local name is N and whose namespace URI is
http://www.w3.org/2005/xpath-functions”.
A document node having a single element node child is processed by processing that child.
An element named null results in the output null.
An element $E named boolean results in the output true or false
depending on the result of xs:boolean(fn:string($E))
An element $E named number is processed as follows.
The input is required to conform to the XSD rules defining a valid instance of xs:double
(excluding infinity and NaN), while the output is required to conform to the
JSON rules defining a valid JSON number. These rules are slightly different.
Specifically, the XSD rules require the value (after removing leading and trailing whitespace) to match the regular expression:
while the JSON rules require:
If the input value does not match the required JSON format, it must therefore be adjusted by applying the following steps:
Remove leading and trailing whitespace.
Remove any leading plus sign.
Remove any leading zero digits in the integer part, while ensuring that at least one digit remains.
If there is a decimal point that is not preceded by a digit, add a zero digit before the decimal point.
If there is a decimal point that is not followed by a digit, add a zero digit after the decimal point.
The output uses exponential notation if and only if the input uses exponential notation.
The rules have changed since version 3.1 of this specification. In previous versions, the supplied
number was cast to an xs:double, and then serialized using the rules of the
An element named string results in the output of the string value of the element, enclosed in
quotation marks, with any special characters in the string escaped as described below.
An element named array results in the output of the children of the array element,
each processed by applying these rules recursively: the items in the resulting list are enclosed between square brackets,
and separated by commas.
An element named map results in the output of a sequence of map entries corresponding to
the children of the map element, enclosed between curly braces and separated by commas.
Each entry comprises the value of the key attribute of the child element, enclosed in quotation marks
and escaped as described below, followed by a colon, followed by the result of processing the child element
by applying these rules recursively. The order of properties in the output JSON representation retains the order
of the children of the map element.
Comments, processing instructions, and whitespace text node children of map and array
are ignored.
Strings are escaped as follows:
If the attribute escaped="true" is present for a string value, or escaped-key="true" for a key value, then:
any valid JSON escape sequence present in the string is copied unchanged to the output;
any invalid JSON escape sequence results in a dynamic error
any unescaped occurrence of escape-solidus option) \", \b, \f, \n, \r, \t, \/
any other codepoint in the range 1-31 or 127-159 is replaced by an escape in the form \uHHHH where HHHH is the upper-case hexadecimal representation of the codepoint value.
Otherwise (that is, in the absence of the attribute escaped="true" for a string value,
or escaped-key="true" for a key value):
any occurrence of backslash is replaced by \\
any occurrence of
\", \b, \f, \n,
\r, or \t respectively;
any other codepoint in the range 1-31 or 127-159 is replaced by an escape in
the form \uHHHH where HHHH is the upper-case hexadecimal representation of the codepoint value.
A dynamic error is raised $options includes an entry whose key is defined in this specification,
and whose value is not a permitted value for that key.
A dynamic error is raised $node is not a document or element node or is not valid according to the schema for the XML representation of
JSONmap element has two children whose normalized key values are the same.
A dynamic error is raised $node includes a string labeled with escaped="true", or
a key labeled with escaped-key="true", where the content of the string or key
contains an invalid JSON escape sequence: specifically, where it contains a backslash (\) that is not followed by one
of the characters ", \, /, b, f, n,
r, t, or u, or where it contains the characters \u
not followed by four hexadecimal digits (that is [0-9A-Fa-f]{4}).
The rule requiring schema validity has a number of consequences, including the following:
The input cannot contain no-namespace attributes, or attributes in the namespace http://www.w3.org/2005/xpath-functions,
except where explicitly allowed by the schema. Attributes in other namespaces, however, are ignored.
Nodes that do not affect schema validity, such as comments, processing instructions, namespace nodes, and whitespace text node
children of map and array, are ignored.
Numeric values are restricted to those that are valid in JSON:
the schema disallows positive and negative infinity and NaN.
Duplicate key values are not permitted. \n and \u000A are treated as duplicates even though
the rules in the schema do not treat them as such.
The rule allowing the top-level element to have a key attribute (which is ignored)
allows any element in the output of the key attribute, and then convert this subtree
back to JSON, perhaps after a transformation. The rule means that an element with the appropriate name will be
accepted if it has been validated against one of the
types mapWithinMapType, arrayWithinMapType, stringWithinMapType,
numberWithinMapType, booleanWithinMapType, or nullWithinMapType.
The input
produces the result [ 1, "is", true ].
The input
produces the result { "Sunday": 1, "Monday": 2 }.
The input
produces the result [ 10, 17e2, 5 ].
An option has been added to suppress the escaping of the solidus (forwards slash) character.
Numbers now retain their original lexical form, except for any changes needed to satisfy JSON syntax rules (for example, stripping leading zero digits).
Analyzes sample data to generate a conversion plan suitable for use by the
The function takes as input a collection of document and element nodes and analyzes the trees rooted at these
nodes to determine a conversion plan for converting elements in these trees to maps, suitable for serialization
in JSON format. The conversion plan can be used
The rules followed by the function, and the detailed format of the conversion plan, are described
in
The conversion plan is organized by element and attribute name, so its effectiveness depends on the
$input collection being homogenous in its structure, and representative of the documents
that will subsequently be converted using the
This function is separate from the
The collection of documents that need to be analyzed to establish an effective conversion plan might be much smaller than the set of documents actually being converted.
Conversely, it might be that only a small number of documents need to be converted at a particular time, but the conversion plan used needs to take into account variations that might exist within a larger corpus.
If JSON output is required in a particular format, it might be necessary to fine-tune the automatically generated conversion plan to take account of these requirements.
It might be necessary to devise a conversion plan that can be used to convert individual documents as they arrive over a period of time, and to ensure that the same conversion rules are applied to each document even though documents might exhibit variations in structure.
The conversion plan is human-readable, which can help in understanding why the
output of
New in 4.0
Converts an element node into a map that is suitable for JSON serialization.
This function returns a map derived from
the element node supplied in $element. The map is in a form
that is suitable for JSON serialization, thus providing a mechanism for conversion
of arbitrary XML to JSON.
The map that is returned will always be a
The entries that may appear in the $options map are as follows.
The
"@"
is used."Q{uri}local".
Names in no namespace are output using the local name alone."Q{uri}local" if in a namespace,
or "Q{}local" if in no namespace. "Top-level" here means that the element
is one that appears explicitly in the sequence of elements passed in the $elements argument,
as distinct from a descendant of such an element.If $element is an empty sequence, the result is an empty sequence.
The principles for conversion from elements to maps are described
in
In general, every descendant element within the tree rooted at the supplied
$element maps to a key-value pair in which the key represents the element name, and the
corresponding value represents the attributes and children of the element. This key-value pair will be added
to the content representing its parent element, in a way that depends on the parent element's layout.
The representation of a node of any other kind depends on the layout chosen for its parent element.
A dynamic error
Any error in the conversion plan is treated as a type error
New in 4.0.
Parses CSV data, returning the results in the form of a record containing information about the names in the header, as well as the data itself.
If $value is the empty sequence, the function returns the empty sequence.
If $value is supplied as a binary value, it is converted to a string.
The function detects the encoding using the same rules as the text/xml
and application/xml may be skipped. Otherwise, if $value
is a string, it is processed unchanged.
The resulting input is CSV data, as defined in
If the input is the a zero-length string, the function
returns a parsed-csv-structure-record whose
rows entry is the empty sequence.
The $options argument can be used to control the way in which the parsing
takes place. The
If the $options argument is omitted or is an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The entries that may appear in the $options map are as follows:
xs:string whose length is exactly one.xs:string whose length is exactly one.
Defaults to a single newline character (xs:string whose length is exactly one.1 to 4 indicates that the output
contains the first, second, third, and fourth columns from the input, in order,
while (1, 5, 4) indicates that the output
contains three columns, taken from the first, fifth, and fourth columns of the input,
in that order. An integer in the sequence is treated as the 1-based
index of the column to include. Any other columns are dropped.
If a particular row includes no field at the specified index,
an empty field is included at the relevant position in the result. If an integer appears
more than once then the result will include duplicated columns.
select-columns is specified.select-columns option.The result of the function is a parsed-csv-structure-record, as
defined in
A dynamic error $csv does not conform to the required grammar.
A dynamic error field-delimiter, row-delimiter, or quote-character
is not a single character.
A dynamic error field-delimiter, row-delimiter, and
quote-character.
The default row delimiter is a single newline character CR and CRLF will already have been normalized to a single
newline.
All fields are returned as xs:string values.
Quoted fields in the input are returned without the quotes.
For more discussion of the returned data, see
Default delimiters, no column headers:
Default delimiters, column headers:
Custom delimiters, no column headers:
Supplied column names:
Filtering columns, with ragged input and header: true()
Filtering columns, with supplied column map
Specifying the number of columns explicitly, with header: false()
Specifying the number of columns with a number and header: true()
New in 4.0
Reads an external resource containing CSV, and returns the results as a record containing information about the names in the header, as well as the data itself.
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The effect of the two-argument function call fn:csv-doc($H, $M)is equivalent to the function composition
fn:unparsed-binary($H) => fn:parse-csv($M).
If $source is the empty sequence, the function returns the empty sequence.
The function may raise any error defined for the
New in 4.0
Parses CSV data supplied as a string, returning the results in the form of a sequence of arrays of strings.
The $value argument is CSV data, as defined in xs:string value. The function parses this string,
after normalizing newlines so that array(xs:string)*; each array represents one row of the CSV input.
If $value is the empty sequence or a zero-length string, the
function returns an empty sequence.
The $options argument can be used to control the way in which the parsing
takes place. The
If the $options argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The entries that may appear in the $options map are as follows:
xs:string whose length is exactly one.xs:string whose length is exactly one.
Defaults to a single newline character (xs:string whose length is exactly one.An empty field is represented by a zero-length string. An empty field is deemed to exist
when a field delimiter immediately follows either another field delimiter, or
a row delimiter, or the start of $value; or when a row delimiter or the
end of $value immediately follows a field delimiter.
A blank row is represented as an empty array (not as an
array containing a single empty field). A blank row is deemed to exist when a
row delimiter immediately follows either another row delimiter or the start of $value,
after trimming of whitespace if the trim-whitespace option is true.
No blank row occurs after the final row delimiter.
If $value is a zero-length string, the CSV is considered to
contain no rows; while if $value consists of a single row delimiter,
it is considered to contain a single blank row. The presence or
absence of a final row delimiter generally has no effect on the result,
except when it appears at the start of the input, in which case it causes a
single blank row to exist.
A dynamic error $csv does not conform to the required grammar.
A dynamic error field-delimiter, row-delimiter, or
quote-character option is not a single character.
A dynamic error field-delimiter, row-delimiter, and
quote-character.
The default row delimiter is a single newline character CR and CRLF will already have been normalized to a single
newline.
All fields are returned as xs:string values.
Quoted fields in the input are returned without the quotes.
The first row is not treated specially.
For more discussion of the returned data, see
Handling trivial input:
Using newline separators:
Quote handling:
Non-default record- and field-delimiters:
Non-default quote character:
Trimming whitespace in fields:
New in 4.0
Parses CSV data supplied as a string, returning the results as an XML document, as described by
The arguments have the same meaning, and are subject to the same constraints, as
the arguments of
If $value is the empty sequence, the function returns the empty sequence.
In other cases, the effect of the function is equivalent to the result of the
following XQuery expression
(where $options is an empty map if the argument is not supplied):
The elements in the returned XML are in the namespace
http://www.w3.org/2005/xpath-functions;
the namespace prefix that is used (or its absence) is
If the function is called twice with the same arguments, it is
The base URI of the element nodes in the result is
A schema is defined for the structure of the returned document: see
The result of the function will always be such that validation against this schema would succeed.
However, it is
See
An empty CSV with default column extraction (false):
An empty CSV with header extraction:
An empty CSV with explicit column names:
With defaults for delimiters and quotes, recognizing headers:
Filtering columns
Ragged rows
Trimming rows to constant width
Specifying a fixed number of columns
New in 4.0
Parses input supplied in the form of a JSON text, returning the results typically in the form of a map or array.
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The first argument is a JSON text as defined in
If $value is the empty sequence, the function returns the empty sequence.
If the input is "null", the result will also be an empty sequence.
If $value is supplied as a binary value, it is converted to a string.
The function detects the encoding using the same rules as the text/xml
and application/xml may be skipped. Otherwise, if $value
is a string, it is processed unchanged.
The $options argument can be used to control the way in which the parsing
takes place. The
The entries that may appear in the $options map are as follows:
JSON-text in escape option is set to truefallback function
as described below; in the absence of a fallback function, it is replaced by
all codepoints in the range
all codepoints that do not represent
the character
\t), or a six-character escape sequence otherwise
(for example \uDEAD). Characters other than these are not escaped in the result, even if they
were escaped in the input.
fallback option if the escape
option is present with the value true.
liberal:true() is specified):
for example \b or \uFFFF or \uDEAD.
By default, the escape sequence is replaced with the Unicode
REPLACEMENT CHARACTER. The function is \x0A).
The string, which results from invoking
null value should be represented.null value.
The default representation of null is an empty sequence, which works
well in cases where setting a property of an object to null has the
same meaning as omitting the property. It works less well in cases where null
is used with some other meaning, because expressions such as the lookup operator
? flatten the result to a single sequence of items,
which means that any entries whose value is an empty sequence effectively disappear.
The property can be set to any XDM value; a suggested value is the xs:QName
value fn:QName("http://www.w3.org/2005/xpath-functions", "null"),
which is recognized by the JSON serialization method as representing the JSON value
null.
xs:double using the XPath casting rules.
Supplying the value xs:decimal#1 will instead convert to xs:decimal
(which potentially retains more precision, but disallows exponential notation), while
supplying a function that casts to (xs:decimal | xs:double) will treat
the value as xs:decimal if there is no exponent, or as xs:double
otherwise. Supplying the value fn:identity#1 causes the value to be retained
unchanged as an xs:untypedAtomic.
If the liberal option is false (the default), then
the supplied number-parser is called if and only if the value conforms
to the JSON grammar for numbers (for example,
a leading plus sign and redundant leading zeroes are not allowed). If the liberal
option is true then it is also called if the value conforms to an
The various structures that can occur in JSON are transformed recursively to XDM values as follows:
A JSON xs:string; the
associated value may be of any type, and is the result of converting the JSON
value by recursive application of these rules. For example, the JSON text
{ "x": 2, "y": 5 } is transformed to the value
{ "x": 2, "y": 5 }.
If duplicate keys are encountered in a JSON duplicates option defined above.
The order of entries is retained.
A JSON [ "a", "b", null ] is transformed (by default) to the value
[ "a", "b", () ].
A JSON xs:string value.
escape and fallback options, as described in the table above.
A JSON number-parser option; by default it isxs:double value using
the rules for casting from xs:string to xs:double.
The JSON true and false are
converted to the corresponding xs:boolean values.
The JSON value null option, which defaults to an
empty sequence.
A dynamic error $value does not conform to the JSON grammar, unless the option
"liberal":true() is present and the processor chooses to accept the deviation.
A dynamic error "duplicates": "reject" is present and the value of
$value contains a JSON object with duplicate keys.
A dynamic error $options
map contains an entry whose key is defined in this specification and whose value is not valid for that key,
or if it contains an entry with the key fallback when the option "escape":true()
is also present.
The result of the function will be an instance of one of the following types. An
instance of test (or in XQuery, typeswitch) can be used to
distinguish them:
map(xs:string, item()?) for a JSON object
array(item()?) for a JSON array
xs:string for a JSON string
xs:double for a JSON number
xs:boolean for a JSON boolean
empty-sequence() for a JSON null (or for empty input)
If the input starts with a byte order mark, this function ignores it. The byte order mark may have been added to the data stream in order to facilitate decoding of an octet stream to a character string, but since this function takes a character string as input, the byte order mark serves no useful purpose.
The possibility of the input containing characters that are not valid in XML (for example, unpaired surrogates)
arises only when such characters are expressed using JSON escape sequences. This is because the input to the function
is an instance of xs:string, which by definition (see
The serializer provides an option to output data in unparsed-text-lines($uri) => parse-json().
The rules regarding use of non-XML characters in JSON texts have been relaxed.
An option is provided to control how the JSON null value should be handled.
An option is provided to control how JSON numbers should be formatted.
The default for the escape option has been changed to false. The 3.1
specification gave the default value as true, but this appears to have been an error,
since it was inconsistent with examples given in the specification and with tests in the test suite.
The order of entries in maps is retained.
Support for binary input has been added.
Reads an external resource containing JSON, and returns the result of parsing the resource as JSON.
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The effect of the two-argument function call fn:json-doc($H, $M)is equivalent to the function composition
fn:unparsed-binary($H) => fn:parse-json($M).
If $source is the empty sequence, the function returns the empty sequence.
The function may raise any error defined for the
An initial byte order mark is dropped, as with the
If the input cannot be decoded (that is, converted into a sequence of Unicode codepoints, which may or may not represent characters),
then a dynamic error occurs as with the
If the input can be decoded,
then the possibility still arises that the resulting sequence of codepoints includes codepoints that are
not \uFFFF),
and the JSON escape sequence is then passed to the fallback function specified in the $options argument, which in turn
defaults to a function that returns the Unicode REPLACEMENT CHARACTER (xFFFD).
The function text/xml
and application/xml may be skipped.
Additional options are available, as defined by
It is no longer automatically an error if the input
contains a codepoint that is not valid in XML. Instead, the codepoint
must be a
Returns the number of members in the supplied array.
The function returns the number of members in the array.
Note that because an array is an item, the 1.
Returns true if the supplied array contains no members.
The function returns true if and only if $array contains no members.
The test for emptiness is not the same as the test used by the
xsl:on-empty instruction in XSLT. For example, an array
is not considered empty by this function if it contains a single
member that is itself an empty array.
New in 4.0
Returns the value at the specified position in the supplied array (counting from 1).
Informally, the function returns the member at a specified position in the array.
If $position is out of bounds (that is, if
it is less than one or greater than array:size($array)), then the effect
depends on the number of arguments:
When there are two arguments, an error is raised (
When there are three arguments, the value of $default is returned.
In the absence of a $default argument,
a dynamic error occurs $position is not in the range 1 to
array:size($array) inclusive.
A third argument is added, allowing user control of how index-out-of-bounds conditions should be handled.
Returns an array containing all the members of a supplied array, except for one member which is replaced with a new value.
Informally, the result is an array whose size is array:size($array), in which all
members in positions other than $position are the same as the members in the corresponding position
of $array, and the member in position $position is $member.
A dynamic error occurs $position is not in the range 1 to
array:size($array) inclusive.
This error will always occur if $array is empty.
Returns an array containing all the members of a supplied array, plus one additional member at the end.
Informally, the result is an array whose size is array:size($array) + 1, in which all
members in positions 1 to array:size($array) are the same as the members in the corresponding position
of $array, and the member in position array:size($array) + 1 is $member.
Concatenates the contents of several arrays into a single array, with an optional separator between adjacent members.
Informally, the function concatenates the members of several arrays into a single array. If a separator is supplied, its members are inserted before the members of the second and the following arrays.
Optional $separator added.
Returns an array containing all members from a supplied array starting at a supplied position, up to a specified length.
Except in error cases,
the two-argument version of the function returns the same result as the three-argument
version when called with $length equal to the value of
array:size($array) - $start + 1.
Setting the third argument to the empty sequence has the same effect as omitting the argument.
A dynamic error is raised $start is less than one
array:size($array) + 1
For the three-argument version of the function:
A dynamic error is raised $length is less than zero.
A dynamic error is raised $start + $length is greater than array:size($array) + 1.
The value of $start can be equal to array:size($array) + 1 provided that $length
is either equal to zero or omitted. In this case the result will be an empty array.
Supplying an empty sequence as the value of an optional argument is equivalent to omitting the argument.
Returns a sequence of positive integers giving the positions within the array
$array of members that are equal to $target.
Informally, all members of $array are compared with $target.
An array member is compared to the target value using the rules of the
The collation used by this function is determined according to the rules in
The first member in an array is at position 1, not position 0.
The result sequence is in ascending numeric order.
If $array is the empty array, or if no member in
$array matches $target, then the function returns the empty
sequence.
New in 4.0
Returns the positions in an input array of members that match a supplied predicate.
The result of the function is a sequence of integers, in monotonic ascending order, representing
the 1-based positions in the input array of those members for which the supplied predicate function
returns true. A return value of () is treated as false.
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Returns an array containing selected members of a supplied input array based on their position.
Informally, the array is converted to a sequence, the function
Note that unlike other operations on arrays, there are no out-of-bounds errors for inappropriate
values of $start, $end, or $step.
New in 4.0
Returns an array containing all the members of the supplied array, except for the members at specified positions.
Informally, the function returns an array of size array:size($array) - fn:count(fn:distinct-values($positions))$array
except the members whose position (counting from 1) is present in the sequence $positions.
The order of the remaining members is preserved.
A dynamic error is raised $positions is not in the range 1 to
array:size($array) inclusive. By implication, an error occurs if $array is empty, unless $positions
is also empty.
Returns an array containing all the members of the supplied array, with one additional member at a specified position.
Informally, the function returns an array of size array:size($array) + 1
containing all members from $array
whose position is less than $position, then a new member given by $member, and
then all members from $array whose position is greater than or equal to $position.
Positions are counted from 1.
A dynamic error occurs $position is not in the range 1 to
array:size($array) + 1 inclusive.
Setting $position to 1 has the effect of prepending the new member at the start of the array. Setting $position
to the value array:size($array) + 1 delivers the same result as array:append($array, $member).
Returns the first member of an array, that is $array(1).
The function returns first member of $array.
A dynamic error occurs $array is empty.
Returns the last member of an array.
The function returns the last member of $array.
A dynamic error occurs $array is empty.
New in 4.0
Returns an array containing all members except the first from a supplied array.
The function returns an array containing all members of the supplied array except the first.
A dynamic error occurs $array is empty.
If the supplied array contains exactly one member, the result will be an empty array.
Returns an array containing all members except the last from a supplied array.
The function returns an array containing all members of the supplied array except the last.
A dynamic error occurs $array is empty.
If the supplied array contains exactly one member, the result will be an empty array.
New in 4.0
Returns an array containing all the members of a supplied array, but in reverse order.
The function returns an array with the same number of members
as $array, but in reverse order.
Returns an array whose size is the same as array:size($array), in which
each member is computed by applying $action to the corresponding member of
$array.
Informally, the function returns an array whose members are obtained by applying
the supplied $action function to each member of the input array in turn.
The $action function is called with two arguments: the first is the
array member (which in general is an arbitrary sequence), and the second is the 1-based
integer position.
The $action callback function now accepts an optional position argument.
Returns an array containing those members of the $array for which
$predicate returns true. A return value of ()
is treated as false.
Informally, the function returns an array containing those members of the input array that satisfy the supplied predicate.
As a consequence of the function signature and the function calling rules, a type error occurs if the supplied
function $function returns anything other than a single xs:boolean item
or an empty sequence; there is no conversion to an effective boolean value.
The $predicate callback function now accepts an optional position argument.
The $predicate callback function may return an empty sequence (meaning false).
Evaluates the supplied function cumulatively on successive members of the supplied array.
The function is defined formally below, in terms of the equivalent
If the supplied array is empty, the function returns $init.
If the supplied array contains a single member $m, the function returns $init => $action($m).
If the supplied array contains two members $m and $n, the function returns
$init => $action($m) => $action($n); and similarly for an input array with more than two members.
true().true().Evaluates the supplied function cumulatively on successive values of the supplied array.
The function is defined formally below, in terms of the equivalent
If the supplied array is empty, the function returns $init.
If the supplied array contains a single member $m, the function returns $action($m, $init).
If the supplied array contains two members $m and $n, the function returns
$action($m, $action($n, $init)); and similarly for an input array with more than two members.
true().true().Returns an array obtained by evaluating the supplied function once for each pair of members at the same position in the two supplied arrays.
Informally, the function applies $action to each pair of values in corresponding positions
within $array1 and $array2, ignoring any excess values if one array is longer
than the other. The results are then assembed into a new array whose size is equal to the shorter of the
two input arrays.
If the arrays have different size, excess members in the longer array are ignored.
The $action callback function now accepts an optional position argument.
Returns an array obtained by evaluating the supplied function once for each item in the input sequence.
If the function is called with one argument, the effect is the same as calling the two-argument
function with fn:identity#1 as the second argument.
Informally, array:build#2 applies the supplied function to each item
in the input sequence, and the resulting sequence becomes one member of the returned array.
The single-argument function array:build($input) is equivalent to the XPath
expression array { $input }, but it is useful to have this available as a function.
The two-argument form facilitates the construction of arrays whose members are arbitrary sequences.
New in 4.0
Delivers the contents of an array as a sequence of
The members of the array are delivered as a sequence of $S: specifically
it is a map comprising a single entry whose key is the xs:string value
"value" and whose corresponding value is $S. The content encapsulated
by a value record $V can be obtained using the expression $V?value.
This function is the inverse of
New in 4.0
Delivers the contents of an array as a sequence of single-member arrays.
The members of the array are delivered as a sequence of
$array.
The function call array:split($array) produces the same result as the
expression for member $m in $array return [ $m ].
This function is the inverse of
New in 4.0
Constructs an array from the contents of a sequence of
The input items must be $S: specifically
it is a map comprising a single entry whose key is the xs:string value
"value" and whose corresponding value is $S. The content encapsulated
by a value record $V can be obtained using the expression $V?value.
This function is the inverse of
New in 4.0
Sorts a supplied array, based on the value of a sort key supplied as a function.
This function is retained for compatibility from version 3.1 of this specification. Version 4.0
introduces a more powerful functions,
The function call array:sort($array, $collation, $key) is defined to have the same effect as the
call array:sort-by($array, { 'key': $key, 'collation': $collation, 'order': 'ascending'}).
See
The result of the function is a sequence that contains all the items from $input,
typically in a different order, the order being defined by the supplied sort key definitions.
If the set of computed sort keys contains values that are not comparable using the lt operator then the sort
operation will fail with a type error (
Sorts a supplied array, based on the value of a number of sort keys supplied as functions.
The result of the function is an array that contains the same members as $array,
typically in a different order, the order being defined by the supplied
A
key: A fn:data#1,
which atomizes the value of the array member.
collation: A xs:string or xs:untypedAtomic. If no collation is supplied, the default
collation from the static context is used.
When comparing values of types other than xs:string or xs:untypedAtomic,
the collation is ignored (but an error
order: An "ascending" or
"descending". The default is "ascending".
The number of sort key definitions is determined by the number of records supplied
in the $keys argument. If the argument is absent or empty, the default is
a single sort key definition using the function data#1, using the default collation
from the static context, and with order ascending.
The result of the array:sort-by function is obtained as follows:
The result array contains the same members as $array,
but generally in a different order.
The sort key definitions are established as described above.
The sort key definitions are in major-to-minor order. That is, the position of two
values $A and $B in the result sequence is determined first by the
relative magnitude of their
primary sort key values, which are computed by evaluating the
When a pair of corresponding sort key values of $A and $B are
found to be not equal,
then $A precedes $B in the result sequence
if both the following conditions are true, or if both conditions are false:
The sort key value for $A is less than the sort key value for $B,
as defined below.
The "ascending".
If all the sort key values for $A and $B are pairwise equal, then
$A precedes $B in the result sequence if and only if
$A precedes $B in the input sequence.
That is, the sort is
Each sort key value for a given array member is obtained by applying the sort key
function of the corresponding sort key definition to that member. The result
of this function is in the general case a sequence of atomic items.
Two sort key values $a and $b are compared as follows:
Let $C be the collation in the corresponding sort key definition.
Let $REL be the result of evaluating op:lexicographic-compare($key($A), $key($B), $C)
where op:lexicographic-compare($a, $b, $C) is defined as follows:
Here op:simple-compare($k1, $k2) is defined as follows:
This raises an error if two keys are not comparable, for example
if one is a string and the other is a number, or if both belong to a non-ordered
type such as xs:QName.
If $REL is zero, then the two sort key values are deemed
equal; if $REL is -1 then $a is deemed less than
$b, and if $REL is +1 then $a is deemed greater than
$b
If the set of computed sort keys contains values that are not comparable using the lt operator then the sort
operation will fail with a type error (
The function is a generalization of the
If the sort key for an item evaluates to an empty sequence, the effect of the rules is that this item
precedes any value for which the key is non-empty. This is equivalent to the effect of the XQuery option
empty least. The effect of the option empty greatest can be achieved by adding an
extra sort key definition with {'key': fn{empty(K(.)}}: when comparing boolean sort keys,
false precedes true.
New in 4.0.
Replaces any array appearing in a supplied sequence with the members of the array, recursively.
The function processes the items in the supplied sequence $input as follows:
An item that is an array is replaced by its members, retaining order.
Any other item is retained unchanged.
The process is then repeated so long as the sequence contains an array among its items.
The argument to the function will often be a single array item, but this is not essential.
Unlike atomization, this function retains any nodes contained in the array.
Returns the sequence concatenation of the members of an array.
The function returns the $array, retaining order.
Unlike
If $A is a single array item, then array:items($A)
returns the same result as $A?*.
New in 4.0
Provides access to the public functions and global variables of a dynamically loaded XQuery library module.
The function loads an implementation-defined set of modules having the target namespace $module-uri.
If the second argument is omitted or an empty sequence, the result is the same as
calling the two-argument form with an empty map as the value of the $options
argument.
The $options argument can be used to control the way in which the function operates.
The
xs:string values) which may be used or ignored in an
location-hints option is ignored. The static base URI of the dynamically loaded
module is the same as the The result of the function is a map
R with two entries, as defined in
The static and dynamic context of the library module are established according to the rules in
It is
The library module that is loaded may import other modules using an import module declaration. The result of
options map supplied in the function call
The library module that is loaded may import schema declarations using an import schema declaration. It is
Where nodes are passed to or from the dynamically loaded module, for example as an argument or result of a function,
they
If $module-uri is a zero length string, a dynamic error is raised
If the implementation is not able to find a library module with the specified target namespace,
an error is raised
If a static error (including a statically detected type error) is encountered when processing the library module,
a dynamic error is raised
If a value is supplied for the initial context item or for an external variable and the value does not conform to the required
type declared in the dynamically loaded module, a dynamic error is raised
If no suitable XQuery processor is available, a dynamic error is raised
No XQuery processor is available;
Use of the function has been disabled;
No XQuery processor supporting the requested version of XQuery is available;
No XQuery processor supporting the optional Module Feature is available.
If a dynamic error (including a dynamically detected type error) is encountered when processing the module
(for example, when evaluating its global variables), the dynamic error is returned
If a function declaration F in the loaded module declares (say) four parameters of which one is optional,
its arity range will be from 3 to 4, so the result will include two function items corresponding to F#3
and F#4. In the lower-arity function item, F#3, the fourth parameter will take its
default value. If the expression that initializes the default value is context sensitive, the static and dynamic
context for its evaluation are the static and dynamic contexts of the
As with all other functions in this specification, conformance requirements depend on the host language. For example, a host language might specify that provision of this function is optional, or that it is excluded entirely, or that implementations are required to support XQuery modules using a specified version of XQuery.
Even where support for this function is mandatory, it is
The load-xquery-module function does not modify the static or dynamic context.
Functions and variables from the loaded module become available within the result returned by the function, but they
are not added to the static or dynamic context of the caller. This means, for example, that function-lookup
will not locate functions from the loaded module.
It has been clarified that loading a module has no effect on the static or dynamic context of the caller.
The return type is now specified more precisely.
A new option is provided to allow the content of the loaded module to be supplied as a string.
Invokes a transformation using a dynamically loaded XSLT stylesheet.
This function loads an XSLT stylesheet and invokes it to perform a transformation.
The inputs to the transformation are supplied in the form of a map.
The
The function first identifies the
If the xslt-version
option is present, the requested XSLT version is the value of that option.
Otherwise, the requested XSLT version
is the value of the [xsl:]version attribute of the outermost element in the supplied stylesheet or package.
The function then attempts to locate an XSLT processor that implements the requested XSLT version.
If a processor that implements the requested XSLT version is available, then it is used.
Otherwise, if a processor that implements a version later than the requested version is available, then it is used.
Otherwise, the function fails indicating that no suitable XSLT processor is available.
The phrase
If more than one XSLT processor is available under the above rules, then the one that is chosen may be selected according to the availability of requested features: see below.
Once an XSLT processor has been selected that implements a given version of XSLT, the processor
follows the rules of that version of the XSLT specification. This includes any decision to operate in backwards or forwards
compatibility mode. For example, if an XSLT 2.0 processor is selected, and the stylesheet specifies version="1.0",
then the processor will operate in backwards compatibility mode; if the same processor is selected and the stylesheet
specifies version="3.0", the processor will operate in forwards compatibility mode.
The combinations of options that are relevant to each version of XSLT, other than xslt-version
itself, are listed below. This is followed by a table giving the meaning of each option.
For invocation of an XSLT 1.0 processor (see
The stylesheet, provided by supplying exactly one of the following:
stylesheet-location
stylesheet-node
stylesheet-text
The source tree, provided as the value of the source-node option.
Zero or more of the following additional options:
stylesheet-base-uri
stylesheet-params (defaults to an empty map)initial-mode (defaults to the stylesheet’s default mode)delivery-format (defaults to document)serialization-params (defaults to an empty map)enable-messages (default is implementation-defined)requested-properties (default is an empty map)vendor-options (defaults to an empty map)cache (default is implementation-defined)For invocation of an XSLT 2.0 processor (see
The stylesheet, provided by supplying exactly one of the following:
stylesheet-location
stylesheet-node
stylesheet-text
Invocation details, as exactly one of the following:
For apply-templates invocation, all of the following:
source-node
Optionally, initial-mode (defaults to the stylesheet’s default mode)
For call-template invocation, all of the following:
initial-template
Optionally, source-node
Zero or more of the following additional options:
stylesheet-base-uri
stylesheet-params (defaults to an empty map)base-output-uri (defaults to absent)delivery-format (defaults to document)serialization-params (defaults to an empty map)enable-messages (default is implementation-defined)enable-trace (default is implementation-defined)requested-properties (default is an empty map)vendor-options (defaults to an empty map)cache (default is implementation-defined)For invocation of an XSLT 3.0 processor (see
The stylesheet, provided either by supplying exactly one of the following:
stylesheet-location
stylesheet-node
stylesheet-text
Or by supplying exactly one of the following:
package-location
package-node
package-text
package-name plus optionally package-versionInvocation details, as exactly one of the following combinations:
For apply-templates invocation, all of the following:
Exactly one of source-node or initial-match-selection
Optionally, initial-mode
Optionally, template-params
Optionally, tunnel-params
For call-template invocation using an explicit template name, all of the following:
initial-template
Optionally, template-params
Optionally, tunnel-params
Optionally, source-node
For call-template invocation using the defaulted template name xsl:initial-template, all of the following:
Optionally, template-params
Optionally, tunnel-params
If the source-node option is present and initial-template is absent,
then apply-templates invocation will be used. To use call-template invocation on the template
named xsl:initial-template while also supplying a context item for use when evaluating
global variables, either (a) supply the context item using the global-context-item option,
or (b) supply source-node, and set the initial-template option explicitly to the
QName xsl:initial-template
For call-function invocation, all of the following:
initial-function
function-params
The invocation method can be determined as the first of the following which applies:
If initial-function is present, then call-function invocation.
If initial-template is present, then call-template invocation.
If source-node or initial-match-selection
is present, then apply-templates invocation.
Otherwise, call-template invocation using
the default entry point xsl:initial-template.
Zero or more of the following additional options:
stylesheet-base-uri
static-params (defaults to an empty map)stylesheet-params (defaults to an empty map)global-context-item (defaults to absent)base-output-uri (defaults to absent)delivery-format
serialization-params (defaults to an empty map)enable-assertions (default is false)enable-messages (default is implementation-defined)enable-trace (default is implementation-defined)requested-properties (default is an empty map)vendor-options (defaults to an empty map)cache (default is implementation-defined)The meanings of each option are defined in the table below.
fn:transform
function call. true indicates an expectation that the same
stylesheet is likely to be used for more than one transformation; the value
false indicates an expectation that the stylesheet will be used once
only.xsl:result-document.xsl:output or xsl:result-document element specifies
build-tree="no" (applies to XSLT 3.0 only), then the default
is raw.xsl:assert instructions in the stylesheet
are to be evaluated.xsl:message instructions in the stylesheet
are to be evaluated. The destination and formatting of any such messages is
implementation-defined.source-nodefunction-params.source-nodeIf the implementation provides a way of writing or invoking functions
with side-effects, this post-processing function might be used to save
a copy of the result document to persistent storage. For example, if the
implementation provides access to the EXPath File library file:write function. Similar mechanisms might be used to issue
an HTTP POST request that posts the result to an HTTP server, or to send
the document to an email recipient. The semantics of calling functions
with side-effects are entirely
If the primary purpose of the post-processing function is achieved by
means of such side-effects, and if the actual results are not needed by
the caller of the
Calls to
system-property function; the values in the map are the requested
settings of the corresponding property. The boolean values true() and
false() are equivalent to the string values yes and
no. As a special case, setting a value for xsl:version has
no effect, because of the potential for conflict with other options. For example: Setting xsl:product-name to a particular value requests a
particular XSLT software product.
Setting xsl:product-version requests a specific version of
that product.
Setting xsl:is-schema-aware to true() requests a
schema-aware processor.
Setting xsl:xsd-version to "1.1" requests a
processor that supports XML Schema version 1.1.
xsl:supports-dynamic-evaluation
to false() is interpreted as an explicit request for a processor in which
the value of the property is false. The effect if the requests cannot be precisely met
is implementation-defined. In some cases it may be appropriate to ignore the request or
to provide an alternative (for example, a later version of the product than the one
requested); in other cases it may be more appropriate to raise an error When a parameter is supplied, the corresponding value overrides or augments
the value specified in the unnamed xsl:output declaration (or
its default), following the same rules as when one xsl:output
declaration overrides another with lower import precedence.
When a parameter is supplied and the corresponding value is an empty
sequence (for example, { "standalone": () }), any value
specified in the unnamed xsl:output declaration is overridden
by the default value.
When a parameter is not supplied in serialization-params (that
is, when the key is absent) the value that applies is the value appearing in
the unnamed xsl:output declaration, or its default.
source-node is supplied then the
global-context-item (the context item for evaluating global variables)
is the root of the tree containing the supplied node. In addition, for apply-templates
invocation, the source-node acts as the
initial-match-selection, that is, stylesheet execution starts by
applying templates to this node.stylesheet-node or
stylesheet-location) then it is fn:transform function call.fn:transform function call.
The value also acts as the default for stylesheet-base-uri.[xsl:]version attribute at the outermost level of the
stylesheet.The result of the transformation is returned as a map. There is one entry in the map for the principal result document, and one
for each secondary result document. The key is a URI in the form of an xs:string value. The key for the principal
result document is the base output URI if specified, or the string "output" otherwise. The key for secondary
result documents is the URI of the document, as an absolute URI. The associated value in each entry depends on the requested
delivery format. If the delivery format is document, the value is a document node. If the delivery format is
serialized, the value is a string containing the serialized result.
Where nodes are passed to or from the transformation, for example as the value of a stylesheet parameter or the result of a function,
they
It is
The function is xsl:source-document change between
one invocation and the next.
A dynamic error is raised
No XSLT processor is available;
No XSLT processor supporting the requested version of XSLT is available;
The XSLT processor API does not support some requested feature (for example, the ability to supply tunnel parameters externally);
A dynamic error is raised
If a static or dynamic error is reported by the XSLT processor, this function fails with a dynamic error, retaining the XSLT error code.
A dynamic error is raised
XSLT 1.0 does not define any error codes, so this is the likely outcome with an XSLT 1.0 processor. XSLT 2.0 and 3.0 do
define error codes, but some APIs do not expose them. If multiple errors are signaled by the transformation (which is most likely
to happen with static errors) then the error code should where possible be that of one of these errors, chosen arbitrarily; the processor
may make details of additional errors available to the application in an
A dynamic error is raised
A dynamic error is raised
Recursive use of the
As with all other functions in this specification, conformance requirements depend on the host language.
For example, a host language might specify that provision of this function is optional, or that it is excluded entirely,
or that implementations are required to support a particular set of values for the xslt-version
parameter.
Even where support for this function is mandatory, it is
The following example loads a stylesheet from the location render.xsl,
applies it to a document loaded from test.xml, and uses an XPath expression
to examine the result:
Returns a random number generator, which can be used to generate sequences of random numbers.
The function returns a random number generator. A random number generator is represented as a value of type
random-number-generator-record, defined in
Calling the
Calling the $seed
is equivalent to calling the single-argument form of the function with an implementation-dependent seed.
If a $seed is supplied, it may be an atomic item of any type.
Both forms of the function are
The value of the number entry xs:double
values are equally likely to be chosen
The function returned in the permute entry
The map returned by the
It is not meaningful to ask whether the functions returned in the next and permute
functions resulting from two separate calls with the same seed are “the same function”, but the functions must be equivalent in the sense
that calling them produces the same sequence of random numbers.
The repeatability of the results of function calls in different execution scopes is outside the scope of this
specification. It is fn:current-dateTime() as a seed.)
The specification does not place strong conformance requirements on the actual randomness of the result; this is left to the implementation. It is desirable, for example, when generating a sequence of random numbers that the sequence should not get into a repeating loop; but the specification does not attempt to dictate this.
The following example returns a random permutation of the integers in the range
1 to 100:
random-number-generator()?permute(1 to 100)
The following example returns a 10% sample of the items in an input sequence $seq, chosen at random:
random-number-generator()?permute($seq)[1 to (count($seq) idiv 10)]
The following XQuery code produces a random sequence of 200 xs:double
values in the range zero to one:
An equivalent result can be achieved with
The 3.1 specification suggested that every value in the result range should have the same chance
of being chosen. This has been corrected to say that the distribution should be arithmetically uniform
(because there are as many xs:double values between 0.01 and 0.1 as there are between
0.1 and 1.0).
Returns true if every item in the input sequence matches a supplied predicate.
The function returns true if $input is empty, or if $predicate($item, $pos)
returns true for every item $item at position $pos (1-based) in $input.
An error is raised if the $predicate function raises an error. In particular,
when the default predicate fn:boolean#1 is used, an error is raised if an
item has no effective boolean value.
If the second argument is omitted or an empty sequence, the predicate defaults
to fn:boolean#1, which takes the effective boolean value of each item.
It is possible for the supplied $predicate to be a function whose arity is less than two.
The coercion rules mean that the additional parameters are effectively ignored. Frequently a predicate
function will only consider the item itself, and disregard its position in the sequence.
The predicate is required to return either true, false, or an empty
sequence (which is treated as false). A predicate such as fn { self::h1 }
results in a type error because it returns a node, not a boolean.
The implementation false; it is not required to evaluate the predicate for every item,
nor is it required to examine items sequentially from left to right.
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Returns a string containing a particular character or glyph.
The function returns a string, generally containing a single $value.
The supplied value of $value must be one of the following:
A Unicode codepoint, supplied as an integer. For example fn:char(9)
returns the tab character.
An HTML5 character reference name (often referred to as an entity name) as defined
at fn:char("pi") represents the character
fn:char("nbsp") returns
A processor
In the event that the HTML5 character reference name identifies a string comprising multiple codepoints, that string is returned.
[TODO: add a proper bibliographic reference.]
A backslash-escape sequence from the set \n (\r (\t (
The result must consist of
fn:char(0xDEAD) is invalid because it is in the surrogate range.
The function fails with a dynamic error $value is not a valid
representation of a
Although all Unicode characters can appear in string literals (the delimiting quotation marks can be escaped by doubling them), some characters are not visually distinctive, so representing them by name may make code more readable. In addition, there may be contexts where it is necessary or prudent to write XPath expressions using ASCII characters only, for example where an expression is used in the query part of a URI.
A few HTML5 character reference names identify glyphs whose Unicode
representation uses multiple codepoints. For example, the name
NotEqualTilde refers to the glyph ≂̸ which is expressed
using the two codepoints
New in 4.0
Splits the supplied string into a sequence of single-character strings.
The function returns a sequence of strings, each string having length 1, containing
the corresponding $value.
If $value is a zero-length string or the empty sequence, the function returns
the empty sequence.
New in 4.0
Splits the supplied string into a sequence of single-grapheme strings.
The function returns a sequence of strings. Each string in the sequence contains one or
more
If $value is a zero-length string or the empty sequence, the function returns
the empty sequence.
The resultant sequence of strings are extended graphemes, not legacy graphemes (see
New in 4.0
Returns those items from a supplied sequence that have the highest value of a sort key, where the sort key can be computed using a caller-supplied function.
The second argument, $collation, defaults to ().
Supplying an empty
sequence as $collation is equivalent to supplying
fn:default-collation(). For more
information on collations see
The third argument defaults to the function data#1.
Let $modified-key be the function:
That is, the supplied function for computing key values is wrapped in a function that
converts any xs:untypedAtomic values in its result to xs:double. This makes
the function consistent with the behavior of
The result of the function is obtained as follows:
If the input is an empty sequence, the result is an empty sequence.
The input sequence is sorted, by applying the function
fn:sort($input, $collation, $modified-key).
Let $C be the selected collation, or the default collation where applicable.
Let $B be the last item in the sorted sequence.
The function returns those items $A from the input sequence such that
(fn:deep-equal($key($A), $key($B), $C), retaining their order.
If the set of computed keys contains xs:untypedAtomic values that are not
castable to xs:double then the
operation will fail with a dynamic error (
If the set of computed keys contains values that are not comparable using
the lt operator then the sort
operation will fail with a type error (
To find employees having the highest salary:
New in 4.0
Returns the positions in an input sequence of items that match a supplied predicate.
The result of the function is a sequence of integers, in monotonic ascending order, representing
the 1-based positions in the input sequence of those items for which the supplied predicate function
returns true. A return value of () from the predicate function
is treated as false.
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Returns true if the argument is the xs:float or xs:double value NaN.
The function returns true if the argument is the xs:float or xs:double value NaN;
otherwise it returns false.
New in 4.0
Returns items from the input sequence prior to the first one that fails to match a supplied predicate.
The function returns all items in the sequence prior to the first one where the result of
calling the supplied $predicate function, with the current item and its position
as arguments, returns the value false or ().
If every item in the sequence satisfies the predicate, then $input is returned
in its entirety.
There is no analogous drop-while or skip-while function,
as found in some functional programming languages. The effect of
drop-while($input, $predicate) can be achieved by calling
fn:subsequence-where($input, fn { not($predicate(.)) }).
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Returns those items from a supplied sequence that have the lowest value of a sort key, where the sort key can be computed using a caller-supplied function.
The second argument, $collation, defaults to ().
Supplying an empty
sequence as $collation is equivalent to supplying
fn:default-collation(). For more
information on collations see
The third argument defaults to the function data#1.
Let $modified-key be the function:
That is, the supplied function for computing key values is wrapped in a function that
converts any xs:untypedAtomic values in its result to xs:double. This makes
the function consistent with the behavior of
The result of the function is obtained as follows:
If the input is an empty sequence, the result is an empty sequence.
The input sequence is sorted, by applying the function
fn:sort($input, $collation, $modified-key).
Let $C be the selected collation, or the default collation where applicable.
Let $B be the first item in the sorted sequence.
The function returns those items $A from the input sequence such that
(fn:deep-equal($key($A), $key($B), $C), retaining their order.
If the set of computed keys contains xs:untypedAtomic values that are not
castable to xs:double then the
operation will fail with a dynamic error (
If the set of computed keys contains values that are not comparable using
the lt operator then the sort
operation will fail with a type error (
To find employees having the lowest salary:
New in 4.0
Returns true if at least one item in the input sequence matches a supplied predicate.
The function returns true if (and only if) there is an item $item at position $pos
in the input sequence such that $predicate($item, $pos) returns true.
An error is raised if the $predicate function raises an error. In particular,
when the default predicate fn:boolean#1 is used, an error is raised if an
item has no effective boolean value.
If the second argument is omitted or an empty sequence, the predicate defaults
to fn:boolean#1, which takes the effective boolean value of each item.
It is possible for the supplied $predicate to be a function whose arity is less than two.
The coercion rules mean that the additional parameters are effectively ignored. Frequently a predicate
function will only consider the item itself, and disregard its position in the sequence.
The predicate is required to return either true, false, or an empty
sequence (which is treated as false). A predicate such as fn { self::h1 }
results in a type error because it returns a node, not a boolean.
The implementation true; it is not required to evaluate the predicate for every item,
nor is it required to examine items sequentially from left to right.
New in 4.0
The $predicate callback function may return an empty sequence (meaning false).
Returns true if all items in a supplied sequence (after atomization) are equal.
Omitting the second argument, $collation, is equivalent to supplying
fn:default-collation(). For more
information on collations see
The result of the function fn:all-equal($values, $collation) is true if and only if the result
of fn:count(fn:distinct-values($values, $collation)) le 1 is true (that is, if the sequence
is empty, or if all the items in the sequence are equal under the rules of the
The expression fn:all-equal(//p/@class) returns true if all
p elements have the same value for @class.
The expression fn:all-equal(* ! fn:node-name()) returns true if all
element children of the context node have the same name.
New in 4.0. Originally proposed under the name fn:uniform
Returns true if no two items in a supplied sequence are equal.
Omitting the second argument, $collation, is equivalent to supplying
fn:default-collation(). For more
information on collations see
The result of the function fn:all-different($values, $collation) is true if and only if the result
of fn:count(fn:distinct-values($values, $collation)) eq fn:count($values) is true
(that is, if the sequence
is empty, or if all the items in the sequence are distinct under the rules of the
The expression fn:all-different(//employee/@ssn) is true if no two employees have the same value for their
@ssn attribute.
The expression fn:all-different(* ! fn:node-name()) returns true if all
element children of the context node have distinct names.
New in 4.0. Originally proposed under the name fn:unique
Parses the URI provided and returns a map of its parts.
If $value is an empty sequence, the result is an empty sequence.
The function parses the $value provided,
returning a map containing its constituent parts: scheme,
authority components, path, etc.
In addition to parsing URIs as defined by
The following options are available:
file: scheme.)This function is described as a series of transformations
over the input string to identify the parts of a URI that are
present. Some portions of the URI are identified by matching
with a regular expression. This approach is designed to make
the description clear and unambiguous; it is not implementation
advice. Comparison of
Processing begins with a $value. If the \), replace them with forward
slashes (/).
Strip off the fragment identifier and any query:
If the ^(.*?)#(.*)$, the
If the ^(.*?)\?(.*)$,
the
Attempt to identify the scheme:
If the ^([a-zA-Z][A-Za-z0-9\+\-\.]+):(.*)$:
the
the
Otherwise, the
If the
If file:
If the ^/*([a-zA-Z][:|].*)$:
the file and
the / followed
by the first match group with the
second character changed to :, if necessary.
Otherwise, if true:
the file and
the
Finally, if neither of the preceding cases apply:
the
the
Now that the scheme, if there is one, has been identified, determine if the URI is hierarchical:
If the true if / and
false otherwise.
If the URI is not
Identify the remaining components according to the scheme and whether or not the URI is hierarchical.
If the scheme is file:
The
If ^/*(//[^/].*)$: then
If the ^//*[A-Za-z]:/ then
all but one leading slash is removed from
Otherwise, the
If the scheme is hierarchical:
If the ^//([^/]+)$, the
If the ^//([^/]*)(/.*)$, the
Otherwise,
the
If the scheme is not hierarchical:
The
If the ^(([^@]*)@)(.*)(:([^:]*))?$,
then the allow-deprecated-features option is true.
When parsing the example.com), an IPv4 address (e.g., 127.0.0.1),
an IPv6 (or IPvFuture) address (e.g., [::1]), or an error
if there is an open square bracket ([) not matched by a
close square bracket (]). In a properly
constructed RFC 3986 URI, the only place where square
brackets may occur is around the IPv6/IPvFuture IP address.
If the ^(([^@]*)@)?(\[[^\]]*\])(:([^:]*))?$,
then the
If the ^(([^@]*)@)?\[.*$
then
If the ^(([^@]*)@)?([^:]+)(:([^:]*))?$,
then the
the
This function does not attempt to decode the components of the
Similar care must be taken to match the port because an IPv6/IPvFuture address may contain a colon.
If the ^(([^@]*)@)?(\[[^\]]*\])(:([^:]*))?$,
then the
Otherwise, if the ^(([^@]*)@)?([^:]+)(:([^:]*))?$,
then the
Otherwise, the
If the omit-default-ports option is true, the port
is discarded and set to the empty sequence if the port number is the same
as the default port for the given scheme. Implementations http (80), https (443),
ftp (21), and ssh (22). Exactly which ports are
recognized
is
If the
A / (solidus) and applying
The
Consider /path%2Fsegment. An application may want to decode that,
using /path/segment in a database query, for example. At the same
time, an application may wish to modify the URI and then reconstruct it.
In the string form, decoding %2F to / is
not reversible. In the ("", "path/segment"). In this format, the
decoding is reversible: escape the non-syntactic delimiters before
reconstructing the path with the syntactic ones.
A consequence of constructing the /,
if the path begins with a
/, after the last
/, if the path ends with a
/, and between consecutive
/ characters. (If the path consists of a single /,
that / counts as /,
producing a segment list containing two empty strings.)
The
empty strings may seem unnecessary at first glance, but they assure
that the path can be reconstructed by joining the segments together
again without having to handle the presence or absence of a leading or
trailing / as special cases.
Applying
The & (ampersand). For each token, identify
the =), the
If the
A
Implementations may implement additional or different rules for URIs that
have a scheme or pattern that they recognize. An implementation might choose
to parse jar: URIs with special rules, for example, since they extend the
syntax in ways not defined by
A dynamic error is raised
Like
Unlike
In the examples that follow, keys with values that are null or an empty sequence
are elided for editorial clarity. String literals that include an ampersand character
are written as string templates (for example `Barnes&Noble`) to ensure
that the examples work in both XPath and XQuery.
This example uses the algorithm described above, not an algorithm that is
specifically aware of the jar: scheme.
This example demonstrates that parsing the URI treats non-URI characters in
lexical IRIs as “unreserved characters”. The rationale for this is given in the
description of
This example demonstrates the use of | instead of : in a Windows
path.
This example demonstrates the use of | instead of : in a Windows
path with an explicit file: scheme.
New in 4.0
Constructs a URI from the parts provided.
A URI is composed from a scheme, authority, path, query, and fragment.
The following options are available:
The components are derived from the contents of the
$parts map. To simplify the description below, a
value is considered to be present in the map if the relevant
field exists and is non-empty.
If the scheme key is present in the map,
the URI begins with the value of that key. A URI is considered to be
non-hierarchical if either the hierarchical key
is present in the $parts map with the value
false() or if the scheme is known to be
non-hierarchical. (In other words, schemes are hierarchical by
default.)
If the scheme is
known to be non-hierarchical, it is delimited by a trailing
:.
Otherwise, if the scheme is file and the unc-path
option is true, the scheme is delimited by a trailing :////.
Otherwise, the scheme is delimited by
a trailing ://.
For simplicity of exposition, we take the
userinfo, host, and
port values from the map and imagine they are
stored in variables with the same name. If the key is not
present in the map, the value of the variable is set to the
empty sequence.
If $userinfo is non-empty and contains a
non-empty password, then $userinfo is set to the
empty sequence unless the
allow-deprecated-features option is true.
If the omit-default-ports option is true
then the $port is set to the empty sequence if
the port number is the same as the default port for the given
scheme. Implementations http (80),
https (443), ftp (21), and
ssh (22). Exactly which ports are recognized is
If any of $userinfo, $host, or $port
exist, the following authority is added to the URI under construction:
If none of userinfo, host, or port
is present, and authority is present, the value of the
authority key is added to the URI. (In this case, no attempt
is made to determine if a password or standard port are present,
the authority value is simply added to the string.)
The path-segments, query-parameters, and
fragment properties. That’s often the most
convenient behavior but, in order to reconstruct a URI from them,
special escaping rules apply. These rules protect delimiters
without encoding additional characters unnecessarily.
The rules for path-segments,
query-parameters, and fragment are
slightly different because the URI encoding conventions are
slightly different in each case.
An application with more stringent requirements can
construct a path or query that
satisfies the requirements and leave the
path-segments and/or
query-parameters keys out of the map.
If the path-segments key exists in
the map, then the path is constructed from the segments. To
construct the path, the possibly encoded segments are
concatentated together, separated by
The rules for encoding the path segments are different
for hierarchical and non-hierarchical URIs. If the URI is
non-hierarchical, no
encoding is performed on the segments. Otherwise,
each segment is encoded by replacing any control characters (codepoints less than 0x20)
and exclusively the following characters with their
percent-escaped forms: [#0-#20%/\?\#\+\[\]]”.
Encoding is performed unless the URI is known to be non-hierarchical;
in other words, encoding is the default. This heuristic improves the
reliability of using fn:build-uri() on the output of
fn:parse-uri(). (For example,
fn:parse-uri('a+b/c') => fn:build-uri() will return
a+b/c.)
It is necessary to avoid encoding non-hierarchical schemes because there is more
variation in them (for example, the tel: scheme
uses a “+” that must not be encoded). Users working with
non-hierarchical schemes may need to address the encoding issue directly
bearing in mind the encoding requirements of the particular schemes in use.
Otherwise the value of the path key is used.
If neither are present, the empty string is used for the path.
The path is added to the URI.
If the query-parameters key exists in the map, its value
must be a map. A sequence of strings is constructed from the values in the map.
To construct the string, each [#0-#20%=&\#\+\[\]]”.
(This differs from the path encoding in that it excludes
If the
Otherwise, the string constructed is the value of the
The query is constructed by joining the resulting
strings into a single string, separated by & (ampersand) characters.
If the query-parameters key does not exist in the map, but
the query key does, then the query is the value of the
query key.
If there is a query, it is added to the URI with
a preceding
If the fragment key exists in the map, then
the value of that key is encoded and added to the URI with a
preceding [#0-#20%\#\+\[\]]”.
(This differs from the path encoding in that it excludes
The resulting URI is returned.
New in 4.0
Partitions a sequence of items into a sequence of non-empty arrays containing the same items, starting a new partition when a supplied condition is true.
Informally, the function starts by creating a partition containing the first item in the input sequence,
if any. For each remaining item J in the input sequence,
other than the first, it calls the supplied $split-when function with three
arguments: the contents of the current partition, the item J, and the current
position in the input sequence.
Each partition is a sequence of items; the function result wraps each partition as an array, and returns the sequence of arrays.
If the $split-when function returns true, the current partition is wrapped as an array and added to the result,
and a new current partition is created, initially containing the item J only. If the $split-when
function returns false or (), the item J is added to the current partition.
The function enables a variety of positional grouping problems to be solved. For example:
partition($input, fn($a, $b) { count($a) eq 3 }
partitions a sequence into fixed size groups of length 3.
partition($input, fn($a, $b) { boolean($b/self::h1) }
starts a new group whenever an h1 element is encountered.
partition($input, fn($a, $b) { $b lt foot($a) }
starts a new group whenever an item is encountered whose value is less than
the value of the previous item.
The callback function is not called to process the first item in the input sequence, because this will always start a new partition. The first argument to the callback function (the current partition) is always a non-empty sequence.
New in 4.0
Produces the sequence of successive partial results from
the evaluation of
The function returns a sequence of N+1
$input. For values of $n in the range 0 to N,
the value of the single member of array $n+1 in the result sequence is the value of the expression
fold-left( subsequence($input, 1, $n), $init, $action ).
A practical implementation is likely to compute each array in the result sequence based on the value of the previous item, rather than computing each item independently as implied by the specification.
New in 4.0
Produces the sequence of successive partial results from
the evaluation of
The function returns a sequence of N+1
$input. For values of $n in the range 0 to N,
the value of the single member of array $n+1 in the result sequence is the value of the expression
fold-right( subsequence($input, count($input)-$n+1), $init, $action ).
A practical implementation is likely to compute each array in the result sequence based on the value of the previous item, rather than computing each item independently as implied by the specification.
New in 4.0
Creates an Invisible XML parser for a grammar.
Conceptually, an
If the function is called twice with the same arguments, it is
For example, the following grammar describes a date as consisting of a year, a month, and a day. Each are a sequence of digits and they are separated by hyphens:
Using this grammar to parse “2023-10-31” will produce:
Using this grammar to parse “2023-10-32” will produce something like this:
The exact format of the error output will vary between implementations.
The only required part of the output is the ixml:state attribute
that contains the value failed.
Careful readers will observe that the example grammar will parse “2023-00-00” as a date. The grammar could easily be extended to exclude the “00” forms for month and day, but this is only intended to be an illustrative example.
The
The provided grammar must be a string conforming to the Invisible XML specification grammar or an XML representation of such a grammar.
The following options are available. The
Additional,
If $grammar is the empty sequence, a parser is returned
for the Invisible XML specification grammar. This $grammar is not
empty, it err:FOIX0001.
The parsing function that is returned behaves as follows:
It takes a string as input and returns an item as its result, usually an
XML document containing the result of the parse. (The return type is item()
to allow implementations to provide other sorts of results.)
It is
If the fail-on-error option is
true(), the parsing function will raise
err:FOIX0002 if the input provided cannot be
parsed successfully. Otherwise, it returns an XML representation of the
error (rooted at a document node) as described by the
New in 4.0
Delivers a root
The function creates a $input, and whose
This has the effect that lookup expressions starting from this JNode retain information for subsequent navigation.
A JNode has unique identity. If two maps or arrays M1 and
M2 have the same function identity, as determined by the
jtree(M1) is jtree(M2)
It is to some extent $m is bound to a map or array,
calling jtree($m) more than once (with the same variable reference)
will deliver the same JNode each time.
The effect of the coercion rules is technically that if an existing JNode is supplied as $input,
the wrapped value will be extracted, and then rewrapped as a JNode: in practice,
this can be short-circuited by returning the supplied JNode unchanged.
Although $map/child::*. Specifically,
if the left-hand operand of the / operator is a map or array,
then the supplied map or array is implicitly wrapped in a JNode.
The effect of applying json-doc($source)//name.
This expression returns a set of JNodes representing all entries in the JTree having the key "name";
each of these JNodes contains not only the value of the relevant "name" entry,
but also the key (which in this simple example is always "name"
and the containing map. This means, for example, if $result
is the result of the expression json-doc($source) // name, then:
$result / .. / ssn locates the map that contained each
name, and returns the value of the ssn entry in that map.
$result / ancestor::course returns any
course entries in containing maps.
$result / ancestor::* => jnode-selector() returns a sequence of map keys and array index
values representing the location of the found entries within the JSON structure.
An alternative way of wrapping a map or array, rather than calling jtree($X),
is to use the path expression $X/..
There are two situations where a map or array is implicitly wrapped in a JNode:
When the value of the left-hand operand of the / operator
includes a map or array;
When the context value for evaluation of an AxisStep
includes a map or array.
fn:jnode would happen automaticallyNew in 4.0
Returns the
If the argument is omitted, it defaults to the context value (.).
If $input is an empty sequence, the function returns an empty sequence.
If $input is a root JNode (one in which the
Otherwise, the function returns the $input.
In the case where the parent JNode wraps a map, this will be the key of the relevant entry
within that map; in the case where the parent JNode wraps an array, it will be the 1-based
index of the relevant member of the array.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type jnode()?,
type error
New in 4.0
Returns the
If the argument is omitted, it defaults to the context value (.).
If $input is an empty sequence, the function returns an empty sequence.
If $input is a root JNode (one in which the
Otherwise, the function returns the $input.
The value of this property will be 1 (one) except in cases where
the value of an entry in a map, or a member in an array, is a sequence that contains
multiple items including maps and/or arrays; in such cases
the position will be the 1-based position of the relevant map or array.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type jnode()?,
type error
This function is relevant only when there are maps whose entries are multi-item sequences that include maps and arrays, or arrays whose members include such multi-item sequences. Such structures are uncommon, and never arise from parsing of JSON source text. It is generally best to avoid such structures by using arrays rather than sequences within array and map content; apart from other considerations, this allows the data to be serialized in JSON format.
If an entry within a map, or a member of an array, contains a sequence of items
that mixes arrays and maps with other content (for example the array
[1, 2, ([1,2], [3,4], 5)), then a lookup using the
child axis will only construct JNodes in respect of those items that are
non-empty maps or arrays. This may leave gaps in the position numbering sequence,
as illustrated in the examples below.
New in 4.0
Returns the
If the argument is omitted, it defaults to the context value (.).
If $input is an empty sequence, the function returns an empty sequence.
Otherwise, the function returns the $input.
The following errors may be raised when $node is omitted:
If the context value is
If the context value is not an instance of the sequence type jnode()?,
type error
In many cases it is unnecessary to make an explicit call on jnode-content, because
the coercion rules will take care of this automatically. For example, in an expression
such as $X / descendant::name [matches(., '^J')], the call on
Other examples where the
Any context where the required type is an atomic value, for example arithmetic operations, value comparisons and general comparisons, and calls on functions that expect an atomic value.
Any context where the required type is a map or array, for example
the first argument of functions such as array:size, a free-standing expression within a map
constructor such as map{ $jnode }, the constructs
for member and for key/value, the left-hand
operand of the lookup operator ? (or the context value
in the case of a unary lookup operator), and the operand of a map/array
filter expression $jnode?[predicate].
Notable places where the
When computing the effective boolean
value. As with XNodes, writing if ($array/child::*[1]) ... tests for the existence
of a child, it does not test its value. To test its value, write if (jnode-content($array/child::*[1])) ...,
or equivalently if (xs:boolean($array/child::*[1])) ....
When calling functions that accept arbitrary sequences, such as
It is possible (though probably unwise) to construct a JNode whose jtree([jtree([]), jtree([])]) creates a JNode whose child axis to this JNode will
return a sequence of two JNodes that themselves have further JNodes as their content.
The