Martin Swanson

This issue can be closed. as changes have been added under commit 19ddc51.

The ISO 20022 Metamodel defines: * `CodeSet` - Complete and enumerated set of `Codes` grouped together to characterise all the values of an attribute. * `IdentifierSet` - Unenumerated set of...

Seems a `specUrl` can only be defined on `appinfo` or a `codeset` currently, and is meant for linking to general purpose documentation rather than an actual codeset? I was thinking...

Visualisation tools like [FIXimate](https://fiximate.fixtrading.org) use section and category for message navigation, so I agree it makes sense to make certain fields required. ### Proposal * Make `name` and `section` required...

Agree this is obsolete and can be removed in RC2.

Why isn't this just part of the configuration for your encoder/decoder?

If we take SBE as an example, null values and associated handling are already defined at the encoding layer. What is the reason we want to duplicate this configuration in...

> Following up on yesterday's call, I checked several different binary protocols (incl. Nasdaq protocols and NYSE Pillar) and all of them are using message types, which are at most...

Generally supportive of adding clearer guidance for the `purpose` attribute, not least because it simplifies document generation. Specific notes: * DISPLAY as a solution to #193 makes sense. * DEFINITION...

I agree with @donmendelson and others that Orchestra specifications should be _fully declarative_, and any necessary pre-processing or transformations to generate correct XML should be handled internally by the publishers....