search

FLOIP / flow-results

Open specification for the exchange of "Results" data generated by mobile platforms using the "Flow" paradigm
6 stars 2 forks source link

Add milliseconds to timestamps #4

Closed markboots closed 6 years ago

markboots commented 7 years ago

Suggestion from @nicpottier to add milliseconds to timestamps in response row data.

Opening this issue to document the rationale. Should it be recommended or required? Should it apply to other timestamps (e.g.: the datetime or time question responses?)

pld commented 7 years ago

I'd suggest we recommend it and we have all our examples use it (as Nic mentioned), the more data the better

nicpottier commented 7 years ago

Maybe the recommendation should just be that providers of results should include as much precision as they have and consumers must be able to parse arbitrary precision for timestamps. Consumers can always throw away precision if it doesn't interest them but seems we should encourage producers to not throw away anything they have.

markboots commented 7 years ago

Thumbs up here to Nic's suggestion. Not all systems will have this, but we should encourage preserving any precision that is available. I think it would be nice to allow data sources that don't have this precision to use 2017-07-06T13:56:78-04:00 instead of 2017-07-06T13:56:78.000-04:00.

nicpottier commented 6 years ago

Fractional seconds being optional sounds good me.

markboots commented 6 years ago

Sounds good! Resolved in https://github.com/FLOIP/flow-results/pull/2/commits/9811b832f3c4ce2dd85cebbc186179d388f52f43