Hi,
while working on XMP Meta Data I noticed that the XPath node fails to validate the XPath which references an attribute with a colon. Interestingly, the XPath actually the one which the node suggests to use, though:
Here is the test workflow. Please note that I have NOT tested other characters which should, theoretically, be valid to use!
Best
Mike
Hi @mwiegand,
To get the value of the attribute with a colon, you can use @*[name()='<attribute:name>']. e.g.:
/rdf:Description/@*[name()='aux:Firmware']
Yes, that is the „fallback“ approach I integrated in my example workflow. I was under the impression, since a colon is supported in the path declaration for leaves, it‘s a bug.
Yes, I didn’t notice the “fallback” in your workflow and I think it’s a good idea to share it with the community.
I’ll discuss this internally and will come back to you soon.
Dear @mwiegand,
I created a ticket for the issue you have mentioned here. (AP-20866)
About the “leaves” or elements, colons are used after the namespaces. So, they are not part of the element name. The reason I have doubts not to consider this issue as a bug is the same fact that typically, colons in XML indicate namespace demarcation (e.g.). Yet, as I promised, I discussed it internally and we decided to have a ticket for it and investigate it further.
Thanks. Doesn’t the name space declaration using colons only apply for doubled colons “::”? Anyways, leaving it to you guys. Cheers and thanks again!
I don’t think so! 
