5.2.1.a built-in primitive types which allow empty content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non-empty-content non empty content non empty content 5.2.1.a built-in primitive types which allow empty content When the form first displays you should not see any valid or invalid messages. If an implementation fires validity events on form initialization (incorrectly) then you may see XFORMS-INVALID output for all types (except string) below. This is not being tested but is an error. When you activate the Run Test trigger below you must see an 'xforms-valid' output for all the data types. If the data type does not accept empty content you will see an 'XFORMS-INVALID' output. An 'XFORMS-INVALID' output is a failure for this test case. Run Test Result: dateTime XFORMS-INVALID (dateTime) xforms-valid (dateTime) time XFORMS-INVALID (time) xforms-valid (time) date XFORMS-INVALID (date) xforms-valid (date) gYearMonth XFORMS-INVALID (gYearMonth) xforms-valid (gYearMonth) gYear XFORMS-INVALID (gYear) xforms-valid (gYear) gMonthDay XFORMS-INVALID (gMonthDay) xforms-valid (gMonthDay) gDay XFORMS-INVALID (gDay) xforms-valid (gDay) gMonth XFORMS-INVALID (gMonth) xforms-valid (gMonth) string XFORMS-INVALID (string) xforms-valid (string) boolean XFORMS-INVALID (boolean) xforms-valid (boolean) base64Binary XFORMS-INVALID (base64Binary) xforms-valid (base64Binary) hexBinary XFORMS-INVALID (hexBinary) xforms-valid (hexBinary) float XFORMS-INVALID (float) xforms-valid (float) decimal XFORMS-INVALID (decimal) xforms-valid (decimal) double XFORMS-INVALID (double) xforms-valid (double) anyURI XFORMS-INVALID (anyURI) xforms-valid (anyURI) QName XFORMS-INVALID (QName) xforms-valid (QName)