Hanno Klein

FIX tag=value is using the `baseType` attribute for its encoding. It would be a significant change to remove that in favor of datatype scenarios. Also, it would add scenarios to...

> Section=Global Category=Common would be for components that are global across all sections and category. Component should be global as soon as it is used in more than one section,...

There are currently more than 500 components that are considered global. A single category "Common" is not enough to structure them, e.g. for documentation purposes. One approach would be to...

@patricklucas first of all thank you for getting involved with Orchestra and raising issues. I suspect that your comment about Orchestra being FIX only in some places relates to specification...

I believe this is a legacy feature from the Basic repository that had separate files for abbreviations, datatypes, enums, fields, components, messages, message contents, categories, sections. All of these files...

Background: LegQty(687) was deprecated with FIX 5.0 SP1. It was hence also deprecated from all components that used it. TrdInstrmtLegGrp was missed and corrected with EP131. The validator ensures referential...

Issuer and EncodedIssuer are not mutually exclusive. Both representations can be provided and the field description of EncodedIssuer actually proposes it, i.e. "If used, the ASCII (English) representation should also...

Propose to add a new attribute, e.g. "baseFieldId" as reference to the non-encoded version of a field. The EncodedIssuer definition would then look like this: ``` Encoded (non-ASCII characters) representation...

Agree with the proposal for the next version of Orchestra. [SBE V1.0](https://www.fixtrading.org/standards/sbe-online/) supports the import of encodings, see Message Schema - Data encodings - Encoding name - Importing encodings (Chapter...

Added the following to v1.1 RC1 section 3.1.4 Support for XInclude: For example, `` element can be replaced with the path to the XML file, e.g. ``. The datatypes then...