Bug #6153: XSD blockDefault effect on complex types - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #6153

closed

XSD blockDefault effect on complex types

Added by Michael Kay 9 months ago. Updated 5 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

Updated by Michael Kay 9 months 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