[This message was posted by Gregor Buehler of Systems&Software Engineering
<[email protected]> to the "5.0 SP2 Feedback" discussion forum at
http://fixprotocol.org/discuss/121. You can reply to it on-line at
http://fixprotocol.org/discuss/read/50849955 - PLEASE DO NOT REPLY BY MAIL.]
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... :-)
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"/>
<!-- BEGIN OF: temporary/in-official fix for missing
'AffectedOrdersGrp_Block_t' -->
<!-- RFAC: other than with 'NotAffectedOrdersGrp_Block_t' the following
definition is to be found in file 'fixml-order-base-5-0-SP2.xsd' -->
<xs:include schemaLocation="fixml-order-base-5-0-SP2.xsd"/>
<!-- END OF: temporary/in-official fix for missing
'AffectedOrdersGrp_Block_t' -->
2) in 'fixml-ordermasshandling-base-5-0-SP2.xsd' after
<xs:attributeGroup ref="NotAffectedOrdersGrpAttributes"/>
</xs:complexType>
<!-- BEGIN OF: temporary/in-official fix for missing
'AffectedOrdersGrp_Block_t' -->
<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>
<!-- RFAC: normally the label 'AffectedOrdGrp_Block_t' should be
'AffectedOrdersGrp_Block_t' like in 'NotAffectedOrdersGrp_Block_t' -->
<!-- RFAC: other than with 'NotAffectedOrdersGrp_Block_t' the following
definition is to be found in file 'fixml-order-base-5-0-SP2.xsd'.
So we comment it out here:
<xs:complexType name="AffectedOrdGrp_Block_t">
<xs:annotation>
<xs:appinfo>
RFAC: normally the label 'AffectOrd' should be 'AffectedOrdersGrp'
like in 'NotAffectedOrdersGrp'
<fm:Xref Protocol="FIX" name="AffectOrd"
ComponentType="ImplicitBlockRepeating"
Category="OrderMassHandling"/>
</xs:appinfo>
</xs:annotation>
<xs:sequence>
<xs:group ref="AffectedOrdersGrpElements"/>
</xs:sequence>
<xs:attributeGroup ref="AffectedOrdersGrpAttributes"/>
</xs:complexType>
-->
<!-- END OF: temporary/in-official fix for missing
'AffectedOrdersGrp_Block_t' -->
3) in 'fixml-fields-base-5-0-SP2.xsd' after definition of 'NotAffOrigClOrdID_t'
<!-- BEGIN OF: temporary/inofficial fix for missing
'AffectedOrdersGrp_Block_t' -->
<xs:simpleType name="AffOrigClOrdID_t">
<xs:annotation>
<xs:documentation>ClOrdID(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>
<!-- END OF: temporary/inofficial fix for missing
'AffectedOrdersGrp_Block_t' -->
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.
[You can unsubscribe from this discussion group by sending a message to
mailto:[email protected]]
--
You received this message because you are subscribed to the Google Groups
"Financial Information eXchange" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fix-protocol?hl=en.
