You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the schema, for boolean values the type xs:boolean is used. The value space of sx:boolean is "true" and "false" together with "1" for true and "0" for false.
Currently, in parse_boolean, the value is only checked against "1" where it also should be checked against "true".
The text was updated successfully, but these errors were encountered:
Thank you for your report. According to ETG 2000 v1.0.13 the data type boolean has the allowed values 0 and 1. I will check if this definition is aligned with the xs:boolean definition.
I know, the v1.0.14 version I have says the values 0 and 1 are to use but then in the descriptive text they often refer to true and false (e.g. for Data/@AdaptAutomatically, there they explicitly show a @AdaptAutomatically = “true”).
In addition I have a couple of example ESI files downloaded from Beckhoff, there they use 'true' for examlple for Device/Mailbox/DataLinkLayer which is a boolean, too.
So for me it looks like are both styles are ok.
I will check with the Conformance Test Tool and some other checkers just to be sure the tools are working properly. The fix will likely be in the next release.
Eventually the conformance test will complain about the use of "true"
and "false" but the XML specification for xs:boolean is also valid. So
we just handle both cases.
Fixes Github Issue #18
According to the schema, for boolean values the type xs:boolean is used. The value space of sx:boolean is "true" and "false" together with "1" for true and "0" for false.
Currently, in parse_boolean, the value is only checked against "1" where it also should be checked against "true".
The text was updated successfully, but these errors were encountered: