Project

Profile

Help

Bug #3479

closed

QName-valued template parameters

Added by Michael Kay over 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
2017-10-10
Due date:
% Done:

0%

Estimated time:
Applies to JS Branch:
Fix Committed on JS Branch:
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

Calling templates with parameters whose names are written as QNames fails if the calling and called templates use different namespace prefixes.

The map holding template values is indexed by the name appearing in the name attribute of the param/withParam elements of the SEF file, and this is the lexical QName as written in the source.

I'm changing this on the JS2 branch to put EQNames in the SEF file.

I'm not sure it's worth fixing on the JS1 branch (who actually does this?) but if so the solution will be a bit more complex because of the constraints on SEF file compatibility.

I added a test case call-template-0702.

Note that we also need to handle EQNames, including the equivalence of NNN and Q{}NNN. Added another test case call-template-0703 for this case.

I have committed a patch on the 9.8 branch that causes LocalParam and WithParam to export the name in the form of an EQName, which solves the problem for Saxon-JS2.

Actions #1

Updated by Michael Kay over 4 years ago

  • Description updated (diff)
  • Status changed from New to Closed

Fixed for 2,0; not worth fixing for earlier releases.

Please register to edit this issue

Also available in: Atom PDF Tracking page