fixml-ordermasshandling-base-5-0-SP2.xsd is not valid

, ,
1

Imported from previous forum

2

I’m picking up the FIXml for the first time and all looks well with the exceptin of fixml-ordermasshandling-base-5-0-SP2.xsd which is not getting through XMLspy’s validation checks :

File H:\FIXml\5.0sp2\fixml-ordermasshandling-base-5-0-SP2.xsd is not valid.
‘AffectedOrdGrp_Block_t’ must refer to an existing simple or complex type.
Error location: xs:schema / xs:group / xs:sequence / xs:element / @type
Details
src-resolve.4.2: Cannot resolve declaration or definition ‘AffectedOrdGrp_Block_t’.

File H:\FIXml\5.0sp2\fixml-ordermasshandling-impl-5-0-SP2.xsd is not valid.
File H:\FIXml\5.0sp2\fixml-ordermasshandling-base-5-0-SP2.xsd is not valid.
‘AffectedOrdGrp_Block_t’ must refer to an existing simple or complex type.
Error location: xs:schema / xs:group / xs:sequence / xs:element / @type
Details
src-resolve.4.2: Cannot resolve declaration or definition ‘AffectedOrdGrp_Block_t’.

Have not investigated as I’m primarily concerned with back office integration and the tradecapture-base and tradecapture-impl part of the scheme but thought the maintenance folk may be interested.

3

Marcus,
Thanks for reporting this. We’ve logged it and will be looking into it shortly.

I’m picking up the FIXml for the first time and all looks well with the
exceptin of fixml-ordermasshandling-base-5-0-SP2.xsd which is not
getting through XMLspy’s validation checks :

File H:\FIXml\5.0sp2\fixml-ordermasshandling-base-5-0-SP2.xsd is not
valid. ‘AffectedOrdGrp_Block_t’ must refer to an existing simple or
complex type. Error location: xs:schema / xs:group / xs:sequence /
xs:element / @type Details src-resolve.4.2: Cannot resolve declaration
or definition ‘AffectedOrdGrp_Block_t’.

File H:\FIXml\5.0sp2\fixml-ordermasshandling-impl-5-0-SP2.xsd is not
valid. File H:\FIXml\5.0sp2\fixml-ordermasshandling-base-5-0-SP2.xsd is
not valid. ‘AffectedOrdGrp_Block_t’ must refer to an existing simple or
complex type. Error location: xs:schema / xs:group / xs:sequence /
xs:element / @type Details src-resolve.4.2: Cannot resolve declaration
or definition ‘AffectedOrdGrp_Block_t’.

Have not investigated as I’m primarily concerned with back office
integration and the tradecapture-base and tradecapture-impl part of the
scheme but thought the maintenance folk may be interested.

4

[ original email was from Gregor Buehler - gregor.buehler@arcor.de ]
I stumbled upon the same issue. I did a temporary fix, which allows validation of the complete SP2. However I do not guarantee that it does what it should in terms of the original intention other than enabling validation… :slight_smile:

Three parts in two files. Insert the pieces between BEGIN and END in the indicated context:

  1. in ‘fixml-ordermasshandling-base-5-0-SP2.xsd’ after

    <xs:include schemaLocation=“fixml-components-impl-5-0-SP2.xsd”/>

    <xs:include schemaLocation=“fixml-order-base-5-0-SP2.xsd”/>

  2. in ‘fixml-ordermasshandling-base-5-0-SP2.xsd’ after

    <xs:attributeGroup ref=“NotAffectedOrdersGrpAttributes”/>
    </xs:complexType>

    <xs:group name=“AffectedOrdersGrpElements”>
    xs:sequence/
    </xs:group>
    <xs:attributeGroup name=“AffectedOrdersGrpAttributes”>
    <xs:attribute name=“AffOrigClOrdID” type=“AffOrigClOrdID_t” use=“optional”/>
    <xs:attribute name=“AffectedOrderID” type=“AffectedOrderID_t” use=“optional”/>
    </xs:attributeGroup>

  1. in ‘fixml-fields-base-5-0-SP2.xsd’ after definition of ‘NotAffOrigClOrdID_t’

    <xs:simpleType name=“AffOrigClOrdID_t”>
    xs:annotation
    xs:documentationClOrdID(11) of the previous order (NOT the initial order of the day) as assigned by the institution, used to identify the previous order in cancel and cancel/replace requests.</xs:documentation>
    xs:appinfo
    <fm:Xref Protocol=“FIX” name=“AffOrigClOrdID” ComponentType=“Field” Tag=“1372???”
    Type=“String”
    AbbrName=“AffOrigClOrdID”/>
    </xs:appinfo>
    </xs:annotation>
    <xs:restriction base=“xs:string”/>
    </xs:simpleType>

Hope this helps. I’d rather be able to upload the patched files, but should work.

I also included some ‘RFAC’ hints for those engineering this framework. Given the sheer complexity of the matter, the RFACs might point to the causes of the validation errors.

I’m picking up the FIXml for the first time and all looks well with the
exceptin of fixml-ordermasshandling-base-5-0-SP2.xsd which is not
getting through XMLspy’s validation checks :

File H:\FIXml\5.0sp2\fixml-ordermasshandling-base-5-0-SP2.xsd is not
valid. ‘AffectedOrdGrp_Block_t’ must refer to an existing simple or
complex type. Error location: xs:schema / xs:group / xs:sequence /
xs:element / @type Details src-resolve.4.2: Cannot resolve declaration
or definition ‘AffectedOrdGrp_Block_t’.

File H:\FIXml\5.0sp2\fixml-ordermasshandling-impl-5-0-SP2.xsd is not
valid. File H:\FIXml\5.0sp2\fixml-ordermasshandling-base-5-0-SP2.xsd is
not valid. ‘AffectedOrdGrp_Block_t’ must refer to an existing simple or
complex type. Error location: xs:schema / xs:group / xs:sequence /
xs:element / @type Details src-resolve.4.2: Cannot resolve declaration
or definition ‘AffectedOrdGrp_Block_t’.

Have not investigated as I’m primarily concerned with back office
integration and the tradecapture-base and tradecapture-impl part of the
scheme but thought the maintenance folk may be interested.