Feature #4955
closed
Getting absolute xpath in XdmAtomicValue
Category:
XPath conformance
Fixed in Maintenance Release:
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.
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.
Can we push to some customary branch and use in production code?
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.
- 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