"isInclusive" parameter and EndPeriod value in generated actual content constraints
In the Actual content constraints that are generated by .Stat Suite during the data uploads, the isInclusive parameter in time ranges is set to "false" by default. Thus, for the time range 1990-2017 it will be:
<common:StartPeriod **isInclusive="false"**>1990-01-01T00:00:00</common:StartPeriod>
<common:EndPeriod **isInclusive="false"**>2017-01-01T00:00:00</common:EndPeriod>
IsInclusive is defined as:
The isInclusive attribute, when true, indicates that the time period specified is included in the range.
According to the schema specification, its default value is "true".
I think it would be more logical to use isInclusive="true" when generating the constraints.
Another question is about the "EndPeriod", which in case of year "2017" should end on 31st of December on 23:59:59, and not on 1st of January 2017, e.g:
<common:EndPeriod isInclusive="true">2017-12-31T23:59:59</common:EndPeriod>
Alternatively the EndPeriod can be on 01.01.2018 (Not Inclusive).
<common:EndPeriod isInclusive="false">2018-01-01T00:00:00</common:EndPeriod>
The example is taken from the Content Constraint generated for AIR_EMISSIONS_DF.