[This message was posted by Matthew Rawlings of JP Morgan <[email protected]> to the "FIXML" discussion forum at http://fixprotocol.org/discuss/7. You can reply to it on-line at http://fixprotocol.org/discuss/read/d3b36d13 - PLEASE DO NOT REPLY BY MAIL.]
This is my personal advice and doesn't reflect the views of any client or employer, past or present. I have setup canonical models at some of the big names in fund management and investment banking, and have a long involvement in the messaging standards. #1 Don't directly edit the FIXML XSD files as then you'll have trouble incorporating FIX upgrades. #2 Don't put things in the FIX namespace that aren't genuine FIX #3 Do download and use the FIX Repository to manage your own canonical form, just as FIX uses the Repository to manage FIX #4 Do remember SWIFT is not a Standard. SWIFT uses the Standards ISO 15022 and ISO 20022 for messages #5 Do remember the canonical form includes the data codes in the message and not just the message definitions #6 Do remember that mapping messages is much easier than mapping the message choreographies, especially as FIXT makes FIX messages sequenced unlike ISO 20022's unsequenced messages #7 Do remember ISO 20022's XSDs put the same element in different namespaces per message definition #8 Do read XFront http://www.xfront.com #9 Do pick one Standard's style to follow no matter how many different messaging standards you import or include #10 Do remember the canonical message model is just models of message layout and not models of the meaning of the data [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=.
