Failed to validate correctly when schema has <xsd:extension> and the base has an attribute Problem with recursive and derived elements minInclusive factet validation alters value maxOccurs="0" is considered an error Model group 'All' with minOccurs='0' reports an error Schema ID validation can fail depending on declaration ordering Incorrect Schema Validation Failure When Redefining Complex Type with Simple Content Validator doesn't enforce xsd:key data from CDATA section is not passed for validation Does implement co-occurence constraints Empty complex type definition is always non-mixed even if declaration says otherwise failure to load grammar if an abstract element is in substitutionGroup of another abstract element References to attributeGroup/group definition are not allowed to have annotations Cyclic import doesn't correctly handle type restrictions The type of an element should depend also on the substitutionGroup attribute xsi:type for union types with pattern facet doesn't work Crash when maxOccurs >= 200000 xs:unique is used like xs:key Schema length validation error in unions Pre-loaded grammar and xsi:type in the root element Regular expressions in schema should allow unescaped '-' Identity constraint is not enforced on xs:anySimpleType Regular expressions in schema should allow unescaped '-' Bad XS:pattern interpretation for XSD length, maxLength, and minLength facets are applied to item instead of list when value specific via default/fixed keyref are not processing with imported schema Mishandling of recursive definition on complex content restriction Namespace handling is wrong in schema validation The type reference will fail when importing a no-namespace schema Using 'list' or 'union' for finalDefault in schema element causes incorrect validation errors Multi-import and schemaLocation ordering Multi-import and schemaLocation ordering Multi-import and schemaLocation ordering Multi-import and schemaLocation ordering Processing of not-declared-element with "xsi:type" under anyType element does not clear SchemaValidator::fXsiType xerces-c reports "Base type definition does not have any attributes" for a valid complex type restriction Invalid anonymous type definition with the name attribute is not caught in some situations Inheritance by restriction does not detect a missing type from an imported schema Bug in schema processing (using the "xsd:extension" for an another file) since v2.8.0 Restriction checking code resolves an element from a wrong schema grammar Wildcard namespace prefixes in XPath are not reported as errors Registry-based URI authority validation Outdated interpretation of ##other Regression - Schema Error for valid Substition Group Regression - Schema Error for valid Substition Group Failure to validate valid instance Regression with handling of ANY Regression with handling of ANY Default value of QName type with non-empty prefix causes segfault Default value of QName type with non-empty prefix causes segfault Xerces-c can not parse instance with special chars (", < and >) in target namespace Namespace definitions attached to xs:extension/xs:restriction are not processed Validation of xs:keys and xs:keyrefs with xpath takes too long Error reported when defining a complex type as an extension of an imported simple type Error reported when defining a complex type as an extension of an imported simple type