NewOrdSingle in the FIXML4.4 Schema

, ,
1

Imported from previous forum

2

I may be totally wrong, but I could not find the definition of NewOrdSingle in the FIXML4.4 Schema.
This elements exist in the 4.4 DTD and can be found in the fix4.4livedtd: http://www.fixprotocol.org/specifications/fix4.4livedtd/fixml.4.4.dtd.html#ElementDef163

Can someone please point me to the schema in which this elements is defined? or is there a difference between the DTD and the Schema?

Thanks in advanced, David

3

Kevin,
Thanks for the quick reply.

If I may, this answer raises more questions… :slight_smile:

  1. If the shcema is different from the DTD, what should I use?

  2. There are additional inconsistencies between the FIXML DTD and the FIX Documention. For example, the ExecInst enumaration is defined to be able to take only one value although the document states “this field can contain multiple instructions separated by space” (I think that ExecInst in the schema is also defined as enumaration which allow one selection only). What document should I refer to when trying to implement the FIXML?

  3. With all that in mind, maybe I should leave FIXML 4.4 and try to implemet and older and more stable FIXML schema? But choosing this options means that I will waste time and money on old protocol which will soon be replaced?

David.

David

The NewOrderSingle is in the FIXML Schema as the Order message.
Specifically it is now mostly defined in the file fixml-order-base-4-
4.xsd within the schema posted to http://www.fixprotocol.org/documents/352/fixml-schema-4-4-
20040109.zip

In writing the schema a couple of things where changed

Lots of long names where given shorter names to save space,
NewOrderSingle became Order for example. This was applied to both some
message names and a lot of field names. Additionally a lot of things
where made attibutes of elements. Additionally the schema has more
structure which was introduced through the use of implicit components.
More details can be found on

http://www.fixprotocol.org/specifications/TechDoc-FIXML

Cheers Kevin Houstoun Consultant to HSBC

4

[ original email was from Jim Northey - jnorthey@jandj.com ]
David,

I think I can speak for the GTC in saying that if you are implementing FIXML you should use the FIXML 4.4 Schema version that has been optimized to resolve major bandwidth consumption issues.

The FIXML DTD was an intermediate release and should be considered obsolete. Yes - we should produce a DTD that corresponds to the Schema version for those requiring DTD support at some point.

I have found in actual implementation experience that the FIXML Schema 4.4 versions that is built upon abbreviations and attributes is much easier to read and also minimizes message size considerably.

In the post trade space we have several clearing houses standardizing on the FIXML 4.4 Schema version. I know of managed funds that are using the FIXML 4.4 Schema version internally within their systems to implement order routing applications - then translating back to the appropriate FIX tag=value version to communicate with counterparties.

Hope this helps.

Kevin, Thanks for the quick reply.

If I may, this answer raises more questions… :slight_smile:

  1. If the shcema is different from the DTD, what should I use?

  2. There are additional inconsistencies between the FIXML DTD and the
    FIX Documention. For example, the ExecInst enumaration is defined to
    be able to take only one value although the document states “this
    field can contain multiple instructions separated by space” (I think
    that ExecInst in the schema is also defined as enumaration which
    allow one selection only). What document should I refer to when
    trying to implement the FIXML?

  3. With all that in mind, maybe I should leave FIXML 4.4 and try to
    implemet and older and more stable FIXML schema? But choosing this
    options means that I will waste time and money on old protocol which
    will soon be replaced?

David.

David

The NewOrderSingle is in the FIXML Schema as the Order message.
Specifically it is now mostly defined in the file fixml-order-base-4-
4.xsd within the schema posted to http://www.fixprotocol.org/documents/352/fixml-schema-4-4-
20040109.zip

In writing the schema a couple of things where changed

Lots of long names where given shorter names to save space,
NewOrderSingle became Order for example. This was applied to both some
message names and a lot of field names. Additionally a lot of things
where made attibutes of elements. Additionally the schema has more
structure which was introduced through the use of implicit components.
More details can be found on

http://www.fixprotocol.org/specifications/TechDoc-FIXML

Cheers Kevin Houstoun Consultant to HSBC