Hanno Klein

The first case is linked to #94 which is about encoded fields equivalent to non-encoded fields. Both are about limitations due to encodings.

Added text for naming rules

I use the term "instance" and not "entry" and a shorter expression, i.e. "PartyRole of the fourth instance of Parties". The term "instance of" implies that the name of a...

Would that only apply to the mapped datatype, i.e. not to the "normal" datatype used by tagvalue syntax?

External code sets make this a larger issue. The idea was to bring the external code sets back into Orchestra, avoiding the need to use URLs. FIX Latest needs to...

Agree, unionDataType attribute should be on the code set. The change of FIX Latest will just not be as quickly as we may have hoped for.

@YuvalCohen, do you mean that a field should be able to have values from more than one code set?

> Please consider the following code: > > ``` > > > > > > > > > ``` > > what is the code that I need to add...

Maybe I was focussed too much on code sets as distinguishing factor for field scenarios. I would not use different field scenarios but different code sets and annotate the code...

Let's try the following example. I define two code sets for PartyRole(452) by declaring two data types (FewRolesCodeSet and ManyRolesCodeSet). I also define FewRolesCodeSet and ManyRolesCodeSet as code sets with...