t Thierry
on

 

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.

 

Forums: Define.xml

Matt
on September 25, 2024

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

t Thierry
on September 26, 2024

Hi Matt,

Thanks for your answer.
I included the Define-XML CT reference because:
1) It is included in both define.xml examples (SDTM and ADaM) that come with the define 2.1 specification
2) 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")
3) We reference ORIGINT – Origin Type from QORIG when the SUPP datasets are paired with define 2.1

Kind regards,
-- Thierry

Matt
on September 27, 2024

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

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

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.