Always supply millisecond component of timestamp in response payloads
OCS returns a timestamp with no ‘milliseconds component’ if milliseconds is zero. This places a (small) burden on the client application to code for both possibilities … milliseconds present in the timestamp field and milliseconds not present. This places a small burden on some clients such that they have to code for both possibilities. It would be nice to have a consistent expression of time in response payloads.