I read https://github.com/FIXTradingCommunity/fix-orchestra/wiki/Concepts-Part2-Workflow-and-Scenarios with great interest, especially the Orchestra definition for ExecutionReport at the bottom of the page. However the latest copy of OrchestraFIXLatest.xml I could find (dated November 15th of 2020) did not have the scenario attribute in ExecutionReport or any other Message element. Is there a version of OrchestraFIXLatest.xml that contains the features described in the GitHub wiki?
The Orchestra XML file for FIXLatest does not have scenarios because that is primarily a feature for users to define the subset of a message, component or field that is supported. FIX itself always supports all fields of a message or component and all values of a field.
That said, FIX may provide scenarios for specific use cases, e.g. Instrument component for asset class XYZ, as recommended practice. But such XML files are separate from the main file that does not limit the scope in any way.
There is a GitHub project orchestrations has an examples folder intended to collect specific (FIX) interfaces expressed with the Orchestra standard. We would like to receive such files for publicly available interface specifications so that others can see how the features of Orchestra are used.