In order for engineering tools to work, companion specifications using dictionary references (like PA-DIM) create a UaNodeSet containing the dictionary references they are using.
The Best Practice Whitepaper already describes this process.

An issue that occurred recently was from people who were mechanically picking a UaNodeSet out of a repository and did not find the right version or publication date.
The question is: What to put in as Version, PublicationDate and SematicVersion in those UaNodeSets and how should the reference of such UaNodeSets from another UaNodeSet should look like.
There is no real version or publication date, but more a list of Objects representing IRDIs which are defined and maybe versioned in a completely different place.

Potential solution: Everybody should always use the same Version and PublicationDate, potentially some "strange" values like 0.0.0 and 1-1-1970. And maybe we should recomend to leave out the NamespaceMetadata Object in the UaNodeSet.