PUBLIC COMMENT PERIOD – User Defined Field Proposal

, ,
1

Imported from previous forum

2

The Global Technical Committee has reviewed and preliminarily approved the User Defined Field proposal. The document now enters a public comment period in which public review and feedback is encouraged. Once the Public Comment period closes, the Global Technical Governance Board will meet to review public comments before final approval.

Please post feedback, comments, and questions as replies to this discussion thread.

A link to the proposal can be found at:

http://www.fixprotocol.org/documents/4894/FIX_Protocol_Proposal_-_UDF_Range_Rev_0.3.doc

The public comment period ends on December 24, 2009.

3

[ original email was from Joseph Horowitz - jhorowitz@aegisoft.com ]
May I suggest adding an Intra-application range for private tags, e.g. 18,000-19,999

Thanks!
-Joey

4

What is the distinction to the rest of the 10-20K range in your view? The entire range 10,000 - 19,999 is private and not subject to bilateral agreement between firms.

Regards,
Hanno.

May I suggest adding an Intra-application range for private tags, e.g.
18,000-19,999

Thanks! -Joey

5

[ original email was from Joseph Horowitz - jhorowitz@aegisoft.com ]
As a vendor we use tags internally within our application. Where our products are installed we would not want a conflict with other in-house or other vendor applications. Having a reserved range for exclusive use only within any single application (e.g. a set of components from a single vendor) is a good way to guarantee that.

What is the distinction to the rest of the 10-20K range in your view?
The entire range 10,000 - 19,999 is private and not subject to bilateral
agreement between firms.

Regards, Hanno.

May I suggest adding an Intra-application range for private tags, e.g.
18,000-19,999

Thanks! -Joey

6

Thanks, the aspect of issues between multiple intra-firm applications is interesting. If I understand you correctly, then such a sub-range with the 10-20K range would be intra-firm and intra-application whereas the rest if intra-firm but inter-application. I am assuming that you have run into conflicts in the past with other intra-firm applications.

As a vendor we use tags internally within our application. Where our
products are installed we would not want a conflict with other in-house
or other vendor applications. Having a reserved range for exclusive use
only within any single application (e.g. a set of components from a
single vendor) is a good way to guarantee that.

What is the distinction to the rest of the 10-20K range in your view?
The entire range 10,000 - 19,999 is private and not subject to
bilateral agreement between firms.

Regards, Hanno.

May I suggest adding an Intra-application range for private tags,
e.g. 18,000-19,999

Thanks! -Joey

7

[ original email was from Joseph Horowitz - jhorowitz@aegisoft.com ]
Exactly; the sub-range would allow us and other vendors to completely avoid conflicts when deployed at a common client.

Thanks!
-Joey

Thanks, the aspect of issues between multiple intra-firm applications is
interesting. If I understand you correctly, then such a sub-range with
the 10-20K range would be intra-firm and intra-application whereas the
rest if intra-firm but inter-application. I am assuming that you have
run into conflicts in the past with other intra-firm applications.

As a vendor we use tags internally within our application. Where our
products are installed we would not want a conflict with other in-
house or other vendor applications. Having a reserved range for
exclusive use only within any single application (e.g. a set of
components from a single vendor) is a good way to guarantee that.

What is the distinction to the rest of the 10-20K range in your
view? The entire range 10,000 - 19,999 is private and not subject to
bilateral agreement between firms.

Regards, Hanno.

May I suggest adding an Intra-application range for private tags,
e.g. 18,000-19,999

Thanks! -Joey