possible fixml4.3v1.0.dtd errata

, ,
1

Imported from previous forum

2

Aside from minor typos, I believe I have detected a bug in the fixml4.3v1.0 dtd.

The element Municipal may have a possible value of
’WAR’ (FIXTag=‘167’), which I believe is incorrect since element Warrant has a fixed attribute Value=‘WAR’ (FIXTag=‘167’).

We should remove ‘WAR’ from the set of possible values for element Municipal.

Is that correct?

Sincerely,
John Coppola
john_coppola_r_s@yahoo.com

3

[ original email was from John Goeller - john.goeller@csfb.com ]
Agreed. This was on our list. The DTD gets its enumerations from the spec so that’s why it is in two places. We’ll address this in the next release of the errata.

Addtionally, please let us know of the minor typos you’ve found.

> Aside from minor typos, I believe I have detected a bug in the fixml4.3v1.0 dtd.
>
> The element Municipal may have a possible value of
> ‘WAR’ (FIXTag=‘167’), which I believe is incorrect since element Warrant has a fixed attribute Value=‘WAR’ (FIXTag=‘167’).
>
> We should remove ‘WAR’ from the set of possible values for element Municipal.
>
> Is that correct?
>
> Sincerely,
> John Coppola
> john_coppola_r_s@yahoo.com
>
>

4

> Addtionally, please let us know of the minor typos you’ve found.

The two minor typos are:

  1. attlist Product DataType='int ’ (trailing space intended) rather than ‘int’.
  2. same goes for Underlying Product.

I have discovered additional errors.
For MassCancelResponse the number of possible
values does not match the number of possible
SDValues. I am guessing that the zero entry in values should be removed.

Likewise for TradeCondition where the number of Value entries out number the number of SDValue entries by three.

----------previous message-----------
> Agreed. This was on our list. The DTD gets its enumerations from the spec so that’s why it is in two places. We’ll address this in the next release of the errata.
>
> Addtionally, please let us know of the minor typos you’ve found.
>
> > Aside from minor typos, I believe I have detected a bug in the fixml4.3v1.0 dtd.
> >
> > The element Municipal may have a possible value of
> > ‘WAR’ (FIXTag=‘167’), which I believe is incorrect since element Warrant has a fixed attribute Value=‘WAR’ (FIXTag=‘167’).
> >
> > We should remove ‘WAR’ from the set of possible values for element Municipal.
> >
> > Is that correct?
> >
> > Sincerely,
> > John Coppola
> > john_coppola_r_s@yahoo.com
> >
> >
>

5

> Addtionally, please let us know of the minor typos you’ve found.
>
>
> I have discovered additional errors.
> For MassCancelResponse the number of possible
> values does not match the number of possible
> SDValues. I am guessing that the zero entry in > values should be removed.
> Likewise for TradeCondition.

There hasn’t been a response to this message yet?

6

[ original email was from John Goeller - john.goeller@csfb.com ]
Typos noted. Thanks

> > Addtionally, please let us know of the minor typos you’ve found.
> >
> >
> > I have discovered additional errors.
> > For MassCancelResponse the number of possible
> > values does not match the number of possible
> > SDValues. I am guessing that the zero entry in > values should be removed.
> > Likewise for TradeCondition.
>
> There hasn’t been a response to this message yet?
>
>

7

your response:
> Typos noted. Thanks

More importantly, what are the correct resolutions to the following errors:

a) For MassCancelResponse the number of possible
values does not match the number of possible
SDValues. I am guessing that the zero entry
in values should be removed.

b) For TradeCondition the number of SDValues do
not match at all.

Sincerely,
John Coppola
john_coppola_r_s@yahoo.com

8

[ original email was from John Goeller - john.goeller@csfb.com ]
We’ll add CancelRequestRejected to SDValue of MassCancelResponse and ImbalanceMoreBuyers, ImbalanceMoreSellers & OpeningPrice to SDValue of TradeCondition in the errata release of the DTD

>
> your response:
> > Typos noted. Thanks
>
> More importantly, what are the correct resolutions to the following errors:
>
> a) For MassCancelResponse the number of possible
> values does not match the number of possible
> SDValues. I am guessing that the zero entry
> in values should be removed.
>
> b) For TradeCondition the number of SDValues do
> not match at all.
>
> Sincerely,
> John Coppola
> john_coppola_r_s@yahoo.com
>
>