Discussion Forums

5.0 Feedback   < Previous   Next >

A few more encoding artifacts for the FIX 5.0 Components document
David Rosenborg / Pantor Engineering AB
21 Aug 2007 7:27AM ET

I think the length fields for data fields should be added to the list, like EncodedTextLen for example.

Also MsgType is an artifact of the encoding, in the same way that ApplVerID is. In FIXML you'd presumably use the element name and namespace to unambiguously identify a message type (I'm not into the specifics of FIXML so this might look a bit off center, but I think you'll understand my intent anyway):

http://www.fixprotocol.org/ns/fix/FIX.5.0"> ...

and in FAST you'd use the name and namespace of the application type reference for the same purpose:

In none of these examples, the MsgType and ApplVerID need to be communicated as an ordinary field. The exact type of the message follows from built-in constructs of the encoding.

/David

A few more encoding artifacts for the FIX 5.0 Components document
David Rosenborg / Pantor Engineering AB   21 Aug 2007 7:27AM ET

Re: A few more encoding artifacts for the FIX 5.0 Components document
Steven Grossman / NYSE TransactTools   22 Aug 2007 10:59AM ET