[This message was posted by Sean Holohan of NYSE Technologies <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/6c5f79b5 - PLEASE DO NOT REPLY BY MAIL.]
Quite right, Hanno. In addition, it becomes even more difficult to identify what's 'custom' when a FIX spec uses the same tag but changes the data type. Arun, as Hanno mentioned each FIX destination has its own flavor of FIX when it comes to tags, values and data types. Therefore the best practice would be to define the datadict structure that includes all the tags, values and data types specific for the destination. Additionally, TCM's datadict structure has no out-of-the-box metadata that indicates whether a tag is custom or not. Therefore there are no APIs around getting that information on a tag. However you can simply compare a tag from a custom datadict to a tag from the FIX spec that you're interested in (which comes with TCM). I'd be interested in hearing what the use-case is for identifying a specific tag as custom. Does it have to do with protocol normalization? > Technically, all tags with numbers between 5000 and 9999 are user- > defined (custom) tags. This does not mean that a specific implementation > might not follow the FIX semantic and simply use a standard tag as a > container for a different purpose. There are also "good" and "bad" > custom tags, i.e. if they are mere additional attributes or if they > change the fundamental behavior/usage of the message. This typically > requires detailed analysis. > > > Hi, I would like to know how can we find which tags are custom tags in > > given Fix message. Does TCM api's provide some methods etc to achieve > > this purpose? [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
