Inconsistent capitalization of keywords True and False

kleihan commented 3 years ago

Keywords true and false are sometimes capitalized, seems inconsistent. They are also not always set in quotation marks.

Chapter 3.3: ... which means it evaluates to "true" when one and only one of its operands is true. If none or more than one of its operands is true then XOR is false.
Chapter 3.8.8: <Edit field="c_LegParamA" operator="EQ" value="True"/>
Definition of Parameter/@trueWireValue: Defines the value with which to populate the FIX message when the boolean parameter is True.
...

Suggest to define single syntax and hamronize.

donmendelson commented 3 years ago

If the attribute is defined as boolean in the XML schema, the legal values are lower case "true", "false", 1 (which indicates true), and 0 (which indicates false).

kleihan commented 3 years ago

FIXatdl also defines two boolean types (Chapter 6), lowercase from XML Schema and uppercase from FIXML. Why are both needed by FIXatdl?

FIXTradingCommunity / fixatdl-specification

Inconsistent capitalization of keywords True and False #25