diff --git a/specifications/xpath-functions-40/src/fos.xsd b/specifications/xpath-functions-40/src/fos.xsd
index 4f2608d0ea..dc2dce54f9 100644
--- a/specifications/xpath-functions-40/src/fos.xsd
+++ b/specifications/xpath-functions-40/src/fos.xsd
@@ -178,6 +178,7 @@
If the static base URI in the static context is not absent, it is used as the effective
- value of $base
.
If the $base
.
Otherwise, a dynamic error is raised: The function computes the effective boolean value of a sequence, defined according to
the following rules. See also
If $input
is the empty sequence, fn:boolean
returns
@@ -11062,7 +11063,7 @@ represented by the $value
argument took place or will take place.
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
@@ -11114,7 +11115,7 @@ represented by the $value
argument took place or will take place.
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 If If If the In all other cases this function returns xs:date
is the xs:dateTime
at
@@ -17879,6 +17880,7 @@ return tokenize(normalize-space($s), ' ')[. castable as xs:IDREF]
+
$source
is the empty sequence, the result is an empty sequence.$source
is a relative URI reference, it is resolved relative to the value
- of the xs:string
.false
.
If this function returns true
, then calling fn:doc($source)
within the same $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 xs:anyURI
, it is resolved
- against the value of the base-URI property from the static context.
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 The zero-argument form of the function returns the URIs in the If $source
is a relative xs:anyURI
, it is resolved
- against the value of the base-URI property from the static context.
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
Thus, some implementations might ensure that calling fn:uri-collection
and then
- applying fn:doc
to each of the returned URIs delivers the same result as
- calling fn:collection
with the same argument; however, this is not
- guaranteed.
In the case where The fn:uri-collection
returns the URIs of resources that
could also be retrieved directly using fn:collection
, there are several reasons why it
@@ -18272,7 +18275,7 @@ return tokenize(normalize-space($s), ' ')[. castable as xs:IDREF]
$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 }
.
@@ -18317,7 +18324,7 @@ return tokenize(normalize-space($s), ' ')[. castable as xs:IDREF]
The mapping of URIs to the string representation of a resource is the mapping defined in
the
If the If it is appropriate to use a base URI other than the dynamic base URI (for example,
+ If it is appropriate to use a base URI other than the
+ 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
@@ -18420,11 +18432,7 @@ return tokenize(normalize-space($s), ' ')[. castable as xs:IDREF]
its content. When errors have been handled in this way, the function may return a
fallback document provided by the error handler. For backwards compatibility reasons, implementations may provide
- configuration options that alter the default for the $source
argument is an empty sequence, the function
@@ -18385,7 +18392,8 @@ return tokenize(normalize-space($s), ' ')[. castable as xs:IDREF]
fn:resolve-uri
function before passing it to the fn:unparsed-text
function.deterministic
- option.
The rules for determining the encoding are chosen for consistency with The The If The mapping of URIs to the string representation of a resource is the mapping defined in
+ the If the The result of the function is an atomic item of type A dynamic error is raised 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
+ function 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 There is no function (analogous to The choice of A comprehensive set of functions for manipulating binary data is available in the
+ EXPath binary module: see 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 Returns the context position from the dynamic context. Returns the context position from the dynamic context. (See Returns the context size from the dynamic context. Returns the context size from the dynamic context. (See Returns the current dateTime (with timezone) from the dynamic context. (See 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 language property from the dynamic context. Components
of the dynamic context are described in fn:binary-resource
function reads an external resource (for example, a
+ file) and returns its contents in binary.$source
argument $source
is a relative URI reference, it is resolved relative to the value
+ of the xs:string
.$source
argument is an empty sequence, the function
+ returns an empty sequence.xs:base64Binary
+ containing the binary representation of the
+ resource retrieved using the URI.$source
argument
+ contains a fragment identifier, fn:resolve-uri
+ function before passing it to the fn:unparsed-text
function.fn:binary-resource
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).<
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.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.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
.file:read-binary
with similar functionality to
+ fn:binary-resource
, the notable differences being (a) that it takes
+ a file name rather than a URI, and (b) that it is defined to be nondeterministic.
+ xs:dateTime
that is current at some time during the evaluation of a
query or transformation in which fn:current-dateTime
is executed.
The default language property can never be absent. The functions fn:format-integer
,
@@ -20175,7 +20354,7 @@ serialize(
The base URI of the returned document node is taken from the static base URI of the +
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
@@ -26301,7 +26481,7 @@ return csv-to-arrays(
location-hints
option is ignored. The static base URI of the dynamically loaded
- module is the same as the static base URI of the caller.fn:transform
+ reference, it is resolved against the
+ fn:transform
function call. fn:transform
function call.
+ the fn:transform
function call.
fn:transform
function call.
+ is resolved against the fn:transform
function call.
The value also acts as the default for stylesheet-base-uri.
+ fn:binary-resource
function when applied to that
+ URI.