Re: Needed: output comparitors

>>The basic XML comparitor confirms that two XML documents are equal
>>at the InfoSet level. Thus, it has to neutralize the order of
>>attributes and namespace nodes.

DHM>Would XML Canonicalization fit this requirement?

Almost. If the output of the canonicalizer is serialized, then we
need to ensure that both outputs (actual and expected) are serialized
the same way after canonicalization. If the output is left as a data
structure in memory, then we need a routine to compare two such
structures and report whether they are "equal" in this sense, and it
might be just as easy to skip the separate canonicalization. Also,
the in-memory compare raises issues of platform neutrality.

>>A second comparitor is needed to check the output of a product that
>>implements the Serialization spec because there are requirements
>>to produce CDATA sections and other details below the InfoSet level.

DHM>Could you give a few examples of such requirements?

See the table at
http://www.w3.org/TR/xslt-xquery-serialization/#serparam
(note especially use-character-maps)

I should also mention that in the XSLT/XPath Conformance testing
group, we specified that we were checking namespaces by seeing if
they were in-scope when needed, rather than checking exactly where
they were positioned in the tree.
.................David Marston

Received on Monday, 16 August 2004 14:30:58 UTC