define.xml standard checking needs to allow selection of CT version(s)

We ran the CDISC Define-XML-2-0_ReleasePackage20140424\adam\define2-0-0-example-adam.xml through the OpenCDISC Community Validator (standard = define.xml , Configuration = Define 2.0.xml ) and incurred 2 errors which should not be errors.  I have attached the OpenCDISC output.

Both of these “Terminology” errors are due to the tool crosschecking the define.xml’s codelist CDISC code OIDs against the CDISC controlled terminology file.  However, unlike using Validator to validate against the ADaM standard, validating the define.xml standard does not allow the user to specify the CDISC CT version to use.  So it appears that, not only is the most recent version used, but only the SDTM CT file is used (even for a define.xml for ADaM). 

For the first error, DD0027, this codelist code does in fact exist in the ADaM controlled terminology.

For the second error, DD0028, this codelist code does in fact exist in the version of the SDTM CT that was the most recent when the define.xml file was released.  The code has since been demoted, so no longer exists in the most recent SDTM CT version.

Although no errors were incurred when using Validator to check the CDISC define.xml version 2 example for SDTM, obviously the same issues are potential problems.

I would think that user should be able to specify the CT version used for define.xml standard checking.  Please note that both the SDTM and ADaM CT versions used for ADaM define.xml version 2 checking should be able to be specified.  ADaM datasets will include data from SDTM that need to be represented in the define.xml.  The Codelist codes that will be used for the variables from the SDTM will be the SDTM CT codes.