Don Mendelson

The schema change accepted so far allows datatype scenarios to be declared but the schema does not provide enough attributes to distinguish their values spaces. (It does a little better...

Data scenarios may obsolete the `baseType` attribute of datatype.

ISO 11404 refers to the *size* of a sequence and other aggregate types, so it seems that term is more generic than *length*.

Adding some comments to the XML schema for attributes of mappedDatatype: **base** - A datatype from which a subtype may be created by restriction or a derived type is created...

I question the utility of Boolean **builtin** attribute. It seems to imply that it need not be explicitly defined in the target encoding. Even if that is the case, we...

Example using proposed size attribute: ```xml A character array of size 6 for an equity symbol ```

The mappedDatatype element also lacks an attribute for void representation in data structures where presence is optional. This case was encountered in mapping of SBE datatypes that have a configurable...

Reacting to @jimnup's aside... Yes, categorization of message elements by business area/process is a taxonomy, isn't it, a job that semantic notation is suited for. - The levels of categorization...

An alternative to consider is to move the name and version attributes to the metadata section as Dublin Core Terms, e.g. title, identifier.

Without imposing DCT or PROV models, I propose simply changing Version_t XML type to the following. ``` Uniquely identifies a revision. Many formats are impossible, including but not limited to...