Is there a standard method for all API's to enable the publishing of their API version to TREP. It appears to be available in some API's by default and not in others.
No, this info is passed at the library tier, it is not controlled by the application. There is no action required from the application. It is intended for monitoring, and is not related to MIFID.
Could you please explain what could cause the concern for your users?
Your understanding is correct, it will not send it.
RFA has been enhanced to supply this information to the infrastructure beginning with version 7.4
Please refer to API README found with SDK for the full details on this enhancement.
Please refer to APi Obsolescence section to get the latest information on API support.
I understand this is not related to MiFID. My concern is do we have applications that will not support MiFID. If I am understanding correctly. If they are not passing their app version then they are running something less than RFA 7.4. I have noticed that older SSL apps populated something as well. Do you have a matrix of versions that are reported to their actual versions.
We have seen this in TREP.
Example "UPA Java Version" = ???
On the concern,
This depends on what you require. If you are asking if your code will break, this is unlikely, as the MIFID data will be distributed via new sets of fids, MS_... and NS_... if you application was not parsing these fids previously, it will not do so now.
However, if you are interested in fully verifying this aspect is working as expected, if you are a customer, there is a way to test. You can download from our Customer Zone a test package MIFID_test_data, it comes with the instructions and you can use it to test your applications for MIFID compliance.
the version you see should be the correct version, for UPA below 7.4 it should not show. UPA above 7.4, version should show.