tests/auto/xmlpatternsdiagnosticsts/TestSuite/DiagnosticsCatalog.xml
changeset 0 1918ee327afb
child 7 3f74d0d4af4c
equal deleted inserted replaced
-1:000000000000 0:1918ee327afb
       
     1 <?xml version="1.0" encoding="UTF-8"?>
       
     2 <?xml-stylesheet type="text/xsl" href="XQTSCatalog.xsl" ?>
       
     3 
       
     4 <test-suite
       
     5   xmlns="http://www.w3.org/2005/02/query-test-XQTSCatalog"
       
     6   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       
     7   CatalogDesignDate="2003-04-03"
       
     8   version="0.1"
       
     9   SourceOffsetPath="./"
       
    10   ResultOffsetPath="ExpectedTestResults/"
       
    11   XQueryQueryOffsetPath="Queries/XQuery/"
       
    12   XQueryXQueryOffsetPath="Queries/XQueryX/"
       
    13   XQueryFileExtension=".xq"
       
    14   XQueryXFileExtension=".xqx"
       
    15   xsi:schemaLocation="http://www.w3.org/2005/02/query-test-XQTSCatalog XQTSCatalog.xsd">
       
    16 
       
    17    <test-suite-info> 
       
    18       <title>KXQTS Harness Test Suite</title>
       
    19       <description>This collection of test cases in the XQTS format does not exist
       
    20                    for testing an XPath, XQuery or XSL-T implementation, but to verify
       
    21                    the test harness tool that runs an actual XQTS test suite. Therefore, 
       
    22                    some tests intentionally fail in this test suite.</description>
       
    23    </test-suite-info> 
       
    24 
       
    25   <citations>
       
    26     <citation-spec name="XQuery">
       
    27       <description last-mod="2004-10-29">XQuery 1.0: An XML Query Language</description>
       
    28       <spec-URI>http://www.w3.org/TR/2004/WD-xquery-20041029/</spec-URI>
       
    29     </citation-spec>
       
    30     <citation-spec name="FuncOps">
       
    31       <description last-mod="2004-10-29">XQuery 1.0 and XPath 2.0 Functions and Operators</description>
       
    32       <spec-URI>http://www.w3.org/TR/2004/WD-xpath-functions-20041029/</spec-URI>
       
    33     </citation-spec>
       
    34     <citation-spec name="DataModel">
       
    35       <description last-mod="2004-10-29">XQuery 1.0 and XPath 2.0 Data Model</description>
       
    36       <spec-URI>http://www.w3.org/TR/2004/WD-xpath-datamodel-20041029/</spec-URI>
       
    37     </citation-spec>
       
    38       <citation-spec name="FormalSemantics">
       
    39       <description last-mod="2004-02-20">XQuery 1.0 and XPath 2.0 Formal Semantics</description>
       
    40       <spec-URI>http://www.w3.org/TR/2004/WD-xquery-semantics-20040220/</spec-URI>
       
    41     </citation-spec>
       
    42     <citation-spec name="SchemaPart2">
       
    43       <description last-mod="2003-03-25">XML Schema Part 2: Datatypes</description>
       
    44       <spec-URI>http://www.w3.org/TR/xmlschema-2/</spec-URI>
       
    45     </citation-spec>
       
    46     <citation-spec name="Schema-Errata">
       
    47       <description last-mod="2003-03-25">XML Schema Errata</description>
       
    48       <note>Current practice is to have one Errata document for all parts of Schema.</note>
       
    49       <spec-URI>http://www.w3.org/2001/05/xmlschema-errata</spec-URI>
       
    50     </citation-spec>
       
    51     <citation-spec name="UseCases">
       
    52       <description last-mod="2003-11-12">XML Query Use Cases</description>
       
    53       <spec-URI>http://www.w3c.org/TR/xquery-use-cases/</spec-URI>
       
    54     </citation-spec>
       
    55     </citations>
       
    56 
       
    57   <comparisons>
       
    58     <comparison name="XML">
       
    59       <description last-mod="2003-03-25">The XML InfoSets should be canonicalized and compared.</description>
       
    60     </comparison>
       
    61     <comparison name="Fragment">
       
    62       <description last-mod="2004-10-20">A 'fragment' refers to an XML based instance which has multiple top-level elements and NO XML declaration.
       
    63         The comparator for this should simply wrap the entire fragment in a container element and perform XML comparisson.
       
    64       </description>
       
    65     </comparison>
       
    66     <comparison name="Text">
       
    67       <description last-mod="2003-03-25">
       
    68                   Each line of non-whitespace text should match. New-line sequences
       
    69                   may vary and should be neutralized. Due to issues with the XML serialization of certain characters (e.g. '&lt;'),
       
    70                   it is not possible to simply compare the actual and expected results. Rather (as is the case with the 'Fragment' comparator)
       
    71                   the test harness should convert the results into valid XML (by adding a container element) and perform comparisson
       
    72                   on the XML canonicalized versions of the results.
       
    73       </description>
       
    74     </comparison>
       
    75     <comparison name="Ignore">
       
    76       <description last-mod="2003-03-25">
       
    77                   Only the presence/absence of this file is significant,
       
    78                   not its content.
       
    79       </description>
       
    80     </comparison>
       
    81     <comparison name="Inspect">
       
    82       <description last-mod="2003-03-25">
       
    83                   Automated comparison is not possible. the output should be
       
    84                   inspected by a human.
       
    85       </description>
       
    86     </comparison>
       
    87   </comparisons>
       
    88 
       
    89   <roles>
       
    90     <role name="principal-data">
       
    91     <description last-mod="2003-03-25">
       
    92                 This is the source that is handed in to the processor as the
       
    93                 initial input sequence, setting the "evaluation context" as described in XQuery chapter 2.
       
    94              </description>
       
    95     </role>
       
    96     <role name="supplemental-data">
       
    97     <description last-mod="2003-03-25">
       
    98                 These are sources that may be read by functions such as
       
    99                 fn:document() as the query is evaluated.
       
   100              </description>
       
   101     </role>
       
   102     <role name="schema">
       
   103     <description last-mod="2003-03-25">
       
   104                 These are schema definitions that may be referenced by sources
       
   105                 or in the query.
       
   106              </description>
       
   107     </role>
       
   108     <role name="dtd">
       
   109     <description last-mod="2003-03-25">
       
   110                 These are dtd definitions that may be referenced by sources
       
   111                 or in the query.
       
   112              </description>
       
   113     </role>
       
   114     <role name="principal">
       
   115     <description last-mod="2003-03-25">
       
   116                 This is an output (either text or XML) that will contain the
       
   117                 query results. If the processor invocation sequence accepts a filename for results, this name may be
       
   118                 passed, possibly prefixed by a partial directory path to allow storage of the results in a separate
       
   119                 directory tree.
       
   120              </description>
       
   121     </role>
       
   122     <role name="console-log">
       
   123     <description last-mod="2003-03-25">
       
   124                 This is an output (text file tagged .log) that will contain the
       
   125                 captured "console" output for a command-line invocation, or equivalent messages from a harness. The
       
   126                 main goal is to capture error messages that came from the processor.
       
   127              </description>
       
   128     <note>
       
   129                 A test lab may choose to capture console output for every test case, in which case the presence
       
   130                 of this element is a signal that the console log of this test contains messages that are significant to
       
   131                 the pass/fail determination.
       
   132              </note>
       
   133     </role>
       
   134   </roles>
       
   135 
       
   136   <scenarios>
       
   137     <scenario name="standard">
       
   138     <description last-mod="2005-06-10">
       
   139                 A query this is expected to produce valid results. Principal input should always be specified, even if the query doesn't have any PathExpr.
       
   140              </description>
       
   141     </scenario>
       
   142     <scenario name="parse-error">
       
   143     <description last-mod="2005-06-10">
       
   144                 A query this is expected to raise a parsing/syntax error at query parse time. Principal input should always be specified, even if the query doesn't have any PathExpr.
       
   145              </description>
       
   146     </scenario>
       
   147     <scenario name="runtime-error">
       
   148     <description last-mod="2005-06-10">
       
   149                 A query this is expected to raise a runtime error at query parse time. Runtime errors in this case include those raised by static typing rules. Principal input should always be specified, even if the query doesn't have any PathExpr.
       
   150              </description>
       
   151     </scenario>
       
   152   </scenarios>
       
   153 
       
   154   <sources>
       
   155     <source ID="XQTSCatalog" FileName="XQTSCatalog.xml" Creator="XQuery Test Task Force" schema="XQTSCatalogxsd">
       
   156     <description last-mod="2005-04-14">XQuery Test Suite Catalog</description>
       
   157     </source>
       
   158     <source ID="bib2" FileName="TestSources/bib2.xml" Creator="spec-authors">
       
   159     <description last-mod="2003-03-25">Bibliography example with extra comments and PIs.</description>
       
   160     </source>
       
   161     <source ID="emptydoc" FileName="TestSources/emptydoc.xml" Creator="David Marston">
       
   162     <description last-mod="2003-03-25">Contains just a "doc" element, no comments/text/PIs.</description>
       
   163     </source>
       
   164     <source ID="fsx" FileName="TestSources/fsx.xml" Creator="Mike Rorke">
       
   165     <description last-mod="2003-03-25">Data about a filesystem represented in XML.</description>
       
   166     </source>
       
   167     <source ID="fsx_NS" FileName="TestSources/fsx_NS.xml" Creator="Mike Rorke">
       
   168     <description last-mod="2003-03-25">Data about a filesystem represented in XML with namespace-qualified names.</description>
       
   169     </source>
       
   170     <source ID="MixNS" FileName="TestSources/MixNS.xml" Creator="David Marston">
       
   171     <description last-mod="2003-03-25">Small tree with element names in mixed namespaces.</description>
       
   172     <note>Use @index to identify elements precisely.</note>
       
   173     </source>
       
   174     <source ID="nw_Customers" FileName="TestSources/nw_Customers.xml" Creator="Kuen Siew">
       
   175     <description last-mod="2003-03-25">Customer name/address file with some non-ASCII characters.</description>
       
   176     </source>
       
   177     <source ID="TopMany" FileName="TestSources/TopMany.xml" Creator="David Marston">
       
   178     <description last-mod="2003-03-25">Like TreeCompass, but with comments and PIs off the root. PI targets vary.</description>
       
   179     <note>All text nodes must have non-whitespace characters.</note>
       
   180     </source>
       
   181     <source ID="Tree1Child" FileName="TestSources/Tree1Child.xml" Creator="David Marston">
       
   182     <description last-mod="2003-03-25">A "compass" tree that has just one child, of an abnormal name, off the center node.</description>
       
   183     <note>One attribute each on west and center.</note>
       
   184     </source>
       
   185     <source ID="Tree1Text" FileName="TestSources/Tree1Text.xml" Creator="David Marston">
       
   186     <description last-mod="2003-03-25">A "compass" tree that has just a text node and no child element off the center node.</description>
       
   187     </source>
       
   188     <source ID="TreeCompass" FileName="TestSources/TreeCompass.xml" Creator="David Marston">
       
   189     <description last-mod="2003-03-25">A tree intended to allow many kinds of path expressions.</description>
       
   190     <note>Need multiple attributes on center, west, and south, plus @mark scattered around.</note>
       
   191     <note>Mix of text and element children in many places, but east should have only a text node.</note>
       
   192     <note>All text nodes must have non-whitespace characters.</note>
       
   193     <note>Top element is far-north.</note>
       
   194     </source>
       
   195     <source ID="TreeEmpty" FileName="TestSources/TreeEmpty.xml" Creator="David Marston">
       
   196     <description last-mod="2003-03-25">A "compass" tree that has just one "south" element at the top, bearing one "mark" attribute.</description>
       
   197     </source>
       
   198     <source ID="TreeRepeat" FileName="TestSources/TreeRepeat.xml" Creator="David Marston">
       
   199     <description last-mod="2003-03-25">A "compass" tree that has center elements off the real center node.</description>
       
   200     <note>Use @mark to distinguish center elements.</note>
       
   201     <note>"Real" center must have multiple element children, some with duplicate names (south-east).</note>
       
   202     <note>Repeating attribute names used, including same name on elements of the same name.</note>
       
   203     <note>Comments and text nodes are strewn about. All text nodes must have non-whitespace characters.</note>
       
   204     </source>
       
   205     <source ID="TreeStack" FileName="TestSources/TreeStack.xml" Creator="David Marston">
       
   206     <description last-mod="2003-03-25">A "compass" tree that has several "south" elements, some stacked within each other.</description>
       
   207     <note>Use "mark" attributes at several levels and on all south elements.</note>
       
   208     </source>
       
   209     <source ID="TreeTrunc" FileName="TestSources/TreeTrunc.xml" Creator="David Marston">
       
   210     <description last-mod="2003-03-25">A "compass" tree that has no content at all in center or west, no attributes anywhere.</description>
       
   211     </source>
       
   212     <source ID="xq311A" FileName="TestSources/xq311A.xml" Creator="David Marston">
       
   213     <description last-mod="2003-03-25">Data that fits first example in XQuery 3.11.</description>
       
   214     </source>
       
   215     <source ID="xq311B" FileName="TestSources/xq311B.xml" Creator="David Marston">
       
   216     <description last-mod="2003-03-25">Data that fits later examples in XQuery 3.11.</description>
       
   217     </source>
       
   218     <source ID="DupNode" FileName="TestSources/DupNode.xml" Creator="Andreas Behm">
       
   219     <description last-mod="2005-04-26">Simple document with all node kinds</description>
       
   220     </source>
       
   221     <source ID="inscope" FileName="TestSources/inscope.xml" Creator="Andreas Behm">
       
   222     <description last-mod="2005-08-26">Simple document with namespaces</description>
       
   223     </source>
       
   224     <source ID="nsmode" FileName="TestSources/nsmode.xml" Creator="Andreas Behm">
       
   225     <description last-mod="2005-04-26">Source document for namespace copy modes</description>
       
   226     </source>
       
   227     <source ID="works" FileName="TestSources/works.xml" Creator="Carmelo Montanez">
       
   228     <description last-mod="2005-03-04">Data for various NIST tests</description>
       
   229     </source>
       
   230     <source ID="works-mod" FileName="TestSources/works-mod.xml" Creator="Carmelo Montanez">
       
   231     <description last-mod="2005-03-04">Data for various NIST tests (abbreviated, unabbreviated syntax)</description>
       
   232     </source>
       
   233     <source ID="lang" FileName="TestSources/lang.xml" Creator="Carmelo Montanez">
       
   234     <description last-mod="2005-10-19">Data for fn:lang tests.</description>
       
   235     </source>
       
   236     <source ID="staff" FileName="TestSources/staff.xml" Creator="Carmelo Montanez">
       
   237     <description last-mod="2005-03-04">Data for various NIST tests</description>
       
   238     </source>
       
   239     <source ID="acme_corp" FileName="TestSources/acme_corp.xml" Creator="Ravindranath Chennoju">
       
   240     <description last-mod="2005-08-30">Source document for Function Declaration tests</description>
       
   241     </source>
       
   242     <source ID="bib" FileName="TestSources/bib.xml" Creator="XML Query WG">
       
   243     <description last-mod="2005-02-11">Data for the the XML Query XMP use cases</description>
       
   244     </source>
       
   245     <source ID="reviews" FileName="TestSources/reviews.xml" Creator="XML Query WG">
       
   246     <description last-mod="2005-02-11">Data for the the XML Query XMP use cases</description>
       
   247     </source>
       
   248     <source ID="books" FileName="TestSources/books.xml" Creator="XML Query WG">
       
   249     <description last-mod="2005-02-11">Data for the the XML Query XMP use cases</description>
       
   250     </source>
       
   251     <source ID="prices" FileName="TestSources/prices.xml" Creator="XML Query WG">
       
   252     <description last-mod="2005-02-11">Data for the the XML Query XMP use cases</description>
       
   253     </source>
       
   254     <source ID="book" FileName="TestSources/book.xml" Creator="XML Query WG">
       
   255     <description last-mod="2005-02-11">Data for the the XML Query TREE use cases</description>
       
   256     </source>
       
   257     <source ID="report1" FileName="TestSources/report1.xml" Creator="XML Query WG">
       
   258     <description last-mod="2005-02-11">Data for the the XML Query SEQ use cases</description>
       
   259     </source>
       
   260     <source ID="items" FileName="TestSources/items.xml" Creator="XML Query WG">
       
   261     <description last-mod="2005-02-11">Data for the the XML Query RDB use cases</description>
       
   262     </source>
       
   263     <source ID="bids" FileName="TestSources/bids.xml" Creator="XML Query WG">
       
   264     <description last-mod="2005-02-11">Data for the the XML Query RDB use cases</description>
       
   265     </source>
       
   266     <source ID="users" FileName="TestSources/users.xml" Creator="XML Query WG">
       
   267     <description last-mod="2005-02-11">Data for the the XML Query RDB use cases</description>
       
   268     </source>
       
   269     <source ID="string" FileName="TestSources/string.xml" Creator="XML Query WG">
       
   270     <description last-mod="2005-02-11">Data for the the XML Query STRING use cases</description>
       
   271     </source>
       
   272     <source ID="company-data" FileName="TestSources/company-data.xml" Creator="XML Query WG">
       
   273     <description last-mod="2005-02-11">Data for the the XML Query STRING use cases</description>
       
   274     </source>
       
   275     <source ID="auction" FileName="TestSources/auction.xml" Creator="XML Query WG">
       
   276     <description last-mod="2005-02-11">Data for the the XML Query NS use cases</description>
       
   277     </source>
       
   278     <source ID="partlist" FileName="TestSources/partlist.xml" Creator="XML Query WG">
       
   279     <description last-mod="2005-02-11">Data for the the XML Query PARTS use cases</description>
       
   280     </source>
       
   281     <source ID="sgml" FileName="TestSources/sgml.xml" Creator="XML Query WG">
       
   282     <description last-mod="2005-02-11">Data for the the XML Query SGML use cases</description>
       
   283     </source>
       
   284     <source ID="atomic" FileName="TestSources/atomic.xml" Creator="Carmelo Montanez" schema="atomicxsd">
       
   285     <description last-mod="2005-03-08">A Schema validated xml file, that contains values for data types. Can be used by any test.</description>
       
   286     </source>
       
   287     <source ID="orderData" FileName="TestSources/orderData.xml" Creator="Carmelo Montanez" schema="orderDataxsd">
       
   288     <description last-mod="2005-06-01">A Schema validated xml file, that contains values for some of the order by tests generated by NIST.</description>
       
   289     </source>
       
   290     <source ID="id-idref" FileName="TestSources/id.xml" Creator="Carmelo Montanez">
       
   291     <description last-mod="2005-06-01">Data for id and idref related functions.</description>
       
   292     </source>
       
   293     <source ID="SpecialTypes" FileName="TestSources/SpecialTypes.xml" Creator="Mike Rorke" schema="SpecialTypesXSD">
       
   294     <description last-mod="2005-06-01">A Schema validated XML file containing certain special types e.g. interleave types, union types, anySimpleType</description>
       
   295     </source>
       
   296     <source ID="QNameSource" FileName="TestSources/QName-source.xml" Creator="Mike Rorke" schema="QNameSourceXSD">
       
   297     <description last-mod="2005-09-28">A schema validated XML file containing QName and QName derived types.</description>
       
   298     </source>
       
   299     <source ID="notation" FileName="TestSources/notation.xml" Creator="Andreas Behm" schema="notationschema">
       
   300     <description last-mod="2005-10-10">A Scehma validated xml file with NOTATION elements</description>
       
   301     </source>
       
   302     <source ID="textWithSpaces" FileName="TestSources/textWithSpaces.xml" Creator="Joanne Tong">
       
   303     <description last-mod="2005-09-29">Data for normalize-space functions</description>
       
   304     </source>
       
   305     <schema ID="XQTSCatalogxsd" uri="http://www.w3.org/2005/02/query-test-XQTSCatalog" FileName="XQTSCatalog.xsd">
       
   306     <description last-mod="2005-04-14">Schema for XQTSCatalog</description>
       
   307     </schema>
       
   308     <schema ID="atomicxsd" uri="http://www.w3.org/XQueryTest" FileName="TestSources/atomic.xsd">
       
   309     <description last-mod="2005-03-08">A Schema for atomic.xml</description>
       
   310     </schema>
       
   311     <schema ID="orderDataxsd" uri="http://www.w3.org/XQueryTestOrderBy" FileName="TestSources/orderData.xsd">
       
   312     <description last-mod="2005-06-01">A Schema for orderData.xml</description>
       
   313     </schema>
       
   314     <schema ID="SpecialTypesXSD" uri="http://typedecl" FileName="TestSources/SpecialTypes.xsd">
       
   315     <description last-mod="2005-06-01">A Schema containing certain special types e.g. interleave types, union types, anySimpleType</description>
       
   316     </schema>
       
   317     <schema ID="QNameSourceXSD" uri="QNameXSD" FileName="TestSources/QName-schema.xsd">
       
   318     <description last-mod="2005-09-28">A schema containing QName and QName derived types</description>
       
   319     </schema>
       
   320     <schema ID="notationschema" uri="http://www.example.com/notation" FileName="TestSources/notationschema.xsd">
       
   321     <description last-mod="2005-10-10">A Schema for NOTATION data</description>
       
   322     </schema>
       
   323     <schema ID="simplexsd" uri="http://www.w3.org/XQueryTest/simple" FileName="TestSources/simple.xsd">
       
   324     <description last-mod="2005-12-07">A schema for simple context tests</description>
       
   325     </schema>
       
   326     <module ID="empty-lib" FileName="TestSources/empty-lib" Creator="Mary Holstege">
       
   327     <description last-mod="2005-12-05">Library module for "modules-none" query</description>
       
   328     </module>
       
   329     <module ID="emptyns-lib" FileName="TestSources/emptyns-lib" Creator="Mary Holstege">
       
   330     <description last-mod="2005-12-05">Library module with empty namespace</description>
       
   331     </module>
       
   332     <module ID="test1-lib" FileName="TestSources/test1-lib" Creator="Mary Holstege">
       
   333     <description last-mod="2005-12-05">Simple library module</description>
       
   334     </module>
       
   335     <module ID="test2-lib" FileName="TestSources/test2-lib" Creator="Carmelo Montanez">
       
   336     <description last-mod="2006-01-19">Library module with namespace URI set to empty string.</description>
       
   337     </module>
       
   338     <module ID="test1a-lib" FileName="TestSources/test1a-lib" Creator="Mary Holstege">
       
   339     <description last-mod="2005-12-05">Simple library module</description>
       
   340     </module>
       
   341     <module ID="test1collide1-lib" FileName="TestSources/test1collide-lib" Creator="Mary Holstege">
       
   342     <description last-mod="2005-12-05">Library module with colliding definitions</description>
       
   343     </module>
       
   344     <module ID="test1collide2-lib" FileName="TestSources/test1collide2-lib" Creator="Mary Holstege">
       
   345     <description last-mod="2005-12-05">Library module with colliding definitions</description>
       
   346     </module>
       
   347     <module ID="test1c1-lib" FileName="TestSources/test1c1-lib" Creator="Mary Holstege">
       
   348     <description last-mod="2005-12-05">Library module with circular includes</description>
       
   349     </module>
       
   350     <module ID="test2c1-lib" FileName="TestSources/test2c1-lib" Creator="Mary Holstege">
       
   351     <description last-mod="2005-12-05">Library module with circular includes</description>
       
   352     </module>
       
   353     <module ID="context-lib" FileName="TestSources/context-lib" Creator="Mary Holstege">
       
   354     <description last-mod="2005-12-05">Library module with interesting context</description>
       
   355     </module>
       
   356     <module ID="module-defs" FileName="TestSources/moduleDefs-lib" Creator="Carmelo Montanez">
       
   357     <description last-mod="2006-01-06">Library module with definitions for various NIST tests.</description>
       
   358     </module>
       
   359   </sources>
       
   360 
       
   361   <implementation-defined-items>
       
   362     <implementation-defined-item name="expressionUnicode" spec="XQuery">
       
   363     <description last-mod="2005-04-04">The version of Unicode that is used to construct expressions.</description>
       
   364     </implementation-defined-item>
       
   365     <implementation-defined-item name="collations" spec="XQuery">
       
   366     <description last-mod="2005-04-04">The statically-known collations.</description>
       
   367     </implementation-defined-item>
       
   368     <implementation-defined-item name="implicitTimezone" spec="XQuery">
       
   369     <description last-mod="2005-04-04">The implicit timezone.</description>
       
   370     </implementation-defined-item>
       
   371     <implementation-defined-item name="warningsMethod" spec="XQuery">
       
   372     <description last-mod="2005-04-04">The circumstances in which warnings are raised, and the ways in which warnings are handled.</description>
       
   373     </implementation-defined-item>
       
   374     <implementation-defined-item name="errorsMethod" spec="XQuery">
       
   375     <description last-mod="2005-04-04">The method by which errors are reported to the external processing environment.</description>
       
   376     </implementation-defined-item>
       
   377     <implementation-defined-item name="XMLVersion" spec="XQuery">
       
   378     <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>
       
   379     </implementation-defined-item>
       
   380     <implementation-defined-item name="overwrittenContextComponents" spec="XQuery">
       
   381     <description last-mod="2005-04-04">Any components of the static context or dynamic context that are overwritten or augmented by the implementation.</description>
       
   382     </implementation-defined-item>
       
   383     <implementation-defined-item name="axes" spec="XQuery">
       
   384     <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>
       
   385     </implementation-defined-item>
       
   386     <implementation-defined-item name="defaultOrderEmpty" spec="XQuery">
       
   387     <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>
       
   388     </implementation-defined-item>
       
   389     <implementation-defined-item name="pragmas" spec="XQuery">
       
   390     <description last-mod="2005-04-04">The names and semantics of any extension expressions (pragmas) recognized by the implementation.</description>
       
   391     </implementation-defined-item>
       
   392     <implementation-defined-item name="optionDeclarations" spec="XQuery">
       
   393     <description last-mod="2005-04-04">The names and semantics of any option declarations recognized by the implementation.</description>
       
   394     </implementation-defined-item>
       
   395     <implementation-defined-item name="externalFunctionProtocols" spec="XQuery">
       
   396     <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>
       
   397     </implementation-defined-item>
       
   398     <implementation-defined-item name="moduleLocationHints" spec="XQuery">
       
   399     <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>
       
   400     </implementation-defined-item>
       
   401     <implementation-defined-item name="staticTypingExtensions" spec="XQuery">
       
   402     <description last-mod="2005-04-04">Any static typing extensions supported by the implementation, if the Static Typing Feature is supported.</description>
       
   403     </implementation-defined-item>
       
   404     <implementation-defined-item name="serializationInvocation" spec="XQuery">
       
   405     <description last-mod="2005-04-04">The means by which serialization is invoked, if the Serialization Feature is supported.</description>
       
   406     </implementation-defined-item>
       
   407     <implementation-defined-item name="serializationDefaults" spec="XQuery">
       
   408     <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>
       
   409     </implementation-defined-item>
       
   410     <implementation-defined-item name="limits" spec="XQuery">
       
   411     <description last-mod="2005-11-01">Limits on ranges of values for various data types, as enumerated in 5.3 Data Model Conformance.</description>
       
   412     </implementation-defined-item>
       
   413     <implementation-defined-item name="traceDestination" spec="FuncOps">
       
   414     <description last-mod="2005-10-10">The destination of the trace output is implementation-defined. See 4 The Trace Function.</description>
       
   415     </implementation-defined-item>
       
   416     <implementation-defined-item name="integerOperations" spec="FuncOps">
       
   417     <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>
       
   418     </implementation-defined-item>
       
   419     <implementation-defined-item name="decimalDigits" spec="FuncOps">
       
   420     <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>
       
   421     </implementation-defined-item>
       
   422     <implementation-defined-item name="roundOrTruncate" spec="FuncOps">
       
   423     <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>
       
   424     </implementation-defined-item>
       
   425     <implementation-defined-item name="Unicode" spec="FuncOps">
       
   426     <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>
       
   427     </implementation-defined-item>
       
   428     <implementation-defined-item name="normalizationForms" spec="FuncOps">
       
   429     <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>
       
   430     </implementation-defined-item>
       
   431     <implementation-defined-item name="collationUnits" spec="FuncOps">
       
   432     <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>
       
   433     </implementation-defined-item>
       
   434     <implementation-defined-item name="secondsDigits" spec="FuncOps">
       
   435     <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>
       
   436     </implementation-defined-item>
       
   437     <implementation-defined-item name="docProcessing" spec="FuncOps">
       
   438     <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>
       
   439     </implementation-defined-item>
       
   440     <implementation-defined-item name="additionalTypes" spec="DataModel">
       
   441     <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>
       
   442     </implementation-defined-item>
       
   443     <implementation-defined-item name="undefinedProperties" spec="DataModel">
       
   444     <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>
       
   445     </implementation-defined-item>
       
   446     <implementation-defined-item name="sequenceNormalization" spec="Serialization">
       
   447     <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>
       
   448     </implementation-defined-item>
       
   449     <implementation-defined-item name="outputMethods" spec="Serialization">
       
   450     <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>
       
   451     </implementation-defined-item>
       
   452     <implementation-defined-item name="normalizationForm" spec="Serialization">
       
   453     <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>
       
   454     </implementation-defined-item>
       
   455     <implementation-defined-item name="additionalParams" spec="Serialization">
       
   456     <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>
       
   457     </implementation-defined-item>
       
   458     <implementation-defined-item name="encodingPhase" spec="Serialization">
       
   459     <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>
       
   460     </implementation-defined-item>
       
   461     <implementation-defined-item name="CDATASerialization" spec="Serialization">
       
   462     <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>
       
   463     </implementation-defined-item>
       
   464   </implementation-defined-items>
       
   465 
       
   466   <features>
       
   467     <feature name="Minimal Conformance"/>
       
   468     <feature name="Schema Import"/>
       
   469     <feature name="Schema Validation"/>
       
   470     <feature name="Static Typing"/>
       
   471     <feature name="Static Typing Extensions"/>
       
   472     <feature name="Full Axis"/>
       
   473     <feature name="Module"/>
       
   474     <feature name="Serialization"/>
       
   475     <feature name="Trivial XML Embedding"/>
       
   476   </features>
       
   477 
       
   478   <context-properties>
       
   479     <context-property name="Statically known namespaces" context-type="static"/>
       
   480     <context-property name="Default element/type namespace" context-type="static"/>
       
   481     <context-property name="Default function namespace" context-type="static"/>
       
   482     <context-property name="In-scope schema types" context-type="static"/>
       
   483     <context-property name="In-scope element declarations" context-type="static"/>
       
   484     <context-property name="In-scope attribute declarations" context-type="static"/>
       
   485     <context-property name="In-scope variables" context-type="static"/>
       
   486     <context-property name="Context item static type" context-type="static"/>
       
   487     <context-property name="Function signatures" context-type="static"/>
       
   488     <context-property name="Statically known collations" context-type="static"/>
       
   489     <context-property name="Default collation" context-type="static"/>
       
   490     <context-property name="Construction mode" context-type="static"/>
       
   491     <context-property name="Ordering mode" context-type="static"/>
       
   492     <context-property name="Default order for empty sequences" context-type="static"/>
       
   493     <context-property name="Boundary-space policy" context-type="static"/>
       
   494     <context-property name="Copy-namespaces mode" context-type="static"/>
       
   495     <context-property name="Base URI" context-type="static"/>
       
   496     <context-property name="Statically known documents" context-type="static"/>
       
   497     <context-property name="Statically known collections" context-type="static"/>
       
   498     <context-property name="Statically known default collection type" context-type="static"/>
       
   499     <context-property name="Context item" context-type="dynamic"/>
       
   500     <context-property name="Context position" context-type="dynamic"/>
       
   501     <context-property name="Context size" context-type="dynamic"/>
       
   502     <context-property name="Variable values" context-type="dynamic"/>
       
   503     <context-property name="Function implementations" context-type="dynamic"/>
       
   504     <context-property name="Current dateTime" context-type="dynamic"/>
       
   505     <context-property name="Implicit timezone" context-type="dynamic"/>
       
   506     <context-property name="Available documents" context-type="dynamic"/>
       
   507     <context-property name="Available collections" context-type="dynamic"/>
       
   508     <context-property name="Default collection" context-type="dynamic"/>
       
   509   </context-properties>
       
   510 
       
   511   <test-group name="ShouldFail">
       
   512     <GroupInfo>
       
   513       <title>Failing Tests</title>
       
   514       <description>These tests should fail -- it's intentional.</description>
       
   515     </GroupInfo>
       
   516 
       
   517     <test-case
       
   518       Creator="Frans Englich"
       
   519       is-XPath2="true"
       
   520       name="fail-1"
       
   521       FilePath="ShouldFail/"
       
   522       scenario="standard">
       
   523       <description>
       
   524         The query is a syntax error, but the test-case requires a pass.
       
   525       </description>
       
   526 
       
   527       <query name="fail-1" date="2006-04-06"/>
       
   528 
       
   529       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   530       <output-file role="principal" compare="Text">fail-1.txt</output-file>
       
   531     </test-case>
       
   532 
       
   533     <test-case
       
   534       Creator="Frans Englich"
       
   535       is-XPath2="true"
       
   536       name="fail-2"
       
   537       FilePath="ShouldFail/"
       
   538       scenario="standard">
       
   539       <description>
       
   540         The query is a dynamic error due to call to fn:error(), but the test-case requires a pass.
       
   541       </description>
       
   542 
       
   543       <query name="fail-2" date="2006-04-06"/>
       
   544 
       
   545       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   546       <output-file role="principal" compare="Text">fail-2.txt</output-file>
       
   547 
       
   548     </test-case>
       
   549 
       
   550     <test-case
       
   551       Creator="Frans Englich"
       
   552       is-XPath2="true"
       
   553       name="fail-3"
       
   554       FilePath="ShouldFail/"
       
   555       scenario="parse-error">
       
   556       <description>
       
   557         The query evaluates to a xs:string, but the test-case requires
       
   558         a parse-error with error code XPST0003.
       
   559       </description>
       
   560 
       
   561       <query name="fail-3" date="2006-04-06"/>
       
   562 
       
   563       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   564       <expected-error>XPST0003</expected-error>
       
   565 
       
   566     </test-case>
       
   567 
       
   568     <test-case
       
   569       Creator="Frans Englich"
       
   570       is-XPath2="true"
       
   571       name="fail-4"
       
   572       FilePath="ShouldFail/"
       
   573       scenario="runtime-error">
       
   574       <description>
       
   575         The query evaluates to a xs:string, but the test-case requires
       
   576         a runtime-error with error code FORG0006.
       
   577       </description>
       
   578 
       
   579       <query name="fail-4" date="2006-04-06"/>
       
   580 
       
   581       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   582       <expected-error>FORG0006</expected-error>
       
   583 
       
   584     </test-case>
       
   585 
       
   586     <test-case
       
   587       Creator="Frans Englich"
       
   588       is-XPath2="true"
       
   589       name="fail-5"
       
   590       FilePath="ShouldFail/"
       
   591       scenario="parse-error">
       
   592       <description>
       
   593         The query evaluates to a parse error with error code XPST0003, but the 
       
   594         test case required a parse error with code XPST0081.
       
   595       </description>
       
   596 
       
   597       <query name="fail-5" date="2006-04-06"/>
       
   598 
       
   599       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   600       <expected-error>XPST0081</expected-error>
       
   601 
       
   602     </test-case>
       
   603 
       
   604     <test-case
       
   605       Creator="Frans Englich"
       
   606       is-XPath2="true"
       
   607       name="fail-6"
       
   608       FilePath="ShouldFail/"
       
   609       scenario="runtime-error">
       
   610       <description>
       
   611         The query evaluates to a parse error with error code XPST0003, but the 
       
   612         test case required a runtime error with code FORG0006.
       
   613       </description>
       
   614 
       
   615       <query name="fail-6" date="2006-04-06"/>
       
   616 
       
   617       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   618       <expected-error>FORG0006</expected-error>
       
   619 
       
   620     </test-case>
       
   621 
       
   622     <test-case
       
   623       Creator="Frans Englich"
       
   624       is-XPath2="true"
       
   625       name="fail-7"
       
   626       FilePath="ShouldFail/"
       
   627       scenario="parse-error">
       
   628       <description>
       
   629         The query evaluates to a dynamic error with error code FOER0000, but the 
       
   630         test case required a parse error with code FOER0000.
       
   631       </description>
       
   632 
       
   633       <query name="fail-7" date="2006-04-06"/>
       
   634 
       
   635       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   636       <expected-error>FOER0000</expected-error>
       
   637 
       
   638     </test-case>
       
   639 
       
   640     <test-case
       
   641       Creator="Frans Englich"
       
   642       is-XPath2="true"
       
   643       name="fail-8"
       
   644       FilePath="ShouldFail/"
       
   645       scenario="runtime-error">
       
   646       <description>
       
   647         The query evaluates to a dynamic error with error code FOER0000, but the 
       
   648         test case required a parse error with code FORG0006.
       
   649       </description>
       
   650 
       
   651       <query name="fail-8" date="2006-04-06"/>
       
   652 
       
   653       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   654       <expected-error>FORG0006</expected-error>
       
   655 
       
   656     </test-case>
       
   657 
       
   658     <test-case
       
   659       Creator="Frans Englich"
       
   660       is-XPath2="true"
       
   661       name="fail-9"
       
   662       FilePath="ShouldFail/"
       
   663       scenario="runtime-error">
       
   664       <description>
       
   665         The query evaluates to an xs:string, but none of the baselines match.
       
   666       </description>
       
   667 
       
   668       <query name="fail-9" date="2006-04-06"/>
       
   669 
       
   670       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   671       <output-file role="principal" compare="Text">succeed-9-1.txt</output-file>
       
   672       <output-file role="principal" compare="Text">succeed-9-2.txt</output-file>
       
   673       <output-file role="principal" compare="Text">succeed-9-3.txt</output-file>
       
   674 
       
   675     </test-case>
       
   676 
       
   677     <test-case
       
   678       Creator="Frans Englich"
       
   679       is-XPath2="true"
       
   680       name="fail-10"
       
   681       FilePath="ShouldFail/"
       
   682       scenario="runtime-error">
       
   683       <description>
       
   684         The query evaluates to an xs:string, but the baseline doesn't match.
       
   685       </description>
       
   686 
       
   687       <query name="fail-10" date="2006-04-06"/>
       
   688 
       
   689       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   690       <output-file role="principal" compare="Text">succeed-10.txt</output-file>
       
   691 
       
   692     </test-case>
       
   693 
       
   694     <test-case
       
   695       Creator="Frans Englich"
       
   696       is-XPath2="true"
       
   697       name="fail-11"
       
   698       FilePath="ShouldFail/"
       
   699       scenario="parse-error">
       
   700       <description>
       
   701         The query contains a parse error, but none of the baselines match.
       
   702       </description>
       
   703 
       
   704       <query name="fail-11" date="2006-04-06"/>
       
   705 
       
   706       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   707       <output-file role="principal" compare="Text">succeed-11-1.txt</output-file>
       
   708       <output-file role="principal" compare="Text">succeed-11-2.txt</output-file>
       
   709       <expected-error>FOER0000</expected-error>
       
   710 
       
   711     </test-case>
       
   712 
       
   713     <test-case
       
   714       Creator="Frans Englich"
       
   715       is-XPath2="true"
       
   716       name="fail-12"
       
   717       FilePath="ShouldFail/"
       
   718       scenario="runtime-error">
       
   719       <description>
       
   720         The query contains a runtime error due to call to fn:error(), but none of the baselines match.
       
   721       </description>
       
   722 
       
   723       <query name="fail-12" date="2006-04-06"/>
       
   724 
       
   725       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   726       <output-file role="principal" compare="Text">succeed-12-1.txt</output-file>
       
   727       <output-file role="principal" compare="Text">succeed-12-2.txt</output-file>
       
   728       <expected-error>FORG0006</expected-error>
       
   729 
       
   730     </test-case>
       
   731 
       
   732     <test-case
       
   733       Creator="Frans Englich"
       
   734       is-XPath2="true"
       
   735       name="fail-13"
       
   736       FilePath="ShouldFail/"
       
   737       scenario="parse-error">
       
   738       <description>
       
   739         The test-case requires a parse error with error code XPST0003,
       
   740         but the query file does not exist.
       
   741       </description>
       
   742 
       
   743       <query name="DoesNotExist" date="2006-04-06"/>
       
   744 
       
   745       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   746       <expected-error>XPST0003</expected-error>
       
   747 
       
   748     </test-case>
       
   749 
       
   750     <test-case
       
   751       Creator="Frans Englich"
       
   752       is-XPath2="true"
       
   753       name="fail-14"
       
   754       FilePath="ShouldFail/"
       
   755       scenario="standard">
       
   756       <description>
       
   757         The query evaluates to a xs:string literal, but the specified
       
   758         baseline file does not exist.
       
   759       </description>
       
   760 
       
   761       <query name="fail-14" date="2006-04-06"/>
       
   762 
       
   763       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   764 
       
   765       <output-file role="principal" compare="Text">fail-DOESNOTEXIST.txt</output-file>
       
   766 
       
   767     </test-case>
       
   768 
       
   769    <test-case is-XPath2="false" name="fail-15"  FilePath="ShouldFail/"
       
   770               scenario="standard" Creator="Frans Englich">
       
   771        <description>An "Ignore" baseline with a query that generates a runtime error.</description>
       
   772        <query name="fail-15" date="2006-10-25"/>
       
   773        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   774        <output-file role="principal" compare="Ignore"/>
       
   775     </test-case>
       
   776 
       
   777    <test-case is-XPath2="false" name="fail-16"  FilePath="ShouldFail/"
       
   778               scenario="standard" Creator="Frans Englich">
       
   779        <description>An "Ignore" baseline with a query that generates a parse error.</description>
       
   780        <query name="fail-16" date="2006-10-25"/>
       
   781        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   782        <output-file role="principal" compare="Ignore"/>
       
   783     </test-case>
       
   784 
       
   785     <test-case is-XPath2="false" name="fail-17" FilePath="ShouldFail/"
       
   786                scenario="standard" Creator="Frans Englich" >
       
   787        <description>Space is significant.</description>
       
   788        <query name="fail-17" date="2007-06-07"/>
       
   789        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   790        <output-file role="principal" compare="XML">fail-3.txt</output-file>
       
   791     </test-case>
       
   792 
       
   793     <test-case is-XPath2="false" name="fail-18" FilePath="ShouldFail/"
       
   794                scenario="runtime-error" Creator="Frans Englich" >
       
   795                <description>Test that XML documents that differs on the top level, are flagged(type being runtime-error).</description>
       
   796        <query name="fail-18" date="2007-10-08"/>
       
   797        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   798        <output-file role="principal" compare="XML">fail-18.txt</output-file>
       
   799     </test-case>
       
   800 
       
   801     <test-case is-XPath2="false" name="fail-19" FilePath="ShouldFail/"
       
   802                scenario="runtime-error" Creator="Frans Englich" >
       
   803                <description>Test that XML documents that differs on the top level, are flagged(type being runtime-error, comparing as Fragment).</description>
       
   804        <query name="fail-18" date="2007-10-08"/>
       
   805        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   806        <output-file role="principal" compare="Fragment">fail-18.txt</output-file>
       
   807     </test-case>
       
   808 
       
   809     <test-case is-XPath2="false" name="fail-20" FilePath="ShouldFail/"
       
   810                scenario="standard" Creator="Frans Englich" >
       
   811                <description>Test that XML documents that differs on the top level, are flagged(type being standard, comparing as XML).</description>
       
   812        <query name="fail-18" date="2007-10-08"/>
       
   813        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   814        <output-file role="principal" compare="XML">fail-18.txt</output-file>
       
   815     </test-case>
       
   816 
       
   817     <test-case is-XPath2="false" name="fail-21" FilePath="ShouldFail/"
       
   818                scenario="standard" Creator="Frans Englich" >
       
   819                <description>Test that XML documents that differs on the top level, are flagged(type being standard, comparing as fragment).</description>
       
   820        <query name="fail-18" date="2007-10-08"/>
       
   821        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   822        <output-file role="principal" compare="Fragment">fail-18.txt</output-file>
       
   823     </test-case>
       
   824 
       
   825     <test-case Creator="Frans Englich" is-XPath2="false" name="fail-22" FilePath="ShouldFail/" scenario="standard">
       
   826       <description>Top elements differing in name, should fail.</description>
       
   827       <query name="fail-22" date="2007-10-08+01:00"/>
       
   828       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   829       <output-file role="principal" compare="XML">fail-22.txt</output-file>
       
   830     </test-case>
       
   831 
       
   832     <test-case Creator="Frans Englich" is-XPath2="false" name="fail-23" FilePath="ShouldFail/" scenario="standard">
       
   833       <description>Attributes differing with the XML prefix, should fail.</description>
       
   834       <query name="fail-23" date="2007-10-08+01:00"/>
       
   835       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   836       <output-file role="principal" compare="XML">fail-23.txt</output-file>
       
   837     </test-case>
       
   838 
       
   839     <test-case is-XPath2="false" name="fail-24" FilePath="ShouldFail/"
       
   840                scenario="runtime-error" Creator="Frans Englich" >
       
   841                <description>Test that XML documents that differs on the top level, are flagged(type being runtime-error, comparing as Fragment).</description>
       
   842        <query name="fail-18" date="2007-10-08"/>
       
   843        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   844        <output-file role="principal" compare="XML">fail-18.txt</output-file>
       
   845     </test-case>
       
   846 
       
   847   </test-group>
       
   848 
       
   849   <test-group name="ShouldSucceed">
       
   850     <GroupInfo>
       
   851       <title>Succeeding Tests</title>
       
   852       <description>These tests should succeed.</description>
       
   853     </GroupInfo>
       
   854 
       
   855     <test-case
       
   856       Creator="Frans Englich"
       
   857       is-XPath2="true"
       
   858       name="succeed-1"
       
   859       FilePath="ShouldSucceed/"
       
   860       scenario="standard">
       
   861       <description>A 'success' test where the query, which is a
       
   862         string literal, evaluates to a string, which must match the baseline.
       
   863       </description>
       
   864 
       
   865       <query name="succeed-1" date="2006-04-06"/>
       
   866 
       
   867       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   868       <output-file role="principal" compare="Text">succeed-1.txt</output-file>
       
   869 
       
   870     </test-case>
       
   871 
       
   872     <test-case
       
   873       Creator="Frans Englich"
       
   874       is-XPath2="false"
       
   875       name="succeed-2"
       
   876       FilePath="ShouldSucceed/"
       
   877       scenario="standard">
       
   878       <description>
       
   879         A 'success' test where multiple output baselines exists.
       
   880       </description>
       
   881 
       
   882       <query name="succeed-2" date="2006-04-06"/>
       
   883 
       
   884       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   885 
       
   886       <output-file role="principal" compare="Text">succeed-2-1.txt</output-file>
       
   887       <output-file role="principal" compare="Text">succeed-2-2.txt</output-file>
       
   888       <output-file role="principal" compare="Text">succeed-2-3.txt</output-file>
       
   889       <output-file role="principal" compare="Text">succeed-2-4.txt</output-file>
       
   890       <output-file role="principal" compare="Text">succeed-2-5.txt</output-file>
       
   891       <output-file role="principal" compare="Text">succeed-2-6.txt</output-file>
       
   892     </test-case>
       
   893 
       
   894     <test-case
       
   895       Creator="Frans Englich"
       
   896       is-XPath2="true"
       
   897       name="succeed-3"
       
   898       FilePath="ShouldSucceed/"
       
   899       scenario="parse-error">
       
   900       <description>
       
   901         A 'parse-error' specifying error code XPST0003,
       
   902         and where the query also is that; a syntax error.
       
   903       </description>
       
   904 
       
   905       <query name="succeed-3" date="2006-04-06"/>
       
   906 
       
   907       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   908 
       
   909       <expected-error>XPST0003</expected-error>
       
   910     </test-case>
       
   911 
       
   912     <test-case
       
   913       Creator="Frans Englich"
       
   914       is-XPath2="true"
       
   915       name="succeed-4"
       
   916       FilePath="ShouldSucceed/"
       
   917       scenario="runtime-error">
       
   918       <description>
       
   919         A 'runtime-error' specifying error code FOER0000,
       
   920         and where the query, containing a call to fn:error(), also results in that.
       
   921       </description>
       
   922 
       
   923       <query name="succeed-4" date="2006-04-06"/>
       
   924 
       
   925       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   926 
       
   927       <expected-error>FOER0000</expected-error>
       
   928     </test-case>
       
   929 
       
   930     <test-case
       
   931       Creator="Frans Englich"
       
   932       is-XPath2="true"
       
   933       name="succeed-5"
       
   934       FilePath="ShouldSucceed/"
       
   935       scenario="runtime-error">
       
   936       <description>
       
   937         A 'runtime-error' specifying error code XPTY0004,
       
   938         and where the query, contains an invalid operator mapping. While the test case
       
   939         is specified as a runtime error, some implementations detects it at compile time, but
       
   940         should nevertheless flag it as a passed test case(even though it failed at compile time
       
   941         instead of runtime).
       
   942       </description>
       
   943 
       
   944       <query name="succeed-5" date="2006-04-06"/>
       
   945 
       
   946       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   947 
       
   948       <expected-error>XPTY0004</expected-error>
       
   949     </test-case>
       
   950 
       
   951     <test-case
       
   952       Creator="Frans Englich"
       
   953       is-XPath2="true"
       
   954       name="succeed-6"
       
   955       FilePath="ShouldSucceed/"
       
   956       scenario="parse-error">
       
   957       <description>
       
   958         The query results in a parse error with error code XPST0003, while the test-case contains
       
   959         many baselines, one of them the error code XPST0003.
       
   960       </description>
       
   961       <query name="succeed-6" date="2006-04-06"/>
       
   962 
       
   963       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   964 
       
   965       <output-file role="principal" compare="Text">succeed-6-1.txt</output-file>
       
   966       <output-file role="principal" compare="Text">succeed-6-2.txt</output-file>
       
   967       <expected-error>XPTY0004</expected-error>
       
   968       <expected-error>XPST0003</expected-error>
       
   969     </test-case>
       
   970 
       
   971     <test-case
       
   972       Creator="Frans Englich"
       
   973       is-XPath2="true"
       
   974       name="succeed-7"
       
   975       FilePath="ShouldSucceed/"
       
   976       scenario="runtime-error">
       
   977       <description>
       
   978         The query results in a runtime error with error code FOER0000, while the test-case contains
       
   979         many baselines, one of them the error code FOER0000.
       
   980       </description>
       
   981 
       
   982       <query name="succeed-7" date="2006-04-06"/>
       
   983 
       
   984       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
   985 
       
   986       <output-file role="principal" compare="Text">succeed-7-1.txt</output-file>
       
   987       <output-file role="principal" compare="Text">succeed-7-2.txt</output-file>
       
   988       <expected-error>XPTY0004</expected-error>
       
   989       <expected-error>FOER0000</expected-error>
       
   990     </test-case>
       
   991 
       
   992     <test-case is-XPath2="false" name="succeed-8" FilePath="ShouldSucceed/" scenario="standard" Creator="Frans Englich"> 
       
   993       <description>A 'standard' test with multiple baselines that caused an assert crash in KXQTS.</description>
       
   994       <query name="succeed-8" date="2006-04-19"/> 
       
   995       <input-file role="principal-data" variable="input-context1">emptydoc</input-file>
       
   996       <output-file role="principal" compare="Text">succeed-8.txt</output-file>  
       
   997       <expected-error>XQST0046</expected-error>                   
       
   998     </test-case>  
       
   999 
       
  1000     <test-case is-XPath2="true" name="succeed-9" FilePath="ShouldSucceed/" scenario="standard" Creator="Frans Englich">
       
  1001       <description>A test whose comparison method is 'Fragment'. Caused assert in KXQTS.</description>
       
  1002       <query name="succeed-9" date="2006-04-19"/>
       
  1003       <input-file role="principal-data" variable="input-context">bib2</input-file>
       
  1004       <output-file role="principal" compare="Text">succeed-9.txt</output-file>
       
  1005     </test-case>
       
  1006     <test-case is-XPath2="true" name="succeed-10" FilePath="ShouldSucceed/" scenario="runtime-error" Creator="Frans Englich">
       
  1007       <description>A test which accepts any runtime error code, by specifying "*".</description>
       
  1008       <query name="succeed-10" date="2006-04-19"/>
       
  1009       <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
  1010       <expected-error>*</expected-error>
       
  1011     </test-case>
       
  1012     <test-case is-XPath2="false" name="succeed-11" FilePath="ShouldSucceed/"
       
  1013                scenario="standard" Creator="Frans Englich"> 
       
  1014        <description>A 'standard' test that accept output, a particular error code, plus any error code(yes, it makes no sense).</description>
       
  1015        <query name="succeed-11" date="2006-04-19"/> 
       
  1016        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
  1017        <output-file role="principal" compare="Text">succeed-11.txt</output-file> 
       
  1018        <expected-error>XQST0038</expected-error>
       
  1019        <expected-error>*</expected-error>                  
       
  1020    </test-case>
       
  1021 
       
  1022    <test-case is-XPath2="false" name="succeed-12"  FilePath="ShouldSucceed/"
       
  1023               scenario="standard" Creator="Frans Englich">
       
  1024        <description>An "Ignore" baseline with a query that generates output.</description>
       
  1025        <query name="succeed-12" date="2006-10-25"/>
       
  1026        <input-file role="principal-data" variable="input-context">emptydoc</input-file>
       
  1027        <output-file role="principal" compare="Ignore"/>
       
  1028     </test-case>
       
  1029 
       
  1030     <test-case is-XPath2="true" name="succeed-13" FilePath="ShouldSucceed/" scenario="runtime-error" Creator="Frans Englich">
       
  1031         <description>The scenario is runtime-error despite it not having an error baseline, and despite that we succeed on a non-error baseline. This could the driver not handle.</description>
       
  1032         <query name="succeed-13" date="2007-10-23"/>
       
  1033         <output-file compare="Text" role="principal">succeed-13.txt</output-file>                   
       
  1034      </test-case>
       
  1035 
       
  1036     <test-case is-XPath2="true" name="succeed-14" FilePath="ShouldSucceed/" scenario="standard" Creator="Frans Englich">
       
  1037         <description>Check that an XML prolog is not considered a processing instruction when comparing.</description>
       
  1038         <query name="succeed-14" date="2008-02-19"/>
       
  1039         <output-file compare="XML" role="principal">succeed-14.txt</output-file>                   
       
  1040      </test-case>
       
  1041 
       
  1042   </test-group>
       
  1043 
       
  1044 </test-suite>
       
  1045 <!-- // vim: et:ts=2:sw=2:sts=2
       
  1046 -->