The OpenCDISC 1.4 configuration files has things like:
<val:Varlength ID="SD1080" Variable="%Variables.Type.Basic:Char%" Minimum="2" Maximum="5" Message="%Variable% variable length is too long for actual data" Description="Variable length should be assigned based on actual stored data to avoid to minimize file size. Datasets should be resized to the maximum length used prior to splitting." Category="Metadata" Type="Information"/>
However, this validation type (Varlength) is not represented in the schema (resources/schema/validator1-0-0.xsd).
Are there plans to keep the schema in synch with the configuration files, so that the configuration files validate against the schema?
Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.
The OpenCDISC 1.4 configuration files has things like:
<val:Varlength ID="SD1080" Variable="%Variables.Type.Basic:Char%" Minimum="2" Maximum="5" Message="%Variable% variable length is too long for actual data" Description="Variable length should be assigned based on actual stored data to avoid to minimize file size. Datasets should be resized to the maximum length used prior to splitting." Category="Metadata" Type="Information"/>
However, this validation type (Varlength) is not represented in the schema (resources/schema/validator1-0-0.xsd).
Are there plans to keep the schema in synch with the configuration files, so that the configuration files validate against the schema?