I’m not part of the Pinnacle21 team, but just want to say that these are OIDs and they have a technical role in Define-XML. They are used to connect different elements within Define-XML file. OID values must be unique and there is no requirement for them to be human-readable. So answering your question - yes, it is a normal OID and does not need to be changed.
I never heard of a regulatory agency giving a comment regarding this. Define-XML 2.0 spec explicitly states the following (section 3.5.1):
Attributes whose names end with “OID”, (or sometimes called “OIDs”), are used to uniquely identify the different metadata objects. The Define-XML specification does not mandate a format for OIDs. OIDs are only intended as a mechanism for unambiguously linking between a definition of an object and references to it. The examples in this document use prefixes at the start of OIDs to indicate the object type, however this is not required. It is equally valid to use randomly generated identifiers.
I’m not part of the Pinnacle21 team either …
To extend to Lex’s answer, the OIDs (Object Identifiers) generated (like “1ea50245ec370ef4afdec5db2faea0cfccfd14f4”) by the Pinnacle tool, look very much like UUIDs, but then with the dashes removed. UUIDs are worldwide unique identifiers, generated by computers, based on the current time, and e.g. the MAC address of your computer.
As Lex already stated, OIDs in define.xml (and its parent standard, the CDISC ODM) are arbitrary, and do not have a meaning on themselves: for or each unique object, there must be a unique OID.
I also think the OIDs are never displayed when applying the stylesheet, but I need to check.
