Problem and Proposal presented at F2F in Genoa on 2025-09-25:

https://opcfoundation.sharepoint.com/:p:/r/sites/wg.UA/Shared%20Documents/sg.Core/Meetings/2025/2025-09-22%20F2F%20Genoa/2025-09-22%20UAFX%20Timestamps.pptx?d=w891b9ccdcf074557b2b0d0e3e401b99d&csf=1&web=1&e=qdaqmT

Result:
We can expect that we can ‘link’ a PubSub Publisher with an application defined time source (maybe Year 1600-Time)​

​We can transport both our timescales (PTP timescale and ARB timescale) as UtcTime, it just looks ‘old’​
​
We can expect that PubSub stacks can take application generated timestamps (sample time) in the NetworkSetMessage timestamp field (UtcTime, but maybe year 1600) … DataSetMessage-Time must be Wall-Clock​

​We shall not use sourceTimestamp or serverTimestamp of DataValues with ‘Year-1600 Time’​

In case we need to transport ‘Year 1600-Time’ together (other than with NetworkMessages) with DataValues, we could define a wrapper (e.g. structure), containing the ‘Year 1600-Time’ (UtcTime) + DataValue (or find a better way)​

TODO: Let Motion/IO/Instruments decide how to continue, probably Information Model-Group to create a special DataValue for SoE ?