Project

Profile

Help

Feature #4955

closed

Getting absolute xpath in XdmAtomicValue

Added by meghana agrawal almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XPath conformance
Sprint/Milestone:
Start date:
2021-03-30
Due date:
% Done:

0%

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

Description

For cases, when giving xpath expression, we get XdmItem in 2 forms, XdmNode and XdmAtomicValue. We can get xpath if it is XdmNode but not in case of XdmAtomicValue. I made changes in FilterIterator, FirstItemExpression, Atomizer for this. Can this change be incorporated by your end. If no, can I pass on the change.

Actions #1

Updated by meghana agrawal almost 3 years ago

This is for Saxon-HE

Actions #2

Updated by Michael Kay almost 3 years ago

No sorry, that's totally against the XDM data model. Atomic values like "3" and "London" do not have any identity or location, the "London" that you get by concatenating "Lon" and "don" is exactly the same "London" that you get by taking the first six characters of "Londonderry". A string has no information about the provenance whence it came.

If you want this kind of location information, retrieve a text node, not an atomic value.

Actions #3

Updated by meghana agrawal almost 3 years ago

Can we push to some customary branch and use in production code?

Actions #4

Updated by Michael Kay almost 3 years ago

Saxon is open source software and you can do anything you like with it, but I don't think this is a good thing to do and it won't have my support.

Actions #5

Updated by Michael Kay almost 3 years ago

  • Status changed from New to Closed

Thanks for your interest in enhancing the product, but we don't think this is a desirable thing to do, so I'm closing this as a "won't fix". Sorry to disappoint.

Please register to edit this issue

Also available in: Atom PDF