JCK : JCK6.0 b16
J2SE : FAIL - mustang b69
Platform[s] : FAIL - Solaris10 on Niagara, Windows XP, seems to be all
switch/Mode : FAIL - default



api/xml_schema/msxsdtest/identityConstraint/idI009.html#idI009 fails due to expression

<xsd:selector xpath="child::imp:iid"/>

test's response is:

Error: file:/C:/niagara/idI009.xsd(18,42): c-general-xpath: The expression 'child::imp:iid' is not valid with respect to the XPath subset supported by XML Schema.
STATUS:Failed.1 errors, 0 warnings.


According specification of XPath (see http://www.w3.org/TR/1999/REC-xpath-19991116#path-abbrev )

" The most important abbreviation is that child:: can be omitted from a location step. In effect, child is the default axis. For example, a location path div/para is short for child::div/child::para. "

BUT, if I change expression to

<xsd:selector xpath="imp:iid"/>

test passes. So problem seems to be in child:: processing.

if seems the following tests has the same problem with child::

api/xml_schema/msxsdtest/identityConstraint/idI013.html#idI013
api/xml_schema/msxsdtest/identityConstraint/idI024.html#idI024
api/xml_schema/msxsdtest/identityConstraint/idI025.html#idI025
api/xml_schema/msxsdtest/identityConstraint/idI009.html#idI009
api/xml_schema/msxsdtest/identityConstraint/idJ010.html#idJ010
api/xml_schema/msxsdtest/identityConstraint/idJ014.html#idJ014
api/xml_schema/msxsdtest/identityConstraint/idL004.html#idL004_i
api/xml_schema/msxsdtest/identityConstraint/idL010.html#idL010_i
api/xml_schema/msxsdtest/identityConstraint/idL014.html#idL014_i
api/xml_schema/msxsdtest/identityConstraint/idL029.html#idL029_i
api/xml_schema/msxsdtest/identityConstraint/idL035.html#idL035_i
api/xml_schema/msxsdtest/identityConstraint/idL039.html#idL039_i
api/xml_schema/msxsdtest/identityConstraint/idL054.html#idL054_i
api/xml_schema/msxsdtest/identityConstraint/idL060.html#idL060_i
api/xml_schema/msxsdtest/identityConstraint/idL064.html#idL064_i



this problem tightly connected with lots of negative tests. This tests should be checked if they fail not due to incorrect processing of child::

all necessary files to reproduce bug are attached.
Sunitha, could you comment paragraph 2.2 from section 3.11.6:

*2.2 It must be an XPath expression involving the child axis whose abbreviated form is as given above.*

As far as I understand it means that child: is allowed axis.