Imported from previous forum
Does anybody know if there is any document from FIX or ISO that clearly specifies
"mapping of every FIX Protocol tag to the appropriate element in the message component in the ISO15022"
Thanks in advance
MK
Muralidhar,
I am on the FIX ISO 15022 XML working group.
As John Goeller mentioned earlier, you can find some more information about what we are doing under the ISO XML archive. Specifically, we have published a draft pre-trade model document that covers IOI’s.
In addition, we (FIX ISOXML WG) are meeting tomorrow. We will see if we can make a draft version of the convergence document for IOI’s available to the public. The convergence table is listed as a related document in the pre-trade model and contains the mapping that you mention in your e-mail, but only for the FIX IOI message.
Regards,
Will Walter
TransactTools
> Does anybody know if there is any document from FIX or ISO that clearly specifies
>
> "mapping of every FIX Protocol tag to the appropriate element in the message component in the ISO15022"
>
>
> Thanks in advance
> MK
>
>
>
Thanks walter for the response,
However my questions are still fundamental, what is the process to get my existing FIX4.3 messages thru SWIFTNetFIX. I am sure you agree that I need to convert all the messages to 15022 format (correct?). Do you have a draft versin (after your October 9th meeting)about how we can map each of the 4.3FIX messges to ISO15022.
Thanks
Muralidhar
> Muralidhar,
>
> I am on the FIX ISO 15022 XML working group.
>
> As John Goeller mentioned earlier, you can find some more information about what we are doing under the ISO XML archive. Specifically, we have published a draft pre-trade model document that covers IOI’s.
>
> In addition, we (FIX ISOXML WG) are meeting tomorrow. We will see if we can make a draft version of the convergence document for IOI’s available to the public. The convergence table is listed as a related document in the pre-trade model and contains the mapping that you mention in your e-mail, but only for the FIX IOI message.
>
> Regards,
>
> Will Walter
> TransactTools
>
>
>
>
>
>
> > Does anybody know if there is any document from FIX or ISO that clearly specifies
> >
> > “mapping of every FIX Protocol tag to the appropriate element in the message component in the ISO15022”
> >
> >
> > Thanks in advance
> > MK
> >
> >
> >
>
Muralidhar,
at the risk of possibly creating more confusion ;-)) let me clarify the issue you have.
SWIFTNet for FIX is a FIX Value Added Network that allows you to connect to other brokers through a single connection on your side provided the brokers you want to connect to are also on SWIFTNet for FIX.
You would connect to SWIFTNet for FIX with your FIX ( probably v 4.3 - not sure ?) compliant FIX Engine. So no need to translate on your part at all.
As I understand SWIFT the operators of SWIFTNet for FIX will within their network translate to SWIFT 15022 cmpliant Messages and retranslate back to FIX (V 4.x) on the other side where your broker in connected to the network. In other word its completely transparent and in fact irrelevat as far a s you are concerned.
Its a great experiment on the convergengce of FIX & SWIFT but really at this time only for SWIFT and SWIFT alone to savour or suffer from.
So you need not worry. What you also should realise is that SWIFTnet for Fix is only one of the Value added networks available and you also have to the option of linking up with your broker via VPN or leased lines etc. So its only one option out of many.
Given the dominance, reputation and experience it is definitely something worth watching though.
Best Regards,
Marcelle
Marcelle von Wendland MSI
UBS AG
Global Asset Mgmt
B&IT Asset Mgmt
Gessnerallee 3-5
8098 Zürich
Switzerland
Email…: Marcelle.von-Wendland@ubs.com
Tel…: +41 1 2345710
Fax…: +41 1 2354639
> Thanks walter for the response,
>
> However my questions are still fundamental, what is the process to get my existing FIX4.3 messages thru SWIFTNetFIX. I am sure you agree that I need to convert all the messages to 15022 format (correct?). Do you have a draft versin (after your October 9th meeting)about how we can map each of the 4.3FIX messges to ISO15022.
>
> Thanks
> Muralidhar
>
>
>
>
>
> > Muralidhar,
> >
> > I am on the FIX ISO 15022 XML working group.
> >
> > As John Goeller mentioned earlier, you can find some more information about what we are doing under the ISO XML archive. Specifically, we have published a draft pre-trade model document that covers IOI’s.
> >
> > In addition, we (FIX ISOXML WG) are meeting tomorrow. We will see if we can make a draft version of the convergence document for IOI’s available to the public. The convergence table is listed as a related document in the pre-trade model and contains the mapping that you mention in your e-mail, but only for the FIX IOI message.
> >
> > Regards,
> >
> > Will Walter
> > TransactTools
> >
> >
> >
> >
> >
> >
> > > Does anybody know if there is any document from FIX or ISO that clearly specifies
> > >
> > > “mapping of every FIX Protocol tag to the appropriate element in the message component in the ISO15022”
> > >
> > >
> > > Thanks in advance
> > > MK
> > >
> > >
> > >
> >
>
[ original email was from Frank Vandamme - frank.vandamme@swift.com ]
All,
I would like to clarify this discussion on the SWIFT initiatives and support for FIX.
SWIFT, in its capacity as standards organisation, is working with FIX protocol Ltd. on future standards convergence. Last year FIX and SWIFT signed a Memorandum of Understanding to work on the convergence of their XML message sets under the ISO umbrella. The driver for this collaboration is the second edition of ISO 15022 (i.e. the XML-aware version of ISO 15022). Currently two project teams have started working on this convergence in two specific business areas in Securities (namely pre-trade and post-trade). One of the results of these projects will be the so-called "convergence documentation" that will describe the relationship between - for instance - a FIX message and a corresponding ISO 15022 XML message. Given the complexity and the amount of work it will take some time before this yields concrete usable results (convergence documentation for pre-trade is tentatively scheduled for mid 2003 - post-trade will be later).
SWIFT, as a supplier of messaging infrastructure to the industry, has also recently launched the SWIFTNet FIX Service. The SWIFTNet FIX Service includes a central value-add application that enables each user to communicate with many trading partners over a single FIX session. This is a Hub architecture rather than a VPN architecture and combined with the SWIFT global managed network is a really unique service. It currently supports FIX 4.0, 4.1 and 4.2, and will support FIX 4.3 and all future versions of FIX. Any FIX Engine will be able to send FIX messages over SWIFTNet using the FIXConnector software. To ensure compatibility with the service SWIFT is in the process of validating all FIX Engine and Order Management Systems under out SWIFTNet Ready Label Program.
The work on standards convergence is independent of the launch of the SWIFTNet FIX service. SWIFTNet FIX provides a FIX messaging service for the market now and will be ready to support the future outcome of the standards convergence work. There is currently no translation or FIX version conversion taking place over the SWIFTNet FIX Service. As a possible interim solution before the above described standards convergence is achieved we are considering the translation of FIX 4.n to the SWIFT 5nn messages, and of FIX to GSTP standards. However, there is no commitment for either and SWIFT is still in the process of evaluating market demand.
Best regards,
Frank Vandamme
Senior Technical Advisor, Standards
SWIFT
>
> Muralidhar,
>
> at the risk of possibly creating more confusion ;-)) let me clarify the issue you have.
>
> SWIFTNet for FIX is a FIX Value Added Network that allows you to connect to other brokers through a single connection on your side provided the brokers you want to connect to are also on SWIFTNet for FIX.
>
> You would connect to SWIFTNet for FIX with your FIX ( probably v 4.3 - not sure ?) compliant FIX Engine. So no need to translate on your part at all.
>
> As I understand SWIFT the operators of SWIFTNet for FIX will within their network translate to SWIFT 15022 cmpliant Messages and retranslate back to FIX (V 4.x) on the other side where your broker in connected to the network. In other word its completely transparent and in fact irrelevat as far a s you are concerned.
>
> Its a great experiment on the convergengce of FIX & SWIFT but really at this time only for SWIFT and SWIFT alone to savour or suffer from.
>
> So you need not worry. What you also should realise is that SWIFTnet for Fix is only one of the Value added networks available and you also have to the option of linking up with your broker via VPN or leased lines etc. So its only one option out of many.
>
> Given the dominance, reputation and experience it is definitely something worth watching though.
>
> Best Regards,
> Marcelle
>
> Marcelle von Wendland MSI
> UBS AG
> Global Asset Mgmt
> B&IT Asset Mgmt
> Gessnerallee 3-5
> 8098 Zürich
> Switzerland
>
> Email…: Marcelle.von-Wendland@ubs.com
> Tel…: +41 1 2345710
> Fax…: +41 1 2354639
>
> > Thanks walter for the response,
> >
> > However my questions are still fundamental, what is the process to get my existing FIX4.3 messages thru SWIFTNetFIX. I am sure you agree that I need to convert all the messages to 15022 format (correct?). Do you have a draft versin (after your October 9th meeting)about how we can map each of the 4.3FIX messges to ISO15022.
> >
> > Thanks
> > Muralidhar
> >
> >
> >
> >
> >
> > > Muralidhar,
> > >
> > > I am on the FIX ISO 15022 XML working group.
> > >
> > > As John Goeller mentioned earlier, you can find some more information about what we are doing under the ISO XML archive. Specifically, we have published a draft pre-trade model document that covers IOI’s.
> > >
> > > In addition, we (FIX ISOXML WG) are meeting tomorrow. We will see if we can make a draft version of the convergence document for IOI’s available to the public. The convergence table is listed as a related document in the pre-trade model and contains the mapping that you mention in your e-mail, but only for the FIX IOI message.
> > >
> > > Regards,
> > >
> > > Will Walter
> > > TransactTools
> > >
> > >
> > >
> > >
> > >
> > >
> > > > Does anybody know if there is any document from FIX or ISO that clearly specifies
> > > >
> > > > “mapping of every FIX Protocol tag to the appropriate element in the message component in the ISO15022”
> > > >
> > > >
> > > > Thanks in advance
> > > > MK
> > > >
> > > >
> > > >
> > >
> >
>