I was going to post that there was some trouble with validating the define file as check DD0004 (unknown attribute) fires on the OrderNumber attribute stating that it is unknown while it is part of CRT-DDS, but then I spotted that I typed it as "Ordernumber" rather than "OrderNumber" (note: n vs N).
I reran using "OrderNumber" and checked again: no more firing of DD0004.
So be warned, OpenCDISC treats this as case sensitive. I looked in the CRT-DDS and the ODM specifications and did not find any explicit mentions of this fact, but the casing is very consistently applied in both documents!
Also note: I am using the version BEFORE 1.3!
[It seems DD0007 (unknown element) is also case sensitive]
Well, XML itself is case sensitive with respect to element names and attribute names. This is not specific for ODM or define.xml. A validator has to treat element and attribute names case sensitive.
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.
Hi everybody,
I was going to post that there was some trouble with validating the define file as check DD0004 (unknown attribute) fires on the OrderNumber attribute stating that it is unknown while it is part of CRT-DDS, but then I spotted that I typed it as "Ordernumber" rather than "OrderNumber" (note: n vs N).
I reran using "OrderNumber" and checked again: no more firing of DD0004.
So be warned, OpenCDISC treats this as case sensitive. I looked in the CRT-DDS and the ODM specifications and did not find any explicit mentions of this fact, but the casing is very consistently applied in both documents!
Also note: I am using the version BEFORE 1.3!
[It seems DD0007 (unknown element) is also case sensitive]