Don Mendelson

The standard way to create an array of records in SBE is to define a repeating group. A field in the group could have a composite encoding. The number of...

I'm inclined to agree, and other FIX XML schemas have `elementFormDefault="qualified"`. I don't recall why this one is different--it's been this way since at least version 1.0 RC3.

Questions about CME's message schema should be addressed to their support group. For one, they can tell you which version of the SBE standard it conforms to.

@ujos `semanticAttributes` is an attribute group containing `description` and `semanticType` attributes, so I assume that you want to know the distinction between those two. `description` is free-form text for any...

I understand that you believe that there "description" attribute is defined twice for the same type, causing a conflict. However, I don't see that for "simpleDataType". It has "description" as...

Proposing to use Dublin Core Terms in the same fashion as the Orchestra schema. It can be optional usage. If rules of engagement are expressed in Orchestra or other document...

@OleksandrKvl you are correct that some of the field attributes are not useful for ``. The documentation should be more specific. In the XML schema, a data attribute group could...

The specification says that the `type` attribute of `` ... > Must match a defined type, enum or set or composite name attribute. It seems to me that your second...

As worded, your comment about making a datatype optional only applies to SBE version 1.0. In version 2, presence is only an attribute of fields, not datatypes. Clearly, changing presence...

A decoder generated from an earlier version of a message schema cannot decode the new group anyway. The downside is that it cannot correctly determine the message length by walking...