v6.1

• Updated details on the usage of the <termSuffix> of the <list> field: the read operation of the termination suffix needs to fail on invalid value, i.e. failOnInvalid property needs to be used.
• Added an example of referencing an inner field of the <optional> in another's <optional> field condition.
• Allow check the size of the sequence fields (<string>, <data>, <list>) in the <optional> field condition by using # character after the sibling reference one $.
• Allow check whether preceding <optional> field exists in another <optional> field condition by using ? character after the sibling reference one $.

v6.0

• Allow referencing <interface> fields in the <optional> field cond-itions.
• Added construct property for <message>, can be used to specify extra construction requirements.
• Added readCond and constructAsReadCond properties for <message>, can be used to specify extra read operation conditions.
• Added validCond and constructAsValidCond properties for <message>, can be used to specify extra validity conditions.
• Added failOnInvalid property for <message>, can be used to fail read operation if the message contents are invalid.
• Sorted properties listings in the appendices by name.

v5.0

• Added availableLengthLimit property to <set> field.
• Added support for semanticType="length" for non-<int> fields.
• Added valueOverride property for fields.
• Support for <replace>-ing member fields after reuse.
• Added copyCodeFrom property for fields.
• Added reuseCode property for fields.
• Added semanticLayerType property for the <custom> layer.
• Deprecated idReplacement property of the <custom> layer.
• Added checksumFrom and checksumUntil properties for the <custom> layer.
• Added termSuffix (termination suffix) support for <list> fields.
• Added missingOnReadFail and missingOnInvalid properties for the <optional> field.
• Support for processing of the multiple <schema> definitions with different names and inter-schema references.

v4.0

• Added "xor" checksum algorithm
• New validateMinLength property of the <message>
• New defaultValidValue property of the <int> field.
• New availableLengthLimit property of the <int> and <enum> fields.
• Allow copyFieldsFrom property of the <message> and <interface> to specify reference to a <bundle> field.
• New code overriding properties (readOverride, writeOverride, refreshOverride, lengthOverride, validOverride, nameOverride) for any field and message definition.
• Improvements to the existing documentation (See #2 and #4).

v3.1.3

• Using Asciidoctor instead of AsciiDoc to generate specification.
• Multiple fixes to XML examples.

v3.1.2

• Updating all the links to point to projects in commschamp organization instead of arobenko user.

v3.1.1

• Fixing remnants of markdown links

v3.1

• Using asciidoc to write specification instead markdown.
• Added forceGen property to force generation of the field's class even if it's not referenced.
• New units to describe memory size (bytes, kilobytes, megabytes, ...).

v3.0

• Support for fields' alias names.

v2.1

• Disallow multiple specials for the same numeric value in <int> and <float> fields, controlled by nonUniqueSpecialsAllowed property.
• Allow control of displaying special values in the testing and analysis tools using displaySpecials property.
• Allow usage of displayName property for special values of <int> and <float> fields.