Hi,

Thanks for the notice. ‘Identifiers’ etc. are related to the core information model, and thus directly on files provided by the OPC Foundation https://github.com/OPCFoundation/UA-Nodeset/, thus SDK basically takes them as-is for code-generation, which then e.g. creates DataTypeIdentifiers.

OPC Foundation does time to time add new features, but also fix issues (that people report on https://mantis.opcfoundation.org/). I believe the removal of ‘Date’ has been one such instance of fixing (though I cannot right now find the issue for that). At least (1.04) https://raw.githubusercontent.com/OPCFoundation/UA-Nodeset/v1.04/Schema/NodeIds.csv does show
Time,292,DataType
Date,293,DataType
UtcTime,294,DataType

but (1.05) https://raw.githubusercontent.com/OPCFoundation/UA-Nodeset/v1.04/Schema/NodeIds.csv only shows
UtcTime,294,DataType

thus, they have been removed. However, as far as I’m aware, the ‘Date’ and ‘Time’ have never been part of the spec text https://reference.opcfoundation.org/Core/Part3/v104/docs/8 in any version. That is that it has been just an error that they have ever existed in the csv. The UtcTime does exist, but I think it was attempted to also be removed in the past as it is basically useless as the base DateTime is already specified to be in UTC when transferred as binary betweeen client-server. The ‘Time’ and ‘Date’ should have been also subtypes of ‘DateTime’, thus they would always be transferred as ‘DateTime’ in binary. Thus, you should be able to just swap the usage of ‘Date’ to ‘DateTime’. Obviously if it is used in a model this does change the NodeId, which could cause issues, but say if this is just e.g. a DataType Attribute value then using DateTime should work.

If you have or know an information model (a NodeSet2 XML file basically) that uses the ids 292/293, then I think it would be best if you contact the OPC Foundation directly e.g. at https://opcfoundation.org/forum/.