Changes

Jump to navigation Jump to search
1,220 bytes removed ,  18:38, 1 December 2023
m
Text replacement - "syntaxhighlight" to "pre"
This article is part of the [[XQuery|XQuery Portal]]. It provides a summary of the most important features of the [httphttps://www.w3.org/TR/xquery-31/ XQuery 3.1] Recommendation.
=Maps=
Maps can be constructed as follows:
<syntaxhighlight pre lang="'xquery"'>
map { }, (: empty map :)
map { 'key': true(), 1984: (<a/>, <b/>) }, (: map with two entries :)
return map { $i: 'value' || $i }
)
</syntaxhighlightpre>
The function corresponding to the map has the signature {{Code|function($key as xs:anyAtomicType) as item()*}}. The expression {{Code|$map($key)}} returns the associated value; the function call {{Code|map:get($map, $key)}} is equivalent. For example, if {{Code|$books-by-isbn}} is a map whose keys are ISBNs and whose associated values are {{Code|book}} elements, then the expression {{Code|$books-by-isbn("0470192747")}} returns the {{Code|book}} element with the given ISBN. The fact that a map is a function item allows it to be passed as an argument to [[Higher-Order Functions]] that expect a function item as one of their arguments. As an example, the following query uses the higher-order function {{Code|fn:map($f, $seq)}} to extract all bound values from a map:
<syntaxhighlight pre lang="'xquery"'>
let $map := map { 'foo': 42, 'bar': 'baz', 123: 456 }
return fn:for-each(map:keys($map), $map)
</syntaxhighlightpre>
This returns some permutation of {{Code|(42, 'baz', 456)}}.
Because a map is a function item, functions that apply to functions also apply to maps. A map is an anonymous function, so {{Code|fn:function-name}} returns the empty sequence; {{Code|fn:function-arity}} always returns {{Code|1}}.
Like all other values, maps are immutable. For example, the <code>[[{{Function|Map Module#map:remove|map:remove]]</code> }} function creates a new map by removing an entry from an existing map, but the existing map is not changed by the operation. Like sequences, maps have no identity. It is meaningful to compare the contents of two maps, but there is no way of asking whether they are "the same map": two maps with the same content are indistinguishable.
Maps may be compared using the {{Code|fn:deep-equal}} function. The [[Map Module]] describes the available set of map functions.
=Arrays=
An ''array'' is a function that associates a set of positions, represented as positive integer keys, with values. The first position in an array is associated with the integer {{Code|1}}. The values of an array are called its members. In the type hierarchy, array has a distinct type, which is derived from function. In BaseX, arrays (as well as sequences) are based on an efficient [httphttps://en.wikipedia.org/wiki/Finger_tree Finger Tree] implementation.
Arrays can be constructed in two ways. With the square bracket notation, the comma serves as delimiter:
<syntaxhighlight pre lang="'xquery"'
[], (: empty array :)
[ (1, 2) ], (: array with single member :)
[ 1 to 2, 3 ] (: array with two members; same as: [ (1, 2), 3 ] :)
</syntaxhighlightpre>
With the {{Code|array}} keyword and curly brackets, the inner expression is evaluated as usual, and the resulting values will be the members of the array:
<syntaxhighlight pre lang="'xquery"'
array { }, (: empty array; same as: array { () } :)
array { (1, 2) }, (: array with two members; same as: array { 1, 2 } :)
array { 1 to 2, 3 } (: array with three members; same as: array { 1, 2, 3 } :)
</syntaxhighlightpre>
The function corresponding to the array has the signature {{Code|function($index as xs:integer) as item()*}}. The expression {{Code|$array($index)}} returns an addressed member of the array. The following query returns the five array members {{Code|48 49 50 51 52}} as result:
<syntaxhighlight pre lang="'xquery"'
let $array := array { 48 to 52 }
for $i in 1 to array:size($array)
return $array($i)
</syntaxhighlightpre>
Like all other values, arrays are immutable. For example, the <code>[[{{Function|Array Module#array:reverse|array:reverse]]</code> }} function creates a new array containing a re-ordering of the members of an existing array, but the existing array is not changed by the operation. Like sequences, arrays have no identity. It is meaningful to compare the contents of two arrays, but there is no way of asking whether they are "the same array": two arrays with the same content are indistinguishable.
==Atomization==
If an array is ''atomized'', all of its members will be atomized. As a result, an atomized item may now result in more than one item. Some examples:
<syntaxhighlight pre lang="'xquery"'
fn:data([1 to 2]) (: returns the sequence 1, 2 :)
[ 'a', 'b', 'c' ] = 'b' (: returns true :)
<a>{ [ 1, 2 ] }</a> (: returns <a>1 2</a> :)
array { 1 to 2 } + 3 (: error: the left operand returns two items :)
</syntaxhighlightpre>
Atomization also applies to function arguments. The following query returns 5, because the array will be atomized to a sequence of 5 integers:
<syntaxhighlight pre lang="'xquery"'
let $f := function($x as xs:integer*) { count($x) }
return $f([1 to 5])
</syntaxhighlightpre>
However, the next query returns 1, because the array is already of the general type {{Code|item()}}, and no atomization will take place:
<syntaxhighlight pre lang="'xquery"'
let $f := function($x as item()*) { count($x) }
return $f([1 to 5])
</syntaxhighlightpre>
Arrays can be compared with the {{Code|fn:deep-equal}} function. The [[Array Module]] describes the available set of array functions.
The following example demonstrates the four alternatives:
<syntaxhighlight pre lang="'xquery"'
let $map := map { 'R': 'red', 'G': 'green', 'B': 'blue' }
return (
$array?(2 to 3) (: 3. returns the second and third values; same as: (1 to 2) ! $array(.) :)
)
</syntaxhighlightpre>
The lookup operator can also be used without left operand. In this case, the context item will be used as input. This query returns {{Code|Akureyri}}:
<syntaxhighlight pre lang="'xquery"'
let $maps := (
map { 'name': 'Guðrún', 'city': 'Reykjavík' },
)
return $maps[?name = 'Hildur'] ?city
</syntaxhighlightpre>
=Arrow Operator=
The arrow operator <code>=></code> provides a convenient alternative syntax for passing on functions to a value. The expression that precedes the operator will be supplied as first argument of the function that follows the arrow. If <code>$v</code> is a value and <code>f()</code> is a function, then <code>$v => f()</code> is equivalent to <code>f($v)</code>, and <code>$v => f($j)</code> is equivalent to <code>f($v, $j)</code>:
<syntaxhighlight pre lang="'xquery"'
(: Returns 3 :)
count(('A', 'B', 'C')),
(for $i in 'welcome' => string-to-codepoints()
return $i + 1) => codepoints-to-string()
</syntaxhighlightpre>
The syntax makes nested function calls more readable, as it is easy to see if parentheses are balanced.
The string constructors syntax uses two backticks and a square bracket for opening and closing a string:
<syntaxhighlight pre lang="'xquery"'
(: Returns "This is a 'new' & 'flexible' syntax." :)
``["This is a 'new' & 'flexible' syntax."]``
</syntaxhighlightpre>
XQuery expressions can be embedded via backticks and a curly bracket. The evaluated results will be separated with spaces, and all strings will eventually be concatenated:
<syntaxhighlight pre lang="'xquery"'
(: Returns »Count 1 2 3, and I will be there.« :)
let $c := 1 to 3
return ``[»Count `{ $c }`, and I will be there.«]``</syntaxhighlightpre>
=Serialization=
Two [[Serialization]] methods have been added to the [httphttps://www.w3.org/TR/xslt-xquery-serialization-31 Serialization spec]:
==Adaptive Serialization==
The {{Code|adaptive}} serialization provides an intuitive textual representation for all XDM types, including maps and arrays, functions, attributes, and namespaces. All items will be separated by the value of the {{Code|item-separator}} parameter, which by default is a newline character. It is utilized by the functions <code>[[{{Function|Profiling Module#prof:dump|prof:dump]]</code> }} and <code>[https://www.w3.org/TR/xpath-functions-31/#func-trace fn:trace]</code>.
Example:
<syntaxhighlight pre lang="'xquery"'
declare option output:method 'adaptive';
<element id='id0'/>/@id,
map { 'key': 'value' },
true#0
</syntaxhighlightpre>
Result:
<syntaxhighlight pre lang="xml">
id="id0"
xs:token("abc"),
}
fn:true#0
</syntaxhighlightpre>
==JSON Serialization==
* If an XML node of type {{Code|element(json)}} is found, it will be serialized following the serialization rules of the [[JSON Module]].
* Any other node or atomic value, map, array, or empty sequence will be serialized according to the [httphttps://www.w3.org/TR/xslt-xquery-serialization-31/#json-output rules in the specification].
The following two queries will both return the JSON snippet <code>{ "key": "value" }</code>:
<syntaxhighlight pre lang="'xquery"'
declare option output:method 'json';
map { "key": "value" }
</syntaxhighlight> <syntaxhighlight lang="xquery"pre>
<pre lang='xquery'>
declare option output:method 'json';
<json type='object'>
<key>value</key>
</json>
</syntaxhighlightpre>
=Functions=
<code>array:size</code>, <code>array:append</code>, <code>array:subarray</code>, <code>array:remove</code>, <code>array:insert-before</code>, <code>array:head</code>, <code>array:tail</code>, <code>array:reverse</code>, <code>array:join</code>, <code>array:flatten</code>, <code>array:for-each</code>, <code>array:filter</code>, <code>array:fold-left</code>, <code>array:fold-right</code>, <code>array:for-each-pair</code>
 
Please check out the [[Array Module]] for more details.
==JSON Functions==
===fn:parse-json===
; Signatures* <codepre>fn:parse-json( $input json as xs:string) as item()?</code>* <code>fn:parse-json($input as xs:string, $options as map(*) := ()) as item()?</codepre>
Parses the supplied string as JSON text and returns its item representation. The result may be a map, an array, a string, a double, a boolean, or an empty sequence. The allowed options can be looked up in the [https://www.w3.org/TR/xpath-functions-31/#func-parse-json specification].
<syntaxhighlight pre lang="'xquery"'
parse-json('{ "name": "john" }') (: yields { "name": "json" } :),
parse-json('[ 1, 2, 4, 8, 16]') (: yields [ 1, 2, 4, 8, 16 ] :)
</syntaxhighlightpre>
===fn:json-doc===
; Signatures* <codepre>fn:json-doc( $uri href as xs:string) as item()?</code>* <code>fn:json-doc($uri as xs:string, $options as map(*) := ()) as item()?</codepre>
Retrieves the text from the specified URI, parses the supplied string as JSON text and returns its item representation (see [[#fn:parse-json{{Function||fn:parse-json]] }} for more details). <syntaxhighlight lang="xquery">
<pre lang='xquery'>
json-doc("http://ip.jsontest.com/")('ip') (: returns your IP address :)
</syntaxhighlightpre>
===fn:json-to-xml===
; Signatures* <codepre>fn:json-to-xml( $string json as xs:string? $options as map(*) := ()) as document-node()?</codepre>
Converts a JSON string to an XML node representation. The allowed options can be looked up in the [https://www.w3.org/TR/xpath-functions-31/#func-json-to-xm specification].
<syntaxhighlight pre lang="'xquery"'
json-to-xml('{ "message": "world" }')
<string key="message">world</string>
</map> :)
</syntaxhighlightpre>
===fn:xml-to-json===
; Signatures* <codepre>fn:xml-to-json( $node as xs:string? $options as nodemap(*) := ()?) as xs:string?</codepreConverts an XML node, whose format conforms to the results created by [[#fn:json-to-xml|fn:json-to-xml]], to a JSON string representation. The allowed options can be looked up in the [https://www.w3.org/TR/xpath-functions-31/#func-xml-to-json specification].
<syntaxhighlight lang="xquery">Converts an XML node, whose format conforms to the results created by {{Function||fn:json-to-xml}}, to a JSON string representation. The allowed options can be looked up in the [https://www.w3.org/TR/xpath-functions-31/#func-xml-to-json specification].
<pre lang='xquery'>
(: returns "JSON" :)
xml-to-json(<string xmlns="http://www.w3.org/2005/xpath-functions">JSON</string>)
</syntaxhighlightpre>
==fn:sort==
; Signatures* <codepre>fn:sort($input as item()*) as item()*</code>* <code>fn:sort( $input as item()*, $collation as xs:string?) as xs :anyAtomicType*)) as item()*</code>* <code>= fn:sort($input as itemdefault-collation()*, $collation as xs:string?, $key as function(item()*) as xs:anyAtomicType*) := fn:data#1) as item()*</codepre>
Returns a new sequence with sorted {{Code|$input}} items, using an optional {{Code|$collation}}. If a {{Code|$key}} function is supplied, it will be applied on all items. The items of the resulting values will be sorted using the semantics of the {{Code|lt}} expression.
<syntaxhighlight pre lang="'xquery"'
sort(reverse(1 to 3)) (: yields 1, 2, 3 :),
reverse(sort(1 to 3)) (: returns the sorted order in descending order :),
sort((1,2,3), (), function($x) { -$x }) (: yields 3, 2, 1 :),
sort((1,'a')) (: yields an error, as strings and integers cannot be compared :)
</syntaxhighlightpre>
==fn:contains-token==
; Signatures* <codepre>fn:contains-token( $input value as xs:string*, $token as string) as xs:boolean</code>* <code>fn:contains-token($input as xs:string*, $token as string, $collation as xs:string? := fn:default-collation()) as xs:boolean</codepre>
The supplied strings will be tokenized at whitespace boundaries. The function returns {{Code|true}} if one of the strings equals the supplied token, possibly under the rules of a supplied collation:
<syntaxhighlight pre lang="'xquery"'
contains-token(('a', 'b c', 'd'), 'c') (: yields true :)
<xml class='one two'/>/contains-token(@class, 'one') (: yields true :)
</syntaxhighlightpre>
==fn:parse-ietf-date==
; Signature* <codepre>fn:parse-ietf-date( $input value as xs:string?) as xs:stringdateTime?</codepre>
Parses a string in the IETF format (which is widely used on the Internet) and returns a {{Code|xs:dateTime}} item:
<syntaxhighlight pre lang="'xquery"'
fn:parse-ietf-date('28-Feb-1984 07:07:07')" (: yields 1984-02-28T07:07:07Z :),
fn:parse-ietf-date('Wed, 01 Jun 2001 23:45:54 +02:00')" (: yields 2001-06-01T23:45:54+02:00 :)
</syntaxhighlightpre>
==fn:apply==
; Signatures* <codepre>fn:apply( $function as function(*), $arguments as array(*)) as item()*</codepre>
The supplied {{Code|$function}} is invoked with the specified {{Code|$arguments}}. The arity of the function must be the same as the size of the array.
Example:
<syntaxhighlight pre lang="'xquery"'
fn:apply(concat#5, array { 1 to 5 }) (: 12345 :)
fn:apply(function($a) { sum($a) }, [ 1 to 5 ]) (: 15 :)
fn:apply(count#1, [ 1,2 ]) (: error. the array has two members :)
</syntaxhighlightpre>
==fn:random-number-generator==
; Signatures* <codepre>fn:random-number-generator() as map(xs:string, item())</code>* <code>fn:random-number-generator( $seed as xs:anyAtomicType? := ()) as map(xs:string, item())</codepre>
Creates a random number generator, using an optional seed. The returned map contains three entries:
Example:
<syntaxhighlight pre lang="'xquery"'
let $rng := fn:random-number-generator()
let $number := $rng('number') (: returns a random number :)
let $permutation := $rng('permute')(1 to 5) (: returns a random permutation of (1,2,3,4,5) :)
return ($number, $next-number, $permutation)
</syntaxhighlightpre>
==fn:format-number==
The function has been extended to support scientific notation:
<syntaxhighlight pre lang="'xquery"'
format-number(1984.42, '00.0e0') (: yields 19.8e2 :)
</syntaxhighlightpre>
==fn:tokenize==
If no separator is specified as second argument, a string will be tokenized at whitespace boundaries:
<syntaxhighlight pre lang="'xquery"'
fn:tokenize(" a b c d") (: yields "a", "b", "c", "d" :)
</syntaxhighlightpre>
==fn:trace==
The second argument can now be omitted:
<syntaxhighlight pre lang="'xquery"'
fn:trace(<xml/>, "Node: ")/node() (: yields the debugging output "Node: <xml/>" :),
fn:trace(<xml/>)/node() (: returns the debugging output "<xml/>" :)
</syntaxhighlightpre>
==fn:string-join==
The type of the first argument is now <code>xs:anyAtomicType*</code>, and all items will be implicitly cast to strings:
<syntaxhighlight pre lang="'xquery"'
fn:string-join(1 to 3) (: yields the string "123" :)
</syntaxhighlightpre>
==fn:default-language==
Items of type <code>xs:hexBinary</code> and <code>xs:base64Binary</code> can be compared against each other. The following queries all yield {{Code|true}}:
<syntaxhighlight pre lang="'xquery"'
xs:hexBinary('') < xs:hexBinary('bb'),
xs:hexBinary('aa') < xs:hexBinary('bb'),
max((xs:hexBinary('aa'), xs:hexBinary('bb'))) = xs:hexBinary('bb')
</syntaxhighlightpre>
=Collations=
XQuery 3.1 provides a default collation, which allows for a case-insensitive comparison of ASCII characters (<code>A-Z</code> = <code>a-z</code>). This query returns <code>true</code>:
<syntaxhighlight pre lang="'xquery"'
declare default collation 'http://www.w3.org/2005/xpath-functions/collation/html-ascii-case-insensitive';
'HTML' = 'html'
</syntaxhighlightpre>
If the [http://site.icu-project.org/download ICU Library] is downloaded and added to the classpath, the full [https://www.w3.org/TR/xpath-functions-31/#uca-collations Unicode Collation Algorithm] features become available in BaseX:
<syntaxhighlight pre lang="'xquery"'
(: returns 0 (both strings are compared as equal) :)
compare('a-b', 'ab', 'http://www.w3.org/2013/collation/UCA?alternate=shifted')
</syntaxhighlightpre>
=Enclosed Expressions=
''Enclosed expression'' is the syntactical term for the expressions that are specified inside a function body, try/catch clauses, node constructors and some other expressions. In the following example expressions, its the empty sequence:
<syntaxhighlight pre lang="'xquery"'> declare function local:x() { () }; i
try { () } catch * { () },
element x { () },
text { () }
</syntaxhighlightpre>
With XQuery 3.1, the expression can be omitted. The following query is equivalent to the upper one:
<syntaxhighlight pre lang="'xquery"'
declare function local:x() { };
try { } catch * { },
element x { }
text { }
</syntaxhighlightpre>
=Changelog=
;Version 8.4
* Added: [[#String Constructors|String Constructors]], [[#fn:default-language{{Code|fn:default-language]]}}, [[#Enclosed Expressions|Enclosed Expressions]]* Updated: [[#Adaptive Serialization|Adaptive Serialization]], [[#fn:string-join{{Code|fn:string-join]]}}
;Version 8.2
* Added: [[#fn:json-to-xml{{Code|fn:json-to-xml]]}}, [[#fn:xml-to-json{{Code|fn:xml-to-json]]}}.
;Version 8.1
* Updated: arrays are now based on a [httphttps://en.wikipedia.org/wiki/Finger_tree Finger Tree] implementation.
Introduced with Version 8.0.
Bureaucrats, editor, reviewer, Administrators
13,554

edits

Navigation menu