Don Mendelson

@patricklucas this change was indeed to support non-FIX protocols or firms that wish to follow their own version system. As I mentioned, the v1.0 schema did not even support the...

I'm not sure of the business use case, so my examples may not be realistic, but I'll try to show the format. 1. You could encode this as presence is...

The overall size of a repeating group may be limited with group attributes; see [Repeating group](https://github.com/FIXTradingCommunity/fix-orchestra-spec/blob/master/v1-0-STANDARD/orchestra_spec.md#repeating-group) > Limits on the size of a repeating group may optionally be specified with...

I propose to add these examples to v1.1 documentation.

A message definition currently contains a `` child element to define its layout, and optionally a `` child element to give workflow. Each response can have a `` element that...

RepositoryValidator is supposed to call either BasicRepositoryValidator or FixRepositoryValidator depending on a parameter but it doesn't correctly get that parameter from the command line. The style parameter is implemented in...

The Orchestra schema already has attribute "lengthId" to tie a Length field (e.g. 348) to a data field (349). (There was no machine readable attribute for that in Repository.) I...

This still needs a schema change pull request to be included in v1.1 as of June 14 2022.

Orchestra working group made a decision on June 15, 2022 to keep the proposed baseFieldId attribute name but widen the definition. As originally proposed, it will relate encoded fields to...

Question: could this type of cross-reference apply to XML elements other than fields, i.e. component or group references?