Project

Profile

Help

Bug #4915

closed

NestedIntegerValue is only partially implemented

Added by Michael Kay over 1 year ago. Updated 4 months ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
2021-02-23
Due date:
% Done:

100%

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

Description

The type saxon:nestedIntegerValue is partially implemented. It validates values of the form 123.45.00.1. It was implemented to meet a practical need and as an experiment in schema extensibility, but it is not well tested and supported. For example, there is no alpha code allocated, and there are plenty of places in the code that assume the 19 built-in primitive types of XSD, even though the XSD specification permits extensions.

Actions #1

Updated by Michael Kay about 1 year ago

The class is used internally to represent version numbers and import precedence values; it's intrinsically useful, but extending it to work fully as a primitive atomic type is significant effort (especially in testing). I'm wondering whether it would be better represented as a custom list type: list of xs:integer, with the saxon:separator facet set to "."?

Actions #2

Updated by Michael Kay 5 months ago

  • Status changed from New to Resolved
  • Fix Committed on Branch 11, trunk added

I have modified the class (on the 11,x branch) so that NestedIntegerValue no longer extends AtomicValue, in fact it is no longer an XDM value, just an ordinary Java object.

Actions #3

Updated by Debbie Lockett 4 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 11.2 added

Bug fix applied in the Saxon 11.2 maintenance release.

Please register to edit this issue

Also available in: Atom PDF