Page History

...

A: The reason would be to optimize the performance and bandwidth.  In other words, don't transfer what is not needed for a certain case.  If a timestamp is not needed, we should make sure we support transferring data without providing a timestamp, for example.

Record Subtypes: 
PlainRecord,TimeStampedRecord,

• PlainRecord ← there is no need to differentiate it from Record unless we want the top parent type (Record) to be "abstract" and only allow subtypes be concrete types.  
  As far as I can see there is nothing to gain from that.  So we can consider Record to be a concrete parent type and  Record == Plain Record
• TimeStampedRecord
• ToleranceTimeStampedRecord, ...

...

• ?

+ Record types which specify the signal name inside: 

• SpecifiedPlainRecord

...

• SpecifiedTimeStampedRecord, etc.

Main "Container" – name for this?   Measurement? 

...

• "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(Plain) Record:

{
   "value" : " 100.54"
}

...