- clock face time, lossy. non geo-aware/geo-normalized value. generally a scalar, or partial date time. value may not be robust if consumed outside of reporter’s locale

- moment in time, geo-aware. scalar + geo-value, such as TZ or UTC offset

I (mediocrely) wrote about this years ago: https://cdaringe.com/managing-application-dates