Page History

...

• Continuous delivery of data points according to a predefined agreement
• Not only a different container type.  It deals more with the delivery method (constant stream compared to atomic message)
• Does not have a fixed start/end time
• Delivers a stream of Records
• + could also deliver side-band information (e.g. Job information)
• Is analogous to the delivery of a Subscription for protocols that support subscriptions.

TimeStamp

NOTE:  The exact format of all of these may differ when these concepts are translated to different protocols or languages.
As a starting point however, let's propose to use ISO 8601 standard format, with fractional seconds (e.g. microseconds) and always UTC (Zulu) time zone, if a TimeStamp is given in text format.  For other purposes such as binary formats, more efficient encodings should be considered. 

Real, "Wall clock time"

•    "ts" : "2020-01-10T02:59:43.492750Z # Zulu time, ISO std with microseconds

Relative to a previously predefined time stamp reference:

• "rts" : "T02:59:43.100044"    # Similar to ISO 8610.  Years/month/dates can be omitted if zero
• "rts" : "02:59:43.100044"      # Alternative, also OK
• "rts2", "rts3", ...                      # If more than one relative time stamp reference had been previously agreed

...

Examples, in JSON

PlainRecord:

...

TimestampedRecord:

{
   "ts" : "20200319123245Z123456"2020-01-10T02:59:43.491751Z   # Zulu time, ISO std + microsecond - FIXME:format is not checkedwith microseconds
   "value" : "42 "
}

SpecifiedRecord:

...