OVAL and case sensitivity of boolean datatype?

[vanderpol]

Does anyone know if the OVAL Boolean datatype is specifically lowercase 'true' and 'false' or if data that comes back from say an xpath test that returns "True" or "False" should be considered Boolean, or should that always be treated with a string operation of equals?

Here is an example from NIST's macOS content

<plist511_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#macos" comment="system_settings_usb_restricted_mode_recommended_state" id="oval:mscp:ste:46" version="1">
  <value_of datatype="boolean" operation="equals">True</value_of>
</plist511_state>

If the object xpath returns back "True" should this test pass or fail? Or should the application say that "True" is not a boolean "true" or "false" and error?

Is the following true and false literals of 'true' and 'false', or just conceptually, where True is binary true?

           <xsd:enumeration value="boolean">
                <xsd:annotation>
                     <xsd:documentation>The boolean datatype represents standard boolean data, either true or false.  This datatype conforms to the W3C Recommendation for boolean data meaning that the following literals are legal values: {true, false, 1, 0}.  Expected operations within OVAL for boolean values are 'equals' and 'not equal'.</xsd:documentation>
                </xsd:annotation>
           </xsd:enumeration>

I should have brought this up in today's call. @solind and @robertgendler any thoughts?

[solind]

The documentation says values of true, false, 1 and 0 are allowed. In practice, from memory, I think I probably permitted case-insensitive variants of true and false when I wrote it, and flagged other values as errors.

[solind]

The content should use lowercase, though. Set a good example for the community!