Don Mendelson

[repository schema] Version attribute should not be so restrictive

5

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...

[repository schema] allow empty collection elements

1

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

[repositorySchema] Correlating an incoming tag-value message to its scenario.

1

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...

[repository schema] Support annotations as introductions to sections

5

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...

[repository schema] unionDataType should be an attribute of a code set, not field

6

The attribute unionDataType is only used on fields that have code sets. It is used to constrain the range of user-defined values that extend the standard code set. Example ```...

[repositorySchema] mappedDatatype lacks size attribute

5

The mappedDatatype element specifies how a FIX datatype maps to a message encoding. Most of the elements originated in the Unified Repository schema that were originally used to map FIX...

[repositorySchema] datatypes lack scenarios

4

Messages, components, groups, fields, and codesets can have scenarios in Orchestra v1.0, but datatypes do not. This resulted in an unanticipated flaw in the schema that begs resolution in v1.1....