W3C home > Mailing lists > Public > public-xml-testsuite@w3.org > May 2002

Re: More test suite problems

From: Glenn Marcy <gmarcy@us.ibm.com>
Date: Tue, 28 May 2002 09:03:12 -0400
To: public-xml-testsuite@w3.org
Cc: w3c-xml-core-wg@w3.org
Message-ID: <OF3F169D61.7EEA5BF3-ON85256BC7.00464287@rchland.ibm.com>

Glenn writes:
>There is also the following problem discovered by the Xerces
>parser that I am not sure how to solve.
>
>Output Tests:
>ibm-valid-P28-ibm28v02.xml
>ibm-valid-P29-ibm29v01.xml
>ibm-valid-P29-ibm29v02.xml
>ibm-valid-P57-ibm57v01.xml
>ibm-valid-P58-ibm58v01.xml
>ibm-valid-P58-ibm58v02.xml
>ibm-valid-P70-ibm70v01.xml
>
>Xerces resolves and returns the complete path of systemIds for
>notation decls, where as the actual outputs do not and can not
>contain complete resolved paths for systemIds.  Xerces appears
>to behave in accordance with the SAX API...
>
>    notationDecl
>    .....
>    If a system identifier is present, and it is a URL, the
>    SAX parser must resolve it fully before passing it to the
>    application through this event.
>
>I am not sure what we can do at this point to support expected
>results files for documents that have absolute path names in
>their infoset.
>
>Does anyone have any thoughts or suggestions for how this
>issue can be addressed?  Otherwise, I think that we would need
>to remove the expected results files for these tests.

One thing that I should have mentioned is that SAX is certainly
inconsistant with the Infoset specification on this point given
this description from Notation information item:

  2. [system identifier] The system identifier of the notation,
     as it appears in the declaration of the notation, without
     any additional URI escaping applied by the processor. If
     no system identifier was specified, this property has no
     value.

However, if most people are testing conformance using the SAX
API and the SAX implementations are "correct" then we cannot
get the correct infoset to test expected results conformance.

One idea that came to me would be to add a new attribute to
the test suite descriptions similar to NAMESPACE that could
be used by a SAX based test harness to identify those tests
that cannot be compared with the expected output.

Best Regards,
Glenn
Received on Tuesday, 28 May 2002 09:04:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:22:04 GMT