Subject: RE: Change draft for #287: default for lastDetectionTimeUtc
I am not sure resurrecting run.startTimeUtc makes sense, please see my most recent reply.
I led us to this situation because I forgot that we removed this property. All things considered, introducing it again seems like it brings more complexity without much incremental value.
I pushed a change draft for Issue #287: “Define default for resultProvenance.lastDetectionTimeUtc”.
In the issue’s discussion thread, Michael and I decided that it made sense to bring back the property run.startTimeUtc. Please read the thread to see how that idea is related to this issue. So we’ve restored that property, and for symmetry, also restored run.endTimeUtc.
We’ll move its adoption at TC #29 on Wednesday December 12th.