Imported from previous forum
[ original email was from Ainhoa Dewisme - ainhoa.dewisme@reuters.com ]
Hello,
Are there any plans to extend FIX protocol to support reference/permission messages? For example, list of counterparties a customer may be able to trade, list of accounts, instruments, etc …
If there are any plans, which is the best way to contribute onto the discussion?
If there are no plans, does FIX Protocol offer guidelines on how custom messages may be defined?
Thanks and Regards
Ainhoa
[ original email was from Rikard Hedberg - rikard.hedberg@omxgroup.com ]
Ainhoa,
Instruments are supported by the Security Definition, Security List, etc messages. Any day now GTC approval is expected for extensions with new messages and numerous fields in the derivatives area (will be part of 5.0 SP1). That extension also means reference data for other asset classes must be considered relevant for FIX. I hope the Global Exchanges and Markets Committee (GEXMC) will start a Gap Analysis soon, but note that reference data is a huge area where standardization has been attempted before.
I’d recommend you to be active in the GEXMC.
I have not seen a recommendation for custom messages, but would recommend you to follow the principles of other reference data messages and workflows.
Regards
Rikard
Hello,
Are there any plans to extend FIX protocol to support
reference/permission messages? For example, list of counterparties a
customer may be able to trade, list of accounts, instruments, etc …If there are any plans, which is the best way to contribute onto the
discussion?If there are no plans, does FIX Protocol offer guidelines on how custom
messages may be defined?Thanks and Regards
Ainhoa
Ainhoa,
FIX permits custom messages to be defined using Message Type (Tag 35) having a value starting with “U” (upper case U) like U1,U2…etc. and the message fields format is privately defined between the sender and receiver. Please take note that lower case “u” is “Cross Order Cancel Request” from FIX.4.3 onwards.
Another option is to use custom fields - this would be a good alternative when there is an existing standard FIX message which almost does what is needed but lacks fields for few data elements, add that as custom fields. You may take a look at User Defined Fields Repository at
http://fixprotocol.org/specifications/fields/5000-9999
Regards,
Mahesh
Ainhoa,
Instruments are supported by the Security Definition, Security List, etc
messages. Any day now GTC approval is expected for extensions with new
messages and numerous fields in the derivatives area (will be part of
5.0 SP1). That extension also means reference data for other asset
classes must be considered relevant for FIX. I hope the Global Exchanges
and Markets Committee (GEXMC) will start a Gap Analysis soon, but note
that reference data is a huge area where standardization has been
attempted before.I’d recommend you to be active in the GEXMC.
I have not seen a recommendation for custom messages, but would
recommend you to follow the principles of other reference data messages
and workflows.Regards
Rikard
Hello,
Are there any plans to extend FIX protocol to support
reference/permission messages? For example, list of counterparties a
customer may be able to trade, list of accounts, instruments, etc …If there are any plans, which is the best way to contribute onto the
discussion?If there are no plans, does FIX Protocol offer guidelines on how
custom messages may be defined?Thanks and Regards
Ainhoa
[ original email was from Ainhoa Dewisme - ainhoa.dewisme@reuters.com ]
Hello Rikard,
I am very keen in contributing to the discussions in any way I can.
Do you know the process I should follow?
Regards
Ainhoa
Ainhoa,
Instruments are supported by the Security Definition, Security List, etc
messages. Any day now GTC approval is expected for extensions with new
messages and numerous fields in the derivatives area (will be part of
5.0 SP1). That extension also means reference data for other asset
classes must be considered relevant for FIX. I hope the Global Exchanges
and Markets Committee (GEXMC) will start a Gap Analysis soon, but note
that reference data is a huge area where standardization has been
attempted before.I’d recommend you to be active in the GEXMC.
I have not seen a recommendation for custom messages, but would
recommend you to follow the principles of other reference data messages
and workflows.Regards
Rikard
Hello,
Are there any plans to extend FIX protocol to support
reference/permission messages? For example, list of counterparties a
customer may be able to trade, list of accounts, instruments, etc …If there are any plans, which is the best way to contribute onto the
discussion?If there are no plans, does FIX Protocol offer guidelines on how
custom messages may be defined?Thanks and Regards
Ainhoa
[ original email was from Rikard Hedberg - rikard.hedberg@omxgroup.com ]
To attend the GEXMC, please contact one of the leaders. See: http://www.fixprotocol.org/committees/gexmc
We have weekly phone meetings (Thursdays). See you there.
Regards
Rikard
Hello Rikard,
I am very keen in contributing to the discussions in any way I can. Do
you know the process I should follow?Regards
Ainhoa
Ainhoa,
Instruments are supported by the Security Definition, Security List,
etc messages. Any day now GTC approval is expected for extensions
with new messages and numerous fields in the derivatives area (will
be part of
5. SP1). That extension also means reference data for other asset
classes must be considered relevant for FIX. I hope the Global
Exchanges and Markets Committee (GEXMC) will start a Gap Analysis
soon, but note that reference data is a huge area where
standardization has been attempted before.I’d recommend you to be active in the GEXMC.
I have not seen a recommendation for custom messages, but would
recommend you to follow the principles of other reference data
messages and workflows.Regards
Rikard
Hello,
Are there any plans to extend FIX protocol to support
reference/permission messages? For example, list of counterparties
a customer may be able to trade, list of accounts, instruments,
etc …If there are any plans, which is the best way to contribute onto the
discussion?If there are no plans, does FIX Protocol offer guidelines on how
custom messages may be defined?Thanks and Regards
Ainhoa
Ainhoa,
acceptable and unacceptable counterparties have been introduced with FIX 5.0 as additional Party Roles (tag 452, values 56 and 57). Any message with a Parties component block, e.g. New Order Single, thus allows you to specify such a list. However, there are gaps in terms of reference data on the user level and this is an area that still needs to be tackled, e.g. in the Global Exchanges and Markets Committee as Rikard pointed out in his posting.
Regards,
Hanno.
Hello,
Are there any plans to extend FIX protocol to support
reference/permission messages? For example, list of counterparties a
customer may be able to trade, list of accounts, instruments, etc …If there are any plans, which is the best way to contribute onto the
discussion?If there are no plans, does FIX Protocol offer guidelines on how custom
messages may be defined?Thanks and Regards
Ainhoa