Message schema for FIX Simple Binary Encoding Version: 1.0 Draft Standard © Copyright 2014-2016 FIX Protocol Limited License: Creative Commons Attribution-NoDerivatives 4.0 International Public License Root of XML document, holds all message templates and their elements More than one set of types may be provided. Names must be unique across all encoding types. Encoding types may appear in any order. Unique ID of a message schema The version of a message schema. Initial version is 0. Application layer specification version, such as FIX version 'FIX.5.0SP2' Name of the encoding type of the message header, which is the same for all messages in a schema. The name has a default, but an encoding of that name must be present under a 'types' element. A message type, also known as a message template Base type of message and repeating group entry Fixed-length fields Variable-length fields Unique ID of a message template Space reserved for root level of message, not include groups or variable-length data elements. A repeating group contains an array of entries Simple wire encoding consisting of a primitive type or array of primitives Override of default null indicator for the data type in SBE specification, as a string. A wire encoding composed of multiple parts An enumeration of valid values Valid value as a string A reference to any existing encoding type (simple type, enum or set) to reuse as a member of a composite type A multi value choice (encoded as a bitset) A choice within a multi value set. Value is the position within a bitset (zero-based index). A field of a message of a specified dataType Must match the name of an encoding contained by 'types' element Deprecated - only for back compatibility with RC2 Application layer class. Maps a field or encoding to a FIX data type. Schema versioning supports message extension The schema version in which an element was added The version of the schema in which an element was deprecated. It is retained for back compatibility but should no longer be used by updated applications. Offset from start of a composite type or block as a zero-based index. The value must always be populated Value may be set to nullValue for its data type Value does not vary so it need not be serialized on the wire A constant value as valid value of an enum in the form enum-name.valid-value-name