Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #1977

closed

Schema processor does not reject xs:group/xs:sequence/@maxOccurs

Added by Michael Kay over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Michael Kay
Category:
Schema conformance
Sprint/Milestone:
-
Start date:
2014-01-09
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

The schema for schema documents states that a top-level xs:sequence, xs:choice, or xs:all compositor within a named model group must not have a minOccurs or maxOccurs attribute.

Saxon performs this check in the case of xs:choice and xs:all, but does not perform it in the case of xs:sequence.

A patch is being applied in the 9.5 and 9.6 branches. The error has probably been in the code for ever.

Test cases Saxonica/Complex/complex019 and /complex020 have been added to the W3C test suite.

Actions
Copy link
 #1

Updated by O'Neil Delpratt over 10 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in version set to 9.5.1.4

Bug fix applied in Saxon maintenance release 9.5.1.4

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF