fix-orchestra
fix-orchestra copied to clipboard
Machine readable rules of engagement
The build specifies the main class to run in repository-validator module. It should be updated since the validator was split into a basic one that only checks schema conformance and...
The format of the repository version attribute should be more freeform. The SBE schema has a simple integer for version, but I found that the Orchestra schema would not allow...
Message from Hanno Klein: > The validate produces an error for empty sections although they are present in the XML file. Just using codesets as an example here: > >...
This proposal was accidently left out of the merge to branch v1.1RC1
From document *Orchestra Enhancements for Scenario Identification* The class of a tag-value message is traditionally identified by MsgType(35). However, this encoding does not by itself support scenarios. In fact, scenarios...
Currently, the selection of expression language is global to an Orchestra repository at its root element, and its default is the Score DSL. It affects the interpretation of conditional expressions...
Fields like Issuer(106) are also supported in an encoded version, in this case EncodedIssuer(349). The latter requires a second field EncodedIssuerLen(348) for tag value encoding that defines the length of...
It is currently not possible to have introductory text for the complete section of messages, components, fields, code sets. Annotations are only supported for a specific message, component, field, code...
FIX naming conventions still need to consider tag=value encoding, i.e. a field name must not appear more than once in a single FIX message definition. This has led to different...