Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #6153

closed

XSD blockDefault effect on complex types

Added by Michael Kay about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Michael Kay
Category:
Schema conformance
Sprint/Milestone:
-
Start date:
2023-08-03
Due date:
% Done:

80%

Estimated time:
Legacy ID:
Applies to branch:
10, 11, 12, trunk
Fix Committed on Branch:
10, 11, 12, trunk
Fixed in Maintenance Release:
12.4, 11.6
Platforms:
.NET, Java

Description

It seems that when a complex type has no @block attribute, we (correctly) look at the @blockDefault on the containing xs:schema, and then (incorrectly) use the value to set the final property rather than the block (aka {prohibited substitutions} property.

The reason that the tests for blockDefault appear to work is that it applies both to element declarations and to types, and in all the relevant test cases, the relevant element declaration is in the same schema document as the type declaration, and substitution is effectively blocked by the element declaration.

Actions
Copy link
 #1

Updated by Michael Kay about 1 year ago

Added two variants of the XSD test group SunTest/combined/test003 to test what happens when extension is blocked on types but not on elements, and vice versa. The test group test003a demonstrates the problem; test003b is added for completeness.

Actions
Copy link
 #2

Updated by Michael Kay about 1 year ago

  • Status changed from New to Resolved
  • Applies to branch 10, 11, 12, trunk added
  • Fix Committed on Branch 10, 11, 12, trunk added
  • Platforms .NET, Java added

Fixed on 10, 11, 12 branches, and on multiple-schemas-2 branch pending integration back into main.

Actions
Copy link
 #3

Updated by Debbie Lockett about 1 year ago

  • % Done changed from 0 to 50
  • Fixed in Maintenance Release 11.6 added

Bug fix applied in the Saxon 11.6 maintenance release.

Actions
Copy link
 #4

Updated by Michael Kay about 1 year ago

  • Category set to Schema conformance
Actions
Copy link
 #5

Updated by Michael Kay about 1 year ago

  • Status changed from Resolved to In Progress

The new tests appear to be failing on the 12.x and main branches, so I'm reopening the bug.

Actions
Copy link
 #6

Updated by Michael Kay about 1 year ago

  • Status changed from In Progress to Resolved

Now fixed on 12.x and main. (Part of the patch was missing).

Actions
Copy link
 #7

Updated by O'Neil Delpratt 11 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 50 to 100
  • Fixed in Maintenance Release 12.4 added

Bug fix applied in the Saxon 12.4 Maintenance release

Actions
Copy link
 #8

Updated by Debbie Lockett 11 months ago

  • Status changed from Closed to Resolved
  • % Done changed from 100 to 80

Leave as "resolved" rather than "closed" as fix has not gone out in a Saxon 10 maintenance release.

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF