Merge lp:~sorin.marian.nasoi/zorba/implementation_defined_features into lp:zorba

Proposed by Sorin Marian Nasoi
Status: Merged
Approved by: Matthias Brantner
Approved revision: 10492
Merged at revision: 10491
Proposed branch: lp:~sorin.marian.nasoi/zorba/implementation_defined_features
Merge into: lp:zorba
Diff against target: 2762 lines (+1778/-494)
9 files modified
doc/zorba/impl_dep_features.dox (+575/-112)
scripts/sanity_checks/README.txt (+1/-2)
scripts/sanity_checks/generate_implementation_defined_features_dox.xq (+23/-23)
test/rbkt/Scripts/w3c/XQFTTS.xml (+733/-117)
test/rbkt/Scripts/w3c/XQTS.xml (+373/-196)
test/rbkt/Scripts/w3c/generate-submission-xqftts.xq (+18/-11)
test/rbkt/Scripts/w3c/generate-submission-xqts.xq (+11/-11)
test/update/Scripts/XQUTS.xml (+32/-10)
test/update/Scripts/generate-submission-xquts.xq (+12/-12)
To merge this branch: bzr merge lp:~sorin.marian.nasoi/zorba/implementation_defined_features
Reviewer Review Type Date Requested Status
Matthias Brantner Approve
Review via email: mp+78133@code.launchpad.net

Commit message

Fixed the implementation defined features, context properties.
Fixed the issues related to the documentation and conformance reports for W3C.

Description of the change

Fixed the implementation defined features, context properties.
Fixed the issues related to the documentation and conformance reports for W3C.

To post a comment you must log in.
Revision history for this message
Matthias Brantner (matthias-brantner) wrote :

I suggest adding some further improvements:

- The first column is always called "Feature" although it's not clear that W3C XQuery update Facility 1.0 is a feature.
- The "Features" of the context properties are wrong. For example, "Default function namespace" seems to be in W3C XQuery and XPath Full Text 1.0

Revision history for this message
Matthias Brantner (matthias-brantner) wrote :

See comments.

review: Needs Fixing
Revision history for this message
Sorin Marian Nasoi (sorin.marian.nasoi) wrote :

> I suggest adding some further improvements:
>
> - The first column is always called "Feature" although it's not clear that W3C
> XQuery update Facility 1.0 is a feature.
Can you please suggest a better name for it?
Is "W3C Specifications" a better table header than "Feature" ?

> - The "Features" of the context properties are wrong. For example, "Default
> function namespace" seems to be in W3C XQuery and XPath Full Text 1.0
It is also part of the W3C XQuery and XPath Full Text 1.0, please check out the W3C XQuery and XPath Full Text 1.0 catalog from the XQFTTS.

The W3C XQuery and XPath Full Text 1.0 also includes the XQuery 1.0 context properties.
If you think it's better I can remove the "Feature" column all together.

Revision history for this message
Matthias Brantner (matthias-brantner) wrote :

> > I suggest adding some further improvements:
> >
> > - The first column is always called "Feature" although it's not clear that
> W3C
> > XQuery update Facility 1.0 is a feature.
> Can you please suggest a better name for it?
> Is "W3C Specifications" a better table header than "Feature" ?
Yes, "W3C Specification" is better.

>
> > - The "Features" of the context properties are wrong. For example, "Default
> > function namespace" seems to be in W3C XQuery and XPath Full Text 1.0
> It is also part of the W3C XQuery and XPath Full Text 1.0, please check out
> the W3C XQuery and XPath Full Text 1.0 catalog from the XQFTTS.
Yes, but this is a bug in the W3C test suite. Please also see Dana's email
"problems with implementation dependent stuff page" from 9/9/11.

>
> The W3C XQuery and XPath Full Text 1.0 also includes the XQuery 1.0 context
> properties.
> If you think it's better I can remove the "Feature" column all together.
I think it should be called "W3C Specification" and the context properties
should indicate properly to which specification they belong. For example,
"Default function namespace" belongs to XQuery 1.0.

Revision history for this message
Sorin Marian Nasoi (sorin.marian.nasoi) wrote :

> > > I suggest adding some further improvements:
> > >
> > > - The first column is always called "Feature" although it's not clear that
> > W3C
> > > XQuery update Facility 1.0 is a feature.
> > Can you please suggest a better name for it?
> > Is "W3C Specifications" a better table header than "Feature" ?
> Yes, "W3C Specification" is better.
>
> >
> > > - The "Features" of the context properties are wrong. For example,
> "Default
> > > function namespace" seems to be in W3C XQuery and XPath Full Text 1.0
> > It is also part of the W3C XQuery and XPath Full Text 1.0, please check out
> > the W3C XQuery and XPath Full Text 1.0 catalog from the XQFTTS.
> Yes, but this is a bug in the W3C test suite. Please also see Dana's email
> "problems with implementation dependent stuff page" from 9/9/11.
>
> >
> > The W3C XQuery and XPath Full Text 1.0 also includes the XQuery 1.0 context
> > properties.
> > If you think it's better I can remove the "Feature" column all together.
> I think it should be called "W3C Specification" and the context properties
> should indicate properly to which specification they belong. For example,
> "Default function namespace" belongs to XQuery 1.0.

All Done: please review the changes.

Thanks for the help.

Revision history for this message
Matthias Brantner (matthias-brantner) wrote :

- The statically known namespaces are wrong: zerr is bound to http://www.zorba-xquery.com/errors

- availale-collections => available-collections

- The current local time on the computer running Zorba. => The current local time (when the XQuery execution is actually started) on the computer running Zorba.

- ...to the context itemvia the... => ...to the context item via the...

- some more space between columns would make it more readable

- we should make the font in the table headers bold

- Implementation Defined Items
Column header "Value" => "Description of the Implementation in Zorba"

Revision history for this message
Sorin Marian Nasoi (sorin.marian.nasoi) wrote :

> - The statically known namespaces are wrong: zerr is bound to http://www
> .zorba-xquery.com/errors
>
> - availale-collections => available-collections
>
> - The current local time on the computer running Zorba. => The current local
> time (when the XQuery execution is actually started) on the computer running
> Zorba.
>
> - ...to the context itemvia the... => ...to the context item via the...
>
> - some more space between columns would make it more readable
>
> - we should make the font in the table headers bold
>
> - Implementation Defined Items
> Column header "Value" => "Description of the Implementation in Zorba"

All fixed.

Revision history for this message
Sorin Marian Nasoi (sorin.marian.nasoi) wrote :

> - The statically known namespaces are wrong: zerr is bound to http://www
> .zorba-xquery.com/errors
>
> - availale-collections => available-collections
>
> - The current local time on the computer running Zorba. => The current local
> time (when the XQuery execution is actually started) on the computer running
> Zorba.
>
> - ...to the context itemvia the... => ...to the context item via the...
>
> - some more space between columns would make it more readable
>
> - we should make the font in the table headers bold
>
> - Implementation Defined Items
> Column header "Value" => "Description of the Implementation in Zorba"

All Done: please review the changes.

Thanks for the help.

Revision history for this message
Matthias Brantner (matthias-brantner) wrote :

Looks good to me now.

review: Approve
Revision history for this message
Zorba Build Bot (zorba-buildbot) wrote :
Revision history for this message
Zorba Build Bot (zorba-buildbot) wrote :

Validation queue job implementation_defined_features-2011-10-05T22-58-03.228Z is finished. The final status was:

All tests succeeded!

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'doc/zorba/impl_dep_features.dox'
--- doc/zorba/impl_dep_features.dox 2011-08-26 23:36:24 +0000
+++ doc/zorba/impl_dep_features.dox 2011-10-05 20:32:28 +0000
@@ -6,279 +6,742 @@
6 <li> \ref Context_properties </li>6 <li> \ref Context_properties </li>
7</ul>7</ul>
8\section IDI Implementation Defined Items8\section IDI Implementation Defined Items
9<table bgcolor="lightcyan">9<table bgcolor="white" cellpadding="2">
10 <tr>10 <tr bgcolor="lightcyan">
11 <td>Feature</td>11 <td>
12 <td>Name</td>12 <strong>W3C Specification</strong>
13 <td>Value/Description</td>13 </td>
14 </tr>14 <td>
15 <tr>15 <strong>Description</strong>
16 </td>
17 <td>
18 <strong>Description of the Implementation in Zorba</strong>
19 </td>
20 </tr>
21 <tr bgcolor="lightcyan">
22 <td>W3C XQuery 1.0</td>
23 <td>The version of Unicode that is used to construct expressions.</td>
24 <td>Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0.</td>
25 </tr>
26 <tr bgcolor="lightcyan">
27 <td>W3C XQuery 1.0</td>
28 <td>The statically-known collations.</td>
29 <td>http://www.w3.org/2005/xpath-functions/collation/codepoint</td>
30 </tr>
31 <tr bgcolor="lightcyan">
32 <td>W3C XQuery 1.0</td>
33 <td>The implicit timezone.</td>
34 <td>The implicit timezone is computed based on the current local time of the computer running Zorba.</td>
35 </tr>
36 <tr bgcolor="lightcyan">
37 <td>W3C XQuery 1.0</td>
38 <td>The circumstances in which warnings are raised, and the ways in which warnings are handled.</td>
39 <td>Warnings are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html and http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_warnings.html.</td>
40 </tr>
41 <tr bgcolor="lightcyan">
42 <td>W3C XQuery 1.0</td>
43 <td>The method by which errors are reported to the external processing environment.</td>
44 <td>Errors are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html.</td>
45 </tr>
46 <tr bgcolor="lightcyan">
47 <td>W3C XQuery 1.0</td>
48 <td>Whether the implementation is based on the rules of [XML 1.0] and [XML Names] or the rules of [XML 1.1] and [XML Names 1.1]. One of these sets of rules must be applied consistently by all aspects of the implementation.</td>
49 <td>XML 1.0</td>
50 </tr>
51 <tr bgcolor="lightcyan">
52 <td>W3C XQuery 1.0</td>
53 <td>Any components of the static context or dynamic context that are overwritten or augmented by the implementation.</td>
54 <td>The following static context components are overwritten/augmented: 1. Statically known namespaces: Augmented with zerr –&gt; http://www.zorba-xquery.com/errors 2. Context item static type: item() 3. Default order for empty sequences: empty_greatest 4. Static Base URI: We use the rules in 4.5, where the implementation-defined default mentioned there is http://www.zorba-xquery.com, 5. Statically known default collection type: item()*</td>
55 </tr>
56 <tr bgcolor="lightcyan">
57 <td>W3C XQuery 1.0</td>
58 <td>Which of the optional axes are supported by the implementation, if the Full-Axis Feature is not supported.</td>
59 <td>All axes are supported</td>
60 </tr>
61 <tr bgcolor="lightcyan">
62 <td>W3C XQuery 1.0</td>
63 <td>The default handling of empty sequences returned by an ordering key (sortspec) in an order by clause (empty least or empty greatest).</td>
64 <td>empty_greatest</td>
65 </tr>
66 <tr bgcolor="lightcyan">
67 <td>W3C XQuery 1.0</td>
68 <td>The names and semantics of any extension expressions (pragmas) recognized by the implementation.</td>
69 <td>No pragmas are recognized.</td>
70 </tr>
71 <tr bgcolor="lightcyan">
72 <td>W3C XQuery 1.0</td>
73 <td>The names and semantics of any option declarations recognized by the implementation.</td>
74 <td>See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/options_and_annotations.html.</td>
75 </tr>
76 <tr bgcolor="lightcyan">
77 <td>W3C XQuery 1.0</td>
78 <td>Protocols (if any) by which parameters can be passed to an external function, and the result of the function can returned to the invoking query.</td>
79 <td>See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/external_functions.html.</td>
80 </tr>
81 <tr bgcolor="lightcyan">
82 <td>W3C XQuery 1.0</td>
83 <td>The process by which the specific modules to be imported by a module import are identified, if the Module Feature is supported (includes processing of location hints, if any.)</td>
84 <td>See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/modules_top.html.</td>
85 </tr>
86 <tr bgcolor="lightcyan">
87 <td>W3C XQuery 1.0</td>
88 <td>Any static typing extensions supported by the implementation, if the Static Typing Feature is supported.</td>
89 <td>Static typing is not supported.</td>
90 </tr>
91 <tr bgcolor="lightcyan">
92 <td>W3C XQuery 1.0</td>
93 <td>The means by which serialization is invoked, if the Serialization Feature is supported.</td>
94 <td>The result of an XQuery program can be serialized via the zorba::XQuery::execute methods (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1XQuery.html). Sequence of items can be serialized via the zorba::Serializer::serialize method (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1Serializer.html).</td>
95 </tr>
96 <tr bgcolor="lightcyan">
97 <td>W3C XQuery 1.0</td>
98 <td>The default values for the byte-order-mark, encoding, media-type, normalization-form, omit-xml-declaration, standalone, and version parameters, if the Serialization Feature is supported.</td>
99 <td>Serialization Feature is supported. Implicit values are: byte-order-mark = no, encoding = UTF-8, media-type = '', normalization-form = '', omix-xml-declaration = no, standalone = omit, version = '1.0', method = xml, doctype-system = '', doctype-public = '', cdata-section-elements = empty list, include-content-type = no, undeclare-prefixes = no, indent = no</td>
100 </tr>
101 <tr bgcolor="lightcyan">
102 <td>W3C XQuery 1.0</td>
103 <td>The result of an unsuccessful call to an external function (for example, if the function implementation cannot be found or does not return a value of the declared type).</td>
104 <td>An error is raised using the regular error handling mechanism of zorba. The kind of error depends on the kind of failure. For example, zerr:ZXQP0008 if the function implementation is not found, or err:XPTY0004 if the result of the function does not match the declared returned type.</td>
105 </tr>
106 <tr bgcolor="lightcyan">
107 <td>W3C XQuery 1.0</td>
108 <td>Limits on ranges of values for various data types, as enumerated in 5.3 Data Model Conformance.</td>
109 <td>totalDigits = 2^63, xs:string length = available memory.</td>
110 </tr>
111 <tr bgcolor="lightcyan">
112 <td>W3C XQuery 1.0</td>
113 <td>The destination of the trace output is implementation-defined. See 4 The Trace Function.</td>
114 <td>By default, it is std:cerr. Users can modify this via the StaticContext::setTraceStream method.</td>
115 </tr>
116 <tr bgcolor="lightcyan">
117 <td>W3C XQuery 1.0</td>
118 <td>For xs:integer operations, implementations that support limited-precision integer operations must either raise an error [err:FOAR0002] or provide an implementation-defined mechanism that allows users to choose between raising an error and returning a result that is modulo the largest representable integer value. See 6.2 Operators on Numeric Values.</td>
119 <td>Zorba raises [err:FOAR0002]</td>
120 </tr>
121 <tr bgcolor="lightcyan">
122 <td>W3C XQuery 1.0</td>
123 <td>For xs:decimal values the number of digits of precision returned by the numeric operators is implementation-defined. See 6.2 Operators on Numeric Values. See also 17.1.3.3 Casting to xs:decimal and 17.1.3.4 Casting to xs:integer.</td>
124 <td>On a 32-bit system, the number of digits of precision is 2^31; on a 64-bit system, the number of digits of precision is 2^63.</td>
125 </tr>
126 <tr bgcolor="lightcyan">
127 <td>W3C XQuery 1.0</td>
128 <td>If the number of digits in the result exceeds the number of digits that the implementation supports, the result is truncated or rounded in an implementation-defined manner. See 6.2 Operators on Numeric Values. See also 17.1.3.3 Casting to xs:decimal and 17.1.3.4 Casting to xs:integer.</td>
129 <td>It does whatever the underlying C++ implementation does.</td>
130 </tr>
131 <tr bgcolor="lightcyan">
132 <td>W3C XQuery 1.0</td>
133 <td>It is implementation-defined which version of Unicode is supported by the features defined in this specification, but it is recommended that the most recent version of Unicode be used. See 7.1 String Types.</td>
134 <td>Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0.</td>
135 </tr>
136 <tr bgcolor="lightcyan">
137 <td>W3C XQuery 1.0</td>
138 <td>For 7.4.6 fn:normalize-unicode, conforming implementations must support normalization form "NFC" and may support normalization forms "NFD", "NFKC", "NFKD", "FULLY-NORMALIZED". They may also support other normalization forms with implementation-defined semantics.</td>
139 <td>Zorba supports NFC, NFKC, NFD, NFKD normalization forms.</td>
140 </tr>
141 <tr bgcolor="lightcyan">
142 <td>W3C XQuery 1.0</td>
143 <td>The ability to decompose strings into collation units suitable for substring matching is an implementation-defined property of a collation. See 7.5 Functions Based on Substring Matching.</td>
144 <td>Zorba does not support this.</td>
145 </tr>
146 <tr bgcolor="lightcyan">
147 <td>W3C XQuery 1.0</td>
148 <td>All minimally conforming processors must support year values with a minimum of 4 digits (i.e., YYYY) and a minimum fractional second precision of 1 millisecond or three digits (i.e., s.sss). However, conforming processors may set larger implementation-defined limits on the maximum number of digits they support in these two situations. See 10.1.1 Limits and Precision.</td>
149 <td>Year values: Zorba supports 9 digits (32bit maxint). Fractional second: Zorba supports 6 digits.</td>
150 </tr>
151 <tr bgcolor="lightcyan">
152 <td>W3C XQuery 1.0</td>
153 <td>The result of casting a string to xs:decimal, when the resulting value is not too large or too small but nevertheless has too many decimal digits to be accurately represented, is implementation-defined. See 17.1.1 Casting from xs:string and xs:untypedAtomic.</td>
154 <td>On a 32-bit system, the number of digits of precision is 2^31; on a 64-bit system, the number of digits of precision is 2^63.</td>
155 </tr>
156 <tr bgcolor="lightcyan">
157 <td>W3C XQuery 1.0</td>
158 <td>Various aspects of the processing provided by 15.5.4 fn:doc are implementation-defined. Implementations may provide external configuration options that allow any aspect of the processing to be controlled by the user.</td>
159 <td>Zorba provides no configuration options for 15.5.4 fn:doc.</td>
160 </tr>
161 <tr bgcolor="lightcyan">
162 <td>W3C XQuery 1.0</td>
163 <td>The manner in which implementations provide options to weaken the stable characteristic of 15.5.6 fn:collection and 15.5.4 fn:doc are implementation-defined.</td>
164 <td>Zorba provides no options to weaken the stable characteristics of 15.5.6 fn:collection or 15.5.4 fn:doc.</td>
165 </tr>
166 <tr bgcolor="lightcyan">
167 <td>W3C XQuery 1.0</td>
168 <td>Support for additional user-defined or implementation-defined types is implementation-defined. (See 2.6.1 Representation of Types)</td>
169 <td>There are no implementation-defined types. User-defined types are created and become “in-scope” when “import schema” statements are processed. User-defined types (including anonymous types) are created within a static context and they are destroyed when their containing static context is destroyed.</td>
170 </tr>
171 <tr bgcolor="lightcyan">
172 <td>W3C XQuery 1.0</td>
173 <td>Some typed values in the data model are undefined. Attempting to access an undefined property is always an error. Behavior in these cases is implementation-defined and the host language is responsible for determining the result. (See 5 Accessors)</td>
174 <td>err:FOTY0012</td>
175 </tr>
176 <tr bgcolor="lightcyan">
177 <td>W3C XQuery 1.0</td>
178 <td>For any implementation-defined output method, it is implementation-defined whether sequence normalization process takes place. (See 2 Sequence Normalization)</td>
179 <td>Zorba performs sequence normalization for the 'binary' serialization method. Zorba's Data Converters module performs sequence normalization for JSON and JSONML (but these are not serialization output methods, i.e. they cannot be invoked with the help of '-z method=JSON')</td>
180 </tr>
181 <tr bgcolor="lightcyan">
182 <td>W3C XQuery 1.0</td>
183 <td>If the namespace URI is non-null for the method serialization parameter, then the parameter specifies an implementation-defined output method. (See 3 Serialization Parameters)</td>
184 <td>Zorba's only implementation-defined output method is 'binary' and it is used unqualified (URI is null).</td>
185 </tr>
186 <tr bgcolor="lightcyan">
187 <td>W3C XQuery 1.0</td>
188 <td>If the value of the normalization-form form parameter is not NFC, NFD, NFKC, NFKD, fully-normalized, or none then the meaning of the value and it's effect is implementation-defined. (See 4 Phases of Serialization)</td>
189 <td>Zorba has no implementation-defined values for the normalization-form parameter.</td>
190 </tr>
191 <tr bgcolor="lightcyan">
192 <td>W3C XQuery 1.0</td>
193 <td>The effect of additional serialization parameters on the output of the serializer, where the name of such a parameter must be namespace-qualified, is implementation-defined or implementation-dependent. The extent of this effect on the output must not override the provisions of this specification. (See 3 Serialization Parameters)</td>
194 <td>Zorba has no implementation-defined serialization parameters.</td>
195 </tr>
196 <tr bgcolor="lightcyan">
197 <td>W3C XQuery 1.0</td>
198 <td>The effect of providing an option that allows the encoding phase to be skipped, so that the result of serialization is a stream of Unicode characters, is implementation-defined. The serializer is not required to support such an option. (See 4 Phases of Serialization)</td>
199 <td>Zorba has no such option.</td>
200 </tr>
201 <tr bgcolor="lightcyan">
202 <td>W3C XQuery 1.0</td>
203 <td>An serializer may provide an implementation-defined mechanism to place CDATA sections in the result tree. (See 5.1.4 XML Output Method: the cdata-section-elements Parameter)</td>
204 <td>Input CDATA sections are treated and serialized as text. Text nodes can be serialized as cdata sections if explicitly requested through the cdata-section-elements parameter.</td>
205 </tr>
206 <tr bgcolor="lightcyan">
16 <td>W3C XQuery Update Facility 1.0</td>207 <td>W3C XQuery Update Facility 1.0</td>
17 <td>supportedRevalidationModes</td>208 <td>The revalidation modes that are supported by this implementation.</td>
18 <td>lax, skip, strict</td>209 <td>lax, skip, strict</td>
19 </tr>210 </tr>
20 <tr>211 <tr bgcolor="lightcyan">
21 <td>W3C XQuery Update Facility 1.0</td>212 <td>W3C XQuery Update Facility 1.0</td>
22 <td>defaultRevalidationMode</td>213 <td>The default revalidation mode for this implementation.</td>
23 <td>lax</td>214 <td>lax</td>
24 </tr>215 </tr>
25 <tr>216 <tr bgcolor="lightcyan">
26 <td>W3C XQuery Update Facility 1.0</td>217 <td>W3C XQuery Update Facility 1.0</td>
27 <td>externalFunctionXDMPUL</td>218 <td>The mechanism (if any) by which an external function can return an XDM instance and/or a pending update list to the invoking query.</td>
28 <td>Zorba allows external functions to be implemented in C++. Such functions may return XDM instances. However, it is not possible to implement an updating external function.</td>219 <td>Zorba allows external functions to be implemented in C++. Such functions may return XDM instances. However, it is not possible to implement an updating external function.</td>
29 </tr>220 </tr>
30 <tr>221 <tr bgcolor="lightcyan">
31 <td>W3C XQuery Update Facility 1.0</td>222 <td>W3C XQuery Update Facility 1.0</td>
32 <td>fnPutSemantics</td>223 <td>The semantics of fn:put(), including the kinds of nodes accepted as operands by this function.</td>
33 <td>fn:put stores a copy (preserving type, preserving namespaces, and inheriting namespace) of the given document or element in Zorba's store. That is it binds the node to the URI passed as first argument. If the URI is relative it's resolved against the base uri. The result of fn:put become effective at the end of the XQuery program or if they are applied using Zorba's made persistent.</td>224 <td>fn:put stores a copy (preserving type, preserving namespaces, and inheriting namespace) of the given document or element in Zorba's store. That is it binds the node to the URI passed as first argument. If the URI is relative it's resolved against the base uri. The result of fn:put become effective at the end of the XQuery program or if they are applied using Zorba's made persistent.</td>
34 </tr>225 </tr>
226 <tr bgcolor="lightcyan">
227 <td>W3C XQuery and XPath Full Text 1.0</td>
228 <td>Tokenization, including the definition of the term "tokens", SHOULD be implementation-defined. Implementations SHOULD expose the rules and sample results of tokenization as much as possible to enable users to predict and interpret the results of tokenization.</td>
229 <td>Zorba uses ICU for word tokenization, so what ever ICU's rules are are Zorba's rules. ICU uses the 'Unicode Standard Annex #29: Unicode Text Segmentation' rules found here http://www.unicode.org/reports/tr29 .</td>
230 </tr>
231 <tr bgcolor="lightcyan">
232 <td>W3C XQuery and XPath Full Text 1.0</td>
233 <td>A phrase is an ordered sequence of any number of tokens. Beyond that, phrases are implementation-defined.</td>
234 <td>A phrase in nothing more that 1+ tokens separated by text boundaries as defined by http://www.unicode.org/reports/tr29 .</td>
235 </tr>
236 <tr bgcolor="lightcyan">
237 <td>W3C XQuery and XPath Full Text 1.0</td>
238 <td>A sentence is an ordered sequence of any number of tokens. Beyond that, sentences are implementation-defined. An implementation is not required to support sentences.</td>
239 <td>Zorba uses ICU for sentence tokenization, so what ever ICU's rules are are Zorba's rules. ICU uses the 'Unicode Standard Annex #29: Unicode Text Segmentation' rules found here http://www.unicode.org/reports/tr29 .</td>
240 </tr>
241 <tr bgcolor="lightcyan">
242 <td>W3C XQuery and XPath Full Text 1.0</td>
243 <td>A paragraph is an ordered sequence of any number of tokens. Beyond that, paragraphs are implementation-defined. An implementation is not required to support paragraphs.</td>
244 <td>Zorba considers XML elements to be paragraph delimiters. For example: &lt;p&gt;It was the best of times. It wat the worse of times.&lt;/p&gt; is 1 paragraph; however: &lt;p&gt;That was a &lt;b&gt;bold&lt;/b&gt; is 3 paragraphs since Zorba attaches no semantic meaning to any particular XML elements.</td>
245 </tr>
246 <tr bgcolor="lightcyan">
247 <td>W3C XQuery and XPath Full Text 1.0</td>
248 <td>Implementations are free to provide implementation-defined ways to differentiate between markup's effect on token boundaries during tokenization.</td>
249 <td>Markup delimits paragraphs and, by implication, sentences and tokens.</td>
250 </tr>
251 <tr bgcolor="lightcyan">
252 <td>W3C XQuery and XPath Full Text 1.0</td>
253 <td>The set of expressions (of form ExprSingle) that can be assigned to a score variable in a let-clause is implementation-defined. The result of passing an expression to the scoring algorithm that it does not support is implementation-defined.</td>
254 <td>Score variables are not currently supported.</td>
255 </tr>
256 <tr bgcolor="lightcyan">
257 <td>W3C XQuery and XPath Full Text 1.0</td>
258 <td>When a sequence of query tokens is considered as a phrase, it matches a sequence of tokens in the tokenized form of the text being searched only if the two sequences correspond in an implementation-defined way.</td>
259 <td>Given the tokens: A B C they have to match: A B C exactly; no more, no less.</td>
260 </tr>
261 <tr bgcolor="lightcyan">
262 <td>W3C XQuery and XPath Full Text 1.0</td>
263 <td>The match option application order, subject to the stated constraints, is implementation-defined.</td>
264 <td>Match options are applied in the following order: Stop Word Option, Stemming Option, Case Option, Diacritics Option, Wildcard Option, Language Option.</td>
265 </tr>
266 <tr bgcolor="lightcyan">
267 <td>W3C XQuery and XPath Full Text 1.0</td>
268 <td>The "language" option influences tokenization, stemming, and stop words in an implementation-defined way. It MAY influence the behavior of other match options in an implementation-defined way.</td>
269 <td>The Language Option: * Affects tokenization as performed by ICU. * Selects the stemming algorithm to be used.* Selects the default set of stop-words to be used. The Language Option does not affect any other Match Option.</td>
270 </tr>
271 <tr bgcolor="lightcyan">
272 <td>W3C XQuery and XPath Full Text 1.0</td>
273 <td>The set of valid language identifiers is implementation-defined.</td>
274 <td>Zorba recognizes the ISO 639-1 and 639-2 language identifiers for the following languages: Danish, Dutch, English, Finnish, German, Hungarian, Italian, Norwegian, Portuguese, Romanian, Russian, Spanish, Swedish, Turkish.</td>
275 </tr>
276 <tr bgcolor="lightcyan">
277 <td>W3C XQuery and XPath Full Text 1.0</td>
278 <td>If an invalid language identifier is specified, then the behavior is implementation-defined.</td>
279 <td>Zorba raises err::XPTY0004 for a string that can not be cast to xs:language and err::FTST0009 for an unsupported language.</td>
280 </tr>
281 <tr bgcolor="lightcyan">
282 <td>W3C XQuery and XPath Full Text 1.0</td>
283 <td>When a processor evaluates text in a document that is governed by an xml:lang attribute and the portion of the full-text query doing that evaluation contains an FTLanguageOption that specifies a different language from the language specified by the governing xml:lang attribute, the language-related behavior of that full-text query is implementation-defined.</td>
284 <td>xml:lang always wins.</td>
285 </tr>
286 <tr bgcolor="lightcyan">
287 <td>W3C XQuery and XPath Full Text 1.0</td>
288 <td>It is implementation-defined which thesaurus relationships an implementation supports.</td>
289 <td>This is covered in the Zorba Full Text Thesaurus documentation, http://www.zorba-xquery.com/site2/doc/latest/zorba/html/ft_thesaurus.html</td>
290 </tr>
291 <tr bgcolor="lightcyan">
292 <td>W3C XQuery and XPath Full Text 1.0</td>
293 <td>If a query specifies thesaurus relationships or levels not supported by the thesaurus, or does not specify a relationship, the behavior is implementation-defined.</td>
294 <td>Unsupported thesaurus relationships are treated as no relationship. All levels are supported. When no relationship is specified, all related words are returned.</td>
295 </tr>
296 <tr bgcolor="lightcyan">
297 <td>W3C XQuery and XPath Full Text 1.0</td>
298 <td>If a query does not specify the number of levels, and the implementation does not follow the default of querying all levels of hierarchical relationships, then the number of levels of hierarchical relationships queries is implementation-defined.</td>
299 <td>Zorba uses 2 levels by default.</td>
300 </tr>
301 <tr bgcolor="lightcyan">
302 <td>W3C XQuery and XPath Full Text 1.0</td>
303 <td>It is implementation-defined what a stem of a token is and whether stemming will based on an algorithm, dictionary, or mixed approach.</td>
304 <td>Zorba uses the publicly available Snowball stemmers found here http://snowball.tartarus.org.</td>
305 </tr>
306 <tr bgcolor="lightcyan">
307 <td>W3C XQuery and XPath Full Text 1.0</td>
308 <td>An implementation-defined comparison is used to determine whether a query token appears in the collection of stop words defined by the applicable stop word option.</td>
309 <td>The query token is compared (case insensitively) against the list of stop words for an exact match.</td>
310 </tr>
311 <tr bgcolor="lightcyan">
312 <td>W3C XQuery and XPath Full Text 1.0</td>
313 <td>Normally a stop word matches exactly one token, but there may be implementation-defined conditions, under which a stop word may match a different number of tokens.</td>
314 <td>Zorba has no such conditions.</td>
315 </tr>
316 <tr bgcolor="lightcyan">
317 <td>W3C XQuery and XPath Full Text 1.0</td>
318 <td>The "stop words default" option specifies that an implementation-defined collection of stop words is used.</td>
319 <td>For each of the supported languages, Zorba defines a set of default stop-words (too big to be listed here).</td>
320 </tr>
321 <tr bgcolor="lightcyan">
322 <td>W3C XQuery and XPath Full Text 1.0</td>
323 <td>An implementation recognizes an implementation-defined set of namespace URIs used to denote extension options. The effect of each, including its error behavior, is implementation-defined.</td>
324 <td>Zorba implements no extension options.</td>
325 </tr>
326 <tr bgcolor="lightcyan">
327 <td>W3C XQuery and XPath Full Text 1.0</td>
328 <td>An implementation recognizes an implementation-defined set of namespace URIs used to denote extension selection pragmas. The effect of each, including its error behavior, is implementation-defined.</td>
329 <td>Zorba implements no extension pragmas.</td>
330 </tr>
331 <tr bgcolor="lightcyan">
332 <td>W3C XQuery and XPath Full Text 1.0</td>
333 <td>The conditions under which tokenization of two equal items produces different tokens is implementation-defined.</td>
334 <td>If items are equal, the tokens will also be equal.</td>
335 </tr>
336 <tr bgcolor="lightcyan">
337 <td>W3C XQuery and XPath Full Text 1.0</td>
338 <td>An implementation may impose an implementation-defined restriction on the operand of FTIgnoreOption.</td>
339 <td>Zorba imposes no restriction; however, the FTIgnoreOption implementation is incomplete.</td>
340 </tr>
341 <tr bgcolor="lightcyan">
342 <td>W3C XQuery and XPath Full Text 1.0</td>
343 <td>For certain full-text components of the static context (see C Static Context Components), the default initial value of the component can be overwritten or augmented with an implementation-defined value or values.</td>
344 <td>FTThesaurusOption has no default value. FTLanguageOption is set to whatever the host's language is. Statically known languages: The ISO 639-1 codes are: da, de, en, es, fi, hu, it, nl, no, pt, sv, ru.</td>
345 </tr>
35</table>346</table>
36\section Features Supported Features347\section Features Supported Features
37<table bgcolor="lightcyan">348<table bgcolor="white" cellpadding="2">
38 <tr>349 <tr bgcolor="lightcyan">
39 <td>Feature</td>350 <td>
40 <td>Name</td>351 <strong>W3C Specification</strong>
41 <td>Value</td>352 </td>
353 <td>
354 <strong>Name</strong>
355 </td>
356 <td>
357 <strong>Value</strong>
358 </td>
42 </tr>359 </tr>
43 <tr>360 <tr bgcolor="lightcyan">
44 <td>W3C XQuery 1.0</td>361 <td>W3C XQuery 1.0</td>
45 <td>Minimal Conformance</td>362 <td>Minimal Conformance</td>
46 <td bgcolor="mediumseagreen">true</td>363 <td bgcolor="mediumseagreen">true</td>
47 </tr>364 </tr>
48 <tr>365 <tr bgcolor="lightcyan">
49 <td>W3C XQuery 1.0</td>366 <td>W3C XQuery 1.0</td>
50 <td>Schema Import</td>367 <td>Schema Import</td>
51 <td bgcolor="mediumseagreen">true</td>368 <td bgcolor="mediumseagreen">true</td>
52 </tr>369 </tr>
53 <tr>370 <tr bgcolor="lightcyan">
54 <td>W3C XQuery 1.0</td>371 <td>W3C XQuery 1.0</td>
55 <td>Schema Validation</td>372 <td>Schema Validation</td>
56 <td bgcolor="mediumseagreen">true</td>373 <td bgcolor="mediumseagreen">true</td>
57 </tr>374 </tr>
58 <tr>375 <tr bgcolor="lightcyan">
59 <td>W3C XQuery 1.0</td>376 <td>W3C XQuery 1.0</td>
60 <td>Static Typing</td>377 <td>Static Typing</td>
61 <td bgcolor="white">false</td>378 <td bgcolor="white">false</td>
62 </tr>379 </tr>
63 <tr>380 <tr bgcolor="lightcyan">
64 <td>W3C XQuery 1.0</td>381 <td>W3C XQuery 1.0</td>
65 <td>Static Typing Extensions</td>382 <td>Static Typing Extensions</td>
66 <td bgcolor="white">false</td>383 <td bgcolor="white">false</td>
67 </tr>384 </tr>
68 <tr>385 <tr bgcolor="lightcyan">
69 <td>W3C XQuery 1.0</td>386 <td>W3C XQuery 1.0</td>
70 <td>Full Axis</td>387 <td>Full Axis</td>
71 <td bgcolor="mediumseagreen">true</td>388 <td bgcolor="mediumseagreen">true</td>
72 </tr>389 </tr>
73 <tr>390 <tr bgcolor="lightcyan">
74 <td>W3C XQuery 1.0</td>391 <td>W3C XQuery 1.0</td>
75 <td>Module</td>392 <td>Module</td>
76 <td bgcolor="mediumseagreen">true</td>393 <td bgcolor="mediumseagreen">true</td>
77 </tr>394 </tr>
78 <tr>395 <tr bgcolor="lightcyan">
79 <td>W3C XQuery 1.0</td>396 <td>W3C XQuery 1.0</td>
80 <td>Serialization</td>397 <td>Serialization</td>
81 <td bgcolor="mediumseagreen">true</td>398 <td bgcolor="mediumseagreen">true</td>
82 </tr>399 </tr>
83 <tr>400 <tr bgcolor="lightcyan">
84 <td>W3C XQuery Update Facility 1.0</td>401 <td>W3C XQuery Update Facility 1.0</td>
85 <td>Minimal Conformance</td>402 <td>Minimal Conformance</td>
86 <td bgcolor="mediumseagreen">true</td>403 <td bgcolor="mediumseagreen">true</td>
87 </tr>404 </tr>
88 <tr>405 <tr bgcolor="lightcyan">
89 <td>W3C XQuery Update Facility 1.0</td>406 <td>W3C XQuery Update Facility 1.0</td>
90 <td>Update Facility Static Typing Feature</td>407 <td>Update Facility Static Typing Feature</td>
91 <td bgcolor="white">false</td>408 <td bgcolor="white">false</td>
92 </tr>409 </tr>
93 <tr>410 <tr bgcolor="lightcyan">
94 <td>W3C XQuery and XPath Full Text 1.0</td>411 <td>W3C XQuery and XPath Full Text 1.0</td>
95 <td>Minimal Conformance</td>412 <td>Minimal Conformance</td>
96 <td bgcolor="mediumseagreen">true</td>413 <td bgcolor="mediumseagreen">true</td>
97 </tr>414 </tr>
98 <tr>415 <tr bgcolor="lightcyan">
99 <td>W3C XQuery and XPath Full Text 1.0</td>416 <td>W3C XQuery and XPath Full Text 1.0</td>
100 <td>FTMildNot Operator</td>417 <td>FTMildNot Operator</td>
101 <td bgcolor="mediumseagreen">true</td>418 <td bgcolor="mediumseagreen">true</td>
102 </tr>419 </tr>
103 <tr>420 <tr bgcolor="lightcyan">
104 <td>W3C XQuery and XPath Full Text 1.0</td>421 <td>W3C XQuery and XPath Full Text 1.0</td>
105 <td>FTUnaryNot Operator</td>422 <td>FTUnaryNot Operator</td>
106 <td bgcolor="mediumseagreen">true</td>423 <td bgcolor="mediumseagreen">true</td>
107 </tr>424 </tr>
108 <tr>425 <tr bgcolor="lightcyan">
109 <td>W3C XQuery and XPath Full Text 1.0</td>426 <td>W3C XQuery and XPath Full Text 1.0</td>
110 <td>FTUnit and FTBigUnit</td>427 <td>FTUnit and FTBigUnit</td>
111 <td bgcolor="mediumseagreen">true</td>428 <td bgcolor="mediumseagreen">true</td>
112 </tr>429 </tr>
113 <tr>430 <tr bgcolor="lightcyan">
114 <td>W3C XQuery and XPath Full Text 1.0</td>431 <td>W3C XQuery and XPath Full Text 1.0</td>
115 <td>FTOrder Operator</td>432 <td>FTOrder Operator</td>
116 <td bgcolor="mediumseagreen">true</td>433 <td bgcolor="mediumseagreen">true</td>
117 </tr>434 </tr>
118 <tr>435 <tr bgcolor="lightcyan">
119 <td>W3C XQuery and XPath Full Text 1.0</td>436 <td>W3C XQuery and XPath Full Text 1.0</td>
120 <td>FTScope Operator</td>437 <td>FTScope Operator</td>
121 <td bgcolor="mediumseagreen">true</td>438 <td bgcolor="mediumseagreen">true</td>
122 </tr>439 </tr>
123 <tr>440 <tr bgcolor="lightcyan">
124 <td>W3C XQuery and XPath Full Text 1.0</td>441 <td>W3C XQuery and XPath Full Text 1.0</td>
125 <td>FTWindow Operator</td>442 <td>FTWindow Operator</td>
126 <td bgcolor="mediumseagreen">true</td>443 <td bgcolor="mediumseagreen">true</td>
127 </tr>444 </tr>
128 <tr>445 <tr bgcolor="lightcyan">
129 <td>W3C XQuery and XPath Full Text 1.0</td>446 <td>W3C XQuery and XPath Full Text 1.0</td>
130 <td>FTDistance Operator</td>447 <td>FTDistance Operator</td>
131 <td bgcolor="mediumseagreen">true</td>448 <td bgcolor="mediumseagreen">true</td>
132 </tr>449 </tr>
133 <tr>450 <tr bgcolor="lightcyan">
134 <td>W3C XQuery and XPath Full Text 1.0</td>451 <td>W3C XQuery and XPath Full Text 1.0</td>
135 <td>FTTimes Operator</td>452 <td>FTTimes Operator</td>
136 <td bgcolor="mediumseagreen">true</td>453 <td bgcolor="mediumseagreen">true</td>
137 </tr>454 </tr>
138 <tr>455 <tr bgcolor="lightcyan">
139 <td>W3C XQuery and XPath Full Text 1.0</td>456 <td>W3C XQuery and XPath Full Text 1.0</td>
140 <td>FTContent Operator</td>457 <td>FTContent Operator</td>
141 <td bgcolor="mediumseagreen">true</td>458 <td bgcolor="mediumseagreen">true</td>
142 </tr>459 </tr>
143 <tr>460 <tr bgcolor="lightcyan">
144 <td>W3C XQuery and XPath Full Text 1.0</td>461 <td>W3C XQuery and XPath Full Text 1.0</td>
145 <td>FTCaseOption</td>462 <td>FTCaseOption</td>
146 <td bgcolor="mediumseagreen">true</td>463 <td bgcolor="mediumseagreen">true</td>
147 </tr>464 </tr>
148 <tr>465 <tr bgcolor="lightcyan">
149 <td>W3C XQuery and XPath Full Text 1.0</td>466 <td>W3C XQuery and XPath Full Text 1.0</td>
150 <td>FTStopwordOption</td>467 <td>FTStopwordOption</td>
151 <td bgcolor="mediumseagreen">true</td>468 <td bgcolor="mediumseagreen">true</td>
152 </tr>469 </tr>
153 <tr>470 <tr bgcolor="lightcyan">
154 <td>W3C XQuery and XPath Full Text 1.0</td>471 <td>W3C XQuery and XPath Full Text 1.0</td>
155 <td>FTLanguageOption</td>472 <td>FTLanguageOption</td>
156 <td bgcolor="mediumseagreen">true</td>473 <td bgcolor="mediumseagreen">true</td>
157 </tr>474 </tr>
158 <tr>475 <tr bgcolor="lightcyan">
159 <td>W3C XQuery and XPath Full Text 1.0</td>476 <td>W3C XQuery and XPath Full Text 1.0</td>
160 <td>FTIgnoreOption</td>477 <td>FTIgnoreOption</td>
161 <td bgcolor="white">false</td>478 <td bgcolor="white">false</td>
162 </tr>479 </tr>
163 <tr>480 <tr bgcolor="lightcyan">
164 <td>W3C XQuery and XPath Full Text 1.0</td>481 <td>W3C XQuery and XPath Full Text 1.0</td>
165 <td>Scoring</td>482 <td>Scoring</td>
166 <td bgcolor="white">false</td>483 <td bgcolor="white">false</td>
167 </tr>484 </tr>
168 <tr>485 <tr bgcolor="lightcyan">
169 <td>W3C XQuery and XPath Full Text 1.0</td>486 <td>W3C XQuery and XPath Full Text 1.0</td>
170 <td>Weights</td>487 <td>Weights</td>
171 <td bgcolor="white">false</td>488 <td bgcolor="white">false</td>
172 </tr>489 </tr>
173</table>490</table>
174\section Context_properties Context Properties491\section Context_properties Context Properties
175<table bgcolor="lightcyan">492<table bgcolor="white" cellpadding="2">
176 <tr>493 <tr bgcolor="lightcyan">
177 <td>Feature</td>494 <td>
178 <td>Name</td>495 <strong>W3C Specification</strong>
179 <td>Context Type</td>496 </td>
180 <td>Value</td>497 <td>
181 </tr>498 <strong>Name</strong>
182 <tr>499 </td>
500 <td>
501 <strong>Context Type</strong>
502 </td>
503 <td>
504 <strong>Value</strong>
505 </td>
506 </tr>
507 <tr bgcolor="lightcyan">
508 <td>W3C XQuery 1.0</td>
509 <td>Statically known namespaces</td>
510 <td>static</td>
511 <td>fn –&gt; http://www.w3.org/2005/xpath-functions, xml –&gt; http://www.w3.org/XML/1998/namespace, xs –&gt; http://www.w3.org/2001/XMLSchema, xsi –&gt; http://www.w3.org/2001/XMLSchema-instance, local –&gt; http://www.w3.org/2005/xquery-local-functions, zerr –&gt; http://www.zorba-xquery.com/errors</td>
512 </tr>
513 <tr bgcolor="lightcyan">
514 <td>W3C XQuery 1.0</td>
515 <td>Default element/type namespace</td>
516 <td>static</td>
517 <td>None.</td>
518 </tr>
519 <tr bgcolor="lightcyan">
183 <td>W3C XQuery 1.0</td>520 <td>W3C XQuery 1.0</td>
184 <td>Default function namespace</td>521 <td>Default function namespace</td>
185 <td>static</td>522 <td>static</td>
186 <td>http://www.w3.org/2005/xpath-functions</td>523 <td>http://www.w3.org/2005/xpath-functions .</td>
187 </tr>524 </tr>
188 <tr>525 <tr bgcolor="lightcyan">
526 <td>W3C XQuery 1.0</td>
527 <td>In-scope schema types</td>
528 <td>static</td>
529 <td>Built-in types in xs.</td>
530 </tr>
531 <tr bgcolor="lightcyan">
532 <td>W3C XQuery 1.0</td>
533 <td>In-scope element declarations</td>
534 <td>static</td>
535 <td>None.</td>
536 </tr>
537 <tr bgcolor="lightcyan">
538 <td>W3C XQuery 1.0</td>
539 <td>In-scope attribute declarations</td>
540 <td>static</td>
541 <td>None.</td>
542 </tr>
543 <tr bgcolor="lightcyan">
544 <td>W3C XQuery 1.0</td>
545 <td>In-scope variables</td>
546 <td>static</td>
547 <td>None.</td>
548 </tr>
549 <tr bgcolor="lightcyan">
189 <td>W3C XQuery 1.0</td>550 <td>W3C XQuery 1.0</td>
190 <td>Context item static type</td>551 <td>Context item static type</td>
191 <td>static</td>552 <td>static</td>
192 <td>item()</td>553 <td>item()</td>
193 </tr>554 </tr>
194 <tr>555 <tr bgcolor="lightcyan">
556 <td>W3C XQuery 1.0</td>
557 <td>Function signatures</td>
558 <td>static</td>
559 <td>Functions in fn namespace, and constructors for built-in atomic types.</td>
560 </tr>
561 <tr bgcolor="lightcyan">
562 <td>W3C XQuery 1.0</td>
563 <td>Statically known collations</td>
564 <td>static</td>
565 <td>Initially, the only available collation is the codepoint collection: http://www.w3.org/2005/xpath-functions/collation/codepoint. More collations can be added to a static context via the StaticContext::addCollation() method of the C++ API.</td>
566 </tr>
567 <tr bgcolor="lightcyan">
195 <td>W3C XQuery 1.0</td>568 <td>W3C XQuery 1.0</td>
196 <td>Default collation</td>569 <td>Default collation</td>
197 <td>static</td>570 <td>static</td>
198 <td>http://www.w3.org/2005/xpath-functions/collation/codepoint</td>571 <td>http://www.w3.org/2005/xpath-functions/collation/codepoint</td>
199 </tr>572 </tr>
200 <tr>573 <tr bgcolor="lightcyan">
201 <td>W3C XQuery 1.0</td>574 <td>W3C XQuery 1.0</td>
202 <td>Construction mode</td>575 <td>Construction mode</td>
203 <td>static</td>576 <td>static</td>
204 <td>preserve</td>577 <td>preserve</td>
205 </tr>578 </tr>
206 <tr>579 <tr bgcolor="lightcyan">
207 <td>W3C XQuery 1.0</td>580 <td>W3C XQuery 1.0</td>
208 <td>Ordering mode</td>581 <td>Ordering mode</td>
209 <td>static</td>582 <td>static</td>
210 <td>ordered</td>583 <td>ordered</td>
211 </tr>584 </tr>
212 <tr>585 <tr bgcolor="lightcyan">
213 <td>W3C XQuery 1.0</td>586 <td>W3C XQuery 1.0</td>
214 <td>Default order for empty sequences</td>587 <td>Default order for empty sequences</td>
215 <td>static</td>588 <td>static</td>
216 <td>empty greatest</td>589 <td>empty greatest</td>
217 </tr>590 </tr>
218 <tr>591 <tr bgcolor="lightcyan">
219 <td>W3C XQuery 1.0</td>592 <td>W3C XQuery 1.0</td>
220 <td>Boundary-space policy</td>593 <td>Boundary-space policy</td>
221 <td>static</td>594 <td>static</td>
222 <td>strip</td>595 <td>strip</td>
223 </tr>596 </tr>
224 <tr>597 <tr bgcolor="lightcyan">
225 <td>W3C XQuery 1.0</td>598 <td>W3C XQuery 1.0</td>
226 <td>Copy-namespaces mode</td>599 <td>Copy-namespaces mode</td>
227 <td>static</td>600 <td>static</td>
228 <td>inherit preserve</td>601 <td>inherit preserve</td>
229 </tr>602 </tr>
230 <tr>603 <tr bgcolor="lightcyan">
604 <td>W3C XQuery 1.0</td>
605 <td>Base URI</td>
606 <td>static</td>
607 <td>Uses the rules in http://www.w3.org/TR/xquery-30/#id-base-uri-decl, where the implementation-defined default mentioned there is http://www.zorba-xquery.com</td>
608 </tr>
609 <tr bgcolor="lightcyan">
610 <td>W3C XQuery 1.0</td>
611 <td>Statically known documents</td>
612 <td>static</td>
613 <td>None.</td>
614 </tr>
615 <tr bgcolor="lightcyan">
616 <td>W3C XQuery 1.0</td>
617 <td>Statically known collections</td>
618 <td>static</td>
619 <td>None.</td>
620 </tr>
621 <tr bgcolor="lightcyan">
622 <td>W3C XQuery 1.0</td>
623 <td>Statically known default collection type</td>
624 <td>static</td>
625 <td>item()*</td>
626 </tr>
627 <tr bgcolor="lightcyan">
628 <td>W3C XQuery 1.0</td>
629 <td>Context item</td>
630 <td>dynamic</td>
631 <td>None. Before execution of a query, a value can be assigned to the context item via the DynamicContext::setContextItem method.</td>
632 </tr>
633 <tr bgcolor="lightcyan">
634 <td>W3C XQuery 1.0</td>
635 <td>Context position</td>
636 <td>dynamic</td>
637 <td>None.</td>
638 </tr>
639 <tr bgcolor="lightcyan">
640 <td>W3C XQuery 1.0</td>
641 <td>Context size</td>
642 <td>dynamic</td>
643 <td>None.</td>
644 </tr>
645 <tr bgcolor="lightcyan">
646 <td>W3C XQuery 1.0</td>
647 <td>Variable values</td>
648 <td>dynamic</td>
649 <td>None.</td>
650 </tr>
651 <tr bgcolor="lightcyan">
652 <td>W3C XQuery 1.0</td>
653 <td>Function implementations</td>
654 <td>dynamic</td>
655 <td>Functions in fn namespace, and constructors for built-in atomic types.</td>
656 </tr>
657 <tr bgcolor="lightcyan">
658 <td>W3C XQuery 1.0</td>
659 <td>Current dateTime</td>
660 <td>dynamic</td>
661 <td>The current local time (when the XQuery execution is actually started) on the computer running Zorba.</td>
662 </tr>
663 <tr bgcolor="lightcyan">
664 <td>W3C XQuery 1.0</td>
665 <td>Implicit timezone</td>
666 <td>dynamic</td>
667 <td>Computed based on the current local time on the computer running Zorba.</td>
668 </tr>
669 <tr bgcolor="lightcyan">
670 <td>W3C XQuery 1.0</td>
671 <td>Available documents</td>
672 <td>dynamic</td>
673 <td>The URIs returned by the availale-documents function of module http://www.zorba-xquery.com/modules/store/dynamic/documents (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_documents.html)</td>
674 </tr>
675 <tr bgcolor="lightcyan">
676 <td>W3C XQuery 1.0</td>
677 <td>Available collections</td>
678 <td>dynamic</td>
679 <td>The URIs returned by the available-collections function of module http://www.zorba-xquery.com/modules/store/dynamic/collections/w3c/ddl (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_collections_w3c_ddl.html)</td>
680 </tr>
681 <tr bgcolor="lightcyan">
682 <td>W3C XQuery 1.0</td>
683 <td>Default collection</td>
684 <td>dynamic</td>
685 <td>None.</td>
686 </tr>
687 <tr bgcolor="lightcyan">
231 <td>W3C XQuery Update Facility 1.0</td>688 <td>W3C XQuery Update Facility 1.0</td>
232 <td>Revalidation mode</td>689 <td>Revalidation mode</td>
233 <td>static</td>690 <td>static</td>
234 <td>lax</td>691 <td>lax</td>
235 </tr>692 </tr>
236 <tr>693 <tr bgcolor="lightcyan">
237 <td>W3C XQuery and XPath Full Text 1.0</td>694 <td>W3C XQuery and XPath Full Text 1.0</td>
238 <td>Default function namespace</td>695 <td>FTCaseOption</td>
239 <td>static</td>696 <td>static</td>
240 <td>http://www.w3.org/2005/xpath-functions</td>697 <td>case insensitive</td>
241 </tr>698 </tr>
242 <tr>699 <tr bgcolor="lightcyan">
243 <td>W3C XQuery and XPath Full Text 1.0</td>700 <td>W3C XQuery and XPath Full Text 1.0</td>
244 <td>Context item static type</td>701 <td>FTDiacriticsOption</td>
245 <td>static</td>702 <td>static</td>
246 <td>item()</td>703 <td>diacritics insensitive</td>
247 </tr>704 </tr>
248 <tr>705 <tr bgcolor="lightcyan">
249 <td>W3C XQuery and XPath Full Text 1.0</td>706 <td>W3C XQuery and XPath Full Text 1.0</td>
250 <td>Default collation</td>707 <td>FTStemOption</td>
251 <td>static</td>708 <td>static</td>
252 <td>http://www.w3.org/2005/xpath-functions/collation/codepoint</td>709 <td>no stemming</td>
253 </tr>710 </tr>
254 <tr>711 <tr bgcolor="lightcyan">
255 <td>W3C XQuery and XPath Full Text 1.0</td>712 <td>W3C XQuery and XPath Full Text 1.0</td>
256 <td>Construction mode</td>713 <td>Statically known thesauri</td>
257 <td>static</td>714 <td>static</td>
258 <td>preserve</td>715 <td>http://wordnet.princeton.edu/</td>
259 </tr>716 </tr>
260 <tr>717 <tr bgcolor="lightcyan">
261 <td>W3C XQuery and XPath Full Text 1.0</td>718 <td>W3C XQuery and XPath Full Text 1.0</td>
262 <td>Ordering mode</td>719 <td>FTStopWordOption</td>
263 <td>static</td>720 <td>static</td>
264 <td>ordered</td>721 <td>no stop words</td>
265 </tr>722 </tr>
266 <tr>723 <tr bgcolor="lightcyan">
267 <td>W3C XQuery and XPath Full Text 1.0</td>724 <td>W3C XQuery and XPath Full Text 1.0</td>
268 <td>Default order for empty sequences</td>725 <td>Statically known stop word lists</td>
269 <td>static</td>726 <td>static</td>
270 <td>empty greatest</td>727 <td>Zorba uses the publicly available lists found here http://snowball.tartarus.org.</td>
271 </tr>728 </tr>
272 <tr>729 <tr bgcolor="lightcyan">
273 <td>W3C XQuery and XPath Full Text 1.0</td>730 <td>W3C XQuery and XPath Full Text 1.0</td>
274 <td>Boundary-space policy</td>731 <td>FTLanguageOption</td>
275 <td>static</td>732 <td>static</td>
276 <td>strip</td>733 <td>Whatever the host's language is.</td>
277 </tr>734 </tr>
278 <tr>735 <tr bgcolor="lightcyan">
279 <td>W3C XQuery and XPath Full Text 1.0</td>736 <td>W3C XQuery and XPath Full Text 1.0</td>
280 <td>Copy-namespaces mode</td>737 <td>Statically known languages</td>
281 <td>static</td>738 <td>static</td>
282 <td>inherit preserve</td>739 <td>The ISO 639-1 codes are: da, de, en, es, fi, hu, it, nl, no, pt, sv, ru.</td>
283 </tr>740 </tr>
284</table>*/741 <tr bgcolor="lightcyan">
742 <td>W3C XQuery and XPath Full Text 1.0</td>
743 <td>FTWildcardOption</td>
744 <td>static</td>
745 <td>no wildcards </td>
746 </tr>
747</table>*/
285\ No newline at end of file748\ No newline at end of file
286749
=== modified file 'scripts/sanity_checks/README.txt'
--- scripts/sanity_checks/README.txt 2011-08-17 13:51:42 +0000
+++ scripts/sanity_checks/README.txt 2011-10-05 20:32:28 +0000
@@ -20,5 +20,4 @@
2020
21generate_implementation_defined_features_dox.xq21generate_implementation_defined_features_dox.xq
22Run it in order to generate the docygen page:22Run it in order to generate the docygen page:
23./zorba --indent -z method=xml --omit-xml-declaration
24-f -q ../../scripts/sanity_checks/generate_implementation_defined_features_dox.xq > /home/spungi/work/zorba2/doc/zorba/impl_dep_features.dox
25\ No newline at end of file23\ No newline at end of file
24./zorba --indent -z method=xml --omit-xml-declaration -f -q ../../scripts/sanity_checks/generate_implementation_defined_features_dox.xq > ../../doc/zorba/impl_dep_features.dox
26\ No newline at end of file25\ No newline at end of file
2726
=== modified file 'scripts/sanity_checks/generate_implementation_defined_features_dox.xq'
--- scripts/sanity_checks/generate_implementation_defined_features_dox.xq 2011-08-18 20:31:17 +0000
+++ scripts/sanity_checks/generate_implementation_defined_features_dox.xq 2011-10-05 20:32:28 +0000
@@ -20,7 +20,7 @@
2020
21return 21return
22("",22("",
23"/** \page impl_dep_features Information about Implementation Dependent Features and Properties23"/** \page impl_dep_features Implementation Dependent Features and Properties
2424
25",25",
26<ul>26<ul>
@@ -30,35 +30,35 @@
30</ul>,30</ul>,
31"31"
32\section IDI Implementation Defined Items",32\section IDI Implementation Defined Items",
33 <table bgcolor="lightcyan">33 <table bgcolor="white" cellpadding="2">
34 <tr><td>Feature</td><td>Name</td><td>Value/Description</td></tr>34 <tr bgcolor="lightcyan"><td><strong>W3C Specification</strong></td><td><strong>Description</strong></td><td><strong>Description of the Implementation in Zorba</strong></td></tr>
35 {35 {
36 for $idi in $XQTSZorba//*:implementation-defined-item36 for $idi in $XQTSZorba//*:implementation-defined-item
37 where not(data($idi/@value) = "")37 where not(data($idi/@value) = "")
38 return38 return
39 <tr>39 <tr bgcolor="lightcyan">
40 <td>W3C XQuery 1.0</td>40 <td>W3C XQuery 1.0</td>
41 <td>{data($idi/@name)}</td>41 <td>{normalize-space($idi/*:description/text())}</td>
42 <td>{data($idi/@value)}</td>42 <td>{data($idi/@value)}</td>
43 </tr>43 </tr>
44 }44 }
45 {45 {
46 for $idi in $XQUTSZorba//*:implementation-defined-item46 for $idi in $XQUTSZorba//*:implementation-defined-item
47 where not(data($idi/@value) = "")47 where not(data($idi/@value) = "")
48 return48 return
49 <tr>49 <tr bgcolor="lightcyan">
50 <td>W3C XQuery Update Facility 1.0</td>50 <td>W3C XQuery Update Facility 1.0</td>
51 <td>{data($idi/@name)}</td>51 <td>{normalize-space($idi/*:description/text())}</td>
52 <td>{data($idi/@value)}</td>52 <td>{data($idi/@value)}</td>
53 </tr>53 </tr>
54 }54 }
55 {55 {
56 for $idi in $XQFTTSZorba//*:implementation-defined-item56 for $idi in $XQFTTSZorba//*:implementation-defined-item
57 where not(data($idi/@value) = "")57 where not(data($idi/@value) = "") and data($idi/@spec) = "XQueryFullText"
58 return58 return
59 <tr>59 <tr bgcolor="lightcyan">
60 <td>W3C XQuery and XPath Full Text 1.0</td>60 <td>W3C XQuery and XPath Full Text 1.0</td>
61 <td>{data($idi/@name)}</td>61 <td>{normalize-space($idi/*:description/text())}</td>
62 <td>{data($idi/@value)}</td>62 <td>{data($idi/@value)}</td>
63 </tr>63 </tr>
64 }64 }
@@ -66,12 +66,12 @@
66 ,66 ,
67"67"
68\section Features Supported Features",68\section Features Supported Features",
69 <table bgcolor="lightcyan">69 <table bgcolor="white" cellpadding="2">
70 <tr><td>Feature</td><td>Name</td><td>Value</td></tr>70 <tr bgcolor="lightcyan"><td><strong>W3C Specification</strong></td><td><strong>Name</strong></td><td><strong>Value</strong></td></tr>
71 {71 {
72 for $feature in $XQTSZorba//*:feature72 for $feature in $XQTSZorba//*:feature
73 return73 return
74 <tr>74 <tr bgcolor="lightcyan">
75 <td>W3C XQuery 1.0</td>75 <td>W3C XQuery 1.0</td>
76 <td>{data($feature/@name)}</td>76 <td>{data($feature/@name)}</td>
77 <td bgcolor="{if(xs:boolean(data($feature/@supported))) then 'mediumseagreen' else 'white'}">{data($feature/@supported)}</td>77 <td bgcolor="{if(xs:boolean(data($feature/@supported))) then 'mediumseagreen' else 'white'}">{data($feature/@supported)}</td>
@@ -80,7 +80,7 @@
80 {80 {
81 for $feature in $XQUTSZorba//*:feature81 for $feature in $XQUTSZorba//*:feature
82 return82 return
83 <tr>83 <tr bgcolor="lightcyan">
84 <td>W3C XQuery Update Facility 1.0</td>84 <td>W3C XQuery Update Facility 1.0</td>
85 <td>{data($feature/@name)}</td>85 <td>{data($feature/@name)}</td>
86 <td bgcolor="{if(xs:boolean(data($feature/@supported))) then 'mediumseagreen' else 'white'}">{data($feature/@supported)}</td>86 <td bgcolor="{if(xs:boolean(data($feature/@supported))) then 'mediumseagreen' else 'white'}">{data($feature/@supported)}</td>
@@ -89,7 +89,7 @@
89 {89 {
90 for $feature in $XQFTTSZorba//*:feature90 for $feature in $XQFTTSZorba//*:feature
91 return91 return
92 <tr>92 <tr bgcolor="lightcyan">
93 <td>W3C XQuery and XPath Full Text 1.0</td>93 <td>W3C XQuery and XPath Full Text 1.0</td>
94 <td>{data($feature/@name)}</td>94 <td>{data($feature/@name)}</td>
95 <td bgcolor="{if(xs:boolean(data($feature/@supported))) then 'mediumseagreen' else 'white'}">{data($feature/@supported)}</td>95 <td bgcolor="{if(xs:boolean(data($feature/@supported))) then 'mediumseagreen' else 'white'}">{data($feature/@supported)}</td>
@@ -98,13 +98,13 @@
98 </table>,98 </table>,
99 "99 "
100\section Context_properties Context Properties",100\section Context_properties Context Properties",
101 <table bgcolor="lightcyan">101 <table bgcolor="white" cellpadding="2">
102 <tr><td>Feature</td><td>Name</td><td>Context Type</td><td>Value</td></tr>102 <tr bgcolor="lightcyan"><td><strong>W3C Specification</strong></td><td><strong>Name</strong></td><td><strong>Context Type</strong></td><td><strong>Value</strong></td></tr>
103 {103 {
104 for $property in $XQTSZorba//*:context-property104 for $property in $XQTSZorba//*:context-property
105 where not(data($property/@value) = "")105 where not(data($property/@value) = "")
106 return106 return
107 <tr>107 <tr bgcolor="lightcyan">
108 <td>W3C XQuery 1.0</td>108 <td>W3C XQuery 1.0</td>
109 <td>{data($property/@name)}</td>109 <td>{data($property/@name)}</td>
110 <td>{data($property/@context-type)}</td>110 <td>{data($property/@context-type)}</td>
@@ -115,7 +115,7 @@
115 for $property in $XQUTSZorba//*:context-property115 for $property in $XQUTSZorba//*:context-property
116 where not(data($property/@value) = "")116 where not(data($property/@value) = "")
117 return117 return
118 <tr>118 <tr bgcolor="lightcyan">
119 <td>W3C XQuery Update Facility 1.0</td>119 <td>W3C XQuery Update Facility 1.0</td>
120 <td>{data($property/@name)}</td>120 <td>{data($property/@name)}</td>
121 <td>{data($property/@context-type)}</td>121 <td>{data($property/@context-type)}</td>
@@ -124,9 +124,9 @@
124 }124 }
125 {125 {
126 for $property in $XQFTTSZorba//*:context-property126 for $property in $XQFTTSZorba//*:context-property
127 where not(data($property/@value) = "")127 where not(data($property/@value) = "") and data($property/@spec) = "XQueryFullText"
128 return128 return
129 <tr>129 <tr bgcolor="lightcyan">
130 <td>W3C XQuery and XPath Full Text 1.0</td>130 <td>W3C XQuery and XPath Full Text 1.0</td>
131 <td>{data($property/@name)}</td>131 <td>{data($property/@name)}</td>
132 <td>{data($property/@context-type)}</td>132 <td>{data($property/@context-type)}</td>
133133
=== modified file 'test/rbkt/Scripts/w3c/XQFTTS.xml'
--- test/rbkt/Scripts/w3c/XQFTTS.xml 2011-09-08 20:49:34 +0000
+++ test/rbkt/Scripts/w3c/XQFTTS.xml 2011-10-05 20:32:28 +0000
@@ -2,128 +2,744 @@
2<zorba xmlns="http://www.w3.org/2005/02/query-test-XQTSResult">2<zorba xmlns="http://www.w3.org/2005/02/query-test-XQTSResult">
3 3
4 <implementation-defined-items>4 <implementation-defined-items>
5 <implementation-defined-item name="expressionUnicode" value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0."/>5 <implementation-defined-item
6 <implementation-defined-item name="collations" value="http://www.w3.org/2005/xpath-functions/collation/codepoint"/>6 name="expressionUnicode"
7 <implementation-defined-item name="implicitTimezone" value="The implicit timezone is computed based on the current local time of the computer running Zorba."/>7 spec="XQuery"
8 <implementation-defined-item name="warningsMethod" value="Warnings are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html. Currently, there are only 2 warnings: 1. ZWST0002: generated when an unknown annotation is encountered in an XQuery program. 2. ZWST0003: generated when a non-external user-defined function is declared as sequential, but its implementation is not really sequential."/>8 value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0.">
9 <implementation-defined-item name="errorsMethod" value="Errors are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html."/>9 <description last-mod="2005-04-04">The version of Unicode that is used to construct expressions.</description>
10 <implementation-defined-item name="XMLVersion" value="XML 1.0"/>10 </implementation-defined-item>
11 <implementation-defined-item name="overwrittenContextComponents" value="The following static context components are overwrtten/augmented: 1. Statically known namespaces: Augmented with zerr –> http://www.zorba-xquery.com/ 2. Context item static type: item() 3. Default order for empty sequences: empty_greatest 4. Static Base URI: We use the rules in 4.5, where the implementation-defined default mentioned there is http://www.zorba-xquery.com, 5. Statically known default collection type: item()*"/>11
12 <implementation-defined-item name="axes" value="All axes are supported."/>12 <implementation-defined-item
13 <implementation-defined-item name="defaultOrderEmpty" value="empty_greatest"/>13 name="collations"
14 <implementation-defined-item name="pragmas" value="No pragmas are recognized."/>14 spec="XQuery"
15 <implementation-defined-item name="optionDeclarations" value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/options_and_annotations.html."/>15 value="http://www.w3.org/2005/xpath-functions/collation/codepoint">
16 <implementation-defined-item name="externalFunctionProtocols" value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/external_functions.html"/>16 <description last-mod="2005-04-04">The statically-known collations.</description>
17 <implementation-defined-item name="moduleLocationHints" value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/modules_top.html."/>17 </implementation-defined-item>
18 <implementation-defined-item name="staticTypingExtensions" value="Static typing is not supported."/>18
19 <implementation-defined-item name="serializationInvocation" value="The result of an XQuery program can be serialized via the zorba::XQuery::execute methods (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1XQuery.html). Sequence of items can be serialized via the zorba::Serializer::serialize method (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1Serializer.html)."/>19 <implementation-defined-item
20 <implementation-defined-item name="serializationDefaults" value="Serialization Feature is supported. Implicit values are: byte-order-mark = no, encoding = UTF-8, media-type = '', normalization-form = '', omix-xml-declaration = no, standalone = omit, version = '1.0', method = xml, doctype-system = '', doctype-public = '', cdata-section-elements = empty list, include-content-type = no, undeclare-prefixes = no, indent = no"/>20 name="implicitTimezone"
21 <implementation-defined-item name="externalFunctionCall" value="An error is raised using the regular error handling mechanism of zorba. The kind of error depends on the kind of failure. For example, zerr:ZXQP0008 if the function implementation is not found, or err:XPTY0004 if the result of the function does not match the declared returned type."/>21 spec="XQuery"
22 <implementation-defined-item name="limits" value=""/>22 value="The implicit timezone is computed based on the current local time of the computer running Zorba.">
23 <implementation-defined-item name="traceDestination" value="By default, it is std:cerr. Users can modify this via the StaticContext::setTraceStream method."/>23 <description last-mod="2005-04-04">The implicit timezone.</description>
24 <implementation-defined-item name="integerOperations" value="Zorba raises [err:FOAR0002]"/>24 </implementation-defined-item>
25 <implementation-defined-item name="decimalDigits" value=""/>25
26 <implementation-defined-item name="roundOrTruncate" value=""/>26 <implementation-defined-item
27 <implementation-defined-item name="Unicode" value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0."/>27 name="warningsMethod"
28 <implementation-defined-item name="normalizationForms" value="Zorba supports NFC, NFKC, NFD, NFKD normalization forms."/>28 spec="XQuery"
29 <implementation-defined-item name="collationUnits" value=""/>29 value="Warnings are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html and http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_warnings.html.">
30 <implementation-defined-item name="secondsDigits" value="Year values: Zorba supports 9 digits (32bit maxint). Fractional second: Zorba supports 6 digits."/>30 <description last-mod="2005-04-04">The circumstances in which warnings are raised, and the ways in which warnings are handled.</description>
31 <implementation-defined-item name="stringToDecimal" value=""/>31 </implementation-defined-item>
32 <implementation-defined-item name="docProcessing" value=""/>32
33 <implementation-defined-item name="weakenStable" value=""/>33 <implementation-defined-item
34 <implementation-defined-item name="additionalTypes" value="There are no implementation-defined types. User-defined types are created and become “in-scope” when “import schema” statements are processed. User-defined types (including anonymous types) are created within a static context and they are destroyed when their containing static context is destroyed."/>34 name="errorsMethod"
35 <implementation-defined-item name="undefinedProperties" value="err:FOTY0012"/>35 spec="XQuery"
36 <implementation-defined-item name="sequenceNormalization" value="Zorba performs sequence normalization for the 'binary' serialization method. Zorba's Data Converters module performs sequence normalization for JSON and JSONML (but these are not serialization output methods, i.e. they cannot be invoked with the help of '-z method=JSON')"/>36 value="Errors are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html.">
37 <implementation-defined-item name="outputMethods" value="Zorba's only implementation-defined output method is 'binary' and it is used unqualified (URI is null)."/>37 <description last-mod="2005-04-04">The method by which errors are reported to the external processing environment.</description>
38 <implementation-defined-item name="normalizationFormBehavior" value="Zorba has no implementation-defined values for the normalization-form parameter."/>38 </implementation-defined-item>
39 <implementation-defined-item name="additionalParams" value="Zorba has no implementation-defined serialization parameters."/>39
40 <implementation-defined-item name="encodingPhase" value="Zorba has no such option."/>40 <implementation-defined-item
41 <implementation-defined-item name="CDATASerialization" value="Zorba has no such mechanism."/>41 name="XMLVersion"
42 <implementation-defined-item name="Tokenization" value="Zorba uses ICU for word tokenization, so what ever ICU's rules are are Zorba's rules. ICU uses the 'Unicode Standard Annex #29: Unicode Text Segmentation' rules found here http://www.unicode.org/reports/tr29 ."/>42 spec="XQuery"
43 <implementation-defined-item name="phrase" value="A phrase in nothing more that 1+ tokens separated by text boundaries as defined by http://www.unicode.org/reports/tr29 ."/>43 value="XML 1.0">
44 <implementation-defined-item name="sentence" value="Zorba uses ICU for sentence tokenization, so what ever ICU's rules are are Zorba's rules. ICU uses the 'Unicode Standard Annex #29: Unicode Text Segmentation' rules found here http://www.unicode.org/reports/tr29 ."/>44 <description last-mod="2005-10-10">Whether the implementation is based on the rules of [XML 1.0] and [XML Names] or the rules of [XML 1.1] and [XML Names 1.1]. One of these sets of rules must be applied consistently by all aspects of the implementation.</description>
45 <implementation-defined-item name="paragraph" value="Zorba considers XML elements to be paragraph delimiters. For example: &lt;p&gt;It was the best of times. It wat the worse of times.&lt;/p&gt; is 1 paragraph; however: &lt;p&gt;That was a &lt;b&gt;bold&lt;/b&gt; is 3 paragraphs since Zorba attaches no semantic meaning to any particular XML elements."/>45 </implementation-defined-item>
46 <implementation-defined-item name="Markup Effect Token Boundaries" value="Markup delimits paragraphs and, by implication, sentences and tokens."/>46
47 <implementation-defined-item name="Scoring Expressions" value="Score variables are not currently supported."/>47 <implementation-defined-item
48 <implementation-defined-item name="Matching" value="Given the tokens: A B C they have to match: A B C exactly; no more, no less."/>48 name="overwrittenContextComponents"
49 <implementation-defined-item name="Match Option Order" value="Match options are applied in the following order: Stop Word Option, Stemming Option, Case Option, Diacritics Option, Wildcard Option, Language Option."/>49 spec="XQuery"
50 <implementation-defined-item name="Language Option Tokenization" value="The Language Option: * Affects tokenization as performed by ICU. * Selects the stemming algorithm to be used.* Selects the default set of stop-words to be used. The Language Option does not affect any other Match Option."/>50 value="The following static context components are overwritten/augmented: 1. Statically known namespaces: Augmented with zerr –> http://www.zorba-xquery.com/errors 2. Context item static type: item() 3. Default order for empty sequences: empty_greatest 4. Static Base URI: We use the rules in 4.5, where the implementation-defined default mentioned there is http://www.zorba-xquery.com, 5. Statically known default collection type: item()*">
51 <implementation-defined-item name="Language Option Valid ID" value="Zorba recognizes the ISO 639-1 and 639-2 language identifiers for the following languages: Danish, Dutch, English, Finnish, German, Hungarian, Italian, Norwegian, Portuguese, Romanian, Russian, Spanish, Swedish, Turkish."/>51 <description last-mod="2005-04-04">Any components of the static context or dynamic context that are overwritten or augmented by the implementation.</description>
52 <implementation-defined-item name="Language Option Undefined" value="Zorba raises err::XPTY0004 for a string that can not be cast to xs:language and err::FTST0009 for an unsupported language."/>52 </implementation-defined-item>
53 <implementation-defined-item name="Mismatched Languages" value="xml:lang always wins."/>53
54 <implementation-defined-item name="Thesaurus Option" value="This is covered in the Zorba Full Text Thesaurus documentation, http://www.zorba-xquery.com/site2/doc/latest/zorba/html/ft_thesaurus.html"/>54 <implementation-defined-item
55 <implementation-defined-item name="Thesaurus Relationships" value="Unsupported thesaurus relationships are treated as no relationship. All levels are supported. When no relationship is specified, all related words are returned."/>55 name="axes"
56 <implementation-defined-item name="Thesaurus Levels" value="Zorba uses 2 levels by default."/>56 spec="XQuery"
57 <implementation-defined-item name="Stemming Option" value="Zorba uses the publicly available Snowball stemmers found here http://snowball.tartarus.org."/>57 value="All axes are supported.">
58 <implementation-defined-item name="Query Token In Stopword List" value="The query token is compared (case insensitively) against the list of stop words for an exact match."/>58 <description last-mod="2005-04-04">Which of the optional axes are supported by the implementation, if the Full-Axis Feature is not supported.</description>
59 <implementation-defined-item name="StopWord Option Match Number" value="Zorba has no such conditions."/>59 </implementation-defined-item>
60 <implementation-defined-item name="StopWord Option Default" value="For each of the supported languages, Zorba defines a set of default stop-words (too big to be listed here)."/>60
61 <implementation-defined-item name="Extension Option" value="Zorba implements no extension options."/>61 <implementation-defined-item
62 <implementation-defined-item name="Extension Selection" value="Zorba implements no extension pragmas."/>62 name="defaultOrderEmpty"
63 <implementation-defined-item name="Equal Items Different Tokens" value=""/>63 spec="XQuery"
64 <implementation-defined-item name="FTIgnoreOption" value="Zorba imposes no restriction; however, the FTIgnoreOption implementation is incomplete."/>64 value="empty_greatest">
65 <implementation-defined-item name="Static Context Items" value=""/>65 <description last-mod="2005-04-04">The default handling of empty sequences returned by an ordering key (sortspec) in an order by clause (empty least or empty greatest).</description>
66 </implementation-defined-item>
67
68 <implementation-defined-item
69 name="pragmas"
70 spec="XQuery"
71 value="No pragmas are recognized.">
72 <description last-mod="2005-04-04">The names and semantics of any extension expressions (pragmas) recognized by the implementation.</description>
73 </implementation-defined-item>
74
75 <implementation-defined-item
76 name="optionDeclarations"
77 spec="XQuery"
78 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/options_and_annotations.html.">
79 <description last-mod="2005-04-04">The names and semantics of any option declarations recognized by the implementation.</description>
80 </implementation-defined-item>
81
82 <implementation-defined-item
83 name="externalFunctionProtocols"
84 spec="XQuery"
85 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/external_functions.html">
86 <description last-mod="2005-04-04">Protocols (if any) by which parameters can be passed to an external function, and the result of the function can returned to the invoking query.</description>
87 </implementation-defined-item>
88
89 <implementation-defined-item
90 name="moduleLocationHints"
91 spec="XQuery"
92 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/modules_top.html.">
93 <description last-mod="2005-11-01">The process by which the specific modules to be imported by a module import are identified, if the Module Feature is supported (includes processing of location hints, if any.)</description>
94 </implementation-defined-item>
95
96 <implementation-defined-item
97 name="staticTypingExtensions"
98 spec="XQuery"
99 value="Static typing is not supported.">
100 <description last-mod="2005-04-04">Any static typing extensions supported by the implementation, if the Static Typing Feature is supported.</description>
101 </implementation-defined-item>
102
103 <implementation-defined-item
104 name="serializationInvocation"
105 spec="XQuery"
106 value="The result of an XQuery program can be serialized via the zorba::XQuery::execute methods (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1XQuery.html). Sequence of items can be serialized via the zorba::Serializer::serialize method (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1Serializer.html).">
107 <description last-mod="2005-04-04">The means by which serialization is invoked, if the Serialization Feature is supported.</description>
108 </implementation-defined-item>
109
110 <implementation-defined-item
111 name="serializationDefaults"
112 spec="XQuery"
113 value="Serialization Feature is supported. Implicit values are: byte-order-mark = no, encoding = UTF-8, media-type = '', normalization-form = '', omix-xml-declaration = no, standalone = omit, version = '1.0', method = xml, doctype-system = '', doctype-public = '', cdata-section-elements = empty list, include-content-type = no, undeclare-prefixes = no, indent = no">
114 <description last-mod="2005-10-10">The default values for the byte-order-mark, encoding, media-type, normalization-form, omit-xml-declaration, standalone, and version parameters, if the Serialization Feature is supported.</description>
115 </implementation-defined-item>
116
117 <implementation-defined-item
118 name="externalFunctionCall"
119 spec="XQuery"
120 value="An error is raised using the regular error handling mechanism of zorba. The kind of error depends on the kind of failure. For example, zerr:ZXQP0008 if the function implementation is not found, or err:XPTY0004 if the result of the function does not match the declared returned type.">
121 <description last-mod="2006-08-09">The result of an unsuccessful call to an external function (for example, if the function implementation cannot be found or does not return a value of the declared type).</description>
122 </implementation-defined-item>
123
124 <implementation-defined-item
125 name="limits"
126 spec="XQuery"
127 value="totalDigits = 2^63, xs:string length = available memory.">
128 <description last-mod="2005-11-01">Limits on ranges of values for various data types, as enumerated in 5.3 Data Model Conformance.</description>
129 </implementation-defined-item>
130
131 <implementation-defined-item
132 name="traceDestination"
133 spec="FuncOps"
134 value="By default, it is std:cerr. Users can modify this via the StaticContext::setTraceStream method.">
135 <description last-mod="2005-10-10">The destination of the trace output is implementation-defined. See 4 The Trace Function.</description>
136 </implementation-defined-item>
137
138 <implementation-defined-item
139 name="integerOperations"
140 spec="FuncOps"
141 value="Zorba raises [err:FOAR0002]">
142 <description last-mod="2005-10-10">For xs:integer operations, implementations that support limited-precision integer operations must either raise an error [err:FOAR0002] or provide an implementation-defined mechanism that allows users to choose between raising an error and returning a result that is modulo the largest representable integer value. See 6.2 Operators on Numeric Values.</description>
143 </implementation-defined-item>
144
145 <implementation-defined-item
146 name="decimalDigits"
147 spec="FuncOps"
148 value="On a 32-bit system, the number of digits of precision is 2^31; on a 64-bit system, the number of digits of precision is 2^63.">
149 <description last-mod="2005-11-01">For xs:decimal values the number of digits of precision returned by the numeric operators is implementation-defined. See 6.2 Operators on Numeric Values. See also 17.1.3.3 Casting to xs:decimal and 17.1.3.4 Casting to xs:integer.</description>
150 </implementation-defined-item>
151
152 <implementation-defined-item
153 name="roundOrTruncate"
154 spec="FuncOps"
155 value="It does whatever the underlying C++ implementation does.">
156 <description last-mod="2005-10-10">If the number of digits in the result exceeds the number of digits that the implementation supports, the result is truncated or rounded in an implementation-defined manner. See 6.2 Operators on Numeric Values. See also 17.1.3.3 Casting to xs:decimal and 17.1.3.4 Casting to xs:integer.</description>
157 </implementation-defined-item>
158
159 <implementation-defined-item
160 name="Unicode"
161 spec="FuncOps"
162 value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0.">
163 <description last-mod="2005-11-01">It is implementation-defined which version of Unicode is supported by the features defined in this specification, but it is recommended that the most recent version of Unicode be used. See 7.1 String Types.</description>
164 </implementation-defined-item>
165
166 <implementation-defined-item
167 name="normalizationForms"
168 spec="FuncOps"
169 value="Zorba supports NFC, NFKC, NFD, NFKD normalization forms.">
170 <description last-mod="2005-10-10">For 7.4.6 fn:normalize-unicode, conforming implementations must support normalization form "NFC" and may support normalization forms "NFD", "NFKC", "NFKD", "FULLY-NORMALIZED". They may also support other normalization forms with implementation-defined semantics.</description>
171 </implementation-defined-item>
172
173 <implementation-defined-item
174 name="collationUnits"
175 spec="FuncOps"
176 value="Zorba does not support this.">
177 <description last-mod="2005-10-10">The ability to decompose strings into collation units suitable for substring matching is an implementation-defined property of a collation. See 7.5 Functions Based on Substring Matching.</description>
178 </implementation-defined-item>
179
180 <implementation-defined-item
181 name="secondsDigits"
182 spec="FuncOps"
183 value="Year values: Zorba supports 9 digits (32bit maxint). Fractional second: Zorba supports 6 digits.">
184 <description last-mod="2005-10-10">All minimally conforming processors must support year values with a minimum of 4 digits (i.e., YYYY) and a minimum fractional second precision of 1 millisecond or three digits (i.e., s.sss). However, conforming processors may set larger implementation-defined limits on the maximum number of digits they support in these two situations. See 10.1.1 Limits and Precision.</description>
185 </implementation-defined-item>
186
187 <implementation-defined-item
188 name="stringToDecimal"
189 spec="FuncOps"
190 value="On a 32-bit system, the number of digits of precision is 2^31; on a 64-bit system, the number of digits of precision is 2^63.">
191 <description last-mod="2006-08-09">The result of casting a string to xs:decimal, when the resulting value is not too large or too small but nevertheless has too many decimal digits to be accurately represented, is implementation-defined. See 17.1.1 Casting from xs:string and xs:untypedAtomic.</description>
192 </implementation-defined-item>
193
194 <implementation-defined-item
195 name="docProcessing"
196 spec="FuncOps"
197 value="Zorba provides no configuration options for 15.5.4 fn:doc.">
198 <description last-mod="2005-10-10">Various aspects of the processing provided by 15.5.4 fn:doc are implementation-defined. Implementations may provide external configuration options that allow any aspect of the processing to be controlled by the user.</description>
199 </implementation-defined-item>
200
201 <implementation-defined-item
202 name="weakenStable"
203 spec="FuncOps"
204 value="Zorba provides no options to weaken the stable characteristics of 15.5.6 fn:collection or 15.5.4 fn:doc.">
205 <description last-mod="2006-08-09">The manner in which implementations provide options to weaken the stable characteristic of 15.5.6 fn:collection and 15.5.4 fn:doc are implementation-defined.</description>
206 </implementation-defined-item>
207
208 <implementation-defined-item
209 name="additionalTypes"
210 spec="DataModel"
211 value="There are no implementation-defined types. User-defined types are created and become “in-scope” when “import schema” statements are processed. User-defined types (including anonymous types) are created within a static context and they are destroyed when their containing static context is destroyed.">
212 <description last-mod="2005-04-04">Support for additional user-defined or implementation-defined types is implementation-defined. (See 2.6.1 Representation of Types)</description>
213 </implementation-defined-item>
214
215 <implementation-defined-item
216 name="undefinedProperties"
217 spec="DataModel"
218 value="err:FOTY0012">
219 <description last-mod="2005-04-04">Some typed values in the data model are undefined. Attempting to access an undefined property is always an error. Behavior in these cases is implementation-defined and the host language is responsible for determining the result. (See 5 Accessors)</description>
220 </implementation-defined-item>
221
222 <implementation-defined-item
223 name="sequenceNormalization"
224 spec="Serialization"
225 value="Zorba performs sequence normalization for the 'binary' serialization method. Zorba's Data Converters module performs sequence normalization for JSON and JSONML (but these are not serialization output methods, i.e. they cannot be invoked with the help of '-z method=JSON')">
226 <description last-mod="2005-04-04">For any implementation-defined output method, it is implementation-defined whether sequence normalization process takes place. (See 2 Sequence Normalization)</description>
227 </implementation-defined-item>
228
229 <implementation-defined-item
230 name="outputMethods"
231 spec="Serialization"
232 value="Zorba's only implementation-defined output method is 'binary' and it is used unqualified (URI is null).">
233 <description last-mod="2005-04-04">If the namespace URI is non-null for the method serialization parameter, then the parameter specifies an implementation-defined output method. (See 3 Serialization Parameters)</description>
234 </implementation-defined-item>
235
236 <implementation-defined-item
237 name="normalizationFormBehavior"
238 spec="Serialization"
239 value="Zorba has no implementation-defined values for the normalization-form parameter.">
240 <description last-mod="2005-04-04">If the value of the normalization-form form parameter is not NFC, NFD, NFKC, NFKD, fully-normalized, or none then the meaning of the value and it's effect is implementation-defined. (See 4 Phases of Serialization)</description>
241 </implementation-defined-item>
242
243 <implementation-defined-item
244 name="additionalParams"
245 spec="Serialization"
246 value="Zorba has no implementation-defined serialization parameters.">
247 <description last-mod="2005-11-01">The effect of additional serialization parameters on the output of the serializer, where the name of such a parameter must be namespace-qualified, is implementation-defined or implementation-dependent. The extent of this effect on the output must not override the provisions of this specification. (See 3 Serialization Parameters)</description>
248 </implementation-defined-item>
249
250 <implementation-defined-item
251 name="encodingPhase"
252 spec="Serialization"
253 value="Zorba has no such option.">
254 <description last-mod="2005-04-04">The effect of providing an option that allows the encoding phase to be skipped, so that the result of serialization is a stream of Unicode characters, is implementation-defined. The serializer is not required to support such an option. (See 4 Phases of Serialization)</description>
255 </implementation-defined-item>
256
257 <implementation-defined-item
258 name="CDATASerialization"
259 spec="Serialization"
260 value="Input CDATA sections are treated and serialized as text. Text nodes can be serialized as cdata sections if explicitly requested through the cdata-section-elements parameter.">
261 <description last-mod="2005-04-04">An serializer may provide an implementation-defined mechanism to place CDATA sections in the result tree. (See 5.1.4 XML Output Method: the cdata-section-elements Parameter)</description>
262 </implementation-defined-item>
263
264 <implementation-defined-item
265 name="Tokenization"
266 spec="XQueryFullText"
267 value="Zorba uses ICU for word tokenization, so what ever ICU's rules are are Zorba's rules. ICU uses the 'Unicode Standard Annex #29: Unicode Text Segmentation' rules found here http://www.unicode.org/reports/tr29 .">
268 <description last-mod="2010-09-17">Tokenization, including the definition of the term "tokens", SHOULD be implementation-defined. Implementations SHOULD expose the rules and sample results of tokenization as much as possible to enable users to predict and interpret the results of tokenization.</description>
269 </implementation-defined-item>
270
271 <implementation-defined-item
272 name="phrase"
273 spec="XQueryFullText"
274 value="A phrase in nothing more that 1+ tokens separated by text boundaries as defined by http://www.unicode.org/reports/tr29 .">
275 <description last-mod="2008-02-18">A phrase is an ordered sequence of any number of tokens. Beyond that, phrases are implementation-defined.</description>
276 </implementation-defined-item>
277
278 <implementation-defined-item
279 name="sentence"
280 spec="XQueryFullText"
281 value="Zorba uses ICU for sentence tokenization, so what ever ICU's rules are are Zorba's rules. ICU uses the 'Unicode Standard Annex #29: Unicode Text Segmentation' rules found here http://www.unicode.org/reports/tr29 .">
282 <description last-mod="2010-09-16">A sentence is an ordered sequence of any number of tokens. Beyond that, sentences are implementation-defined. An implementation is not required to support sentences.</description>
283 </implementation-defined-item>
284
285 <implementation-defined-item
286 name="paragraph"
287 spec="XQueryFullText"
288 value="Zorba considers XML elements to be paragraph delimiters. For example: &lt;p&gt;It was the best of times. It wat the worse of times.&lt;/p&gt; is 1 paragraph; however: &lt;p&gt;That was a &lt;b&gt;bold&lt;/b&gt; is 3 paragraphs since Zorba attaches no semantic meaning to any particular XML elements.">
289 <description last-mod="2010-09-16">A paragraph is an ordered sequence of any number of tokens. Beyond that, paragraphs are implementation-defined. An implementation is not required to support paragraphs.</description>
290 </implementation-defined-item>
291
292 <implementation-defined-item
293 name="Markup Effect Token Boundaries"
294 spec="XQueryFullText"
295 value="Markup delimits paragraphs and, by implication, sentences and tokens.">
296 <description last-mod="2010-09-16">Implementations are free to provide implementation-defined ways to differentiate between markup's effect on token boundaries during tokenization.</description>
297 </implementation-defined-item>
298
299 <implementation-defined-item
300 name="Scoring Expressions"
301 spec="XQueryFullText"
302 value="Score variables are not currently supported.">
303 <description last-mod="2010-09-16">The set of expressions (of form ExprSingle) that can be assigned to a score variable in a let-clause is implementation-defined. The result of passing an expression to the scoring algorithm that it does not support is implementation-defined.</description>
304 </implementation-defined-item>
305
306 <implementation-defined-item
307 name="Matching"
308 spec="XQueryFullText"
309 value="Given the tokens: A B C they have to match: A B C exactly; no more, no less.">
310 <description last-mod="2010-09-17">When a sequence of query tokens is considered as a phrase, it matches a sequence of tokens in the tokenized form of the text being searched only if the two sequences correspond in an implementation-defined way.</description>
311 </implementation-defined-item>
312
313 <implementation-defined-item
314 name="Match Option Order"
315 spec="XQueryFullText"
316 value="Match options are applied in the following order: Stop Word Option, Stemming Option, Case Option, Diacritics Option, Wildcard Option, Language Option.">
317 <description last-mod="2010-09-16">The match option application order, subject to the stated constraints, is implementation-defined.</description>
318 </implementation-defined-item>
319
320 <implementation-defined-item
321 name="Language Option Tokenization"
322 spec="XQueryFullText"
323 value="The Language Option: * Affects tokenization as performed by ICU. * Selects the stemming algorithm to be used.* Selects the default set of stop-words to be used. The Language Option does not affect any other Match Option.">
324 <description last-mod="2010-09-16">The "language" option influences tokenization, stemming, and stop words in an implementation-defined way. It MAY influence the behavior of other match options in an implementation-defined way.</description>
325 </implementation-defined-item>
326
327 <implementation-defined-item
328 name="Language Option Valid ID"
329 spec="XQueryFullText"
330 value="Zorba recognizes the ISO 639-1 and 639-2 language identifiers for the following languages: Danish, Dutch, English, Finnish, German, Hungarian, Italian, Norwegian, Portuguese, Romanian, Russian, Spanish, Swedish, Turkish.">
331 <description last-mod="2010-09-16">The set of valid language identifiers is implementation-defined.</description>
332 </implementation-defined-item>
333
334 <implementation-defined-item
335 name="Language Option Undefined"
336 spec="XQueryFullText"
337 value="Zorba raises err::XPTY0004 for a string that can not be cast to xs:language and err::FTST0009 for an unsupported language.">
338 <description last-mod="2010-09-17">If an invalid language identifier is specified, then the behavior is implementation-defined.</description>
339 </implementation-defined-item>
340
341 <implementation-defined-item
342 name="Mismatched Languages"
343 spec="XQueryFullText"
344 value="xml:lang always wins.">
345 <description last-mod="2010-09-17">When a processor evaluates text in a document that is governed by an xml:lang attribute and the portion of the full-text query doing that evaluation contains an FTLanguageOption that specifies a different language from the language specified by the governing xml:lang attribute, the language-related behavior of that full-text query is implementation-defined.</description>
346 </implementation-defined-item>
347
348 <implementation-defined-item
349 name="Thesaurus Option"
350 spec="XQueryFullText"
351 value="This is covered in the Zorba Full Text Thesaurus documentation, http://www.zorba-xquery.com/site2/doc/latest/zorba/html/ft_thesaurus.html">
352 <description last-mod="2010-09-16">It is implementation-defined which thesaurus relationships an implementation supports.</description>
353 </implementation-defined-item>
354
355 <implementation-defined-item
356 name="Thesaurus Relationships"
357 spec="XQueryFullText"
358 value="Unsupported thesaurus relationships are treated as no relationship. All levels are supported. When no relationship is specified, all related words are returned.">
359 <description last-mod="2010-09-17">If a query specifies thesaurus relationships or levels not supported by the thesaurus, or does not specify a relationship, the behavior is implementation-defined.</description>
360 </implementation-defined-item>
361
362 <implementation-defined-item
363 name="Thesaurus Levels"
364 spec="XQueryFullText"
365 value="Zorba uses 2 levels by default.">
366 <description last-mod="2011-01-04">If a query does not specify the number of levels, and the implementation does not follow the default of querying all levels of hierarchical relationships, then the number of levels of hierarchical relationships queries is implementation-defined.</description>
367 </implementation-defined-item>
368
369 <implementation-defined-item
370 name="Stemming Option"
371 spec="XQueryFullText"
372 value="Zorba uses the publicly available Snowball stemmers found here http://snowball.tartarus.org.">
373 <description last-mod="2010-09-16">It is implementation-defined what a stem of a token is and whether stemming will based on an algorithm, dictionary, or mixed approach.</description>
374 </implementation-defined-item>
375
376 <implementation-defined-item
377 name="Query Token In Stopword List"
378 spec="XQueryFullText"
379 value="The query token is compared (case insensitively) against the list of stop words for an exact match.">
380 <description last-mod="2010-09-16">An implementation-defined comparison is used to determine whether a query token appears in the collection of stop words defined by the applicable stop word option.</description>
381 </implementation-defined-item>
382
383 <implementation-defined-item
384 name="StopWord Option Match Number"
385 spec="XQueryFullText"
386 value="Zorba has no such conditions.">
387 <description last-mod="2010-09-17">Normally a stop word matches exactly one token, but there may be implementation-defined conditions, under which a stop word may match a different number of tokens.</description>
388 </implementation-defined-item>
389
390 <implementation-defined-item
391 name="StopWord Option Default"
392 spec="XQueryFullText"
393 value="For each of the supported languages, Zorba defines a set of default stop-words (too big to be listed here).">
394 <description last-mod="2010-09-17">The "stop words default" option specifies that an implementation-defined collection of stop words is used.</description>
395 </implementation-defined-item>
396
397 <implementation-defined-item
398 name="Extension Option"
399 spec="XQueryFullText"
400 value="Zorba implements no extension options.">
401 <description last-mod="2010-09-17">An implementation recognizes an implementation-defined set of namespace URIs used to denote extension options. The effect of each, including its error behavior, is implementation-defined.</description>
402 </implementation-defined-item>
403
404 <implementation-defined-item
405 name="Extension Selection"
406 spec="XQueryFullText"
407 value="Zorba implements no extension pragmas.">
408 <description last-mod="2010-09-17">An implementation recognizes an implementation-defined set of namespace URIs used to denote extension selection pragmas. The effect of each, including its error behavior, is implementation-defined.</description>
409 </implementation-defined-item>
410
411 <implementation-defined-item
412 name="Equal Items Different Tokens"
413 spec="XQueryFullText"
414 value="If items are equal, the tokens will also be equal.">
415 <description last-mod="2010-09-16">The conditions under which tokenization of two equal items produces different tokens is implementation-defined.</description>
416 </implementation-defined-item>
417
418 <implementation-defined-item
419 name="FTIgnoreOption"
420 spec="XQueryFullText"
421 value="Zorba imposes no restriction; however, the FTIgnoreOption implementation is incomplete.">
422 <description last-mod="2010-09-17">An implementation may impose an implementation-defined restriction on the operand of FTIgnoreOption.</description>
423 </implementation-defined-item>
424
425 <implementation-defined-item
426 name="Static Context Items"
427 spec="XQueryFullText"
428 value="FTThesaurusOption has no default value. FTLanguageOption is set to whatever the host's language is. Statically known languages: The ISO 639-1 codes are: da, de, en, es, fi, hu, it, nl, no, pt, sv, ru.">
429 <description last-mod="2010-09-17">For certain full-text components of the static context (see C Static Context Components), the default initial value of the component can be overwritten or augmented with an implementation-defined value or values.</description>
430 </implementation-defined-item>
431
66 </implementation-defined-items>432 </implementation-defined-items>
67 433
434
68 <features>435 <features>
69 <feature name="Minimal Conformance" supported='true' />436 <feature
70 <feature name="FTMildNot Operator" supported='true' />437 name="Minimal Conformance"
71 <feature name="FTUnaryNot Operator" supported='true' />438 supported='true' />
72 <feature name="FTUnit and FTBigUnit" supported='true' />439
73 <feature name="FTOrder Operator" supported='true' />440 <feature
74 <feature name="FTScope Operator" supported='true' />441 name="FTMildNot Operator"
75 <feature name="FTWindow Operator" supported='true' />442 supported='true' />
76 <feature name="FTDistance Operator" supported='true' />443
77 <feature name="FTTimes Operator" supported='true' />444 <feature
78 <feature name="FTContent Operator" supported='true' />445 name="FTUnaryNot Operator"
79 <feature name="FTCaseOption" supported='true' />446 supported='true' />
80 <feature name="FTStopwordOption" supported='true' />447
81 <feature name="FTLanguageOption" supported='true' />448 <feature
82 <feature name="FTIgnoreOption" supported='false' />449 name="FTUnit and FTBigUnit"
83 <feature name="Scoring" supported='false' />450 supported='true' />
84 <feature name="Weights" supported='false' />451
452 <feature
453 name="FTOrder Operator"
454 supported='true' />
455
456 <feature
457 name="FTScope Operator"
458 supported='true' />
459
460 <feature
461 name="FTWindow Operator"
462 supported='true' />
463
464 <feature
465 name="FTDistance Operator"
466 supported='true' />
467
468 <feature
469 name="FTTimes Operator"
470 supported='true' />
471
472 <feature
473 name="FTContent Operator"
474 supported='true' />
475
476 <feature
477 name="FTCaseOption"
478 supported='true' />
479
480 <feature
481 name="FTStopwordOption"
482 supported='true' />
483
484 <feature
485 name="FTLanguageOption"
486 supported='true' />
487
488 <feature
489 name="FTIgnoreOption"
490 supported='false' />
491
492 <feature
493 name="Scoring"
494 supported='false' />
495
496 <feature
497 name="Weights"
498 supported='false' />
499
85 </features>500 </features>
86 501
87 <context-properties> 502 <context-properties>
88 <context-property name="Statically known namespaces" context-type="static" value="fn –> http://www.w3.org/2005/xpath-functions, xml –> http://www.w3.org/XML/1998/namespace, xs –> http://www.w3.org/2001/XMLSchema, xsi –> http://www.w3.org/2001/XMLSchema-instance, local –> http://www.w3.org/2005/xquery-local-functions, zerr –> http://www.zorba-xquery.com/"/>503 <context-property
89 <context-property name="Default element/type namespace" context-type="static" value="None."/>504 spec="XQuery"
90 <context-property name="Default function namespace" context-type="static" value="http://www.w3.org/2005/xpath-functions ."/>505 name="Statically known namespaces"
91 <context-property name="In-scope schema types" context-type="static" value="Built-in types in xs."/>506 context-type="static"
92 <context-property name="In-scope element declarations" context-type="static" value="None."/>507 value="fn –> http://www.w3.org/2005/xpath-functions, xml –> http://www.w3.org/XML/1998/namespace, xs –> http://www.w3.org/2001/XMLSchema, xsi –> http://www.w3.org/2001/XMLSchema-instance, local –> http://www.w3.org/2005/xquery-local-functions, zerr –> http://www.zorba-xquery.com/errors"/>
93 <context-property name="In-scope attribute declarations" context-type="static" value="None."/>508
94 <context-property name="In-scope variables" context-type="static" value="None."/>509 <context-property
95 <context-property name="Context item static type" context-type="static" value="item()"/>510 spec="XQuery"
96 <context-property name="Function signatures" context-type="static" value="Functions in fn namespace, and constructors for built-in atomic types."/>511 name="Default element/type namespace"
97 <context-property name="Statically known collations" context-type="static" value="http://www.w3.org/2005/xpath-functions/collation/codepoint"/>512 context-type="static"
98 <context-property name="Default collation" context-type="static" value="http://www.w3.org/2005/xpath-functions/collation/codepoint"/>513 value="None."/>
99 <context-property name="Construction mode" context-type="static" value="preserve"/>514
100 <context-property name="Ordering mode" context-type="static" value="ordered"/>515 <context-property
101 <context-property name="Default order for empty sequences" context-type="static" value="empty greatest"/>516 spec="XQuery"
102 <context-property name="Boundary-space policy" context-type="static" value="strip"/>517 name="Default function namespace"
103 <context-property name="Copy-namespaces mode" context-type="static" value="inherit preserve"/>518 context-type="static"
104 <context-property name="Base URI" context-type="static" value="Uses the rules in http://www.w3.org/TR/xquery-30/#id-base-uri-decl, where the implementation-defined default mentioned there is http://www.zorba-xquery.com"/>519 value="http://www.w3.org/2005/xpath-functions ."/>
105 <context-property name="Statically known documents" context-type="static" value="None."/>520
106 <context-property name="Statically known collections" context-type="static" value="None."/>521 <context-property
107 <context-property name="Statically known default collection type" context-type="static" value="item()*"/>522 spec="XQuery"
108 <context-property name="Context item" context-type="dynamic" value="None. Before execution of a query, a value can be assigned to the context itemvia the DynamicContext::setContextItem method."/>523 name="In-scope schema types"
109 <context-property name="Context position" context-type="dynamic" value="None."/>524 context-type="static"
110 <context-property name="Context size" context-type="dynamic" value="None."/>525 value="Built-in types in xs."/>
111 <context-property name="Variable values" context-type="dynamic" value="None."/>526
112 <context-property name="Function implementations" context-type="dynamic" value="Functions in fn namespace, and constructors for built-in atomic types."/>527 <context-property
113 <context-property name="Current dateTime" context-type="dynamic" value="The current local time on the computer running Zorba."/>528 spec="XQuery"
114 <context-property name="Implicit timezone" context-type="dynamic" value="Computed based on the current local time on the computer running Zorba."/>529 name="In-scope element declarations"
115 <context-property name="Available documents" context-type="dynamic" value="The URIs returned by the availale-documents function of module http://www.zorba-xquery.com/modules/store/dynamic/documents (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_documents.html)"/>530 context-type="static"
116 <context-property name="Available collections" context-type="dynamic" value="The URIs returned by the availale-collections function of module http://www.zorba-xquery.com/modules/store/dynamic/collections/w3c/ddl (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_collections_w3c_ddl.html)"/>531 value="None."/>
117 <context-property name="Default collection" context-type="dynamic" value="None."/>532
118 <context-property name="FTCaseOption" context-type="static" value=""/>533 <context-property
119 <context-property name="FTDiacriticsOption" context-type="static" value=""/>534 spec="XQuery"
120 <context-property name="FTStemOption" context-type="static" value=""/>535 name="In-scope attribute declarations"
121 <context-property name="FTThesaurusOption" context-type="static" value=""/>536 context-type="static"
122 <context-property name="Statically known thesauri" context-type="static" value="http://wordnet.princeton.edu/"/>537 value="None."/>
123 <context-property name="FTStopWordOption" context-type="static" value=""/>538
124 <context-property name="Statically known stop word lists" context-type="static" value="Zorba uses the publicly available lists found here http://snowball.tartarus.org."/>539 <context-property
125 <context-property name="FTLanguageOption" context-type="static" value=""/>540 spec="XQuery"
126 <context-property name="Statically known languages" context-type="static" value=""/>541 name="In-scope variables"
127 <context-property name="FTWildcardOption" context-type="static" value=""/>542 context-type="static"
543 value="None."/>
544
545 <context-property
546 spec="XQuery"
547 name="Context item static type"
548 context-type="static"
549 value="item()"/>
550
551 <context-property
552 spec="XQuery"
553 name="Function signatures"
554 context-type="static"
555 value="Functions in fn namespace, and constructors for built-in atomic types."/>
556
557 <context-property
558 spec="XQuery"
559 name="Statically known collations"
560 context-type="static"
561 value="Initially, the only available collation is the codepoint collection: http://www.w3.org/2005/xpath-functions/collation/codepoint. More collations can be added to a static context via the StaticContext::addCollation() method of the C++ API."/>
562
563 <context-property
564 spec="XQuery"
565 name="Default collation"
566 context-type="static"
567 value="http://www.w3.org/2005/xpath-functions/collation/codepoint"/>
568
569 <context-property
570 spec="XQuery"
571 name="Construction mode"
572 context-type="static"
573 value="preserve"/>
574
575 <context-property
576 spec="XQuery"
577 name="Ordering mode"
578 context-type="static"
579 value="ordered"/>
580
581 <context-property
582 spec="XQuery"
583 name="Default order for empty sequences"
584 context-type="static"
585 value="empty greatest"/>
586
587 <context-property
588 spec="XQuery"
589 name="Boundary-space policy"
590 context-type="static"
591 value="strip"/>
592
593 <context-property
594 spec="XQuery"
595 name="Copy-namespaces mode"
596 context-type="static"
597 value="inherit preserve"/>
598
599 <context-property
600 spec="XQuery"
601 name="Base URI"
602 context-type="static"
603 value="Uses the rules in http://www.w3.org/TR/xquery-30/#id-base-uri-decl, where the implementation-defined default mentioned there is http://www.zorba-xquery.com"/>
604
605 <context-property
606 spec="XQuery"
607 name="Statically known documents"
608 context-type="static"
609 value="None."/>
610
611 <context-property
612 spec="XQuery"
613 name="Statically known collections"
614 context-type="static"
615 value="None."/>
616
617 <context-property
618 spec="XQuery"
619 name="Statically known default collection type"
620 context-type="static"
621 value="item()*"/>
622
623 <context-property
624 spec="XQuery"
625 name="Context item"
626 context-type="dynamic"
627 value="None. Before execution of a query, a value can be assigned to the context item via the DynamicContext::setContextItem method."/>
628
629 <context-property
630 spec="XQuery"
631 name="Context position"
632 context-type="dynamic"
633 value="None."/>
634
635 <context-property
636 spec="XQuery"
637 name="Context size"
638 context-type="dynamic"
639 value="None."/>
640
641 <context-property
642 spec="XQuery"
643 name="Variable values"
644 context-type="dynamic"
645 value="None."/>
646
647 <context-property
648 spec="XQuery"
649 name="Function implementations"
650 context-type="dynamic"
651 value="Functions in fn namespace, and constructors for built-in atomic types."/>
652
653 <context-property
654 spec="XQuery"
655 name="Current dateTime"
656 context-type="dynamic"
657 value="The current local time (when the XQuery execution is actually started) on the computer running Zorba."/>
658
659 <context-property
660 spec="XQuery"
661 name="Implicit timezone"
662 context-type="dynamic"
663 value="Computed based on the current local time on the computer running Zorba."/>
664
665 <context-property
666 spec="XQuery"
667 name="Available documents"
668 context-type="dynamic"
669 value="The URIs returned by the availale-documents function of module http://www.zorba-xquery.com/modules/store/dynamic/documents (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_documents.html)"/>
670
671 <context-property
672 spec="XQuery"
673 name="Available collections"
674 context-type="dynamic"
675 value="The URIs returned by the available-collections function of module http://www.zorba-xquery.com/modules/store/dynamic/collections/w3c/ddl (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_collections_w3c_ddl.html)"/>
676
677 <context-property
678 spec="XQuery"
679 name="Default collection"
680 context-type="dynamic"
681 value="None."/>
682
683 <context-property
684 spec="XQueryFullText"
685 name="FTCaseOption"
686 context-type="static"
687 value="case insensitive"/>
688
689 <context-property
690 spec="XQueryFullText"
691 name="FTDiacriticsOption"
692 context-type="static"
693 value="diacritics insensitive"/>
694
695 <context-property
696 spec="XQueryFullText"
697 name="FTStemOption"
698 context-type="static"
699 value="no stemming"/>
700
701 <context-property
702 spec="XQueryFullText"
703 name="FTThesaurusOption"
704 context-type="static"
705 value=""/>
706
707 <context-property
708 spec="XQueryFullText"
709 name="Statically known thesauri"
710 context-type="static"
711 value="http://wordnet.princeton.edu/"/>
712
713 <context-property
714 spec="XQueryFullText"
715 name="FTStopWordOption"
716 context-type="static"
717 value="no stop words"/>
718
719 <context-property
720 spec="XQueryFullText"
721 name="Statically known stop word lists"
722 context-type="static"
723 value="Zorba uses the publicly available lists found here http://snowball.tartarus.org."/>
724
725 <context-property
726 spec="XQueryFullText"
727 name="FTLanguageOption"
728 context-type="static"
729 value="Whatever the host's language is."/>
730
731 <context-property
732 spec="XQueryFullText"
733 name="Statically known languages"
734 context-type="static"
735 value="The ISO 639-1 codes are: da, de, en, es, fi, hu, it, nl, no, pt, sv, ru."/>
736
737 <context-property
738 spec="XQueryFullText"
739 name="FTWildcardOption"
740 context-type="static"
741 value="no wildcards "/>
742
128 </context-properties>743 </context-properties>
744
129</zorba>745</zorba>
130746
=== modified file 'test/rbkt/Scripts/w3c/XQTS.xml'
--- test/rbkt/Scripts/w3c/XQTS.xml 2011-09-22 16:08:42 +0000
+++ test/rbkt/Scripts/w3c/XQTS.xml 2011-10-05 20:32:28 +0000
@@ -1,273 +1,450 @@
1<?xml version="1.0" encoding="UTF-8"?>1<?xml version="1.0" encoding="UTF-8"?>
2<zorba xmlns="http://www.w3.org/2005/02/query-test-XQTSResult"> 2<zorba xmlns="http://www.w3.org/2005/02/query-test-XQTSResult">
3 <implementation-defined-items>3 <implementation-defined-items>
4
5 <implementation-defined-item 4 <implementation-defined-item
6 name="expressionUnicode" 5 name="expressionUnicode"
7 value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0."/>6 spec="XQuery"
87 value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0.">
9 <implementation-defined-item 8 <description last-mod="2005-04-04">The version of Unicode that is used to construct expressions.</description>
10 name="collations" 9 </implementation-defined-item>
11 value="Initially, the only available collation is the codepoint collection: http://www.w3.org/2005/xpath-functions/collation/codepoint. More collations can be added to a static context via the StaticContext::addCollation() method of the C++ API."/>10
1211 <implementation-defined-item
13 <implementation-defined-item 12 name="collations"
14 name="implicitTimezone" 13 spec="XQuery"
15 value="The implicit timezone is computed based on the current local time of the computer running Zorba."/>14 value="http://www.w3.org/2005/xpath-functions/collation/codepoint">
1615 <description last-mod="2005-04-04">The statically-known collations.</description>
17 <implementation-defined-item 16 </implementation-defined-item>
18 name="warningsMethod" 17
19 value="Warnings are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html. For the list of all warnings, see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_warnings.html"/>18 <implementation-defined-item
2019 name="implicitTimezone"
21 <implementation-defined-item 20 spec="XQuery"
22 name="errorsMethod" 21 value="The implicit timezone is computed based on the current local time of the computer running Zorba.">
23 value="Errors are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html."/>22 <description last-mod="2005-04-04">The implicit timezone.</description>
2423 </implementation-defined-item>
25 <implementation-defined-item24
26 name="XMLVersion" 25 <implementation-defined-item
27 value="XML 1.0"/>26 name="warningsMethod"
2827 spec="XQuery"
29 <implementation-defined-item28 value="Warnings are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html and http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_warnings.html.">
30 name="overwrittenContextComponents" 29 <description last-mod="2005-04-04">The circumstances in which warnings are raised, and the ways in which warnings are handled.</description>
31 value="The following static context components are overwrtten/augmented: 1. Statically known namespaces: Augmented with zerr –> http://www.zorba-xquery.com/errors 2. Context item static type: item() 3. Default order for empty sequences: empty_greatest 4. Static Base URI: We use the rules in 4.5, where the implementation-defined default mentioned there is http://www.zorba-xquery.com, 5. Statically known default collection type: item()*"/>30 </implementation-defined-item>
3231
33 <implementation-defined-item 32 <implementation-defined-item
34 name="axes" 33 name="errorsMethod"
35 value="All axes are supported"/>34 spec="XQuery"
3635 value="Errors are handled via instances of the zorba::DiagnosticHandler class. For details, see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler.html.">
37 <implementation-defined-item 36 <description last-mod="2005-04-04">The method by which errors are reported to the external processing environment.</description>
38 name="defaultOrderEmpty" 37 </implementation-defined-item>
39 value="empty_greatest"/>38
4039 <implementation-defined-item
41 <implementation-defined-item 40 name="XMLVersion"
42 name="pragmas" 41 spec="XQuery"
43 value="No pragmas are recognized."/>42 value="XML 1.0">
4443 <description last-mod="2005-10-10">Whether the implementation is based on the rules of [XML 1.0] and [XML Names] or the rules of [XML 1.1] and [XML Names 1.1]. One of these sets of rules must be applied consistently by all aspects of the implementation.</description>
45 <implementation-defined-item 44 </implementation-defined-item>
46 name="optionDeclarations" 45
47 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/options_and_annotations.html."/>46 <implementation-defined-item
4847 name="overwrittenContextComponents"
49 <implementation-defined-item 48 spec="XQuery"
50 name="externalFunctionProtocols" 49 value="The following static context components are overwritten/augmented: 1. Statically known namespaces: Augmented with zerr –> http://www.zorba-xquery.com/errors 2. Context item static type: item() 3. Default order for empty sequences: empty_greatest 4. Static Base URI: We use the rules in 4.5, where the implementation-defined default mentioned there is http://www.zorba-xquery.com, 5. Statically known default collection type: item()*">
51 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/external_functions.html."/>50 <description last-mod="2005-04-04">Any components of the static context or dynamic context that are overwritten or augmented by the implementation.</description>
5251 </implementation-defined-item>
53 <implementation-defined-item 52
54 name="moduleLocationHints" 53 <implementation-defined-item
55 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/modules_top.html."/>54 name="axes"
5655 spec="XQuery"
57 <implementation-defined-item 56 value="All axes are supported">
58 name="staticTypingExtensions" 57 <description last-mod="2005-04-04">Which of the optional axes are supported by the implementation, if the Full-Axis Feature is not supported.</description>
59 value="Static typing is not supported."/>58 </implementation-defined-item>
6059
61 <implementation-defined-item 60 <implementation-defined-item
62 name="serializationInvocation" 61 name="defaultOrderEmpty"
63 value="The result of an XQuery program can be serialized via the zorba::XQuery::execute methods (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1XQuery.html). Sequence of items can be serialized via the zorba::Serializer::serialize method (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1Serializer.html)."/>62 spec="XQuery"
6463 value="empty_greatest">
64 <description last-mod="2005-04-04">The default handling of empty sequences returned by an ordering key (sortspec) in an order by clause (empty least or empty greatest).</description>
65 </implementation-defined-item>
66
67 <implementation-defined-item
68 name="pragmas"
69 spec="XQuery"
70 value="No pragmas are recognized.">
71 <description last-mod="2005-04-04">The names and semantics of any extension expressions (pragmas) recognized by the implementation.</description>
72 </implementation-defined-item>
73
74 <implementation-defined-item
75 name="optionDeclarations"
76 spec="XQuery"
77 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/options_and_annotations.html.">
78 <description last-mod="2005-04-04">The names and semantics of any option declarations recognized by the implementation.</description>
79 </implementation-defined-item>
80
81 <implementation-defined-item
82 name="externalFunctionProtocols"
83 spec="XQuery"
84 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/external_functions.html.">
85 <description last-mod="2005-04-04">Protocols (if any) by which parameters can be passed to an external function, and the result of the function can returned to the invoking query.</description>
86 </implementation-defined-item>
87
88 <implementation-defined-item
89 name="moduleLocationHints"
90 spec="XQuery"
91 value="See http://www.zorba-xquery.com/site2/doc/latest/zorba/html/modules_top.html.">
92 <description last-mod="2005-11-01">The process by which the specific modules to be imported by a module import are identified, if the Module Feature is supported (includes processing of location hints, if any.)</description>
93 </implementation-defined-item>
94
95 <implementation-defined-item
96 name="staticTypingExtensions"
97 spec="XQuery"
98 value="Static typing is not supported.">
99 <description last-mod="2005-04-04">Any static typing extensions supported by the implementation, if the Static Typing Feature is supported.</description>
100 </implementation-defined-item>
101
102 <implementation-defined-item
103 name="serializationInvocation"
104 spec="XQuery"
105 value="The result of an XQuery program can be serialized via the zorba::XQuery::execute methods (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1XQuery.html). Sequence of items can be serialized via the zorba::Serializer::serialize method (see http://www.zorba-xquery.com/site2/doc/latest/cxx/html/classzorba_1_1Serializer.html).">
106 <description last-mod="2005-04-04">The means by which serialization is invoked, if the Serialization Feature is supported.</description>
107 </implementation-defined-item>
108
65 <implementation-defined-item 109 <implementation-defined-item
66 name="serializationDefaults" 110 name="serializationDefaults"
67 value="Serialization Feature is supported. Implicit values are: byte-order-mark = no, encoding = UTF-8, media-type = '', normalization-form = '', omix-xml-declaration = no, standalone = omit, version = '1.0', method = xml, doctype-system = '', doctype-public = '', cdata-section-elements = empty list, include-content-type = no, undeclare-prefixes = no, indent = no"/>111 spec="XQuery"
68112 value="Serialization Feature is supported. Implicit values are: byte-order-mark = no, encoding = UTF-8, media-type = '', normalization-form = '', omix-xml-declaration = no, standalone = omit, version = '1.0', method = xml, doctype-system = '', doctype-public = '', cdata-section-elements = empty list, include-content-type = no, undeclare-prefixes = no, indent = no">
69 <implementation-defined-item 113 <description last-mod="2005-10-10">The default values for the byte-order-mark, encoding, media-type, normalization-form, omit-xml-declaration, standalone, and version parameters, if the Serialization Feature is supported.</description>
70 name="externalFunctionCall" 114 </implementation-defined-item>
71 value="An error is raised using the regular error handling mechanism of zorba. The kind of error depends on the kind of failure. For example, zerr:ZXQP0008 if the function implementation is not found, or err:XPTY0004 if the result of the function does not match the declared returned type."/>115
72116 <implementation-defined-item
73 <implementation-defined-item name="limits" value=""/>117 name="externalFunctionCall"
74118 spec="XQuery"
75 <implementation-defined-item 119 value="An error is raised using the regular error handling mechanism of zorba. The kind of error depends on the kind of failure. For example, zerr:ZXQP0008 if the function implementation is not found, or err:XPTY0004 if the result of the function does not match the declared returned type.">
76 name="traceDestination" 120 <description last-mod="2006-08-09">The result of an unsuccessful call to an external function (for example, if the function implementation cannot be found or does not return a value of the declared type).</description>
77 value="By default, it is std:cerr. Users can modify this via the StaticContext::setTraceStream method."/>121 </implementation-defined-item>
78122
79 <implementation-defined-item 123 <implementation-defined-item
80 name="integerOperations" 124 name="limits"
81 value="Zorba raises [err:FOAR0002]"/>125 spec="XQuery"
82126 value="totalDigits = 2^63, xs:string length = available memory.">
83 <implementation-defined-item name="decimalDigits" value=""/>127 <description last-mod="2005-11-01">Limits on ranges of values for various data types, as enumerated in 5.3 Data Model Conformance.</description>
84128 </implementation-defined-item>
85 <implementation-defined-item name="roundOrTruncate" value=""/>129
86130 <implementation-defined-item
87 <implementation-defined-item 131 name="traceDestination"
88 name="Unicode" 132 spec="FuncOps"
89 value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0."/>133 value="By default, it is std:cerr. Users can modify this via the StaticContext::setTraceStream method.">
90134 <description last-mod="2005-10-10">The destination of the trace output is implementation-defined. See 4 The Trace Function.</description>
91 <implementation-defined-item 135 </implementation-defined-item>
92 name="normalizationForms" 136
93 value="Zorba supports NFC, NFKC, NFD, NFKD normalization forms."/>137 <implementation-defined-item
94138 name="integerOperations"
95 <implementation-defined-item name="collationUnits" value=""/>139 spec="FuncOps"
96140 value="Zorba raises [err:FOAR0002]">
141 <description last-mod="2005-10-10">For xs:integer operations, implementations that support limited-precision integer operations must either raise an error [err:FOAR0002] or provide an implementation-defined mechanism that allows users to choose between raising an error and returning a result that is modulo the largest representable integer value. See 6.2 Operators on Numeric Values.</description>
142 </implementation-defined-item>
143
144 <implementation-defined-item
145 name="decimalDigits"
146 spec="FuncOps"
147 value="On a 32-bit system, the number of digits of precision is 2^31; on a 64-bit system, the number of digits of precision is 2^63.">
148 <description last-mod="2005-11-01">For xs:decimal values the number of digits of precision returned by the numeric operators is implementation-defined. See 6.2 Operators on Numeric Values. See also 17.1.3.3 Casting to xs:decimal and 17.1.3.4 Casting to xs:integer.</description>
149 </implementation-defined-item>
150
151 <implementation-defined-item
152 name="roundOrTruncate"
153 spec="FuncOps"
154 value="It does whatever the underlying C++ implementation does.">
155 <description last-mod="2005-10-10">If the number of digits in the result exceeds the number of digits that the implementation supports, the result is truncated or rounded in an implementation-defined manner. See 6.2 Operators on Numeric Values. See also 17.1.3.3 Casting to xs:decimal and 17.1.3.4 Casting to xs:integer.</description>
156 </implementation-defined-item>
157
158 <implementation-defined-item
159 name="Unicode"
160 spec="FuncOps"
161 value="Zorba's Unicode version is whatever ICU's Unicode is. Latest ICU supports Unicode 6.0.">
162 <description last-mod="2005-11-01">It is implementation-defined which version of Unicode is supported by the features defined in this specification, but it is recommended that the most recent version of Unicode be used. See 7.1 String Types.</description>
163 </implementation-defined-item>
164
165 <implementation-defined-item
166 name="normalizationForms"
167 spec="FuncOps"
168 value="Zorba supports NFC, NFKC, NFD, NFKD normalization forms.">
169 <description last-mod="2005-10-10">For 7.4.6 fn:normalize-unicode, conforming implementations must support normalization form "NFC" and may support normalization forms "NFD", "NFKC", "NFKD", "FULLY-NORMALIZED". They may also support other normalization forms with implementation-defined semantics.</description>
170 </implementation-defined-item>
171
172 <implementation-defined-item
173 name="collationUnits"
174 spec="FuncOps"
175 value="Zorba does not support this.">
176 <description last-mod="2005-10-10">The ability to decompose strings into collation units suitable for substring matching is an implementation-defined property of a collation. See 7.5 Functions Based on Substring Matching.</description>
177 </implementation-defined-item>
178
97 <implementation-defined-item 179 <implementation-defined-item
98 name="secondsDigits" 180 name="secondsDigits"
99 value="Year values: Zorba supports 9 digits (32bit maxint). Fractional second: Zorba supports 6 digits."/>181 spec="FuncOps"
100182 value="Year values: Zorba supports 9 digits (32bit maxint). Fractional second: Zorba supports 6 digits.">
101 <implementation-defined-item name="stringToDecimal" value=""/>183 <description last-mod="2005-10-10">All minimally conforming processors must support year values with a minimum of 4 digits (i.e., YYYY) and a minimum fractional second precision of 1 millisecond or three digits (i.e., s.sss). However, conforming processors may set larger implementation-defined limits on the maximum number of digits they support in these two situations. See 10.1.1 Limits and Precision.</description>
102184 </implementation-defined-item>
103 <implementation-defined-item name="docProcessing" value=""/>185
104186 <implementation-defined-item
105 <implementation-defined-item name="weakenStable" value=""/>187 name="stringToDecimal"
106188 spec="FuncOps"
107 <implementation-defined-item 189 value="On a 32-bit system, the number of digits of precision is 2^31; on a 64-bit system, the number of digits of precision is 2^63.">
108 name="additionalTypes" 190 <description last-mod="2006-08-09">The result of casting a string to xs:decimal, when the resulting value is not too large or too small but nevertheless has too many decimal digits to be accurately represented, is implementation-defined. See 17.1.1 Casting from xs:string and xs:untypedAtomic.</description>
109 value="There are no implementation-defined types. User-defined types are created and become “in-scope” when “import schema” statements are processed. User-defined types (including anonymous types) are created within a static context and they are destroyed when their containing static context is destroyed."/>191 </implementation-defined-item>
110192
111 <implementation-defined-item 193 <implementation-defined-item
112 name="undefinedProperties" 194 name="docProcessing"
113 value="err:FOTY0012"/>195 spec="FuncOps"
114196 value="Zorba provides no configuration options for 15.5.4 fn:doc.">
115 <implementation-defined-item 197 <description last-mod="2005-10-10">Various aspects of the processing provided by 15.5.4 fn:doc are implementation-defined. Implementations may provide external configuration options that allow any aspect of the processing to be controlled by the user.</description>
116 name="sequenceNormalization" 198 </implementation-defined-item>
117 value="Zorba performs sequence normalization for the 'binary' serialization method. Zorba's Data Converters module performs sequence normalization for JSON and JSONML (but these are not serialization output methods, i.e. they cannot be invoked with the help of '-z method=JSON')"/>199
118200 <implementation-defined-item
119 <implementation-defined-item 201 name="weakenStable"
120 name="outputMethods" 202 spec="FuncOps"
121 value="Zorba's only implementation-defined output method is 'binary' and it is used unqualified (URI is null)."/>203 value="Zorba provides no options to weaken the stable characteristics of 15.5.6 fn:collection or 15.5.4 fn:doc.">
122204 <description last-mod="2006-08-09">The manner in which implementations provide options to weaken the stable characteristic of 15.5.6 fn:collection and 15.5.4 fn:doc are implementation-defined.</description>
123 <implementation-defined-item 205 </implementation-defined-item>
124 name="normalizationFormBehavior" 206
125 value="Zorba has no implementation-defined values for the normalization-form parameter."/>207 <implementation-defined-item
126208 name="additionalTypes"
127 <implementation-defined-item 209 spec="DataModel"
128 name="additionalParams" 210 value="There are no implementation-defined types. User-defined types are created and become “in-scope” when “import schema” statements are processed. User-defined types (including anonymous types) are created within a static context and they are destroyed when their containing static context is destroyed.">
129 value="Zorba has no implementation-defined serialization parameters."/>211 <description last-mod="2005-04-04">Support for additional user-defined or implementation-defined types is implementation-defined. (See 2.6.1 Representation of Types)</description>
130212 </implementation-defined-item>
131 <implementation-defined-item 213
132 name="encodingPhase" 214 <implementation-defined-item
133 value="Zorba has no such option."/>215 name="undefinedProperties"
134216 spec="DataModel"
135 <implementation-defined-item 217 value="err:FOTY0012">
136 name="CDATASerialization" 218 <description last-mod="2005-04-04">Some typed values in the data model are undefined. Attempting to access an undefined property is always an error. Behavior in these cases is implementation-defined and the host language is responsible for determining the result. (See 5 Accessors)</description>
137 value="Zorba has no such mechanism."/>219 </implementation-defined-item>
220
221 <implementation-defined-item
222 name="sequenceNormalization"
223 spec="Serialization"
224 value="Zorba performs sequence normalization for the 'binary' serialization method. Zorba's Data Converters module performs sequence normalization for JSON and JSONML (but these are not serialization output methods, i.e. they cannot be invoked with the help of '-z method=JSON')">
225 <description last-mod="2005-04-04">For any implementation-defined output method, it is implementation-defined whether sequence normalization process takes place. (See 2 Sequence Normalization)</description>
226 </implementation-defined-item>
227
228 <implementation-defined-item
229 name="outputMethods"
230 spec="Serialization"
231 value="Zorba's only implementation-defined output method is 'binary' and it is used unqualified (URI is null).">
232 <description last-mod="2005-04-04">If the namespace URI is non-null for the method serialization parameter, then the parameter specifies an implementation-defined output method. (See 3 Serialization Parameters)</description>
233 </implementation-defined-item>
234
235 <implementation-defined-item
236 name="normalizationFormBehavior"
237 spec="Serialization"
238 value="Zorba has no implementation-defined values for the normalization-form parameter.">
239 <description last-mod="2005-04-04">If the value of the normalization-form form parameter is not NFC, NFD, NFKC, NFKD, fully-normalized, or none then the meaning of the value and it's effect is implementation-defined. (See 4 Phases of Serialization)</description>
240 </implementation-defined-item>
241
242 <implementation-defined-item
243 name="additionalParams"
244 spec="Serialization"
245 value="Zorba has no implementation-defined serialization parameters.">
246 <description last-mod="2005-11-01">The effect of additional serialization parameters on the output of the serializer, where the name of such a parameter must be namespace-qualified, is implementation-defined or implementation-dependent. The extent of this effect on the output must not override the provisions of this specification. (See 3 Serialization Parameters)</description>
247 </implementation-defined-item>
248
249 <implementation-defined-item
250 name="encodingPhase"
251 spec="Serialization"
252 value="Zorba has no such option.">
253 <description last-mod="2005-04-04">The effect of providing an option that allows the encoding phase to be skipped, so that the result of serialization is a stream of Unicode characters, is implementation-defined. The serializer is not required to support such an option. (See 4 Phases of Serialization)</description>
254 </implementation-defined-item>
255
256 <implementation-defined-item
257 name="CDATASerialization"
258 spec="Serialization"
259 value="Input CDATA sections are treated and serialized as text. Text nodes can be serialized as cdata sections if explicitly requested through the cdata-section-elements parameter.">
260 <description last-mod="2005-04-04">An serializer may provide an implementation-defined mechanism to place CDATA sections in the result tree. (See 5.1.4 XML Output Method: the cdata-section-elements Parameter)</description>
261 </implementation-defined-item>
138262
139 </implementation-defined-items>263 </implementation-defined-items>
140 264
141 <features>265 <features>
142 <feature name="Minimal Conformance" supported="true"/>266 <feature
143 <feature name="Schema Import" supported="true"/>267 name="Minimal Conformance"
144 <feature name="Schema Validation" supported="true"/>268 supported="true"/>
145 <feature name="Static Typing" supported="false"/>269
146 <feature name="Static Typing Extensions" supported="false"/>270 <feature
147 <feature name="Full Axis" supported="true"/>271 name="Schema Import"
148 <feature name="Module" supported="true"/>272 supported="true"/>
149 <feature name="Serialization" supported="true"/>273
274 <feature
275 name="Schema Validation"
276 supported="true"/>
277
278 <feature
279 name="Static Typing"
280 supported="false"/>
281
282 <feature
283 name="Static Typing Extensions"
284 supported="false"/>
285
286 <feature
287 name="Full Axis"
288 supported="true"/>
289
290 <feature
291 name="Module"
292 supported="true"/>
293
294 <feature
295 name="Serialization"
296 supported="true"/>
150 </features>297 </features>
151 298
152 <context-properties>299 <context-properties>
153 <context-property 300 <context-property
154 name="Statically known namespaces" context-type="static" 301 name="Statically known namespaces"
155 value="fn –> http://www.w3.org/2005/xpath-functions, xml –> http://www.w3.org/XML/1998/namespace, xs –> http://www.w3.org/2001/XMLSchema, xsi –> http://www.w3.org/2001/XMLSchema-instance, local –> http://www.w3.org/2005/xquery-local-functions, zerr –> http://www.zorba-xquery.com/"/>302 context-type="static"
303 value="fn –> http://www.w3.org/2005/xpath-functions, xml –> http://www.w3.org/XML/1998/namespace, xs –> http://www.w3.org/2001/XMLSchema, xsi –> http://www.w3.org/2001/XMLSchema-instance, local –> http://www.w3.org/2005/xquery-local-functions, zerr –> http://www.zorba-xquery.com/errors"/>
156304
157 <context-property 305 <context-property
158 name="Default element/type namespace" context-type="static" 306 name="Default element/type namespace"
307 context-type="static"
159 value="None."/>308 value="None."/>
160309
161 <context-property 310 <context-property
162 name="Default function namespace" context-type="static" 311 name="Default function namespace"
312 context-type="static"
163 value="http://www.w3.org/2005/xpath-functions ."/>313 value="http://www.w3.org/2005/xpath-functions ."/>
164314
165 <context-property 315 <context-property
166 name="In-scope schema types" context-type="static" 316 name="In-scope schema types"
317 context-type="static"
167 value="Built-in types in xs."/>318 value="Built-in types in xs."/>
168319
169 <context-property 320 <context-property
170 name="In-scope element declarations" context-type="static" 321 name="In-scope element declarations"
171 value="None."/>322 context-type="static"
172323 value="None."/>
173 <context-property 324
174 name="In-scope attribute declarations" context-type="static" 325 <context-property
175 value="None."/>326 name="In-scope attribute declarations"
176327 context-type="static"
177 <context-property 328 value="None."/>
178 name="In-scope variables" context-type="static" 329
179 value="None."/>330 <context-property
180331 name="In-scope variables"
181 <context-property 332 context-type="static"
182 name="Context item static type" context-type="static" 333 value="None."/>
334
335 <context-property
336 name="Context item static type"
337 context-type="static"
183 value="item()"/>338 value="item()"/>
184339
185 <context-property 340 <context-property
186 name="Function signatures" context-type="static" 341 name="Function signatures"
342 context-type="static"
187 value="Functions in fn namespace, and constructors for built-in atomic types."/>343 value="Functions in fn namespace, and constructors for built-in atomic types."/>
188344
189 <context-property 345 <context-property
190 name="Statically known collations" context-type="static" 346 name="Statically known collations"
347 context-type="static"
191 value="Initially, the only available collation is the codepoint collection: http://www.w3.org/2005/xpath-functions/collation/codepoint. More collations can be added to a static context via the StaticContext::addCollation() method of the C++ API."/>348 value="Initially, the only available collation is the codepoint collection: http://www.w3.org/2005/xpath-functions/collation/codepoint. More collations can be added to a static context via the StaticContext::addCollation() method of the C++ API."/>
192349
193 <context-property 350 <context-property
194 name="Default collation" context-type="static" 351 name="Default collation"
352 context-type="static"
195 value="http://www.w3.org/2005/xpath-functions/collation/codepoint"/>353 value="http://www.w3.org/2005/xpath-functions/collation/codepoint"/>
196354
197 <context-property 355 <context-property
198 name="Construction mode" context-type="static" 356 name="Construction mode"
357 context-type="static"
199 value="preserve"/>358 value="preserve"/>
200359
201 <context-property 360 <context-property
202 name="Ordering mode" context-type="static" 361 name="Ordering mode"
362 context-type="static"
203 value="ordered"/>363 value="ordered"/>
204364
205 <context-property 365 <context-property
206 name="Default order for empty sequences" context-type="static" 366 name="Default order for empty sequences"
367 context-type="static"
207 value="empty greatest"/>368 value="empty greatest"/>
208369
209 <context-property 370 <context-property
210 name="Boundary-space policy" context-type="static" 371 name="Boundary-space policy"
372 context-type="static"
211 value="strip"/>373 value="strip"/>
212374
213 <context-property 375 <context-property
214 name="Copy-namespaces mode" context-type="static" 376 name="Copy-namespaces mode"
377 context-type="static"
215 value="inherit preserve"/>378 value="inherit preserve"/>
216379
217 <context-property 380 <context-property
218 name="Base URI" context-type="static" 381 name="Base URI"
382 context-type="static"
219 value="Uses the rules in http://www.w3.org/TR/xquery-30/#id-base-uri-decl, where the implementation-defined default mentioned there is http://www.zorba-xquery.com"/>383 value="Uses the rules in http://www.w3.org/TR/xquery-30/#id-base-uri-decl, where the implementation-defined default mentioned there is http://www.zorba-xquery.com"/>
220384
221 <context-property 385 <context-property
222 name="Statically known documents" context-type="static" 386 name="Statically known documents"
223 value="None."/>387 context-type="static"
224388 value="None."/>
225 <context-property 389
226 name="Statically known collections" context-type="static" 390 <context-property
227 value="None."/>391 name="Statically known collections"
228392 context-type="static"
229 <context-property 393 value="None."/>
230 name="Statically known default collection type" context-type="static" 394
395 <context-property
396 name="Statically known default collection type"
397 context-type="static"
231 value="item()*"/>398 value="item()*"/>
232399
233 <context-property 400 <context-property
234 name="Context item" context-type="dynamic" 401 name="Context item"
235 value="None. Before execution of a query, a value can be assigned to the context itemvia the DynamicContext::setContextItem method."/>402 context-type="dynamic"
236403 value="None. Before execution of a query, a value can be assigned to the context item via the DynamicContext::setContextItem method."/>
237 <context-property 404
238 name="Context position" context-type="dynamic" 405 <context-property
239 value="None."/>406 name="Context position"
240407 context-type="dynamic"
241 <context-property 408 value="None."/>
242 name="Context size" context-type="dynamic" 409
243 value="None."/>410 <context-property
244411 name="Context size"
245 <context-property 412 context-type="dynamic"
246 name="Variable values" context-type="dynamic" 413 value="None."/>
247 value="None."/>414
248415 <context-property
249 <context-property 416 name="Variable values"
250 name="Function implementations" context-type="dynamic" 417 context-type="dynamic"
418 value="None."/>
419
420 <context-property
421 name="Function implementations"
422 context-type="dynamic"
251 value="Functions in fn namespace, and constructors for built-in atomic types."/>423 value="Functions in fn namespace, and constructors for built-in atomic types."/>
252424
253 <context-property 425 <context-property
254 name="Current dateTime" context-type="dynamic" 426 name="Current dateTime"
255 value="The current local time on the computer running Zorba."/>427 context-type="dynamic"
428 value="The current local time (when the XQuery execution is actually started) on the computer running Zorba."/>
256429
257 <context-property 430 <context-property
258 name="Implicit timezone" context-type="dynamic" 431 name="Implicit timezone"
432 context-type="dynamic"
259 value="Computed based on the current local time on the computer running Zorba."/>433 value="Computed based on the current local time on the computer running Zorba."/>
260434
261 <context-property 435 <context-property
262 name="Available documents" context-type="dynamic" 436 name="Available documents"
437 context-type="dynamic"
263 value="The URIs returned by the availale-documents function of module http://www.zorba-xquery.com/modules/store/dynamic/documents (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_documents.html)"/>438 value="The URIs returned by the availale-documents function of module http://www.zorba-xquery.com/modules/store/dynamic/documents (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_documents.html)"/>
264439
265 <context-property 440 <context-property
266 name="Available collections" context-type="dynamic" 441 name="Available collections"
267 value="The URIs returned by the availale-collections function of module http://www.zorba-xquery.com/modules/store/dynamic/collections/w3c/ddl (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_collections_w3c_ddl.html)"/>"/>442 context-type="dynamic"
443 value="The URIs returned by the available-collections function of module http://www.zorba-xquery.com/modules/store/dynamic/collections/w3c/ddl (see http://www.zorba-xquery.com/site2/doc/latest/zorba/xqdoc/xhtml/www.zorba-xquery.com_modules_store_dynamic_collections_w3c_ddl.html)"/>"/>
268444
269 <context-property 445 <context-property
270 name="Default collection" context-type="dynamic" 446 name="Default collection"
447 context-type="dynamic"
271 value="None."/>448 value="None."/>
272 </context-properties>449 </context-properties>
273 450
274451
=== modified file 'test/rbkt/Scripts/w3c/generate-submission-xqftts.xq'
--- test/rbkt/Scripts/w3c/generate-submission-xqftts.xq 2011-08-17 11:42:16 +0000
+++ test/rbkt/Scripts/w3c/generate-submission-xqftts.xq 2011-10-05 20:32:28 +0000
@@ -11,7 +11,7 @@
11 <test-suite-result>11 <test-suite-result>
12 <implementation12 <implementation
13 name="Zorba" 13 name="Zorba"
14 version='2.0 (svn rev. 11228)'14 version='2.0.3'
15 anonymous-result-column="false">15 anonymous-result-column="false">
16 16
17 <organization 17 <organization
@@ -32,21 +32,28 @@
32 database servers, XML message dispatchers, or smartphones.32 database servers, XML message dispatchers, or smartphones.
33 Its architecture employes a modular design, which allows customizing33 Its architecture employes a modular design, which allows customizing
34 the Zorba query processor to the environment’s needs.34 the Zorba query processor to the environment’s needs.
35 In particular the architecture of the query processor allows a35 For more details please check out http://www.zorba-xquery.com.</p>
36 pluggable XML store (e.g. main memory, DOM stores, persistent
37 disk-based large stores, S3 stores). Zorba runs on most platforms
38 and is available under the Apache license v2. Currently, Zorba
39 implements the following W3C specifications: XQuery 1.0, XQuery Update
40 Facility 1.0, XQuery Scripting Extension 1.0, and XSLT 2.0 and XQuery 1.0
41 Serialization.</p>
42 </description>36 </description>
4337
44 {38 {
45 let $XQFTTSZorba := fn:doc("XQFTTS.xml")39 let $XQFTTSZorba := fn:doc("XQFTTS.xml")
46 return40 return
47 (41 (
48 <implementation-defined-items>{$XQFTTSZorba//*:implementation-defined-item}</implementation-defined-items>,42 <implementation-defined-items>
43 {
44 for $idi in $XQFTTSZorba//*:implementation-defined-item
45 return
46 <implementation-defined-item name="{data($idi/@name)}" value="{data($idi/@value)}" />
47 }
48 </implementation-defined-items>,
49 <features>{$XQFTTSZorba//*:feature}</features>,49 <features>{$XQFTTSZorba//*:feature}</features>,
50 <context-properties>
51 {
52 for $cp in $XQFTTSZorba//*:context-property
53 return
54 <context-property name="{data($cp/@name)}" context-type="{data($cp/@context-type)}" value="{data($cp/@value)}" />
55 }
56 </context-properties>
50 <context-properties>{$XQFTTSZorba//*:context-property}</context-properties>57 <context-properties>{$XQFTTSZorba//*:context-property}</context-properties>
51 )58 )
52 }59 }
@@ -55,11 +62,11 @@
5562
56 <syntax>XQuery</syntax>63 <syntax>XQuery</syntax>
5764
58 <test-run dateRun="2011-07-13">65 <test-run dateRun="2011-09-23">
59 <test-suite version="current"/>66 <test-suite version="current"/>
60 <transformation><p>Standard</p></transformation>67 <transformation><p>Standard</p></transformation>
61 <comparison><p>Standard</p></comparison>68 <comparison><p>Standard</p></comparison>
62 <otherComments><p>XQFTTS taken from W3C CVS as of 2011-07-13.</p></otherComments>69 <otherComments><p>XQFTTS taken from W3C CVS as of 2011-09-21.</p></otherComments>
63 </test-run>70 </test-run>
6471
65 {72 {
6673
=== modified file 'test/rbkt/Scripts/w3c/generate-submission-xqts.xq'
--- test/rbkt/Scripts/w3c/generate-submission-xqts.xq 2011-08-17 11:42:16 +0000
+++ test/rbkt/Scripts/w3c/generate-submission-xqts.xq 2011-10-05 20:32:28 +0000
@@ -10,7 +10,7 @@
10 validate {10 validate {
11 <test-suite-result>11 <test-suite-result>
12 <implementation name="Zorba" 12 <implementation name="Zorba"
13 version='2.0 (svn rev. 11228)'13 version='2.0.3'
14 anonymous-result-column="false">14 anonymous-result-column="false">
15 15
16 <organization16 <organization
@@ -31,20 +31,20 @@
31 database servers, XML message dispatchers, or smartphones.31 database servers, XML message dispatchers, or smartphones.
32 Its architecture employes a modular design, which allows customizing32 Its architecture employes a modular design, which allows customizing
33 the Zorba query processor to the environment’s needs.33 the Zorba query processor to the environment’s needs.
34 In particular the architecture of the query processor allows a34 For more details please check out http://www.zorba-xquery.com.</p>
35 pluggable XML store (e.g. main memory, DOM stores, persistent
36 disk-based large stores, S3 stores). Zorba runs on most platforms
37 and is available under the Apache license v2. Currently, Zorba
38 implements the following W3C specifications: XQuery 1.0, XQuery Update
39 Facility 1.0, XQuery Scripting Extension 1.0, and XSLT 2.0 and XQuery 1.0
40 Serialization.</p>
41 </description>35 </description>
4236
43 {37 {
44 let $XQTSZorba := fn:doc("XQTS.xml")38 let $XQTSZorba := fn:doc("XQTS.xml")
45 return39 return
46 (40 (
47 <implementation-defined-items>{$XQTSZorba//*:implementation-defined-item}</implementation-defined-items>,41 <implementation-defined-items>
42 {
43 for $idi in $XQTSZorba//*:implementation-defined-item
44 return
45 <implementation-defined-item name="{data($idi/@name)}" value="{data($idi/@value)}" />
46 }
47 </implementation-defined-items>,
48 <features>{$XQTSZorba//*:feature}</features>,48 <features>{$XQTSZorba//*:feature}</features>,
49 <context-properties>{$XQTSZorba//*:context-property}</context-properties>49 <context-properties>{$XQTSZorba//*:context-property}</context-properties>
50 )50 )
@@ -54,11 +54,11 @@
54 54
55 <syntax>XQuery</syntax>55 <syntax>XQuery</syntax>
56 56
57 <test-run dateRun="2011-07-13">57 <test-run dateRun="2011-09-23">
58 <test-suite version="current"/>58 <test-suite version="current"/>
59 <transformation><p>Standard</p></transformation>59 <transformation><p>Standard</p></transformation>
60 <comparison><p>Standard</p></comparison>60 <comparison><p>Standard</p></comparison>
61 <otherComments><p>XQTS taken from W3C CVS as of 2011-07-13.</p></otherComments>61 <otherComments><p>XQTS taken from W3C CVS as of 2011-09-21.</p></otherComments>
62 </test-run>62 </test-run>
6363
64 {64 {
6565
=== modified file 'test/update/Scripts/XQUTS.xml'
--- test/update/Scripts/XQUTS.xml 2011-08-17 11:42:16 +0000
+++ test/update/Scripts/XQUTS.xml 2011-10-05 20:32:28 +0000
@@ -2,19 +2,41 @@
2<zorba xmlns="http://www.w3.org/2005/02/query-test-XQTSResult">2<zorba xmlns="http://www.w3.org/2005/02/query-test-XQTSResult">
3 3
4 <implementation-defined-items>4 <implementation-defined-items>
5 <implementation-defined-item name="supportedRevalidationModes" 5 <implementation-defined-item
6 value="lax, skip, strict"/>6 name="supportedRevalidationModes"
7 <implementation-defined-item name="defaultRevalidationMode" 7 value="lax, skip, strict">
8 value="lax"/>8 <description last-mod="2008-11-05">The revalidation modes that are supported by this
9 <implementation-defined-item name="externalFunctionXDMPUL" 9 implementation.</description>
10 value="Zorba allows external functions to be implemented in C++. Such functions may return XDM instances. However, it is not possible to implement an updating external function."/>10 </implementation-defined-item>
11 <implementation-defined-item name="fnPutSemantics" 11 <implementation-defined-item
12 value="fn:put stores a copy (preserving type, preserving namespaces, and inheriting namespace) of the given document or element in Zorba's store. That is it binds the node to the URI passed as first argument. If the URI is relative it's resolved against the base uri. The result of fn:put become effective at the end of the XQuery program or if they are applied using Zorba's made persistent."/>12 name="defaultRevalidationMode"
13 value="lax">
14 <description last-mod="2008-11-05">The default revalidation mode for this
15 implementation.</description>
16 </implementation-defined-item>
17 <implementation-defined-item
18 name="externalFunctionXDMPUL"
19 value="Zorba allows external functions to be implemented in C++. Such functions may return XDM instances. However, it is not possible to implement an updating external function.">
20 <description last-mod="2008-11-05">The mechanism (if any) by which an external function can
21 return an XDM instance and/or a pending update list to the invoking query.</description>
22 </implementation-defined-item>
23 <implementation-defined-item
24 name="fnPutSemantics"
25 value="fn:put stores a copy (preserving type, preserving namespaces, and inheriting namespace) of the given document or element in Zorba's store. That is it binds the node to the URI passed as first argument. If the URI is relative it's resolved against the base uri. The result of fn:put become effective at the end of the XQuery program or if they are applied using Zorba's made persistent.">
26 <description last-mod="2008-11-05">The semantics of fn:put(), including the kinds of nodes
27 accepted as operands by this function.</description>
28 </implementation-defined-item>
13 </implementation-defined-items>29 </implementation-defined-items>
14 30
15 <features>31 <features>
16 <feature name='Minimal Conformance' supported='true' />32 <feature
17 <feature name='Update Facility Static Typing Feature' supported='false' />33 name='Minimal Conformance'
34 supported='true' />
35
36 <feature
37 name='Update Facility Static Typing Feature'
38 supported='false' />
39
18 </features>40 </features>
19 41
20 <context-properties>42 <context-properties>
2143
=== modified file 'test/update/Scripts/generate-submission-xquts.xq'
--- test/update/Scripts/generate-submission-xquts.xq 2011-08-17 11:42:16 +0000
+++ test/update/Scripts/generate-submission-xquts.xq 2011-10-05 20:32:28 +0000
@@ -10,7 +10,7 @@
10 validate {10 validate {
11 <test-suite-result>11 <test-suite-result>
12 <implementation name="Zorba" 12 <implementation name="Zorba"
13 version='2.0 (svn rev. 11228)'13 version='2.0.3'
14 anonymous-result-column="false">14 anonymous-result-column="false">
15 15
16 <organization16 <organization
@@ -31,20 +31,20 @@
31 database servers, XML message dispatchers, or smartphones.31 database servers, XML message dispatchers, or smartphones.
32 Its architecture employes a modular design, which allows customizing32 Its architecture employes a modular design, which allows customizing
33 the Zorba query processor to the environment’s needs.33 the Zorba query processor to the environment’s needs.
34 In particular the architecture of the query processor allows a34 For more details please check out http://www.zorba-xquery.com.</p>
35 pluggable XML store (e.g. main memory, DOM stores, persistent
36 disk-based large stores, S3 stores). Zorba runs on most platforms
37 and is available under the Apache license v2. Currently, Zorba
38 implements the following W3C specifications: XQuery 1.0, XQuery Update
39 Facility 1.0, XQuery Scripting Extension 1.0, and XSLT 2.0 and XQuery 1.0
40 Serialization.</p>
41 </description>35 </description>
42 36
43 {37 {
44 let $XQUTSZorba := fn:doc("XQUTS.xml")38 let $XQUTSZorba := fn:doc("XQUTS.xml")
45 return39 return
46 (40 (
47 <implementation-defined-items>{$XQUTSZorba//*:implementation-defined-item}</implementation-defined-items>,41 <implementation-defined-items>
42 {
43 for $idi in $XQUTSZorba//*:implementation-defined-item
44 return
45 <implementation-defined-item name="{data($idi/@name)}" value="{data($idi/@value)}" />
46 }
47 </implementation-defined-items>,
48 <features>{$XQUTSZorba//*:feature}</features>,48 <features>{$XQUTSZorba//*:feature}</features>,
49 <context-properties>{$XQUTSZorba//*:context-property}</context-properties>49 <context-properties>{$XQUTSZorba//*:context-property}</context-properties>
50 )50 )
@@ -54,11 +54,11 @@
5454
55 <syntax>XQuery</syntax>55 <syntax>XQuery</syntax>
56 56
57 <test-run dateRun="2011-07-13">57 <test-run dateRun="2011-09-23">
58 <test-suite version="current"/>58 <test-suite version="current"/>
59 <transformation><p>Standard</p></transformation>59 <transformation><p>Standard</p></transformation>
60 <comparison><p>Standard</p></comparison>60 <comparison><p>Standard</p></comparison>
61 <otherComments><p>XQUTS version taken from CVS as of July 13th 2011.</p></otherComments>61 <otherComments><p>XQUTS version taken from CVS as of 2011-09-21.</p></otherComments>
62 </test-run>62 </test-run>
63 63
64 {64 {
@@ -70,7 +70,7 @@
70 <test-case70 <test-case
71 name="{$testname}"71 name="{$testname}"
72 result="not applicable"72 result="not applicable"
73 comment="this test was not run by Zorba: please consult the 'Guidelines for Running the XML Query Update Test Suite' for more details."73 comment="This test was not run by Zorba: please consult the 'Guidelines for Running the XML Query Update Test Suite' for more details."
74 />74 />
75 else if (fn:contains(fn:data($test),'StaticTypingFeature')) then75 else if (fn:contains(fn:data($test),'StaticTypingFeature')) then
76 <test-case76 <test-case

Subscribers

People subscribed via source and target branches