Text (field 58) should be indented in Email and News?

, ,
1

Imported from previous forum

2

[ original email was from Michael Cavén - michael.caven@sungard.com ]
Shouldn’t the Text field (58) be indented in News and Email messages? This is not the case neither in the Fix Repository files and in FIXimate 4.0.

In FIX 4.1 and later it is however corrected.

3

[ original email was from Michael Cavén - michael.caven@sungard.com ]
I am looking forward to the next release of the Repository! However I have spotted some more mistakes (maybe this is not the right forum for all of them, but anyway…)

  • “New Order Single” is called “Order Single” in FIX 4.0, 4.1 and 4.2.

  • “New Order List” is called “Order List” in FIX 4.0, 4.1 and 4.2.

  • “Indication of Interest” is called “IOI” in FIX 4.3 and 4.4.

  • In FIX 4.3 the tag 588 (LegFutSettDate) has Type “LocalMMktDate” which is wrong. It should be “LocalMktDate”.

  • In FIX 4.3 the tag 536 (AffectedSecondaryOrderID) has Type “Stirng” which is wrong. It should be “String”.

/Michael

Well caught, the parser we used to capture the repository content used
indentation in the FIX message table in the word doc to determine
whether a field was a repeating group. As the Word document does not
show this for those messages it did not pick it up. We’ll correct this
in the next release of the Repository. Since FIXimate is generated from
the repository it is also incorrect.

Thanks for highlighting this.

Kevin Houstoun

Shouldn’t the Text field (58) be indented in News and Email messages?
This is not the case neither in the Fix Repository files and in
FIXimate 4.0.

In FIX 4.1 and later it is however corrected.

4

So any news about when the Repository is going to be updated with these suggested changes?

Thanks we’ll make sure you capture them. The best place to report these
things is the Repository Working Group
http://www.fixprotocol.org/working_groups/repwg . If you use the
Repository we’d also like your feedback on what you use it for and how
you’d like to see it developed. We know people use it as a data
dictionary for FIX engines; others for the FIX – FIXML translation
piece. FPL use it to generate FIXimate, the XML Schema and various other
parts of the documentation.

Thanks Kevin

I am looking forward to the next release of the Repository! However I
have spotted some more mistakes (maybe this is not the right forum for
all of them, but anyway…)

  • “New Order Single” is called “Order Single” in FIX 4.0, 4.1 and 4.2.

  • “New Order List” is called “Order List” in FIX 4.0, 4.1 and 4.2.

  • “Indication of Interest” is called “IOI” in FIX 4.3 and 4.4.

  • In FIX 4.3 the tag 588 (LegFutSettDate) has Type “LocalMMktDate”
    which is wrong. It should be “LocalMktDate”.

  • In FIX 4.3 the tag 536 (AffectedSecondaryOrderID) has Type “Stirng”
    which is wrong. It should be “String”.

/Michael

Well caught, the parser we used to capture the repository content
used indentation in the FIX message table in the word doc to
determine whether a field was a repeating group. As the Word
document does not show this for those messages it did not pick it
up. We’ll correct this in the next release of the Repository. Since
FIXimate is generated from the repository it is also incorrect.

Thanks for highlighting this.

Kevin Houstoun

Shouldn’t the Text field (58) be indented in News and Email
messages? This is not the case neither in the Fix Repository files
and in FIXimate 4.0.

In FIX 4.1 and later it is however corrected.