#1122 anyAttribute intersection with notQName=##defined

v9.3
closed
Michael Kay
5
2012-10-08
2011-02-07
Michael Kay
No

When Saxon forms the interesection of two attribute wildcards (needed, for example, when a complexType definition has two attributeGroup children and both include an xs:anyAttribute wildcard), then Saxon puts notQName="##defined" on the resulting wildcard only if it is present on both the input wildcards; it should do so if it is present on either of the inputs. A patch will be applied to the 9.3 branch. (Saxonica-only code module Wildcard)

Discussion

  • Michael Kay
    Michael Kay
    2011-04-21

    Fixed in 9.3.0.5