FIXatdl1.1 Errata 20101221
Errata for FIXatdlSM Specification version 1.1
December 21, 2010
Purpose: This document contains a list of minor adjustments to the FIXatdl 1.1 Specification document due to typographical errors or ambiguities. The nature and scope of these adjustments is restricted such that no new functionality is introduced, and the goal of these Errata is that no breaking changes are introduced. NOTE: In order to meet this goal, no functional changes have been made to the FIXatdl
FIXatdl1.1 Errata 20101221
Errata for FIXatdl
SM
Specification version 1.1
December 21, 2010
Purpose:
This document contains a list of minor adjustments to the FIXatdl 1.1 Specification document due totypographical errors or ambiguities. The nature and scope of these adjustments is restricted such thatno new functionality is introduced, and the goal of these Errata is that
no breaking changes areintroduced
.
NOTE:
In order to meet this goal, no functional changes have been made to the FIXatdl 1.1 XSDschema files.
This means that where the schema and the Word specification disagree, then theWord specification should be taken as the authoritative definition of the protocol.
The knownvariations between the schema and the Word document are listed at the end of this document.
Outstanding Issues:
Issues with the FIXatdl 1.1 Specification which have not been addressed by the combination of theFIXatdl 1.1 Specification document or this Errata document should be brought forward via the FIXweb site (http://www.fixprotocol.org) discussion pages. It is the responsibility of the AlgorithmicTrading Working Group to see that outstanding issues are addressed. The Algorithmic TradingWorking Group is co-chaired by Rick Labs, CL&B Capital Management (rick@clbcm.com) and GregMalatestinic, Jordan & Jordan (greg.malatestinic@jandj.com).
Changes to the FIXatdl Specification Document
ID/JIRA #Item/Area AffectedDescription
ATDL-146Label_tIt was not previously clear whether a label’s text should beinitialized from the initValue attribute or the label attribute.This has been clarified and a precedence rule given.ATDL-147Control/@initValueClarification on how CheckBoxList_t items should beseparated.ATDL-147StrategyLayoutThe StrategyLayout element if supplied must containexactly one StrategyPanel.ATDL-147Boolean values (throughout)Clarified to be “true” / “false” or “Y / “N” as appropriate.ATDL-147Strategy/@commonIDTagThis attribute was missing from the Word document.ATDL-147Strategy/@totalOrdersTagThis attribute was missing from the Word document.ATDL-147StrategyPanel/@titleThis attribute was missing from the Word document.ATDL-147Strategies/@draftFlagIdentifierTagOriginally incorrectly referred to as @draftIdentifierTag.ATDL-148Edit_tThe meaning of short-circuit evaluation has been clarified. N/AParameter/@xsi:typeDefinition was previously missing the option “Country_t”. N/AStrategyPanel/@collapsedPreviously incorrectly detailed in the Word document as
Page 1
FIXatdl1.1 Errata 20101221
having a default of “true”. (The XSD schema was alreadycorrect). N/AStrategyPanel/@collapsibleRecommendation that this attribute be treated asmandatory. N/AStrategyPanel/@orientationThis is now a mandatory attribute (as there is no way programmatically to determine a sensible default value).ATDL-144Parameter Type-Attribute MatrixChar_t and Country_t were missing from the table.ATDL-147Control Type-Attribute MatrixDoubleSpinner_t was erroneously shown as allowingincrementPolicy.ATDL-147Parameter Element Extension tableFloat_t was missing the precision attribute.ATDL-151StateRule_tThe meaning of XOR has been clarified.ATDL-152Control/@orientationThis is now a mandatory attribute of CheckBoxList_t andRadioButtonList_t controls (as there is no way programmatically to determine a sensible default value).ATDL-155Parameter Element ExtensionAn example provided at the end of the section made use of a deprecated attribute. Another example using validattributes was added. N/AConstraints beyond XML SchemaThree additional constraints have been identified.
Known Variations between the FIXatdl Specification Word Document and the XSD Schema
Item/Area AffectedDescription
StrategyPanel/@orientationThe attribute, StrategyPanel/@orientation, is a required attribute. This isincorrectly defined in the schema file, fixatdl-flow.xsd, as being an optionalattribute. All FIXatdl conforming XML instances must declareStrategyPanel/@orientation.StrategyPanel/@collapsibleThe attribute, StrategyPanel/@collapsible, has a default value of False. Thisis incorrectly defined in the schema file, fixatdl-layout.xsd, as being True. Itis recommended that all FIXatdl conforming XML instances treatStrategy/@collapsible as a required attribute to avoid varying behaviour when rendering the XML in several vendors E/OMS.StrategyLayoutStrategyLayout element must contain one and only one StrategyPanel. Thexsd, fixatdl-layout.xsd, allows a StrategyLayout to have more than morethan one child StrategyPanel element, but this should not be allowed.Control/@incrementPolicyControl/@innerIncrementPolicyControl/@outerIncrementPolicyThe valid values are “Static”, “LotSize” and “Tick”. However in the xsd,fixatdl-layout.xsd, the enumeration, “Static”, is missing. Accordingly, anyFIXatdl conforming XML instance may fail validation if it contains aControl element with incrementPolicy, innerIncrementPolicy or outerIncrementPolicy equal to “Static”.The specification document now advises against the use of “Static” as avalue for this attribute. The same behaviour can be achieved by omitting theattribute altogether.Control/@orientationThe attribute, Control/@orientation, is applicable only when the control is aCheckBoxList_t or RadioButtonList_t and, in these cases, is a requiredattribute. This is incorrectly defined in the schema file, fixatdl-flow.xsd, as being an optional attribute of CheckBoxList_t and RadioButtonList_t. AllFIXatdl conforming XML instances must declare Control/@orientation
Page 2
FIXatdl1.1 Errata 20101221
when Control/@xsi:type is either CheckBoxList_t or RadioButtonList_t.
Page 3