OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] ANN: X-Hive/DB 7.0 Released

[ Lists Home | Date Index | Thread Index ]
  • To: mike@saxonica.com
  • Subject: Re: [xml-dev] ANN: X-Hive/DB 7.0 Released
  • From: David Carlisle <davidc@nag.co.uk>
  • Date: Thu, 20 Oct 2005 13:08:37 +0100
  • Cc: xml-dev@lists.xml.org
  • In-reply-to: <200510201151.MAA01682@nag.co.uk> (mike@saxonica.com)
  • References: <200510201151.MAA01682@nag.co.uk>

> I also found a large number of tests where I had to apply much looser rules
> to comparison of test results than those prescribed, for example by
> stripping XML declarations at the start of a file or newlines at the end.
> Again, I'd be interested whether you had the same experience.

Certainly that was my experience, in the test report for xq2xsl

I make the following comments


    XML: The result of is not serialised. The expected result is parsed
    using doc() and compared using deep-equal(), if this fails, text
    nodes are normalized with normalize-space(), then deep-equal() is
    retried (Use of normalize-space is noted in the comment field in
    this case). 

    Fragment: The result is not serialised. The expected result is
    wrapped in an element node so it can be parsed by an XML parser, the
    child nodes of this element are then compared using deep-equal (and
    optionally normalize-space, as for the XML comparision). 

    Text: The result of is not serialised, its string value is compared
    (optionally after using normalize-space()) with the expected result,
    which is read using XSLT unparsed-text() function. The comment field
    records if normalize-space() was used. 

    Errors are currently NOT compared. If (any) error is expected, (any)
    error raised is considered to be a test pass. (Due to limitations of
    the test harness): This should be fixed in time for a future version
    of the test suite 

Looking in the comment fields shows that white space normalization  was
applied in a _lot_ of cases. It's possible that some of these are
masking problems in xq2xsl, but I suspect most are due to spurious white
space in the expected results. In half a dozen or so cases I had to
change the Catalog to change the comparator _not_ to use XML (as the
published result file isn't well formed) This is for 0.7 but I had to
make similar changes for 0.6, basically I updated as need be if there
was a bugzilla entry indicating what fix was going to be applied.


This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS