Element output with incorrect prefix (bytecode only)
For the element
a:a ns a:= http://example.com/A and element b:a ns b:= http://example.com/A
These are considered as equal at the bytecode level.
#2 Updated by Michael Kay over 8 years ago
More specifically the issue is that Saxon generates bytecode containing the required node-names as static variables. When generating static variables, it eliminates duplicates, and the name objects representing two QNames are considered duplicates if they have the same local name and URI, even if the prefixes are different. Currently a stronger test is used for atomic values (so for example the integer 3 and the decimal 3.0 are not considered duplicates); the fix for this problem introduces a stronger test also for NodeName objects.
Please register to edit this issue