Constants on fields cannot provide element body about fix-simple-binary-encoding HOT 7 CLOSED

Most of the examples of constants in the specification are encoding types rather than fields, but in RC3, presenceAttributes belongs to both encodedDataType as element <type> and fieldType as element <field>.

When the constant is a value of an enumeration, attribute valueRef can be used to refer to an enum value by name in the form <enum-name>.<valid-value-name>. Using your example, "MDEntryType.TRADE". See section "Constant field of an enumeration value".

Not sure if I answer your question.

from fix-simple-binary-encoding.

Thanks @donmendelson that makes sense. Is this a new RC3 feature?

from fix-simple-binary-encoding.

Attribute valueRef was mentioned in RC2, but presence was only allowed in type encoding in that version. Allowing it in <field> with cross-reference to an enum constant should make it more useful.

from fix-simple-binary-encoding.

Thanks. Is there a complete list of changes from RC2 to RC3 we can work from?

from fix-simple-binary-encoding.

Yes, see Release Notes

from fix-simple-binary-encoding.

So where are the details like the changes to vlaueRef?

from fix-simple-binary-encoding.

Right, the release notes are highlights. Actually, the XSD was considerably refactored for attribute organization, even though elements are the same.

The attributes presence and valueRef were moved to new presenceAttributes group and is now referenced by both encoding and field types, as mentioned above.

Other significant changes:

• Message and group elements now use commonblockType as a recursive collection of fields and nested groups. This allows variable length <data> elements in repeating groups, as mentioned in release notes.
• Composite type now can contain an arbitrary collection of simple types, enums and sets, not just simple types. (Your suggestion, I believe.)

from fix-simple-binary-encoding.