Project

Profile

Help

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:
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:
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.

Please register to edit this issue

Also available in: Atom PDF