Project

Profile

Help

Bug #4361

closed

Multiple function bindings for EXPath Archive extract-map()

Added by John Lumley over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Saxon extensions
Sprint/Milestone:
-
Start date:
2019-10-25
Due date:
% Done:

0%

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

Description

Calling the (unsupported/defined) function Q{http://expath.org/ns/archive}extract-map() fails with possible mutliple bindings.

This call is only documented in an editor version of the EXPath Archive spec, and not in the main specification (http://expath.org/spec/archive) which used a different namespace of map-defined forms of the functions, and as such was an experimental piece of code that stayed in the SaxonPE/EE code base.

Historically, the EXPath archive specification, which was a generalisation/development of the earlier EXPath Zip module, was never finalised and the Saxon implementation stands as that defined in the last editor's draft (i.e. http://expath.org/spec/archive/editor). In this case the *-map() calls have been implemented but, as in this case, not tested.

We'll have to consider how/whether we'll change the support.

Actions #2

Updated by Michael Kay over 4 years ago

  • Category set to Saxon extensions
  • Status changed from New to Resolved
  • Fix Committed on Branch 9.9, trunk added

For 9.9 and trunk, I have renamed one of the extractMap() methods so that (a) there should no longer be a binding conflict, and (b) the one that remains corresponds to the Saxonica documentation cited above.

Actions #3

Updated by O'Neil Delpratt over 4 years ago

  • Status changed from Resolved to Closed
  • Fixed in Maintenance Release 9.9.1.6 added

Patch committed to the Saxon 9.9.1.6 maintenance release.

Please register to edit this issue

Also available in: Atom PDF