Don Mendelson
Don Mendelson
It's a business decision whether to edit code sets in FIX Latest and subject them to GTC review versus editing them externally under a different process. Either way, I'm suggesting...
Consider whether to leave unionDataType on `` as well as adding to `` for back compatibility.
Orchestra working group made a decision on June 15, 2022 to retain the unionDataType attribute on fields for back compatibility while adding it to code sets.
Use cases would be helpful for defining requirements.
@YuvalCohen, this forum is fine for public questions. Other resources include FIX Forum and iMeetCentral for discussion within the Orchestra working group. Let me answer Q1 first. Different use cases...
Regarding Q2 above: I'm not sure I understand the requirement. Are you saying that you wouldn't know until runtime which code set applies, based on other values in a message?
Currently, there is no syntax in the schema to indicate a union of codesets. (I think restriction is the more common use case.) The closest thing is a union datatype,...
@YuvalCohen, add the scenario name of the field. `` BTW in the current RC5 schema, the fieldRef only has id and scenario attributes, name is redundant.
@YuvalCohen, yes a code set scenario for each use case. You may propose a syntax for code set union if you think it has general applicability. Theoretically, code set could...
Yes, any non-key fields can be different in a field scenario, including rules.