Imported from previous forum
Hello,
I’m new to the fix community and this is my first time using the FixRepository. All of my understanding comes from looking at the file thus far.
I noticed that in the FixRepository.xml file there are a number if discrepancies concerning Hop and HopGrp that make parsing this group very difficult. I am trying to build the tag set of all repeating groups in all versions of fix using the same parser if possible.
For example:
"NstdPtysSubGrp"
804
545
805
Hop and HopGrp seems to be the only problem with this approach.
Fix.4.3 defines a repeatingGroup in the StandardHeader with /repeatingGroup id=“627” name=""/ yet it has no name and there is no corresponding Component of type ImplicitBlockRepeating.
Fix.4.4: Defines a component named Hop of type ImplicitBlock yet has an element called “repeatingGroup”.
Fix.4.5-Fix.5.0SP1: Defines a component named HopGrp of type ImplicitBlock yet has an element called “repeatingGroup”.
Fix.5.0SP2: This seems to be the only version that is correct where the HopGrp is typed as ImplicitBlockRepeating and has an element called “repeatingGroup” as expected.
My parser looks for "Repeating’ in the component type to identify repeating groups and then looks for the “repeatingGroup” element to identify the field set.
Hop and HopGrp seem to be the only exception to this rule unless I’m skipping things.
Are these errors in the XML or am I missing something? If so what is an algorithm for capturing all field members of repeating groups if looking for BlockRepeating and ImplicitBlockRepeating is not sufficient?
Thanks,