Hi Thierry,
Can you explain why you are providing DEFINE-XML as a Standard OID in your define.xml? As you stated, this cannot be referenced in the define.xml. In general, excluding it resolves both DD0138/9. While DEFINE-XML is in the CTSTDTYP Codelist, DEFINE-XML is not a Publishing Set value under Section 4.1.1 of the Define-XML 2.1 Specification for Type = CT.
Kind regards,
Matt
Hi Matt,
Thanks for your answer.
I included the Define-XML CT reference because:
- It is included in both define.xml examples (SDTM and ADaM) that come with the define 2.1 specification
- It allows a quicker understanding of the define CT version used than the def:DefineVersion=“2.1.7” tiny version (“7” means “2024-03-29”)
- We reference ORIGINT – Origin Type from QORIG when the SUPP datasets are paired with define 2.1
Kind regards,
– Thierry
Hi Thierry,
Great! Thanks for the background information. I will discuss this with out define team, but for now the rule simply will be explained.
Kind regards,
Matt
I also met DD0139 issue and not found good method to fix it. Detail description is “Only Standards that are referenced from a Dataset or Codelist should be included in Define.xml. Define-XML specification represents Standards as def:Standard elements within the def:Standards element.”. Has anyone encountered this issue before? Could you suggest how to resolve it?
Standard part in define.xml:
This is another bug that I found, in the same circumstances as DD0138.
I get this message:
DEFINE DD0139: 1 Warning - Standard ‘DEFINE-XML’ is not referenced
| Standard OID, Standard Type, Standard Name = std.ct.define, CT, DEFINE-XML | Standard ‘DEFINE-XML’ is not referenced (Warning)
This is a false positive: the Define-XML CT cannot be referenced inside the define.xml itself, as far as I understand from the specification.